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
Related
First, thanks $aur0n for the nice work and I can now also boot from SD card and enjoy the rooted system in EXT4
For those interested in overclock, you can try this kernel (I have tested it in Archos 70IT, but it should work in A101/A43IT as well):
** See below for instructions on how to apply this overclock kernel with the newest firmware
2011-04-15 (Latest version)
=========================
- Re-compile the whole kernel from archos latest kernel source code
- Suggested to use with newest chulri's initramfs
- Overclock to 1200Mhz
For firmware 2.3.20:
Download here: http://www.mediafire.com/?pnbev44hk2m1346
Click to expand...
Click to collapse
File name: zImage_archos_2.3.20_recode09.zip (MD5: 7756BA280F3FEBAD23A528A10EB1D6B5)
==================================================
Get rooted with newest firmware 2.X.X + overclock!
Click to expand...
Click to collapse
** Special thanks to chulri for the updated initramfs **
0) Install SDE first
1) Download chulri's initramfs from here: http://code.google.com/p/archos-gen8-sde-rooting/downloads/list
(Download the appropriate version that matches with your firmware version)
2) Grap the newest overclock kernel: http://www.mediafire.com/?pnbev44hk2m1346
3) Reboot your Archos holding "Volume -"
4) Recovery System -> Developer Edition Menu -> Flash Kernel and Initramfs
5) Connect USB and copy initramfs from (e.g. avos_2.X.XX_temproot.zip) and copy zImage from (e.g. zImage_archos_recode04A.zip) to Archos machine
6) Reboot by holding "Volume -"
7) Choose the 2nd menu item (Developer Edition)
8) Here, you get rooted in the newest firmware + overclock kernel
9) Enjoy ^_^
==================================================
Previous Versions
==================================================
2011-02-11
===================
- Further complier optimization
- Better performance on Archos 101
- Max frequency back to 1200Mhz because some users report not stable at 1280Mhz
- Revert interactive CPU governor (seems not stable)
- Suggested to use with chulri's initramfs
1200Mhz version:
Download here: http://www.mediafire.com/?eo3cmqg64md7qdb
Mirror: http://www.zshare.net/download/8731000468bf80d9/
Click to expand...
Click to collapse
File name: zImage_archos_recode04A.zip (MD5: 950D533F09131FCFCBD2BE4084C44691)
File name: zImage_archos_2.1.04_recode01.zip (MD5: ADF0C6FCCA503932D1C3860B3BAF61B3)
2011-02-01
===================
- Rebase from the original kernel source
- Complier optimization
- Add interactive CPU governor
- Bluetooth fix (please test, should still have problems)
- For those enjoying online flash movie, e.g. myTV.tvb.com, please set the freq to min:1000/max:1000 (Best with flash player v10.1.105.6 or upper)
- Set freq to min:1100/max:1100 for best 3D gaming experience
- Suggested to use with chulri's initramfs
1280Mhz version:
Download here: http://www.mediafire.com/?wu37fj90g69o61e
Mirror: http://www.zshare.net/download/860178577cd732f3/
Click to expand...
Click to collapse
File name: zImage_archos_2.1.04_recode01.zip (MD5: ADF0C6FCCA503932D1C3860B3BAF61B3)
2011-01-17
==================
- Not guarantee to work with $aur0n's 0.4.1 initramfs. Please use 0.2/0.3 initramfs (boot from SD) if you get problems
- More stable & smooth
- Overclock to 1280Mhz (Stable in playing NFS shift for a few hours - I am in world track now...)
- Remove 250Mhz and add 600Mhz (as 600Mhz is needed for SetCPU to display correctly)
- Fix the SetCPU 'time in state' problem
- Revert the bluetooth driver
- Cherry-pick more commits (refer to my github)
- Special thanks to $aur0n's initramfs
1280Mhz version:
Download here: http://www.mediafire.com/?1qweknppsoyb6rx
Mirror: http://www.zshare.net/download/8536472801a3552a/
1200Mhz version:
Download here: http://www.mediafire.com/?36wjsvkh6615dxg
Click to expand...
Click to collapse
Alternative link to $aur0n's initramfs (boot from SD): http://www.mediafire.com/?t41kvaonad7c83d
File name: zImage_archos_1280_fix01.zip (MD5: 5DAC535DA0EFFB1422BC887EF19564F8)
File name: zImage_archos_1200_ext4_fix07.zip (MD5: 1F022CCCD127A051154E98C5AC56CD2F)
2011-01-12
================
- More stable & smooth
- Apply 2.6.29.6 patchset - kernel
- Apply 2.6.29.6 patchset - ipv4
- ramzswap support (refer: http://code.google.com/p/compcache/)
- Cherry-pick more commits (refer to my github)
Download here: http://www.mediafire.com/?dih30gjy0lvljpk
Mirror: http://www.zshare.net/download/85094141432e0aae/
File name: zImage_archos_1200_ext4_fix05.zip (MD5: ECA8381E8371D1FE89FE2253D3482E9E)
2011-01-06
======================
- EXT4 fix (Quadrant score ~ 2500)
- Stable at max frequency 1200Mhz and min frequency 250Mhz (thanks Tzbob)
- Selectable frequency using SetCPU: 250/300/1000/1152/1200 Mhz
- 2.6.31 scheduling tweaks
- Source code pushed to github.com for easy sharing and conforming to GNU public license
- Merge various commits ( details can be seen in my github: https://github.com/ardatdat/archos-kernel/ )
- Quadrant scoring 2808 using 1200Mhz and boot from SD (Sandisk 8G Class 4)
Download here: http://www.mediafire.com/?7o7wnyipxwffx3w
Mirror: http://www.zshare.net/download/8483628818cf11b2/
File name: zImage_archos_1200_ext4_fix04.zip (MD5: 2CEF2D7F526DCD81B9C75EE2DAEBFF6F)
2011-01-03
================
- Updated a new kernel that supports $aur0n script (EXT4 support)
- Down-clock to 1100 Mhz because 1200 Mhz seems too hot and not too stable
- Merge some patches from kernel 2.6.29.6
Download here: http://www.mediafire.com/?ut6deu41216wdyd
Mirror (zip): http://www.mediafire.com/?83rd6te7a8ndmts (MD5: 7C8F9D48D74F45251B358FB3E2454485)
2011-01-02
============
- Initial version (not EXT4 support)
- Over-clock to 1200Mhz
http://www.mediafire.com/?bw8iq34tkvkllxe (MD5: 83D2A38A84C97C9336325EDD48C8D1B3)
Beware! After overclock, you will feel a bit hotter than before and battery drains much faster!! Flash it at your own risk.
What you need to do is:
1) Install SDE
2) Get the initramfs from this post (download the kernel+init.zip and extract it): http://forum.xda-developers.com/showpost.php?p=9948644&postcount=1
3) Replace the zImage with the new overclocked kernel
4) Boot into SDE recovery menu and copy the initramfs.cpio.gz and zImage through USB cable
5) Boot into SDE developer OS
6) You should get all your apps here and have superuser right now
You will now have read/write access to /system/ or /data/ ...etc.
Next step: You can download GScript from the market (free) to make some custom scripts to remove unnecessary apps and replace the hosts file, etc.
=================================================
Give us a "Thank" if you think this kernel works great for you
* Feel free to buy me a beer by clicking at the 'donate' button
=================================================
Oh thanks man! I'll impliment this into my own version of Auron's, yeah there was some confusion about your method, thanks for clearing that up!
Nevermind XD I don't know enough to add that, but Auron heavily uses EXT4 which he compiled into his kernel, which is probably why it isn't working for you, he explains in his topic the things he did or did not do.
Tzbob said:
Oh thanks man! I'll impliment this into my own version of Auron's, yeah there was some confusion about your method, thanks for clearing that up!
Nevermind XD I don't know enough to add that, but Auron heavily uses EXT4 which he compiled into his kernel, which is probably why it isn't working for you, he explains in his topic the things he did or did not do.
Click to expand...
Click to collapse
Thanks. BTW, it would be good if Auron will release his source such that we know what exactly is changed apart from the EXT4 things.
New kernel updated!!!
Get it at the #1 post
Now, it is EXT4 support and can be used together with $aur0n initramfs !!!
Down-clock to 1100Mhz seems to make it more stable
Thanks man really appreciate your quick work! works perfectly with Auron's
Although I'm curious how that overclock works, I've read up on it and it seems that everyone else is making overclocking modules etc. your solution seems a lot more efficient. Do other people know about it too?
I first though it was just a soft change, something that didn't affect the hardware, but something that just forced the digit 1100 instead of 1000, this doesn't appear to be the case since I get some speed gains in Quadrant
~ benched a 2438 ^^
edit: is it possible for you to change the LOWEST value as well? i'm not sure how it would react but I imagine a 100Mhz/200Mhz feature would save up some standby-battery-usage also is it possible to change the intervals with this method? so that we can get 300/400/500/600/700..1100?
edit2: would it be theoretically possible to compile a kernel with driver support for gamepads and others? perhaps ntfs-3g to mount ntfs external drivers... thinking about this we have usb host on this device and an open bootloader
Tzbob said:
Thanks man really appreciate your quick work! works perfectly with Auron's
Although I'm curious how that overclock works, I've read up on it and it seems that everyone else is making overclocking modules etc. your solution seems a lot more efficient. Do other people know about it too?
I first though it was just a soft change, something that didn't affect the hardware, but something that just forced the digit 1100 instead of 1000, this doesn't appear to be the case since I get some speed gains in Quadrant
~ benched a 2438 ^^
edit: is it possible for you to change the LOWEST value as well? i'm not sure how it would react but I imagine a 100Mhz/200Mhz feature would save up some standby-battery-usage also is it possible to change the intervals with this method? so that we can get 300/400/500/600/700..1100?
edit2: would it be theoretically possible to compile a kernel with driver support for gamepads and others? perhaps ntfs-3g to mount ntfs external drivers... thinking about this we have usb host on this device and an open bootloader
Click to expand...
Click to collapse
The most difficult part is to determine how much voltage to be given to each frequency. So, it would take some efforts to study.
In addition, setting too low frequency is not necessary be good because the machine might go into deep sleep and never wake up.
Have you run any Super PI tests (or something similar) to see if there are stability issues with the increased clock rates?
Typically when I over-clock my CPU on my PC I increase the voltages at the micro or mini level (CPU, Front Side Bus, Memory, Memory Controller, etc.). As an example 1.3500 may not be stable but 1.3501 could be. Typically You can find the voltage tolerances typically at CPU manufacturer website (ie Intel for me). of course you also have to deal with the temperature of the CPU and other supporting components that regulate the voltage. I will run a Super PI type application to test stability for a few hours. If it works then dont add voltage.. if it comes back with a miscalculation OR an application/OS crash then increase the voltage by a micro amount...
You are correct when you saw it not performing at a higher clock rate... typically what happens if the CPU does not have enough voltage to perform at the expected clock rate it seems to throttle the execution rate to ensure some level of integrity of the executing transaction..
Unfortunately over-clocking is not a science..
ardatdat said:
The most difficult part is to determine how much voltage to be given to each frequency. So, it would take some efforts to study.
In addition, setting too low frequency is not necessary be good because the machine might go into deep sleep and never wake up.
Click to expand...
Click to collapse
its using the same cpu as a lot of android phones are and i daresay that most of the work (working out optimal cpu voltage etc) has already been done
The question is for non-standard clock rates. Standard clock rates should have well defined voltages.
thefunkygibbon said:
its using the same cpu as a lot of android phones are and i daresay that most of the work (working out optimal cpu voltage etc) has already been done
Click to expand...
Click to collapse
can this kernel work on a101 or not?
Yes it will work, I'm 90% sure since they tested it on the 70IT and it's working perfect on my 43IT.
Tzbob said:
Yes it will work, I'm 90% sure since they tested it on the 70IT and it's working perfect on my 43IT.
Click to expand...
Click to collapse
ok i will give it a try....
I have tried this 1100 Mhz kernel and angry birds don't want to start and asphalt 5 have to force closing, I have returned with the only rooted rom....
merlin_1492 said:
I have tried this 1100 Mhz kernel and angry birds don't want to start and asphalt 5 have to force closing, I have returned with the only rooted rom....
Click to expand...
Click to collapse
While this kernel has been OC, it only allows you to choose higher frequencies. BUT, you can still choose 1000 Mhz as the highest by setting it in SetCPU.
After setting min/max as 1000Mhaz in SetCPU, this kernel is just like any other kernels, except that I have applied some of the newest kernel patches (fix bugs?) so that this kernel MUST be better than the stock one.
Hope you enjoy using it
no no, the problem is that after installing oc kernel(without touching anything about frequency), angry birds doesn't run and asphalt 5 doesn't run well and it closes when init a race...So, what's the problem? I have returned to original kernel(with rooting), and now are perfectly running(angry birds and asphalt5)...
merlin_1492 said:
no no, the problem is that after installing oc kernel(without touching anything about frequency), angry birds doesn't run and asphalt 5 doesn't run well and it closes when init a race...So, what's the problem? I have returned to original kernel(with rooting), and now are perfectly running(angry birds and asphalt5)...
Click to expand...
Click to collapse
It is quit strange, coz I can run angry birds, dungeon hunter, etc.. very smoothly even when I use 1100 Mhz, have you tried to install SetCPU and set the frequency?
Any one have similar problems?
Working great on my A101! It's subtle, but I do notice a slight performance increase in pocket legends. Keep up the great work ardatdat!
ok so i did it and now the youtube app freezes up with 1100 or 1200 mhz...the video plays for like 3 or 4 sec and than freeze leaving only audio playback.. video plays normal at 1000 mhz and down...
thanks for your sharing
but I can't unzipped the newest kernel
the 7-zip showed "file broken"
uglin said:
thanks for your sharing
but I can't unzipped the newest kernel
the 7-zip showed "file broken"
Click to expand...
Click to collapse
Thanks. A mirror (zip) link is posted in post #1, please check and re-download
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 .
[FAQ] >> RBAP for miniCM10 by nAa, nAa's kernel X10mini/X8/x10miniPRO .:08/07/2013:.
Read Before Asking Please
FAQ for MiniCM10, and nAa kernel
reading may answer to lots of your questions !
for X10mini, X8 & x10miniPRO
{
"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"
}
i decided to create a new thread dedicated to Q&A about miniCM10
this thread is the place of your questions, answers, tips about miniCM10 and nAa ics kernel
so please, as usual, read FAQ, use search option or anything else before asking commonly answered questions
the FAQ will be incremented when needed
the Q&A is written as Q are asked
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the JBnAa kernel
Instructions:
paste miniCM10-4.X.X on the root of your SDcard
backup
flash JB kernel
get in recevery and format /system ; /data ; /cache
flash rom
flash gapps
wait for the very long first boot
enjoy
Please make sure you followed the above steps before reporting any issues, especially 'wipe data/factory reset'
something else that is useful to read before asking :
Here we (nearly all? XDA members, regardless of being devs or only users [like me], me at least ) don't care about your good/bad English the important is trying to be understood and to understand the content of the threads
only ask things you can't find, or you don't understand, please if you don't understand something in any process tell us exactly where is your problem : it will optimize the answer
sometime rephrasing things can make you understand better, feel free to help us for making the most understandable sentence for anybody
i'm always trying to use a proper English (not so easy for a non native English ^^)
but if there's something misunderstood because of my English your are welcome to correct me
BUT if you don't make the effort to read, I won't make the effort to answer (ok, you can't read everything... but read the minimum )
that's it
miniCM website is now available (http://minicm.dyndns.org/site/Chat/ for chatroom)
clic on the red text above
register, and then enjoy
________________________________
bug tracking template :
twins.7 said:
#BUG Report
DO
Reboot - Recovery
BUG
the screen stuck in rebooting dialog. It should just rebooting
ACTION
press home key (or any key maybe) to make it reboot
Click to expand...
Click to collapse
________________________________
we seek for you, TESTERS, go there for helping : [DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
2nd part of FAQ
FAQ :
for miniCM7 refer to THIS THREAD PLEASE
for miniCM9 refer to THIS THREAD PLEASE
for quick search, use ctrl+f and enter keyword, you should find an answer to your question
ok, let's start with some fun :
how to understand FAQ :
0/ question(which build(s) is(are) concerned with q/
answer to the question
old, wrong or obsolete answer
additionnal comments if needed
__________________________________________________
nobodyAtall said:
about nAa JB kernel :
Preface:
Read through [that] post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Click to expand...
Click to collapse
1/ any problem with display overridding?( ? ; ? )
in settings > development settings :
_____________________
2/ wanna go back to a non jelly bean based rom?( all builds ; all devices )
go to CWM > mount&storage and format :
/system
/data
/cache
then flash the kernel you want, (press flash on flashtool, plug the phone to pc, force reboot by pressing home+power, press and hold back button)
==> you can now restore a backup of the old rom you were previously using or install another non JB based rom
_____________________
3/ hard/software keyboard isn't working properly??( ? ; mimmi )
x10man said:
Quick fix for the soft keyboard:
On the select input method screen turn the hardware keyboard to off like so:
The software keyboard will now appear but the hardware keyboard still works.
Basically this needs to auto-switch when the hw keyboard opens and closes.
X10man
Sent from my U20i using xda premium
Click to expand...
Click to collapse
DanielFran said:
Power off, then remove sim card. Reboot and select language, change keyboard layout in advanced definitions (mimmiparts). Then put again sim.
Sent from my U20i using Tapatalk 2
Click to expand...
Click to collapse
4/ why my wifi can't load? ( all builds ; all devices )
you may have that kind of logcat:
Code:
D/WifiService( 1694): setWifiEnabled: true pid=2095, uid=1000
E/WifiStateMachine( 1694): Failed to load driver!
E/WifiStateMachine( 1694): DriverFailedState
open terminal emulator :
Code:
lsmod
if it doesn't answer anything, maybe /system is out of space and kernel fails to copy wifi modules at boot (note that undervolt module wont work either)
try the following :
open any file explorer that is root capable,
go to /system/media/audio/ringtones
delete some ringtones (at least to recover about 3 or 4 MB free, the more is safer) [1.5 MB seems to be enough though ]
reboot
try lsmod and see, if the kernel succeeded to copy modules at boot it's ok and and lsmod outputs what you are waiting for, if not reflash kernel and/or try to install a reduced miniCM10 zip (by deleting ringtones as for the previous way, but in a zip editor)
hoping it will solve your problem
5/ you have various problems with wifi ? ( all builds ; all devices )
refer to miniCM7 and miniCM9 miniFAQs !!!
6/ what are I/O schedulers ? ( all builds ; all devices )
a kind of answer here
7/ i updated from miniCM10-4.0.0 to 4.0.1 and after updating the gapps to 20120923 i've lost the camera ? (miniCM10-4.0.1 ; all devices)
go to mount&storage
format /system (NO data lost )
install miniCM4.0.1 again
install gapps 20120923
reboot&wait
all should be back to normal : fast and feature full
8/ how can i set keyboard shortcuts on my hardware keyboard? (all builds ; mimmi)
just edit azerty.xml or qwerty.xml in system\usr\keyboard-config\layouts
9/ how can i fix my azerty/qwerty/qwertz... HardWare keyboard? (miniCM10-4.0.2+ ; mimmi)
first flash this : from here
and then the zip corresponding to your specific language : look here
/!\ choose "default input method" so that the KB works correctly, if you don't it will behaves strangely
/!\ do not modify keyboard_layouts and keyprints in any way if you want the above to work, edit: seems you can edit the xml finally
/!\ do not modify advanced>mimmiperts, make sure you have not touched it before processing the installs. it is recommended to start from a "fresh build" i.e. to wipe all user data, and so on.
defauld input and sym button should be back
/!\here is another way to fix it : follow allesand's instructions
10/ i wanna use a2sd, what is it and how to make it work? (all builds ; all devices)
refer to that short tuto & infos here by drfr
11/ my LED is not blinking properly is there any way to change that? (all builds ; all devices)
You must delete /system/lib/hw/lights.msm7x27.so with rootexplorer or any other file manager that allows you to explore and modify root files
handcent led settings does not work properly with lights.robyn.so
of course, you need to reboot your phone after that.
REDELETE AFTER EACH UPDATE if you have the same problem SINCE THE FILE IS REWRITTEN
12/ why flastool doesn't flash the kernel i choose? (any version)
when there are lots of kernel builds in flashtool firmware folder, flashed kernel might not be the right one,
to void this, create a folder in it, cut/paste all your previous kernel there
and only keep the one you want to flash in the firmware folder
then, start flastool and process flashing operations
13/ i'have some problem for sending mms (all builds until miniCM10-4.0.2+ ; all devices)
--> with CM7/9/10 you just CANT send mms without data enabled
if you can't even with data enabled:
DaRk_dOg said:
I think that this is a common issue with CM7 and not just MiniCM7 (I experienced it on my DHD too).
Here is a small workaround for now:
Before sending the mms, disable data traffic, then enable it again and then send your mms.
You have to do it every time, before an mms but it is working for me.
Regards, D_d
Click to expand...
Click to collapse
--> seems now, mms can be sent without enabling data or anything, just need to have correct APN set up
14/ CM file manager doesn't work well for no (not at all in fact) (all builds? ; all devices?)
see details here.
15/concerning brightness on MiniCM10-4.0.2 nightly 20130119 and higher, (MiniCM10-4.0.2-nightlies ; shakira, robyn, mimmi?
to get compatibility with .32 kernel, nAa needed to change some things related to brightness monitoring
and that's why some issues appeared with .29 kernel, and then were fixed, but with the drawback of light being at max for a short time before dimming when turning the screen on.
using .32 kernel solves this issue
with old .29 kernel, use MiniCM10-4.0.2-stable or nightlies until 20130114
for newer nightlies (especially 20130207+) prefer .32 kernel
16/ concerning Undervolting and newer .32 kernels : (MiniCM10-4.0.2+ and nAa .32-03+ ; all devices)
NobodyAtall said:
VDD levels
From 03 onwards, I've ported the vddlevels functionality from msm7x30
so that we can variably change the voltage level of the frequency we
want without the need for external modules.
The current voltage information is available at:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
E.g. the defaults after flashing the kernel should be:
Code:
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
122880: 3
245760: 4
320000: 5
480000: 6
604800: 7
614400: 7
633600: 7
652800: 7
672000: 7
691200: 7
710400: 7
729600: 7
748800: 7
768000: 7
787200: 7
806400: 7
825600: 7
844800: 7
864000: 7
To change for example the voltage level of the 122880 frequency, you could do:
Code:
echo '122880 0' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
If you cat this file again, you should see that the voltage level is
picked up. The new voltage level is picked up when the CPU will scale
to the particular frequency level.
The undervolting tickbox in the 'Performance Settings' of the latest
MiniCM10 nightlies already uses the new interface. The values that are
set there are the same ones as those passed by the old undervolting
module:
Code:
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
122880: 0
245760: 2
320000: 3
480000: 5
604800: 6
614400: 7
633600: 7
652800: 7
672000: 7
691200: 7
710400: 7
729600: 7
748800: 7
768000: 7
787200: 7
806400: 7
825600: 7
844800: 7
864000: 7
Do I need undervolting?
You dont NEED undervolting. It can save though hours of some battery
life during the day.
Overvolting?
Even though the interface allows you to overvolt, I don't suggest
doing so. It will result to instabilities or crashes and is totally
unsupported.
Performance?
Undervolting decreases the performance results - this is to be expected.
Click to expand...
Click to collapse
17/ why can't i connect my device to USB on PC ? (MiniCM10-4.1.0+ & nAa05+ ; all devices)
SmG67 said:
That's because MTP (Media Transfer Protocol) is default now, so it gets connected as a media device. If you want Mass Storage, go into Settings-Storage on your ROM and press the menu-button, you can select USB-storage from there.
Click to expand...
Click to collapse
18/ where is my dualtouch?? (MiniCM10-4.1.0+ &nAa05+ ; all devices)
this is a copy of kernel OP, that you should have read before
nobodyAtall said:
Dualtouch (for synaptics):
By default dual touch is disabled for improved touch accuracy and avoidance of the 'ghost touch' side-effect.
If you want to enable the fake DT by andrej456, you have to insert the following line in the /system/etc/hw_config.sh file:
Code:
echo "1" > /sys/module/synaptics_i2c_rmi4/parameters/cfg_dt
If you want to enable the fake DT by dx, you have to insert the following line in the /system/etc/hw_config.sh file:
Code:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Dualtouch (for cypress):
Cypress supports dualtouch, so this is enabled by default
Click to expand...
Click to collapse
19/ why do i get a kernel version error (installation abort, status 7) while installing MiniCM10? (MiniCM10-4.1.0 up to 20130518-NIGHTLY &nAa06 ; all devices)
matmutant said:
change in rom zip to *.61 for kernel version if you want the installation to complete (in META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
3rd part
3rd part
usefull links and performance tricks
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
what CPU governors, and how do they work?
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish
for both :
to see if your swap works, open terminal, and type the following :
Code:
free
to see the swapiness :
drfr said:
To check in terminal:
Code:
cat /proc/sys/vm/swappiness
Default value is 30 if you have zram and swap enabled, or 60 if only swap without zram.
To change it TILL NEXT REBOOT:
Code:
echo X > /proc/sys/vm/swappiness
where X is your desired value
To change it PERMANENTLY:
add the above line to the end of your hw_config.sh (you can find it in /sýstem/etc)
Note: it is always way easier to type those things on PC keyboard, so you´d better do it in adb shell.
Click to expand...
Click to collapse
__________________
some usefull lines of commands for any user wanting to know what's going on :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to siplay the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know how much swap there is (total and free are what you want to know), use the following command since the way using menu is broken :
Code:
free
to know if KSM is really turned on :
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb pm install /home/user/app1.apk
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
Benchmarks, screenshots and thklist
to start with, some screenshots
MiniCM10 theme:
MiniCM10 Crystal2:
benchmarks :
MiniCM10-4.0.2-nightly, using .32 kernel :
all has been done at 729MHz, on robyn
on .32-02:
antutu : fps2D:
I/O performance on miniCM10-4.0.2-20130120/nAaJB03 (2.6.29.6) :
conclude what you want
NOOP:- The NOOP scheduler inserts all incoming I/O requests into a simple, unordered FIFO queue and implements request merging.
The scheduler assumes I/O performance optimization will be handled at some other layer of the I/O hierarchy; e.g., at the block device; by an intelligent HBA such as a Serial Attached SCSI (SAS) RAID controller or by an externally attached controller such as a storage subsystem accessed through a switched Storage Area Network.
ANTICIPATORY:- Anticipatory scheduling is an algorithm for scheduling hard disk input/output.
It seeks to increase the efficiency of disk utilization by "anticipating" synchronous read operations.
CFQ:-CFQ, also known as "Completely Fair Queuing", is an I/O scheduler for the
Linux kernel which was written in 2003 by Jens Axboe.
CFQ works by placing synchronous requests submitted by processes into a number of per-process queues and then allocating timeslices for each of the queues to access the disk. The length of the time slice and the number of requests a queue is allowed to submit depends on the IO priority of the given process. Asynchronous requests for all processes are batched together in fewer queues, one per priority.
BFQ:- BFQ is a proportional share disk scheduling algorithm based on the slice-by-slice service scheme of CFQ. But BFQ assigns budgets, measured in number of sectors, to tasks instead of time slices. The disk is not granted to the active task for a given time slice, but until it has exahusted its assigned budget. This change from the time to the service domain allows BFQ to distribute the disk bandwidth among tasks as desired, without any distortion due to ZBR, workload fluctuations or other factors. BFQ uses an ad hoc internal scheduler, called B-WF2Q , to schedule tasks according to their budgets. Thanks to this accurate scheduler, BFQ can afford to assign high budgets to disk-bound non-seeky tasks (to boost the throughput), and yet guarantee low latencies to interactive and soft real-time applications.
I/O performances on MiniCM10-4.1.0 /w 2.6.32.60 nAa-JB-05 :
here is a chart showing scheduler specific results,
the benchmarks were based on Antutu, regarding IO and SDcard R/W
my settings are :
122~729MHz
smartassH3
undervolted
KSM
zram 18%
swap file 128MB
all i can say for now, is that SIO is the more balanced scheduler, and CFQ/VR are the worst
here are the results
what does the chart shows us?
SIO is the more balanced scheduler, it has a good IO, and a good read/write
Anticipatory has the best IO, but a bad SDwrite
Deadline has the best SDwrite, but is quite average for IO and SDread
NOOP, CFQ and VR are a bit behind
for people using swap, i would say that they should use SIO or deadline, for others, Anticipatory or BFQ might be better
i ran the benchmark 4 times for each scheduler.
source
Benchmarks history since stock rom here
MORE BENCHMARKS HERE
thanks to Heronger and some others helping to build this FAQ
are the reserved threads in x8 development for JB?
hetunandu said:
are the reserved threads in x8 development for JB?
Click to expand...
Click to collapse
where are the reserved threads you are talking about?
matmutant said:
where are the reserved threads you are talking about?
Click to expand...
Click to collapse
in x8 android development section
http://forum.xda-developers.com/forumdisplay.php?f=1704
hetunandu said:
in x8 android development section
http://forum.xda-developers.com/forumdisplay.php?f=1704
Click to expand...
Click to collapse
maybe
matmutant said:
maybe
Click to expand...
Click to collapse
arghhhh!! cant wait!!
BTW do u need testers? im in. I have an X8. PM me
Great job matmutant!:good:
I have questions/suggestion request about minicm 10 for xperia x8, i have a very little space to store applications, any suggestions? With GB I can use a lot of apps moving its in SD but with MiniCM 10 also moving apps I can install all the apps that I use before.
Use an ext partition for example it would be useful?
Another thing is the automatic conversion trom SMS to MMS when it exceeds a page in length. Only using another app for messages it wont be this way but i thing it would be great if we can use the stock app that I think is great!
A q aswell(actually I'm not sure of something)
nAa said it will repartition our space and said to uninstall we need to flash using seus or flashtool so that means to go back to stock partition we need to flash good ol eclair or any other kernel(eg. nAa gb) will get back our partition?
Sent from my heart™ using Xperia X8
X8invisible13 said:
A q aswell(actually I'm not sure of something)
nAa said it will repartition our space and said to uninstall we need to flash using seus or flashtool so that means to go back to stock partition we need to flash good ol eclair or any other kernel(eg. nAa gb) will get back our partition?
Sent from my heart™ using Xperia X8
Click to expand...
Click to collapse
I think he means that if we want move to another kernel we have to use seus or flashtool the way we always flash new kernel, for example flashing again naa-13 over jb kernel using flashtool without going back to eclair first.
I tried to make an ext partition in my sd card with CWM, now I have more memory to store my apps and system is so fast! This rom is great!
I only have sometimes random reboots and sometimes the screen crashes but now this is my daily rom!
Does swap partition works in MiniCM10 ?
I still don't quite understand about the meaning of clearing data, cache, etc...
Currently, I'm still at MiniCM 2.2, with a swap partition, EXT 4 partition, and FAT partition...
What is the correct sequence to run JB for the first time ?
Do I have to :
1. Reformat my MMC first + deleting the partition, go to recovery, format data, cache, etc, then make new partition (Swap, EXT4, and FAT)
OR
2. Format data, cache, etc, then reformat my MMC (as Swap partition gets changed to EXT3 automatically when doing factory reset), then make new partition.
Can somebody help ? Thank you in advance
StardustGeass said:
Does swap partition works in MiniCM10 ?
I still don't quite understand about the meaning of clearing data, cache, etc...
Currently, I'm still at MiniCM 2.2, with a swap partition, EXT 4 partition, and FAT partition...
What is the correct sequence to run JB for the first time ?
Do I have to :
1. Reformat my MMC first + deleting the partition, go to recovery, format data, cache, etc, then make new partition (Swap, EXT4, and FAT)
OR
2. Format data, cache, etc, then reformat my MMC (as Swap partition gets changed to EXT3 automatically when doing factory reset), then make new partition.
Can somebody help ? Thank you in advance
Click to expand...
Click to collapse
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size)
then set up your swap
and install the rom
swap partition should work
what doesn't work is the swap info menu
_______________________
benchmark of the day :
matmutant said:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size)
then set up your swap
and install the rom
swap partition should work
what doesn't work is the swap info menu
_______________________
benchmark of the day :
Click to expand...
Click to collapse
Please show your settings.MATMUTANT
Sent from my U20i using xda premium
benchmark :
[/QUOTE]
SERIOUSLY. I haven't had a high score on my mimmi with my MiniCM7 with most of apps I need and apps for UI improvements(themes/widgets/etc). I also use v6 SuperCharger of zepplinerox. I only had a 1853 score. but this score is higher. does this have potential to overthrow the speed and performance of MiniCM7?
minicm10 doesn't have as much features as minicm7 or 9 but is much smoother and more powerful right now .
my settings are simple:
ksm on, disable hardware override on, swap file 128 , uv on, else: default
note that this screen shot was taken on a private nightly of the next release :
Presenting...
neXusKERNEL
with SWEEP2WAKE (alpha)
by neXusPRIME
CHANGELOG:
V4.0
1. Sweep2Wake........ do you want anything else??? :highfive::highfive:
It is in alpha mode, so dont blame me for bugs, use v3.
Click to expand...
Click to collapse
V3.0
1. USB Fast Charge. For details see: http://forum.xda-developers.com/showpost.php?p=45743315&postcount=65
Click to expand...
Click to collapse
V2.0
1. Added "BFQ Scheduler", my favourite
2. Added experimental GPU OC
Click to expand...
Click to collapse
V1.0
1. HTC Write protection disabled.
2. Enabled swap support.*
3. Added scheduler "sio"
4. Added Smartassv2 governor
5. HTC perflock disabled
6. Enable KSM support (Flash zip in link to enable KSM http://forum.xda-developers.com/showpost.php?p=38569436&postcount=8)
7. No modules needed, everything inside boot.img
8. Init.d supported. Use app in link to verify init.d support http://forum.xda-developers.com/showthread.php?t=1933849
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DOWNLOADS (JB):
V4:
http://d-h.st/j9E its ALPHA, you have been warned
V3:
http://d-h.st/84i
V2:
http://d-h.st/zuB
V1:
http://d-h.st/3UP
Click to expand...
Click to collapse
OLD ICS VERSIONS:
V3: http://d-h.st/7C6
OLD VERSION: V2: http://d-h.st/HcS
OLD VERSION: V1: http://d-h.st/dOq
SOURCE:
https://github.com/ProtoU/neXusKERNEL
CREDITS
atis112 - for My 1st ClassRoom
cybojenix - for S2W
galaxyfreak - for S2W
helicopter88 - for S2W
zarboz - for S2W
franco-c - for USB Fast Charge
cute_prince - for OC attempts, not final yet
KonstaT - for general performance patches
and maybe a few others
Click to expand...
Click to collapse
@neXus PRIME
Thanks for your great effort.
Here is my findings :
Features:
1. HTC Write protection disabled.
This works great Removed both wp_mod2.ko & init.d script to load it... I can confirm the HTC write protection now disabled.
Updating busybox with no problem
2. Enabled swap support. (if you make a swap partition, it should get used. But need testers)
I don't need this feature, so I don't test it.
3. Default scheduler "noop" (I've always liked noop better then all others)
"noop" as default is shown in the attached screenshot
4. HTC perflock disabled (SetCPU does some magic when perf lock is disabled. Test n report)
No idea how to test this
5. Default Min set to 245 Mhz (My liking)
I like 245 Mhz too but I don't see it in both No Frill and CPU Spy (see attached screenshot)
6. Enable KSM support
Don't really need it but will test later with my old KSM init.d script
7. Default governor "ondemand" (later you can select whatever you like e.g
smartassv2)
"ondemand" is shown as default.
8. Ext2/ext3 file system support. (testers needed)
Don't need this so I do not test
9. Aren't above enough ???
Well... it's enough for now... maybe later s2w feature ? Maybe you can contact maxwen (One V kernel dev) for assistance.
I maybe wrong but I see that the init.d support is not enabled in your kernel. All the above test I ran it with my own ramdisk.
ckpv5 said:
@neXus PRIME
Thanks for your great effort.
Here is my findings :
Features:
1. HTC Write protection disabled.
This works great Removed both wp_mod2.ko & init.d script to load it... I can confirm the HTC write protection now disabled.
Updating busybox with no problem
2. Enabled swap support. (if you make a swap partition, it should get used. But need testers)
I don't need this feature, so I don't test it.
3. Default scheduler "noop" (I've always liked noop better then all others)
"noop" as default is shown in the attached screenshot
4. HTC perflock disabled (SetCPU does some magic when perf lock is disabled. Test n report)
No idea how to test this
5. Default Min set to 245 Mhz (My liking)
I like 245 Mhz too but I don't see it in both No Frill and CPU Spy (see attached screenshot)
6. Enable KSM support
Don't really need it but will test later with my old KSM init.d script
7. Default governor "ondemand" (later you can select whatever you like e.g
smartassv2)
"ondemand" is shown as default.
8. Ext2/ext3 file system support. (testers needed)
Don't need this so I do not test
9. Aren't above enough ???
Well... it's enough for now... maybe later s2w feature ? Maybe you can contact maxwen (One V kernel dev) for assistance.
I maybe wrong but I see that the init.d support is not enabled in your kernel. All the above test I ran it with my own ramdisk.
Click to expand...
Click to collapse
The default min freq is 245 but.... i forgot to modify CPU freq tables so once you try to move the slider, the 245 Mhz freq is lost. And also, smartassv2 somehow becomes default. Maybe i'll fix, maybe not. Coz atis is already hard at CM work, so thought maybe ppl could test the ksm/ext2/3/swap features.
Regards
neXus PRIME said:
The default min freq is 245 but.... i forgot to modify CPU freq tables so once you try to move the slider, the 245 Mhz freq is lost. And also, smartassv2 somehow becomes default. Maybe i'll fix, maybe not. Coz atis is already hard at CM work, so thought maybe ppl could test the ksm/ext2/3/swap features.
Regards
Click to expand...
Click to collapse
If you used my sources for smartass it becames default because i add it as a default governor. You can modify it in the config. Just use "make menuconfig" and set the default things what you would like. (but first load the original config). Your new modified configuration will saved to "kerneldir/.config"
Just cause I saw your post in the atis's thread, I thought I'd check this out. I have a suggestion for you, instead of using swap, try zram. zram uses part of ram as a compressed swap device. You can get about a 3 to 1 compression ratio and it's much, much faster than swap on a disk. It can be enabled in menuconfig under drivers/staging/zram. Download any of my kernels (in my signature) if you need an example of an init script to start zram.
And, once more, added to Index.
Keep up the good work.
Re: [Kernel/modded] neXusKERNEL v1.0
Who has atis112 kernel can flash this other kernel safely ?
It should work right ?
neXus PRIME said:
The default min freq is 245 but.... i forgot to modify CPU freq tables so once you try to move the slider, the 245 Mhz freq is lost. And also, smartassv2 somehow becomes default. Maybe i'll fix, maybe not. Coz atis is already hard at CM work, so thought maybe ppl could test the ksm/ext2/3/swap features.
Regards
Click to expand...
Click to collapse
Maybe a fix to 245 Mhz is great. The governor not necessary to fix as user can choose what they prefer.
Tested the KMS support... it runs great. With KMS enabled, I have more free RAM available at anytime with no performance decrease.
Anyone want to try, you need init.d script with below command
Code:
echo "1" > /sys/kernel/mm/ksm/run
Or just flash attached kms script that I'm using
Good job neXus PRIME :good:
ckpv5 said:
Maybe a fix to 245 Mhz is great. The governor not necessary to fix as user can choose what they prefer.
Tested the KMS support... it runs great. With KMS enabled, I have more free RAM available at anytime with no performance decrease.
Anyone want to try, you need init.d script with below command
Code:
echo "1" > /sys/kernel/mm/ksm/run
Or just flash attached kms script that I'm using
Good job neXus PRIME :good:
Click to expand...
Click to collapse
Linked your KSM script post to OP. Plus, im doing the 245 Mhz fix right now.
Regards
Updated. Changelog in OP.
@neXus PRIME
Here my finding so far:
Version 2:
1. Freq Table fixed, (Min 122, then 245 just after it)
:good::good:
2. ZRAM support added. (Testers needed)
With zram support added but not enable at default, I find that my ROM lags a lot.
Code:
C:\Users\ckpv5\Desktop\fastboot>adb shell
[email protected]:/ # busybox free
busybox free
total used free shared buffers
Mem: 620984 521988 98996 0 13236
-/+ buffers: 508752 112232
Swap: 0 0 0
[email protected]:/ #
with zram enabled, there is no lag but the smoothness/performance is less compare to v1. Maybe this is due to minfree is default value and cannot be changed with init.d script, will test with lower minfree (as suggested by flar2 in his thread) thru ramdisk change later.
Anyway.. maybe it's my own wrong doing; maybe other user with other ROM can have better result.
Code:
C:\Users\ckpv5\Desktop\fastboot>adb shell
[email protected]:/ # busybox free
busybox free
total used free shared buffers
Mem: 620984 523556 97428 0 13576
-/+ buffers: 509980 111004
Swap: 102396 25600 76796
[email protected]:/ #
Problem...
neXus PRIME said:
Hi,
I'm not making a thread in dev section as i'm not gonna maintain this over time. I just added a few things in atis's config and modified some others to my own liking.
DOWNLOAD:
V2: http://d-h.st/HcS
OLD VERSION: V1: http://d-h.st/dOq
NOTE: Flash zip in below post to enable KSM
http://forum.xda-developers.com/showpost.php?p=38569436&postcount=8
NOTE: Use this excellent app for enabling and verify init.d support
http://forum.xda-developers.com/showthread.php?t=1933849
Features:
Version 2:
1. Freq Table fixed, (Min 122, then 245 just after it)
2. ZRAM support added. (Testers needed)
Version 1
1. HTC Write protection disabled.
2. Enabled swap support. (if you make a swap partition, it should get used. But need testers)
3. Default scheduler "noop" (I've always liked noop better then all others)
4. HTC perflock disabled (SetCPU does some magic when perf lock is disabled. Test n report)
5. Default Min set to 245 Mhz (My liking)
6. Enable KSM support
7. Default governor "ondemand" (later you can select whatever you like e.g smartassv2)
8. Ext2/ext3 file system support. (testers needed)
9. Aren't above enough ???
Guys, atis had a huge role in teaching me how this all works, so major credits to him. The sources are available on my git as well so all are free to fork and try out their own combo of settings.
I'll need a few reports about above features.
Just download n enjoy !!!
Regards
Yasir
Click to expand...
Click to collapse
The min cpu frequency is 122 and i cannot set it to lower no 98MHZ available...
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
SaadCrackz said:
The min cpu frequency is 122 and i cannot set it to lower no 98MHZ available...
Click to expand...
Click to collapse
Yeah that's what I did. I don't like 98
Sent from my HTC Desire X using xda app-developers app
neXus PRIME, can you tell me what do you mean with "4. HTC perflock disabled (SetCPU does some magic when perf lock is disabled. Test n report)"? I mean, I have flashed your kernel and I have SetCPU installed but I don't know what is that "magic". Also, if you want, I can test or see what does happen with it enabled (so far, I see no issues).
I have selected: min 122, max 1008, smartassV2, sio.
Thank you very much!
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
gbueno6 said:
neXus PRIME, can you tell me what do you mean with "4. HTC perflock disabled (SetCPU does some magic when perf lock is disabled. Test n report)"? I mean, I have flashed your kernel and I have SetCPU installed but I don't know what is that "magic". Also, if you want, I can test or see what does happen with it enabled (so far, I see no issues).
I have selected: min 122, max 1008, smartassV2, sio.
Thank you very much!
Click to expand...
Click to collapse
I don't know what setcpu does that's why I called it magic.
Btw, I heard v2 is laggy, so v3 won't have zram enabled.
Sent from my HTC Desire X using xda app-developers app
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
neXus PRIME said:
I don't know what setcpu does that's why I called it magic.
Btw, I heard v2 is laggy, so v3 won't have zram enabled.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Ok then! I've found laggy my phone (1.18 deodexed ROM) while it's starting, may be more than with atis's kernel but other than that, I find it great.
Also, may I ask you which are the settings you'd recommend me to set?
Thank you very much!
EDIT: About SetCPU, according to the author through the app, Perflock disabler must be activated in the app if you have a kernel that prevent SetCPU from setting frequencies correctly (stock kernel for example). BUT with neXus PRIME kernel that has perflock disabled, you won't have a single issue using it and you don't need to set on boot Perflock disabler.
Sent from my HTC Desire X using Tapatalk 2
Here you go:
ZRAM is off for ppl having lag
v3
http://d-h.st/7C6
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
I can confirm that loop back devices work. I successfully chrooted Ubuntu using Complete Linux Installer...
Sent from my HTC branded muffin...
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
Stereo8 said:
I can confirm that loop back devices work. I successfully chrooted Ubuntu using Complete Linux Installer...
Sent from my HTC branded muffin...
Click to expand...
Click to collapse
Me too..
Sent from my HTC Desire X using xda premium
Re: Updated 28/02/13 [Kernel/modded] neXusKERNEL v2.0
By the way, @neXusPRIME change the op title to v3.0
Flowed from my HTC branded muffin...
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