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

[Guest admanirv]

Ahhhh,

Plug in the cable to the handset and PC

then using the adb command use

1. adb shell
   
2. su
   
3. enter the commands as previously posted.
   
4. Ctrl+D to exit the adb shell
   

Then reboot your handset by long-pressing power button and select reboot.

Thanks, im being stupid here. I am using the terminal emulator on the phone.

I do i have the boot the phone up in a special way?, then use DOS command prompt in windows?.

I dont understand sorry.

Thanks

[Guest Matthew Ferguson]

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.

:)

This particular discussion hasn't come to an end, and as I've already stated - IT IS NOT A LAUNCHER ISSUE, therefore it's very much relevant to CM7. It's an issue with this rom. The poor 2D performance, as has been stated before by other users, is also noticeable when scrolling through the settings app, and similar applications that behave in the same way.

As another user has stated below - he was only able to get Launcher Pro to run NEARLY as good as Froyo by removing a vast quantity of system apps. Evidently, there's a problem here which I and many other users have flagged up. It's your insistence to deny this issue, and your lack of logic to prove why your launcher runs smoothly, that makes me question your motives. Also, it's pretty petty to call in the moderators, as it's clear you're embarrassed as it's been proved your logic is questionable.

Interesting you're now asking ME to post videos documenting my issue, and proving that, when a few posts ago you said this would be a waste of time. It's obvious you wish this particular discussion would come to an end, as you've realised there is an issue with the launcher and your insistence to deny it previously now is very embarrassing. I wish you the best with your phone, and hope your poor 2D performance doesn't ruin it for you.

Edited March 1, 2011 by Matthew Ferguson

[Guest css771]

Thanks, im being stupid here. I am using the terminal emulator on the phone.

I do i have the boot the phone up in a special way?, then use DOS command prompt in windows?.

I dont understand sorry.

Thanks

Open up a command prompt window on your computer.

Enter "adb shell" without the quotes

then enter the commands posted earlier

Done. Ctrl+D to exit (I suppose that works on Windows too. Or just close the command prompt.)

[Guest mELIANTE]

Tried that (superuser popped up as expected), and then typed adb shell.

adb: not found.

Any ideas?

Cheers

Do not type adb shell, go straight to the next command :huh:

[Guest ThrashMan]

Regarding whether the akmd2 "fix" saves battery, I don't really know because I never used CM7 for more than a couple of hours before but here's my figures to see if you can cross reference them with your experiences.

Phone was on USB cable charging all night

Disconnected from USB @ 07:20 this morning (battery is 100%)

Today the phone has:

sync'd as it wants over 2G

made a couple of short phone calls

played with wifi for half hour at lunch time

installed compass from market over 2G

played with compass for 10 mins (2 smoke breaks)

fiddled with settings on & off all day

So phone has been off any charge for 10 hours and now reads: 61%

Hope that gives some meaning to someone :huh:

Oh, the power button is set to sleep in spare parts

PS: The change has not affected the functionality of accelerometer, GPS or compass.

Edited March 1, 2011 by ThrashMan

[Guest admanirv]

Okay, opened up terminal emulator on phone.

Typed and pressed enter: echo 250 > /data/delay

It then went to dollar prompt, then did CTRL - D (had to softmap CTRL to volume down button).

So thats it?, should now reboot the phone?

Cheers

Edited March 1, 2011 by admanirv

[Guest gladiamos]

Which command line do you use ?

adb shell

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

echo "2147483647" > /data/delay

chown compass:compass /data/delay

OR

adb shell

echo 250 > /data/delay

Regards

Edited March 1, 2011 by gladiamos

[Guest css771]

Regarding whether the akmd2 "fix" saves battery, I don't really know because I never used CM7 for more than a couple of hours before but here's my figures to see if you can cross reference them with your experiences.

Phone was on USB cable charging all night

Disconnected from USB @ 07:20 this morning (battery is 100%)

Today the phone has:

sync'd as it wants over 2G

made a couple of short phone calls

played with wifi for half hour at lunch time

installed compass from market over 2G

played with compass for 10 mins (2 smoke breaks)

fiddled with settings on & off all day

So phone has been off any charge for 10 hours and now reads: 61%

Hope that gives some meaning to someone :huh:

Oh, the power button is set to sleep in spare parts

Well that looks quite good :) I've made those changes. Right now my phone is on charge. Will have to see if the phone goes to sleep as normal on standby this time. I Hope it works. Coz the battery drain is the only thing holding this back from being a perfect rom.

[Guest anneliese]

My personal fix, as the &$/(§$% process came back...

adb shell

echo 250 > /data/delay

after that I ran:

#akmd2 -s

 ----------  AK8973 Console Application -------- 

   T. Start Factory Shipment Test. 

   1. Start measurement. 

   Q. Quit application. 

 -----------------------------------------------

Selected Factory Shipment Test for several times till it passed (failed the in the beginning).

[Guest t0mm13b]

My personal fix, as the &$/(§$% process came back...

adb shell

echo 250 > /data/delay

after that I ran:

#akmd2 -s

 ----------  AK8973 Console Application -------- 

   T. Start Factory Shipment Test. 

   1. Start measurement. 

   Q. Quit application. 

 -----------------------------------------------

Selected Factory Shipment Test for several times till it passed (failed the in the beginning).

I have asked this question previously - what's the difference between 250 and the rather ginormous number used in Thrashman's posting?

[Guest Frankish]

If this really does make battery last much longer than the only big issue for me now is the screen freezes...i want to make it through a match on Pro Evo without screen off...screen on...continue....freeze....screen off...

[Guest Victor von Zeppelin]

Added to second post, as this is a monumental, albeit still temporary, fix.

[Guest requies]

This particular discussion hasn't come to an end, and as I've already stated - IT IS NOT A LAUNCHER ISSUE, therefore it's very much relevant to CM7. It's an issue with this rom. The poor 2D performance, as has been stated before by other users, is also noticeable when scrolling through the settings app, and similar applications that behave in the same way.

As another user has stated below - he was only able to get Launcher Pro to run NEARLY as good as Froyo by removing a vast quantity of system apps. Evidently, there's a problem here which I and many other users have flagged up. It's your insistence to deny this issue, and your lack of logic to prove why your launcher runs smoothly, that makes me question your motives. Also, it's pretty petty to call in the moderators, as it's clear you're embarrassed as it's been proved your logic is questionable.

Interesting you're now asking ME to post videos documenting my issue, and proving that, when a few posts ago you said this would be a waste of time. It's obvious you wish this particular discussion would come to an end, as you've realised there is an issue with the launcher and your insistence to deny it previously now is very embarrassing. I wish you the best with your phone, and hope your poor 2D performance doesn't ruin it for you.

at my side i see that with launcher pro everything works great, but with the "stock" launcher i get hicups

why you cannot accept that each zte is diferent? (take for example the OC at some you get 694 at other you can go to 800)

[Guest css771]

A bit of googling led to this: apparently the number 2147483647 is from the donut version of the file and

Its the largest positive value of a signed integer on a 32 bit operating system.

http://code.google.com/p/gaosp/issues/detail?id=152#c11

On the original page, a few posts down, there's an explanation

http://www.drakaz.com/forum/viewtopic.php?pid=3773#p3773

So the number 2147483647 is the largest possible value that can be assigned to delay, effectively turning off akmd and its related functions. But compass still works for me on Maps after performing those steps. Now 250 is apparently high enough and sufficient according to the second link. Why that is, I have no idea.

Edited March 1, 2011 by css771

[Guest Pakatus]

Added to second post, as this is a monumental, albeit still temporary, fix.

you should see this post here....

http://www.drakaz.com/forum/viewtopic.php?pid=3773#p3773

[Guest Victor von Zeppelin]

you should see this post here....

http://www.drakaz.com/forum/viewtopic.php?pid=3773#p3773

I was just thinking that- as akmd would have shoved the phone into high CPU mode to run it and polling so frequently, having a 250ms (so, 2.5 second?) blip is comparatively excellent.

Alright, I'll add both fixes to the first page.

[Guest RoVlad]

I was just thinking that- as akmd would have shoved the phone into high CPU mode to run it and polling so frequently, having a 250ms (so, 2.5 second?) blip is comparatively excellent.

Alright, I'll add both fixes to the first page.

250MS = 0.25 SECONDS

[Guest Brumski]

Using nightly 8. Have noticed 3 random restarts. 2 of which when I wasn't using the phone and I just happened to see the blue Cyanogenmod startup logo. Happened today when I was using the Youtube application, watching a video and pressed the power button then it came back on and then just suddenly the startup logo appeared.

This problem that I mentioned has happened again today, definitely seems linked to using that power on/off button. Pressed it to put phone to sleep and it just instantly brought up the Cyanogen screen.

[Guest That-Guy]

Just a quick one, can you disable the "Add to Blacklist" popup after a call?

Had a look but cant seem to find a way to disable it?

Other than that Nightly 8 seems to be working great apart from known bugs!

[Guest timsewell]

I've had this too - I have brought it up on the Cyanogen nightly discussion forum - could anyone else who's experiencing it too perhaps do likewise so it has more chance of being noticed and acted on?

http://forum.cyanogenmod.com/topic/15851-c...es/page__st__40

[Guest t0mm13b]

A bit of googling led to this: apparently the number 2147483647 is from the donut version of the file and

On the original page, a few posts down, there's an explanation

So the number 2147483647 is the largest possible value that can be assigned to delay, effectively turning off akmd and its related functions. But compass still works for me on Maps after performing those steps. Now 250 is apparently high enough and sufficient according to the second link. Why that is, I have no idea.

Interesting, I thought that would have overflowed to a -1!!! Funny... :huh:

[Guest sandriderman]

Sorry to ask but I am not sure if I have done the battery fix correctly, this is what I have done:

1. Launch Terminal Emulator on phone

2. Type SU

3. Give permission to SU

4. Type "echo 250 > /data/delay" without quotes

5. Done

Would i have to run stage 4 everytime the phone is rebooted?

I am using the latest version of CM7 which was installed with a wipe.

This is the first rom of all I have tried that has given me 100% reliability with the wifi issues.

Cheers :huh:

Edited March 1, 2011 by sandriderman

[Guest css771]

Sorry to ask but I am not sure if I have done the battery fix correctly, this is what I have done:

1. Launch Terminal Emulator on phone

2. Type SU

3. Give permission to SU

4. Type "echo 250 > /data/delay" without quotes

5. Done

Would i have to run stage 4 everytime the phone is rebooted?

I am using the latest version of CM7 which was installed with a wipe.

This is the first rom of all I have tried that has given me 100% reliability with the wifi issues.

Cheers :huh:

No it needs to be done only once.

[Guest peterdalrymple]

Sorry to ask but I am not sure if I have done the battery fix correctly, this is what I have done:

1. Launch Terminal Emulator on phone

2. Type SU

3. Give permission to SU

4. Type "echo 250 > /data/delay" without quotes

5. Done

Would i have to run stage 4 everytime the phone is rebooted?

I am using the latest version of CM7 which was installed with a wipe.

This is the first rom of all I have tried that has given me 100% reliability with the wifi issues.

Cheers :huh:

When I type "SU" into terminal all I get is "access denied"

What am I doing wrong?

Cheers,

Peter

Edited March 1, 2011 by peterdalrymple

[Guest Frankish]

When i run top for akmd2 it is already running at 0% when screen is off. This is on nightly 8. I did the "fix" anyway and rechecked but it's pretty much identical usage.