Guest targetbsp Posted March 2, 2011 Report Posted March 2, 2011 (edited) The 250 tip did nothing for me for the standby battery time. I did reboot after applying. Lost 18% overnight in airplane. Edited March 2, 2011 by targetbsp
Guest Scoopading Posted March 2, 2011 Report Posted March 2, 2011 (edited) The 250 tip did nothing for me for the standby battery time. I did reboot after applying. Lost 18% overnight in airplane. Yep. I can confirm that too (not that I thought it'd do much!) I still lose around 2% battery per hour (just ordinary sleep, not airplane mode) whilst the phone sleeps, which was the same amount as before. Edited March 2, 2011 by Scoopading
Guest Rotmann Posted March 2, 2011 Report Posted March 2, 2011 (edited) The 250 tip did nothing for me for the standby battery time. I did reboot after applying. Lost 18% overnight in airplane. Hmmm, ok so it seems that echo "2147483647" > /data/delay remains the only solution. Or maybe nightly 11 solves the problem? Downloading now. @Victor von Zeppelin, could you please leave at the batter fix only echo "2147483647" > /data/delay because the 250 and the two "chown compass" lines do not bring anything. Thanks for the hard work, I bet if you wouldn't have written the first two posts, we would have 150 pages untill now :huh: Edited March 2, 2011 by Rotmann
Guest targetbsp Posted March 2, 2011 Report Posted March 2, 2011 What makes you think the bigger number will fix it? :huh:
Guest css771 Posted March 2, 2011 Report Posted March 2, 2011 Alright the akmd delay thing doesn't work. I used the large number. Battery Lost 22% overnight.
Guest Rotmann Posted March 2, 2011 Report Posted March 2, 2011 (edited) Alright the akmd delay thing doesn't work. I used the large number. Battery Lost 22% overnight. Which one did you apply? Did you restart after applying? What makes you think the bigger number will fix it? :huh: Look here, post 1456, chall32 confirmed that the garbage collector ain't paranoid anymore. He did not restart though, maybe that's the secret? :) Also why is "2147483647" between quotes and 250 without quotes? :P Edited March 2, 2011 by Rotmann
Guest Letoo Posted March 2, 2011 Report Posted March 2, 2011 I'm wondering guys, what is supposed to be the difference between 2.3.2 and 2.3.3 in general?
Guest The Soup Thief Posted March 2, 2011 Report Posted March 2, 2011 Good morning all and hello Nightly 10, running 2.3.3! So, I was having problems on nightly 8 with the screen going to sleep during calls and not waking (heretofore, "the proximity sensor problem"); posted about this on monday after ringing voicemail and the problem reappearing Downloaded and installed N10 a couple of hours ago. Restored settings with Titanium, rang voicemail to check if "the proximity sensor problem" was still a problem, and once again the screen turned off and wouldn't wake Wondered if it might have been to do with the settings I'd just restored with Titanium so I wiped and did a clean reinstall of N10 - rang voicemail. Phone reawakened fine, suggesting it ain't N10 having this problem, it's the settings I'm restoring with Titanium that are creating the problem. Restored all my apps (but not settings) with titanium, and lo and behold the problem is back! So, when I've time to play (and wireless access) I'm gonna do a clean reinstall and download all my apps again from the market, see if the problem comes back and if not I'll wipe my last titanium backup and backup at that point Hope that makes sense Incidentally, if anyone has this proximity sensor problem occur, I've found a workaround that will at least wake your phone up, meaning you won't need to pull the battery (works for me anyway - may or may not work for you) If you take your phone away from your head and it doesn't wake, just cover the sensor with your hand (top left of the screen, but you knew that already) for 5 seconds or so, take your hand away for a while and it will probably reawaken (had to give mine 10 secs or so). If it doesn't work, repeat a few times Will let you know if I find out what program it is that seems to be making the sensor a bit unresponsive
Guest css771 Posted March 2, 2011 Report Posted March 2, 2011 I used the larger number and I did restart after. I don't think the akmd2 process was consuming that much CPU during sleep anyway. So false alarm. Another thing I noticed was that com.android.systemui is consuming more than 10% CPU during sleep after this fix.
Guest rayraven Posted March 2, 2011 Report Posted March 2, 2011 I'm wondering guys, what is supposed to be the difference between 2.3.2 and 2.3.3 in general? Near Field Communication [NFC] improvements & Minor bugfixes http://developer.android.com/sdk/android-2.3.3.html
Guest chall32 Posted March 2, 2011 Report Posted March 2, 2011 Which one did you apply? Did you restart after applying? Look here, post 1456, chall32 confirmed that the garbage collector ain't paranoid anymore. He did not restart though, maybe that's the secret? :huh: Also why is "2147483647" between quotes and 250 without quotes? :) Bad news I'm afraid. I lost 25% overnight, which is the same as usual. Only thing out of the ordinary is that Twitter used 12 mins "keep awake time".... Full wipe, hello nightly 11 (plus delay fix) & bye bye Twitter for the moment
Guest Krinyo Posted March 2, 2011 Report Posted March 2, 2011 Move it to the phone, where is the problem? If you have more than 20 apps and games format an ext3 primary partition to it, get s2e from the market, enable install onto the ext partition and you're good to go. I'm using so many programs, thats my problem. :huh: And no, I don't want repartition my SD card again, I played with it enough on my Pulse. Thanx, no. It's a showstopper bug FOR ME, hope it'll fixed soon.
Guest Frankish Posted March 2, 2011 Report Posted March 2, 2011 (edited) There has been no changes on the Blades CM7 github since last month. I think they abandoned this. Everyone flash back to FLB. :huh: Joke lulz Edited March 2, 2011 by Frankish
Guest Nathorr Posted March 2, 2011 Report Posted March 2, 2011 Fast and simple question: do I need to wipe data & cache if I update from a old nightly to a newer one, for example N8 -> N11?
Guest MrEasy Posted March 2, 2011 Report Posted March 2, 2011 Fast and simple question: do I need to wipe data & cache if I update from a old nightly to a newer one, for example N8 -> N11? I did not do a wipe when updating from N6 to N8 and it worked - but the safe and recommended way is to do it.
Guest dadashi Posted March 2, 2011 Report Posted March 2, 2011 Ive installed S2E, my question should i let Dalvik cache and all others install to Ext2 or just Applications? I dont know what was put on Ext2 in previous versions...
Guest daniel2k10 Posted March 2, 2011 Report Posted March 2, 2011 3g problem is fixed in nightly 11 but contacts won't sync with the google account :huh: does anyone else have this bug?? overall wifi performance is low compared to flb...
Guest Swimmerboy Posted March 2, 2011 Report Posted March 2, 2011 I did not do a wipe when updating from N6 to N8 and it worked - but the safe and recommended way is to do it. Gone from N6->N8->N11 and haven't wiped, although when I tried to pull, edit and push build.prop I got an 'Out of space' error when pushing. Phone seems stable but I'm slightly concerned that if /system has been filled up then it might not have installed the full update so might do a wipe and install just to be sure...
Guest Simon O Posted March 2, 2011 Report Posted March 2, 2011 (edited) There has been no changes on the Blades CM7 github since last month. I think they abandoned this. Everyone flash back to FLB. :huh: Joke lulz The blade port is official now so all changes are found at https://github.com/CyanogenMod/android_device_zte_blade Also remember HCDRJacob has school work to do during the week and Tom G works. They simply can't spend 24/7 working on CM7. But others can fix bugs and submit them through gerrit. Edited March 2, 2011 by flibblesan
Guest dadashi Posted March 2, 2011 Report Posted March 2, 2011 just to add, my Titanium Backup has backed up from my Ext2 partition as well...How can reinstall all my apps back on the sd card including Ext2 partition...I installed S2E but it doesnt see my Ext2 partition...!
Guest Frankish Posted March 2, 2011 Report Posted March 2, 2011 The blade port is official now so all changes are found at https://github.com/CyanogenMod/android_device_zte_blade Also remember HCDRJacob has school work to do during the week and Tom G works. They simply can't spend 24/7 working on CM7. But others can fix bugs and submit them through gerrit. I don't think you saw the hidden text in my post when you quoted me :huh:
Guest Pakatus Posted March 2, 2011 Report Posted March 2, 2011 N11...seems nice until now. No noticable bugs until now. No 3G/Wifi bug Battery drain seems a little more stable now...(in 2:30 hours after flash, have lost 1% on standby). Nice work CM crew...
Guest ballist1x Posted March 2, 2011 Report Posted March 2, 2011 On nightly 11 too now will update with issues as I go.
Guest mvheuver Posted March 2, 2011 Report Posted March 2, 2011 I did not do a wipe when updating from N6 to N8 and it worked - but the safe and recommended way is to do it. I went from N6 to N11 without wiping. Had to remove and add some widgets again (they were stuck loading, as if there was no data connection) but other than that it seems to work fine. Frankish's circle battery mod doesn't seem to work for me any more though.
Recommended Posts