Database Info

[Q] CYANOGEN 10 V6 Kernel + ROM Sleep Wake-up WiFi Crash Issue

Hello. I have been a "lurker" on these boards for roughly 2 years. I have rooted, flashed and installed custom ROMs, bootloaders, recoveries and radios on the following devices:
Samsung Vibrant (original samsung galaxy S)
HTC Amaze (a.k.a Ruby.... wire trick and all)
ASUS Transformer 1 WiFi Only model ( a.k.a TF101)
Anyway, I am posting for the first time. Because of this, I cannot post directly to the development thread involved with my issue. Never the less, here it is:
I am running RaymanFX's JellyBean Cyanogen 10 V6 (STABLE) with Rayman's custom kernel on my TF101. I was running a Revolver ICS ROM prior to installing this JB ROM.... or Revolution HD, I can't remember... anyway
I am having an issue with the TF101 either 1) involuntary reboot or 2) freeze/lockup/crashing after wakeup from sleep mode and complete loss of WiFi radio.
Yes, I have extensively searched the development threads and I found posts related to this one, but none of them solve the issue and I also noticed a few people have this same problem but have no known solution.
I have wiped and done clean install of this ROM several times always with the same result. I also flashed LiquidSmooth (Rayman worked on this ROM and his kernel is cross compatible) to see if it was ROM-related and discovered it is not.... this is a kernel issue. My wipe procedure is:
Factory Reset (cache/data wipe)
Run Superwipe script for TF101 from Android Revolution HD thread (format cache, data, etc...)
Wipe Dalvik Cache
Flash ROM
Reboot
Flash GAPPS (latest version linked on Cyanogen thread from goo.im)
Reboot
Everything runs buttery smooth and flawlessly, HOWEVER.... "Wake on WiFi fix" solution on RaymanFX's post does not work for me.
The "fix" is to designate WiFi Always On during Sleep. Changing this setting doesn't stick... WiFi still sleeps even with this setting corrected. With one caveat... Changing the setting to "Never" and then modifying WiFi Idle Timeout to "3 hours" and then changing the Keep WiFi on During Sleep to "Always" will delay the WiFi from idling out temporarily unless the tablet is in Sleep longer than 3 hours.... at which it idles anyway and causes a crash or reboot.
Secondly, I have discovered that the CPU Frequency setting under Performance could be part of the reason it crashes. I have "Set on Boot" enabled. Setting a CPU Frequency, regardless of governor, above 1408 Mhz WILL cause tablet to lockup/crash upon wakeup from Sleep as the processor jumps to maximum set frequency. If maximum frequency is set to 1408, it will stutter and lag out the system forcing it to become unresponsive to touch commands but "stable" and useable.... albeit very laggy. If the Max Frequency is set to 1200, it will NOT reduce the maximum frequency set for the CPU unless tablet is put into Sleep mode and then woken again.... it will constantly cycle between the "old" maximum frequency setting and the "new" maximum frequency setting (observed by monitoring the frequency in the Performance setting screen after changing from a higher max frequency to a lower max frequency and staying on the menu screen and allowing the CPU to "settle" without any user input).
I really like this ROM and I hate to give up on it, so I'm hoping someone out there will have an idea about what I can do to make this work... or at least recommend a different kernel that will work with this ROM and also has a way to change CPU frequencies and governers.
Any ideas?

[Q] Most battery efficient kernel and settings

I'm using and experimenting around with ARHD now.
Using Sultan's latest kernel.
I am a guy that likes battery a lot. Under what settings will the battery be the most efficient?
I'm using.
MPDecision(or smth) - On
Badass
Balanced
Max -810
SecP - 594(or the closest one to it)
ThirdP - 704(or the closest one to it)
SIO.
Vsync - ON
Fsync - Off(dont know what this really do anyway)
Max aggressive OOM
No Swaps.
-50mv
disabled logcat
If its okay I'd love suggestions to max out battery life.
Or the best efficiency to balance battery life and performance prioritizing on battery life. (at least no lags on UI)

KiD3991 said:
I'm using and experimenting around with ARHD now.
Using Sultan's latest kernel.
I am a guy that likes battery a lot. Under what settings will the battery be the most efficient?
I'm using.
MPDecision(or smth) - On
Badass
Balanced
Max -810
SecP - 594(or the closest one to it)
ThirdP - 704(or the closest one to it)
SIO.
Vsync - ON
Fsync - Off(dont know what this really do anyway)
Max aggressive OOM
No Swaps.
-50mv
disabled logcat
If its okay I'd love suggestions to max out battery life.
Or the best efficiency to balance battery life and performance prioritizing on battery life. (at least no lags on UI)
Click to expand...
Click to collapse
Don't make your OOM settings that aggressive if you want battery life. When you have the OOM set to the most aggressive setting, the phone will use more CPU power and thus battery power in order to clean the RAM. Another problem with OOM settings that aggressive is that applications you use frequently and multitask with will be terminated and when you open them the phone has to open them from scratch all over again, wasting much more power than if the program was still cached in the RAM.

I see. Thanks for the tip. I always thought when OOM is set to maximum, there won't be background apps running so it'll save battery.
If its not too much to ask, what about governor and scheduler combination? Max freq I feel smooth is 910. So I can coup with low freq. With no GPU underclock NFS most wanted still runs smooth so its fine too. I disable Vsync because it felt like its using CPU power to keep the sync on.

KiD3991 said:
I see. Thanks for the tip. I always thought when OOM is set to maximum, there won't be background apps running so it'll save battery.
If its not too much to ask, what about governor and scheduler combination? Max freq I feel smooth is 910. So I can coup with low freq. With no GPU underclock NFS most wanted still runs smooth so its fine too. I disable Vsync because it felt like its using CPU power to keep the sync on.
Click to expand...
Click to collapse
Disabling vsync causes a lot of visual tearing and I'm not sure if doing that saves power
Best I/O scheduler is SIO. As for governor, best for battery is badass. In the next release of my kernel I'll add badass GPU scaling so you can save even more power
Other ways to save power: use PM_MAX instead of PM_FAST and set the 2D GPU frequency to 145MHz.

[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

CM11 Nightlies, major lag after phone comes out of sleep

Hello,
I was able to see that a few others have been having this issue (noted in the dev section ) but I wanted to ask if anyone else has noticed that their CPU frequency does not go above 384 mhz after phone comes out of deep sleep?
Using CyanogenMod 11.0 Nightlies with stock kernel. A reboot of the phone makes is speedy again, however if the phone goes to sleep, its super laggy when it it wakes up. ( the only solution I found is to either reboot, or set the minimum frequency and max frequency to be the same 1500 mhz)
Please let me know if I am alone in experiencing this mhz lock to 384 mhz after phone wakes up.
Note: I did a clean flash and I am still having the same issue.

exhalum said:
Hello,
I was able to see that a few others have been having this issue (noted in the dev section ) but I wanted to ask if anyone else has noticed that their CPU frequency does not go above 384 mhz after phone comes out of deep sleep?
Using CyanogenMod 11.0 Nightlies with stock kernel. A reboot of the phone makes is speedy again, however if the phone goes to sleep, its super laggy when it it wakes up. ( the only solution I found is to either reboot, or set the minimum frequency and max frequency to be the same 1500 mhz)
Please let me know if I am alone in experiencing this mhz lock to 384 mhz after phone wakes up.
Note: I did a clean flash and I am still having the same issue.
Click to expand...
Click to collapse
change to ondemand in cpu settings, its not the default as to why idk, issue and fix has been posted many times b4.
if it is set to ondemand then you have some other prob or a setting that needs to be adjusted or app running in the background

vincom said:
change to ondemand in cpu settings, its not the default as to why idk, issue and fix has been posted many times b4.
if it is set to ondemand then you have some other prob or a setting that needs to be adjusted or app running in the background
Click to expand...
Click to collapse
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.

exhalum said:
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.
Click to expand...
Click to collapse
Interactive does usually end up being default, but I believe it was sometime last month where ondemand was removed from that ROM... which was the point where I jumped ship to another ROM.

Cpu Sticks at 384 On Call Or Wake
Hey All Hate to Bump this, but I have been having this same Issue for Months, Has Anyone Come Up With a Solution Other The Changing ROM??
I'm Also Having this "FREEZE" When The Phone screen is off and I get a Call but the Answer screen doesn't come up while the phone rings straight thru to Voice Mail, But if I slide to The right (On The Blank Screen) It answers.... I have messed with the CPU Performance Settings, and No Help....It does it On the Default settings and the Altered Settings??? I Checked the DEV Thread and Really Didn't see much about this....
Any Help Appreciated;
Mike

exhalum said:
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.
Click to expand...
Click to collapse
You can use conservative; remember to tick de option "Apply automatically on boot".

franzpimp87 said:
You can use conservative; remember to tick de option "Apply automatically on boot".
Click to expand...
Click to collapse
Ya I set it after I made that post and was gonna update today These Settings SEEM to be working extremely well... Will update if it changes..
Governor :Conservative
Min :192
Max:1512
I/O: NOOP
And it's Kinda Strange I/O on NOOP Is Actually throttling the CPU pretty well....Gonna run Like this for awhile and a see how Performance/Battery Use Work Out, And Probably Start Playing with the NOOP Setting, But from my tests it actually seems the most fluid, and Actually drops to 192 when no use....
Mike

Interactive governor VS sched

I've been reading about some kernel modification staff for couple of days now. I have searched for best kernel governor for Google pixel, there was 2-3 threads and in all of them people stated like "bro you're crazy, don't touch stock sched governor it's the most optimised one for pixel". I was like okay, I won't touch, I get it. But than I saw one thread where users voted for which governors they used, and interactive governor had enormous votes compared to other ones, so I thought there must be the reason for that. After messing up with interactive governor settings, I managed to get about 25-30% more battery life than I had on sched. all this without any noticable decrease in performance. Sched governor rises frequencies so often even if you are just on home screen and simply press empty space, all four CPU cores go to sky at max speed, whereas interactive governor is like quiet intelligent killer who sits and waits for big tasks to go full power. Screenshot below shows my screen on time. Before that, it was somewhere between 3-4 hours. So, any thoughts or links about why I could be wrong and what am I missing - would be very very useful.

Interactive again, this time more optimised.

Levan_i said:
I've been reading about some kernel modification staff for couple of days now. I have searched for best kernel governor for Google pixel, there was 2-3 threads and in all of them people stated like "bro you're crazy, don't touch stock sched governor it's the most optimised one for pixel". I was like okay, I won't touch, I get it. But than I saw one thread where users voted for which governors they used, and interactive governor had enormous votes compared to other ones, so I thought there must be the reason for that. After messing up with interactive governor settings, I managed to get about 25-30% more battery life than I had on sched. all this without any noticable decrease in performance. Sched governor rises frequencies so often even if you are just on home screen and simply press empty space, all four CPU cores go to sky at max speed, whereas interactive governor is like quiet intelligent killer who sits and waits for big tasks to go full power. Screenshot below shows my screen on time. Before that, it was somewhere between 3-4 hours. So, any thoughts or links about why I could be wrong and what am I missing - would be very very useful.
Click to expand...
Click to collapse
So other than changing to interactive governor, which settings did you change?

Arju said:
So other than changing to interactive governor, which settings did you change?
Click to expand...
Click to collapse
Decreased cpu frequencies a bit, also changed some settings inside the interactive gov. Exkernel manager app also helps a lot with blocking wakelocks. Right now, I have small cores set to sched and big cores set to interactive, I guess this variant also will make a good screen on time and better performance. Anything else is the same as it was on sched governor before

Here are the screenshots

Current Sot is 1:30 so at the zero battery it must be somewhere near 4*1:30=6 hours

I suppose I'll stay with sched+interactive governor