Hi,
I new to the whole rooting scene so please bear with me.
I unlocked the bootloader and rooted my phone (using twrp and SuperSU) and installed LMT Launcher v2.0 RC5.
Setting it up was easy, however when I use it to launch an app nothing happens.
Well, only the wifi and bluetooth toggle actions actually work.
But setting a Pie Item to trigger an arbitrary app - this does not work (by work, I mean nothing happens when you select that pie item)
any help appreciated.
thanks,
KS
Hi,
I'm running ARHD 9.1 on an HTC One M8, S-ON.
I've noticed that whenever I boot up my phone, some Xposed modules or root apps in general won't autostart.
These include GMD Gesture Control, LMT Launcher (I think this does autostart, but the service is always deactivated - I have to manually activate it every time), Adblock Plus and a few others.
I'm wondering how to get them to load automatically pretty much as soon as I boot up my device? I've tried some non-root Play Store apps (like Autostart - No Root) but they take ages loading each app. I'd love to be able to have selected apps already running, with automatic SuperSU access, as soon as I access my phone from a boot/reboot.
Thanks in advance!
(also, sorry if this is in the wrong section, I'm quite new to XDA and the whole rooting business)
Hi!
I know from experience that LMT takes a bit to start after booting. That's just how it is. Takes awhile for gapps to start running after a boot.
Tho, if they aren't auto starting...you have either somehow disabled them from auto starting, or you have a root issue.
Anyway....here us the section for your device....specifically the Q&A section. You will need to ask here for any issues with the M8....
>*HTC One (M8)*>*One (M8) Q&A, Help & Troubleshooting
Good luck!
I have a n915k, updated with Odin to stock 5.01 and rooted. I want to try and remove the Korean calling protocol and roaming data block. After a reboot, everything works fine for a few hours, then for some reason it decides I am roaming/in Korea (?) and when I try and make a call it asks ‘Calling Korea’ or ‘Calling other countries’. I can no longer send MMS messages, it decides I am roaming and ‘data is blocked’ (for MMS), but data still works from my Vodafone (New Zealand) supplier. A reboot and everything works again for a few hours.
I had the same problem with the original 4.4.4 but after rooting and installing Xposed framework there were some modules which fixed this issue. Unfortunately the framework isn’t working yet with 5.01. I tried the Aroma bloatwear uninstaller, however, that also seems to be 5.01 incompatible. I did write down all the items it wanted to uninstall and then manually uninstalled using Uninstall (root), which works well. Most of the items Aroma bloatwear uninstaller wanted to remove weren’t there, so I assume they have changed name or not in this ROM.
Any suggestions what these Korean market additions might be called, so I can remove them? I have already uninstalled anything with Kor in it. Or any other recommendations?
Thanks in advance.
Peterbnz said:
I have a n915k, updated with Odin to stock 5.01 and rooted. I want to try and remove the Korean calling protocol and roaming data block. After a reboot, everything works fine for a few hours, then for some reason it decides I am roaming/in Korea (?) and when I try and make a call it asks ‘Calling Korea’ or ‘Calling other countries’. I can no longer send MMS messages, it decides I am roaming and ‘data is blocked’ (for MMS), but data still works from my Vodafone (New Zealand) supplier. A reboot and everything works again for a few hours.
I had the same problem with the original 4.4.4 but after rooting and installing Xposed framework there were some modules which fixed this issue. Unfortunately the framework isn’t working yet with 5.01. I tried the Aroma bloatwear uninstaller, however, that also seems to be 5.01 incompatible. I did write down all the items it wanted to uninstall and then manually uninstalled using Uninstall (root), which works well. Most of the items Aroma bloatwear uninstaller wanted to remove weren’t there, so I assume they have changed name or not in this ROM.
Any suggestions what these Korean market additions might be called, so I can remove them? I have already uninstalled anything with Kor in it. Or any other recommendations?
Thanks in advance.
Click to expand...
Click to collapse
Fixed with:
http://forum.xda-developers.com/note-edge/general/roaming-pop-dial-solved-t2994143
Although Any Cut kept crashing when trying to add 'Activity', but concept worked, with another shortcut manager QuickShortcutMaker working
Hello people! My phone is IQX2(it is rebranded here in the Philippines as Equinox Night),and i am currently experiencing systemui has stopped. i've been struggling with this problem for quite some time , I flashed the stock ROM in hopes of averting the problem, but it still persists. Below is a list of steps i did after flashing rom
When the phone booted up i proceded with the configurations,such as time and signing in to wifi,
Then I reinstalled Titanium backup and installed some of my backups(first batch was app only),
Then i froze easy finder,android aosp keyboard,pinoy app shop(bloat),easy finder,the default launcher and start( i use nova launcher, freezing them didn't cause problems so far)
Then restored the rest of my backups(app+data ,like swift-key and some games)
Restored xposed installer then proceeded to activate module of lucky patcher and greenify
After reboot was fine,updated apps through wifi, decided to install app setting xposed module to make clash of clans smoother(full hd on 1gb ram is not a good idea gaming wise),but seemed to fail to take effect so I uninstalled it, after a reboot it's still working properly ,so i decided to download app settings again from the xposed app, after i activated module and rebooted systemui started crashing. I flashed the xposed disabler but it still didnt work.
I force hibernated the weather services,because i never used it,im beginning to think they are the cause(there are three of them)
Additional info: i flashed a cell standby fix and performance + battery saver tweak
I experienced systemui FC even before this, even without touching xposed,each time after rebooting,and one time i drained my battery and the crash appeared.originally i thiught the cause was gravity box,but it was eliminated because the problem still persists.
I thank you for taking the time to read this lenghty post and i hope to receive some help from the experienced people
Hi there,
I'm sorry but I can't find anything related to your question/device.
You must start asking that in the forum bellow for more answers from the experts:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
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.