Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
[CM7] Discussion of Nightlies
Started by ciwrl, Jan 17 2011 12:00 AM
1079 replies to this topic
#1001
Posted 17 July 2011 - 09:50 PM
Now it appears the GPS work for most users, thankfully, is to experiment a bit with electro beam for screenoff, some new settings to get it to work quicker to avoid lag, 'll see how tests go during the week if it is stable enough to push changes.
#1002
Posted 18 July 2011 - 02:42 AM
re GPS, yes I think you're correct. I did myself have problems with GPS causing reset, but after somebodys tip to use 'GPS Status' from the market to reset the GPS, it now works fine.
will we get a stable RC?
will we get a stable RC?
#1003
Posted 18 July 2011 - 08:33 AM
Where's the right place to file bug reports about DSPManager (pretty sure not device specific issue)?
My complaint: that it is always running as a service ('HeadsetService') which on a low memory device like my htc hero I can't justify considering I have nothing enabled in the DSPManager app. If I had the headset connected and in use and had selected an effect in DSPManager, then fair enough.
My complaint: that it is always running as a service ('HeadsetService') which on a low memory device like my htc hero I can't justify considering I have nothing enabled in the DSPManager app. If I had the headset connected and in use and had selected an effect in DSPManager, then fair enough.
#1004
Posted 18 July 2011 - 04:15 PM
SteelBytes, on 18 July 2011 - 02:42 AM, said:
re GPS, yes I think you're correct. I did myself have problems with GPS causing reset, but after somebodys tip to use 'GPS Status' from the market to reset the GPS, it now works fine.
will we get a stable RC?
will we get a stable RC?
I hope for stable RC soon, I personally feel it stable enough already, are testing the final settings with screenoff on my custom rom, very grateful to several thousand test pilots
#1005
Posted 19 July 2011 - 06:56 AM
I tested #125 with GPS for more than half hour twice using (Papago) it was fine, no restarts. 
thanks guys
thanks guys
#1006
Posted 20 July 2011 - 06:11 AM
elelinux, on 18 July 2011 - 04:15 PM, said:
I hope for stable RC soon, I personally feel it stable enough already, are testing the final settings with screenoff on my custom rom, very grateful to several thousand test pilots 
I agree completely with you, the rom is pretty stable, it runs fast.
Ele, thank for your contribution!!!
#1007
Posted 20 July 2011 - 12:26 PM
Hi,
Yesterday I flashed #128 which has lot of changes. Since this time the phone app was closed or killed few times so I had to enter PIN code again. Anyone elese can confirm this issue?
Thanks.
Yesterday I flashed #128 which has lot of changes. Since this time the phone app was closed or killed few times so I had to enter PIN code again. Anyone elese can confirm this issue?
Thanks.
#1008
Posted 20 July 2011 - 03:36 PM
Are you using a task killer? Try to add the phone app to ignore list. I didn't encounter this problem on my Hero running CM7 #129, maybe because I don't use any task killers.
#1009
Posted 20 July 2011 - 05:15 PM
Gardner, on 20 July 2011 - 03:36 PM, said:
Are you using a task killer? Try to add the phone app to ignore list. I didn't encounter this problem on my Hero running CM7 #129, maybe because I don't use any task killers.
Yes I'm using AutoKiller from AndRS which isn't classic "task killer". It is changing minfree parameters to tune android bult-in memory manager. I had "Strict" preset active so maybe this was too much. Now I'm testing with "Optimum" preset. I let you know. Thanks.
J.
#1013
Posted 23 July 2011 - 04:29 PM
Since first nightlies I started to test (around #108) screen off animation worked until first reboot. Now I flashed nightly #132 and not sure how but screen off animation was back, was - I rebooted to be sure and it vanished again, so it works when it wants.
About @Rashidi Zin problem, I'm using nightlies for everyday use and didn't meet with blank screen issues since #108
About @Rashidi Zin problem, I'm using nightlies for everyday use and didn't meet with blank screen issues since #108
#1015
Posted 26 July 2011 - 08:19 AM
I can confirm that GPS is working fine again, took a 2+ hours ride with my bike with Endomondo app.
#1016
Posted 28 July 2011 - 09:29 PM
Using CM 7 nightly #126 I have experienced some random reboots. Most seem to occur when I use the GPS and the phone is under heavy load (never had a reboot when the phone is not under heavy load), I have overclocked to 691MHz on my Hero, could be that.
On the other hand I also took a 2+ hour long bike ride yesterday, with gps tracking and experienced no problems.
On the other hand I also took a 2+ hour long bike ride yesterday, with gps tracking and experienced no problems.
#1019
Posted 29 July 2011 - 09:11 AM
I have both enabled but there are times my data plan is unstable. That could probably be the reason.
Thanks.
Thanks.
#1020
Posted 29 July 2011 - 12:14 PM
Hi!
I still get the out-of-memory problem. It happens only with the GroundSpeak geocaching app, thus I am not sure whether it's a problem with the design of that particular application or with android. Here is a part of the logcat: http://pastebin.com/yybu0ETM
The effect of this bug is the same as in April, i.e. missing elements on the screen (keyboard, text fields and so on). I tried to tweak a little bit via the settings (especially the heap size - it's currently set to 48m, Dithering is set to off, and resources may be reclaimed by the system).
It would be nice if somebody could have a look at the error and tell me if I should rather file this report to Groundspeak directly. I am currently running a recent nightly build (28th of July).
Thanks,
Alex
I still get the out-of-memory problem. It happens only with the GroundSpeak geocaching app, thus I am not sure whether it's a problem with the design of that particular application or with android. Here is a part of the logcat: http://pastebin.com/yybu0ETM
The effect of this bug is the same as in April, i.e. missing elements on the screen (keyboard, text fields and so on). I tried to tweak a little bit via the settings (especially the heap size - it's currently set to 48m, Dithering is set to off, and resources may be reclaimed by the system).
It would be nice if somebody could have a look at the error and tell me if I should rather file this report to Groundspeak directly. I am currently running a recent nightly build (28th of July).
Thanks,
Alex


















