Related
{
"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"
}
Before we get to the mod, I want to get a little personal. I make these mods so that your Android experience will be enhanced. If you find something wrong with the mod then provide constructive criticism. Don't just sit there behind your computer and degrade the effects based on what you see in the code, especially if you are even unwilling to try the mod in the first place. That irritates the hell out of me and unfortunately, I can't help you with your issues...so do yourself and others a favor and either use the mod and provide constructive criticism such as results (positive or negative) or ways to improve it or don't use it at all. That being said, these tweaks work in conjunction with each other, they are not each meant to increase your battery life.
This is 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. The increase in battery life may not be "tenfold" for you, but it does increase, which is still better than not increasing. Contact me before including it in your own ROM (that you plan on publicly releasing). I will allow you to use it, just ask first. 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 - Updated May 3, 2012Requirements:
HTC Incredible (preferably)
Kernel with zram swap (for swappiness)
Kernel with init.d support
Currently working on:
HTC Incredible - Anthem, Clutch, AOKP, ICSenseless
HTC Amaze 4G
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.sched_compat_yield=1;
kernel.panic=5;
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;
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;
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.sched_compat_yield=1
kernel.panic=5
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
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.
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.
I would be stoked if someone made a flashable zip for me to try
Sent from my ADR6300 using XDA
Could you please explain how this will increase battery life? And if it can be used in other phones?
Sent from my ADR6425LVW using XDA
Does this work on x10 mini with miniCM by NAa ?
I have sysctrl.conf file and when open it with rootexplorer its empty .
Can I add this lines from phone ? Copy/paste them into the files whith rootex ?
Pls answer me and thk U .
Sent from my E10i using xda premium
how do we know if our rom has init.d support?
do we have to ask the rom creator or is there a way to check
Is this already included in your Clutch Rom as well?
Sent from my HTC Droid Incredible using XDA
OMG_VTEC said:
how do we know if our rom has init.d support?
do we have to ask the rom creator or is there a way to check
Click to expand...
Click to collapse
You should have a line in /init.rc with busybox run-parts. To check the easiest way may be from the terminal:
Code:
grep busybox /init.rc
and look for a line like this:
Code:
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
graymonkey44 said:
Could you please explain how this will increase battery life? And if it can be used in other phones?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Trust me it works, I had over 20+ hours at a semi heavy use.
Sent from my ADR6300 using Tapatalk 2
withbloodskies said:
Trust me it works, I had over 20+ hours at a semi heavy use.
Click to expand...
Click to collapse
Was there any system performance degradation and/or instability?
Would someone knowledgeable be willing to give an overview description as to what the proposed changes effect?
Would also like to know if this could be done from phone.
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. Giving credit would be nice
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, post 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;
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/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
sysctl -p is what initializes the code.
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.
Click to expand...
Click to collapse
Would this work on my HTC Inspire 4g?
Sent from my HTC Inpsire 4G using XDA
Would this work on my HTC Inspire 4G?
Sent from my Desire HD using XDA
I will try this method, as do the necessary tests will comment if it works or not, Greetings!
Does this code change things like how often you're phone checks the cell tower? Have you experienced any missed calls if this is the case? 50+ hours of battery life sounds like it'd be worth the risk, just curious as to what this script is actually doing.
Sent from my ADR6300 using XDA
ferotakis said:
Does this work on x10 mini with miniCM by NAa ?
I have sysctrl.conf file and when open it with rootexplorer its empty .
Can I add this lines from phone ? Copy/paste them into the files whith rootex ?
Pls answer me and thk U .
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Yeah you should be able to paste it with rootex and get it working.
david.degraw54 said:
Would this work on my HTC Inspire 4G?
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Yes it should. It works with mine lol
jprow507 said:
Is this already included in your Clutch Rom as well?
Sent from my HTC Droid Incredible using XDA
Click to expand...
Click to collapse
Yep
ChuckFarley said:
Does this code change things like how often you're phone checks the cell tower? Have you experienced any missed calls if this is the case? 50+ hours of battery life sounds like it'd be worth the risk, just curious as to what this script is actually doing.
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
Nope, no missed calls. Everything works fine after using this script. Basically, if you use this, you're just getting the same or similar battery life and performance experience of Anthem on different ROMs.
Can someone please explain what this exactly does to improve battery life?
Sent from my ADR6425LVW using XDA
graymonkey44 said:
Can someone please explain what this exactly does to improve battery life?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Yes please answer this.
And can someone make this into a flashable .zip?
PureMotive said:
Nope, no missed calls. Everything works fine after using this script. Basically, if you use this, you're just getting the same or similar battery life and performance experience of Anthem on different ROMs.
Click to expand...
Click to collapse
Wow, sounds too good to be true. I'm all in!
Sent from my ADR6300 using XDA
I'll update the OP later with an explanation.
Quick question about adding the code to the sysctl.conf file: Do you completely replace the existing code with your suggested code, or append yours to the existing?
This ROM is stock XT862 5.7.906 deodexed and meticulously optimised to make the lowest use of resources possible.
The zipfile download is just 75.9Mb - everything unnecessary has been removed, many resources hand optimised and blur/moto apps replaced where better alternatives exist.
Features :-
- All hardware, camera/camcorder, sensors, GPS, bluetooth, LEDs, HDMI etc working
- Reboot+screenshot on power menu
- MMS from CM7
- Calendar from CM7
- Networklocation fixed
- Minimum and auto brightness lowered to increase battery life with screen on
- Calculator replaced with latest (2012-12-20) MobiCalc (Scientific calculator with DEC/BIN/HEX conversion)
- Blur Setup removed
- Uses standard android account+sync settings, no more need for Blur services
- optimised blurphone/dialer UI
- black themed notification bar
- vol up/down wake
- Optimised Flash player (You must reboot once for it to work)
- HDMI fixed and fully tested now
- Smooth scrolling patch from MrObvious
- Camera from Atrix, hacked for 100% jpeg quality, added fps lowlight patch in 1.65
- Gallery replaced with QuickPic
- N1 Magic Alarm replaces Blur Alarm Clock, which was very big and slow for a simple alarm app.
- ICS iconset
- Pre-rooted
- Default browser forced to desktop view and always shows debug menus
- 1% battery (using icons lifted from mavrom's framework-res.apk)
- Notification power toggles from Steel Droid 4.8
- Very minimal Gingerbread Google Apps - much smaller than the one on goo.im
- Email app from CM7, syncs contacts/calendar/email from MS exchange, Office365, Gmail, Hotmail or any POP3/IMAP account
- Total control of over/under clocking/volting
- Busybox 1.20 replaces all binaries wherever possible (lowers disk/mem/cache usage)
- Latest Holo Launcher (2013-01-06) pre-installed and updatable
- DSPManager
- FMRadio
- Quickoffice (we have a license for this as part of stock ROM, so well worth having)
- Terminal emulator (2013-01-06)
- One alarm tone "alarm classic", one ringtone "ring", one notification tone "bells"
- No bootanim/sound (shows default android logo)
- init.d support
- command line tools
---- "rw" - read/write system
---- "ro" - revert to read only
---- "ssh"/"scp"
---- "zip" - create archives from cmd-line
---- "ash" as default shell using busybox
---- "zipalign" - force zipped APK contents to 32-bit boundaries for better use of RAM
---- "repack_apks" - rezip and zipalign a dir full of apks, cd to /data/app and run it to optimise apps downloaded from market
More details, credits, how-to for overclocking etc in 2nd post.
DOWNLOAD LINK - UPDATED v1.7 - Network location fixed, optimised camera and framework-res, icons from lotzakritters, updated hololauncher, terminal, superuser, flash mod, removed unused ducati binaries, removed unused libs, added reboot+screenshot, removed VZW location services and lots more optimisations.
http://d-h.st/bI1 - XT862 version
http://d-h.st/SOc - XT860 version, thanks to docardoso, updated to fix keymap
****FLASHING INSTRUCTIONS - IMPORTANT THESE ARE SPECIFIC TO MINIMOTO ROM****
This ROM should work with safestrap 2 or 3, but has only been tested on v3.05.
To flash, first create a ROM slot in SS3, activate that slot, wipe data, then install the ZIP.
Do not clear data again after installing - this ROM installs some necessary files to the /data partition.
Credits/Howtos
Credits :-
Hashcode - for every single thing that makes this phone still worth having. Particularly safestrap3, which allows me to mod ROMs on the train to/from work and still have a working phone the rest of the time
Buckmarble - for mavrom - I used Buck's /etc directory as a quick way to get this bootable under safestrap, and the battery icons from his framework-res.apk
http://forum.xda-developers.com/showthread.php?t=1612537
Chevycam94 - for Steel Droid ROM - I used his SystemUI.apk file to add power toggles.
I've used Chevy's to save time, but plan to do my own later with less theming.
http://forum.xda-developers.com/showthread.php?t=1278056
Opptimizer projekt - for the overclocking kernel modules
http://code.google.com/p/opptimizer/
Cyanogenmod team - for their fantastic mail/calendar/mms apps
http://www.cyanogenmod.org/
Motorola - for making all our lives more difficult
http://www.motorola.com
How-tos :-
===Over/Under Clock/Volt===
You can find a template overclocking script in /etc/init.d named "02overclock".
By default, all the options are commented out.
The script includes example values tuned for my specific CPU, so yours will probably not work with these values, but it also lists the default moto values for reference.
While testing, copy the script to /data and run it from there - don't put testing values in /etc/init.d or your device may bootloop.
To edit the script, type "rw" in terminal to enter read/write mode, then make the changes you want using your favorite text editor.
First, uncomment these lines
#echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo 1 > /sys/devices/system/cpu/cpu1/online
#insmod /system/lib/modules/symsearch.ko
#insmod /system/lib/modules/overclock.ko
#echo hotplug > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Then start trying various settings for the 0,1,2,3 Steps of CPU scaling.
See the following article for details on tuning the VSEL and clock speeds to your device - proceed with caution.
http://rootzwiki.com/topic/14511-opptimizer-projekt-milestone-overclock-for-omap4-devices/
Once you have a stable set of values, in terminal "cp /data/02overclock /etc/init.d" and reboot.
Now your phone will apply these values on every boot.
Sounds cool, might give it a shot.
Couple of cuestions:
what launcher does it have? ( I know I could easily replace it, but, just curious )
since it's deodexed, do you reckon rom toolbox themes would work?
thingonaspring said:
This ROM is stock XT862 5.7.906 deodexed and meticulously optimised to make the lowest use of resources possible.
The zipfile download is just 99.5Mb - everything unnecessary has been removed, and blur/moto apps replaced where better alternatives exist.
Features :-
- Pre-rooted
- Very minimal Gingerbread Google Apps - much smaller than the one on goo.im
- Email app from CM7 - syncs contacts/calendar/email from exchange, office365, etc, also supports gmail and hotmail (works for me even without a "plus" account!)
- Total control of over/under clocking/volting
- Busybox replaces all binaries wherever possible (lowers disk/mem/cache usage)
- Latest (2012-11-07) ADWLauncher pre-installed and updatable (fast stable modern launcher)
- DSPManager (replaces "audio effects" from stock)
- FMRadio
- Quickoffice (we have a license for this as part of stock ROM, so well worth having)
- Terminal emulator
- One alarm tone "alarm classic", one ringtone "ring", one notification tone "bells"
- No bootanim/sound (shows default android logo)
- TCP/Filesystem/VM tweaks
- init.d support
- command line tools "rw" - read/write system, "ro" - revert to read only, "ssh", "scp", "zip", "ash" as default shell (busybox)
- All hardware, camera/camcorder, sensors, GPS, bluetooth, LEDs etc working
More details, credits, how-to for overclocking etc to follow.
DOWNLOAD LINK
http://www.multiupload.nl/652II0AO7F
****FLASHING INSTRUCTIONS - IMPORTANT THESE ARE SPECIFIC TO MINIMOTO ROM****
This ROM should work with safestrap 2 or 3, but has only been tested on v3.05.
To flash, first create a ROM slot in SS3, activate that slot, wipe data, then install the ZIP.
Do not clear data again after installing - this ROM installs some necessary files to the /data partition.
Click to expand...
Click to collapse
Launcher - ADW, latest as of today.
Theming - should be possible, only some static resources in framework-res.apk have been modified, which I don't think will cause any problems.
I'll update 1st and 2nd posts with a lot more info in a few hours, am at work right now, so not cool to be spending too much time on forums.
If I understand correctly this is NOT overclocked by default?
Sent from my XT860 using xda premium
It looks fine so far, with one major exception: there is no settings->accounts & sync, so, since GMail is not installed by default, I cannot set my GMail account to sync after installing the app. (I do like to tweak these settings, so I'd have to see it back.)
Also, settings->battery & data manager->battery mode force closes (not a huge issue). Settings->battery & data manager->data delivery->Social applications force closes (expected that one.) If there is a way to disable these menu items, that would be a good thing - nobody like to get an FC.
Also, like Maverick, the default typeface dos not distinguish visibly between normal and bold type. In GMail, it is nearly impossible to tell which conversations have unread messages and which do not (unread have bold type on stock.) You can sort-of tell because unread and read conversations have a slightly different background, but it's too subtle to tell at a glance - you really have to look to see the difference.
Nice to see a new rom development
@Endoroid Yep - not overclocked by default - you need to tune the overclock script in /etc/init.disabled/02overclock, testing carefully. Only when you have good settings for your CPU should you copy that script to /etc/init.d so it applies on boot.
@doogald
settings->accounts & sync - I'd recommend using the built-in email client. It handles gmail really well and has sync settings in the app.
settings->battery & data manager->battery, settings->battery & data manager->data delivery->Social applications force closes, yep both those features are removed. I'll look into tidying up the XML so it no longer shows those settings.
A patch release has just been uploaded to the OP, its a fix for headphone connectivity, well worth having.
Next target is a tidyup of the settings menus and an effort to get notification power widget and better battery/signal indicators.
Meanwhile - does anyone know of a source for a better built-in browser APK?
The D3's default one doesn't remember mobile/desktop useragent settings, so I usually end up installing Opera instead.
it will be great if you add more languages to it....
thingonaspring said:
Meanwhile - does anyone know of a source for a better built-in browser APK?
Click to expand...
Click to collapse
how about dolphin? its very fast, and has a lot of enhancements.
thingonaspring said:
@doogald
settings->accounts & sync - I'd recommend using the built-in email client. It handles gmail really well and has sync settings in the app.
Click to expand...
Click to collapse
Thanks. I'll look at the email app, but I generally prefer the GMail app for important message support, etc. Second, I like to tweak the sync settings at times - turn off Google+, for example, or turn on Picasa if I am looking for photos that I know I have online, and then turn it off when I don't need it (most of the time). There are other apps that store sync settings in settings->accounts, such as Dropbox, so I'd like/need to have those settings exposed. Also, I know that some people like to sync Facebook or Twitter contacts.
Lastly, thanks for taking the time to develop this. It's great to see another ROM choice.
boazal said:
it will be great if you add more languages to it....
Click to expand...
Click to collapse
Hehe - so far I've been removing languages. It might be possible to make flashable language packs for it, I'll see if anyone's done something simillar.
@doogald
There are other apps that store sync settings in settings->accounts, such as Dropbox
Click to expand...
Click to collapse
Hmm, that does make sense yes. I'll have a look at reinstating it.
doogald said:
Thanks. I'll look at the email app, but I generally prefer the GMail app for important message support, etc. Second, I like to tweak the sync settings at times - turn off Google+, for example, or turn on Picasa if I am looking for photos that I know I have online, and then turn it off when I don't need it (most of the time). There are other apps that store sync settings in settings->accounts, such as Dropbox, so I'd like/need to have those settings exposed. Also, I know that some people like to sync Facebook or Twitter contacts.
Lastly, thanks for taking the time to develop this. It's great to see another ROM choice.
Click to expand...
Click to collapse
+1.
absolutely needed...
seems like global APNs were not set? I wasn't able to get 3G yet....
thingonaspring said:
DOWNLOAD LINK - UPDATED v1.01 patch release - Fixes headphone output (this is what we get for making last minute changes)
http://www.multiupload.nl/0VFD1QP9L6
Click to expand...
Click to collapse
Not to be rude, but that link doesn't work. It tries to redirect me to download some kind of client. 4 browsers have been tried.
thingonaspring said:
Hehe - so far I've been removing languages. It might be possible to make flashable language packs for it, I'll see if anyone's done something simillar.
@doogald
Hmm, that does make sense yes. I'll have a look at reinstating it.
Click to expand...
Click to collapse
Thanks, but could I reenable the account sync setttings somewhat urgently by myself?
I needed to set up for google+ instant upload, but G+ fc'd at settings... which seems related to this missing menu.
---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------
Cyrus221 said:
Not to be rude, but that link doesn't work. It tries to redirect me to download some kind of client. 4 browsers have been tried.
Click to expand...
Click to collapse
had the same experience, but i found the link when i used Firefox nightly.
Cyrus221 said:
Not to be rude, but that link doesn't work. It tries to redirect me to download some kind of client. 4 browsers have been tried.
Click to expand...
Click to collapse
I was able to download using the PutLocker link yesterday. I just tried again, and it worked. (Chrome on my Mac... I always use a computer to download and get to the device either by direct connect or via Dropbox.)
@Cyrus221
You're looking at the interstitial advert between multiupload and the actual download site. Click "Skip Ad" in the top right, then you goto the actual download.
Don't blame me, blame crafty tactics by multiupload's commercial partners.
@palmwangja
I've found the reason AccountAndSyncSettings.apk isn't simply working when I reinstate it - it depends on moto's "blur" account syncing engine, which is heavily woven into a lot of the stuff I've removed to make this rom so small and efficient in the first place.
If we enable that bunch of settings, then the rom loses much of its point - being small and fast.
Instead of that, I'm looking at getting CM7's apk for the same function to work instead.
thingonaspring said:
Instead of that, I'm looking at getting CM7's apk for the same function to work instead.
Click to expand...
Click to collapse
Thanks for taking the time to try this. If you can get CM7's to work, that could be a big plus.
thingonaspring said:
@palmwangja
I've found the reason AccountAndSyncSettings.apk isn't simply working when I reinstate it - it depends on moto's "blur" account syncing engine, which is heavily woven into a lot of the stuff I've removed to make this rom so small and efficient in the first place.
If we enable that bunch of settings, then the rom loses much of its point - being small and fast.
Instead of that, I'm looking at getting CM7's apk for the same function to work instead.
Click to expand...
Click to collapse
Thanks, sounds like a plan.
BTW, Will there be any chance of getting a widget on notification bar, just like any other ICS roms?
Your rom seems really promising, and can be one of the best daily driver.
Uninstall the rampig known as adblock plus, night and day difference. Use greenigy to Hibernate Google plus too! My tablet is now usable, and I was considering the n7 2013 because of how slow it was but now it is great
78mb of ram consumption is unacceptable, it's not even worth it. Epic fail for adblock
so what's using instead? adaway or adfree?
Glad I came across this post because I hadn't heard of Greenify before. My n7 is now virtually lag-free after installing that app. Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app
heatledger said:
so what's using instead? adaway or adfree?
Click to expand...
Click to collapse
There might be more elegant solutions, but arguably the lightest-weight and fastest method is simply using a hosts file (rooted devices only, /system/etc/hosts) that black-holes many many ad-serving/tracking domains to the loopback address on your device [127.0.0.1]
e.g. http://winhelp2002.mvps.org/hosts.htm
lightweight because the only thing added to your tablet is a single file.
fastest because DNS lookups on those domains return instantaneously, and IP RST occurs nearly instantaneously when your browser goes looking for a http server at 127.0.0.1:80 - there are no network delays in looking up and connecting/RST to blackholed servers - and no additional traffic interception app/services running on your device and pilfering system resources.
You will find that there are all sorts of tricks employed by various media sites that effectively check to see that cookies associated with ad-publishing/tracking domains have been set, so YMMV with respect to any ad-block method.
good luck
I'm not using any ad blocker right now because it makes the tablet virtually unusable with all the RAM consumption. Again Google Plus is also guilty of the same, taking up 40 megabytes of RAM and slowing down your tablet even though you are not using that app
Sent from my Nexus 4 using xda app-developers app
I'm glad that I could recommend that to you
Sent from my Nexus 4 using xda app-developers app
Our device only has 1 gig of ram 1 apps start taking up over 30 megabytes of RAM it definitely is a huge problem, not only that is completely unnecessary there's no reason that should be consuming that much
Sent from my Nexus 4 using xda app-developers app
When you think about it it's actually absurd, 78 megabytes of RAM just so that I don't see advertisements I'll just deal with the advertisements and have a smooth experience. The trade off is not good
Sent from my Nexus 4 using xda app-developers app
bftb0 said:
There might be more elegant solutions, but arguably the lightest-weight and fastest method is simply using a hosts file (rooted devices only, /system/etc/hosts) that black-holes many many ad-serving/tracking domains to the loopback address on your device [127.0.0.1]
e.g. http://winhelp2002.mvps.org/hosts.htm
lightweight because the only thing added to your tablet is a single file.
fastest because DNS lookups on those domains return instantaneously, and IP RST occurs nearly instantaneously when your browser goes looking for a http server at 127.0.0.1:80 - there are no network delays in looking up and connecting/RST to blackholed servers - and no additional traffic interception app/services running on your device and pilfering system resources.
You will find that there are all sorts of tricks employed by various media sites that effectively check to see that cookies associated with ad-publishing/tracking domains have been set, so YMMV with respect to any ad-block method.
good luck
Click to expand...
Click to collapse
Yep... this is the method AdAway uses to block adverts...
QUOTE: (from AdAway) "An ad blocker that uses the hosts file. The hosts file contains a list of mappings between hostnames and IP addresses. When an app requests an ad, that request is directed to 127.0.0.1 which does nothing. There are options to run a web server to respond to blocked hostnames and to direct requests to the IP address of your choosing. You can download hosts files from the app but it is possible to use your own and to add certain sites to the white- and black-lists."
With AdaAway installed on my Nexus 7 (and my other rooted devices), it uses no system resources at all (CPU/RAM etc.) until I actively run it (which I do every couple of weeks or so) to see if there any new hosts files updates available... and even then it only uses around 21Mb of RAM. After a reboot (necessary for the hosts files update to take effect), AdaAway is exited, and it no longer appears in a list of running processes... until it's run again to check for further updates. However, it does require root.
Rgrds,
Ged.
Um, ad blockers use zero ram unless you set them to stay active, such as to listen to local host. They copy a file and are done.
khaytsus said:
Um, ad blockers use zero ram unless you set them to stay active, such as to listen to local host. They copy a file and are done.
Click to expand...
Click to collapse
Hi, khaytsus...
That's certainly true of AdAway... but AdBlock Plus (the one the OP is referring to) runs as a background service... and filters ads out by routing internet traffic through a proxy.
AdBlock Plus' chief attraction lies in it not requiring root... but having just installed AdBlock Plus on my Nexus 7, and then running System Panel (from Playstore), I can see it hogging around 80Mb of RAM.
Though it really shouldn't cause the lag problems as described by the OP... given that the Nexus 7 is equipped with a gigabyte of RAM... and that within that context, 80Mb is a miniscule RAM requirement.
I have Dolphin Browser (with Jetpack) installed on my Nexus 7... and that routinely occupies anywhere from between 170Mb to 300Mb of RAM. Significantly more than the 80Mb used by AdBlock Plus... and I have no discernible lag.
So maybe AdBlock Plus is causing problems elsewhere... running the CPU into the ground maybe? Although I suspect that routing traffic via a proxy may be the cause of the reported lag.
Anyway... it seems that AdBlock Plus is the least optimal way of blocking ads (by routing traffic through a proxy), and running a constant background service whilst it does so.
The best way of blocking ads (IMHO), is to root the device, and then install AdAway (which just modifies the /system/etc/hosts file when AdAway is run).
And even if you automate the process of AdAway checking for updates, it appears this only happens upon boot or daily. It runs a check to see if there are any new hosts files updates available... informs you if there are... and then exits. It doesn't hang around in the background, 'listening' for updates, consuming system resources whilst it does so.
Rgrds,
Ged.
GedBlake said:
Hi, khaytsus...
That's certainly true of AdAway... but AdBlock Plus (the one the OP is referring to) runs as a background service... and filters ads out by routing internet traffic through a proxy.
Click to expand...
Click to collapse
AdBlock Plus can run as a service. It does not need to. Perhaps the OP isn't rooted.. But it's still nonsense IMO.
@GedBlake
Thanks for the informative posts man, you have enlightened me. I was completely unaware that adblock was running in the background. I used adaway and it seems that my browsing speeds seems to hasten up a little bit.
If you're rooted:
http://winhelp2002.mvps.org/hosts2.htm
1. Download and extract hosts file from that page.
2. If extracting from PC, transfer the file to the n7 via usb.
3. Use your fav root text editor and copy the contents of the hosts file to /etc/hosts
Note: You can exclude the introductory messages in the extracted host file n start from the 1st ip entry.
Reboot.
Tada...
Ram/proc/battery hit? Almost none!
If it doesnt work, let me know. Sometimes there is a problem on the formatting, i can fix it and upload a proper one for you to follow the steps again. Why? Android is more particular than windows or mac on the hosts file.good luck.
More info on hosts file, google or wikipedia
andrew9292 said:
If you're rooted:
http://winhelp2002.mvps.org/hosts2.htm
1. Download and extract hosts file from that page.
2. If extracting from PC, transfer the file to the n7 via usb.
3. Use your fav root text editor and copy the contents of the hosts file to /etc/hosts
Note: You can exclude the introductory messages in the extracted host file n start from the 1st ip entry.
Reboot.
Tada...
Ram/proc/battery hit? Almost none!
If it doesnt work, let me know. Sometimes there is a problem on the formatting, i can fix it and upload a proper one for you to follow the steps again. Why? Android is more particular than windows or mac on the hosts file.good luck.
More info on hosts file, google or wikipedia
Click to expand...
Click to collapse
Hi, andrew9292...
What you suggest will probably work... but it's like cutting the grass with a pair of scissors!... it's time consuming and labour intensive. And there are better tools available, more suited to the task.
AdAway will do the job for you, with minimal effort. And also, the one link you provide may not be sufficient to provide full ad blocking capability.
AdAway compiles the /system/etc/hosts file from four sources. These are...
http://winhelp2002.mvps.org/hosts.txt
http://adaway.sufficientlysecure.org/hosts.txt
http://hosts-file.net/ad_servers.asp
http://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext
As I've previously stated, AdAway consumes no system resources until the user chooses to run it... in order to update the /system/etc/hosts file. So there is no "Ram/proc/battery hit", as you put it... until AdAway is run.
This seems to me to be the far more easier option, than manually messing around with large text files, copying them into /system/etc and with the potential screwups and errors that might result.
AdAway is installed on all of my rooted devices, and I rarely give it a second thought.... until I remember that ad blocking needs updating ('cos I haven't run it for a few weeks), I then just run AdAway... it updates... and upon my next reboot, the update takes effect.
Result - no ads... no hit on battery/CPU/RAM... and no complicated messing around in /system/etc.
Rgrds,
Ged.
GedBlake said:
Hi, andrew9292...
What you suggest will probably work... but it's like cutting the grass with a pair of scissors!... it's time consuming and labour intensive. And there are better tools available, more suited to the task.
AdAway will do the job for you, with minimal effort. And also, the one link you provide may not be sufficient to provide full ad blocking capability.
AdAway compiles the /system/etc/hosts file from four sources. These are...
http://winhelp2002.mvps.org/hosts.txt
http://adaway.sufficientlysecure.org/hosts.txt
http://hosts-file.net/ad_servers.asp
http://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext
As I've previously stated, AdAway consumes no system resources until the user chooses to run it... in order to update the /system/etc/hosts file. So there is no "Ram/proc/battery hit", as you put it... until AdAway is run.
This seems to me to be the far more easier option, than manually messing around with large text files, copying them into /system/etc and with the potential screwups and errors that might result.
AdAway is installed on all of my rooted devices, and I rarely give it a second thought.... until I remember that ad blocking needs updating ('cos I haven't run it for a few weeks), I then just run AdAway... it updates... and upon my next reboot, the update takes effect.
Result - no ads... no hit on battery/CPU/RAM... and no complicated messing around in /system/etc.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thats nice bro! n im aware of it...i agree its a great app, does a wonderful job! Jus providing a manual method if anyone prefers it.
Pros, just some extra experience for the nerdy. This is xda anyway Cons, like you stated possible fakaps, time consuming, inadequate etc. Cheers :highfive:
THANK YOU!
Krooked22 said:
Uninstall the rampig known as adblock plus, night and day difference. Use greenigy to Hibernate Google plus too! My tablet is now usable, and I was considering the n7 2013 because of how slow it was but now it is great
Click to expand...
Click to collapse
OMG, thanks much for your post. I uninstalled adblock and installed Greenify, and it's like I finally have my N7 back again. I was close to junking it out of frustration but will keep it for a little longer now...
biggerguy_sf said:
OMG, thanks much for your post. I uninstalled adblock and installed Greenify, and it's like I finally have my N7 back again. I was close to junking it out of frustration but will keep it for a little longer now...
Click to expand...
Click to collapse
Awwww, if you'd waited a month it would have been a full year since the last post in this DEAD thread.
I modified host file and no problems so far...
Hello,
I have a simple question about the compilation in the cloud for wp8 apps. As detailed on the MS Blog post titled Compile in the Cloud with WP8, when a developer submits an WP8 (only) app to the store, the app is compiled in MDIL in order to optimize the subsequent execution.
Despite this, on my unlocked Samsung Ativ S I experienced that even in the case of wp8 app - and I mean, apps that target ONLY the WP8 platform - the DLLs are still in CIL and not MDIL, and so they can be easily decompiled with tool such as dotPeak.
My question is: where am I wrong?
Thanks,
Sandro.
.NET binaries have multiple pieces. One of them is the CIL, which is what something like dotPeek decompiles. There's also an area where JIT output can be stored, to speed up future execution. It sounds like what the Store is doing is JITing the apps for ARM processors, to reduce load time after installing (otherwise, JITing a large app on the phone can take a while; you can see this yourself if you ever sideload a large app). This slightly increases the size of the binaries, but improves performance. The CIL isn't removed though, either because they want to allow the phone to make different optimizations (for example, different amounts of CPU cache can effect when you would want to unroll loops or inline function calls vs. when you wouldn't) or just because the format of a .NET binary *expects* there to be CIL there.
GoodDayToDie said:
.NET binaries have multiple pieces. One of them is the CIL, which is what something like dotPeek decompiles. There's also an area where JIT output can be stored, to speed up future execution. It sounds like what the Store is doing is JITing the apps for ARM processors, to reduce load time after installing (otherwise, JITing a large app on the phone can take a while; you can see this yourself if you ever sideload a large app). This slightly increases the size of the binaries, but improves performance. The CIL isn't removed though, either because they want to allow the phone to make different optimizations (for example, different amounts of CPU cache can effect when you would want to unroll loops or inline function calls vs. when you wouldn't) or just because the format of a .NET binary *expects* there to be CIL there.
Click to expand...
Click to collapse
Can you please point me to any documentation that describes the .NET binaries format, in order to better understand the CIL and MDIL section and .NET binary structure in general ?
Thanks, Sandro
The ones I found were all pre-MDIL, I'm afraid. There's plenty of documentation of the general format of a PE binary - it's a public standard - but I'm not sure where the MDIL is stored, actually. I was mistaken about the normal JIT output; it's either stored in memory only for that process execution, or in an assembly cache (as when you run ngen.exe on a managed assembly).
*** Disclaimer
I am not responsible for any damage you made to your device.
Potential heat problems still there in this ROM.
If you unlock your bootloader from stock rom, be sure to backup your drm keys / TA partition in case you want to go back to stock ROM (otherwise drm keys are forever lost, and you may be missing camera features if you go back).
You have been warned.
Click to expand...
Click to collapse
I did a rebuild of LineageOS 18.1 with the sources of Berni-0815 and tarkzim, many thanks to them for their hard work!
SELinux: enforcing
Camera: Stock camera works ok at first glance (up to 8MP, camera.disable_zsl_mode=0 is set).
Small further tweaks in device/sony/kitakami-common/system.prop:
Spoiler
ro.config.hw_quickpoweron=true
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
power_supply.wakeup=enable
ro.config.hw_power_saving=1
ro.HOME_APP_ADJ=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
debug.performance.tuning=1
Flashing and tuning Instructions:
Clean flash advised.
From TWRP:
1. Flash ROM + optionally gapps in a row (read https://wiki.lineageos.org/gapps and https://forum.xda-developers.com/t/...-e6653-build-2022-11-18.4517491/post-87743699), Google app may cause high battery drain though (deactivate it if need be/Google Go being a possible alternative)
Click to expand...
Click to collapse
2. Optionally: Restart to recovery / TWRP, then flash magisk
Click to expand...
Click to collapse
Attached images showing sample setup with Google apps. MMApp is Magisk renamed apk.
Click to expand...
Click to collapse
Install Android System WebView Beta to get updates for WebView (or bromite webview and ff-updater app on F-Droid).
Install Google Google Go app if you want to use Google Assistant (Google app may cause high battery drain). Chimera seems to be possible to be disabled anyway: https://forum.xda-developers.com/t/...ry-drain-due-to-google-play-services.4406617/ (edit: disabling chimera seems to cause other problems in logcat, so better leave it as it is).
For temperature cooldown use a Kernel Manager like Smartpack Kernel Manager / Franco Kernel Manager by Franciso Franco / EX Kernel Manager by flar2 (root/magisk required) and set:
- CPU: set CPU governor of little CPU to "ondemand" - saves a bit of energy compared to "interactive" cpu governor. Don't change big CPU governor (especially if you set minimum of big cpu cores to 0), because Smartpack will crash then.
In CPU governor tunables optionally also set powersave_bias to something higher than 0 (up to 100), like 50 or even 100 works fine (reduces CPU upclocking a bit)
- CPU hotplug: minimum big CPU cores to 0. Edit: Set Busy Down threshold to 40 and Busy Up threshold to 70 or 80 to reduce the probability of big CPUs being activated.
- Thermal: turn on all three thermal drivers (seems to work despite the warnings).
Click to expand...
Click to collapse
- Edit: set GPU governor to "simple_ondemand" too, it's more balanced than msm-adreno-tz.
If you don't use graphics intensive apps, also set GPU max frequency to 180 Mhz - this makes a huge difference in Passmark PerformanceTest app - Open GL ES Unity benchmark (complex space game simulation), but the other 2D and 3D benchmarks in the same app are not much affected by this.
Click to expand...
Click to collapse
- i also changed I/O scheduler of internal/external sd card to deadline noop (simplest one / is supposed to save a little bit of energy). Passmark Performance Test didn't show much difference on them anyway. And disabled I/O stats for internal and external SD card.
Edit: see https://forum.xda-developers.com/t/...ng-camera-quality-guide.4515659/post-87794505
Click to expand...
Click to collapse
- Also turn on Battery saver mode (Extreme battery saver). Without it, little CPUs will clock high, with Battery saver, little CPUs will try to clock down
- and optionally Data Saver mode (quick settings)
- switch off NfC and Ambient display.
- Also enable Dark mode with pitch black Background and set a pitch black wallpaper (apps in Playstore for this available).
- Install naptime (with aggressive doze, disabling motion detection/enabling the first five options) helps for saving energy a lot. If you don't use Playstore, on F-Droid there also Doze alternatives to Naptime, like ForceDoze, beware who you give root though / or use adb to give the doze app the required permissions.
For further debloating: use the attached shell script sumirecleanapp.sh as root in adb shell or TWRP Terminal (TWRP Advanced section) with System partition mounted as writable (execute the script with "sh sumirecleanapp.sh" in the Terminal application). You can use the script direcdtly after flashing ROM and gapps in TWRP to shorten the first boot too (need to remount System partition as writable because other installscripts unmount it). Look at the comments in the script before you do so, to avoid deleting apps you might wanna use. They are backed up to /sdcard/sumirebackup/ and corresponding system subfolder though in case you wanna reinstall them. In case you reinstall an app make sure to chmod 755 to the dir and 644 to the apk files.
Click to expand...
Click to collapse
Sources (lineage-18.1 branches):
ROM: https://github.com/LineageOS/android.git
Kernel: sony msm8994 https://github.com/Professor-Berni/android_kernel_sony_msm8994
Vendor: https://github.com/Professor-Berni/proprietary_vendor_sony
Device-tree:
kitakami-common https://github.com/Professor-Berni/android_device_sony_kitakami-common
sumire https://github.com/Sony-MSM8994-Dev/android_device_sony_sumire
Local manifests: https://github.com/Professor-Berni/local_manifests (devices.xml modified to use tarkzim's sumire device sources)
Download:
ROM https://drive.google.com/drive/folders/1uq_O3lgPX4fjmzKpqnOoWIdxBvVch3bO
Issues:
Potential heat problems (tweaking advised/see instructions above,). If your phone crashes you're probably running too hot.
Edit: Stock Voice Recorder app is working
Audio/microphone recording of Whatsapp/Telegram should work
Edit: The screen brightness seems alright, no suddenly dimmed display
If you experience an app not starting (potential SELinux errors) please post a logcat with "avc: denied" errors (use MatLog app or adb logcat | grep "avc: denied")
Contributors
berni-0815, tarkzim
Thanks to LineageOS
LineageOS – LineageOS Android Distribution
LineageOS Android Distribution
lineageos.org
Build system:
Linux Mint 21, 8 GB Ram, 8 GB swap partition, ~170 GB SSD space used for the whole Linux partition with the compiled sources (repo option --depth=1), 4,5 GB ccache used.
Had to modify build/soong/java/droiddoc.go to avoid out of memory error while building the ROM, so there
after
cmd.BuiltTool(ctx, "metalava").
Flag(config.JavacVmFlags).
Click to expand...
Click to collapse
i inserted:
Flag("-J-Xmx6114m").
Click to expand...
Click to collapse
Using HedgeCam 2 (fork of Open Camera) as photo app recommended (camera2-API works there).
Also turning on some Autofocus bugfixes there may help (but test yourself).
To focus anew tap on the screen where you want the focus on.
Best results when you get a green circle and then take the photo.
Manual ISO mode makes the camera server crash on Camera2-API, so use Auto ISO mode (you can restart camera server in Hedgecam by switching the API back and forth also) or disable Camera2-API.
Note:
After using Hedgecam with Camera2-API and then builtin camera app, the latter one doesn't seem to work properly.
If you want to remove the internal Camera app, move the folder /system/system_ext/priv-app/Snap to somewhere else on /sdcard (as backup). To do so, in TWRP mount System partition, then use TWRP File manager or Terminal (advanced section).
Edit: Integrated the removal of the buitin camera app Snap into my debloating script (sumirecleanapp.sh)
Edit 2: Updated recommended camera settings, see below:
[ROM][11.0][UNOFFICIAL] LineageOS 18.1 [sumire/E6653] tuned rebuild 2022-11-23 + cooldown tuning + camera quality guide
*** Disclaimer I am not responsible for any damage you made to your device. Potential heat problems still there in this ROM. If you unlock your bootloader from stock rom, be sure to backup your drm keys / TA partition in case you want to go back...
forum.xda-developers.com
Overnight test (flight mode) of 11 hours with the above settings resulted in same accu battery percentage after the 11 hours (10% before/10% after).
CPU, CPU hotplug and GPU governor tuning suggestions updated in the first post (see also attached screenshots).
When surfing in Opera with deskop site mode, the temperatures stay like below 50 degrees at the moment with this.
Edit: For better surfing performance and battery life use mobile browser mode instead of desktop browser mode by default in your browser... complex websites (for example YouTube) suck up a lot of power for rendering in desktop mode.
Update for best Hedgecam 2 settings, giving more consistent good picture quality:
In Hedgecam 2 settings, Camera Controls, set Touch to Capture.
This enables you to click on a spot on the screen where you want the picture focus on, and take the picture immediately!
(instead of having to click on a spot in the picture to focus, and then press the camera button some seconds later - with the risk of losing autofocus, and iso auto mode changing in the meantime).
Also in Hedgecam 2 settings, Bug fixes, enable alternative flash method: Torch
These were the most consistent settings to get good picture quality in suboptimal lighting conditions for me, and also easy to use!
Note: picture quality will be best when the focus circle (where you tap the camera preview picture) turns green when (or shortly before) you take a photo.
So if you're intent to have a good quality picture just take 2 or 3 shots where Hedgecam 2 (for at least one of the pictures) gives you the green circle feedback. Focus and quality will be good then
See also the attached photo, and for comparison with HTC camera app 20MP and Open camera app 8 MP on sumire, see here in the crdroid 11 thread (same foto spot and similar lighting conditions):
[ROM+KERNEL][UNOFFICIAL][11.0] crDroid
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
For anyone interested in crDroid, i did a crDroid Android 11 / crDroid version 7.23 build for Xperia Z5/sumire, similar to this LOS 18.1 build:
[ROM+Kernel][11.0][UNOFFICIAL] crDroid 7.24 Android 11 - NOT STABLE [sumire/E6653] build 2022-11-18
*** Disclaimer I am not responsible for any damage you made to your device. Potential heat problems still there in this ROM. If you unlock your bootloader from stock rom, make sure to backup your drm keys / TA partition in case you want to go...
forum.xda-developers.com
Note: Flamegapps Device Health Services app (including Google Playstore app update for it), seems to break accu battery statistics in Settings.
Potentially SELinux or other permissions related.
So for the moment don't install Flamegapps Device Health Services (use config script).
Google app showing a lot of battery drain now, didn't use it much, just some Voice commands for Weather and Alarm clock with Assistant. Reasons could be Google Voice recognition machine learning (?). (i didn't activate the constant Google Assistant Voice listening by Hey Google). Or maybbe because i reinstalled english language(?)
A bit too much anyway.
Edit: Google Go app instead of Google app seems to work fine regarding battery usage.
W
psi78 said:
Note: Flamegapps Device Health Services app (including Google Playstore app update for it), seems to break accu battery statistics in Settings.
Potentially SELinux or other permissions related.
So for the moment don't install Flamegapps Device Health Services (use config script).
Google app showing a lot of battery drain now, didn't use it much, just some Voice commands for Weather and Alarm clock with Assistant. Reasons could be Google Voice recognition machine learning (?). (i didn't activate the constant Google Assistant Voice listening by Hey Google). Or maybbe because i reinstalled english language(?)
A bit too much anyway.
Click to expand...
Click to collapse
For comparison: the Google app doesn't show up anywhere near top on my Google Pixel 2 XL, despite i use Google Assistant Voice commands for Weather and Alarm clock there too.
Ok, Flamegapps Device Health Services app and Google app seem to be not working correctly.
Probably better follow the LineageOS advice regarding gapps (make sure to flash gapps directly after flashing the ROM):
Google apps | LineageOS Wiki
wiki.lineageos.org
Google App potentially causing high accu battery drain with Mindthegapps too though (experienced it on crDroid with Mindthegapps).
Little update to debloating script sumirecleanapp.sh (see first post), changing permissions of backup files for Security reasons.
The following qcom and other tweaks can be added to /system/build.prop (tested it on crDroid ROM version for sumire), phone is snappier and a bit cooler then (unless it's all placebo):
debug.gralloc.enable_fb_ubwc=1
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
#debug.qc.hardware=true
#com.qc.hardware=true
com.qc.hw=1
debug.qc.hw=1
ro.config.nocheckin=1
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.mm.enable.prefetch=true
persist.data.mode=concurrent
# buffers shared between Camera and Video
vendor.vidc.enc.dcvs.extra-buff-count=2
vendor.vidc.enc.disable.pq=1
# Bluetooth
debug.bt.lowspeed=true
net.bt.name=Android
See also https://androidforums.com/threads/qualcomm-speific-build-prop-edits.548317/
New build 2022-11-23 is up (download link in first post).
LOS 18.1 as of 2022-11-21
More tuning and possible battery optimizations:
- Kernel tuned for cortex-a57.cortex-a53 big.little setup (crashes on crdroid were crdroid related, not kernel related)
- VM optimizations for cortex-a57
- Using Open GL ES 3.2 now in build.prop (instead of 3.1 as wrongly stated there before, drivers were already 3.2)
- boot process limited to CPUs 0-3
- some more optimizations in /system/build.prop
Clean flash or semi clean flash at least recommended (wipe Dalvik, Cache, System partitions, or if possible also Data partition)
PS: I'm staying on LOS now because of crashes on crDroid still occuring under high load (even with standard kernel)
Edit: modified files regarding ROM version 2022-11-23 here:
LOS18.1_source_modifications - Google Drive
drive.google.com
My gf broke her phone and is using my Xperia Z5 now (my main phone is a Google Pixel 2 XL nowaday).
Regarding telephoning, i noted there are more crackling sounds with VoLTE in mobile settings on, and less crackling when VoLTE is switched off (german Telekom carrier). This may be also because of SmartPack throttling down the CPUs in my setup, but not sure of that.
psi78 said:
My gf broke her phone and is using my Xperia Z5 now (my main phone is a Google Pixel 2 XL nowaday).
Regarding telephoning, i noted there are more crackling sounds with VoLTE in mobile settings on, and less crackling when VoLTE is switched off (german Telekom carrier). This may be also because of SmartPack throttling down the CPUs in my setup, but not sure of that.
Click to expand...
Click to collapse
well as it happens, gf uses the phone in another way than me, and for some reason the keyboard reacted sometimes not or very slow.
in the end i deinstalled Smartpack to just deactivate all the CPU throttling and also installed Gboard.
(Extreme) Battery Saver mode and Naptime still do a lot for cooldown though - CPU cores 0-3 still throttling down to lower frequencies with Battery saver, and naptime putting unused apps quicker to deep sleep.
Ah, crackling noise, for some reason it occurs frequently with system sounds (ringtone, button presses, etc.)
I have bought my mom a new phone, so I can test things on Z5 now.
works well,thank you.
Hello, during videocalls via viber the person I am calling with is hearing himself as an echo. Has enyone such problem? I dont know if it is spec of this phone or is something wrong, I didnt use this phone with stock rom before lineageos. Thanks.
in regards to audio crackling i have been suspecting that it's rendering the audio via Software Rendering (CPU gets overloaded hence Audio Crackling) instead of utilizing the built-in Qualcomm DAC for Hardware rendering if this is not the case then you might want to look on the playback bitrate and frequency. As far as i remember tarkzim set the audio bitrate and frequency to 32-Bit/48KHz while on the previous build from sony it was only at 24-Bit/192KHz
Ramon111 said:
Hello, during videocalls via viber the person I am calling with is hearing himself as an echo. Has enyone such problem? I dont know if it is spec of this phone or is something wrong, I didnt use this phone with stock rom before lineageos. Thanks.
Click to expand...
Click to collapse
Don't have any experience with Viber, sry. In case you want to test it on stock Sony ROM, you can use Sony's Flash Tool "EMMA" to go back to stock ROM:
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
_harley said:
in regards to audio crackling i have been suspecting that it's rendering the audio via Software Rendering (CPU gets overloaded hence Audio Crackling) instead of utilizing the built-in Qualcomm DAC for Hardware rendering if this is not the case then you might want to look on the playback bitrate and frequency. As far as i remember tarkzim set the audio bitrate and frequency to 32-Bit/48KHz while on the previous build from sony it was only at 24-Bit/192KHz
Click to expand...
Click to collapse
Sounds plausible
Edit: Audio crackling may be a different issue than audio echos though?
There are some threads about voice echos here on xda, some attributing it to phone cases/covers, some to hardware problems, some to noise reduction, but i don't have a clue atm if it's possible to change that.
When i do video calls in home office (on PC with webcam) i sometimes experience the problem of hearing echos.of my voice when the other person isn't using headphones, and the voice coming out of the other person's speaker is loud and recorded by their microphone again. The other person using headphones is a workaround for that, but not sure if that's a similar issue there @Ramon111 . Does it work for you with other devices than the Z5?