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.a52.%s
(gprs encryption algorithm)
ro.ril.a53.%s
(gprs encryption algorithm)
ro.ril.enable.a52=0-1
disable enable encryption a52
ro.ril.enable.a53=0-1
disable enable encryption a53
ro.ril.enable.dcm.feature= 0- 1
Database Correlation Method to get phone location I was getting faster an data connection when on however phone was finding this value by it self was my experience.
ro.ril.radio.svn= 0-99
to identify phones more easily currently displayed as 01 on our hd2.
ro.ril.qos.traffic.priority= 0-3
(lowest priority =0 highest =3) request QOS priority in your network might not be supported by your provider.
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.
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.a52.%s
(gprs encryption algorithm)
ro.ril.a53.%s
(gprs encryption algorithm)
ro.ril.enable.a52=0-1
disable enable encryption a52
ro.ril.enable.a53=0-1
disable enable encryption a53
ro.ril.enable.dcm.feature= 0- 1
Database Correlation Method to get phone location I was getting faster an data connection when on however phone was finding this value by it self was my experience.
ro.ril.radio.svn= 0-99
to identify phones more easily currently displayed as 01 on our hd2.
ro.ril.qos.traffic.priority= 0-3
(lowest priority =0 highest =3) request QOS priority in your network might not be supported by your provider.
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.
Last edited:
