Hi,
there's an issue installing updates for Whatsapp and Instagram on my wifes Nexus 5 (rooted Stock ROM / Stock Kernel).
When she starts the updates it take a few seconds, then an error message occures. All updates of the other apps work normally. And her Nexus 5 has still 19GB free memory says Titanium Backup.
Here's a logcat what happens when Google Play tries to update Whatsapp:
Code:
D/Finsky (1466): [1] LightPurchaseFlowActivity.handleAppPermissionResult: Permissions accepted: com.whatsapp
D/Finsky (1466): [1] InstallerImpl.requestInstall: Request install of com.whatsapp v=48348 for single_install
D/Finsky (1466): [1] InstallerImpl.kick: Installer kick com.whatsapp - starting com.whatsapp
D/MarketUpdateReceiver(3748): market has promised to install: com.whatsapp
D/Finsky (1466): [1] DownloadImpl.setState: com.whatsapp from null to UNQUEUED.
D/Finsky (1466): [1] DownloadQueueImpl.add: Download com.whatsapp added to DownloadQueue
D/Finsky (1466): [1] DownloadImpl.setState: com.whatsapp from UNQUEUED to QUEUED.
D/Finsky (1466): [1] DownloadQueueImpl.startDownload: Download com.whatsapp starting
D/Finsky (1466): [79] 7.run: Enqueued com.whatsapp as content://downloads/my_downloads/130
D/Finsky (1466): [1] DownloadImpl.setState: com.whatsapp from QUEUED to DOWNLOADING.
D/Finsky (1466): [1] DownloadQueueImpl.onStart: com.whatsapp: onStart
D/MarketUpdateReceiver(3748): market is downloading (0%): com.whatsapp
D/Finsky (1466): [1] DownloadQueueImpl.notifyProgress: com.whatsapp: onProgress 0/-1 Status: 190.
D/MarketUpdateReceiver(3748): market is downloading (0%): com.whatsapp
I/DownloadManager(3618): Download 130 starting
D/Finsky (1466): [1] DownloadQueueImpl.notifyProgress: com.whatsapp: onProgress 0/-1 Status: 192.
D/MarketUpdateReceiver(3748): market is downloading (0%): com.whatsapp
I/DownloadManager(3618): Download 130 finished with status SUCCESS
D/Finsky (1466): [1] DownloadQueueImpl.notifyProgress: com.whatsapp: onProgress 2220931/2220931 Status: 200.
D/MarketUpdateReceiver(3748): market is downloading (0%): com.whatsapp
D/Finsky (1466): [1] DownloadImpl.setState: com.whatsapp from DOWNLOADING to SUCCESS.
D/Finsky (1466): [1] DownloadQueueImpl.onComplete: com.whatsapp: onComplete
D/Finsky (1466): [1] DownloadQueueImpl.remove: Download com.whatsapp removed from DownloadQueue
D/Finsky (1466): [1] 6.onPostExecute: Successfully applied patch to update com.whatsapp
D/MarketUpdateReceiver(3748): market is installing: com.whatsapp
W/ActivityManager(771): No content provider found for permission revoke: file:///data/data/com.android.vending/cache/patches/com.whatsapp1352738165.apk
I/PackageManager(771): Copying native libraries to /data/app-lib/vmdl1352738165
W/NativeHelper(771): Could not delete native binary: /data/app-lib/com.whatsapp-1/libframeconv.so
E/PackageManager(771): Cannot rename native library directory /data/app-lib/vmdl1352738165 to /data/app-lib/com.whatsapp-1
D/Finsky (1466): [61] 1.packageInstalled: Package install status for "com.whatsapp" is -4
D/Finsky (1466): [1] InstallerTask.cancelCleanup: Cancel running installation of com.whatsapp
D/MarketUpdateReceiver(3748): market has decided not to install: com.whatsapp
I tried some things without success:
- Wiping cache / dalvik cache
- Delete cache of the apps Whatsapp and Instagram
- Delete cache of the Google Play
- Delete both apps and tried install them new (A reinstallation by Play Store is not possible!)*
Any ideas?
Thanks and regards
Koetermann
* Only recopy the saved .apks into /data/app bring them back
No one who has an idea?
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Also, titanium backup freezes when I try to restore them. Does anybody have any idea what this is about? AOSP ROMs work fine.
Code:
12-19 12:35:24.806 I/PackageManager(820): Verification timed out for file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.806 I/PackageManager(820): Continuing with installation of file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.813 D/Finsky (14536): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 43
12-19 12:35:24.816 D/Finsky (14536): [1] PackageVerificationService.cancelVerificationIntent: Cancel active verification id=43
12-19 12:35:25.105 E/Vold (185): Error creating imagefile (Read-only file system)
12-19 12:35:25.105 E/Vold (185): ASEC image file creation failed (Read-only file system)
12-19 12:35:25.105 W/Vold (185): Returning OperationFailed - no handler for errno 30
12-19 12:35:25.106 E/PackageHelper(22123): Failed to create secure container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): Failed to copy package at /mnt/sdcard/badland_android_46.apk
12-19 12:35:25.106 W/DefContainer(22123): java.io.IOException: Failed to create container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:323)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
12-19 12:35:25.106 W/DefContainer(22123): at android.os.Binder.execTransact(Binder.java:446)
12-19 12:35:25.242 I/art (820): Explicit concurrent mark sweep GC freed 71196(3MB) AllocSpace objects, 20(8MB) LOS objects, 27% free, 42MB/58MB, paused 1.163ms total 133.773ms
12-19 12:35:25.246 D/InstallAppProgress(29894): Installation error code: -18
Geo2160 said:
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Does anybody have any idea what this is about?
Code:
12-19 12:35:24.806 I/PackageManager(820): Verification timed out for file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.806 I/PackageManager(820): Continuing with installation of file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.813 D/Finsky (14536): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 43
12-19 12:35:24.816 D/Finsky (14536): [1] PackageVerificationService.cancelVerificationIntent: Cancel active verification id=43
12-19 12:35:25.105 E/Vold (185): Error creating imagefile (Read-only file system)
12-19 12:35:25.105 E/Vold (185): ASEC image file creation failed (Read-only file system)
12-19 12:35:25.105 W/Vold (185): Returning OperationFailed - no handler for errno 30
12-19 12:35:25.106 E/PackageHelper(22123): Failed to create secure container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): Failed to copy package at /mnt/sdcard/badland_android_46.apk
12-19 12:35:25.106 W/DefContainer(22123): java.io.IOException: Failed to create container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:323)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
12-19 12:35:25.106 W/DefContainer(22123): at android.os.Binder.execTransact(Binder.java:446)
12-19 12:35:25.242 I/art (820): Explicit concurrent mark sweep GC freed 71196(3MB) AllocSpace objects, 20(8MB) LOS objects, 27% free, 42MB/58MB, paused 1.163ms total 133.773ms
12-19 12:35:25.246 D/InstallAppProgress(29894): Installation error code: -18
Click to expand...
Click to collapse
Hope you are not talking about cracks and warez. Not allowed on XDA.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Ofc not. I've mentioned clearly that the ones I have tried are from humble bundle. Also, I forgot to mention that restoring big apps like these through titanium causes it to freeze, even if they were downloaded from google play.
Try different gapps versions? Like.. There's PA gapps.. Banks gapps..
a maguro wrote this.
I didn't mention that I used different gapps for the ROMs because I didn't think the issue is related to gapps. I've even tried no gapps. What's the reasoning behind suggesting a different gapps package, since I'm not even trying to install google dependent apks?
Probably the same as yours then.
Does it work on stock?
Stock ROM, stock based ROMs like optipop and AOSP based ROMs like omni rom work fine.
The error you're getting is "read only".
Can you manually create files in the same location a on your /sdcard?
Geo2160 said:
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Also, titanium backup freezes when I try to restore them. Does anybody have any idea what this is about? AOSP ROMs work fine.
Click to expand...
Click to collapse
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Jani- said:
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Click to expand...
Click to collapse
Thanks a lot anyway! I can now go back to trying CM based ROMs.
That solution worked for me too. Thanks.
Jani- said:
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Click to expand...
Click to collapse
That solution unfortunately doesn't work for me. Under Settings > Apps > Menu I don't see "Preferred install location". Maybe because my Nexus 5 doesn't have a SD card?
I'm on CM 12.1-20150804-NIGHTLY. Any idea how I can fix this? Would really like to be able to restore apps via Titanium Backup and install apps from Amazon App-Shop.
Thanks!
Update:
Found a solution myself If you don't see the option "Preferred install location" like me you can set it via terminal:
Either open a shell on your phone via adb (adb shell) or with a terminal application on your phone, then type
su (to get superuser rights)
pm set-install-location 1 (to set install location to internal [0 = auto, 1 = internal, 2 = external])
Hello everyone,
I own a OnePlus One 64GB, running CM11s stock rom + Xposed + Boeffla kernel 2.3 stable, rooted, unlocked bootloader, TWRP(2.8.5.1).
My issue came out of nowhere. Now, without any action of mine (really, at morning I took my OPO, and discovered all of this), I cannot:
- Install or update from Google Play
- Install or update from internal memory
- Install with command from pc "adb install "Path/to/apk"
- Restore app or app+data from titanium backup
In each one of these cases, I get the same error: "Insufficient Storage Space ..." (even in my windows console after adb install).
Of course I have plenty of space available.
Here is what I tried so far (you can find common "solutions" to this problem across the internet, but none worked for me):
- Wiping cache
- Wiping dalvik cache
- Fix permission via TWRP
- Delete cache and/or data of G.Play, Play services and google framework
- Delete cache and/or data of download manager (see why below)
- Manually setting the permission of data/local to 755 with "chmod" in terminal emulator (look red line in logcat: "permission revoke")
- Delete the folder "/data/app-lib/APPNAME" related to the apps which won't update
- Look for leftover .odex files (http://newton.cx/~peter/2013/07/fixing-erroneous-insufficient-storage-available-errors-on-android/)
- Searching around on the internet for hours...
This is a VERY COMMON issue, and there was never ONE solution. For different people/devices, one solution among the above has worked when the others don't. Still, in EACH CASE, the concerned person never knew what caused the problem, only assumptions from other forum posts, or after looking at logcats but not really understanding them and then do things without knowing why.
Of course, I wanna find a solution for my device, but I am also willing to provide the community with a dedicated solution. We don't know if there is one or multiple cause (at least this is what I can conclude from my personal research).
Now, I used Android device monitor to see what is happening on my device when I try to install or update any app (this is for the google play case, but for every other method, the error message is the same, only the path to the file is different):
Code:
03-06 18:37:52.966: D/Finsky(2167): [1] LightPurchaseFlowActivity.handleAppPermissionResult: Permissions accepted: com.appgenix.bizcal
03-06 18:37:52.966: D/Finsky(2167): [1] InstallerImpl.requestInstall: Request install of com.appgenix.bizcal v=201200 for single_install
03-06 18:37:52.976: D/Finsky(2167): [1] InstallerImpl.kick: Installer kick - starting com.appgenix.bizcal
03-06 18:37:53.216: I/qtaguid(2167): Failed write_ctrl(u 126) res=-1 errno=22
03-06 18:37:53.216: I/qtaguid(2167): Untagging socket 126 failed errno=-22
03-06 18:37:53.226: W/NetworkManagementSocketTagger(2167): untagSocket(126) failed with errno -22
03-06 18:37:53.646: I/Timeline(2167): Timeline: Activity_idle id: [email protected] time:576066
03-06 18:37:53.656: I/qtaguid(2167): Failed write_ctrl(u 126) res=-1 errno=22
03-06 18:37:53.656: I/qtaguid(2167): Untagging socket 126 failed errno=-22
03-06 18:37:53.656: W/NetworkManagementSocketTagger(2167): untagSocket(126) failed with errno -22
03-06 18:37:53.826: D/Finsky(2167): [1] DownloadImpl.setState: com.appgenix.bizcal from null to UNQUEUED.
03-06 18:37:53.826: D/Finsky(2167): [1] DownloadQueueImpl.add: Download com.appgenix.bizcal added to DownloadQueue
03-06 18:37:53.826: D/Finsky(2167): [1] DownloadImpl.setState: com.appgenix.bizcal from UNQUEUED to QUEUED.
03-06 18:37:53.826: I/installd(256): free_cache(2210712) avail 29941784576
03-06 18:37:53.856: D/Finsky(2167): [1] DownloadQueueImpl.startDownload: Download com.appgenix.bizcal starting
03-06 18:37:53.886: D/Finsky(2167): [130] 7.run: Enqueued com.appgenix.bizcal as content://downloads/my_downloads/13
03-06 18:37:53.896: D/Finsky(2167): [1] DownloadImpl.setState: com.appgenix.bizcal from QUEUED to DOWNLOADING.
03-06 18:37:53.896: D/Finsky(2167): [1] DownloadQueueImpl.onStart: com.appgenix.bizcal: onStart
03-06 18:37:53.926: I/DownloadManager(1799): Download 13 starting
03-06 18:37:53.956: D/Finsky(2167): [1] DownloadQueueImpl.notifyProgress: com.appgenix.bizcal: onProgress 0/-1 Status: 192.
03-06 18:37:54.996: D/MobileDataStateTracker(946): default: setPolicyDataEnable(enabled=true)
03-06 18:37:55.206: D/Finsky(2167): [1] DownloadQueueImpl.notifyProgress: com.appgenix.bizcal: onProgress 2210712/2210712 Status: 200.
03-06 18:37:55.236: I/DownloadManager(1799): Download 13 finished with status SUCCESS
03-06 18:37:55.276: D/Finsky(2167): [1] DownloadBroadcastReceiver.onReceive: Intent received at DownloadBroadcastReceiver
03-06 18:37:55.286: D/Finsky(2167): [1] DownloadImpl.setState: com.appgenix.bizcal from DOWNLOADING to SUCCESS.
03-06 18:37:55.286: D/Finsky(2167): [1] DownloadQueueImpl.onComplete: com.appgenix.bizcal: onComplete
03-06 18:37:55.286: D/Finsky(2167): [1] DownloadQueueImpl.remove: Download com.appgenix.bizcal removed from DownloadQueue
03-06 18:37:55.286: D/Finsky(2167): [1] InstallerTask.startApplyingPatch: Prepare to patch com.appgenix.bizcal from content://downloads/my_downloads/13
03-06 18:37:55.286: I/installd(256): free_cache(0) avail 29941768192
03-06 18:37:57.766: D/Finsky(2167): [1] 9.onPostExecute: Successfully applied patch to update com.appgenix.bizcal
03-06 18:37:57.766: D/Finsky(2167): [1] InstallerTask.startInstaller: Begin install of com.appgenix.bizcal
[COLOR="Red"]03-06 18:37:57.986: I/installd(256): free_cache(533725184) avail 29934342144
03-06 18:37:57.996: W/ActivityManager(946): No content provider found for permission revoke: file:///data/data/com.android.vending/cache/copies/com.appgenix.bizcal1571224167.apk
03-06 18:37:58.186: D/Finsky(2167): [147] 1.packageInstalled: Package install status for com.appgenix.bizcal is -4
03-06 18:37:58.256: W/Finsky(2167): [1] 4.installFailed: Install failure of com.appgenix.bizcal: -4 null
03-06 18:37:58.266: D/Finsky(2167): [1] InstallerTask.cancelCleanup: Cancel running installation of com.appgenix.bizcal[/COLOR]
03-06 18:38:02.486: W/InputMethodManagerService(946): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
: E/(): Device disconnected
(I colored lines where error occurs)
: I observed that when I update this app from G.Play, the download progress bar goes from 0% up to 16% every time, then show "installing...", and then the error message. I though it may be related to the google play cache or download manager. Same for others apps (but different %).
Here are some useful links I found while going through the internet (I'll add more tomorrow):
http://forum.cyanogenmod.org/topic/...tions-in-play-store-bug-cm-or-something-else/
I am willing to do tests, or anything else that could help for understanding where is this coming from. :good:
Thank you for reading this, and for help.
Cheers,
Debye
i have the same problem.. any fix?
---------- Post added at 05:37 PM ---------- Previous post was at 05:01 PM ----------
i have found a fix.
using lucky patcher i've changed the defult install location to "mobile" (as this is the only option).
cleaned the play store settings and that problem was fixed.
that for:
.packageInstalled: Package install status for .... is -4
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609
cthulu said:
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
cthulu said:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
Click to expand...
Click to collapse
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
zagorteney said:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
Click to expand...
Click to collapse
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
PHPanos said:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
Click to expand...
Click to collapse
And this was happening immediately after booting your phone? Then must be hardware. ?
It works fine everytime I reboot, for xx minutes. It's difficult to say for how long but not too long. I see that "Trusted face" unlock stops working and that's a signal the whole camera subsystem is gone. Everything else works just no camera access from any app is possible.
zagorteney said:
And this was happening immediately after booting your phone? Then must be hardware. ��
Click to expand...
Click to collapse
No. It works at first. Then after a few times of locking/unlocking the phone and opening the camera app and switching to front camera it shuts down. The problem goes away after a reboot but it comes back again after a while.
cthulu: We have both the same problem.
Same here for me since upgrading to 5.0 every now and then i must reboot my phone in order to fix it.This is really annoying maybe we should wait for a new camera app by google ?
Same issue
Hi guys,
This has been the problem for me since 5.0 . I thought maybe its just me. But after a while, the camera stops working. I assume this is a s/w issue since the phone was fine in Kitkat. Even in 5.1 the issue persists.
I am also getting frequent "can't connect to camera" since 5.1. Nexus 5.
Do you know if there's an issue for this in Google's issue tracker? I'm sure they won't check xda forums for bug reports.
I've clicked a few times to send the error to Google when starting the camera but I honestly don't think they're checking those...
I hoped full wipe will fix this but as it happens to the folks who did full wipe I'm rather not going to do it yet...
Already reported here https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
THRUSTer said:
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
Click to expand...
Click to collapse
You are on a right direction. Just start to read a little more careful.
Happens the same for me.
Some days ago i see that the face Trusted face have Stop. So, now i desible the Trusted face, clear data of camera app e until now (about 2 hours) the camera works fine, without any shut up.
Try you too, i think that the problems are in the Smart lock.
Many people have this issue since they moved to 5.1
'Hardware defect' and 'no full wipe' were told to be the culprit straight away, but looking at the bug report that seems unjustified, especially given the number of reports with exactly this issue.
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
zagorteney said:
Flash completely and it will fix it.
Click to expand...
Click to collapse
zagorteney said:
Then must be hardware. ?
Click to expand...
Click to collapse
So please be a bit more thorough in your advice....
Can't connect to camera error Nexus 5 Android 5.1
Hi gays, I am new here. I keep getting the ' can't connect to camera' error on my Nexus 5 Android 5.1, and I tried everything that is suggested here and it did not help. I turned off Face unlock, uninstall Viber and install again, cleared cache of the camera and force stop and everything else. Only help restart the device. I succeeded to catch the logcat with the error. Here is the logcat:
04-02 21:19:26.744 724-2687/? I/ActivityManager﹕ START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[849,1532][1050,1784] (has extras)} from uid 10019 on display 0
04-02 21:19:26.747 724-2687/? V/WindowManager﹕ addAppToken: AppWindowToken{2498ae08 token=Token{83da7ab ActivityRecord{3a47c5fa u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t32}}} to stack=1 task=32 at 0
04-02 21:19:26.751 724-819/? V/WindowManager﹕ Based on layer: Adding window Window{15bd6123 u0 Starting com.google.android.GoogleCamera} at 3 of 9
04-02 21:19:26.824 724-1360/? I/ActivityManager﹕ Start proc 22932:com.google.android.GoogleCamera/u0a42 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
04-02 21:19:26.837 1361-3270/? W/GsaThreadFactory﹕ Not creating another thread for Background Blocking because there are already 30
04-02 21:19:26.876 22932-22932/? W/ResourcesManager﹕ Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
04-02 21:19:26.935 22932-22932/? W/CAM_Log﹕ Tag SessionStatsCollector is 2 chars longer than limit.
04-02 21:19:26.989 22932-22932/? I/CameraManagerGlobal﹕ getCameraService: Reconnecting to camera service
04-02 21:19:27.254 22932-22979/? I/CAM2PORT_AndCamAgntImp﹕ Opening camera 0 with camera1 API
04-02 21:19:27.266 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 116
04-02 21:19:27.268 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.289 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 117
04-02 21:19:27.290 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.301 193-1682/? I/Camera2ClientBase﹕ Camera 0: Opened. Client: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.302 22932-22992/? W/CAM_PhotoData﹕ Zero dimension in ContentResolver for /storage/emulated/0/DCIM/Camera/IMG_20150402_180439.jpg:0x0
04-02 21:19:27.303 193-1682/? D/mm-camera-intf﹕ mm_camera_open: dev name = /dev/video1, cam_idx = 1
04-02 21:19:27.304 206-206/? I/mm-camera-sensor﹕ module_sensor_start_session:583 session 1
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ csiphy_open:126 VIDIOC_MSM_CSIPHY_IO_CFG failed
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:335 failed rc -1
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_close:2499 VIDIOC_MSM_SENSOR_CFG failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:500 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:612 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:617 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_get_capabilities:1632 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_query_mod:2421 failed rc -4
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_hardware_process_command:254: failed, subdev not opened
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_query_mod:268: failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_query_mod:1697] error in cpp query mod
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_module_set_session_data:2666 max delay 2 report dSelay 1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ isp_set_session_data: Session could not be found!
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_get_params_for_session_id:178, failed, session_id=0x1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_set_session_data:329, failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_set_session_data:1928] error in cpp set_session_data
04-02 21:19:27.307 206-206/? D/mm-camera﹕ module_faceproc_set_session_data:1836] Per frame control 2 1
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_sensor_stop_session:636 session 1
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_deinit_session:526 ref count 0
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:664 failed
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:669 failed
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:462, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:504, info: session 1 stopped.
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:322, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:361, info: session 1 stopped.
04-02 21:19:27.308 206-206/? E/mm-camera﹕ main: New session [1] creation failed with error
04-02 21:19:27.308 193-1682/? D/mm-camera-intf﹕ mm_camera_open: opened, break out while loop
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ camera_open: mm_camera_open err = -1
04-02 21:19:27.308 193-1682/? E/QCamera3HWI﹕ camera_open failed.
04-02 21:19:27.308 193-1682/? E/Camera3-Device﹕ Camera 0: initialize: Could not open camera: No such device (-19)
04-02 21:19:27.308 193-1682/? E/Camera2ClientBase﹕ initialize: Camera 0: unable to initialize device: No such device (-19)
04-02 21:19:27.308 193-1682/? E/CameraService﹕ connectFinishUnsafe: Could not initialize client from HAL module.
04-02 21:19:27.308 193-1682/? I/Camera2Client﹕ Camera 0: Closed
04-02 21:19:27.309 193-1682/? I/Camera2ClientBase﹕ Closed Camera 0. Client was: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.313 193-1682/? W/AudioFlinger﹕ session id 116 not found for pid 22932
04-02 21:19:27.317 193-1682/? W/AudioFlinger﹕ session id 117 not found for pid 22932
04-02 21:19:27.318 22932-22979/? W/CameraBase﹕ An error occurred while connecting to camera: 0
04-02 21:19:27.318 22932-22979/? E/CAM2PORT_AndCamAgntImp﹕ RuntimeException during CameraAction[OPEN_CAMERA] at CameraState[1]
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.<init>(Camera.java:497)
at android.hardware.Camera.open(Camera.java:342)
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.handleMessage(AndroidCameraAgentImpl.java:370)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
04-02 21:19:27.371 22932-23015/? D/OpenGLRenderer﹕ Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-02 21:19:27.377 22932-22932/? D/Atlas﹕ Validating map...
04-02 21:19:27.381 724-1360/? V/WindowManager﹕ Adding window Window{312f9c81 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 3 of 10 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.387 22932-22932/? W/CAM_CameraActivity﹕ Camera open failure: HIST_ID0_-1_1_HEND
04-02 21:19:27.387 22932-22932/? E/CAM_Util﹕ Show fatal error dialog
04-02 21:19:27.402 724-2689/? V/WindowManager﹕ Adding window Window{302ae167 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 11 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.406 22932-22932/? D/WearableClient﹕ WearableClientImpl.onPostInitHandler: done
04-02 21:19:27.431 22932-23015/? I/Adreno-EGL﹕ <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-02 21:19:27.432 22932-23015/? I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-02 21:19:27.444 22932-23015/? D/OpenGLRenderer﹕ Enabling debug mode 0
04-02 21:19:27.487 22932-22932/? I/CAM_UsageStats﹕ PlayLogger.onLoggerConnected
04-02 21:19:27.512 724-2689/? D/WifiService﹕ acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ onPreviewUIReady
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ attempted to start preview before camera device
04-02 21:19:27.518 724-851/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source 10007 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=10:fe:ed:4e:a3:ae RSSI=-47
04-02 21:19:27.574 724-819/? I/ActivityManager﹕ Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +790ms
Please HELP, it's really annoying
Best regards.
meranto said:
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
So please be a bit more thorough in your advice....
Click to expand...
Click to collapse
Nope..
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
has a lot of people who didn't use face unlock and still experienced the issue.
Replay
Hi meranto,
thanks for the replay. I did not use face unlock and the issue still show up