• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Build.prop Performance Tweaks - Updated 04.14.2012

ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=5

I can confirm even though they do increase data transfer speeds, they do cause battery drain *CRAP!!!!!!!!*they seem to throttle the 3g radio to full and in doing so eats up alot of juice even when not in use.
 
I found these guys today. Just added the lines a little bit ago and everything is at least working. Have not yet tested effectiveness.

ro.ril.enable.a52=1
ro.ril.enable.a53=1

Not expecting anything with the above.

net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hsdpa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hsupa=4096,87380,256960,4096,16384,256960 (Broke Google SYNC)

sure spaces will appear like the others.



Assuming all goes well with the above I intend to check these out but have not as of yet.

dalvik.vm.heapstartsize=5m
ro.media.enc.hprof.vid.fps=65
persist.sys.ui.hw=1
dalvik.vm.verify_bytecode=false
debug.composition.type=gpu
ro.mot.hw.HAC=1



Have no idea what these do yet but know they are [FONT=&quot]qualcomm device specific.

[/FONT] debug.qctwa.statusbar=1 - qualcomm device specific
debug.qctwa.preservebuf=1 - qualcomm device specific
debug.qc.hardware=true - qualcomm device specific
com.qc.hardware=true - qualcomm device specific
 
Would like to get a second confirmation on these guys if anyone is board. Seem to give a slight 3g boost but at my house anyway using Wifi without the lines am getting about 4500 down on average after ten tests. After adding the lines I averaged about 13000 down.

net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hsdpa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=4096,87380,256960,4096,16384,256960
 
Improve 3g data speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5

I am on CM9 with the latest build. I added all the lines from the original post. I can tell a huge difference with it. Everything is quicker and I love that the apps open instantly.

I did have some issues with the 3G lines. When those were added, the power toggles in the notification pull down would freeze. I turn off data throughout the day since I don't have great signal at work and it will leave data on and eventually my phone would freeze and reboot. Once I removed those lines, it works just fine. I tried removing some of the lines one at a time to see if it was a specific one and I didn't get anywhere.

Edit: I've confirmed adding this line (ro.ril.hsxpa=2) kills your 3G in CM9. Everything else seems to be working fine. I'm going to go ahead and test the following ones to see what else I can break.

dalvik.vm.heapstartsize=5m
ro.media.enc.hprof.vid.fps=65
persist.sys.ui.hw=1
dalvik.vm.verify_bytecode=false
debug.composition.type=gpu
ro.mot.hw.HAC=1
 
minikirchner said:
Improve 3g data speeds
I'm going to go ahead and test the following ones to see what else I can break.

dalvik.vm.heapstartsize=5m
ro.media.enc.hprof.vid.fps=65
persist.sys.ui.hw=1
dalvik.vm.verify_bytecode=false
debug.composition.type=gpu
ro.mot.hw.HAC=1
Click to expand...

Thats funny,

I actually had not tested those with CM9. they work very well with CM7/MIUI but was on my way to adding a warning that it has some battery draining potential. Its almost not that noticeable at all with a fresh install but after a bit of time and the app list growing again my battery started draining drastically. Couldn't tell for certain but if I had to guess its because more apps equals more data use.

jarjar124 said:
I'm pretty sure it said edit existing line.
Click to expand...

Honestly it probably depends on the Rom, fairly certain its in CM7 and maybe stock. Either way if you don't see the line its probably ok to just add it. Probably best to avoid the lines at the bottom of the Op or the above list of things to brake unless prepared with a backup.
 
hi, I'm having a problem with my galaxy pocket. I replaced the build.prop with a new one with some of the lines you posted. I did a backup of the original build.prop. But when i reboot the phone, it blocks on the "samsung" opening screen. So i guess i need to replace the prop file with the original one.
How to do that?:) Do I need to connect the phone on the pc ? Cause I saw there's no way to do that on the recovery mode of the phone..
thanks in advance.

edit: just noticed this post was for motorola...ok. i'm an idiot. please help:(
 
blacklava777 said:
hi, I'm having a problem with my galaxy pocket. I replaced the build.prop with a new one with some of the lines you posted. I did a backup of the original build.prop. But when i reboot the phone, it blocks on the "samsung" opening screen. So i guess i need to replace the prop file with the original one.
How to do that?:) Do I need to connect the phone on the pc ? Cause I saw there's no way to do that on the recovery mode of the phone..
thanks in advance.

edit: just noticed this post was for motorola...ok. i'm an idiot. please help:(
Click to expand...

You could try finding an original copy of your own device's build.prop, re-creating the series of folders that contains your build.prop file, then zipping it all up, then flashing it from recovery as an update to replace your modified build.prop on the phone.
 
aricblunk said:
You could try finding an original copy of your own device's build.prop, re-creating the series of folders that contains your build.prop file, then zipping it all up, then flashing it from recovery as an update to replace your modified build.prop on the phone.
Click to expand...

thanks, but how to copy this modified update.zip file into the phone to be launched from recovery?
is there any way to get into the root directory via usb?
 
blacklava777 said:
thanks, but how to copy this modified update.zip file into the phone to be launched from recovery?
is there any way to get into the root directory via usb?
Click to expand...

not that i know if.my only method is going into root via phone. using a file explorer with root permission,
 
If stuck on the boot logo you could try the qtADB posted in the OP. Should still is able to access your system files from a computer, even if stuck on the boot logo. I have gotten stuck on the Motorola M Logo a few times and was able to replace the build.prop using ADB. After doing this just enter the shell tab on the side and give a
 
Chairshot215 said:
If stuck on the boot logo you could try the qtADB posted in the OP. Should still is able to access your system files from a computer, even if stuck on the boot logo. I have gotten stuck on the Motorola M Logo a few times and was able to replace the build.prop using ADB. After doing this just enter the shell tab on the side and give a
Click to expand...
 
blacklava777 said:
thanks for the reply. Tried to open qtadb but it can't find any device connected. Phone stucks on the boot logo and vibrate randomly. windows only detect a new drive but cannot access the mass storage. don't know any adb.exe command line, could it be different/better then qtadb?

big f. mistake here:(
Click to expand...

Is actually the same thing, in order for QTADB to work you must first download and extract the ADB binary. Should be a link for the ADB binary on the same page as the interface.Then either the first time you open QTADB or in the settings you tell it what directory you extracted ADB in. QTADB is really just a GUI that is running the commands using the ADB binary for those who are not familiar.

Its not a bad little program and is how I started learning to use ADB. I still use the Shell option for running commands as it saves the time of needing to change directory or add ADB in the beginning of every line.

Are you on the Stock Rom or a custom Rom? Another option if your phone has it would be to enter USB storage from recovery and put another Rom on the drive you could flash in recovery.

Edit: Also with Samsung phones you can do allot with "Odin". I am not familiar with Odin but I bet if you go to your phones forum either here or XDA someone would be able to help with it. It is used allot with Samsung phones for bootloaders, recovery and Root.

Sorry keep thinking of more things you can try. If your recovery has an option for mount system you can also use QTADB why in recovery to swap out the file. Still, your best bet is asking on the forum for your phone.
 
Chairshot215 said:
Is actually the same thing, in order for QTADB to work you must first download and extract the ADB binary. Should be a link for the ADB binary on the same page as the interface.Then either the first time you open QTADB or in the settings you tell it what directory you extracted ADB in. QTADB is really just a GUI that is running the commands using the ADB binary for those who are not familiar.

Its not a bad little program and is how I started learning to use ADB. I still use the Shell option for running commands as it saves the time of needing to change directory or add ADB in the beginning of every line.

Are you on the Stock Rom or a custom Rom? Another option if your phone has it would be to enter USB storage from recovery and put another Rom on the drive you could flash in recovery.

Edit: Also with Samsung phones you can do allot with "Odin". I am not familiar with Odin but I bet if you go to your phones forum either here or XDA someone would be able to help with it. It is used allot with Samsung phones for bootloaders, recovery and Root.

Sorry keep thinking of more things you can try. If your recovery has an option for mount system you can also use QTADB why in recovery to swap out the file. Still, your best bet is asking on the forum for your phone.
Click to expand...

I'm on the stock rom, rooted of course. I tried to connect the phone to qtadb both turned "on" (samsung logo blocked) and on recovery mode. It cannot detect any device. The only options I have in the recovery mode is:

-reboot system now;
-apply update from sdcard; (and here you can explore the directories but NOT the root one, here I have the update.zip file that i used to root the phone days ago. tried to apply it again but now it gives me an error)

-wipe data/factory reset; (tried to launch it, loosing all the phone content, but still blocks on samsung logo)

-wipe cache partition;

so it seems there's no way to have any access from recovery, the only way could be via usb, but looks like the phone is not detected by qtadb, only windows gives a new letter driver, but empty/not working.

going to read something on this odin, and maybe repost all this in a more appropriate thread. thanks again, very kind
 
blacklava777 said:
I'm on the stock rom, rooted of course. I tried to connect the phone to qtadb both turned "on" (samsung logo blocked) and on recovery mode. It cannot detect any device. The only options I have in the recovery mode is:

-reboot system now;
-apply update from sdcard; (and here you can explore the directories but NOT the root one, here I have the update.zip file that i used to root the phone days ago. tried to apply it again but now it gives me an error)

-wipe data/factory reset; (tried to launch it, loosing all the phone content, but still blocks on samsung logo)

-wipe cache partition;

so it seems there's no way to have any access from recovery, the only way could be via usb, but looks like the phone is not detected by qtadb, only windows gives a new letter driver, but empty/not working.

going to read something on this odin, and maybe repost all this in a more appropriate thread. thanks again, very kind
Click to expand...

Sorry for the delay, you would get the update.zip with the stock build.prop onto the phone by inserting your SD card into a computer with an SD card reader and copying the zip to it, then flash it from recovery.
 
aricblunk said:
Sorry for the delay, you would get the update.zip with the stock build.prop onto the phone by inserting your SD card into a computer with an SD card reader and copying the zip to it, then flash it from recovery.
Click to expand...

But as I can see opening the back of the phone, there's no SD card extractable. Only the SIM card and the microsd slot, which is empty of course. Maybe removing the screws? thanks.
 
You must log in or register to reply here.
Back
Top Bottom