Hey Guys,
I thought while waiting for the first custom kernels that maybe i should have a look at the interactive values and try to tweak them based on this way:
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
So i took a script from @Alcolawl and modified it to work with our device. Many thanks for his scripts.
I adjusted the values to our snapdragon 820 as the original scripts are for the nexus 6p which runs with a snapdragon 810. (octa on the 810 vs quad-core on the 820)
I´d highly recommend to try these values as it gave me a significant boost in battery life. here is a screenshot:
https://drive.google.com/file/d/0BxbxiBXaZVu-N1lsRTMyZ2hsY1k/view?usp=sharing
https://drive.google.com/file/d/0BxbxiBXaZVu-N1MzamRvM2FVZlk/view?usp=sharing
BIG UPDATE: with base 1.80 i´m not able to trick the touch/Input boost from htc´s pnpmgr with a chmod command like i did before. so all versions since Butterfly v11 will disable pnpmgr completely.
that means if you Play high end games and your device overheats like crazy please Report back. i had no Problem until now.
also there are now 2 versions. the oc one is for overclocked cpus with elementalx. without oc is for the default clock speeds.
here are explanations on what the 2 different stragies do:
Butterfly - A culmination of all strategies, provides smoothest performance of all currently published settings, though battery savings are a little more modest. Excellent for light and moderate users; heavy/marathon users might want to check out a different setting profile as it gets battery intense with heavy usage.
GhostPepper - Uses a quantized, frequency-aligned parametric curve to influence low core clock rates while providing extremely smooth transitions from each clock rate and exceptional battery life. Good for light to medium usage and multitasking.
So basically there will be two ways of applying this mod.
First one is via scripts. this allows to set parameters outside of the interactive governor controls like cpu boost, editing of pnpmgr, min/max frequencies etc. so basically there´s more control.
Second one is via EX Kernel Manager. I will upload the profiles and you can apply them directly into the app. This will however only affect the tunables of the interactive governor. Touchboost has to be set manually for the profile to work exactly as intended.
when the phrase "elex" is in the zips name it is for use with ex kernel manager app (loading profile in governor options screen.
so to try the script method follow these steps. (and before do a nandroid as always)
1. download the attched file.
2. unzip the file, choose the correct script (oc if you have overclocked)
3. with a root explorer or terminal copy the file to system/su.d
4. set the correct permissions (rwxr-xr-x)
now you may either choose to change the settings temporary (step 5A) until the next reboot or permanently upon each reboot (step 5B)
5A. rename the file to 50ghostpeppertenv3.sh
use any script manager and run the script from this location (system/su.d)
alternatively use any terminal emulator app with the following commands
su
cd system/su.d
sh 50ghostpeppertenv3.sh
Be advised that the script takes in its current state 60 seconds to be applied. So the changes need a minute to be applied.
now check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this: "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully
- the values changed with each update. what´s important to check is just the generel layout
5B. (-if you did the temporary approach beforehand remove the .sh)
- it should look like 50ghostpeppertenv3 (make sure there are now spaces at the end)
reboot and check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this : "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully.
-- the values changed with each update. what´s important to check is just the generel layout
Important!!!
if you run permissive and run into no signal issue due to this look here
if you should run into a no signal issue where your baseband shows as unknown under software status ( currently on custom roms eg leedroid) you have to put a script to system/su.d that sets selinux to permissive. attached is such a script.
unzip it. copy it to system/su.d
set the same permissions as the ghostpepper script and your good to go.
running in terminal the command "getenforce" should return permissive.
Second method via Elemental App:
1. Download the desired profile from the attachments
2.Extract the Profiles from the zip
3. Choose the Overclocked(oc) version if you overclocked
4.Copy the file to sdcard/ElementalX/gov_profiles
5. Open the app and apply the values
let me know if it brings a little battery boost for you. you may also let me know if you face performance issues.
Thank you and have fun testing it.
Changelog:
Ghostpepper:
v1: Initial Release
v2: Tweaking The Script so the values will get applied properly on all roms
adding a permissive script in case of getting enforced
v3: Removed touchboost so the profile may unleash its full potential <<--- results in overall slower device.
v4: Added back short input boost
v4withtb: Added back original touch boost from htc
v8: New try on getting the interface smooth and disabling touchboost (minimal stutter remains)
v8withtb: same as v8 touchboost is still active
v9: only one version with touchboost now. tweaked target loads (lower freqs are used more), short input boost
there are now two files inside the zip.
v10: try to further improve frequency usage, less aggressive scaling
v11: fix in case Little cores might get stuck at highest clock
Butterfly
v4: Initial Release
v4withtb: Initial Release with original touch boost from htc (extremely smooth)
v6withtb: tuned the values and kept touchboost from pnpmgr, kernel touch boost is disabled, extremely smooth for me
v7: less aggressive scaling, performance should be really good while reducing less power than v6
v9: basically scaling is tuned to respect the crossover effieciency point from big and little cluster
v11: updated to work on base 1.80
- disable pnpmgr completely because the chmod trick for disabling pnpmgr´s touchboost is no longer working
- enable msm_thermal and core_control
v12: tweak some values to work better with the new base
v13: hotfix as i made a mistake in the previous version
credits:
thanks to @Alcolawl for the script template
also thanks to @soniCron for the original thread
reserved
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Captain_Throwback said:
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Click to expand...
Click to collapse
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
gusoldier said:
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Click to expand...
Click to collapse
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Freak07 said:
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Click to expand...
Click to collapse
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
gusoldier said:
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
Click to expand...
Click to collapse
yeah. I can try this later. But compared to my nexus 6 and my pixel c the 10 is about as smooth.
Freak07 said:
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
Click to expand...
Click to collapse
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
P.S. You didn't answer my question about why you're not using su.d instead of init.d?
Captain_Throwback said:
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
Click to expand...
Click to collapse
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Or is it just like "sleep 30"?
Edit2: it is indeed. thank you again.
Freak07 said:
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Click to expand...
Click to collapse
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Captain_Throwback said:
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Click to expand...
Click to collapse
yeah you´re right. thanks for the reference and the hint. i knew about it but didn´t remember i could use this see my edited last post. with sleep 30 it´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Freak07 said:
yeah you�´re right. thanks for the reference and the hint. i knew about it but didn�´t remember i could use this see my edited last post. with sleep 30 it�´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i�´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Click to expand...
Click to collapse
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Captain_Throwback said:
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Click to expand...
Click to collapse
Okay i'll edit it to 60.
This is what I'm talking about. Every Chip has a pvs bin. The higher the bin the lower the voltage for a certain cpu frequency.
And every bin has its own voltage table.
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
rav101 said:
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
Click to expand...
Click to collapse
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Freak07 said:
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Click to expand...
Click to collapse
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
rav101 said:
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
Click to expand...
Click to collapse
How did you recover? Full Wipe?
Delete
Freak07 said:
How did you recover? Full Wipe?
Click to expand...
Click to collapse
Yeah, I tried a dirty wipe but that didn't work so had to do a full wipe.
Related
Discontinued for now.
-------------------------------------
Okey just did some reorganisation to get this post a little bit cleaner.
I just deleted the unneeded versions, but I have a backup of them, so if you really want to have one of the older versions send me a pm and which one you want, else just stick to my recommendations below.
Most important question first:
Which Version should you take?
Siyah Kernel 2.6.6i and newer: init.d Gen 2.6.6i SE
Siyah Kernel 2.6.2 to 2.6.6: init.d Gen 2.6.2
Siyah Kernel 2.6_S99 to 2.6.1: init.d Gen 2.6
Siyah Kernel 2.5.* (all Versions, also GT): init.d Gen 2.5 SE
Siyah Kernel 2.4.2 to 2.4.*: init.d Gen 2.4.2 SE
Siyah Kernel 2.4.1 and older: init.d Gen 2.2 Beta 16 SE
What does SE and RRW stand for?
SE is for "Second Edition" and should be preferred, but you are free to take the version you like.
RRW is for "Remount Read/Write" and will remount "/system" with rw permissions, use this version if ADB Push fails to push the bootscript to the phone.
If you want to use push, pull or activate function you have to enable USB Debugging Mode else ADB can't recognize the device.
(Can be found under Menu > Settings > Applications > Developement > USB Debugging)
Please tell me if there are any issues with any function.
Known issues:
The function for deep sleep levels is not implemented correctly in the following 4 versions:
-init.d Gen 2.6
-init.d Gen 2.6 RRW
-init.d Gen 2.6.2
-init.d Gen 2.6.2 RRW
Fixed since 2.6.6i!
Thanks to gokhanmoral for the best kernel ever and helping me via pm!
Thanks to droidphile for this epic manual!
http://forum.xda-developers.com/showthread.php?t=1369817
Read it first for a better understanding of the values.
Screenshots (v 2.6.2):
Thanks to D5PiX for free image hosting
Changelog:
2.6.6i SE:
added ignore nice load to ondemand
fixed import function
fixed lazy governor
2.6.6.i:
deep sleep levels fixed
added suspend_freq to ondemand (since ondemandx was merged with it)
updated all values to the new ones from Siyah Kernel 2.6.7
2.6.2:
3 step gpu settings added
lulzactive v2 settings added
2.6:
Excluded charging currents (not needed)
Added a handfull of new options:
- deepsleep cpu and bus level
- second core sample settings (rate 2nd core on, off, screen off)
- smooth scaling parameters
- added AFTR settings
2.5 SE:
Added lulzactive samplerate settings
2.5:
Added touchscreen threshold
2.4.2 SE
Added delay function (the script will delay for a choosen amount of seconds before execution)
Added governordepending settings (sampling rate, up/downscale thresholds etc)
Added function to pull bootscript from phone to hard disk
2.4.2:
Updated to new default values.
Excluded "insmod/non insmod/legacy"-modes, insmodding will be included as needed by 2.4.2 Kernel
2.2 Beta 16 SE:
Exchanged "2.2 Beta 16 mode" with "always insmod mode"
2.2 Beta 16:
Improved including options
Added Siyah 2.2 Beta 16 referring insmod-settings
Added possibility to activate bootscript without restarting the phone
Added possibility to import settings from existing bootscript
Beta 2.2:
Included 2nd core thresholds for screen on and screen off
Included 2nd core loadbalancing (sched_mc)
Included displaysettings (min backlight and max gamma)
Change permission after pushing script to phone
Beta 2.1:
Possibility to include only selected tabs to the created script
Beta 2:
Added ADB to the package
Possibility to push script directly to phone via ADB
Beta:
CPU frequencies and voltages
Minimum/Maximum frequency used by governor
Governor
GPU frequencies and voltages
IO scheduler
Static busspeeds
Charging currents
Possibility to create and save script on harddisk
Beta 2 out now!
Will push your generated script directly to your plugged phone via ADB, just unzip, choose options, press ADB on Save tab and done.
Sources didnt change that much, will provide them later or after implementing the new siyah kernel functions.
Anything that you want me to implement first?
Any issues or errors while using it?
goose2600 said:
Runnig executable open a window where you can choose your preferred settings.
Then the program will generate the script and you have to copy it to device by hand
Click to expand...
Click to collapse
KcDaRookie said:
as goose said ATM you have to copy it by hand to /system/etc/init.d
but I will try to implement adb autopush so that you only have to click a button while the phones connected
Click to expand...
Click to collapse
Getting an old man, but always trying to learn more....
Can you give me (US) more explaination on the basic way to use it ?
CPU OK, GPU don't, IO Scheduler don't, BUS don't, CHARGING OK
Maybe if you could provide a text with your init. Gen
Sorry to be such a newbee...
GREAT JOB !
Kindly yours
Nice one
bvannier said:
getting an old man, but always trying to learn more....
Can you give me (us) more explaination on the basic way to use it ?
Cpu ok, gpu don't, io scheduler don't, bus don't, charging ok
maybe if you could provide a text with your init. Gen
sorry to be such a newbee...
Great job !
Kindly yours
Click to expand...
Click to collapse
think you !
The script generated works fine. ADB push too.
There is just a little mistake, the argument for busfreq_static si "disbled" by default instead of "disabled". But if you enable it then you disable it, it's well written "disabled".
I just add some lines in the script in order to modify the hotplug thresholds and it's perfect !
Thank you
Thank you Reno_kun, will change that asap!
altough the default kernel value is disabled so echoing disbled shouldn't have any effect ^^
will implement hotplugging treshold and brightness settings in next update, i hope i'll have time tomorrow ^^
edit: fixed that and did some rearranging.
Better and better
Incredible work, THINK YOU
Kindly yours
any chance to make phone app from this?
KcDaRookie said:
Thank you Reno_kun, will change that asap!
altough the default kernel value is disabled so echoing disbled shouldn't have any effect ^^
will implement hotplugging treshold and brightness settings in next update, i hope i'll have time tomorrow ^^
edit: fixed that and did some rearranging.
Click to expand...
Click to collapse
I've got an other problem
At boot, the script in init.d is not applied. I need to change permissions from rw-rw-rw- to rwxrw-rw- in order it is used.
What are usual permissions for a script in init.d ?
Thank you for your work KcDaRookie
@bvannier: thank you very much
@lokotus: you are free to use to sources to make an phone app from this, I don't have the knowledge that is needed for this, also i think using SetCPU, nofrills, voltage control or gokhanmorals tool for his kernel once it's released is much more efficient because the changes will take effect on the fly.
with this script you have to reboot at least once...
hmm.. I getting a great idea.. I think I will implement that the new values will directly be echoed via adb to the phone, so that they will immediately take place..
I tested a bit and this isn't impossible, thank you for this idea
Reno_kun said:
I've got an other problem
At boot, the script in init.d is not applied. I need to change permissions from rw-rw-rw- to rwxrw-rw- in order it is used.
What are usual permissions for a script in init.d ?
Thank you for your work KcDaRookie
Click to expand...
Click to collapse
I have mines set to 777 (rwxrwxrwx) but I think 766 (rwxrw-rw-) should be enough
I see if I can change permission via adb directly after push ^^
Thanks for that comment =)
Thank you guy !
I tried several time and I always had 666, it's may be due to the ROM ? Which one do you use ?
You should post some pict in the OP for showing that your soft is very easy to use
Reno_kun said:
Thank you guy !
I tried several time and I always had 666, it's may be due to the ROM ? Which one do you use ?
You should post some pict in the OP for showing that your soft is very easy to use
Click to expand...
Click to collapse
Am still on Stock ROM ^^
Will add pictures as soon as Beta 2.2 is uploaded.
There we go, new version with sources released.
It should set the permissions to 766 and also kill the adb-deamon after pushing the script to the phone.
Just tested and all work fine !
Thank you a lot !
If you have time, could you add an "import" feature in order to use a script already saved ?
@OP: awesome job dude
@Reno_kun: I'll think about it, but I think this will take some more time, will put it on the to do list ^^
@TecQuality: your welcome =)
KcDaRookie said:
@Reno_kun: I'll think about it, but I think this will take some more time, will put it on the to do list ^^
@TecQuality: your welcome =)
Click to expand...
Click to collapse
So with this tool we dont need voltage control anymore right?
Anyways, the intructions are: enable the debug mode, plug the device, generate a script and select the push command correct? We need to start the adb server?
Directly from my SGS II using xda premium
@TecQuality: No, you don't have to start the server manually, the adb push command starts the adb-deamon/adb server automatically but won't stop the deamon afterwards therefor I stop the server after pushing the bootscript and setting the permissions.
So you just start the tool, plug your phone to the pc in usb-debug mode, choose your configs and press ADB Push, after that restart your phone and the bootscript should apply at systemstart.
FuguMod kernel is now available for the Galaxy Nexus.
It has been reported to work both on GSM and CDMA versions. But I can only test it on GSM version myself.
You can download them at:
http://fugumod.org/galaxy_nexus/
Source and changelog can be found here:
https://github.com/renaudallard/gnexus_kernel
IRC channel:
irc.freenode.net #fugumod
To install, just download the appropriate version for your ROM (4.0.x) and flash it with fastboot (RAW version: fastboot flash boot kernel-$VERSION.img) or flash it with CWM (CWM/zip version).
Please note that not all versions exist in CWM format.
4.0.2 version is based on official google initramfs + init.d support (is now in deprecated state, no future updates will be brought)
4.0.3 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.4
4.0.4 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.3
4.1.x version is based on the initramfs of AOSP + init.d support.
4.2.x version is based on the initramfs of stock kernel
4.3 version is based on the initramfs of stock kernel (use that one for CM, not reco)
4.3-reco version is based on the initramfs of stock kernel, even with install-recovery.sh enabled (so supersu can work, but if you don't have supersu, don't use it)
for experimental versions, do not flash if you are not ready for big troubles, they may not even boot, burn your phone and eat your cat.
Features:
- stackprotector
- various security enhancements
- RCU boost
- Automatic process grouping
- TUN (compiled in kernel)
- latest 3.0 linux kernel
- newer wifi driver
- gamma/color hack
- CM9 compatibility
- PaX (from r333)
- grsec (from r624)
- TouchWake from Ezekeel (from r778)
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20120111_r20-4.0.3.img
20120111 is the date it has been packaged
r20 is the release number
4.0.3 is the ROM it is compatible with
Color offsets
In CM9, just use the built in function.
For other ROMs, the settings offsets are in
/sys/class/misc/samoled_color/
For example green_v1_offset
Just edit the three green red and blue color settings. Default value is 60.
It can be done on the console with a command like this: echo 55> /sys/class/misc/samoled_color/green_v1_offset
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Radio drops and blueish/faded screens
Please ensure you are running the correct firmware for bootloader and baseband, like in the matrix in bottom of that page: http://source.android.com/source/building-devices.html
For those where problems persist after flashing recommended versions, try "echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp"
OTG unmounting internal SD
Please see http://forum.xda-developers.com/showpost.php?p=24040652&postcount=174
Mirrors
bootloaders: http://fugumod.org/bootloaders-gn/
basebands: http://fugumod.org/modem/galaxy_nexus/
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
Touchwake
to enable it "echo 1 > /sys/devices/virtual/misc/touchwake/enabled"
to make it always on: "echo 1 > /sys/devices/virtual/misc/touchwake/always"
Beware, touchwake is known to sometimes produce screen locks
PGM
See "Compatibility with hackish style apps". Use touchwake instead.
Lost root
Use supersu instead of superuser from chainsDD (superuser from koush seems to work fine too). Change the setting in SuperSU to ignore CM root setting if you are running CM.
Updater app
https://play.google.com/store/apps/details?id=my.zin.rashidi.android.fugumod
root on 4.3
Currently only reco version has support for root access with supersu. Keep in mind that su access is now (as of 4.3) provided by a daemon, which may drain your battery or worse. Please think about your uses for root to see what is better fit for you.
W00t fugumod on the nexus!!
Will try it, thanks for dropping this here.
I'm totally happy
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Nitroz said:
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Click to expand...
Click to collapse
You probably mean SGS1.
I'm not entirely sure how accurate setcpu is at reading frequencies, but it seems to be stuck at 700mhz after a reboot. Moving the sliders a bit allows the cpu to use the entire range of 350-1200mhz as intended. I'm on AOKP milestone 2 if it matters and using r26.
Haven't yet tried this, but maybe min frequency when booting is set to 700mhz?
when you open setcpu, is the min slider at 350mhz?
What governor are you using? Not sure it matters though, but it might so.
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
nikademus said:
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Click to expand...
Click to collapse
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
j.go said:
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
Click to expand...
Click to collapse
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
nikademus said:
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
Click to expand...
Click to collapse
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
j.go said:
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
Click to expand...
Click to collapse
Try the latest version, I removed all Francisco tweaks.
nikademus said:
Try the latest version, I removed all Francisco tweaks.
Click to expand...
Click to collapse
All right, I'll give it a spin tonight and post how it goes. Thanks!
I think I will be upgrading my phone to 4.0.3. This would mean I would not support 4.0.2 as I would not be able to test it properly. Are there users here who need the 4.0.2 version?
great
R37 für 4.0.3 runs flawless.
I use CM9 kang by fitsnugly.
R40 also flawless on fitsnugglys CM9 kang
r41 is out, probably last release for today
I flashed the latest KANG from today and the 122211 gapps with R41.
Works like a charm so far
aosp kang built today, flashed R43 just now. booted fine first try, wifi/bluetooth are fine, data call as well, rebooted, set scheduler/gov to deadline/ondemand, min/max freq to 1.2ghz, score on antutu maxing out around 5200, 5300. with my modified stock, i hit 6200+ in those conditions.
switch back to cfq/interactive, sd write speed goes up a bit to 10.4mb/s (deadline was just under 9.4mb/s), cpu integer 1304, float 1099, pushes score up a bit but still not reaching 5400 (this is with all tests selected, 2d/3d, database..). tweaked lowmemorykiller, antutu score jumps to 5600+.
but benchmarks mean almost nothing, i know. overall it's pretty smooth, fast on bootup, ocasional "lag" here and there (but that may be Mr. Android's fault).
will report more as the kernel settles in.
thanks nikademus.
edit: just re-installed gta. it seems i have no in-game sounds at all? it's fine until it gets to the main menu though. anybody else seeing this? happening on stock kernel too, wth..
edit2: jumping on r44.
flashed R44 on the latest fitsnugly kang. all is well. as expected, as only unused modules have been removed
Introducing Trickster MOD, bringing Trickster experience to virtually every ROM out there.
Users using Trickster ROM 1.2.1 or newer can use this MOD to update
This CWM zip include the binaries and scripts I used for optimization in Trickster ROM. What it can do/set:
- Zipalign and sqlite DB optimization at boot
- Some android properties tweaks with mobile network speed tweak
- Screen state optimization for kernel task scheduler and virtual memory management (ch33kybutt)
- Set I/O scheduler, read ahead buffer, CPU scaling governor, min and max CPU speed
Following features are dependent on kernel features:
- Color (applied by default), contrast and gamma tweaks
- Generic hotplug
- CPU Temp limit
- Minimal SmartReflex voltage of Core, IVA, and MPU domains
- Nominal SmartReflex voltage for Core, IVA, and MPU domains
- Regulator voltages
- GLaDOS live OC of Core, GPU and MPU
- WIFI mode for screen off (power saving or full speed)
- Vibrator strength
- Headset volume boost
- High performance sound
- Force fast charge
- Battery live extender
- Touch wake and touch wake duration
- fsync control
Download
Trickster MOD 20120709
Control App
Changelogs
Requirements:
- CWM
- Someone who understands instructions below
Installation/Update instructions:
- Reboot to CWM recovery
- Do a nandroid if you're scared (recommended in case you have problem)
- Install zip from sdcard
- Reboot the phone
- If you see /sdcard/trickster directory with configuration files inside then this mod installed successfully
Usage:
By default Trickster color, some android property regarding UI smoothness and mobile data speed tweaks and screen state optimization are applied. If you want to change additional settings then either use the app or :
- Go to /sdcard/trickster directory, you'll see at most four following configuration files, depending on kernel features:
. color.conf: color related tweak
. general.conf: generic tweaks like zipalign, sqlite, and screenstate optimization
. kern_general.conf: generic kernel tweaks like CPU speed, governor, IO scheduler and readahead buffer
. kern_specific.conf: specific kernel features like sound control, WIFI power, fast charge... - Edit any above file to change the settings you want using app like ES Explorer, Root Explorer..., instructions included inside
- Settings are automatically applied when user saves any of these files
- Some changes require restarting your phone
- To check log to see if it works use "logcat|grep Trickster" from adb/terminal
Reinstall boot service, Reset settings, Removal instructions:
- If you install a new kernel that includes ramdisk (boot.img format like franco or leanKernel), you can either reinstall Trickster MOD, run "tricks install" from adb root shell or terminal, or apply this CWM zip from recovery.
- You can delete a configuration file, files, or entire /sdcard/trickster directory to reset to default settings for a file, files or all configuration respectively
- If you mess up and can't boot, say aggressive OC/UV , use this CWM zip to reset
- If you want to uninstall, use this CWM zip
Credits:
- Google
- Our great kernel devs
- chainfire for SuperSU and su
- stericson for busybox
- ch33kybutt's for his brilliant idea on screen state optimizations
- Beta testers for your dedication in testing this
- nexus.prime for his unintallation script
- phone_user for init.d CWM zip
- Anyone I learnt from
Disclaimer: This is provided with NO GUARANTY whatsoever. Use your common sense.
Beta test: If you want to test my stuffs, including other things beside this. Contact me through PM.
First
Thanks for this! Downloading now
Sent from my Galaxy Nexus using XDA
tanner4137 said:
First
Thanks for this! Downloading now
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
DERP!
Looks great! @OP, I remember your contributions in Franco's thread. Will any of these modifications conflict with his setup?
Cheers,
mazubo said:
Looks great! @OP, I remember your contributions in Franco's thread. Will any of these modifications conflict with his setup?
Cheers,
Click to expand...
Click to collapse
No, it won't. This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
TBH with the recent CM episode I felt this is needed even more, screw them all. My script or app won't include things that won't work with CM like what they did, I assure you.
bigeyes0x0 said:
No, it won't. This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
TBH with the recent CM episode I felt this is needed even more, screw them all. My script or app won't include things that won't work with CM like what they did, I assure you.
Click to expand...
Click to collapse
Awesome, thank you! I'm currently running paranoid android which is cm9 base.
I'll report back!
bigeyes0x0 said:
...
This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
...
Click to expand...
Click to collapse
Cooool!
---------- Post added at 02:39 PM ---------- Previous post was at 02:14 PM ----------
Hi bigeyes0x0
Air kernel V1.3 changed many things
http://forum.xda-developers.com/showpost.php?p=26318191&postcount=3
Woooow, Thank you !!
nexus.prime said:
Hi bigeyes0x0
Air kernel V1.3 changed many things
http://forum.xda-developers.com/showpost.php?p=26318191&postcount=3
Click to expand...
Click to collapse
It's fine, the mod is already written in a way that it can handle update like this with ease. If there's actually a new sysfs that isn't exist anywhere else, I will add it if I deem it necessary. If that were not the case I would be in for maintenance hell for every kernel of every dev's update .
r_data said:
Woooow, Thank you !!
Click to expand...
Click to collapse
You're welcome. I actually wanted to get into kernel dev before but it seems like destiny is a ***** and I am stuck with these, as I am not going able to find enough time to care for my ROM, this mod, the app that I wanted to create and a kernel to add to these. Ranting aside, I'm fine with how things are .
Where is trickster.conf?
Don't understand, I installed the zip, but no trickster.conf appeared in /sdcard...
Ok, probably a dumb question,
But can these literally be used on ANY rom?
Or at least any ICS rom?
For example, would this be useful on a moto atrix running ICS? (CM9 based)
There a few ICS roms for the atrix floating around and I just wanna know if I should share this thread with some of the devs over there?
I do have a G-nex that ive been able to play with over the last couple days, and its sweet! If I flash this mod, are there any noticeable changes right off the bat, or just after imputing a command through terminal?
Thanks, and nice job
sperug said:
Don't understand, I installed the zip, but no trickster.conf appeared in /sdcard...
Click to expand...
Click to collapse
Your ROM does not have init.d function, I think
forum.xda-developers.com/showpost.php?p=21232559&postcount=2
Sent from my Galaxy Nexus
Will this work without a custom rom, 4.04 boot unlocked with root and custom kernel?
Sent from my BlackBerry 9700 using Tapatalk
ATRIXXIRTA said:
Ok, probably a dumb question,
But can these literally be used on ANY rom?
Or at least any ICS rom?
For example, would this be useful on a moto atrix running ICS? (CM9 based)
There a few ICS roms for the atrix floating around and I just wanna know if I should share this thread with some of the devs over there?
I do have a G-nex that ive been able to play with over the last couple days, and its sweet! If I flash this mod, are there any noticeable changes right off the bat, or just after imputing a command through terminal?
Thanks, and nice job
Click to expand...
Click to collapse
Theoretically, it should work anywhere with an ARMv7 CPU and Android 2.3 or higher but this has been tested only on GNex varieties by me and my testers. Still as I wrote this for GNex kernels, this script of course can't change kernel features that this script does not have. Basically I think it should work but with limited functionality, to be sure just nandroid first before applying it. Still I do not support this in anyway so don't come crying to me later if anything happens and I won't answer question regarding this script and other devices further. I do believe it has some values for any device out there, but it needs ppl with some knowledge to tweak it.
EVERED78 said:
Will this work without a custom rom, 4.04 boot unlocked with root and custom kernel?
Sent from my BlackBerry 9700 using Tapatalk
Click to expand...
Click to collapse
Yeah, it should.
nexus.prime said:
Your ROM does not have init.d function, I think
forum.xda-developers.com/showpost.php?p=21232559&postcount=2
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for this, I will add this info in the first post.
any pics?
There's no pic for this, it's for tweaking and enhance ROM usability, battery life and performance.
ds4 said:
any pics?
Click to expand...
Click to collapse
Rotflmao. Apparently some people have alot to learn.
Sent from my i9250 (GSM) Galaxy Nexus
Anyone tried it on AOKP b37? Any noticeable improvement?
eRajesh said:
Anyone tried it on AOKP b37? Any noticeable improvement?
Click to expand...
Click to collapse
Don't work for me... Lost navbar and notification bar..
Sent from my Galaxy Nexus using XDA
Works lovely on Liquid 1.4
Sent from my i9250 (GSM) Galaxy Nexus
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Reserved for any common questions, or general information.
red_can_soda said:
Reserved for any common questions, or general information.
Click to expand...
Click to collapse
Nice bud, I'll have to see if it works on Lollipop TW
Using it in pvs bin 0 lol
So far so good. Make sure to set permissions to 755
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
kevp75 said:
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
Click to expand...
Click to collapse
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
red_can_soda said:
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
Click to expand...
Click to collapse
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
kevp75 said:
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
Click to expand...
Click to collapse
Forgot I had that there... Lol. Threw that in a while back so init.d would operate with a 100% stock boot.img
@kvp75, can I drop this into Phoenix Rom?
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
It will work with any galaxy note 3 using Qualcomm hardware.
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
red_can_soda said:
Drop this file in your /system/etc folder, replacing the stock one.....
Click to expand...
Click to collapse
Lmao....Cob
kevp75 said:
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
Click to expand...
Click to collapse
All good, I went ahead and did it anyway, it's def making a difference, battery life was not great but now it's better! Thanks for all the hard work guys, keep it up! I'll reflash DomPop again soon, it was unstable for me but Phoenix has been great
This activated all cores and set to performance... when i selected interactive the min value was 422... Am I doing something wrong? Everything stock and rooted 442
Edit. .. Ok I changed from interactivex to interactive and that fixed gov problem but all cores activated and min set to 422... Is that right?
Yes, minimum is 422 MHz because the l2 cache is bumped into action at that speed (as opposed to not being so at 300) and the voltage is the same.
In short, 300 is no5 used because 422 is faster, and without the extra hit on battery
Will this work with 4.4.4 w/o any issues? Been thinking on trying it on but I don't want it to mess anything and re-install stuff.
d-wad,
I cannot give you a definite answer there, as I have not yet looked at anything in 4.4.4.
If you can provide me a copy of the post_boot file for 4.4.4, I can take a look at it and see. I can't imagine why anything would have changed in this file, but you never know. All it takes is one line of code to cause something to go a little wonky for you.
Thanks, and just shoot me a PM.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated file and link... I recommend using this file or implementing these items into your current set up. Many of the changes are critical errors existing in the stock post_boot file, or simple optimization enhancements for our devices.
How to revert?
Sorry... TOTAL NOOB here...Do I just copy the orig file somewhere else, and drop this in place as you instruct? ( may have answered my own Q)
Seems a wise precaution.
I am running effortless rom rev 8 (lovin it too)
OPTIMIZE YOUR CM13
PREREQUISITES:
CyanogenMod 13 ROM
Nokia X
You
First of all, this thread's purpose is to make our Marshmallow Experience better. I have been using a CM13 ROM and it's good, but it can never surpass Stock ROM in stability, smoothness and other things alike.
Now, assuming that you've already done all the things that has to be done on successfully booting the ROM (repartitioning, flashing Gapps, etc), we're gonna start .
TIPS
NO. 1
Code:
Do not use too many apps! I mean, we have a very low end phone right here and were aiming to make it better. Use only the apps that you need. Much less apps, much less lag :good:
NO. 2
Code:
If you're gonna have to flash Gapps, flash the [I]pico[/I] one. Since it's the most logical thing to use in this device.
NO. 3
Code:
Refrain from using themes. They consume RAM and lags the UI.
NO. 4
Code:
Replace Trebuchet(CM's default launcher) with any other third party launchers. *cough*Nova*cough*
NO. 5
Code:
Use other root solutions (SuperSU, Magisk etc). I had problem with CM su.
More to come
TRICKS
NO. 1
You're gonna have to enable developer options in setting (tap build no. until it's enabled). The go to Hardware accelerated rendering. Enable Force GPU rendering and Disable HW overlays. You can optionally tweak the animation speed if you like.
NO. 2
The DPI of the ROM is 240, which I think is okay for our phones. But on my opinion, the best one that suites or device is 220. You can change it in Setting > Display & lights > LCD density
NO. 3
Having only the back button working is a pain. We can enable the Navigation Bar by adding this line to /system/build.prop
Code:
[FONT="Courier New"]qemu.hw.mainkeys=0[/FONT]
NO. 3
Enable root in Settings > Developer options > Root access. Choose Apps and ADB
REMOVING CM BLOATWARES
Assuming you already have Root access, Install Terminal Emulator.
After that type:
Code:
su
Which will then prompt you with Root authentication, grant it.
Now, we can disable (not delete/uninstall) bloats using this command,
Code:
pm disable <name of the app>
Here's the list of what we don't need:
org.cyanogemod.screencast (Screen Recorder)
org.cyanogenmod.theme.chooser2 (Theme Chooser, we don't need it )
com.android.email (Do you use email?? If you do, do not include this)
com.android.exchange (Exchange Services)
All of the live wallpapers and Live wallpaper picker (i think you can find them on your own)
com.android.cellbroadcastreceiver (Cell Broadcast)
com.cyanogenmod.updater (CM Updater)
com.android.printspooler (Print Spooler)
com.svox.pico (Pico TTS)
org.cyanogenmod.screencast (Screen Recorder)
org.cyanogenmod.weather.provider (Weather Provider)
org.cyanogenmod.weather.service (Weather service)
BUILD.PROP TWEAKS
Next thing we do is to add these on build.prop
Code:
debug.performance.tuning=1
persist.sys.ui.hw=1
persist.sys.composition.type=gpu
dalvik.vm.dex2oat-filter=interpret-only
dalvik.vm.image-dex2oat-filter=interpret-only
debug.composition.type=gpu
video.accelerate.hw=1
ro.kernel.checkjni=0
profiler.force_disable_ulog=0
profiler.debugmonitor=false
debugtool.anrhistory=0
# more to come
KERNEL ADIUTOR
Install this one Kernel Adiutor and you can edit many things.
Go to CPU section, then choose ondemand as default governor since it's basically more performance driven that other governors (except performance governor ).
MORE TO COME :highfive:
XDA:DevDB Information
CM13 Optimizer, Tool/Utility for the Nokia X
Contributors
veez21, weritos
Version Information
Status: Beta
Created 2016-12-31
Last Updated 2017-05-01
Reserved
Reserved
let me add some..open kernel adiutor...
1) change io scheduler...its most important.. better choose cfq bcoz default is deadline which means single task only...that is you can't pull even status bar while an app is opening!!!
2) my CPU settings ( to prevent overheating and greater performance)
choose conservative governor
then choose its settings and set
low/min threshold=65
high/max threshold=90
its just the best setting for everything
ani00 said:
let me add some..open kernel adiutor...
1) change io scheduler...its most important.. better choose cfq bcoz default is deadline which means single task only...that is you can't pull even status bar while an app is opening!!!
2) my CPU settings ( to prevent overheating and greater performance)
choose conservative governor
then choose its settings and set
low/min threshold=65
high/max threshold=90
its just the best setting for everything
Click to expand...
Click to collapse
Thanks for the suggestion. I will add that but not now. It's almost New Year :laugh:
can you give me kenrel and boot.img and build.prop for xl
UPDATED
New Tricks
Added more build.prop tweaks
New bloats
Fixed some typos
please make a patch for nokia xl...
We Need All This Is The Most Important On Cyanogen ROM
i still not have cm13 rom....where can i get it????
abhijit1998 said:
i still not have cm13 rom....where can i get it????
Click to expand...
Click to collapse
sorry, I'm not allowed to do that, but you can actually just apply these in cm11 based roms, we have plenty of those here. :good:
veez21 said:
sorry, I'm not allowed to do that, but you can actually just apply these in cm11 based roms, we have plenty of those here. :good:
Click to expand...
Click to collapse
ok.....:crying:
veez21 said:
sorry, I'm not allowed to do that, but you can actually just apply these in cm11 based roms, we have plenty of those here. :good:
Click to expand...
Click to collapse
Do I have to bought cm13 ROM from weritos?
UPDATED
New build.prop tweaks
veez21 said:
New build.prop tweaks
Click to expand...
Click to collapse
Where to get cm13 ROM?
https://forum.xda-developers.com/an...od-ultimate-performence-blazing-fast-t3482317
just try this bro...
you will love it
ani00 said:
https://forum.xda-developers.com/an...od-ultimate-performence-blazing-fast-t3482317
just try this bro...
you will love it
Click to expand...
Click to collapse
lol, most of the scripts inside it doesn't work. Placebo of you ask me. The dev(or is he?) doesn't even know what he's doing. He was just putting things together not knowing what they do and how they work. Trust me. All guys who complimented the so called mod has no idea what's going on with the scripts inside and what they do and if they work. I don't even want to comment there.
veez21 said:
lol, most of the scripts inside it doesn't work. Placebo of you ask me. The dev(or is he?) doesn't even know what he's doing. He was just putting things together not knowing what they do and how they work. Trust me. All guys who complimented the so called mod has no idea what's going on with the scripts inside and what they do and if they work. I don't even want to comment there.
Click to expand...
Click to collapse
agreed...but bro if it works theoretically or not, doesnt matter..
what finally matter is the performance amd battery,
with 1st boot, i can feel a massive difference... i actually cant feel if its old slow nokia..
even i have tried many mod, none worked before
anyways its your opinion
ani00 said:
agreed...but bro if it works theoretically or not, doesnt matter..
what finally matter is the performance amd battery,
with 1st boot, i can feel a massive difference... i actually cant feel if its old slow nokia..
even i have tried many mod, none worked before
anyways its your opinion
Click to expand...
Click to collapse
Actually, the difference you feel comes from the cpu/governor something script, which pushes the cpu to it's limits. Every other script won't do anything, that's why they have another guy managing the beta thread because the orig guy doesn't know how to
any place for getting cm13 ROM????