Database Info

[MOD] IncrediControl - Easy GUI Undervolting

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229

Hi,
Good job, just one thing, i use Eviollet kernel (svs) and there's a step at 128 mhz.
The apps doesn't show these step.
It Would be great if you can implement it.
Otherwise i found no bug.
Thx in advance.

sffmandrake said:
Hi,
Good job, just one thing, i use Eviollet kernel (svs) and there's a step at 128 mhz.
The apps doesn't show these step.
It Would be great if you can implement it.
Otherwise i found no bug.
Thx in advance.
Click to expand...
Click to collapse
The app skips the first frequency because on a lot of phones its a.useless frequency like 19mhz. Thanks for letting me know though. I will add an exception and upload a new version later.
Sent from my ADR6300 using XDA App

7/31/11 - Preview 5-4
Minor change to no longer skip the first frequency. On many phones the first frequency is a useless frequency like 19mhz so the app was set up to skip that frequency. This is only a temporary fix until I change it to display only the available frequencies instead of all of them.

Sounds interesting, will have a go

Hi,
Thx chad0989, now it works at 128 mhz

sffmandrake said:
Hi,
Thx chad0989, now it works at 128 mhz
Click to expand...
Click to collapse
Great. I just sent you a PM.

Works great thanks!

IncrediControl v1.0!
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!

Good job. Works on cm7 nightly with manU kernel 2.1.1.

chad0989 said:
The app skips the first frequency because on a lot of phones its a.useless frequency like 19mhz.
Click to expand...
Click to collapse
The eviollet Kernel implements AXI @ 128Mhz, which drops the bus down to 19Mhz which potentially could save more battery

rootSU said:
The eviollet Kernel implements AXI @ 128Mhz, which drops the bus down to 19Mhz which potentially could save more battery
Click to expand...
Click to collapse
But the actual cpu speed still never drops below 128mhz if I'm not mistaken (at least thats how it is on the inc, its possible to enable the use 19mhz cpu speed, but the phone is unusable). So the cpu voltage for 19mhz would never be used. I have changed the app now though to show all cpu frequencies available for use, so if you did enable the use of 19mhz cpu speed (you have to comment out a line in the acpuclock file), it would show up.
Hopefully that clears up confusion.

IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.

IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.

I'm making an enquiry for a friend who uses his HTC desire with RCMix S v2.0 Evolutionary Sense using SNQ v05 kernel. Does this Rom / kernel meet the InvrediControl system requirements?
One other question, in other utils I've used in the past they also supply a "reset" zip which can be used to revert the settings back to default in the event if instability/freeze (requires flash from recovery). Do you see value in creating a similar zip for over agressive UV?
Thanks again for a wonderful utility. Can't wait to try it.
Sent from my Desire HD using XDA App

fidoedidoe said:
I'm making an enquiry for a friend who uses his HTC desire with RCMix S v2.0 Evolutionary Sense using SNQ v05 kernel. Does this Rom / kernel meet the InvrediControl system requirements?
One other question, in other utils I've used in the past they also supply a "reset" zip which can be used to revert the settings back to default in the event if instability/freeze (requires flash from recovery). Do you see value in creating a similar zip for over agressive UV?
Thanks again for a wonderful utility. Can't wait to try it.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I don't believe that kernel has the sysfs interface for adjusting voltages. You can still give it a shot though. The app will let you know if the kernel doesn't have the correct interface.
I also have a reset zip. It's on the site and there is a link in the OP.

SNQ anyone?
Ahhhw...no love for the wildly popular SNQ Kernal?!

SilverHawk2 said:
Ahhhw...no love for the wildly popular SNQ Kernal?!
Click to expand...
Click to collapse
The kernel dev has to implement the interface in order to use the app. Since I don't believe that the source for the GB kernel has been released yet for the desire, the dev won't be able to implement the interface until it is.

chad0989 said:
The kernel dev has to implement the interface in order to use the app. Since I don't believe that the source for the GB kernel has been released yet for the desire, the dev won't be able to implement the interface until it is.
Click to expand...
Click to collapse
Thanks for the heads up. Next time I have access to the phone I will install and see what unfolds. But from what you said I'm not expecting much with SNQ.
Maybe time to suggest to my friend a new Rom

[Kernel][GPL] Development 3.0 Kernel

Current state of 3.0 Kernel
WiFi/Thether/p2p - 100%
TouchScreen - 100%
Video Codec/hw 720p/ION stuff - 100%
Display/DSS - 100%
Phone/3G data - 100%
Sound/FM-Radio - 100%
F2FS support - 100%
GPU OC 266mhz - 100%
Bluetooth - 95%
USB - 98%, otg bugged.
Sensors - 98%, Need test all sensors, looks like all sensors works
Camera - 85%, Preview/Photo(Red have random problem)/Panorama works for both lenses. Video rec not work yet.
Overclock CPU- 0%, not implemented.
For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
Tips:
Do not format System and Cache to F2FS!!!
1. To use f2fsl "/system/bin/mkfs.f2fs /dev/block/mmcblk1p25" or format via TWRP (Advanced wipe menu).
2. To restore ext4, in recovery unmount data, mount system, and do via adb shell /system/bin/make_ext4fs /dev/block/mmcblk1p25 or format via TWRP (Advanced wipe menu).
3. If you have 0 bytes free bug, reformat data to f2fs or ext3/4.
4. 1.1 Ghz can be enabled in performance settings.
Click to expand...
Click to collapse
If you liked this project, you can donate
Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]
Click to expand...
Click to collapse
Download: http://quarx2k.ru/index2.php?dir=buildbot/roms/defy-cm11.0-3.0
Sources of kernel availabe here(branch p-android-omap3-3.0): https://github.com/Quarx2k/jordan-kernel/tree/p-android-omap3-3.0

Changelog:
17.11:
Added timer slack controller
Added dynamic fsync
Added proportional rate reduction for TCP
Added opensource camera driver (mt9p012)
Added syspanic driver for panic_daemon
Added sync framework (together with ION its part of androids graphical "project butter")
Switched to SLUB allocator
Enabled ram console Support
Synced binder to mainline version (~3.10)
Fixed reboot while incoming or outcoming call (fix proximity sensor in general)
Many small performance patches and fixes for better android support all over the place
Logs or it didn't happen! If you want to report a problem, be sure to post a log file!
Here is a small guide when we need which log file and how to get it.
Old Changelog;
Added new extra_free_kbytes tuable (4.4 compatibility)
Added our Interactive Governor from 2.6.32 for additional performance
Added a basic display control driver
Added a dynamic writeback control interface
Enabled cgroups for memory (4.4 compatibility)
Enabled deadline and changed tunables to the same as on 2.6.32
Enabled xattr and fs security for ext3/4
Patched up trim (ext3/4) to the latest mainline version
Switched to XZ compression for a smaller kernel image
Reclaimed some RAM from logger and vram
*Fixed the wakeup delay and the "funny" screen on resume
TODO:
Add Overclock driver
Fix kpanic with pvr and dss (solved?)
Fix sleep problem
How To Build
Code:
git clone https://github.com/Quarx2k/jordan-kernel.git
cd jordan-kernel
git checkout --orphan p-android-omap3-3.0
git pull https://github.com/Quarx2k/jordan-kernel.git p-android-omap3-3.0
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
make mapphone_defconfig
make -j12
Sys-Values explanation;
Let me explain some of this features a little bit. 3.0.8 offers completely new opportunities to do some magic stuff.
One thing i developed a while back ago is a dynamic writeback driver with a sys-interface. It uses the earlysuspend kernel api
to flush dirty pages more frequent when in suspend, while display is on it avoids it to give a more fluid user interface.
Can be controlled via the following command;
echo 1 > /sys/devices/virtual/misc/writeback/writeback_enabled
(1 for enabled = default, 0 for disabled)
Click to expand...
Click to collapse
Also new; a basic display driver! As i tried to fix some things in our dss driver i noticed that we have different panel configurations.One is for all defy green and one for defy red lense users. I exposed those values to user space so that they can be changed. The
new default one are those, which are used on the red lense defy. In theory there could be 256 values (0-255), however could only find the
following as useful. This is not the final gamma control i wanted to have, but at least it gives some control. If someone knows the proper
addresses for gamma values, i can add them too
echo xx > /sys/class/misc/display_control/display_brightness_value
(0 will set the screen to almost 0,
9 will set the screen to some kind of blue-washed colors,
31 will set the screen to more warmer colors = default)
Click to expand...
Click to collapse
In order to run 4.4 more fluid, google made a guide and also published some recommended patches. One of them let you change
the VM's behavior to have a minimum amount of free memory. Also controllable over a interface;
echo 8192 > /proc/sys/vm/extra_free_kbytes
Click to expand...
Click to collapse
8192 means 8 MB of free ram (in any case).

Thanks for this information
Gesendet von meinem Nexus 4 mit Tapatalk 2

If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?

a separate thread was really needed for 3.0.8 kernel.
thank u quarx and Blechd0se

matiasrey said:
If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?
Click to expand...
Click to collapse
I am guessing it's the Camera?

Honestly, i think its time to stop working on the 2.6.32 kernel and focus on 3.0.x, looking as an atrix user, its definetly the best choice devs could do. Hehe
Sent from my LG-E975 using Tapatalk

Once again, thanks!!!

@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?

niksy+ said:
@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?
Click to expand...
Click to collapse
its a 5mp camera, so we should go for the old moto drivers, easiest stuff to do right?

Once it works with open source driver for camera, free forever...
Sent from my Nexus 7 using xda app-developers app

I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho

niksy+ said:
I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho
Click to expand...
Click to collapse
Yes Quarx is doing a very good job here, still struggling with a last few bugs. Anyway, its progress! Also the huge battery drain should be fixed,
i disabled kmemleak. 3.0 is such a nice base to work with, no need to do hacky things, it just works out of the box.
Next version will have timer_slack controller (its working perfectly). Also many fixes for crashes and memory leaks.
One big thing is still the display. Although wakeup delay is gone for me, dss/pvr crashes sometimes. Its very random.
Also overclocking has two sides; on the one side its much easier to understand, on the other side it doesn't work as expected (can't overclock
to 1200mhz for example). But we have finally a nice voltage/frequency table.

Glad to read the good news, doesn´t seem too far from a usable kernel!
Have you decided what camera drivers you´ll go for?

F* yeah! "isl29030: fix reboot of proximity sensor" commit signed off by Blechd0se
Quarx has been focusing on the in-call sound issue today, so things are looking brighter by the day
*edit* I'm guessing more and more people use the thanks button as the like button

When I wake up in the morning and read Quarx github , appear "Add Micron MT9P012 sensor driver" , so I think we can hope at an camera soon...

OTG!!
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?

mayur2j said:
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?
Click to expand...
Click to collapse
Yes, but with external power.

major9 said:
Yes, but with external power.
Click to expand...
Click to collapse
So it's of almost no use then..

External power? I can conenct mouse/keyboard or flash drives, no need external power.

[KERNEL][A510/A700][07/30] Z-Kernel Beta

Welcome to Z-Kernel's thread!​
Features
- Base kernel fully updated to linux-tegra-nv-3.1 (bug fixes & performance improvements)
- Simplified board codes
- Cleaned up Acer specific code
Click to expand...
Click to collapse
Changelog
r2:
- Restarted kernel development (r1's features not implemented yet)
- Base kernel fully updated to linux-tegra-nv-3.1 (bug fixes & performance improvements)
- Simplified board codes
r1:
- CPU OC to 1.6 ghz by default (should be stable)
- GPU OC support up to 700MHz (default is 520 mhz)
- Overclocked LP core from 500 to 620 mhz
- Custom user voltage control for CPU and Core components such as EMC, GPU, and LP (faux123)
- Dynamic FSYNC
- Optimized KSM
- Optimized ZRAM
- Compiled using latest Linaro toolchain with optimized compiler flags
- Optimized SLUB and use SLUB by default instead of SLAB
- Glibc memcpy and memmove
- Deadline improvements for solid state drives
- Proportional Rate Reduction for TCP
- Tegra 3 variant display (faux123)
- Optimized swahb32 byteswap helper
- Asynchronous I/O latency improved through removal of plug in do_io_submit()
- allow use of an I/O controller's native max block size
- Optimized ARM RWSEM algorithm
- timer: optimize apply_slack()
- Optimized crypto algorithms
- Optimized AES and SHA1 routines
- LowMemoryKiller fixes and improvements
- Lock performance governor to all 4 cores
- Many scheduler improvements and optimizations
- updated bcmdhd driver (wifi)
- over 450 changes committed, so the above list isn't complete
Click to expand...
Click to collapse
Complete list of changes can be found in the commit log: https://github.com/Ziyann/android_kernel_acer_t30
I'm not responsible if anything bad happens with your device!
This build has been tested on CM11 only, so if you run into something with other ROMs, report it and I will see what I need to change to cooperate with it.
XDA:DevDB Information
Z-Kernel, Kernel for the Acer Iconia A700 and A510
Contributors
Ziyan
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R2
Stable Release Date: 2014-07-30
Created 2014-09-23
Last Updated 2014-09-23

Nice, if it's working fine, I hope you will also support the A510/A511

Shreps said:
Nice, if it's working fine, I hope you will also support the A510/A511
Click to expand...
Click to collapse
Of course, I'll see what can I do when I get everything (OC, UV, ...) working here waiting for a tester...

it is indeed slow. even when completely debloated plus stripped of "essential" system components that I personally do not use. I will try this right away. will report back within an hour in this post.
@Ziyan
it boots, runs, everything seems standard. not seeing any performance increases though. same ol' 10 to 15 fps is there anything more you wish for me to test with it? I replaced this tab a while ago with galaxy note pro 12.2 so I can't really use it enough to check for random reboots

Sterist said:
@Ziyan
it boots, runs, everything seems standard. not seeing any performance increases though. same ol' 10 to 15 fps is there anything more you wish for me to test with it? I replaced this tab a while ago with galaxy note pro 12.2 so I can't really use it enough to check for random reboots
Click to expand...
Click to collapse
Thanks, that's good, it means I can continue improving it. I need to check the kernel periodically after a big bunch of commits, because if something gets broken, it can be hard to find what causes it if from a thousand things I'll push a new version and changelog later today or tomorrow.

sounds good. quote this post when it's uploaded, it'll send me am email notification and I can get right on it.

Sterist said:
sounds good. quote this post when it's uploaded, it'll send me am email notification and I can get right on it.
Click to expand...
Click to collapse
Here's a new version. Before testing it, please make some benchmarks with the previous version (mainly 3D), because - if everything works as it should -, the GPU is now working at 520 mhz instead of 416. It should also have CPU overclocking and voltage control support, so please install Trickster Mod, or something like that from Play Store to see if it works (screenshots are welcome). If it works (i'd be a bit surprised lol it was too easy), please run some benchmarks again to see if there's a noticeable difference. I've got 12 pages of commits waiting to be merged, so yeah, if something got broken, I better fix it now :silly:

Ziyan said:
Here's a new version. Before testing it, please make some benchmarks with the previous version (mainly 3D), because - if everything works as it should -, the GPU is now working at 520 mhz instead of 416. It should also have CPU overclocking and voltage control support, so please install Trickster Mod, or something like that from Play Store to see if it works (screenshots are welcome). If it works (i'd be a bit surprised lol it was too easy), please run some benchmarks again to see if there's a noticeable difference. I've got 12 pages of commits waiting to be merged, so yeah, if something got broken, I better fix it now :silly:
Click to expand...
Click to collapse
just woke up and leaving for work in 20 minutes. when I get there and settle in (about an hour and 20min from this post) I'll test it
which benchmark though, antutu?

Sterist said:
just woke up and leaving for work in 20 minutes. when I get there and settle in (about an hour and 20min from this post) I'll test it
which benchmark though, antutu?
Click to expand...
Click to collapse
Yeah, antutu will do, just note the invidual points

Ziyan said:
Yeah, antutu will do, just note the invidual points
Click to expand...
Click to collapse
woah woah... I just went to download the second version and the tab was dead from 77% last night, still warm.
there's a wake problem, screen will turn on one time after booting up but only that one time
and a sleep problem, after manually turning the screen off it will not turn back on (and kills battery very quickly!)

Sterist said:
woah woah... I just went to download the second version and the tab was dead from 77% last night, still warm.
there's a wake problem, screen will turn on one time after booting up but only that one time
and a sleep problem, after manually turning the screen off it will not turn back on (and kills battery very quickly!)
Click to expand...
Click to collapse
Thanks for the report, I'll investigate the problem tomorrow (it's 01:30 AM here :silly. If you could take a dmesg (while turning the screen off, then trying to turn it back on), or last_kmsg, that would be great help! If you don't know how, refer to section 2 and 3: http://forum.xda-developers.com/showthread.php?t=1520508

Ziyan said:
Thanks for the report, I'll investigate the problem tomorrow (it's 01:30 AM here :silly. If you could take a dmesg (while turning the screen off, then trying to turn it back on), or last_kmsg, that would be great help! If you don't know how, refer to section 2 and 3: http://forum.xda-developers.com/showthread.php?t=1520508
Click to expand...
Click to collapse
higher score / lower 3D performance is v1
lower score / higher 3D is v0
recent apps cleared and CPU set to 1400 performance and ROW
no app gives OC/UV options with v1
I don't have access to a pc at work so can't run dmesg properly for this, and I'm having trouble reproducing the sleep crash now
this is probably all exactly what you did not want me to say lol
edit: so, I got it to crash again (yay!) but can't get klast to work (read only fs) I tried mounting various directories as RW but honestly I have no idea which to do... and here's dmesg which may or may not contain what you need.
I know it might be a little early to ask but any chance you could implement Frandom?

Sterist said:
(cut)
edit: so, I got it to crash again (yay!) but can't get klast to work (read only fs) I tried mounting various directories as RW but honestly I have no idea which to do... and here's dmesg which may or may not contain what you need.
I know it might be a little early to ask but any chance you could implement Frandom?
Click to expand...
Click to collapse
Thanks for the detailed report, I think I revert Franco's hotplugging driver for now, seems like it's on a rampage. May try again in the future.
As for the last_kmsg, your first command was correct, it's just that it doesn't always get created.
We'll see about Frandom when we get things working nice
Here's a build with the stock hotplugging driver, report back if it still crashes.

Ziyan said:
Thanks for the detailed report, I think I revert Franco's hotplugging driver for now, seems like it's on a rampage. May try again in the future.
As for the last_kmsg, your first command was correct, it's just that it doesn't always get created.
We'll see about Frandom when we get things working nice
Here's a build with the stock hotplugging driver, report back if it still crashes.
Click to expand...
Click to collapse
ok I let it idle for about 30 minutes (that was enough to crash every time I left it alone at work) and so good so far.
still no OC/UV though
edit... idle 2 more hours and no problems

Sterist said:
ok I let it idle for about 30 minutes (that was enough to crash every time I left it alone at work) and so good so far.
still no OC/UV though
edit... idle 2 more hours and no problems
Click to expand...
Click to collapse
Great, let's see if CPU OC/UV works with this one. If it does, don't forget to run a benchmark, as GPU OC didn't work till now

Ziyan said:
Great, let's see if CPU OC/UV works with this one. If it does, don't forget to run a benchmark, as GPU OC didn't work till now
Click to expand...
Click to collapse
still no CPU OC/UV. also, that 52mhz step has never worked on any ROM or kernel I've tried, that may extend battery life

Sterist said:
still no CPU OC/UV. also, that 52mhz step has never worked on any ROM or kernel I've tried, that may extend battery life
Click to expand...
Click to collapse
Ok, it must work now.
About 52 mhz, it's so low that any small background work would ramp up the CPU to hispeed_freq, so in the end, it would shorten battery life. The same thing happens with Galaxy Nexus if we go down to 180 mhz, which is a lot, compared to 52 mhz
I've added about 200 commits since your last try (this is a great daily activity :silly, the kernel is getting to be on pair with a Nexus 7 kernel soon if we get OC/UV and some more extra things working :highfive:

Ziyan said:
Ok, it must work now.
About 52 mhz, it's so low that any small background work would ramp up the CPU to hispeed_freq, so in the end, it would shorten battery life. The same thing happens with Galaxy Nexus if we go down to 180 mhz, which is a lot, compared to 52 mhz
I've added about 200 commits since your last try (this is a great daily activity :silly, the kernel is getting to be on pair with a Nexus 7 kernel soon if we get OC/UV and some more extra things working :highfive:
Click to expand...
Click to collapse
ok so UV menu now loads but doesn't look to work quite right - not usable. this is the menu I was looking for that did not load before
OC still does not work though
about 52 (51 actually) every time it is selected, after I leave the screen and come back 102 becomes the selected minimum automatically, even if lock frequency at 51
need benchmark? and ty ty your time!

Sterist said:
ok so UV menu now loads but doesn't look to work quite right - not usable. this is the menu I was looking for that did not load before
OC still does not work though
about 52 (51 actually) every time it is selected, after I leave the screen and come back 102 becomes the selected minimum automatically, even if lock frequency at 51
need benchmark? and ty ty your time!
Click to expand...
Click to collapse
At least we're making progress :good: try this one, and also try trickster mod (specific and general menu).
Benchmarks are welcome, those 200 commits should improve performance a bit, though I think most of them can only be seen in real usage (low memory killer, zram, ...)

Ziyan said:
At least we're making progress :good: try this one, and also try trickster mod (specific and general menu).
Benchmarks are welcome, those 200 commits should improve performance a bit, though I think most of them can only be seen in real usage (low memory killer, zram, ...)
Click to expand...
Click to collapse
bootloop, won't get past Acer logo
benchmark is from the last kernel

[Kernel][Ville S4][LP] - Mrak Kernel by mikronac.ns 2015-10-12

Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/
I am presenting to you StockLike kernel. My idea is to keep kernel simple, close to stock functions. For beggining, I just undervolted frequencies to achive better battery life. Additional functionality like S2W, d2tw, etc will not be implemented.
Changelog:
Feb 23
Enable S2W, S2W, DT2W
Feb 22
-Compiled with Linaro GCC 4.9.3-2015.02 Toolchains
-Set Multi Core Power Saving Mode to 2
-New name, Mrak kernel
Feb 21
- GCC 4.9 Used
- Linux 3.4.106
- Some Updates From CM 12
- F2FS ready
- Voltage Control
- CPU and GPU OC
- TCP Congestion Controls
- Optimized Algorithms
- Fast Charge
- Export Krait Variant
- Simple GPU Governor
- BFQ, FIOPS, SIO I/O Schedulers
- Intellidemand, Intelliactive, Intellimm, and ElementalX Governors
- FRANDOM Support
- exFAT Support
- Asynchronous Fsync
- BLN (report if (not) works)
-Add -Stockie-Kernel to the Kernel Version
Jan 15
-GCC 4.8 Used
-Base Updated to 3.4.105
-Overclocked L2 Cache
Click to expand...
Click to collapse
Download: LINK
Kernel Souce
XDA:DevDB Information
[Kernel][Ville S4][AOSP][KK && LP] - Mrak Kernel by mikronac.ns, Kernel for the HTC One S
Contributors
mikronac.ns, javelinanddart
Kernel Special Features:
Version Information
Status: Stable
Created 2014-10-02
Last Updated 2015-10-16

Mine...

Will this kernel have some of the Bubba features? Also it'll be based on the 3.4.82 kernel or it'll be in sync with CAF like bubba was (I think it has reached 3.5.x something already or it is 3.4.100+ since latest Bubba was 3.4.99)?
Will you also include additional governors (like the intellidemand, intelliactive and so on), GPU govs/OC, BLN ..?
Thank you

Rapier said:
Will this kernel have some of the Bubba features? Also it'll be based on the 3.4.82 kernel or it'll be in sync with CAF like bubba was (I think it has reached 3.5.x something already or it is 3.4.100+ since latest Bubba was 3.4.99)?
Will you also include additional governors (like the intellidemand, intelliactive and so on), GPU govs/OC, BLN ..?
Thank you
Click to expand...
Click to collapse
Please, write me which Bubba features?
It will be based on stock 3.4.82. I have plan to add additional governors, IO schedulers and BLN...
Maybe some optimization algorithms but without OC (for now)...

mikronac.ns said:
Please, write me which Bubba features?
It will be based on stock 3.4.82. I have plan to add additional governors, IO schedulers and BLN...
Maybe some optimization algorithms but without OC...
Click to expand...
Click to collapse
Mainly it is that "sleepy-plug" that rmbq used instead of the mpdecision algorithm to increase battery life. It was a brilliant idea and was working great, I would love to see that feature again not being "dead". Then comes the GPU new govs and ability to OC the GPU (not the CPU).... And the sync with CAF sources, eg. keeping the kernel updated to the last base. I'll add more if I remember more.
Sent from nowhere over the air...

Rapier said:
Mainly it is that "sleepy-plug" that rmbq used instead of the mpdecision algorithm to increase battery life. It was a brilliant idea and was working great, I would love to see that feature again not being "dead". Then comes the GPU new govs and ability to OC the GPU (not the CPU).... And the sync with CAF sources, eg. keeping the kernel updated to the last base. I'll add more if I remember more.
Sent from nowhere over the air...
Click to expand...
Click to collapse
yeah but it is better to compile Bubba kernel with newest WiFi base. Here I want to be close to stock kernel...
Maybe I will have time today after work to compile and test Bubba... I dont know what is happening with @rmbq?

mikronac.ns said:
yeah but it is better to compile Bubba kernel with newest WiFi base. Here I want to be close to stock kernel...
Maybe I will have time today after work to compile and test Bubba... I dont know what is happening with @rmbq?
Click to expand...
Click to collapse
Thank you, I've already send a PM to you regarding this since I didn't want to clutter the thread with discussions about other kernels. Take your time.
Nothing is wrong with rmbq I guess, he said he'll move to another device/projects so that's why he stopped bubba
Sent from nowhere over the air...

Primary devhost link don't have DL links, DB mirror is ok.
Can't play with phone until evening, so will test it then but just a quick question - Qualcomm iris fm supported?
Update: FM radio is working. WiFi is not, but I'm on oneplus one cm11 so it's my side. What has suprised me was that after flashing kernel, i was on 13.08. Ice, battery dropped from 64% to 21% in a flash. I remember that it was on 66% when switch to recovery, 64% after boot and several sec later it was on 21%. Than reboots started, reboots with data loss. Traffic counter was reseted, all zeroes, whatsapp was like data was cleared, no recents pics or docs, root explorer was back to fabric state. So i had to quickly return to Ice cause i had no charger in vicinity. OFC soon phone turned off

Loreane Van Daal said:
Primary devhost link don't have DL links, DB mirror is ok.
Can't play with phone until evening, so will test it then but just a quick question - Qualcomm iris fm supported?
Update: FM radio is working. WiFi is not, but I'm on oneplus one cm11 so it's my side. What has suprised me was that after flashing kernel, i was on 13.08. Ice, battery dropped from 64% to 21% in a flash. I remember that it was on 66% when switch to recovery, 64% after boot and several sec later it was on 21%. Than reboots started, reboots with data loss. Traffic counter was reseted, all zeroes, whatsapp was like data was cleared, no recents pics or docs, root explorer was back to fabric state. So i had to quickly return to Ice cause i had no charger in vicinity. OFC soon phone turned off
Click to expand...
Click to collapse
It happens to me on Bubba every time I flashed it... Stock kernel haven't that behavior... About FM: Which FM App are you using? I guess that is 1+1 Native app? Can you share it?

mikronac.ns said:
It happens to me on Bubba every time I flashed it... Stock kernel haven't that behavior... About FM: Which FM App are you using? I guess that is 1+1 Native app? Can you share it?
Click to expand...
Click to collapse
Do you know what is a reason for such behavior? I also had strange reboots on bubba. Think it's because of lower voltage on slower krait. But, with lowered voltage on @AKToronto 's IceCold phone is rock solid. So it beats me up.
Using Spirit fm. Both 1 and 2 r working.
1+1 don't have FM radio, although it does have qualcomm combo wifi/bt/fm chipset.

Loreane Van Daal said:
Do you know what is a reason for such behavior? I also had strange reboots on bubba. Think it's because of lower voltage on slower krait. But, with lowered voltage on @AKToronto 's IceCold phone is rock solid. So it beats me up.
Using Spirit fm. Both 1 and 2 r working.
1+1 don't have FM radio, although it does have qualcomm combo wifi/bt/fm chipset.
Click to expand...
Click to collapse
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app

Delete

mikronac.ns said:
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was on interactive, set it via trickster, but there were reboots.
Spirit2 is working with me with no aditional settings, just changed to EU+ from US. Tuner knob is not tunning but i use "arrows". Spirit1 has a good reception in Belgrade and also down the "south railway"

https://www.androidfilehost.com/?fid=95897840722643297
This is basically stock kernel with undervolted table.
And, it is based on 3.4.105, not on 3.4.82.
Nothing less, nothing more.
It is only for KitKat, when I switch to LP, there will be LP version.

mikronac.ns said:
https://www.androidfilehost.com/?fid=95897840722643297
This is basically stock kernel with undervolted table.
And, it is based on 3.4.105, not on 3.4.82.
Nothing less, nothing more.
It is only for KitKat, when I switch to LP, there will be LP version.
Click to expand...
Click to collapse
Switching to LP won't be hard:
Code:
git remote add cm https://github.com/CyanogenMod/android_kernel_htc_msm8960
git fetch cm
git checkout -b cm-12.0
git reset --hard 594eaa187a86da35487f59b9f2913e0f28fc5826
git merge cm/cm-12.0
git push -u origin cm-12.0
curl https://raw.githubusercontent.com/mikronac/android_kernel_htc_msm8960/cm-11.0/arch/arm/mach-msm/acpuclock-8960.c > arch/arm/mach-msm/acpuclock-8960.c
git commit -asm "Undervolting & L2 Cache OC"
curl https://raw.githubusercontent.com/mikronac/android_kernel_htc_msm8960/cm-11.0/drivers/cpufreq/cpu-boost.c > drivers/cpufreq/cpu-boost.c
git commit -asm "Fix cpu-boost.c"
git push
Also you might want to take a look at this commit:
https://github.com/javelinanddart/a...mmit/53b9168f745d100be8841b3d89eb04c122ac3924
It's GCC 4.9.x Fixups for future-proofing or to start using GCC 4.9

I knew this but thanks. I don't want to make it until I switch to LP.
Sent from my One S using XDA Free mobile app

mikronac.ns said:
I knew this but thanks. I don't want to make it until I switch to LP.
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Just letting you know.
I'm with you though. I haven't switched to LP and it's still a long way in the works.
What features are you planning on adding?

@mikronac.ns You should check out my Linux 3.10 Kernel porting project. I added you as a collaborator
Here's the development thread
http://forum.xda-developers.com/htc-one-s/development/kernel-t3003992#post58205030

javelinanddart said:
@mikronac.ns You should check out my Linux 3.10 Kernel porting project. I added you as a collaborator
Here's the development thread
http://forum.xda-developers.com/htc-one-s/development/kernel-t3003992#post58205030
Click to expand...
Click to collapse
Thanks man... I will take a look these days, maybe even tomorrow...

mikronac.ns said:
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Spirit2 Requires the Radio Iris and Radio Iris Transport Drivers in the Kernel. @rmbq and @AKToronto included that a long time ago. In Bubba/Void the Voltages are lowered further than IceCode so it randomly rebooted. About the Governors, IDK why that's happening for you, that's really strange.

[MOD] [A11-A12/A13, Magisk 23+] PK's Tuning Script v16/v17 [2022-05-26]

A11 & A11 - use v16
A13 - use v16
Hey Coral / Flame Gang!
First off, I'm glad to be here. I just came from Pixel 2 XL after my phone died from hardware issues and I needed to upgrade!
Anyway, here's a script that I put together for my own use, but still develop occasionally; tuned especially for our Coral / Flame devices.
Enjoy!
The Back-Story:
I helped some good guys out with developing the awesome Franco.Kernel tuning parameters "back in the day" (Franco's Dev Team - you can look us up, the great osm0sis still hosts the original file set - but they won't even run on Android Pie or later). What is still applicable to Android 12 is in this file; trimmed and consolidated into a single script, along with some other goodies I've come across since.
Philosophy:
- I don't write untested BS or questionable crap in my scripts. If a given tweak doesn't show an objective improvement in benchmarks or battery life or a subjective improvement in performance that can be turned on or off by running or not running the script in a blind test - it doesn't get added.
- If I do not believe a given tweak is safe to run on everyone's daily driver device, I also won't include it my script, regardless of the benefit.
- This script is biased toward increasing performance - but it takes advantage of battery saving opportunities that don't affect performance.
Notes:
- This script is lean and mean, but it's not rocket science.
- I didn't invent anything here. Feel free to use it (or not), distribute, alter, whatever; to your satisfaction, giving credit for redistribution only to "Franco's Dev Team", and maybe me if you're feeling generous.
- I have verified it works well on my personal Pixel 4 XL, and is compatible with all Android versions, Kernels, and Magisk versions applicable to the device.
- It won't make your phone run any worse, and it should make it feel a bit "snappier", but YMMV.
- Most benchmark scores improve marginally (1% - 4%) on my device with stock or EX kernel. Again, YMMV.
- I do not plan to do heavy maintenance on this, but I will keep it up to date so it at least safely runs on the Pixel 4 / 4 XL as long as I own one. I will post updates with a minimal change log (it's a script, you can read it!). If I stumble across something that helps the community, I'll share it!
Disclaimer:
I can't see how this could possibly cause irreparable harm to any Android device on which it is run.
However, I suppose untested configurations may (rarely) have slow-downs, reboots, or other effects.
REGARDLESS, it is offered as-is with no warranty, and you choose to run this at your own risk.
If you do encounter issues, let me know and stop using the script. I may ask you for further help with debugging.
Requirements:
Root
BusyBox installation (I recommend the Magisk module by osm0sis)
Knowledge of how to execute a linux script and/or where to place it and allow permissions to run on boot
Usage:
Download the linked file to your device
Copy it to /data/adb/service.d
Ensure permissions are correct (0755)
Reboot and wait a three minutes
NOTE: The script will generate a text file called "pksp4_script_result" in the base of your "external storage" directory (/storage/emulated/0). This file will state either "Success!" or "Failure..." indicating if the script completed at the last execution attempt (it will over-write each time the script is run - check the date/time stamp on the file properties) .
Credits:
Franco's Dev Team, esp. osm0sis
Others as noted in the script file header
94pksp4v16.sh
Shared with Dropbox
www.dropbox.com
94pksp4v17.sh
Shared with Dropbox
www.dropbox.com

Change Log
V17 (use for A13)
- Audited script against A13 to ensure compatibility
- Script timing edits to support successful execution on A13 with Magisk 24 (especially ZRAM)
V16 (use for A11 and A12):
Fixed V15!
- Delayed and slowed ZRAM change to enhance the reliability of it "taking" on each boot
- Made Adrenoboost and power-efficient work queues contingent on those modules actually existing in the user's kernel
- (Did the same with the wakelock blocker while I was at it)
- Fixed a script typo that was the likely root-cause of V15 not running to completion or outputting "failure" for some users.
V15:
Enabled power-efficient work queues by default (most kernels have this functionality built in)
Enabled GPU Adrenoboost module by default, set to low boost (many kernels have this available, on/low seems preferred for a slight / smooth gaming boost without battery life detriment)
Changed vm.vfs_cache_pressure to 50 (was 200, wrong-direction from 100, I now believe after more testing)
Changed vm.dirty_ratio to 10 (from 20; avoids latency when having to write-out data to disk asynchronously by halving the amount of data needing to be written; this could reduce occasional "hang-up's" you may have experienced on this device regardless of kernel or mod - including stock!)
V14:
Increased ZRAM capacity by 50% to 3 GB
Turned off TCP timestamps to reduce overhead
Adjusted VM settings for having more memory
Added a couple minor VM tweaks
Added a minor kernel scheduler tweak
Minor code clean-up and re-ordering
V12:
Small core schedutil up/down rate limit tweaks, making small cores more responsive to increasing frequency and maintaining higher frequencies a bit longer. This should keep more load on small cores / reduce offloading to big cores unless big core utilization is truly necessary. I noted a little less latency and a little better battery life in my testing.
V11:
REMOVED.
V10:
Welcome to 2021.
Minor update - now bbr2>bbr>westwood (depends on what your kernel offers) for TCP congestion control algorithm. As an aside, I reconfirmed txquelen of 512 is still optimal for modern wifi and lte networks.
V9:
Happy holidays!
Added some TCP and kernel cfs tweaks that reduce device latency.
V8:
Stable, slightly improved Android 11 release.
Minor CFQ tunable tweaks that very slightly improved IO in benchmark testing.
Now blocks a single wakelock: qcom_rx_wakelock (if your personal philosophy is to never block any wakelocks, feel free to comment that line out in the script).
Changed TCP congestion avoidance algorithm to BBR2 (if available in kernel) - else, Westwood; based on network speed testing (BBR2 > Westwood > BBR).
V7:
Removed mount tweaks - they no longer do anything useful
Increased DBR slightly
Modified write-out file to not list time/date (for some reason it was being written twice on R). Just look at the file properties in your file manager to see when it was last written, if needed.
V6 is deprecated: Use V7 for R, V5 for Q
V6:
- Updated for Android 11 B1, verified to run without outputting any errors and is 100% stable.
- Removed one schedutil tweak that is no longer available on A11.
- Reverted kernel entropy settings to stock; tweaked settings were no longer increasing entropy pool.
- Users on A10 may use v6 without any issues, but v5 will still provide very slightly better performance on A10.
V5:
- A minor kernel overhead reduction from scheduler statistics
- Force CFQ as scheduler (just in case non-stock kernel isn't already set that way)
- Two CFQ tweaks, one that eliminated backward seeking penalty (makes no sense on non-rotational storage) and one that my testing showed sped up throughput and in theory should also reduce latency (so a true win-win!).
V4:
- Reverted foreground app schedtune boost, swappiness, vfs_cache_pressure, and dirty_ratio to stock
- Reverted IO scheduler to CFQ
- Removed wakelock blocking - verified no / minimal effect on deep sleep (I got 0.12%/hr idle drain overnight)
(for all of the above, thanks to @Freak07 for the advice / education!)
- Re-verified tx_queue_len (512) and tcp_congestion_control (westwood+) are optimized for WiFi and LTE networks
V3:
- Remove fstrim commands for /data and /cache since device is F2FS and fstrim doesn't apply (thanks to @woundman for pointing this out to me)
- Changed to Deadline scheduler with Franco Dev Team tunables - I just verified still benchmarks better after all these years
- If your kernel does not have Deadline available (e.g. stock kernel), the script will still keep you on Noop, as before.
V2:
- Reduce schedutil downrate limit to increase battery life.
- Block some safe wakelocks to increase battery life.
- Oh yeah, and a magic trick to turn off vm dirty write back timer (it still happens, just memory based and not every 5 seconds), to also increase battery life.
V1:
- Initial Pixel-4/XL release.

ooh interesting! would this play nice with the blackened mod found in this forum?

pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:

I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk

Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out. ?

I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.

Welcome brother... Nice to see another Taimen dev jump into the pool here!

I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks

Running great on fsociety!)

Stock ROM only? Or will it work in pixeldust too.

pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
It should. My script runs after BlakenedMod, so you'll get most of xFirefly93's battery savings, with a little bit of the PK snappiness.
xFirefly93 said:
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:
Click to expand...
Click to collapse
See above. Should be fine to run both... might even be best for some users! Let us know if it doesn't work!
MarcoG: said:
I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk
Click to expand...
Click to collapse
Glad to hear it!
Curiousn00b said:
Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out.
Click to expand...
Click to collapse
Thanks. Hope you like it!
2WildFirE said:
I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.
Click to expand...
Click to collapse
Glad to hear it - it should...
CyberpodS2 said:
Welcome brother... Nice to see another Taimen dev jump into the pool here!
Click to expand...
Click to collapse
Thanks! Great to see you again, too. Athouth, technically, I'm not a Dev
bl4dy_pt said:
I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks
Click to expand...
Click to collapse
Probably won't help much, but I'm working on some improvements for V2 (probably tomorrow or the day after!)
FlatOutRU said:
Running great on fsociety!)
Click to expand...
Click to collapse
Thanks for letting me know!
chopt51 said:
Stock ROM only? Or will it work in pixeldust too.
Click to expand...
Click to collapse
Any ROM!

New Version - V2
A little Sunday night treat!
V2 available in OP, change log in 2nd post.
Better battery life as I tune this in for Pixel 4/XL...

Any testing with kirisakura's kernel? You said not to mix things

I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.

tlxxxsracer said:
Any testing with kirisakura's kernel? You said not to mix things
Click to expand...
Click to collapse
It should work on any kernel... I've used on on stock and EX on Pixel 4, but I used it on kirisakura on my previous Pixel 2 XL device. If there are any issues, let me know.
woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
Thanks for the heads-up. Running the fstrim command doesn't return any errors, so the script is "safe" to use, but if it's not actually doing anything on the device, I'll remove it in a future release.

woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..

xFirefly93 said:
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..
Click to expand...
Click to collapse
Looks like you're right.
That said, I stopped trimming /System to be safe once Android went SAR, and /Cache is sym-linked to another partition anyway. So, I don't think the commands are actually doing anything anymore - at least not anything useful since /cache isn't really used for much on newer Android versions.
I'll be removing the fstrim commands starting with the next version. In the meantime, it's not really hurting anything.

Thanks for the mod. How can one confirm if this is actually running?

sharpz811 said:
Thanks for the mod. How can one confirm if this is actually running?
Click to expand...
Click to collapse
Look for the log as in the pic. Then view it with your text viewer. It should say script successful :good: