Hey all, I was updating the system apps of my mtk6589 device (infinix X451 - RBoltQ, android 4.2.1) device ie calender, email , deskclock, launcher etc to that of the android 4.4Kkat . Thay all worked perfectly it felt cool. I then updated my camera to that android 4.2.2 (all done with root explorer and link2SD ). Later on I came across the google camera. It always FC so I thought maybe making it a system app (using Link2SD) & deleting my other camera apps will resolve the issue. This didn't work . I even changed some lib files like I saw on a blog (libjn...mosaic,liblightcycle, lib..google.. - backed them all manually 1st though) still no avail. Now I restored the normal camera and the lib files, with their required permissions (root explorer) but ALL CAMERA apps installed FC ..even with a hard reset, the camera icon is NO LONGER there , only the gallery (for the stock camera). Apps like Antutu BM and Dx toolbox can't detect the camera (front and rear) or say Not supported. Same with apps that use Cam or flash or both. Flashlight too is no longer available while I noticed that the Glauncher now FC when I want to change wallpaper and the STOCK RECOVERY now shows an android with a red exclamaition mark. Gone 3 weeks without the camera, FL and now going through blogs and forums & I just don't know what to do.. Please any help will be appreciated as I don't want to loose my mtk device or its camera - even as my joy of getting my first android smartphone last year (dec 29) is turning into a nightmare. Thanks in advance.
(Sorry mods if I posted in the wrong section, kindly help me move it to the right place if possible, thanks)
Did you make backup before? I don't think so. Try to flash stock recovery and then install stock ROM (or custom ROM).
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.
Hello guys!
At first when i was using a Custom Rom Lineageos 14.1, video recording wasn't working.
So the temporary fix for that was using a build.prop tweak "persist.camera.HAL3.enabled=1".
Which did work. I was using AICP C-Rom with that tweak and everything was fine for some weeks.
But then i started getting an error.
I'm encountering an error when trying to record a video on my Lenovo P2.
Everytime when i try to record a video the following Message appears in a little toast message.
"Could not start media recorder."
"Can't start video recording."
Things to know and what i've already tried to trouble shoot:
- I'm currently using Custom Roms: RR - right now.
- I've done a Clean Flash, Dirty Flash, Rom Flash only.
- I've tried flashing Stock Firmware with Fastboot commands, flashed successful and all, but the camera just gave errors. Before i ever encountered an Error, the stock firmware was working fine. But now, it doesn't.
- i cleared cache.
- Script to enable Camera2Api : persist.camera.HAL3.enabled=1 , tried with and without.
Only working video recording App: Footej Camera
So my question is ..how might i be able to fix this and is this a hardware issue?
#Which i highly doubt..because Footej Camera CAN record video just fine. It is so weird.
Solution: It was so simple, i uninstalled Xposed and installed Systemless Xposed.
sm00th4f3 said:
Hello guys! At first when i was using a Custom Rom Lineageos 14.1, video recording wasn't working...
Click to expand...
Click to collapse
I don't have this device but, I believe that one or more of the following threads may be helpful for what you are looking for and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3725591
https://forum.xda-developers.com/showthread.php?t=3668029
https://forum.xda-developers.com/showthread.php?t=3714295
https://forum.xda-developers.com/showthread.php?t=3590025
https://forum.xda-developers.com/showthread.php?t=3723968
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks ibuprophen!
But i alread found a fix. It was Xposed. It caused some error, and the magisk Version did the trick.
could you be more specific, I have the same problem, but I don't have xposed in my note 3
Played around with installing TWRP so I could try and flash LineageOS
Couldn't get it to flash, so I just flashed the stock firmware released by Umidigi
Now even after multiple formats and flashes of different firmware versions (All official stock FW) my camera app is missing
Upon going into App Manager the Camera App does appear in it and I can forcestop it, but no way of getting onto the camera, downloading Camera Apps from Play Store doesn't work either as it says the camera is either busy or not found
Unsure what to do, I've flashed and flashed, everything's back to stock too, once you format or flash and the phone sets up, the app icon is missing on the homescreen where it's meant to be
I am trying to install oos camera in the OP6 from the apk store into my lineage. and when it is download in the phone, I can open the app, but the screen keeps black and cant see anything.
anyones knows how to use oos camera in the lineageOS??
pekas said:
I am trying to install oos camera in the OP6 from the apk store into my lineage. and when it is download in the phone, I can open the app, but the screen keeps black and cant see anything.
anyones knows how to use oos camera in the lineageOS??
Click to expand...
Click to collapse
I had the same issue. Installed com.oneplus.camera_3.8.116-23270457_minAPI28(arm64-v8a)(nodpi)_apkmirror.com because 3.8.xxx is shipped in official OxygenOS builds. I was able to take images with the front camera (long press on app > selfie), but whenever switching to back camera, the app crashes. I did record a logcat but don't know if anybody can help with that...
Unfortunately, it will not work. Reason why is the Oneplus Camera app requires some system frameworks to be installed. Thats why on 3rd party roms without the cam app, it is incredibly unstable/broken. One roms where the oneplus cam is stock, it will work fine because the devs included the necessary cam frameworks. Unfortunately, your only solutions is to either use gcam, or install a rom that has oos cam installed by default.
Cheers.