[DEV] miniCM9 debug only thread (shakira, robyn and mimmi) 19/07/12

---

[DEV] miniCM9 debug only thread (shakira, robyn and mimmi)

there is 3 thread for miniCM9, each device specific.
things i say in one thread is also applicable to others

for debugging purpose, i need this only thread for the 3 devices to centralize the data

this thread is NOT for asking or requesting anything, it is there for providing test results !

the thing i ask you to focus about is battery life since it is an important thing.

post #2 : gsm standy influence on battery life
post #3 : system app freezing and battery life
post #4 : adreno config and performance improvement (GPU)

to improve miniCM9, you could :

• post results after following protocols,
• help me to set up test new protocols,
• give advices about them
• suggest things to investigate IF you can prove it worths to

debug part1

---

Dear miniCM9 users, you wanna help us to increase miniCM9 battery life ? (regarding GSM standby)

here is a simple protocol to find if some conditions can or not increase battery life without messing up everything else

atm, we will see for gsm standby that seems to extremely eats battery when phone is idle
thank to sonty for the idea on which the following protocol is based

since there is no difference between conditions on batterylife, we now want to prove qcomuiccstack has no side effect.

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

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

protocol ended, qcomuiccstack used as defaulf in miniCM9, if you have any other idea, feel free to share

protocol opened again, see there for details :
http://forum.xda-developers.com/show...&postcount=173


after editing the build.prop, don't forget to reboot!
here are the 2 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

push your phone to its limits, and see if the 2/ condition is as stable as control.

__________________________
NB :
245~748MHz, smartassV2, KSM, UV, zram18%, purging of assest, dithering, 16bit transparency.
theses apps are frozen (+dsp manager that is just deleted), and will be same for all the next tests i'll do (need two more power cycles for qcomuiccstack, and then 3 of control)


__________________________

old protocol, kept for archive

Originally Posted by matmutant

________________________
NB :
245~748MHz, smartassV2, KSM, UV, zram18%, purging of assest, dithering, 16bit transparency.

theses apps are frozen (+dsp manager that is just deleted), and will be same for all the next tests i'll do (need two more power cycles for qcomuiccstack, and then 3 of control)


__________________________

Are those obligatory? I mean should everybody use exactly those settings and exactly those apps frozen? In that case I should disable my swap, right? What about ext? Or are we gonna test stability regardless of everybody`s various conditions? Just asking to be sure of what we are aiming at.

Originally Posted by drfr

Are those obligatory? I mean should everybody use exactly those settings and exactly those apps frozen? In that case I should disable my swap, right? What about ext? Or are we gonna test stability regardless of everybody`s various conditions? Just asking to be sure of what we are aiming at.

absolutely not, this my own example, do what you want, just keep same configuration between each of your personnal tests

Good and wanted to inform you that the battery got me consume 1% or more per hour and that the deceased was the GPS that was in the background without being able to see on and eats the battery disable storing means that when more clear to remove the GPS got a 2% but 1% should be no more than that I have the settings qcomuiccstack and then adding Sonty and I put the famous apex that I can remove the animations to your more and I got the 1% per hour or more
but what I did was descargarme the ROM and put it all started again in the ZIP to install it I got it and added the pitcher also underolt the CPU and I have a frequency of 122 to 480 that do not cost much to put both processor by the time I see you now I'll upload it and installing it works applications for everyday

So I take from last night that I first had a 30% loading or leave it overnight and not to download vuevle fast as to, by which the carrying cuadno happened before that and now I'm doing well =)

Originally Posted by VinceMetalHeart

Good and wanted to inform you that the battery got me consume 1% or more per hour and that the deceased was the GPS that was in the background without being able to see on and eats the battery disable storing means that when more clear to remove the GPS got a 2% but 1% should be no more than that I have the settings qcomuiccstack and then adding Sonty and I put the famous apex that I can remove the animations to your more and I got the 1% per hour or more
but what I did was descargarme the ROM and put it all started again in the ZIP to install it I got it and added the pitcher also underolt the CPU and I have a frequency of 122 to 480 that do not cost much to put both processor by the time I see you now I'll upload it and installing it works applications for everyday

So I take from last night that I first had a 30% loading or leave it overnight and not to download vuevle fast as to, by which the carrying cuadno happened before that and now I'm doing well =)

Very good but this translate is not very much comprehensible, sorry. GPS turned off is all too obvious, this is not the culprit for all of us.

Originally Posted by drfr

Very good but this translate is not very much comprehensible, sorry. GPS turned off is all too obvious, this is not the culprit for all of us.

Well is there not translate all the truth I have a high level of English for
write everything down and do what I can xD
so I wonder if those people have and limit standard limit processes that consume that is not to do things more and I have it disabled may be the culprit: S

Well, you should use the betterbatterystats and autorun manager that helps to locate my battery wear and locate it that would put the GPS when at rest

245~748MHz, smartassV2, KSM, UV, zram18%, purging of assest, dithering, 16bit transparency.

"qcomuiccstack"

I'm using this now! I disable some apps,unistall dsp manager and reboot. I think that battery is better for now in 5 minutes.

My other settings: no animations, ultra brightness+auto brightness...
I'll charge it now to 100% and I'll leave charging for some time, now it's 77%.
I'll leave phone discharging at night and I'll see at morning how many % will be lost !

GOOD LUCK MY BATTERY

And I'll try next day with "undervolt" "122MHz -600Mhz" ...

Hey guys,
at last I can see some progress in battery drain problem.
Since sonty came with the qcomuiccstack tweak and proved that it had influence on his battery life I´ve been using it too, but couldn´t see any difference for me. So it was obvious something else had to play role and I´ve been continually searching for it.
There are couple of posts around that claim proper charging and battery calibrating might help.
I wasn´t particularly positive about that but I changed my mind.
Here´s what I did:
Charged to 100% while connected to PC /haven´t tried with wall charger yet/, powered off, waited for a while, went to recovery, wiped battery stats and rebooted, still connected. After full boot, battery was at 99%, waited till 100% and then disconnected. Since then I´m observing 1% power usage per hour and it´s been around 4 days now.
Funny part is that when I tried "plain" reboot since then, drain came back to 4%, but after another reboot while connected to PC /without charging to 100% and without wiping stats/, 1% returned! I was able to reproduce this for a couple of times. I even tried the brave thing and did a fresh install of ROM after full wipes, added qcomuiccstack back, did this charging procedure and I´m still on 1% !



Edit: might be useful to say what are my other settings, but I haven´t changed them for some time. Anyway: smartassV2 122-748, no compcache but swap partition 256M, no KSM, no UV, sd-ext on ext4 without journaling /if interested, can post how/, no auto syncing, couple of useless apps disabled /if interested can post which/.

Just an udpate to previous post.
Yesterday I tried "plain" reboot with device disconnected from PC and no drain occured! It´s even less than 1% per hour now. Things seem to "settle down".



Edit:
Here`s my disabled apps list:
Android Live Wallpapers, AntHalService, Black Hole, Bubbles, CyanogenMod Wallpapers, Default Input, DSP Manager, Email, Exchange Services /this one seems to be important/, FM Radio, Google Calendar Sync, Google Search, Live Wallpaper Picker, Magic Smoke Wallpapers, Maret Feedback Agent, Market Updater, MiniCM Update Notification, Music Visualisation Wallpapers, Network location, News & Weather, Phase Beam, Pico TTS, Setup Wiyard, Sound Recorder, Speech Recorder, Talk, Trebuchet, Voice Dialer

Edit:
After several hours later the drain came back - reboot while connected solved the problem .... again.