[XPERIA X8 Android Development] matmutant:
the following is outdated, kept for archive.

this is also my conclusion,

since we (nAa, D_d and me) want to keep "qcomuiccstack" in build.prop for its "network unlock dialog box" disabling property, we (you and me) need to show it has no side effect as i said before.

so :

now, please use qcomuiccstack condition and push your phone to the limits to see if it is as stable as with the control :)

the following is outdated, kept for archive.

thank you all for you help, please keep helping by following the new short and simple protocol

​

____________________________________________

we have 3 condtions to test :

in the build.prop you'll find the following :

ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall

after editing the build.prop, don't forget to reboot!

here are the 3 conditions :

1/ keeping as it is:

ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall

2/ add "qcomuiccstack"

ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall,qcomuiccstack

the 3/ is optionnal, please focus on 2/ + control (1/)

3/ delete "signalstrength" & add "qcomuiccstack"

ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,datacall,qcomuiccstack

here is the protocol :

for each :

fully charge,

use by the same way the phone for each (same phone call length, same web browsing length, same idle time while sleeping at the same place ...)

try 3g,2g,gsm,wifi,bluetooth,FMradio and all regarding connectivity for each

keep idle for at least 8hrs (and about the same time for each condition)

take a screen shot for each when about 10 battery % are left :)

on each screen shot, place numbers and comment the way you used the phone at each graph inflection or state (idle, wifi, 3g using, phone call ... )

tell us your phone carrier, and kind of network coverage (dBm) too please :)

repeat the test at least on 3 power cycle for each condition to be able to see how much the result is accurate

here is the way the 3 screen shots should look like :

*

on this screen the phone never really went idle properly and i used airplane mod, this is not how you should proceed, this is just an example of the way i would like to see the numbers ;)

you should proceed in similar way for each 3 condition so that the results can be comparable and the conclusion accurate!

what i wait for is:

the more people will do the test properly, and the more precisely they will do, the more accurate will be the results.

thanks for helping us !

have a nice day

m@

________________

my own results :

using 2/, i.e. :

ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall,qcomuiccstack

signal&carrier as control :

overall usage :

what is what? :

* **

0 - hard usage and normal 10 first % drain due to my old age battery, then, wifi browsing for some time (1h of moderate wifi usage)

1 - ~7h of idle, about -3%

2 - heavy wifi browsing, 100% usage for 1h30 -15%

3 - idle/wake alternate, we clearly see a difference between the two state

# i experience 1 reboot due to CPU overload during the current test, i don't know from what it comes from

never happened before, this is the only time in a few days of testing qcomuiccstack...

if during your tests you encounter a freeze/reboot, provide /proc/last_kmsg for debugging purpose

control :

little update to show a control,

all i consider is time idle and the battery decrease linked to it

the problem is, i can't keep the same build during the test protocol (i changed kernel, and rom yesterday for new kind of tests)

resulting in less and less accurate tests and results regarding battery life...