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
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.
I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?
had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.
Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though
If it was a PC you would say its overheating .
jje
Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why
quick answer. Reflash the phone .
I guess reflashing and removing some dangerous apps will be good for you phone.
Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it
I keep getting random lockups, at least more than once a day, and sometimes several reboots in a row.
It appears that i can happen almost any time, whether it be at a lock screen, while titanium is asking for root, or opening twitter or facebook, even the gmail app. It simply freezes, and requires me to long press the off button and reboot.
Unfortunately, i can't get adb via usb to work on the nook, so i can't get a reliable logcat.
Is this common? I have had two nook devices so far, tranferred the rom over through nandroid and have had lock ups on both, I am flashing regular cm7 nightlies now (emmc), but it occured using phiremod too.
Help?
I never had one, maybe I'm lucky
Have you tried fixing permissions in clockwork?
Sent from my LG Optimus V using Tapatalk
I am having the same problem. I loaded CM7 to my emmc yesterday and I have had it freeze on me a couple of times now. All have been random. I do have performance set to 1.1 and on demand gov set.
So I can just go to ROM manager to fix permissions? Hopefully that works.
EDIT**
Did not work. Was fine, then I uninstalled market updates, connected to wifi, opened the old market, searched for flash and it froze up. Any ideas?
EDIT 2**
uninstalled beautiful widgets (read that somewhere), so far no lockups (fingers crossed).
i had mine lock-up twice last night
i was in dolphinHD and i had just installed swype beta
i have only had 1 time that it has locked up before then in the last 1-2 months that i have had it.
im blaming swype, since i havent had the problem in the past
perhaps not your problem, if you dont have it installed.
I get lockups pretty regularly. It's irritating. Not sure what the cause is. I thought overclocking had something to do with it but everyone else is overclocked and this problem doesn't seem to be common.
How low do you have the voltage settings in tweaks? Having a voltage just barely too low for your CPU can cause a lot of weirdness. Also, it could be any one of the stepping voltage settings, not necessarily either the min/max frequency.
Folks, playing with the voltage settings in nook tweeks is not for the average user. These settings can really bork your nook. That's why you get a warning when you open those settings.
That being said, I have been running cm7 on eMMC for months and have never had a lockup. I am overclocked to 1200 mHz but have left the voltages alone.(cm7.1 nightly 160).
If you are running on eMMC,try fix permissions first. If that does not help, start looking at the apps you are running to determine if one of them might be the problem. Several people have reported issues running beautiful widgets. There are other apps that can cause issues. If you have good backups of all your apps, try removing apps one at a time. In the process, you might learn something about your system.
Worst case, reinstall cm7, wipe data, cache, and dalvic cache. Start over with a clean system and add your apps (apps only, not apps+data) one at a time. This will ensure that a possibly currupt data set was not causing the issue.
The key to a fast, well functioning nook is to start slowly and ensure each change works well before moving on to the next step.
While it's true I have more time than most to play (retired), my nook can run circles around most competitors but only because I took the time to set it up right the first time and I am not afraid to wipe everything and start over.
Sent from my NookColor using Tapatalk
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
I had been getting irritated by these these random locks up for a while. It seems that uninstalling beautiful widgets fixed the problem for me. I thought it might be that BW was trying to access the GPS, but it still locked up after disabling geo location in BW.
liam.lah said:
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
Click to expand...
Click to collapse
In case you're still interested, BeWeather is a great substitute for BW and FlexT9 in place of Swype.
Also, I had issues with lockups no matter my overclocking and formatting the eMMC and possibly reseating the SD card fixed it.
I just wanted to share with you my recent issue & solution to the XOOM 2 rebooting issue.
Now to give you an overview of my situation, I purchased the XOOM 2 10.1 UK back in January 2012.
I use it almost every single day. No surprises I was getting random screen freezing followed by reboots every single day. Most days twice!
Now I was hoping that when the update happen back around 2 months ago that it would solve this issue. It never.
In fact my freezing & reboots were happening more frequent.
Basically within 5-10 mins of using the Xoom2 it would reboot.
Some days I just wished I could throw the dam thing through the wall.
I rooted using Dan’s method. The only method. & tried various ways to solve the issue.
NOTHING worked.
In fact, I was convinced that my rooting & installing things that should not be there was making the reboots worse.
So I cleaned up my Xoom 2, went into recovery, wiped cache & cleaned data & rebooted.
This still did not work.
Then I tried task managers, cache cleaners & even paid for that system panel app that logs all apps & usage.
Nothing worked; I was still getting the reboots. Everyday.
So after looking over many Xoom 2 forums & with many issues and complaints about this issue, I was close to selling & getting an iPad.
I was convinced it was hardware.
Then I tried this way:
1. I rooted.
2. I installed ADW Launcher & made default.
3. I installed SetCPU
4. I installed Titanium Backup
5. I froze the stock ‘launcher’ – (whatever you do – do not un-install any app, you CANNOT update Xoom if you do)
6. I changed CPU from ‘hotplugmoto’ to ‘performance’ 1200min 1200max
(I know you might think this uses lots of battery but I found not)
7. Set up setCPU profile for ‘screen off’ I use ‘on demand / 300 to 600’
Battery over night on this setting did not go down by 1%
8. Rebooted.
After 4 days of constant use & trying so hard to get the Xoom to freeze & reboot – I can’t.
This method works.
I have surfed using ‘Firefox’ while using ‘Currents’ while using ‘Google+’ while downloading files and steaming music via ‘Google Music’. I have open every single app & been quickly switching between them all trying to over load the system.
Nothing will freeze or reboot my XOOM 2.
What I can get from this is that the Xoom 2 works perfectly.
With the high CPU set, it is so fluid and lag free. It works almost perfectly now. It also means the hardware is absolutely fine.
Maybe with newer firmware updates in the future this will be sorted naturally.
I makes me think something with the high CPU means a bug in the processing won’t make the Xoom freeze & reboot.
Until then this method works for me and I can’t see why it won’t work for you.
If you are having this issue I hope this helps.
I messaged you on the Motorola Forums, but I think they may take it down since they don't like talks about rooting.
But thanks for posting this, I will give it a shot.
When you changed to performance 1200 min/1200 max - I'm guessing you also checked set on boot? right?
Yes i ticked set on boot. Make sure you have a screen off profile otherwise it will be running at max all the time.
Hope it works for you.
Sent from my XOOM 2 using Tapatalk 2
Hi,
I froze some bloat before and uninstalled flash 10.3 cause flash streaming online videos didn't work 4 me (neither 10,3 or 11,x), then installed flash 10.2 and all starts to work ok but still 2 or 3 reboots for week.
Also seems that "memory booster" app helps when some apps starts to freeze and u can finish em and free some mem.
So now i'm trying setcpu and then i will do launcher trick
Thx a lot!
Vanpeebles, Did you switch launchers because you think it will help the reboots? or because of personal preference?
List of frozen apps
List of frozen apps 2 months ago without issues:
App used: Ultimate Backup
Amazon Kindle (I dont use it)
Citrix Receiver
Drippler Motorola DROID Xyboard 8.2
Drive
Fuze Meeting
Google+
GoToMeeting
Servicios de estadisticas de dispositivo ("Device statistics Services")
Twonky
Good luck everybody!
Now i'm not expecting ICS, this is working almost perfect. Let's see setcpu improve.
It does seem that the source of the freezing/reboots is the Motorola Launcher. Since I switched to Go Launcher HD I've definitely seen less freezes.
Hi
I switched launcher on personal preference but to be fair I have had no freezes now for 5 days
So I'm not messing now if it ain't broke.
The reason is I did this is I read 1 post on another forum that someone changed launcher &, this helped him.
So wether launcher or high cpu I'm not bothered
To finally have a working tablet is such a huge relief!
Sent from my GT-I9100 using Tapatalk 2
Thank Vanpeebles,
I did everything you said and now hoping for the best!
Either way, I'm loving ADWLauncher Ex..... sooo fast and snappy!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
Thanks my Xoom 2 is running great again!
Also add this warning. Do NOT remove the Launcher2 app if you do then your Xoom 2 will never boot again and the is no current way to fix this because of the locked bootloader.
luke.arran said:
Thanks my Xoom 2 is running great again!
Also add this warning. Do NOT remove the Launcher2 app if you do then your Xoom 2 will never boot again and the is no current way to fix this because of the locked bootloader.
Click to expand...
Click to collapse
That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
big ach said:
That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
Click to expand...
Click to collapse
No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.
luke.arran said:
No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.
Click to expand...
Click to collapse
Yeah but won't freezing the launcher (or changing its name to launcher2.apk.bak) cause problems if your tablet faces a failure and the adwlauncher crashes?
EDIT: I guess titanium backup unfreezes apps if you do a wipe so the best option is to freeze the stock launcher (NOT uninstall it and NOT rename it)
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
Over 1 week now and not 1 reboot.
I can't answer these questions on the launcher?
All I know is this works for me, I have had not 1 freeze or reboot, so the stock launcher can stay frozen.
(it may have absolutely nothing to do with it, but I really don't care)
Hi after several days over GO Laucher EX (or HD "Tablet version but less customizable") with Setcpu 1200 1200 performance and etc....
only 1 reboot when several web pages were opened on stock browser with flash videos etc.
I've noticed that now when apps stops to work it goes back to home instead of reboot except that time.
Almost no free ram and that's seems to be the clue..Stock launcher doesn´t free enought memory
And battery drains suddenly stopped.
Super happy man . More fluid launcher, more customizable, and also wifi starts to work better when comes back from sleeping
Thanks for not to give up!
Have to say... this solution seems to be working very well. I'm running set CPU in conjunction with auto memory manager set to "aggressive" and AdwLauncher Ex!
Using many apps that in the past would give me reboots, but now they are working flawlessly.
Thank you very much for this awesome contribution!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.
Neolo said:
I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.
Click to expand...
Click to collapse
When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!
So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!
big ach said:
When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!
So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!
Click to expand...
Click to collapse
I'm currently running on stock kernel without ability to scale over 1000. Tried to set to performance governor only, but failed and got regular reboot during usage. Will try your method.
Seems to be it's operating system problem. Don't understand why motorola still didn't resolved it, including that fact that problem also present in first Xoom model.
Worked a bit around with your solutions and stabled on the following:
Stock launcher frozen;
SetCPU profiles:
Screen ON/unlocked: Governor OnDemand (1200-800) with Noop Scheduler
Screen OFF: Governor standard hotplug (800-300) with noop scheduler
It looks like moto_hotplug governor doesn't work quite well but I also noticed some glitches on systemui.apk. Whenever you turn your screen on and unlock doesn't show smooth you must turn off screen and try again... if you unlock with a laggy unlocker the whole system will be a mess.
With those setting I'm not having reboots, just some lags here and there; battey, however, lasts much less due to ondemand governor.