Related
Here is where I'll post my CM10 builds.
qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.
This is based on the amazing dhiru1602's work, big thanks to him.
Dowloads:
Google Drive
You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.
Sources:
Device, kernel, vendor
Misc changes/instruction to build this ROM. The patches not available on Github are here.
Please, read carefully the whole post.
There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.
I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.
CyanogenMod 10 - kernel 3.0
Click to expand...
Click to collapse
Known bugs:
Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
Rare reboots. If they happen, post the content of /proc/last_kmsg.
CyanogenMod 10 - kernel 2.6.35
Click to expand...
Click to collapse
Known bugs:
Missing HW composer.
WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
HD video playback suffer low framerate issues.
The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
There are sometimes lags in the preview while video calling with the front facing camera
Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.
Release changes:
Code:
Look for the name of the zip in this thread to find its changes. This is no more updated.
...
20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
20130416: Camera HAL: experimental changes
20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
20130402: Several kernel changes, UMS regression fixed
20130329: Video pillarbox. Regression: UMS requires adb
20130326: Optimized build
20130320: SSID fetch fixed
20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.
Instructions
Click to expand...
Click to collapse
Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
dhiru1602 said:
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Click to expand...
Click to collapse
Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
Download the zip of the ROM and save it into the internal SD or the external one (*)
Reboot to recovery
Flash the downloaded zip
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
Reboot
(*) While flashing, the device will reboot and you'll see a different recovery after that.
If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.
CyanogenMod 10:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
Reboot
Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.
CyanogenMod 10.1/10.2:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
Wipe data/factory reset
Reboot
Downgrades are probably not expected, that's why you need to do a data wipe.
Important note:
The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.
Useful informations
Click to expand...
Click to collapse
The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
(3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
This ROM allows you to force two apps to stay in memory. See this post for more info.
I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
(3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
FM radio is available through third party apps, such as Spirit FM
"Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
(3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
(3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
If the keyboard keeps crashing, you probably flash the wrong gapps.
The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
(3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
Weird activity in standby? Read this.
(3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.
If you find a bug not listed, please report.
Post as many informations as possible, ways to reproduce it and logs.
You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.
The standalone kernel is no more mantained. Flash the ROM instead.
Click to expand...
Click to collapse
Kernel - 2.6.35
Click to expand...
Click to collapse
After months of use, I decided to publicly release my kernel.
This is for CyanogenMod 10 Alpha 4.
It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.
Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.
Main features:
XDA_Bam's code and fixes:
◦ 5 OPPs
◦ Booting at stock speed (1000MHz)
◦ Slight undervolt (3%) on all OPPs
◦ Home button double presses fix
◦ Lowered processor transition latency
◦ Stable Bluetooth connections
Modified light sensor driver: [1]
◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
◦ Dynamic polling interval
◦ Code cleanup
Modified battery driver [2]
CPU Governors:
◦ Ondemand (default)
◦ SmartassV2
◦ Conservative
◦ Performance
I/O schedulers:
◦ Deadline (default)
◦ Noop
◦ CFQ
◦ SIO
Toggable FSync
Fixed always ON LEDs bug when used for notifications only
VPN networks support (not tested)
Slightly increased touchkeys sensitivity (from 45 to 35)
Other minor changes and optimizations
Downloads:
version 4.0: kernel-qwerty-cm-10-galaxysl-v4.0.zip: kernel with custom DeviceParts.apk [3], hostap and tiap_drv.ko [5]
clean-qwerty-cm-10-galaxysl.zip: restore zip with dhiru1602's kernel
UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
If you need RNDIS, flash this kernel release or the previous one.
Additional zips:
powerHAL-cm-10-galaxysl.zip: power HAL for boosting the CPU when ondemand is used [4]
libsensor-cm-10-galaxysl.zip: custom libsensor. Read note [1]
Changelog:
Code:
22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release
Notes:
[1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.
[2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.
[3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.
[4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.
[5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.
Special thanks to dhiru1602 and XDA_Bam for their awesome work.
Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.
Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Re: [KERNEL][CM10] qwerty [08/02/13]
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Re: [KERNEL][CM10] qwerty [08/02/13]
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Works fine for me. Try wiping cache+dalvik cache.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
Click to expand...
Click to collapse
Are you using SIRI kernel?
Hetalk said:
Works fine for me. Try wiping cache+dalvik cache.
Are you using SIRI kernel?
Click to expand...
Click to collapse
I am just using the signal fix kernel by loSconosciuto before ...........
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Re: [KERNEL][CM10] qwerty [08/02/13]
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Sent from my GT-I9003 using xda premium
Re: [KERNEL][CM10] qwerty [08/02/13]
Hetalk said:
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Click to expand...
Click to collapse
i post here becoz i wanna flash this kernel will try what u say later, thx
Sent from my U9GT2 from moage.com using xda premium
^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.
Re: [KERNEL][CM10] qwerty [08/02/13]
just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..
Sent from my GT-I9003 using xda app-developers app
I am pleased thank you very much !!!
Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^
Thank you for taking us solicitous
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
just added a tab (specific options) available in the parameter menu
vishal24387 said:
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Click to expand...
Click to collapse
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
vishal24387 said:
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Click to expand...
Click to collapse
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Click to expand...
Click to collapse
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Click to expand...
Click to collapse
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.
@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.
rodero95 said:
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Click to expand...
Click to collapse
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.
wee2wee said:
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
Click to expand...
Click to collapse
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
loSconosciuto said:
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
Click to expand...
Click to collapse
Thanks...found it...
loSconosciuto said:
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
Click to expand...
Click to collapse
Thanks for ur simplified explaination This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels
EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results
Re: [KERNEL][CM10] qwerty [08/02/13]
Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.
Sent from my GT-I9003 using xda premium
Really nice Kernel with good combination of battery and performance and many good tweaks
Thank you very much Sir :laugh:
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.
Ktoonsez presents:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.106
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz and AOSP
•F2FS compatible with AOSP 4.4
Click to expand...
Click to collapse
Canadian users, DO NOT FLASH the kernel from this thread, flash the TMO version from the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2289140
AOSP Lollipop 5.0 VERSION:
02.06.2015: http://ktoonsez.jonathanjsimon.com/sgs4/AOSP/KT-SGS4-LP5.0-AOSP-INTL-02.06.2015.zip
Click to expand...
Click to collapse
AOSP KITKAT 4.4 VERSION:
12.09.2014: http://goo.gl/ZPpZwn
Google Edition KITKAT 4.4 VERSION:
07.12.2014: http://goo.gl/bnhW1F
Touchwiz Kitkat 4.4 VERSION:
07.12.2014: http://goo.gl/MebJ4Z
To make wifi work when it wont turn on or connect, change this in the build.prop:
ro.securestorage.support=true TO ro.securestorage.support=false
Click to expand...
Click to collapse
******* END OF LIFE *******
AOSP JELLYBEAN 4.3 VERSION:
06.19.2014: http://goo.gl/GqNAUp
Touchwiz JELLYBEAN 4.3 VERSION:
06.19.2014: http://goo.gl/Vso846
Google Edition JELLYBEAN 4.3 VERSION:
06.19.2014: http://goo.gl/vtI0Tt
Click to expand...
Click to collapse
Touchwiz JELLYBEAN 4.2.2 VERSION:
http://ktoonsez.jonathanjsimon.com/sgs4/TW/KT-SGS4-JB4.2-TW-ATT-02.20.2014.zip
AOSP JELLYBEAN 4.2.2 VERSION:
http://ktoonsez.jonathanjsimon.com/sgs4/AOSP/KT-SGS4-JB4.2-AOSP-ATT-11.04.2013.zip
Click to expand...
Click to collapse
KTweaker Shop and previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/showthread.php?t=2393708
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
If you get this message after booting up the kernel:
"The device has detected an application attempting ..."
Go to the "/system/app/" folder and delete the files that begin with "knox"
Post #2 will be reserved for change logs
Post #3 will be reserved for MY Settings, Extras and FAQ's
Sources can be found here:
https://github.com/ktoonsez/KT-SGS4
Change Log 12.09.2014
1. Sync with CM code changes
2. Sync ramdisk updates in CM-12
3. Add back in f2fs support for AOSP 4.4 kernel
Change Log 11.30.2014
1. After hundreds of hours I finally gave up porting to new code so I had to start all over again.
2. Everything works except the Screen wake functions!!!!!!!
3. Sync with CM-11
4. Sync with CM-12
5. Enjoy
6. Unified the code so everybody willl use the INTL version
7. Thanks to all that were patient while I worked a million hours for work and good-bye to all the whiner/haters that said I abandoned this, you are now allowed to download this .
Change Log 07.12.2014
1. Linux 3.4.95.
2. Linux 3.4.96.
3. Linux 3.4.97.
4. Linux 3.4.98.
5. Modified KTMonitor to fit better with wider fonts.
6. New ktoonservativeq parameter named "cpu_load_adder_at_max_gpu"!!!!!!!!!!!! This is an awesome parameter you can use to boost your CPU while the GPU is at max level. Example: if you set cpu_load_adder_at_max_gpu = 30 and while playing a game and your GPU is at max Mhz, the CPU load is only 22%, this parameter will add the 30 thus making the CPU load a 52% which will bring up the Mhz and more cores according to your settings.
7. 4.3 kernels are now moved into ******* END OF LIFE ******* section
Change Log 06.19.2014
1. Linux 3.4.93.
2. Linux 3.4.94.
3. Couple KTweaker patches.
4. Updated compiler misc stuff.
Change Log 06.09.2014
1. Linux 3.4.92.
2. Merged in latest CM commits.
3. Ramdisk updates for AOSP.
4. 4.4.3 miscelanious stuff.
5. Fix IR for GE ROMs.
6. Merge in some more 4.4.3 stuff for GE.
7. Ktweaker update: AUTO HOTPLUG OPTION IS NOW A LIST SELECTION INSTEAD OF CHECK BOX, MAKE SURE YOU GO AND SET IT TO THE PROPER VALUE!!!!!!!!!!!!! So if you used to have the checkbox off, select "Disabled", if you had it checked, select "KT Auto Hotplug"
Change Log 05.28.2014
1. Linux 3.4.90
2. Linux 3.4.91
3. Upgraded to latest Linaro
4. Merged in the 1 commit from CM
Change Log 05.14.2014
1. KTweaker 7.1 (this is just an update for my S3 guys, nothing new for S4)
2. sched: set mc_power_savings=2 this feature packs tasks together and try to bind them to cpu0, which in theory will let cpu1 idle longer, thus improving battery life.
3. kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
4. smp: patches from mainline 3.5 to hopefully help with hotplug efficiency
5. Linux 3.4.89
Change Log 05.05.2014
1. Mostly a TWRP update on todays release
2. Modified TWRP to do ext4 or F2FS on the fly based on "Settings" screen to reduce problems, no more need for flashing format zips like before, and no more rebooting in and out of recovery.
3. When you change the "Settings" you will notice that the name at the top will change according to your settings. EXT4 for ext4 formatting, F2FS for F2FS on data and cache, and F2FS+S for data, cache, and system.
4. Under "Settings" screen in TWRP you will see a new option called "Force data and cache wipe functions to use F2FS". When checked it will force wipes on the cache and data partitions to format it F2FS, unchecked forces to ext4.
5. Under "Settings" screen in TWRP you will see a new option called "Include system partition." When checked it will force wipes on system partitions to format it F2FS, unchecked forces to ext4.
6. KTweaker: New option under "Tools" screen called "Get Partition info" so you can check the format of the 3 partitions.
7. Since I made the new TWRP, I modified the ramdisk back to my original testing code to load the partitions based on there format. Since it does this, you will have to use KTweaker now to verify if you did indeed format everything properly using the new option from #6 above.
8. Link to newest TWRP-ALL-IN-1: http://goo.gl/xl5VwI
9. Link to newest F2FS folder (updated instructions in the folder, moved all the old stuff to the "OLD WAY" folder): http://goo.gl/HLz4al
Change Log 04.28.2014
1. Linux 3.4.88
2. Now compiling with Linaro 4.9.1 a-15 optimized from @Christopher83
3. Updated kernel flash routine to detect F2FS partitions and include the appropriate fstab so it works with /data and /cache or /data and /cache and /system
4. Updated KT-TWRP.F2FS and KT-TWRP.EXT4 to have one common recovery binary, during flash uses same algorythm as kernel flash zip to use the proper fstab.
5. KTweaker 7.0
6. Under "Tools" screen added "F2FS: Convert ROM ZIP option". To use it, click that option, it opens a KT File Explorer, navigate to the folder where your zip files is, click the ROM zip file that needs converting and it will create a second file with the same exact name except adds a -F2FS to the end. A little hint, instead of using the back button once you are done converting, press the menu button and select close and KTweaker will remember that folder and take you right back the next time you go back in. It takes around 1:45 to do it my phone running ktoonsified v6, other profiles may take longer and if you are converting from external SD it may take longer depending on the quality of your SD.
7. TWRP for normal EXT4 format link is here http://goo.gl/jwMSEn
8. TWRP for F2FS format link is here http://goo.gl/Zw1akJ
Change Log 04.19.2014
1. ktoonservativeq: Optimized new block_cycle code that was causing slow issues for some
2. Updated Ktoonserified v6, so be sure to redownload it to work with todays kernel
3. Updated KTGaming profi.e, so be sure to redownload it to work with todays kernel
4. Probably the fastest version of ktoonservativeq to date
5. Guys on 04.18 test kernel from yesterday, there is no change but might as well update so you are the newest dated file.
6. KTweaker 6.9
7. KTweaker: Added new sub screen when picking ktoonservativeq "Gov Adjustments" screen to give you the choice to show "All Parameters", "ONLY Screen ON parameters", "ONLY Screen OFF parameters" to make it easier to see only the parameters you want to see. Thanks @elesbb for the idea
8. Linux 3.4.87.
9. I was unable to reproduce the inability to download scripts, but I made a change and 2 people have told me it doesnt do that anymore with 6.9 so I think I got it fixed.
10. Updated TWRP for normal EXT4 format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/jwMSEn
11. Updated TWRP for normal F2FS format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/Zw1akJ
Change Log 04.17.2014
1. Ktoonsez CRAZY BIRTHDAY EDITION!!!!!!!!!!!!!!!!!!
2. KTweaker 6.8
3. Made Fast Charge Widget size based on left side alignment so people that want a 1x1 widget of FC can do that (by request from someone)
4. 20+ new parameteres for Ktoonservativeq. I went a little crazy with it but you are going to love it!!!!!!!!!!!
5. WARNING!!!!!!!!!!! All the rest of these are going to require you to check and maybe set some of your ktoonservativeq governor settings from scratch!!!!!!!!!!!!!! I did the best I can at converting them to the new names but can account for every old version of the Profile files. So write down your settings before flashing so you can manually set them up with the new names.
6. Ktoonservativeq: Renamed all up_threshold and down_threshold items to have a version for screen on and off. So all 8 items turned into 16 items no so you have total control for screen on and seperate control for screen off.
7. Ktoonservativeq: Changed all parameters that said hotplugging into hotplug to shorten the names.
8. Ktoonservativeq: Rename all the block parameters to more commonized names. New item names are as follows. block_cycles_online = blocking cycles before letting a CPU come online. block_cycles_offline = blocking cycles before letting a CPU go offline. block_cycles_raise = blocking cycles before letting the CPU raise the Mhz.
9. Ktoonservativeq: All of the block parameters from item 5 have a screen on and scree off option.
10. Ktoonservativeq: Renamed freq_step to have a screen on and off option plus seperate values for the raise and lowering of the CPU Mhz.
11. Ktoonservativeq: lockout_2nd_core_hotplug, lockout_3rd_core_hotplug and lockout_4th_core_hotplug all have a screen on and screen off option.
12. Ktoonservativeq: Renamed sync_extra_cores parameter to have screen on and off options
13. Ktoonservativeq: Renamed boost_2nd_core_on_button, boost_3rd_core_on_button and boost_4th_core_on_button to have screen on and off options.
14. KTweaker Shop: Now when you select Profiles or Scripts, it will come up with a sub screen that lets you choose from All Profiles/Scripts, ONLY Conservative Profiles/Scripts, ONLY Balanced Profiles/Scripts, or ONLY Performance Profiles/Scripts. Thanks to @CamFlawless for creating the type list for me.
15. Added Ktoonsified v6 to KTweaker Shop.
16. Update the server for KTweaker Shop to support the 3 types of profiles now.
17. Update a bunch of profiles to the server for KTweaker Shop, BIG thanks to @LuigiBull23 for helping me update all the files for the server.
18. LED: Boost cores on LED calls to help incoming calls and unplug-plug charger turn screen on quicker.
19. Make call_in_progress a global variable so we have access to its status in more places. Use the call_in_progress in ktoonservativeq to block super_conservative so phone calls r smoother
20. Remove loki on PC side and use loki scripting in flash zip
21. F2FS: add support for F2FS so people that want to run it can. THIS ONLY WORKS TO AOSP4.4 SO FAR!!!!!!!!! All kernels will come with standard ext4 as default, people that want F2FS will have to do the instructions from Post #3 !!!!!!!!!!!!!!!!
22. F2FS: See Post #3 for a download link and a set of instructions to move convert to F2FS.
23. Post #3 updated with my latest settings and fixed the screen names for each setting.
24. Flashable kernel zip now do the loki'ing when it is needed for ATT and VZW and also determine your file system to know whether to flash F2FS or ext4 ramdisk.
25. For those that use TWRP and want to try mine, you can download it here (Normal ext4 version, not for people that format to F2FS): http://goo.gl/jwMSEn. It seems to have gotten rid of the boot hang that some people get with official 2.7.0.1.
Change Log 04.07.2014
1. Applied battery drain fix to all versions
2. Shorten internal kernel name so Antutu does not crash
3. KTweaker 6.7.3
4. KTweaker: Couple of fixes for numeric entry
5. KTweaker: Fix CPU count error
6. Linux 3.4.86
7. Revert code from 04.02 release that was causing UI lag.
8. Added "booting" LED pattern, because its cool and tells me when kernel takes over from bootloader and when ROM takes over from kernel
Change Log 04.02.2014
1. Fix memset issue when moving to Linaro 4.8.3 (this fixes ROMs that Settings app was crashing and could not rename files/folders)
2. Major rewrite of random code ( this should make games perform even better)
3. Sched:fair: Tons of merges from stuff around the net and faux
Change Log 04.01.2014
1. Linux 3.4.85
2. Ktweaker 6.7.2
3. Modified Ktweaker OTA flashing options to work with CWM/Philz recoveries
4. Using newest Linaro 4.8.3 toolchain optimized for a15 cortex
5. Added -o3 optimizations to TW 4.4
Change Log 03.27.2014
1. Ktweaker 6.7.1
2. Modified Ktweaker Widget S2W toggle to include the S2W, DT2W... options
3. Fixed KTweaker issue with not saving "Vibration Strength" option.
4. Linux 3.4.84
5. Added @Fenny's code to let people charge while phone is power off on GE and TW 4.4 versions. Be sure to go thank Fenny for tracking that down!!!
6. Added ZCACHE to TWGE 4.4 and TW 4.4
7. Added FRONTSWAP v16 to all 4.4 versions, thanks to all the guys that tested yesterday.
8. Added back all standard screen on/off code for initialization to hopefully stop the no touch issue for the few people that get it here and there.
9. char:random: Some tweaks from around github.
10. For TW 4.4 merged in Linux 3.4.1 thru 3.4.84
11. cpufreq: Fix broken uevents for cpufreq governor and cpu devices from CM 11
12. Ramdisk updates for AOSP 4.4
Change Log 03.19.2014
1. Moved Double tap, sweep, etc... to its own screen in "Main Settings" called "Wake/Sleep Settings"
2. NEW item in "Wake/Sleep Settings"!!!!!!!!!!: Double tap to sleep. Double tap the top status bar area when the screen is on and it will to go sleep.
3. Made a duplicate item of "Prox Sensor Checker" in the "Wake/Sleep Settings" screen for easy access.
4. Made a duplicate item of "Charging Current" in the "Fast Charge" screen for easy access.
5. Remove all the main debug flags, zip files are about 2-3mbs smaller now
6. Sync with CM commits from a few days ago.
7. Remove DCVS flag to remove some unnecessary Samsung Mhz manipulation
8. Linux 3.4.83
9. Ondemand governor patches
10. Optimized ARM RWSEM algorithm from Ashwin Chaugule
11. Added 4 zram drives from TW 4.3 into 4.4.
Change Log 03.12.2014
1. Improved "on a phone call" code to make sure it is isnt executing the screen wake code while screen is off and you are on a call.
2. Increased speed for wake up on the screen wake functions, sensor wake functions wake a little quicker too but will always be limited by the 1 second timer.
3. Finally found a better spot to trigger and make the screen turn on way quicker when an incoming call is coming in.
4. KTweaker version 6.6.
5. NEW item under "Tools" screen called "Charging Current". You can click on the item and it will update the field with the current mA it is charging at.
6. NEW item under "Fast Charge" called "MTP while fast charging". Enabled will keep MTP on so you can still access the phone, disabled will disable MTP and you will not be able to access it, just simply charges. To take effect this option requires the cable to be unplugged and re-plugged in.
7. NEW item under "Fast Charge" called "Screen ON charging limit". BE VERY CAREFUL WITH THIS ITEM!!!!!!! When enabled it will keep the Samsung limit they imposed of 1200 mA while charging and the screen is on, if it is disabled it will allow you to charge at the full 1900 mA or whatever custom mA you have set for A/C. To take effect this option requires the cable to be unplugged and re-plugged in.
Change Log 03.10.2014
1. Improved Sweep 2 wake recognition.
2. Ignore double tap if more than 1 finger is used.
3. New option for "Hold Wake Lock for wake" called "Enabled ONLY while charging" so you can choose to only hold wake lock during charging.
4. Added wake lock montitor so wake locks can be kicked back on if they are killed prematurely.
5. New "Prox value when clear" added so you can specify the prox value to allow the screen wakes to still work when your prox is not functioning properly/dirty.
6. New item under "Tools" called "Prox Sensor Checker". Click it start/stop the monitor timer. Use this to see what you 100% clear prox value is, then add 20 to that number and use it for the "Prox value when clear" value mention in #5 above.
7. LEDs: Added some code that was needed on the TW version to catch all the notification scenerios.
8. Fix the issue where touch screen would become unresponsive on TW ROMs.
9. Thats all I can remember, ENJOY!!!!!
Change Log 03.06.2014
1. NEW!!!!!!! LED: 3 New options in KTweaker to select from, "Disable LED Start Hour", "Disable LED Stop Hour", "Disable LED Always". Start and Stop value are in 24 hour military time.
2. NEW!!!!!!! "Screen Wake Options" of: Sweep 2 Wake, Sweep 2 Wake ONLY on Charger, Double Tap 2 Wake, Double Tap 2 Wake ONLY on Charger, Both, Both ONLY on Charger.
3. Screen Wake Options: For Sweep 2 Wake, sweep the screen from left to right or right to left to turn on the screen.
4. Screen Wake Options: For Double Tap 2 Wake, double tap the screen if the bottom left corner to turn on the screen.
5. NEW!!!!!!! "Sensor Wake Options" of: Wave 2 Wake, Wave 2 Wake ONLY on Charger, Pocket 2 Wake, Pocket 2 Wake ONLY on Charger, Both, Both ONLY on Charger.
6. Sensor Wake Options: For Wave 2 Wake, hold your hand in from of the proximity sensor for about 1/2 second and then wave it back and forth to turn on the screen.
7. Sensor Wake Options: For Pocket 2 Wake, simply have the phone in your pocket for at least 10 seconds, take it out and the screen turns on.
8. NEW!!!!!!! "Hold Wake Lock for Wake" of: Check them out, there is freaking 18 of them, lol. By using any of these methods you will guarantee that the wake methods will work, without them its a crap shoot. My favorite is "Enabled ALWAYS on LED notif", this will turn on a wake lock when the LED is blinking for a notification and will obey your "Disable LED Start Hour" and "Disable LED Stop Hour" to block a wake lock when u dont want LED on. The name of the wake lock is "kt_wake_funcs" so you can track it when using them.
9. FastCharge: Completely re-did FastCharge interface adapted from Jean-Pierre and Paul Reioux. There are 3 options now for for the main selection (Enabled, Disabled, Custom mA)
10. FastCharge: When Custom mA is selected, it will obey the "Custom USB mA" and "Custom A/C mA".
11. FastCharge: Another new option is "Fail safe", when enabled it will use the lowest A/C or USB value when the cable type is UNKNOWN. When disabled it will allow you to use any custom mA instead of the predefined ones that you will see in Ktweaker when choosing the 2 Custom mA's.
12. Removed some more dmesg spam to keep logs clean and fast.
13. Linux 3.4.82
14. New ADB binary for wifi support.
15. Ramdisk merge from the CM changes for AOSP.
16. KTweaker: KTweaker update to 6.4 adding all the features from above for wake functions and new Fast Charge options.
17. KTweaker: Added menu item on main screen to quick toggle Fast Charge for Enabled/Disabled.
18. Date added to the OP links so everybody knows what the last date that particular kernel was updated last.
Change Log 02.24.2014
1. KTweaker: KTweaker update to 6.2.
2. KTweaker: New Widget by request from you guys, its a quick Profile chooser, simply click the text area left of the "Set" (if you see "-----" then it means you never did a restore profile) button and it will scroll thru all the profiles you have on your phone. Once you have the one you want, click the "Set" button . The widget is also sizable so you can size it from 1x1 all the way up to 4x1.
3. Merged in TW 4.4 into GE 4.4 version, sound is much crisper and louder
4. Added faux sound to TW 4.4
5. ktoonservativeq: New tunables called super_conservative_screen_on and super_conservative_screen_off (remove old super_conservative) so people can choose when they want to go super conservative. Be sure to go set these items if you used the old super_conservative item.
6. Added my newest settings to the KTShop as ktoonsified v5.
7. Linux 3.4.81
8. Changed upgrade routine to not try to upgrade files with .xml extention in the /ktweaker/ folder
9. Couple other general fixes in KTweaker and KTmonitor.
10. Added PPP protocol for people using USB network/modem devices.
11. BFQ-v7r2
Change Log 01.23.2014
1. Stop charging from obeying Fade mode by default
2. LEDs: Add tunable to set led fade mode while charging. Cycling cable to take effect is required.
3. AOSP 4.4: gcc-wrapper: force python version 2.
Change Log 01.17.2014
1. KTweaker: New feature by request from someone (can't remember who) to set a password to get into the UI (Under Extras - > UI Password). Feature is disabled by default leaving password blank.
2. KTweaker: New feature to control the LEDs for notifications derived from vladnosferatu and invano implementation + some extras (see next 9 items)
3. KTweaker: LED Fade Mode - lets you choose to use the fade effect of LED
4. KTweaker: LED Fade Intensity - lets you choose the light intensity of the LED
5. KTweaker: LED Time on - lets you override the ROMs setting for how long the the LED stays ON
6. KTweaker: LED Time off - lets you override the ROMs setting for how long the the LED stays OFF
7. KTweaker: LED Step Speed 1 - lets you control the steps it takes as it makes the LED brighter/dimmer when in fade mode, play around with it and have fun.
8. KTweaker: LED Step Speed 2 - lets you control the steps it takes as it makes the LED brighter/dimmer when in fade mode, play around with it and have fun.
9. KTweaker: LED Step Speed 3 - lets you control the steps it takes as it makes the LED brighter/dimmer when in fade mode, play around with it and have fun.
10. KTweaker: LED Step Speed 4 - lets you control the steps it takes as it makes the LED brighter/dimmer when in fade mode, play around with it and have fun.
11. KTweaker: LED Step Bit Shift - lets you control the main speed that the LEDs go brighter/dimmer when in fade mode, play around with it and have fun.
12. KTweaker: No all number and text inputs will automatically bring up the keyboard
13. KTweaker: New KTweakerWFC widget that is a 2x1 widget containing ONLY the Fast Charge toggle
14. Added BIC TCP Congestion control
15. Added HSTCP TCP Congestion control
16. Added HYBLA TCP Congestion control (I will be testing this one today as I heard a couple of reports that i really increases download speeds)
17. Added HTCP TCP Congestion control
18. Added VEGAS TCP Congestion control
19. Added RENO TCP Congestion control
20. Added SCALABLE TCP Congestion control
21. Added LP TCP Congestion control (I have been using this one for last 3 days with great speed increase)
22. Added YEAH TCP Congestion control
23. Added ILLINOIS TCP Congestion control
24. WiFi: filter multicast during sleep for AOSP 4.4 to help wifi wakelocks/better deep sleep. All other version already had it so dont ask to add it to other versions.
25. Linux 3.4.77
Change Log 01.13.2014
1. ktoonservativeq: Added new tunable called super_conservative. When enabled (enter a 1) this will dramitacally reduce the bouncing effect from Min Mhz and the amount of hotplugging. Performance may take a hit for the really picky user but 95% of the people that have been testing say its not enough to bother them.
2. Linux 3.4.76
3. Fix for TW 4.3 slow motion recording (thanks @elesbb for testing for me ).
4. Tweaked disable hotplugging while music/video is playing option.
5. Updated my setting in Post 3 so go check it out.
6. Added pac framework compatibility to AOSP 4.4
7. KTweaker 5.1 for all versions.
Change Log 01.05.2014
1. Upgraded Linaro to newest compiler for ALL versions.
2. Added about 200 ramdisk tweaks from my Nexus 10 kernel for ALL versions.
3. Wireless charging will now work with the Min Mhz option while charging, by request from @1Raiders (under extras).
4. ktoonservativeq: New option added to disable hotplugging while music/video is playing. Should help the few people that have trouble playing music with screen off.
Change Log 01.03.2014
1. Upgraded Linaro to newest compiler.
2. Massive amount of ramdisk updates from CM.
3. Added about 200 ramdisk tweaks from my Nexus 10 kernel to see how it goes.
4. Added dynamic fsync by request from you guys.
Change Log 01.01.2014
1. Happy NEW YEAR EDITION
2. Merged in more stock ramdisk to try and fix installing from external sd.
3. Linux 3.4.73
4. Linux 3.4.74
5. Linux 3.4.75
Change Log 12.30.2013
1. Made a BUNCH of adjustments for INTL Google Edition KITKAT 4.4 VERSION.
2. Hopefully reboots are gone, just left with PURE AWESOME!!!!!!!!
3. If you are already on the test kernel, this is the same, no need to redownload.
Change Log 12.22.2013
1. TW and TWGE: ktoonservativeq: Added "touch_boost_gpu" option. Be sure if you are using the max GPU frequency that if you adjust the max, also adjust the "touch_boost_gpu" option.
2. TW and TWGE: Linux 3.4.73
3. TW and TWGE: Linux 3.4.74
4. TW and TWGE: Linux 3.4.75
Change Log 12.21.2013
1. SUPER CRAZY WACK FUNKY SPEED EDITION!!!!!!!!!!!
2. cpufreq: Some general re-write to make freq changes smoother and more efficient
3. acpuclock-8960ab; Update from ML4
4. subsystem: Add extra checks to make sure subsys_domain and iommu_domain are NOT NULL
5. msm: msm_bus: More checks to insure pdata and bus driver vars are not in error and NO NULL
6. grp3d_low_vectors: Bump MBPS to 1700 for low vectors for better low speeds
7. gfx3d_fs_data: Change reset_rate 27000000 from 1800000. Remove 1800000 from clk_tbl_gfx3d. Increase log length for msm_rpm
8. dcvs: Set msm_dcvs_enabled = 0 when msm_dcvs_scm_init() fails adn be sure to return early when msm_dcvs_enabled == 0
9. perf_event_msm_krait_l2 sync with ML4
10. scm: Rewrite scm_call funcs and ML4 merges
11. Linux 3.4.75
Change Log 12.19.2013
1. ONLY USE THIS WITH CM 11 BUILT ON 12.18 OR NEWER!!!!!!!
2. Prox sensor
3. Fix for Battery issues on builds 12.18 and newer
4. ktoonservativeq: Added "touch_boost_gpu" option. Be sure if you are using the max GPU frequency that if you adjust the max, also adjust the "touch_boost_gpu" option.
Change Log 12.18.2013
1. ONLY USE THIS WITH CM 11 BUILT ON 12.18 OR NEWER!!!!!!!
2. Fix battery update for the 2nd day in a row!!!!!!!!!!!!!!!!!!!!!!!!!!
Change Log 12.17.2013
1. ONLY USE THIS WITH CM 11 BUILT ON 12.16 OR NEWER!!!!!!!
2. Upgrade camera to ML4 source from Samsung
3. Sync GPU/Display drivers from ML4
4. cpufreq: interactive: Allow 1 ms error in above_hispeed_delay
5. cpufreq: interactive: Reset floor_validate_time if busy at max for 100ms
6. cpufreq: interactive: Add a sampling_down_factor for max frequencies
7. Many msm: msm_fb updates
8. Many msm: msm_mdp updates
9. Many msm: msm_vidc updates
10. Updated healthd binary for charging routines for CM 11
11. ENJOY!!!!!!!!!!!!!!!!!!
Change Log 12.12.2013
1. Linux 3.4.72
2. Linux 3.4.73
3. Linux 3.4.74
4. Ramdisk sync for CM 11.
5. Use Google Edition wifi driver in AOSP 4.4.
6. Compatiblity for 4.4.2.
7. TMobile guys will use the INTL version for Google Edition
Change Log 11.28.2013
1. Release version of KITKAT for Google Edition
2. Add extsdCard to ramdisk so apps that have not been updated for Kitkat will work.
Change Log 11.16.2013
1. Updated ramdisk for CM11 to latest from http://sourceforge.net/projects/unofficial-cm/files/Nightlies/.
2. Above includes more sdcard pathes and radio/3G/4G patches
3. ONLY LOAD THIS WITH NEWEST 11/16 OR NEWER ROMs
Change Log 11.14.2013
1. Change ramdisk for CM11 for external SD mounting for todays release of ROMs for all versions.
2. Change File name to KK instead of JB for all versions.
3. Couple of minor fixups.
Change Log 11.13.2013
1. Change ramdisk for CM11 for external SD mounting for todays release of ROMs.
2. Change File name to KK instead of JB.
3. OTA will work with new KK version after flashing this new update.
Change Log 11.12.2013
1. Change ramdisk for I9505 phone to match I9505 version of CM11 for external SD mounting.
2. Change File name to KK instead of
Change Log 11.11.2013
1. Added Kitkat version
Change Log 11.08.2013
1. CM sync from late night 11.4 updates
2. Plus 1 update from CM on 11.5
My Settings, F2FS, Extras and faq's
My settings
Main Settings-> CPU Settings Screen
governor = ktoonservativeq
Min Mhz = 189
Max Mhz = 1998
Main Settings-> Scheduler/SD Settings Screen
scheduler = sio
Internal Read Ahead = 1024
External Read Ahead = 1024
Voltage Screen
UV'd 50mv across the board for CPU and 75 for GPU (use menu button for hidden menu option to globally subtract)
Main Settings-> CPU Settings->Screen OFF Settings Screen
Screen OFF Profile Mhz = 702
Disable Screen Off Mhz Call = Enabled
Main Settings-> GPU Settings Screen
GPU Max Mhz = 504
Screen OFF GPU Max Mhz = 128
GPU governor = simple
Main Settings-> TCP/IP Settings Screen
Congestion Control=hybla
Main Settings-> LED Settings Screen
LED Fade Mode = Enabled
LED Time on = 3000
LED Time off = 3000
Main Settings-> CPU Settings->Governor Adjustments Screen
block_cycles_offline_screen_off=1
block_cycles_online_screen_off=22
block_cycles_raise_screen_off=22
down_threshold_screen_off=72
down_threshold_screen_off_hotplug_1=73
down_threshold_screen_off_hotplug_2=74
down_threshold_screen_off_hotplug_3=75
freq_step_lower_screen_off=8
freq_step_raise_screen_off=1
super_conservative_screen_on=0
super_conservative_screen_off=1
sync_extra_cores_screen_on=1
touch_boost_cpu = 1242
touch_boost_cpu_all_cores=1
sampling_rate_screen_off = 90000
touch_boost_gpu = 504
up_threshold_screen_off=85
up_threshold_screen_off_hotplug_1=86
up_threshold_screen_off_hotplug_2=87
up_threshold_screen_off_hotplug_3=88
ALL THE REST ARE STOCK
__________________________________________________________________
F2FS Links for using F2FS with my AOSP 4.4 kernel
http://goo.gl/HLz4al
__________________________________________________________________
Governors
ktoonservative Governor
This governor is based on conservative, but added some tunable vars and made it a hotplugging governor unlike conservative. With the settings I included stock it is probably the most responsive gov and is pretty good at saving battery as well. Especially with my screen off option to limit the CPU top Mhz. Hope that answers all ur questions.
Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Enable ZRAM: Flashable zip
http://db.tt/8vssawIO
well that was quick lol.
Yay! Is this Loki'd?
:highfive: :victory:
I love you.
ChaosMinionX said:
Yay! Is this Loki'd?
Click to expand...
Click to collapse
Yes, as long as u have custom recovery you are good to go . I used TWRP. :good: :highfive:
I need this... And thus my hate for locked bootloaders increases threefold.
Sent from my SAMSUNG-SGH-I337 using xda premium
ktoonsez said:
Yes, as long as u have custom recovery you are good to go . I used TWRP. :good: :highfive:
Click to expand...
Click to collapse
You might want to add that its Loki in the op so people know its safe for att
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Ktoonsez to save the day!!! Flashing!!
WOO!
Im somewhat new to kernels.
By flashing this is it going to make my phone automatically run better or does this just give me the option to tweak myself and figure out how to make the phone run better?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
ktoonsez said:
ktoonservative Governor
This governor is based on conservative, but added some tunable vars and made it a hotplugging governor unlike conservative. With the settings I included stock it is probably the most responsive gov and is pretty good at saving battery as well. Especially with my screen off option to limit the CPU top Mhz. Hope that answers all ur questions.
Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Click to expand...
Click to collapse
Ktoonservative?
I dont see that on the governor list lol
awesome! must feel good to use your own kernel @ktoonsez!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Thanks man! Running great. Can't wait for a CM compatible kernel.
Sent from my SAMSUNG-SGH-I337
jetlitheone said:
Ktoonservative?
I dont see that on the governor list lol
Click to expand...
Click to collapse
Not in there yet, thats the next step now that I can use the kernel :good:
And we're off!
ktoonsez said:
Yes, as long as u have custom recovery you are good to go . I used TWRP. :good: :highfive:
Click to expand...
Click to collapse
You are my hero. Haha its good to see you and Task650 over here!
ktoonsez said:
Not in there yet, thats the next step now that I can use the kernel :good:
Click to expand...
Click to collapse
Lol anyway to get rid of the message saying its detected an application doing blah blah blah lol and wants you to reboot..
jetlitheone said:
Lol anyway to get rid of the message saying its detected an application doing blah blah blah lol and wants you to reboot..
Click to expand...
Click to collapse
Delete the /system/app/Knox files.
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
Attention
/*
I'm not a developer, im taking effort to put more choices of kernel for our community.
This kernel is tweaked for my own taste.
Please do not request for more features because i want to ensure the stability of the kernel first.
And thank you for using this kernel.
*/
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Disclaimer
CODE NAME: VALKYRIE VERSION
Features
Optimization Flags
- Compiled with latest Built with latest custom Gcc 4.8 LINARO Toolchain optimized for Cortex-A7
- -O3 Optimization (optimize for more performance! )
- Graphite optimizations
Click to expand...
Click to collapse
Hotplug Drivers
- Add AutoSMP hotplug driver - default hotplug (really nice)
Click to expand...
Click to collapse
Audio and Sound Tweaks
- Faux Sound Control
- add high performance mode audio (enabled by default)
Click to expand...
Click to collapse
Extra Users Change-able Features (please refer to #4 post for more explanation in how you can adjust this below features)
- Upgraded Zram from kernel 4.x with 500mb size - full smooth multitasker
- KEXEC Support
- KCAL support for post processing control [v2]
- selinux in permissive - not in force, you can change it to enforcing if you want so don scare !
- DOUBLETAP2WAKE and SWEEP2WAKE/SWEEP2SLEEP
- Enabled all kind Advance TCP
Click to expand...
Click to collapse
Extra Driver Modification differ from stock/CM kernel
- GPU driver aligned with CAF latest update
- Disable many debug option to reduced overhead of the kernel
- Modified Movement, Compass, Acceleration sensors to keep suspend when screen off.
- silenced various kernel logs
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide :
Using TWRP
1. Reboot to recovery > Install > Pick the kernel > Confirm to Flash > Reboot
or
2. Flash it using Flashify
Click to expand...
Click to collapse
Code:
[I]Credit to :-[/I]
- CyanogenMod Developer team for providing the source
- developers that contributed in my github changes - all credit goes to them
- xda-developers.com
- and to all my kernel users, thanks.
Click to expand...
Click to collapse
XDA:DevDB Information
[Kernel][6.0] Valkyrie-L-6 [14/9/2016], Kernel for the Moto G
Contributors
hurtsky
Source Code: https://github.com/hurtsky/android_kernel_motorola_msm8226
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 8
Stable Release Date: 2016-01-10
Created 2015-11-22
Last Updated 2016-09-14
FAQ - Freaking Annoying Question
THIS KERNEL WORKING IN STOCK ROM ????
1. NO, this kernel for ROM that based on CM kernel - Android 6 - Marshmallow and up only
2. This kernel not for AOSParadox also .
SYNAPSE NOT WORKING SUDDENLY ????
1. Read this >>> CLICK HERE
IF HAVING ANY REBOOT? WHAT TO DO?
1. upload file last_kmsg that located in /proc/last_kmsg
2. infomation about what setting that you use : example: intelli plug with zzzmove
3. if only state that youre having reboot without any logs will be ignore.
ERROR DURING OR AFTER FLASHING THE KERNEL
1 . if you comes from others kernel or after flashing the kernel you had this following "error : Fastboot Reason : Fall-through from normal boot mode" or any error during flashing, please dirty flash your rom again to clean up any conflict from different kernel script.. let it reboot.. and flash this kernel..
2. If still happen, flash recommended recovery for this kernel >>> CLICK HERE
KERNEL DID NOT FLASH/THE VERSION STILL THE OLD VERSION
1. Put the kernel ZIP at folder /sdcard and flash it.
2. Please use recommended recovery for this kernel >>> CLICK HERE
OWN CUSTOM SETTING FOR KERNEL DID NOT STICKING AFTER BOOT
1. Make sure you used only 1 kernel tweaks and make sure you did change anything in "advance setting", remove the others apps and start tweaking your own favorite config. (i always suggested to use only Kernel Adiutor for tweaking the kernel)
2. Some ROM had they own boot script that will force the user to stick with it, this happen normally with interactive and cpu-boost config (in this kernel i already disabled completely cpu-boost so no need to worry about this). change interactive to another governors if you did not like what the ROM already did for you. (but i always recommend interactive, as it the most stable governors and updated for current time)
WHAT THE BEST OR RECOMMENDED CONFIGURATION FOR THIS KERNEL??
1. Default configuration is always the best for me because i already tweaked and tested by my own and with my tester before release it to the forum.
2. If you did not like default config, just do your own way (google,do research or re-read all post in this thread because there are some advance users posted their own configuration) and i wont answer or provide any advice for this kind of questions because i always stick with my own configuration
A LITTLE UNRESPONSIVE TOUCH AFTER DOUBLETAP2WAKEUP
1. Please read 4th post in dt2w/s2w/s2s section.
HAVING LAG AFTER USING "YOUR OWN CONFIGURATION OR OTHERS CONFIGURATION" OR NOT USING THIS DEFAULT KERNEL CONFIG
1. Well, i only test my own configuration.. for newbies that try to use their own setting, please do research more before applying or changing any value or using other tweakable features here.. Having lag with your own setting is not my fault, this tweakable features e.g other governors/hotplug/io and etc is for advance user that love trying new stuff and the result is depend on how user tweak it....
2. i only provided guarantee for performance and better battery through my own config (flash and use it).
HELP ! HELP ! I SUDDENLY HAD ALL AWAKE IN BATTERY STATS
1. Just clear dalvik cache from your recovery/twrp
Click to expand...
Click to collapse
.
Changelogs of VALKYRIE Kernel
CHANGELOGS for VALKYRIE VERSION > CLICK HERE
Click to expand...
Click to collapse
DOWNLOAD SECTION FOR VALKYRIE KERNEL
>>>>PLEASE CLICK HERE TO DOWNLOAD<<<<
Click to expand...
Click to collapse
.Note : - if you comes from others kernel or after flashing the kernel you had this following "error : Fastboot Reason : Fall-through from normal boot mode" or any error during flashing, please dirty flash your rom again to clean up any conflict from different kernel script.. let it reboot.. and flash this kernel.. thank you
Special features and sysfs settings
Dynamic dirty page writebacks
This feature has been developed by me and allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off.
It is based on a commit of Francisco Franco, but instead of using hard coded values and of disabling at all the dirty page writebacks while the screen is on (possibility of data loss), I preferred to use a customizable higher dirty page writebacks interval (15 seconds) than the default one (5 seconds) while the screen is on and a customizable default interval (5 seconds) when the screen is off.
By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
How to customize the dynamic dirty page writebacks feature (default enabled):
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
To change the value you can use Performance Control to suit your own taste
Click to expand...
Click to collapse
KCAL support for post processing control [v2]
Please click the link below for more information, and how to use it : - all credits to savoca
[DEV][PATCH] KCAL - Advanced color control for Qualcomm MDSS 8x10/8x26/8974/8084
Click to expand...
Click to collapse
ZZMoove Governor Profile
use tools like Kernel Adiutor, Android Tuner or similar tools which are supporting the change of multible tuneables on-the-fly
or just do it directly in kernel sysfs via a terminal emulator and give the tuneable "profile_number" one of the following values:
1 for Default Balanced Profile
2 for Yank Battery -> Better battery, try to use lower freq as possible
3 for Yank Battery Extreme -> Aggressive Battery profile, by trying to reduce hotplugging as can as possible and with this profile the user will suffer abit in performance side
4 for ZaneZam Performance -> Extreme tuned for performance, aggressively try to hold on high frequency to obtain higher performance
5 for ZaneZam Relax -> Moderate tuned, more to balance but abit performance
Click to expand...
Click to collapse
DT2W/S2W/S2S = DOUBLETAP2WAKE/SWEEP2WAKE/SWEEP2SLEEP
Implemented with Pocket mode, in which, each time proximity sensor been covered, it will suspend touch to avoid sudden screen wakeup.
Normally proximity sensor will active to covered when it detect any object about 3cm from phone distance.
Please use kernel adiutor to enable it.
Known bug for this features for now is:
1 - touch will less responsive during first wakeup after doubletap
Click to expand...
Click to collapse
/-------------New wakegesture been reverted because bugging touch in multiROM startup screen-------------------/
/-------------Wake Gesture implementation only available in Hs9 until Hs12, and simplerV5-----------------------------/
Unhide to read more information about it
WAKE GESTURE
Implemented with Pocket mode, in which, each time proximity sensor been covered, it will suspend touch to avoid sudden screen wakeup. Normally proximity sensor will active to covered when it detect any object about 3cm from phone distance.
Known bug for this features for now is:
1 - touch will less responsive during first wakeup after doubletap
NOTE !
1- To ensure all the wake gesture working correctly, users must use this apk >>> http://elementalx.org/wake-gestures/ to enable or modify the setting
2- Only use kernel adiutor to change doubletap2wake function for FULL SCREEN or HALF SCREEN/bottom side and to enable sleep2wake ONLY.
3- Do not use kernel adiutor to enable sweep2wake feature and all feature that activate through swipe
4- Pocket detection in wake gesture.apk wont work for us, so no need to enable or tick it, we already had automatic pocket detection from kernel directly
5- doubletap2wake is default in HALF SCREEN MODE/bottom side only, which means, you can only double tap on bottom side only to wake up, use kernel adiutor to change it.
EXTRA FEATURES IN WAKE GESTURE!
Wake Gestures
This is a new feature similar to the Motion Launch Gestures on the HTC One m8. Requires this app:http://elementalx.org/wake-gestures/
Set /sys/android_touch/wake_gestures to 1 to enable input events for wake gesture actions. Set to 0 to use traditional sweep2wake or doubletap2wake (wakes up the phone and turns on the screen only).
Click to expand...
Click to collapse
Sweep2wake
Sweep2wake allows you to turn on your phone by swiping your finger across the screen. There are four sweep actions that will work
Gesture........Value
Sweep right......1
Sweep left........2
Sweep up.........4
Sweep down....8
Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)
/sys/android_touch/sweep2wake
Click to expand...
Click to collapse
Doubletap2wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping anywhere on the screen. This causes significant battery drain.
/sys/android_touch/doubletap2wake
0 = disabled
1 = enabled (bottom of screen only)
2 = enabled (full screen)
Click to expand...
Click to collapse
Vibration Strength
Haptic feedback can be enabled for the wake gestures in /sys/android_touch/vib_strength. This setting takes a number between 0 and 90. Default is 20. Setting this to 0 disables haptic feedback for gestures.
Click to expand...
Click to collapse
S2W/DT2W power key toggle
If enabled, turning the screen off with the power button disables s2w and dt2w to save battery (since s2w/dt2w cause significant battery drain). When you turn the screen back on, s2w and dt2w return to their previous settings. If the screen times out, s2w/dt2w are not disabled this is only if you use the power button to turn it off. You can edit /etc/elementalx.conf to change the setting on boot.
Click to expand...
Click to collapse
S2W/DT2W Timeout
Doubletap2wake and sweep2wake can be automatically disabled after a certain number of minutes. I give a few choices between 5 and 120 minutes in the installer. Default is 30 minutes. You can put in whatever you want in /etc/elementalx.conf.
When the screen is turned on, the timeout is canceled and will start again next time you turn the screen off. This means that if you have your screen set to come on for incoming messages or notifications, the timeout will start over again.
If you also enabled the power button to toggle s2w/dt2w, there is no timeout when you use the power button, the wake functions are immediately disabled (same as before).
You can edit /etc/elementalx.conf to change the setting on boot.
Click to expand...
Click to collapse
Sweep2Sleep
Sweep2Sleep allows you to put the device to sleep by sweeping your finger across the navigation bar area. Unlike Sweep2wake, this does not cause any battery drain.
/sys/android_touch/sweep2sleep
0 = disabled
1 = sweep right
2 = sweep left
3 = sweep left or right
Click to expand...
Click to collapse
DRAW CIRCLE TO OPEN CAMERA
[Note/Requirement] - The ROM's itself must have this function > Click 2 times to open the Camera < enabled in settings, a ROM without this features, cannot use this "Draw Circle to Open Camera" option.
Credits to @antarix
"Tips to use circle gesture for camera(it won't work if you enable any gesture from wake gestures app) - need to use Kernel Adiutor for this options
The best thing is we can still use dt2w and s2w/s2s from kernel tweaking apps.
Draw a semi circle(it reacts too good even at semi circle)/full circle from top right/left to use circle gesture to open camera directly while screen is off.
The drawn circle should at least consume half of the screen".
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MSM_LIMITER
This function will limit the cpu in certain condition such as frequency during suspend, resume and min frequency. This features enabled in default and the frequency already been set for highest suspend freq to 787Mhz (screen off), min freq 300Mhz, resume freq 1.2Ghz. This feature may can reduce power consumption as it limit our cpu frequency after the screen off.
so here the step to disable it: -
1. By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable msm_limiter feature
Code:
su
echo "0" > /sys/kernel/msm_limiter/limiter_enabled
echo "0" for disable or echo "1" for enable it back
Furthermore, you can adjust the frequency of suspend, resume and min frequency to suit your taste here the command
1. For resume frequency
Code:
su
echo "<put you own frequency here without ">" symbol >" > /sys/kernel/msm_limiter/resume_max_freq
example:-
Code:
su
echo "1824000" > /sys/kernel/msm_limiter/resume_max_freq
this will make your CPU freq up to 1.8Ghz when screen on.. it just an example.
2. For suspend frequency
Code:
su
echo "<put you own frequency here without ">" symbol >" > /sys/kernel/msm_limiter/suspend_max_freq
Table of our devices frequency
Code:
300000
384000
600000
787200
998400
1094400
1190400
Click to expand...
Click to collapse
.
CUSTOM LOGO !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flash it like any zip
thanks to @antarix and @Angua 666 for testing with me and for inspiration for the logo ! :angel:
Cheers!
Sent from my Moto G using Tapatalk
hurtsky said:
updated ! ... enjoy ! thanks to @antarix and @Angua 666 for testing with me..
Click to expand...
Click to collapse
And enjoying too [emoji6]
Great kernel as always, thanks hurtsky
Sent using XDA One
smooth kernel ,by installing this dont know how truecaller started working previously it used to give fc
Good to see marshmallow version of this kernel...downloading...
thanks @hurtsky
very good work ,great! as japan cup
Thanks for this marshmallow version cool I already used it under lollipop....
Anyone having success in XT-1032?????
subodhverma21 said:
Anyone having success in XT-1032?????
Click to expand...
Click to collapse
\^^
No troubles for me under X1032 device
Envoyé de mon Moto G en utilisant Tapatalk
There is a problem with the download link
AFH says file not found
@hurtssky thankyou for coming so early... going to give it a ride...
fire7777777 said:
very good work ,great! as japan cup
Click to expand...
Click to collapse
Mchasard said:
Thanks for this marshmallow version cool I already used it under lollipop....
Click to expand...
Click to collapse
sachoosaini said:
@hurtssky thankyou for coming so early... going to give it a ride...
Click to expand...
Click to collapse
hope you guys enjoys the kernel, for those who still using CM12.1 , you may try flashing this kernel.. but please do backup first.. i only test it under M rom, but there is some devs said it still can be use for CM12.1..test it out and let me know how the result
FlasheD MM kernel on lollipop and that's work !!
Envoyé de mon Moto G en utilisant Tapatalk