Hey guys I'm currently running Hyperdrive15. I think there is a conflict between the hyperdrive tweaks and wanam that I can't figure out. After doing some tweaks in wanam now my power menu causes my phone to hot boot. I can't find an option for this in wanam to reverse it. I even tried to write the epm script in tasker but when it runs the command it hot boots. It is driving me nuts. Does anyone know what is causing this and how I fix it?
Related
Hey - I recently downloaded Das BAMF 3.0 RC3 with Imo's leanKernel on Extreme, and everything seemed to be running smoothly (at one point my touch screen did not respond, but a battery pull fixed that, ha). Just recently my app animations (for example, when I go to the app drawer, the apps 'fly' in and then 'fly' away when I close them) is VERY laggy, and they were not before. I did not update or change anything... I am using LauncherPro and WidgetLocker, but always have been. I have been trying to change settings around but no luck. Does anyone have any suggestions or know how to fix this? Any help would be appreciated! Thanks!
EDIT: And scrolling them the apps is very fast - it is just them flying in and out. Very strange...
EDIT 2: A completely other problem I am having - when I try to reboot, it doesn't reboot, it just shuts off. Is this a serious problem or something small that can fix it, or is this a known issue with the ROM that I will have to deal with until they fix?
Anyone heard of a problem like this? I'm on CleanROM but about half the time after a task runs the touch screen is only responsive for 5 seconds out of every 20.
The only task I run turns on bluetooth, run an autoconnect, and turns off wifi.
Searching came up with zip.
Details?
Clean or dirty flash? This can cause issues if it is the latter.
What kernel are you using? If you are using a custom kernel, undervolting too much can cause issues like un responsiveness.
Sent from my Xposed Beans Note 2
Flashed skydragon v3.0.1 the other day to my vs985. Today this circle with the slashthrough it [see img attached] showed up in my notifications bar. It doesn't seem to have an effect on performance or anything but I would like to be able to get rid of it. Does anyone know of a solution of had this problem before? Also, first time rooted here so if you do know how to fix it I would greatly appreciate an "explanation for dummies".
Many thanks!
That means Priorty mode is on. Turn it off or configure it differently to fix it.
Sent from my VK810 4G
Well they aren't exactly random...But I'm getting a hotboot when I enable power saving mode after a low batt warning under 10% or 5%.
SCH-I545 (VZW S4) Running:
*(Of course, locked bootloader)
· OC1-NK4 stock deodex
· Stock Kernel
· FlashFire
· Xposed for TW LP
-------------------------------------
· Modules:
Wanam, greenify, awesome pop up video & YouTube plug-in, xled, memory leak, MinMinHider, xtoast, disable clear defaults, network speed indicator, commander for Google now, *LP blurred systemUI*<<(not activated).
My guess is: I have DFVS disabled in Wanam and it's causing a conflict since power saving mode decreases the cpu speed and DFVS is preventing regulation of the table. Thoughts?
I would think that as well. Did disabling DFVS fix it(if you have tried)
XxD34THxX said:
I would think that as well. Did disabling DFVS fix it(if you have tried)
Click to expand...
Click to collapse
Haven't tried yet. Damned ROM gets awesome battery life lol...
UPDATE : Turned on power saving and unchecked lower CPU performance and screen output. And immediately turned power saving back off, and about 5 seconds later it soft booted. It gotta be xposed causing it. Just a gut feeling.
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more