Does anyone have this problem? Updated today to the new camera version and discovered the new playground option does not work, when launched it just sits there and does nothing. Quitting the app causes all subsequent launches of the camera app to display no images on screen through the lens just a big block of grey. Only a hardboot will restore the camera functions. I did an uninstall of all updates to go back to the November system version and the Arc Core function reacts the same way. Anybody have any similar experience?
Running the November security updates with stock kernel and only Magisk 17.3 applied.
I installed the new camera today - Playground works just fine. No issues at all. I am running a custom kernel - not sure if that matters - (Franken Kernel 5.1) and all is good.... sorry you are having issues - have you tried to clear cache/Data on camera APK to see if that helps?
Good Luck...
Tried all of that, even went so far as to do a complete factory reset and wipe to see if it would work on a completely stock system but still no go. Maybe I have a bad AR chip or something.
Reapply your animation serrings
If Google playground has stopped working, active your animation settings on your phone. This fixed it for me!!
:fingers-crossed:
Related
I have a known camera issue in which I cannot solve.
My camera does not work. Any app that tries to get to the camera fails.
I know that is not an hardware issue because on stock ROM the camera works.
Crash report:
java.lang.RuntimeException: startPreview failed
at android.hardware.Camera.startPreview(Native Method)
at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:261)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.os.HandlerThread.run(HandlerThread.java:61)
NOTES ַ& UPDATES
- I updated my firmware to NE4 so I cant install CM11
- I noticed that on CWM recovery its asks to ROOT my phone if I dont have one. This ROOT makes to phone to not detect the camera even on stock ROM.
- I used S3Rx_UCUFNE4_AROMA_11-9-14 to install the stock ROM. The camera wont work until I removed the KNOX app.
- I have tried to install ROM cm-10.2.1-d2att_for_NE4 and its the same problem
- Installing different kernels make my phone stuck on bootloop.
- The camera worked for one time only on CM10 after enabling " temp unroot" and than remove it in superuser app. But after this its not working.
Here is that things that I have tried:
- I checked to camera with no SD card so that gallery is empty.
- I updated my firmware from UCUFNE4 to UCUFNE4.
- I have installed different camera apps.
Threads that I have looked at:
http://forum.xda-developers.com/showthread.php?t=2542700
http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973
https://play.google.com/store/apps/details?id=com.billgbennett.camerafix
I have tried this ROM and I have the same problem
http://forum.xda-developers.com/galaxy-s3-att/development/rom-dirty-unicorns-t2844362
IDEAS
I think that the problem is with the kernel or something with the ROOT.
Any room expect the stock one have broken camera.
I WILL GIVE BIG DONATION TO THE ONE WHO WILL SOLVE THIS ISSUE
There is a corrupt image or video file in your gallery that is preventing the camera from connecting. Look in your gallery for any recent files that just show a black square for their thumbnail and then delete them.
After that, clear data for your camera app and maybe even restart your phone just to be safe. It should work.
ScOULaris said:
There is a corrupt image or video file in your gallery that is preventing the camera from connecting. Look in your gallery for any recent files that just show a black square for their thumbnail and then delete them.
After that, clear data for your camera app and maybe even restart your phone just to be safe. It should work.
Click to expand...
Click to collapse
Thanks for trying to help but my gallery is empty and I still got this error.
Bump
I WILL GIVE BIG DONATION TO THE ONE WHO WILL SOLVE THIS ISSUE
Have you tried to revert all OS updates and flash original stock with odin and then root and install cm11 ?
Sent from my LG-D802
I tried various of the recommended fixes , nothing worked for me, but installing the nexus camera from the google play somehow fixed the problem and my camera works again
Good Morning,
I've had the Moto G5 since January and successfully rooted it with Magisk 11.6 / no verity opt encrypt 5.1 / twrp cedric 3.1.1-0 (stock ROM). It was working perfectly until last week when the camera suddenly stopped working, followed all the "camera problems" guides such as clear cache etc. and it disn't resolve the issue. Did a factory reset, re-locked the bootloader and re-flashed with stock firmware - this time with the November security patched version retgb NPP25.137-93. The camera started working again, so I'm assuming it isn't a hardware issue. Re-rooted and re-installed my apps and again the camera has been working fine then suddenly it stopped again. It does seem to have coincided with updating apps on the play store, pretty sure it took and camera app update ok and my gut feeling it that one of the Google app updates is causing the problem.
Installed apps include BBC iplayer, BT wifi, Gallery, Gallery vault, tomtom go, MX player, Nova Launcher, Power toggles, Root browser, Stellio, Superbeam, weather and clock widget.
Any ideas?
Thanks
Flashed with this (November variant).
https://forum.xda-developers.com/g5/development/rom-debloated-optimized-t3722396
So far so good, yet to re-root it though.
I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?
I just updated my Asus Zenfone 5z to Android P (Indian update) today. However, after the update the Google Lens icon that used to show inside the default camera app of the device is no more to be seen. I tried clearing caches, data for both apps (camera & lens) but none helped. I even tried safe mode boot & then restarted the device but naah! Some end users are reporting that they still have the integration intact but a couple of them also report the contrary, on Asus ZenTalk forum. Any help? Is there a way out without factory reset?
VergilXavier said:
I just updated my Asus Zenfone 5z to Android P (Indian update) today. However, after the update the Google Lens icon that used to show inside the default camera app of the device is no more to be seen. I tried clearing caches, data for both apps (camera & lens) but none helped. I even tried safe mode boot & then restarted the device but naah! Some end users are reporting that they still have the integration intact but a couple of them also report the contrary, on Asus ZenTalk forum. Any help? Is there a way out without factory reset?
Click to expand...
Click to collapse
Not in my case. I also updated to Android 9 and the Google lens still at camera app. I'm from Malaysia.
Try reinstalling Google Lens. I have upgraded to WW .175, but my integration still there.
What Asus PixelMaster version you guys have?
I accepted the latest OTA update for lineage. After the reboot my camera app shows a black screen for the main camera and crashes after a few seconds.
What I've tried:
Messing with the camera app, permissions etc.
Trying other camera apps, same problem.
Rebooting.
Since I wanted to see what grapheneOS was like I tried installing that.
Same problem....?
Okay so then I thought they might be sharing the same camera driver. So I installed...
The latest Google factory image.
Then I tried reverting to Android 11 (everything was 12 before)
Main camera is still dead. Selfie camera works.