After not having an issue for a while, NlpCollectorWakelock seems to be rearing its ugly head again. I've looked for ways to disable/block it but they all involve xposed (Amplify, Wakelock Terminator, etc.). I'm really hesitant to put xposed back on my phone as I feel I get worse battery with it installed, never mind the performance issues that arise when on TW.
Tldr; Is there a way to block the NlpCollectorWakelock without installing xposed?
Up.
Is there a way to kill this wakelock using adb commands?
Related
Hey all,
I am currently running my VZW Galaxy Tab with a stock 2.2 Froyo build that is rooted and running Boushh's KhasMek Kernel V5.
Ever since I installed that kernel, I have been experiencing constant force closes. It's really not any one app either, it is most of them. So far, I have put the freeze (via Titanium Backup) on all the apps that have FC'd a lot that I don't use. Maps was one of the biggest culprits. Facebook FCs a lot as well, and the only way to fix it is to go into app management and clear data. Similar issues with random games and such as well.
I have tried uninstalling and reinstalling multiple apps, and this helps for a time, but doesn't last too long. I have tried switching launchers, just in case it was somehow related, but it doesn't seem to be.
Basically, whenever I leave the tablet on idle for more than a few minutes, when I unlock it something hangs and I get an FC of a random app.
And a lot of times, it just does the single vibrate, followed by two quick ones, and nothing comes up as having FC. But, in the mean time, the tablet is unusable until it hits the second set of vibrations.
This is extremely annoying and is preventing usage of the tablet for periods of time. So, I am wondering, is anyone else experiencing this? If so, what have you done to fix it? At this point, I am inclined to just revert back to stock, though I would rather not.
Thanks for any insight.
As of now, I am constantly getting
com.google.process.gapps
force closing.
Okay so I'm really confused. I just had to get a refurb replacement for my Sprint HTC One because I accidentally bricked it and couldn't get it backed, took it to Sprint, they said it was water damage, blah blah blah. Whatever. So I get the new one in the mail, use it for a couple of days to make sure it's not broken, then root it.
All of that goes fine, with a couple of hiccups like flashing an outdated SuperSU. I use the TitaniumBackup from my previous phone to get all of my apps back. That goes fine. Note that I keep it a stock ROM.
Now here's the kicker.
I go to Xposed installer to install it. Normal install method won't work (it used to, but won't on this phone, probably because my old phone had a GPE ROM), so I switch to automatic install via recovery. So it installs, and- all of my mods work! Great! I disable Gravitybox since my phone is no longer on GPE and I come to a sudden realization. My multitasking won't work. I double tap the home button and it takes me back to the homescreen. It's like multitasking doesn't even exist. So I go through Xposed and disable all but the first mod, thinking I'll go through on by one to find the culprit. So I reboot with only the first mod active, and multitasking still doesn't work. Wha? This mod barely even does anything, much less to do with multitasking. So I think "Hey, maybe I should reinstall Xposed, that should fix it." So I uninstall Xposed and reboot, and viola, multitasking works. So now I wonder if it's Xposed itself that's screwing with it. So I reinstall Xposed, but don't activate any mods. I reboot, and sure enough, there's no multitasking. So it's 100% Xposed that's causing the issue, not a GPE mod conflicting with Sense.
What do I do?
Also note that the phone runs fine with Xposed enabled aside from multitasking not existing.
Thanks!
I'm not sure what the issue is with xposed but whenever the screen turns off sometimes the phone will completely reboot. It'll vibrate twice and then completely reboot. I have a log cat running in the background and after it reboots I check the log and before the reboot occurs it says system error and then XposedMainBridge. It doesn't just happpen with Firekat, it's happening with other TW Roms too. Does anyone else have the same issue. aswell? The modules I'm running are App Settings, Keepchat, No Lock Home, Snapshare, Wanam Xposed, and Xposed Torch
alfadog77 said:
I'm not sure what the issue is with xposed but whenever the screen turns off sometimes the phone will completely reboot. It'll vibrate twice and then completely reboot. I have a log cat running in the background and after it reboots I check the log and before the reboot occurs it says system error and then XposedMainBridge. It doesn't just happpen with Firekat, it's happening with other TW Roms too. Does anyone else have the same issue. aswell? The modules I'm running are App Settings, Keepchat, No Lock Home, Snapshare, Wanam Xposed, and Xposed Torch
Click to expand...
Click to collapse
Your correct i had the same issue i jst uninstalled all xposed modules and my phone never had another reboot again. Its still buggy thus causing all of the random issues throughout the rom.
I also have Xposed installed on Fire Kat V8 and I haven't had any random reboots.
It depends on the module really. Xposed isn't buggy lol! It's the "app" per se. I've had this issue with my Note 2 and it was that particular module. The only way to figure it out is trial and error. Uncheck one and reboot. Wait for the random reboot. If it happens... Check it back and just go down the list. It's pretty simple really. Just a bit time consuming. Fixed the issue without losing xposed. I mean with xposed... you can do anything! You can the customization of what most aosp roms offer without the broken crap that may not ever work on our phone model and enjoy a stable touchwiz based rom. Also you can't beat Dynamic Kat rom. Most other roms (not all) I've seen have just removed a few stock apps, deodexed, added a few init.d scripts, and call it a custom rom. Many claim custom kernels cause issues as well which is total bs. Problem was the user setting frequencies that were too low. It's all subjective but has just been my experience being in IT for many years and here as well. Good luck and enjoy the phone! It's pretty badass either way you go
I have 11 modules, those included are:
App Settings
Autoinstall
Bootmanager
Customshare
GravityBox
WanamXposed
Xposed Torch
Youtube Adaway
I would recommend intalling echoAEL kernel.
I suffer no reboots as mentioned in this post.
Ok it seems to be Wanam xposed causing the reboots for me when using power saving mode. Once i disabled wanam xposed module, no more reboots! Not sure which setting in wanam caused the issue, so will keep testing until I can figure it out. Don't want to have to choose between wanam and power saving mode lol. It's likely just a single setting in wanam causing the issue.
---------- Post added at 11:59 AM ---------- Previous post was at 11:23 AM ----------
sefrcoko said:
Ok it seems to be Wanam xposed causing the reboots for me when using power saving mode. Once i disabled wanam xposed module, no more reboots! Not sure which setting in wanam caused the issue, so will keep testing until I can figure it out. Don't want to have to choose between wanam and power saving mode lol. It's likely just a single setting in wanam causing the issue.
Click to expand...
Click to collapse
Ok i found the issue! It's DVFS in Wanam xposed. If it is disabled then when i turn on power saving mode the phone reboots. If you enable DVFS in Wanam though and reboot to activate it of course, then you wont have any more reboots when you turn on power saving mode! I posted in the Wanam thread to see if this is a bug or if 5here is any way to disable DVFS without causing Power Saving mode reboots. Will post back here if I get any positive news.
Hi. I rooted my S6 with magisk, but there is an issue where root randomly disappears. It happens within 2 minutes of the phone booting or whenever I launch and close the app. What could be the issue?
Possible culprits:
Aggressive battery optimisation.
MagiskHide fails to remount files after hiding.
Something completely different.
Didgeridoohan said:
Possible culprits:
Aggressive battery optimisation.
MagiskHide fails to remount files after hiding.
Something completely different.
Click to expand...
Click to collapse
Check response below. Don't know how to delete.
Flashed custom kernel, thought it helped. Wrote a long reply. It showed that it's uninstalled 10/10. Trying to disable the samsung useless battery manager. Where can I find the logs for MagiskHide?
TheHurtmaster said:
Flashed custom kernel, thought it helped. Wrote a long reply. It showed that it's uninstalled 10/10. Trying to disable the samsung useless battery manager. Where can I find the logs for MagiskHide?
Click to expand...
Click to collapse
The logs that might show something would be Magisk log, but preferably the magisk_debug.log, and possibly a logcat.
Didgeridoohan said:
The logs that might show something would be Magisk log, but preferably the magisk_debug.log, and possibly a logcat.
Click to expand...
Click to collapse
In your signature I saw that there's a troubleshooting guide. One of the solutions is to see if there's a faulty module. It seems that Pixel Experience doesn't like my phone that much. I left the phone alone for 4 hours so far and Magisk is still there. I found the culprit!
I'm just going to stop saying that it worked because I keep jinxing it. Here's the log. From what I see, it could be a battery optimization problem.
Edit: Debug log added too.
Disabled Samsung's battery optimization and android battery optimization that google implemented. Didn't help.
Did you ever figure this out? Keeps happening to me. Would the EX Kernel Manager's powersave cause this? Switching between performance and powersave is when I typically notice this... Will be pretty bummed if that feature won't work.
Running Pixel Dust on Pixel XL
Since rooting, I've been noticing small performance issues. Occasional, brief lag when scrolling left to news feed, small intermittent freezing in certain apps like Facebook or Instagram.
If I uninstall Magisk, the issues aren't there.
While it's not significant, it's noticable enough to be somewhat annoying. Not sure exactly what causes it, or if there's a way to eliminate the problem.
Solutions, if any, appreciated in advance.
I've had this problem too. It generally occurs shortly after booting. Force stopping Magisk (and opening it afterwards) seems to fix it.