CM7 Nightly Discussion Thread [Old, please use new thread]

[Guest css771]

I think this is standard Android behaviour. Boot process is decent load and battery voltage drops under that load. During boot process there battery percentage is calculated from actual - dropped - battery voltage. After boot is completed battery voltage is restored nearly to level before boot. But because Android never (or nearly never) rises estimated battery percentage you can see same percentage for next few hours. If you reboot for second time there probably will be no drop in percentage at all because final voltage will be same. If you connect phone to computer/charger Android must rise its estimated percentage and because battery voltage is already restored Android rises battery percentage very quickly to previous level.

Thanks for the explanation. I thought it was an Android thing, since I had encountered it on other roms as well. But with all the talk about misrepresentation of battery voltage, thought it might be related.

[Guest IronDoc]

Holding volume keys to switch track with the screen off isn't working correctly for me. The volume change still get applied and then track is changed.

Eg if I hold vol + the volume will go up one and the track will be skipped. Can anyone confirm?

[Guest ThrashMan]

I don't know if this is "normal" but in N8 using the "top -m 10" command in an ADB SHELL:

131 7% S 2 1196K 132K fg root /system/bin/akmd2

which I think is related to the chip that handles screen rotation, compass etc

Should that be running in "sleep" mode? and why does it use so much CPU?

Can anyone using a non-CM7 ROM see if it's in their top 10 tasks please?

Edited March 1, 2011 by ThrashMan

[Guest skymera]

Holding volume keys to switch track with the screen off isn't working correctly for me. The volume change still get applied and then track is changed.

Eg if I hold vol + the volume will go up one and the track will be skipped. Can anyone confirm?

Can confirm.

[Guest ThrashMan]

I don't know if this is "normal" but in N8 using the "top -m 10" command in an ADB SHELL:

131 7% S 2 1196K 132K fg root /system/bin/akmd2

which I think is related to the chip that handles screen rotation, compass etc

Should that be running in "sleep" mode? and why does it use so much CPU?

Can anyone using a non-CM7 ROM see if it's in their top 10 tasks please?

This issue seems to be quite common. I tried this fix on N8:

adb shell

chown compass:compass /data/misc/akmd_set.txt


echo "2147483647" > /data/delay

chown compass:compass /data/delay


Now reboot the phone.

and it certainly makes akmd2 go to sleep when the phone is asleep.

Accelerometer responce seems normal when phone is awake.

akmd2 resumes its constant 7% CPU usage with phone awake.

[Guest skymera]

This issue seems to be quite common. I tried this fix on N8:

adb shell

chown compass:compass /data/misc/akmd_set.txt


echo "2147483647" > /data/delay

chown compass:compass /data/delay


Now reboot the phone.

and it certainly makes akmd2 go to sleep when the phone is asleep.

Accelerometer responce seems normal when phone is awake.

akmd2 resumes its constant 7% CPU usage with phone awake.

Thanks for heads up.

Please let me know if it does affect the accelerometer. The alarm i use relies on it to wake me up.

[Guest Rotmann]

I don't know if this is "normal" but in N8 using the "top -m 10" command in an ADB SHELL:

131 7% S 2 1196K 132K fg root /system/bin/akmd2

which I think is related to the chip that handles screen rotation, compass etc

Should that be running in "sleep" mode? and why does it use so much CPU?

Can anyone using a non-CM7 ROM see if it's in their top 10 tasks please?

Akmd is in the top 10 on my wife's FLB Froyo with 5-6% while on and while the phone sleeps it does not register anything in the terminal, as soon as I switch it on it shows it 5-6% again.

[Guest t0mm13b]

This issue seems to be quite common. I tried this fix on N8:

adb shell

chown compass:compass /data/misc/akmd_set.txt


echo "2147483647" > /data/delay

chown compass:compass /data/delay


Now reboot the phone.

and it certainly makes akmd2 go to sleep when the phone is asleep.

Accelerometer responce seems normal when phone is awake.

akmd2 resumes its constant 7% CPU usage with phone awake.

That's interesting... would a update script in the flashing of the ROM be able to cater this automatically upon installation?

Mind explaining how this daemon akmd works and what's the difference with akmd2?

there was a thread about this a while ago on this forum :huh:

Side note, this was reported on another blog.

Nice catch and heads up Thrashman... will try this out... :) w00t!

Edited March 1, 2011 by t0mm13b

[Guest Scoopading]

If this is true, backup your launcher pro and uninstall it, and install a completely fresh instance of it. Video its performance and I'll do the same, and we can compare.

If it isn't true you should dance the macarena, video your performance, and upload it - I won't do the same. Whilst people on forums might write silly things sometimes, hopefully most of them have better things to do than tell lies about something as mundane as Android launcher performance :)

I've told you my experience, and even given some reasons for why there might be differences from yours. If you don't accept that for what it is then that's your issue, not mine. 2D is performing quite well with Launcher Pro on CM7 for me, and there's really nothing for me to "prove". Also, whilst a video would show severe performance issues, it'd need a high framerate (preferably 60 fps+) to really show up more minor graphical issues properly. If you have a camera that can go that fast, and want to make your own comparisons of how your phone performs, then knock yerself out. Although, if you do that, pehaps you should start a specific thread about comparisons between different launchers performance rather than drag this thread off topic.

Even if there were differences, all it would prove is that it does that on your phone. It would be unlikely to be directly comparable to mine since the first thing I do when I install is shut down everything I don't need with Autoruns, remove whatever else I don't want with Titanium, and then shut off things like animations, since I don't require much eye candy to be happy. If you're the sort of person who prefers all singing and dancing animations, or your phones launcher screen looking like a MySpace web page circa 2007, that's cool too. Personally I'm looking more for performance rather than giant clock weather widgets pulling data from weather stations 20 miles away (if you're lucky). That's why I'm trying CM7. Battery issues aside it's the first large advance over the stock rom, in terms of performance IMO. :huh:

[Guest Matthew Ferguson]

If it isn't true you should dance the macarena, video your performance, and upload it - I won't do the same. Whilst people on forums might write silly things sometimes, hopefully most of them have better things to do than tell lies about something as mundane as Android launcher performance :)

I've told you my experience, and even given some reasons for why there might be differences from yours. If you don't accept that for what it is then that's your issue, not mine. 2D is performing quite well with Launcher Pro on CM7 for me, and there's really nothing for me to "prove". Also, whilst a video would show severe performance issues, it'd need a high framerate (preferably 60 fps+) to really show up more minor graphical issues properly. If you have a camera that can go that fast, and want to make your own comparisons of how your phone performs, then knock yerself out. Although, if you do that, pehaps you should start a specific thread about comparisons between different launchers performance rather than drag this thread off topic.

Even if there were differences, all it would prove is that it does that on your phone. It would be unlikely to be directly comparable to mine since the first thing I do when I install is shut down everything I don't need with Autoruns, remove whatever else I don't want with Titanium, and then shut off things like animations, since I don't require much eye candy to be happy. If you're the sort of person who prefers all singing and dancing animations, or your phones launcher screen looking like a MySpace web page circa 2007, that's cool too. Personally I'm looking more for performance rather than giant clock weather widgets pulling data from weather stations 20 miles away (if you're lucky). That's why I'm trying CM7. Battery issues aside it's the first large advance over the stock rom, in terms of performance IMO. :huh:

As MANY other individuals on this thread have written, there are huge issues with 2D performance in this rom. Of course, considering you CONTINUE to insist yours runs "smoothly" when others don't, it'd be interesting to find what process you're ending, so we can see if we can improve the 2D performance on our phones. Considering I've tried both launchers I've mentioned on Froyo roms, and Launcher pro runs vastly different, THIS HAS NOTHING TO DO WITH THE PERFORMANCE OF DIFFERENT LAUNCHERS, it is purely to do with the issue of 2D performance in this rom.

Considering your continuing ridiculous statements about performance, and your blatant disregard for the obvious - with standard settings on both roms, the launcher runs considerably - noticeable on a slow framerate camera - slower than on other versions of android for our devices - it's hard to take anything you say seriously.. As I don't understand your continuing desire to deny providing any form of proof, I judge you to be lying, and see little point in taking any of the info you provide seriously.

If you had actually tried a Froyo rom recently on your device, in comparison to stock, you'd see that there is a vast leap in and "advance" in performance. However, since your experience seems to be limited to this rom (as you seem unable to tell when LauncherPro is running slowly) and you've already made such ridiculous points as "the launcher runs so smooth with opening speed set to 9" which effectively disables the animation entirely, it's pointless.

As my launcher will run speedily with or without Fancy Widget present on the home screen, in Froyo, it shows that you have a serious issue with... WHAT? that's right, 2D performance, if it's making a vast difference to you, as it has me, in this ROM.

You, sir, are obviously not understanding what I'm trying to communicate. If you disable the animation you won't actually see the issue I'm trying to point out. THANK GOD the rom developers have more sense than you.

Edited March 1, 2011 by Matthew Ferguson

[Guest leszekpap]

No Nightly today ? eh

[Guest BigBearMDC]

Guys, please stay calm.

Best regards,

BB

[Guest Maringer]

Hmmm. A strange issue for me overnight on Nightly 8.

I came downstairs this morning and the screen was lit although I'd left the phone on standby last night as usual.

An automated Titanium Backup took place at around 3.30am this morning so I assume this must have affected something and led to the screen coming on for some reason or other! Battery down to about 34% from 90-odd. I had to reboot before the phone before the auto-dimming and sleep would work once again.

akmd2 was showing a fair bit of CPU usage but, following the reboot, this is again back down to low levels.

[Guest The Soup Thief]

No Nightly today ? eh

Rats - nothing for any phone since 27/2/11

Nightly -> binightly -> trinightly

Damn my impatience!

[Guest Scoopading]

I don't understand your continuing desire to deny providing any form of proof

And I don't understand why you think someone posting their own experience has anything to "prove" to you? You seem to be the one with a problem about this stuff for whatever reason. So how about you do your own video(s) and post a new launcher thread with your own issues and video examples?

Apparently, when someone has a different experience from you, you appear to think the onus is on them to prove you wrong. But the world doesn't revolve around you, if you hadn't already noticed. Nobody has to "prove" anything to you in order to hold a different (and valid) opinion. It'd be different if I were actually seeking to change your opinion. But I'm not because, shocking as it may seem to you, I don't actually care what you think. I'm satisfied with drawing my own conclusions based on my own experience.

As for "poor 2D performance", the only thing I think you've mentioned so far is the animation when opening the app drawer. How about you video some more real world examples of actual poor 2D performance manifesting itself on the phone? Or are you merely complaining about an animation some of us prefer to switch off anyway?!

I don't have any problems with Launcher Pro performance on CM7. You, apparently, do. Thus, if you didn't realize, it's normal that the person with the problems should be the one attempting to document what their issues are, rather than calling people who don't have the same issues "liars" and demanding "proof". When discussions descend to that childish level it's best they stop before the moderators step in :huh:

If you actually care about your issue and want to document it on video for feedback from others then knock yourself out. I'd even encourage you to do so. But, since I don't feel I share the same apparent problem and I'm more interested in other issues on the current CM7, I think it best that this particular discussion come to an end.

:)

[Guest Scoopading]

Anyone else finding that N8 won't allow USB mounting?

Yes, but it's only happened a few times. Had the same experience with N6. It's always resolved itself when I physically disconnected and reconnected the USB cable and then tried to mount it again.

[Guest Scoopading]

But the nightly discussion on cm says no bug reports too!

Yep, but you're misreading :huh: They mean don't post bug reports on the bug tracker. But it's poorly worded so it can be read that people shouldn't post bugs on their nightly forum thread either! :) It's fine to post bugs on there ( http://forum.cyanogenmod.com/topic/15851-c...n-of-nightlies/ ) . The only thing I'm sure they'd want you to do is check the Issues Tracker first, so you're not posting about already known issues.

[Guest MrEasy]

Yes, but it's only happened a few times. Had the same experience with N6. It's always resolved itself when I physically disconnected and reconnected the USB cable and then tried to mount it again.

Same here - happened to me about 2 times since RC.

[Guest ballist1x]

Charged to 100% last night. Put to sleep overnight and I'm down to 74% in the morning. I turn wifi off and change end key to sleep but the result is pretty bad!

And after typingg that message I'm down 64 and now 58%. Yikes.

Edited March 1, 2011 by ballist1x

[Guest Rotmann]

Could anyone compare the md5 between this nightly 8 (download it again please) and the first one, ONLY if you have downloaded this on the 27th? Maybe the bot is doing the same stuff as with nightly 4 where the latest nightly 4 was nightly 5 with the wrong name. :) Damn bots, you can never trust 'em :huh:

Edited March 1, 2011 by Rotmann

[Guest Scoopading]

Could anyone compare the md5 between this nightly 8 (download it again please) and the first one, ONLY if you have downloaded this on the 27th? Maybe the bot is doing the same stuff as with nightly 4 where the latest nightly 4 was nightly 5 with the wrong name. :P Damn bots, you can never trust 'em :huh:

Not this time I'm afraid. No changes :)

[Guest Lord Kurisu]

Both exactly the same 2bc3490038b325ecb5529374f341e01e

[Guest targetbsp]

Not to be argumentative but my Launcher Pro ran well too! It didn't when it was first installed but after I'd uninstalled loads of system stuff I don't want loaded in titanium and stopped lots of other stuff running in Autostarts it was pretty smooth. Not quite Froyo but really not far off. Not as smooth as ADW Ex which I later switched too though - that is slick! I highly recommend it (as others have previously) if you need a smooth launcher for CM7.

[Guest t0mm13b]

That's interesting... would a update script in the flashing of the ROM be able to cater this automatically upon installation?

Mind explaining how this daemon akmd works and what's the difference with akmd2?

there was a thread about this a while ago on this forum :huh:

Side note, this was reported on another blog.

Nice catch and heads up Thrashman... will try this out... :) w00t!

This certainly has seemed to help the battery and prevent the drain. I can confirm this, it's much better....

@Victor - any chance this could be stickied in the second post to help others, well, its a temporary fix I'd say... unless there's a permanent way of doing this?

[Guest mELIANTE]

This certainly has seemed to help the battery and prevent the drain. I can confirm this, it's much better....

@Victor - any chance this could be stickied in the second post to help others, well, its a temporary fix I'd say... unless there's a permanent way of doing this?

Following those threads it appears that after aplying that command the compass gets broken. Is it not true?