(DISCONTINUED)[KERNEL][JB] JellyKernel for Optimus L7 II (Single SIM) - LG Optimus L3 II, L5 II, L7 II, L9 II

{
"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"
}
-----JellyKernel-----​
This is an all-in-one kernel for Jelly Bean.
Keep in mind, that this kernel is made for balanced battery life. And be advised, that phone could end up in a bootloop. Be awared of that.​
DOWNLOAD SECTION IS BELOW!!!​
OTG:​
HTML:
Some notes:
-Stock ramdisk doesn't have appropriate lines for mounting /sys/kernel/debug, which is needed for manipulating OTG implementation on our device.
-You need to enable OTG support in the system itself. There are apps for fixing that, look up in the Play Store.
-It's still could be kind of jerky to get it to work. Feel free to ask about OTG.
Instructions for OTG support:
1. Open up your terminal and first type:
mount -t debugfs nodev /sys/kernel/debug
2. Now it's tricky:
For peripheral mode (it's default mode used when charging and etc):
Type in the terminal:
echo peripheral > /d/otg/mode
For host mode (for connecting USB devices):
echo host > /d/otg/mode
That's the current implementation atm. I'll try to do something easier later.
Features, which should be implemented later:​-Gamma control (will implement that later)
-CPU VDD sysfs interface (useless)
-Higher CPU overclock (not possible yet)
Installation:
Flash this zip through CWM and you're good to go.
Please leave me THANKS if you can.
I want to say thanks to:
CrashBandicootX (for amazing kernel banner)
neutrondev (for giving me some opinions)
dazzozo (for fixing OTG)
skyinfo (for awesome commits)​

DOWNLOADS:
BE AWARE, THAT DATA COULD GET CORRUPTED!!! ALWAYS MAKE NANDROID BACKUP BEFORE FLASHING MY NEWEST KERNEL BUILDS! I WON'T BE RESPONSIBLE FOR THE DAMAGE YOUR DATA GOT!!!! IT'S HIGHLY RECOMMENDED TO MAKE FULL DATA WIPE AND REFLASH SYSTEM, BECAUSE KERNEL IS ABSOLUTELY DIFFERENT FROM NOW ON!!!
Build 20150517-015 (STABLE)
HTML:
Fixed camera
Some more cpufreq driver updates
Build 20150516-012 (TESTING)
HTML:
Updated fat filesystem drivers, fixed some bugs
CPU usage dropped at idle
Heavy SLUB optimizations and fixes
Build 20150516-006
HTML:
Fixed some bugs regarding CPU access
Much better hotplug functionality (now you can leave mpdecision enabled)
CPU scaling optimizations
ext4 fix (one weird thing: after installing this kernel, startup wizard will appear - turn off wifi and go through all the procedure, otherwise you will be stuck at google login)
Fixes from LG G2 kernel
Build 20150515-001
HTML:
Tons of improvements
KGSL fixes, stability fixes, working scaling governor
Dynamic FSYNC
Made scaling drivers to work more efficiently
Lessened up chances of QDSP5 to crash in low memory situations, improved decoding
Stabilized wakeup/sleep switching
Several quirks for better interconnect between MDP and GPU
TONS of camera fixes, now it should work marginally better, provide better framerate when recording
Improved ZRAM efficiency
Introduced optimized percpu variable access, which improves performance a little bit
added optimized AES and SHA1 routines
Optimized Adreno drivers, reverted back to stock ones
AND TONS MORE OF STUFF!!!!
DOWNLOAD LINK:
https://www.mediafire.com/folder/78e7p85s3fc9p/KERNELS​
Link for the source code:
GITHUB:
https://github.com/airidosas252/android_jellykernel_vee7

thanks for you work,i will definitely try this one.

This is definetly awesome news, I'd like to give a link from my rom to this kernel-can't implement it now, but I'd like to make new versions with your kernel, credits given. Great job, thank you!

Good thing I haven't posted this kernel yesterday. You would have gotten into a real mess: networking would stop working after some use of it.
It was a problem related to compilation. I've fixed it now and testing.
I will upload it to you a little bit later today. Sorry for waiting.
Sent from my LG-P710 using XDA Free mobile app

Please add swap support in next version of this kernel

Doing nandroid backup then im gonna test it,thanks. :good:

Ilyazzzz said:
Please add swap support in next version of this kernel
Click to expand...
Click to collapse
It is there.

i tested the kernel a couple of hours,maybe i made something wrong cause the phone was heating and everytime i exit an app i had redraws on the home screen,some apps just close after using them,without the warning of a FC,like testing the kernel with antutu qhen it reaches 80% the app just closes. And it made the phone slower.
When i made the backup restore i lost a few apps none of them are important,i can download them again.
I used no frills cpu with smartassH3 and vr,with the kernel in max OC and min UC values,and i did not touch the gpu frequency,because i dont know hot to do that.
So basically im not saying the kernel its bad,is that maybe i neded to use another app in order to have better perfomance
So,yes i need help or just point me into the right direction so i can search about it.
I've been using modified kernels,since xperia x10,but this its the first time i have these problems.
And thanks again for your work and effort.

As I mentioned in the thread, avoid using 500 MHz GPU clock. This is the most obvious thing, that makes phone unstable. Set it off using Trickster MOD.
Don't know, why mine is rock stable for like 3 days now (there is something wrong with deep sleep, though. I think different toolchain is responsible for such issue).
I even broke into 10000 (10420 points) mark in Antutu, so yeah... Definitely something's wrong on your phone.
With stock kernel my phone was very laggy, always redrawing no matter which launcher, stutter in almost every game (now even Hungry Shark doesn't lag anymore).
Sent from my LG-P710 using XDA Free mobile app

airidosas252 said:
As I mentioned in the thread, avoid using 500 MHz GPU clock. This is the most obvious thing, that makes phone unstable. Set it off using Trickster MOD.
Don't know, why mine is rock stable for like 3 days now (there is something wrong with deep sleep, though. I think different toolchain is responsible for such issue).
I even broke into 10000 (10420 points) mark in Antutu, so yeah... Definitely something's wrong on your phone.
With stock kernel my phone was very laggy, always redrawing no matter which launcher, stutter in almost every game (now even Hungry Shark doesn't lag anymore).
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response,but mate,as i mentioned ,i never touched the GPU frequencies.because i was using only no frills cpu in order to use the max oc and the min oc for the cpu.
I will check that app (trickster mod) asap, right now im at the work,also,if you can ,can you tell me your settings please?
And thanks again.

kalel29 said:
Thanks for the response,but mate,as i mentioned ,i never touched the GPU frequencies.because i was using only no frills cpu in order to use the max oc and the min oc for the cpu.
I will check that app (trickster mod) asap, right now im at the work,also,if you can ,can you tell me your settings please?
And thanks again.
Click to expand...
Click to collapse
Regarding GPU frequencies, it's the same deal as the CPU frequencies, although changing it could either improve performance or make it worse more drastically.
There's nothing so special about my settings: Using 1024 Kb of sd cache, sio i/o governor, smartassv2 cpu governor, leaving both cores online all the time (deleted mpdecision binary from /system/bin folder, because it's too poor for keeping optimal on and off switching of second CPU core). From OS side I've deleted every possible LG app (left nearly at AOSP level), disabled logcat (because I don't need such right now), using Class 10 microSD card, because it won't bottleneck the phone too much. So that's about it.

airidosas252 said:
Regarding GPU frequencies, it's the same deal as the CPU frequencies, although changing it could either improve performance or make it worse more drastically.
There's nothing so special about my settings: Using 1024 Kb of sd cache, sio i/o governor, smartassv2 cpu governor, leaving both cores online all the time (deleted mpdecision binary from /system/bin folder, because it's too poor for keeping optimal on and off switching of second CPU core). From OS side I've deleted every possible LG app (left nearly at AOSP level), disabled logcat (because I don't need such right now), using Class 10 microSD card, because it won't bottleneck the phone too much. So that's about it.
Click to expand...
Click to collapse
ok then,thanks i will try the same settings,also i have a 16gb,class 10 microsd card,and deleted all the lg apps that i dont use. :V
thanks for the reply.

Any possibility of USB OTG being implemented anytime soon?

CrashBandicootX said:
Any possibility of USB OTG being implemented anytime soon?
Click to expand...
Click to collapse
I don't know. It's in the same position as it was in Kitkat - drivers are included but it just doesn't work.
I'll try talking to other developers.

RAM
Hello! :cyclops:
Is there any form to optimize the RAM usage? Any application or something? Greenify works?

Im using v2,everything runs better,and its feels smoother,the only thing that i noticed is that i lost data in some apps,had to disable superSU,and Xposed,and open all the apps that requiere root,in order to regain access to the apps that use superSU again,and finally when im using antutu in order to see how is the perfomance it just closes when its about to finish the benchmark,always,besides that minor thing,the kernel its solid,im using no frills cpu with max freq in 1037mhz,min in 245 mhz, sioplus and smartassh3,(im not touching GPU freq),but every time i restart the phone,the values doesnt stay,y have to manually change the governor and scheduler.

Sorry dude,thanks for your effort but i think my phone doesnt like your kernel,i used trickstermod,no frills,set cpu,and the antutu one,and everytime y reboot the phone the kernel has the default settings again,min freq in 245,max freq in 1,036,and it returns also to ondemand and sio.
:/
I made a backup of my kernel,what partition do i need to restore in order to have the old kernel back?????
and again,thanks.
P.S. a friend is using same kernel in his phone,he is using stock firmware,odexed and im using a custom rom,deodexed. And its the same result in both phones.

@kalel29
To restore old kernel in CWN go to advanced restore and choose boot

sasa g said:
@kalel29
To restore old kernel in CWN go to advanced restore and choose boot
Click to expand...
Click to collapse
Yeah, now I'm encountered certain problems and I was testing backported Kitkat kernel for some time now.
That one is miles better than Jellybean's one (it is too buggy, because simply compiling breaks certain things)
Kitkat kernel, at least, puts phone to sleep state properly (now my phone stays cold throughout whole day, if I don't use it at all, while with Jelly Bean's one, it was always warm, sometimes even hot)
And yeah, sorry, who feels, that posted kernel causes some problems. It is addressed now and fixed.
I'm not an expert in C code, so some specific programming issues are unsolvable for me.
And the feedback is always welcome for me.

Related

[KERNEL][ExTweaks] SiyahKernel v2.6.14 - "One kernel to rule them all"

Although some parts can be considered as original, all are based on inspirations, examples and other people's code.
I have no claim to be original. I am only trying to make my (and probably other's) SGS2 experience better and fun.
I do this for fun. so, if you just want to argue with me please don't. use the energy coming from your youth in something useful.
SiyahKernel v2.6.14
FEATURES
Can be flashed on Samsung ROMs and AOSP Based ROMS. Currently all Samsung 2.3.4, 2.3.5, 2.3.6, 2.3.7 based ROMS, CM7 (CM9 or any other ICS based ROMs are not supported) and MIUI ROMS are supported.
Based on linux kernel 2.6.35.14 + drivers from Samsung sources
Auto-Rooting
CWM touch Recovery with gesture support
Custom boot animation support
Supports SetCPU (OC upto 1600MHz, UC downto 100MHz)
User customizable frequency steps. You can edit "freq_table" and use 25MHz as the lowest step and 1696MHz as the highest. You have 8 steps (it is fixed) but the frequencies can be set.
Supports undervolting (UV between 800 mV and 1500 mV)
Supports voltage control via SetCPU (thanks to netarchy, ninpo, hacre)
Stock voltages as default
smartassV2, lulzactiveV2 governors. and lots of other governors which are available as modules
Default governor is lulzactive (200-1200MHz)
Tweaked ondemand and conservative governors
no compiler optimization. it is just a myth.
Touchscreen fix (thanks to vitalij)
Increased touchscreen sensitivity
GPU clock (thanks to netarchy), voltage and scaling thresholds control interface.
I/O, scheduler, hotplug and vm tweaks
automatic battery calibration. (removed. thanks to Entropy512. we do not need battery calibration for SGS2)
Available I/O schedulers: noop, deadline, CFQ, BFQV3r2(default), V(R), SIO
Available CPU governors: see this thread for the list of available governors and modules (thanks to droidphile)
/system/etc/init.d startup scripts support
Automatic backup of efs partition. You will have the files in your sdcard as well as /data/.siyah directory. copy them to a safe location in case you may need them later.
BLN (thanks to creams), liblights is autoinstalled if the existing one doesn't support BLN
supports advanced touch tune driver. thanks to vitalij Link. the control app from Web, from Mobile. Thanks to tegrak for the driver patch file download
2nd core application support (thanks to tegrak)
Automounting of NTFS volumes for USB sticks (ntfs on external card is not supported). although your rom says "clear storage", just check /mnt/usb folder. ntfs drives will be automatically mounted in read-only mode.
LZOP compression for the kernel to have very fast decompression. We have a VERY BIG kernel image because we have ntfs-3g, CWMManager and lots of other things both in initramfs and payload.
Integrated new&faster sha-1, crc32 slice-by-8, crc32c, jhash and rwsem algorithms
SCHED_MC enabled to have less power consumption.
Lower brightness levels for low-light conditions to save battery.
Brightness behaviour modification via setting min_bl, min_gamma and max_gamma values. you can control the lowest and hightest levels used in autobrightness.
Native BLN support for CM7 based roms.
Three GPU stepping (160-267-300) instead of two
optimized and configurable hotplug thresholds and rates.
Thunderbolt! script integrated (thanks to pikachu01)
Voodoo louder app support (thanks to supercurio)
Current Widget support while charging the device.
ExTweaks (uci.sh) support. (Thanks to xan and AndreiLux) ( https://market.android.com/details?id=com.darekxan.extweaks.app )
CIFS, SLUB, FUSE, NTFS, cgroup_timer_slack,... and lots of other mambojambo that I forgot...
Download link: http://www.gokhanmoral.com/
FLASHING GUIDE
TO FLASH TAR:
If you already have root, use DarkyOTA app from the market ( https://market.android.com/details?id=com.ficeto.darkyromota ) .
If not, use ODIN.
TO FLASH ZIP:
Use CWM Recovery and install zip file. Wiping cache&dalvik cache is recommended for those who use BLN.
if you lose root after flashing the kernel (unlikely), flash http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip in CWM.
Some Example Init.d Scripts
Example CWM-flashable /system/etc/init.d/99gpuv script (thanks to AndreiLux)
Example GPU/CPU undervolting and underclocking scripts by kwerdenker
Improved version of CPU undervolting script by kwerdenker
Another couple of nice init.d scripts created by fenomeno83
flashable lionheart cpu governor and setting default i/o scheduler to deadline (remove /system/etc/init.d/01lionheart to uninstall. thanks to knzo for the tweaked conservative governor settings)
releases can be found here: http://www.gokhanmoral.com/
source code repository: http://bitbucket.org/gokhanmoral/siyahkernel
CHANGELOG
see http://www.gokhanmoral.com/ for the changelog.
TODO
more and more optimizations for less battery drain
ICS edition when samsung releases new kernel sources
stable wifi driver which doesn't cause a lot of wakelocks with proper offloading
BLN notifications without wakelocks
OTA application (just to prevent users downloading wrong kernel for their device. other than that, it will be useless for a kernel)
THANKS:
Samsung, supercurio, hardcore, Hacre, RAvenGEr, tegrak, cattleprod, codeworkx, hellcat, creams, vitalij, arighi and others I might have forgotten...
{
"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"
}
Who Should NOT Use This Kernel?
If you are going to use very low voltage settings and complain about having lockups, you SHOULD NEVER use this kernel... just run away! This kernel is just as stable as the stock kernel if you do not modify any settings. Do not blame the kernel if you change the voltage or clock settings. If you do so I will blame your stupidity. I will not remove any feature just because some dumb users select wrong settings. If you are a rookie with an uncontrollable instinct of modifying advanced settings please use speedmod or stock kernel.
This kernel generally contain some experimental code and some of them may be even undocumented. I have different release strategy. I always use the latest version and if I notice any problem I try to fix it. However, I do not use all the features of the phone. So, if you notice any problem please report it. bug reports are welcomed, whining is not.
If you judge a kernel by quadrant score, please, I beg you, don't use this kernel. I don't have enough time nor motivation to answer your questions... Some people got 8000+ quadrant (search the thread) and there is no way you can beat them anyway.. so, go away...
If you are one of those who judges a kernel while sleeping ("oh my god!! lost %1 during sleep"-guy) please use another kernel, sleep and never wake up. it will maximize your battery and minimize the tension in the thread.
If you still believe in battery calibration, discuss it in some thread else. we respect all religions but missionary acts are not welcomed in this thread.
99.9% of the code belong to others. I have some modifications and/or additions to the kernel as C code or scripts but they are so little compared to the original code base. If you think you are better developer than I am, don't waste your time (and mine) as I accept it beforehand so please just go away.
FAQ
Q: Does this kernel support Samsung's ICS leak, CM9 or any ICS edition?
A: No, it does not.
Q: Does this kernel support latest Samsung i9100 ROM?
A: Yes, it does. Unless otherwise stated, you can use this kernel on latest Samsung ROMs (official and leaks). it is tested on 2.3.4, 2.3.5, 2.3.6.
Q: Can I use this kernel on I9100G?
A: No, you cannot. Only european i9100 models are supported. Also, I compile ntt-docomo version for each release but beta versions do not support gps and digital tv on ntt-docomo devices.
Q: Does this kernel support CM7 or any other AOSP based roms?
A: Yes, but it only support cm7 or miui based roms for now. If you are using another aosp based Rom tell me and I will support it.
Q: Can I use app protectors with this kernel?
A: Yes, you can. Android logger is enabled by default.
Q: Some custom lockscreens or protectors do not work with this kernel. Can you fix it?
A: see the question above.
Q: What is smartassV2 governor?
A: It is a governor to control CPU frequency. This governor has a built-in "profile" similar to SetCPU but the profile has no upper frequency limit. It tends to stay on lower frequencies when the screen is off and scale up very slowly, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Q: What is the best UV settings?
A: There is nothing as best UV settings. You have to find the best settings for your device for yourself. Start by decreasing 25mV on each freq and decrease it every day until your device becomes unstable.
Q: What can I do to have the best battery life ever?
A: put your phone into airplane mode. if you don't like to do it read the guide below.
Q: Which roms are supported?
A: All android 2.3.4 and 2.3.5 roms are supported. Try the latest version. if you have any problems leave a post to this forum and ask for help.
Q: I get random reboots or freezes. What should I do?
A: Before reporting any problems you have to make sure that you are using stock voltage values. Some phones cannot handle undervolting. Secondly, you have to give details. When did it happen, which rom are you using, can you reproduce it, do you have any custom init scripts which changes kernel parameters such as freq voltage or anything else?
Q: do I need to recalibrate the battery?
A: You don't need to calibrate battery for SGS2. Thanks to Entropy512 to pointing out that our device uses MAX17042 which is specifically designed not to require calibration.
Q: do I need to perform any wipe?
A: no. you don't have to wipe anything. however, try wiping cache and dalvik cache if you have any force closes or any other issues before reporting the issue.
Q: Is the battery life better/worse?
A: maybe... you'll never know if you don't try... People are reporting that they are having the best battery but it may not be the case for your device.
Q: where is the interface to change GPU clock and voltage?
A: There is no GUI (graphical user interface). the interface is used via device files. you have to use init.d scripts to adjust the values. there are some examples in the first post about how to use init.d scripts and gpu voltage/clock interface.
Q: Which governor is the best? Which I/O scheduler is the best?
A: You have to try them and select the one you like. There is a very good explanation about governors and i/o schedulers here: http://forum.xda-developers.com/showthread.php?t=1242323
Q: My phone doesn't go into deep sleep mode. Why?
A: try to clear cache and dalvik cache by using CWM recovery and make sure that your phone is not connected to a charger. it does not go into deep sleep when it is charging.
Q: Which version is the best?
A: supposedly, the latest version is the best. But if the latest version is beta there may be unstable code in it. testing the beta version and reporting bugs will help me. but it's your choice... try and see... maybe this kernel is not stable for your device at all, who knows... I will not answer any "what is the best?" questions and I kindly ask you not to ask that kind of questions since there is no answer to that.
Q: How does the automatic battery calibration work?
A: Automatic battery calibration feature is removed as it was useless for SGS2.
Q: What is an init.d script?
A:init.d scripts are the scripts which are executed during the boot time. actually, they are meant to initialize and deinitialize system daemons and manage some startup/shutdown tasks. but in android world they are just "autoexec.bat"s. so, it is a mix of rc.d and init.d directories in linux distros. everything in /system/etc/init.d are executed during the booting process. since it is not standard in every android device,some developers choose to execute files starting with "S" and some execute everything. in this kernel, everything in /system/etc/init.d is executed. you can create a script to change, lets say, voltages, schedulers, apply tweaks, run overclocking daemon or run anything else you can imagine.
Q: My phone doesn't go into deep sleep. What is wrong?
A: Make sure that you have cleared cache and dalvik-cache after you install the kernel. Also, reboot once more after the flashing. the phone doesn't go into deep sleep if it is connected to a charger or to a computer. There may be an application running in the background which is preventing deep sleep. In that case you can check which app causing the problem with "BetterBatteryStats" application (search in Google).
Q: I want more info about CPU governors.
A: There is a great post about cpu governors (thanks to droidphile): http://forum.xda-developers.com/showpost.php?p=19339524&postcount=10023
If you still want more info, try them by yourself.
Q: Can I use this kernel with I9100T?
A: Yes, you can. the only difference between I9100 and I9100T is that they have different SAR values.
quick and dirty guide to have less battery drain:
- use 2G-only if you don't need 3G
- monitor programs which cause wake-lock. use betterbatterystats and either uninstall or tweak them
- do not use task killers. see the previous item and find the malicious programs instead of repeatedly killing them.
- do not activate google latitude on maps.
- if you don't need pushmail, uncheck gmail sync and use k-9 mail to pull mail, lets say, every 1 hour or so.
- go to settings / location and security. disable "use wireless networks" and "use gps satellites". enable them when you need them, other than that keep them disabled.
- disabling auto-brightness and using a low brightness level helps. do you know that you can adjust the brightness by swiping your finger across the notification bar? try it...
- using juicedefender may help, but it may also cause more drain. test it yourself.
- if you need more speed than 2.5G (i.e. edge) disable HSDPA (*#301279#, select 2 then select 1). you will have 3G instead of H(SDPA) and I think it is fast enough
- disable fast dormancy. dial *#9900# and disable.
- disable auto sign in for google talk (search for talk in appdrawer and use settings to disable automatic sign in)
- disable samsung update and don't use samsung gadgets if you are not in love with them. (this part may be taken care of the rom developers)
- try several radios. I recommend you to try KE7, KG2 and KH3 and choose the one which suits you best. KG2 seems to be the best for me. however, in terms of battery life, there is not much difference between those three.
- be aware that more you use your phone more the battery drains don't complain like "my battery drains quite fast but I did not use my phone. I only played angry birds for hours without making a single call" or don't expect to have a decent battery life if you use your phone as a computer or download torrents using your phone.
i think i will wait 4 feedback because it's based on u2 source.
But good job anyway
cheers
Just flashed this on checkrom. Lost my haptic feedback and wifi.
Sent from my GT-I9100 using Tapatalk
sileshn said:
Just flashed this on checkrom. Lost my haptic feedback and wifi.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I've just noticed that I haven't uploaded the version that I am using. sorry for that. I will recompile and upload again.
gokhanmoral said:
I've just noticed that I haven't uploaded the version that I am using. sorry for that. I will recompile and upload again.
Click to expand...
Click to collapse
Take your time and post the sources as well, else this thread will get locked pretty quick.
Sent from my GT-I9100 using Tapatalk
Tebrikler dostum.. Great work..
sileshn said:
Take your time and post the sources as well, else this thread will get locked pretty quick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
yes, I know that is why I have asked for patience in OP. If the moderators were a bit more patient maybe I would be using some other kernel and wouldn't bother to compile my own
I've uploaded the recompiled kernel. enjoy.
Salam!
Any benchmarks results sir?
Sent from my GT-I9100 using Tapatalk
sileshn said:
sileshn
Click to expand...
Click to collapse
Thank you sir
Sent from my GT-I9100 using Tapatalk
So~ Any battery life improvement using this kernel sileshn?
Desperate for battery saving stuff for my lovely S2~
03188lee said:
So~ Any battery life improvement using this kernel sileshn?
Desperate for battery saving stuff for my lovely S2~
Click to expand...
Click to collapse
you have to try.
smartassv2 governor with 200-1200mhz setting is very satisfying and the battery lasts at least as long as speedmod-v27 for me.
bfq scheduler maybe
..........will u add it in the next release?
CFQ scheduler really drain too much power.....
Sick Enough To Die said:
bfq scheduler maybe
..........will u add it in the next release?
CFQ scheduler really drain too much power.....
Click to expand...
Click to collapse
I have already added. testing now..
power drain change is not noticable though.
Did you get better battery life than REGEmod-U1?
gokhanmoral said:
you have to try.
smartassv2 governor with 200-1200mhz setting is very satisfying and the battery lasts at least as long as speedmod-v27 for me.
Click to expand...
Click to collapse
chonshon said:
Did you get better battery life than REGEmod-U1?
Click to expand...
Click to collapse
I haven't tested it, but theoretically smartassv2 governor that I am using in the kernel should give better battery life than ondemand with a little (not even noticable) sacrifice of performance. you don't need to use any setcpu profiles with smartass governors.
test it. it may or may not give better battery life for you.
I will. Thank you.
gokhanmoral said:
I haven't tested it, but theoretically smartassv2 governor that I am using in the kernel should give better battery life than ondemand with a little (not even noticable) sacrifice of performance. you don't need to use any setcpu profiles with smartass governors.
test it. it may or may not give better battery life for you.
Click to expand...
Click to collapse
great work

[KERNEL][JetStream] DooMKernel [Rel:v01][Dt:04/Jan]

hello everyone,
i present to u the first custom kernel for the HTC JetStream!
i have developed kernels for Xperia X10, Xperia ARC, Xperia PLAY, Huawei Ideos X6, Samsung Galaxy SL, Kindle Fire, HTC Flyer and now i bring u my kernel for HTC JetStream!!! this is my first kernel for a MSM8x60 (Snapdragon S3 device)..
i dont have this device with me and so it was a pain getting this kernel working without device in hand but thanks to the testers it was possible!!!
special thanks to: bmw-boy, nmyseteroious & Russ741 for testing it out on their tablets!
[ disclaimer ]
OVERCLOCKING CAN BE DANGEROUS! U RISK THE HARDWARE GETTING DAMAGED!
PROCEED WITH CAUTION!
U HAVE BEEN WARNED!
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
[ features ]
CPU overclocked to 2.052 Ghz
CPU underclocked to 192 Mhz
GPU overclocked to 320 Mhz
for safe booting CPU is capped at bootup to 1.536GHz/384MHz (max/min)
slightly undervolted (atleast for stock frequencies)
uses LZMA compression
added lots of fixing/patches (including CPU HOTPLUG notifications/CPU unaligned access) thanks to faux132
VDD CPU voltage control (@ /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels)
compiled using Snapdragon optimizations
PERFLOCK disabled
SWAP enabled
enabled few file systems support:
NTFS
NFS
CIFS
insecure kernel (ro.secure=0 & USB debugging enabled by default)
/system mounted as RW
[ credits for features ]
most of the stuff in this kernel is based on the work by faux132 and showp1984 on their HTC Sensation kernel!
thank you all for ur work!
[ requirements ]
stock HTC JetStream ROM (or ROMs based on it)
bootloader unlocked
working recovery
android app for overclocking like SetCPU (paid) or NoFrills CPU Control (free)
VDD control app: IncrediControl
[OPTIONAL] CIFS Manager (free)
[OPTIONAL] Swapper 2 (free)
[ how to install my kernel ]
download the provided kernel image & wifi module (zip file)
save the wifi module (zip file) to external sdcard
reboot device into fastboot mode (adb reboot bootloader)
flash my kernel using (fastboot flash boot kernelname.img)
reboot device (fastboot reboot)
enter recovery (adb reboot recovery)
flash the wifi module (zip file) via recovery (install zip from sdcard)
reboot phone and enjoy the kernel
FOR OVERCLOCKING
start SetCPU/NoFrills CPU Control app on ur device (or any other app which supports overclocking) (u may get a popup asking for SuperUser permissions, click ok/yes/allow)
now slowly increase the MAX slider to the right (one notch at a time) to increase the maximum frequency limit
DO NOT JUMP TO THE LAST POSSIBLE FREQUENCY
SLOWLY increase the frequency one notch at a time and do stability/testing for few hours
during testing never set "SET ON BOOT" option of these apps... u might get stuck in bootloops...
[ my kernel sources ]
https://github.com/DooMLoRD/HTC-JetStream-HC-Kernel
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ downloads ]
[JetStream] DooMKernel v01 (mirror)
MD5HASH: dc8093f0b349f14580515e52be7f1fff
Wifi Module (mirror)
{
"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"
}
ENJOY!!!
reserved for later
what's the wifi module?
and also, i have no intention of OCing or UCing..will this kernel make a difference for me?
guru_shastri said:
what's the wifi module?
and also, i have no intention of OCing or UCing..will this kernel make a difference for me?
Click to expand...
Click to collapse
custom kernels need the corresponding wifi module for wifi to work correctly... else u will get error...
if u are not planning to OC then dont worry... the kernel will always boot at 384mhz/1536Mhz (similar to stock speeds)... so if u dont overclock using apps then kernel will never be run at those high clocks
though u might be interested in undervolting... CPU Voltage control interface is provided!!!
Interesting.
I have flashed many roms and mods but never delved into kernels much.
I don't plan on OC or UC either. Saying that, is SetCPU and VDD Control app still required to use the kernel for proper control?
I'm sorry if I ask basic questions. Like I said, not dealt with Kernels much before.
So what's the next to make our tablet flying
will it make the tablet quicker? without OCing that is...
and if something goes wrong - are the kernels at bmw-boy the stock ones? in case i'd need them
and i think all that is left is a proper ROM.
and than - just waiting for ICS.
I"m unsure if this is related to this kernel, but... after flashing, when i switch from Disk drive to charge only the jetstream freezes for quite a long while. Does anyone else experience this?
UC/OC
I have seen several posts making statements about "I have no intention to overclock...." etc. Why? One of the great benefits of using a custom Kernel/ROM is the ability to over/under clock the device (JetStream or whatever). Do you drive your car at exactly 45MPH and 2500RPM everywhere you go and park it on a treadmill at night so it can continue to turn the tires at 45MPH and 2500RPM? No you drive slow when needed and fast when needed. When you come to a traffic light you car idles and uses less fuel. This is what UC/OC is about. By using a dynamic CPU control (SetCPU or NoFrills) the CPU clock will increase/decrease as needed. SAVING you battery and giving you a performance boost when needed. Can you damage your processor? Sure you can, but you can damage it just as much by dropping it on the floor. Set the CPU controls properly (DooMLord tells you how above) and you wont have any negative affects. I have been UC/OC my several devices for years.
I tested this Kernel and have it running flat out at 2+GHz with no issues.
Enjoy the battery life extension, the better usability and DooMLord's hard work. He was up till about 5am his time yesterday testing.
Just my 2C.
Russ741
Russ741 said:
I have seen several posts making statements about "I have no intention to overclock...." etc. Why? One of the great benefits of using a custom Kernel/ROM is the ability to over/under clock the device (JetStream or whatever). Do you drive your car at exactly 45MPH and 2500RPM everywhere you go and park it on a treadmill at night so it can continue to turn the tires at 45MPH and 2500RPM? No you drive slow when needed and fast when needed. When you come to a traffic light you car idles and uses less fuel. This is what UC/OC is about. By using a dynamic CPU control (SetCPU or NoFrills) the CPU clock will increase/decrease as needed. SAVING you battery and giving you a performance boost when needed. Can you damage your processor? Sure you can, but you can damage it just as much by dropping it on the floor. Set the CPU controls properly (DooMLord tells you how above) and you wont have any negative affects. I have been UC/OC my several devices for years.
I tested this Kernel and have it running flat out at 2+GHz with no issues.
Enjoy the battery life extension, the better usability and DooMLord's hard work. He was up till about 5am his time yesterday testing.
Just my 2C.
Russ741
Click to expand...
Click to collapse
I actually take back what I said!
I am clocked at about 500/1800 min/max.
Though after I reboot, SetCPU forcecloses two or three times without me even opening the app. (And it is not set to boot)
I see this as an opportunity to learn more about kernels and UC/OC. I appreciate all of Doom's efforts and am happy to donate to him for it!
its not personal, and i have great appretiation for the work Doomlord put in it.
and i will flash it as soon as i could.
that being sayd, i don't think OC a device is a good thing. i'm happy with what i get right now, and i think there's a reason the CPU is clocked the way it is.
i've tried OCing in some of my past devices and never felt the difference besides having another app grinding my memory.
that's my opinion for now. it might change someday..
guru_shastri said:
its not personal, and i have great appretiation for the work Doomlord put in it.
and i will flash it as soon as i could.
that being sayd, i don't think OC a device is a good thing. i'm happy with what i get right now, and i think there's a reason the CPU is clocked the way it is.
i've tried OCing in some of my past devices and never felt the difference besides having another app grinding my memory.
that's my opinion for now. it might change someday..
Click to expand...
Click to collapse
as i told u earlier:
>>>
the kernel will always boot at 384mhz/1536Mhz (similar to stock speeds)... so if u dont overclock using apps then kernel will never be run at those high clocks
<<<
flashed it. everything seems fine so far...
let's see how it goes for the upcoming days.
should anything happen and i'd like to restore he original kernel - is it posted here somewhere? maybe it should be?
Battery Life
@DoomLord
Question, just by having the Kernel will I have a better battery life or should I do some configurations?
Thanks
sikorski said:
@DoomLord
Question, just by having the Kernel will I have a better battery life or should I do some configurations?
Thanks
Click to expand...
Click to collapse
There are already some optimizations to improve battery life... I will tell u later how to undervolt further to get even better battery life..
Sent from my HTC Flyer P510e using XDA App
EXCELLENT kernel!
prolly one of the best kernels I've EVER flashed and used with regard to battery life, speed, stability, etc. been runnin this kernel since it's first moment of release at 192mhz min/2.05ghz max/ondemand... absolutely NO crashes, NO reboots, NO heating issues (matter fact it runs cooler than stock pre rooting!). VERY GOOD job!!!! can/will u help us out in the Rezound community as well??
when I open the incredicontrol app, the app says that I need a Rom that supports the apps configuration methods.... ?
since i dont have the device with me i cant test but the CPU voltage VDD control interface will provide u with following features:
get the current CPU frequency/voltage table
Code:
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
lower voltages for all frequencies
e.g.: lower voltage by 25mV
Code:
echo '-25000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
increase voltages for all frequencies
e.g.: increase voltage by 25mV
Code:
echo '+25000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
specify voltages for a particular frequency
e.g.: say u want to set voltage for 1536 MHz frequency to 1225 mV then:
Code:
echo '1536000 1225000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
here is a useful app:
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
may be someone can test it?
the current frequency/voltage table is as follows:
https://github.com/DooMLoRD/HTC-Jet...ernel/arch/arm/mach-msm/acpuclock-8x60.c#L220
all this can be made into simple init.d script
i will later post a update.zip to enable init.d support...
After flashing kernel and opening incredicontrol, this is what I get.
Advice?
Should I reflash the kernel? It flashed properly...
i reflashed. Still the same error message...?

[SCRIPTS][TWEAKS] Init.Doh | Battery & Performance | 0.4.6b | 3/16/12

{
"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"
}
Credits: Pikachu01, geko95gek, crypted, droidphile, User Feedback​​Features:
Pikachu01's ThunderBolt! scripts (v2.6.1). (Also extracts the bolt_scripts onto the SDCARD)
80MB LMK Tweaks (v6 SuperCharger Memory Tweaks)
Crypted's GPS.conf for Quick Fixes
Ad Blocking Hosts file (5 of the best merged together)
Undervolted - Safe -50mV on most
Easy to tweak with ExTweaks
GPU Rendered UI Enabled
AFTR enabled, Sched_mc disabled. Siyah logger disabled. Custom Brightness, Touch Sensitivity Parameters, Static Bus Frequencies, Custom Deepsleep Levels, Dynamic hotplug, Logging disabled, Phone / Memory / SDCard / WIFI/3G/4G Tweaks, Hot Plug Thresholds, Sampling Interval & Frequency, Gtalk Wifi Only = False.
CPU set to: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Battery Version:
In this version you will be sacrificing some cpu & gpu performance for a decent amount of battery. Hotplugging checks at a slower rate for battery, Ondemand is tweaked for battery instead of speed. Minimum brightness levels are set lower, our #1 Battery Drainer.
100-1000Mhz
Ondemand/sio
GPU set to: 100/160/200Mhz | 800/850/900mV
Hotplug/Governor Tweaked for Battery
Performance Version:
This version you should be noticing a difference in benchmarks/responsiveness. The battery drain should be a little more than stock because of the overclocking. Hotplugging is set to Siyah Defaults, and lulzactive is tweaked for performance/battery.
100-1400Mhz
lulzactive/sio
GPU set to: 100/200/400Mhz | 800/900/1150mV
Hotplug/Governor Mostly at Stock/ThunderBolt!
Requirements:
Most of the Features will not work in ICS - Backup First
SiyahKernel v2.6.13+
ExTweaks Installed - If you wish to tweak init.doh
Files installed:
/system/etc/init.d/
S01logger - Disables Android Logging
S02sysctl
S70darky_zipalign - Zipalign
S91SuperCharger - Memory Tweaks
S98CFS - ThunderBolt! Kernel Tweaks
S98system_tweak - Most ThunderBolt! Tweaks
S92init_doh - CPU/Misc Tweaks
/system/etc/
gps.conf - GPS Tweaks
hosts - AdBlocking
SuperChargerAdj - LMK Memory Tweaks
SuperChargerMinfree - LMK Memory Tweaks
SuplRootCert - GPS Cert.
/system/
default.prop - LMK Memory Tweaks
/data/.siyah/
default.profile - Most of CPU/GPU Tweaks (ExTweak Profile)
Init.d scripts deleted each install:
Files Listed Above (Overwritten)
S98gekoh
s91voltctrl
Installation:
Download the latest zip below
Do a Backup in Recovery Mode
Flash Init.Doh in CWM (Recovery)
Reboot
The following steps are not required
If you now have 2 zipaligns scripts, please delete one of them (Keeping the one listed above)
Download Script Manager
Open Script Manager, Scroll down to the "bolt_scripts" on your sdcard
Open "sqlite_optimize", press the Skull/Bones icon "Su" and "Save"
Press Run, this will take a minute or two. Ignore the Errors.
It is finished when you see "Exit code 0", Click Close.
Run this script once once in a while (Whenever you have installed a few apps)
Updating/Changing Version: Just flash the latest zip and all the files are overwritten.
Uninstall: Download the file (uninstall_doh.zip) and flash it in CWM.
Note:
If you have any issues, try clearing your cache/dalvik
Give this script some time to work. At least one full batteries worth.
Some people give up after one SoD, just adjust the voltages up a little. Could also be kernel related (Read your kernels thread for latest issues)
This script changes at least once a week, so let me know if you run into any issues.
General Battery Saving Tips: - Thanks AndroidGX
Never use Tasks killer things or related.
Settings > Display > Touch key light duration : "OFF"
Settings > Display > Auto adjust screen power : [TICK]
Settings > Applications > Samsung Apps > "OFF"
Settings > Privacy > Back up my data > [UNTICK]
Settings > Location and security > Use wireless networks : [UNTICK]
Settings > Wireless and network > Wi-Fi settings > (press Menu button) > Advanced > Wi-Fi sleep policy > "Never" or "When screen turns off"
Deactivate auto sync for accounts
Deactivate GPS (and wifi gps)
Set brightness level to automatic/low
Disable motion
Changelog:
v0.4.6b: Upped Hotplugging a little. Disabled Static Bus. Changed back/updated to Crypted GPS v3.1 No-SSL. Smooth Scaling Enabled 2/2/2. GPU Thresholds changed to 90/50/90/50. Wifi/Phone Experiments added to bottom of S92init_doh. Should be a faster release without hopefully any additional battery drain.
[*]v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.
[*]v0.4.4b: Changed freq_cpu1on to 800Mhz. Changed GPS Quick Fix to H3llstorm's. Updated Ad Blocking Hosts file. Uncommented Wifi/Phone Experiments in s92init_doh.
[*]v0.4.3: 2.6.13 Siyah Required. Moved most of the tweaks in init_doh to default.profile for the new 2.6.13 SiyahKernel. This will allow you to edit most of this in ExTweaks app. Added 80MB LMK v6 SuperCharger memory tweaks by zepp & Pika. Cleaned out most commented lines in system_tweak, and a couple AOSP issues. Updated ThunderBolt! scripts. Changed hotplug values / GPU steps for hopefully better battery. Changed scheduler to SIO. Choosing a lower minimum brightness for better battery. Commented out Experimental Tweaks in init_doh script.
[*]v0.4.2b: Few build.prop tweaks again, these from ICScrewD. You will see them at the bottom of init_doh under "Latest Experiments". Could cause AOSP issues. Also extracting bolt_scripts to both /emmc/ and /sdcard/, hopefully fixing some peoples complaints about it missing. Overall, just a small update.
[*]v0.4.1b: Deep Sleep Freq set back to 100-800 @ 400mhz bus. If .4.0 is working fine for you, no need to update.
[*]v0.4.0b: Deep Sleep Freq set to 100-500Mhz and bus @ 133Mhz (This could cause SoD's, let me know). Set Governor to Ondemand (Good Battery Life with Moderate Use), tweaked ondemand towards Battery Saving. Fixed 100Mhz mV to 925 (Instead of 920). Changed GPS fix to Crypted's patch (experiment). Back to 3 step GPU (100/160/[email protected]/850/900mV). 1000Mhz bus set back to 266Mhz.
Q: Where is my init.d folder? A: On your main storage. "/system/etc/init.d/". Find it with File Manager
Q: I want to change stuff like voltages/governor, but how? A: Browse to the init.d folder, open s99init_doh with a text editor such as Jota Text Editor. Trial and error from here.
Q: Cool story bro, but I can't edit/save the file. Wth? A: Calm down. The directory is read only. In file manager go to the directory, then open your menu -> more -> settings, scroll to the bottom and check root and mount. When u are finished, unchecked those two.
Q: How do I boot into recovery (CWM) mode? A: Through your power menu, through the CWM app on your phone, or: With the phone off, Vol-Up,Vol-Down, Power Button - Hold down at same time till your in recovery
Q: I tried hitting my power button recently, but the screen never came on (SOD). Whats up? A: Hard to say exactly, but lets start pumping the CPU voltages up. 25mV at a time. If it continues even at stock voltages, long-press power to reset the phone and then pull /proc/last_kmsg and let me know!​A lot of people can push their voltages lower, I can too. Trying to make this script universal for us siyah people. Don't be afraid to increase/decrease your CPU voltages 25mV at a time, never go higher than stock in my opinion.
Undervolting is pretty much a placebo with your screen on. At most people save is 5% more battery with extreme undervolting. If you get one reboot, you may have drained more power than you have saved. If you want to save battery, turn your brightness low and choose a governor that stays away from the max freq the most. Your phone will also save a little more juice if you can handle 100Mhz as lowest state.
Stock CPU Voltages: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Stock GPU Voltages: [email protected] [email protected]
Backup your init.d folder if you want to be safe, this will overwrite all the files listed above. Also if you have a voltage control service, odds are that this won't work (at least the cpu/gpu/voltage tweaks).​Go give thanks to: (Click on their names below)
Pikachu01 - 99% of the scripts
geko95gek - CPU/GPU/Voltage Settings, Tons of user feedback
Armisael - Misc Tweaks, User Feedback
stevehkim - Misc Tweaks, User Feedback
GadgetCheck - CheckROM, Misc Tweaks
droidphile - Amazing reference/guide
bedalus - Another Amazing Reference
crypted - GPS Quick Fix
H3llstorm - GPS Quick Fix
I9100 & SGH-I777 Community
To anyone I forgot: Thank you for all your hard work​SiyahKernel Only: Download: Battery 0.4.6b | Performance 0.4.3p​
Does it work on ICS?
Konstantinos said:
Does it work on ICS?
Click to expand...
Click to collapse
Doubt it. Parts of it would, so you could dissect certain things like the gps/hosts file. Thanks for bringing that up though, I have to remember you i9100 folks are currently in love with ICS. Us i777 have it way to buggy.
Update: I will check back later today to see if anyone has any issues.
love the name
Lets try it. Thanks!
Will give feedback after a day or so. Installed battery version
Sent from my GT-I9100 using xda premium
No harm in having something new to play with i guess. Great thread mate.
Just installed the performance version and it's working great coupled with Checkrom and Siyah. Thanks!
EDIT: Hmm, my SGS2 seems to be having issues with the three GPU frequency steps, as ShadowGun isn't running smooth anymore.
Toss3 said:
Just installed the performance version and it's working great coupled with Checkrom and Siyah. Thanks!
EDIT: Hmm, my SGS2 seems to be having issues with the three GPU frequency steps, as ShadowGun isn't running smooth anymore.
Click to expand...
Click to collapse
This is where I need your help. If you could, go into ExTweaks. In the gpu tab could you increase the first step to 160 2nd to 267. First step mV 850. 950mV for 2nd. Let me know how that runs.
cwc3 said:
This is where I need your help. If you could, go into ExTweaks. In the gpu tab could you increase the first step to 160 2nd to 267. First step mV 850. 950mV for 2nd. Let me know how that runs.
Click to expand...
Click to collapse
Tried changing the settings, but it seems it wasn't related to the settings of your script, but the kernel. Running stock now and everything is working as it should. Would definitely recommend this script for anyone wanting a little boost in performance!
Just checking in. Curious if anyone has any issues/recommendations. This script has over 1500 installs since last month in the i777 community. I am looking for ways to improve it, and your feedback is much appreciated.
Thanks again folks.
will try soon, after reflashing back to 100% stock KI4 on my S2
and this thread has the best appearance that i've ever seen on xda, really
Hi cwc3,
After recharge and your scripts it last 22 hours before my battery is empty with normal use.
It runs very smooth, where I expected some lags as its the battery version.
I have the feeling longer usage is possible if the voltage is set a bit lower. What do you think?
Sent from my GT-I9100 using xda premium
Checkrom v6
kart_man_21 said:
Hi cwc3,
After recharge and your scripts it last 22 hours before my battery is empty with normal use.
It runs very smooth, where I expected some lags as its the battery version.
I have the feeling longer usage is possible if the voltage is set a bit lower. What do you think?
Sent from my GT-I9100 using xda premium
Checkrom v6
Click to expand...
Click to collapse
Worth a try. I'm my tests, lowering voltages was more of a placebo. The voltages are found in the s92initdoh init.d script.
Did you notice any increase in battery? Typically you should notice a little lag when switching between things. The main battery saving from this script is going to be from the underclocking on both CPU and gpu.
Anyways, thanks a bunch for the feedback.
Hi,
I noticed big difference compared to stock, as that would empty my battery within 18 hours.
Sent from my GT-I9100 using xda premium
kart_man_21 said:
Hi,
I noticed big difference compared to stock, as that would empty my battery within 18 hours.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Glad to hear! I know I'm not thank button shy, but I also appreciate the feedback. If choose to continue using the script, be sure to let me know how things are going. Thanks kart man.
New Update
v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.​
Still experimenting with these values based off of peoples feedback/droidphile's thread. Be sure to let me know if you run into any issues, always looking for feedback.
cwc3 said:
v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.​
Still experimenting with these values based off of peoples feedback/droidphile's thread. Be sure to let me know if you run into any issues, always looking for feedback.
Click to expand...
Click to collapse
Mate nice to see this in the original android development thread..great stuff and some great tweaks you have going here..if there is anything i can do to help out feel free to PM me my friend.
Great job again..we should get this lot working for cm9 which i am currently using
Hi mate. Just flashed this, will give u feedback very soon. But so far after 2 hours its sweet! . Using the battery version.
Sent from my GT-I9100 using xda premium
I'm very Curious to try this on my ICS SGSII... lol is this working on ICS?
_____________________
Sent From OFFICIAL CM9 BUILD using SAMSUNG GALAXY S II
sam razzy said:
I'm very Curious to try this on my ICS SGSII... lol is this working on ICS?
_____________________
Sent From OFFICIAL CM9 BUILD using SAMSUNG GALAXY S II
Click to expand...
Click to collapse
Some of the features. Could you possibly backup and let me know? I can't touch ics for a few more days, and owning a sgh-i777 doesn't help either.

[KERNEL][CWM] TerraSilent 1.3.5 for Galaxy 4.0 (YP-G1) INTL & USA (22/06/2012)

TerraSilent 1.3.5
{
"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"
}
After a lot of testing I can release it
Well sorry for the /data partition, I don't know why, but it's stuck at RFS. I format it, I tried everything, everytime you relaunch the recovery and try to mount the partition, it mount it as RFS and wipe it out.
I advice you to let it as RFS or, change it to ext4 when you are sure you won't need to do further change in it from the recovery.
Click to expand...
Click to collapse
THIS IS ONLY FOR THE INTL AND USA VERSION OF THE GALAXY PLAYER 4.0 (YP-G1).
The kernel is based on the R3 version of Klin1344.
Current features :
All features of R3 of Klin Kernel (see below)
Battery life improvement using the patch of Entropy512
Jhash3
Optimized CFS (process scheduler)
A lot of memory tweak
TinyRCU
New Governor created for the kernel (based on smartassV2) : TerraSilent (I recommend you to use it)
CleanCache (using zCache) (see below for explanation)
zRam (see below for explanation)
Updated crc32 algorithm (that is quite used everywhere in the kernel)
Using optimized Sha1 algorithm
Lzma compressed initramfs
Swap enabled
New Boot logo (same image (but bigger) as the one in the begin of the Thread)
Feature Coming from based kernel :
V(R), BFQ, SIO Scheduler
OC to 1.2GHz
ClockWorkMod (recovery)
interactiveX, smartassV2, ondemandX, and the default governors.
Netarchy/coolbho3ks SoD patch from Entropy512's source (allows you to use screen off profiles of under 800Mhz)
Ext4 support
Voodoo Sound
etc ... see http://forum.xda-developers.com/showthread.php?t=1601773
Changelog
Version 1.3.5
[RECOVERY] Optimization of the recovery with better use of the busybox
[RECOVERY] Can save the /dbdata partition in nandroid
[USA] Added VOODOO FM
Version 1.3
[CHANGE] Zram built-in not a module anymore
[BUSYBOX] Updated busybox to last version 1.20.1 meaning any init.d script will be launched with that version.
Version 1.2
[MAJOR BUG FIX]Corrected a bug with the recovery that wasn't able to mount correctly the /data partition, it was leading to a complete wipe of data when applying ZIP that needed that partition to be mounted
[OPTIMIZATION]Using LZO Compression for ZRam also, after some test, I discover that Snappy compression is not really optimized on our device.
Feature Explanation :
faux123 said:
CleanCache (via ZCache backend)
ZCACHE is a new technology I introduced to Sensation Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.
Source : http://forum.xda-developers.com/showthread.php?t=1359951
Click to expand...
Click to collapse
faux123 said:
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Source : http://forum.xda-developers.com/showthread.php?t=1359951
Click to expand...
Click to collapse
Dark_Balor said:
TerraSilent Governor
TerraSilent is completely based on the SmartAssV2 kernel with some improvement for the battery. When you are putting your device on sleeping/suspend, it's changing the frequency to 100Mz (if you set a minimum higher then that, it will be used instead) to avoid using too much battery when not needed, you can still listen to music without any lag. (if you experience some lag just change the minimum to 200Mhz).
It also less aggressive on ramp up the frequency, instead of always trying to reach the ideal frequency (400Mhz by default, I'll explain for tweaker all they can change if they want) it will try under frequency first (200Mhz if you were at 100Mhz before). Meaning using less battery.
By default when the load >= 85%, it will ramp up the frequency and if its lower than 35, ramp down it to an new frequency calculated using the current load.
Click to expand...
Click to collapse
How to tweak/activate special features
By default zCache and zRam are disabled because they can be unstable depending on the device.
By example, I don't have problem with zCache but with zRam yes, and Klin the exact opposite. The better is to try for your device and then choose which one you want, the 2 or none.
zCache :
To activate zCache, you only need to put a script in your init.d directory (in etc) or using ScriptManager to launch that line on boot :
Code:
insmod /lib/modules/zcache.ko
zRam:
To activate zRam, you only need to put a script in your init.d directory (in etc) or using ScriptManager to launch theses lines on boot :
Code:
mkswap /dev/block/zram0
swapon /dev/block/zram0
Changing by script the governator to TerraSilent
if you don't want to use (but I recommend noFrill Cpu to do that) an application to change the governator, you just need to do :
Code:
echo terrasilent > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Tweaking TerraSilent
in /sys/devices/system/cpu/cpufreq/terrasilent you'll find these files :
Code:
debug_mask --> for debug (possible value 0(disabled),1,2,4)
up_rate_us --> µs to wait before ramp up
down_rate_us --> µs to wait before ramp down
sleep_ideal_freq --> Freq used when sleeping/suspend
sleep_wakeup_freq --> Freq use when waking up
awake_ideal_freq --> Freq ideal for daily usage
sample_rate_jiffies --> DON'T TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING
ramp_up_step --> step used when ramp up in Hz (to calcule the new frequency) (0 = maximum freq will be used when ramp up)
ramp_down_step --> step used when ramp down in Hz (to calcule the new frequency) (0 = using heuristic to found the best new lowered freq)
max_cpu_load --> max load that trigger the freq change for ramp up
min_cpu_load --> min load that trigger the freq change for ramp down
Where you can put your own values. (You have to do that after every boot, the best is to create a script that change the governor to TerraSilent, and set the wanted values)
FAQ
How to create a script
With ScriptManager it's easy, just push the menu button -> New -> Script
Put the script lines you want
Menu -> save
That's done
Manually : create a file name my-script.sh
put as first line :
Code:
#! /system/bin/sh
and then what you want your script to do.
Don't forget to do a
Code:
chmod +x my-script.sh
to make it executable.
Download (ODIN PACKAGES) :
http://www.mediafire.com/?cf9aw48dnmiqi
Source Code
Kernel : https://github.com/Belphemur/Galaxy-Player-4.0-Kernel
Initramfs : https://github.com/Belphemur/initramfs_yp-g1
If you love my work, don't hesitate to click the thanks button
Thanks to
Steve for the first modded kernel of our device
Klin1344 for continuing, improving the work of Steves and testing my kernel for the USA version.
Entropy512 for the battery patch, and a lot of other tweak
Faux123 for all the patch he have backported to the 2.6.35 kernel (zCache, zRam, etc ...)
THanks for your hard work in this kernel. You certainly know more about linux kernels than me.
But for some reason now enabling zram causes crashing and reboots but zcache does not. Oh well, at least one of them works!
klin1344 said:
THanks for your hard work in this kernel. You certainly know more about linux kernels than me.
But for some reason now enabling zram causes crashing and reboots but zcache does not. Oh well, at least one of them works!
Click to expand...
Click to collapse
I'm a Computer Sciences Student, and I already compile some kernel for my server, my computer ^^
It just my first kernel for an ARM device.
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
ChaosChris said:
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I just flashed, but it still runs at 800mhz constantly while playing music with the stock player!
I am using the terraslilent governor.
Sent using Tapatalk
ChaosChris said:
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I'm sure this is a stupid question, but I don't know the answer and the only way to learn is to ask, but how do you tell what the CPU is running at with music playing and screen off?
CPU spy (search for it on the market).
My theory is that the music player is programed to run at the max CPU speed available, which is 100mhz (I think) with the stock kernal. So, when you up the Max frequency to 800mhz, than the music player runs at that. What I still don't get, though, is 1; why doesn't your terrasilent governor solve the problem for me like it did for others, and 2; why does flashing the stock kernal not solve the issue?
Anyway, I'm not entirely sure that it really is running at 800mhz, as I let it play music overnight for 8 1/2 hours, and it only drained 30% battery from 70% to 40%. That makes about 4% per hour, which seems alot lower than I would expect a device running at 800mhz constantly would get. What do you guys think?
Sent using Tapatalk
iJimaniac said:
CPU spy (search for it on the market).
My theory is that the music player is programed to run at the max CPU speed available, which is 100mhz (I think) with the stock kernal. So, when you up the Max frequency to 800mhz, than the music player runs at that. What I still don't get, though, is 1; why doesn't your terrasilent governor solve the problem for me like it did for others, and 2; why does flashing the stock kernal not solve the issue?
Anyway, I'm not entirely sure that it really is running at 800mhz, as I let it play music overnight for 8 1/2 hours, and it only drained 30% battery from 70% to 40%. That makes about 4% per hour, which seems alot lower than I would expect a device running at 800mhz constantly would get. What do you guys think?
Sent using Tapatalk
Click to expand...
Click to collapse
After a lot of testing, I'm sure the application is wrong (or disabling the early suspend state).
When suspended the device have a freq of 100Mhz, you can check it with this command :
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
using adb when the device is suspended. You'll see it's 100Mhz (or the min you set if the min above 100Mhz)
The other test you can do is checking the time in state
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
You'll see that is passing more time in 100Mhz and 400Mhz then every other states.
(for the stats SetCpu or NoFrillCpu can read it for you)
Well, setcpu says the same as cpuspy: constantly 800mhz. However, I just ran it for 1 hour, from 100%, and it drained 4%. While I used to get around 2% per hour, this still seems fairly low consumption to actually be at 800mhz. I guess I will just live with it.
One more question; is there a way I could "undo" the SoD patch, or whatever would be causing this? I thought it would be as simple as flashing stock kernal, but not so. Would a flash of a stock kernal AND factoryfs.rfs do the trick?
Actually two more questions, lol; you realize that this is only happening with the stock music app; all other apps work fine. (Just not sure if I actually made that clear)
Sent using Tapatalk
got the kernel loaded up and since my primary use of my player is music playback i've used nofrills to underclock my cpu to max out at 400 mhtz, my question is can I and if so what app to use, to under volt my cpu to maximize my battery life?
daniel644 said:
got the kernel loaded up and since my primary use of my player is music playback i've used nofrills to underclock my cpu to max out at 400 mhtz, my question is can I and if so what app to use, to under volt my cpu to maximize my battery life?
Click to expand...
Click to collapse
Voltage control (free) will let you UV
iJimaniac said:
Well, setcpu says the same as cpuspy: constantly 800mhz. However, I just ran it for 1 hour, from 100%, and it drained 4%. While I used to get around 2% per hour, this still seems fairly low consumption to actually be at 800mhz. I guess I will just live with it.
One more question; is there a way I could "undo" the SoD patch, or whatever would be causing this? I thought it would be as simple as flashing stock kernal, but not so. Would a flash of a stock kernal AND factoryfs.rfs do the trick?
Actually two more questions, lol; you realize that this is only happening with the stock music app; all other apps work fine. (Just not sure if I actually made that clear)
Sent using Tapatalk
Click to expand...
Click to collapse
I have the governor set to smartassv2 and my cycles through. It was at 800 mhz for about 35% of the time. I'm using PlayerPro with the DSP pack and voodoo sound, though, and not stock.
Yeah, just something wrong with the stock player. Oh well, I'm going to buy poweramp since I just tried the trial and now the stock player seems pathetic anyway I love the lockscreen controls!
Sent using Tapatalk
iJimaniac said:
Yeah, just something wrong with the stock player. Oh well, I'm going to buy poweramp since I just tried the trial and now the stock player seems pathetic anyway I love the lockscreen controls!
Sent using Tapatalk
Click to expand...
Click to collapse
Quick off topic question... Can you get Poweramp's settings to stick? Such as to not show the rating, EQ, etc (the look and feel settings). I like Poweramp a little better (sounds about same as PlayerPro with DSP) but the settings being wonky bothers me.
Hmm, I don't remember and my trial is up. I don't think there was a problem (that I noticed).
Sent using Tapatalk
indyssee said:
Quick off topic question... Can you get Poweramp's settings to stick? Such as to not show the rating, EQ, etc (the look and feel settings). I like Poweramp a little better (sounds about same as PlayerPro with DSP) but the settings being wonky bothers me.
Click to expand...
Click to collapse
YES, under settings / Look and feel, just go in and set the things you don't want to see to Hidden.
daniel644 said:
YES, under settings / Look and feel, just go in and set the things you don't want to see to Hidden.
Click to expand...
Click to collapse
That's my point, it just ignores everything and doesn't change anything. I've tried all different ways to get them to stick. Doesn't work on my phone, either.
indyssee said:
That's my point, it just ignores everything and doesn't change anything. I've tried all different ways to get them to stick. Doesn't work on my phone, either.
Click to expand...
Click to collapse
Have you tried unistalling rebooting then reinstalling? Are you on a custom ROM?
Any suggestions for a boot loop that doesn't involve wiping data?
rozelle25 said:
Any suggestions for a boot loop that doesn't involve wiping data?
Click to expand...
Click to collapse
NOPE, bootloops are caused by conflicting files and the ONLY way to solve is to WIPE.
You could try to get into Download Mode and flash back to the ROM/Kernel you where on before your flash that caused the bootloop.

[Kernel] Lightning Zap Kernel... Update to Lollipop 5.0

Thomas.Raines presents
The Lightning Zap! kernel for the Nexus 4 Mako
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"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"
}
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
kexec hack for dual booting with MultiRom.ak
Overclocked cpu
sweep2wake/doubletab2wake (disabled by default. must be enabled via script by uncommenting lines 7 and 8 in /etc/init.d/05s2w then reboot)
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Governors:
POWERSAVE
USERSPACE
ONDEMAND
INTERACTIVE
BADASSS
INTELLIDEMAND
LIONHEART
ONDEMANDX
SMARTASS2
GALLIMAUFRY
LAZY
io-schedulers
NOOP
DEADLINE
CFQ
SIO
See 2nd post for download links and changelogs
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Reboot
Wait 10 minutes
Enjoy the Lightning Zap!
See 2nd post for download links and changelog
**The first boots usually takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
mako-lz kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
Special thanks to:
jrummy16 for Root Browser Lite
show-p1984 for bricked kernel (used for rebase)
Download Links and Changelogs
Nexus-4-Mako-LightningZap_p5.1.2.zip
cpufreq adjustments
led driver adjustments
Import RB tree adjustments from Motorolla
Input packet management adjustments
EOL
https://github.com/LightningZap/and...mmit/9ee0e0e3f9cf2733c554f0da69724c79f71cb4d9
Nexus-4-Mako-LightningZap_p5.1.1.zip
Fixed voltages and frequencies
uv_bin overhaul
Fixed inconstancies in installer
Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy. On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.
Nexus-4-Mako-LightningZap_p5.1.0.zip (dl link unavailable)
Major upstream update (166 commits)
TCP tweaks
Added GCC optimizations
Updated linaro toolchains
If you are having random reboot issues or you get stuck on the Google screen, try raising your min voltage to 700MHz. If that still doesn't work, let me know here. Please try to attach a dmesg log and make sure you tag me in the post so I don't miss it (@thomas.raines)
Enjoy!
Nexus-4-Mako-LightningZap_p5.0.2.zip
Added intelli_plug to handle CPU hot swapping
Disbabled MSM_HOTPLUG
Bumped to 5.0.2
Set min CPUFREQ to 9450
Changed Aroma installer defaults to my recommendations.**NOTE** If overclocking, I recommend using higher voltage min...
Included a LightningZap! tailored init.mako.rc that sets vibrator amp to 100, disables all that unneeded cpu governor junk and more...
Nexus-4-Mako-LightningZap_p5.0.1.zip
Bump to 5.0.1
added 5.0 emmc support
speedup /proc/net/unix
network speed tweak
exec_hardboot:updated with more current patch.
Avoids bogus error messages for the suspend aborts.
Avoid using global variable total_cpus
added sound control Thanks @faux123
Nexus-4-Mako-LightningZap_p5.0.zip
Update kernel to Lollipop 5.0
Added script to fix wonky sdcard issue. (5.0 was changing it from /sdcard/<your files> to /sdcard/0/<your files>. Script prevents that from happening and all is well)
All the same greatness of Lightning Zap! 4.4.X with no issues
Enjoy folks!
Nexus-LightningZap_p4.4-3.3.zip
Added remaining uv options to table
Backlight dimmer options
USB Fast Charge
CPUFREQ:rework of all tables. New implementation of freq's using PVS.
cpufreq: properly sync current scaling governor across all cores
Slight boost in L2 cache. Corrected number of cpufreqs
enable max screen off freq on/off support
added RESTRICT_ROOTFS_SLAVE
Added fsync on/off support:Enabled by default
Added f2fs and exfat support
Inspired by elementalx's flashing format using Aroma Installer, I have revamped cpufreq and uv tables, as well as added a few options.
You can now set your default options with the installer. Just follow the prompts as you go thru.
The flashing instructions are the same; however, at the end of the flashing process, you will have an option to save the log. I would recommend doing so. But only share it with me if you have an issue.
The installer is not without it's little glitch. Occasionally, your screen might flash and appear to be going from screen to screen in recovery after the installation process has finished. Nothing to worry about. Just let it settle down and then reboot. I only had this issue in philz_touch.
With the L2 cache boost, and the lightningzap booster, those pesky random reboots due to L2 cache failing to sync are a thing of the past.
One thing to note, when selecting your cpufreq, this will set you MAXIMUM. Meaning, even with an app, you will not be able to go over the default you set. Select carefully. I would recommend setting core 1 to the highest you desire and then setting the other 3 cores lower in the case you need more. And just use trickstermod to adjust as necessary. Oddly enough, even if you set the cores individually and cores 2-3 lower than core 1, your max will be whatever core 1 was set on. But if you adjust them reverse to what I said, then you will be limited to whatever default core 1 is. Hopefully that makes sense.
I have also linked all cores. This means that when you use Trickstermod app to set your cpufreq, it applies it to ALL cores. I have notice some apps, like kernel tweaker, do not do this as they are not written correctly for multi-core processors. Most of the defaults like voltages, fsync, and sweep2* can still be controlled with trickstermod even if you disable them during install.
TBH the only thing you cannot change, is your max cpufreq (meaning, if you choose 1512(stock) as your max during install, the only way to raise it is to re-install the kernel. However, you can still fine tune it).
Another note, max freq is set to 1620; however, if you can still set it higher, will just have to use trickster mod to fine tune it...
Previous Changelogs and links
Nexus4-LightningZap_p4.4-3.2.zip
Dropped mpdecision
Added msm_hotplug (With updates)Reconfigured voltage table. Boots @ 700000uV on 94500mHz
Possible UV/OV is now 600000uV min 1450000uV max (Be careful with this as too low/high for your device could cause instability. Test your settings BEFORE setting it to set at boot. If you go below the thresholds, your device will become EXTREMELY unstable, reboot, say you should have listened and then blow up in your face...lol. Not really, but it will go into a kernel panic and reboot)
And FYI, the voltages are reported in uV not mV. If you don't know, 1000uV = 1mV; therefore, the kernel boots @ 700000 is 700mV...
Nexus4-LightningZap_p4.4-3-1.zip
Added sec_dvfs_dual. All CPU's handle hotplugging better now
Added lulzactive cpu gov
add row and fiops schedulers
set fiops as default scheduler
Working on getting smartassv2 to compile...
added LCD Gamma Hack from faux kernel
Nexus4-LightningZap_p4.4-3.zip
2 stage update on this one.
Stage 1
Dropped bricked base and went back to kk4.4 (AOSP & CAF) base
Revamped OC/UV. Still compatible with Trickster Mod app
(Because I dropped the bricked base and went back to original base, you won't have full control on thermald and mpdecision for now. Working on adding it, please be patient)
Stage 2 With results of the latest poll in mind:
Dropped the following governors:
Conservative
Gallimaufry
Ondemandx
Userspace
Made Intellidemand/deadline as default
Nexu4-LightingZap_p4.4-2.zip
Complete revamp of base. Used bricked kernel as base (thanks to show-p1984)
Created new branch for revamp (bricked-lz) Keeping kk4.4 branch for now.
Per user requests:
Moved RootBrowser to /data **Must remove it from /system/app prior to flashing
Removed voltage control app. No longer compatible with vc.
Fully compatible with TricksterMod app
Vote on the next poll for your favorite governor & io-scheduler (If I can get it setup right)
Nexu4-LightingZap_p4.4-1.2.zip
Reverted back to Linux Android Kernel version 3.4.0 due to instability
Bumped to p4.4-1.2
Revamped mako_defconfig in order to enable loadable modules
changed build cifs & tun as modules
Left WiFi modules as hard-coded drivers to avoid WiFi issues on other Roms (Sorry about this one guys and gals)
Nexus4-LightningZap_p4.4_1.1.zip
Bumped to latest stable kernel version 3.84.4 (LightningZap version p_4.4-1.1)
Added sweep2wake and doubletap2wake from bricked-kernel Mako (special thanks to show-p1984)
sweep2wake and doubletap2wake is disabled by default. To enable one or both, refer to this post
Nexus4-LightningZap_p4.4_1.zip
Initial release
Just a note, some combinations of governors and io-schedulers don't mix well and you could experience instability like freezes and reboots. Before posting an issue, change your governor and or io-scheduler. This will help me narrow down any issues. And by all means, please let me know which combination you experienced an issue with, and what exactly occurred.
Note that certain ROMs like Omni and Ubuntu Touch that use a modified initramfs or some other kernel modification, may not work with this kernel. I am working on it now.
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
Great seeing you here! My brother uses your kernel on his E4GT and he likes it a lot.
I hope you do good work for the N4 as well. :good::good::good::good:
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
The OP says it's for Blaze 4G You might want to edit it to avoid confusion Thanks for your work, sir. I had use yours in my Blaze 4G.
Maybe a bit explanation of governors? Like for lionheart and galli
Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
Wow I saw you in the Blaze fourms. Great to see you developing on the N4!
Sent from my Nexus 4 using xda app-developers app
Saw you in the et4g forums
Sent from my Nexus 4 using Tapatalk
I'm glad people say this is real looked like a hoax to zap my n4!
So who has flashed this?
sent from a toilet...
phone always fc's for me on 3 different AOSP roms
Thanks for the kernel......Testing-----------------:good:
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
Can you be more specific?
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
by chance you tried it in the rom Purity? by that I have not had problems with.:good:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Yadro said:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Click to expand...
Click to collapse
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
thomas.raines said:
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Click to expand...
Click to collapse
Thanks! So far i'm enjoying this kernel a lot! Working out for me on XenonHD.
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
thomas.raines said:
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
Click to expand...
Click to collapse
okay i'll try that now too.
---------- Post added at 09:00 AM ---------- Previous post was at 08:49 AM ----------
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
M3drvr said:
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
Click to expand...
Click to collapse
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
I wasn't too worried. Just wondering. Thanks! So far the new kernel very good. The first 5 minutes of it being installed there were quite a few lags and glitches. But after that, its smooth as ever!
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
That's to be expected while the kernel settles in. Glad you're enjoying it!
Sent from my Nexus 4 using xda app-developers app
Should MPDecision be enabled if using the noop scheduler and Lionheart governor? Or whats your recomendation?

Categories

Resources