[INFO] Random Reboots aren't True Reboots - Atrix 4G General

I think many of you are misinterpreting the "Random Reboots" you're experiencing. Unless the screen goes completely blank, then it is not a true reboot, if all it does is flash back to boot animation it is just the graphical shell crashing.

Good point, I did notice that it booted up significantly faster than a full reboot when it happened to me before and that it only dropped to the boot animation.

That makes a lot of sense actually
Sent from my MB860 using XDA App

Thanks for the suggestion - that does make some sense. Is there a way to verify this, though? In my case, my DInc will be in a stand on my desk - screen off, so I can't actually see what happens - when I'll hear it vibrate, and I'll notice the white HTC screen followed by the boot animation. It's only done this since I rooted, and it has done it with at least three of the ROMs I've used.

CaptBananaPants said:
Thanks for the suggestion - that does make some sense. Is there a way to verify this, though? In my case, my DInc will be in a stand on my desk - screen off, so I can't actually see what happens - when I'll hear it vibrate, and I'll notice the white HTC screen followed by the boot animation. It's only done this since I rooted, and it has done it with at least three of the ROMs I've used.
Click to expand...
Click to collapse
Yeah, same deal. I have learned to do "real" reboots, especially after rooting. What I mean is actually turning it off, counting to like 20 (maybe pull the battery), and then turn it back on.
Recently I had an issue with the capacitive buttons not lighting up at all so I tried a "quick" reboot (the kind that requires root) and it did nothing, then I tried a "real" reboot and they work fine now.

Agreed. I can confirm the Atrix is not doing a full reboot. I had a call on speaker phone then all of a sudden my screen showed the boot animation and I could hear the other person talking for an additional 15-20 sec while the phone finished "booting". Our conversation was not ended until the home screen came back up, at this point my bars/service dropped to no service. Also, I have not rooted or modified the Atrix, its stock.. w/LauncherPro+.

WiredPirate said:
Agreed. I can confirm the Atrix is not doing a full reboot. I had a call on speaker phone then all of a sudden my screen showed the boot animation and I could hear the other person talking for an additional 15-20 sec while the phone finished "booting". Our conversation was not ended until the home screen came back up, at this point my bars/service dropped to no service. Also, I have not rooted or modified the Atrix, its stock.. w/LauncherPro+.
Click to expand...
Click to collapse
I had those "reboots" twice now. Once while using Maps and once while sitting on my desk not being used. I was also using LauncherPro+. I wonder if that might have been part of it. I stopped using LP+ and haven't had a "reboot" yet (knock on wood)

Related

cyanogen 5.0.5.3 touch screen

is it normal that my touchscreen goes nuts sometimes? I find that sometimes (usually at night or first thing in the morning) my touchscreen on my n1 is inaccurate. I'll touch in the middle of the screen and it will click on something on the bottom of the screen. if I reboot my phone, the phone works great again.
yes its normal, its been posted here that even stock rom will get that problem now and then. Although mine has been random, not at a certain time.
Google is working on a software fix for it, and cyanogen 5053 (for my experience) has cut that problem to a minimum. I think ive experienced that problem 2 times since flashing. So a span of 3 weeks it happend twice. So i say its been pretty good.
And you dont need to reboot, just turn off the screen and turn it back on. Last i had a problem, i did that and it worked.
So as soon google fixes it im sure this board will be flooded with threads about it. And the devs are fast enough to implement it to their ROMS!
Are you holding it differently at those times? You mentioned at night or in the morning. Are you still in bed? I find I sometimes grip the phone is a way that my hand touches the edges of the screen. That throws off the touches and I've noticed it jumping down to a different icon at times. Just make sure your hand doesn't wrap around to the front of the screen.
My nexus one touchscreen will go nuts at times too. Locking the phone and unlocking does fix it though. I'm also 100% positive it has nothing to do with erroneous input from the way I'm holding it.
ya I was making sure that I wasn't holding it weird. hopefully Google makes a fix : )
p.s. thanks for the tip on turning off the screen rather than rebooting the device.
mine does this too but it seems that if I just put it to sleep and wipe it off it's back to normal
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Mine too does this w/ cyanogen 5053. sometimes it's so bad that i cannot even unlock the phone. I never noticed it this bad before on stock... but then again i only used stock for about two weeks before i rooted it.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I'm on a non modded phone and I get it every once in a while. Hit the power button and all is well.

Vibrant Freezes and WIFI freezes?

So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Samsung Vibrant Freeze
drgnclwk said:
So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Click to expand...
Click to collapse
has any solution been found for this ?? i have similar freezing issues with my vibrant .. i found one possible culprit listed on another site .. there is a way to disable the TeleNavGPS app (as you cannot uninstall) .. it is supposed that this interferes with the phone to the point of complete failure
Are you running stock 2.2 from Kies? I had exactly the same problems.
Sent from my SGH-T959 using XDA Premium App
You could try backing up and doing an ODIN flash to KA6. I've had similar lockups with some builds in the past but they are fairly infrequent. Currently running stock KB1 rooted with KA6 radio and it has been smooth for a long while now.
I've tried some of the 2.2.1 Roms, but I absolutely need wifi calling so I stick with stock.
Sent from my SGH-T959 using XDA Premium App
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
FirefighterZ said:
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
Click to expand...
Click to collapse
Have you tried another ROM? I thought my phone was broken with stock 2.2. Haven't had issues with Bionix.
Sent from my SGH-T959 using XDA Premium App
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
FirefighterZ said:
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
Click to expand...
Click to collapse
Yeah, know what you mean. It is silly that stock is just broken. Hopefully the OTA will be better than the Kies release. (Are they doing an OTA?)
Maybe they'll swap for a Nexus S.
Sent from my SGH-T959 using XDA Premium App
im rooted on android 2.2 but stock rom stock modem stock everything just root. i have had the same wif issue as the op. i just go to settings>wireless settings> wifsettings and turn on wifi that way. if you notice it will say error. 90% of the time this works and you will not have to reboot. i switch from wifi to 3g a lot. i have not figured the cause just yet but this is a work around for now.
as far as deleting the bloatware i rooted and deleted all that crap like sims, and other apps that i do not/will not ever use. there is a thread on which ones are safe to delete. be careful about deleting apps that are used by google such as google talk.
Unreal, Samsung. I wanted to sell my Vibrant, but can't get anywhere near what it's worth because of these stupid issues.
Sent from my SGH-T959 using XDA Premium App
I'm having the same problems!!!
I am now on the 3rd replacement (that's the 4th T-Mobile's Samsung Vibrant 3G!!!) and still having problems.
My phone will just be sitting on my desk at work and I'll hear it buzz a couple times. I know that buzz. It's something "Force Closing" in the background. I will pick my phone up and it will be unresponsive. It will light up the 4 buttons on the bottom of the device, but nothing else. Normally, it will then immediately start rebooting. It will go through the usual start-up screens. It will then show the status bar at the top; battery life, alarm clock, signal, 3G/WiFi, Media Scanning progress. However, the rest of the screen will be black. It will then vibrate once, then 2 more times and do it all over. It repeats this at least once for around an hour EVERY DAY!!! Other times, it will not restart on it's own and I will have to hold down the power button to manually do so.
I have also gone through ALL the troubleshooting I can imagine. All logs, history, texts, cache... EVERYTHING... has been cleared.
Please forgive me for asking, but it appears that I am to possibly root my phone for a resolution... is this true?
Also, has anyone heard of this "3 Returns Within 90 Days" policy with T-Mobile? I could easily do this with this phone. Has anyone had any luck getting them to do that?

Phone went by itself to a ... recovery screen?

WI don't know what happened (really, I don't) but last night something really strange happeend to the phone.
I wasn't even using the phone or running any apps (heck, even background data was turned off) and the next thing I know, my girlfriend points out something weird on the screen: my phone had gone into a recovery-like screen. It had a picture of a phone and a red triangle with a exclamation point. Red, I tell you. After more than a year tinkering with Android, I had never seen a red one sign. Also, what the heck? It just reboot into that screen by itself, it seems.
Wish I could explain where it came from, give you a log or show you a picture but none of these I can provide. All I can tell you is the image of a phone with a red exclamation point.
Happed to my girlfriend phone don't know why she was at school when it happened....
Sent from my T-Mobile G2 using XDA App
This happened to me this morning. My phone was just sitting there doing nothing. I came out of the shower and was like ? Its a little concerning. I have a trouble ticket open with tmobile about my reception issues so next time I talk to them I'll bring it up.
phazedplasma said:
This happened to me this morning. My phone was just sitting there doing nothing. I came out of the shower and was like ? Its a little concerning. I have a trouble ticket open with tmobile about my reception issues so next time I talk to them I'll bring it up.
Click to expand...
Click to collapse
Let us know what's up, see if they know what it's about. I have no idea what it was, it was surprising.
I'll see if I can exchange mine for another one this week, I think.
Umm details? How long did it stay on this screen? What did it do after? Reboot, power off, ect. Did you do anything after? I can't offer any answers but anyone that can needs this info and ill be watching mine for the same. You never know this could be an exploit path.
It went all by itself to this screen. It was set on a table, doing nothing. Only telephony was turned on (meaning only phone calls or text could come in); data, BT, GPS, and WiFi were turned off.
It stayed on this screen until I decided to reboot it. It seems to have been on this screen for a while. I did a hard reboot (Power + volume down + trackpad).
rmcsc said:
It went all by itself to this screen. It was set on a table, doing nothing. Only telephony was turned on (meaning only phone calls or text could come in); data, BT, GPS, and WiFi were turned off.
It stayed on this screen until I decided to reboot it. It seems to have been on this screen for a while. I did a hard reboot (Power + volume down + trackpad).
Click to expand...
Click to collapse
Same here, it happened just as i plugged it in last night and I freaked out since I haven't seen that screen before (rooted my G1 two winters ago) but I thought I did something until I read your post. No updates though.
is it possible that maybe that update pushed out to yalls phones without needing approval and it was in recov for a second from it??? just throwing that out there, otherwise im clueless.
User needs to give the phone the approval for update to start. No way in hell this was an update.
rmcsc said:
User needs to give the phone the approval for update to start. No way in hell this was an update.
Click to expand...
Click to collapse
Too lazy to dig it up now, but I recall that there is a provision to make a FOTA update forced install, even possibly w/o user intervention. However I don't think this has ever actually been utilized before, and neither would I expect the update background to use a red exclamation mark.
Logcat of one of these "red exclamation mark" devices would be useful.

Problems booting

Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
HoochieCoo said:
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
Click to expand...
Click to collapse
Are you rooted or completely stock?
Sent from my ADR6300 using XDA App
Rooted. I just tried restoring a backup from 3 days ago and had the same problem. So I restored back to the latest. When it finally does boot, it seems to run great.
I have a backup from further back, just not sure it will make a difference. Might give that so shot too.
I really think it is booting all the way, and just doesn't stop displaying the boot animation.
The reason I think that is because at some point the power button makes the screen go on and off, and there is haptic feedback in the same places where my lock screen tabs are.
At any rate, and this sounds unbelievable, but I pulled the sd card out and it booted normally. I put the card back in, and now it seems to boot normally. Can't explain it.

Verizon i815 random reboots

Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.
I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium
Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.
Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.
Good luck! hopefully the new one is error free.
I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr
Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.
Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.
Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...
Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.
My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.
gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.
I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium

Categories

Resources