I have been getting some random reboots recently. I just recently flashed sbf and then OTA 1.8.3, rooted and installed CWM. It doesnt seem like a full reboot because it is faster but I don't know. I am using LP+ and I have widget locker if that means anything. Also I just ran gladenable and it happened twice after that very close together.
I was told your not actually experiencing a reboot, it is the graphical shell crashing. There was a thread about this months ago but no solution was given afaik. I would also like to know if anyone has any more info on this.?
Edit: The reason I believe it is not a reboot is because it happened to me while I was on a call and I could hear the other person just fine until the phone finished its "rebooting", then it ended my call.
Related
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
So I have run in to a bit of a snag, and though I doubt it is ROM specific, I thought I'd start by asking here to see if anyone else has run across this and might have a fix
I first noticed it when I was running ShiftAO5P 3.2, and though I didnt specifically think 3.2.1 would fix it, I tried that, and now the problem has come back.
The gist of the issue is that if I havent used my phone to talk to someone for some unspecified length of time, when I call someone, they cant hear me. I can hear them just fine, but they can't hear anything from my end. If I hang up, and call right back, then it all works fine. Also, it is fine if they call me - works right away without having to re-make the call.
Like I said, I did a complete reload to get to 3.2.1(full wipe, and even reformatted sd card), and since I suspected the tiamat kernel and the call recorder app I had been using under 3.2, I didnt reload those pieces and stuck with just the stock 3.2.1
Everything seemed OK for about the first week or so, but now it is doing the same thing again.
I am guessing it is some app, but I have no idea how to try to chase it down.
I have a logcat that I just dumped right after the problem happened, but dont really know what process to look for.
Any suggestions? TIA!!!
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
Hey everybody.
My girlfriend is having a terrible problem with her new Xperia Go. It's running the latest Stock Firmware and Kernel without Root and every time she gets an incoming call, the phone won't react for about 15 seconds and then a FC Popup appears. This happens as soon she tries to answer the call. We rebooted it and it worked as it should after a fresh boot, but as soon she uses apps like Whatsapp, Facebook and so on, the problem persists and it's kinda of frustrating. A smartphone should be able to handle those things and she's really disappointed. Thinks I've tried:
-Clear data and cache of Contacts and Phone.
-Hard Reboot
-Recently installed the latest update via OTA (I hoped the problem would get fixed, but unfortunately it's still there)
-Tried using the stock launcher since she uses Nova Launcher
If someone has got an idea of what's going on please reply this post. I don't know if I should root her phone or maybe install a custom ROM. Honestly I wouldn't like to do that since she's a Noob in Android and basically in Technology Stuff. But if that's the solution, I would do that. It's really frustrating.
Thanks! Hope anybody could help
EDIT: SOLVED!
I tried to limit the background processes in developer settings and set the maximum to 4 processes and it magically solved the problem!
Moderator please delete this thread
Sent from my GT-I9305 using xda premium
I have been rooting and installing custom roms for a while. I'm no expert, but now newb either. I recently rooted my S4. It's running on the stock verizon ME7 build.
The problem I have been having is that a few minutes after I reboot it all the sounds stop working. No music, notification or in call sounds. If I restart it goes away for a little while, but soon comes back. I tried factory defaulting it, which worked for a little while, but it recently started doing it again. The only thing I can think of is I installed avast Anti-theft with root access recently. Has anyone else had this problem & do you know of a solution? I can always try factory defaulting it again to see if that helps, but I would like to know if anyone else has any ideas.
Odined back
I tried everything I could thing of, then decided to Odin back to stock. Same problem started almost immediately . There are no system sounds and I can not hear anything when I call. Also it does not pick up sounds from my voice via voice commands & the person on the other end of my calls can not hear me. At this point I wonder if blocking is some how activated. Since Verizon was nice enough to prevent me from making changes to it I can't check.... Upwards on onward. I will keep this updated in-case someone else has this problem.
I have noticed that when I am in recovery, if I try to wipe the cache partition. I get a android on his back with a triangle exclamation point & then it reboots itself... Is this normal. I have never experienced this behavior before.
I installed the blocking mode MOD. It does not seem to be the problem. No sounds after using the phone for a few minutes. I guess its time to send it back. I really enjoyed the phone. But I seems like a received a bad one. Unless anyone has anythoughts.
When your sound stops have you tried to see if it is working with headphones or Bluetooth? If there is no sound using headphones or a Bluetooth device there's probably an issue with the phone itself. If you've done a stock Odin flash and its still doing it, I would have to guess the phone is bad. Send it back. The only problem you might have is if they check the flash count, you may end up paying for a new phone. I've never had to use Triangle Away to reset my flash counter, but I believe it needs to be flashed in a custom recovery (which you don't have).
Sent from my SCH-I545 using Tapatalk 4