Related
Simple Poll.
Have you seen a decrease or increase?
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
nagash91 said:
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
Click to expand...
Click to collapse
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
OK I have done.. but the problem is that when I use it 3 o 4 minutes (for example I install an application using a file explorer, then I read a message and then I come back to home) m battery get 5% lower...
In standby I lose 10% in 6 - 7 hours (I think this is normal).
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
I am currently without a computer therefore immune to this USB bug. I flashed CM6.1 to this and the other g1 and both suffered substaintial amounts of battery drain so I nandroid restored back to CSDIv4 and still the lowest frequencies and settings did little to combat the descending digits. So I tried this...
Recalibrated my battery
Flashed SuperWipe.zip
Reboot
Flashed SparksMod's latest
Reboot
Wiped battery stats
Unplugged...reboot
Battery lasted 23 hours the first day never seen anything like it.
Lifes great.
Sent from my HTC Grandaddy via XDA app
Sent from my HTC Grandaddy via XDA app
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
nagash91 said:
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
Click to expand...
Click to collapse
I got real excited when I heard about the new radio and hboot even thought that its exclusion was the source of the the battery issues. Haven't been able to try it as I'm without a up-to-date PC at the moment.
It would be real nice if I could find a seasoned dev who understands battery consumption. I thought the kernal was the main culprit but I've tried two different roms with the same kernal and one has notably better battery life than the other. So confusing.
Sent from my HTC Grandaddy via XDA app
I can't use my phone with this battery drain...
I will come back to official android OTA-AOSP 1.6.. with +14mb.
So I'll test if this kernel with 14mb is a cause of battery drain.
PS: I'm not a lover of rom customizations.. I think the official roms are the best.
The other are all too heavy. I'm not a fan of cm kernel, that is too heavy for g1.
I would see an official OTA 2.2 without customizations, so every one could customize as he want, and if he want.
PS: OK I flashed AOSP 1.6 using ezBiff_kernel to have 15mb (cause I have new radio and spl, so I can flash roms only using this kernel).
Result: my battery life is similar to froyo 2.2 roms... so the problem is:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
2) New radio/spl?
3) My battery (I don't think so.. it's new battery. I buy it 2 weeks ago and in the beginning it works so well.. but then I flashed new radio/spl and new kernel for 15mb..)
nagash91 said:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
Click to expand...
Click to collapse
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Cm/pershoot have some interesting new power management code from other htc devices.. So hopefully soon all will be better. (I merged most of it to my kernel but there are some loose ends.. works well untill the phone locks up.. so no public release yet)
ezterry said:
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Click to expand...
Click to collapse
Ok sorry I talk without knowledge. I really don't know the effect of the cm kernel. I only know that all roms based on cm release, with cm kernel, are so heavy and slow.
I like your rom (2.2.1 AOSP) and I love your new way to get 14mb.
But I have this orrible problem. My phone has a lot of battery drain when I use it. With screen off, no problems.
I have never used swap or compcache in this days, and I also try different clock speeds (not over 528mhz).
The result is that when I unlock my phone, I go to settings, I see for example 95% battery. Ok, I return to home, I open a message, I return to home, I open contacts and I scroll some contacts without make calls.
Then I come back to battery settings and I see that is 92-93%..
in 2 minutes of soft use.. I think this is impossible. If I open stupids 2D games... ahah in 5-10 minutes my battery lose 10 - 20%.
I remember 1 year ago, with 1.6 (no cyanomod) my battery was good.
Now it isn't (I have a new battery).
Today I flashed aosp 1.6 with your kernel for 14mb (I have new radio&spl) but nothing... I lose a lot of battery percent as in froyo.
So I think problem is or battery calibration, or something to wipe, or cm kernel, or new radio&spl + your new kernel...
Now I'm recalibrating battery (is at 1% from 2 hours, I'm not using it.. ) then I will recharge for 8 - 9 hours and then wipe battery state, but I have done this process a lot of time without a benefit.
I'll try to remove the new radio+spl (so also using standard kernel) if my battery continue to lose percents so fast.
I'll keep you update on my "story".
PS: Sorry for my bad english!! XD
OK.. after a day of low discharging and a night of 8 hour of recharging, I wiped battery states, I wiped data-cache-ext ecc... I flashed aosp 1.6 and ezbiff kernel..
"battery drain" continue...
I will try tomorrow to reflash death-spl and old radio..
BTW, is normal for hours battery 4v at 90%?
On the back of the battery sais 3.7v... I thought 3.7 was the voltage for 100%
Update
I know this thread is a little old, but I ran into this problem as well. What I found was that the official US radio (2.22.23.02) used considerably more battery than the international one (2.22.19.26i). The other thing I noticed is that switching to "use 2G networks only" in mobile networks settings and disabling data over mobile drastically improved battery life.
I also noticed that wifi used a fair bit of juice so my recommendation is to disable wifi if you're going to be on the go for a bit, and disable data/3g if you're just going to be hanging out in the local webcafe, your/a friend's house, or some other location with wifi access for a while.
If you wanted to be ambitious and cared enough you could write a script to use as a shortcut on the home screen to do the swap automatically (detect which setting(s) are enabled and swap them to the opposite).
With those changes, you should get much better battery life. My thoughts on different Froyo flavors is that possibly different builds have different settings by default. Cyanogen comes with data and 3g enabled by default so this will quickly suck out your battery if you're running your 3g, 2g and wifi antennas all at once.
The stock build (1.6) got about the same battery life as I'm getting now with those settings applied. With either build, having all antennas on all the time will drain your battery very rapidly. Being a little more cognizant of the settings (perhaps you also had it set to 2g only on the stock build) you're using will significantly improve your battery life. And when I say significantly, I mean night and day (but the antenna version definitely does also make a difference... at least in my case).
Just wanted to gather together the current remaining problems with CM7. What apps don't work, what's unstable, etc...
It actually seems very stable for me. I like it more than nookie froyo. With the 1.1ghz kernel it runs very smooth with launcher pro.
Every app I've tried works fine, and best of all - they show up in the market.
Its definitely worth a try, you can always go.back to what you had if you don't like it - just make a backup.
Sent from my SCH-I500 using XDA App
Bawb3 said:
It actually seems very stable for me. I like it more than nookie froyo. With the 1.1ghz kernel it runs very smooth with launcher pro.
Every app I've tried works fine, and best of all - they show up in the market.
Its definitely worth a try, you can always go.back to what you had if you don't like it - just make a backup.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Bawb3, are you using dalingrin's overclocked kernel? If so, are you able to mount your nook on your computer via USB? I just installed the kernel last night and I'm unable to get USB debugging to come up when I plug in. I tried on Windows 7 and OSX and nothing happened in either OS.
Other than that, I love CM7. I started out on Customized Nookie Froyo, but I was having major issues with scrolling speeds and weird market issues. So far CM7 has been rock solid and blazing fast. I would recommend you give it a go.
Just make sure you use one of the latest nightlies if you do. The customized versions are nice, but no one does CM7 like the actual team.
New NC user this week, I've been running CM7 on eMMC for about 48 hours (first nightly v12, now v13) and it's been very stable. DSP video is the major thing lacking. Flash is smooth (including Hulu). I am having some trouble with seeing my installed/purchased apps in the Market but there are work-arounds I haven't tried yet.
I noticed in v12, Google Reader worked 100% fine and Maps FC'd. Now in v13, Reader scales down to 480x320 as soon as I open an article, but maps works fine. I've read this is a problem with DPI settings but I haven't got around to fixing it.
Overall if you're sick of B&N's Android, CM7 on CWM 3.0.1.0 seems to be the most stable of all the ROM's I tried, even in its nightly stage. But I have read of other peeps having major problems. I just really love Gingerbread. Google has really got a winner with 2.3
battery life is horrible w/ CM7, lots of drain when sleeping.
time pilot aka said:
New NC user this week, I've been running CM7 for about 48 hours (first nightly v12, now v13) and it's been very stable. DSP video is the major thing lacking.
I noticed in v12, Google Reader worked 100% fine and Maps FC'd. Now in v13, Reader scales down to 480x320 as soon as I open an article, but maps works fine. I've read this is a problem with DPI settings but I haven't got around to fixing it.
Overall if you're sick of B&N's Android, CM7 on CWM 3.0.1.0 seems to be the most stable of all the ROM's I tried, even in its nightly stage. But I have read of other peeps having major problems. I just really love Gingerbread. Google has really got a winner with 2.3
Click to expand...
Click to collapse
I would be interested to see if anyone has flashed #14 and had Google Reader scale to full size in article view. I'm on #13 as well and haven't been able to get it to scale properly no matter what LCD Density I use.....
dalamchops said:
battery life is horrible w/ CM7, lots of drain when sleeping.
Click to expand...
Click to collapse
I'm not too concerned with the battery drain considering the tear downs have shown that the battery is plugged in and not soldered onto the board. By the time we kill these batteries with multiple charges someone will have put out a kit to replace the battery yourself...just like with the ipods that weren't supposed to have user replaceable batteries.
dalamchops said:
battery life is horrible w/ CM7, lots of drain when sleeping.
Click to expand...
Click to collapse
I second this, i notice it drains the battery pretty fast when im not using it. not really sure what it is doing. its not like its connected to the internet or doing something productive for the battery drain.
dalamchops said:
battery life is horrible w/ CM7, lots of drain when sleeping.
Click to expand...
Click to collapse
I turn off WiFi when I'm not using it (you could use Tasker to have it automagically go off/on at sleep/wake) and battery life improved significantly. I'm guessing when wifi is on, a lot of background activity happens.
But battery also isn't a big deal for me either. I probably use the thing for about an hour a day untethered, and the rest of the time it is plugged in.
time pilot aka said:
I turn off WiFi when I'm not using it (you could use Tasker to have it automagically go off/on at sleep/wake) and battery life improved significantly. I'm guessing when wifi is on, a lot of background activity happens.
But battery also isn't a big deal for me either. I probably use the thing for about an hour a day untethered, and the rest of the time it is plugged in.
Click to expand...
Click to collapse
It might be that an app like TweetDeck is scheduled to get updates every 3 minutes or something. I make sure to turn all of that stuff to manual as I pick up the Nook with checking it in mind anyway and can wait the few seconds it takes after I hit refresh.
john10101 said:
I second this, i notice it drains the battery pretty fast when im not using it. not really sure what it is doing. its not like its connected to the internet or doing something productive for the battery drain.
Click to expand...
Click to collapse
Is battery life alot better in nookie froyo?
barrist said:
Is battery life alot better in nookie froyo?
Click to expand...
Click to collapse
Yes, battery life was was a lot better in Froyo for me. However I had a load of other problems in Froyo such as market intermittently not working, wifi problems, flash not working in firefox. I am sure it could be fixed, but it worked out of the box in CM7 and I liked CM7 UI much better.
Is anyone running CM7 out of an sd card?
If you're seeing battery drain, it seems SetCPU profiles eat up a lot of CPU. Just use the inbuilt settings (Settings > Cyanogenmod Settings > Performance > CPU)
Dalingin posted a new kernel that supports USB mounting on N13+ and also a new Interactive governor which should be faster.
DSP is really the only thing missing. I replaced Google Reader with a dolphin bookmark to the smartphone site, which I feel works a bit better anyway.
I just watched the video below and am pretty close to loading this. I tried Nookie Froyo was wasn't happy at all. I actually like the rooted stock appearance and performance except for the lack of flash. I just wish these ROM's allowed me to make the home screen look like the stock experience with the "continue reading" options on top and the stock B&N reading/store app.
http://www.youtube.com/watch?v=u1Z29zs70YE
I'm running CM7 v13 and I feel like this is the best one overall. I had a few minor hiccups with the wifi but i found a work around to it.
Contrary to what people say, I am impressed with the battery life. This is why. The original NC is used as an e-reader, but i purchased it as a tablet. I haven't had alot of experience with it, but i was able to get at least 6 hard hours out of it with the OC. Left it on overnight (roughtly 6 hours) with wifi and battery only dropped like 5% which is pretty good to me.
The only gripe i have is the DSP but that's tolerable considering all the other advantages of it.
The xda community has been very helpful and alot of the quirks with it has already been worked out if you do some searching in the threads.
Just my 2 cents.
TheReformedPirate said:
I would be interested to see if anyone has flashed #14 and had Google Reader scale to full size in article view. I'm on #13 as well and haven't been able to get it to scale properly no matter what LCD Density I use.....
Click to expand...
Click to collapse
Just flashed v14 annnnnnd....
Reader is still borked
Market is working 100%! All my previous purchases & installs are available in My Apps with the option to update!
Maps is still working.
time pilot aka said:
Just flashed v14 annnnnnd....
Reader is still borked
Market is working 100%! All my previous purchases & installs are available in My Apps with the option to update!
Maps is still working.
Click to expand...
Click to collapse
Quick question on the nightlies: If I update from lets say #13 to #14, does it erase everything I had installed? or is it just and update that keeps all the apps and settings?
I am on #13, and some problems I noticed:
- Wifi would go on and off by itself coming out of sleep
- The "clear" notification button is REALLY unresponsive (might be a hardware issue thou)
- Takes FOREVER to charge (more than 5 hours)
cuoreesitante said:
Quick question on the nightlies: If I update from lets say #13 to #14, does it erase everything I had installed? or is it just and update that keeps all the apps and settings?
I am on #13, and some problems I noticed:
- Wifi would go on and off by itself coming out of sleep
- The "clear" notification button is REALLY unresponsive (might be a hardware issue thou)
- Takes FOREVER to charge (more than 5 hours)
Click to expand...
Click to collapse
As long as you don't wipe your data (though do wipe your cache) before reflashing, it should keep everything. It kept everything for me from v12 to v13, and then kept everything from v13 to v14. You should always double check the important stuff though.
I have the same responsiveness problem with the Clear button, but I'm 99% certain that's the hardware. I have had response/accuracy problems consistently in the corners of my screen, especially the top. Since the problem was on stock, nookie froyo, and CM7 (it's actually a lot better on CM7 than stock), I'm guessing it's the touch panel's fault.
Charging goes a lot faster for me if I've got it plugged into a wall (like 2 hours for 30% to 100%) instead of my computer. Probably a lower current coming through the USB on my computer than from the wall plug, I get the same difference when charging my Milestone. Don't know why the ROM would affect charging at all.
The only main problem with CM7 is that video acceleration doesn't work. That means no Youtube app, Orb app, playing x264 files with the local player, etc.
That is a deal breaker for me, but if its not for you then.....
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
HinotoriBR said:
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
Click to expand...
Click to collapse
Are you serious?
iceandfire v2.1 is the best ROM I've found so far in terms of battery life. Don't know why, but it just lasts SO long!
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
mcdevtingz said:
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
Click to expand...
Click to collapse
As mentioned, nothing beats Eclair. And if we talk about Eclair, nothing beats Telus Lite.
I have CM7 installed.
Your battery mileage may vary depending on your usage habits... But I'm typically a pretty heavy user. Lots of Angry Birds/other games, surfing, Pandora, etc. I go to sleep at around 11pm with my phone unplugged at a full charge (100%), and I can use my phone until the next day mid to late afternoon - that's about 15-18 hours. Granted, a lot of it is when I'm asleep (until about 7am) and during my working hours, but it's still pretty decent considering how I use the phone. ESPECIALLY with all I've heard about CM7 having terrible battery life.
I DO have several apps and tweaks to try to lengthen my battery life though...
Some things you can do:
- install "Network Switcher" from the market. You can set conditions between certain hours and the screen off to turn off WiFi and 3G. I have mine set turn off all data between 11:15pm and 7:15am when the screen is off.
- install the "Toggle 2G" app. This automatically switches the phone to 2G mode when the screen is off. 2G typically sucks less juice than 3G. (get it here: http://forum.xda-developers.com/showthread.php?t=739530)
- tweak your /system/build.prop file so your wifi scan interval is a higher number. I have mine set to 360 seconds (that's 6 minutes). I don't know about you, but I don't need my wifi scanning every 15 seconds for an open or known signal.
- also in the build.prop file; change your ro.telephony.default_network setting from 3 to 0. 3 means GSM/WCDMA mode; 0 means WCDMA preferred. From everything I've read, WCMDA preferred tends to switch signal types less often, which benefits your battery.
Heck, even if you DON'T have a Milestone w/CM7 installed, these tweaks can help immensely with your battery life.
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
pippocannelunghe said:
Are you serious?
Click to expand...
Click to collapse
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
HinotoriBR said:
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
Click to expand...
Click to collapse
Have u tried the ROM that is banned from XDA yet?
dmo580 said:
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
Click to expand...
Click to collapse
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
mcdevtingz said:
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Get either an extra battery or extended battery if u are a heavy user.
pcphobic said:
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
Click to expand...
Click to collapse
That doesn't come remotely close to the V6 SuperCharger script.
The minfree levels is only one aspect of it.
AKMO doesn't fix groupings or priorities.
With those settings, all your apps are getting killed at 28 mb - because of the screwy groupings they are in the 5th slot while slot 3 are 4 are basically empty holes.
And that whole "banned rom" spiel is getting pretty annoying.
I'd bet money that HONO's SuperCharged CM7 kicks Cronos' ass with those AKMO settings.
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
I agree with zeppelinrox, running his V6 supercharge scripts work wonders.
And no matter what ROM I use, i always use SetCPU to auto-adjust the processor speed based on certain scenarios. For example, I'm using CM7 right now, which auto overclocks to 1000mhz. That's great for performance but crappy on the battery. However, with SetCPU I can force the CPU to run between 250mhz and 400mhz when the screen is turned off. There's simply no need to let it go up to 1000mhz if I'm not even using the thing! Calls still come through fine, as do emails and messages. But it really extends your battery life. You can go as low as 125mhz, but then things do start messing up. As soon as the screen turns on, the phone is automatically allowed to run at 1000mhz again.
It's also useful for when your phone gets really hot, as a precaution. If my phone reaches 42*C it automatically underclocks as well. I picked that number out of a hat though. It's just a number I felt was too hot based on my own experience with the phone.
SetCPU:
https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result
pcphobic said:
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
Click to expand...
Click to collapse
I think you're reading too much into it. I didn't think he was being arrogant/nasty. He was just being straight forward.
Just my 2 cents though
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
zeppelinrox said:
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
Click to expand...
Click to collapse
Ah yes, now your tone of voice is much better... more professional and more matured as compared to when u said wrote b4.
Thank you for clearing this up.
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Best Battery -> Official 2.1-update1. Simple as that.
pcphobic said:
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Click to expand...
Click to collapse
I check it out time to time.
Cronos is good and feeyo is cool but lack of updates, v1.2 had issues plus I needed to test other roms.
Btw the memory managent on cm7 and cronos mimics my strategy from v5 anyway - which was to give the laubcher its own OOM grouping/slot but everything else is just weirdly placed far down the list so still not as good as v5.
Tthen V6 simply out does v5 hands down.
Sent from my Milestone using Tapatalk
Hi guys, I've flashed MIUI 5.2 yesterday and I didn't have time to play around with it. But I've noticed today that even when left idle, the battery drops from 100 to 84 in about 2 hours or so. All the other services are off except 3g. Plus when I fiddle around with it, the battery drop is even more noticeable. I went from darky 10.1-Miui5.2, just fyi with the default kernels on the miui page. Any suggestions on how to fix this?
Sent from my GT-I9000 using XDA App
Miui is to heavy
If u want longer life then Miui aint for u.
Miui is by far the best rom for galaxy s ever if u like to be able to change every aspect of ur phone but the more a rom can do the more juice it takes.
If u want more life and less tweakeblity then u need to use pony roms like darky or ultimate aso.
Edit : Miui bat life is slowly increased by each release (5.2 is way better then 4.1)
Yeah I've noticed that. I switched back to Darky,happy to see 16hours of battery life again. But I wouldn't hesitate to go back to miui in the future though, provided the battery life increases. Or at least until juicedefender has some effect on it
Sent from my GT-I9000 using XDA App
flashing from stock to MIUI is a painful process and it reflects on the phone too !!
after such a vigorous beating from ODIN and Recovery flashing, the phones battery needs time to settle,
Do the battery calibration a few times, generally the battery will settle after a week, Until then its hard to judge battery life, albeit it is definitely less than a stock ROM, But some MIUI users report 1 day, some report short of 3 days..
so dont give up just yet
azzledazzle said:
flashing from stock to MIUI is a painful process and it reflects on the phone too !!
after such a vigorous beating from ODIN and Recovery flashing, the phones battery needs time to settle,
Do the battery calibration a few times, generally the battery will settle after a week, Until then its hard to judge battery life, albeit it is definitely less than a stock ROM, But some MIUI users report 1 day, some report short of 3 days..
so dont give up just yet
Click to expand...
Click to collapse
wow 3 days? imma try it again then, right after my battery finishes charging. what kernel do you think is the most ideal one to use? i live in the uk
Edit: I saw a guy getting 14% loss after 12 hours using JXJV6. Isn't JXJV6 a modem for the middle east? Is it possible for me to use it here in the uk?
farisiylia said:
wow 3 days? imma try it again then, right after my battery finishes charging. what kernel do you think is the most ideal one to use? i live in the uk
Edit: I saw a guy getting 14% loss after 12 hours using JXJV6. Isn't JXJV6 a modem for the middle east? Is it possible for me to use it here in the uk?
Click to expand...
Click to collapse
im not sure about that modem, but i dont see why it wont work, i use at the moment ZSJV5 - i am in the uk too, that modem works fine for me .
As for the kernel, the latest Glitch V10 is good enough, you could also maybe undervolt and underclock just a little, this would increase battery life too.
but 2 -3 full cycle charges really makes a huge difference.
Awesome, I'll try that soon. Mind sharing the link for ZSJV5? And the app for undervolt and underclocking?
Edit: It seems that I have the insufficient storage space bug, I've read the faqs,
1.3 Apps not installing - Not enough memory message pop up (Known bug for CM7/MIUI)
1. (Using root explorer or any equivalent app) Delete folder /data/data
2. Copy "folder" /datadata to /data/
3. Change name of folder /data/datadata to /data/data/
But it still doesnt work. If I reboot, I have to go through the setup wizard again, and rootexplorer will be uninstalled. Any idea how to fix this as well?
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch. Betterbatterystats gave a temperature of 52C and avg of 50. Needless to say, my battery also runs out very quickly like this, also dropping about 5% an hour when the screen is off.
Another thing I've noticed is that SDcard takes 25% of my battery usage, and when I go to storage settings, it will infinitely calculate. I mounted my storages and chkdsked them, fixed some corrupted files but the problem still persists. The only storage I haven't mounted is the internal storage, which I'm unable to do. I can't seem to connect to adb from recovery and mounting /data alone does nothing. After about 10 mins of using the phone, it becomes too hot(burns my hand) and it will shut down.
I've replaced 2 batteries so it's very unlikely that it's a battery issue. Also tried other chargers and wiping everything.
Phone OS: 4.1.2 stock LT5 before.
Did factory wipe/dalvik wipe + flash to CM11 4.4.4 and the problem is still present.
Betterbatterystats doesn't indicate a draining app, just high temperature.
Removing the external SD card and sim card had no impact.
I'm getting deep sleep when I turn off the screen, so it's not media scan being stuck. Mediascan disabled and problem still persists.
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Poopfeast said:
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch.....
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Click to expand...
Click to collapse
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
julian67 said:
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
Click to expand...
Click to collapse
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
edit: just flashed to omnirom and it's still burning my hand.
In the team win recovery repairing internal storage gives me the error: unable to repair /emmc, so I just wiped it, problem is still there.
Poopfeast said:
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
Click to expand...
Click to collapse
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
julian67 said:
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
Click to expand...
Click to collapse
Thanks for taking your time to write this. I've already disabled GPS/sync and turned on power saving. Clearing the storage now lets android calculate properly, and the Media/sdcard is gone from battery usage. But it's still running very hot and draining. CPUspy says 20% on 1400 and the rest on 800mhz when I'm using it. The system is freezing often and generally really slow.
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.
Temperature seems to drop to a reasonable 35C when I'm in airplane mode.
With everything on and sync off it's not going above 40C even when watching videos or something, so I guess it's all good now.
So basically what I've done to fix it:
Wipe internal storage and repair all partitions
Flash to OmniROM
Turn off Sync/GPS
Problem seemed to be mainly on the internal storage corruption, maybe related to my bugged chip.
Poopfeast said:
.....
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.......maybe related to my bugged chip.
Click to expand...
Click to collapse
According to eMMC Brickbug Check my Note is exactly the same as yours - supposedly "Insane chip" but Memory check passed with no problems, and guess what? It works 100% perfectly running 4.1.2 rooted. I have the full capacity of storage available to me, apps do not freeze, everything works as good as new. It is absolutely stable and reliable and terribly boring (just how I like it). It never surprises me or does any weird stuff at boot or crashes or freezes. All the hardware features work, all the supported video and audio codecs and formats work, the networking is rock solid, I can rely on my VPN when away from home, GPS gets a fix in no time, battery life is excellent, video playback is great etc. etc..
I bought my 16GB GT-N7000 a few months ago, a used item on ebay. It is an unlocked retail UK item (boxed with all manuals, paperwork, accessories etc) so no network/vendor bloatware but it was supplied by the seller with Supernexus ROM installed and was obviously suffering from the usual problems often described by users of custom ROMs on exynos. After various frustrating episodes and trials of different ROMs I used ODIN 3.09 to flash an official Samsung ICS 4.04 firmware and 16GB pit file to restore the partition table and stock firmware. Then I ran Kies on Windows XP on the "virgin" restoration. It recognised the hardware and the firmware and notified me of the update to 4.1.2. I went ahead and updated over ethernet and also captured the official 4.1.2 firmware for purpose of backup.
Since then I have tried out various ROMs and have always been able to revert to stock Samsung 4.1.2 via ODIN and without going back to the scary brickbug "insane" ICS versions. As far as I can tell the brick bug is irrelevant if you aren't stuck on ICS. After trying numerous ROMs of various android versions I am in no doubt at all that if you spend half the time setting up a rooted stock Samsung firmware as most people spend setting up ROM X/Y/Z you actually get a much more reliable and useful device.
If you need a known-good pit file for a 16GB GT-N7000 you can use this: ftp://takla.linuxd.org/Q1_20110914_16GB.pit
I had a similar issue lately. Go to developer settings and activate the cpu load display. Processes and their cpu load along with a bar graph will appear on the screen. I found out that google's music app was hanging on my phone. This did not show up in BetterBatteryStats!!!