Related
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
This problem just started for me and I have experienced nothing like it. I'm running the LG p930 with CM10.1.3 RC2. Yesterday, the phone began restarting whenever it tries playing a sound. This happens in Netflix/ Youtube once a video starts, Pandora when it attempts to start playing a song, even the sound panel when I use the volume rocker to try changing my volume and it attempts to play the little beep. It also happens no matter what speaker it tries using - headphones, speakerphone or earpiece, meaning I can't actually use the telephone functionality of the device either..
As far as fixing- I've tried clearing the cache and dalvik, fixing permissions, and even flashed several other ROMs. Everything seemed to have the same problem. Does anyone know what could be going on?
This exact thing happened to me. I couldn't find any information on it.
I had to completely format and un-brick the phone. I'm not even sure that it worked the first time. But after completely wiping and un-bricking a couple of times, it was back to normal. I think this is the guide that I have always used for that.
http://forum.xda-developers.com/showthread.php?t=1597488
Hope this works for you. I know that problem can really suck.
Thank you so much! I'll try this. I can't believe someone else had this issue, it seems incredibly rare. Can you tell me more about it? What ROM were you running? could you play any sounds at all?
Thanks again
I know what you mean. I was surprised to stumble across this post about it. I feel like I have had a few issues that just seemed very strange with this phone.
Mine was just like you described. I couldn't even change the volume without it crashing. If my phone was on vibrate, I could see the call come through. When I answered the call, the phone crashed.
I was probably on a PAC-ROM or CM10 Nightly. But like you, I probably went through every available ROM, stables and nightlies at that time. I think I even tried to flash a stock ROM.
Thank you so much. Actually, you don't have to follow the whole guide. All you need to do is download the image files, and skip to step 4 in the section "Restoring the original Nitro HD images:" Then get cwm working, and move on from there with whatever ROM you want. I would never have thought to try this. Thanks again.
I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Is this a known issue with the D851 and CM13? I keep getting a force close over and over and it won't stop unless I reboot the phone witch in turn disables Bluetooth. I can't seem to find anything about it other than one post with no answers. Here is a pic of the build causing the problem. Any way to fix this?
Same issue here. Seems to be caused by a commit to lg g3 update init in the cm changelog.
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
SovereignKnight said:
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
Click to expand...
Click to collapse
Looking at the changelog for the next potential nightly, it seems like it will be fixed. They added back part of that file.
See http://review.cyanogenmod.org/#/c/132118/
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
UPDATE: re-flashed, GPS is working fine.
I dirty flashed 20160212 and now my GPS doesn't work, but the Bluetooth messages have stopped on my D851.
mdphoenix said:
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
Click to expand...
Click to collapse
CM maintainers Forget our Device is BCMD unlike their devices.. so they think if it works for them, it must work for all.......
Only the D851/D856/F400/LS990 use BCMD while the others use that wcn crap.
as for data. Leave that to CM to mess that up to............. I had to go and fix my Device tree for PAC that CM totally screwed up.
your data issue is more a apn-cong.xml issue.. if you want a fix to that.. go read the last few pages on my Pac thread. and I listed a fix for data issues..............
Nice. Thanks!
..
Had this issues on an earlier build fixed it by reflashing
MuF123 said:
What was the fix?
Click to expand...
Click to collapse
A long hard road followed all of this. Lessons were learned, and in the end, nothing really gained. Except a working phone.
The entire issue started when I tried to flash SuperSU. Not knowing that CM didn't use SU. That began the decline. I ended up using the LG flash tool to put it back to an older stock version. It worked for a while, then I rebooted and it went to hell. Deader than dead. I shipped it off to a guy in Texas I found on Ebay to JTAG it. Came back just fine. Except I think whatever I did to it before then jacked up the charging. The phone wouldn't charge at all. Sitting on a charger for two days gave it about 5%. Come to find out, it was still under warranty. I shipped it to LG. They fixed it, returned it, and now it's on stock Lollipop, and I have to say - I quite like LG's interface. I've turned off a few things, installed Nova, etc. But at this point I have no reason to root or go custom. I did with my VZ phones because they were such nazis about everything. But I've got free tethering with Tmo. The phone works well. So, I'm sticking with what I have for now.
Good morning all,
I wanted to get some thoughts on random rebooting and wi-fi dropouts I am having with my Samsung Galaxy Tab Pro 8.4. For some time now I have had issues with random rebooting of my tablet - often when first starting a game or other app. I mostly dealt with it, but finally got frustrated enough to really start trying some other options. My tablet has long been rooted and for a while I had some success with CyanogenMod. But then I started getting freq crashes with that. Tried rolling back to earlier and later versions (always with a complete wipe)...still got crashes. Then went back to complete stock, still crashes. Then reloaded TWRP and tried two other ROMS - Resurrection Remix and Slim (always with a complete wipe). Still getting random reboots.
At this point I wonder if it is hardware issue.
As pointed out in other threads I have the issue of the wi-fi frequently dropping. It usually reconnects after a bit, but very frustrating.
Any thoughts or insight is appreciated.
Thank you.
Raife1 said:
Good morning all,
I wanted to get some thoughts on random rebooting and wi-fi dropouts I am having with my Samsung Galaxy Tab Pro 8.4. For some time now I have had issues with random rebooting of my tablet - often when first starting a game or other app. I mostly dealt with it, but finally got frustrated enough to really start trying some other options. My tablet has long been rooted and for a while I had some success with CyanogenMod. But then I started getting freq crashes with that. Tried rolling back to earlier and later versions (always with a complete wipe)...still got crashes. Then went back to complete stock, still crashes. Then reloaded TWRP and tried two other ROMS - Resurrection Remix and Slim (always with a complete wipe). Still getting random reboots.
At this point I wonder if it is hardware issue.
As pointed out in other threads I have the issue of the wi-fi frequently dropping. It usually reconnects after a bit, but very frustrating.
Any thoughts or insight is appreciated.
Thank you.
Click to expand...
Click to collapse
I am sorry to see that we both have exactly the same problem, and that nobody seems to have an answer :crying:
I have wiped and installed numerous times several roms, but my tablet just won't boot again ...
misery loves company...
Fortunately mine boot and usually works...but the rebooting is very frustrating...
Good luck and I'll post if I find anything out.
Follow these simple steps to go back to stock ROM : https://forum.xda-developers.com/ga...ral/firmware-stock-firmware-tab-pros-t3087238
Tablet looks to work fine.
Still have to install twrp and flash RR or LOS and see what happens...
Edit: rereading your OP and realizing you already tried that : /
Hope second shot will be the good one...
Edit 2: RR 5.7.4 working perfectly
Mine just started to do something similar. Using ResurrectionRemix 5.8.2020170401 for months with no problem. In the last few weeks, tablet would not wake up after powering down. Had to do hard reset, then would work fine for hours until next failure.
I wiped the device and reinstalled RR and Gapps, same thing happens. Wondering if there is a hardware problem sneaking up on us?
pilotbob3 said:
Mine just started to do something similar. Using ResurrectionRemix 5.8.2020170401 for months with no problem. In the last few weeks, tablet would not wake up after powering down. Had to do hard reset, then would work fine for hours until next failure.
I wiped the device and reinstalled RR and Gapps, same thing happens. Wondering if there is a hardware problem sneaking up on us?
Click to expand...
Click to collapse
I will be able to answer precisely within a few days.
In the meantime, tablet working great after reverting to stock, then falshing MM version of RR for 2 days straight...
ROM has nothing to do with hardware problem, especially the flaw in Samsung battery connector's cables, loosely contact to pins of battery connector on mainboard.
Everyone has a good technical background will clearly see what is causing reboot or shutdown:
https://forums.androidcentral.com/s...350-goes-continual-boot-loop.html#post5928150
You will see this problem in any Samsung tablet which has that battery connector: Tab A, Tab Pro, Note Pro, Tab S.....etc...
This is another example of this problem regardless different ROMs are loaded.
https://forum.xda-developers.com/galaxy-note-pro-12/help/wifi-disconnecting-battery-charge-t3664128