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?

[KERNEL] [UNIVERSAL] [AOSP] WildKernel Reloaded v008 - October 21, 2013

WildKernel
README
Emmanuel U said:
Ugh... (oh how I've dreaded making this post, go grab the kleenex or you can just skip the next paragraph and get to the jist)
So my (previously used and "refurbished") myTouch is slowly becoming useless. So I had originally dropped it onto concrete (a month and a half ago) in which I didn't notice any visual/cosmetic damages so I assumed I was fine. However promptly after attempting to open my keyboard I notice my phone would freeze for 5 or seconds before registering the hardware event and rotating screen etc. It eventually began to progress to display weird digital artifacts at random times during use (which would cause annoying lag). Then one faithful day, the 'lag' was getting to excessive while I urgently needed to use my phone so I battery pulled in hopes of rebooting the phone as quickly as possible to use...but just my luck; the phone turned back on but the display didn't (in the sense that I felt the phone vibrate when I initially pressed the power button alongside seeing the small red light in my trackpad light up). So after a stressful day of trying to play with my phone in fastboot/adb I managed to turn my display back on. But now the display failure has progressed to the point of my phone only being usable when they keyboard is pulled out around 2/5 of the way and kept in that position....all other positions render the display useless. This makes it fairly difficult to use the device seeing as it has to be kept in this abnormal position to function.
Jist: I ordered a temporary Galaxy S2 off ebay until my contract ends so that I can switch carriers all together. So I won't really be able dev on this phone like I use to with it being broken. However I'll try to still occasionally update my roms as far as upstream...but any bug fixes at this point sadly won't be able to come from me as debugging on this phone is tedious. But keep in mind I'll still poke my head periodically in this forum and see if my 2 cents is needed anywhere. But don't expect anything more from me then 'upstream updates'.
Good day guys and remember to have a firm grip on your phone at all times.
Update:
First of all I'm quite flattered to all the people who offered up a MT4GS to giveaway, such a generous community we have here :good:
However this will not be necessary as I still have a slightly working MT4GS...the only reason I got a GSII is because it's not functional enough to be my daily driver due to the position it has to be held in to function. Nevertheless I can still develop on the phone (which was why I stated I was planning on updating this rom soon). But I'd like to say thanks again directly to @BaconPancakes and @Ziida and anyone else who may have been planning to offer me a a MT4GS...but it won't be needed.
Click to expand...
Click to collapse
Please report anything good and bad so that I know what to keep and what not to keep for a final release. This also helps me push out fixes faster when presented with lots of information.
Please wipe cache and dalvik cache
Note: If your S-ON, after flashing the zip you'll see a file called "WildKernel-boot.img" on your sdcard, use that to flash the kernel in fastboot (bootloader) with the following commands:
Code:
1. *connect device to computer and adb*
2. adb pull /sdcard/WildKernel-boot.img
3. fastboot flash boot WildKernel-boot.img
4. fastboot reboot
Download Latest WildKernel for All Android Versions (AOSP) S/ON + S/OFF
Mirror (HTTP) / (FTP)
OLD Downloads for WildKernel ICS and JB for S-ON(Mirror)
View all public kernel releases (Mirror)
You may find my source hosted @ Github
Info on Governors/Schedulers
Changelog:
Code:
[B]October 21, 2013 - ver008 reloaded[/B]
1. Rebase to Linux 3.0.100
2. Support for Android 4.3.1
3. Enable universal CPU frequency synchronization for all roms (not just mine)
4. Add back all governors
[B]August 27, 2013 - ver007 reloaded[/B]
1. [B]MAJOR[/B] Update to Kernel, lots of fixes
2. Now Universal with any Rom, S-ON/S-OFF (see first post for details)
3. Recommended if using any earlier version of WildKernel
4. Rebase to Linux 3.0.93
[B]April 29, 2013 - ver006 reloaded[/B]
1. Thermal updates
2. GPIO updates
3. MSM Framebuffer tweaks + YUV4444 additions to support recent CM 10.1
4. Update to Git Kernel v3.0.75
5. Add QCOM crypto engine [lomarb]
6. Fixed all battery/reboot issues that may have been kernel or rom related
7. Lots of driver updates (crypto, genlock, rotator, frame-buffer, kgsl, etc.)
[B]April 19, 2013 - ver005 reloaded[/B]
1. Change low clock speeds to stable volts to fix BSoDs
2. Update to Git Kernel v3.0.74
3. Update the Battery Driver
4. Build CIFS, TUN, and NIFS as modules to reduce zImage size
5. Update to CodefireX Linaro 4.7.3 optimized toolchain
6. Updated Early Suspend/Late resume drivers [intellidemand]
7. More tweaks from faux and showp1984 [intellidemand & badass]
8. -03 compiler optimizations
9. Fixed some bluetooth wakelocks
[B]April 17, 2013 - ver004 reloaded[/B]
1. Add QDSP6 V3
2. Update to to Git Kernel v3.0.73
3. Update to Latest CAF Bluetooth Drivers
4. Thermal changes and improvements
5. Major revamp to CM kernel (fixed black screens of death)
6. Lower Ondemand/Intellidemand phase frequencies to be more battery saving
7. Snapdragon Optimizations from earlier WildKernels
8. NEON optimizations
9. GPIO power button tweaks [upstream]
10. Increased Max frequency to 1728mhz (1512mhz by default)
11. Imported moderate undervolting from earlier WildKernels
12. Wifi Optimizations for battery life
[B]March 17, 2013 - ver003 reloaded[/B]
1. Major update upstream to scherhagen's base
2. Update to to Git Kernel v3.0.69
3. Update to Latest CAF Bluetooth Drivers
4. KGSL hacks to ensure glitch free changing on speeds and better hang detection
5. KGSL updare to Ville
6. Use Linaro Toolchain
7. Use *really* low power Wifi when idle
8. Allow Flash to be used at any battery percentage
9. Lower Badass phase frequencies to be more battery saving
[B]Sep 3, 2012 - ver003[/B]
1. Bluetooth updates upstream
2. Downgrade to linux Kernel v3.0.39 with custom libs to *really* fix lag
3. Badass back to default governor as the most stable
4. More LMK tweaks
[B]Sep 2, 2012 - ver002[/B]
1. Implemented USB forced fast charge v3.1
2. Downgrade to linux Kernel v3.0.40 to fix lag
3. Ondemand tweaks, early suspend updates, and is now default governor because of balance of stababilty, battery, and speed.
4. LMK tweaks
5. Updates to bluetooth from CAF (more battery saving and stable)
6. Updates to scheds from faux
7. mpdec ready but disabled until stabalized
8. A lot of improvements since ver001
Thanks:
SilverL
Scverhagen
Team Hydra
TeamDS
faux123
Sultan
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed

boot.img
please kernel boot.img from divice S-ON

Re: [KERNEL] WildKernel Reloaded v003 - March 17, 2013
Will try this tomorrow on CM 10.1 (by SilverL)
Greets Vauvenal7
Sent from my myTouch 4G Slide

Could you kindly list the governors this kernel? Also, am i right to say that this kernel contains all the features found in scverhagen's kernel? Thanks in advance.

This kernel is pretty good in performance and behaves better than scverhagen's but wifi isn't working properly.

SKAm69 said:
This kernel is pretty good in performance and behaves better than scverhagen's but wifi isn't working properly.
Click to expand...
Click to collapse
Whats wrong with wifi?

xmc wildchild22 said:
Whats wrong with wifi?
Click to expand...
Click to collapse
At times, it wouldn't turn on or the speeds be very slow. Reboot helps though.
But I like the kernel and how it works with option "disable HW overlays" unchecked. And video playbacks aren't glitchy. Also, it gave me about 5fps gain in NenaMark2 gbench.

Update, enjoy (and report feedback)

Thanks for the update!
FPS in NenaMark2 seems to be lower even on max 1.7Ghz. Still testing the kernel.

SKAm69 said:
Thanks for the update!
FPS in NenaMark2 seems to be lower even on max 1.7Ghz. Still testing the kernel.
Click to expand...
Click to collapse
Which governor/scheduler?
Everyone:
Update, enjoy (and report feedback)

xmc wildchild22 said:
Which governor/scheduler?
Everyone:
Update, enjoy (and report feedback)
Click to expand...
Click to collapse
Both intellidemand and Badass.
Will try the 005 version.

SKAm69 said:
Both intellidemand and Badass.
Will try the 005 version.
Click to expand...
Click to collapse
also you said scores are lower, but lower compared to what?

Build 005 broke my camera viewfinder.
The picture is fine after you snap the photo but green/garbled picture while looking before taking the shot (if that makes sense)
I tried screenshotting but the picture was also fine!
Might be just me, I wiped Dalvik after the flash though.

xmc wildchild22 said:
also you said scores are lower, but lower what?
Click to expand...
Click to collapse
I was getting around 48 fps on SilverL's and Tbalden's AOKP and CM stock kernels (scverhagen's base I think), now it's less than 42fps on v.004. 43-44fps on v.005.
The test is NenaMark2.
But overall the kernel seems to be smooth and nice.

SKAm69 said:
I was getting around 48 fps on SilverL's and Tbalden's AOKP and CM stock kernels (scverhagen's base I think), now it's less than 42fps on v.004. 43-44fps on v.005.
The test is NenaMark2.
But overall the kernel seems to be smooth and nice.
Click to expand...
Click to collapse
This is to be expected. These two governors seem to be doing what they're supposed to. They not made for benchmarks. The way mine is currently they have a middle ground frequency which i assume you may be hitting most of the time while this is going.
These 2 governors also take gpu into consideration and adjust their speeds accordingly. If it doesnt need both cpu and gpu to process, the cpu will actively throttle and not stay maxed which possibly results in the fluctuating scores. I get 42 fps on mine...(currently not updated to latest). You probably just ended up running the tests at times where something else was keeping the cpu at a higher frequency.
When I use the performance governor I get 52 but that governor keeps the cpu at the current max frequency (mine being 1080).
OpenGL scores will fluctuate with these governors... its nothing to worry about. I ran the test too, it doesnt seem to be as intensive as any game would be, doesnt require user interaction(something which also drives the cpu frequency throttling in games), so I wouldnt worry about these benchmarks. If you want to benchmark you should really be using performance as the stepping in any other governor will always vary based on load, and this tests puts more load on the gpu allowing the cpu to change frequencies as it sees fit.
Should mention my intellidemand score is 48 and badass is 42.

SilverL said:
This is to be expected. These two governors seem to be doing what they're supposed to. They not made for benchmarks. The way mine is currently they have a middle ground frequency which i assume you may be hitting most of the time while this is going.
These 2 governors also take gpu into consideration and adjust their speeds accordingly. If it doesnt need both cpu and gpu to process, the cpu will actively throttle and not stay maxed which possibly results in the fluctuating scores. I get 42 fps on mine...(currently not updated to latest). You probably just ended up running the tests at times where something else was keeping the cpu at a higher frequency.
When I use the performance governor I get 52 but that governor keeps the cpu at the current max frequency (mine being 1080).
OpenGL scores will fluctuate with these governors... its nothing to worry about. I ran the test too, it doesnt seem to be as intensive as any game would be, doesnt require user interaction(something which also drives the cpu frequency throttling in games), so I wouldnt worry about these benchmarks. If you want to benchmark you should really be using performance as the stepping in any other governor will always vary based on load, and this tests puts more load on the gpu allowing the cpu to change frequencies as it sees fit.
Should mention my intellidemand score is 48 and badass is 42.
Click to expand...
Click to collapse
Thanks for exlaining the things about these governors. But I've noticed that Badass keeps the max frequency only up to 908Mhz even if the load is 100% unlike intellidemand. That's weird. BTW I've tried the 1.7 performance and got only 48 without any background tasks.

i think this is a kernel issue...why does the phone keep resetting the max frequency is 1188?! happens no matter what i do. is it an adaptive governor limitation or something?

anitgandhi said:
i think this is a kernel issue...why does the phone keep resetting the max frequency is 1188?! happens no matter what i do. is it an adaptive governor limitation or something?
Click to expand...
Click to collapse
set the max freq with an app that is set to restore on boot (SetCPU, CM performance, etc.)

That's what I've been doing. And I even tested by restarting and it'll keep the 1512, then I'll check a bit later and it's back to 1188.
So I switched to kernel tuner thinking that won't have the issue, but I just checked and it switched back to 1188 and I haven't restarted in between.
Within one boot session it shouldn't just reset the frequency. And it's not just adaptive cuz I'm on badass now
Sent from my MyTouch 4G Slide using xda app-developers app

anitgandhi said:
That's what I've been doing. And I even tested by restarting and it'll keep the 1512, then I'll check a bit later and it's back to 1188.
So I switched to kernel tuner thinking that won't have the issue, but I just checked and it switched back to 1188 and I haven't restarted in between.
Within one boot session it shouldn't just reset the frequency. And it's not just adaptive cuz I'm on badass now
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
Sounds like you may have conflicting bootup settings or init.d settings. I would find a way to clean those up. Id suggest wipiing but no one ever likes doing that.

[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

[Kernel][23-12-2014]halaszk-UNIVERSAL5420

Changelog and downloads here:
https://github.com/halaszk/halaszk-UNIVERSAL5420/wiki

Issues and solutions :
https://github.com/halaszk/halaszk-UNIVERSAL5420/issues

https://github.com/halaszk/halaszk-UNIVERSAL5420/blob/master/arch/arm/configs/halaszk_defconfig_N900
I love your setting
Well i'm on the phone so i didn't see something but.. i advise to put row as the main scheduler (best for ssd hardware) and the conservative governor modified with the sampling rate min at 50.000.. the same for the ondemand..
If you need i'll patch those 2 for you.. (i don't know how to use github but i can patch the *.c)
Anyway the kernel seems good.. i'll test it tomorrow
---------- Post added at 04:36 AM ---------- Previous post was at 03:40 AM ----------
http://www.imgur.com/mLVh6cc.png
Works good with correct uv :thumbup::thumbup:

this is the best kernel with so many controls including LED which i was missing coz note 2's led is much brighter than ours
now i can fade in and out
cheers !

I think now I really need to root and install CWM on my phone!!!!!!!!
Features are great man. thanks. keep up the good work

When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase

great work best kernel for n900

karthickkatta said:
When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase
Click to expand...
Click to collapse
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)

halaszk88 said:
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)
Click to expand...
Click to collapse
Yes it works now ..what about AC main input current how to control it ? Will new features be added ?

synapse not work in screen setting in cpu and io it works i use trickster mod and its work when enabledmaster sequence or register hook

Cortexbrain script should be great. found this piece of information from dorimanx weblog,
This script will manipulate all the system / cpu / battery behavior. Based on chosen EXTWEAKS profile+tweaks and based on SCREEN ON/OFF state.
When User select battery/default profile all tuning will be toward battery save! But user loose performance -20% and get more stable system and more battery left.
When user select performance profile, tuning will be to max performance on screen ON!
When screen OFF all tuning switched to max power saving! as with battery profile, so user gets max performance and max battery save but only on screen OFF.
This script change governors and tuning for them on the fly!
Also switch on/off hotplug CPU core based on screen on/off.
This script reset battery stats when battery is 100% charged.
This script tune Network and System VM settings and ROM settings tuning.
This script changing default MOUNT options and I/O tweaks for all flash disks and ZRAM.
Click to expand...
Click to collapse

Flashed, need a couple of days testing, but at glance that is impressed
Sent from my SM-N900 using Tapatalk

Cortexbrain script functions from Dorimanx SGSII kernel with auto screen on/off module
Click to expand...
Click to collapse
You bring the best from Dorimanx kernel!!!

Synapse can't work ,FC everytime

who can recommend / advise the settings which will increase the battery life?
may be there is any instruction with examples?
thank you in advance!

Coffee
.
Hi halaszk,
Thanks for you work.
I have sent you a coffee over paypal. Confirmation number: 1C413099LN2241531
Keep up your work. Thanks again.

Sview Cover
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.

No uci support detected

alleshi said:
No uci support detected
Click to expand...
Click to collapse
After a reboot it worked for me.

First of all thank you halaszk for the best kernel for our note 3. Cheers and keep up the work. Just a little confusion. On set cpu n cpu spy the min frequency is 100mhz (the whole frequency table is different than the one in synapse) I'm a little confused due to this. Can somebody explain?
kadiremrah said:
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.
Click to expand...
Click to collapse
Can you post your voltages pls. Thank you

[Guide] Post-Root Common Issues, Bugs, and Fixes

This guide is meant to help those who have rooted their phones and are now finding it slow, laggy, messy, etc.
I've been seeing a lot of posts repeating common problems that have been fixed by other members of the forums, so I'll compile a list of the most common bugs and fixes for them (the ones that can be fixed) in this guide so people can refer to it instead of swamping dev threads with the same questions over and over again. The quicker we can get through the common problems, the quicker we can get to fixing the ones we don't have solutions to so far.
Disclaimer: After installing the ENG bootloader, you are going to experience less battery life. There are things we can do to improve this, but nothing I have discovered so far will get you back to stock battery life... except re-installing stock ROM. Also standard disclaimer that all of the fixes here are done at your own risk. I am not responsible for any of these fixes breaking your phone.
Bug #1: Phone is laggy after rooting the phone/Battery is down the tank.
Fix: The phone is (partially) lagging because the ENG bootloader automatically sets the CPU governor to "Performance." While this is supposed to lock the CPU frequency at the maximum values, it does cause a lot of heat and possibly throttling. Additionally, the max core clocks are set to 1.593Ghz instead of their actual maximums. Not every CPU Tuner will allow you to set the big cores separately, so look around for one that does if you don't want to use Kernel Toolkit.
First, use Flashfire to flash one of two zips provided by psouza4 on our sister Verizon Galaxy S7 (Edge) threads.
1. Kernel fixes & tweaks V15
2. Kernel fixes, tweaks, & Debloater
You need only flash one of these two zips. One additionally debloats the system, one does not. Choose whichever suits your needs.
What the zips do:
Adds a rotate button to the native gallery app.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
Removes bloatware and/or apps that can be downloaded from the Play Store and don't need to live in /system (fix+debloat version):
Next, install a CPU Tuner utility like Kernel Toolkit, then change the governor from "Performance" to "Interactive." Also change the max CPU frequency of the little cores to 1.593Ghz and the big cores to 2.150Ghz while you're at it. Leave the cores at their default minimum frequency. This will go a long way to improving the speed of the phone. Also make sure you that have the new settings to apply on boot. Every kernel manager should have this option somewhere.
Note: Although the max frequency in the settings screen will drop to some number, as long as you can see the CPU ramp up to the new settings in the information screen, then everything is fine. You can test the max frequency by turning the screen off and then back on.
Then, install sEFix and set entropy to "Ultra."
Lastly, install L Speed and:
Code:
-Main Tweaks: Turn on
-Battery Improvement
-OOM Killer
-Kernel Tweaks - "Light"
-CPU Tuner: Turn on
-CPU Optimizer
-LNET Optimizer: Turn on
-Google DNS
-Faster Streaming
-Faster Dormancy
-IO Tweaks: Turn on
-IO Boost
-Partition Remount
-RAM Manager
-Balanced
-Seeder
-Moderate
Their individual effects can be read up on here.
Bug #2: Weird "hurricane" icon in the corner.
Fix: This is related to the imsservice.apk which controls the RCS icon and the VoLTE icon being displayed. Someone has a modified version of the Note 5 imsservice.apk with these removed. You can find the apk HERE in the OP's attachment. HOWEVER, you will push this to a different location than the location mentioned in the guide there. You have two choices, you can either push the apk via ADB from you computer or you can copy the file using a root file manager.
ADB Method (Assumes you know what you're doing. Don't copy the code verbatim if you don't know what the command is doing):
Code:
adb remount
adb push imsservice.apk /system/priv-app/imsservice/imsservice.apk
adb reboot
Root File Manager Method:
Transfer the imsservice.apk to your phone. Anywhere where you'll remember the location is fine. Open the file manager with root compatibility and copy the file to /system/priv-app/imsservice/ and overwrite the imsservice.apk already in the folder.
Set permissions of the file to 0644 or rw-r--r-- depending on your file manager. You can set permissions using most file managers.
Restart the phone.
I've included the stock PD8 imsservice.apk as an attachment below if anyone has issues with the modified one from the guide.
Bug #3: Notification warning that system has been modified.
Fix #1: Disable com.samsung.android.securitylogagent & com.tmobile.pr.adapt using your favorite package disabler. This will hide all notifications associated with this app as well as the root check that you might have encountered.
Fix #2: This fix requires Xposed. You can follow the instructions to install Xposed HERE.
Then install the Xposed module NotifyClean, activate the module, and reboot the phone. You will then use this app to block the notification under the package com.samsung.android.securitylogagent by clicking on the package so that it is highlighted red. The notification should disappear!
Note: This app can also be used to hide the icon for WiFi Calling if it's annoying you. You can still use the WiFi calling function while hiding the notification.
Bug #4: I keep losing root.
Fix #1: Secure boot/startup has caused the loss of root. So make sure you DO NOT SETUP the secure boot option when you're first setting up the phone or any time afterwards. This is the same option that forces users to type in/swipe in their password on a screen with a black background. This is not the normal type/swipe your password on your lockscreen after a boot.
Fix #2: Disable Security policy updates. I've also heard that people who leave this option on lose their root after a couple of reboots. You can find this setting under:
Settings > Lock screen and security > Other security settings > Security policy updates > Automatic updates (Turn this setting off).
Fix #3: Disable auto-updates for apps in Google Play Store. It's possible that SuperSU auto-updated, breaking root.
Fix #4: Disable automatic updates for the phone. I don't think these run anyways on modified software, but it can't hurt. You can disable the applications responsible for automatic updates using Titanium Backup, EZ Disabler, or any other package disabler you know of. The packages to disable are:
com.sec.android.soagent
com.wssyncmldm
com.samsung.firmware.nfc
com.samsung.android.firmware.tsp
Bug #5napchat: Unable to log into Snapchat.
Fix #1: This happens if you attempt to login to Snapchat after installing Xposed. Just make sure you login to Snapchat prior to installing Xposed. Done.
Fix #2: If you've already installed Xposed, you can:
-Do a clean install through ODIN, and re-root your phone, install and log into Snapchat, then install Xposed.
-Uninstall Xposed by flashing THIS through Flashfire, uninstalling the Xposed framework app, and clearing the data on your Snapchat app. Then login to Snapchat and re-install Xposed.
Bug #6: WiFi passwords aren't being saved
Fix: Use a root file manager like Solid Explorer and go to /system and open/edit build.prop. Scroll down or use the "find" function to search for ro.securestorage=true and change it from true to false (ro.securestorage=false). Save the file. Done!
If you guys have any more bugs that you run into, please feel free to post them here. Anyone who knows of any additional fixes to these bugs or solutions to any bugs that others post, also feel free to add them in the comments and I will compile them into this guide when I get a chance.
I've included the PD8 imsservice.apk below if you need it

Reserved
Reserved

I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too

thegameksk said:
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
Click to expand...
Click to collapse
Not every CPU Tuner utility will let you set the individual big.LITTLE cores separately. Try using the one recommended or look for another one that does allow it. Kernel Toolkit is the only one that I remember off the top of my head. I'll also make an edit in the post to avoid further confusion.

hey all, does anyone have or has experienced your incoming calls not being recieved? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,

Great post! Unfortunately I'm having problems with smart view after rooting. Every time I try to screen mirror it works but it is extremely laggy making it unusable. This has only been an issue since root and I've tried mirroring to three different devices and it's the same with all of them. I followed the instructions in this thread to see if these tweaks would help but they didn't change my screen mirroring issue at all. Is anyone else out there experiencing this?

little help please.
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks

cris_epic said:
hey all, does anyone have or has experienced your incoming calls not being received? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Click to expand...
Click to collapse
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?

JKLIMES1 said:
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
Click to expand...
Click to collapse
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.

JKLIMES1 said:
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
Click to expand...
Click to collapse
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app

Is this what you mean about the cores?

thegameksk said:
Is this what you mean about the cores?
Click to expand...
Click to collapse
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.

h.nocturna said:
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
Click to expand...
Click to collapse
AWESOME!! changing the permissions did the job for me. Thanks.

h.nocturna said:
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
Click to expand...
Click to collapse
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593

cris_epic said:
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Trying changing the permissions as mentioned, that worked perfect for me.

thegameksk said:
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
Click to expand...
Click to collapse
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.

h.nocturna said:
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
Click to expand...
Click to collapse
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307

thegameksk said:
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
Click to expand...
Click to collapse
This is the expected behavior. This just means that they will clock up to the max when there is a high load, but then drop back down to the lowest frequency to save battery when there is nothing to be done. Everything is working as it should.

Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.

thegameksk said:
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
Click to expand...
Click to collapse
Mines was hot just with normal usage. I used every tip and fix that people suggested but it was still pretty slow and lagged if I had a game running and a couple of more apps running. Battery was OK though.