Related
NON DEV ISSUES AND QUESTIONS ABOUT KERNEL POST HERE. THIS IS A WORK IN PROGRESS THREAD
HISTORY
I have been given Permission by the Kernel's Author (Gokhanmoral) to create this thread. Please put your issues or questions you have with the Kernel in this thread. Also functional request should also be made here. The aim of this thread is to filter out excess questions regarding the use and experience from the development thread. The author of the kernel and many experience users\testers and primary dev contributors need to use the Development thread in order to help Gokhan to implement his kernel. Would also request the community to contribute in terms of info to compile a knowledge base if you will. Many Thanks Gokhan and future contributors.
THANKS:
Samsung, supercurio, hardcore, Hacre, RAvenGEr, tegrak, cattleprod, codeworkx, hellcat, creams, vitalij, arighi, ninpo,netarchy .. Any others that I missed.
SiyahKernel v2.6.12
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
Custom CWM compatible Redpill Recovery from af974 (For more info: http://forum.xda-developers.com/showpost.php?p=21727136&postcount=9680 )
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, BFQV3r1, V(R), SIO(default)
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.
Charging the battery stops when the battery draws less than 100mA (stock value is 200mA).
CIFS, SLUB, FUSE, NTFS, cgroup_timer_slack, autogroup,... and lots of other mambojambo that I forgot...
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.
FAQ (WIP)
General
Q: Does this kernel support latest i9100 ROM which is based on android 2.3.5 -2.3.7?
A: Yes, it does.
Q: Can I use this kernel on I9100G?
A: No, you cannot. Only International i9100 and Canadian (Bell Mobility) models are supported (Chinese or AT&T T-Mobile US are not 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 from 2.0 and above. If you are using another AOSP based Rom tell me and I will support it.
Q. What is the latest version of the Kernel?
2.6.3 is the latest and can be found here:
SiyahKernel Edition v2.6.12 (Please ensure you choose the right one for your phone)
Q. I have an International i9100 can I flash NTT version?
A. Important Notice: the one with "ntt" in the filename is NTT DoCoMo SC-02C version. do not flash it if you have EU version
Q. Where can I get the latest Kernel Source for this Kernel?
A. It can be Found Here: Kernel Source
Q.Are there any Variants based on this Kernel?
A. Yes there is DK SIYAH KERNEL
Q: Can I use app protectors with this kernel?
A: Yes, you can. But you have to flash EnableLogger.zip using CWM after flashing the kernel.
TO ENABLE ANDROID LOGGER USE THIS:
ENABLE LOGGER
TO DISABLE ANDROID LOGGER USE THIS:
DISABLE LOGGER IF IT IS INSTALLED
Battery & Performance Factors
Q: What is battery life like on this kernel?
A: Some have said the battery life has improved. Others said not as good as others, this however maybe down to rogue apps creating wakelocks. Could be the rom is does not take advantage of the kernels features or could be a bad battery. Let's just say your Mileage may vary...
Q. I keep hearing about AOS having a factor on performance, whats all this about?
A. The Android OS using quite a lot of resources. AndreiLux wrote and in depth reference post about this which you can find here: [REF][Rewrite 26/10] What the Android OS usage is and what it's not
Q: What can I do to improve battery life?
A: put your phone into airplane mode or do not use packet data when you are not using it. Check for Rogue Apps and also check for unnecessary wakelocks and close them.
Q: I get random reboots or freezes. What should I do?
A: Make sure you boot in Recovery wipe cache and dalvik, then reflash the kernel. Although the kernel will do this if you apply the CWM.zip of the Kernel. It can still leave data behind.
If you are undervolting revert back to stock values. Then start reducing voltage by.25 and test. If that does not work make a note of:
1. When did it happen?
2. Which rom are you using, can you reproduce it
3. do you have any custom init scripts which changes kernel parameters such as freq voltage or anything else?
Post in this thread and we will try and help you.
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: 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.
OC/UV and init Scripts
Q. What tools can be used to manipulate the clock speeds of this kernel?
SetCpu : http://www.youtube.com/watch?v=X9Sn4Uz4pkM Just an overview
Voltage Control: http://www.youtube.com/watch?v=XkhBFVUKBTQ Just an overview
No-frills cpu: More Info here about the tool
And Initialization Scripts
Tegrak Overclocking app is currently NOT SUPPORTED by this kernel
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. Okay how do I start to create my own Init.d Script for the kernel?
A: KWERDENKER has written a reference guide to help you get started. You can find his excellent Guide on POST #2 of this thread.
example of Kwerdenker scripts are also in Post 2.
DROIDPHILE'S NOOBS SCRIPTING GUIDE:
http://forum.xda-developers.com/showpost.php?p=19519757&postcount=10699
Here are other examples of init.d scripts supplied by Fenomeno83:
Another couple of nice init.d scripts created by fenomeno83
Q: where is the interface to change GPU clock and voltage?
A:There is now a GUI to change GPU voltage and Charging current it's voltage control and probably one by Gokhanmoral soon
For Undervolting your GPU use this Script from AndreiLux as a Reference:
Example CWM-flashable /system/etc/init.d/99gpuv script
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
HERE IS DROIDPHILE CONCISE GUIDE TO GOVERNORS
http://forum.xda-developers.com/showpost.php?p=19339524&postcount=10023
More info might help those you get a better understanding for schedulers:
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt Source: Cyanogenmod Githubs
Info about Lulzactive Governor.
http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html
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. I notice one of the features is the ability of customizing Voltages for Charging?
A. Gokhan has written a script which he converted to be applied using CWM recovery (PLEASE BE CAREFUL WHEN APPLYING THIS, IF YOU ARE UNSURE PLEASE ASK IN THIS THREAD BEFORE DOING IT)
Set AC and MISC charging current to 1000mA - CWM flashable (keeps USB charging current at 450mA)
Q. I read that different frequencies would assist in better battery performance do you have any examples of this so I can use it my script?
A. Bene2K11 Created some scripts which allows you modify the bus frequencies when using this kernel, they can be found here:
3 flashable zips for the lowest, mid and highest bus frequencies
MISCELLANEOUS
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.
My Thanks for their contribution to this thread to Gokhanmoral, AndreiLux, ChadouMing, Nilste, Matriak31,Ger5,Kwerdenker,Fenomeno83, Bene2k11,Droidphile
__________________
Reproduce with permission from Gokhan by Dragon546
[REF]Init-Script Reference Guide By kwerdenker
MANY THANKS KWERDENKER FOR THIS. REPRODUCED WITH HIS AUTHORIZATION.
Original post from kwerdenker here.
I hope some of you find this useful as a reference for creating your own init-scripts. This contains everything I use or at least remember about the options in this kernel. If I forgot something or made an error somewhere, please send me a PM and I will gladly correct it.
How to use these settings:
If you want to test some settings before you commit them to a script, you can use either the adb shell if your on a pc with adb installed or you can use Terminal Emulator directly on your phone. Remeber to enter superuser mode by entering su in the terminal before you try to set anything or you will get errors. After that just enter the line you want with the values you want to test (if the values are incased in "", keep them that way!). If you want to see if it worked just enter cat followed by the part behind the > of the lines and you will get the values that are currently set. Everything you do in this fashion will not survive a reboot of your phone, if you want to make them permanent you'll have to use an init-script. A how-to on that is (currently) out of the scope for this post. Have a look/search in the kernel release thread as there are many examples for that there. I'm sure with this post and these examples you can figure it out by yourself
The values in the echo commands are the stock values (from 2.1.1 version) if not noted otherwise
[CPU]
[Frequency]
[Steps]
# Controls which frequency steps are available
# Should probably only be used to set the lowest step to 25 and/or the highest to 1696
echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table [Scaling Min]
# Controls which frequency is use by the governor as the minimal frequency (has to be a valid value in the frequency table!)
echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq [Scaling Max]
# Controls which frequency is use by the governor as the maximal frequency (has to be a valid value in the frequency table!)
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq [Voltages]
# Controls with what voltages the frequency steps are supplied
# Highest step is to the left, lowest to the right
echo "1425 1325 1275 1175 1075 975 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table [Governor]
# Available governors: ondemand, lulzactive, smartassV2, conservative, userspace, performance, powersave, brazilianwax, savagedzen, smartass, lagfree, ondemandx
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor[GPU]
[Frequency]
# Controls with what frequencies the GPU works
# Valid frequency steps are 100 114 133 160 200 267 400
echo "160 267" > /sys/class/misc/gpu_clock_control/gpu_control [Voltages]
# Controls with what voltages the GPU works
# Lowest possible value is 800000, maximum is 1200000
# Changes are only possible in 50000 steps
echo "950000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control[IO]
[Scheduler]
# Controls how IO requests are scheduled.
# Available schedulere: noop deadline cfq bfq sio vr
echo sio > /sys/block/mmcblk0/queue/scheduler[BUS]
[Frequency]
# Controls with what frequency the bus operates
# Valid values are: 0 (400MHz), 1 (266MHz), 2 (133MHz)
# Highest frequency step of cpu is to the left, lowest to the right
echo "0 0 0 0 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
echo disabled > sys/devices/system/cpu/cpu0/cpufreq/busfreq_static # Use enabled to activate this feature[Charging Current]
# Controls how much power the phone is willing to draw from a specific charger type
# Values are from left to right: AC Misc USB
# !This is a dangerous setting. Use with caution and never change the USB value and never set the other ones higher than 1000!
echo "650 550 450" > sys/devices/virtual/misc/charge_current/charge_current
I will try to keep this post up to date with any relevant changes in the kernel.
Example GPU/CPU undervolting and underclocking scripts by kwerdenker please just use for Reference
Improved version of CPU undervolting script by kwerdenker please just as a reference
P.S.: I will not respond to request what settings you should use to achieve the highest score in a benchmark or how you get the most battery life. This is just to gather the information that is already floating out there. What you do with it is up to you
BETA and RC
beta releases will be available when gokhan releases them
Someone asked in another posting about whats the difference between the governors you can choose in Siyah kernel.
Here is an informative article from Github that explains the difference. The governors are from Cyanogen but I beleive it will give you a fair insight in their caracteristics for Siyah also.
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt
There are also a couple more governors you can choose in the latest RC. Maybe others can give some info. about their caracteristics.
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
nilste said:
Someone asked in another posting about whats the difference between the governors you can choose in Siyah kernel.
Here is an informative article from Github that explains the difference. The governors are from Cyanogen but I beleive it will give you a fair insight in their caracteristics for Siyah also.
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt
There are also a couple more governors governors you can choose in the latest RC. Mabye others can give some info. about their caracteristics.
Click to expand...
Click to collapse
This is exactly the stuff I am looking for thank you nilste
Corndude said:
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
Click to expand...
Click to collapse
Corndude How does insanity do its reporting? is it like miui where you can see the app usage in battery usage section like stock's app manager?
Did you get the stats before on the last kernel you use? I am not on insanity but if I cannot answer your query others can.
Originally Posted by Corndude
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
Click to expand...
Click to collapse
Corndude How does insanity do its reporting? is it like miui where you can see the app usage in battery usage section like stock's app manager?
Did you get the stats before on the last kernel you use? I am not on insanity but if I cannot answer your query others can.
Click to expand...
Click to collapse
i did get the stats before rc3, also doesn´t show the monitor´s use. Insanity is just like cm7, same stuff.
http://forum.xda-developers.com/showthread.php?t=1242323
i do not know if it helps but a bit more regarding governors..
Corndude said:
i did get the stats before rc3, also doesn´t show the monitor´s use. Insanity is just like cm7, same stuff.
Click to expand...
Click to collapse
Did you just install Rc3 without wiping dalvik? Just want to check . I always do a dalvik and cache wipe before I use CWM to apply the kernel update or If I use Odin to apply the kernel I then boot up into CWM recovery and perform a cache and Dalvik afterwards
Nice thread. Can anybody explain/point me to a good guide on cpu schedulers? This kernel allows changing the scheduler, but i don't know which one is the best for my kind of usage: movies-games-browsing, gpu intensive stuff i guess. Thanks.
Matriak31 said:
http://forum.xda-developers.com/showthread.php?t=1242323
i do not know if it helps but a bit more regarding governors..
Click to expand...
Click to collapse
Any help is appreciated Mat. Ty for your input
No probs mate.. good idea regarding the thread...At least now the Siyah one can stay just kernel related and all the Q&A can be moved here now..Great job
Issue I had with RC2:
-3G not functional, I didn't realize this until a few hours later when I wasn't at home enjoying my network; tested phone signal, was able to make calls, was in a bit of a cellular black hole but others on the same, and other networks, were able to access data easily,
-Restored my APN's from b/u to address 3G connectivity and at this point I lost all signal, no IMEI, phone number, etc... and would get an FC if I attempted to open the dialer, this was back at home where I have no data issues ever,
-Restored a nandroid b/u and all was good; did not try restoring EFS prior to this.
Just curious what the issue might have been; EFS corrupted (seemed to be a step wise loss), other?
And yes, at this point I realize I should learn a lot more before testing betas, etc... it's on my list Other than that I was thoroughly impressed with the lulzactive governor.
dragon546 said:
Did you just install Rc3 without wiping dalvik? Just want to check . I always do a dalvik and cache wipe before I use CWM to apply the kernel update or If I use Odin to apply the kernel I then boot up into CWM recovery and perform a cache and Dalvik afterwards
Click to expand...
Click to collapse
Siyah wipes it all by itself when installing via cwm.
mudferret said:
Issue I had with RC2:
-3G not functional, I didn't realize this until a few hours later when I wasn't at home enjoying my network; tested phone signal, was able to make calls, was in a bit of a cellular black hole but others on the same, and other networks, were able to access data easily,
-Restored my APN's from b/u to address 3G connectivity and at this point I lost all signal, no IMEI, phone number, etc... and would get an FC if I attempted to open the dialer, this was back at home where I have no data issues ever,
-Restored a nandroid b/u and all was good; did not try restoring EFS prior to this.
Just curious what the issue might have been; EFS corrupted (seemed to be a step wise loss), other?
And yes, at this point I realize I should learn a lot more before testing betas, etc... it's on my list Other than that I was thoroughly impressed with the lulzactive governor.
Click to expand...
Click to collapse
What rom you using?
I am on RC2 on Miui as far as I am aware I did not think it would interfere with EFS or change modem. Was there any think else that might have cause the EFS corruption or APN changes.
Corndude said:
Siyah wipes it all by itself when installing via cwm.
Click to expand...
Click to collapse
You tried clear data on the app manager and reboot the phone?
i have this problem whereby UV settings are applied during boot. am using init.d scripts. it sticks for 5-10mins and then it automatically reverts back to stock values. anyone else facing this prob?
am running gingermod 0.7
dragon546 said:
What rom you using?
I am on RC2 on Miui as far as I am aware I did not think it would interfere with EFS or change modem. Was there any think else that might have cause the EFS corruption or APN changes.
Click to expand...
Click to collapse
I'm on DlevROM (XXKI4 based); Siyah 2.0 does back up EFS, so there must be a chance for corruption somewhere along the line.
dragon546 said:
You tried clear data on the app manager and reboot the phone?
Click to expand...
Click to collapse
Just wiped manually and restarted - works, thanks a lot
Please leave non-development related posts to the discussion thread in general section: http://forum.xda-developers.com/showthread.php?p=27389678
STOP! This kernel supports ONLY Samsung JellyBean or CM10.1 ROMs. It won't work on ICS, CM9.
{
"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"
}
Sources :-
Sources at http://github.com/gokhanmoral/siyahkernel-sgs3
Ramfs at http://github.com/gokhanmoral/ramfs-sgs3
Toolchain at http://github.com/gokhanmoral/android_prebuilt
Simply clone all to a directory and run build_kernel.sh in the kernel directoryFeatures :-
Samsung and CM10.1 support with a single kernel image
based on i9300 update9 sources
CPU OC/UC/UV
GPU OC/UC/UV (5 step GPU clock)
Audio enhancement and sound boosting for great headphone experience (partial-port of wm8994 based implementation from project-voodoo)
init.d support
Triangle-away app support
Auto-root
Adjustable charging speeds for AC and USB
Automatic EFS Backup
Samsung proprietary ExFat modules are loaded. Don't ask about ExFat support for aosp roms in this thread.
Kernel based gestures support by Tungstwenty. See http://forum.xda-developers.com/showthread.php?t=1831254
NTFS automounting for USB sticks, mounted to /mnt/ntfs folder in Read Only mode.
mDNIe negative effect toggle with 4 consecutive press of home button
mDNIe values can be adjusted using the interfaces in /sys/class/misc/mdnie.
Almost everything is configurable via simple and free STweaks (included in the kernel or from Google Play)
Dual-booting. You can have Samsung JB and CM10 ROMs on a single device at the same time.
slide2wake (WIP, still incomplete)
Known Problems :-
No known problems.
Thanks To :-
Chainfire, AndreiLux, Tegrak, Entropy512, Netarchy, Pikachu, Tungstwenty, Codeworkx, XploDwilD
This part will be expanded. most of the patches I applied are coded by someone else. please remind me if I forget to give credits to anybody..
Downloads :-
http://www.gokhanmoral.com/
Changelog :-
See http://www.gokhanmoral.com/ for changelog.
Todo:
these are my future plans and some of them are dreams only...
fix bugs
add optional teamwin recovery
implement BFN (BackFlashNotification)
...
Video Review of v1.7rc1 by KingRamo
IRC support and chat:
Server: irc.FreeNode.net
Channel: #siyah-kernel
web client: http://siyah.twosx.net/ (thanks to omniwolf)
READ THESE FIRST
First thing you need to have before posting to this thread is respect. If you don't have it for others you will regret leaving a post as people in this thread don't like disrespect. The items below are just detailed description of what "respect" means in this context. If you have common sense you probably won't need to read all the following items but please do read them anyway.
Never report any bugs to CM9/CM10 thread if you use it together with SiyahKernel
Do not ask questions to me directly. This is a common thread, not my personal inbox. Ask your questions in the thread and do not target them to anyone.
Do not expect answers to all your questions. There are some questions which nobody knows the answer of.
Do not forget that this is a development thread. There is another thread in general section for those who wants to discuss battery life and chats. If your post does not include a feature request, bug report or suggestion it should be posted to the other thread.
Make sure you state your ROM, settings and any other relevant information while telling about your problem/a bug. "I have lag", "I had crash" or any similar posts will be ignored if you don't give any more details.
No ETA for new version. Even if I sometimes talk about release dates those may change and they change for some good reason or because of my real-life obligations.
Make use of "Search this Thread -> Advanced Search". If you humiliate people and waste their time by asking a question which is answered in the last 3 pages I guarantee that you will be treated as you deserve.
You need STweaks app to configure/change most of the features in this kernel. However it is not required if you don't want to modify anything.
Never ever discuss anything deep-sleep related in this thread. I do not make modifications to prevent sleep and 99% of deep sleep problems are application/ROM related. discuss it in general section. I do not want any positive ("this kernel sleeps like a baby") or negative ("There is a big problem with deep sleep. Please fix it") messages in my development thread.
I am not interested in any bug reports if you undervolt your device. I don't want ANY kind of undervolting related discussions or bug reports in this thread.
Useful Links:
Almost everything that you need to know about Kernels, schedulers and so by droidphile
Another great post explaining more and ICS differences by droidphile
Although I put it in the first post, this is my github for kernel sources, initramfs and some more
You can find all the answers you need here, even those that I don't know
last one
FAQS and More
FAQS and More
In no particular order.
1. "How the heck do i flash the kernel.tar within device. I see a boot.img and recovery.img in the tar and not zimage like before?? I don't wanna increase flash counter by using odin from PC!"
A. Use mobile odin. (Paid on market, free on XDA).
Open the app, Click on "kernel", select the kernel.tar. Scroll down, select "flash firmware". Reboot.
2. "Why two mountable image files in tar?"
A. GS3 has separate kernel and recovery partition.
Kernel partition : /dev/block/mmcblk0p5
Recovery Partition: /dev/block/mmcblk0p6
Both partitions has a max size limit of 8 MB each.
3. "Does that mean i can flash only kernel/only recovery if i don't need the other?"
A. Yes. However, if recovery was modified to support a new feature in kernel, you may want to flash both.
4. "If i flash tar from Odin on PC, both kernel and recovery is flashed and i can't choose to flash only one?"
A. Yes, both are flashed.
5. "How to flash only kernel/only recovery with cwm flashable zip?"
A. If you know what you're doing, open updater-script in the zip and comment out the line that starts with write_raw_image for the one you don't need - kernel or recovery.
6. "Should i wipe cache and dalvik before flashing kernel?"
A. NO
7. "Best governor, best i/o scheduler for this kernel?"
A. Define best governor and best i/o scheduler!
Pegasusq is good enough to be responsive, battery friendly and quad core friendly if tweaked properly. Use any i/o scheduler. Sio/deadline are good.
8. "Why is Idle+Lpa default on STweaks and the recommended settings. In Siyah kernel for GS2, Aftr+Lpa was recommended!"
A. Aftr ofcourse saves more power than Idle if you consider what each of those low power state modes do. But combination of quad core architecture and pegasusq governor (or any external hotplugging logic combined with other governors) which need to respect rq values along with load thresholds makes it a little slower to turn off last 3 cores (if all the cores are ON obviously). AFTR requires that all cores except first (cpu0) be turned off - to kick in. So we're better off with Idle+Lpa.
However if you're using forced single core mode always (which is non sense in this powerful device), you can go for Aftr+Lpa.
9. "How do i overclock/underclock/undervolt GPU?"
A. Either use STweaks app or use a script
Ex:
#Frequency steps
echo 160 > /sys/module/mali/parameters/step0_clk
echo 266 > /sys/module/mali/parameters/step1_clk
echo 350 > /sys/module/mali/parameters/step2_clk
echo 440 > /sys/module/mali/parameters/step3_clk
echo 533 > /sys/module/mali/parameters/step4_clk
#Voltages
echo "875000 900000 950000 1025000 1075000" > /sys/class/misc/mali_control/voltage_control
10. "My device is not stable at 1.8 Ghz. But i still wanna overclock the device to possible maximum and show off to friends"
A. Try setting last frequency as 1750 mhz. (Modify 1.8 to 1.75 ghz with 1.7 ghz still in place)
Use kmemhelper interface. Put this line in your initd script.
kmemhelper -n exynos4x12_apll_pms_table -t int -o 0 14353152
11. "I OCed to 1.7/1.8 Ghz. My device is able to handle it. But i can't get high benchmark scores. Why?"
A. Your CPU is getting throttled during benchmark during benchmarking because of heating. This is a thermal safeguard measure. It might be getting throttled to 800 mhz or so.
Forget benchmarks, treat the overall responsiveness in daily usage as the criteria to determine if the device is fast enough for you or not.
12. "Any rule of thumb to increase life span of the battery? And I see percentage drops to 99 immediately after a charge till 100%"
A. Do not recharge to 100% often and even if you do, don't keep it plugged in 100% for long time. Best is to charge till 98%. And make sure charge does not drop below 10% while on normal use.
Charge dropping to 99% swiftly is a protection mechanism, not a fault with your battery or kernel or rom.
13. "I adjust the voltage by some mV in STweaks. I checked SetCpu and voltage has not changed!"
A. Voltage settings in STweaks follow VDD interface. They're applied ONLY during boot time. Why? The code is to reduce X mV specified by you in STweaks, for all voltages. If the settings is applied real time, it will cause reduction of voltage every time and instabilities.
14. "If I have no root, and flash this kernel using desktop odin will i get root?"
A. YES. However, if you don't see a CWM recovery, download and flash a recovery from Chainfire thread.
15. "Does the kernel backup EFS partition automatically?"
A. YES.
16. "Is there NTFS support?"
A. YES. Mounted to mnt/ntfs in Read only mode. Unmount and remount in Read Write mode if you need to.
17. "What voltage step does GS3 support while UV/OV?"
A. Regulator supports increments of +/-12.5 mV (Those who had GS2 will remember it's regulator supported +/- 25mV)
18. "Why is resetting STweaks profile recommended sometimes after a kernel flash?"
A. Your profiles are stored under /data/.siyah with ".profile" extension. ".active.profile" file under the same directory stores the name of your active profile. Contents in profiles are in the format parameter = <default_value>
There could be changes in Stweaks interface for a new build:-
i) Some new tunables were added
ii) Some tunables were removed
iii) Transposition of some tunables
iv) Default value of some tunable was changed.
When such a change occurs, your profiles should know it too so that it can contain all the parameters. That's why you have to reset profiles after a new kernel flash if it changes something in STweaks.
Resetting simply copies .profile files from /res/customconfig to /data/.siyah . You can do it manually using a file manager to avoid a reboot to recovery and back to rom. Kernel already detects STweaks changes to reset profile automatically on first boot after flashing.
19. "How to insert a module that's available in /system/lib/modules?"
A. Safe to be root. In terminal or adb
su
insmod /lib/modules/<module_name.ko>
20. "How to know which modules are pre-loaded by kernel?"
A. Terminal or adb:
lsmod
21. "I don't see an init.d folder in my rom. I wanna create some initd scripts. What to do?"
A. Using a root explorer create init.d directory under /system/etc. Set perm 777.
22. "After flashing a new kernel i see there are some stuffs missing from STweaks"
A. Either the support for those missing tunables were removed or just the STweaks interface was removed. The parameters might still be accessible through scripts. Check the file path to make sure.
23. "Does notification LED cause wakelock and lot of drain?"
A. Hm Yes and No. CPU has to wake to help turn on notif led and to turn off when it's timeout. When LED is blinking, no wakelocks are held. Notif led is controlled by a diff h/w and not directly by CPU.
24. "How do I know if my modified charge current settings (using STweaks) are effective?"
A. Use CurrentWidget from playstore. Monitor the reading while charging.
25. "What happens if my smooth scaling frequency is greater than my scaling max frequency?"
A. Smooth scaling will be inactive/disabled.
26. "Can I flash this kernel on a non-international variant - At&T/Korean/Japanese...?"
A. NO. Don't risk 800 dollars. Dev might release different variants for these devices later.
27. "I tried setting a negative value for a symbol using kmemhelper interface. I see the value is not applied properly. What could be wrong"
A. The negative value might be detected my kmemhelper as an argument. To prevent that, use two minus signs (--) before the negative value.
Ex: "kmemhelper t int -n touch_boost_level -- -1" (This resets touch boost frequency to default).
28. "I wanna disable all the audio enhancement stuffs. How?"
A. In your script
echo 0 > /sys/class/misc/scoobydoo_sound_control/enable
29. "Least voltage for a CPU frequency I can undervolt to?"
A. 600 mV. Maximum = 1500 mV
30. "Does sound enhancements in stweaks applies to bluetooth headsets?"
A. NO. Only for wired headphones.
31. "Do we have temperature sensor in our CPU?"
A. YES
32. "I have this habbit of unknowingly pressing home button multiple times and that result in inverting colors on my screen."
A. Disable "mDNIe negative toggle under Screen tab in STweaks.
33. "I sometimes get unexpected reboots. What could be wrong?"
A. Number of reasons.
- Problem from ROM side - wrong dpi setting for an app, wrong build.prop tweaks, etc.
- Too much UV on CPU/GPU
- Too much CPU OC/GPU OC
- CPU/Battery heated up too much because of weather/benchmarking/faulty charger, etc
34. "I want to help dev debug an issue providing a kmsg. How to?"
A. After the problem (random reboot/freeze/lockup), do not pull out battery to recover. Just long press power button so that device can reboot. Then connect device to PC, (provided you have setup adb), type
adb pull /proc/last_kmsg
Save the file as .txt and post in the thread along with description of the problem and possible way to reproduce it.
If you can't use adb from pc, just copy last_kmsg file from /proc directory to internal sd, copy it to your PC and post in the thread.
35. "I'm not able to copy Person X's undervolting settings. Why? Sometimes, across different builds of Siyah, my UV settings are stable in one version and not in another. Why?"
A. One or more of the following
- Every device is different - diff grades of CPU
- CPU drivers might change across different builds
- Power requirements may differ depending on the temperature, altitude or the defaults.
36. "GPU OC/UC range?"
A. 54 to 700 mhz. With voltage range of 600mv to 1200mv at 25mv steps.
more might follow..
Know the STweaks Tunables
You have a custom kernel and an app to control different tweaks. Read below to have a fair understanding of all the sliders and drop-downs in the app plus read some faqs.
Q. "What's STweaks?"
A. It's an app developed by GM to provide a simple interface for various kernel tweaks.
STweaks works using /res/uci.sh interface. (Universal Configurator Interface). Ideally when you run /res/uci.sh config you get an xml file. The app render that XML file to an UI. (The xml is customconfig.xml in /res/customconfig directory)
Q. "Where are profile files (default, performance etc) stored in my device?"
A. /data/.siyah with extension ".profile"
Contents are in the format <tunable> = <value>
Q. "How come STweaks takes a little long to load every time? Other CPU tuner apps like SetCPU opens faster!"
A. Stweaks needs to query the values of ALL tunables from the active profile file, then set the UI elements (sliders, checkboxes, dropdowns, etc) to match the values queried. Only after these it can expose itself for you. So yeah! Some time is needed.
It loads in about 2 seconds now.
Q. "So every tunable possible with SiyahKernel is included in STweaks?"
A. NO. That would make the app complicated and while some users like to have lotttsa tweaks in the app, some users prefer the opposite. So to be fair, STweaks will not be cluttered with way too many options.
For users who know what they're doing, there are scripts, and kmemhelper.
Q. "After flashing a new version of Siyah, I can't see STweaks in my app drawer. Help!!"
A. Using a Root File Explorer, copy STweaks.apk from /res directory to /system/app. Set permissions rw- r-- r--
Q. "I find that after flashing a new kernel version, while adjusting some tunables there's no effect."
A. In the app, under EXTRAS Tab, hit "Reset settings to default". Now reconfigure all your settings. Should be fine in most cases.
Q. "Sometimes, after flashing a new kernel build, i see all my settings are reset to kernel defaults. Is it normal?"
A. YES. It's just so that profile files contains all the tunables matching config XML in the latest build. If resetting is not done, some settings will not work.
Q. "Does that mean - every time I flash a new kernel build, I need to reset settings?"
A. NO
Q. "What should I change in STweaks to have best battery/best performance?"
A. Read below to know what each tunables do. If you still don't get it, don't change anything. Trust defaults. All will be good.
1) CPU Tab
Gentle_Fair_Sleepers:-
This is a CFS tweak. CFS aka Completely Fair Scheduler is your default Task Scheduler. Task Scheduler is responsible to manage task executions - decides what task to execute next from a queue. CFS scheduler tries to fairly distribute the CPU time among all tasks in such a way that each of them gets the same amount of the virtual run-time. CFS maintains two arrays - active and expired. Tasks once served from active array are placed in expired array. When there are no more tasks in active array, the two arrays are swapped. Sleeper Fairness means to consider sleeping tasks similar to the ones on the runqueue and credit the sleepers in a way that it would get CPU as if it were running. With Gentle_Fair_Sleepers enabled, sleeping tasks will get a little bonus time w.r.t to their virtual run time. While this may seem fair in some cases, disabling this tweak may possibly improve UI responsiveness:- may be because sleeping tasks are not given additional priority and the task that's responsible for UI do not sleep while screen is ON.
* Arch_Power:-
Another scheduler tweak. Helps in using specific ARM topology functions instead of generic functions. Benefits may include idle higher number of threads in a core, etc.
* CFS Tweaks:-
Three options which sets different value for your task scheduler's a) Minimum Granularity b) Latency c) Wake-up Granularity
A new "epoch" or a new time origin begins when scheduler swaps active and expired array.
Latency is the length of an epoch in nano seconds.
Minimum Granularity is the granularity of one epoch.
Wake Up Granularity is the ability of tasks being waken up to preempt the current task (5 ms by default). The larger the value the more difficult it is for the task to force the preemption.
- Samsung Defaults:- Leave it as Samsung defaults if you want higher benches.
-Linux Kernel Defaults:- My fav.
-Thunderbolt Scripts Defaults:- Pikachu's tweaks are aggressive low values for parameters. May improve UI responsiveness.
CPU Idle Modes:-
Leave it as Idle+Lpa. AFTR seems to be a difficult world to conquer for i9300.
* Smooth Scaling Level:-
Leave it as 1800mhz (which disables smooth scaling) if your governor has the parameter "freq_step" (ex: Pegasusq). Otherwise, the two concepts may conflict. Use smooth scaling for other supported governors. CPU driver scales CPU to frequency as defined by Smooth Scaling Level before jumping to Max Frequency.
Sched_mc:-
Leave it disabled = 0. 1 will overload first core, 2 will try to save power by biasing task-wakeups to semi-idle core.
CPU Undervolting:-
[Courtesy Andreilux for the info] 32 nm Exynos 4412 on our device decreases the need for higher voltages for transistors to switch and decreases voltage leakage. So they actually successfully switch more of the time compared to SiON on Galaxy S2 i9100 where leakage was big enough to not make a transistor switch and crash the system. In short, this is why GS3 supports higher UV compared to GS2. You might be lucky enough to UV more than 200mv on certain frequencies. Try on own risk.
Max CPU Lock:-
Defines no of cores to be used along with Pegasusq governor. Leave it quad core. You have beast of a phone. This parameter actually changes the max_cpu_lock parameter of your governor - pegasusq or lulzactiveq.
CPU Governor:-
Use Pegasusq.
CPU Max Frequency:-
Sensible OC for our device is 1.5 Ghz. You can try more and see what happens.
CPU Minimum Frequency:-
Use 200 or 100.
2) CPU_UV Tab
Like SetCPU or voltage control, sets voltage per CPU frequency. Note that the values DO NOT represent the actual voltage levels on the frequencies. If you UV in Stweaks and also use SetCPU to set voltage levels, SetCPU will over ride Stweaks.
3) GPU Tab
* Mali Touch Boost Level:-
If this option is enabled to any steps, when you touch on the screen/press soft back or menu keys/press homebutton - GPU voltage is set to the GPU step that match the step set by you here and frequency is set to that step. This may helps in better responsiveness of unlocking via lockscreen, etc. Note that, this doesn't mean GPU is locked to that forever. After one second, depending on thresholds and stepcounts, soon GPU is clocked down or up.
If Mali Touch Boost Level is disabled, GPU resumes at lowest frequency (your first step).
GPU Frequency Steps:-
Now we have frequency steps taken from Korean sources, as hard coded in clock-exynos4212 file. You won't find a formula to calculate valid frequency steps. (Unlike i9100 for which any GPU step was 800 divided by an integer)
GPU Voltage Levels:-
You may be able to UV a little more compared to GS2 if your ex device was GS2. Try and see. (Thanks to 32 NM SoC). Remember that you will know UV was too much only while GPU is being heavily used - like gaming.
GPU Thresholds:-
If you're not sure about this, use default thresholds. Wrong thresholds can cause lags.
* GPU Stay Counts:-
Stay count is the number of Seconds GPU should stay at a frequency level before it can scale up or down, overriding "load exceeds threshold condition". To avoid any possible stutters in gaming, use staycount = 1 second for the last step. May be for 4th step too, just to be sure.
If you don't find StayCount interface in the app, use script.
echo "0 0 0 0 1" > /sys/class/misc/mali_control/staycount_control
From left to right, each digit represents StayCount for lowest to highest GPU frequency steps.
4) AUDIO Tab
Speaker Tuning:-
Check to enable better bass response on speakers. Note that GS3 speakers don't play well with bass (even with open source audio HAL developed by codeworkx for CM10. So if you find sound distorting on speakers, uncheck this option instead of trying to play with some equalizer.
Speaker Amplification Offset:-
Default zero. Increase to amplify speaker volume. At level 5 or 6, speaker is most likely to distort playing ringtones/sounds.
Headphone Amplifier:-
Volume boost for your headphones. Level 0 = -57 dB. Level 63 = +6 dB which is the hardware maximum. Please take care of your hearing.
3D Effect:-
Stereo expansion may tighten the stereo field. In general, there are multiple techniques to achieve surround effect/3d effect/stereo expansion effect.
3D Effect Gain:-
Valid only if 3d effect is enabled. Higher value may not sound pleasant to most ears. 2-4 should do.
EQ Presets:-
Use inbuilt presets or use graphical equalizer bands to tune the 5 band equalizer.
Graphical Equalizer:-
The five band equalizer(with a range of -12dB to +12dB) is a hardware equalizer. So it controls all the sound coming from your headphones. Software equalizers such as inbuilt EQ of powerampp can only control the sound output 'formatted' by this 5 band h/w EQ. As you know, the first two bands - Lows/Bass. Middle one - Mids/Vocal and last two bands for - Highs/Treble.
Negative Digital Gain:-
Or dynamic range. Increase this to prevent distortion. It defines how much volume is to be digitally reduced from headphone amplification level.
FLL Tuning:-
Aka Anti Jitter is an audio enhancement technique as an internal clock optimization to reduce noise and produce a better quality sound.
DAC Oversampling:-
Increases dac oversample rate for a 48 khz rate and produce better outpund sound.
DAC Direct:-
Aka DAC ME, Bypass analog channels and redirect sound directly to output.
Mono Downmix/Force Mono:-
Force mono sound even if source is stereo.
5) SCREEN TAB
* MIN_BL, MIN_GAMMA, MAX_GAMMA:-
In simplest form, set this higher to have lower brightness at bright conditions on automatic-brightness settings. And vice-verse.
We have lowest brightness for a brightness level read from sensor less than min_bl. Any level higher than min_bl will be linearly mapped to min_gamma:max_gamma to interpret brightness of the display. Difference between min_gamma and max_gamma along with their values affect overall brightness response curve.
mDNIe Sharpness Tweaks:-
Makes thin fonts more readable. You're most likely to see weird display if you disable this option.
mDNIe Negative Toggle:-
If this is enabled, quickly pressing home key four times will invert all the colors on your scree. Useful for ex: Reading a webpage in the dark which has white background by default. By inverting colors to make it black, your eyes will strain lesser, plus it saves battery in such cases.
Touch Boost Level:-
Defines the frequency to which CPU is instantly ramped up to when we touch the screen. Advantage? UI responsiveness. Setting this too low might be a v bad idea on some devices.
Slide2Wake:-
If enabled, slide on screen in a straight fashion from left to right to wake your device. Helps prevent wear down of physical home/power buttons. If in doubt this drains more battery, leave it disabled.
FB Early Suspend Delay:-
Early suspend delay to run CRT off animation. If you're sure that Settings > Developer Options > Windows Animation Scale is 1x or higher (not 0.5x or off) and still can't get CRT-off animation to work, set this param to 100 ms or so.
6) MISC TAB
Android Logger:-
Enable disable android logger. Logger hardly uses any extra battery, and will be very useful if to pull a log after a crash or freeze. Leave it enabled.
* Insecure Adbd:-
Enables to run your Android Debugging Bridge Daemon (adbd) in root mode by default. Use "adb remount" command in a terminal to mount /system as r/w.
I/O Scheduler:-
Use any among deadline/sio/noop.
* Zram Size:-
Compressed swap space aka compcache aka zram allocates defined amount of space from your physical RAM as compressed swap space. You can debate all along to see if zram is useful on a fast device like GS3 with a fast flash storage inside. If in doubt, disable this option.
Notification LED Behavior:-
Force blinking/fading of notification LEDs. Useful for Sammy based roms. (aosp roms has blinking/fading setting inbuilt).
AC Charge:-
Charge current from your wall charger. Increase the value for faster charging at own risk. If you see currentwidget app displaying only 800/1000 mA (when you have set 1200 mA in stweaks) while connected to car charger - it's because the charger can not output more current than that.
USB Charge:-
Charge from usb charger. Increase at the risk of possible damage to PC motherboard. (if it's an old board)
Discrete Wakelock Status:-
Helps betterbatterystats app to report deleted and non-overlapping wakelocks. You may see new wakelocks like your mailclient-inbox-sync, etc if this option is enabled.
Remove Root:-
Some apps detect root and refuse to work if found (certain banking apps for example). To remove root, click this button, run your app and re-enable root when you're done.
Auto Install Root:-
Tries to install superuser apk and binary. If it fails, download latest superuser flashable zip from here and flash in recovery OR download SuperSU from playstore.
6) DUALBOOT TAB
Reboot into 2ndRom Utils:-
Reboots to alternate recovery where you can configure and play with dual boot options. This doesn't change your cwm recovery, but just runs an alternate recovery.
Reboot into 1stRom:-
As it says, reboot to 1st rom without displaying a timeout.
Reboot into 2ndRom:-
As it says, reboot to 2nd rom without displaying a timeout.
No boot logo:-
Check this to disable Siyah bootlogo displayed during dual-boot rom selection time out. (If you're dual booting, logo will be shown anyhow)
Default Rom:-
Specified the default rom (among 1st and 2nd) to which device will boot into, if no keys are pressed during boot. If 2nd rom is default, pressing home/vol down keys will boot 1st rom.
Hijack Recovery:-
We know the second rom utilities aka embedded recovery is a part of the kernel - it holds the same partition as kernel. You can use this button to flash the embedded recovery to main recovery partition (overwriting your existing recovery) so that 3 button method/booting to recovery using extended power menu will take you to Siyah recovery. This is NOT a dangerous operation. You can flash cwm/twrp recovery anytime if you need another recovery.
7) EXTRAS TAB
Reset Settings to Default:-
Reset the profile file, and resets all values in device files to kernel defaults.
Check for Updates:-
Checks and downloads a new build.
Flash Kernel:-
Flash a .tar kernel. Alternative to Mobile Odin!
* Indicates tunables removed from STweaks as of now.
Flashable Zips
Update: Find sample Stweaks Profiles as flashable zip here. http://forum.xda-developers.com/showthread.php?t=2034981. Profiles after flashing will be available in the profile app.
Here are 5 Governor Tweaks scripts as flashable zips.
Flash remove_governor_tweaks zip to remove init.d script that contains governor tweaks. One governor zip can be flashed over another and it will just replace the previous. All governor tweak scrips contains tweaks for pegasusq and luzactiveq. Gamerstweaks is also a governor script that's similar to extremeperformance script but does some additional GPU tuning (for which there is no interface in Stweaks) to enhance gaming experience.
Since order of execution is like this:-
1) STweaks applies its settings
2) Init.d scripts are executed
3) Apps such as SetCPU applies its "set on boot" options,
Script applies the tweaks to the governor selected in Stweaks (depending on if it's pegasusq or lulzactiveq). So if you want pegasuq tweaks to be applied, make sure pegasusq is the default governor in stweaks, and same for luzactiveq.
I will keep updating zips while new kernel builds are released - if it changes any tunable.
DualBoot FAQs
Dual Boot FAQs
* "Alternate Recovery" or "Embedded Recovery" is embedded recovery that's the part of kernel since 1.7.x versions when dual booting was introduced. It's the recovery you boot into using "Reboot to 2nd Rom Utils" in STweaks.
"Regular Recovery" or just "Recovery" is your CWM recovery in recovery partition (/mmcblkp06) which is accessed by 3-button method or "boot to recovery" in the extended power menu from your rom.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, FM radio and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before. And if you don't want to see the Siyah logo as well, create a .nobootlogo file without any extension or content in internal SD.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p10 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Special Cases:-
5) Use an existing nandroid backup as 2nd Rom (and existing rom as 1st)
6) Use an existing nandroid backup as 1st Rom (and existing rom as 2nd)
Prerequisites for any setup is
a) Flash latest Siyah
b) Atleast 90% battery left.
c) 2 GB free on internal SD.
d) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Hit "Run 2nd Rom Utils" in Stweaks app from your current rom. This will run the embedded recovery in the kernel. Under dual boot options, wipe 2nd Rom data and cache+dalvik. Format 2nd Rom System.
ii) Using install zip to 2nd rom option, flash aosp rom as 2nd rom.
iii) Fix 2nd Rom permissions
iv) Flash Siyah again
2) Present sammy, setup aosp as primary:-
i) Hit "Run 2nd Rom Utils" in Stweaks app from your current rom. This will run the embedded recovery in the kernel. Under dual boot options, Clone 1st Rom to 2nd Rom.
ii) From recovery (your default cwm recovery which can be accessed from extended power menu or 3 button method), full wipe and install aosp rom zip as you'd normally do when you were single booting.
iii) Fix 2nd Rom permissions
iv) Flash Siyah again.
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first Rom, flash sammy.
5) Restore the nandroid backup using "Restore as 2nd Rom" option in the embedded recovery. If there are problems while restoring, wipe 2nd Rom data, cache+dalvik, format second rom /system and try restoring.
6) Clone 1st Rom to 2nd Rom from embedded recovery then restore nandroid backup from your regular cwm recovery.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure to fix permissions of second rom after setting up 2nd rom for the first time or else you're likely to see a black screen.
- If Wi-FI on aosp doesn't work, flash a sammy ICS rom (on to 1st rom or second rom depending on location of aosp) before flashing aosp rom.
- If NFC doesn't work, flash that NFC fix zip you can find on XDA which replaces ICS NFC firmware on aosp with JB NFC fw from sammy.
- Even if you're installing second rom for the first time, wiping data and cache+dalvik of 2nd rom and formatting system of 2nd rom is necessary; As it creates empty 1.5 gb system.img to be used as system partition for 2nd rom and also creates data directory of second rom in /.secondrom dir in the internal sd.
6. "How to boot into primary rom?"
A. Wait for the 3 second timeout or press volume up/power to skip the timeout. Or use the option in Stweaks if you're booted into second rom already.
7. "How to boot into secondary rom?"
A. During the 3 second timeout, press volume down or home button. Or use the option in Stweaks if you're booted into 1st rom already.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest Siyah.
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from recovery. Flash Siyah again if Rom zip flashed another kernel.
14. "How to flash newer version of 2nd rom?"
A. Using stweaks, boot into 2nd Rom utils. Flash the rom using "Install zip to 2nd Rom" under dual boot options. Flash Siyah again if Rom zip flashed another kernel.
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. You can use any recovery. Alternate recovery can be just run using the option in STweaks.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see Stweaks app in second rom."
A. Delete /system/.siyah/stweaks-installed file in 2nd rom. Reboot to second rom.
20. "Do I need to anything special before flashing a newer Siyah?"
A. NO. Just flash kernel as tar or in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition.
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. While on 1st rom, copy the file /data/.siyah/default.profile to /data/media/.secondrom/data/.siyah directory. If you modify STweaks settings in 2nd rom and want to avail same settings on first rom, do the other way around. (Copy "default.profile" from /data/media/.secondrom/data/.siyah to /data/.siyah while on 1st Rom)
22. "How do I remove everything related to DB and run single boot again?"
A. In recovery, under dual boot options - "delete 2nd Rom". OR Delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Reboot to 2nd Rom Utils" in STweaks change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings. Using extended power menu or 3 button method, you always lands in your own CWM recovery.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the feature embedded recovery, which can be accessed using "Reboot to 2nd Rom Utils" in STweaks app.
28. "I booted into recovery using 3 button method. But some dual-boot options are not working even though dev said they're implemented.
A. Use "Reboot to 2nd Rom Utils" in Stweaks app to boot to embedded recovery.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p12 = /data
mmcblk0p9 = /system
mmcblk0p8 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk10 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p12 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p10 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Nice! I like your work on Galaxy S2 hope to see you here often and regulary updating your thread.! well done mate
Sent from my GT-I9300 using XDA
Thanks my friend
Inviato dal mio GT-I9300 usando Tapatalk
energie said:
Best kernel ever finally
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
Absolutely
Gesendet von meinem GT-I9300
gokhanmoral said:
last one
Click to expand...
Click to collapse
This is gonna be HUGE!!!
Thanks GM
Sent from my GT-I9100 using XDA
+
siberian tiger said:
This is gonna be HUGE!!!
Thanks GM
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
fully agree ...now i am using 0.94 and no problems at all
PS: just a USB Mass Storage is only little thing i miss...but DropBox and FTP are ok too
Looking forward to this. Using 0.94b now and it is oh so smooth. I'm sure 1.0 will be even better.
Cheers gokhanmoral.
/love....
Many thanks, the best kernal ever, is the focus on battery life on this release? can the kernal fix the high cell standby issue? i believe my device will keep your kernal until i sell the device !
Thank you
WOOT!
Where is the download link I opened the link above but there is no 1.0 only hv 94
Sent from my GT-I9300 using XDA
ThisIsIt...
saberzaid said:
Where is the download link I opened the link above but there is no 1.0 only hv 94
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
compiling now.. I will edit the blog post after editing the first post in this thread.
As I tested v0.92b, this kernel is very promising ( of course because of Gokhan ) but not yet stable. I love to see @gokhanmoral progress like sgs2 kernel .
I will test v0.94b right now .
{
"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"
}
xTraFactory
100% Stock Odex Factory IMG debloated from optional Gapps , Systemless Root and No Force Encrypt
This rom is created on 100% stock factory.img with the intent to optimize extremely performance and battery consumption without altering the originality.
With xTraSmooth you will have a stable rom like the original factory.img of google, you can leave safely traveling with my rom without risking blocks or problems.
This is my daily rom for nexus 5 uploaded for you at the request of some xda users.
I plan to regularly update xTraSmooth and give support to all users if necessary.
My ROM is a official Nexus 5 factory.img with maximium optimization.
Do not just read the build name, just my xTraSmooth currently offers a 100% stock-based on official factory.img, where they were introduced all optimizations possible without altering the originality and reliability.
Now I work with a Team of my community users and xda users for built all Nexus's xTra Rom.
This group of developers has been called xTraTeam.
You can read the ROM developer on build info on AFH.
xTraROMs Official Google Plus Community
xTraROMs Official Facebook Community
xTra Rom's has 3 priority:
- Stability on long time.
- Speed
- Battery.
xTraFactory
Features:
Android 6.01
xTraFactory MMB29K Hammerhead
- 100% Stock MMB29K 6.01 Factory.img debloated from optional's gapps.
- Stock MMB29K Kernel
- Reduced running services and improved ram usage
- 100% Clean System Aligned with new Systemless Root
- No Build Name this is a 100% Factory.IMG flashable ROM.
- Supersu 2.64 included in the zip , auto root and patch stock kernel with new systemless Root.
- Fully Odex system/app , priv-app and data/app
- Super Fast and Stable 4 Daily Driver
- Disabled ADS on browser and apps
- Compatibile with xposed framework
- Compatibile with all Layers themes
Data Wipe Factory Reset is required , without it layers not work properly , use titanium in future for backup your apps and your data apps.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
Bugs:
Ahha Ahha Ahha Is a joke .
No bug here.
This is a daily driver rom, stable as the stock, maybe even more.
**What is ODEX and DEODEX?
TL;DR:
Odex = More speed__Less customization
Deodex = Less speed__More customization
Extensive explenation:
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These odex files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applicationsdifficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating theworry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
I think that you like more speed and less customization (less costumization for dev because is to difficult mod an odex file) and for this reason you press thank and download my work!
Another explanation is this:
If you use a odex rom, you'll have also more space in data (this is important because if you don't have partition ext4 in sdcard, you won't have too free space), increase battery life, more stability and increase perfomance( the Rom is more faster to load system and app) but you can't modifie apk after odex (you can't mod program with classes.dex).
Infact ODEX is an OPTIMIZED-DEX and Android load system and app faster than deodexed (DEOPTIMIZED-DEX) app and system.
When you have a deodex file (a lot of roms are deodexed) you have File.apk in system/app and in data/dalvik-cache [email protected]@[email protected], but with odex file you have File.apk in system/app and File.odex in system/app
Advices And Tutorial For xTreme Battery Life , Custom DPI , manually set Speaker Boost , manually set Earphone Stereo Boost and Increase touch response.
Multi DPI
This rom from 2.7 and up is Multi DPI if you can't see some app in PlayStore or any apps is incompatible with your device, go to my folder and download latest Multi DPI Gapps.
Simple App For Chance Display DPI
Tutorial to manually set Speaker Boost and Stereo Earphone Mod Boost.
1) Download a Root file manager personally use solid explorer, the best ...
2 Go to the following location / system / etc and look for the file mixer_paths.xml
3) edit at will the two strings highlighted with values from 88 stock to 95 +7 Boost
- ctl name="RX1 Digital Volume" value="0"
- ctl name="RX7 Digital Volume" value="88"
RX1 = Earphone (Set 0 to disable it)
RX7 = Speaker (88 Google Stock Value)
With the set values should not be a problem for 95% of users, however, have some nexus defective speaker that with the default values do not highlight this issue .... The stock ringtones are of poor quality, the board before changing these strings to try with audio 320kbps or HDAudio ....
Increase Touch Response:
- Set all animations to developer options at 0.5 to substantially increase touch response;
To drastically increase the battery life:
The system and the kernel need some charging cycles / days of adjustment, Android finished its first installation starts to sync your phone with google server, load the images in the gallery, sync contacts and so on.
My nexus with this rom and FKU beta with power saving profile consumes with good coverage and wireless network,10% of battery with 1 hour SOT.
There are too many variables that affect the battery, cpu temperature, ambient temperature, humidity, mobile network signal, synchronization in the backgroud, applications in your device, so it would be extremely difficult to judge your consumption without knowing all these things.
How to reduce battery consumption and exceed 6h Screen On Time with xTraSmooth Rom.
1) CPU
To simplify the set-up of the CPU the application FKU integrates three custom profiles that allow you to automatically set all these parameters to suit your needs. However for those who wish Further, use another application or manually change these parameters I provide these simple advice.
- Undervolt, this practice serves to reduce the overall heat of exercise and consumption of the CPU.
A CPU that uses the correct current is still more stable compared to a CPU which uses the standard tables set with average values adapted to all CPUs.
Each CPU is different so you need to calculate their boards UV.
To calculate their boards UV is necessary from a global base of -25 or -50.
Working frequency by frequency by setting the same value as the minimum and maximum frequency and disabling start at boot is that the frequencies of the voltages.
Example set the frequency 300 MHz and 300 MHz as max as min, get off gradually with small steps -5mv until you find the limit, when you restart pinned the value of a piece of paper or on the notepad.
You will find the limit, now set 5/10 mv more and you will have your first value of the table UV.
Now proceed so for each frequency using a moment smartphone before you jump to conclusions.
These values can not be adapted to each kernel, but you will have to redo this procedure for each kernel. Without this you will have your tables UV ready and saved as in my case on google keep.
- Use a frequency that allows to work with a low voltage, in my case a frequency ranging from 1036 MHz (765mv) 1267 MHz (795mv)
- Hotplug limit work on Core 2, setting the use of the 4 Core when the load reaches 99%
- Touchboost on kernel using the touchboost set to values less than the maximum frequency, such as 1267 MHz maximum frequency and touchboost with values between 883 MHz and 960 MHz.
- Hi speed freq set the same frequency as the touchboost.
- Limit the GPU working frequency between 200 MHz and 320 MHz
2) Android
- Disable Geolocation
- Turn off system sounds
- Disable vibration to the touch and keyboard
- Disable adaptive brightness
- Use a brightness value between 5% and 10%
- Manually set in 2G if you are in areas with little signal and if necessary set airplane mode.
- Disable use mobile data and set 2G when using WiFi.
- Use a few applications that use push or remain active in the background, in my case use whatsapp, facebook stable, tapatalk and FKU beta.
- Do not change rom or kernel continuously will make continuous wipe system.
Android is that the kernel need a period of adaptation and some charge cycles to work properly.
- Use a few gapps to reduce app in sync automatically or disable synchronization of the app that you use in the shortest way, and that you do not need a synchronization between multiple devices in real time.
Many gapps have a web version app that saves space in SD and have less app in sync automatically.
- Turn off Google Now
- Deactivate Ok google hotword
- No close the app by recent, open and close the app to continued increases fuel consumption and reduces the fluidity of the system, lollipop has a system like iOS and works well with all the app open.
- Do not use greenify sharply reduces the fluidity of the system and increases the overall consumption.
- Do not use task manager to free up RAM.
- Do not use the Clean master plan to avoid unnecessary.
- Do not use snapdragon battery guru or similar programs that promise lower fuel consumption.
- Avoid heavy 3D games and games continuously running type clash of clans, Simpson, etc. etc.
3) Battery
- With modern lithium battery is not advisable to go below 20%
- Lithium batteries like short courses of charge, does not always pay full charges from 0 to 100, but prefer partial charges.
- 1 charge cycle means from 0 to 100 so if charge the battery from 50% to 100% will have carried out a half charge cycle.
- You can even connect the battery to charge a 10% charge, I repeat the lithium batteries do not damage unplugging and plugging the power supply but working with infeririore charge to 20%.
- Perform a complete cycle 2/3 times in 1 year from death and charge off up to 100%.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
Delta Update:
When is possible i'll release a small delta update, to avoid that you have to download the full rom, recommended xTraSmooth Updater for best OTA experience. They allow the upgrade of your xTraSmoth on the go in 4G \ 3G.
Installation instructions:
Instructions For xTraSmooth and StocK
-Dirty flash on you rom, the script perform an automatic wipe cache
FOR M BUILD USERS IS NECESSARY START FROM ANDROID M2 FACTORY , FROM LOLLIPOP THERE ARE MANY BUGS.
INSTRUCTIONS
- FLASH BY TOOLKIT MPZ79M
- FLASH TWRP
- FLASH DIRECTLY MY ROM
- BOOT
CHROME SINCH NOT WORK ON M2 , FOR FULLY WORKING CHROME DOWNLOAD LATEST CHROMEDEV.
Downloads:
xTraFolder
https://www.androidfilehost.com/?w=files&flid=20898
Donations
A special thank you to those who appreciate my work and decided to contribute to the project.
Thanks to all donators, You are the people who push me to continue my work.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
Acknowledgements
First my work friend
- Prempal Singh my xTraSmooth Partner Great App Developer
- Cristiano Spada aka @CriGio Best Themes Developer and app icon designer
- Google
- franciscofranco
- flar2
- hellsgod
- tassadar
- sshafranko
- chdloc
- Adr990
- badboy47
- david279
- GtrCraft
- guerreromanuel
xTraSmooth Signature
daniel84cs said:
no root for best performance e more battery life ;
Click to expand...
Click to collapse
I lol'd, oh well goodluck with the rom
Sorry it was my mistake edit it.
Thanks for your job, :good:
Guys could you help me, I can not make the title bold :crying:
daniel84cs said:
Guys could you help me, I can not make the title bold :crying:
Click to expand...
Click to collapse
Sorry can't help you I'am noob and I never open thread on XDA but I wait for a link to download and try your rom. I new rom is always be welcome on XDA. Thank's to work for the Android community and Good luke :good:
Thank you, upload the rom is 33%, as soon as possible up on other file hosts.
Hi I'm on cyanogen 11 right now all I have to do is that download your ROM ,,, do full wipe ,,, and install ?
Am I right ?
Thanks Daniel
B.E.H.N.A.M said:
Hi I'm on cyanogen 11 right now all I have to do is that download your ROM ,,, do full wipe ,,, and install ?
Am I right ?
Click to expand...
Click to collapse
Yes....
- full wipe
- flash the LPX13D modem on OP ,
- flash supersu
- reboot in rom
For sd bug this is because 4.4.x seems to point to: storage/emulated/0 & L points to: data/media/0 :
- root by supersu zip
- download terminal emulator from playstore and run :
su
restorecon -FR /data/media/0
For remove root dirty flash my rom .
For future update no sd bug fix is not necessary.....
upload is at 66%
Can you make advanced reboot?
It is currently not possible, I look forward the final version of Lollipop, there may be other changes. Mine is a stock ROM that optimized use every day. Flashing my ROM has the same effect as flashing the stock LPX13D by toolkit, except that I tweaked slightly around to my liking.
An temporary alternative to advanced power menu
https://play.google.com/store/apps/details?id=com.scartech.hololightreboot
Ok, thanks you.
ROM is online on mega...
https://mega.co.nz/#!gNgXzJLD!eu4PqiaIfQEnENnRtdUZUccyN2GGT36ergrlFkxSHso
DevHost in uploading
thanks for creating another Android L ROM
any chance of exchange services being added as POP and IMAP are not good for me when connecting to my work email.
other than that, so far looking really good and fast
@AirwolfUK
Test this.....
http://forum.xda-developers.com/android/apps-games/app-gmail-5-0-t2912373
With Franco Kernel, does not have the "No enough space to install" or no folders thru any file explorer?
No....
Read the original OT, the "no SD bug" not is a problem of franco kernel.
My SD work fine...
This is my daily ROM....
As for those who want to set the SELinux to permissive is an application which lets you toggle, https://play.google.com/store/apps/details?id=com.mrbimc.selinux
daniel84cs said:
No....
Read the original OT, the "no SD bug" not is a problem of franco kernel....
Click to expand...
Click to collapse
Yes, i used that App to change to permissive when flash FK or CodeBlue on Sykopompos rom... nice, i'll give it a try to your rom
I'm going to create update.zip to update the rom when I make small changes to make sure that you do not have to download the whole ROM every time. Of course also put the full version ...
Now I'm going to sleep, I awake from yesterday, in Italy is 3:33 pm ..... almost 24 hours a day online for work-related reasons. Whatever you need we will reply when I wake up.
☆☆[ZIP] [GUIDE] NOTE 4 - KERNEL Profiles and Tweaks [Simple, Easy] [5 Jan] ☆
NOTE 4 Snapdragon Kernel-Tweaks
*Post 4 Updated with profiles zip , but don't forget to read
Hello fellow Note 4 users and all other who have a device with a Snapdragon 805 SoC , Ever since I made the Nameless Optimizer for our Nameless ROM , there was a lot of requests for making it available for all ROMs , I wish to express here that such a thing is impossible without modding the whole ROM , but I'll guide you to use some important tweaks that would make a DIFFERENCE
CONTENTS
1. Introduction and Credits
2. The Guide
3. The tweaks
4. Profiles zip (NEW)
5. RAM Manager (*NEW)
6. Troubleshooting and FAQ
Optimizing the CPU
I am sure you have always wondered whether it is possible to have a better battery life without sacrificing performance ,
I won't say its magically possible to get 10 hrs sot with ultra-heavy usage...
But if you follow this guide carefully/use these profiles it would much better than what u have ever had on your Note 4
Contributors
@Senthil360
Google+ : Find Me Here
My sincere thanks to
@Crimsonthunder for adding things in kernel and helping me,
@Pafcholini for that incredible touchboost option , and lot of other helps
@friedrich420 for AEL kernel
@psyntific and @F4uzan for testing the values
and my whole Nameless Team
Note to users : Be helpful to each other , use this thread as an opportunity to enhance your knowledge in kernel tweaks, I sincerely expect this thread to be filled with any/all sorts of tweaking doubts , so before posting something, kindly hit the search button
Ok lets cut to the chase
So I want to mention here three things which affects the battery and performance
1. Screen Brightness (affects only battery) - Well it depends on our personal usage , and we can't do much regarding that
2.Apps , services , background tasks- These topics have been discussed a million times here on XDA , disabling services , amplify , greenify and infinite other things...
My personal settings are
Greenify - Yes - (most of the data dependent user apps ,excluding system apps)
Xposed -No
Sync - Occasionally
Location - Disabled(default)
P.S - I use a greenify widget at homescreen to hibernate time to time
** I will provide the custom lmk values below
3.CPU frequencies and Voltages
Ok this is the most important thing that we are going to discuss here,
This is for INTERACTIVE and Interactive based governors.
Most of us use Interactive and interactive based governors because its the most reliable and its good balance between battery and performance , but actually it could be improved way more than how it behaves at default state...
The Problem
The most annoying feature of this governor are
1. It spends unnecessary time at higher frequencies draining too much battery
2. At times it stays at lower freqencies when we need that sudden burst , instead we only see stutters and delayed app opening/loading
These silly behaviour is what we are going to change (Note : Tested with following kernels , NL (not official), Emotion and AEL)
A Comparison
Take a look below in these screenshots, the first one is without tweaks ,
{
"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 is below is tweaked interactive
** Tweaked interactive has more battery life and performance than default **.
So now after those screenshots you might be wondering , yeah I see a bunch of frequencies being used , What's the deal?
Here's the answer, what we are going to do , we are going to instruct the CPU to use frequencies according to the situation ,cleverly to improve battery life without sacrificing performance.
** Here CPU = Governor + Hotplug
For example consider the activity of *Loading and reading a webpage*
Default interactive behaviour :
Opening browser : 2649 Mhz
Loading : 2649 Mhz
And while u look at screen , without touching - it scales to 1574 Mhz every 2 secs for no reason
Scrolling webpage - It will start with minimum of 1574 Mhz at 2 cores and reach 2649 Mhz
Damn thats too much...
**Tweaked Interactive Behaviour :
Opening browser : 1190 to 1497 mhz
loading 729 mhz to 1728 mhz on each core (depending on load of webpage)
looking at screen : 300mhz to 499 mhz
scrolling webpage : 729 to 1190 mhz across each core ( it will increase depending on ur scrolling speed )
That was just an example for Browser , but it is optimized for every activity, right from listening music in idle to Playing a hd game )
The Solution
"Really? But How?" you might ask , lol
** A) Well first of all, you might not have heard a dumber thing than this, Samsung had put tons of Exynos value on the snapdragon variants which we are going to deal with (Note : stock exynos values may have beem removed in custom kernels)
** B) Next , here is the golden formula
Power consumption = (Voltage^2) × (Frequency× no of cores)
**(Actually the real formula also needs to be multiplied with the Capacitance of SoC but since it is a constant it is insignificant in this formula)
Alright what that means , To put it simply More cores with LESSER frequency is MORE EFFICIENT than lesser cores with HIGHER frequency
Yeah that's right,and huge thanks to @psyntific for helping with me during all tests irrespective of Night or Day
See these calculated values,
For 2649 ghz at 2 cores
(1080^2) × (2649 × 2) = 6,179,587,200 (i)
Similarly for 1497 at 4 cores
(890^2) × (1497 × 4) = 4,743,094,800 (ii)
Dividing (ii) by (i) , we are saving 25 % at higher frequency, but as i said above this saving is much more in other cases , i.e Browsing , scrolling , app opening
C) Tweaking more cores to start scaling up from lesser frequency
This is one other important tweak , the holtplugs are tweaked in such a way that they will give priority to using more cores rather than frequency while task is increasing and shutting down much better while task decreases , infact its a combination of governor and hotplug tweaks
D) And tons of more governor and system tweaks like Boost duration, frequency sampling/polling rate (Every milliseconds makes a difference) , pardon me its impossible to mention everything here , I'll add it in the tweaks section
Oh have to mention this,
However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance.*-*Chainfire
Phew and now that you are ENLIGHTENED , let's proceed to the easier tweaking part
The Tweaks
Required app : Kernel Adiutor (special build for Note 4 by @Pafcholini)
Find it here :
https://mega.nz/#!JgMjBLab!m1Hgm0S0Xs-YqN5PM5wkmREndb_QsLsNLH66yzo3bj0
☆ 1. Interactive based -performance and battery
Hotplug tweak
* Disable all other hotplugs
*Enable MSM Mpdecision Hotplug (at bottom)
* Minimum CPU online = 2
* Maximum CPU online = 4
* Max Cores Screen-off = 1
* Idle Frequency = 960 Mhz
* Start delay = 5000 ms or lesser
* Delay = 75
Interactive tweak
Follow the same order while tweaking and do exactly as described , otherwise it won't work
* Set governor to Interactive
* Disable scheduled workqueues
*Disable cpu-boost unless absolutely necessary
Open governor tunables and change the following
*(Note for Emotion users) If bk_locked is 1 change it to 0 before tweaking and then for making the new values stick change it back to 1
* boostpulse_duration = 80000
* go_hispeed_load = 95
* hispeed_freq = 499200
* input_boost_freq = 960000
* min_sample_time = 100000
** target_loads = 98 422400:15 729600:30 1190400:35 1344000:40 1497600:55 1574400:60 1651200:65 1728000:75 1958400:85 2035200:90 2265600:95 2496000:98
(just copy paste lol)
* Now above_hispeed_delay = 20000 1497600:40000 1728000:30000 1958400:30000 2035200:15000 2265600:20000
== If above_hi_speed_delay does not stick copy and paste these values in /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay , save the file and change its permission to 444 to prevent overriding
CPU Voltage tweak
* Decrease global offset by 40 mV (Minus 40 mV)
==========================
Other recommendations
* Intellithermal ON (for gamers)
* I/O scheduler cfq
* KSM OFF (u really don't need this )
* Software CRC control OFF
That's it for now so simple right , more guides technical info will be added later
Even though my intention was to teach you and help people to make thier own tweaks, its proving to be difficult for few or some don't have much time
So now I share my profiles as a falshable zip , you can use it , as it is or as a base to make your own settings , somehow I hope this will be helpful to all the users. Good luck
1. Marshmallow
2. Lollipop
MM kernel based
PROFILES-V4 StableRelease date : 12 / Jun / 2016
These profiles were tested on
* Nameless Kernel 1.2 MM edition
Download here
Spoiler
https://www.androidfilehost.com/?fid=24580943222146101
LP kernel based
PROFILES-V3
Release date : 06 /Feb/2016
These profiles were tested on
* AEL 8.4
*Emotion RC23 & 24
*Nameless V7
Download here and flash from recovery
https://www.androidfilehost.com/?fid=24399994186369309
PROFILES-V2 StableRelease date : 18 /Jan /2016
These profiles were tested on
* AEL 8.2
*Emotion RC23 and 24 betas
*Nameless V7.0
Download here and flash from recovery
https://www.androidfilehost.com/?fid=24369303960687778
PROFILES-V1 StableRelease date : 05 / Jan / 2016
These profiles were tested on
* AEL 8.1
*Emotion RC23
*Nameless V6.0
Download here and flash from recovery
https://mega.nz/#!V9M0kDCI!yc8T4T7-S5BoDwTaboYtODkWn4sdRrLxHUIRLTD5eBQ
The profiles here have few additional codes for settings that are not available in UI of Kernel adiutor , so for full functionality apply after each boot manually. For those who are wondering if these profiles are just the result of changing few settings like governor , hotplug . Its not that and in reality its much more complex, It involves things such as ,
*Going through committ changes of each kernel to make best use of the available features.
*Calculating tunables for governors ,I/O schedulers ,Hotplugs based on the complex algorithms ,formulas that govern them
*Applying these knowledge for our device considering the real-time usage and the interaction between Cpu,hotplugs,schedulers,VM,LMK ,/proc/sys values /sys/module and a lot of other things.
What you see in app is just what the app allows you to see
*Setting up tasker for set on boot :- http://forum.xda-developers.com/showpost.php?p=64875576&postcount=261
RAM Management
So without further delay let me start with the LMK (Low Memory Killer) parameters
1.Foreground Applications - These are the the current applications that you are using in front of your eyes , For example the browser while you are browsing
2. Visible applications - Let's say after downloading something using browser , it loads another page in the meantime you open the file with a file manager, Now here the Browser is Visible Application and File manager is Foreground application
3. Secondary Server - The components of UI and launcher fall in this category
4. Hidden Applications - This one is little anamolous , the apps which are not running currently visibly like the browser or file manager i mentioned above , but these are the apps that run in background and live on RAM (some are essential, some are useless (bloat) )
5. Content Provider - We can call these linked apps , for example when pressing a number in whatsapp , the dialer comes up here the dialer app is content provider for whatsapp
6. Empty Applications These are needless apps just running and living on RAM which can be killed
Ok Now let's see what happens with the values we set..
To put it simply , suppose say we set the values as 88 , 110 , 132 , 164 , 176 , 220 respectively for the slots 1 to 6 .. (Note 4 5.1.1. Default values ) ,
Lets take the 132 , 3rd slot for example , I said the 3rd slot i.e 'Secondary Server' holds things such as UI launcher related stuff ,
That's Ok but what the hell does 132 represents ? It is nothing but a parameter which tells the system to always keep the 3rd slot a minimum free available memory of 132 MB , so when you try to add more launchers or UI stuff see lags because the system is killing/struggling to keep 132 mb free but you are not allowing it to settle by overloading stuff , you may ask then why can't we simply reduce that value so that it can survive ,
That's right way to think but the problem are
1. To keep android stable the lmk values should be in order i.e 1<2<3<4 <5<6
2. When you reduce these values RAM is piled up with loads of apps which will have negative impact on battery and performance ..
So which way to go , what's the ideal solution , before we discuss that let mention a few more things ...
* The RAM management is completely different in Touchwiz (poor) and Aosp/cm (good) - Samsung has tons of bloat apps , services processes which are like a parasite on the RAM
*Note When i said System keeps a minimum of 132 mb for secondary server it doesn't mean 132 mb out of whole RAM
** Total Availble RAM is NOT the same as Total physical RAM
** There are things such as overcommitt ratio , memory , low watermark to consider which is too much tedious to discuss here right now
** Lastly locking app in memory or assgning oom (out of memory) score to apps are not possible since kitkat due to changes in Android Run Time (ART)
With these points in mind lets proceed to find out the working method to improve our Note 4's RAM management
If you have read all the points , I guess by now you might have an idea of what does what..
Generally,
The first three control multitasking
The last three, can be increased to free up RAM
** NAMELESS Users need NOT use any values , I have intergrated special formula and mechanism inside ROM for scheduler and RAM management
LMK values
Default 5.1.1 - 88 , 110 , 132 , 164 , 176 , 220
Multitasking - 48, 56 , 64 , 110 , 132 , 166
Balanced - 56 , 64 ,82 , 194 , 250 , 305
Gaming/ Aggressive - 32 , 64 , 128 , 250 , 470 , 512
Thank you , thats it for now
* Setting up tasker to apply profiles on boot : http://forum.xda-developers.com/showpost.php?p=64875576&postcount=261
* Cannot add or delete Profiles? Follow this : http://forum.xda-developers.com/showthread.php?p=64954992
* App Crashes or lag builds up , check this : http://forum.xda-developers.com/showpost.php?p=64991257&postcount=350
* Further reading (deeper stuff) : http://forum.xda-developers.com/showpost.php?p=64622626&postcount=35
I've failed at the first hurdle. I don't get the MSM mpdescision hotplug option.
Update. Doh. On nameless kernel. Sorry.
Sent from my SM-N920C using Tapatalk
ninjabadger said:
I've failed at the first hurdle. I don't get the MSM mpdescision hotplug option.
Update. Doh. On nameless kernel. Sorry.
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Oops , NL kernel with msm_mpdecision is coming soon ?? , right now this guide is applicable with Emotion and AEL kernel ?
Nice thread and well organised
Semma Post bro :good:
May I know which ROM , kernel , bootloader , modem combo is best for battery backup (N910G) ?
I wanna try ur kernel adiutor settings in it.. :victory:
I'm not able to find emotion and AEL kernel for our N910G 5.1.1 .. where can I get it bro?
https://www.mediafire.com/folder/rvxdm018fdm1o/EMOTION_KERNELS_NOTE4#dsxr7ruz9p0ub
kalaishere said:
Semma Post bro :good:
May I know which ROM , kernel , bootloader , modem combo is best for battery backup (N910G) ?
I wanna try ur kernel adiutor settings in it.. :victory:
I'm not able to find emotion and AEL kernel for our N910G 5.1.1 .. where can I get it bro?
https://www.mediafire.com/folder/rvxdm018fdm1o/EMOTION_KERNELS_NOTE4#dsxr7ruz9p0ub
Click to expand...
Click to collapse
Thanks bro.
Correct link than,
The 5.1.1 910F kernel will also work on 910G , ?? ,
The link you provided in the 3rd post for Kernel Adiutor for Note 4 doesn't work
http://"https://mega.nz/#!JgMjBLab!m...sNLH66yzo3bj0"
Wise.Guy said:
The link you provided in the 3rd post for Kernel Adiutor for Note 4 doesn't work
http://"https://mega.nz/#!JgMjBLab!m...sNLH66yzo3bj0"
Click to expand...
Click to collapse
Thanks for the tip bro ,updated . Check now
Senthil360 said:
Thanks for the tip bro ,updated . Check now
Click to expand...
Click to collapse
It's ok now. Thank you
@Senthil360 can you provide kernel backup settings and share it with us? it will be easier to restore your backup so we can test.
if you have time, please provide backup settings for the 2 kernels below (either from synapse or kernel auditor)
-emotion r23 rc1
-ael v8.1 multivariant
thank you! i love to try your kernel settings ?
Dealte.
Whenever I downloaded the emotion kernel it changes from a .zip to a .jar
Anyone else get that?
Sent from my SM-N920C using Tapatalk
ninjabadger said:
Whenever I downloaded the emotion kernel it changes from a .zip to a .jar
Anyone else get that?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
yeah. you have to use firefox or use pc to download.
b.eslabon said:
@Senthil360 can you provide kernel backup settings and share it with us? it will be easier to restore your backup so we can test.
if you have time, please provide backup settings for the 2 kernels below (either from synapse or kernel auditor)
-emotion r23 rc1
-ael v8.1 multivariant
thank you! i love to try your kernel settings ?
Click to expand...
Click to collapse
No no bro , see that's the whole point , I want the users to be individualistic and i want you to help do these things on your own , Its very simple to follow and its been tested and approved , I hope that every bit of time you take to do this will certainly be useful and I cannot provide ready-made things outside Nameless now bro.
Senthil360 said:
No no bro , see that's the whole point , I want the users to be individualistic and i want you to help do these things on your own , Its very simple to follow and its been tested and approved , I hope that every bit of time you take to do this will certainly be useful and I cannot provide ready-made things outside Nameless now bro.
Click to expand...
Click to collapse
no problem bro ? i got your point. im just suggesting for easier ways tho
when you say interactive governor, it includes all the governor which are based on interactive such as interactive pro, intelliactive, etc
ModeSelektor is a simply app for manage power consumption and performance of redmi note 3.
The purpose of app is create a simply platform that give the possibility to set quickly the kernel parameters that affect the power consumption and performance. For do it ModeSelektor set this parameters:
-cpu interactive governors
-cpubw governors
-min cpu freq
-hmp sched boost
-low power level
-input boost
-touch boost
-stock hotplug
-entropy
-brightness
ModeSelektor is compatible with all N and MM custom rom with stock or custom kernels, but optimised for kernel that use the stock hotplug.
ModeSelektor is also compatible with miui but some users report that the copy from assets sometimes give error then it's possible fix it by manually copying the files. For fix it download the ModeSelktor.zip that contain the files and extract it in /sdcard make sure that the contents of zip are located in /sdcard/ModeSelektor
ABOUT SELEKTOR
Battery:
The perfect mode for medium and ligth use like chat, media reproduction and browsing.
Balanced:
An optimised version of stock cm settings
Performance:
The perfect mode for the players and the users with only a think in mind...kill any lag
Personally I recommend this optionals settings:
Adreno idler on for the Battery and the Balance modes
Zen scheduler set to 2048 kb
Adreno boost low during soft use and medium during game
For more info about script check /sdcard/ModeSelektor or the souces.
CHANGELOGS
Version 2.5.3
New hotplug configuration for battery and changes in targets_loads
New hotplug configuration for balanced and changes in input_boost
Reduce the brightness if battery is enabled
Add others parameters in build.prop tweaks
Version 2.5.2
Add a missed string in Seeder_On script
Fix the copy of assets
Version 2.5.1
Some fixes for the seeder
Version 2.5
Add a Seeder (fast random entropy generator) thanks to @Ryuinferno, @lambgx02
Add splash screen for fix fc related to permission
Remove Auto enable battery
New hotplug settings for all modalities
Fix hotplug permission in some cases
Fix switchs enabled after reboot also with apply on boot disable
New Battery (more use of frequency below 1017)
Remove max GPU freq in the scripts
Tune the entropy if the Seeder is enabled
New icon
New accent color and background
Version 2.4
Added Performance mode QS Tile
Added Build.prop tweak
Tune more parameters of stock cm hotplug
New revision for Battery and Balanced
Fix issue for apply the settings when core 0 or and core 4 are offline
Fix issue with Auto enable battery that sometimes start also if disabled when the charger is disconnected
Remove in the scripts commands that change scheduler, zram, arch power, adreno idler
Remove Ultra Battery and Ultra Performance (now Ultra Performance is Performance)
Version 2.3
Update battery mode (less use of 1017MHz)
Add option for reduce google play wakelock (thanks to @Alcolawl)
Fix phh superuser compatibility (now work on nitrogen os)
Fix fc with miui
Version 2.2
Fix last log not show shell output
Fix toasts apply on boot and auto ultra battery
Add more parameters:
Adreno idler
Zram
Scheduler
Arch power
Entropy
Stock hotplug
Now the app try to change others parameters if they are presents in your kernel. Look the last log for see if they have been correctly applied.
PS I'm not sure that all new parameters work also in miui, I can't test it, so if someone try the app on miui + custom kernel please give me a report. Thanks
Version 2.1
Fix Ultra Battery auto enabled alert text not disappear after enable a other profile
Move about in the menu and add a dialog window with info
Remove the refresh option by menu to action bar
Add confirm dialog window for reset scripts option
Add last log in menu and a new activity that show it
Make Ultra Battery more conservative
Auto update the database after install a new version
Probably fix the compatibility with Nitrogen Os (need confirm of it. If someone can test it, let me know, I would like a lot)
Version 2.0
New black theme
Fix some issue for Auto enable ultra battery feature
Add refresh option in menu
Version 1.2.3
Add menu with links and reset scripts option that overwrites the file in case of wrong edit replacing their with the stocks
Version 1.2.2
Add compatibility with MIUI + custom kernel
Fix database copy need restart after first boot
Version 1.2.1
Fix Fc during first boot
Fix some toast and remove service toast
Delete duplicate string in ultra battery script
Restore last selected mode during charging if ultra battery was enabled by auto ultra battery
Version 1.2
Revert ultra performance change
Ultra battery now is extreme
Add service for activate automatically ultra battery if battery go under the selected level
Version 1.1.1
tune a bit ultra battery and ultra performance
add gpu min and max freq tune
add timer_rate tune
Version 1.1
add apply on boot option
fix replace database every time that app start
fix app not save last selected mode
Version 1.0
Initial release
REQUIREMENTS:
Root permission
Custom kernel for Miui roms
INSTRUCTIONS:
- if you came by old app version before install uninstall old app version
- install the app
- run the app
- give root and storage permissions
- enjoy
FULLY TESTED ON:
Citrus caf
Slim 7
Nitrogen OS
DnD
Aosip
Aocp
All with stock and some customs kernels
DOWNLOAD:
https://sourceforge.net/projects/modeselektor/files/?source=navbar
SOURCES:
https://github.com/lafonte0/ModeSelektor
LICENCE:
GNU General Public License version 3
CONTRIBUTORS:
@lafonte @Stefano 99
ModeSelektor its an open source and free software, so all persons who want to improve it, contribute to the development, port the app on others devices, in compliance with the above license, are welcome. Also because it's my first app, software development isn't my sector, and help is always welcome.
Screenshot:
lafonte said:
Screenshot:
Click to expand...
Click to collapse
Tell me, how your script works?
abhy27 said:
Tell me, how your script works?
Click to expand...
Click to collapse
The app place scripts from internal apk database to /sdcard/ModeSelektor/scripts after when you press a mode the app run the script referred to selected mode, for see what script change you can look into scripts, you can also change the content of one, some or all script and make your personal modalities.
Not working!!!
LogCat attached
SerJo87 said:
Not working!!!
LogCat attached
Click to expand...
Click to collapse
You need to give root permission
I gave
I'm on the NitrogenOS. There integrated phh's superuser. Maybe that's why
SerJo87 said:
I gave
I'm on the NitrogenOS. There integrated phh's superuser. Maybe that's why
Click to expand...
Click to collapse
Sorry but the problem is in the name of directory, what is your internal storage name? it's /sdcard ?
Yes, most likely. I read logcat and saw this:
Code:
01-06 01:43:17.490 E/su (8325): Unknown id: /sdcard/ModeSelektor/scripts/S01_Ultra_Battery
internal storage name /storage/emulated/0
But the scripts are moved to sdcard(screenshot attached). Why is not working?
SerJo87 said:
Yes, most likely. I read logcat and saw this:
internal storage name /storage/emulated/0
But the scripts are moved to sdcard(screenshot attached). Why is not working?
Click to expand...
Click to collapse
Other users report me that app work, and it is strange issue because if the app create the ModeSelektor directory the path its the same when it run the script. The app until now have only one issue it replace all time the script in ModeSelektor folder when start, I forget to add an exception in this build. Last think, you can check if sh file is present in /system/bin?
Yes, sh file is present
SerJo87 said:
Yes, sh file is present
Click to expand...
Click to collapse
Then it must work...
Now I have no idea. All the time I thought that the result of battery only have due to radon 3.5 and the script does not working
SerJo87 said:
Now I have no idea. All the time I thought that the result of battery only have due to radon 3.5 and the script does not working
Click to expand...
Click to collapse
Before report that the app don't work post a complete review, you can't tell that app don't work without specify what mode you try and without post complete statistics about battery.
Ultra Battery with Umang kernel default settings by battrey
Version 1.1.1
https://sourceforge.net/projects/modeselektor/files/ModeSelektor_v1.1.1.apk/download
Testing a new version. Thank you
So i need to put rhe governor to interactive or the app do itself?
Sebaskyclad said:
So i need to put rhe governor to interactive or the app do itself?
Click to expand...
Click to collapse
The app do itself
FC in RR 5.7.4 + radon v3.5