Hello,
I am having issue with my camera "can't connect to the camera" on oneplus one (64gb).
Recently i formatted my system data using TWRP and after that it showed NO OS INSTALLED. So i downloaded nightly build from cyanogenmod's website and sideloaded the build in fastboot mode with gapps as well. During this process l lost recovery & backup, & encountered Can't connect to the camera issue, Please Help.
Everything was working properly even after this my device was much lightning fast & smoother.
But when i opened my Google camera then it displayed Can't Connect to the camera. I did almost all the things-
1. Firstly restarted the device to check whether it can be fixed by this method or not but my issue didn't resolve then i force stopped camera by clearing cache & data & then restarted the device but still same pop up appeared. On some forum thread's i also found that by installing app "Camera (CMFix) for Cyanogenmod" from play store will fix this issue, but app was not getting launched my problem didn't get resolve.
2. After getting all this issue i thinked to install snapshot build to check whether i can use my camera but this thing didn't work as well.
3. On so many forum's i found that changing the ROM will fix this issue so i downloaded Paranoid Rom and installed it but still my issue with camera didn't resolve.
I am following XDA forum as viewer since so years time and also i know that from here i can get fastest solution.
This is my first post on XDA developers cause i didn't find solution for this issue
Please please help me as i did almost all thing to fix my issue. I am ready to do anything to solve this issue. Please help
what version of gapps did you installed? in order for the camera to work you must install the "mini or micro" gapps package, when you are running AOSP, somehow the complete gapps package breaks the camera.
you can get the micro gaaps package from PA, it works for me https://www.androidfilehost.com/?w=files&flid=15797
livito said:
what version of gapps did you installed? in order for the camera to work you must install the "mini or micro" gapps package, when you are running AOSP, somehow the complete gapps package breaks the camera.
you can get the micro gaaps package from PA, it works for me https://www.androidfilehost.com/?w=files&flid=15797
Click to expand...
Click to collapse
To clarify this, you can install any gapps package as long as it doesn't contain a camera.
Transmitted via Bacon
I did this once and had to flash cm11s once and then whatever rom I wanted after that in order to have a working camera.
Unjust updated CyanogenMod nightly, and it deleted my gapps.
Then, I got an Android l gapps package and installed that
Now I still have all my apps installed, but only chrome shows up
Now I don't know how to update my apps because I usually just press update all
Can someone help me fix 4th is problem?
I am using the same google account as used to previously install the apps
Jeffmagma said:
Unjust updated CyanogenMod nightly, and it deleted my gapps.
Then, I got an Android l gapps package and installed that
Now I still have all my apps installed, but only chrome shows up
Now I don't know how to update my apps because I usually just press update all
Can someone help me fix 4th is problem?
I am using the same google account as used to previously install the apps
Click to expand...
Click to collapse
Here is a similar thread: Google Play not detecing installed apps and not-updated apps.
Maybe thi scan help in your case too.
If not, you may try different version of Gapps, such as this for KK ([GAPPS][4.4.x] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's) [2015-01-17]), or this for LP ([GAPPS][5.0.x][BETA] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's) [2015-01-16]).
They should work for CM too.
Good luck !
Thread closed and thank you.
Hi guys,
I searched the forum and I found a thread with "Google Play Services Stops Working" with no fix for this problem and unfortunately this issue started affecting me when I completely wiped the phone with OS (accident) on it and started from scratch.
I tried latest version of play store, not so late, different installation methods and the result is still same. After awhile the google account is deleted and play services are not working.
I forgot to mention when the OS was restored and updated I had to manually install Play services.
It says not supported by my device. Is there any way how to get it permanently fixed again ?
Thanks in advance,
E.
How did you install GAPPS (Google Apps with all the needed services?
I downloaded latest play store .apk and installed it from there. I even tried different versions, different sources ...
It's working for few hours and then it stops working ( I click on play store and it's just about to open, few ms quick white flash and nothing happens) and I have to reinstall it and redo my accounts.
You have flashed all the services and apps google play store need?
Try flashing the latest opengapps package.
Use the following options to generate:
Platform: ARM64
Android: 5.1
Version: you choose
maybe try install gapps from HiAPP (market from huawei)
pavlick said:
maybe try install gapps from HiAPP (market from huawei)
Click to expand...
Click to collapse
No need. I had the same issue; at some point my stock Play Market just vanished, ran into a bunch of other issues, but solved it by installing a full gapps package generated on opengapps (I use the pico version).
I installed gapps successfully :highfive:
There was some error with MD5 but at the end it was fine.
Let's wait and hope it did what it was supposed to do.
Thank you guys
E.
Can someone post a step by step guide on how to get this fixed? Would really appreciate the help. Started happening to me today after i installed the latest EMUI update.
LRTan said:
Can someone post a step by step guide on how to get this fixed? Would really appreciate the help. Started happening to me today after i installed the latest EMUI update.
Click to expand...
Click to collapse
I also will be Thankful for some "step by step" instructions
how to find out for sure on what recovery version is my phone...?
how to do a "force update" ...?
how to "total format" my phone and flash all needed including GAPPs
Thanks,
Michael.
[SOLVED] Solution below. Original Post:
Hello everyone,
i am currently modding a Moto G 2013 for a friend of mine with the latest CM13 nightly and everything worked fine so far.
I've installed TWRP 3.0.2 without any problems as well.
Now i've tried different versions of ARM 6.0 GApps packages and all result in the same errors:
After booting, there are constant messages of both the Setup Wizard and the Google Play Services stopping.
With GApps mini i was able to stop the Setup Wizard messages by clearing it's cache and granting it permissions - as some online articles suggest.
But after trying out dozens of fixes for the Google Play services it's still crashing. (Tried stock, full, aroma, mini, pico - all from a working fresh CM13 installation)
Is there anything i might have missed or is CM13 + GApps just unregularily broken? (It's broken in the same way when testing CM13 on my Xperia Z1c).
I haven't had any problems with GApps on CM12.1, but i'd really like to get CM13 working.
Thanks for any advice or tipps! =)
Click to expand...
Click to collapse
Solution:
This thread and allowing Setup Wizard all permissions.
Maybe this is a very stupid question but I really have no idea why this problem occurs
My phone (HTC One S Ville mit Resurrection Remix (Android 5.1)) worked perfectly fine until last Friday.
At this date a new update of Telegram Messenger was released. I installed it and while installation of this app my phone did a restart and got stuck in a bootloop.
I restored using TWRP and retried - same problem. I also deleted the app and its data to do a fresh install - bootloop after installation.
Furthermore I noticed the exactly same behavior for the last update of WiGLE. All other apps could be updated to their latest versions without problems.
I used Google Play to update these apps.
What could be a problem for that? Is android just too old to these apps or could there be a collision with something installed on my phone/the ROM? How can I debug this?
I am not an android expert and I am very thankful for any kind of help :')
Thank you! =)
Same Problem with LG G2 mini / Android 6
Hello,
I'm facing the similar problems since a few days. Running Resurrection 6.0.1 on LG G2 Mini.
It started with installing maxdome-app at thursday, last week. Phone went into bootloop.
Wiping and or deinstalling the app in safe-mode did not work. So I restored to an older backup. This worked some time but ran into bootloop after a while ( I do not know what I've done exactly to get into this, this time).
I tried around a little. One part was a fresh install of cyanogenmod 13. This worked some time and I could find out that installing telegramm messenger had the bootloop-effect repeatable.
Sorry for not giving any help to the thread-creator but I hope we can give any more information to each other or anyone else can help?
Right now I am installing apps and backing up all the time to get some half-working system, but better ideas would be appreciated
Good to know that I am not alone
I figured out that there are a few more apps causing the bootloop. Here is a list:
WiGLE Wardriving
Telegram Messenger
pr0gramm.com app
Playstore Changelog (XPosed Module)
Statusbar Download Progress (XPosed Module)
Maxdome
I already updated Xposed Framework, Google Play Services and Google WebView to prevent incompatibilities. Problem still exists.
I updated everything as far as possible and made a backup using TWRP so I can restore my OS at any point. Further you could backup your apps using Titanium Backup. I it worth its price!
I started facing a similar problem of app updates causing bootloops on my device which was running CandySix ROM / 6.0.1. Apps causing bootlooping included Greenify and Nova Launcher. I had another device which has a factory 6.0.1 ROM rooted with Xposed and that device didn't have bootloop issues with these same versions of apps. Fortunately I was able to update the first device to a LineageOS 14.1 7.1.2 ROM and once again continue using the latest version of apps without bootlooping issues - but I never did understand exactly what was causing the bootlooping problem. That was a rather frustrating experience.
When the first bootloop happened, I was updating one single app, so I knew it was probably the one I should roll back to the previous version to fix the problem - so I didn't have to resort to a full TWRP restore.
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
In my case I can boot to custom recovery/TWRP to delete the app apk from the its /data/app folder - which basically prevents it from running when I reboot the phone. I also use an apk extractor app to save the apk of all apps I install and I also use Titanium Backup - so between those two I have copies of the older apk versions to install. You can also find older apk versions on apkmirror.com.
Depending on the severity of the bootloop, you can also connect your phone to a PC and use adb to disable/uninstall the app causing the problem if you know which one it is.
-kw said:
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
Click to expand...
Click to collapse
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Thanks and can confirm that deleting the app folder/apk via twrp can help. I got back into my android 6 again. For me seems more that DavDroid caused it (but Telegram was suspicious, too).
DavDroid mentioned in the last update on 4th November, that they released a workaround against crash and bootloops on some custom roms
Depending on how old your TWRP backup is, restoring from TWRP is an option. But often I have not made a backup in a while or made many recent changes that I didn't want to lose, so the other ways I suggested are more time efficient in some cases.
-kw said:
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Click to expand...
Click to collapse
Upgrade to Android 7
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Glad you were able to update ROMs and escape the bootlooping problem
I have been running LineageOS 14.1 for about a month now without any bootlooping issues due to app updates - so I expect you won't have any issues. I did cause some dread time consuming to resolve bootlooping due to some bad substratum themes, but that's a different issue altogether .
michibr said:
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Click to expand...
Click to collapse
@michibr:
I am very pleased with my Resurrection ROM; but this is stuck on Android 5.1. I will give a new ROM a try when I have the time for that
At this time it seems like this is the only solution of escaping the bootloop-problem
FYI
I updated to Android 7.1 RR and now I can update all my Apps without problems
I am sorry that this is the only solution I can provide, but still better than nothing
Hi all,
I'm having exactly the same problem, it all started with FB, then some other apps.
I had to reboot into Safe Mode to uninstall those apps.
I'm running on cm12.1 and I have my own reason not to upgrade to higher Android.
Am hoping someone can come out with a solution.
For now, here's my list of apps:
- Facebook (Facebook Lite is fine)
- Telegram
- Bluemail
- Local telco app
I am sorry to inform you that I did a lot of research and was not able to find any other solution than upgrading to a higher android.
The problem is with appt2 someone reported it in google's issue tracker and someone from goole descriped it in detail here's it :-
CyanogenMod has this function getPkgName (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/AssetManager.cpp). It creates a ResXMLTree on the stack and points it at a buffer from an asset without making a copy. Then it closes the asset before the ResXMLTree is destroyed.
For apps built by aapt, this is benign. However, aapt2 produces UTF-8 string pools, which cause the ResXMLTree's ResStringPool(mStrings)'s mCache to become non-null in ResStringPool::stringAt (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/ResourceTypes.cpp). Then ResStringPool::uninit dereferences mHeader (which is now dangling), and a crash ensues.
This crash shows up in different ways. On one Cyanogen OS device, the launcher crashes when an app built with aapt2 has been installed, but only if the manifest is large (probably due to how deallocation happens for small vs large blobs). On another device, system_server crashes at boot if an aapt2-built app is installed.
We're attempting to work around this with a custom build of aapt2 that always produces a UTF-16 string pool for the manifest. Results so far are promising.
Can this be patched somehow at the OS via xposed for all of the roms that won't get updated?
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Is this .zip patch for any device with any Lollipop 5.1.1 ROM?
Because I just installed it and my HTC one X with Resurrection Remix ROM (Lollipop 5.1.1) goes black after the HTC logo.
lescht said:
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Click to expand...
Click to collapse
Hello what is about cm11 kitkat 4.4.4 sameissue but no fix-
could anyone make a fix? Please help.