[ROM][GEN2]CyanogenMod 7 (Android 2.3.7)

[Guest achmann]

(sorry haven't read whole thread)

Reading the first post would have been enough.

[Guest dadashi]

since 7.0.3 upgrade my SF dies after I unplug from charger...Pressing the power button doesn't work and I have to remove the battery and then press power each time....

[Guest sej7278]

One hot candidate for high drain is issue 3608. Seems it's not sensors after all but the audio circuits that sometimes do not get powered down properly. This exists since N40.

i think you're right - i've lost 30% or more in 7 hours of standby with n64, apparently dialer used 33% of the battery in the last 13 hours so is the likely candidate as i've been playing with the speaker issue.

[Guest _amano]

since 7.0.3 upgrade my SF dies after I unplug from charger...Pressing the power button doesn't work and I have to remove the battery and then press power each time....

Because 7.0.3. is an old build (just a security fix different from 7.0.2). Use a 7.1 nightly to get the charger issues fixed.

[Guest]

i think you're right - i've lost 30% or more in 7 hours of standby with n64, apparently dialer used 33% of the battery in the last 13 hours so is the likely candidate as i've been playing with the speaker issue.

I agree on this!

I performed a few tests and it looks like N64 is better than N63 on this point: in N63, any time a sound was played, the hiss appeared and never stopped; in N64, the hiss appears but stops after a few secs, except in the case of notifications...

The only way to stop the hiss is to reboot the phone.

Do you confirm this behaviour on your blades?

[Guest sej7278]

I agree on this!

I performed a few tests and it looks like N64 is better than N63 on this point: in N63, any time a sound was played, the hiss appeared and never stopped; in N64, the hiss appears but stops after a few secs, except in the case of notifications...

The only way to stop the hiss is to reboot the phone.

Do you confirm this behaviour on your blades?

could you put that info on the issue tracker? http://code.google.com/p/cyanogenmod/issues/detail?id=3608

[Guest Grain]

Take off the battery case and touch the SIM and SD-Card. See if they are hot.

For me they get hot when charging or when using GPS.

I don't know the location of the battery temperature sensor but maybe it is affected by whatever part of the phone heats up the SD card and SIM.

The battery sensor and/or the software reading the battery sensor in the Blade are pretty much broken. I got ~50°C readings the whole afternoon yesterday with the phone sleeping, ~1% drain per hour, in the shadow.

Can perhaps someone with a Froyo firmware install Battery Manager Widget, let it run for some days, and report whether temperature readings are strange there as well? (but I'd guess so as there is pretty much no change in this regard from Froyo to Gingerbread)

Re Issue 3608, Ogami, you are wrong. Nothing has changed between N63 and N64 in this regard. What you are seeing is normal for the bug - it triggers only in special situations. See the steps to reproduce the hissing state in the issue tracker. Please do not add comments to the tracker without reading it thorougly.

[Guest]

could you put that info on the issue tracker? http://code.google.com/p/cyanogenmod/issues/detail?id=3608

Was thinking about this, done now :unsure:

[Guest sej7278]

The battery sensor and/or the software reading the battery sensor in the Blade are pretty much broken. I got ~50°C readings the whole afternoon yesterday with the phone sleeping, ~1% drain per hour, in the shadow.

i think 1% per hour of standby is fine. that's what i was getting on mcr12 as i recall. that's gone up to 5% per hour on n64 with the broken libaudio.

the temperate readings i think have been broken throughout cm7. my gen1 oled is always 25-35c even though it feels hotter when its charging.

your 50c seems insanely hot for just standby. have you tried the 2nd libaudio.so patch?

[Guest alex1alex2alex3alex4]

Re Issue 3608, Ogami, you are wrong. Nothing has changed between N63 and N64 in this regard. What you are seeing is normal for the bug - it triggers only in special situations. See the steps to reproduce the hissing state in the issue tracker. Please do not add comments to the tracker without reading it thorougly.

As wbaw briefly mentioned the white noise appeared with the Gen2 libaudio.so and it should be fine with the Gen1

version I swapped in the Gen1 libaudio.so from N39 while installing N64 this morning, tried a few things, and so far

no problems, no hiss.

Will monitor it for a while and report back again later.

[Guest]

Re Issue 3608, Ogami, you are wrong. Nothing has changed between N63 and N64 in this regard. What you are seeing is normal for the bug - it triggers only in special situations. See the steps to reproduce the hissing state in the issue tracker. Please do not add comments to the tracker without reading it thorougly.

Cross posts - re-read the comments & deleted mine :unsure:

Edited May 9, 2011 by Guest

[Guest targetbsp]

Any of you guys tried the fixed lib TomG posted in the comments for the hissing issue?

[Guest dadashi]

Because 7.0.3. is an old build (just a security fix different from 7.0.2). Use a 7.1 nightly to get the charger issues fixed.

Thanx, but from what I'm reading the nightlies have a range of other problems. I prefer a stable release....I didn't have this issue with 7.0.2 so I might go back to that...

[Guest sej7278]

Any of you guys tried the fixed lib TomG posted in the comments for the hissing issue?

yes i just tried the 2nd patch (comment #19) and updated the issue tracker. it seems to fix the hiss, but not battery drain on n64.

[Guest targetbsp]

Really? Aside from the hissing issue, which as I posted above there is a fix for, N62 and above are sounding the best CM7's yet to me! I'm still on an ancient CM7 but I'm looking to go Gen 2 and N62+ as soon as the battery drain (which is suspected to be the speaker) is fixed.

Though I'll be going via 7.03 to log that notification led bug.

Also 7.03 has no changes other than a security bug fix so that it introduced the charging issue over 7.02 makes no sense... :S More likely 7.02 has the issue and you just didn't experience it - it is random.

[edit]

yes i just tried the 2nd patch (comment #19) and updated the issue tracker. it seems to fix the hiss, but not battery drain on n64.

Ah well, waiting a bit longer then. :unsure:

Edited May 9, 2011 by targetbsp

[Guest alex1alex2alex3alex4]

yes i just tried the 2nd patch (comment #19) and updated the issue tracker. it seems to fix the hiss, but not battery drain on n64.

Did you make sure maps / market aren't active in the background ?

[Guest manji]

Did you make sure maps / market aren't active in the background ?

One thing I've noticed is that Maps doesn't go completely out since 5.2.0 or something (maps version).

But it could have be related to the GPS 'sensor' as it seems to be present in the Spare Parts' list.

[Guest sej7278]

Did you make sure maps / market aren't active in the background ?

market is running in the background but using no battery, wifi/gps/3g are off. this is fresh from being powered off during a charge cycle.

display is using 49% of the battery, dialler is now using 21%, android is 19% and a few other bits using the rest (<5% each).

dialler is the process whose usage is creeping up, not maps/market.

i have maps 5.4 installed but with gps/3g off it has no way to run.

Edited May 9, 2011 by sej7278

[Guest alex1alex2alex3alex4]

i have maps 5.4 installed but with gps/3g off it has no way to run.

Which doesn't mean it won't try ... in the background.

It is there, lurking, since I manually stop it after a reboot I don't have

any drains anymore while the phone is sitting there idle.

[Guest sej7278]

Which doesn't mean it won't try ... in the background.

It is there, lurking, since I manually stop it after a reboot I don't have

any drains anymore while the phone is sitting there idle.

its not in my running process list.

i only get battery drain when i make/receive a call and use the speaker.

[Guest Grain]

your 50c seems insanely hot for just standby. have you tried the 2nd libaudio.so patch?

Yes. But it's unrelated. The 50+°C readings are just wrong. Apart from the fact that the phone was cool, battery would drain A LOT if something was heating the phone that much.

yes i just tried the 2nd patch (comment #19) and updated the issue tracker. it seems to fix the hiss, but not battery drain on n64.

How can you tell that quick? Checking battery drain takes a while. You have to test at least half a day to be reasonably sure. Detailed battery stats (spare parts, battery history) are a jumble and cannot be trusted. I often see apps way up (in the 50% range) with the phone sleeping already for hours, and with the normal ~1% battery drain per hour.

[Guest sej7278]

How can you tell that quick? Checking battery drain takes a while. You have to test at least half a day to be reasonably sure. Detailed battery stats (spare parts, battery history) are a jumble and cannot be trusted. I often see apps way up (in the 50% range) with the phone sleeping already for hours, and with the normal ~1% battery drain per hour.

yes i'm going to leave the phone a few hours now and see how it goes with the 3rd patch applied, as although the battery stats are high for the dialler process, the actual battery drain is still minimal at the moment - if you can even believe the battery monitor!

its silly of me to dry to test the issue when you can't trust any of the stats/sensors/readings to be accurate, i guess you can only tell by seeing how long it takes for the phone to turn off from having no battery left at all.

Edited May 9, 2011 by sej7278

[Guest targetbsp]

The battery usage thing makes absolutely no sense to me. If I flatten the battery playing a game from full battery to pretty much empty it'll tell me the game used 20-odd % of the battery. If I load maps for a minute and then shut it down (and confirm its not running in a task manager) its battery usage will continue to gain in percentage over days despite the phone running down at its normal idle rate.

So to me, the fact the battery is staying at a high percentage despite what usage reports is pretty promising.

[Guest sej7278]

The battery usage thing makes absolutely no sense to me. If I flatten the battery playing a game from full battery to pretty much empty it'll tell me the game used 20-odd % of the battery. If I load maps for a minute and then shut it down (and confirm its not running in a task manager) its battery usage will continue to gain in percentage over days despite the phone running down at its normal idle rate.

So to me, the fact the battery is staying at a high percentage despite what usage reports is pretty promising.

yes, we've just proven that the libaudio.so speaker hiss issue is fixed and the patch (#19) submitted, and isn't related to battery drainage - by testing n36's libaudio.so which was before the sip fix broke the sound system!

all the battery stats are complete bullshit it seems, although i think there is still something draining the battery intermittently.

you've got to think of the battery stats as a percentage of a percentage - i.e. even though stats say dialer is using 21% of the battery, battery remaining is still at 94%, so its still only 21% of the 6% battery that has discharged (so just over 1%) its not like dialer has eaten 21% of the charge, just 1%, which is still a bit high given that 1% is about an hour of standby.

maybe the "battery use" gui should be changed to display the usage as a percentage of total battery life, so instead of 21% (of 6% used) it should say 1% (of 100% capacity).

[Guest alex1alex2alex3alex4]

maybe the "battery use" gui should be changed to display the usage as a percentage of total battery life, so instead of 21% (of 6% used) it should say 1% (of 100% capacity).

That would give you very, very low readings until a substantial percentage of the battery has been used,

imho a percentage relative to what's been used already makes more sense.