Serious performance and battery drain issues - Galaxy Tab 2 Q&A, Help & Troubleshooting

I haven't been on here for a while...
I have a p5113 and I flashed unlegacy-android 7.1 and s1mple-espresso kernel several months ago. About 3 months ago, it suddenly started having issues. I had not made any changes to the device for several months, but it just started happening one day. The system would lag really badly (completely unusable) unless I set the CPU governor to anything other than interactive. Even the powersave governor performed better than interactive. The system also would not put the CPU to sleep, so the device had severe standby battery drain and even got warm while in "standby." Unfortunately, wakelock detector apps could not find anything, so I just lived with it. A week ago, I decided not to put up with it anymore and flashed Omnirom 7.1 without the custom kernel. It worked fine for a bit, but the issues came back. Niether wakelock apps nor the built in wakelock scanner could find anything, but the device won't go to sleep, and it has unusable lag when set to the interactive CPU governor. What could be causing these issues? It is just a coincidence that I'm experiencing it on two different ROMs, or is it somehow related?

A new problem just appeared. Every few minutes, the device will almost completely freeze. Navigation buttons and volume keys also stop working. However, the power key still kinda works. The screen turns on and off but does not lock. The freezes last a couple seconds (a minute at most), then the device will react to all of the input its been given in that time as if it was all done in one instant. I usually get an app not responding dialog for the active app after the incident. In apps written in C/C++ such as Minecraft and SimplePlanes, only the UI freezes but the rest of the app keeps going. This leads me to believe it is a problem with the Android Runtime that interprets and compiles Java code. I can't figure out why, but the freezing issue almost completely goes away if I disable kernel samepage merging. Wiping cache and dalvik/art cache does not fix it.

Never mind. I'm giving up and going back to marshmallow.

Related

[Q] Reboot, crash, freeze tracker?

Are there any apps available tharly can runin the background and track when my phone reboots, crashes or freezes? How about logging battery usage?
For some reason, my Dell Streak has been having issues lately. To try and fix it I have even reset back to defaults and reinstalled the firmware.
What has been happening is...
- freezes when the phone has been sleeping. Requires a battery pull.
- random reboots.
- getting extremely warm in my pocket and draining the battery.
Since the phone is dead or reset, I can't determine what was happening when the problem happens.
CPU Speed
My Phone was doing that same thing. When I installed an RCMix3d kernel it nearly doubled my CPU speed and was making my phone crash and freeze all the time. Once I got SetCPU and set up some profiles to lower my CPU speed to something it could handle everything has been smooth sailing since.

[Q] EOS4 #99 w/ KatKernel_96_JB4.2_Lidpatch SODs and RRs

Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Turning on Fsync in KatKernel
pursleyt said:
Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Click to expand...
Click to collapse
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
pursleyt said:
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
Click to expand...
Click to collapse
1 RR while tablet was asleep, plugged in and charged to 100%.
Solved
pursleyt said:
1 RR while tablet was asleep, plugged in and charged to 100%.
Click to expand...
Click to collapse
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
pursleyt said:
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
Click to expand...
Click to collapse
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
pursleyt said:
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
Click to expand...
Click to collapse
using preview 181 kk96 dock sd removed getting RR during sleep, I tried with fsync=on, rr's stopped but that prevented tab from entering deep sleep. now trying with microsd removed. still docked

[Q] TF300T won't wake from sleep

I'm trying to help my mother revive her TF300T. She was running the stock 4.2.1 ROM and it was borderline unusable. Task switching was horrible and upon waking from sleep, when that worked, it would be several minutes before it would work smoothly - it definitely wouldn't work when background sync was going on. More often, once it went to into deep sleep, it would have to be manually rebooted since it would not wake. She also had an issue where the volume turns itself up.
I installed CM11 on there and much of the usability problems have been taken care of. It is much, much speedier. However, it appears it still will not wake from deep sleep, at least sometimes. The volume issue persists as well. The latter is probably a hardware issue. I'm wondering if the inability to wake is also a hardware problem. Any ideas?

Oneplus one acting weird

Hi!
Recently, my oneplus one has been misbehaving or acting weird. I'm running the latest CM13 (has been like this for the past 5 builds or so) and the latest boeffla kernel (also tried a couple of versions) here are the things it does:
Randomly freezes and turns off and won't automatically reboot (sometimes takes about 30 minutes before I can even hard reboot it sometimes the red LED is on and lots of unreadable partitions show up on my pc when plugging it in) and it will also enter some super battery drain mode where it can kill it's entire battery in less than an hour
the WI-FI randomly dies and won't reconnect until rebooted
Top part of the touch screen not really workig? Like the adress bars in browsers don't work but when I try to interact with the notification shade in that area it works fine...
Battery drain: not really an issue, just started happening today with nova launcher sucking the battery dry
And overall it's really slow...
I'm not sure if it's boeffla kernel or CM13 or the phone is just dead...
I tried to reflash a dozen times so not sure
Can anyone help me with this?
Same here but i have everything stock... Except Root and bootloader unlocked
Flash stock rom, make no changes don't even restore Google data just set it up as a clean device, and see if it's still misbehaving. If it is its hardware.

SNS_SMD and RMNET_DFC wakelocks

Greetings, I have a problem with constant wakelocks on my MI11i phone since the day I bought it. Those wakelocks drain battery by 30% overnight, but also cause increased drain during the day in standby too since they instantly kick in as soon as the phone is locked, overall resulting in poor battery life. Even thou I am not an advanced user and has no need of it, I went so far that I completely factory reset the phone(this was the 2nd time), then reflashed new recovery and new official ROM to see will that sort the issue, then for a good measure I also rooted it with TWRP and Magisk. I tried underclocking the cpu to the lowest but it makes no difference while in standby since obviously that isn't the case. I tried using icebox but there were no processes that had SNS or RMNET in their names, so I just froze some analytics apps. Both wakelocks are gone as soon as I turn on the airplane mode or switch to wifi. Any app that can help me freeze those or edit something in kernel?
I found a rom that fixes the wakelock, listed here https://miuiflash.com/roms/miui-csx/alioth/miui-csx-v13-0-8-0-stable-alioth
But i couldn't find a way to contact the author for more info can i fix the kernel myself

Categories

Resources