[Q] Phone reboot after application crash - Galaxy S II Q&A, Help & Troubleshooting

Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
09-30 10:58:51.570 E/android.os.Debug( 1991): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
09-30 10:58:51.595 I/dumpstate(10861): Check if stand-alone
09-30 10:58:51.605 I/dumpstate(10861): begin
09-30 10:58:52.070 W/ActivityManager( 1991): Activity pause timeout for r
(...)
09-30 10:59:36.900 I/Process ( 1991): Sending signal. PID: 1991 SIG: 3
09-30 10:59:36.905 I/dalvikvm( 1991): threadid=3: reacting to signal 3
09-30 10:59:37.005 I/dalvikvm( 1991): Wrote stack traces to '/data/anr/traces.txt'
09-30 10:59:37.005 E/Watchdog( 1991): [email protected] 183
(...)
09-30 11:00:09.125 I/Watchdog_N( 1991): dumpKernelStacks
09-30 11:00:09.145 E/android.os.Debug( 1991): [email protected]umpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_watchdog
09-30 11:00:09.145 E/Watchdog( 1991): WATCHDOG caused by null
(...)
09-30 11:00:21.200 I/Process ( 1991): Sending signal. PID: 1991 SIG: 9
09-30 11:00:21.200 W/Watchdog( 1991): *** WATCHDOG KILLING SYSTEM PROCESS: null
09-30 11:00:21.330 I/binder_sample(10879): [,14,86755,app_process,100]
09-30 11:00:21.330 I/binder_sample(10847): [,2,89808,com.prodtestapp,100]
09-30 11:00:21.330 I/binder_sample( 2219): [com.android.internal.telephony.ITelephonyRegistry, 4,18131,com.android.phone,100]
09-30 11:00:21.330 I/Process (10847): Sending signal. PID: 10847 SIG: 9
09-30 11:00:21.330 E/AndroidRuntime(10847): Error reporting crash
09-30 11:00:21.330 E/AndroidRuntime(10847): android.os.DeadObjectException
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.os.BinderProxy.transact(Native Method)
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.app.ActivityManagerProxy.handleApplication Crash(ActivityManagerNative.java:2950)
09-30 11:00:21.330 E/AndroidRuntime(10847): at com.android.internal.os.RuntimeInit$UncaughtHandle r.uncaughtException(RuntimeInit.java:96)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:693)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:690)
09-30 11:00:21.330 E/AndroidRuntime(10847): at dalvik.system.NativeStart.main(Native Method)
09-30 11:00:21.335 W/Sensors ( 8861): sensorservice died [0x1523e0]
09-30 11:00:21.335 W/Sensors ( 2219): sensorservice died [0xb9640]
(...)
Click to expand...
Click to collapse
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.

dedykjp said:
Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.
Click to expand...
Click to collapse
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see

Jokesy said:
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Click to expand...
Click to collapse
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH

dedykjp said:
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH
Click to expand...
Click to collapse
Flash a custom kernel first, then perform a factory data reset

Jokesy said:
Flash a custom kernel first, then perform a factory data reset
Click to expand...
Click to collapse
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.

dedykjp said:
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.
Click to expand...
Click to collapse
5 minutes ago I discovered a reason of my problem. The reason was rooted phone. After unroot my phone works well. It means that when application crash then I get ANR. Again after root my phone I also get this exception.
Why? Is this only my problem or it's global, but not discovered to now.

Related

not using google voice?

When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.

[Sorta Tutorial] Netflix Stupid Simple Install Explanation-No tutorial needed

The latest version of the Netflix android app (1.2.1) seems to work fine on any 2.3 vibrant roms out of the box, no mods needed!
The previous tutorial is now obsolete, all you need to do is install any 2.3 rom and Netflix should work directly from the market, or you can download it here: http://bit.ly/mA0ar0. Enjoy. Btw, from my personal experience, I have yet to find a 2.2 rom where Netflix actually works, but this shouldn't be a problem if you install a ginger-rom or wait for the official sammy 2.3 update (if it ever happens lmao).
Reserved for OP
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
n1gh7mar3 said:
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
By unlocking the device you mean, actually pressing the lock button on the side of the phone and unlocking it? I know, stupid questions, but I wasn't sure lol. And no problem on the credit or the tutorial, it was the least I could for the guy who discovered how to get netflix running on the Vib!
works!
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
gramlights4 said:
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
Click to expand...
Click to collapse
awesome good to know.
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Edit: got it installed, and it isn't telling me wrong device. But when I log in it flashes white the exits out.. updating flash to see if that helps.
Tynen said:
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Click to expand...
Click to collapse
very nice reference my friend, very nice indeed lmao.
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
I get the same thing with the Bionix-v 1.3.2.
I sure that there will be some work around soon. I am so happy that this app was finally released.
d_bot said:
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Click to expand...
Click to collapse
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
bobofosho123 said:
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
Click to expand...
Click to collapse
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Didn't Google add a DRM framework into GB?? Makes sense that it wouldn't work without that framework.
Tynen said:
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Click to expand...
Click to collapse
it's made by htc. the hardware and software on the nexus s 2.3 is the only similar one.
Yeah i definately think a 2.3 rom needs to be the base!
Sent from my HTC Vision using XDA Premium App
i flashed Simply Galaxy RC3.3 and all i did was install netflix and it worked!!!!
works gorgeously on miui 1.5.6b edited reboot cleared, rebooted play. no data toggling, locking etc.
Got it working on CM7.
Sent from my SGH-T959 using XDA Premium App
Hmmm so I either get GPS or Netflix...... I think I use my GPS much more than I will Netflix
Sent from my HTC Vision using XDA App
I amgetting a boot loop with bonixV 1.2.1, I let it sit for awhile then restore my nandroid backup.
Ahhh it booted up.

[Q] How to get Boot2Gecko working on 2ndROM?

Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers

[Q] YP-G1CWY/XAA Mysterious Bootloop

Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony
"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread

suspicious shared libs in /system/lib

device is:
ST70208-1
Android Version: 4.1.1
Kernel Version: 3.0.8+
Build: ST70208-1_20130808_INT
aka Trekstor Surftab Ventos 7.0 HD
As Chrome crashes at start even after factory reset and all known measures did not help,
i installed root/su/bussybox/ssh-server and did a logcat.
...
/ActivityManager( 3603): Start proc com.android.chrome:sandboxed_process0 for service com.android.chrome/org.chromium.content.app.SandboxedProcessService0: pid=24769 uid=99001 gids={}
I/LibraryLoader(24750): loading: chromeview
E/Main (24750): Failed to load native library.
E/Main (24750): org.chromium.content.common.ProcessInitException
E/Main (24750): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.loadLibraryNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.access$400(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation$2.run(Unknown Source)
E/Main (24750): at android.os.Handler.handleCallback(Handler.java:615)
E/Main (24750): at android.os.Handler.dispatchMessage(Handler.java:92)
E/Main (24750): at android.os.Looper.loop(Looper.java:137)
E/Main (24750): at android.os.HandlerThread.run(HandlerThread.java:60)
E/Main (24750): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/Main (24750): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/Main (24750): at java.lang.System.loadLibrary(System.java:535)
E/Main (24750): ... 8 more
E/Trace (24769): error opening trace file: No such file or directory (2)
D/OpenGLRenderer(24750): Enabling debug mode 0
I/SandboxedProcessService(24769): Creating new SandboxedProcessService pid=24769
I/LibraryLoader(24769): loading: chromeview
E/SandboxedProcessService(24769): Failed to load native library, exiting sandboxed process
E/SandboxedProcessService(24769): org.chromium.content.common.ProcessInitException
E/SandboxedProcessService(24769): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/SandboxedProcessService(24769): at org.chromium.content.app.SandboxedProcessService$2.run(Unknown Source)
E/SandboxedProcessService(24769): at java.lang.Thread.run(Thread.java:856)
E/SandboxedProcessService(24769): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/SandboxedProcessService(24769): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/SandboxedProcessService(24769): at java.lang.System.loadLibrary(System.java:535)
E/SandboxedProcessService(24769): ... 3 more
..
"ls -al" in /system/lib showed amongst others 4 suspicious shared native libraries:
-rw------- 1 0 0 59996 Mar 17 18:50 libjnigraphics.so
-rw------- 1 0 0 10017928 Mar 17 18:18 libmsrmsdk.so
-rw------- 1 0 0 8577120 Mar 17 18:50 libreader.so
-rw------- 1 0 0 135864 Mar 17 18:51 librss.so
all other libs here look like that:
-rw-r--r-- 1 0 0 31363328 Aug 1 2008 libchromeview.so
The 4 suspects have a date 03/17/2016 and no read permission for group/other but the rest all are 8/1/2008 and have the permissions.
I did "chmod 644" to them.
But i had to remount /system as readwrite.
Seams it is normaly readonly!
And i had to do "su"!
How/Who can change anything here in /system/lib?
Chrom still crashes but logcat shows it is not because it does not find the libjnigraphics.so.
Now it crashes with a dump.
I think it is because libchromeview.so loads the dependency libjnigraphics.so,
but that is an newer version than that it was linked against.
After i left the device in the morning on the day this **** happend, it was working ok.
In the evening (my wife had used it) there was tones of error msg at starting of many apps (Contacts, Playstore, ...).
So i did a factory reset, but the Chrome problem persists (Google+ and Maps where *****y too but worked after update).
I did not switch of auto update.
So i think some update messed it up, or my wife had switched it hard off during something important/longer lasting, as it was not responsive to her.
But how can a normal apk do something to /system?!
Any ideas why Chrome still uses these old native shared libraries?
Please can somebody who is having the same device, send me a "ls -al" of /system/lib.
Any ideas how to fix Chrome (PlayStore)?
Greetings
Michael
PS: This was the 3rd factory reset i had to make because some update managed to screwed it. But the two before worked, ok.
The stock "firmware" of this device looks as if it was the 5th test build a new greenhorn system builder.
And ADB does not work. The device announces itself only in recovery mode to USB (of course "USB debugging" is on).

Categories

Resources