Related
Version 5.x of xtrROM builds on the heritage and continues the evolution of this fast reliable feature rich ROM that you as the user can customize to enhance your Droid Eris Android experience! This ROM has a very Vanilla feel but is based on the core HTC framework to offer the best relibility possible in a custom ROM. I am reliant on my phone at work so stability and consistent quality of user experience are the top priorities for xtrROM. If you like the HTC Sense experience then be sure to check out xtrSENSE and if you would like a "pure" Vanilla 2.1 AOSP experience then be sure to try VanillaASOP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base xtrROM Features:
All the goodness of Android 2.1 with Root access and Superuser permissions
A very Android ASOP Vanilla feel from removing HTC "bloat"; while embracing reliable HTC sync and app coordination
Fully odex to save as much "usable" internal space as possible and provide faster boot times
Over clock support - default to 710400
Many reliable "hacked" tweaks such as: Collin_ph battery tweak, some Flash support, OpenGLES 1.1, new Android Market, wired tether, etc...
Included opensource GScript app allows you to easily turn on/off core ROM settings (CPU OC, Apps2sd, Cache2sd, JIT, etc...) with one-click
Live wallpapers as a separate module you can enable
Full Cache2cache support (see details below) - better use of the /data/ and /cache/ file blocks which opens up unused internal storage allowing you to install close to 100 apps without using Apps2sd!
Apps2sd support (see instructions below)
Customized theme including wallpapers, phone dialer, keyboard, bootanimation, and other small touches...
Lean and very crisp running ROM - it almost "feels" lighter in your hand!
Designed to be a stable everyday ROM
Check out the change log to see the full evolution and details
Credits and General Public License (GPL):
HTC kernel source: http://member.america.htc.com/download/RomCode/Source_and_Binaries/desirec_2.6.29_8a03cb9a.tar.bz2
Zanfur OC kernel support – source: http://forum.xda-developers.com/showthread.php?t=679102
GScripts source: http://code.google.com/p/gscript-android/source/checkout
Wired tether source: http://code.google.com/p/android-wired-tether/source/checkout
Built from the July Verizon 2.37.605.4 Eris code base
bertoch for hosting and helping me understand Linux
dsixda for his time saving kitchen – source: http://forum.xda-developers.com/showthread.php?t=633246
gr0gmint on how to make jit (mostly) work with HTC ROMs – source: http://forum.xda-developers.com/showthread.php?t=684535
ChainsDD for Superuser – source: http://forum.xda-developers.com/showthread.php?t=682828
vash8806 for Flash 10 source: http://forum.xda-developers.com/showpost.php?p=7316925&postcount=46
synaptyc for custom boot animation - source:http://forum.xda-developers.com/showthread.php?t=768513
rogro82 for starting GScript - source: http://forum.xda-developers.com/showthread.php?t=486486
nfinitefx45 from the Hero CDMA forum on his companion work with cache2cache
thenestor on help with the DroidXIME keyboard
firestrife23 for helping me understand permission issues with the init.d process
Damageless and TrevE for a model on how to do apps2sd (originally based on tkirton's Darktremor A2SD work) and other boot settings
t2noob on the July patch
Collin_ph for the battery tweak code – source: http://forum.xda-developers.com/showthread.php?t=737352
dearmasfamily for OpenGLES1.1 - source: http://forum.xda-developers.com/showthread.php?t=915058
xda member beta testers (you ROCK)
other xda members for tips and tricks
Download xtrROM5.0.1: http://zach.xtr.i6ix.com/xtrROM5.0.1.zip
MD5 checksum:1e5482eb3fc8486182151c5fad01a253
Default ROM Configuration:
You do not need to run any scripts unless you would like to change the following default configuration:
Live Wallpapers: Not supported (you must run GSript to enable)
dalvik.vm.heapsize: 24m
min free memory values: "balanced" (1536,2048,4096,10240,12800,38400)
CPU Overclocked: Min-245760 Max-710400
CPU Governor: Ondemand
Just In Time Compiler (JIT): Off
Cache Location: Cache2cache On
Apps2sd: Off
User service and battery tweak: Off
Thanks to Canop you can flash other Kernel options from the links below:
BFS - http://forum.xda-developers.com/showthread.php?t=772053
CFS - http://forum.xda-developers.com/showthread.php?t=774211
Get older versions of xtrROM in the change log
OPTIONS AND CONTROLS:
Stock Battery Icon
If you prefer the stock battery icon over the circle battery then flash the below zip.
Make sure to wipe dalvik-cache AFTER flashing this zip
Stock battary Icon: http://zach.xtr.i6ix.com/xtrStockBattery.zip
Live Wallpapers
Live Wallpapers is a feature you can enable for this ROM. I have included my favorite for you to try and you can get others from the Market. Many of the live wallpapers from the market DO NOT function well on our Eris or do not "stick" after reboot, our hardware is underpowered for most and I also find them to be a battery drain. That said I still run a few at times because they are just COOL !
To enable live wallpaper functionality just run the appropriate GScript.
Android ASOP Keyboard and Themed Dialer
This ROM uses a custom themed Android ASOP keyboard as the default keyboard and I have themed the phone dialer to match. If you prefer the standard HTC style keyboard check out jonasl HTC_IME mod keyboard – source: http://forum.xda-developers.com/showthread.php?t=624416. Or if you would like the stock setup download and flash the below .zip file.
Stock keyboard and dialer: http://zach.xtr.i6ix.com/xtrStockKeys.zip
LOOKS LIKE THIS DOES NOT WORK FOR XTRROM5.0 ONLY OLDER VERSIONS - I'LL UPDATE SOON FOR XTRROM5.0...
Clear HTC Lockscreen
It is my personal favorite and since I make the ROM I get to pick . To update the lockscreen go to the Photos app - select the photo you want - select the Set as option - and then select lockscreen.
To get back to the clear lockscreen just run the set_lockscreen_clear.sh GScript and reboot your phone.
GScript
I have compiled and incorporated the opensource GScript app to load and one-click run user settings.
To setup your GScripts complete the following steps:
1. After opening GScript press the menu button and select "Add script"
2. A new window will open.
3. Press the Load file button
4. Select a script from the list (each is obviously named as to its function)
5. Ensure Needs SU? is checked
6. Now select "Save" and you have added your script
7. To run just select it from the list in the main GScript screen
8. Some scripts may prompt you to reboot the phone for the change to take effect.
There are a lot of scripts but remember your phone has been setup great by default with this ROM and if you do not understand the function or purpose of a GScript then best to not save and run it . One can always search this forum and ask others about all the fun things you can now do with your phone! I will look to add a list of each GScript and its function as time allows...
Wired Tether
For wired tether to work you must make sure that your computer has the appropriate RNDIS drivers. Learn how to do this at the android-wired-tether Wiki.
Per roirraW "edor" ehT:
The wiki incorrectly states, or implies, that Windows 7 includes the RNDIS support. Or at least, they imply that Windows 7 includes the RNDIS driver necessary. I can confirm that neither Windows 7 x86 or x64 works with tethering out of the box. The instructions for XP users are correct and also work for Windows 7. Just download HTCSync for your device (Eris) and install it, and it'll install the correct driver.
Flash Support
A hacked version of Flash 10.1.123 is baked into this ROM however it has proven to be hit and miss and preforms more like a flash "lite"... Full flash sites such as Halo do not work however many others do; they may just take a while as the Eris is not a powerful phone
Performance Improvements:
Free Internal Memory and Dalvik-cache heapsize - I have update default user settings to allow a larger dalvik heapsize of 24mb (think more space for apps to play) AND optimized how memory is freed up using Androids internal task killer.
Default min memory free: “balanced” (1536, 2048, 4096, 10240, 12800, 38400)
Default dalvik vm heapsize: 24m (48m with JIT on)
To change dalvik vm heapsize or min memory free settings you can just run the appropriate GScript.
If you would like to further modify the default min memory free settings then download Autokiller or MinFreeManager, these apps will allow you to set and monitor the min memory free values. For more information on Androids “internal task killer” and min memory free values go here.
default Overclock Settings - the ROMs kernel supports overclocking and as part of the custom sysinit process I have added scripts that automatically set the below CPU clock settings when the phone boots:
Min: 245760
Max: 710400
I have included a few GScripts to change between stock cpu settings and default overclock settings without using a market app . You can also run the report_cpu_freq script from GScript to get a printout of which frequencies and time in each you phone has been operating.
To change CPU overclock settings just run the appropriate GScript.
If you would like to further modify OC settings then download SetCPU or Overclock Widget, these apps will allow you to set and monitor the CPU speed. Remember YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings. MAKE SURE TO RUN THE set_cpu_stock GSCRIPT IF YOU INSTALL A MARKET APP. The internal overclock support may overwrite the market app settings...
JIT - JIT (Just In Time compiler) is a built in option for the ROM but is off by default. For a detailed overview of JIT go here. PLEASE NOTE for Android 2.1 JIT is not stable with all applications and can cause odd things on your phone.
To enable/disable JIT just run the appropriate GScript and reboot your phone.
User Services Power Management (Collin_ph Battery Tweak) - I have built in a user services that runs at a polled interval and can set the performance settings of your phone in realtime. The first script that is available is a 2.1 HTC framework version of the Collin_ph Batter Tweak. For a detailed overview of you can view the original thread at here.
The power management battery tweak is disabled by default but there is a gscript to enable plus you can run "battconf" from terminal on the phone or adb shell to configure... The battery tweak runs a script every 60 (or less if you are on power) to poll the capacity of the battery, and as the battery goes down the cpu max freq is progressively lowered. It also changes the CPU write characteristics (all of which I do not yet fully understand). You can see all the details in the /system/bin/batter_tweak file.
I take no real credit on this and just ported the concept to the HTC framework and HTC kernel (with the zanfur OC patch). This took a lot of work and I fixed a few bugs but the concept is not mine and all Collin_ph.
When you first run terminal remember to type "su" (or equivilent for your app) to run as root and select "1" then enter when first prompted after starting "battconf".
So how do I know it is working? just run the report_log.sh GScript and you will see when it logs a change to the system settings. Also you can run the report_system_settings.sh GScript and for a display of current settings. This process will be faster if you plug into a power source and wait about 60 seconds
To enable/disable the battery tweak just run the appropriate GScript (user_service_batterytweak_enable.sh or user_service_batterytweak_disable.sh) and reboot your phone.
Cache Location (Cache2cache):
By default, the dalvik-cache has been relocated from the internal /data/dalvik-cache/ directory to the internal /cache/dalvik-cache directory. The Eris comes with an internal /cache/ file block of 130mb that is not used! After reviewing a number of xda member file system usage reports (thanks xtrROM and xtrSENSE users!) the MOST reported use of this space was 5%... So by moving the dalvik-cache to this free area you now have over 150mb on internal /data/ for apps and over 75mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT having to partition and move anything to the SD Card ext!
You can also move the dalvik-cache to your sd card ext or back to the stock internal /data/ file block.
To change the dalvik-cache location just run the appropriate GScript and reboot your phone.
So why does my Settings>SD card & phone storage>Internal phone storage only show 150mb or less? This is because this number ONLY reflects the /data/ file block on your phone and does not "see" the /cache/ block that is now being used for dalvik-cache storage. You can run the GScript report_system_settings script to see amount available in /cache/.
Apps2sd and Cache2sd:
I have revamped my implementation of apps2sd to use simpler and better organized scripts. For apps2sd to work you must first complete the listed prerequisites and it is a good idea to read through the "things you may want to know about apps2sd" section. Although it can provide gobs of space for apps, Apps2sd is not for everyone as it ties the stability of your phone to your SD card... If you do not need the space I would recommend that you keep the default of DISABLED; if you want to try you can always disable it again however there is always the chance of issues.
To enable/disable apps2sd and cache2sd just run the appropriate GScript and reboot your phone.
Prerequisites
If you have not setup your SD card (for those new to Apps2sd) as per tkirton:
BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
Reboot into recovery
In Android System Recovery, select Partition sdcard
In the Partition sdcard menu, select Partition SD
Follow the instructions on the phone to partition your SD card. Most folks seem to recommend using the default values however you can go larger or smaller use values 256, 512,768,1024. You will also be asked to set a swap size; I stayed at 32mb (anticipate future ROM options to allow moving swap to sd)
Once the partition is initially created you must then convert to ext3 - In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
Press the back button on the phone to go back to the main menu.
Your SD card is now ready to work with an Apps2sd supported ROM.
Things you may want to know about apps2sd
Bootloop protection is built in if your SD card is corrupted or is removed from the phone with Apps2sd enabled. Your apps will go away but your phone will boot .
There are 3 subsets of data associated to an app when it is installed and run on your phone.
1) /data/app/ (and /data/app-private) - actual .apk files we think of as the applications that are not system apps (i.e. installed on /system/app)
2) /data/data/ - the files produced by ALL apps (system apps and market apps) during installation that are used by the Android system to run the app
3)/data/dalvik-cache/ - app cache file and work space for ALL apps (system apps and market apps).
From root explorer (or similar) you can browse to the /data/app OR the /system/sd/app folders and you will see the same thing, both will tell you how much space you have used and have left. The way apps2sd works is by "linking" the /system/sd/app to the /data/app folder so that the Android system thinks it is accessing the /data/app it is really at /system/sd/app.
I have seen using Apps2sd cause issues with some.zip flash updates as they try to write directly to the /data/app folder which no longer "physically" exists
If you get into a bootloop issue using apps2sd boot into amon_ra recovery and try one of the follow:
1) from the Other menu option select the Fix apk uid mismatches
2) from the Wipe menu option complete a)Wipe data/factory reset b)Wipe Dalvik-cache c)Wipe SD:ext partition
Apps2sd and Cache2sd Basics
When you run the apps2sd or cache2sd script, upon reboot, it will move ALL your existing apps or cache to the sd card ext partition and ALL future apps and cache will be installed and stored on the sd card ext partition.
Running the apps2internal or cache2internal script, upon reboot, it will move ALL your existing apps or cache to the /data block of internal storage and ALL futures apps and cache will be stored in internal storage.
With HTC based ROMs it is all or nothing and you cannot move individual apps like in the CyanogenMod ROMs.
So how do I know Apps2sd is on? - You can run the GScript report_system_stats which will give you a printout of what fileblocks are used as well as a “true/false” value for Apps2sd On. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will go down at a VERY slow rate when new apps are installed.
TO INSTALL:
YOU MUST HAVE A ROOTED PHONE
download the xtrROM .zip file
complete NANDROID backup
copy the .zip file to the root of your sd card
From Wipe data/factory reset, Wipe Dalvik-cache, and Wipe SD:ext partition (folks coming from previous versions may try no wipe updates but a full wipe is always "cleanest")
flash the xtrROM file from sd card
reboot (first boot may take around 10 minutes)
complete short setup and let your accounts sync
you can save and run GScripts to personalize settings at any time
Available Market Apps You May Want to Add:
Widgetsoid - provides the CyanogenMod style customizable power widget that can be put in the notificaton bar
Root Explorer
Launcher Pro
Tips
For an even faster feel turn off window animations under Settings>Sound & Display>Animaiton.
To update the lockscreen goto the Photos app select the photo you want and select the Set as option and then select lockscreen.
Random FC - Lower your overclock settings or turn off JIT. Our little Eris's can only do so much and not all hardware is equal... Also remember this ROM is quite fast in stock form and higher Linpack scores DO NOT make for a better user experience
Google contact sync issus? check out the following fix http://forum.xda-developers.com/showpost.php?p=6796805&postcount=102. I think this is not uncommon coming from 2.2 Froyo ROMs as they seem to sync with Google a little differently and I do not think the folks at HTC or Google built their systems with the thought that users would be jumping back and forth between versions as much as we all do...
Slow facebook sync? per erishasnobattery: log into your facebook account on your computer - Click Account>Application Settings>under Authorized - remove listing for HTC Sense.
To turn on vibration with keypress for the keyboard long hold the ?123 button in the bottom left and select Android keyboard settings>Vibrate on keypress
If you have 50% time without signal under Settings>About Phone>Battery>Cell Standby complete the "airplane trick" by turning Airplane mode on wait just a few seconds and then Airplane mode off (search the forum for "time without a signal")
If you are syncing facebook then you may want to remember to check the "View contacts" for facebook from the People app Menu>View setting
Turn off notifications for Superuser from the Settings tab of the app
Known Issues
Messaging sometimes FC when send and IMMEDIATE rotate from portrait to landscape. The message still sends and the app stays open there is just an annoying FC on the screen...
Flash does not work for some sites, Halo for example.
The keyboard does not have an updateable user dictionary
Verizon NFL does not work with JIT on
CHANGE LOG:
Click here to view the full change log
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
kenshincbb said:
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
Click to expand...
Click to collapse
And I run at 806 but he is saying this for the majority of ppl. So if they DO damage their phone, they dont blame him.
always good to have more options ...i will check it out
rvpartsguy said:
always good to have more options ...i will check it out
Click to expand...
Click to collapse
You really try everything dude. It's a very nice thing to do.
Anyone try it with JIT yet?
Wondering if wired tethering would be included in a later release? Seems to work somewhat faster than wireless for me.
Spencer_Moore said:
You really try everything dude. It's a very nice thing to do.
Click to expand...
Click to collapse
I've been lurking for quite a while, just recently started posting on xda. Pretty sure I've tried all of the ROMs too.
Just got this one downloaded, about to flash it and see how it goes. Won't have to worry about A2SD with over 140mb of internal memory. Outstanding!
Nice Job
Just got XTR setup and it is very responsive. If battery life is decent then I will definitely use this everyday! Excellent effort and I commend you on your opening page. Very clear and consise!
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Wondering if wired tethering would be included in a later release?
Click to expand...
Click to collapse
Thanks for the feedback. I will add wired tethering to the StockApps.zip flash and re post tonight or tomorrow.
-------------------------------------
Sent via the XDA Tapatalk App
Jit Failure for me.
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
Click to expand...
Click to collapse
OTA is disabled.
-------------------------------------
Sent via the XDA Tapatalk App
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Click to expand...
Click to collapse
Thanks for trying it out and the feedback! This ROM still runs on the core HTC framework and during my testing with jit could not get it stable enough for a daily ROM.
-------------------------------------
Sent via the XDA Tapatalk App
The widgets are broken apparently. I installed Advance Task Killer and everytime I click on it, it'll vibrate and that's it. OC widget isn't working either. Any ideas?
[EDIT] Oh, reboot was needed. Disregard.
Advanced task killer is not needed. The autokiller app does a much better job. Get rid of atk.
-------------------------------------
Sent via the XDA Tapatalk App
Great running ROM. No troubles yet. Thanks.
I'm running Launcher Pro Beta instead of Sense UI. JIT works GREAT. Getting 5.3mflops @ 806mhz. 5.1mflops @ 768mhz. This thing is FAST!!
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Click to expand...
Click to collapse
Nav works very well with lwp on this ROM & I use almost daily. the Nav I have included is Googles NOT the HTC version which is where I believe (though I have fully tested) the issues are caused.
-------------------------------------
Sent via the XDA Tapatalk App
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.
Hi,
I´m spanish and my sim card of Tuenti Movil don´t be detected for the phone and I haven´t got web but when I introduce the sim card of movistar the phone I have web and detecte it.
When I desactive the pIn code the phone detected the sim and I have got web but I haven´t got 3G.
Help me please.
Sorry for mi bad english.
Here are photos of jellycast V6 that is a rom based on cm9
mjgs17 said:
Hi,
I´m spanish and my sim card of Tuenti Movil don´t be detected for the phone and I haven´t got web but when I introduce the sim card of movistar the phone I have web and detecte it.
When I desactive the pIn code the phone detected the sim and I have got web but I haven´t got 3G.
Help me please.
Sorry for mi bad english.
Here are photos of jellycast V6 that is a rom based on cm9
Click to expand...
Click to collapse
r u using the right baseband (check the version number in about phone eg v10k and confirm it with lg firmware website just google it )if not then U have to flash your home country's or open europe's baseband via Kdz flasher then flash the jellycast...!
Problem
drkingtech said:
r u using the right baseband (check the version number in about phone eg v10k and confirm it with lg firmware website just google it )if not then U have to flash your home country's or open europe's baseband via Kdz flasher then flash the jellycast...!
Click to expand...
Click to collapse
I test many firmwares versions, I test open europe and firmwares of spain and always I have the problem.
The problem is in all roms based on cm9.
Sorry for my bad english
mjgs17 said:
I test many firmwares versions, I test open europe and firmwares of spain and always I have the problem.
The problem is in all roms based on cm9.
Sorry for my bad english
Click to expand...
Click to collapse
seems to be a odd problem did u try crossbreeder?
(this for the 3g btw)
http://forum.xda-developers.com/showthread.php?t=2113150
Problem
drkingtech said:
seems to be a odd problem did u try crossbreeder?
(this for the 3g btw)
http://forum.xda-developers.com/showthread.php?t=2113150
Click to expand...
Click to collapse
Thanks you but I dont understand well that is the crossbreeder my level of english isnt be very well and i dont understand this.
mjgs17 said:
Thanks you but I dont understand well that is the crossbreeder my level of english isnt be very well and i dont understand this.
Click to expand...
Click to collapse
just download cross breeder installer
http://forum.xda-developers.com/attachment.php?attachmentid=2086051&d=1372770386
crossbreeder uninstaller
http://forum.xda-developers.com/attachment.php?attachmentid=2086052&d=1372770386
copy them to the sdcard
go cwm wipe cache/dalvik cache install from sdcard-select the CrossBreeder_7.2.13.zip and flash it
reboot device
open the terminal emulator and type and check the codes given on the page
1. VALIDATION and TROUBLESHOOTING:
You can check your DNS boost functionality by running the following command:
Code:
getprop net.dns1
It should report 0.0.0.0
Then to verify Adblock you can select any one host from the blocked hosts file using the command:
Code:
tail /etc/CrossBreeder/dnrd_root/master
Pick one from there and browse to it in your browser. You should get a blank space
If you're experiencing any issues with your tethering, then you can first try and disable the tethering using:
Code:
su -c /system/etc/CrossBreeder/REMOVE_TETHER_BOOST
and rebooting.
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/INSTALL_TETHER_BOOST
and rebooting.
Similarly if you're getting any issues with browser not reaching pages etc. then you can try and disable the entire DNS speedup functionality using:
Code:
su -c /system/etc/CrossBreeder/REMOVE_DNS_CLIENT
and rebooting.
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/INSTALL_DNS_CLIENT
and rebooting.
Also of note is the Adblock feature. CrossBreeder now uses it's own Adblock file in /etc/CrossBreeder/dnrd_root/master ( NOTE - CHANGED FROM PREVIOUS VERSION). It also serves up these blocks in a clean blank format so you don't get an ugly 'Page not found' error instead of every ad. This is quite unique. If you want to disable Adblock to save around 3 MB of RAM on low end devices, you can run the command:
Code:
su -c /system/etc/CrossBreeder/DISABLE_ADBLOCK
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/ENABLE_ADBLOCK
The biggest improvements are in general usability of apps, both local and network based.
2. You can check your entropy values with this tool:
http://play.google.com/store/apps/de...ndentropyavail
or use this method for more fine grained graphs: http://forum.xda-developers.com/show...php?p=38509664
You should get values moving to 4000 regularly with this mod.
Also of some use is this Lag Test app: Lag Test http://db.tt/eBHYJWYn ( Thanks MW86 ). This is for generally testing the CPU based GUI rendering functionality. The aim is to approach 60 fps, but there isn't a guaranteed correlation with CrossBreeder and your FPS result as of now. It is mostly related to your Governor but CrossBreeder certainly helps.
2. If for some reason, your entropy values aren't hovering around 4096 then the app most probably didn't start automatically. You can try and run it manually using:
Code:
su -c "/system/etc/CrossBreeder/zzCrossBreeder FORCE"
If the entropy values go up to around 4096 and stay there, it's working. CrossBreeder is now in it's separate directory and not dependent on your init.d support. You can make it run automatically on boot using an app like SManager from the Play store, just remember to check both 'BOOT' and 'ROOT' for the execution.
3. If you're still getting issues, you can run the collection script:
Code:
su -c /system/etc/CrossBreeder/CHECK_PROCS
(if it hangs you can close the window and run it again) and post the resultant /data/cb_CHECK_PROCS.log file here in this thread or anywhere else and post here pointing to it please. I will try to find a solution or post a bugfix soon.
You can also disable CrossBreeder if you have any problems using:
Code:
su -c /system/etc/CrossBreeder/DISABLE_CROSSBREEDER
4. If you tried (2) and (3) above and it still doesn't work for you or you would still like to uninstall the mod, then please flash the CrossBreeder_Uninstall.zip.
Click to expand...
Click to collapse
Hope u understand...cant get clearer than this lol..!
Problem
drkingtech said:
just download cross breeder installer
http://forum.xda-developers.com/attachment.php?attachmentid=2086051&d=1372770386
crossbreeder uninstaller
http://forum.xda-developers.com/attachment.php?attachmentid=2086052&d=1372770386
copy them to the sdcard
go cwm wipe cache/dalvik cache install from sdcard-select the CrossBreeder_7.2.13.zip and flash it
reboot device
open the terminal emulator and type and check the codes given on the page
Hope u understand...cant get clearer than this lol..!
Click to expand...
Click to collapse
Thank you I understand this
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa5 v1.3 is a Lollipop ROM for Sero 7 Pro owners worldwide. It focuses on core functionality that must be built-in and relies on 3rd-party apps to provide features that can be added-on. This release also offers a version of TWRP Recovery that is compatible with all models of the S7P.
Key Features
International Support - a single ROM for all Sero 7 Pros sold worldwide (US, UK, Australia, Germany, and elsewhere)
Speed Control - speed when you need it and stock performance when you don't
OTG Charging - charge the tablet while an external device is attached to the USB port
Flexible Formatting - full support for both F2FS and EXT4 on your internal storage, and exFAT/FAT32/NTFS/F2FS/EXT4 support for external storage
Installation
First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install TWRP or Philz Touch Recovery
Users outside the US must use the DoPa versions of these recoveries to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use them just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install TWRP or Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip the recovery zip and put the .img file (twrp.img or philz.img) in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter, as appropriate, fastboot flash recovery twrp.img or fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then either the TWRP or Philz menu
CWM
If you have CWM installed, copy your choice of recovery zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the TWRP or Philz menu
Regardless of how you install your chosen recovery, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
using Philz, select "Backup and Restore", then "Backup to /storage/sdcard1" -if there's enough space on the card, the backup will start without any further prompt;
using TWRP, select "Backup", then tap "Storage" (halfway down the screen) and ensure that "sdcard" is selected; on the previous screen, swipe the slider to start the backup;
it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: for TWRP, you can check "Enable compression" on its main backup screen; for Philz, select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
STEP 3: Install the DoPa5 ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See the TK Gapps thread for details. I recommend the "Nano Modular" package which gives you the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
using TWRP, select "Wipe", then "Format data"; on the next screen type "yes" to confirm you want to proceed;
using Philz, select "Wipe and Format Options", then "Custom Format Options"; next select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice;
return to the main menu
using TWRP, select "Install"; at the top it should show "Storage: sdcard" - if not, tap there and change the setting
using Philz, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp511-dopa5-v1.3.zip, then OK your choice - the install process should take about 40-60 seconds
next, install your Gapps package
return to the main menu, select "Reboot" then "System" if using TWRP, or "Reboot System Now" for Philz, then hold your breath for the next 3-4 minutes
the Hisense screen should be up for 30 seconds, followed by the DoPa boot animation for another 3 minutes
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
UK, AU, and DE users must use the DoPa versions of TWRP or Philz Touch to install the ROM because they are the only ones compatible with your tablet. US users can use any SELinux-enabled version of CWM, Philz, or TWRP.
from DoPa5 AOSP Lollipop ROMs - no need to wipe or format anything!
from DoPa AOSP Kitkat ROMs (v1.0-v2.7) - a clean install is recommended but not required
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp511-dopa5-v1.3.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa5-v1.3.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed TWRP or Philz Touch Recovery, please do so first.
TWRP
make a backup to your external SD card
select Wipe then Advanced Wipe
select the partition to reformat, then tap Repair or Change File System
on the next screen, tap Change File System, then F2FS (or EXT4 to restore the default file system)
swipe the slider below to start formatting
when done, use the Restore option on the main screen to restore the contents of the partitions you reformatted
Philz
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Changes since DoPa5 v1.2
Xposed and GravityBox - these staples of the DoPa KitKat ROMs are back and preinstalled to provide all the tweaks you want - and none of the ones you don't
ArchiDroid Optimizations - this version of Android was built using gcc 4.9 and is highly optimized thanks to settings provided by JustArchi. To help ensure stability, the kernel uses standard optimization levels but is better tuned to our Cortex A9 processor due to the use of linaro 4.9 (a version of gcc optimized for ARM processors).
No Odex-ing - odex-ing has been abandoned because Xposed recompiles all apps, making the .odex files redundant. There should now be enough space on the /system partition to install the TK-Gapps Micro package.
Adaptive Brightness - a longstanding bug that could cause the screen to go black has been fixed. Overall brightness levels have been adjusted to provide greater dynamic range in low lighting conditions.
Notes
Xposed - having the Xposed framework installed shouldn't cause any issues, but if you wish to remove it you can do so using the xposed-uninstaller available in the Xposed XDA thread. The Xposed Installer and GravityBox apps will remain but will be inactive - you can use a root-enabled filemanager to remove them if you wish.
Encryption - if you wish to encrypt your /data partition, you must first use Philz Recovery to format it. Using TWRP to format may cause the partition to become un-decrytable, resulting in the complete loss of all your data. This is NOT an issue if you don't plan to use encryption.
WiFi Display - end a WiFi Display session from your television, not the tablet; doing so from the tablet may cause it to lock up. Chromecast is reportedly not subject to this issue.
USB Audio - booting up with a USB audio device attached may result in a bootloop.
Gapps - due to limited space on the /system partition, the TK Gapps's "Mini Modular" and larger packages will not install. I suggest using the "Nano" package, then downloading those apps you really want from PlayStore.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp511-dopa5-v1.3.zip the full ROM
sero7pro-nexus7spoof-dopa-v1.3.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-twrp287-dopa5-v1.3.zip a customized version of TWRP Recovery v2.8.7 usable on all versions of the Sero 7 Pro
sero7pro-philz6.58.0-dopa-v2.7.zip the final version of Philz Touch CWM-based Recovery v6.58.0 compatible with all models of the Sero 7 Pro
TK Gapps an XDA thread with links to various Gapps packages
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to a previous version (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
XDA:DevDB Information
Sero 7 Pro (US/UK/AU/DE) - DoPa5 AOSP, ROM for the Android General
Contributors
dolorespark
Source Code: https://github.com/dolorespark
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v1.3
Stable Release Date: 2015-09-26
Created 2015-01-28
Last Updated 2016-01-02
Reserved
Thx for all your hard work
on these tablet
Thx
ok, so I have a question or several as I remember them...
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models.
Has this been fixed yet?
If not, is there a workaround?
If so, what is it?
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Also, can the cpu be overclocked beyond 1.5 Ghz?
If so, is this already enabled, or is there some magic involved?
I really liked the beta 4 (beta r3) Rom and the way it looked, felt, and ran.
I found it to be better at managing free memory than kitkat in that I had at least 50% more free ram than Kitkat. I believe this contributed to some of the performance increase. But I had a hard time with the Google Play Movies bug. And some people were saying it was a general problem within the os's video subsystem.
Legend, keep up the great work
Excellent work! Looking forward to this!
Sent from my Nexus 7 using XDA Free mobile app
alpurl said:
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models. Has this been fixed yet?
Click to expand...
Click to collapse
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug. Here's the fix - install it from Recovery:
sero7pro-video-drm-fix-dopa5-v1.0.zip
I'll repackage the main ROM in the near future to include this fix, but first I want to investigate a few possible problems I noticed while getting this fixed.
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Click to expand...
Click to collapse
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off. If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Also, can the cpu be overclocked beyond 1.5 Ghz?
Click to expand...
Click to collapse
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Loving the first build. Very silky smooth speed and pretty stable as well as far as Lollipop is concerned at this point. As far as themes are concerned I haven't had too many issues using them on the current CM12 nightly for the Sero 7 Pro despite the DPI difference. Can't wait to see where this goes from here. Thanks for all the hard work! :highfive:
dolorespark said:
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Click to expand...
Click to collapse
Well, on nVidia's page it recommend a maximum of 1.6 GHz, so 1.7 is not too much of an overboard if Hisense had built these units well enough. However, even with 1.5 GHz the chips is already running uncomfortably hot so it would be wise to back off from any higher clock. I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz? (granted that there would be a possibility of artifacts )
dolorespark said:
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug.
Click to expand...
Click to collapse
Being under that magic number of 10 posts, I couldn't post this in that main thread, and when I tried to post in the q&a thread where "reply" sent me, the forums bot catcher tripped me up.
Thanks, that worked like a charm.
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Click to expand...
Click to collapse
To my knowledge, they don't, or at least I haven't figured that part out yet. Haven't figured it out in trickster mod either. I'll try the code. I only remember seeing one init.d file, does it matter where in that file I add the code?
Yeungers said:
on nVidia's page it recommend a maximum of 1.6 GHz
Click to expand...
Click to collapse
The Tegra3 is a family of SoCs with models designed for mobile, automotive, and embedded use. Ours is the low-power mobile version. Some variants do have higher maximum clock speeds but they use more power at every frequency step than ours.
I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz?
Click to expand...
Click to collapse
Possibly. The original overclock patch just upped the GPU speed to 520mhz without increasing the voltage any - and that seemed to work. When I rewrote the o/c code, I increased the voltage when running at 520mhz for what I considered solid reasons, Since it now has more power, I suspect I could up the speed somewhat without causing problems. However, even at a higher speed, it's still going to be an also-ran in today's market.
alpurl said:
dolorespark said:
If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
Click to expand...
Click to collapse
Having some other app set the CPU or GPU speeds isn't going to make it any more or less stable than having the built-in facility do it.
Be aware that if you're trying to use one of these apps to set the Interactive Governor's parameters, you're wasting your time. Not only does our Interactive Governor NOT work like you'd think - and not work like other implementations - it's totally ineffective. Every time the kernel brings another core online, it kicks all cores to the maximum allowed speed, totally sabotaging the governor's efforts. If you use Trickster to track the time at each speed, you'll see that the bulk of the time is spent either at very low speed or max speed, with all the intermediate speeds hardly used at all.
I only remember seeing one init.d file, does it matter where in that file I add the code?
Click to expand...
Click to collapse
Create a new file named, f'rinstance. "02gpuspeed". Put "#!/system/bin/sh" on the first line, then the code I provided on the following lines. The files will be executed in alpha-numeric order: 00banner, 02gpuspeed, 99SuperSUDaemon. Be sure to set its permissions to '755' so it is executable.
I pretty well figured that would be the case, but...
Based on my somewhat limited understanding ,If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise. Based on my pc understanding, conflict equals poor performance and instability.
And it was honestly one where I was using performance settings for the gpu, and then one of the other apps for the cpu.
So, I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable. So I was asking about how to get the higher gpu clock without using the cpu overclock portion of the performance tab.
You pretty well answered that, and I thank you.
Now, do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520?
Also, I don't understand setting permissions to 755. I understand setting read, write, own, etc, but not 755, if that's the case, then what app do I use for that? I created the file as a blank text document on my tablet directly and input the code there, then rebooted. Or did I screw the pooch on that one?
Sadly, I know nothing about the individual governor settings within each governor configuration. Therefore, I figure that the wisest and safest course of action is to leave it alone. It's easier and safer to work with the stuff I DO know until I can get feedback and advice from someone who DOES know.
I realize that some of this may seem stupid to you, but it's the only way I know to learn.
I will make another post later when I have more time to comment on some other things I keep seeing and would like to know what to do there.
alpurl said:
If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise.
Click to expand...
Click to collapse
The CPU/GPU settings on the Performance page are set-and-forget values. They simply set the maximum speeds once bootup is done, and again when you display that page. They don't monitor anything - the CPU governor does that, and it is constrained by these settings. The corresponding settings in the other apps you've tried operate the same way.
You should be aware that the "performance" governor is really no governor at all. It simply sets the processor to the maximum permitted speed and never changes it. On the whole, this governor generates more heat than performance.
I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable.
Click to expand...
Click to collapse
This strongly suggests that your device really can't handle the higher speed - at least when the CPU is running full-bore at all times. You may want to search for the postings in some of the early S7P threads where people described attaching copper foil to the SoC to dissipate excess heat.
do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520? Also, I don't understand setting permissions to 755.
Click to expand...
Click to collapse
Anything after a '#' in a shell script is a comment. As to '755', that's "read/write/execute" for the owner, and "read/execute" for the group and other users. Do a search for the 'chmod' command for more details on setting and interpreting Unix permissions.
Ok, that's fair enough.
Occasionally, I'll boot and get an error that the process called system is not responding and then it wants to know if I want to wait, or close it. It will do this every subsequent boot until I wipe cache and Dalvik (because I end up doing both out of habit) from recovery and then all is well again for several boot cycles where we start up again.
What am I missing here?
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Sent from my XT1034
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Click to expand...
Click to collapse
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on.
Click to expand...
Click to collapse
AngryManMLS said:
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
Click to expand...
Click to collapse
Of course you're welcome to discuss RRO - especially since it gives me an opening to throw in my 2 cents
Runtime Resource Overlays provides a way to override and/or replace the "resources" (icons, layouts, colors, strings, and fixed values) that are built into an .apk file. Since the resources used by Android itself are packaged into an .apk, you can modify the OS as well as individual applications.
RRO has been around for a long time but no one other than Sony ever used it. BitSyko's greatest contribution has been to make people aware that it's a superior way to do theming which is already built into the OS and is fairly easy to use. Unlike CM's theme engine, no custom code is required.
Beyond that, their contribution is somewhat less revolutionary than their many admirers seem to think. Their efforts are directed primarily at ease of use. The Layers app is essentially a file manager that makes copying themes into place a bit easier. What the app does you can do yourself using ESFileExplorer or ADB (though without some niceties they've added).
Their tweaks to the OS are designed to make life a bit easier for themers by changing hard-coded color values into "symbolic references". In other words, rather than specifying the color for each checkbox, you say each one should be the "checkbox_color", then define what that means somewhere else. That way, rather than having to modify the color of many different checkboxes, you change the definition of "checkbox_color" once and they all become that color.
Now, as to what all this means to the Sero 7 Pro and the DoPa5 v1.0 ROM... I delayed the ROM's release for several days until I could get their patches in place and tested, so this facility is in there and ready for use. The problem is that none of the themes I've seen really support the S7P. Any color changes a theme makes will show up just fine (I'm using someone's orange theme currently). However, all the icons are targeted at higher resolution screens than ours, so the OS ignores them and uses the same ones it has always used. If you can find themes for the Nexus 7, or some of the older Asus or HP tablets that also have a 1280*800 screen (213dpi), they should work just fine.
FYI... if you want to install a theme without using Layers, create an 'overlay' directory in '/system/vendor' (i.e. '/system/vendor/overlay'). Next, get some theme packages from this thread and unzip them. Select the .apk files you want, copy them into the 'overlay' directory, then reboot. If you don't like the result, delete them and reboot again.
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
AngryManMLS said:
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
Click to expand...
Click to collapse
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Sent from my XT1034 using XDA Free mobile app
kenundrem said:
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Click to expand...
Click to collapse
That would be amazing if you could. Here is an example of what I mean as well.
http://forum.xda-developers.com/android/themes/theme-dark-holo-theme-v1-0-01-25-15-t3012227
It takes half of the total memory by system itself for 4gb ram phones .
That's left only 1~1.5gb if some user servers app.
It greatly reduces mutil-task abilities for 4gb ram phones.Once I thought :victory: for 4gb.
The memory took by system cannot be released by mutil-apps ,apps that just kill processes to each other.But it can be released by single one large memory starved app, like games.
That inspired me to find a way that easy to reproduce.
By searching some,I found this one:
https://unix.stackexchange.com/questions/99334/how-to-fill-90-of-the-free-memory/99435#99435
The answer "tail /dev/zero" did the trick.
On android,I use Termux to execute this command.
With the combination of totalcommander , it can be done easier.
In totalcommander ,add a new 'sh command' :
Code:
am start -n com.termux/com.termux.app.TermuxActivity
sleep 1
input text 'tail /dev/zero'
input keyevent 66
exit the termux, wait a few seconds, it should be done for you.
If you look at the "running servers" in developer mode,you'll see that system's memory usage shrinks down to 700+mb.And of course not that low , it will take up to 1.3gb around.
After a month observation, it all works well for released about 500mb from system.
This command not only releases system memory,but also releases ui resources of user server apps. So I recommend that starting all user service apps including servers by termux , then execute this command.
(This command will not kill servers hold by termux , but "</dev/zero head -c 4000m | pv | tail" this one will. So,the better choice is the "tail /dev/zero")
For better multi-task experience, also recommend to set /sys/module/lowmemorykiller/parameters/minfree to
2048,4096,8192,16384,24576,32768
That's 8mb,16mb,32mb,64mb,96mb,128mb in app kernel adiutor.
(set enable_adaptive_lmk to 0 and vmpressure_file_min to 33280 (130mb) too)
can u build a flashable zip?
how to revert to default ?
Enmaulana_ said:
how to revert to default ?
Click to expand...
Click to collapse
If you want something about "tail" to be default, basically you don't need to do anything.
A reboot should make all back if you want.