The old thread filled with sparse reports of Cyanogen Nightly release experiences has gotten old in the tooth. As we approach the release of 6.1.0, I feel it necessary to start fresh and record configurations (dates, kernel's, etc) with details that have the potential to benefit us all.
I am currently running the #169 nightly and an underclocked kernel (shooting for battery life at the moment), and have run into no stability issues thus far. This includes use of both wireless and bluetooth features.
Please reply with your positive or negative take on CM nightlies for the Incredible Build #100 or newer. Thank you!
Anecdotal Reports for 169:
-Video camera functions, Infinite focus only
-LEDs function as expected. Please remember Pule under your audio settings
-Stock kernel performs VERY well, however invisibleKs may improve your mileage
Download the newest nightlies from:
http://mirror.teamdouche.net/?device=inc
mp3sum said:
The old thread filled with sparse reports of Cyanogen Nightly release experiences has gotten old in the tooth. As we approach the release of 6.1.0, I feel it necessary to start fresh and record configurations (dates, kernel's, etc) with details that have the potential to benefit us all.
I am currently running the 9/18 nightly when Adrenylyne's underclocked kernel (shooting for battery life at the moment), and have run into no stability issues thus far. This includes use of both wireless and bluetooth features.
Please reply with your positive or negative take on CM nightlies for the Incredible 9/18 or newer. Thanks!
Click to expand...
Click to collapse
Can you verify that the built in wifi tethering works (using adrenylynes kernel)? if that doesn't, what about the wifi tethering app, and if it works, what version are you running, pre9?
I ran nightly 9/19 starting last night until now. The email FC problem seemed fixed from the 6.0.2 but i would get random restarts and incredilight would FC alot.
Cant wait for 6.1
i'd recommend using the HTC flashlight apk.. it works without the sense framework (works with cm6).
you can grab it from the themes/apps forum.
dnoyeb said:
i'd recommend using the HTC flashlight apk.. it works without the sense framework (works with cm6).
you can grab it from the themes/apps forum.
Click to expand...
Click to collapse
Unless I found the wrong post, the com.htc.flashlight.apk that was ported over from the Desire 2.2 Rom does not use the LEDs, but uses the screen instead. That is pretty gay.
alexdw369 said:
Unless I found the wrong post, the com.htc.flashlight.apk that was ported over from the Desire 2.2 Rom does not use the LEDs, but uses the screen instead. That is pretty gay.
Click to expand...
Click to collapse
I'm not sure about CyanogenMod and other AOSP ROMs, but the HTC Flashlight included in froyo uses the LEDs
alexdw369 said:
Unless I found the wrong post, the com.htc.flashlight.apk that was ported over from the Desire 2.2 Rom does not use the LEDs, but uses the screen instead. That is pretty gay.
Click to expand...
Click to collapse
must have been the wrong post... it uses the LEDs.
click here.
I am on 9/19 and I'm happy to announce that my Gallery and Music Player can detect pictures and music on BOTH the eMMC and microSD.
However, Gallery still doesn't set pictures as wallpaper.
Running King's kernel but about to switch to Adrynalyne's new Battery Saver kernel.
dnoyeb said:
Can you verify that the built in wifi tethering works (using adrenylynes kernel)? if that doesn't, what about the wifi tethering app, and if it works, what version are you running, pre9?
Click to expand...
Click to collapse
I am using the 9/19 version. With adrenylynes kernel the built in wifi does not work.....the pre9 does work. I just tried this kernel to see if it worked or not.....it does not allow adb wireless to work, so I went back to Koush's stock kernel. I have not had any problems running the stock kernel and my battery life is quite good.
^^ Gallery lets me set a pic as wallpaper..
dnoyeb said:
must have been the wrong post... it uses the LEDs.
click here.
Click to expand...
Click to collapse
Haha thats the post I found, but I didn't read deep enough. The first post says that it uses the screen INSTEAD of the LEDs. a later post points this out as false. i wish the op had been edited
wwjdd44 said:
I am using the 9/19 version. With adrenylynes kernel the built in wifi does not work.....the pre9 does work. I just tried this kernel to see if it worked or not.....it does not allow adb wireless to work, so I went back to Koush's stock kernel. I have not had any problems running the stock kernel and my battery life is quite good.
^^ Gallery lets me set a pic as wallpaper..
Click to expand...
Click to collapse
Gallery lets me set as wallpaper on 9/20... but some dark ones (black wood) look like they're all black.
Does anyone know when 6.1 will be released? I can't wait to be able to hold the back button and close the app.
I can confirm that wifi-tether (packaged and pre-9) both function as expected. No reboots overnight. Uptime of 21 hours, wifi and bluetooth on and off, mostly the former. Installing 9/20, no wipe.
i was running the 9/15 nightly for a few days with minimum apps to test stability. still had the "temp drop" problem on both incoming and outgoing calls. battery life was abysmal (8-10 hours max, light usage...something was keeping my cell standby in the same percentage as display usage and chewing up battery).
last night i got several freezes, reboots, and two battery pulls. so now i'm on 9/20 nightly. so far so good for stability, but already down 20% 2 hours after unplugging. something isn't letting my phone sleep; any idea what it might be, or how to find out? i'm running relatively few apps at the moment, but see no performance differences to when i had a ****-ton of apps/widgets running.
edit: emmc still doesn't mount in windows. shows up as 660 MB according to the OS's "SD Card and phone storage", but all the Gee Bee's are being reported as 6.6 GB under astro.
mcgoo99 said:
i was running the 9/15 nightly for a few days with minimum apps to test stability. still had the "temp drop" problem on both incoming and outgoing calls. battery life was abysmal (8-10 hours max, light usage...something was keeping my cell standby in the same percentage as display usage and chewing up battery).
last night i got several freezes, reboots, and two battery pulls. so now i'm on 9/20 nightly. so far so good for stability, but already down 20% 2 hours after unplugging. something isn't letting my phone sleep; any idea what it might be, or how to find out? i'm running relatively few apps at the moment, but see no performance differences to when i had a ****-ton of apps/widgets running.
Click to expand...
Click to collapse
Are you using the most recent Trillian beta? If so, set it to battery saver mode or it will drain the crap out of your battery. The polling frequency on the regular mode is too frequent.
mcgoo99 said:
i was running the 9/15 nightly for a few days with minimum apps to test stability. still had the "temp drop" problem on both incoming and outgoing calls. battery life was abysmal (8-10 hours max, light usage...something was keeping my cell standby in the same percentage as display usage and chewing up battery).
last night i got several freezes, reboots, and two battery pulls. so now i'm on 9/20 nightly. so far so good for stability, but already down 20% 2 hours after unplugging. something isn't letting my phone sleep; any idea what it might be, or how to find out? i'm running relatively few apps at the moment, but see no performance differences to when i had a ****-ton of apps/widgets running.
Click to expand...
Click to collapse
I've also had great luck with Adrenylyne's new undervolted kernel.
Asterdroid said:
Are you using the most recent Trillian beta? If so, set it to battery saver mode or it will drain the crap out of your battery. The polling frequency on the regular mode is too frequent.
Click to expand...
Click to collapse
no sir
10 chars
mp3sum said:
I've also had great luck with Adrenylyne's new undervolted kernel.
Click to expand...
Click to collapse
ok i'll bump-charge and give it a shot. anything's gotta be better than this! sad, because on my Nexus One with stock CM6 + juice defender, i got some 40 hours out of a charge. i miss that phone lol.
mp3sum said:
I've also had great luck with Adrenylyne's new undervolted kernel.
Click to expand...
Click to collapse
This.
Started with 6.0.2, upgraded to 9/20 nightly with no wipe. I've previously tried KK, CM6's stock kernel, and adrynalyne's AOSP kernel. Of the four, this newest undervolted kernel is performing like an absolute champ. Tethering (both built-in and pre9) is working, and I am having none of the CDMA signal attenuation issues while also using the WiFi radio that I previously had.
Somebody is getting laid for this.
nordr said:
This.
Started with 6.0.2, upgraded to 9/20 nightly with no wipe. I've previously tried KK, CM6's stock kernel, and adrynalyne's AOSP kernel. Of the four, this newest undervolted kernel is performing like an absolute champ. Tethering (both built-in and pre9) is working, and I am having none of the CDMA signal attenuation issues while also using the WiFi radio that I previously had.
Somebody is getting laid for this.
Click to expand...
Click to collapse
sounds awesome, I am installing latest now and will follow suit.
I noticed battery life on ae leaked Captivate Froyo 2.2 build (with AT&T bloatwares intact) was stellar!!! The battery life nearly doubled the custom ROMs that I have tried (the latest Cognition 2.3b8 and Axura 2.3 ROms).
I have tried all three on a regular work schedule from 8am - 4pm in a same location. I left all the ROMs installed as is. Here are the battery life meter findings at the end of my shift listed by ROM:
1. Leaked Captivate Froyo 2.2 --- Battery Life (92%)
2. Axura 2.3 --- Battery Life (69%)
3. Cognition 2.3b8 --- Battery Life (65%)
Anyone know why is this? Don't get me wrong, I love the Axura new functions and all that extras built-in. However, the battery life is discouraging.
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
I almost want to say this is common sense. If you load something that increases your phones speed with a lagfix, gives you stronger reception and faster download speeds with using a different modem, and has many more enabled options would you not think battery may be effected?
All this being said I can get 20 hrs of moderate use on my current configuration. I do not need much more then that
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
I almost want to say this is common sense.
Click to expand...
Click to collapse
*almost*
I have questioned this myself sometimes, then realizing that there is a lagfix installed. it's like buying a Vette for the gas mileage.. not gonna happen.
Hence, some custom ROM's do have damn good battery life with lagfixes! So, it's just a matter of finding what suits your needs.
The issue I've been seeing with the latest builds of most of the ROMs in the Dev Forums are:
Using customized i9000 Kernels and Modems. These are hacks/tweaks (and very good ones) to work with Captivate phones.
OC/UV Kernels that offer awesome overclocking/voltage capabilities but at a price - battery usage.
Using a Vibrant build for Captivate phones.
Custom "Captivate Kernels" (sorry the quotes aren't there for sarcasm just emphasis) that are still in beta or development.
All of the above cause battery issues as they are not optimized for our phone, missing some bits in the software that handle the OS/battery life, or straight up bleed the battery to death as your OVERCLOCKING YOUR PHONE.
And to make it worse utilizing different modems just exacerbates the problem.
Lag Fixes - SHOULD NOT AFFECT BATTERY LIFE AS THEY ARE JUST CHANGING YOUR EXISTING FILE STRUCTURE IN YOUR PHONE.
So it does make sense that while using a "stock" ROM you would get better battery life.
Now.. on to battery life/usage:
Calibrating the battery helps at least keep a more accurate track of how your phone's battery performance is doing.
You can do a few things to optimize your battery usage:
Of course Calibrate your battery - removing battery stats on your phone, doing the drain it down to 0% and re-charge to 100% to ensure you have an accurate idead of true battery usage is always helpful. I delete battery stats right after every flash to a new ROM.
Turning off Wireless/GPS/Data etc. while not in use. This does NOT mean to use a task killer since if you have an errant app running it will just make battery life worse not better.
If your using an OC kernel - then the usually install Voltage Control is a must! I have heard great things about tweaking these settings and people getting great battery life from their devices. Now.. mind you you don't have to overclock if your running the OC kernel. It's just there if you want it.
Also - being careful of what you have installed on your phone is one of the biggest ones most people miss. If it's trying to do a push every 3 seconds that is utilizing your battery/proc and that will be killing your phone.
With all that being said though? The custom ROMs are all awesome and I'm very glad we have them - even if it means I sacrifice a little bit of battery performance (which to me is horrid to begin with). I use a little common sense and I can at least get through an entire day with average usage (txts, email, calls, xda, angry birds etc..) without having to throw it on a charger.
Sorry.. long post - too much coffee and 90 wpm does that to me sometimes
cachookaman said:
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
Click to expand...
Click to collapse
whats the easiest way to do this?
vuoflfan said:
whats the easiest way to do this?
Click to expand...
Click to collapse
For battery stats - you go into the advanced Clockwork Recovery Menu - go to Advanced - and you should see Clear Battery Stats there.
I would make sure that your phone is charged to 100% before doing this.
There is another trick you can do also that works for some people.
Charge your phone in.. as SOON as you get the notification stating to unplug your phone you should unplug it - wait 30 seconds then plug it back in. If it wasn't calibrated correctly you will see the percentage on your battery typically at around 97% instead of the reported 100%.
The improved battery life can probably be most attributed to the difference between the Java interpreter in 2.1 and Froyo's JIT.
In short, when Java does interpretation, it reads a single application instruction, decides what to do with it, does it, and repeats. If the same function is encountered again, the interpreter still has to re-read the instructions, decide what to do again, and do it.
In comparison, when Froyo's JIT encounters an application function, it reads the instructions in a large batch, decides what all of them should do, and records the result in the processor's "native-language". If the same function is encountered again, the processor just does it without needing to make all of those decisions again.
The speed difference is more than 30x. Running application code is only a small fraction of the total "working time", so benchmarks typically only see about 3x improvement. For the parts that are running applications (including even the home screen), Froyo is ultimately running 1 operation that used to take 30 operations - that means fewer electrons are wasted on the processor.
Also, Samsung's crappy filesystem decision certainly will impact battery life, since the format they chose (a relative of the old DOS format) performs seeks optimized for linear mechanical devices (like hard drives), not from FLASH, which suffers on fractional block reads and excels at non-linear reads. Lots of electrons will be wasted interacting with FLASH unnecessairily, but that kind of interaction is rare compared to other battery consumers.
- Kipp
Embedded Systems Hardware and Software Engineer
Can anyone say what are the common confirmed bugs of 2.2 leaked kernel(s) for the Milestone? I'm trying to figure out if I should stick to Eclair based ROMs until official Froyo comes out because I need a reliable phone that won't die on me in the middle of the day, although I've charged it that morning.
So, what are the common problems of 2.2 ROMs? I've tried searching but everyting's scattered around, I couldn't find all the problems listed in one place.
So, I heard of:
1. Phone not going to sleep, thus draining the battery excessively.
2. Phone not charging to 100% (fixed in latest kernel leak).
3...?
Are there any other confirmed bugs?
Topuz said:
Can anyone say what are the common confirmed bugs of 2.2 leaked kernel(s) for the Milestone? I'm trying to figure out if I should stick to Eclair based ROMs until official Froyo comes out because I need a reliable phone that won't die on me in the middle of the day, although I've charged it that morning.
So, what are the common problems of 2.2 ROMs? I've tried searching but everyting's scattered around, I couldn't find all the problems listed in one place.
So, I heard of:
1. Phone not going to sleep, thus draining the battery excessively.
2. Phone not charging to 100% (fixed in latest kernel leak).
3...?
Are there any other confirmed bugs?
Click to expand...
Click to collapse
1. Not true. Phone does go to sleep.
Everytime after charge, when unplugged, it is better to reboot the phone and you'll know for sure your phone goes to sleep.
It does go to sleep many time without reboot. You can check this on "Spare parts" "Battery History" and there you have "Running".
If "Running" shows "100%" means you should reboot in order for you phone to go to sleep.
Actually battery life is pretty good on 2.2.1. The most I got from it was 60 hours with medium usage. I'm using latest CM6 and I'm pretty satisfied.
For better performances and when you are switching from one ROM to another you should remove:
/data/system/batterystats.bin
2. Yes. That problem was fixed with these latest releases.
Hope I've been helpfull!
Right now I'm using cyanogen 6.1 but I'm noticing a lot of battery drain and on my car charger my phone continues to drain even while charging. I don't want to go back to stock because I love features like portable wifi, but I'm a heavy user and I need solid battery life. Any ROM suggestions for me that I can flash through clockwork while I'm at work? Or any ideas on how I can fix the battery on my current CM ROM?
first about the battery life... Got to settings, about phone, battery use. What is eating up your battery? usually display eats up most of my life. Try turning your display down... Maybe you have a rogue app running in the background eating up your juice?
As for ROMS, the stock ROM does have wifi hotspot and USB tethering. Perhaps try the stock ROM for a while and see if that makes any difference? It could be a battery problem/ issue. There is a great app for CM that allows you to see your battery life/wear @ http://forum.xda-developers.com/showthread.php?t=765609
The ROM I have been using is here: http://forum.xda-developers.com/showthread.php?t=714184. It is very close to stock, but has many performance tweaks and such. I use it with this kernel : http://forum.xda-developers.com/showthread.php?t=820172. By far the best battery life on any ROM/kernel combination I have tried. Both can be flashed by Clockwork.
Also, when Gingerbread finally gets here, there is a much updated and detailed battery meter installed with graphs. Hopefully it will only be a few more weeks.
Hey All,
My Milestone running MIUI 1.6.4 doesnt go to sleep when I turn the screen off. This is leading to poor dormant battery life. The battery drops by about 10 percent for every 1 hr, when the phone is not in use(ironic, cos when the device is actively used, MIUI seems to have the best battery life). I checked the built in battery usage chart, and the thread that keeps the device awake is Android System itself. Is this a known issue? and are there any solutions available?
Had same problem!
Had exactly same problem a couple of months back and posted question here but no response.
I was able to initiate deep sleep but had to do various things such as reboot time after time until successful, open up a variety of apps, use a task killer, etc., to try and resolve problem.
I was using CM 6.0 initially and even updated to the latest update of that build by wiping everything but all to no avail. I was beginning to think that it was a hardware problem when I flashed an entirely different rom - MIUI 1.2.25 and hey presto problem resolved.
I suggest that you may have to do likewise and try another rom entirely. BTW the battery life of 1.2.25 is very good indeed. I also recommend using CPU Spy found in the market and/or CPU Stats found in the Themes/Apps section of this forum to monitor deep sleep status.
Hope this helps
uptheironsrafi said:
Hey All,
My Milestone running MIUI 1.6.4 doesnt go to sleep when I turn the screen off. This is leading to poor dormant battery life. The battery drops by about 10 percent for every 1 hr, when the phone is not in use(ironic, cos when the device is actively used, MIUI seems to have the best battery life). I checked the built in battery usage chart, and the thread that keeps the device awake is Android System itself. Is this a known issue? and are there any solutions available?
Click to expand...
Click to collapse
for best battery life use cronosginger 1.4.0
Where are you getting the milestone 1.6.4 build?
magiman7 said:
Where are you getting the milestone 1.6.4 build?
Click to expand...
Click to collapse
1.6.4 ?
last ive seen is 1.6.3
http://forum.xda-developers.com/forumdisplay.php?f=670
rrohanjs said:
1.6.4 ?
last ive seen is 1.6.3
http://forum.xda-developers.com/forumdisplay.php?f=670
Click to expand...
Click to collapse
He's probably talking about the 6-3 build released on 6-4 by Lalit or Eybee.
Get the update. 1.6.10.
find it way better and stable
Kulch said:
Get the update. 1.6.10.
find it way better and stable
Click to expand...
Click to collapse
waiting for eyebee's version wud b a better choice .. his update shud come by monday ..