Database Users

Phone keeps freezing...please help

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.

Diagnosing hardware failure

For the past few days I seemed to be getting a lot of random force close errors on my legend, with no discernible pattern. This continued up to the point where all of a sudden pretty much every app crashed and wouldnt remain open more than a few seconds. I then tried to reboot, and since then the phone just gets stuck in a bootloop at the rom loading screen. I've tried four or five different roms, all with the same error.
I would assume this was a memory/processor malfunction, however the fact that I can still flash roms and make backups with clockwordmod suggests to me the hardware could be ok? Does anybody know of some sort of diagnostic rom I could run to check this?
Thanks guys
Matt

Here's some stuffs to check out, don't over clock, Max 600mhz, not every phone can be oc'd, maybe even try less processor speed say 480 MHz. Have u been ocing your phone on extream speed for long time, like 806+ mhz, that will kill a processor for sure.
Have you done a fix permissions with clockwork mod? This can help heaps with fc's.
If using an ext partition which type are you using 2 3 or 4, apparantly if your using ext4 and your phone is crashing it can cause even more issues.
Using lots if widgets on your screens?
Have you tried a different/new SD card?
My understanding is your rom space can eventually fail if your flashing lots n lots of roms, but you said you can flash successfully, so that sounds good.
There is a few to start you off.
Sent from my Legend using XDA

Amazingly I have managed to completely fix the problem. In a last moment of desperation before buying a new phone I decided to try wiping the battery stats, simply because I had never tried it before (didnt see the need to). Miraculously this did the trick, and I managed to boot into cyanogen 6!
I then restored a backup I made when the phone first died, and confirmed it was still broken as I expected. I then wiped the battery stats , and viola it worked!
I have no idea what is stored in the battery stats, but I am very surprised this made a difference. Thanks for your help anyway ranger.

[Q] High memory usage?

Hello.
I've read various other topics about how not having too much ram is good, expected, and so on.
However, when I first got my n7, it would use perhaps about 50% of the RAM, without any apps. I could run a bunch of apps, and they'd be responsive, I could move between apps quickly and easily, and everything was smooth. I've tried multiple roms, and kernels, and everything was good.
Until lately. Suddenly, when I boot, apparently i'm using up 75-90% of the ram. I've manually added up the amount of ram being used, and found that the apps that were running in the background were only using about 128mb. Starting applications takes a while, scrolling is laggy, and switching apps can take up to 15 seconds at times.
I figured it was a kernel, so I switched back to a reliable kernel. Nope, everything was the same. Was it the rom? I've tried AOKP, Dirty AOKP, paranoid android, and a few others. Bootloader perhaps? I've switched between clockwork and TWRP. Cleared the caches. Tried changing the I/O governers, various schedulers. Still laggy, and still using up a lot of RAM.
Should I back up my data, and do a factory restore? Or am I just missing something that's staring me, ready to slap me in the face with it's obviousness?
Thanks in advance.

Depends on which apps are you running in background , like for ex Chameleon Launcher uses around 100mb of ram . Better go back to stock and see if the problem persists
Sent from my Nexus 7 using xda premium

Any 5.1 ROM that isn't horribly slow?

I use CM12.1 on both my N7 2012 and N6 and it's incredibly slow on the N7. Clearing the cache does nothing, trim does nothing, F2FS /cache and /data does nothing and even the stock 5.1.1 image is slow.
I've read everything under the sun about poor NAND, not enough RAM, poor CPU, etc but none of them really make that much sense. I have hardly anything running EVER and I only have a few apps installed for opening documents an such. No Facebook or Email clients or anything that would be running in the background. The built in RAM manager tells me that I usually have over 50% of my RAM free and with such a small number of things running, my CPU usage is low, so I fail to see where the issue lies. I guess the NAND, but I also read articles about how that's kind of a load of bull as someone tested old 2012 N7s that had been heavily used and slow, as well as new ones and the R/W speeds were the same.
The main thing that bothers me about it is the fact that when I do a clean install of the 5.1.1 factory image or even CM12.1, it will be snappy for all of 10 minutes and then suddenly it becomes annoyingly slow. It's by no means unusable, but compared to my Nexus 6 every action feel like it takes 2-3 times a long. Even doing my pattern unlock feels sluggish.
I went back to KitKat tonight and it seems to run much better, but there are some things I've gotten so used to with Lollipop and Holo looks plain ugly now that I'd really rather not use KK. Does ANYBODY know of something I can do to speed it up even a little bit. This almost seems like a kernel related issue to me, seeing as how the N7 has been running off of an old kernel for most of it's life. It makes me wonder if there are some kernel-level things that might be done to help.

admiralspeedy said:
I use CM12.1 on both my N7 2012 and N6 and it's incredibly slow on the N7. Clearing the cache does nothing, trim does nothing, F2FS /cache and /data does nothing and even the stock 5.1.1 image is slow.
I've read everything under the sun about poor NAND, not enough RAM, poor CPU, etc but none of them really make that much sense. I have hardly anything running EVER and I only have a few apps installed for opening documents an such. No Facebook or Email clients or anything that would be running in the background. The built in RAM manager tells me that I usually have over 50% of my RAM free and with such a small number of things running, my CPU usage is low, so I fail to see where the issue lies. I guess the NAND, but I also read articles about how that's kind of a load of bull as someone tested old 2012 N7s that had been heavily used and slow, as well as new ones and the R/W speeds were the same.
The main thing that bothers me about it is the fact that when I do a clean install of the 5.1.1 factory image or even CM12.1, it will be snappy for all of 10 minutes and then suddenly it becomes annoyingly slow. It's by no means unusable, but compared to my Nexus 6 every action feel like it takes 2-3 times a long. Even doing my pattern unlock feels sluggish.
I went back to KitKat tonight and it seems to run much better, but there are some things I've gotten so used to with Lollipop and Holo looks plain ugly now that I'd really rather not use KK. Does ANYBODY know of something I can do to speed it up even a little bit. This almost seems like a kernel related issue to me, seeing as how the N7 has been running off of an old kernel for most of it's life. It makes me wonder if there are some kernel-level things that might be done to help.
Click to expand...
Click to collapse
Turn off journaling, use trimmer and try Minimal OS

XenonHD and BSZAospLP run fairly well on my N7. I've got the 32GB model, which purportedly has less memory slowdown issues than the original 16GB model, fwiw.
If your flash memory has bad blocks in it, that will slow down your device whenever it tries to read/write data. A full format of the /system /data and /cache partitions may help. I can't remember if there is a way to mark off bad sectors from being used. You'll have to research that. You may have to do a special kind of format to remove bad blocks from use.
Sent from my Nexus 7

GtrCraft said:
Turn off journaling, use trimmer and try Minimal OS
Click to expand...
Click to collapse
Well, disabling journaling did nothing and trimmer does nothing.

Dirty Unicorns with /data and /cache formatted to f2fs works perfectly with my n7 2012. I'd highly recommend it.

I assume you went from a full flash of the latest stock images, flashed latest twrp recovery, formatted f2fs for cache and data, flashed latest stable CM snapshot, and optionally installed the relevant open gapps as linked to on CM's wiki site?
Have you tried running this setup with no additional apps installed? Chrome isn't much better under this CM 12.1 installation than stock 5.1.1 for me, but everything else seems to run about as good as stock 4.4.4. One thing I do is reboot my 2012 N7 every time I put it on the charger

Chroma works fine on my N7.

admiralspeedy said:
Well, disabling journaling did nothing and trimmer does nothing.
Click to expand...
Click to collapse
Then you clearly did something wrong. Try with a custom rom like Minimal OS, Chroma or Ressurection. And with M kernel

What could I have done wrong? I flashed the file to disable journaling and I've always used trimmer... Disabling journaling literally did nothing.

im right there with you OP, my nexus 7 is ****. Doenst matter what rom, or what format (ext4 or f2fs). I slows to a crawl in a few mins of use, more often than not, takes forever to wake, and then will sometimes just go black before i can unlock, freezes constantly and requires reboots. I hate this piece of ****.

I've added
ro.config.low_ram=true
to the build.prop and I am running the Trimmer app once a day. There is still some lag from time to time, but at least it's useable.

Why Galaxy S5 gets slow gradually?

My Galaxy S5 was getting super slow. Often I had to wait 10 seconds or so that it reacts to my touches. I had the latest manufacturer rom installed.
I reinstalled Kitkat manufacturer rom and the device got as fast as original.
So my question is why the device got slow or how could measure what is causing these problems? I have noticed similar effect on other phones, when the same rom is installed for a long period of time.

Too much cache and datas. Try first of all wipe cache from recovery mode and do it once a week. If neither this will work, wipe data (factory restore) always from recovery mode and the phone comes responsive like new untill to much data and caches will slow it again. Don't install to many apps, even this slowers the phone. This happens even on KitKat.

You could also try to install an app called KernelTuner and see if the cpu is always on high load.
Is the battery draining fast or is the touch screen just unresponsive? But there are a lot of possibilities for this issue and if everything is falling apart you could switch to a custom Rom or buy a new phone.

I have the same problem with G900F which is SUPER SLOW after official Marshmallow 6.0.1 update. Stock Rom. It is the worst and slowest Android exprerince I've had so far. Is the solution installing custom Rom if there is any reliable and safe one?

Just install lineage os or debloated stock problem solved

There was/is an issue with the contacts db blowing up to gigantic size which had/has an impact on performance & stability.
My S5 was not affected, and i've been using 6.0. 1 for at least a year.
But today you can expect such behaviour on various occasions with a phone that has only 2GB of ram and a Snapdragon 801(which should still be competitive with the MediaTek SoCs in cheap phones, at least.).
E.g. my fav weather app WetterOnline becomes a resource hog sometimes on my S5 till the dreaded "app not responding" message, but not on my more powerful LG G6, and on other occasions the app runs super smooth again.
Something as basic and simple as a weather app should perform well on any device except the oldest or most basic ones.

My S5 became snappy after downgrading to Lollipop. Keep in mind it came with Marshmallow when I bought it brand new.