1079 replies to this topic

[Gerhard_H]

peterj, on 30 May 2011 - 05:55 PM, said:

Hi *,


The second problem perhaps is a bit more tricky. Bluetooth seems to work so (it shows some devices in reach). But it does not work any longer with the hands-free equipment in my car (Audi "RNS-E"), it doesn't see it anymore.
I had the same problem long time ago with old modaco-Builds, but CM 6.1 worked great. Maybe it has something to do with the kernel-freqs?

Ditto here, no bluetooth connectivity to Audi RNS-E up to nightly-15, upgraded already to nightly-18 and will try tomorrow.
Connectivity to the bluetooth-capable cd-player JVC KD-BT1 in my other car does work. strange.

Sorry, wrong device, my problem is Galaxy S related, but maybe same problem ?

Gerhard

Edited by Gerhard_H, 06 June 2011 - 12:59 PM.

[iugrina]

I've been playing with GPS and nightlies for a while and the summary is
that mod/phone will restart only if I turn the screen off
(and continue to use GPS). I've tested it on cyanogenmod + full wipe.

[duck]

I've had another problem with the GPS, when it loses signal it takes a very long time to reaquire a lock, and thus leave long stretches bare when recording with MyTracks... Not good. Only had it spontaneously reboot once with the GPS on and that was ages ago, I had just entered the stairwell (no gps signal in this concrete bunker) and turned the screen on and splat. :-)

[vetinari]

Hello, I am new here!

In case anyone is interested, I compared CM 6.1 (final) against CM 7 (#84) regarding battery and performance. I noticed that CM7 is finally stable enough and it does not feel sluggy at all, but it somehow feels like the battery last less than with CM6.1.

Performance:
BenchmarkPI w/ CM6.1: 13494. BenchmarkPI w/ CM7: 10596. The lower the better, so CM7 wins (22% faster?).
Linpack w/ CM6.1: 2302. Linpack w/ CM7: 3147. The higher the better, so CM7 wins (27% faster?).

Methodology:
I did not enable JIT in 6.1, so unless it is enabled by default, that would account for the difference. I only ran the tests once (no average values, I know), with zero apps manually loaded. Of course, I rebooted a couple of times after flashing (wiping everything first) to make sure that the system becomes stable.
Edit: After enabling JIT in CM6.1, BenchmarkPI returns 13236, so no change. After enabling JIT in CM6.1, Linpack returns 3626, so it's much better than default CM7.

Battery:
In CM6.1, the battery runs out in: 230.113 minutes. In CM7, the battery runs out in: 162.467 minutes. The higher, the better, so CM61 wins (30% more battery?).

Methodology:
Battery Dog records to a CSV file in the SD the battery percentage at any given moment. PlaysVideo runs a video in an infinite loop. So, after charging battery up to 95%, I started logging the battery levels and started playing the "wildlife.mp4" video (which came with the phone). So, the screen remains on while the video is playing until the battery runs out.
This is done with WiFi on (syncing to 1 Google account, Facebook, 1 email account, and Twyca pulling for twitter mentions, everything with the default frequencies), GPS on (indoors, no signal), media sound off and airplane mode on. Why airplane mode on? Well, I did not want unnecessary interruptions.
Yes, I would have liked to have a battery of tests that can benchmark more aspects from the phone with many different conditions, but there is no such app and I can't create one of my own. It's as good as I could get it.

Conclusion: Gingerbread is noticeably faster, probably due to JIT, but the battery performance is horrible compared to Froyo. Since I do not think that there is a big improvment in 2.3 over 2.2 (I use Swype as a keyboard anyway), I'm going back to Froyo and I will stay there. I will miss the crisper OS icons in GB, but I think the extra battery is worth it.

PS: Please someone check my percentages, I'm horrible at maths.

Edited by vetinari, 08 June 2011 - 05:51 PM.

[M@rk]

vetinari, on 08 June 2011 - 03:16 PM, said:

Hello, I am new here!

In case anyone is interested, I compared CM 6.1 (final) against CM 7 (#84) regarding battery and performance. I noticed that CM7 is finally stable enough and it does not feel sluggy at all, but it somehow feels like the battery last less than with CM6.1.

Performance:
BenchmarkPI w/ CM6.1: 13494. BenchmarkPI w/ CM7: 10596. The lower the better, so CM7 wins (22% faster?).
Linpack w/ CM6.1: 2302. Linpack w/ CM7: 3147. The higher the better, so CM7 wins (27% faster?).

Methodology:
I did not enable JIT in 6.1, so unless it is enabled by default, that would account for the difference. I only ran the tests once (no average values, I know), with zero apps manually loaded. Of course, I rebooted a couple of times after flashing (wiping everything first) to make sure that the system becomes stable.
Edit: After enabling JIT in CM6.1, BenchmarkPI returns 13236, so no change. After enabling JIT in CM6.1, Linpack returns 3626, so it's much better than default CM7.

Battery:
In CM6.1, the battery runs out in: 230.113 minutes. In CM7, the battery runs out in: 162.467 minutes. The higher, the better, so CM61 wins (30% more battery?).

Methodology:
Battery Dog records to a CSV file in the SD the battery percentage at any given moment. PlaysVideo runs a video in an infinite loop. So, after charging battery up to 95%, I started logging the battery levels and started playing the "wildlife.mp4" video (which came with the phone). So, the screen remains on while the video is playing until the battery runs out.
This is done with WiFi on (syncing to 1 Google account, Facebook, 1 email account, and Twyca pulling for twitter mentions, everything with the default frequencies), GPS on (indoors, no signal), media sound off and airplane mode on. Why airplane mode on? Well, I did not want unnecessary interruptions.
Yes, I would have liked to have a battery of tests that can benchmark more aspects from the phone with many different conditions, but there is no such app and I can't create one of my own. It's as good as I could get it.

Conclusion: Gingerbread is noticeably faster, probably due to JIT, but the battery performance is horrible compared to Froyo. Since I do not think that there is a big improvment in 2.3 over 2.2 (I use Swype as a keyboard anyway), I'm going back to Froyo and I will stay there. I will miss the crisper OS icons in GB, but I think the extra battery is worth it.

PS: Please someone check my percentages, I'm horrible at maths.

Useful info - thanks vetinari.  Unfortunately I think (from my own experience only) with airplane mode off, (i.e. Phone Idle and Cell Standby on)... battery drain would be even quite a lot higher than what you've experienced, even without taking any call or SMS/MMS   

My latest experience is also that the battery doesn't drain consistently, even if the phone is not used. It crashes to empty from about 35-40% to 0 very, very quickly. Have tried resetting stats, etc. but same results.

Any suggestions on the best-baked Froyo ROM to try? I went from I think cupcake (MoDaCo 3.1?) to CM7 GB 2.3.4 so I have no idea what Froyo can or can't do versus GB  

[SteelBytes]

had phone reboot when trying to use GPS today. was running build 82. didn't get this way back in 2.3.2 / 2.3.3 (I think).  but rarely use GPS so don't know when it first started on my phone

[elelinux]

SteelBytes, on 12 June 2011 - 08:59 AM, said:

had phone reboot when trying to use GPS today. was running build 82. didn't get this way back in 2.3.2 / 2.3.3 (I think).  but rarely use GPS so don't know when it first started on my phone

Strange this GPS issue for some,I have been testing this GPS with different navigations applications but manage not to have a reboot or other strange stuff,Some good news,I have been working on Las_Venturas the last days,and now the camera works perfect for me, and another user in Sweden who have tried.The kernel is available on my thread on xda and I hope that more will test, soon we have a good working 2.6.35 kernel to Hero (I hope).

[iugrina]

elelinux, on 12 June 2011 - 08:31 PM, said:

Strange this GPS issue for some,I have been testing this GPS with different navigations applications but manage not to have a reboot or other strange stuff,Some good news,I have been working on Las_Venturas the last days,and now the camera works perfect for me, and another user in Sweden who have tried.The kernel is available on my thread on xda and I hope that more will test, soon we have a good working 2.6.35 kernel to Hero (I hope).

Have you tried using GPS with your screen off?

[elelinux]

iugrina, on 12 June 2011 - 08:38 PM, said:

Have you tried using GPS with your screen off?

Yes I tried maverick today no problems at all, but im running LV-0.4.6.3 kernel for moment,will try with flykernel to.

[M@rk]

Update on my high battery drain investigations since about Nightly 68... sorry for the long post.

One thing I had not yet been aware of or tried in my hunt for the battery eating culprit, was the (phone) network settings. I discovered if you go into phone Testing menu (to get there, use the phone's dialer, key in *#*#4636#*#* don't press call or anything, it will go into the menu after the last '*' is pressed - then select Phone Information - I found my phone was on default of WCDMA Preferred. BTW - pressing the external MENU button on your phone when on that screen also allows you to Select Radio Band.

In the Phone Info details of that screen however, I could see that my phone was switching betwen HSDPA and EDGE network types very often. Each time it did is when I could hear the radio interference in my desk speakers. The problem seems to be where I am at work, my phone is switching between two cell towers, one enabled for 3G, one using EDGE (a bolt on to 2G to enhance data rates apparently) or something like that (try 'Open Signal Maps' for some interesting info about your cell and wifi). Maybe this switching even happens because the 3G cell is overloaded... who knows.

Anyway - it seems that with the default preferred network type (WCDMA preferred), my phone's radio was constantly powering up to try find a 3G signal when it dropped to 2G, (and also preventing sleep I think).

My phone's battery usage showed a lot is used by Cell Standby and Phone Idle (40-50% combined) since I started trying to solve this on CM7. In Cell Standby details, you can also see Time Without Signal - this should be low (0-5%). If it's high, it means phone is searching (and consuming loads of battery!).

I've subsequently set network to GSM only (or GSM auto (PRL)) - I think this works the same as going into settings -> Wireless & networks -> Mobile Networks - > Use only 2G networks. There's also a 2G/3G button in power widget and I'll use that now - so when I'm away from my desk I can enable 3G again. I use WiFi at work anyway. My Mobile Data connection is OFF unless I specifically want to use it anyway, which is why I never suspected this to be a problem. But I think even though you might not be using Mobile Data (3G), doesn't mean your Hero is not trying to stay connected to a 3G level of service. Maybe this is only a problem on the old GSM network here in South Africa where 2G is still prevalent.

One thing I suspect is that perhaps in CM7 since 2.3.3 something has changed in this default network setting. Can anyone offer insight on this? I suspect this because I've been on the latest radio for some time - even on older ROMs - with no battery problems at all - but I'm not sure if these settings come in via the ROM or the Radio. Only since switching to CM7 did this whole battery drain problem come up - and I've sat at the same desk for nearly two years now

I think I've found the problem on my phone/circumstances. Now Cell Standby and Phone Idle are way down on the list of battery useage. Display is tops with 70-80%, which is how it should be IMHO. Battery life seems a lot (>40%) better now - will update after a few more days.

Hope this helps... thought I'd share... learned a lot the last few days. What a way to spend a Sunday evening with my Hero

[vetinari]

M@rk, on 13 June 2011 - 10:02 AM, said:

I could see that my phone was switching betwen HSDPA and EDGE network types very often.

If you read a few posts earlier, you will find me talking about two benchmarks: CM6.1 vs CM7 in terms of performance and battery. The battery benchmark was done with radio off, and yet there is a very noticeable battery drop in CM7 compared to CM6.1. So, it looks like radio is either not the only culprit or not the main one when it comes to battery usage.

Of course, fixing radio to either 3G or 2G (specially to 2G) will increase your battery, I'm not saying it won't.

[ASHURiCAN.iDe]

M@rk, on 13 June 2011 - 10:02 AM, said:

Update on my high battery drain investigations since about Nightly 68... sorry for the long post.

One thing I had not yet been aware of or tried in my hunt for the battery eating culprit, was the (phone) network settings. I discovered if you go into phone Testing menu (to get there, use the phone's dialer, key in *#*#4636#*#* don't press call or anything, it will go into the menu after the last '*' is pressed - then select Phone Information - I found my phone was on default of WCDMA Preferred. BTW - pressing the external MENU button on your phone when on that screen also allows you to Select Radio Band.

In the Phone Info details of that screen however, I could see that my phone was switching betwen HSDPA and EDGE network types very often. Each time it did is when I could hear the radio interference in my desk speakers. The problem seems to be where I am at work, my phone is switching between two cell towers, one enabled for 3G, one using EDGE (a bolt on to 2G to enhance data rates apparently) or something like that (try 'Open Signal Maps' for some interesting info about your cell and wifi). Maybe this switching even happens because the 3G cell is overloaded... who knows.

Anyway - it seems that with the default preferred network type (WCDMA preferred), my phone's radio was constantly powering up to try find a 3G signal when it dropped to 2G, (and also preventing sleep I think).

My phone's battery usage showed a lot is used by Cell Standby and Phone Idle (40-50% combined) since I started trying to solve this on CM7. In Cell Standby details, you can also see Time Without Signal - this should be low (0-5%). If it's high, it means phone is searching (and consuming loads of battery!).

I've subsequently set network to GSM only (or GSM auto (PRL)) - I think this works the same as going into settings -> Wireless & networks -> Mobile Networks - > Use only 2G networks. There's also a 2G/3G button in power widget and I'll use that now - so when I'm away from my desk I can enable 3G again. I use WiFi at work anyway. My Mobile Data connection is OFF unless I specifically want to use it anyway, which is why I never suspected this to be a problem. But I think even though you might not be using Mobile Data (3G), doesn't mean your Hero is not trying to stay connected to a 3G level of service. Maybe this is only a problem on the old GSM network here in South Africa where 2G is still prevalent.

One thing I suspect is that perhaps in CM7 since 2.3.3 something has changed in this default network setting. Can anyone offer insight on this? I suspect this because I've been on the latest radio for some time - even on older ROMs - with no battery problems at all - but I'm not sure if these settings come in via the ROM or the Radio. Only since switching to CM7 did this whole battery drain problem come up - and I've sat at the same desk for nearly two years now

I think I've found the problem on my phone/circumstances. Now Cell Standby and Phone Idle are way down on the list of battery useage. Display is tops with 70-80%, which is how it should be IMHO. Battery life seems a lot (>40%) better now - will update after a few more days.

Hope this helps... thought I'd share... learned a lot the last few days. What a way to spend a Sunday evening with my Hero

Nice ! Will try ...

Edited by ASHURiCAN.iDe, 13 June 2011 - 11:22 AM.

[peterj]

peterj, on 30 May 2011 - 05:55 PM, said:

The second problem perhaps is a bit more tricky. Bluetooth seems to work so (it shows some devices in reach). But it does not work any longer with the hands-free equipment in my car (Audi "RNS-E"), it doesn't see it anymore.
I had the same problem long time ago with old modaco-Builds, but CM 6.1 worked great. Maybe it has something to do with the kernel-freqs?

Fixed my problem with the RNS-E now: I flashed Elelinux 7.1.0-hero-v2.6.1 (which is absolutly fantastic!) with las venturas kernel. Bluetooth is working as before now. I'm not sure if the new Rom or optional install of the las venturas kernel fixed that issue.

Edited by peterj, 13 June 2011 - 06:58 PM.

[Moopere]

Flashed nightly #92 yesterday after getting some unexplainable reboots with a much earlier #5x build.  

REALLY fast, very nice.  No reboots so far and all seems to work, GPS, Bluetooth, camera.  Running at 710MHz with Smartass, nice.

[M@rk]

vetinari, on 13 June 2011 - 10:35 AM, said:

If you read a few posts earlier, you will find me talking about two benchmarks: CM6.1 vs CM7 in terms of performance and battery. The battery benchmark was done with radio off, and yet there is a very noticeable battery drop in CM7 compared to CM6.1. So, it looks like radio is either not the only culprit or not the main one when it comes to battery usage.

Of course, fixing radio to either 3G or 2G (specially to 2G) will increase your battery, I'm not saying it won't.

Absolutely agree. Will keep trying to find more culprits
FYI: Battery only down to 65% after 24 hours since switching to 2G only. Used my Hero quite a bit yesterday afternoon too, including WiFi, Mobile Data, flashing nightly 92 and a few reboots just to be sure. CPU frequency upped again too with no noticeable impact on battery. Definitely an improvement... Yay!

[gavtaylor]

elelinux, on 12 June 2011 - 08:31 PM, said:

Some good news,I have been working on Las_Venturas the last days,and now the camera works perfect for me, and another user in Sweden who have tried.The kernel is available on my thread on xda and I hope that more will test, soon we have a good working 2.6.35 kernel to Hero (I hope).

that's brilliant news, I bet @riemervdzee was glad someone else is looking at the camera. I think it was turning him grey
have you got a link to the post? I couldnt find it on your xda thread

[M@rk]

M@rk, on 14 June 2011 - 08:42 AM, said:

Absolutely agree. Will keep trying to find more culprits
FYI: Battery only down to 65% after 24 hours since switching to 2G only. Used my Hero quite a bit yesterday afternoon too, including WiFi, Mobile Data, flashing nightly 92 and a few reboots just to be sure. CPU frequency upped again too with no noticeable impact on battery. Definitely an improvement... Yay!

ADD: Battery at 50% after 48 hours - now we're talking!

[centsi]

Hi all.

Just experimented with my first mod install. Going from stock 2.1 to the latest nightly.

I like CM7 a lot, and am grateful for all the work that's been put in, but I do seem to have caused an issue to come to light.

I don't know if this is specific to the hero or not, but as the hero build is experimental, I thought it better to ask here.

The notification power toggle is really cool, so I added screen brightness control to it amongst other things. As soon as I clicked on that toggle however, my screen when completely blank, and I've not been able to get it back since.  

Who knows what I've pressed since then - I've probably locked the pattern out. I tried rebooting, but that didn't help.

I really hate the idea of having to reflash the rom, as I was just getting everything as I like it.

Worse, I'm not sure how to get into the clockwork recovery system without being first in cyanogen, as power + home gets me into the standard recovery agent. I would really, really hate to go back to HTC 2.1...

Any ideas?

Thanks a lot.

Centsi

[centsi]

Aah - no worries, I got into clockwork and did a factory reset.

Still I wonder why the brightenss toggle did that?

Thanks - centsi

[centsi]

OK, so I remember why this happened now.

Being so used to having to reduce the minimum brightness on HTC's firmware to zero, I did the same on cyanogenmod (although 1 rather than zero), which pretty much means no light at all!

Sory for wasting your time, and thanks all for the great mod.

Cheers - centsi.