I am using CMYLXGO's NAND stock Desire HD build. Its great. However, I am having so many lag issues. I seem to be one of the few that is experiencing this with the build so i turn to some of you to see if you have had similar issues with your phones.
Problems:
1. when auto populating apps (like using installer, uninstaller, managing applications in the system tab) the phone will take forever to pull up all the apps , the screen will cut off (because the screen times out) and when I hit the home button or any button to cut the phone back on it stays black.
2. every action makes the cpu run high. adding a widget to the home screen (apps populating issue again), changing screens really fast and other assorted minor processed.
I have stopped auto sync
I do not use auto rotate any more
I do not have any rogue processes for the most part
I don't understand why I seem to have these lag issues. Everyone else talks about how fast and fluid the build is. I am under the impression that with the build NOT being run from the memory card NAND would add to speed. This is not happening for me. If anyone has any idea why this is happening. I am convinced it is something on my end but I don't know where to start. I am open to suggestions.
I have 2.15 radio, 16 gig class 2 memory card.
Hmmm, not sure but have you tried another ROM similar to see if it does the same? You can also go into MAGLDR and wipe dalvik cache. I used this ROM and all was good for me. I have sense been using this one which is also working very well.
http://forum.xda-developers.com/showthread.php?t=976384&page=1
every version of this build has been tried. That is the part that gets me. differnt kernels don't help either. i have even used SetCPU and overcloced to try and get through some of the lag. it works, but it is only when I play games not when I need to perform uninstall or widget selection for the home pages. I use SeePU which is ususally shows my cpu strain in the bright orange (for high use). most of my processes/actions raise the cpu use to high levels. I never really operate in a green (or low) usage level no matter what the action is. I would really like to capitalize on the speed NAND is supposed to offer.
Personally I would try something else (a totally different ROM) and see if you are still getting the same results, maybe even revert back to a windows mobile rom just to see if you are still getting the hang up. Last option would be to restore your phone to stock and start over, reinstall HSPL 2.08 new radio, etc...etc...
do you use an app killer?
XthelordinatorX said:
do you use an app killer?
Click to expand...
Click to collapse
yeah. but i did not at first. however, it is needed to stop some of the rogue processes. android.process.acore comes to mind.
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
WorldWide60 said:
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
Click to expand...
Click to collapse
Believe me, I know. Everything is working in his build. GPS, MMS, easy to install - the works. This is why i really want this to work properly so I can use it, without the hiccups, as my daily build. It has to be something with my phone but I can't figure out what it is yet....
On Cmylxgo's build, the first time I loaded it, I had the laggy and unresponsiveness you described for the same reasons. What I found is that rebooting the system to off/on a couple of times when I first loaded the build, addressed the first initial lag and unresponsiveness. After doing a couple of reboots, I found the build as smooth as everyone says it is. I am now trying the GL Core v11 kernel and it gives an extra 300 pts to the Quadrant Score and seems to be a bit quicker than the Rafpigna 1.8 kernel that comes with the build. Also, standby battery drain seems to be a bit better with the hourly peaks at half what I see with Rafpigna. If rebooting a couple of times doesn't do it for you, I know trying another build which may not have all the bells and whistles as Cmylxgo, but it is worth a try to see if it makes a difference. For me at least Cmylxgo's stock Desire (HD)2 build is much faster and smoother than any of the MDJ SD builds I was using.
Related
Im using darkstone's android version on my htc hd2 tmobile 1024mb with 2.12 radio, hspl 3, newest chucky rom gtx lite and every once in a while my phone would freeze up for about 10 secs then resume functioning. This is very annoying and frustrating so i was wondering what can i do to fix this?
mine does it too with a completly different rom..
i think it is because when the screen is off it goes into a "sleep" mode where the cpu gets throttled back to save battery..
when you push the button it takes a few seconds for the cpu to load everything up and resume the phone..
its probably because your loading everything off the sd card and its alot slower then the inernal memory.
Fasty12 said:
Im using darkstone's android version on my htc hd2 tmobile 1024mb with 2.12 radio, hspl 3, newest chucky rom gtx lite and every once in a while my phone would freeze up for about 10 secs then resume functioning. This is very annoying and frustrating so i was wondering what can i do to fix this?
Click to expand...
Click to collapse
this is a known issue on all builds thus far.
try disabling autorotation in display settings. this fixes it for some but not for others (me)
thesweeney said:
this is a known issue on all builds thus far.
try disabling autorotation in display settings. this fixes it for some but not for others (me)
Click to expand...
Click to collapse
Some people say problem is less when they calibrate g-sensor in winmo before started android
I've had this issue on every build as well. Usually for me it gets worse progressively to the point I have to un-install or add a different build. Thankfully when it happens there's a build that is released that I haven't tried.
mines done the same on all builds tested and I am constantly changing it, but downloading 160MB every 3-4 days is getting a little old... I'm going to look into a faster micro SD card..
I had freezing issues like everyone else but mine was when i restarted the phone at once it loads up it would freeze at the first sync. Other times would be during any game play or any cpu intensive app. i found it to be a combo of things. i realize that the sync freeze was due to the hd2 trying to grab all my 120 emails for the gmail app. so i went and deleted al my emails and it hasn't freeze since. i also disable full weather animation, turn off all unneeded sync like stocks, news, and disable any sense widgets that i did not need, also turn service provider to manual and not auto. My phone hasn't freeze once in 5 days ( fingers crossed) versus 3 or 4 per day before i did this. hope it helps someone
NAND!
Sent from my Android Powered HD2 using XDA App
Guide:
If you get SoDs as often as I do, you might be getting mad. in fact, you might even go back to WinMo! But, try this tip out.
[0] Disable automatic phone lock / screen time out. (I'm not sure if Aldiko does this)
[1] Download the Aldiko app from the Android marketplace (before you ask, yes, the eBook reader one.)
[2] Start the app and click one of the included books.
[3] Slide your finger from the top left corner of your screen to the bottom left corner of your screen. This is your new "locked" screen.
[4] To unlock your screen, hit the home button and go to your home screen, or phone button and go straight to your phone.
[5] Next time you want to lock your screen, just start the Aldiko app, it should already be a blank screen but if not just slide your finger down again.
Question: Is there any way to make the power/hang up hardware button on your phone start Aldiko?
While I appreciate your creative work around, I've not experienced a hard freeze or touch screen freeze in almost a month.
If your juggling android builds, this can cause corruption in some cases, and can result in said-per SOD.
If your working with an older build, the g-sensor can cause a freeze, but its not quite a hard freeze unless you fiddle with it to the point of it not recovering.
If your using Set CPU and its clocked on the lowest settings, this can cause hard freezes via it being clocked too low to wake up.
These are the main reasons that I've found for my own SOD. My suggestion? Use a WM Rom built specifically for android. Use a RECENT build that specifies that most everything is working. There are some new chefs out there working on builds that aren't quite as polished as some of the more experienced chefs.
Good luck, and may you never experience an SOD again!
M&ate said:
While I appreciate your creative work around, I've not experienced a hard freeze or touch screen freeze in almost a month.
If your juggling android builds, this can cause corruption in some cases, and can result in said-per SOD.
If your working with an older build, the g-sensor can cause a freeze, but its not quite a hard freeze unless you fiddle with it to the point of it not recovering.
If your using Set CPU and its clocked on the lowest settings, this can cause hard freezes upon wake up.
These are the main reasons that I've found for my own SOD. My suggestion? Use a WM Rom built specifically for android. Use a RECENT build that specifies that most everything is working. There are some new chefs out there working on builds that aren't quite as polished as some of the more experienced chefs.
Good luck, and may you never experience an SOD again!
Click to expand...
Click to collapse
The thing about the Windows ROM is bringing up this question. What is the best WM ROM to use? I'm using Miri's V17 but it sucks so much it can't even get the flipping time right... I really hate it, what should I change to?
I'm using ChuckyDroidRom, and its working out pretty well for me. But I cant say its the BEST.
M&ate said:
I'm using ChuckyDroidRom, and its working out pretty well for me. But I cant say its the BEST.
Click to expand...
Click to collapse
I'll give it a try. Anything is better than a POS that can't even get time right... should probably try Elegancia too, hearing good things about that.
Im using an old energy rom from back in june i believe and i will get a random screen freeze. Maybe one every 3 days. thats it. and my radio is still on 2.10 and i can get through a day of normal use with just one battery. Someone had referred to that aldiko app but thats too much trouble. If your getting that many SOD's then reformat your memory card, add a fresh android build. And try not messing with setcpu. Im using the froyo build by tytung and its running great.
+1 for not having anymore freezes. I have not had 1 freeze in the last 7 days using latest darkstone froyo build. Im also using a old full energy rom from july. Also a class 6 8gb memory card.
I think with all this work that has been done on these kernals and builds have REALLY reduced the SOD's.
I tried the initial NAND build upon release but had to go back to Winmo for the following reasons;
Higher battery drain than Duttys Family Rom
Led stuck on all the time after a message
No screen rotation
Crashing playing .wma files
Contacts listed by first name, no way to change it without editing it all.
Random freezes, slow to respond after standby, low volume in calls even after trying the speaker fix, g sensor would not calibrate.
All in all, enough to put me off. However, having gone back to winmo I can see that android is the way I want to go.
So, simple question; which build, if any, has the most of these issues fixed particularly battery drain and rotation? I am not bothered about getting 'under the hood' to tweak everything just a nice clean stable ROM with no fancy UI tweaks.
And I have searched on this for days but there are many, many opinions in hundreds of pages of comments. Thought I would ask here for the benefit of anyone else looking for a nice clean android build.
I have only tried the CM build (call me a fanboy), and it's really stable. I have noticed the 60mA battery drain still happens at times, but using Quick Reboot (free on market) one or sometimes multiple times fixes this without too much effort.
Speed, stability and features (well, the ones I use, didn't do a thorough test on everything) are all good.
I will no doubt slap my forehead for this but what is the CM build?
Has any build so far fixed the battery drain and sensor properly?
Cynagen mod =cm
I'm using MDJ's gingerbread its very stable and plenty of free space but no gps usb or camcorder apart from that smoorhest Android build I've ever used and one used most
i suggest NexusHD 1.9 NAND version, it's very stable, smooth and fast and i have no problem with it. just works well ;-)
Are these suggestions based just on personal preference or do they address those issues I had in the first post i.e battery drain, lack of rotation (G-Sensor problem I guess), LED stuck etc?
Appreciate your input all the same but I feel like reflashing Android today and want the best ROM...if those issues are fixed.
CM based or Nexus1. I think that until they are optimized, Sense are a no-go for Nand : too heavy, too big. You will be left with 50-40mo for apps and that includes apps2sd. Count on the double with CM and N1 Nand's. And in terms of battery life, G-sensor, they work perfectly.
The Led seems to give problem to most of the Nand for the moment...
Downloading the Nexus 1 rom now, I can live with the led if sensor and battery are better, especially as it is so easy to get back to winmo if needed.
I Know Ill Slap Myself Too For Asking Nooby Questions...but
Does it Matter What Radio i Use To Flash nand android as long as its above 2.08.whatever number ....i forgot....will it still work
I think I am on 2.50.14 and it installed like a charm. Absolutely great Rom; getting 2ma in idle and everything I wanted works fine.
Two things though;
1. LED doesn't blink to notify of messages
2. .wma files don't play (maybe that is normal for Android).
Just one thing to bear in mind (I didn't). As this is non-sense you cannot use HTC sync so I spent quite a while getting my contacts back in via business card from Outlook.
Great rom so far though. Nice and clean UI.
splinters69 said:
I think I am on 2.50.14 and it installed like a charm. Absolutely great Rom; getting 2ma in idle and everything I wanted works fine.
Two things though;
1. LED doesn't blink to notify of messages
2. .wma files don't play (maybe that is normal for Android).
Just one thing to bear in mind (I didn't). As this is non-sense you cannot use HTC sync so I spent quite a while getting my contacts back in via business card from Outlook.
Great rom so far though. Nice and clean UI.
Click to expand...
Click to collapse
Sync contacts with gmail then it stores them in the clouds
Try HD2ONE froyo cm 6.1.1 nand.
http://forum.xda-developers.com/showpost.php?p=10246269&postcount=228
It supports using your existing cm6 data.img on sd card. This alleviates the issue of low device storage.
This was rock solid as an sd build and better on nand.
I'll be sticking with this until gingerbread has all features working.
Hi,
I have been using my HD2 with android for a long time without too much trouble. Not long ago, while still using SD builds I would find that my phone would often freeze, this would happen almost always while surfing the web or playing games or while putting the phone under heavy load. Using nand builds the issue has gotten even worse. Every single build I have tried is almost certain to freeze during the initial setup, even if I leave it alone and give it a long time to setup and stabilize. I have been using a stock gingerbread NAND build for a week or so and it just won't be stable. It freezes during games or surfing the web mostly (though upon first installing the build, almost anything might trigger a freeze, including scrolling through a menu). I have tried task 29, and many builds but they are all giving me this issue. Even the last WINMO rom I tried did the same. I am completely baffled by this and have no idea what could be wrong. Does any one have any advise?
Thanks
Pray that you're still under warranty???
If it does it in winmo, try flashing your original stock (From HTC) ROM. This will remove HSPL and any & all customisations. Make sure the phone is in it's 'from factory' state. If it STILL has freezing issues, you need to get it repaired. If not. Start installing ROMs again from scratch.
Hope This Helps.
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
wtf, there is seriously no one else who has heard of this?
Bump.
Are you Overclocking it? Try Underclocking it to see if it is more stable. Maybe your hardware is failing. User currentWidget to see your current usage.
Maybe you're using too much ram. o.o
The phone will get really laggy if you use up all the ram, so clear it up with a task killer.
No overclock, running at 998 (stock) and smartass governor. Tried interactive governor and still does it.
Its just strange that it crashes left and right from doing anything when I first install a build and after a few reboots it stabilizes enough to be rock solid for all tasks except playing something like angry birds or surfing the web. I tried running quadrant 10 times in a row to stress the phone and it did fine.
Could the phone be overheating? I notice its almost always warm or hot when it crashes.
poweroutlet said:
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
Click to expand...
Click to collapse
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
nightcraw said:
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
Click to expand...
Click to collapse
I'll try to cap it at 800 Mhz and see if I can cause a crash. Regardless Its probably best to flash to stock rom.
Here is what I think I'll do:
Flash to stock rom.
Reflash HSPL
Task 29
Flash new radio
Flash MAGLDR
Flash new android rom
So I flashed 2.10.1 stock rom from here:
http://forum.xda-developers.com/showthread.php?t=655653
And it did not remove HSPL...though it reset my radio to 2.08.
So far things are not looking good. On the very first boot the stock winmo rom crashed and rebooted. Should I flash another winmo rom?
EDIT:
I've reflashed HSPL and also flashed the latest winmo stock rom with Radio 2.15 now. Running Android off the SD card, 2 minutes of angry birds is all it took it to freeze it. I'm starting to believe there must be some hardware damage or something, this is making no sense.
Even surfing the web in the stock winmo rom caused a reboot, the phone is getting quite hot too.
Having exact same problem... should i warranty it and send it in?
ArkAngel_X said:
Having exact same problem... should i warranty it and send it in?
Click to expand...
Click to collapse
If you are lucky enough to still have warranty, do it. I don't have that option sadly.
So I have pretty much narrowed down the cause of the problem to overheating. I let the phone cool down to about 25c and then I ran angry birds and surfed the web and it didn't crash and I played for about 15 minutes. When the temp approaches about 37-40c, the chances of a crash become pretty high, once it crashes it will keep crashing left and right until I let it cool back down.
All evidence now points to an overheating problem. Especially because it is only intensive tasks which seem to cause crashes and only the more CPU/GPU intensive tasks can cause the phone to heat up fast.
Anyone else dealt with this issue? I have no other way to prevent this than to stop heavy use of the phone when it gets warm. This is ridiculous, next thing I know, I'll be walking around with a desktop CPU heatsink mounted on my HD2...
First post WOOO
I have been having a similar issue with my HD2 (Telstra). I was running darkstone on the SD card but occasionally my phone would freeze then I would have to restart a few times to get it working (or leave it for a while). I decided to install the android desire stock ROM using NAND. I changed the radio according to the recommended 2.15.50.14.. after I did this I had a lot of problems with frequent freezing even before installing the new ROM (so during the process). I did successfully install the stock ROM but I now have the issue where if I enable internet usage within about 5 minutes my phone will freeze (but only if I am using the phone). However if I use wi-fi or usb tethering I can use the net for anywhere between 5 minutes and 8-9 hours.
I also have the problem of freezing just after boot, but apart from that my phone has never frozen unless I enable internet usage. Furthermore, this issue only became frequent after changing radios. (for the life of me I can't remember what the previous radio was). When I have more stable internet access I'll try flashing a few different radio's...
But right now funnily enough.. I'm jumping between my phone internet and someones open network in my apartment block... both of which are very sporadic...
Hope this helps somewhat (or will at least..)
There are many threads regarding this issue. If you still have the problem after trying different radios and roms, then it is probably the mainboard.
Mine was also overheating and after I tried all possible fixes, I sent it for repair. They changed the mainboard and everything is OK now. No overheating at all.
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