Database Info

Tweaks, a place to start.

Recently I've been looking into the build.prop file in the /system/ directory, and after making a few modifications I feel that I have gained a little performance not only from the network, but my phone overall.
***************************
I DON'T RECOMMEND DOING THIS IF YOU DON'T KNOW WHAT YOU ARE DOING.
MODIFYING THESE VALUES MAY EVEN REDUCE PERFORMANCE.
***************************
To use these values you must have an app like root explorer installed.
1. Open your explorer of choice.
2. Navigate to the /system/ directory, and mount it as r/w.
3. Make a copy of build.prop as build.prop.bak, so you can revert back to the original should you suffer any complications.
4. Open build.prop in text editor and at the bottom of the file make two lines space before adding these values so you can distinguish between these values and the normal values.
# Make UI more responsive (sweet spot is between 200 - 300)
windowsmgr.max_events_per_sec=300
# Dial out delay
ro.telephony.call_ring.delay=0
# Disable usb debugging icon (no more exclamation mark when connected to USB)
persist.adb.notify=0
# Enable hardware acceleration
debug.sf.hw=1
# Unknown
debug.performance.tuning=1
# Unknown (won't produce error log files due to apps or system if I remember right)
logcat.live=disable
# Unknown (render graphics using hardware)
video.accelerate.hw=1
# Unknown (disables graphics dithering)
persist.sys.use_dithering=0
# Unknown (deletes unnecessary cache)
persist.sys.purgeable_assets=1
# Force launcher into memory
ro.HOME_APP_ADJ=1
# WiFi scanning intervals (currently set at every 3 minutes)
wifi.supplicant_scan_interval=180
These are a few that I am using personally, but once again use these with care as you may recieve results different to what I get.
# Increase the memory of the Dalvik virtual machine
dalvik.vm.heapsize=64m
# Disable boot animation
debug.sf.nobootanimation=1
I do have a few more, but the ones I'm looking at currently could go bad depending on the user/ROM, but they aren't anything too amazing, so no ones missing anything big ;-).

Also network settings to add.
These were taken from the build.prop file on the Telstra HTC Desire S RUU ROM file, and I'm finding performance a lot better than what I was getting from any of the custom ROMs, not trying to bad mouth them in saying this though.
ro.ril.oem.ecclist=112,000,911
ro.ril.enable.a52=0
ro.ril.enable.a53=0
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.fast.dormancy.rule=0
ro.ril.disable.mcc.filter=1
ro.ril.emc.mode=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.oem.show.act=1
ro.ril.enable.amr.wideband=1
ro.ril.vmail.50501=+61101
ro.ril.gprsclass=12
# Default network type WCDMA
ro.telephony.default_network=0
Once again these values work rather well on the Telstra network in Australia.

Nice post man, keep 'em coming.
Peace
Sent from my phone using my fingers

Thanks for sharing this is great - although should it possibly be in the Dev section, even though you have provided a decent warning, it still has the potential to seriously destroy devices?
Also slightly concerned with the number of tweaks that are marked or commented as UNKNOWN.....I'd really like to know what these things are or at least what they're supposed to do before I attempt to implement them for my self on my device.
Although don't take this as a criticism., this is certainly the sort of stuff that I'd like to understand more.

Sorry, most of the ones marked as unknown, are mostly graphics which are normally processed by the software being moved to primarily being processed by the hardware.
I'll quickly edit now.
Added the dalvik and boot animation tweaks. Modified the post a little as well ;-).

(MOD) 108 Triumph & Hollyname B.P Tweaks (4.28.2012) Two Sweet

Ok I’m sure by now most have read the previous Op about losing half my Teeth, all in the back thank the Gods but still can’t wait until I get the fakes bolted in. Sure that will also be an awesome experience, forgot to add that I can’t take pain killers either. Anyhow I originally started working on this Mod for personal use and a means of keeping sanity. Because it ended up working out much better than anticipated I decided to share the script. Since then I have made some changes as I first have learned a little bit more and second because it has expanded beyond its original intention of being made specifically for CM7 and optimized in some areas around my own personal device configuration. Because of this I just decided to kind of give things a Reboot.
What does this Mod do you may ask? In short it just makes everything a little better and snappier! How does it go about doing these things you may ask?
In Short,
IPV4 Internet speed Tweaks,
Chainfire Touchscreen Tweaks,
Increased Cache Sizes,
Defrag Database Files On Boot,
Remove Logger,
Running fewer background Processes,
Set’s Higher Priority for App's like Phone, Launcher, Contacts, SMS, SystemUI & Camera, (Loopy Smoothness)
Two Sweet Edition Changes (04.28.2012)
Linux Laptop Tweaks for Battery Life
Ondemand, Interactive & SmartassV2 Govenor Tweaks
APK Zipalign (Already performed by most Roms but included for the few that do not)
Many more along the same lines.
Again just so it’s clear, I did not develop any of these Tweaks on my own. If any credit should go my way it would be for looking around various websites and inside ROMs for other devices, finding things that look interesting, testing on the Triumph for effectiveness, making minor adjustments if needed and then collecting them into a method that is easy to apply. This should work with just about any Rom with Init.d Support. The easiest way of determining if your Rom has Init.d support would probably be to look at the below directions. If you find an Init.d folder in the spot they say you should then your Rom supports Init.d. It would still be recommended to keep a backup handy as I am not responsible for any damage caused to anything you own.
.
Instructions (Busybox must be installed, if not, download from the Market)
1, Download 108 Triumph Script.
108 Triumph Script (04.22.2012)
http://www.mediafire.com/file/l8x4pyt1u3wfjck/108TriumphScript
108 Triumph Script Two Sweet Edition (04.28.2012)
http://www.mediafire.com/file/77cd8dzdgzmsar1/108TriumphScript2sweet
If for some reason and I noticed this with Dolphin, .txt has been added to the end of the file name after downloading .text will need to be removed or the Tweaks will not be applied. So far I have only seen this happen with Dolphin but no dots should appear in the file name and should be removed.
2, Place file on your SD-card. (USB Dropbox, doesn't matter how)
3, Use Root Explorer or Root Browser Free and move the file into system/etc/init.d folder. (Remember to hit the tab that makes the folder Read/Write as Read Only is the default setting for most File Explorers.)
Root Browser Free if you need a free File Explorer.
http://dl.dropbox.com/u/29969403/rootbrowser.apk
4, Give the file full Permissions.
5, Reboot! (Will take a bit longer to boot and will appear to be held up on the Motorola Logo for a bit. This is nothing to worry about, the script is running and the Tweaks are being applied.)
Clear both Caches in recovery if you have any issues. Should not be needed but have noticed that sometimes Root System Apps like SD-Booster or Auto-Killer when installed before applying the script will restore pre-script values when the restore default settings option in the App is used.
To remove these Tweaks simply delete the file and reboot. To update the file use the file explorer to delete the old version after placing the new version in the init.d folder.
Going forwarded at least for the time being the Build.prop Tweaks can be applied by using the optional Hollyname Script. This was done because to apply these Tweaks correctly as part of the 108 Script with my current knowledge would do either one of two things, permanently add these Tweaks to the Build.prop or make the script Rom specific. Because I’m trying to stay away from having the Mod make any permanent adjustment or have the willingness or time for keeping up with every version of every Rom until I figure a way around the issue they can still be easily applied without making any changes to the Build.prop by following the following.
Additional Build.Prop Tweaks (Recommended)
1, Download Hollyname Build.Prop Tweaks Script and place on SD-Card.
Hollyname Build.prop Tweaks (04.22.2012)
http://www.mediafire.com/file/9f843s9j47czw4z/HollynameBPTweaks
Hollyname Build.prop Tweaks Two Sweet Edition (04.28.2012)
http://www.mediafire.com/file/gzg44q7hho1q8qx/HollynameBPTweaks2sweet
2, Install Script Manager Free from the market.
3, Open Script manager and select the script.
4, Select SU, Boot and then save.
5, Reboot! (All Build.prop Tweaks will now be applied during each boot unless un-selecting the option in script manager or deleting the script from the SD-Card. This will not make any actual changes to your Build.prop. Nor will it effect any properties associated with Market Access.
You Can run "getprop" in either ADB or a Terminal to confirm all current property values if not sure everything was done correctly. If so you should now see the following included among the listed properties,
debug.sf.hw 1
dalvik.vm.heapsize 48
persist.sys.ui.hw 1
ro.max.fling_velocity 12000
ro.min.fling_velocity 8000
ro.ril.disable.power.collapse 1
pm.sleep_mode 1
windowsmgr.max_events_per_sec 150
ro.media.enc.jpeg.quality 100
ro.media.dec.jpeg.memcap 8000000
ro.media.enc.hprof.vid.bps 8000000
media.stagefright.enable-player true
media.stagefright.enable-meta true
media.stagefright.enable-scan true
media.stagefright.enable-http true
net.tcp.buffersize.default 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi 524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge 6144,87380,524288,6144,16384,262144
net.tcp.buffersize.evdo_b 4096,87380,256960,4096,16384,256960
ro.kernel.android.checkjni 0
ro.kernel.checkjni 0
debug.performance.tuning 1
video.accelerate.hw 1
dalvik.vm.dexopt-flags v=n,o=v
persist.adb.notify 0
wifi.supplicant_scan_interval 180
ro.config.disable_hw_accel false
ring.delay 0

[Q] Manipulating buildinfo.sh during build

I've searched and reviewed quite a few threads, and so far all I've found is using userinit scripts to perform updates to build.prop, however I was wondering if there was any way to manipulate what buildinfo.sh outputs during the initial rom build process. IE: Can I set BUILD_VERSION_ID somewhere so ro.build.display.id is updated in build.prop?

So far, the only ways I've found so far is quite simple, but requires you to edit build.prop while the build is taking place. However, you only need to edit it once until you want it changed, as build.prop doesn't seem to be regenerated (as long as you didn't clean your build tree).
I am still looking for any other methods, however this one works for me.

chadddexter said:
So far, the only ways I've found so far is quite simple, but requires you to edit build.prop while the build is taking place. However, you only need to edit it once until you want it changed, as build.prop doesn't seem to be regenerated (as long as you didn't clean your build tree).
I am still looking for any other methods, however this one works for me.
Click to expand...
Click to collapse
ro.custom.build.version is not changing at phone info.....strange its happening first time ...any idea?

[GUIDE] How to Save Battery

BATTERY TWEAKS AND TIPS
Introduction:
This is a guide that will help you save battery. After searching many forums and websites i came across a few tips that worked and a few that didn't. These tips are based on my own personal experience and therefore may not apply to everyone.
WARNING: Battery calibration is a big no-no. This can reduce your battery's life and in most cases does not work. I tried it a few times and one of my batteries went bad and had to be replaced. Also, task killers are not recommended at all. This is because android is based on a linux kernel which keeps apps running in the background by default. By killing these apps, many experts say that there is an actual decrease in battery life.
Also avoid battery saving or startup managing apps...
Apps that clear cache are ok and would not result in loss of battery life.
Remeber: do these at your own risk. I am not responsible for any damage cause to your device.
TIPS
The following tips do not require you to be rooted:
1. First and foremost, you must do the obvious stuff:
- Set screen brightness low
- Turn off 3G, packet data and WIFI if not in use
-use 2G networks if you don't use data
-turn off auto-sync
-allow Wifi to sleep when the phone is asleep (Go to the Wifi settings in your phone, press the Menu Button, press advanced, press Wi-Fi sleep policy and change it to "When screen turns off")
-Uninstall unused or unwanted apps
-Remove unwanted widgets from your homescreen
2. This is a trick i have tested and has given me excellent results:
-remove your battery and take a knife or another sharp object and scrape the metal contacts with it and also scrape the metal contacts in the phone's batter compartment. This allows for the batter to be in good contact with the contacts (avoid shortage).
The following tips require you to be rooted or have experience with using ADB:
1.Unwanted Files and Apps
-It is recommended to use root explorer to delete any system apps that you do not need
-What many people seem to neglect is also clearing out the "left-behind" data files of these apps. You must clear these by finding the corresponding folder in the director /data/data with RootExplorer etc.
-After uninstalling apps I highly recommend that you clear the dalvik-cache folder and reboot.
-Many unwanted samsung apps or sync apps cause battery drainage and should be deleted.
-Remember Google is your friend, if you see an app of which you are unsure if to delete, Google it!!
2.Build Prop Tweaks
-I am unsure about how well these work but i have them in my build.prop anyway.
In rootexplorer go to the directory: /system and you will see a file called build.prop. Open that file with the text editor (Ensure the partition is mounted as RW) and add these following lines to the end of the file:
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
ro.mot.eri.losalert.delay=1000
ro.kernel.android.checkjni=0
profiler.force_disable_err_rpt=1
profiler.force_dosable_ulog=1
ro.kernel.android.checkjni=0
logcat.live=disable
persist.sys.purgeable_assets=1
3. Avoid some init.d scripts
-I have no intention of bashing developers but some zipaligning and sqlite tweaks have been proven to cause battery drain. This is very unnoticeable though and if you want, you can keep those
-A ram managing tweak is highly recommended. Google "Flyon Mod" or "V6 supercharger"
these allow your phone to store apps in ram for faster access and prevents the ram from becoming overloaded.
4. Use a good CPU governer, IO Scheduler and Cpu freqencies
- These can be adjusted using apps such as: SetCPU and No-Frills
- More info about these can be found at: CLICK

Thanks for the guide! Although the knife part seemed a little too much

Viability of using older ROMS with older security patches

I have an old device, a nexus 10....yes there are some of us still using these
I am currently using a Lineage 16 ROM which is having security updates regularlly released. This is a big plus, but comes with drawbacks, namely a lot of hardware stuff doesnt work, the tablet runs hot doing basic tasks and performance is very slow. I would like to run an older ROM more suited to the hardware, but the security patch on some of these goes back to 2015 and rings alarm bells!
My use case is simple, browse and view YouTube videos via Adblock browser (gets rid of annoying adverts), run some games and apps from the play store. Some minimal web browsing.
Simply, what is the risk of using older ROMS? Can you mitigate the risk by 'not browsing'? is being online in itself an issue? Do you avoid having root access if your on an old device? I know next to nothing on this area so would appreciate advice.
Thanks
Graham

IMO any browser, especially its extensions, can be thought of as suspicious software.

jwoegerbauer said:
IMO any browser, especially its extensions, can be thought of as suspicious software.
Click to expand...
Click to collapse
Thanks for the answer...so in short its a bad idea to run the older ROMS from a security perspective, regardless of use case.

Well, it depends on what you use the phone/tablet, if you use it for the simple things (calls, videos, music, etc.) you can use older android version roms, alternatively you can use build.prop tweaks and scripts like v6 supercharger for android, you can try these build.prop tweaks i use on an HTC One M8 (2 GB RAM) and an Moto G 2014 (Titan, 1 GB RAM)
Code:
# GALACTIC DeepSleep Ultimate Mod By PawanRockz
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
wifi.supplicant_scan_interval=180
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
ro.config.hw_power_saving=true
ro.max.fling_velocity=20000
ro.min.fling_velocity=18000
debug.performance.tuning=1
debug.kill_allocating_task=0
debug.overlayui.enable=1
ro.config.disable.hw_accel=false
persist.radio.add_power_save=1
settings.display.autobacklight=1
ro.ril.sensor.sleep.control=1
# More RAM
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
profiler.force_disable_ulog=true
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
profiler.force_disable_err_rpt=true
profiler.hung.dumpdobugreport=false
debugtool.anrhistory=0
debug.mdpcomp.logs=0
profiler.debugmonitor=false
profiler.launch=false
# Better RAM management
ro.HOME_APP_ADJ=1

chuy19312 said:
Well, it depends on what you use the phone/tablet, if you use it for the simple things (calls, videos, music, etc.) you can use older android version roms, alternatively you can use build.prop tweaks and scripts like v6 supercharger for android, you can try these build.prop tweaks i use on an HTC One M8 (2 GB RAM) and an Moto G 2014 (Titan, 1 GB RAM)
Code:
# GALACTIC DeepSleep Ultimate Mod By PawanRockz
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
wifi.supplicant_scan_interval=180
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
ro.config.hw_power_saving=true
ro.max.fling_velocity=20000
ro.min.fling_velocity=18000
debug.performance.tuning=1
debug.kill_allocating_task=0
debug.overlayui.enable=1
ro.config.disable.hw_accel=false
persist.radio.add_power_save=1
settings.display.autobacklight=1
ro.ril.sensor.sleep.control=1
# More RAM
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
profiler.force_disable_ulog=true
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
profiler.force_disable_err_rpt=true
profiler.hung.dumpdobugreport=false
debugtool.anrhistory=0
debug.mdpcomp.logs=0
profiler.debugmonitor=false
profiler.launch=false
# Better RAM management
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
I think my useage will be as far as watching YouTube videos and adjusting my fantast league team through the Ad block browser. Probably some games i own as well.
Build prop tweeks? this is a new term to me, given the hardware you are using and some of the things im reading in the script this this will help with running newer ROMS on the older hardware by tweaking th install (i know thats gotta be the wrong word, im basically noob lol!)

I've used old unpatched Android OSs for years on devices without root with only minor issues.
No forced reloads due to infections.
A malware jpeg gave me trouble once but caught it at the get go; it did some damage to the files of the folder it was in but was contained.
Keep a close lookout for abnormal behavior and act quickly if found.
A good firewall is a very useful tool; been using Karma Firewall, which uses very little battery and runs well.
Had a Malwarebytes scan pick off a nasty trojan preloader that auto downloaded it's self too. The free Malwarebytes can occasionally be a useful app.
Always keep email in the cloud, be wary of all downloads, especially of side loading apks and know the OS's vulnerabilities/lock it down as much as possible.
Just be ready to do a no warning reload if things go south*... and no big deal. Keep time staggered backups on multiple physically isolated hdds.
*pre Pie OSs may get a rootkit that will force you to reflash the firmware to eradicate it. So there's that.

graham_uk said:
I think my useage will be as far as watching YouTube videos and adjusting my fantast league team through the Ad block browser. Probably some games i own as well.
Build prop tweeks? this is a new term to me, given the hardware you are using and some of the things im reading in the script this this will help with running newer ROMS on the older hardware by tweaking th install (i know thats gotta be the wrong word, im basically noob lol!)
Click to expand...
Click to collapse
Build.prop tweaks are some tweaks like the ones that i put on my comment to improve performance, battery or modify things,build.prop is an file located on /system (/system/system on android 10 or higher when using TWRP), i will give you instructions to modify it on pc with notepad++
1. Go to system folder using TWRP or apps like root explorer, then copy build.prop to your sd card or internal storage
2. Connect your phone to your computer, and put your build.prop file to any place, i recommend to documents, then download and install notepad++
3. Edit build.prop file using notepad++, add tweaks i gave to you at the end of your build.prop file, add an empty line at the end of the file if there is no one to prevent errors
4. Save it
5. Put it again in your phone
6. Rename your build.prop file on system to build.bak, so you will have an backup in case things go bad or you get in an bootloop
7. Paste your modified build.prop file on system
On root explorer, you only paste your file on system and give permissions like this
RR
R
R
and restart your phone
On TWRP, after putting it into system, go to system and press on build.prop file, press on chmod and on value put 0644, then reboot your phone

So firstly, to @jwoegerbauer @chuy19312 @blackhawk
Thankyou for responsing to my question. I am in every way new to working with modified ROMS and having these working with old but still viable hardware. It gives confidence knowing that it is not a complete loss if i am running old hardware and thus ROMs on them. I am going to give the prop.tweak a go and see how i get on (really appreciate the detailed instructions Chuy19312) , at least i have a fall back position of using an older ROM given Blackhawks experiences.
Graham