Database Info

[TUT] Tasker CPU Control V5|Frequency/Governor Customisable Profiles|SetCPU with OCD

INSTALLATION INSTRUCTIONS ADDED TO POST #2
For those of you not familiar with Tasker, it’s a pretty damn amazing application that works toward fully automating your Android phone.
You can pick up a free trial version from here.
This thread is to show, assist and learn (from your input) how to fully utilise the newly introduced CPU controls, with the ultimate goal of preserving battery life without using additional applications such as SetCPU or other power saving scripts. This may look like a beast of a tutorial, but it really doesn't take that long to set up. Honest...
Tasker can be a little daunting at first, but a quick read through the manual, some tweaking of the profiles and step-throughs on the Tasker wiki and you’ll be up to speed in no time.
In order to control the CPU, you’ll need a rooted device and a compatible kernel. A quick acronym lesson can be found here. In brief, you require the following Governors (or as many of them as you can get!):
Performance (keeps the CPU frequency always at the maximum. Most power-hungry, most responsive)
Ondemand (when the CPU is needed, immediately sets it to maximum frequency. Slowly reduces the frequency back down to the minimum as time passes. Responsive, reasonable power usage).
Interactive (like Ondemand, but more responsive with slightly more battery usage)
Conservative (when the CPU load is needed, slowly increases the frequency to maximum. When the CPU is no longer needed, immediately drops back to the minimum. Less power-usage than Ondemand or Interactive, less responsive).
If there isn’t such a kernel for your device, then I can only suggest you beg and plead with a Dev in your device’s forum!
You can check the following in a file explorer to see your available frequencies and governors of your current/updated Kernel:
sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
I have a Desire and am running an Oxygen AOSP ROM. I’m therefore using vorkKernel detailed here. There’s a detailed breakdown in the first post of that thread showing the kind of kernel you’re looking for.
WARNING! DO NOT ENABLE THE PROFILES UNTIL YOU HAVE DOUBLE CHECKED THEY DO NOT EXCEED YOUR PHONE’S CAPABILITIES!! I TAKE NO RESPONIBILITY IF IT SETS ON FIRE! BE CAUTIOUS TO BEGIN WITH. IF THE AVAILABLE FREQUENCIES I DETAIL ARE NOT IN YOUR KERNEL, USE YOUR COMMON SENSE AND APPLY SIMILAR ONES! Ok? Right, ready to blow your phone up…? Just kidding….! Maybe….
Before you import the profiles, make sure you disable/archive/uninstall SetCPU or any other similar applications or scripts that could take precedent over the CPU control.
You’ll also need a couple of tools to see/hear your progress at a glance/listen:
A widget that shows CPU frequency, with regular refresh intervals would be handy. (If you don’t have one, I suggest you use Process Monitor available for free on the market here . The widget refreshes every 5 seconds from the home-screen).
As they’ll be some ‘screen-off’ states, it's very useful to have a speech engine so you can be told what’s happening without having to turn the screen on and therefore changing the state! (I use Pico TTS)
The application CPU Spy can be helpful to show you how these profiles combined with the Data Sync profiles will increase the amount of time your device will be spending in 'deep-sleep' and at lower frequencies. Thanks leftAlone for pointing this app out.
In Tasker, the main triggers for the CPU controls are as follows:
Display Off
Display On
Battery Low
Battery Hot
Phone Charging
In call (added in V2)
End Call (added in V2)
Initial Boot (added in V2)
Application Launched (added in V2)
In my set-up, these triggers become intertwined as there is often more than one active state to consider. Here we go....
READ THE REST OF THIS POST, BUT INSTALL WITH INSTRUCTIONS FROM POST TWO!
The speech profile (CPU-SayState) is the first one to download – it’s set up to tell you every 5 minutes (in very clear English), your frequency and governor. Not only will this confirm that your screen-off state is working correctly by just listening, but when you are performing other routine tasks, it will alert you if for some reason you find yourself overclocking/underclocking when you don’t want to be and you'll know something is wrong (the alternative to this is good old fashioned log files).
Next, CPU-BatteryHot. It's stand alone. You’ll see that the ‘Event’ is simply ‘Battery Overheating’. If this event occurs, then the governor is set to conservative and the frequencies to 245 and 422,400. Let’s be honest, if you do have an overheating battery, you’re more likely to panic and put the phone in the fridge rather than rely on this profile to resolve it, but it’s a simple start and provides a useful notification should this ever occur.
Next, CPU-DisplayOff. This is a good chance to save some battery life. The event is ‘screen off’ and the task sets a tiny vibrate notification so you’ll know it’s applied whilst the screen is off. An icon will be present in the status bar when you turn the screen back on. Conservative governor and frequency of 245 and 384. You of course should tweak these to whatever you wish - that's the point of this! The other tasks within the profile are removing the notification of other CPU profiles that may have been active prior to the screen turning off.
Next, let’s set up CPU-BatteryLow. It’s relatively stand alone again, triggered by an event of the ‘battery level’ being less than 25%. Conservative governor, with frequencies of 245 and 499,200 with an added IF statement at the bottom confirming the battery level. A popup on the screen will tell you the battery is low, which will go away on its own or can be pressed to dismiss. All other notifications of previous states are cancelled and finally a ‘stop’ is applied IFthe battery goes above 35%. At this point a task is performed that matches the governor and frequency of what will be your ‘regular ***’ CPU settings (again, these should be whatever you wish). This will end once the screen is turned off so the profile returns to CPU-DisplayOff.
Next, CPU-ChargingAny. Triggered by the 'power' state, the first task checks the battery level being above 50%. If it isn’t, an interactive governor is applied (to concentrate on charging), if it is, a performance governor is applied pushing the frequency up to 1075200. A status bar notification/icon and a vibrate pattern alert you that you are overclocking. Other notifications are killed.
Now we have to look at cancelling the overclocking once the phone is no longer charging/on external power. This isn’t totally straight forward, as the preferable states (inverted) of ‘no usb connected’ or ‘battery not charging’ relate to most of the time you use your phone.
The answer is to use an ‘exit task’, which will activate once the current state no longer applies e.g. the charge is removed. At this point, we need to check the current state of the phone, by applying tasks in order of their priority. The first task checks if the screen is off (therefore assuming the phone is no longer being used). If it is, it applies the DisplayOff profile. Secondly, if the battery level is now greater than 25%, it applies the DisplayOn profile (shown below). Finally (assuming the other two tasks states were not true), it applies the BatteryLow profile. The current task is instructed to ‘stop’ once a true state is found.
Finally, CPU-DisplayOn. The event is of course ‘display on’ and it applies the governor and frequencies that you would consider your ‘regular profile***’ for your normal phone usage. For me this is interactive with frequencies of 245 and 998,400. It of course first checks that the battery is not less than 25%, otherwise the BatteryLow profile would have already been activated and should be left to do so. A status notification and the killing of existing notifications is included at the end.
You’ll need to create a manual ‘regular profile’ (mine is called CPU-InteractiveManual in the .zip folder) that you can leave unchecked. This is named to match the *** above. It’s also there in case circumstances require you deactivate all of the other profiles and just run your regular profile (because you want to).
Very finally (!), I have a manual MaxOverclock profile, which I activate when I’m going to be using certain applications – A ROM Emulator for example.
Added in Version 2
CPU-DeviceBoot. I noticed that the Kernel I'm using boots as standard using a conservative governor (this surprised me a little) and overclocking to max frequency (I assume to help boot speed). This profile waits 30 seconds on initial boot and then checks the phone state before applying the correct profile from above.
CPU-DuringCall. During a call, my proximity sensor turns the screen on and off. When inputting numbers on a call (Voicemail for example), this caused the CPU-DisplayOff and CPU-DisplayOn profiles to be constantly flicking on and off unnecessarily. This profile deactivates all CPU profiles until the call is finished.
CPU-EndCall. Once the call is finished, the profiles are activated once again.
An obvious way (so obvious I previously didn't include it) to preserve battery life is to set individual CPU profiles for individual applications. Tweaking of these if you suffer lag, will help you find the minimal settings for each application.

STEP-THROUGH INSTRUCTIONS
With Tasker currently ristricting the import of CPU actions, I've had to strip them out of the profiles, meaning you have to add them in manually for the time being. Shouldn't take too long... Follow these instructions:
Download the latest 'Tasker CPU Profiles STEP-THROUGH.zip' and Unzip the profiles into sdcard/Tasker/profiles - Import them individually from the menu options. There should be 11:
CPU_BatteryHot
CPU_BattertLow
CPU_ChargingAny
CPU_DeviceBoot
CPU_DisplayOff
CPU_DisplayOn
CPU_DuringCall
CPU_EndCall
CPU_InteractiveManual
CPU_MaxManual
CPU-SayState
There is one additional stand-alone task:
MTVar
Ensure they remain unchecked until we've added all of the CPU activities below.
Before applying your custom CPU profiles, it would be highly recommended that you observe your current kernel's/ROM's/device's behaviour using home-screen widgets and the speech task included. My device (Desire), has custom kernels that use different governors to get the best performance out of the device. Please understand which governor(s) your kernel dev has focused on and if the voltage and/or governor(s) are changed in certain states. This will be well documented in your Kernel thread.
Overclocking
Please be more than aware that overclocking your device is not without its risks. Within the profiles Overclocking will occur only when the screen is on, the device is on charge and the battery is above 50% to ensure this is intentional. Should your screen go off, you will have to manually restart overclocking by unplugging and replugging the charger. Using a 'Performance' governor, will increase the CPU frequency to the maximum available and remain at that level. This is unecessary unless you are using a particularly high resource application such as a ROM emulator. Using an alternative governor that allows maximum frequency when required, but does not remain there when not, should be considered.
Instructions
The CPU settings have been replaced by actions entitled 'Type'. The text says 'Insert Frequency and Governor here'. In addition, they may be instructions to tick the 'IF' statement and add the values included in the text. Remove the 'Type' entries as you go, replacing them with the following suggested entries:
(CPU action entries are contained under 'Misc'
Select Edit
Press +
Select Misc
CPU)
Tap CPU-DisplayOn
Tap on CPUDispOn - Replace action #6 | Interactive | 128,000 | 998,400
Tap CPU-DisplayOff
Tap on CPUDispOff - Replace action #7 | Conservative | 128,000 | 245,000
Tap CPU-BatteryLow
Tap on CPUBatLow - Replace action #2 | Conservative | 128,000 | 998,400
Tap CPU-ChargingAny
Tap on CPUCharg - Replace action #2 | Interactive | 128,000 | 998,400
Replace action #3 | Performance | 128,000 | 1,075,200
Tap CPU-BatteryHot
Tap on CPUBatHot - Replace action #1 | Conservative | 128,000 | 422,400
Tap CPU-InteractiveManual
Tap on CPUManual - Replace action #1 | Interactive | 998,400 | 128,000
Tap CPU-MaxManual
Tap on CPUMaxMan - Replace #1 | Performance | 128,000 | 1,075,200
----------------------------------------------------------------------
Enable all APART FROM CPU-MaxManual and CPU-InteractiveManual, click 'On', then apply and turn the screen off and on and you should be up and running!
I assume you'll need to add your own icons in to each of the notifications.
-----------------------------------------------------------------------
Minimalistic Text Widget
Also included in the tasks and the V5 download is a profile for Minimalistic Text showing the Tasker variables all of my profiles use. Drag it into the Minimalistic Text folder on the SD card and it will be there in the preference manager. It you don't use all of my other profiles (why the hell not?!) you can delete the entries that are not applicable to you. My other profiles are in my signature btw. I've no idea where my signature is though... Not using Minimalistic Text?? It's a great low resource home-screen widget with Tasker integration. Check out the XDA thread here
I DON'T WISH TO USE THE MINIMALISTIC TEXT PLUGIN!
Then delete the following 'Perform Task MTVar' entries:
CPUDispOn - Action #9
CPUDispOff - Action #14
CPUCharge - Action #10
CPUBatLow - Action #8
CPUEndCall - Action #2
CPUBatHot - Action #6
CPUManual - Action #5
CPUMaxMan - Action #5

Conclusion
I’ve never used so much battery working these out!! It may well be that the amount of tasks, or the way they are structured, actually uses more battery life than controlling the CPU could save. I’ll be running some tests over the coming days to monitor it. If that does prove to be the case, I'll still be glad I’ve done this and learnt more about this fantastic application and look forward to it making me even more lazy.
Let me know your feedback please folks, inconsistencies, errors, I’m all ears and feel free to use the 'thanks meter'
harmohn said:
Battery life:
Without brandall's profiles: ~9hrs
With brandall's profiles: ~16hrs!
Click to expand...
Click to collapse
torsrex said:
my batterylife has GREATLY improved!
Without tasker: 10h 21% left, with tasker: 15h 67% left..!
Click to expand...
Click to collapse
MadeUpPost said:
Since using your profiles, I haven't had to charge my battery in 23 days and I'm having much better sex with my wife! Thanks!
Click to expand...
Click to collapse
FAQ
Q) I'm getting missing plug-in errors on V5? What do I do?
A) Read the bottom of post #2 and delete the Minimalistic Text actions if you do not wish to use it.
Q) Which profiles do I leave unticked and ticked again??
A) See this post
Q) I get a CPU Action Not Available error - why?!?
A) See the bottom of this page (thanks wanfauzan)
Q) Why doesn't Overclocking start again when the display is turned on and the phone is on charge?
A) Best solution see here. Credit Matrix72
Q) The icons you use are rubbish. How do I use my own?
A) See this post
Q) I have many other Tasker questions, can I post them here??
A) To avoid clutter, probably best to use this official Google group
Q) My phone is sluggish when the 'battery low' profile is active.
A) Be cautious, but adjust the frequencies and maybe governor until you find the perfect settings for your phone.
Change Log
Code:
[B][U]V2[/U][/B]
Added [B]CPU-DuringCall[/B] profile to V2 .zip
Added [B]CPU-EndCall[/B] profilie to V2 .zip
Added [B]CPU-DeviceBoot[/B] profile to V2.zip
Changed how [B]CPU-DisplayOn[/B] behaves when battery level low
Changed how [B]CPU-ChargeAny[/B] behaves when battery is less than 50%. Also added sound effect and matching vibrate pattern because I'm childish.
Added wait task to [B]CPU-BatteryLow[/B] until charge reaches 35%
Added [B]CPU-Navigation[/B] example profile to V2 .zip
Changed how cancelled notifications are handled for aesthetic reasons.
[B][U]V2.1[/U][/B]
Added missing IF statement to vibrate pattern of 'Overclocking' on [B]CPU-ChargeAny[/B]
[B][U]V2.2[/U][/B]
Changed collision handling of [B]CPU-BatteryLow[/B] to consider wait task
[B][U]V3[/U][/B]
Updated [B]CPU-DuringCall[/B] to create an 'in call' variable ([B]%INCALL[/B]), that can be used in other tasks.
Updated [B]CPU-EndCall[/B] to create an 'in call' variable ([B]%INCALL[/B]), that can be used in other tasks.
Changed notification handling to include specific titles, so not to cancel notifications of other Tasker profiles.
Removed Overclocking Sound and chilled the vibrate pattern.
[B][U]V4[/U][/B]
The below update [COLOR="Red"]*REMOVED AS IN V5*[/COLOR] prevents the quick screen off/screen on changes between [B]CPU-DisplayOff[/B] and [B]CPU-DisplayOn[/B] which can cause lag and echo errors. This was a headache to resolve due to too many reasons to list, but I've resolved it by adding a 5 second wait before the display off CPU settings are applied - if within that 5 seconds you turn the screen back on, the display off settings will not apply, consequently neither will the display on settings reapply. Someone needs to donate me some paracetamol...
It's achieved with an additional variable [B]%CPUSS[/B] (CPU sleep state) which is set to a value of 1 within the 5 second wait and a value of 2 after (once the CPU screen off settings have applied). This way, the CPU display on settings know whether to activate, or they remain active and therefore don't reapply....
[B][U]V5[/U][/B]
* So many I've forgotten them all.... Oops!
Bugs
All totally fixed in V5 (I hope).
Feature Requests
Consider states for 'smartass' governor.
Thanks
torsrex - Risking device and limb testing
-----------------------------------------------------------------------------------------------------
Due to the amount of changes, there is no 'step-through' update for users of the lower versions. Delete the profiles you have and it's a lightening quick addition of the CPU entries from post #2!
------------------------------------------------------------------------------------------------------
The thanks meter lets me know I'm appreciated!

I've used a lot of battery working out similar profiles myself
Will have to check yours out when I get home. Having voice overs for frequency and governor is a good addition!

I used CPU control with tasker and since then I uninstalled SetCPU that was a great soft but Tasker give me so much freq control for each application.
Example Book reader don't need the full juice and you can set automaticaly a low frequency.
Tasker is a great tool.

harmohn said:
I've used a lot of battery working out similar profiles myself
Will have to check yours out when I get home. Having voice overs for frequency and governor is a good addition!
Click to expand...
Click to collapse
Since I've stopped playing around quite so much, my battery life does seem to have improved! Could be just wishful thinking though...
enotar said:
I used CPU control with tasker and since then I uninstalled SetCPU that was a great soft but Tasker give me so much freq control for each application.
Example Book reader don't need the full juice and you can set automaticaly a low frequency.
Tasker is a great tool.
Click to expand...
Click to collapse
I've added an example of setting the CPU profiles for individual applications just in case.
Let me know your feedback! I assume no news is good news!? V2 updated in change log.

I get error trying to import any of your profiles, I'm I doing something wrong??

goz5000 said:
I get error trying to import any of you profiles, I'm I doing something wrong??
Click to expand...
Click to collapse
What is the error? I'll start with the obvious:
Have you checked you're running the latest version of Tasker? Mine is 1.0.20u3m
Have you unzipped the files into sdcard/Tasker/profiles ?

import failed, task contains actions unsuitable for import.
I got cpu end call, cpu device boot, and cpu during call to import but the others will not.
I'm using the vork kernel on CM7

goz5000 said:
import failed, task contains actions unsuitable for import.
I got cpu end call, cpu device boot, and cpu during call to import but the others will not.
I'm using the vork kernel on CM7
Click to expand...
Click to collapse
You're absolutely right - I just tried to import them myself and got the same result! Ok... I'll find out what's causing the problem...

Wow, I don't know much (anything) about the app, but I'm surprised you're allowed the level of control over the OS from userland like this without root privileges.

Syndacate said:
Wow, I don't know much (anything) about the app, but I'm surprised you're allowed the level of control over the OS from userland like this without root privileges.
Click to expand...
Click to collapse
The CPU controls are only for rooted devices unfortunately. The are many other customisations within Tasker that don't require root though. It's worth a free trial

brandall said:
The CPU controls are only for rooted devices unfortunately. The are many other customisations within Tasker that don't require root though. It's worth a free trial
Click to expand...
Click to collapse
Ah, that makes sense. I didn't catch the 'it needs to be rooted' part when I read the OP.

Syndacate said:
Ah, that makes sense. I didn't catch the 'it needs to be rooted' part when I read the OP.
Click to expand...
Click to collapse
I'll add it in, as I don't want it to be misleading...
Thanks.

goz5000 said:
import failed, task contains actions unsuitable for import.
I got cpu end call, cpu device boot, and cpu during call to import but the others will not.
I'm using the vork kernel on CM7
Click to expand...
Click to collapse
Tasker didn't allow the import of the CPU actions. For now, a step-through guide is added to post two to get these working. Please download the new .zip file.
Your feedback would be appreciated.

Adjust the following profiles as follows:
Tap CPU-DisplayOn
Tap on INT DISP ON
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Tick IF
Click on lable icon, select Battery Level
Click on '-' select Maths:Greater Than
Enter 25 in box
Done
Drag to position 3
Done
Tap CPU-DisplayOff
Tap on CPU CON 384/245
Select Edit
Press +
Select Misc
CPU
conservative
245000
384000
Done
Drag to position 1
Done
Tap CPU-BatteryLow
Tap on CPU CON 254/499
Select Edit
Press +
Select Misc
CPU
conservative
245000
499200
If
Click on lable icon, select Battery Level
Click on '-' select Maths:Less Than
Enter 25 in box
Done
Drag to position 1
Click on tools icon - ensure Collision Handling is set to 'Abort Existing Task'
Done
Tap CPU-ChargingAny
Tap on CPU PER 998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Tick IF
Click on lable icon, select Battery Level
Click on '-' select Maths:Less Than
Enter 50 in box
Done
Drag to position 1
Press +
Select Misc
CPU
performance
245000
1075200
If
Click on lable icon, select Battery Level
Click on '-' select Maths:Greater Than
Enter 50 in box
Done
Drag to position 2
Ensure the Carstart.wav (included in the .zip) is selected (if you want it) under 'Music Play' - Otherwise just delete the entry.
Done
Tap CPU-BatteryHot
Tap on CPU CON 422/245
Select Edit
Press +
Select Misc
CPU
conservative
245000
422400
Done
Drag to position 1
Done
Tap CPU-InteractiveManual
Tap on CPU INT 245/998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Done
Drag to position 1
Done
Tap CPU-MaxManual
Tap on CPU-MAX
Select Edit
Press +
Select Misc
CPU
performance
245000
1075200
Done
Drag to position 1
Done
Tap CPU-Navigation
Tap on CPU-NAV 245 998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Done
Drag to position 1
Done
Tap on CPU INT 245/998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Done
Drag to position 1
Done
So after I do the above...do I just enable CPU-MaxManual and CPU-InteractiveManual...or all.

Action unavailable
RESOLVED. found the user guide at the bottom of this page
http://tasker.dinglisch.net/userguide/en/cpu.html
hello,
I can't set the CPU setting. Tasker said, that action is unavailable on this device. I am using HTC Magic 32b rooted with this rom [ROM]Enomther's TheOfficial D/S - v2.14.2 - 12/28/2010
http://forum.xda-developers.com/showthread.php?t=538456
What could be the problem?
Thanks

brandall said:
Tap CPU-Navigation
Tap on CPU-NAV 245 998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Done
Drag to position 1
Done
Tap on CPU INT 245/998
Select Edit
Press +
Select Misc
CPU
interactive
245000
998400
Done
Drag to position 1
Done
----------------------------------------------------------------------
Enable all APART FROM CPU-MaxManual and CPU-InteractiveManual, click 'On', then apply and turn the screen off and on and you should be up and running!
I assume you'll need to add your own icons in to each of the notifications.
-----------------------------------------------------------------------
Click to expand...
Click to collapse
For the last step, the variables for CPU INT 245/998 are already keyed in before.

Thanks for the tutorials. I think I'll simplify it for my tastes, but this was a very helpful place to start. Looking forward to seeing how your performance/battery pans out.

Regarding the default setup:
Charging + turning display back on + >50% battery: you go back into "CPU interactive" when I would expect to go back into "Overclocking" since it is still plugged in.

[ROM] CyanogenMod 10 (qwerty)

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:

[ROM] Epsilon Project < V5.0 | 12/01 > / < Clean | Fast | Stable | +Battery >

[ROM] Epsilon Project < V5.0 | 12/01 > / < Clean | Fast | Stable | +Battery >
{
"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"
}
This version is developed on the last update of KitKat (4.4.4). It has been optimized for better battery life and performance development, without losing any proper function of our device. There was eliminated some google apps that are available in the playstore, has integrated settings within setting menu. If you want a 100% Stable Rom, Updated, Light and with Good Performance without losing any functionality Epsilon Project ROM is for you.
- Base KXB21.14-L1.40 (XT1032 Stock 4.4.4 Brasil)
- All system apps updated
- Updated Drivers Qualcomm/Adreno GPU
- Optimizations GPS
- Kernel Aero (improve battery life while keeping up a reasonable performance.)
- Busybox initramfs
- Deodexed
- Zipaligned
- Rooted SuperSu
- Smooth Scroll Patched
- SQlite3 script (Wes Garner)
- Auto-Zipalign script (Wes Garner)
- Init.d support
- Bash support
- Op.App Enabled (With White tabs) under Security Settings
- Reduced navigation bar 40dpi
- Adblock Host
- Battery saving tweaks
- Best Performance, no more lags
- Removed Update option in Settings
- Removed some bloats (You can install from the Playstore)
- Fixed Google Bootanimation (Dankoman)
- Fixed Boot Logo (Google Edition)
- ...more changes in changelog for the next version
Epsilon Project V5 - Download
Update GravityBox 3.5.1 - Download
Stock Kernel (optional) - Download
Remove GravityBox Patch (optional) - Download
Fix Lang ENG Power Battery - Download
V-1
Initial Version
V-2
Rezipalign
Extended Power Menu (reboot / fast reboot / recovery / bootloader)
Navbar reduced to 38dpi
New Live Wallpaper Google Edition Sunbean
SuperSU has been moved to the setting menu
CM Calculator with more options
Xposed Gravity Box and Integrated Framework to the setting menu
Moved and translated the privacy manager application to the main setting panel
V-3
New Animations
New interface Holo Light 99%
Power Battery integrated in menu settings
New icons for navigation bar
Optimized Launcher Stock
New Boot Image
CM Calculator
Redesigned icons in settings
System Applications updated
Updated Adhost
Signal AOSP style icons (thanks tiaoalvino)
Changed dialer icon
Lidroid File Explorer (root explorer / file manager / ftp / and more)
GravityBox Updated (3.4.1)
V-4
Google Keyboard 3.2
Google Play Music 5.7 Material Design
PlayStore 5.0 Material Design
Google Chrome 38.0 Material Design
Google Services 6.1.71 Material Design
Updated AdBlock Host
Render GPU
GravityBox 3.4.7
New Tweaks for Better Battery
Unlock Camera Options
Rezipalign
Updated AeroKernel
V-5
New Script Installation
Updated SuperSU 2.36
Removed SuperSU Settings Menu
Updated ad blocking
Removed Google Chrome, feel free to choose the browser that you like
Removed Google Music, feel free to choose the player that you like
Removed File Explorer, feel free to choose the file explorer that you like
Removed the Motorola Demos well as services report errors motorola
Aero updated kernel (11/05)
Included AeroControl to configure the kernel Aero included in the Rom
Updated Fm Player
They have integrated and upgraded options motorola who brought default as migration, moto assist, etc
Updated the Gallery and Camera Motorola
Updated Google Play Service, Google Play and Google Keyboard
Updated GravityBox 3.4.9
Fixed status bar AOSP
Removed extended menu reboot, it can be enabled from the GravityBox
Drivers native GPU Moto G
Fixed the bug that did not allow for problems ViperSound install BusyBox
Installation unknown sources enabled by default
ReZipalign System
​

WHAT IS POWER BATTERY ?
Is an application that has been developed Kisler to improve the battery and in which we can select a number of options available to suit our needs can optimize the duration of battery . The idea of ​​this application has been to combine options that are useful for battery management and in turn be simple to use for everyone .
OPTIONS AND WHAT BRINGS ?
To improve this consumption have a number of options are:
Battery Percentage : This section is intended to determine the percentage of battery from Battery Power shall act performing the operations described below, default is 15 %.
BASIC SETTINGS
Wireless Mode: Selecting this option turns off the wifi if you have it activated before entering in the range of battery action defined in the beginning to Battery Power .
Data Mode : Selecting this option disables the data if activated before entering them in the range of battery action defined in the beginning to Battery Power .
Sync Mode: Selecting this option disables the synchronization should have it checked before entering the battery range of action defined in the beginning to Battery Power .
Bluetooth Mode: Selecting this option disables the bluetooth if you have it activated before entering in the range of battery action defined in the beginning to Battery Power .
mode Location: Selecting this option disables the location should have it checked before entering the battery range of action defined in the beginning to Battery Power .
Silent mode : Selecting this option disables the sound / vibration should have it checked before entering the battery range of action defined in the beginning to Battery Power .
Led Mode: Selecting this option disables the LED notification should have it checked before entering the battery range of action defined in the beginning to Battery Power .
ADVANCED
Mode Range: detects a known and active wifi zone wifi to connect automatically or off when leaving the area. (Discussed in detail below).
CPU Mode: Reduces CPU frequency automatically when entering the range defined in Battery Power Battery .
CPU Maximum Frequency : Defines how often you will use the CPU and the CPU mode , default 540 MHz
OPTIONS SCREEN
Brightness Mode : Reduces brightness automatically when entering the range defined in Battery Power Battery .
Brightness Percentage : Brightness Percentage to be applied in the glow mode , default 0 %.
Dark Mode: Controls the brightness as if it were an automatic but with lower values ​​to making work less and reducing the brightness sensor
Pocket Mode: Turn the screen to remove the phone from his pocket and is optimized to consume less than the native rom
Notification Mode: If a notification arrives for a few seconds to pick up the phone turns on the screen without pressing the (must activate accessibility " settings / accessibility / power battery" )
Notification Time : used in the second mode is defined notification
HOURS SMOOTH
Hours Mode : Turn the hour mode to manage data and wifi connection at a time interval.
Week end mode : Activates the alternate schedule for weekend
Restore Links: Restore connections to turn the screen during the hours so
Disable Sensors: Disables the sensors during the quiet hours
Set time : Set the time and day of the week that will activate the quiet hours
PROFILES
These options are combined with profiles Cyanogenmod . Its operation is as follows:
Battery power gives you the option to choose 2 profiles ( of Cyanogenmod ) for that you must enter the name of the previously created profile in the " Settings / Profiles " on Battery Power (default is "Home" and " street" ) . In each of the profiles you can enter a range of performance Power Battery, for example in the profile " House " 15% if we select the profile " Street " 25% . This is so that the Battery Power switch profiles automatically change its range of action and will know when your battery should act removing the options that you feel is necessary . To enable the use of profiles with Cyanogenmod Power battery is made from the " Profile Mode " option.
If not select any profile or the profile used is not one defined in Power Battery percentage to be used will be the first that we have defined earlier .
DISCLAIMER MODE RANGE
This mode produces no wakelock , battery consumption or anything similar . It is designed to conserve battery power in the event that we get out of range of our wifi preventing the active connection be used and consumed without activating it when we get to a place where there is a known wifi stay.
To do this I have based on location through LAC and Cell ID , or put more colloquially by the position of the antennas.
In the picture above you can see a simple design of antennas and radios. Battery Power antenna detects how you are and if you are in your area or not. To do this the first time I conectéis the wifi zone start checking nearby antennas ( depending on the house may be affected by one or more antennas ) .
Once detected out of the range of action of these antennas ( this may vary ) check the state of wifi is connected and if it will be off. The opposite case is that when entering the range of a registered as a wifi access point antenna, wifi be activated.
In the case we are in the same location, for example our home and want to disable / enable wifi to not have changed position we can do like coming to a new area to choose a new wifi network , since disconnection / automatic connection is made just by changing antenna .
In the event that wifi is turned off before choosing a new wifi network you connect may be due to a crossing of antennas ( due to the change from one to another so quickly disconnection may occur ) and if the problem persists after several attempts the solution may be to move a few steps to avoid this junction or off the range mode temporarily to introduce this new wifi.
Advantages of this: It has no wakelock , maximum energy savings by not using the location network location.
Disadvantages: If you are traveling to a remote area of your home, but that you get that antenna signal , being detected as " known antenna " believes these at home and activate the signal . This drawback will very much depend on where you live each and the number of antennas that affect the area. As a rule in the city or area where a large number of antennas work better this way .

Sounds great, shall test! Sounds smooth without even testing

core720 said:
.... reserved[
Will report.... Downloading
Click to expand...
Click to collapse

bugs
Hi, are there any bugs?
because I have school tomorrow and I don't want to have bugs. I need the gps. Is it working?
and is there the same bug as in the CM that you can't connect to wifi extender networks or is it all stock based?

Need to download Stock Kernel or no?
Any bugs to look out for?
Cool, it has app ops!
Bugs
MAC address is messed up @core720

will I lose duel sim support, if I flash this? Given this is based on 1032 single sim.

xt1033 compatible?

!n0x said:
Need to download Stock Kernel or no?
Any bugs to look out for?
Testing...
Click to expand...
Click to collapse
No

its not support xt1033 dual sim its based on (XT1032 Stock 4.4.4 Brasil). so not working on our devices. no signal.

Any chance of a xt1033 compatible?

ART compatible?

Perhaps the DEV will kindly make a version of this ROM based on Stock XT1033 for Dual-SIM people. Having quickly looked: FM Radio should work and Motorola Camera / Gallery are included.

Wow
Waauw, this rom is greaaaat, soo smooth. I flashed the PA mini gapps on it and everything works great.
Thank you so much for this rom. I would like to hit the thanks button 30 times if I could

Sounds nice ROM, i will test

I just tried to install but the file is corrupted by me

I do believe you have to convert your file system type if you're running GPE or custom roms before flashing this one due to being based on stock. Is that right?

rogeriorp said:
I do believe you have to convert your file system type if you're running GPE or custom roms before flashing this one due to being based on stock. Is that right?
Click to expand...
Click to collapse
Only GPE converts USERDATA partition. If you are running anything else; you can just wipe and flash this.

Mchasard said:
I just tried to install but the file is corrupted by me
Click to expand...
Click to collapse
What problem u r facing ??

[Kernel][6.0] Valkyrie-L-6 [14/9/2016]

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

[DISCONTINUED][KERNEL][6.x/7.x][ULTIMATE™][3.10.104] for Lenovo K3 note

Warnings:-
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and no point
* in pointing the finger at me for messing up your device
*/
FEATURES
Compiled with UBERTC-6.0.x
Added CPU Governers
->Intellidemand
->ThunderX
->Wheatley
->Alucard
->Interactiveplus
->Elementalx
->Adaptive
->Lionheart
Added I/O Schedulers
->sio
->fiops
->zen
->tripndroid
->vr
->bfq
WiFi Power management control
Wake Gestures
ThunderQuake Engine 1.0 - Vibration Intensity Controller
Add OC 1.9Ghz
CPU Hotplugging
->Thunderplug
->Intelliplug
Dynamic FSync for better performance
F2FS & NTFS support
Selinux set to permissive
Added Advanced new TCP Congestion controls
Lock initial TCP window size to 64k (Improves network ping and output)
Init.d support
Overclock/Underclock
Android Nougat support
INSTALLATION INSTRUCTIONS
Make a BACKUP of boot partition using TWRP just to be on safeside!!.
Flash the zip according to the ROM which you are using.
Note:
1. Wake gestures can be controlled by using this app.
2. All thunder features can be controlled from ThunderZap Control app. Download it from playstore.
3. Use Kernel Adiutor to enable/disable options.
4. I personally recommend to use EX Kernel Manager by flar2.
**SweeptoSleep works only at bottom of screen i.e above navigation bar (Area where you open app drawer).
All thunder stuff can be known at this site.
5. Please use intelliplug driver when frequency transistion doesnt take place in right way.(It may crosses the freqency to max one.)
DOWNLOADS
Non Overclock
Ultimate v1.4.zip
Ultimate v1.3_Vibe.zip
Ultimate v1.3.zip
Overclock
Ultimate v1.4 (OC).zip
Ultimate v1.3 (OC).zip
Ultimate v1.3_Vibe (OC).zip
View attachment 3971231
View attachment 3971230
View attachment Ultimate_v1.1.zip
View attachment Ultimate_v1.0.zip
CHANGELOG
Version 1.4
Few fixes for full Nougat compatibility.
Change the modem default to LWG.
Version 1.3
Enable UID_CPUTIME.
Update GT9XX touch driver(Fix to avoid button touches being recognized as digitizer presses when wakegestures are turned on).
Set Westwood as default TCP Congestion Alogorithm.
Seperated into OC and Non OC flashable zips.(as per user's request).
Version 1.2
F2FS & NTFS support.
Selinux : Permissive.
Added various TCP Congestion algorithms.(Check out this for more information)
Init.d support.
Added Intelliplug hotplug driver.
Android N support.
Upgraded Dynamic Fsync to 2.0.
Optimized for performance.
LED notifications are fixed now.(Separated into two flashable zips for Stock/VIBE and CM/AOSP Roms. You need to flash accordingly.)
Added various clock rates (including overclock frequencies) in default DVFS table. (You can even underclock frequencies which are not Stock enabled).
Temporarily removed thunder charge driver as it depends on linear charging but our device implements Lenovo standard charging support.(Need to switch to linear charge before implementing the driver. Will look into this later).
Version 1.1
Added Dynamic fsync.
Improved Wake gestures with Haptic feedback.(Use Wake Gesture App)
Removed Tap2Unlock.
Added OC 1.9 Ghz.
Fixed LED notification bug.
Removed Smartmax Governor
3.10.103->3.10.104
Version 1.0
Added CPU Governers
Added I/O Schedulers
WiFi Power management control
Wake Gestures(Wake Gestures : Sweep2wake, Sweep2sleep, DoubleTap2wake and Tap2Unlock).
ThunderQuake Engine 1.0 - Vibration Intensity Controller
ThunderCharge Fast Charge Driver
XDA:DevDB Information
ULTIMATE Kernel, Kernel for the Lenovo K3 Note
Donations:
Contributors
GSandeep
Thanks to
1. Daniel_hk for fixing tfa9897.:good:
2. Varun.chitre15 for his thunder drivers.
3. faux123 for Intelliplug driver.
4. flar2 for elementalx.
Source : https://github.com/GSandeep96/Kernel_Ultimate_6.0-7.1_k50a40
Anykind of bugs if you come across can be notified.
My email Id : [email protected]
Version Information
Status: Stable
Current Stable Version: 1.4
Stable Release Date: 2017-02-23
Created 2016-11-16
Last Updated 2017-02-23

Reserved

I'm replying so the thread would be seen in XDA Labs. It's apparently a known issue.
EDIT: Threads with no replys are sometimes not shown inside XDA Labs app. Okay, now the thread is visible. I will test the kernel later...

anyone try this already?

GSandeep said:
Warnings:-
FEATURES
Compiled with UBERTC-6.0.x
Added I/O Schedulers
->sio
->fiops
->zen
->tripndroid
->vr
->bfq
Wake Gestures
ThunderCharge Fast Charge Driver
CPU Hotplugging(thunderplug driver)
Make a BACKUP of boot partition using TWRP just to be on safeside!!.
Added Dynamic fsync.
Removed Tap2Unlock.
Fixed LED notication bug.
3.10.103->3.10.104
Version 1.0
Added CPU Governers
WiFi Power management control
ThunderQuake Engine 1.0 - Vibration Intensity Controller
ThunderCharge Fast Charge Driver
XDA:DevDB Information
ULTIMATE Kernel, Kernel for the Lenovo K3 Note
Contributors
GSandeep
Thanks to
1. Daniel_hk for fixing tfa9897.:good:
2. Varun.chitre15 for his thunder drivers.
3. Sandeep.sethi for fixing thunder quake & LED bug.
Source : https://github.com/GSandeep24/Kernel_Ultimate_K50a40
Anykind of bugs if you come across can be notified.
My email Id : [email protected]
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2016-11-17
Created 2016-11-16
Last Updated 2016-11-16
Click to expand...
Click to collapse
Can you tell me how to increase battery and better ram management?

GSandeep said:
....
Click to expand...
Click to collapse
Downloading and testing. Will report soon.

Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything

raghuM said:
Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything
Click to expand...
Click to collapse
WiFi sleeps when your device is docked

how to control the wake from back key..

jomypjose said:
how to control the wake from back key..
Click to expand...
Click to collapse
Use kernel auditor app

Flahsed with 1631 vdt rom... working well so far..
Thanks for this kernel and keep it up... :good:
Sent from my Lenovo K50-t5 using XDA Labs

Here it is all about!
raghuM said:
Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything
Click to expand...
Click to collapse
There are three power modes for the Wi-Fi Power Management area and they are:
PM_CAM
PM_FAST
PM_MAX
CAM (Constantly Awake Mode) – keeps the radio powered up continuously to ensure there is minimal lag in response time. This power save setting consumes the most power but offers the highest throughput.
Fast – switches between PSP mode and CAM mode, depending on network traffic. For example, it switches to CAM when it is receiving a large number of packets and switches back to PSP after the packets have been retrieved. Fast is recommended when power consumption and throughput is a concern.
Maximum – the access point buffers incoming messages for the radio. The radio occasionally ‘wakes up’ to determine if any buffered messages are waiting and then returns to sleep mode after it requests each message. This setting conserves the most power but also provides the lowest throughput. It is recommended for radios in which power consumption is most important (such as small battery-operated devices).

GSandeep said:
There are three power modes for the Wi-Fi Power Management area and they are:
PM_CAM
PM_FAST
PM_MAX
CAM (Constantly Awake Mode) – keeps the radio powered up continuously to ensure there is minimal lag in response time. This power save setting consumes the most power but offers the highest throughput.
Fast – switches between PSP mode and CAM mode, depending on network traffic. For example, it switches to CAM when it is receiving a large number of packets and switches back to PSP after the packets have been retrieved. Fast is recommended when power consumption and throughput is a concern.
Maximum – the access point buffers incoming messages for the radio. The radio occasionally ‘wakes up’ to determine if any buffered messages are waiting and then returns to sleep mode after it requests each message. This setting conserves the most power but also provides the lowest throughput. It is recommended for radios in which power consumption is most important (such as small battery-operated devices).
Click to expand...
Click to collapse
Ok now i get it. Thanks

Sorry.
jomypjose said:
how to control the wake from back key..
Click to expand...
Click to collapse
I didnt get you. If you are troubling with wake gestures. Just go to Kernel Aduitor app. Go to wake menu... enable all options and check Apply on boot. Also use wake gestures app to customize. Check out screenshots that i have posted.

Rajendran Rasa said:
Use kernel auditor app
Click to expand...
Click to collapse
there is only dt2w,s2w and s2s no option for back key

just flash this kernel , and wow! i never think this cpu can boost up to 1.9 ghz! and so far no issue because is just an hour ago.
Can you share what is the best setting for thunderplug ? Or we remain it as default?

this is the second time phone reboot because game halt.
not sure is frequency too high or thunderplug cause it .

adikri said:
Flahsed with 1631 vdt rom... working well so far..
Thanks for this kernel and keep it up... :good:
Sent from my Lenovo K50-t5 using XDA Labs
Click to expand...
Click to collapse
Good news, is the notification led working with your rom?
Thanks

ekihd said:
Good news, is the notification led working with your rom?
Thanks
Click to expand...
Click to collapse
Yes, it working as well..

temporary back to renice because this kernel makes so much auto reboot . i already limited cpu frequency to 1.6ghz .switch off the thunderplug .only select governor as wheatley .
but phone still hang .
not sure whats going on