Related
Sorry for disappearing guys, I wasn't in the mood for posting or working on the kernel: unfortunately it looks like I bricked my phone.
I couldn't believe it myself but as soon as I restarted it phone after CWM-flashing my usual JPO rom, going back from official JPU+803.pit, the screen went black and never came up again, no matter the key combination. No signs of life besides warming up slightly after pressing power or connecting the USB cable. No luck with a JIG cable aswell, tried all the way from 290K to 315K Ohm and nothing happens... I guess there's nothing I can do.
The problem is, I came back to Europe last month and official Samsung centers around here are refusing to offer repair services on US phones because of some kind of freak policy they have, even if I pay myself.
Update Dec 13:
I have no words to explain how thankful I am: PAulyhoffman offered to donate a spare phone he had, and promptly shipped it on the same day.
A special mention goes to Patrick Richter, Pauly's father in law, who just passed away on Saturday: a most generous man in honor of whom he would like to dedicate the donation.
I've already covered the shipping fee myself but customs will add a variable amount in taxes (most definitely 20% of original value as they usually do, although the specified value is just $100).
Hoping customs won't hold the package over the holidays, untested version versions will have to do for now.
HUGE thanks go to every single one who offered help, I really am moved by the affection demonstrated by this wonderful community.
Click to expand...
Click to collapse
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels, including OC/UV support, 340Mb RAM and compiling optimizations.
Being based on the i9000 JPM source, it comes with every issue xcaliburinhand's kernel might have.
As I have absolutely no kernel programming knowledge, all credit goes to the respective coders: I've merely copied, pasted and compiled things, so I won't be able to offer much additional support or modify any of the function unless they provide source.
THIS IS A FROYO KERNEL, USE ONLY WITH A 2.2 ROM, PREFERABLY AN I9000 ONE
DO NOT USE SETCPU
Features:
- Sztupy's Ultimate Lag Fix V. pre-0.4https://github.com/sztupy
Multiple configurable Lagfix options:
Ext4 No-Journal DATA: /data converted to Ext4 with no journaling, everything else stays RFS
Ext4 No-Journal ALL: /data, /cache and /dbdata converted to Ext4 with no journaling
Ext4 DATA: /data converted to Ext4, everything else stays RFS
Ext4 ALL: /data, /cache and /dbdata converted to Ext4
Ext2 DATA: /data converted to Ext2, everything else stays RFS
Ext2 ALL: /data, /cache and /dbdata converted to Ext2
Advanced options: lets you specifically configure each partition and eventually add an Ext2 loop on top of them
Ext3/4 mount options: enables writeback journaling mode
(Using BIND_DATA_TO_DBDATA you might run out of space with many apps installed)
Suggested configuration (Ext4 ALL):
DATA_FS=ext4
CACHE_FS=ext4
DBDATA_FS=ext4
DATA_LOOP=false
CACHE_LOOP=false
DBDATA_LOOP=false
BIND_DATA_TO_DBDATA=false
Use FAST mount opts
You will get a "Configuration has changed" recovery screen at the first reboot after setting lagfix options, it's perfectly normal. If you wish to keep your current data, select the first option and wait (a separate backup is recommended).
- Modded CWM integrated
- CWM pre-installed (no more install from update.zip)
- reboot to 2e recovery
- reboot to download mode
- tweaking options
- root from recovery
- configure lagfix
- raspdeep's OC/UVhttp://forum.xda-developers.com/showthread.php?t=822027
If you do not want to mess with commands, use Xan's Voltage Settings app
- do note that you're subtracting voltage from the default setting, which varies with frequency:
Code:
1600MHz CPU 200MHz GPU 1400mV
1552MHz CPU 194MHz GPU 1375mV
1488MHz CPU 186MHz GPU 1350mV
1440MHz CPU 205MHz GPU 1325mV
1400MHz CPU 200MHz GPU 1300mV
1344MHz CPU 192MHz GPU 1300mV
1288MHz CPU 184MHz GPU 1300mV
1200MHz CPU 200MHz GPU 1300mV
1000MHz CPU 200MHz GPU 1275mV
800MHz CPU 200MHz GPU 1200mV
400MHz CPU 200MHz GPU 1050mV
200MHz CPU 200MHz GPU 950mV
100MHz CPU 100MHz GPU 950mV
the lastest Voltage Settings version includes voltage calculation
- 345Mb available RAM with 720p and JPU support
And improved minfree memory management
- Hardcore's SpeedModhttp://forum.xda-developers.com/showthread.php?t=822756
- jhash3
- Kernel HZ
- startup tweak scripts (available from cwm)
- ext4 kernel patches from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
- compiling optimizations:
(thanks to laststufo)
-O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -fno-gcse -fprefetch-loop-arrays --param l2-cache-size=512 --param l1-cache-size=64 --param simultaneous-prefetches=6 --param prefetch-latency=400 --param l1-cache-line-size=64
- config optimizations: (XT variant only)
CONFIG_UACCESS_WITH_MEMCPY=y
CONFIG_KSM=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
additional config settings found in other kernels are pointless or even counterproductive for performance/stability
- BFQ I/O schedulerhttp://lwn.net/Articles/306641/
Set as default, you may change it using Xan's Voltage Settings app
- supercurio's Voodoo Color&Sharpnesshttps://github.com/project-voodoo
- HSUPA support (with i9000 modems)
Enable WCDMA 850Mhz by dialing *#2263# (COMBI BANDS -> choose WCDMA 850)
- neldar's v2.2 BackLight Notifications supporthttps://github.com/neldar/backlightnotification
Configure with BacklightNotification settings app
To enable BLN it is necessary to flash a CWM zip or enable BLN in CWM from ULK advanced options
- Boot animations support
http://forum.xda-developers.com/showthread.php?t=819686
http://forum.xda-developers.com/showthread.php?t=822955
http://forum.xda-developers.com/showthread.php?t=623960
Once again, none of it comes from me and all credit goes to the original developers, especially xcaliburinhand, raspdeep and hardcore
Nevertheless, if you're feeling particularly generous and have already provided for the developers, I'll gladly accept a token of gratitude (after all, being so ignorant I did have to invest quite a bit of time into it).
Everything comes at your own risk, I offer no support at all.
Thank you aleadam, ReedX50v, junktzu, shaolin95, Shane, krl66, Smokestack76, Henry, Xstop, lpsi200, Arffer, newter55, Lertets, txRangerXDA, id10terrordfw and Bedwa for your donations.
Code:
- v1.5.6
fixed boot-up and CWM instability
updated modules from JPX kernel
new frequency table
full compatibility with Voltage Control 3 (lowering frequency with it seems to cause freezes)
removed update_frequency, making changes to the freq table immediately applies them
- v1.4.7
fixed boot animation issues
fixed init.d script execution
fixed CIFS support
- v1.5.5
lowered default freq to 1000MHz
updated ram disk to late 1.4.x versions
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
- v1.4.6
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
Changelog:
- v1.4.5
Frequencies/battery fix
- v1.4.4
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
gained an additional MB of RAM thanks to kernel size optimization
implemented Xcaliburinhand's wired headset fix
optimized RAM utilization (minfree tweaks)
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations, GPS tweaks, CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
HZ=500, PREEMPT_VOLUNTARY
JPU variant with modules and mem config extracted from samsung's JPU kernel: DO NOT USE IT ON FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG JPU AND ONLY THEN FLASH THIS KERNEL
v1.5.4
initial boot and recovery frequency lowered from 1200MHz to 800MHz
reduced voltage change delay
frequency jumps set up more like 1.4 in order to improve performance
v1.5.3
/system mounts as RO
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
corrected frequencies script, should now work on every ROM
only available as a CWM update.zip to make sure everyone has working init scripts
increased default voltages for 1456-1464MHz to 1325mV, 1504-1544MHz to 1375mV and 1600MHz to 1400mV, regulate your UV settings BEFORE upgrading
gained an additional MB of RAM thanks to kernel size optimization
v1.5.2
DELETE USER GENERATED SCRIPTS IN /system/etc/init.d/ BEFORE UPGRADING
(remember it's necessary to unlock higher frequencies from both freq_table and Xan's app)
implemented Xcaliburinhand's wired headset fix
mount /system R/W - could be dangerous, but solves script creation issues
optimized frequency jumps for better battery life
optimized RAM utilization (minfree tweaks)
workaround for the highest frequency step being sometimes briefly used during bootup and recovery operation
effectively set 1200MHz as the default frequency
corrected wrong display of highest frequency in Quadrant
added frequencies scheduler script in the CWM zip package with a visual aid
reorganized performance levels with a few additions
- v1.5.1
skipped, integrated in 1.5.2
- v1.5
updated raspdeep's OC/UV to v300
multiple performance levels:
100
200
400
800
1000
1200
1360 (GPU downclocked, don't worry performance improves anyway)
1400
1440 (GPU slightly overclocked)
1460 (GPU downclocked)
Default clock at 1200MHz, additional frequencies can be enabled by editing /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
in order to update the states table it's necessary to edit to 1 /sys/devices/system/cpu/cpu0/cpufreq/update_states (echo from terminal or by manually editing the file, just like the states table)
added compatibility with Xan's voltage app v2.0 (please update, v1.9x wouldn't work correctly)
reduced 14xxMHz default voltage to 1.3v
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations and CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
- v1.4.3
fixed 2e recovery, now completely functional
added 1350Mhz, 1400MHz and 1450MHz variants, only available as ODIN packages. The latter two have a default voltage of 1350mV. Keep using Xan's Voltage App v1.98b's 1200MHz setting to undervolt, higher frequencies replace the 1200MHz step, bear in mind the app doesn't show the updated frequency/voltage. Remember to reset said setting before upgrading and please realize how 14xxMHz will only run on few lucky devices
from now on there won't be a CWM version for 1350MHz+ and XT variants as well as a release integrating the modem, just install it on its own if necessary
- v1.4.2
implemented Tiny RCU
re-enabled Samsung's bootanimation when there's no bootanimation.zip
re-added -noatime optimization script
XT variant: 1280MHz, config optimizations: HZ=500, PREEMPT_VOLUNTARY, UACCESS_WITH_MEMCPY, KSM (possibly unstable, slightly higher performance and battery drain, might be necessary to lower UV)
- v1.4.1
fixed BLN (flashing as update.zip or re-enabling it from CWM might be necessary)
- v1.4
raspdeep's OCUV updated to v217
implemented fastscaling for 100-400MHz frequencies
added 1280MHz variant (UV setting for 1200MHz applies to 1280MHz, so reset it)
ULF updated to pre-0.4, modified to support bootanimations
fixed potential /system corruption
integrated JK3 modem in CWM flash package
kernel version updated to reflect frequency variant (#140-1280 / #140-1200)
BLN has issues
- v1.3.5
removed config optimizations
removed -noatime remount script
(should provide stability for those experiencing hangups/reboots/charging issues)
- v1.2.6
removed config optimizations (should provide stability for those experiencing hangups/reboots/charging issues)
HZ=300
- v1.3.4
rebuilt from scratch
even more stability fixes
build # updated according to version (#134->v1.3.4)
- v1.2.5
rebuilt from scratch
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
fixed script execution
kernel HZ back to default
build # updated according to version (#125->v1.2.5)
- v1.3.3
fixed screen lock issue
kernel HZ lowered to 300
more stability fixes
supposedly fixed charging issues (oneclick to JF6, reset battery stats and masterclear)
- v1.3.2
stability fixes
- v1.3.1
included ext4 patches from [url]http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/[/url]
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
- v1.3
Corrected a small bug that was preventing scripts from running
updated raspdeep's OC/UV to v2.1
update [url=http://forum.xda-developers.com/showthread.php?t=829731]Xan's app[/url] to undervolt
- v1.2.1
hopefully fixed script execution on Captivate ROMs aswell
fixed CWM option for enabling BLN
fixed 500hz setting
enabled CONFIG_UACCESS_WITH_MEMCPY and CONFIG_PREEMPT_VOLUNTARY as they apparently make no difference in battery use
- v1.2
increased available RAM to 343Mb
updated BLN to v2.2
- v1.1.1
enabled init.d script execution on boot (Xan's app voltage settings are now being kept)
- v1.1
added BFQ I/O scheduler
updated Voodoo color&sharpness
BLN reverted to v2.0, now working (flashing from an update.zip is required to install the Library)
- v1.0.1
fixed JFS filesystem support, added bootanimations, BLN still not working (no clue why not, waiting for xcaliburinhand's upcoming update)
- v1.0
initial release
RESET ALL UV SETTINGS (DELETE INIT.D SCRIPTS) BEFORE UPGRADING TO HIGHER VERSIONS
IF YOU'RE HAVING SLEEP DEATH ISSUES, REVISE UV SETTINGS
Modules and mem config extracted from samsung's JPU kernel: DO NOT USE THIS KERNEL ON JPU FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG STOCK AND ONLY THEN FLASH THIS KERNEL
The XT variant is slightly faster but can cause instability (which might require higher voltage) and charging death.
Voltage Control 3 supports enabling higher frequencies from the freq table, but doesn't yet let you disable selective ones.
To disable a certain frequency its corresponding value in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table has to be set to '0'.
Changing update_states is no longer necessary. That file can either be manually edited or modified through an 'echo' command, which is much more convenient if you're in front of a PC and able to use ADB.
It's a volatile RAM file, which means changes made to it won't stick through reboots; I've included a script that reapplyies settings on boot in the CWM package (also attached to this post).
Let's say you wish to overclock to 1400MHz and disable 1288-1344:
1344MHz corresponds to the 6th value, 1288 to the 7th:
Code:
#!/system/bin/sh
#SET OC - below are GHz decimals (i.e. 1.60GHz, 1.55GHz, 1.50GHz and so on)
#60 55 48 44 40 34 28 20 00 .8 .4 .2 .1
[color=red]#[/color]echo 0 0 0 0 1 [color=blue]0[/color] [color=blue]0[/color] 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
REMEMBER TO REMOVE # FROM THE LAST LINE
jk3_modem_update.zip
SetiroN_v1.4.7xt_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7xt_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7xt_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7xt_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7xt_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7xt_1200.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1200.tar.7z [email protected] frequency - 200MHz GPU
setiron_v1.5.6.tar.7z
setiron_v1.5.6_cwmupdate.zip
setiron_v1.5.6xt.tar.7z
setiron_v1.5.6xt_cwmupdate.zip
Voltage Control 3 alpha3
FINALLY! Going back to 2.2 so i can try this out. Can't wait for the link.
Sent from my Cappy using mental telepathy, *****ezz.
SetiroN said:
- neldar's v2.2 BackLight Notifications support
coming in the next release
Click to expand...
Click to collapse
Awwww that's a deal breaker for me, need bln badly. But yes finally, sztupy ulf on the cappy.
BLN now included, untested.
Awesome. I've been trying to figure out the how to do all this as well. I edited the code this morning at work and I just thought I'd check XDA while CodeSourcery finished installing...and what do I see?
I'll be flashing this immediately. FWIW, I've actually been running raspdeep's OC/UV 2.0 since Monday. I have it set at -100UVLF, -75UVHF, and I've had absolutely no problems with it at all, but it seems to be a YMMV situation. I don't think all processors can handle the UV. Even with (I think) unhelpful's, JAC's, and kingklick's kernels for the Galaxy S, phones handle the UV fine, some don't. Battery life is amazing with this though.
Also, I've had problems with screen off settings with setCPU. You probably don't want to use them at all.
SetiroN said:
BLN now included, untested.
Click to expand...
Click to collapse
that's some fast support...
Yes please. Link?
DOAlaboratories said:
that's some fast support...
Click to expand...
Click to collapse
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm
so has anyone run this yet? it seems pretty alpha and my phone just went into download mode to test it
By the way everyone - the UV is still what I think raspdeep considers alpha. You will probably want to stress your system a bit to ensure it can handle it. I found that with -100UVLF/-75UVHF flash video was a little bit choppier than with the settings at -75UVLF/-50UVHF.
That said, it has been steady for me over the last couple days, no problems at all with it. I can watch flash video and my CPU temps still stay under 100.
Also, link to xan's UV GUI seems to be missing - so here is another one.
And having alogcat installed and knowing how to use it would probably be the best practice if you want to help raspdeep make this even better.
Athailias said:
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm
Click to expand...
Click to collapse
Just get in download mode and flash it over
SetiroN said:
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels
Click to expand...
Click to collapse
Which version of reorient is this based on?
Thanks!
Since I see the compass patch works, it is at least version 2.1.1...
watch out, i think this may have master cleared me...
simething did at least.
no worries though, i have a whole SDCARD backup, so it's all good
This is freaking sweet. I am undoing voodoo at the moment and then will flash and give it a try. I am on the memory version of reorient at the moment so I will post back when results
it keeps booting intoa recovery loop on me after applying a lagfix
DOAlaboratories said:
it keeps booting intoa recovery loop on me after applying a lagfix
Click to expand...
Click to collapse
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.
BLN doesn't seem to be working. Yes I did enable it in the custom recovery menu, and yes I'm using a version of Mms.apk that supports "led notifications."
Has anyone tried with cogs new b2.3 rom yet? How is the battery life?
glitterballs said:
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.
Click to expand...
Click to collapse
JFS overkill was what did it me and obsessing over having the best ****.
i'll try RFS overkill and see if that works. also, after i got it to boot back up, it wouldn't install any apps
Can I flash this over Tayutama's Tom using ODIN? What slot do I put the file in?
Improve your battery life tenfold by PureMotive
tested and working at: SGS, Xperia Play, HTC Inc S, the battery life has increased significantly
Original link: http://forum.xda-developers.com/showthread.php?t=1621808http://forum.xda-developers.com/showthread.php?t=1621808
PureMotive said:
Okay guys, I just thought I'd give you my mod for achieving good-great battery life. This is the mod I use in Anthem™ which has given me 50+ hours on a single charge. Feel free to include it in your own ROM or whatever. Please give credit or thanks or both
First: Here is a flashable .zip of the mod that may or may not work with your ROM. I'd still advise doing it manually.
Sysctl.conf - Outdated as of 4/29/2012
Step 1
Open up your ROM.zip (or whatever it's called) in 7zip (Windows) or Betterzip (OSX) and locate
sysctl.conf in /system/etc
If it's not in this directory, create it.
Step 2
In your sysctl.conf file, paste the following code and save it.
Code:
#sysctl.conf file
fs.nr_open=1053696;
fs.inotify.max_queued_events=32000;
fs.inotify.max_user_instances=256;
fs.inotify.max_user_watches=10240;
fs.lease-break-time=10;
fs.file-max=165164;
kernel.threads-max=525810;
kernel.random.write_wakeup_threshold=256;
kernel.random.read_wakeup_threshold=128;
kernel.panic=5;
kernel.sched_compat_yield=1;
kernel.panic=0;
kernel.panic_on_oops=1;
kernel.msgmni=2048;
kernel.msgmax=64000;
kernel.shmmni=4096;
kernel.shmall=2097152;
kernel.shmmax=268435456;
kernel.sem='500 512000 64 2048';
kernel.sched_features=24189;
kernel.hung_task_timeout_secs=30;
kernel.sched_latency_ns=18000000;
kernel.sched_min_granularity_ns=1500000;
kernel.sched_wakeup_granularity_ns=3000000;
kernel.sched_shares_ratelimit=256000;
kernel.sched_child_runs_first=0;
fs.lease-break-time=10;
fs.file-max=65536;
net.core.wmem_max=524288;
net.core.rmem_max=524288;
net.core.rmem_default=262144;
net.core.wmem_default=262144;
net.core.optmem_max=20480;
net.unix.max_dgram_qlen=50;
net.ipv4.tcp_keepalive_time=900;
net.ipv4.tcp_keepalive_probes=5;
net.ipv4.tcp_keepalive_intvl=156;
net.ipv4.tcp_timestamps=0;
net.ipv4.tcp_sack=1;
net.ipv4.tcp_fack=1;
net.ipv4.tcp_window_scaling=1;
net.ipv4.tcp_tw_recycle=1;
net.ipv4.tcp_tw_reuse=1;
net.ipv4.tcp_congestion_control=cubic;
net.ipv4.tcp_syncookies=1;
net.ipv4.conf.all.rp_filter=1;
net.ipv4.conf.default.rp_filter=1;
net.ipv4.tcp_synack_retries=2;
net.ipv4.tcp_syn_retries=2;
net.ipv4.tcp_max_syn_backlog=1024;
net.ipv4.tcp_max_tw_buckets=16384;
net.ipv4.icmp_echo_ignore_all=1;
net.ipv4.icmp_ignore_bogus_error_responses=1;
net.ipv4.tcp_no_metrics_save=1;
net.ipv4.tcp_fin_timeout=15;
net.ipv4.tcp_keepalive_intvl=30;
net.ipv4.tcp_keepalive_probes=5;
net.ipv4.tcp_keepalive_time=1800;
net.ipv4.ip_forward=0;
net.ipv4.conf.default.accept_source_route=0 ;
net.ipv4.conf.all.accept_source_route=0;
net.ipv4.conf.all.accept_redirects=0;
net.ipv4.conf.default.accept_redirects=0;
net.ipv4.conf.all.secure_redirects=0;
net.ipv4.conf.default.secure_redirects=0;
net.ipv4.udp_rmem_min=6144;
net.ipv4.udp_wmem_min=6144;
net.ipv4.tcp_rfc1337=1;
net.ipv4.ip_no_pmtu_disc=0;
net.ipv4.tcp_ecn=0;
net.ipv4.route.flush=1;
net.ipv4.tcp_rmem='6144 87380 524288';
net.ipv4.tcp_wmem='6144 87380 524288';
net.ipv6.conf.default.use_tempaddr=2;
net.ipv6.conf.all.use_tempaddr=2;
net.ipv6.conf.all.temp_prefered_lft=3600;
net.ipv6.conf.default.temp_prefered_lft=3600;
vm.dirty_ratio=90;
vm.dirty_background_ratio=80;
vm.oom_kill_allocating_task=1;
vm.overcommit_memory=1;
vm.page-cluster=3;
vm.drop_caches=3;
vm.min_free_kbytes=4096;
vm.panic_on_oom=0;
vm.dirty_expire_centisecs=1000;
vm.dirty_writeback_centisecs=2000;
vm.oom_kill_allocating_task=0;
vm.vfs_cache_pressure=10;
vm.min_free_order_shift=4;
vm.laptop_mode=0;
vm.block_dump=0;
PureMotive said:
I updated the OP with a new code (Thanks to Tiny). I just removed the semicolons. Use this version if the other does not work for you.
Click to expand...
Click to collapse
If the above code does not work for you, try this one. It has the semi-colons removed. Thanks Tiny
Code:
#sysctl.conf file
fs.nr_open=1053696
fs.inotify.max_queued_events=32000
fs.inotify.max_user_instances=256
fs.inotify.max_user_watches=10240
fs.lease-break-time=10
fs.file-max=165164
kernel.threads-max=525810
kernel.random.write_wakeup_threshold=256
kernel.random.read_wakeup_threshold=128
kernel.panic=5
kernel.sched_compat_yield=1
kernel.panic=0
kernel.panic_on_oops=1
kernel.msgmni=2048
kernel.msgmax=64000
kernel.shmmni=4096
kernel.shmall=2097152
kernel.shmmax=268435456
kernel.sem='500 512000 64 2048'
kernel.sched_features=24189
kernel.hung_task_timeout_secs=30
kernel.sched_latency_ns=18000000
kernel.sched_min_granularity_ns=1500000
kernel.sched_wakeup_granularity_ns=3000000
kernel.sched_shares_ratelimit=256000
kernel.sched_child_runs_first=0
fs.lease-break-time=10
fs.file-max=65536
net.core.wmem_max=524288
net.core.rmem_max=524288
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.optmem_max=20480
net.unix.max_dgram_qlen=50
net.ipv4.tcp_keepalive_time=900
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_intvl=156
net.ipv4.tcp_timestamps=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_fack=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_tw_recycle=1
net.ipv4.tcp_tw_reuse=1
net.ipv4.tcp_congestion_control=cubic
net.ipv4.tcp_syncookies=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.conf.default.rp_filter=1
net.ipv4.tcp_synack_retries=2
net.ipv4.tcp_syn_retries=2
net.ipv4.tcp_max_syn_backlog=1024
net.ipv4.tcp_max_tw_buckets=16384
net.ipv4.icmp_echo_ignore_all=1
net.ipv4.icmp_ignore_bogus_error_responses=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_fin_timeout=15
net.ipv4.tcp_keepalive_intvl=30
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_time=1800
net.ipv4.ip_forward=0
net.ipv4.conf.default.accept_source_route=0
net.ipv4.conf.all.accept_source_route=0
net.ipv4.conf.all.accept_redirects=0
net.ipv4.conf.default.accept_redirects=0
net.ipv4.conf.all.secure_redirects=0
net.ipv4.conf.default.secure_redirects=0
net.ipv4.udp_rmem_min=6144
net.ipv4.udp_wmem_min=6144
net.ipv4.tcp_rfc1337=1
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.tcp_ecn=0
net.ipv4.route.flush=1
net.ipv4.tcp_rmem='6144 87380 524288'
net.ipv4.tcp_wmem='6144 87380 524288'
net.ipv6.conf.default.use_tempaddr=2
net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.all.temp_prefered_lft=3600
net.ipv6.conf.default.temp_prefered_lft=3600
vm.dirty_ratio=90
vm.dirty_background_ratio=80
vm.oom_kill_allocating_task=1
vm.overcommit_memory=1
vm.page-cluster=3
vm.drop_caches=3
vm.min_free_kbytes=4096
vm.panic_on_oom=0
vm.dirty_expire_centisecs=1000
vm.dirty_writeback_centisecs=2000
vm.oom_kill_allocating_task=0
vm.vfs_cache_pressure=10
vm.min_free_order_shift=4
vm.laptop_mode=0
vm.block_dump=0
Step 3
Now we need to enable it. So, navigate to /system/etc/init.d and create a file with the following code:
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
# Load /sys/etc/sysctl.conf
sysctl -p
sysctl -p is what initializes the code.
Just FYI: You don't actually need these lines:
Code:
# grep sysctl /etc/init.d/*
Code:
# Load /sys/etc/sysctl.conf
So this would have just sufficed.
Code:
#!/system/bin/sh
sysctl -p
If the above code does not work for any reason, try this:
Code:
#!/system/bin/sh
sysctl -p /system/etc/
Name your file something like this 10sysctl
Save your file.
NOTE: Your ROM must support init.d. You can do this by using dsixda's android kitchen
Step 4
Save your ROM and install it via recovery
OR
you could just push the files into your current ROM and try them out.
Step 5
For operating the script enter the following code in terminal emulator
Code:
su
sysctl -p
is all that is really needed to run the script. So here are some more options:
If you think that init.d is being faulty, enter in terminal emulator
Code:
su
sysctl -p
and then
Code:
sysctl -a| grep vm
What this does is manually start up sysctl.conf and then verify it with the succeeding code.
OR
Ignore what
Code:
sysctl -a| grep vm
is outputting and just see if you experience better battery life (you should)
----------- For knowledge -----------
Credits to imoseyon for portions of the info
Ok, so what exactly is sysctl.conf?
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
min free kbytes (vm.min_free_kbytes)
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure)
Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
oom allocating task (vm.oom_kill_allocating_task)(enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.)
This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
block_dump (vm.block_dump)
This enables block I/O debugging when set to a nonzero value. If you want to find out which process caused the disk to spin up (see /proc/sys/vm/laptop_mode), you can gather information by setting the flag.
When this flag is set, Linux reports all disk read and write operations that take place, and all block dirtyings done to files. This makes it possible to debug why a disk needs to spin up, and to increase battery life even more. The output of block_dump is written to the kernel output, and it can be retrieved using "dmesg". When you use block_dump and your kernel logging level also includes kernel debugging messages, you probably want to turn off klogd, otherwise the output of block_dump will be logged, causing disk activity that is not normally there.
overcommit_memory (vm.overcommit_memory)
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
page-cluster (vm.page-cluster)
This controls the number of pages which are written to swap in a single attempt. The swap I/O size.
It is a logarithmic value - setting it to zero means "1 page", setting it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
The default value is three (eight pages at a time). There may be some small benefits in tuning this to a different value if your workload is swap-intensive.
panic_on_oom (vm.panic_on_oom)
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill().
Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
The default value is 0.
Panic is a system error that is detected by the kernel.
dirty_expire_centisecs (vm.dirty_expire_centisecs)
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs (vm.dirty_writeback_centisecs)
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
Click to expand...
Click to collapse
Woah.!!
Sent from my GT-S5830 using Tapatalk
Flashable ZIP
Tenfold huh? should give it a try..
EDIT (updated):
Heres a flashable zip to make things a little easier:
Instructions:
1. Reboot to CWM
2. Mount system
3. Flash
DOES IT WORK?
See for yourself
v2-04/30/2012 [without semi-colons of sysctl.conf (refer Step 2) & removed extra lines of 10sysctl (refer step 3)]
pure AWESOMENESS
Sent from my GT-I9100 using xda premium
Is it working. For ace?????
Sent from my GT-S5830 using Tapatalk 2
Anyone comfirm this working?
added to my future rom
Sure.. after 30min from the first post someone definitely will answer if it extends battery life
Let's see who'll be the first to notice that his bettery last longer
Thanks for sharing this
Is it compatible with CM9?
I installed this on my 2.3.6 based ROM and everything is smooth so far. I also ran the supercharger scripts and all 3 had no errors just in case anyone was wondering if they'd conflict with eachother.
/me Flashed,charging Batt ... ->Start
Testing ...edit with notes follows in 24h ...
Thx 4 sharing
(Edit) for me the battery jumps stopped,its more accurate...but i dont have more battery life.
Verstuurd va men ace via Tapatalk
Installed on 2.3.6 based ROM. Everything went smoothly installing. I ran the V6 turbocharger scripts and it didnt cause any errors to come up in case anyone was wondering.
Sent from my VS910 4G using xda premium
Just installed now, on CM9, Beta 8 by the GalaxyICS team.
Currently charging, and I will show a battery life screenie tomorrow and report on the performance
Downloaded, short term testing looks promising, played angry bird for 30mins, that use to drain like 10% battery, now it's only 6%. Not ten fold but still, improvement from just a file, i'll take that any day, this should come standard on all roms now
Does it works on Lewa rom?
Yes i think it was we need It appears to save battery ... Tomorrow i will do full test with full charge
ok installed 5 minutes back on Lk's I two Rom aka cyanogenmod. no problem but I notified a significant change in speed.. phone feels faster. battery backup dropped two percent in 3 minutes of edge usage. ll update this post after 5 hours.. those who want to install do it without fear its installing no bootloops no errors...
thanks for the share
---------- Post added at 08:01 AM ---------- Previous post was at 07:38 AM ----------
kohrangi said:
Does it works on Lewa rom?
Click to expand...
Click to collapse
Yes it works...
Mmm... testing... im at hospital for 2 days without my charger so... It will come handy if works.
Thanks!
Enviado desde el hospital usando Tapatalk con la mano derecha (soy surdo pero tengo suero)
A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.
AlterJack said:
A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.
Click to expand...
Click to collapse
Files sysctl.conf are the same. Original sysctl.conf contains one empty line at the end of file - that is all.
This kernel is based on teamhacksung's kernel for Jellybean
This kernel is meant be working on every Rom based on cm10
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me
Download link and changelog can be found here:
http://www.hellybean.com/jelly.html
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
Changelog:
changelog 02.08.2012:
- bug fix to bln, to prevent kernel panic in some situations (thx to thalamus)
- switched from deep_idle 2 to idle2 (also thx to thalamus)
- updated kernel to linux 3.0.38
- dockaudio sysfs for captivate and fascinate
IDLE2 can be enabled with the following command:
echo 0 > /sys/module/cpuidle/parameters/idle2_disabled
IDLE2 can be disabled with the following command:
echo 1 > /sys/module/cpuidle/parameters/idle2_disabled
Stats can be obtained from the standard cpuidle interface, which, for
IDLE2 is located at:
/sys/devices/system/cpu/cpu0/cpuidle/state*/time
where * = 1, 2, 3
Click to expand...
Click to collapse
changelog 27.07.2012:
- hack mfc driver, to give all available mem to an application, if the requested mem is more than the max. available (maybe useful later, does not change anything right now (afaik))
- fix execution of boot-patch.sh, disabled twice execution of init.d, enabled tv-out server for all devices (i9000 already had this)
- battery: fix charging display for car dock
- increase read-ahead on moviNAND
changelog 25.07.2012 part2:
- fixed cwm backup and restore for kernels without /datadata partition
changelog 25.07.2012:
- updated recovery (no "sdcard format"-bug anymore, external sd card is named correctly)
- vibrant: hopefully fixed froyo ril
- jellybean: galaxy s settings working now
changelog 22.07.2012:
- updated kernal base to linux 3.0.36
- updated "block" to linux 3.3
- readded fiops io scheduler (kept cfq this time)
- updated cwm recovery to 6.0.1.0 (please create a new nandroid, because of possible incompatibilities between old/new recovery)
- compiled with linaro toolchain (gcc 4.7.1) and O3 compiler flags
- made uksm scan less often (save cpu time and power)
- at first boot: only delte init.d scripts created by other kernels
- increased usb write performance
- lowered ram and display voltages a little bit
- fixed some bugs related to devil settings (they should stick now after reboot, if set by one of the devil apps)
- support for scripts in /system/etc/shutdown.d (thx to Efpophis)
all scripts placed at /data/local/shutdown.d or /system/etc/shutdown.d get executed at shutdown/reboot
you can use this, to play a shutdown sound for example.
by default 00shutdown gets created, which plays a music file, when it is placed at one of these folders/places
/system/media/audio/ui/shutdown.ogg
/data/media/audio/ui/shutdown.ogg
Click to expand...
Click to collapse
- disabled some debugging options
- audio (and for fascinate: camera fixes) by Efpophis+
- patch for improving batterie life by CML
- nfts read/write driver built in (for use with usb host mode)
- reverted refreshrate_mod and gpu_oc mod, as both weren't working
changelog 18.06.2012:
- some changes to load balancing
- added ultra ksm (metioned by zach thx for this my friend)
- readded fiops io scheduler (still experimental and could cause instablilities)
- using snappy compression for zram now (2 times faster, but only 2% less compression)
- added the possibility to change zram size (at /data/local/devil/zram_size, with valid values: 50, 75, 100 and 150 (all in mb))
- fixed the applying of user_min/max freq after reboot
- vibrant: fixed gps
- fascinate: fixed nandroid in cwm recovery
what is ksm? http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)
uksm is more optimized and also working for single core systems. using this should give much better ram usage, but at the cost of more cpu usage
############# most probably not working (yet)##############
i have added seperate gpu oc from jt1134's galaxy_tab (to switch between 200 and 250 mhz), but i did not get any improvements in antutu...further tests needed
echo 1 > /sys/kernel/pvr_oc/pvr_oc (for 250 mhz)
echo 0 > /sys/kernel/pvr_oc/pvr_oc (for 200 mhz), no reboot needed
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
######################################################
changelog 10.06.2012:
cwm recovery:
- fixed mounting of external sd card to pc
kernel:
- picked two commits from linux 3.0.32 (avoid a possible memory leak, small fix to ext4 driver)
fascinate:
- fixed wrong mount points
changelog 09.06.2012:
- updated Zram and Zcache from linux 3.3
- updated android binder driver from linux 3.3
- fixed restoring of backups within TWRP recovery
- added virtual buttons to cwm recovery (Attention: they still don't work!)
- call vol hack from tk glitch (take a look at init.d folder and edit the script to make changes to call vol hack)
- bigmem values get applied at first boot after power on (if there is a value at /data/local/devil/bigmem, 1 for 391 mb and 2 for 403 mb (the last one breaks 720p)
- prevent phantom key presses (from tk glitch)
changelog 24.05.2012:
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- no need for activating/deactivating of selective live_oc anymore --> just change target low and target high
- BLX back in
- fixes to devil idle to be more stable while in call
- 1,5 mb more ram (thanks to mialwe)
- added aroma filemanager to cwm recovery
- added fully working TWRP recovery optional to cwm recovery (to use TWRP, just create a file named "twrp" at /cache)
- added option to select ram config in kernel --> no need for flashing an other kernel to get more ram (thanks to stratosk)
- switched to new initramfs from stratosk and mialwe ( now there will be cmw zip and odin tar file of every kernel version)
- added possibility to use Zram instead of Swap
- no need for flashing/using special scripts to make swap/zram working anymore
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
changelog 01.05.2012:
- all changes from cm9 stock kernel (including mount points option)
- some fine tuning to deadline and sio
- Devil Idle: limiting bus/ram/gpu speed to 100 mhz for 100-800 mhz cpu freq, while screen off (automatic mode) or always (permanet), both modes automatically reduce the int voltages of the affected freq by 50 mV
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
- rest oc_value to 100 while screen off, and back when screen turns on (combined with devil idle automatic, can't be turn on/off without devil idle)
- added posibility for different voltages while screen off (also bundled with devil_idle, with default settings, stock arm voltages are applied, because of live_oc set to 100)
- added the possibility to set freq limits while screen off (min and max freq)
19.04.2012
- even better fix to selective live_oc (last one (in test kernel) generated some overhead)
- fixed sampling rate of ondemand and conservative (have ported mialwe's/stratosk's sleep multipliers)
- new tunables for ondemand and conservativ
sleep multiplier and tunables:
mialwe and stratosk had the great idea, to change the sampling rate of conservative and ondemand governor while display of. for this, he introduced the sleepmultiplier (in his case factor 3). this means, if you set sampling rate to 20000, it changes to 60000 while screen off, and back, when screen on.
for ondemand and conservative:
i have made this multipliers tunable. proper values are between 1 and 5, because one could want a higher multiplier while screen off, if sampling rate is very low while screen on (higher sampling rate means, less checking for work load --> better batterie, worse performance). with this tunables you get better batterie, without making the performance worse while screen on.
two other tunables: up_threshold_min_freq and responsiveness_freq
the first one is a very low threshold while on low freq (by default 40), to make the governor scale up faster, until the responsiveness_freq is reached.
the responsiveness_freq is set to 400000 (400 mhz) by default. while the freq is below this value, up_threshold is the same as up_threshold_min_freq, and freq jumps to responsiveness_freq, with skipping the freq between the actual one and the responsiveness_freq. (conservative governor does not jump up to this step)
responsiveness_freq can be set to values between 100000 and 1400000
up_threshold_min_freq can be set to the same values as the normal up_threshold.
not tunable: while screen off, up_threshold is set to 95, no matter your other settings, to save more batterie.
up_threshold_min_freq is disbaled by default for conservative governor
for lulzactive:
for this governor, i did similar things, but they are not tunable till now.
when screen off:
- inc_cpu_load is set to 90, and back to the original value, when screen turns on
- up_sample_time is set to 50000, and back to the original value, when screen turns on
- down_sample_time is set to 40000, and back to the original value, when screen turns on
other changes:
- fix to touchwake from ezekeel, and another fix from stratosk
- upstream fix to compass
- building for i9000B now, too (big thanks to F4k for the hints by pn )
- removed some typos from recovery
- removed some annoying "no's" and "yes" from recovery in misc menu
- fixed wifi mode switch (pm_fast is the one with better signal)
14.04.2012:
- new b versions (only stock ram) changend to 377 mb, VC version needs the 720p fix from my ftp server. cmc version already patched
13.04.2012:
- updated wifi driver
- added the possibility to switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
- user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel, so it should be ok ), default is off, to be safe
- fixed voodoo color kernels (these have the VC in their names)
10.04.2012:
- added vibrator intensity control (by mialwe), presets can be changend in recovery
- stock ram version now available (348 mb ram), XL (390 mb), XL_bm (402 mb)
- removed 1080 mhz freq for now
- small correction to touchwake
- small correction to selective live_oc (now the low freq really are not live_oc'ed)
05.04.2012:
- fixed bug in selective live_oc, which caused the target high not taking affect to the highest freq, if highest freq equals target high
- fixed another bug in selective live_oc, which could lead to gpu crashes due to overclocking the ram, but not the cpu freq (for low steps)
- added a switch to change between "normal" and selective live_oc
by changing the live_oc mode while using it, live_oc value is set back to 100, to prevent strange things
- added possibility to set max. freq for boot (in recovery). This freq is set until init.d is executeted (it is automatically set to 1000 at this point, to make sure there are no conflicts with other cpu settings from users)
#Already in the last version, but i forgot about it:
- deep idle fixes from stratosk (many thanks)
- added possibility to underclock by using live_oc (limit is 90 now, which means lowering all freq and bus speed by 10%, to save more batterie when really needed)
03.04.2012:
For now there are three different RAM versions:
- stock mem kernel has 379 mb ram, everything working
- "slim ics" (XL) kernel comes with 390 mb, this is breaking playback of some high resolution videos
- XL_BM is coming with 402 mb ram, but breaking 720p
(while flashing the kernel, the modded rom files are also flashed, so you don't need to flash a new rom to get 379 or 390 mb)
-added new frequency: 1080 mhz (1100 does not like live_oc)
- fixed SmartassV2 for live_oc (after changing live_oc value, you have to change the smartass values, too, but then they automatically apply to the live_oc value (although you can only select 800 mhz in nstools (for example))
- touch recovery with custom devil menu (for some reason it takes a few seconds to load the first time, missing virtual keys is a warning, because there are no virtual keys yet)
-fast charge (thx to chad0989 for this), disabled by default.
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
- added datafix script to init.d (this script is deactivated by deafult. to make it work, you have to creat a file named datafix and placed in /data/local/)
- reworking and cleaning many parts to get more ram, speed, and stability
05.03.2012:
- updated sio i/o scheduler to latest version
- small updates to ondemand and conservative governor from linux 3.2
- bettter performance for CFS kernel due to tuning and patches
- tuning to deadline scheduler
- better i/o performance
- changed bootlogo (probably not the last time )
28.02.2012
- finally working bln V9 (no need for LED2 anymore)
- fixed lockscreen freezes
- reverted memory tweaks, which could be the reason for lagging after using a day
- again wlan fixes from tk-glitch
- tweaked conservative and ondemand governor (conservative still is not too aggressive)
- added dm-cache again (who has removed this from my github? )
- improve usb signal quality
- xcaliburinhand's dock audio support (untested, do not have a dock)
- less debugging
- fixed kernel version not displayed under "about phone"
12.02.2012
- Added newest Fiops scheduler (tuned for more performance)
- When Gpu is active, min CPU freq is set to second lowest step
- fixes to live_oc and custom voltage
- default mount parameter NOATIME and NODIRATIME (faster)
- updated Wifi drivers (thanks to tk-glitch)
- tuned intellidemand for better performance
- removed some stuff (zram, swap, tweaks to cpufreq untill I know what was causing the instabilities of last build)
05.02.2012
- added Touchwake
- added BLX
- upgraded BLN from V8 to V9 (working for missed calls, blinking or static light, configurabel by using NSTools or BLN Pro App)
- added Intellidemand governor
- added mdnie settings to voodoo color version
- readded deep idle v2 again (I think it is the best/only working one, although
- version with CFS (instead of BFS) now also available (maybe better multitasking and batterie life, but slower)
- removed BFQ I/O Scheduler
- tons of smaller fixes and improvements
30.01.2012
-revert: Voodoo Sound now to be set with DSP Manager
29.01.2012
- Linux kernel 3.1.10
- Deep Idle from Eugene373 (always enabled, no stats)
- added BFQ v 3.1 I/O Scheduler
- Voodoo Sound now to be set with DSP Manager
- Zram (can be disabled by removing Zram file from init.d)
- Zcache and Cleancache (not working yet?)
- optimized rwsem algorithm
- USB Host V5
24.01.2012
- init.d support (the folder is not created by the kernel. You have to do it for yourself)
- Deep Idle V2 back in
- new Cpu governors: MinMax, Lagfree, Lulzactiv
- LED V2 (you can set blinking by using nstools, also working for missed calls in most cases (sometimes it is not working for missed calls, don't know why at the moment))
- Backlight Dimmer (only LED version): used to turn led backlight of, while screen is on, after defined period of time. Deactivating it, makes your backlight stay on all the time
- I/O-less dirty throttling completely backported from kernel 3.2
- Ext4 with 3.2 patches
- Proportional Rate Reduction for TCP - by Google
- USB Host V 4
19.01.2012
- Usb Host drivers integrated
- Cm9 Color adjustment
- Removed Deep Idle because of Bluetooth problems (hopefully it will come back, still testing)
16.01.2012:
- Updated Kernel basis to Linux 3.1.9
15.01.2012:
- fixed bug in cpu spy, caused by live_oc
- still using voodoo color for now, maybe two additional kernel versions tomorrow
[/quote]
files with .zip have to be flashed within recovery (twrp or cwm)
files with .tar can be flashed by using odin or heimdall (they are placed at the end of post 3)
Downloads:
http://rootaxbox.no-ip.org/divers/jellybean/ many thanks to Rootax
http://devil.haxer.org/ many thanks to SysTem-X (not updatet yet)
just in case ...
First
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
Continuing my discussion from ICS thread here. Either I effed up enabling Idle2 or running a internal Cat of kmsg is not letting my phone drop to idle . Can Idle 2 be enabled from the app or that needs to be implemented?
Edit: Got everything to work. Here is the KMSG that I got. The problem is, if I use ADB the phone doesn't activate Idle2 but i feel like making my phone cat kmsg while I'm trying to crash it might not get the whole txt? I could be wrong. Hope it provides more info.
Idle2kmsg.txt
Wait so what's the difference between deep_idle 2 and idle2? Anyways I'm going to flash it and see what's the difference!
Sent from my SGH-I897 using xda app-developers app
@DerTeufel
Apparently I don't get SoD with idle2, my phone locks up. Screen Actually showed lockscreen this time when I attempted to wake it up while playing music. Sadly my computer doesn't see the device during this state. Any advice? Did you take a look at the kmsg I provided in my earlier post?
Thanks for your contribution .
Can't get to recovery?
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?
Tsaukpaetra said:
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?
Click to expand...
Click to collapse
yes, i think best would be to reflash the kernel, and then try to get to recovery.
DerTeufel1980 said:
yes, i think best would be to reflash the kernel, and then try to get to recovery.
Click to expand...
Click to collapse
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...
Tsaukpaetra said:
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...
Click to expand...
Click to collapse
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt
DerTeufel1980 said:
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt
Click to expand...
Click to collapse
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.
Tsaukpaetra said:
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.
Click to expand...
Click to collapse
Boot.txt is fine now
Gesendet von meinem GT-I9000 mit Tapatalk 2
Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?
Tsaukpaetra said:
Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?
Click to expand...
Click to collapse
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2
DerTeufel1980 said:
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
One thing that always frustrated me was the fact that there is literally no way to watch the kernel messages on the display as it boots. That's one of my most trusted debug methods on the computer: Have it show what it's doing on the console.
Of course, there is a serial port somewhere, but it's apparently not easily accessible without special hardware...
Something just occurred to me: What if we could manually load the TWRP ramdisk and chroot into it? Would that allow us to interactively watch it? or (since stuff is already loaded and junk) that may not be possible? I noticed that adb starts, but we can't get a shell, so...
There is 1.1.3 kernel uploaded.
http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/
Sent from my SGH-I897 using xda premium
Search Button not working. Press it, not working, no response.. Have to go to the search app instead.
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
The search button no longer invokes the normal search function in an app, instead it launched Google Now in Jelly Bean. If that feature is missing in your ROM, nothing will happen when you press it, you must press-and-hold instead.
(ROM) Android 4.4.4 by usol38 (N-7100) (Stable) (Final v1.5)
Hello to all the users of Galaxy Note II.
Description update 1-6:
This port based on the port from Samsung S III (Note4).
+ Works as a USB host (to connect a mouse, keyboard, flash drives! In the photo there is a screen of the operation of the mouse and keyboard)
+ Sewn region SER
+ Removed all unnecessary programs
+ Added flashlight Samsung Galaxy Note 1
+ New sounds
+ Recording with line
+ Multiwindow mode (Floating window)
+ Renamed SPlaner in the Calendar
+ Advanced Russian menu reset
+ Amended and sewn-in firmware kernel AGNi pureSTOCK v4.3.7 (Removed the program from Agni to disperse, removed the folder after you restart the phone)
+ Watch center
+ Sidebar
+ The maximum savings (welcome shade of gray)
+ In the firmware were only 2 Islands language (Russian and English)
+ Added a button call log
+ Fixed graphics in many files (tipo black treugolnikov or something like that! Now there is a full white color)
+ Fixed bugs
+ Updated libraries
+ gps.config touch was not because of the meaning and difference between Europe and Russia I have not seen
+ Updated some programs
+ Removed SFinder and Bestreplica of blinds
+ Also fixed work with Gmail
+ Fixed the bug when recording line
+ Optimization system
+ New sounds
+ Updated services
+ Optimization of RAM
+ Added updated weather
+ Fixed minor bugs
+ Updated libraries
+ Optimize some system files
+ Optimized and fixed some core files
+ Fixed bug quick restart
+ Sewn into the system busybox , zipaling, zip, sqlite3
+ Fixed all the graphics in applications
+ Changed the gps.conf (Improved accuracy of determining the location)
+ Stitched into the modem firmware
+ Optimization zipaling
+ Sewn Recovery (PhilZ Touch 6)
+ Optimization (ext4 file system)
+ Updated biblioteki
+ Support tune2fs
+ Fixed core files (Now the folder AGNi_efs_backup after a reboot is not created!)
+ Opravil some files PhilZ Touch 6
+ Fixed minor bugs
+ Fixed bugs in feature.xml
+ Updated libraries to spen
+ Translated into Russian SystemUI
+ Fixed position of the point of the stylus (Now at the center!)
+ Fixed error when selecting automatic time pole
+ Optimization system
+ Now all firmware in white
+ Removed not nuzhnego buttons from the blinds (if someone wants dobavit buttons You need to edit file feature.xml)
+ Fixed bugs
+ Fixed bug life standard browser
Android 4.4.4 Note 2 update 7
Description:
+ This includes all updates from the update 1-6
+ System Optimization
+ New recovery
+ Bug fixes
Android 4.4.4 Note 2 update 8
Description:
+ System Optimization
+ Fixed a bug download all video files via a standard browser
+ Update some system files and libraries
Android 4.4.4 Note 2 update 9
Description:
+ Returned kernel AGNi 4.3.7 as 4.3.8 is not stable!
+ Optimization file system
+ Update libraries
+ Fixed some bugs
+ Optimization Interface
+ Updated library of modules for mali400
Android 4.4.4 Note 2 update 10
Description:
+ Update all libraries
+ Fixed bug emulation screen in settings
+ Fixed minor bugs
+ Fixed schedule in some files
+ Optimized all apk files
Android 4.4.4 Note 2 update 11
Description:
+ Update all libraries
+ Fixed bug Samsung account
+ Fixed bugs Music to Adap Sound
+ Optimized kernel
+ Fixed some bugs
+ Fixed bug Download
+ Fixed bug Service
Android 4.4.4 Note 2 update 12
Description:
+ Returned the video driver from Mali 400 update 9. As a new driver itself is poorly established in the work! (With the old working not only additional emulation screen)
+ Optimization of RAM
+ Fixed schedule
+ Returned pre-start settings
+ Upgraded the theme file
+ Upgraded the setup file
Android 4.4.4 Note 2 update 13
Description:
+ The phone is now to determined as expected Galaxy Note II
+ Fixed bugs
+ Completed to schedule in some applications
+ Corrected kernel code
+ Updated some libraries
+ Bug fix for Samsung Platform
+ Updated recovery now it's in Russian
Android 4.4.4 Note 2 update 14
Description:
+ Updated libraries of standard video (Now plays all formats)
+ Fixed scroll Wallpaper to your desktop
+ Updated video driver (emulation Now works extra screen)
+ Corrected and translated recovery 2.8.6.2
+ Fixed tank with effects when charging
+ Corrected schedule in some programs
+ Fixed minor bugs
+ Optimized the kernel AGNi 4.3.7
+ Updated libraries
+ Tweaked the code android.policy.jar
+ Everything that was associated with Not4 I altered the Not2
+ Smooth interface
+ Optimization of RAM
+ Moved some settings on Russian
+ Ismini called S Planner Calendar
+ Updated Superuser to latest version
+ Updated all apps to latest versions
Android 4.4.4 Note 2 update 15
Description:
+ The new base N7100XXU1ANK5
+ Fix departure Google voice search
+ Update libraries
+ Ispravlenie translation
+ Fix translation recovery
+ Fixed minor bugs
+ Modifying the core code AGNi 4.3.7
Android 4.4.4 Note 2 update 16
Description:
+ Optimization of a new database N7100XXU1ANK5
+ Optimiza RAM
+ Tweaked the code of the kernel AGNi 4.3.7
+ Moved all programs to Russian
+ Interface optimization
Android 4.4.4 Note 2 Final
Description:
+ Optimization of the system
+ Revision recovery and upgrade to 2.8.6.3
+ Tweaked the code of the kernel AGNi 4.3.7 (Final)
+ Moved all programs to Russian
+ Update libraries
+ Fixed some bugs
+ Updated the driver in the vendor folder
Android 4.4.4 Note 2 Final v1.0
Description:
+ Fixed the display of the widget alarm clock
+ Fixed core! Removed the scripts and everything related to overclocking! AGNi Control with this kernel doesn't work!
+ Fixed bugs
+ New recovery (Now Russian)
+ Install the firmware without any firmware mods kernels and recoveriesr
Android 4.4.4 Note 2 Final v1.1
Description:
+ Fixed crash lock screen
+ Fixed minor bugs
+ Fixed translation in applications
+ Also fixed the graphics in applications
+ Core mod
Android 4.4.4 Note 2 Final v1.2
Description:
+ Bug fix calendar
+ Optimization of RAM
+ Optimization of the core code
+ Fixed some not decety
Android 4.4.4 Note 2 Final v1.3
Description:
+ Fixed crash SPen smart choice
+ Optimization of the system
+ Optimization of electricity
+ Fixed some bugs
Android 4.4.4 Note 2 Final v1.4
Description:
+ Added paragraphs in settings
+ Fixed bug lock valve
+ To effect unlock "Abstract tiles"
+ New keyboard from Samsung S6
+ New sounds
+ Fixed bug sending paid SMS
+ Fixed some bugs
View attachment 3202200View attachment 3202201View attachment 3202202View attachment 3202225View attachment 3202226View attachment 3202243
Android 4.4.4 Note 2 Final v1.5
Description:
+ Added patch poured the camera
+ Fixed bug screen unlock pin code
+ Fixed translation
+ Optimization of the system
+ Update libraries
This firmware does not work with mods from DN4 correctly! So the firmware is sharpened by the core of AGNi v 4.3.7! Firmware fully working excellent! I write sometimes what they type after the firmware is not loaded phone! Everything loaded perfectly if done according to instructions!
Click to expand...
Click to collapse
Download:
Android 4.4.4 Note 2 by usol38 mail.ru
Android 4.4.4 Note 2 by usol38 mega.co.nz
Download Russian recovery based on TWRP from me:
Download: View attachment 3350108
Credits:
gencho81
XDA:DevDB Information
(ROM) Android 4.4.4 by usol38 , ROM for the Samsung Galaxy Note II
Contributors
usol38
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-06-23
Last Updated 2015-06-23
No need to follow this, Flash Files are available here to do automatically !
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773?nocache=1
Do not judge by how the device will work by looking at the code, which is completely different from what have been suggested all this years.
That is the reason I am providing the boot image. So that you can test it on your tablet and see it for yourself.
None of this will create any damage, is the opposite your tablet will have less work to do and work faster.
Before trying this out you must have already created a swap partition here are the steps:
https://forum.xda-developers.com/hp-touchpad/general/how-to-backup-restore-using-twrp-copy-t3892047
https://forum.xda-developers.com/hp-touchpad/general/how-to-create-swap-partition-size-t3892060
If installing on a running system with a swap partition, or you back up the system and then restore it after creating the partition.
The Dalvik/Art Cache
Cache
Must be wipe using TWRP ( For all settings to work properly )
What would the changes do?
Make the HP Touchpad work as originally intended, a tablet not a smartphone.
You will be able to play HD 720 videos, using google youtube app and any browser.
Use Google Maps, Google Earth and many others apps that is impossible to use now.
CPU settings (The normal that all tablets will work) It can be increase to 1890000.
MAX 1728000 Minimum 192000 interactive
Readahead buffers (as per LVM)
4096
Scheduler bfq
The following Skz Kernel modules permanently removed. Even if the module is disable its settings will be active, that is the reason of the removal.
Code:
# CONFIG_HOTPLUG is not set
# CONFIG_INTELLI_PLUG is not set
# CONFIG_ASMP is not set
# CONFIG_HOTPLUG_CPU is not set
# CONFIG_KSM is not set
# CONFIG_UKSM is not set
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set
# CONFIG_ANDROID_LOW_MEMORY_KILLER_AUTODETECT_OOM_ADJ_VALUES is not set
The following Ramdisk files have been modified to apply the optimum settings.
fstab.tenderloin
init.tenderloin.power.rc
init.tenderloin.rc
Code:
Details
fstab.tenderloin
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p13 /boot ext3 ro,noatime,barrier=0 recoveryonly
/dev/store/cm-system /system ext4 rw,errors=panic wait
/dev/store/cm-data /data f2fs rw,nosuid,nodev,noatime,nodiratime,inline_data,inline_xattr,inline_dentry wait,check,formattable
/dev/store/cm-data /data ext4 nosuid,nodev,noatime,noauto_da_alloc,errors=panic wait,check,formattable
/dev/store/cm-cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_data,inline_xattr,inline_dentry wait,check,formattable
/dev/store/cm-cache /cache ext4 nosuid,nodev,barrier=1 wait,check,formattable
/dev/store/swap swap swap defaults swapprio=1, 0 0
/devices/virtual/block/dm-6 auto vfat defaults voldmanaged=sdcard1:auto,nonremovable,encryptable=userdata
/devices/platform/msm_hsusb_host.0 auto auto defaults voldmanaged=usbdisk:auto,noemulatedsd
# zRAM
# /dev/block/zram0 none swap defaults zramsize=1073741824,max_comp_streams=2,notrim,swapprio=2
init.tenderloin.power.rc
# Configure Performance Governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "performance"
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor "performance"
# CPU boost
write /sys/module/cpu_boost/parameters/boost_ms 0
write /sys/module/cpu_boost/parameters/input_boost_ms 0
write /sys/module/cpu_boost/parameters/sync_threshold 1728000
# write /sys/module/cpu_boost/parameters/input_boost_freq 1728000
# GPU boost
write /sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/max_gpuclk "266667000"
write /sys/class/kgsl/kgsl-3d0/max_gpuclk "320000000"
# KGSL trustzone governor
write /sys/class/kgsl/kgsl-3d0/pwrscale/trustzone/governor ondemand
on property:sys.boot_completed=1
# Configure Interactive
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "interactive"
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor "interactive"
# CPU Workqueues
write /sys/module/workqueue/parameters/power_efficient "N"
# Entropy
write /proc/sys/kernel/random/write_wakeup_threshold 4096
write /proc/sys/kernel/random/read_wakeup_threshold 4096
# I/O
write /sys/block/mmcblk0/queue/rq_affinity "0"
write /sys/block/mmcblk0/queue/scheduler "bfq"
init.tenderloin.rc
# Swap Settings
write /proc/sys/vm/block_dump 0
write /proc/sys/vm/dirty_background_bytes 0
write /proc/sys/vm/dirty_background_ratio 80
write /proc/sys/vm/dirty_bytes 0
write /proc/sys/vm/dirty_expire_centisecs 60000
write /proc/sys/vm/dirty_ratio 90
write /proc/sys/vm/dirty_writeback_centisecs 60000
write /proc/sys/vm/drop_caches 0
write /proc/sys/vm/extra_free_kbytes 9216
write /proc/sys/vm/highmem_is_dirtyable 0
write /proc/sys/vm/laptop_mode 0
write /proc/sys/vm/legacy_va_layout 0
# write /proc/sys/vm/lowmem_reserve_ratio 32 32
write /proc/sys/vm/max_map_count 65530
write /proc/sys/vm/min_free_kbytes 10000
write /proc/sys/vm/min_free_order_shift 4
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/vm/mmap_rnd_bits 16
write /proc/sys/vm/nr_pdflush_threads 0
write /proc/sys/vm/oom_dump_tasks 1
write /proc/sys/vm/oom_kill_allocating_task 0
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/overcommit_ratio 50
write /proc/sys/vm/page-cluster 0
write /proc/sys/vm/panic_on_oom 0
write /proc/sys/vm/percpu_pagelist_fraction 0
write /proc/sys/vm/scan_unevictable_pages 0
write /proc/sys/vm/stat_interval 1
write /proc/sys/vm/swappiness 60
write /proc/sys/vm/vfs_cache_pressure 100
# Increase readahead buffers on MMC devices
write /sys/block/mmcblk0/bdi/read_ahead_kb 4096
Download the file and copy it as is in your boot directory using TWRP. That is if you have extra space for 5.9MB, you should if only using Android.
Before booting you should have already disable any app that you have installed to optimized the settings, otherwise settings will be overwriten and will not take effect.
After booting for firs time, depending on how many apps you have, it could take very long time to be ready for use.
Give it some time, let it rest and finish rebuilding.
Many thanks to everyone that work on the Evervolv Team that provided the TP users with this great ROM and also to Shumash for creating the fastest Kernel for all Android ROMS.
HP_TOUCHPAD said:
No need to follow this, Flash Files are available here to do automatically !
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773?nocache=1
Do not judge by how the device will work by looking at the code, which is completely different from what have been suggested all this years.
That is the reason I am providing the boot image. So that you can test it on your tablet and see it for yourself.
.......
Click to expand...
Click to collapse
Going to have to give this a try.
Thanks for taking the time to put it together.
@HP_TOUCHPAD. Cheers for this man. I've flashed the rom yesterday and followed the guide after you posted the final version.
Evervolv 7.x feels really snappy
jhonnyx said:
@HP_TOUCHPAD. Cheers for this man. I've flashed the rom yesterday and followed the guide after you posted the final version.
Evervolv 7.x feels really snappy
Click to expand...
Click to collapse
Yes all the ROMs works the same as it have the same settings. Pick and the one you like the most all work with the same speed.
Thanks for trying it out and reporting, enjoy your brand new Tablet. !
HP_TOUCHPAD said:
Yes all the ROMs works the same as it have the same settings. Pick and the one you like the most all work with the same speed.
Thanks for trying it out and reporting, enjoy your brand new Tablet. !
Click to expand...
Click to collapse
Not all the roms. Picked DU 12.5, which was Oreo based, I believe, and it was sluggish. That's why I chose the other ROM.
Anyhow, I'll test the Other roms as they come. Feel free to hit me up/mention me if you need testing.
Great work, man, keep it up!
jhonnyx said:
Not all the roms. Picked DU 12.5, which was Oreo based, I believe, and it was sluggish. That's why I chose the other ROM.
Anyhow, I'll test the Other roms as they come. Feel free to hit me up/mention me if you need testing.
Great work, man, keep it up!
Click to expand...
Click to collapse
I want to make sure we are on the same page, you installed 7.1.2 using this guide and flash the proper speed for your tablet:https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
You also installed 8.1 from that guide but found it slow?
Did you tried 9?
HP_TOUCHPAD said:
I want to make sure we are on the same page, you installed 7.1.2 using this guide and flash the proper speed for your tablet:https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
You also installed 8.1 from that guide but found it slow?
Did you tried 9?
Click to expand...
Click to collapse
Is there any advantage to using to this SKZ kernel over the Max 1836 kernel? Or is your Max kernel included in the "All files for this rom.zip" based off of this kernel? Also, does the Max kernel include the GPU overclock? I noticed the Touchpad is a bit lacking in the GPU department.
Sanras said:
Is there any advantage to using to this SKZ kernel over the Max 1836 kernel? Or is your Max kernel included in the "All files for this rom.zip" based off of this kernel? Also, does the Max kernel include the GPU overclock? I noticed the Touchpad is a bit lacking in the GPU department.
Click to expand...
Click to collapse
This is an obsolete guide, it is posted on the first page:
No need to follow this, Flash Files are available here to do automatically !
HpTp_Max and HpTp_MaXtreme (optimized settings ) includes everything.
The HP Touchpad lack of everything, is an 11 year old device, now in 2022.
But still functional in many ways.
HP_TOUCHPAD said:
This is an obsolete guide, it is posted on the first page:
No need to follow this, Flash Files are available here to do automatically !
HpTp_Max and HpTp_MaXtreme (optimized settings ) includes everything.
The HP Touchpad lack of everything, is an 11 year old device, now in 2022.
But still functional in many ways.
Click to expand...
Click to collapse
Ok, thanks. And to confirm, HpTp_Max does include the GPU overclock too right?
Sanras said:
Ok, thanks. And to confirm, HpTp_Max does include the GPU overclock too right?
Click to expand...
Click to collapse
For all ARM based devices, the GPU is built into the CPU ( combo ) same as desktop or laptops that do not offer a dedicated GPU.
For the HP Touchpad:
ChipsetQualcomm APQ8060 Snapdragon S3CPUDual-core 1.2 GHz ScorpionGPUAdreno 220
The 1GB RAM is shared by the GPU, some of that RAM is used by the GPU for the driver resources.
Then Android run a Virtual Machine for the java apps and the graphics settings are specified in the build.prop.
If you are familiar with virtual machines on the PC, there are settings to allocate GPU RAM for the graphics ( display settings ). It does not matter how fast or new the GPU card is, but how much RAM is assigned to the virtual machine to be able to handle the proper display resolution.
The same applies to Android, if the settings to run the virtual machine in the build.prop are not properly configured then nothing will run regardless of how overclock the GPU is. The lack of graphics performance on the tablet is due to 1GB or RAM and that is why the importance of the swap partition to gain some RAM.
There is no magic code to improve or make the display better because is all about " RAM " and there is only 1GB for everything.
If you would like to see all the settings from any Kernel that is running on the Tablet, then you can install Kernel Adiutor, just to check the settings.
https://m.apkpure.com/kernel-adiutor-root/com.grarak.kerneladiutor
HP_TOUCHPAD said:
For all ARM based devices, the GPU is built into the CPU ( combo ) same as desktop or laptops that do not offer dedicated GPU.
For the HP Touchpad:
ChipsetQualcomm APQ8060 Snapdragon S3CPUDual-core 1.2 GHz ScorpionGPUAdreno 220
Click to expand...
Click to collapse
Yes, I know it's integrated into the SoC. It does seem to have a separate clock speed though.
The original thread for the SKZ kernel mentions a GPU overclock as well: https://forum.xda-developers.com/t/...vervolv-7-1-x-1890khz-cpu-320mhz-gpu.3513534/
Sanras said:
Yes, I know it's integrated into the SoC. It does seem to have a separate clock speed though.
The original thread for the SKZ kernel mentions a GPU overclock as well: https://forum.xda-developers.com/t/...vervolv-7-1-x-1890khz-cpu-320mhz-gpu.3513534/
Click to expand...
Click to collapse
Install Kernel Adiutor and you will see all the settings. It must be uninstall or better re-flash the ROM to avoid any issues.
As already mentioned, the issue with the GPU is the limited about of RAM, not the clock speed.
I have to say thanks to HP_TOUCHPAD for his consistent replies and guidance for overclocking and getting this tablet to work again.
Vicious942 said:
I have to say thanks to HP_TOUCHPAD for his consistent replies and guidance for overclocking and getting this tablet to work again.
Click to expand...
Click to collapse
You are very welcome ! A lot of developers spent a lot of time on this Tablet, they deserve all the credits.