Hi,
I was wondering if anyone can help me figuring out what happened to my NST.
I was checking my NST hidden settings menu (NSTHiddenSettings.apk) when I pressed one the generic settings buttons (they appears at the bottom of the menu and they look all the same). One of these buttons initiated a "cleaning" process + reboot that I could not stop.
The end result of this was:
My NST was hanging after the reboot. I resetted to factory settings using NookManager and upgraded to 1.2.2 US firmware (my Nook has originally a 1.2.0 UK firmware), registered the device and re-rooted again: It all went well.
However NookManager "'informed me" that the NookButtons Mod APK was not installed during the rooting process.
I understood why when I tried install more apps. The system would not allow me to because every time I try to install a new apk I get a "memory full" message (mind you: the Nook is just rooted, so plenty of space, in theory).
Moreover, "back"/menu/notifications buttons on the top toolbar disappear when I access the settings menu
I have the feeling the file system is quite messed up (e.g. .orig files that should not be there), however since I do not have a backup copy (yes, silly me!), I cannot verify it. I have copied my Nook filesystem, and I was wondering if you could gather what happened to it and how I can fix it.
Code:
drwxrwx--- system system 1970-01-01 01:00 rom
drwxrwxrwt root root 2019-02-03 20:34 sqlite_stmt_journals
drwxrwxrwx system system 2019-02-03 20:34 sdcard
drwxrwxr-x system sdcard_rw 1970-01-01 01:00 media
drwxrwx--- system cache 2019-02-03 15:09 cache
drwxrwxrwx root root 2019-02-03 20:34 tmp
lrwxrwxrwx root root 2019-02-03 20:34 etc -> /system/etc
drwxrwx--x system system 2019-02-03 20:34 data
-rw-r--r-- root root 324 2019-02-03 15:44 env.txt
-rwxr-x--- root root 128000 2019-02-03 15:44 init
-rwxr-x--- root root 1677 2019-02-03 15:44 init.goldfish.rc
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwxr-x--- root root 2019-02-03 15:44 sbin
drwxr-xr-x root root 1970-01-01 01:00 sys
drwxr-xr-x root root 2019-02-03 15:44 system
-rw-r--r-- root root 118 2019-02-03 15:44 default.prop.orig
-rw-r--r-- root root 118 2019-02-03 15:44 default.prop
-rw-r--r-- root root 118 2019-02-03 15:44 init.rc.orig
-rwxr-x--- root root 19284 2019-02-03 15:44 init.rc
drwx------ root root 2017-05-17 09:47 root
drwxr-xr-x root root 2019-02-03 20:34 dev
NOTE: I have tried to factory-reset it also using the 8 failed boot ups followed by holding both bottom "page left/right" buttons. Nothing. I always end up with the same messed-up configuration.
Can anyone help me?
Marco
You're going to have to dig deeper than that to find out what's what.
First step:
Code:
# df
That will tell you what you have for disk space.
And this is what I've got:
Code:
/dev: 116520K total, 0K used, 116520K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 3655K used, 12460K available (block size 512)
/system: 285583K total, 210512K used, 75071K available (block size 1024)
/data: 808292K total, 64200K used, 744092K available (block size 4096)
/cache: 237987K total, 6263K used, 231724K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
And this is just right after the rooting process. Nothing else installed.
Renate NST said:
You're going to have to dig deeper than that to find out what's what.
First step:
Code:
# df
That will tell you what you have for disk space.
Click to expand...
Click to collapse
Well, you've got the space.
The "memory full" thing might be a red herring.
The package installer copies the file to somewhere temporary before it ends up in /data/app.
It could be a permission problem.
How are you installing the app? With adb install?
Use a second window running adb logcat and look for anything that happens.
In the original NookManager thread similar issues were discussed with early versions starting about here. There are some suggested work-arounds, including adb install (useful, but annoying) and, if I recall correctly, some attempts at patches for the permissions issue.
I have seen questions regarding the "out of space" issue from time to time but it took awhile for them to bubble up to the top in my brain. Why this happens with some installations, I have no idea.
Renate,
this is interesting: [email protected] always installed the apps with PackageManager, and that's what I did this time too, and that's what gave me the "memory full" error.
However, I have now used adb install and things went pretty smooth. I installed NookMods from NM and this is the log:
Code:
D/AndroidRuntime( 2112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 2112): Heap size: -Xmx64m
D/AndroidRuntime( 2112): CheckJNI is OFF
D/dalvikvm( 2112): creating instr width table
D/AndroidRuntime( 2112): --- registering native functions ---
I/NATIVE-EPD( 2112): framebuffer_handle: 17
D/PackageParser( 788): Scanning package: /data/app/vmdl35313.tmp
I/PackageManager( 788): /data/app/vmdl35313.tmp changed; unpacking
D/installd( 745): DexInv: --- BEGIN '/data/app/vmdl35313.tmp' ---
D/dalvikvm( 2125): creating instr width table
D/dalvikvm( 2125): DexOpt: load 32ms, verify 151ms, opt 7ms
D/installd( 745): DexInv: --- END '/data/app/vmdl35313.tmp' (success) ---
I/installd( 745): move /data/dalvik-cache/[email protected]@[email protected] -> /data/dalvik-cache/[email protected]@[email protected]
D/PackageManager( 788): New package installed in /data/app/org.nookmods.ntmm.apk
D/AndroidRuntime( 2112): Shutting down VM
D/dalvikvm( 2112): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 2112): DestroyJavaVM shutting VM down
D/dalvikvm( 2112): HeapWorker thread shutting down
D/dalvikvm( 2112): HeapWorker thread has shut down
D/jdwp ( 2112): JDWP shutting down net...
I/jdwp ( 2112): adbd disconnected
D/dalvikvm( 2112): VM cleaning up
W/ResourceType( 788): Resources don't contain package for resource number 0x7f060001
I/AmazonAppstore.UpdateService( 874): Self-updating enabled: true
D/AmazonAppstore.UpdateService( 874): Adding self-update command to UpdateService
D/AmazonAppstore.UpdateService( 874): Received action: com.amazon.mas.client.framework.UpdateService.APP_WAS_INSTALLED from intent: Intent { act=com.amazon.mas.client.framework.UpdateService.APP_WAS_INSTALLED cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService (has extras) }
D/InstallReceiver( 1444): org.nookmods.ntmm
D/dalvikvm( 2112): LinearAlloc 0x0 used 625764 of 5242880 (11%)
D/dalvikvm( 788): GC freed 15270 objects / 1017944 bytes in 70ms
and the adb install message:
Code:
adb install org.nookmods.ntmm.apk
822 KB/s (170731 bytes in 0.202s)
pkg: /data/local/tmp/org.nookmods.ntmm.apk
Success
rm failed for -f, Read-only file system
May this be the problem encountered by PackageManager (and not adb install):
Code:
rm failed for -f, Read-only file system
------------------------
Incidentally, logcat keeps throwing this connectivity error at me, even though I actually registered the device succcessfully:
Code:
I/BnCloudReqMgr( 837): BnCloudRequest Service: starting now
W/ActivityManager( 788): Unable to start service Intent { act=com.bn.cloud.IRequestHandler }: not found
E/GPBRequestHelper( 837): Cannot get handle on BN Cloud Request Service
E/GPBRequestHelper( 837): com.bn.cloud.ServiceUnavailableException: Cannot bind with service: Context.bindService() failed
E/GPBRequestHelper( 837): at com.bn.cloud.RequestManagerImpl$BnCloudServiceConnection.<init>(RequestManagerImpl.java:255)
E/GPBRequestHelper( 837): at com.bn.cloud.RequestManagerImpl.<init>(RequestManagerImpl.java:217)
E/GPBRequestHelper( 837): at com.bn.cloud.BnCloudRequestManager.getRequestHandler(BnCloudRequestManager.java:29)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper.obtainBnCloudRequestHandler(GPBRequestHelper.java:110)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper.access$300(GPBRequestHelper.java:18)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper$3.handleMessage(GPBRequestHelper.java:148)
E/GPBRequestHelper( 837): at android.os.Handler.dispatchMessage(Handler.java:99)
E/GPBRequestHelper( 837): at android.os.Looper.loop(Looper.java:123)
E/GPBRequestHelper( 837): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/GPBRequestHelper( 837): at java.lang.reflect.Method.invokeNative(Native Method)
E/GPBRequestHelper( 837): at java.lang.reflect.Method.invoke(Method.java:521)
E/GPBRequestHelper( 837): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/GPBRequestHelper( 837): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/GPBRequestHelper( 837): at dalvik.system.NativeStart.main(Native Method)
Renate NST said:
Well, you've got the space.
The "memory full" thing might be a red herring.
The package installer copies the file to somewhere temporary before it ends up in /data/app.
It could be a permission problem.
How are you installing the app? With adb install?
Use a second window running adb logcat and look for anything that happens.
Click to expand...
Click to collapse
We have here a total of three badly worded/misleading errors.
"Memory full"
It isn't.
"rm failed for -f"
They are trying to rm -f on something but the error message is just presuming what is immediately after "rm" must be the file name.
They didn't think that there could be some flags after "rm".
"Resources don't contain package for resource number 0x7f060001"
You're missing a resource that is referenced in some other resource (or AndroidManifest).
It's not a resource that is referenced in the code because that would be a runtime error.
The "7f" tells you that it's a user-supplied resource, the "06" tells you not much because they are issued sequentially.
My bet, probably a string referenced in AndroidManifest.
Link, please, to the apk that gives you this error.
Here it is, attached.
It is the version of nookmods contained in NookManager 0.50. (NookManager/files/data/app/org.nookmods.ntmm.apk)
NM does not install it already when I try to root the Nook. (It throws a "Nook Mods not installed" message)
Renate NST said:
We have here a total of three badly worded/misleading errors.
"Memory full"
It isn't.
"rm failed for -f"
They are trying to rm -f on something but the error message is just presuming what is immediately after "rm" must be the file name.
They didn't think that there could be some flags after "rm".
"Resources don't contain package for resource number 0x7f060001"
You're missing a resource that is referenced in some other resource (or AndroidManifest).
It's not a resource that is referenced in the code because that would be a runtime error.
The "7f" tells you that it's a user-supplied resource, the "06" tells you not much because they are issued sequentially.
My bet, probably a string referenced in AndroidManifest.
Link, please, to the apk that gives you this error.
Click to expand...
Click to collapse
Related
Is it possible to emulate an android ROM on a computer?
If you grab the SDK, you can run any version of Android in the emulator. If you want to run an actual ROM you will need to create an image of /system (as system.img) and replace that with those in the SDK folder.
thanks alot! that helped me alot
and yes, i want to run an actual ROM. what filesystem does it have to be?
was thinking about something like...
(cd PATH)
dd if=/dev/zero of=system bs=1024 count=#KB_needed
losetup /dev/loop0 system
mkfs -f FS /dev/loop0
(mkdir /mnt/system)
mount /dev/loop0 /mnt/system/
cp -a system /mnt/system/
umount /mnt/system/
losetup -d /dev/loop0
do you know any good tools for this exept for dd?
Never tried so I honestly don't know, you sound like you know a lot more than me about creating/mounting images than me, so it's probably best to use your judement. The easiest way is just to make a nadroid back backup, flash the ROM you want to test, nadroid that and grab system.img, revert to your old nandroid backup. It's tedious, and it doesn't help if you want to test a ROM before flashing, but that's the only method I've heard people use.
okay. thanks
HTC Sense UI system.img
Does anybody know where I can download a system.img for a HTC with Sense UI (Hero for example)? I have been looking for ages with no luck.
My app is not working on a customers Hero and I am trying to find a Hero system.img to run in the emulator so I can work out why it fails on this phone.
I dont own a Hero, so am unable to extract my own system.img.
You can get HTC official ROMs here:
http://forum.xda-developers.com/showthread.php?t=559622
if you've got a windows computer you probably could extract the content of this exe file and then try to follow my previous instructions to make the system.img.
And if you don't have an unix/linux box.. You could send the content of the exe file to me, if you are able to extract the data in it. (I'm in China with a netbook atm and not able to extract the exe file with my limited tools). Then I could try to make you a system.img
I tried that, but without an HTC phone connected to the PC USB the exe wont extract.
I take that back. I found the files in my temp folder. I have extracted ROM.zip including the system.img into the avd folder, but the emulator is failing to bring it up.
could you upload that zip file here or on rapidshare? then i could have a look at it
Here is the rom.zip file from RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe:
rom.zip
Other people must be doing this kindof thing to test their apps?
Here is the logcat. It looks like the sytem process is starting to come up, then fails. This repeats over and over.
12-16 18:34:20.945: INFO/SystemServer(113): Starting telephony registry
12-16 18:34:20.975: INFO/SystemServer(113): Starting Package Manager.
12-16 18:34:21.056: INFO/Installer(113): connecting...
12-16 18:34:21.075: INFO/installd(33): new connection
12-16 18:34:21.205: INFO/PackageManager(113): Got library com.google.android.maps in /system/framework/com.google.android.maps.jar
12-16 18:34:21.225: INFO/PackageManager(113): Got library com.google.android.gtalkservice in /system/framework/com.google.android.gtalkservice.jar
12-16 18:34:21.265: INFO/PackageManager(113): Got library com.htc.framework in /system/framework/com.htc.framework.jar
12-16 18:34:21.515: INFO/PackageManager(113): Got library android.awt in /system/framework/android.awt.jar
12-16 18:34:21.535: INFO/PackageManager(113): Got library android.test.runner in /system/framework/android.test.runner.jar
12-16 18:34:21.535: INFO/PackageManager(113): Got library com.android.im.plugin in /system/framework/com.android.im.plugin.jar
12-16 18:34:21.545: INFO/PackageManager(113): Got library com.htc.android.pimlib in /system/framework/com.htc.android.pimlib.jar
12-16 18:34:21.565: INFO/PackageManager(113): Got library com.htc.android.easopen in /system/framework/com.htc.android.easopen.jar
12-16 18:34:21.565: INFO/PackageManager(113): Got library com.scalado.util.ScaladoUtil in /system/framework/com.scalado.util.ScaladoUtil.jar
12-16 18:34:22.596: DEBUG/dalvikvm(113): GC freed 4273 objects / 216216 bytes in 302ms
12-16 18:34:23.476: ERROR/PackageManager(113): Adding duplicate shared user, keeping first: android.uid.shared
12-16 18:34:23.526: ERROR/PackageManager(113): Occurred while parsing settings at line -1, column -1
12-16 18:34:23.546: ERROR/PackageManager(113): Adding duplicate shared user, keeping first: com.htc.rosie.uid.shared
12-16 18:34:23.596: ERROR/PackageManager(113): Occurred while parsing settings at line -1, column -1
12-16 18:34:23.746: ERROR/PackageManager(113): Bad package setting: package com.android.providers.contacts has shared uid 10008 that is not defined
12-16 18:34:23.746: ERROR/PackageManager(113): Bad package setting: package com.android.launcher has shared uid 10008 that is not defined
12-16 18:34:23.756: ERROR/PackageManager(113): Bad package setting: package com.android.googlesearch has shared uid 10008 that is not defined
12-16 18:34:23.766: ERROR/PackageManager(113): Bad package setting: package com.android.inputmethod.latin has shared uid 10008 that is not defined
12-16 18:34:23.786: ERROR/PackageManager(113): Bad package setting: package com.htc.MusicWidget has shared uid 10047 that is not defined
12-16 18:34:23.816: ERROR/PackageManager(113): Bad package setting: package com.android.contacts has shared uid 10008 that is not defined
12-16 18:34:23.836: ERROR/PackageManager(113): Bad package setting: package com.android.providers.userdictionary has shared uid 10008 that is not defined
12-16 18:34:23.846: ERROR/PackageManager(113): Bad package setting: package com.android.providers.im has shared uid 10008 that is not defined
12-16 18:34:23.896: INFO/dalvikvm(113): DexOpt: Some deps went away
12-16 18:34:23.926: ERROR/dalvikvm(113): /system/framework/com.scalado.util.ScaladoUtil.jar odex has stale dependencies
12-16 18:34:23.926: ERROR/dalvikvm(113): odex source not available -- failing
12-16 18:34:23.926: WARN/dalvikvm(113): threadid=15: thread exiting with uncaught exception (group=0x40013140)
12-16 18:34:23.936: ERROR/AndroidRuntime(113): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
12-16 18:34:23.956: ERROR/AndroidRuntime(113): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
12-16 18:34:23.966: ERROR/AndroidRuntime(113): dalvik.system.StaleDexCacheError: /system/framework/com.scalado.util.ScaladoUtil.jar
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:419)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.PackageManagerService.main(PackageManagerService.java:261)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.ServerThread.run(SystemServer.java:126)
12-16 18:34:24.006: ERROR/AndroidRuntime(113): Crash logging skipped, no checkin service
12-16 18:34:24.006: ERROR/AndroidRuntime(113): Crash logging skipped, no htc checkin service
12-16 18:34:24.036: INFO/Process(113): Sending signal. PID: 113 SIG: 9
12-16 18:34:24.066: INFO/Zygote(102): Exit zygote because system server (113) has terminated
12-16 18:34:24.086: INFO/ServiceManager(26): service 'usagestats' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'SurfaceFlinger' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'power' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'batteryinfo' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'telephony.registry' died
12-16 18:34:24.106: ERROR/installd(33): eof
12-16 18:34:24.106: ERROR/installd(33): failed to read size
12-16 18:34:24.106: INFO/installd(33): closing connection
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.audio_flinger' died
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.player' died
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.camera' died
12-16 18:34:25.096: DEBUG/AndroidRuntime(130): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
12-16 18:34:25.116: DEBUG/AndroidRuntime(130): CheckJNI is ON
12-16 18:34:25.686: DEBUG/AndroidRuntime(130): --- registering native functions ---
12-16 18:34:25.956: INFO/(129): ServiceManager: 0xac38
12-16 18:34:25.956: DEBUG/AudioHardwareInterface(129): Running in emulation - using generic audio driver
12-16 18:34:25.956: INFO/AudioFlinger(129): Create BTIPSA2dpInterface
12-16 18:34:25.966: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpInterface 1.0.0.0.
12-16 18:34:25.966: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpInterface:penOutputStream 1, 0, 0
12-16 18:34:25.966: INFO/(129): Creating ashmem region names /data/btips/btips_mm_shm size 20480
12-16 18:34:25.966: INFO/AudioFlinger(129): AudioFlinger's thread ready to run for output 0
12-16 18:34:25.986: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpStreamOut::set 1, 0, 0
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 0 2 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 1 2 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 2 1 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setMode to mode 0
12-16 18:34:25.996: INFO/AudioFlinger(129): AudioFlinger's thread ready to run for output 1
12-16 18:34:26.006: INFO/CameraService(129): CameraService started: pid=129
12-16 18:34:26.086: DEBUG/(130): ======================== register_android_graphics_Canvas, g_haveProfilerFile=0
12-16 18:34:26.476: INFO/Zygote(130): Preloading classes...
12-16 18:34:26.486: DEBUG/dalvikvm(130): GC freed 786 objects / 43096 bytes in 9ms
12-16 18:34:26.746: DEBUG/dalvikvm(130): GC freed 275 objects / 17264 bytes in 6ms
12-16 18:34:26.956: DEBUG/dalvikvm(130): GC freed 200 objects / 12200 bytes in 8ms
12-16 18:34:27.096: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.346: DEBUG/dalvikvm(130): Added shared lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.356: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.356: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.366: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.366: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.386: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.386: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.396: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.396: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.426: DEBUG/dalvikvm(130): GC freed 467 objects / 29272 bytes in 10ms
Click to expand...
Click to collapse
Anybody?
Someone must have emulated HTC Touch / Sense UI?!
Okay... After unzipping and manipulating a 2.1 ROM to my liking; I have now resigned it...
Can someone please explain to me how I would go about testing it with the Android SDK Emulator?
I have already created a 2.1 AVD and the emulator loads to the "ANDROID" screen...
What must I do to test out this newly packaged ROM file?
I was working on an app and after I uploaded a *.ttf to the assets folder I went to run my app in the android emulator. It uploaded okay but during installation I got
[2011-08-03 14:36:37 - katastroapp] Installing katastroapp.apk...
[2011-08-03 14:36:40 - katastroapp] Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE
[2011-08-03 14:36:40 - katastroapp] Please check logcat output for more details.
[2011-08-03 14:36:41 - katastroapp] Launch canceled!
Here is my logcat
08-03 21:34:12.316: DEBUG/SntpClient(59): request time failed: java.net.SocketException: Address family not supported by protocol
08-03 21:36:37.893: DEBUG/AndroidRuntime(395): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
08-03 21:36:37.893: DEBUG/AndroidRuntime(395): CheckJNI is ON
08-03 21:36:38.183: DEBUG/AndroidRuntime(395): --- registering native functions ---
08-03 21:36:39.613: DEBUG/dalvikvm(247): GC_EXPLICIT freed 158 objects / 7584 bytes in 80ms
08-03 21:36:39.793: DEBUG/dalvikvm(59): GC_EXPLICIT freed 1624 objects / 73120 bytes in 145ms
08-03 21:36:39.904: DEBUG/AndroidRuntime(395): Shutting down VM
08-03 21:36:39.904: DEBUG/dalvikvm(395): Debugger has detached; object registry had 1 entries
08-03 21:36:39.943: INFO/AndroidRuntime(395): NOTE: attach of thread 'Binder Thread #3' failed
08-03 21:39:12.383: DEBUG/SntpClient(59): request time failed: java.net.SocketException: Address family not supported by protocol
If anyone knows whats up with that I would be greatly helped.
I figured it out, I just didnt give my emulator enough memory. stupid easy fix.
I think this one is definitely needed for this forum. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Don't be a noob. Be a newbie..!!
Details here.
Great Guide! Should become a sticky.
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Prawesome said:
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Click to expand...
Click to collapse
I said i am no expert. That doesn't mean i cannot take, read or understand logcat..!!
Don't be a noob. Be a newbie..!!
Details here.
This thread is perfect to be a sticky in the Android Development Section.
Newcommers should know how to properly report bugs. I also leave a redirect in the Original Android Development.
I rather use ddms for all
Command prompt is the most basic thing same old Windows
Sent from my GT-P7300 using xda app-developers app
helped me out. Thanks
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Click to expand...
Click to collapse
And it colours out errors according to their priority
I am a potato, problem?
Thanks bro
Sent from my GT-S5830 using Tapatalk 2
Extremely useful,
thank you!
However, catlog force closes when I added it as system app.
How can i get application specific logcat like i want to get logcat of systemui only
Really helpful!
Aman
Wysłane z mojego GT-I8190 przy użyciu Tapatalka
Thanks Sir...its helped me a lot..about understanding logcat
---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------
Thanks Sir...its helped me a lot..about understanding logcat
I'm building a new version of the Alegen rom, but i have found this bug with cache!
I've found a first solution, i'va increased cache partition. But i was wondering if there is an other solution that would be better that mine.
this is the logcat with the error in cache.
HTML:
D/dalvikvm( 468): Zip inflate: partial write (will retry): (8152 of 32768)
E/dalvikvm( 468): Zip inflate: write failed: No space left on device
E/dalvikvm( 468): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 468): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 468): opt header write failed: No space left on device
I/dalvikvm( 468): Unable to open or create cache for /system/framework/android.policy.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 468): Unable to process classpath element '/system/framework/android.policy.jar'
E/dalvikvm( 468): opt header write failed: No space left on device
I/dalvikvm( 468): Unable to open or create cache for /system/framework/services.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 468): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 468): opt header write failed: No space left on device
I/dalvikvm( 468): Unable to open or create cache for /system/framework/core-junit.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 468): Unable to process classpath element '/system/framework/core-junit.jar'
E/JNIHelp ( 468): Native registration unable to find class 'android/debug/JNITest'
OK so I have Magic 2014 on my tablet, version 1.2.0. I installed it from Amazon Appstore because it worked, whereas Play Store kept throwing errors at me while downloading the extra content. And hence, the in-app content purchases I've made have also been through Amazon.
This evening I tried upgrading the app to 1.4.0 from Amazon. It went through the entire 1.5 GB download, commenced the install... and then promptly rebooted. The app is still sitting at version 1.2.0.
I found the apk file cached in /sdcard/Android/data/files/apks. So I attempted to install from there. Again after about a minute it rebooted.
So, next, I monitored with adb logcat while doing the install. There was a lot of gunk in the log from other apps, so I tried again while enabling Developer Options "Don't keep activities". It was still too much text to monitor in a Command Prompt window, so I tried one more time using:
adb logcat > magic-crash.txt
to save in a text file. Here are the critical moments:
I/ActivityManager( 8603): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 17478
I/ActivityManager( 8603): Start proc com.android.packageinstaller for activity com.android.packageinstaller/.PackageInstallerActivity: pid=17705 uid=10044 gids={50044, 1028}
I/ActivityManager( 8603): START u0 {dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 17705
I/ActivityManager( 8603): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=17730 uid=10013 gids={50013, 1028, 1015, 1023, 2001}
W/ActivityManager( 8603): No content provider found for permission revoke: file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/ActivityManager( 8603): Start proc com.android.vending for broadcast com.android.vending/com.google.android.vending.verifier.PackageVerificationReceiver: pid=17744 uid=10047 gids={50047, 3003, 1028, 1015}
I/PackageManager( 8603): Verification timed out for file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/PackageManager( 8603): Continuing with installation of file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
W/Watchdog( 8603): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on PackageManager (PackageManager)
W/Watchdog( 8603): PackageManager stack trace:
W/Watchdog( 8603): at android.os.BinderProxy.transact(Native Method)
W/Watchdog( 8603): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResource(IMediaContainerService.java:290)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:7953)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:960)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:593)
W/Watchdog( 8603): at android.os.Handler.dispatchMessage(Handler.java:102)
W/Watchdog( 8603): at android.os.Looper.loop(Looper.java:137)
W/Watchdog( 8603): at android.os.HandlerThread.run(HandlerThread.java:61)
W/Watchdog( 8603): *** GOODBYE!
Does this give any clues to why this won't install without rebooting?
Incidentally I also tried to copy the 1.5 GB apk to my desktop and use "adb install -r". However I get this:
could not allocate buffer for 'magic140.apk'
rm failed for /data/local/tmp/magic140.apk, No such file or directory
Incidentally, I also tried taking a Titanium Backup of the 1.2.0 app and restoring the same version over top of itself. This, too, prompted a reboot with a similar logcat message.
Sent from my Nexus 5 using Tapatalk
Any advice would be appreciated. The same apk has no trouble installing on Nexus 5.
Sent from my Nexus 5 using Tapatalk
Update: I ended up going the brute force route. In TWRP recovery I replaced the existing APK version in /data/app/ with the new one, renamed it appropriately, applied chmod 644 and chown system.system to match. Starting it up now to see if that did the trick. Appears to work.