Hi All,
I've recently bought a H60-L02 terminal. But I'm having some problems, since the antivirus application is detecting a virus in the twitter application which comes preinstalled and cannot be uninstalled.
The app cannot be updated from Play Store, since there is an error about the provider authority already exists....
The exact version which is coming with the phone is:
H60-L02V100R001CHNC00B1116SP02 (with EMUI 2.3)
Has anyone faced this problem? Should I try to root the phone and eliminate the app, or should it be better just to upgrade the ROM to a newer one?
Hi all,
A few months ago I've installed a Developer Preview of Android 6.0 on my Nexus 5. It has worked surprisingly well and today I've updated manually to the latest build (MRA58N). So no root, official recovery...
Android itself works well, but many apps from the Play Store stop with the famous "Unfortunately [App name] has stopped" message. Virtually half of them.
I've tried the usual ways to fix the problem like the cache cleaning and so on, but nothing works. The only way is to uninstall the app and to install it again. Of course, every one needs to be configured next.
What can I do? Of course, I can reinstall and reconfigure every single app, but maybe there is a global fix already available?
[Update]: I continue to investigate the issue because my other Nexus 5 has been updated perfectly. It seems the problem is related to the app permissions as some of them can't access the files, other launch, but can't open any file. Any way to repair the permissions?
Thanks in advance.
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.
Hi all
I installed android 8 on my mate 9 chinese version but unfortunately google launcher is not working on it after it crashed numerous times then i deleted it but couldnt re-download it from app store as it was giving a message it is not compatible with my device so i downloaded the APK but it is again not showing in my default launcher page then i tried to tick all permissions but the tab was grey not allowing me to provide permissions. In the middle of that i also deleted google now app to fix the issue and reinstalled but still the launcher is nowhere to be seen.
I said let me try downloading another launcher so i downloaded nova but it kept crashing as well and i deleted it.
Anyone faced this? Any solutions?
Hi everyone, I am a long-time user of the forum who recently purchased this tablet. It was delivered to me with fake global rom and I managed following the guides on the forum to flash the CN rom and block the bootloader. In doing so I managed to enable ota updates and certified L1, but now I have two problems, and specifically in this thread I will submit one that in my opinion is the worst: notifications problems. I tried to turn off battery optimization for the apps I was interested in receiving notifications, but despite this the notifications still do not arrive in any way, have you also had this problem? Is there anyone who by chance has solved it and in case knows how to help me? Thank you in advance for your support
You need to look for an app called security or security center. Within there you'll find an option to whitelist the apps you use regularly.
Sadly my tab suffers from the same bug described here
ZUI 13 Lenovo Security Center Problem Crashes?
Hi all, EDIT - I am reading reports this is also occurring on any Lenovo XiaoXin Pad Pro with the ZUI 13 update (perhaps it's the secondary update that does it?) not just the 12.6 inch version. I've just upgraded my tablet from a 2021 XiaoXin...
forum.xda-developers.com
So idk how to fix the issue
There is no fix yet as far as I am aware. They need to release an OTA. Its been an issue for a while though! What a joke the chinese software is!
antoniob91 said:
Sadly my tab suffers from the same bug described here
ZUI 13 Lenovo Security Center Problem Crashes?
Hi all, EDIT - I am reading reports this is also occurring on any Lenovo XiaoXin Pad Pro with the ZUI 13 update (perhaps it's the secondary update that does it?) not just the 12.6 inch version. I've just upgraded my tablet from a 2021 XiaoXin...
forum.xda-developers.com
So idk how to fix the issue
Click to expand...
Click to collapse
Did you try this version:
ZUI 13 Lenovo Security Center Problem Crashes?
Hi all, EDIT - I am reading reports this is also occurring on any Lenovo XiaoXin Pad Pro with the ZUI 13 update (perhaps it's the secondary update that does it?) not just the 12.6 inch version. I've just upgraded my tablet from a 2021 XiaoXin...
forum.xda-developers.com
Yeah sadly i think i have a newer version of the app and i can't install it , i tried also to uninstall with ADB command but it says failed not installed for user 0 , idk how to solve it
Also you can't disable it as the app controls permissions.
Do you know how to extract an app? When my XiaoXin Pad Pro 12.6 arrives late next week (hopefully) I could try and extract the latest version as I belive they've fixed it via an OTA.
i created a backup of the faulty app with es file explorer, but even trying to reinstall the one that is the same version gives me an error, i tried downloading app ops as someone suggested on the forum, but i have no idea how to set the apps i need.
The software on this tablet is a piece of crap, I'm regretting having locked the bootloader, at that point I should have flashed the twrp and the GSI.
if anyone else has any idea how to fix it i'm open to any suggestion and @mardon85 thank you for your help, i hope with your apk the problem can be solved.
I finally managed to uninstall the application using the ADB command " adb shell pm uninstall --user 0 com.zui.safecenter " but even in this case I can't install the working version of the apk (probably because the uninstall only affects my user and not the whole tablet, which would require the root).
also trying to install the older and working apk from the ADB terminal gives me error [INSTALL_FAILED_INVALID_APK: Package com.zui.safecenter is a persistent app. Persistent apps are not updateable.] even trying to ignore the version of the app
I'd say that at the moment I'm keeping it uninstalled while waiting for some good soul to give me some advice on how to proceed to solve the problem
I update you for those who may have the same problem. With the latest update the security app works smoothly, however the problem of notifications persists. Even disabling battery optimization for selected apps, whitelisting them for auto-start, and enabling all notifications within the app whenever I close the application from the task manager, notifications stop coming. This happens even when I simply closed the application and I continue to use the tablet for other operations (it is therefore not a problem related to the disconnection of the wifi or the standby of the device). I have no idea how to fix it, I tried everything (including some settings in the developer mode). So if anyone has any other suggestions I'm happy to try it
I have found that disabling the night mode in power settings, keeps my apps from getting closed even though I had the apps set for no battery optimization, and whitelist.
Do all Users on 13.1.555 suffer fromm the notification Bug like me?
Does a factory reset help?