Related
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.
I've recently been having all apps on my phone close frequently. No error messages or anything, just close back to the home app (which happens to be repopulating widgets and such suggesting that it was closed too). For the life of me I can't figure out what is wrong. Once I see it happens I know my phone is unusable except for the basics until I reset it. At first it was mildly annoying, but it has been happening faster and faster after each reset. First a reset grabbed me a few days, now only about 4 hours. I tried a factory reset but it was only mildly better. Finally in desperation I tried using mattlgroff's "DROID RAZR HD Utility" to reflash stock, but that only bought me a week and a half.
Does anyone know what might have caused this? The only significant mod I made to my phone was rooting it while it was new to use Titanium, then I unrooted it and it was fine for several months after. I can't think of anything I had done outside my normal use before it started. I tried looking at logcat but I wasn't very good at sorting though it. Found the lines stating the apps were closed/services were restarting, but nothing else looked abnormal to me.
Sounds like a hardware issue.
Try a safe boot
Power up
At the appearance of the bootlogo, big m or warning, press & hold the vol down all the way home.
So I bought the S6, new, never been opened, sealed etc, let it charge the proceeded to turn it on. Then comes the welcome bit and startup, this is where it went tits up. Apparently everything stopped responding, google maps stopped responding, voice commands stopped responding, etc. Thought nothing of it, skipped through everything, got into home screen and then "Touchwiz has stopped responding". So naturally I though oh dear. Oh, it also started restarting on it's own randomly as well, I tried booting in safe mode, disabling things, that didn't work, sometimes it would even get in a bootloop, loop 3 times and then start.
I tried updating it, didn't work, tried flashing it with "G920FXXU3QOLD_G920FH3G3QOJ1_G920FXXU3QOJB_HOME", problems still persist. It's currently on 5.1.1, it wont update in settings, just starts downloading more than 1.2gb's of downloads then says "Software update has stopped responding".
Tried samsungs live chat, was awful, they didn't present any useful information.
I'm wondering if it's just 5.1.1 being awful, because when I boot to the system recovery menu thing where it has the blue screen with android logo, then has yellow exclamation mark, that doesn't reboot on it's own at all. Never reboots in download mode either. Phone is not rooted, knox hasn't been tripped or anything, so I'm left clueless. What do I do? Bought this phone, what, 4 days ago ish. Came here yesterday. My question is, if I flash it with idk, a 6.0.1 update in odin or something, will that fix the problems?
Hi,
It seems to me that you have a defective device, you can either try reflashing the stock firmware and then factory resetting, I believe that it really is a software issue, but as it's brand new (as you stated), you can return it to the store and get another one.
There are quite a few guides to flashing stock firmware back, hope you can do it .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
I have the latest firmware on my S7 (exynos) and once every while the system freezes and then the phone reboots.
I don't know what's wrong with it.
Funny thing is my S5 with cm13 is WAY more stable than the S7...
Gesendet von meinem SM-G930F mit Tapatalk
I have tried few times in my previous S7. I guess it is the compatibility of app
My SD S7 does that when using the iheartRadio app - quite annoying
I'm on my second s7, the first would freeze and reboot regularly. Some folks here said they believed it was a software issue. I ended up exchanging it for a new one and haven't have had a single freeze or reboot since.
I Have it occasionally hoping an update fixes it
I have had mine for more than a week and so far no issues at all
Sent from my SM-G930F using Tapatalk
having the same extremely annoying problem on my g930fd (DUAL sim) nougat
several times even had a black screen with nothing responding anymore so I had to wait to drain the battery completely so the device could reboot
resetted, hardresetted, re-flashed, re-rooted numerous times ... with no sollution
NOW (april 1st) just had a new update from samsung GF930FXXU1DQB7/G930FOLBDQB8/G930FXXU1DQB1
anybody else experience with this last update ?
I'm having the same problem and wrote about it on a Reddit page where a number of other people are having the problem with their S7's also: https://www.reddit.com/r/GalaxyS7/comments/5xx705/after_nougat_s7_keeps_getting_unresponsive/
No solution so far
I wrote:
"I also have this problem with S7 on Nougat which started about 3 weeks ago. It seems to be getting worse.
A couple of times where I've ignored it the S7 got so hot I actually thought about keeping it away from my person. I can always force restart it by Power+Volume. Mostly I can wake it up by pressing the power button and the screen will light up after about 10 seconds of waiting, but nothing responds.
Once I had it happen while using the device. When this happened, I noticed that swiping down the notification bar sped everything up temporarily. If the notification bar was hidden the current application would be laggy. If I swiped down the notification bar partially the application would render quickly as normal.
I've also found that Google Maps and Spotify are the two main apps when this happens, but a common link for me is that either one will be connected to bluetooth in the car or bluetooth headphones. I don't think it's ever frozen without bluetooth being connected, but that could just be coincidence.
A strange thing is that Spotify stays playing songs and responding remotely when the S7 has frozen. If I have Spotify open on my laptop controlling music on the S7, I can still skip forward/pause/play etc for ages, although the songs start skipping audio after 10mins or so before stopping completely. It's like the System UI is the problem on the S7, and the app itself is still responding?
I'm wondering about doing a full reset but I'm dreading the several hours of setting everything back up, without knowing if it will solve the problem.
I use Lightflow and I'm going to try uninstall that for a week and see if I still get the freezing, simply because it is the only app that is continuously running on my phone in the notification drawer."
Re above, I did a factory reset as advised by Samsung support and the problem has gone away.
no solution, not alone
meanwhile I have tried several things
factory reset, swipe, root, no root
I noticed that the problem starts to appear when more and more memory is being used ...
no update from anybody else ?
meanwhile I read on the net this problem is not exceptional anymore, more and more people having this problem ...
Just posting to say it's been two weeks in total since i did the factory reset and I haven't seen the problem happen once since. Thankfully.
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.