Database Users

Dead camera

Hey guys!
Hoping someone might be able to help. My camera stopped working about a year ago and I haven't been able to get it to work. Every time I try to use it my phone reboots. I've tried running every ROM available here, every radio, every SPL. At this point I figure it's probably hardware but I want to rule out every other possibility before I give up on it. Any suggestions ?
TY in advance.
PS. 32a Rogers - current radio is 6.35.16.19 - playing with gingerbread atm

I have the same issue with a Vodafone htc magic 32b. It started after the OTA of Vodafone to go to Android 2.2.1. I hoped it would work in Cyanogenmod 6.1 but it still gives reboots.
This is the log cat when I start the camera:
Code:
I/ActivityManager( 155): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera }
I/ActivityManager( 155): Start proc com.android.camera for activity com.android.camera/.Camera: pid=771 uid=10011 gids={1006, 1015}
I/WindowManager( 155): Setting rotation to 1, animFlags=1
I/ActivityManager( 155): Config changed: { scale=1.0 imsi=206/1 loc=nl_BE touch=3 keys=1/1/2 nav=3/1 orien=2 layout=18 uiMode=17 seq=8}
I/GPSButton( 155): Update State
I/ActivityManager( 155): Start proc com.ramesp.amissed for service com.ramesp.amissed/.LockWatchDog: pid=779 uid=10093 gids={1015}
E/mm-camera( 123): mt9t013_process_start: ioctl(MSM_CAM_IOCTL_ENABLE_OUTPUT_IND) error Invalid argument
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
D/RAMES ( 779): Registering--------------
D/Camera ( 771): app passed NULL surface
D/CameraSettings( 771): [antibanding-values=off,50hz,60hz,auto, antibanding=auto, effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboa
rd,aqua, effect=none, exposure-compensation-step=0.5, exposure-compensation=0, focal-length=3.72, focus-mode-values=auto,infinity, focus-mode=auto, horizontal-v
iew-angle=51.6, jpeg-quality=90, jpeg-thumbnail-height=384, jpeg-thumbnail-quality=90, jpeg-thumbnail-size-values=512x384,0x0, jpeg-thumbnail-width=512, max-exp
osure-compensation=4, max-zoom=12, min-exposure-compensation=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=2048x1536,1600x1200,1024x7
68,512x384, picture-size=2048x1536, preview-format-values=yuv420sp, preview-format=yuv420sp, preview-frame-rate-values=15, preview-frame-rate=15, preview-size-v
alues=800x480,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144, preview-size=384x288, vertical-view-angle=39.7, whitebalance-values=auto,
incandescent,fluorescent,daylight,cloudy-daylight, whitebalance=auto, zoom-ratios=100,102,107,109,114,117,123,128,131,138,141,148,155, zoom-supported=true, zoom=0]
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
V/camera ( 771): startPreview
It also reboots if I start any application that uses the camera e.g. goggles, barcode scanner,...
Would really like to have this fixed. Any suggestions?

my fix
try to reflash your rom if all else fail do a restore or flash of your stater rom and send it back to your carrier don't forget to unroot after that flash change your boot image back if not changed double check your fastboot

I've had this same issue. It looks from your logcat that the camera hardware works, it's just not loading properly.
The problem is that the camera's preferences file needs to be rewritten by the system. the solution is to adb shell into your phone, then go into /data/data/com.android.camera (or your Rom's specific directory; different Roms will likely have different directory names, but it shouldn't vary too much) and look for camera_hardware_preferences.xml (or your Rom's specific hardware preferences XML file for the camera) and move this to camera_hardware_preferences.xml_, then reboot.
Doing this will make your phone have to rewrite it's profile for camera hardware. Once done, it should work.

Findulmundo. I tried this and now my camera no longer crashes but is stuck on a black screen when starting the camera app. The camera_preferences.xml file is not being generated either. Any ideas?

Guys im having a similar issue, my camera will start normally but when i try to take a picture it will get stuck and wont shoot the pic. I can exit the app normally, no force close but im unable to take any pics any ideas?
Currently on cm5, already tried different sd cards, fastboot wipe and then reflashed the ROM, tried different roms also its still a no go though
Sent from my HTC Glacier using XDA Premium App

I'm not sure, but you should try to flash a new kernel - you'll find it in the dev section...
Btw. I'm using Ginger Yoshi RC 6.1 - to use it I needed to flash a new radio hboot and kernel - you can find the instructions in the ROM's thread step-by-step!

[Q] Wi-Fi connection fails (do not activate)

Every time I try to activate wifi the following error appears in logcat:
Code:
I/WifiManager( 1421): setWifiEnabled : true
I/WifiService( 879): setWifiEnabled: true pid=1421, uid=10141
E/WifiHW ( 879): ##################### set firmware type 0 #####################
E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 879): ==========[WIFI] Station firmware load ===========
D/SSRMv2:Monitor( 879): SIOP:: AP = 400 (read only)
E/WifiHW ( 879): return of insmod : ret = -1, No such device
E/WifiStateMachine( 879): Failed to load driver
D/WfdService( 879): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 1421): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 1421): Nothing, mRoamingIconId = 0
I/elm ( 2716): MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
E/WifiStateMachine( 879): sendErrorBroadcast code:10
E/WifiController( 879): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I/elm ( 2716): MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
D/elm ( 2716): ELMEngine.getInstance().
I/DownloadNowBroadcastReceiver( 3770): onReceive
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.TMNetworkReceiver() Enter 1 main
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - exit
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() UnHandled
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Exit
D/MTPRx ( 4799): DRIVER_TIME_OUT 60s lapsed
and I tried all sorts of wifi fixers available in the forum without success. After some research I found the following post:
http://forum.xda-developers.com/showthread.php?t=1652702
what makes me think it's a problem with the driver.
The solution was found by this user:
I fixed this issue by copying libhardware_legacy.so from my OEM ROM to the ported ROM. Rebooted and WiFi worked just fine
Click to expand...
Click to collapse
I would like to know how to apply this solution to the GT-I9505. I must confess I do not think there is a solution to my problem, so any suggestion will be very welcome.
I am using Stock 4.3
Thanks in advance

Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....

Pulse654321 said:
Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....
Click to expand...
Click to collapse
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!

arleybarros said:
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!
Click to expand...
Click to collapse
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.

Pulse654321 said:
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.
Click to expand...
Click to collapse
I really appreciate the help, but this also did not work. I'm starting to think I have a hardware problem. is possible to diagnose it via ADB?

I'm thinking that I must have a problem with the permissions of folders and partitions, because the file "/ data / .cid.info" should be created automatically (if I'm not mistaken) and here, no matter what I do, this file is not available.
Could someone show me how to check the correct permissions for the folders and partitions?

Yeah that's really odd. The file is recreated for me when I was deleting it before and restarting. I'm not sure which file browser I'm using atm. 2 secs and I'll get some pictures up and the permissions for folders.
This is the file manager I'm using, should work ok. Hopefully it works with root features.
I've included pictures of permissions for folders, hopefully they help.

Whoops mis interpreted the pictures
Cat you give an example of what should be in the .cid.info?

[Q] Nexus 10 hangs every night - something in libEGL/OpenGL?

Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?

_anarion_ said:
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
Click to expand...
Click to collapse
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?

rlrbjr said:
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
Click to expand...
Click to collapse
Hi!
I was able to find some old threads about this aptly named Sleep of Death issue, here for example.
Unfortunately no conclusion, most people seem to return their devices :/
Now I think this is indeed some massive memory leak, becasue I was able to see ADB logs with all processes stopping, and the screen blinking with lock screen once when this happened.
As for MovieMaker, this might be misleading - I froze it in TitaniumBackup but the issue still exists.
My plan now is to write a script that would run
Code:
adb shell dumpsys meminfo
every couple seconds/minutes and plot the memory usage until the issue strikes.
I will report here if I find anything.
Best regards,
anarion

I uninstalled Movie Editor (rather than freezing it) and my system is much better (so far). I have not had a single lockup. It still too early to know if this is a god long term solution but I will keep you informed.
Sent from my Nexus 10 using Tapatalk 4

Fingerprint and Homebutton stopped working

Hello Guys,
I got my Oneplus Two a week ago. I fell in love with it and everything worked perfectly. Now after 1 week of usage the home button and fingerprint sensor stopped working. I don't get any feedback from the Button at all.
I'm an android developer and looked into my logcat output. The phone is spamming 10 messages every 100ms with the following content:
Code:
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
11-20 13:19:02.044 4828-13709/? E/QSEECOM_fingerprint_CLIENT:: ioctl FPC_GET_INTERRUPT errno = 9
Can someone help me with the problem or at least tell me what the error code is? I would be very happy if someone could help me to narrow the problem.
Regards,
Sebastian

One quick question: Version of OOS? Are you already at 2.1.2?

Yes. The problem occurred on 2.1.1 though. I updated after because i thought it was a software related bug or somthing but the problem still occurred.
Maybe I should mention that my device is rooted

Even im also facing the same issue my home button stopped working a week before but suddenly its started to working from yesterday night so i updated to OOS 2.1.2 and flash AK kernel all fine for 10hours after that again it stopped working . i don't have any idea whether it hardware issue or software issue. How did you checked that error message ? I can also check and report u
PS : i flashed OOs every version no luck and even hydrogen also still my home button dead

sudhakarstoopy said:
Even im also facing the same issue my home button stopped working a week before but suddenly its started to working from yesterday night so i updated to OOS 2.1.2 and flash AK kernel all fine for 10hours after that again it stopped working . i don't have any idea whether it hardware issue or software issue. How did you checked that error message ? I can also check and report u
PS : i flashed OOs every version no luck and even hydrogen also still my home button dead
Click to expand...
Click to collapse
You'll need Android Studio or adb to get the log from your oneplus two.

Hey guys. I was having the same issue. Out of no where my home button stopped working. I was using H2oS, but when going back to my 2.1.1 Oxygen I continued to have the issue. Then I downloaded 2.1.2, deleted my fingerprints, dirty flashed 2.1.2 and cleared cache. My fingerprint and home have been working ever since. Its been about 24 hrs. Hope I don't jynx it...

bababaus said:
You'll need Android Studio or adb to get the log from your oneplus two.
Click to expand...
Click to collapse
I dropped my mobile To service center
Sent from my YU4711 using Tapatalk

Happened to me. I rolled back some of the mods I did like amplify, greenifying some of system apps. Take note that some uses fingerprint APIs like Google+ and on op2, if is a system app. So try what I did and my home button and fingerprint scanned becomes normal again. And try not to kill it from boot using bootmanager.
Sent from my ONE A2003 using Tapatalk

override182 said:
Happened to me. I rolled back some of the mods I did like amplify, greenifying some of system apps. Take note that some uses fingerprint APIs like Google+ and on op2, if is a system app. So try what I did and my home button and fingerprint scanned becomes normal again. And try not to kill it from boot using bootmanager.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
can you please tell me briefly?
Sent from my YU4711 using Tapatalk

sudhakarstoopy said:
can you please tell me briefly?
Sent from my YU4711 using Tapatalk
Click to expand...
Click to collapse
Mind telling me which part you're not clear with? I would be glad to help but I'm not sure which part though
Sent from my ONE A2003 using Tapatalk

how you find those application using fingerprint? what will happen if i completely delete those application
Sent from my YU4711 using Tapatalk

Its an hardware problem rather than the software.
Happened with me too.....
Took it to the service center n replaced the sensor.

has anyone found a good solution?
I'm living in London but will leave back to my country in 2 weeks and I cant go back without cellphone (in case I send it for repair)
is there a place where I can have it fixed?

I had the same problem and all I had to do to fix it was go into recovery and clear cache, after restart the scanner and home button started working again.

Fix for constant rebooting after upgrade to 2.1.0

**TLDR** - If your shield keeps rebooting after the 2.1.0 update, unplug your ethernet cable and/or disable your wifi as a temporary fix.
I recently got a 16GB model. After the latest firmware update (to 2.1.0) I started to get constant rebooting. My first thought was to use fastboot to get back to 2.0.0 - I believe you can do this without wiping your user data, as the official images are signed with the nvidia key and I believe their bootloader would allow you to downgrade - can anyone confirm this? See https: // developer .nvidia. com/ gameworksdownload (sorry, can't link with <10 posts...) for nvidia 2.0.0 image.
However I wanted to see what was happening first. Running
Code:
$ adb logcat
...lots of output
...the system just rebooted, so let's watch the logs!
D/AndroidRuntime( 4318): Shutting down VM
E/AndroidRuntime( 4318): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 4318): java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0
E/AndroidRuntime( 4318): at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255)
E/AndroidRuntime( 4318): at java.util.ArrayList.get(ArrayList.java:308)
E/AndroidRuntime( 4318): at com.android.server.pm.PackageManagerService$PMLocationListener.getCountryFromLocation(PackageManagerService.java:14375)
E/AndroidRuntime( 4318): at com.android.server.pm.PackageManagerService$PMLocationListener.onLocationChanged(PackageManagerService.java:14282)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:281)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport.access$000(LocationManager.java:210)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport$1.handleMessage(LocationManager.java:226)
E/AndroidRuntime( 4318): at android.os.Handler.dispatchMessage(Handler.java:104)
E/AndroidRuntime( 4318): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 4318): at com.android.server.SystemServer.run(SystemServer.java:276)
E/AndroidRuntime( 4318): at com.android.server.SystemServer.main(SystemServer.java:177)
E/AndroidRuntime( 4318): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4318): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 4318): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime( 4318): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
I/Process ( 4318): Sending signal. PID: 4318 SIG: 9
E/installd( 226): eof
E/installd( 226): failed to read size
I/installd( 226): closing connection
For those of you that don't speak stacktrace or android internals, what happened here is that something (presumably, my network state tracker noticed either an IP change or something else from my ethernet) sent a message to the internal LocationManager saying "something happened, update your location estimate". In the process of doing this LocationManager crashes, and then the entire android framework crashes in response to this critical component (system_server) crash. Then the init binary helpfully restarts everything, and in a few minutes it crashes again.
Unplugging the ethernet cable has resulted in a stable system. I haven't experienced the crash while on WiFi, but I wouldn't rule it out yet.
While I have not looked in extreme detail, my suspicion is that something about the firmware update broke google mobile services - I see an error trying to mount the data for GMS in the logs, and noticed the stacktrace above seems to be failing when the LocationManager uses the PackageManager which uses installd which then fails with some kind of file read.
Code:
E/Vold ( 206): Failed to find mounted volume for /storage/sdcard1/Android/data/com.google.android.gms/files/
W/Vold ( 206): Returning OperationFailed - no handler for errno 0
W/ContextImpl( 6163): Failed to ensure directory: /storage/sdcard1/Android/data/com.google.android.gms/files

Turning off location services seems to stop this too
I'm 100% that no ethernet stops the rebooting (got a few hours of testing and no crashes). Tried turning off location services after I saw the logs of the error, and I've had about 30 min with no crashes, so that's obviously a much more preferred way to address this issue until nvidia fixes the bug

well interesting to know about this issue.

slammertime said:
I'm 100% that no ethernet stops the rebooting (got a few hours of testing and no crashes). Tried turning off location services after I saw the logs of the error, and I've had about 30 min with no crashes, so that's obviously a much more preferred way to address this issue until nvidia fixes the bug
Click to expand...
Click to collapse
Has having locations services turned off solved the random restarts for you inevitably?

Yes, it seems so

Sorry for resurrecting an old thread, but I'm still having this issue.
Tried disabling location, changing languages, every other suggestion here and elsewhere online.. still getting reboots ~3-5 mins after the system starts, and random lockups. Only started happening post 2.1. The device is basically unusable at this point.
I'm just about to factory wipe/reinstall. Is there any other solution?

Same
grivad said:
Sorry for resurrecting an old thread, but I'm still having this issue.
Tried disabling location, changing languages, every other suggestion here and elsewhere online.. still getting reboots ~3-5 mins after the system starts, and random lockups. Only started happening post 2.1. The device is basically unusable at this point.
I'm just about to factory wipe/reinstall. Is there any other solution?
Click to expand...
Click to collapse
I am having the same issue. Talked to support, and they told me to unpair, and reset my devices that were attached to it, and unplug the hdmi and power, and still no dice.

peppy6582 said:
I am having the same issue. Talked to support, and they told me to unpair, and reset my devices that were attached to it, and unplug the hdmi and power, and still no dice.
Click to expand...
Click to collapse
I got sick of it, wiped the device, and did a fresh install of 2.1 (IIRC, whatever factory image was available a few weeks back) and applied the OTA once prompted. Zero issues since. It took some time installing and configuring everything again, but having a completely stable device made it worth it. It was unusable before, as it'd reboot every few minutes no matter what it was doing.
It looks like they have the 3.0 image up now, if you're thinking of reinstalling as well.
https://developer.nvidia.com/shield-open-source

grivad said:
I got sick of it, wiped the device, and did a fresh install of 2.1 (IIRC, whatever factory image was available a few weeks back) and applied the OTA once prompted. Zero issues since. It took some time installing and configuring everything again, but having a completely stable device made it worth it. It was unusable before, as it'd reboot every few minutes no matter what it was doing.
It looks like they have the 3.0 image up now, if you're thinking of reinstalling as well.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
Yeah, I actually did that, with a fastboot -w after the system.img part, just to make sure.

hey guys, do you still have the problem with the random reboot?
I have the same problem with the 500gb version but I didn't root this device or whatever, it isn't even my intention to root it.
Any idea what it is?? Nvidia want to send me a new one (or refurbished item) but I have like the idea that it will not be solved if I get a new one.
I read to much people with the same problems, even on 2 links I read from someone who got a new one and the problem was still there :s
I'm a little scared to send it back , because I fear it will not be solved.
Any idea guys???