Related
Has anyone noticed any long term disadvantages to overclocking the Wizard? Does the battery life permanently decrease? What speeds are you running yours at, and how long have you been doing it? Have you noticed anything at all which indicates it's not good for the hardware?
Cheers
reply
i believe that it's safe to overclock the mda...just set it at an acceptable rate (264mhz for me) and make sure not to run the battery all the way down...if you overclock the settings too high the device will freeze and reset (this is a fail safe procedure it goes through), so there is no need to worry...also don't overclock the settings too low as the phone becomes disfunctional when too low (about less than 132mhz for me)...the screen flickers because it's not being refreshed quick enough (my guess)...hope this helps...
I would set it to 240. I have done before, i'm just wondering if it's a bad idea leaving it permanently set to that level?
Cheers
yea you should be fine at that speed, but if you want you can overclock it higher if it will let you...just make sure that the phone is stable when using it...like i said in my earlier post my device is oc at 264mhz
Cool, thanks for your replies. How long have you had yours overclocked for? Do you use Smartskey?
Cheers
My self i ownly use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
My self i only use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
Mine is also set at 264 24/7. Battery still lasts me all day. Been doing it since the oc program was found which I guess has been a couple of months.
Don't forget, you're wizard is only overclocked when it is active (i.e. not in standby mode). When your wizard goes into standby, it automatically goes back to the default 180mhz. Only when you bring it out of standby does it overclock again (assuming you're running it with smartskey with the option of overclocking on wakeup)
i'm using smartkey to constantly run at 264mhz...i have been doing this for a month now...like i said there is not really any problems with the batt unless you run it down totally...there was a post about this in the overclocking thread...the process is set low so that the phone will have a longer batt life...this was also stated in the overclocking thread...theoretically there is more wear if you overclock it since you are making the processor work harder, so use it at your own risk! if you want to be on the safe side then use smartkey and the overclocking prog in the same directory...then use total commander's note pad (while the ini file is highlighted) and change the value lower when you don't want it to constantly run at 264mhz or whatever speed you want to overclock or underclock at...just use it when needed, but i overclock mine constant 264mhz with great results combined with tweaks2k2, registry wizard, and of course the tmobile custom rom ...internet is a blast...just wish i could get it to run like the IE in a pc
anyways hope this helps out a bit further...
activesync
your activesync will hang allot if you overclock, I have noticed this.
DOnt know why.
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Re: DOnt know why.
xSoNiCcRaCkErSx said:
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Click to expand...
Click to collapse
hey sonic, where did you get your copy of warcraft 2 for windows mobile ?
I've never heard of warcraft for Windows mobile, how does it run on a 240 MHz overclock?
I got it from the Wargus engine. i can email you the files if need be, i dont want to jeprodize this sites reputation. The game last time i checked was free though...
Actually I'm not sure if it's the overclocking issue or not but ...
For couple of weeks now my Wizard's red led is on all the time, not like it is when your battery is very low but about half of this brightness. I'm not really worried about that, it doesn't change much but it may be connected with overclocking (it was 240 for about a month).
Another thing - once I had sth like 110% speed of every tone played, either a phone call or an incoming message.
It doesn't really matter to me since it's still working fine but it may mean that overclocking isn't that safe as we might think.
TroLoo
So I've recently bought a Cingular Wizard, and flashed TNT wm6 rom onto it. I installed PocketGnuBoy, and some other games, but I keep running into a problem. After I play for a while, or after my phone has been on for some time, games seem to start to 'skip'. It's really weird, and its still playable, but its extremely annoying. I would assume that someone happens after a while when you have your phone on, but I have no clue what it could be. My guess that it has something to do with activesync, but I can't seem to fix this lagging problem.
By the way, if it helps, I'm using battery status to overclock my processor to 260 mhz.
if i could first comment about your overclocking program...
XCPUScalar has a much better algorithm for overclocking. you should switch.
i tried both programs and XCPUScalar is much more stable. maybe if you tried overclocking using that you wouldn't get the lag.. maybe your processor gets all crazy from the heat of overclocking after some playtime that it can't handle the pressure... to be honest.. you should never overclock to the maximum.. it burns the MOSFETS on the processor.
other than that.. notice that some games eat RAM as they go.. check the ram demand in the beginning and check the change during gameplay..
that's something you can't really overcome.
Well if I'm playing my emulator and it starts to lag, and I exit, it seems like doing everything else or playing any other game will also get the lag. Even if I dump my memory.
ok.. so if it's a function of the time... maybe it IS about the overclocking.
try changing the program and if that doesn't work maybe you should ease up on the pressure.. after all it's a 195Mhz processor and you have a few other programs running.
I don't know. I literally have no other things running while I'm playing, and I still get this problem. The only way to fix it is to soft reset, and then it will run perfectly for 10-20 minutes. I tested it with 195 mhz default, and it still does the same thing.
hmm.. i have no idea then, im sorry
Okay so one thing I've noticed is that every time it starts lagging, the little icon where the keyboard is on your screen pops up. It's not there normally when you first start the program (pocketgnuboy) so when it starts up there is no lag. I'm absolutely sure that this has something to do with it, because of the exact timing of the lag and the appearance of the icon.
So I am at work, looking at my N1, and I'll let you all tell me if you think there is a problem...Since a full charge last night, my phone has been off the dock for 2h9m ...
In that time, my battery has dropped 14% already. The biggest culprit...the display...with 59%...despite only being on for 15m. I always use it on the middle brightness setting from the power bar. Ive lost basically 1% for every minute the screen has been on. At that rate, my phone wouldn't even last 2 hours turned on.
Am I being paranoid? Do I have some rogue program sucking battery life? Your thoughts?
Everybody says controversial stuff about phones like N1 or iPhone regarding battery life. But I can tell you from experience and some conferences I have been the following tips to improve your N1 battery:
-Leave brightness to minimum. Only at street you will need to have it at medium or maximum so you can see well.
-Use 3G or wifi when available. It will save more battery than if you use edge.
-Use push, also it's better.
-User apps like TaskManager to auto kill some application that remain open.
And last thing, if you have a new N1 the battery life will improve with the use within the next 2 weeks. Also, I'm sure you are playing around more than usual if you just got it.
I hope this help you.
*#*#4636#*#*
Battery History
See what the figure for 'running' is, if it's high, something is stopping the phone sleeping. Should that be the case, chage the top drop down box to 'partial wake usage' and see what is to blame.
blastik said:
Everybody says controversial stuff about phones like N1 or iPhone regarding battery life. But I can tell you from experience and some conferences I have been the following tips to improve your N1 battery:
-Leave brightness to minimum. Only at street you will need to have it at medium or maximum so you can see well.
-Use 3G or wifi when available. It will save more battery than if you use edge.
-Use push, also it's better.
-User apps like TaskManager to auto kill some application that remain open.
And last thing, if you have a new N1 the battery life will improve with the use within the next 2 weeks. Also, I'm sure you are playing around more than usual if you just got it.
I hope this help you.
Click to expand...
Click to collapse
This is the complete opposite of what everyone else will tell you.
Most people say to force 2G (Edge) because it'll save battery over 3G. There are reports that WiFi will use less battery than 3G though, but not as good as 2G. Google even says this on the screen where you force 2G.
Push Email will require a constant polling on the internet. Since Android is a web OS, its probably connected to the internet anyway, but you can disable Auto Sync and Background Sync to save battery (once again, Google says this on that screen).
I agree with #1 and #4 though. If you don't want to do the lowest brightness setting, try the Auto Dim, it seems to dim it a lot more than my old Windows Mobile phones did.
mindfrost82 said:
This is the complete opposite of what everyone else will tell you.
Most people say to force 2G (Edge) because it'll save battery over 3G. There are reports that WiFi will use less battery than 3G though, but not as good as 2G. Google even says this on the screen where you force 2G.
Push Email will require a constant polling on the internet. Since Android is a web OS, its probably connected to the internet anyway, but you can disable Auto Sync and Background Sync to save battery (once again, Google says this on that screen).
I agree with #1 and #4 though. If you don't want to do the lowest brightness setting, try the Auto Dim, it seems to dim it a lot more than my old Windows Mobile phones did.
Click to expand...
Click to collapse
At first I had the same opinion as you have but after I watched this video it changed radically
http://www.youtube.com/watch?v=OUemfrKe65c&feature=player_embedded
mindfrost82 said:
Push Email will require a constant polling on the internet.
Click to expand...
Click to collapse
No it doesn't, that's the beauty of push email. It opens a connection to the server and just sits idle.
Rusty! said:
No it doesn't, that's the beauty of push email. It opens a connection to the server and just sits idle.
Click to expand...
Click to collapse
You are right so ... it saves battery at the end.
@mindfrost82. Check out the video, it will tech you few things because most of people is wrong as I was in the past.
Battery Drain
My phone would drain 15% battery in 1 hour just being idle witht he screen off. I dialed *#*#4636#*#* and changed the option from WCDMA preffered to WCDMA only. When I don't get a 3g signal (not often) I jsut go back to that and set it to GSM only. For one reason or another the WCDMA preffered SUCKS THE BATTERY!
4 hours of the phone being idle and only 5% battery drain! DO IT! IT WORKS!
blastik said:
At first I had the same opinion as you have but after I watched this video it changed radically
http://www.youtube.com/watch?v=OUemfrKe65c&feature=player_embedded
Click to expand...
Click to collapse
WTF? 3g uses LESS POWER than edge/wifi?!
My whole world just got turned upside down
Thanks for posting the video
ap3604 said:
WTF? 3g uses LESS POWER than edge/wifi?!
My whole world just got turned upside down
Thanks for posting the video
Click to expand...
Click to collapse
You need to be careful of this. The point the video made is that if you download something OF SIMILAR SIZE, you will realize battery gains by virtue of the fact that what you are downloading/uploading takes exponentially less time to retrieve. The real question is, if 2 phones are both casually browsing for the same amount of time...without worrying how much information was actually transferred...one on Edge, the other on 3G...is there a difference in battery performance?
What the video said is just common sense. If I am going to send you 20 MB file and one way takes 2 minutes to download it and the other takes 10 minutes to download, then OF COURSE the 2 minute method is going to be more efficient. So you can download on Wifi where it might take x amount of time, compared to 3G where it takes 5x or edge where it takes 10x. Thus, if the file size the person is going to download is known, then of course it makes sense to tell them to wait until they are on wifi. However, many of us casually browse, on the spot, without regard to the type of connection we are on.
RayKinStL said:
You need to be careful of this. The point the video made is that if you download something OF SIMILAR SIZE, you will realize battery gains by virtue of the fact that what you are downloading/uploading takes exponentially less time to retrieve. The real question is, if 2 phones are both casually browsing for the same amount of time...without worrying how much information was actually transferred...one on Edge, the other on 3G...is there a difference in battery performance?
What the video said is just common sense. If I am going to send you 20 MB file and one way takes 2 minutes to download it and the other takes 10 minutes to download, then OF COURSE the 2 minute method is going to be more efficient. So you can download on Wifi where it might take x amount of time, compared to 3G where it takes 5x or edge where it takes 10x. Thus, if the file size the person is going to download is known, then of course it makes sense to tell them to wait until they are on wifi. However, many of us casually browse, on the spot, without regard to the type of connection we are on.
Click to expand...
Click to collapse
Yeah, what you just said is right. But still you are saving battery up! Plus I wouldn't use edge at all in my N1. What's the point of having almost everything disabled so I can receive calls?
I remind you that while edge is sending/receiving data you cannot get any calls
blastik said:
At first I had the same opinion as you have but after I watched this video it changed radically
http://www.youtube.com/watch?v=OUemfrKe65c&feature=player_embedded
Click to expand...
Click to collapse
This is an excellent video, I highly recommend watching it if you are even remotely interested in the inner workings of our phones.
blastik said:
I remind you that while edge is sending/receiving data you cannot get any calls
Click to expand...
Click to collapse
Thanks, I didn't know this, for the info this thread is full of great stuff...
1) middle brightness is very bright. I'm sure you can live with 25%. Display brightness will always drain battery like mad.
2) 3G power use is usually decent. The N1 has terrible RF so it might be fighting 2G/3G. That will cost you a lot of power. If you're getting full 4 bars 3G everywhere you go even underground, you might be ok, but in low reception areas, it's gonna drain your battery struggling to boost power. Bigger issue during a call too.I notice this on my Milestone. The N1 completely fails at 3G while my Milestone fights for it. As a result the Milestone gets quite hot.
3) There are sometimes apps that run in the background. Some people insist task killers aren't necessary, but lemme give you an example. Stupid Speedtest program failed to acquire my location. After a test, you can't really exit, so you just hit home. Droidforums fanatics will always repost that link to that one thread where they talk about memory and its ok to not have to kill an app. Think again. The GPS turns on because of Speedtest and it keeps trying to acquire your location. Gotta kill it with a task manager or that thing will kill you. Or a webpage. I've heard of people going to some site that keeps refreshing. Oh good luck to your battery. Make sure you close these things. Use a task manager. Sometimes Facebook or Twitter might be the culprit even if your refresh rates are awfully long. I do not understand this phone sometimes. At times I feel that multitasking/memory management on Android gets you into more trouble than if you just flat out restricted it like in the iPhone. I'm not saying the iPhone's restrictions are the way to go, but Apple knew what it was doing. There's a reason Android phones gobble power and pull data like mad even when you aren't aware. Random apps sometimes start. Facebook widget refreshes even though the app itself is set not to auto notify and to update on its own. So with so many things running loose, its quite easy to see why your battery can go down so fast.
RayKinStL said:
You need to be careful of this. The point the video made is that if you download something OF SIMILAR SIZE, you will realize battery gains by virtue of the fact that what you are downloading/uploading takes exponentially less time to retrieve. The real question is, if 2 phones are both casually browsing for the same amount of time...without worrying how much information was actually transferred...one on Edge, the other on 3G...is there a difference in battery performance?
What the video said is just common sense. If I am going to send you 20 MB file and one way takes 2 minutes to download it and the other takes 10 minutes to download, then OF COURSE the 2 minute method is going to be more efficient. So you can download on Wifi where it might take x amount of time, compared to 3G where it takes 5x or edge where it takes 10x. Thus, if the file size the person is going to download is known, then of course it makes sense to tell them to wait until they are on wifi. However, many of us casually browse, on the spot, without regard to the type of connection we are on.
Click to expand...
Click to collapse
That's exactly the idea I got from that video too, which makes sense.
dmo580 said:
1) middle brightness is very bright. I'm sure you can live with 25%. Display brightness will always drain battery like mad.
2) 3G power use is usually decent. The N1 has terrible RF so it might be fighting 2G/3G. That will cost you a lot of power. If you're getting full 4 bars 3G everywhere you go even underground, you might be ok, but in low reception areas, it's gonna drain your battery struggling to boost power. Bigger issue during a call too.I notice this on my Milestone. The N1 completely fails at 3G while my Milestone fights for it. As a result the Milestone gets quite hot.
3) There are sometimes apps that run in the background. Some people insist task killers aren't necessary, but lemme give you an example. Stupid Speedtest program failed to acquire my location. After a test, you can't really exit, so you just hit home. Droidforums fanatics will always repost that link to that one thread where they talk about memory and its ok to not have to kill an app. Think again. The GPS turns on because of Speedtest and it keeps trying to acquire your location. Gotta kill it with a task manager or that thing will kill you. Or a webpage. I've heard of people going to some site that keeps refreshing. Oh good luck to your battery. Make sure you close these things. Use a task manager. Sometimes Facebook or Twitter might be the culprit even if your refresh rates are awfully long. I do not understand this phone sometimes. At times I feel that multitasking/memory management on Android gets you into more trouble than if you just flat out restricted it like in the iPhone. I'm not saying the iPhone's restrictions are the way to go, but Apple knew what it was doing. There's a reason Android phones gobble power and pull data like mad even when you aren't aware. Random apps sometimes start. Facebook widget refreshes even though the app itself is set not to auto notify and to update on its own. So with so many things running loose, its quite easy to see why your battery can go down so fast.
Click to expand...
Click to collapse
I'll second this, I never used to use a task killer as I figured it was just extra drain on the battery but after running across some rogue programs that kept running after being closed and draining the heck out of my battery I decided to install taskkiller and set it up to autokill apps when the screen goes off.
It's really easy to setup just install it from the market then use it to kill everything then flip through your homescreens make sure everything is up and running and go back into task killer and add everything there to the ignore list and turn on "autokill when screen off" now you don't ever have to worry about rogue apps killing your battery again and everything else will function normally.
blastik said:
Yeah, what you just said is right. But still you are saving battery up! Plus I wouldn't use edge at all in my N1. What's the point of having almost everything disabled so I can receive calls?
I remind you that while edge is sending/receiving data you cannot get any calls
Click to expand...
Click to collapse
yes you can, the phone will stop whatever data it's processing and take the call.
seanhassars said:
yes you can, the phone will stop whatever data it's processing and take the call.
Click to expand...
Click to collapse
I'm sure 100% that while phone is receiving data over edge you wont get calls. I know because I had push enabled and afterwards I was getting SMS from my carrier that I have missed calls. It might say "ey sb is trying to call you" and then stop data transfer but for sure your will miss first call if someone is trying to reach you several times.
Check it out yourself.
blastik said:
Everybody says controversial stuff about phones like N1 or iPhone regarding battery life. But I can tell you from experience and some conferences I have been the following tips to improve your N1 battery:
-Leave brightness to minimum. Only at street you will need to have it at medium or maximum so you can see well.
-Use 3G or wifi when available. It will save more battery than if you use edge.
-Use push, also it's better.
-User apps like TaskManager to auto kill some application that remain open.
And last thing, if you have a new N1 the battery life will improve with the use within the next 2 weeks. Also, I'm sure you are playing around more than usual if you just got it.
I hope this help you.
Click to expand...
Click to collapse
there are a lot of people who say do not use a task killer, including google devs etc.
i used advanced task killer for the longest time, being used to needing one as a WM user before getting my n1. after reading various posts on the issue, i tested without and my battery life increased.
i use juice defender now as well to turn off the apn and wifi, based on speeds/location/etc
have it set to prefer 2g (dont get 3g at home)
screebl also setup to turn screen off when not in certain position in hand
last one is setcpu (need root for this though) underclocking the cpu (including advanced setting and profiles i have set)
lowest setting for brightness
also keep gps off unless needed
i hit about 24hr from unplug til 10% w/ heavy useage, wifi on all the time (although juicedefender handles when its on/off)
just now went to kmobs UV kernel and testing that to increase my times
i've done a 24hr test from 100%>10% based on each app i've mentioned
I think while we are on topic of battery life.. for those of you who are rooted. Here is another link that I would recommend. I used these on my HTC Dream and works great on the Nexus One. Increase your battery life 10 fold.
Your Tube: "Get Better Battery Life" by droiddog
sorry not allowed to link yet
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain