Database Info

ro.ril.hsxpa=3

what does this do
ro.ril.hsxpa=3

qbills314 said:
what does this do
ro.ril.hsxpa=3
Click to expand...
Click to collapse
this will enable hsupa. Fast upload speeds.

klquicksall said:
this will enable hsupa. Fast upload speeds.
Click to expand...
Click to collapse
HSUPA is already enabled with ro.ril.hsxpa=2
http://forum.cyanogenmod.com/topic/9781-buildprop-roril-meanings/

That I, true I think, setting it to 2 does as well. But inspire's problem is its set to 1 stock which caps upload speed.

mike1986. said:
HSUPA is already enabled with ro.ril.hsxpa=2
Click to expand...
Click to collapse
Is this default enabled in your ARHD Roms? Or need i the [Mod] to enable it?

RogerPodacter said:
That I, true I think, setting it to 2 does as well. But inspire's problem is its set to 1 stock which caps upload speed.
Click to expand...
Click to collapse
The stock ROM has had this value set to 2 since the OTA update in April.

henrybravo said:
The stock ROM has had this value set to 2 since the OTA update in April.
Click to expand...
Click to collapse
3 on all of mine... Including the new Gingerbread leak that came out recently.

id10terrordfw said:
3 on all of mine... Including the new Gingerbread leak that came out recently.
Click to expand...
Click to collapse
You know there are duplicate fields in the stock build.prop. One entry is "2", the other one says "3". The way I understand it the one that says 2 overrides the one that says 3 due to placement in the file....it's a goofy quirk of the stock build.prop. I don't think anyone knows why there are these duplicate fields with different values.

meiguoguizi said:
You know there are duplicate fields in the stock build.prop. One entry is "2", the other one says "3". The way I understand it the one that says 2 overrides the one that says 3 due to placement in the file....it's a goofy quirk of the stock build.prop. I don't think anyone knows why there are these duplicate fields with different values.
Click to expand...
Click to collapse
This drives me nuts and I want to delete the second values sooo bad Lol
Can anyone confirm that 2 works better than 3?
Sent from my Microwave

seh6183 said:
This drives me nuts and I want to delete the second values sooo bad Lol
Can anyone confirm that 2 works better than 3?
Click to expand...
Click to collapse
2 and 3 work the same. The stock ROM is set to 2, even though there is a duplicate entry further down the build.prop set to 3. As meiguoguizi said, when there are duplicate values, the top value wins. I have confirmed this by playing around with the duplicate hsxpa entries and checking the "P" or "U" in the radio version.

meiguoguizi said:
You know there are duplicate fields in the stock build.prop. One entry is "2", the other one says "3". The way I understand it the one that says 2 overrides the one that says 3 due to placement in the file....it's a goofy quirk of the stock build.prop. I don't think anyone knows why there are these duplicate fields with different values.
Click to expand...
Click to collapse
LOL I think I know all about build.prop. I have triple checked the stock update that am running, 3 is the only setting. But hb is right, I can't see any difference between two or three.
Sent from my Desire HD using XDA Premium App

id10terrordfw said:
LOL I think I know all about build.prop. I have triple checked the stock update that am running, 3 is the only setting. But hb is right, I can't see any difference between two or three.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Interesting. There must be different versions of "stock" floating around. The attn1 updated rooted stock ROM and the supposed new GB leaked ROM had these settings at the top:
ro.ril.enable.a53=1
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.def.agps.mode=1
ro.ril.att.feature=1
ro.ril.radio.svn=3
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.gea3=1
ro.ril.enable.ucsq=2

Possible 4G performance tweaks???

I found these on the net and all though these were found by another XDA member. The numbers are carrier specific for ATT but i was wondering if all the Guru's and tech geeks can concur if they might actually be useful/tweaked for our Tmob network.
These tweaks are not ment to increase download speed's but rather give better performance wise.
Original numbers for ATT from post
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=9
ro.ril.hsxpa=3
Here's the link where i found them:click here
After checking out some things i came out with these numbers.
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.hsxpa=0
Although they are not set in stone and your mileage may vary but i have noticed the responsiveness for anything data related is a tad bit quicker then again it might just be a placebo.
Hence why I'm reaching out to see if these tweaks are or could be done better for our network with some testing done in other areas.
These numbers are located in the build.prop file. A quick google can tell you how to get there using root explorer on a rooted phone.

Well I tell u this much I did change my build prop on my MT4G
hsxpa from 3 to 2 and it did improve my data speed.
Sent from my HTC Vision using Tapatalk

asesino said:
Well I tell u this much I did change my build prop on my MT4G
hsxpa from 3 to 2 and it did improve my data speed.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Kool so there is some merit with these tweaks atleast with that part.
To everyone else post your results if your testing and lets find out together to make our data network a little more streamlined so we can enjoy our youtubing, break.com app watching, and pandora listening selves ^_^
To the guru's feel free to chime in...this is a constructive thread so no worries...everybit of knowledge can help.

YAY GOT A sensation and got a question

How many ROMS have GPU acceleration enabled. Im running Android Revolution atm and I understand now how powerful GPU can be. I see virtually no lag in browser even in the longest website while doing pinch to zoom. Are there any other ROMS that have this kind of smoothness in browser? Let me know!!!
Question 2: My mytouch 4g lasts a while on a single charge. I browse for 2 hours andplay music 1 hour everyday and with wifi on about 5-6 hours I get 24-28 hours of battery on Mytouch. With Sensation Im barely getting 15 hours.

Whatever special features a rom has will be mentioned in the changelog or rom info page.
Although you didn't ask a second question, i'll assume you meant to ask if the battery life can be improved? I'd suggest flashing Bricked kernel (usually comes with ARHD) and not overclocking. Also turn data off when you're not using it...if you need longer battery life, i'd suggest buying an Evo 3D battery (fits the Sensation but more capacity) or purchasing a 1900 ma Ankar battery.
Hit Thanks if i've helped

In regards to your first question, you can actually enable GPU acceleration on ANY ROM by adding this line to your build.prop:
debug.sf.hw=1
These next two lines will help with smoothness:
video.accelerate.hw=1
debug.performance.tuning=1
Bada bing! Hope this helps
EDIT: Not sure if a stock kernel will work with these tweaks.. also, you MUST have a rooted device as you cannot edit the build.prop otherwise!

maff1989 said:
In regards to your first question, you can actually enable GPU acceleration on ANY ROM by adding this line to your build.prop:
debug.sf.hw=1
These next two lines will help with smoothness:
video.accelerate.hw=1
debug.performance.tuning=1
Bada bing! Hope this helps
EDIT: Not sure if a stock kernel will work with these tweaks.. also, you MUST have a rooted device as you cannot edit the build.prop otherwise!
Click to expand...
Click to collapse
That is SO AWESOME!!! So wait what are the limitations for this tweak? Can this be used in Single core devices like Mytouch 4g or like Incredible or other phones in general?

build.prop tweaks???

Has anyone found any build.prop tweaks that boost signal or wifi for the nexus s 4g that work or maybe perhaps some media profile.XML tweaks that let the camera take better pics or maybe play video back in better resolution????

Seriously? Take better pics, play high res movies is all hardware related for as far as I know lol.
For better signal, try flashing different radios.
Sent from my Nexus S

subnoize soulja said:
Has anyone found any build.prop tweaks that boost signal or wifi for the nexus s 4g that work or maybe perhaps some media profile.XML tweaks that let the camera take better pics or maybe play video back in better resolution????
Click to expand...
Click to collapse
Try:
ro.ext4fs=1
debug.sf.hw=1
pm.sleep_mode=1
video.accelerate.hw=1
debug.performance.tuning=1
What good it will do on 4.0+ android I do not know. It did wonders on gingerbread back in the day.
Sent from my Nexus S 4G using Tapatalk 2

Can you answer
Exit_Only said:
Try:
ro.ext4fs=1
debug.sf.hw=1
pm.sleep_mode=1
video.accelerate.hw=1
debug.performance.tuning=1
What good it will do on 4.0+ android I do not know. It did wonders on gingerbread back in the day.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
What does ro.ext4fs=1 mean
(just being cautious what i use on my Sony Xperia S)

For a while i thougt i was in t-mobile g1 forum

Ext4 is a linux filesystem, though I don't know what that command specific does about it.
If you're feeling lucky, you can open up the phone and put some solder ontop of the goldplated contacts for antennas to improve signals such as data and gps: http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1

[MOD] CM7.2 BASED ROMS build.prop mod

Well...I suppose this isn't devvin, but, I learned a little about build.prop modifications from the devs and experience on my Acer Iconia A100. Soooo, I decided to share a few tweaks that have made me notice some difference in performance.
Here is a cut of the lines I added into the build.prop:
============================================================================
# Added by justjackyl#
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapstartsize=8m
debug.performance.tuning=1
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
pm.sleep_mode=1
ro.config.nocheckin=1
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=150
=============================================================
This should give a slight boost on overall responsiveness, video performance, slight memory performance to the dalvik VM, and decrease wirelesss canning to save battery, as well as boost wireless performance and throuput, as well as possible power saving across the board (only slight increase, say 5-10% MAX so don't expect huge savings!)
Anyone willing to test with me? These tweaks really pumped life into my Tegra 2 tablet, and seem to being doing the same, while being stable so far, on my G2x.
To use the mod, you just need to use a root access file browser, browse to system, rename the current build.prop to build.prop.bak and copy and paste in the build.prop.mod one. Just make sure whichever one you are using, it is named build.prop with no extensions, so rename build.prop.mod to build.prop, and same to restore your back up original.
Than boot into recovery, wipe cache and dalvik cache, reboot and good to go.
Your first couple reboot cycles may be slower than normal as dalvik cache is rebuilding.
File----> justjackyl's build.prop mod for G2x

Posting this to see it in tapatalk and start trying it...!
ready, i put it after the V6 build.prop entries... only thing that i dont have used are the signal mods becouse v6 already have imput different values...
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
Click to expand...
Click to collapse

DankoFGL said:
Posting this to see it in tapatalk and start trying it...!
Click to expand...
Click to collapse
This should work on any CM7.2 ROM, maybe GB. I'll test that later.
It will not brick or cause bootloop on a CM7.2 ROM.

i use last cm7 nightly and worked well...

DankoFGL said:
Posting this to see it in tapatalk and start trying it...!
ready, i put it after the V6 build.prop entries... only thing that i dont have used are the signal mods becouse v6 already have imput different values...
Click to expand...
Click to collapse
I've actually never even used V6, so now I feel sorta stupid because I suppose most my tweaks are there. lol

Not, not all your tweaks are there, i use all of the twaks that you posted with the exception of the net edits
Enviado desde mi LG-P999 usando Tapatalk 2

DankoFGL said:
i use last cm7 nightly and worked well...
Click to expand...
Click to collapse
So you did notice a difference?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)

Let me test it for one or two days, i getting a litle better battery performance while sleeping, also my max events per sec are 200 and worked better than 150 at scrolling
Enviado desde mi LG-P999 usando Tapatalk 2

DankoFGL said:
Let me test it for one or two days, i getting a litle better battery performance while sleeping, also my max events per sec are 200 and worked better than 150 at scrolling
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Thanks, I'll keep that in mind.
I wonder if it may be a difference between Faux054 and Trinity158

Has you see any difference between this two kernels?
Enviado desde mi LG-P999 usando Tapatalk 2

DankoFGL said:
Has you see any difference between this two kernels?
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
In contrast to this mod?
Or between the two kernels themselves?

With or without the mod, talk.about your experience
Enviado desde mi LG-P999 usando Tapatalk 2

DankoFGL said:
With or without the mod, talk.about your experience
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Well...the mod itself is in testing, as these mods worked on a Tegra 2 tablet, but may not work so well for this Tegra 2 phone.
As for the kernels...
I started modding in Jan 2012 and faux was the first GB kernel I ever found, and so I kinda became a faux fanboy when going for CM7 ROMs.
I've used Trinity, but not much experience with the ELP series. (cricketAC intro'd me to those)
I've used faux and can't even remember how old.
Both SOD randomly. I was able to control it more with faux.
Both random reboot, not often. I found faux OOM Panic and reboot more often than Trinity, but I don't multi tasks too hard, so I kept it in control, but faux would lag like an SOB sometimes.
Both OC nicely, but I prefer faux over Trinity in this case. Faux offers more steps in between frequencies than the Trinity I used, while both obtained an OC of >=1.5GHz.
The steps in frequencies are important to me as An underclock at 750MHz than next step is 1GHz, with Trinity, or an underclock of I think 654MHz and steps to 816Mhz, 912MHz and 1GHz, as with faux.
With the steps being laid out, I had better battery with faux as it had more room to play with frequency steps than Trinity. If you only can jump from 750 to 1Ghz when 750 wasn't enough, than your using more juice than if you jumped from 654 to 816 to 912 and CPU finds 912 was enough, well you didn't hit 1GHz and saved a little bit more juice.
So faux wins in battery.
But, faux does not like to OC above 1.4MHz IMO as it heats up so fast >1.4GHz it freezes.
Trinity will sustain itself much longer at >=1.5GHz much longer before the overheat freeze.
It is really hard to pick. IMO
Faux
Pros: Battery, OC in smaller steps possible, great performance in gaming environment (just one large single task), less SOD than trinity
Cons: Overheats quicker at OC, seems to panic more in multi task situations, more random reboots than Trinity
Trinity
Pros:Smoother multi taks performance, more stable at higher OC speeds, less random reboots than faux
Cons: Consumes more battery, less tweaking OC steps, more SODs than faux
I think it really comes down to personal use. These are just my experiences for my uses. Results vary.

Okay, i've to say... that is one of the best explaniations post of the kernels i've readed, so thanks you, i will stay with faux more time according what you say...
Thanks you
Enviado desde mi LG-P999 usando Tapatalk 2

justjackyl said:
Well...I suppose this isn't devvin, but, I learned a little about build.prop modifications from the devs and experience on my Acer Iconia A100. Soooo, I decided to share a few tweaks that have made me notice some difference in performance.
Here is a cut of the lines I added into the build.prop:
============================================================================
# Added by justjackyl#
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapstartsize=8m
debug.performance.tuning=1
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
pm.sleep_mode=1
ro.config.nocheckin=1
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=150
=============================================================
This should give a slight boost on overall responsiveness, video performance, slight memory performance to the dalvik VM, and decrease wirelesss canning to save battery, as well as boost wireless performance and throuput, as well as possible power saving across the board (only slight increase, say 5-10% MAX so don't expect huge savings!)
Anyone willing to test with me? These tweaks really pumped life into my Tegra 2 tablet, and seem to being doing the same, while being stable so far, on my G2x.
To use the mod, you just need to use a root access file browser, browse to system, rename the current build.prop to build.prop.bak and copy and paste in the build.prop.mod one. Just make sure whichever one you are using, it is named build.prop with no extensions, so rename build.prop.mod to build.prop, and same to restore your back up original.
Than boot into recovery, wipe cache and dalvik cache, reboot and good to go.
Your first couple reboot cycles may be slower than normal as dalvik cache is rebuilding.
File----> justjackyl's build.prop mod for G2x
Click to expand...
Click to collapse
These tweaks were posted 5-6 months back, and there is another thread for them too. They are fine, not a major improvement though.....
old thread: http://forum.xda-developers.com/showthread.php?t=1806868

5 hours of battery with always the screen on and using is good?
Enviado desde mi LG-P999 usando Tapatalk 2

DankoFGL said:
5 hours of battery with always the screen on and using is good?
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Your battery life is not due to these tweaks...I`ve tried them a long ago.Trust me on this one

BigDig said:
These tweaks were posted 5-6 months back, and there is another thread for them too. They are fine, not a major improvement though.....
old thread: http://forum.xda-developers.com/showthread.php?t=1806868
Click to expand...
Click to collapse
That one is for stock GB 2.3.4, OP states.
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)

justjackyl said:
That one is for stock GB 2.3.4, OP states.
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
If you scroll the pages, they posted an cm7.2 buid prop also. The tweaks are fine, but nothing magnificent....

BigDig said:
If you scroll the pages, they posted an cm7.2 buid prop also. The tweaks are fine, but nothing magnificent....
Click to expand...
Click to collapse
Oh well. I tried.
Sometimes we overlook things on accident ...
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)