Phone.apk is not loading in emulator

by vishnu » Tue, 08 Sep 2009 15:58:23 GMT


Sponsored Links
 i All,

I am porting s3c6410 on emulator (only platform side not kernel). I
removed the hardware dependencies (from hardware folder). when i am
running emulator it's not able to load Phone.apk showing following :

Could not find end-of-central-directory in Zip
D/asset ( 634): failed to open Zip archive '/system/app/Phone.apk'
W/PackageParser( 634): Unable to read AndroidManifest.xml of /system/
app/Phone.apk
W/PackageParser( 634): java.io.FileNotFoundException:
AndroidManifest.xml
W/PackageParser( 634): at
android.content.res.AssetManager.openXmlAssetNative(Native Method)
W/PackageParser( 634): at
android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:
471)
W/PackageParser( 634): at
android.content.res.AssetManager.openXmlResourceParser
(AssetManager.java:439)
W/PackageParser( 634): at
android.content.pm.PackageParser.parsePackage(PackageParser.java:265)
W/PackageParser( 634): at
com.android.server.PackageManagerService.scanPackageLI
(PackageManagerService.java:1759)
W/PackageParser( 634): at
com.android.server.PackageManagerService.scanDirLI
(PackageManagerService.java:1709)
W/PackageParser( 634): at
com.android.server.PackageManagerService.<init>
(PackageManagerService.java:464)
W/PackageParser( 634): at
com.android.server.PackageManagerService.main
(PackageManagerService.java:261)
W/PackageParser( 634): at com.android.server.ServerThread.run
(SystemServer.java:119)

and later it crash:

: Unable to start service Intent
{ action=android.accounts.IAccountsService comp=
{com.google.android.googleapps/
com.google.android.googleapps.GoogleLoginService} }: not found
W/AccountMonitor( 634): Couldn't connect to Intent
{ action=android.accounts.IAccountsService comp=
{com.google.android.googleapps/
com.google.android.googleapps.GoogleLoginService} } (Missing service?)
I/SystemServer( 634): Starting System Content Providers.
I/ActivityThread( 634): Publishing provider sync:
android.content.SyncProvider
I/SystemServer( 634): Starting Battery Service.
I/SystemServer( 634): Starting Hardware Service.
D/qemud ( 547): fdhandler_accept_event: accepting on fd 10
D/qemud ( 547): created client 0xe078 listening on fd 8
D/qemud ( 547): client_fd_receive: attempting registration for
service 'hw-control'
D/qemud ( 547): client_fd_receive: -> received channel id 2
D/qemud ( 547): client_registration: registration succeeded for
client 2
W/HAL ( 634): load: module=/system/lib/hw/lights.goldfish.so
error=Cannot find library
W/HAL ( 634): load: module=/system/lib/hw/lights.s3c6410.so
error=Cannot find library
W/HAL ( 634): load: module=/system/lib/hw/lights.default.so
error=Cannot find library
E/ActivityThread( 634): Failed to find provider info for settings
W/dalvikvm( 634): threadid=31: thread exiting with uncaught exception
(group=0x4000fe70)
E/AndroidRuntime( 634): Uncaught handler: thread PowerManagerService
exiting due to uncaught exception
E/AndroidRuntime( 634): *** EXCEPTION IN SYSTEM PROCESS. System will
crash.
E/AndroidRuntime( 634): java.lang.NullPointerException
E/AndroidRuntime( 634): at android.content.ContentQueryMap.<init>
(ContentQueryMap.java:65)
E/AndroidRuntime( 634): at
com.android.server.PowerManagerService.initInThread
(PowerManagerService.java:418)
E/AndroidRuntime( 634): at com.



Other Threads

1. Keeping an Activity alive instead of destroying it?

Hi Mark,

It's only causing a slight annoyance to the user. Although the UI
takes about 1.5 seconds to completely build, I am doing a staggered
load. This lets the user see content immediately, but they're
wondering why every time they leave the search activity, then come
back, all the content must be reloaded. The actual search data is kept
in a global static singleton, no problem there, just the UI is kind of
heavy to keep regenerating around it.

This would work better as a tabbed-view in a single Activity, but my
spec calls for the search screen to be in a separate Activity. I like
keeping it separated too, just wish I could pause the app to resume it
later since I'm sure it's an Activity users will keep coming back to
while using the app.

Thanks








-- 

2. Tapping activity after startActivityForResult

Hi,

I have two buttons in an activity/view A0, b1 and b2 that respectively
starts (for result) the activities A1 and A2. After tapping/clicking
b1 I quickly tap b2 aswell. The result will be that both A1 and A2 are
launched. Is there any obvious way to not have this behaviour, i.e. to
"lock" A0? I am thinking of overriding dispatchTouchEvent to consume
everything after the call to startActivityForResult, but it seems a
bit much...

Best regards,
Michael

-- 

3. Sending binary signals on the USB port

4. Programmatically setting the layout_above value

5. How to play two videos gapless using MediaPlayer.

6. New to android and java - Cannot run or debug with eclipse 3.5.1 on windows

7. RSSI like indicator in notification area