[DEV] Data on HD2 (ril tweaks)

Since I was not happy with my current battery life I decided to invest time in finding ril build.prop tweaks for our hd2. Wich will be readed by lib_htcril.so and will acutally work. Android htc ril interface supports over 60 commands.

All tough it looks our phone has a working data connection it works far from optimal. There is no rill officialy developed for our radio and singal is very sensitive in my experience.

RMNET is currently providing us stable data by loading desire rmnet radio code into the radio when start up. Altough we should know wich radio from the desire is included so we can use the right wrapper

Anyway I will here clearify some commands.
ro.ril.fast.dormancy.rule= 0 - 1 disable enable.Save a lot of battery by letting the phone request for fast dormancy. Phone will stay in UMTS until data is requested and will then switch to hdspa. This is not supported by all providers.

ro.ril.fd.scron.timeout= 0- to infinity in theory
The timeout in seconds after a data request before switching back.When screen is on

ro.ril.fd.scroff.timeout=0 to infinity in theory
The timeout in seconds after a data request before switching back.When screen is off.

ro.ril.enable.dtm=1
Dual transfer mode for networks that support calling and data connection at the same time.

ro.telephony.default_network=3 (0-8)
Not really new this will make the phone prefere a strong gsm singal over a really weak hdspa can save a bit of battery. This can also be set by typing *#*#4636#*#* in dialer

This are the ones I exactly know what they mean however after some testing I am using the following commands in build.prop by researching htc build.props
Altough I don't know the meaning of all it definately helps because I dont get a weird logcat out put when turning data on or off and it goes almost instant on and off with b4 wrapper in CLK.

Just some more clearyfing why we have high standby usage.
Because phone is searching a lot for singal in my case it can swtich from 1 bar to 5 bars in the same room.

The power usage in 3G can be reduced by using fast dormancy because the phone doesnt switch from 3g to hdspa when there is no data request but phone will still search for optimal singal but it wont constantly switch between 3g and hdspa and waste battery. (lost 4 % in 8 hour with constantly bumping singal)

What is the goal of this thread:
Giving everybody the chance for an optimal data experience and maybe useful for devs who wanna update radio code or update ril wrappers.

Yeah it should work especially that fast dormancy really hepls if your network support it. I tested this in combination with clk b4 wrapper in theory when we initialize ril on boot using tytung r10 instead of lib_htcrilwrapper.so it should work for sure.

Yeah well you just need to test I they will work for both. It depends the most on your provider. I Think because lack of missing code system has trouble by setting some parameters by it self. That is why It might be needed to apply the ril tweaks in build.prop.

Agree with the signal strength... my connection shows H, perfect reception when its laying on my desk, but as soon as i pick it up data drops to 1 or 0 bars. VERY sensitive.

Switching to GSM auto (PRL) seemed to do the trick for switching from H to E faster so i wont lose my reception and fixes the battery drain but this is still far from optimal use of our data connection as the data drops still occur as frequent as before.

Hi will this work on rafdroid 4.2 rom am a newb to changing code where to start and which folder etc and how to insert this code can u do it in zip form so we can flash it by mgldr?? or if not a step by step explanation of how to do it my kernal is rafdroid 1.9 thanking u in advance for any help on this

Since I was not happy with my current battery life I decided to invest time in finding ril build.prop tweaks for our hd2. Wich will be readed by lib_htcril.so and will acutally work. Android htc ril interface supports over 60 commands.

All tough it looks our phone has a working data connection it works far from optimal. There is no rill officialy developed for our radio and singal is very sensitive in my experience.

RMNET is currently providing us stable data by loading desire rmnet radio code into the radio when start up. Altough we should know wich radio from the desire is included so we can use the right wrapper

Anyway I will here clearify some commands.
ro.ril.fast.dormancy.rule= 0 - 1 enable disable.Save a lot of battery by letting the phone request for fast dormancy. Phone will stay in UMTS until data is requested and will then switch to hdspa. This is not supported by all providers.

ro.ril.fd.scron.timeout= 0- to infinity in theory
The timeout in seconds after a data request before switching back.When screen is on

ro.ril.fd.scroff.timeout=0 to infinity in theory
The timeout in seconds after a data request before switching back.When screen is off.

ro.ril.enable.dtm=1
Dual transfer mode for networks that support calling and data connection at the same time.

ro.telephony.default_network=3 (0-8)
Not really new this will make the phone prefere a strong gsm singal over a really weak hdspa can save a bit of battery. This can also be set by typing *#*#4636#*#* in dialer

This are the ones I exactly know what they mean however after some testing I am using the following commands in build.prop by researching htc build.props
Altough I don't know the meaning of all it definately helps because I dont get a weird logcat out put when turning data on or off and it goes almost instant on and off with b4 wrapper in CLK.

Just some more clearyfing why we have high standby usage.
Because phone is searching a lot for singal in my case it can swtich from 1 bar to 5 bars in the same room.

The power usage in 3G can be reduced by using fast dormancy because the phone doesnt switch from 3g to hdspa when there is no data request but phone will still search for optimal singal but it wont constantly switch between 3g and hdspa and waste battery. (lost 4 % in 8 hour with constantly bumping singal)

What is the goal of this thread:
Giving everybody the chance for an optimal data experience and maybe useful for devs who wanna update radio code or update ril wrappers.

Hi,

This is very cool set!

i will use it in my ROM,

Your name will be in my build prop.

but first i will check that all ok, dont want my users to lose data / wifi / signal.

CWM is not possible because each build is using a different build.prop

@dorimanx only issue is that some networks dont support fast dormancy. And then it will use extra battery instead of saving. Then you need to set fast dormancy rule = 0
For the rest I don't see any disadvantage of using this tweaks.

@dorimanx only issue is that some networks dont support fast dormancy. And then it will use extra battery instead of saving. Then you need to set fast dormancy rule = 0
For the rest I don't see any disadvantage of using this tweaks.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service