Develop Bugs

[PROBLEM] Random freezes/crashes on Desire

Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...

it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...

Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.

Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse

Try reinstalling the ROM or installing another ROM.

hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long

Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't

Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App

Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin

Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App

[Q] Proper flashing of ics rom

I've been running the ICS roms on my kindle fire for 2 months now and wanted to start out by thanking everyone involved in it's development (currently cm9.2.24 and current gapps). I spend a lot of time reading the posts and learning as I go.
I read a lot about black screens and screen lock ups but until recently it only happened occasionally to my device. For the last 3 updates my device has been experiencing each constantly. every time my screen goes to sleep or i turn it off I either open up a frozen screen or a black screen and I need to do a restart to get it to work again. and I haven't seen any comments in the development thread that describe this happening to this extent.
My question is...Is this happening to everyone else or might I be doing something wrong. This isn't my primary device and I can deal with it if happening to everyone and I enjoy the tinkering but I'm thinking its more me and something I'm missing. What is MD5?
When I flash the rom i wipe I do a factory reset, clear delvik cache, cache, and system. and simply restart. Should I be doing more? thanks for your help.

My kindle turns on just fine after sitting for hours or even all night. This may be due to the fact that I have wifi keep alive installed so the wifi never shuts off.
Sent from my GT-I9100 using xda premium

I have also been updating routinely keeping abreast of the latest ICS and have not had any problems so far doing he same cleaning. Could an app be the cause?

MD5 is a way to check to make sure you haven't downloaded and are about to install a corrupted file. You can download a program like MD5 Calculator and check the value of the file on your computer against what the value is supposed to be

I had this issue before with another device. It was wifi going to sleep and not wanting to wakeup... try downloading some sort of powermanagement app and set wifi to.never sleep

Thanks for the help. I thought early on that the problem might arise from an app and have held off installing apps once I flash and it still happen right away. I've read about others with issues related to wifi but never considered that might be my issue. I'll give that a try and let you know if that takes care of it. thanks for the suggestions and with the md5 clarification.

I've set my wifi to always on for 24 hours now and the same issues are still happening constantly. I've also removed the bulk of my downloaded apps to test if they are causing the issue. I only have words w/ friends, g-reader and gmail on the kindle which I assume are fairly popular and others are using too. if I try to re-flash should I wipe more than what I listed in the OP (factory reset, delvik, cache and system) ? issues again are constant black screen and frozen screen. Any other suggestions would be appreciated.

Are you still having the issue? Im suprised that didnt fix it. 99 percent of the time screen of death is wifi sleep problems.

It happened to mine this morning ...
I tried to turn on/ return from sleep mode this morning, and it was the Black screen ... had to hold for 30secs, before it would boot.
I think my issue was related to an alternate Keyboard App I had installed - Touch Pal. It was working perfectly for several days then this morning after the reboot gave me constant FC errors, until I removed the app, with root explorer.

[Q] A Couple VERY Weird Glitches Occurring (Need help please!)

*Originally I posted this in the Help section of the G3 forums but got no help, so I am posting this here*
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.

I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.

GuyInTheCorner said:
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
Click to expand...
Click to collapse
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/

iDefalt said:
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
Click to expand...
Click to collapse
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?

Sounds like your phone is superstitious
Sent from my LG-D855 using XDA Free mobile app

GuyInTheCorner said:
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Click to expand...
Click to collapse
Yeah I thought that but I wanted to know if anyone here has had the same issues.

iDefalt said:
Yeah I thought that but I wanted to know if anyone here has had the same issues.
Click to expand...
Click to collapse
the WiFi issue seems like its something to do with battery saver/quiet mode (to me anyway). Unless your router is kicking the phone off at that time?
EDIT:
oh and regarding the Voice Mate issue it could be either the jack or your headphones?

Please do not double post. It is a violation of Forum Rules.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer
Click to expand...
Click to collapse
This thread is closed. Your original will remain open here: http://forum.xda-developers.com/lg-g3/help/couple-weird-glitches-occuring-help-t2974077

Persistent debris/moisture error

My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.

Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.

blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.

drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.

Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?

Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.

drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...

drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.

Question Multiple restarts

Just got my 6p yesterday and Getting multiple restarts and system UI crashes , I did restore my phone with apps ect I wonder if that could be the issue anything helps thank you .

Sounds like it. If your using a custom launcher delete the widgets and readd them

No custom launcher should I factory reset? or try something else will delete the 1 widget and see if that helps any other solutions is welcomed thank you

There are some people here that had a similar issue (including me), I myself had to get a new device (replacement) from Google to solve that issue. We already had/have a thread about this, maybe you can find some info there.

Okay thank you back from a restore less restarts but still getting them & phone freezes up from time to time guess this is a serious issue & not just software smfh.

sunnybwoy1 said:
No custom launcher should I factory reset? or try something else will delete the 1 widget and see if that helps any other solutions is welcomed thank you
Click to expand...
Click to collapse
I'd do a FDR and start from scratch. I know it takes longer but I do it with every new phone and after a major OS update. I'm a firm believer in not bringing any data over from an old phone.

Can you define FDR? I have done a factory reset if that's what you mean but I think I have fixed the issue will report back after 12 hrs of testing & results

I had the same issue before but this is what I had done before and after, so I hope this advice may help you.
I had come from a OnePlus 8 Pro, so I naturally wanted to transfer all data from 1 phone to the other. BIG MISTAKE! I had several reboots during the 1st few days. So I started searching around this forum and found a few people suggesting that you factory reset your phone but DO NOT TRANSFER any data from your old phone to your new phone (using the cable). Instead, factory reset your Pixel 6 without restoring any data, then once you get through the initial setup, upgrade to the latest version using an OTA file. Once you did that, then start slowly manually transferring the data from your old phone manually. This is what I did and have had no issues since, no reboots and everything seems solid. Battery life seems way better doing is this way and the UI seems more stable as well, as before, it would be janky and the battery would drain.
I hope this helps

I had the exact same issue and it was only solved by getting the device replaced. I found the replacement device worked better in all respects, not just solving the reboot problem.
Just get a replacement!