Related
NON DEV ISSUES AND QUESTIONS ABOUT KERNEL POST HERE. THIS IS A WORK IN PROGRESS THREAD
HISTORY
I have been given Permission by the Kernel's Author (Gokhanmoral) to create this thread. Please put your issues or questions you have with the Kernel in this thread. Also functional request should also be made here. The aim of this thread is to filter out excess questions regarding the use and experience from the development thread. The author of the kernel and many experience users\testers and primary dev contributors need to use the Development thread in order to help Gokhan to implement his kernel. Would also request the community to contribute in terms of info to compile a knowledge base if you will. Many Thanks Gokhan and future contributors.
THANKS:
Samsung, supercurio, hardcore, Hacre, RAvenGEr, tegrak, cattleprod, codeworkx, hellcat, creams, vitalij, arighi, ninpo,netarchy .. Any others that I missed.
SiyahKernel v2.6.12
FEATURES
Can be flashed on Samsung ROMs and AOSP Based ROMS. Currently all Samsung 2.3.4, 2.3.5, 2.3.6, 2.3.7 based ROMS, CM7 (CM9 or any other ICS based ROMs are not supported) and MIUI ROMS are supported.
Based on linux kernel 2.6.35.14 + drivers from Samsung sources
Auto-Rooting
Custom CWM compatible Redpill Recovery from af974 (For more info: http://forum.xda-developers.com/showpost.php?p=21727136&postcount=9680 )
Custom boot animation support
Supports SetCPU (OC upto 1600MHz, UC downto 100MHz)
User customizable frequency steps. You can edit "freq_table" and use 25MHz as the lowest step and 1696MHz as the highest. You have 8 steps (it is fixed) but the frequencies can be set.
Supports undervolting (UV between 800 mV and 1500 mV)
Supports voltage control via SetCPU (thanks to netarchy, ninpo, hacre)
Stock voltages as default
smartassV2, lulzactiveV2 governors. and lots of other governors which are available as modules
Default governor is lulzactive (200-1200MHz)
Tweaked ondemand and conservative governors
no compiler optimization. it is just a myth.
Touchscreen fix (thanks to vitalij)
Increased touchscreen sensitivity
GPU clock (thanks to netarchy), voltage and scaling thresholds control interface.
I/O, scheduler, hotplug and vm tweaks
automatic battery calibration. (removed. thanks to Entropy512. we do not need battery calibration for SGS2)
Available I/O schedulers: noop, deadline, CFQ, BFQV3r1, V(R), SIO(default)
Available CPU governors: see this thread for the list of available governors and modules (thanks to droidphile)
/system/etc/init.d startup scripts support
Automatic backup of efs partition. You will have the files in your sdcard as well as /data/.siyah directory. copy them to a safe location in case you may need them later.
BLN (thanks to creams), liblights is autoinstalled if the existing one doesn't support BLN
supports advanced touch tune driver. thanks to vitalij Link. the control app from Web, from Mobile. Thanks to tegrak for the driver patch file download
2nd core application support (thanks to tegrak)
Automounting of NTFS volumes for USB sticks (ntfs on external card is not supported). although your rom says "clear storage", just check /mnt/usb folder. ntfs drives will be automatically mounted in read-only mode.
LZOP compression for the kernel to have very fast decompression. We have a VERY BIG kernel image because we have ntfs-3g, CWMManager and lots of other things both in initramfs and payload.
Integrated new&faster sha-1, crc32 slice-by-8, crc32c, jhash and rwsem algorithms
SCHED_MC enabled to have less power consumption.
Lower brightness levels for low-light conditions to save battery.
Brightness behaviour modification via setting min_bl, min_gamma and max_gamma values. you can control the lowest and hightest levels used in autobrightness.
Native BLN support for CM7 based roms.
Three GPU stepping (160-267-300) instead of two
optimized and configurable hotplug thresholds and rates.
Thunderbolt! script integrated (thanks to pikachu01)
Voodoo louder app support (thanks to supercurio)
Current Widget support while charging the device.
Charging the battery stops when the battery draws less than 100mA (stock value is 200mA).
CIFS, SLUB, FUSE, NTFS, cgroup_timer_slack, autogroup,... and lots of other mambojambo that I forgot...
TO FLASH ZIP:
Use CWM Recovery and install zip file. Wiping cache&dalvik cache is recommended for those who use BLN.
if you lose root after flashing the kernel (unlikely), flash http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip in CWM.
FAQ (WIP)
General
Q: Does this kernel support latest i9100 ROM which is based on android 2.3.5 -2.3.7?
A: Yes, it does.
Q: Can I use this kernel on I9100G?
A: No, you cannot. Only International i9100 and Canadian (Bell Mobility) models are supported (Chinese or AT&T T-Mobile US are not supported). Also, I compile ntt-docomo version for each release but beta versions do not support gps and digital tv on ntt-docomo devices.
Q: Does this kernel support CM7 or any other AOSP based roms?
A: Yes, but it only support CM7 or MIUI based roms for now from 2.0 and above. If you are using another AOSP based Rom tell me and I will support it.
Q. What is the latest version of the Kernel?
2.6.3 is the latest and can be found here:
SiyahKernel Edition v2.6.12 (Please ensure you choose the right one for your phone)
Q. I have an International i9100 can I flash NTT version?
A. Important Notice: the one with "ntt" in the filename is NTT DoCoMo SC-02C version. do not flash it if you have EU version
Q. Where can I get the latest Kernel Source for this Kernel?
A. It can be Found Here: Kernel Source
Q.Are there any Variants based on this Kernel?
A. Yes there is DK SIYAH KERNEL
Q: Can I use app protectors with this kernel?
A: Yes, you can. But you have to flash EnableLogger.zip using CWM after flashing the kernel.
TO ENABLE ANDROID LOGGER USE THIS:
ENABLE LOGGER
TO DISABLE ANDROID LOGGER USE THIS:
DISABLE LOGGER IF IT IS INSTALLED
Battery & Performance Factors
Q: What is battery life like on this kernel?
A: Some have said the battery life has improved. Others said not as good as others, this however maybe down to rogue apps creating wakelocks. Could be the rom is does not take advantage of the kernels features or could be a bad battery. Let's just say your Mileage may vary...
Q. I keep hearing about AOS having a factor on performance, whats all this about?
A. The Android OS using quite a lot of resources. AndreiLux wrote and in depth reference post about this which you can find here: [REF][Rewrite 26/10] What the Android OS usage is and what it's not
Q: What can I do to improve battery life?
A: put your phone into airplane mode or do not use packet data when you are not using it. Check for Rogue Apps and also check for unnecessary wakelocks and close them.
Q: I get random reboots or freezes. What should I do?
A: Make sure you boot in Recovery wipe cache and dalvik, then reflash the kernel. Although the kernel will do this if you apply the CWM.zip of the Kernel. It can still leave data behind.
If you are undervolting revert back to stock values. Then start reducing voltage by.25 and test. If that does not work make a note of:
1. When did it happen?
2. Which rom are you using, can you reproduce it
3. do you have any custom init scripts which changes kernel parameters such as freq voltage or anything else?
Post in this thread and we will try and help you.
Q: My phone doesn't go into deep sleep. What is wrong?
A: Make sure that you have cleared cache and dalvik-cache after you install the kernel. Also, reboot once more after the flashing. the phone doesn't go into deep sleep if it is connected to a charger or to a computer. There may be an application running in the background which is preventing deep sleep. In that case you can check which app causing the problem with "BetterBatteryStats" application (search in Google).
Q: do I need to recalibrate the battery?
A: You don't need to calibrate battery for SGS2. Thanks to Entropy512 to pointing out that our device uses MAX17042 which is specifically designed not to require calibration.
OC/UV and init Scripts
Q. What tools can be used to manipulate the clock speeds of this kernel?
SetCpu : http://www.youtube.com/watch?v=X9Sn4Uz4pkM Just an overview
Voltage Control: http://www.youtube.com/watch?v=XkhBFVUKBTQ Just an overview
No-frills cpu: More Info here about the tool
And Initialization Scripts
Tegrak Overclocking app is currently NOT SUPPORTED by this kernel
Q: What is an init.d script?
A:init.d scripts are the scripts which are executed during the boot time. actually, they are meant to initialize and deinitialize system daemons and manage some startup/shutdown tasks. but in android world they are just "autoexec.bat"s. so, it is a mix of rc.d and init.d directories in linux distros. everything in /system/etc/init.d are executed during the booting process. since it is not standard in every android device,some developers choose to execute files starting with "S" and some execute everything. in this kernel, everything in /system/etc/init.d is executed. you can create a script to change, lets say, voltages, schedulers, apply tweaks, run overclocking daemon or run anything else you can imagine.
Q. Okay how do I start to create my own Init.d Script for the kernel?
A: KWERDENKER has written a reference guide to help you get started. You can find his excellent Guide on POST #2 of this thread.
example of Kwerdenker scripts are also in Post 2.
DROIDPHILE'S NOOBS SCRIPTING GUIDE:
http://forum.xda-developers.com/showpost.php?p=19519757&postcount=10699
Here are other examples of init.d scripts supplied by Fenomeno83:
Another couple of nice init.d scripts created by fenomeno83
Q: where is the interface to change GPU clock and voltage?
A:There is now a GUI to change GPU voltage and Charging current it's voltage control and probably one by Gokhanmoral soon
For Undervolting your GPU use this Script from AndreiLux as a Reference:
Example CWM-flashable /system/etc/init.d/99gpuv script
Q: Which governor is the best? Which I/O scheduler is the best?
A: You have to try them and select the one you like. There is a very good explanation about governors and i/o schedulers here:
http://forum.xda-developers.com/showthread.php?t=1242323
HERE IS DROIDPHILE CONCISE GUIDE TO GOVERNORS
http://forum.xda-developers.com/showpost.php?p=19339524&postcount=10023
More info might help those you get a better understanding for schedulers:
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt Source: Cyanogenmod Githubs
Info about Lulzactive Governor.
http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html
Q: What is smartassV2 governor?
A: It is a governor to control CPU frequency. This governor has a built-in "profile" similar to SetCPU but the profile has no upper frequency limit. It tends to stay on lower frequencies when the screen is off and scale up very slowly, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Q: What is the best UV settings?
A: There is nothing as best UV settings. You have to find the best settings for your device for yourself. Start by decreasing 25mV on each freq and decrease it every day until your device becomes unstable.
Q. I notice one of the features is the ability of customizing Voltages for Charging?
A. Gokhan has written a script which he converted to be applied using CWM recovery (PLEASE BE CAREFUL WHEN APPLYING THIS, IF YOU ARE UNSURE PLEASE ASK IN THIS THREAD BEFORE DOING IT)
Set AC and MISC charging current to 1000mA - CWM flashable (keeps USB charging current at 450mA)
Q. I read that different frequencies would assist in better battery performance do you have any examples of this so I can use it my script?
A. Bene2K11 Created some scripts which allows you modify the bus frequencies when using this kernel, they can be found here:
3 flashable zips for the lowest, mid and highest bus frequencies
MISCELLANEOUS
Q: Which version is the best?
A: supposedly, the latest version is the best. But if the latest version is beta there may be unstable code in it. testing the beta version and reporting bugs will help me. but it's your choice... try and see... maybe this kernel is not stable for your device at all, who knows... I will not answer any "what is the best?" questions and I kindly ask you not to ask that kind of questions since there is no answer to that.
My Thanks for their contribution to this thread to Gokhanmoral, AndreiLux, ChadouMing, Nilste, Matriak31,Ger5,Kwerdenker,Fenomeno83, Bene2k11,Droidphile
__________________
Reproduce with permission from Gokhan by Dragon546
[REF]Init-Script Reference Guide By kwerdenker
MANY THANKS KWERDENKER FOR THIS. REPRODUCED WITH HIS AUTHORIZATION.
Original post from kwerdenker here.
I hope some of you find this useful as a reference for creating your own init-scripts. This contains everything I use or at least remember about the options in this kernel. If I forgot something or made an error somewhere, please send me a PM and I will gladly correct it.
How to use these settings:
If you want to test some settings before you commit them to a script, you can use either the adb shell if your on a pc with adb installed or you can use Terminal Emulator directly on your phone. Remeber to enter superuser mode by entering su in the terminal before you try to set anything or you will get errors. After that just enter the line you want with the values you want to test (if the values are incased in "", keep them that way!). If you want to see if it worked just enter cat followed by the part behind the > of the lines and you will get the values that are currently set. Everything you do in this fashion will not survive a reboot of your phone, if you want to make them permanent you'll have to use an init-script. A how-to on that is (currently) out of the scope for this post. Have a look/search in the kernel release thread as there are many examples for that there. I'm sure with this post and these examples you can figure it out by yourself
The values in the echo commands are the stock values (from 2.1.1 version) if not noted otherwise
[CPU]
[Frequency]
[Steps]
# Controls which frequency steps are available
# Should probably only be used to set the lowest step to 25 and/or the highest to 1696
echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table [Scaling Min]
# Controls which frequency is use by the governor as the minimal frequency (has to be a valid value in the frequency table!)
echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq [Scaling Max]
# Controls which frequency is use by the governor as the maximal frequency (has to be a valid value in the frequency table!)
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq [Voltages]
# Controls with what voltages the frequency steps are supplied
# Highest step is to the left, lowest to the right
echo "1425 1325 1275 1175 1075 975 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table [Governor]
# Available governors: ondemand, lulzactive, smartassV2, conservative, userspace, performance, powersave, brazilianwax, savagedzen, smartass, lagfree, ondemandx
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor[GPU]
[Frequency]
# Controls with what frequencies the GPU works
# Valid frequency steps are 100 114 133 160 200 267 400
echo "160 267" > /sys/class/misc/gpu_clock_control/gpu_control [Voltages]
# Controls with what voltages the GPU works
# Lowest possible value is 800000, maximum is 1200000
# Changes are only possible in 50000 steps
echo "950000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control[IO]
[Scheduler]
# Controls how IO requests are scheduled.
# Available schedulere: noop deadline cfq bfq sio vr
echo sio > /sys/block/mmcblk0/queue/scheduler[BUS]
[Frequency]
# Controls with what frequency the bus operates
# Valid values are: 0 (400MHz), 1 (266MHz), 2 (133MHz)
# Highest frequency step of cpu is to the left, lowest to the right
echo "0 0 0 0 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
echo disabled > sys/devices/system/cpu/cpu0/cpufreq/busfreq_static # Use enabled to activate this feature[Charging Current]
# Controls how much power the phone is willing to draw from a specific charger type
# Values are from left to right: AC Misc USB
# !This is a dangerous setting. Use with caution and never change the USB value and never set the other ones higher than 1000!
echo "650 550 450" > sys/devices/virtual/misc/charge_current/charge_current
I will try to keep this post up to date with any relevant changes in the kernel.
Example GPU/CPU undervolting and underclocking scripts by kwerdenker please just use for Reference
Improved version of CPU undervolting script by kwerdenker please just as a reference
P.S.: I will not respond to request what settings you should use to achieve the highest score in a benchmark or how you get the most battery life. This is just to gather the information that is already floating out there. What you do with it is up to you
BETA and RC
beta releases will be available when gokhan releases them
Someone asked in another posting about whats the difference between the governors you can choose in Siyah kernel.
Here is an informative article from Github that explains the difference. The governors are from Cyanogen but I beleive it will give you a fair insight in their caracteristics for Siyah also.
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt
There are also a couple more governors you can choose in the latest RC. Maybe others can give some info. about their caracteristics.
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
nilste said:
Someone asked in another posting about whats the difference between the governors you can choose in Siyah kernel.
Here is an informative article from Github that explains the difference. The governors are from Cyanogen but I beleive it will give you a fair insight in their caracteristics for Siyah also.
https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt
There are also a couple more governors governors you can choose in the latest RC. Mabye others can give some info. about their caracteristics.
Click to expand...
Click to collapse
This is exactly the stuff I am looking for thank you nilste
Corndude said:
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
Click to expand...
Click to collapse
Corndude How does insanity do its reporting? is it like miui where you can see the app usage in battery usage section like stock's app manager?
Did you get the stats before on the last kernel you use? I am not on insanity but if I cannot answer your query others can.
Originally Posted by Corndude
Is it normal, that on 2.1 rc3 i cant see how much juice every app consumes???
Click to expand...
Click to collapse
Corndude How does insanity do its reporting? is it like miui where you can see the app usage in battery usage section like stock's app manager?
Did you get the stats before on the last kernel you use? I am not on insanity but if I cannot answer your query others can.
Click to expand...
Click to collapse
i did get the stats before rc3, also doesn´t show the monitor´s use. Insanity is just like cm7, same stuff.
http://forum.xda-developers.com/showthread.php?t=1242323
i do not know if it helps but a bit more regarding governors..
Corndude said:
i did get the stats before rc3, also doesn´t show the monitor´s use. Insanity is just like cm7, same stuff.
Click to expand...
Click to collapse
Did you just install Rc3 without wiping dalvik? Just want to check . I always do a dalvik and cache wipe before I use CWM to apply the kernel update or If I use Odin to apply the kernel I then boot up into CWM recovery and perform a cache and Dalvik afterwards
Nice thread. Can anybody explain/point me to a good guide on cpu schedulers? This kernel allows changing the scheduler, but i don't know which one is the best for my kind of usage: movies-games-browsing, gpu intensive stuff i guess. Thanks.
Matriak31 said:
http://forum.xda-developers.com/showthread.php?t=1242323
i do not know if it helps but a bit more regarding governors..
Click to expand...
Click to collapse
Any help is appreciated Mat. Ty for your input
No probs mate.. good idea regarding the thread...At least now the Siyah one can stay just kernel related and all the Q&A can be moved here now..Great job
Issue I had with RC2:
-3G not functional, I didn't realize this until a few hours later when I wasn't at home enjoying my network; tested phone signal, was able to make calls, was in a bit of a cellular black hole but others on the same, and other networks, were able to access data easily,
-Restored my APN's from b/u to address 3G connectivity and at this point I lost all signal, no IMEI, phone number, etc... and would get an FC if I attempted to open the dialer, this was back at home where I have no data issues ever,
-Restored a nandroid b/u and all was good; did not try restoring EFS prior to this.
Just curious what the issue might have been; EFS corrupted (seemed to be a step wise loss), other?
And yes, at this point I realize I should learn a lot more before testing betas, etc... it's on my list Other than that I was thoroughly impressed with the lulzactive governor.
dragon546 said:
Did you just install Rc3 without wiping dalvik? Just want to check . I always do a dalvik and cache wipe before I use CWM to apply the kernel update or If I use Odin to apply the kernel I then boot up into CWM recovery and perform a cache and Dalvik afterwards
Click to expand...
Click to collapse
Siyah wipes it all by itself when installing via cwm.
mudferret said:
Issue I had with RC2:
-3G not functional, I didn't realize this until a few hours later when I wasn't at home enjoying my network; tested phone signal, was able to make calls, was in a bit of a cellular black hole but others on the same, and other networks, were able to access data easily,
-Restored my APN's from b/u to address 3G connectivity and at this point I lost all signal, no IMEI, phone number, etc... and would get an FC if I attempted to open the dialer, this was back at home where I have no data issues ever,
-Restored a nandroid b/u and all was good; did not try restoring EFS prior to this.
Just curious what the issue might have been; EFS corrupted (seemed to be a step wise loss), other?
And yes, at this point I realize I should learn a lot more before testing betas, etc... it's on my list Other than that I was thoroughly impressed with the lulzactive governor.
Click to expand...
Click to collapse
What rom you using?
I am on RC2 on Miui as far as I am aware I did not think it would interfere with EFS or change modem. Was there any think else that might have cause the EFS corruption or APN changes.
Corndude said:
Siyah wipes it all by itself when installing via cwm.
Click to expand...
Click to collapse
You tried clear data on the app manager and reboot the phone?
i have this problem whereby UV settings are applied during boot. am using init.d scripts. it sticks for 5-10mins and then it automatically reverts back to stock values. anyone else facing this prob?
am running gingermod 0.7
dragon546 said:
What rom you using?
I am on RC2 on Miui as far as I am aware I did not think it would interfere with EFS or change modem. Was there any think else that might have cause the EFS corruption or APN changes.
Click to expand...
Click to collapse
I'm on DlevROM (XXKI4 based); Siyah 2.0 does back up EFS, so there must be a chance for corruption somewhere along the line.
dragon546 said:
You tried clear data on the app manager and reboot the phone?
Click to expand...
Click to collapse
Just wiped manually and restarted - works, thanks a lot
Please leave non-development related posts to the discussion thread in general section: http://forum.xda-developers.com/showthread.php?p=27389678
STOP! This kernel supports ONLY Samsung JellyBean or CM10.1 ROMs. It won't work on ICS, CM9.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources :-
Sources at http://github.com/gokhanmoral/siyahkernel-sgs3
Ramfs at http://github.com/gokhanmoral/ramfs-sgs3
Toolchain at http://github.com/gokhanmoral/android_prebuilt
Simply clone all to a directory and run build_kernel.sh in the kernel directoryFeatures :-
Samsung and CM10.1 support with a single kernel image
based on i9300 update9 sources
CPU OC/UC/UV
GPU OC/UC/UV (5 step GPU clock)
Audio enhancement and sound boosting for great headphone experience (partial-port of wm8994 based implementation from project-voodoo)
init.d support
Triangle-away app support
Auto-root
Adjustable charging speeds for AC and USB
Automatic EFS Backup
Samsung proprietary ExFat modules are loaded. Don't ask about ExFat support for aosp roms in this thread.
Kernel based gestures support by Tungstwenty. See http://forum.xda-developers.com/showthread.php?t=1831254
NTFS automounting for USB sticks, mounted to /mnt/ntfs folder in Read Only mode.
mDNIe negative effect toggle with 4 consecutive press of home button
mDNIe values can be adjusted using the interfaces in /sys/class/misc/mdnie.
Almost everything is configurable via simple and free STweaks (included in the kernel or from Google Play)
Dual-booting. You can have Samsung JB and CM10 ROMs on a single device at the same time.
slide2wake (WIP, still incomplete)
Known Problems :-
No known problems.
Thanks To :-
Chainfire, AndreiLux, Tegrak, Entropy512, Netarchy, Pikachu, Tungstwenty, Codeworkx, XploDwilD
This part will be expanded. most of the patches I applied are coded by someone else. please remind me if I forget to give credits to anybody..
Downloads :-
http://www.gokhanmoral.com/
Changelog :-
See http://www.gokhanmoral.com/ for changelog.
Todo:
these are my future plans and some of them are dreams only...
fix bugs
add optional teamwin recovery
implement BFN (BackFlashNotification)
...
Video Review of v1.7rc1 by KingRamo
IRC support and chat:
Server: irc.FreeNode.net
Channel: #siyah-kernel
web client: http://siyah.twosx.net/ (thanks to omniwolf)
READ THESE FIRST
First thing you need to have before posting to this thread is respect. If you don't have it for others you will regret leaving a post as people in this thread don't like disrespect. The items below are just detailed description of what "respect" means in this context. If you have common sense you probably won't need to read all the following items but please do read them anyway.
Never report any bugs to CM9/CM10 thread if you use it together with SiyahKernel
Do not ask questions to me directly. This is a common thread, not my personal inbox. Ask your questions in the thread and do not target them to anyone.
Do not expect answers to all your questions. There are some questions which nobody knows the answer of.
Do not forget that this is a development thread. There is another thread in general section for those who wants to discuss battery life and chats. If your post does not include a feature request, bug report or suggestion it should be posted to the other thread.
Make sure you state your ROM, settings and any other relevant information while telling about your problem/a bug. "I have lag", "I had crash" or any similar posts will be ignored if you don't give any more details.
No ETA for new version. Even if I sometimes talk about release dates those may change and they change for some good reason or because of my real-life obligations.
Make use of "Search this Thread -> Advanced Search". If you humiliate people and waste their time by asking a question which is answered in the last 3 pages I guarantee that you will be treated as you deserve.
You need STweaks app to configure/change most of the features in this kernel. However it is not required if you don't want to modify anything.
Never ever discuss anything deep-sleep related in this thread. I do not make modifications to prevent sleep and 99% of deep sleep problems are application/ROM related. discuss it in general section. I do not want any positive ("this kernel sleeps like a baby") or negative ("There is a big problem with deep sleep. Please fix it") messages in my development thread.
I am not interested in any bug reports if you undervolt your device. I don't want ANY kind of undervolting related discussions or bug reports in this thread.
Useful Links:
Almost everything that you need to know about Kernels, schedulers and so by droidphile
Another great post explaining more and ICS differences by droidphile
Although I put it in the first post, this is my github for kernel sources, initramfs and some more
You can find all the answers you need here, even those that I don't know
last one
FAQS and More
FAQS and More
In no particular order.
1. "How the heck do i flash the kernel.tar within device. I see a boot.img and recovery.img in the tar and not zimage like before?? I don't wanna increase flash counter by using odin from PC!"
A. Use mobile odin. (Paid on market, free on XDA).
Open the app, Click on "kernel", select the kernel.tar. Scroll down, select "flash firmware". Reboot.
2. "Why two mountable image files in tar?"
A. GS3 has separate kernel and recovery partition.
Kernel partition : /dev/block/mmcblk0p5
Recovery Partition: /dev/block/mmcblk0p6
Both partitions has a max size limit of 8 MB each.
3. "Does that mean i can flash only kernel/only recovery if i don't need the other?"
A. Yes. However, if recovery was modified to support a new feature in kernel, you may want to flash both.
4. "If i flash tar from Odin on PC, both kernel and recovery is flashed and i can't choose to flash only one?"
A. Yes, both are flashed.
5. "How to flash only kernel/only recovery with cwm flashable zip?"
A. If you know what you're doing, open updater-script in the zip and comment out the line that starts with write_raw_image for the one you don't need - kernel or recovery.
6. "Should i wipe cache and dalvik before flashing kernel?"
A. NO
7. "Best governor, best i/o scheduler for this kernel?"
A. Define best governor and best i/o scheduler!
Pegasusq is good enough to be responsive, battery friendly and quad core friendly if tweaked properly. Use any i/o scheduler. Sio/deadline are good.
8. "Why is Idle+Lpa default on STweaks and the recommended settings. In Siyah kernel for GS2, Aftr+Lpa was recommended!"
A. Aftr ofcourse saves more power than Idle if you consider what each of those low power state modes do. But combination of quad core architecture and pegasusq governor (or any external hotplugging logic combined with other governors) which need to respect rq values along with load thresholds makes it a little slower to turn off last 3 cores (if all the cores are ON obviously). AFTR requires that all cores except first (cpu0) be turned off - to kick in. So we're better off with Idle+Lpa.
However if you're using forced single core mode always (which is non sense in this powerful device), you can go for Aftr+Lpa.
9. "How do i overclock/underclock/undervolt GPU?"
A. Either use STweaks app or use a script
Ex:
#Frequency steps
echo 160 > /sys/module/mali/parameters/step0_clk
echo 266 > /sys/module/mali/parameters/step1_clk
echo 350 > /sys/module/mali/parameters/step2_clk
echo 440 > /sys/module/mali/parameters/step3_clk
echo 533 > /sys/module/mali/parameters/step4_clk
#Voltages
echo "875000 900000 950000 1025000 1075000" > /sys/class/misc/mali_control/voltage_control
10. "My device is not stable at 1.8 Ghz. But i still wanna overclock the device to possible maximum and show off to friends"
A. Try setting last frequency as 1750 mhz. (Modify 1.8 to 1.75 ghz with 1.7 ghz still in place)
Use kmemhelper interface. Put this line in your initd script.
kmemhelper -n exynos4x12_apll_pms_table -t int -o 0 14353152
11. "I OCed to 1.7/1.8 Ghz. My device is able to handle it. But i can't get high benchmark scores. Why?"
A. Your CPU is getting throttled during benchmark during benchmarking because of heating. This is a thermal safeguard measure. It might be getting throttled to 800 mhz or so.
Forget benchmarks, treat the overall responsiveness in daily usage as the criteria to determine if the device is fast enough for you or not.
12. "Any rule of thumb to increase life span of the battery? And I see percentage drops to 99 immediately after a charge till 100%"
A. Do not recharge to 100% often and even if you do, don't keep it plugged in 100% for long time. Best is to charge till 98%. And make sure charge does not drop below 10% while on normal use.
Charge dropping to 99% swiftly is a protection mechanism, not a fault with your battery or kernel or rom.
13. "I adjust the voltage by some mV in STweaks. I checked SetCpu and voltage has not changed!"
A. Voltage settings in STweaks follow VDD interface. They're applied ONLY during boot time. Why? The code is to reduce X mV specified by you in STweaks, for all voltages. If the settings is applied real time, it will cause reduction of voltage every time and instabilities.
14. "If I have no root, and flash this kernel using desktop odin will i get root?"
A. YES. However, if you don't see a CWM recovery, download and flash a recovery from Chainfire thread.
15. "Does the kernel backup EFS partition automatically?"
A. YES.
16. "Is there NTFS support?"
A. YES. Mounted to mnt/ntfs in Read only mode. Unmount and remount in Read Write mode if you need to.
17. "What voltage step does GS3 support while UV/OV?"
A. Regulator supports increments of +/-12.5 mV (Those who had GS2 will remember it's regulator supported +/- 25mV)
18. "Why is resetting STweaks profile recommended sometimes after a kernel flash?"
A. Your profiles are stored under /data/.siyah with ".profile" extension. ".active.profile" file under the same directory stores the name of your active profile. Contents in profiles are in the format parameter = <default_value>
There could be changes in Stweaks interface for a new build:-
i) Some new tunables were added
ii) Some tunables were removed
iii) Transposition of some tunables
iv) Default value of some tunable was changed.
When such a change occurs, your profiles should know it too so that it can contain all the parameters. That's why you have to reset profiles after a new kernel flash if it changes something in STweaks.
Resetting simply copies .profile files from /res/customconfig to /data/.siyah . You can do it manually using a file manager to avoid a reboot to recovery and back to rom. Kernel already detects STweaks changes to reset profile automatically on first boot after flashing.
19. "How to insert a module that's available in /system/lib/modules?"
A. Safe to be root. In terminal or adb
su
insmod /lib/modules/<module_name.ko>
20. "How to know which modules are pre-loaded by kernel?"
A. Terminal or adb:
lsmod
21. "I don't see an init.d folder in my rom. I wanna create some initd scripts. What to do?"
A. Using a root explorer create init.d directory under /system/etc. Set perm 777.
22. "After flashing a new kernel i see there are some stuffs missing from STweaks"
A. Either the support for those missing tunables were removed or just the STweaks interface was removed. The parameters might still be accessible through scripts. Check the file path to make sure.
23. "Does notification LED cause wakelock and lot of drain?"
A. Hm Yes and No. CPU has to wake to help turn on notif led and to turn off when it's timeout. When LED is blinking, no wakelocks are held. Notif led is controlled by a diff h/w and not directly by CPU.
24. "How do I know if my modified charge current settings (using STweaks) are effective?"
A. Use CurrentWidget from playstore. Monitor the reading while charging.
25. "What happens if my smooth scaling frequency is greater than my scaling max frequency?"
A. Smooth scaling will be inactive/disabled.
26. "Can I flash this kernel on a non-international variant - At&T/Korean/Japanese...?"
A. NO. Don't risk 800 dollars. Dev might release different variants for these devices later.
27. "I tried setting a negative value for a symbol using kmemhelper interface. I see the value is not applied properly. What could be wrong"
A. The negative value might be detected my kmemhelper as an argument. To prevent that, use two minus signs (--) before the negative value.
Ex: "kmemhelper t int -n touch_boost_level -- -1" (This resets touch boost frequency to default).
28. "I wanna disable all the audio enhancement stuffs. How?"
A. In your script
echo 0 > /sys/class/misc/scoobydoo_sound_control/enable
29. "Least voltage for a CPU frequency I can undervolt to?"
A. 600 mV. Maximum = 1500 mV
30. "Does sound enhancements in stweaks applies to bluetooth headsets?"
A. NO. Only for wired headphones.
31. "Do we have temperature sensor in our CPU?"
A. YES
32. "I have this habbit of unknowingly pressing home button multiple times and that result in inverting colors on my screen."
A. Disable "mDNIe negative toggle under Screen tab in STweaks.
33. "I sometimes get unexpected reboots. What could be wrong?"
A. Number of reasons.
- Problem from ROM side - wrong dpi setting for an app, wrong build.prop tweaks, etc.
- Too much UV on CPU/GPU
- Too much CPU OC/GPU OC
- CPU/Battery heated up too much because of weather/benchmarking/faulty charger, etc
34. "I want to help dev debug an issue providing a kmsg. How to?"
A. After the problem (random reboot/freeze/lockup), do not pull out battery to recover. Just long press power button so that device can reboot. Then connect device to PC, (provided you have setup adb), type
adb pull /proc/last_kmsg
Save the file as .txt and post in the thread along with description of the problem and possible way to reproduce it.
If you can't use adb from pc, just copy last_kmsg file from /proc directory to internal sd, copy it to your PC and post in the thread.
35. "I'm not able to copy Person X's undervolting settings. Why? Sometimes, across different builds of Siyah, my UV settings are stable in one version and not in another. Why?"
A. One or more of the following
- Every device is different - diff grades of CPU
- CPU drivers might change across different builds
- Power requirements may differ depending on the temperature, altitude or the defaults.
36. "GPU OC/UC range?"
A. 54 to 700 mhz. With voltage range of 600mv to 1200mv at 25mv steps.
more might follow..
Know the STweaks Tunables
You have a custom kernel and an app to control different tweaks. Read below to have a fair understanding of all the sliders and drop-downs in the app plus read some faqs.
Q. "What's STweaks?"
A. It's an app developed by GM to provide a simple interface for various kernel tweaks.
STweaks works using /res/uci.sh interface. (Universal Configurator Interface). Ideally when you run /res/uci.sh config you get an xml file. The app render that XML file to an UI. (The xml is customconfig.xml in /res/customconfig directory)
Q. "Where are profile files (default, performance etc) stored in my device?"
A. /data/.siyah with extension ".profile"
Contents are in the format <tunable> = <value>
Q. "How come STweaks takes a little long to load every time? Other CPU tuner apps like SetCPU opens faster!"
A. Stweaks needs to query the values of ALL tunables from the active profile file, then set the UI elements (sliders, checkboxes, dropdowns, etc) to match the values queried. Only after these it can expose itself for you. So yeah! Some time is needed.
It loads in about 2 seconds now.
Q. "So every tunable possible with SiyahKernel is included in STweaks?"
A. NO. That would make the app complicated and while some users like to have lotttsa tweaks in the app, some users prefer the opposite. So to be fair, STweaks will not be cluttered with way too many options.
For users who know what they're doing, there are scripts, and kmemhelper.
Q. "After flashing a new version of Siyah, I can't see STweaks in my app drawer. Help!!"
A. Using a Root File Explorer, copy STweaks.apk from /res directory to /system/app. Set permissions rw- r-- r--
Q. "I find that after flashing a new kernel version, while adjusting some tunables there's no effect."
A. In the app, under EXTRAS Tab, hit "Reset settings to default". Now reconfigure all your settings. Should be fine in most cases.
Q. "Sometimes, after flashing a new kernel build, i see all my settings are reset to kernel defaults. Is it normal?"
A. YES. It's just so that profile files contains all the tunables matching config XML in the latest build. If resetting is not done, some settings will not work.
Q. "Does that mean - every time I flash a new kernel build, I need to reset settings?"
A. NO
Q. "What should I change in STweaks to have best battery/best performance?"
A. Read below to know what each tunables do. If you still don't get it, don't change anything. Trust defaults. All will be good.
1) CPU Tab
Gentle_Fair_Sleepers:-
This is a CFS tweak. CFS aka Completely Fair Scheduler is your default Task Scheduler. Task Scheduler is responsible to manage task executions - decides what task to execute next from a queue. CFS scheduler tries to fairly distribute the CPU time among all tasks in such a way that each of them gets the same amount of the virtual run-time. CFS maintains two arrays - active and expired. Tasks once served from active array are placed in expired array. When there are no more tasks in active array, the two arrays are swapped. Sleeper Fairness means to consider sleeping tasks similar to the ones on the runqueue and credit the sleepers in a way that it would get CPU as if it were running. With Gentle_Fair_Sleepers enabled, sleeping tasks will get a little bonus time w.r.t to their virtual run time. While this may seem fair in some cases, disabling this tweak may possibly improve UI responsiveness:- may be because sleeping tasks are not given additional priority and the task that's responsible for UI do not sleep while screen is ON.
* Arch_Power:-
Another scheduler tweak. Helps in using specific ARM topology functions instead of generic functions. Benefits may include idle higher number of threads in a core, etc.
* CFS Tweaks:-
Three options which sets different value for your task scheduler's a) Minimum Granularity b) Latency c) Wake-up Granularity
A new "epoch" or a new time origin begins when scheduler swaps active and expired array.
Latency is the length of an epoch in nano seconds.
Minimum Granularity is the granularity of one epoch.
Wake Up Granularity is the ability of tasks being waken up to preempt the current task (5 ms by default). The larger the value the more difficult it is for the task to force the preemption.
- Samsung Defaults:- Leave it as Samsung defaults if you want higher benches.
-Linux Kernel Defaults:- My fav.
-Thunderbolt Scripts Defaults:- Pikachu's tweaks are aggressive low values for parameters. May improve UI responsiveness.
CPU Idle Modes:-
Leave it as Idle+Lpa. AFTR seems to be a difficult world to conquer for i9300.
* Smooth Scaling Level:-
Leave it as 1800mhz (which disables smooth scaling) if your governor has the parameter "freq_step" (ex: Pegasusq). Otherwise, the two concepts may conflict. Use smooth scaling for other supported governors. CPU driver scales CPU to frequency as defined by Smooth Scaling Level before jumping to Max Frequency.
Sched_mc:-
Leave it disabled = 0. 1 will overload first core, 2 will try to save power by biasing task-wakeups to semi-idle core.
CPU Undervolting:-
[Courtesy Andreilux for the info] 32 nm Exynos 4412 on our device decreases the need for higher voltages for transistors to switch and decreases voltage leakage. So they actually successfully switch more of the time compared to SiON on Galaxy S2 i9100 where leakage was big enough to not make a transistor switch and crash the system. In short, this is why GS3 supports higher UV compared to GS2. You might be lucky enough to UV more than 200mv on certain frequencies. Try on own risk.
Max CPU Lock:-
Defines no of cores to be used along with Pegasusq governor. Leave it quad core. You have beast of a phone. This parameter actually changes the max_cpu_lock parameter of your governor - pegasusq or lulzactiveq.
CPU Governor:-
Use Pegasusq.
CPU Max Frequency:-
Sensible OC for our device is 1.5 Ghz. You can try more and see what happens.
CPU Minimum Frequency:-
Use 200 or 100.
2) CPU_UV Tab
Like SetCPU or voltage control, sets voltage per CPU frequency. Note that the values DO NOT represent the actual voltage levels on the frequencies. If you UV in Stweaks and also use SetCPU to set voltage levels, SetCPU will over ride Stweaks.
3) GPU Tab
* Mali Touch Boost Level:-
If this option is enabled to any steps, when you touch on the screen/press soft back or menu keys/press homebutton - GPU voltage is set to the GPU step that match the step set by you here and frequency is set to that step. This may helps in better responsiveness of unlocking via lockscreen, etc. Note that, this doesn't mean GPU is locked to that forever. After one second, depending on thresholds and stepcounts, soon GPU is clocked down or up.
If Mali Touch Boost Level is disabled, GPU resumes at lowest frequency (your first step).
GPU Frequency Steps:-
Now we have frequency steps taken from Korean sources, as hard coded in clock-exynos4212 file. You won't find a formula to calculate valid frequency steps. (Unlike i9100 for which any GPU step was 800 divided by an integer)
GPU Voltage Levels:-
You may be able to UV a little more compared to GS2 if your ex device was GS2. Try and see. (Thanks to 32 NM SoC). Remember that you will know UV was too much only while GPU is being heavily used - like gaming.
GPU Thresholds:-
If you're not sure about this, use default thresholds. Wrong thresholds can cause lags.
* GPU Stay Counts:-
Stay count is the number of Seconds GPU should stay at a frequency level before it can scale up or down, overriding "load exceeds threshold condition". To avoid any possible stutters in gaming, use staycount = 1 second for the last step. May be for 4th step too, just to be sure.
If you don't find StayCount interface in the app, use script.
echo "0 0 0 0 1" > /sys/class/misc/mali_control/staycount_control
From left to right, each digit represents StayCount for lowest to highest GPU frequency steps.
4) AUDIO Tab
Speaker Tuning:-
Check to enable better bass response on speakers. Note that GS3 speakers don't play well with bass (even with open source audio HAL developed by codeworkx for CM10. So if you find sound distorting on speakers, uncheck this option instead of trying to play with some equalizer.
Speaker Amplification Offset:-
Default zero. Increase to amplify speaker volume. At level 5 or 6, speaker is most likely to distort playing ringtones/sounds.
Headphone Amplifier:-
Volume boost for your headphones. Level 0 = -57 dB. Level 63 = +6 dB which is the hardware maximum. Please take care of your hearing.
3D Effect:-
Stereo expansion may tighten the stereo field. In general, there are multiple techniques to achieve surround effect/3d effect/stereo expansion effect.
3D Effect Gain:-
Valid only if 3d effect is enabled. Higher value may not sound pleasant to most ears. 2-4 should do.
EQ Presets:-
Use inbuilt presets or use graphical equalizer bands to tune the 5 band equalizer.
Graphical Equalizer:-
The five band equalizer(with a range of -12dB to +12dB) is a hardware equalizer. So it controls all the sound coming from your headphones. Software equalizers such as inbuilt EQ of powerampp can only control the sound output 'formatted' by this 5 band h/w EQ. As you know, the first two bands - Lows/Bass. Middle one - Mids/Vocal and last two bands for - Highs/Treble.
Negative Digital Gain:-
Or dynamic range. Increase this to prevent distortion. It defines how much volume is to be digitally reduced from headphone amplification level.
FLL Tuning:-
Aka Anti Jitter is an audio enhancement technique as an internal clock optimization to reduce noise and produce a better quality sound.
DAC Oversampling:-
Increases dac oversample rate for a 48 khz rate and produce better outpund sound.
DAC Direct:-
Aka DAC ME, Bypass analog channels and redirect sound directly to output.
Mono Downmix/Force Mono:-
Force mono sound even if source is stereo.
5) SCREEN TAB
* MIN_BL, MIN_GAMMA, MAX_GAMMA:-
In simplest form, set this higher to have lower brightness at bright conditions on automatic-brightness settings. And vice-verse.
We have lowest brightness for a brightness level read from sensor less than min_bl. Any level higher than min_bl will be linearly mapped to min_gamma:max_gamma to interpret brightness of the display. Difference between min_gamma and max_gamma along with their values affect overall brightness response curve.
mDNIe Sharpness Tweaks:-
Makes thin fonts more readable. You're most likely to see weird display if you disable this option.
mDNIe Negative Toggle:-
If this is enabled, quickly pressing home key four times will invert all the colors on your scree. Useful for ex: Reading a webpage in the dark which has white background by default. By inverting colors to make it black, your eyes will strain lesser, plus it saves battery in such cases.
Touch Boost Level:-
Defines the frequency to which CPU is instantly ramped up to when we touch the screen. Advantage? UI responsiveness. Setting this too low might be a v bad idea on some devices.
Slide2Wake:-
If enabled, slide on screen in a straight fashion from left to right to wake your device. Helps prevent wear down of physical home/power buttons. If in doubt this drains more battery, leave it disabled.
FB Early Suspend Delay:-
Early suspend delay to run CRT off animation. If you're sure that Settings > Developer Options > Windows Animation Scale is 1x or higher (not 0.5x or off) and still can't get CRT-off animation to work, set this param to 100 ms or so.
6) MISC TAB
Android Logger:-
Enable disable android logger. Logger hardly uses any extra battery, and will be very useful if to pull a log after a crash or freeze. Leave it enabled.
* Insecure Adbd:-
Enables to run your Android Debugging Bridge Daemon (adbd) in root mode by default. Use "adb remount" command in a terminal to mount /system as r/w.
I/O Scheduler:-
Use any among deadline/sio/noop.
* Zram Size:-
Compressed swap space aka compcache aka zram allocates defined amount of space from your physical RAM as compressed swap space. You can debate all along to see if zram is useful on a fast device like GS3 with a fast flash storage inside. If in doubt, disable this option.
Notification LED Behavior:-
Force blinking/fading of notification LEDs. Useful for Sammy based roms. (aosp roms has blinking/fading setting inbuilt).
AC Charge:-
Charge current from your wall charger. Increase the value for faster charging at own risk. If you see currentwidget app displaying only 800/1000 mA (when you have set 1200 mA in stweaks) while connected to car charger - it's because the charger can not output more current than that.
USB Charge:-
Charge from usb charger. Increase at the risk of possible damage to PC motherboard. (if it's an old board)
Discrete Wakelock Status:-
Helps betterbatterystats app to report deleted and non-overlapping wakelocks. You may see new wakelocks like your mailclient-inbox-sync, etc if this option is enabled.
Remove Root:-
Some apps detect root and refuse to work if found (certain banking apps for example). To remove root, click this button, run your app and re-enable root when you're done.
Auto Install Root:-
Tries to install superuser apk and binary. If it fails, download latest superuser flashable zip from here and flash in recovery OR download SuperSU from playstore.
6) DUALBOOT TAB
Reboot into 2ndRom Utils:-
Reboots to alternate recovery where you can configure and play with dual boot options. This doesn't change your cwm recovery, but just runs an alternate recovery.
Reboot into 1stRom:-
As it says, reboot to 1st rom without displaying a timeout.
Reboot into 2ndRom:-
As it says, reboot to 2nd rom without displaying a timeout.
No boot logo:-
Check this to disable Siyah bootlogo displayed during dual-boot rom selection time out. (If you're dual booting, logo will be shown anyhow)
Default Rom:-
Specified the default rom (among 1st and 2nd) to which device will boot into, if no keys are pressed during boot. If 2nd rom is default, pressing home/vol down keys will boot 1st rom.
Hijack Recovery:-
We know the second rom utilities aka embedded recovery is a part of the kernel - it holds the same partition as kernel. You can use this button to flash the embedded recovery to main recovery partition (overwriting your existing recovery) so that 3 button method/booting to recovery using extended power menu will take you to Siyah recovery. This is NOT a dangerous operation. You can flash cwm/twrp recovery anytime if you need another recovery.
7) EXTRAS TAB
Reset Settings to Default:-
Reset the profile file, and resets all values in device files to kernel defaults.
Check for Updates:-
Checks and downloads a new build.
Flash Kernel:-
Flash a .tar kernel. Alternative to Mobile Odin!
* Indicates tunables removed from STweaks as of now.
Flashable Zips
Update: Find sample Stweaks Profiles as flashable zip here. http://forum.xda-developers.com/showthread.php?t=2034981. Profiles after flashing will be available in the profile app.
Here are 5 Governor Tweaks scripts as flashable zips.
Flash remove_governor_tweaks zip to remove init.d script that contains governor tweaks. One governor zip can be flashed over another and it will just replace the previous. All governor tweak scrips contains tweaks for pegasusq and luzactiveq. Gamerstweaks is also a governor script that's similar to extremeperformance script but does some additional GPU tuning (for which there is no interface in Stweaks) to enhance gaming experience.
Since order of execution is like this:-
1) STweaks applies its settings
2) Init.d scripts are executed
3) Apps such as SetCPU applies its "set on boot" options,
Script applies the tweaks to the governor selected in Stweaks (depending on if it's pegasusq or lulzactiveq). So if you want pegasuq tweaks to be applied, make sure pegasusq is the default governor in stweaks, and same for luzactiveq.
I will keep updating zips while new kernel builds are released - if it changes any tunable.
DualBoot FAQs
Dual Boot FAQs
* "Alternate Recovery" or "Embedded Recovery" is embedded recovery that's the part of kernel since 1.7.x versions when dual booting was introduced. It's the recovery you boot into using "Reboot to 2nd Rom Utils" in STweaks.
"Regular Recovery" or just "Recovery" is your CWM recovery in recovery partition (/mmcblkp06) which is accessed by 3-button method or "boot to recovery" in the extended power menu from your rom.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, FM radio and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before. And if you don't want to see the Siyah logo as well, create a .nobootlogo file without any extension or content in internal SD.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p10 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Special Cases:-
5) Use an existing nandroid backup as 2nd Rom (and existing rom as 1st)
6) Use an existing nandroid backup as 1st Rom (and existing rom as 2nd)
Prerequisites for any setup is
a) Flash latest Siyah
b) Atleast 90% battery left.
c) 2 GB free on internal SD.
d) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Hit "Run 2nd Rom Utils" in Stweaks app from your current rom. This will run the embedded recovery in the kernel. Under dual boot options, wipe 2nd Rom data and cache+dalvik. Format 2nd Rom System.
ii) Using install zip to 2nd rom option, flash aosp rom as 2nd rom.
iii) Fix 2nd Rom permissions
iv) Flash Siyah again
2) Present sammy, setup aosp as primary:-
i) Hit "Run 2nd Rom Utils" in Stweaks app from your current rom. This will run the embedded recovery in the kernel. Under dual boot options, Clone 1st Rom to 2nd Rom.
ii) From recovery (your default cwm recovery which can be accessed from extended power menu or 3 button method), full wipe and install aosp rom zip as you'd normally do when you were single booting.
iii) Fix 2nd Rom permissions
iv) Flash Siyah again.
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first Rom, flash sammy.
5) Restore the nandroid backup using "Restore as 2nd Rom" option in the embedded recovery. If there are problems while restoring, wipe 2nd Rom data, cache+dalvik, format second rom /system and try restoring.
6) Clone 1st Rom to 2nd Rom from embedded recovery then restore nandroid backup from your regular cwm recovery.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure to fix permissions of second rom after setting up 2nd rom for the first time or else you're likely to see a black screen.
- If Wi-FI on aosp doesn't work, flash a sammy ICS rom (on to 1st rom or second rom depending on location of aosp) before flashing aosp rom.
- If NFC doesn't work, flash that NFC fix zip you can find on XDA which replaces ICS NFC firmware on aosp with JB NFC fw from sammy.
- Even if you're installing second rom for the first time, wiping data and cache+dalvik of 2nd rom and formatting system of 2nd rom is necessary; As it creates empty 1.5 gb system.img to be used as system partition for 2nd rom and also creates data directory of second rom in /.secondrom dir in the internal sd.
6. "How to boot into primary rom?"
A. Wait for the 3 second timeout or press volume up/power to skip the timeout. Or use the option in Stweaks if you're booted into second rom already.
7. "How to boot into secondary rom?"
A. During the 3 second timeout, press volume down or home button. Or use the option in Stweaks if you're booted into 1st rom already.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest Siyah.
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from recovery. Flash Siyah again if Rom zip flashed another kernel.
14. "How to flash newer version of 2nd rom?"
A. Using stweaks, boot into 2nd Rom utils. Flash the rom using "Install zip to 2nd Rom" under dual boot options. Flash Siyah again if Rom zip flashed another kernel.
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. You can use any recovery. Alternate recovery can be just run using the option in STweaks.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see Stweaks app in second rom."
A. Delete /system/.siyah/stweaks-installed file in 2nd rom. Reboot to second rom.
20. "Do I need to anything special before flashing a newer Siyah?"
A. NO. Just flash kernel as tar or in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition.
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. While on 1st rom, copy the file /data/.siyah/default.profile to /data/media/.secondrom/data/.siyah directory. If you modify STweaks settings in 2nd rom and want to avail same settings on first rom, do the other way around. (Copy "default.profile" from /data/media/.secondrom/data/.siyah to /data/.siyah while on 1st Rom)
22. "How do I remove everything related to DB and run single boot again?"
A. In recovery, under dual boot options - "delete 2nd Rom". OR Delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Reboot to 2nd Rom Utils" in STweaks change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings. Using extended power menu or 3 button method, you always lands in your own CWM recovery.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the feature embedded recovery, which can be accessed using "Reboot to 2nd Rom Utils" in STweaks app.
28. "I booted into recovery using 3 button method. But some dual-boot options are not working even though dev said they're implemented.
A. Use "Reboot to 2nd Rom Utils" in Stweaks app to boot to embedded recovery.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p12 = /data
mmcblk0p9 = /system
mmcblk0p8 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk10 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p12 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p10 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Nice! I like your work on Galaxy S2 hope to see you here often and regulary updating your thread.! well done mate
Sent from my GT-I9300 using XDA
Thanks my friend
Inviato dal mio GT-I9300 usando Tapatalk
energie said:
Best kernel ever finally
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
Absolutely
Gesendet von meinem GT-I9300
gokhanmoral said:
last one
Click to expand...
Click to collapse
This is gonna be HUGE!!!
Thanks GM
Sent from my GT-I9100 using XDA
+
siberian tiger said:
This is gonna be HUGE!!!
Thanks GM
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
fully agree ...now i am using 0.94 and no problems at all
PS: just a USB Mass Storage is only little thing i miss...but DropBox and FTP are ok too
Looking forward to this. Using 0.94b now and it is oh so smooth. I'm sure 1.0 will be even better.
Cheers gokhanmoral.
/love....
Many thanks, the best kernal ever, is the focus on battery life on this release? can the kernal fix the high cell standby issue? i believe my device will keep your kernal until i sell the device !
Thank you
WOOT!
Where is the download link I opened the link above but there is no 1.0 only hv 94
Sent from my GT-I9300 using XDA
ThisIsIt...
saberzaid said:
Where is the download link I opened the link above but there is no 1.0 only hv 94
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
compiling now.. I will edit the blog post after editing the first post in this thread.
As I tested v0.92b, this kernel is very promising ( of course because of Gokhan ) but not yet stable. I love to see @gokhanmoral progress like sgs2 kernel .
I will test v0.94b right now .
MIUI v5 (3.12.13) for P760/P768 and P769
Most of bugs are fixed and it's very stable after test it about a week. There're some know issues you should aware of, so please read it carefully below.
Only for P760/P768 and P769 phone with Unlocked bootloader! (should work with P765)
Thanks AntonX for his P769 kernel and files.
Thanks Versatil2010 and NGD1 to help me test P769 ROM
Click to expand...
Click to collapse
Features
Update to MIUI v5 - 3.12.13
Based on my CM 10.1.3 unofficial 20131214 (build only for this rom, not publish)
Jellybean 4.2.2
Aroma installer for choosing phone model, applications and enable NFC (for P760 only, my P768 kernel didn't compile with NFC enabled)
Swap internal/external sdcard
MTP / UMS (enable via mtp.sh & ums.sh)
Reduce headset volume and increase speaker volume
Move app2sd using Titanium Backup
XperiaT keyboard by Ghostfreak NB
Multi language support with patch, include these languages
Enable some Settings (some works some don't work), ex. Front key light, Multi touch config, display color (I think these don't work), Noise supression (Don't know this work or not)
MIUICamera
Boot to Recovery in Power menu
Navigation bar mod (selectable in Aroma installer)
Modified Kernel by AntonX (P769) from this thread
Compiled with Linaro 4.7
Extended frequency table with 200MHz, 1200MHz, 1350MHz (overclocking doesn't work on some phones)
Slightly undervolted
Userspace voltage control. Use SetCPU, VoltageControl, or similar. Warning: Save a recovery script with either of these programs before playing with voltages!
GPU is extended with 384MHz, IVA with 430 MHz
Selectable screen-off maximum frequency
Included SmartassV2 governor, SIO scheduler.
Few performance tweaks.
Modified Kernel 30.0.31 CM+ for OMAP board (P760/P768).
OC - 300, 600, 800, 1008, 1200 Not OC by default, you can use CPU control app from market to set max frequency
UV - 925, 1075, 1175, 1275, 1350
Add SIO, SIOPLUS, FIFO, ROW and VR I/O scheduler (Default : CFQ)
Add sanjose, lazy, interactiveX, ondemandx, pegasusq, adaptive, adaptivex, smartass2, zenx and abyssplug CPU Governor (Default : interactive)
Change log - What is changed since my last update (3.11.29)
3.12.13
3.12.6
How to install
CWM Backup your phone.
Download rom and put it in sdcard.
Download Google Apps for MIUI and put it in sdcard. (I remove google setting which conflict with MIUI and some rarely used app. You can reinstall it in market)
Boot into recovery and Clear cache, dalvik cache and format /system. (Full wipe is recommended)
Flash rom, then flash Google Apps for MIUI. Please select your phone model (P765 user should select P760).
Flash all patch by order (If any)
Reboot.
Download Link
2013/12/18 - 3.12.13 upgrade patch (You must on 3.11.22 or later before flash this)
English/Chinese md5:06c965e8ac1327f5901c90503562b691
Multi languages, coming soon md5:
2013/11/27 - 3.11.22 full rom
P760/P768 md5:d809123e8e2cf33ec1acb75f0b31a345
P769 md5:7d63a8aff963d1db82a140aa5b382a36
Multi languages patch md5:f3ce08d20bcecba461629f5186b14891
Recommend Apps
Weather BZ. It's compatible with MIUI Weather (thanks @garik345 for this info)
Titanium Backup. Some app install directly to sdcard some don't. You can use this app to move app to sdcard.
FasterGPS. You can use this program to change your gps config & region.
MIUI Usage & Tips
56 Tips You Should Know About MIUI V5
MIUI: 13 Shortcuts you need to know!
MIUI Manual
The Official MIUI V5 User Guide (IN PROGRESS)
Bugs
Lyric in 4x4 Music widget scroll all the way to bottom. Don't know this is my bug or widget bug?
Sound is muted when you got another call during conversation.
MiuiCamera flash may not work in the first shot, (Set flash on)
In Browser, select text in link not work.
Recording sound is too low (fixed in next update)
Known issues
Sometime my Wifi MAC address reset to 00:00:00:00:00:00, solve by reboot phone 2 times (or 1 time if it's solved). I rarely got this problem, but it still there. I think it occur after some app error.
In Play Store, if you got download via wifi only while on 3G, it's because download limit setting in Download app. Please open download app and adjust download limit to 20M.
Bugs Fixed/Feature Added
2013/12/18
Update to MIUI v5 3.12.13
Fix recording sound too low
2013/11/27
Update to MIUI v5 3.11.22
MiuiCamera from latest Mi2 device
Add bluetooth audio fix (need testing, fix came from AntonX rom)
Add in call volume adjustment (fix came from AntonX rom)
Fix Call waiting FC
What's next
MIUI update weekly, I'll update this rom every two weeks.
Screen shot
{
"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"
}
Version History
2013/12/18 v.1.2
Update to MIUI v5 3.12.13
Fix recording sound too low
2013/11/27 v.1.1
Update to MIUI v5 3.11.22
MiuiCamera from latest Mi2 device
Add bluetooth audio fix (need testing, fix came from AntonX rom)
Add in call volume adjustment (fix came from AntonX rom)
Fix Call waiting FC
2013/10/30 v.1.0
P760/P768, md5:cb7155c1b5d783272dd9d7462511fa33
P769 md5:7a69fbf0bc834b9d7ca6ce100d2e64b6
Multi languages patch - 3.10.25, md5:b8827219ca5175829d93f51e84c545d7
Build separate rom for P760/768 and P769
[Added] MIUI Camera
[Added] Update to MIUI v5 - 3.10.25
[Removed] Remove CM Trebuchet because it don't work (and I don't want to find out why.)
[Added]Create a multi language patch instead of include it in rom.
[Added] modified framework to enable nav bar. You can select it in Aroma.
[Added] Boot to Recovery menu (Thanks ZduneX25)
2013/10/24 - RC.1 release MIUIv5_L9_RC1.zip, md5:61c5fd416d59ad61c1df543f529997e1
[Removed] SDCard emulated
[Added] Swap internal/External SDCard
[Added] UMS/MTP script (/system/xbin/ums.sh, mtp.sh)
[Added] Move app2sd using Titanium Backup (Sorry no option in MIUI App setting)
[Added] XperiaT keyboard by Ghostfreak NB
[Added] Multi language support
[Added] Update to MIUI v5 3.10.18
[Fixed] Music FC (MIUI update)
[Fixed] LGE Guard FC (MIUI update)
[Fixed] Long press Home, Back & Menu works in Buttons setting
[Fixed] Background blur/transparent effect not work. (Fixed with my workaround patch)
[Fixed] MIUI dialog background is black (ex. Shutdown dialog)
[Fixed] CPUBooster & NetworkConfig works
2013/10/12 - BETA.2 release MIUIv5_L9_BETA2.zip, md5:352e9272f95d34e6e4fb1485f7d7cd41
[Added] Now support P769. Big thanks to AntonX for his P769 kernel and files
[Added] Add all CM & MIUI removed apps back
[Added] Modify Aroma installer to allow application selection
[Fixed] Long press Home to bring Recent app may not work. After fixed it still not work well with "Menu" button.
[Fixed] Menu item in "Display" below "Font size" display as @2131495341
[Fixed] Add MIUI shutdown screen
[Added] Emulate internal sdcard
[Fixed] Music & Pictures don't show in player/gallery.
[Fixed] Screenshot reboot your phone. (Vol- + Power)
Bugs
Music sometime get FC because sdcard is FAT32 and Music require some ext4 feature.
All MIUI background blur/transparent effect not work.
2013/10/10 - Patch 02 for BETA1 P760 md5:a883a38075902eda4e44dc9f43c38bf0, P768 md5:cb8670033b3dba611208815b4b3ac9dc
[Added] Swap internal/external sdcard
[Added] UMS
[Fixed] Music & Pictures don't show in player/gallery
2013/10/10 - Patch 01 for BETA1 Flash in recovery over BETA1 version, md5:e7e659c1f7f78b1cecd835a42d914ea7
[Fixed] Long press Home to bring Recent app may not work. After tested, Recent app action don't work well on "Menu" and "Home" button. I switch it to "Back" and it always works.
[Removed] Weather app only display City in China You can install other weather app from market
[Fixed] Menu item in "Display" below "Font size" display as @ 2131495341
[Added] MIUI shutdown screen
2013/10/10 - BETA.1 release MIUIv5_L9_BETA1.zip, md5:d39f641cc466a1ebb38ec63a63e534c0
Based on my CM 10.1.3 unofficial 20130927
Modified Kernel 30.0.31 CM+ for OMAP board (P760/P768).
Jellybean 4.2.2
Aroma installer for choosing phone model and enable NFC (for P760 only, my P768 kernel didn't compile with NFC enabled)
Emulate SDCard
Reduce headset volume and increase speaker volume
OC - 300, 600, 800, 1008, 1200 Not OC by default, you can use CPU control app from market to set max frequency
UV - 925, 1075, 1175, 1275, 1350
Add SIO, SIOPLUS, FIFO, ROW and VR I/O scheduler (Default : CFQ)
Add sanjose, lazy, interactiveX, wheatley, ondemandx, pegasusq, adaptive, adaptivex, smartass2, zenx and abyssplug CPU Governor (Default : interactive)
MTP (internal/external) and PTP
Remove some CM apps (CMUpdater, CMAccount, CMFilemanager, Torch, Trebuchet, Apollo, and more...)
Bugs
Sometime my Wifi MAC address reset to 00:00:00:00:00:00, solve by reboot phone 2 times (or 1 time if it's solved).
Don't use Permission Manager app (MIUI on green background) on desktop to enable root. Please use same app in System folder. You will get FC if mess with it.
You cannot view files and folders that created by last rom on internal/external sd on computer, in Gallery or Music. But it show in File manager. If you want your Music app to able to play your music please copy it after install rom. Strange I think it something about permission.
In Browser, select text in link and Magnifier not work. Due to webkit problem.
Weather app only display City in China
Menu item in "Display" below "Font size" display as @ 2131495341
There're annoying background sound when you touch screen, please disable touch sound to get rid of it.
I cannot remove CM gallery because Camera is in that apk. And for this strange CM approach you will get error com.android.camera not found in logcat. Don't report this to me.
There're also some method not found error in logcat, all about user right & permission.
Credits
CM Team for base rom & P760 device tree
MIUI Team for patchrom & MIUIv5
artas182x for UV value
amnik & mateo1111 for kernel source that I review and add OC to my based rom
dtrail1 for JBX Kernel, I get i/o schedule & cpu governor source from this kernel
AntonX for his P769 kernel and files, and some bugs fix
Ghostfreak NB for XperiaT keyboard
ZduneX25 for Boot to Recovery power menu
HOW TO (Update : 2013/11/27)
Flash over last version
You can flash new version over old version
Put rom & gapps for MIUI in sdcard
Boot to recovery
Wipe cache & dalvik cache
Flash rom & gapps
Reboot
Flash this ROM over CM10.1
Didn't try it yet
Enable OC, change I/O scheduler and chnage CPU governor
You need to enable enable root permission first. Do it by open Permissions, MIUI logo on green background in System folder (Don't use Permission Manager on Desktop).
Select "Manage ROOT permission" > "Enable permission manager"
Install some CPU control app from market. I use "No frill CPU control". You can set frequency, I/O scheduler and CPU governor.
Read more about CPU governor at http://forum.xda-developers.com/showthread.php?t=1792369 and http://translate.google.com/transla...013/01/governor-scheduler-tcp-bejegyzest.html
Read more about I/O scheduler at https://www.vincentkong.com/wiki/android/android-io-schedulers/
Please test all changes before select "Set on Boot" because if something go wrong you can reboot your phone to revert it.
If you select "Set on Boot" you must allow CPU control application to Auto Start in MIUI Auto-Start app. If not it'll not work.
Cannot connect to wireless access point
This problem mostly occur when you got some error at first boot. The problem is error interrupt startup service to write proper MAC address data to file. Your wifi mac address will be 00:00:00:00:00:00
If you got this problem during normal use please reboot your phone once or twice to solve it.
If above solution doesn't work try
Use file manager or adb to delete /data/misc/wifi folder from your phone
Reboot (disconnect usb cable to make sure there're no error at startup)
Safely switch between MTP/UMS in this ROM
You can run mtp.sh or ums.sh using script manager widget (install from play store) or terminal to switch between MTP and UMS.
Some usb dialog don't changed according to the mode you just switch to, please reboot your phone to make a proper change.
In UMS mode, don't try to click enable Mass Storage button because it'll unmount sdcard.
In UMS mode, don't set usb connection to "Mount sdcard" because it'll unmount sdcard upon connected.
Please set usb connection mode to "Charge only"
How to remove unused MIUI Chinese app
You can remove following apps
SuperMarket, MIUI chinese market. You can use root file explorer to remove /system/app/supermarket.apk
Some pre-install chinese apps setup files in /data/preinstall_apps. Just delete preinstall_apps folder.
Some pre-install chinese apps, delete AlipayMsp.apk, MiShop.apk and Userbook.apk from /data/app/
How to port MIUI v5 to using other CM rom as based
This is how I port my MIUI v5 to P769
Find CM 10.1.3 based rom that work on your phone (I used AntonX CM 10.1.3 rom)
Download MIUI v5 (may work with others MIUI that use CM 10.1.3 as based)
Copy following files from MIUI rom to based rom
Code:
/etc/
license/
permission_config.json
pinyinindex.ldf
telocation.ldf
weather_city.db
yellowpage.db
/fonts/
Miui-Bold.ttf
Miui-Regular.ttf
TobysHand.ttf
/framework/
android.policy.jar
framework-miui-res.apk
framework-res.apk
framework.jar
framework_ext.jar
services.jar
telephony-common.jar
/lib/
content-types.properties
libFreqFilter.so
libMiuiGalleryJNI.so
libaudiofp.so
libffmpeg_xm.so
libffplayer_jni.so
libimageprocessor_jni.so
libimageutilities_jni.so
libjni_resource_drm.so
libjni_resource_patcher.so
libkeygen_jni.so
liblbesec.so
liblocSDK_2_5OEM.so
libmp3lame.so
libpatcher_jni.so
libphotocli.so
libshell.so
libshell_jni.so
libshellservice.so
/media/
audio/ (missing files only or just copy all files)
lockscreen/
theme/
wallpaper/
bootanimation.zip
/xbin/
shelld
su
/etc/vold.conf
Extract based rom boot.img and add following lines at the end of init.rc file
Code:
service shelld /system/xbin/shelld
class main
Add additional jar to BOOTCLASSPATH, after framework.jar as below
Code:
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:[COLOR="Red"]/system/framework/framework_ext.jar:[/COLOR]/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
You may need to edit sdcard mount point in following files to match internal/external sdcard setting.
/etc/vold.conf
/init.lgep{MODEL}board.rc
/res/xml/storage_list.xml in framework-res.apk (decompiled)
Below is what I used in my rom
/etc/vold.conf
Code:
dev_mount sdcard /storage/sdcard0 auto /devices/platform/omap/omap_hsmmc.0/mmc_host
/init.lgep{MODEL}board.rc
Code:
...
on init
# See storage config details at http://source.android.com/tech/storage/
mkdir /storage/sdcard0 0666 system system
mkdir /storage/sdcard1 0555 shell shell
export EXTERNAL_STORAGE /storage/sdcard0
# Support legacy paths
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
...
# create virtual SD card at /mnt/sdcard, based on the /data/media directory
# daemon will drop to user/group system/media_rw after initializing
# underlying files in /data/media will be created with user and group media_rw (1023)
# FUSE daemon
service sdcard /system/bin/sdcard /data/media /storage/sdcard1 1023 1023
class main
/res/xml/storage_list.xml in framework-res.apk (decompiled)
Code:
<?xml version="1.0" encoding="utf-8"?>
<StorageList
xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:allowMassStorage="true" />
<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/storage_internal" android:emulated="true" android:mtpReserve="100" />
</StorageList>
too many bugs... i will try it after some fixes...
After applying a theme it gives me an err on showing the theme has unfortunately stopped plus many more bugs it was there on gariks rom too..
Sent from my LG-P760 using xda app-developers app
mussi96 said:
After applying a theme it gives me an err on showing the theme has unfortunately stopped plus many more bugs it was there on gariks rom too..
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I don't sign in to test theme yet. I'll give it a try and see what's the problem.
mussi96 said:
After applying a theme it gives me an err on showing the theme has unfortunately stopped plus many more bugs it was there on gariks rom too..
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
It works on my phone. Can you give me your logcat?
Oh I didn't notice that your phone model is P760, wait for other user before I'll try to switch to that kernel and test again. And which theme you apply, I apply "Tinylove" with no error.
edit: I also tried "Tasteful" theme and it works fine.
Can this work for the p769?
Sent from my LG-P769 using Tapatalk 4
I'm verry happy to se miui developed for our LG's. I'll be flashing this myself in a couple of days on my P760.
Yupi
I have waited to see post titled "miui" on this section since I have bought my LG L9. I am very glad to see this downloading rom right now and will be flashing as soon as it is download
Good luck in further development of it
Just found new annoying error. Long press home button don't work when there are open window. I have to press it 3-4 times to bring recent app up.
Sent from my LG-P768 using xda app-developers app
No it don't work on p769. I don't have that phone to test. If I build kernel for p769 will it work? Some P769 Dev may know it.
Sent from my LG-P768 using xda app-developers app
for weather you can use weather bz.
I'll ask around
Sent from my LG-P769 using Tapatalk 4
What build of miui, what did you mean sdcard emulation, your rom have echo?
Changed ROM to BETA.1 to notify user about its bugs. And if there're serious bug that I cannot solve I will use original CM webkit and replace MIUI Browser with CM stock. Hope that there're no other app that use new webkit features.
Sound isn't working at all.
Sent from my LG-P760 using Tapatalk 4
pedja1 said:
Sound isn't working at all.
Sent from my LG-P760 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I forgot to include p760 sound library. It works on my p768
Edit:I'll correct it tomorrow.
Sent from my LG-P768 using xda app-developers app
pedja1 said:
Sound isn't working at all.
Sent from my LG-P760 using Tapatalk 4
Click to expand...
Click to collapse
Absolutely not true. Read OP please, the known bug are described well. Try to be polite and thankfull with developers, that put a lot of efforts in porting miui for p760.
However i would like to know for which device your MIUI sorgent is. I suggest you to use the miui for Optimus 3D.
garik345 said:
What build of miui, what did you mean sdcard emulation, your rom have echo?
Click to expand...
Click to collapse
Not sure about echo. But it should be base ROM problem. My cm 10.1.3 don't have echo bug.
I use miui jb42 patchrom.
I enable internal memory emulate as sdcard so it could work on phone without sdcard. All official cm enable this by default.
Sent from my LG-P768 using xda app-developers app
simosimi said:
Absolutely not true. Read OP please, the known bug are described well. Try to be polite and thankfull with developers, that put a lot of efforts in porting miui for p760.
However i would like to know for which device your MIUI sorgent is. I suggest you to use the miui for Optimus 3D.
Click to expand...
Click to collapse
No based device, it use l9 ROM as base. Because miui patch rom can port miui to any device that has working rom. It also harder to port than normal method. But if I did it carefully it will work as stable as CM based ROM. If I mess my ROM source all I have to do is reverse to last known working one.
Sent from my LG-P768 using xda app-developers app
This is a modified ROM of the 4.70 mm sony firmware.
Internal packages features:
- SystemUI tiles changed (animation, icons, added a couple of more tiles that I find useful).
- SystemUI notifications changed to blue background.
- Framework icons changed.
- System Settings icons changed.
- Removed all non essential applications.
- Some phone and some incallui icons changed.
- Busybox preinstalled.
- DRM fix integrated.
- Blue Theme all around the packages
Kernel features:
- compiled with linaro toolchain (greater speed all around)
- implemented double wave to wake for the proximity sensor (you can enable/disable in the battery settings)
- implemented hexacore mode (only 2 cpu on from the big cluster) - I could not run waze on this phone because it overheated a lot with default config (you can enable/disable this from battery settings)
- implemented limited cpu frequency for the big cluster (from 1950MHz the big cluster will have a maximum frequency of 1200MHz) - again you can switch this to on/off from battery settings (it helps with overheating, but it will make your phone to run slower).
- fixed the jumps in brightness when auto is set (lazy brightness - the changes in brightness settings are done slower when the brightness goes up and a little bit faster when it goes down)
- CPU and GPU undervolted.
- it has init.d support for apps2sd - ran along with the boot process
- it has userinit.d support (this is ran when the boot process has completed)
The rom has the selinux flag set to restrictive.
The rom comes as a TWRP backup archive as I'm too lazy to continue the work on this as this phone I considered to be a crap phone.
Files:
1. http://www53.zippyshare.com/v/rpuhZnXw/file.html
2. http://www53.zippyshare.com/v/sUieWRHd/file.html
3. http://www53.zippyshare.com/v/A1HsTFFE/file.html
4. http://www53.zippyshare.com/v/GsL4nnlG/file.html
How to install:
1. Download all four files. They represent a tar.gz split archive.
2. Extract the archive like this: cat bluesplash470mm.tar.gz.* | tar -zxvf -
3. Put the extracted directory in the TWRP backup folder.
4. Make a backup of your current rom.
5. Restore backup of the rom.
WARNING: Make a backup of your current rom, just in case anything goes wrong.
I'm not responsible for any bricks, if they happen. They shouldn't happen as this is just a backup of a sony rom, but who knows what can go wrong ...
Enjoy!
I've attached a small movie with the rom...
Kernel update 2 (flashable zip):
https://www20.zippyshare.com/v/kOkec3Zv/file.html
- fixed dw2w - it was not activated sometimes (rarely, but it happened) - it seems to be working all time now...
Updated kernel:
- fixed double wave 2 wake for prox sensors (sometimes it did not activate when screen went off - seemed to be a thread race issue) - still testing.
- OC a little bit the little cores (1.2GHz - initially was 1.1GHz)
- limited the big cpu cores to 1.5GHz when the limit cpu freq is set (Initially was 1.2GHz - phone is a little bit snappier). You can still use the 1.2GHz for big cluster if you set /sys/android_ptweaks/vlpowermode to 1 (I have an automagic rule that does this when I use waze)
I get around 5h of SOT with this kernel and when browsing over wifi. Still ****ty. My wife has a huawei nova and she gets 10h of SOT over WIFI with a battery of 3000mA which that phone has... Last phone from Sony for me ... Overpriced and crappy ...
cojocar.andrei said:
This is a modified ROM of the 4.70 mm sony firmware.
Internal packages features:
- SystemUI tiles changed (animation, icons, added a couple of more tiles that I find useful).
- SystemUI notifications changed to blue background.
- Framework icons changed.
- System Settings icons changed.
- Removed all non essential applications.
- Some phone and some incallui icons changed.
- DRM fix integrated.
- Blue Theme all around the packages
Kernel features:
- compiled with linaro toolchain (greater speed all around)
- implemented double wave to wake for the proximity sensor (you can enable/disable in the battery settings)
- implemented hexacore mode (only 2 cpu on from the big cluster) - I could not run waze on this phone because it overheated a lot with default config (you can enable/disable this from battery settings)
- implemented limited cpu frequency for the big cluster (from 1950MHz the big cluster will have a maximum frequency of 1200MHz) - again you can switch this to on/off from battery settings (it helps with overheating, but it will make your phone to run slower).
- fixed the jumps in brightness when auto is set (lazy brightness - the changes in brightness settings are done slower when the brightness goes up and a little bit faster when it goes down)
- CPU and GPU undervolted.
- it has init.d support for apps2sd - ran along with the boot process
- it has userinit.d support (this is ran when the boot process has completed)
The rom has the selinux flag set to restrictive.
The rom comes as a TWRP backup archive as I'm too lazy to continue the work on this as this phone I considered to be a crap phone.
Files:
1. http://www53.zippyshare.com/v/rpuhZnXw/file.html
2. http://www53.zippyshare.com/v/sUieWRHd/file.html
3. http://www53.zippyshare.com/v/A1HsTFFE/file.html
4. http://www53.zippyshare.com/v/GsL4nnlG/file.html
How to install:
1. Download all four files. They represent a tar.gz split archive.
2. Extract the archive like this: cat bluesplash470mm.tar.gz.* | tar -zxvf -
3. Put the extracted directory in the TWRP backup folder.
4. Make a backup of your current rom.
5. Restore backup of the rom.
WARNING: Make a backup of your current rom, just in case anything goes wrong.
I'm not responsible for any bricks, if they happen. They shouldn't happen as this is just a backup of a sony rom, but who knows what can go wrong ...
Enjoy!
Click to expand...
Click to collapse
Epicc dude :good: but is there any rom for f3116
no, but you can try restoring only the system image from the backup along with the kernel to see if it works... probably you'll need some props changed, just so your phone would be recognized as f3116...
Sent from the center of the galaxy
any bugs? any problems? for rom.
( 2. Extract the archive like this: cat bluesplash470mm.tar.gz.* | tar -zxvf - )
how to open archive ? windows 7?
yek26119 said:
( 2. Extract the archive like this: cat bluesplash470mm.tar.gz.* | tar -zxvf - )
how to open archive ? windows 7?
Click to expand...
Click to collapse
You'll need an application to concat the archive. Search on the internet how to concat a split archive on windows...
There is 7.0 android?
No.
For xa 3112 ?
samirt said:
For xa 3112 ?
Click to expand...
Click to collapse
No, sorry, I have a F3111 and I've worked for this type of phone... It's hard to port everything to 7.0 or another type of xa (well not really hard, but very time consuming, time which I don't have - work, wife, kid...) so no updates or port. If someone wants to port the changes you should look for XperiaXASystemMod github and port from there...
I'll probably make changes to this rom if I find something which is not working...
is this an legacy or OMS rom?
Drm fix
can you guide me on how you managed to intergrate drm fix for this rom as i would like to fix drm on my stock rom 4.70 too? this will be very helpful thanks!
root lost
everithing is fine but i lost root
dedeer said:
everithing is fine but i lost root
Click to expand...
Click to collapse
Root is back just instal su again
Hello I have an xa f3111but it is in version 7.0. How do I downgrade to this version? Can I flash this kernel in a ROM stock MM?
The download link broken. From kernel
broken links
Broken links, a mirror to androidfilehost would be nice.
thank's:good:
re upload please
Introduction:
This modification / custom kernel configuration for Pixel and Pixel XL is optimized and made with the focus on bringing several, carefully tuned behind-the-scenes enhancements & adjustments that improves overall critically needed performance, system responsivness and battery life to the highest possible level. The seed to this project can by the way be found here, for anyone that is interested of its origins.
Note: This script is not recommended to be modified or customized by the user.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
[
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give the script the following permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for both the first generation as well as the second generation of Pixels!
Credits:
@nathanchance for his contributions with his Flash Kernel
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory from the beginning
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2018-10-08
Last updated: 2019-01-04
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Edit: sorry for stealing the first post btw hehe
EDIT: My changelog dedicated post have exceeded 30000 characters, so I have decided that the changelog will only be included in the respective update posts from now on!
So you all know how the situation is.
shagbag913 said:
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Click to expand...
Click to collapse
I'll do whatever I can on the first generation Pixels for giving you guys & girls the same awesome experience.
And thanks btw.
:highfive:
Update!
v1.1 (Minor release)
- Made a few more (hopefully) battery conserving adjustments to the Sched governor.
Enjoy!
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Core control screenshot
Phalanx7621 said:
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Click to expand...
Click to collapse
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
xFirefly93 said:
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Click to expand...
Click to collapse
I can confirm that the same happens to me.
Thanks for the work!
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
Old Man Dave said:
I can confirm that the same happens to me.
Thanks for the work!
Click to expand...
Click to collapse
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
xFirefly93 said:
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
Click to expand...
Click to collapse
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Phalanx7621 said:
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Click to expand...
Click to collapse
I will compare how my Marlin / Pixel XL performs with it disabled respectively enabled and see which "solution" that is giving best battery life with less performance tradeoffs, and then I will include the best overall compromise in v1.2 of my kernel configuration / script.
For anyone else interested in this, this is how I went about it:
1) Downloaded Flash Kernel from his thread over here https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300
2) Downloaded the latest version of this mod
3) Downloaded the Magisk module required, which you can find by searching Magisk for "busybox" and choosing the "Busybox for android NDK" version
4) Flash that Magisk module, reboot into recovery, flash the Flash kernel (no need to reflash magisk, it's automatic), reboot back into system.
5) Check to make sure Magisk is functioning properly, for me I had to reboot due to an error in the application but that may have been on my end.
6) So now you have Flash kernel and the Magisk module required to be able to properly run this script. Extract the script from the .zip file you downloaded to a folder.
7) Ok so these next steps if you aren't familiar with this stuff could be tricky, but it's actually simple it just sounds tricky. I use Mixplorer for this, I highly suggest using it, it's free and it's on XDA Labs here. https://labs.xda-developers.com/store/app/com.mixplorer But any file explorer w/ root access will do. Inside the folder you extracted the script into there are two versions, choose the Public Release version and copy that file. Navigate to root ( / ) and go to /data/media/0 and paste the file there. The reason for this is you have to change the permissions to allow it to be an executable script and this folder allows that. (there are other ways to do this, FYI but this works just fine for me) You want the permissions to be 755, so it would look like this: (see attachment) To change permissions in Mixplorer, just long press the file and hit the little i (for information) in the upper right. Then click on the permissions you want to change.
8) Now all you have to do is copy that file you just changed the permissions to and paste it into: /sbin/.core/img/.core/service.d | | Now you won't be able to SEE .core unless you have hidden files on, in Magisk it's in the upper right hand corner 3 dot menu. Click Show Hidden. After you paste the file there, reboot and congratulations, you have achieved greatness.
Phalanx7621 said:
.. FYI..
Click to expand...
Click to collapse
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
xFirefly93 said:
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
Click to expand...
Click to collapse
Oh ok cool, just wanted anybody else to be able to use this awesome mod too, it works wonderfully!
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
It's there.... I'm on the same rom. You need to start at root and not device storage, as well as show hidden folders
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
Use X-plore file manager adn give Root permissions and in settings Show hidden files or folders something.
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
xFirefly93 said:
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
Click to expand...
Click to collapse
Hi, which release from Public and Maintenance we have to use. Thank you for your hard work.