Well, something very odd just happened to my samsung focus (at&t) when I rebooted it. After the samsung screen shows, a pure red screen shows up for about 2 seconds and then it goes black. when I push the power button (or hold it) it simply goes back to the red screen again! Naturally, I thought to battery pull which simply put it back onto the samsung screen only to then go back to the red screen again.
I then thought 'maybe this is some sort of glitched state that it is in (it does seem to be stable in this state of redness, the capacitive buttons seem to give haptic feedback when pressed and the power button turns the screen off and on) so I decided to battery pull again and then connect it to my pc to see if it would detect that the phone was in this special "mode". after the battery pull, the phone booted back as normal??? It had about 89% power according to the battery percentage app when I rebooted??
it is fine now, but WTF was that anyway??
EDIT: ok, now it gets weirder, I got it to go into this state and quickly connected my usb cable to the computer and... zune pops up and it goes to that screen with the phone wanting to sync, but the phone being grayed out?? when I dragged a picture to my device, IT STARTED TO SYNC WITH DEVICE! It didn't even get an error and, after a successful reboot to the actual phone, THE PICTURE WAS ON MY DEVICE??? oh, and btw, it boots insainly fast when it is in redscreen mode...
i am now seriously confused beyond all hope
happened to my omnia 7 yesterday.
Just as well since i was going to flash the new rom anyways (and i did.. hasnt happened yet)
I think...it happened when i took my sim out.. i put it in and dont think it happened.
Might have to do with samsung. Other than Dell, Samsung has proven to be the weakest OEM in terms of hardware/software/firmware reliability.
I had this after I tried the 16Bit gradient hack. Setting the values back to 16 solve the red screen problem.
Wow... Ur right! Thanks for the fix =D
Sent from my mailbox
it is related to the 16 bit banding reg hack. It has been discussed/mentioned in that thread several times...
Has happened to me 3 or 4 times in the last month, ever since I changed the values to fix the banding on my Samsung Focus.
Just yank the battery and restart, hasn't been a continuous problem for me, and definitely a small trade-off to get rid of banding, IMO.
Same over here
Now that you mention it. I have the same RSOD problem with my Omnia 7 after the 32 colour bit hack. In my case it will happen after I have switch the phone off for the night and switch it back on in the morning. It's fine when the phone is switched off and on again.
Related
I did not have that problem for a long time, it only recently happened. In the morning the device 'froze' for the first time and did not react to any input without the screen turning on.
I took out the battery to restart and everything seemed fine. But later on it happened while I was using the device, certain pixels moved out of place (like a green pixel distortion) and the device froze. Screen turned off soon after. Taking out the battery was the only option.
Now, this is either battery or some other hardware flaw. After restart the battery had been hit with a 20% drop.
Might the device act up by some charging problems? When I am charging the device, I can feel the electric 'buzz' from the docking connectors (the three golden circles).
Also, when it is not charging, I cannot detect it myself, but if I take a strand of hair, the end of it 'sticks' lightly to the screen (and to the docking connector) if I put it close there. I fear like there's some manufacturing flaw there that broke loose.
The device has not dropped once, nor has had any other physical damage happen to it.
Has anyone else had the same symptoms happen?
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
I found this issue (or one very much like it) at code.google.com here:
http://code.google.com/p/android/issues/detail?id=22748
jss42 said:
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
Click to expand...
Click to collapse
Thank you. I thought it was different from Sleep of Death since the initial symptoms were different from weeks ago when I read that thread, but now reading it this seems correct. This thread can be merged or removed, I'll post in the other thread. Thanks again!
I've had that too, couple days ago using Facebook everything just froze. The keyboard went all buggy and green pixels everywhere. The back of the phone started to warm up phone wouldn't respond in any way.
Tried everything I could try, only option was to pull the battery, once that happened phone wouldn't turn back on!
I gave the phone 5 mins to rest before putting battery back in then it turned on.
My heart was pounding I thought my phone had died!
Thankfully it hasn't happened since
Sent from my Galaxy Nexus using xda premium
It's happened to me multiple times. Less since I turned off the EQ in the Music app, but it's still happening.
Once it happened with the device just sitting there with Tapatalk displaying a list of posts. I wasn't even interacting with it.
I think it's a OS or driver problem and will be fixed in an OTA.
happened to me once, although when it happened I was already pretty low on battery, about 20% left, maybe less.
I was in a settings menu for some app, I can't remember which. But I had the keyboard up, and the green pixels hit, froze, unfroze, green pixels again, froze, and then shut off.
it would not turn on via the power button, so I quickly pulled the batt and put it back after 30 secs or so and powered it up. Batt did not drop any lower than it was, and it worked fine. Plugged it in, recharged overnight, and has been fine ever since.
I'm running 4.0.1 and I don't have anything but apps made by Google on the phone at the moment.
never rooted or unlocked bootloader.
Hopefully 4.0.2 or 4.0.3 fixes this
i realize now that there's no support for 720P AC3 .MKV files on the Nexus yet, but every time i tried the phone would lock up and i'd have to do a battery pull. other then that, i notice if i have Google Music running and attempt to do something else(multi-task) the phone will also lock up.. but then it will reboot on it's own. i also get lag regularly switching views/menus or going from portait/landscape. additionally, the browser(regardless of which one i use) will occasionally just freeze & close by itself.. usually if i try to do a secure login on a site. i will also sometimes get FC's(have seen them for launcher pro & android keyboard)
So I recently installed CM 10.1.2 on my S3, and everything worked perfectly for a few days. Yesterday though, my phone started acting strangely (lag when turning screen off, registering phantom input, etc) and began rebooting every few minutes. At some point, it ran out of battery - and now I can no longer boot past the CM loading wheel screen.
I can't boot to recovery, and I don't think my phone is taking charge (from my computer or a wall outlet), and the farthest I can get is the loading wheel - sometimes it only gets as far as displaying the Samsung logo, or the Galaxy S3 screen with the android dude at the bottom.
I'm still covered under warranty, and would love to take it to the store for a replacement (I've had battery issues prior to this), but the fact that it can get to the CM loading wheel means that they might figure out that I've rooted and whatnot. But I can't get to recovery to flash a stock image, so...what can I do?
vortexface said:
So I recently installed CM 10.1.2 on my S3, and everything worked perfectly for a few days. Yesterday though, my phone started acting strangely (lag when turning screen off, registering phantom input, etc) and began rebooting every few minutes. At some point, it ran out of battery - and now I can no longer boot past the CM loading wheel screen.
I can't boot to recovery, and I don't think my phone is taking charge (from my computer or a wall outlet), and the farthest I can get is the loading wheel - sometimes it only gets as far as displaying the Samsung logo, or the Galaxy S3 screen with the android dude at the bottom.
I'm still covered under warranty, and would love to take it to the store for a replacement (I've had battery issues prior to this), but the fact that it can get to the CM loading wheel means that they might figure out that I've rooted and whatnot. But I can't get to recovery to flash a stock image, so...what can I do?
Click to expand...
Click to collapse
Your best shot is to either borrow someone's S3 battery or buy a battery pack. Use that to restore your phone back to stock (unroot) and then you can go to the store for replacement.
alltechinside said:
Your best shot is to either borrow someone's S3 battery or buy a battery pack. Use that to restore your phone back to stock (unroot) and then you can go to the store for replacement.
Click to expand...
Click to collapse
So turns out battery isn't the issue, I used a wall charger to get it to full charge. I can get it to the download mode confirmation screen, and can press volume up to confirm - but my phone reboots soon after that.
Recovery isn't really possible either, I can see the blue text in the upper right but my phone reboots after that as well.
My phone will often show an empty battery icon with a little refresh icon in the middle; does this indicate that it doesn't see the battery as charged (even though it is)?
vortexface said:
So turns out battery isn't the issue, I used a wall charger to get it to full charge. I can get it to the download mode confirmation screen, and can press volume up to confirm - but my phone reboots soon after that.
Recovery isn't really possible either, I can see the blue text in the upper right but my phone reboots after that as well.
My phone will often show an empty battery icon with a little refresh icon in the middle; does this indicate that it doesn't see the battery as charged (even though it is)?
Click to expand...
Click to collapse
My phone started having the same problem yesterday and I tried my friends battery but it still doesn't work.
mtmodi said:
My phone started having the same problem yesterday and I tried my friends battery but it still doesn't work.
Click to expand...
Click to collapse
Yeah I've been doing some research into the issue...
I've noticed that my phone automatically boots when I put the battery in, and that it'll do a quick vibrate when plugged in to a power source (outlet or computer) but won't turn on.
Apparently the phone isn't supposed to boot automatically when the battery is put in, and this could be the source of the random reboots - I think if I can get the rebooting under control, I'll be able to get into download mode and fix it all. But I'm not sure how to do that. Maybe the power button has gone bad, as it also doesn't usually respond when I try to use it to turn on.
If there is a problem with the power button, does anyone have any ideas on how to fix it?
vortexface said:
Yeah I've been doing some research into the issue...
I've noticed that my phone automatically boots when I put the battery in, and that it'll do a quick vibrate when plugged in to a power source (outlet or computer) but won't turn on.
Apparently the phone isn't supposed to boot automatically when the battery is put in, and this could be the source of the random reboots - I think if I can get the rebooting under control, I'll be able to get into download mode and fix it all. But I'm not sure how to do that. Maybe the power button has gone bad, as it also doesn't usually respond when I try to use it to turn on.
If there is a problem with the power button, does anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
Mine does the exact same thing where I have to pull the battery and when I put it back in it automatically starts up and when I go to download or recovery it turns off before I can do anything
Sounds like power button issue.
I was having the same issues (random reboots, boot loop, powering on when battery put in, reboots in download mode and recovery)
This is not an easy fix. I ended up pulling the power button out and just setting my screen to time out after 15 seconds. Sucks but it works now.
If I ever need to turn off or hard reboot, I stick a pin in the power button hole and push down on the button.
Really turning me off on purchasing future Samsung phones
Sent from my SAMSUNG-SGH-I747 using xda premium
The power button is a common issue for these phones.
Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!
Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!
Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?
Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it
The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!
I have an idol 4s and last night before bed, around 11:30pm, it decided it was a good time to windows update. I looked over and I saw the reboot and the gear icon, so although I knew I had about 50% battery I plugged it in and continued to read my book while waiting for it to finish.... except after the progress bar got to the end my phone never turned back on.
Despite several attempts at holding the power button to get it to come on, or plugging and unpluggin the power , all I get is the White Alcatel Idol4S boot screen, followed by the pink TMobile Logo.
Then, coincidentally as I'm writing this I plug it in again (coincidentally into my pc at work if that makes any difference) and it finally gets passed the windows logo and it shows the message at the top something about finishing up or whatever.
But as I recall, this happened on the last update, whenever that was too. Any idea what the heck is going on? Has this happened to anyone else?
RobbieRobski said:
I have an idol 4s and last night before bed, around 11:30pm, it decided it was a good time to windows update. I looked over and I saw the reboot and the gear icon, so although I knew I had about 50% battery I plugged it in and continued to read my book while waiting for it to finish.... except after the progress bar got to the end my phone never turned back on.
Despite several attempts at holding the power button to get it to come on, or plugging and unpluggin the power , all I get is the White Alcatel Idol4S boot screen, followed by the pink TMobile Logo.
Then, coincidentally as I'm writing this I plug it in again (coincidentally into my pc at work if that makes any difference) and it finally gets passed the windows logo and it shows the message at the top something about finishing up or whatever.
But as I recall, this happened on the last update, whenever that was too. Any idea what the heck is going on? Has this happened to anyone else?
Click to expand...
Click to collapse
I cannot tell much from what you are describing, but my best advice is to let it do what it needs to do and finish.
Just plug it in and leave it alone. Possibly you interrupted the update/upgrade process, but who knows? Unless it hangs there for hours and hours I try to never touch my windows phones to force a soft reset unless I absolutely have to.
Yeah, so it happened again last night. Just as I was going to bed, I saw the black and white screen with the gears rotating, so I just plugged the phone into power and went to bed... but making sure to turn on my other device so I'd atleast have an alarm to wake up to. 8 hours later nothing. If I plug in power or unplug power, I'll see the tmobile splash screen and then nothing else.
[edit] Not sure how relevant this is. But when I plug it in to power. The white led near the camera turns on as usual. But after a while it turns off, which leads me to believe that the device is literally turned off because as I recall, genreally speaking, it is not possible to plug in a windows phone device and not have it charge. What makes it interesting though is that even though the led is turned off, I still see the device in "This PC" when it is connected. I just can't browse the device storage of course. So as soon as I disconnect, it is not visible on my windows 10 pc until I plug it in again. I finally long pressed the power button, and unlike earlier when I would just remove and reconnect usb power, this time, the White Alcatel/windows 10 branding showed up, THEN the pink tmobile logo. And finally it booted up.
Mine's been doing the same since the start of the year... I have to keep rebooting till it finally "works" again... takes about 45-60mins of rebooting.
Not sure if there's anyone left who browses this forum, but I guess it never hurts to try. If there's a better place to post this nowadays, please let me know!
I have been using my Samsung Galaxy S II Epic 4G Touch for about 9 years now. I never messed around with rooting or installing any custom stuff.
I don't remember what version of Android it was using; I'd assume it was whatever the latest official version was.
Last night, I was reading an ebook on my phone; nothing out of the ordinary. Phone seemed fine. Battery was at about 75% or so.
And then, for no discernible reason, the phone froze and became unresponsive. I tried rebooting, and when I did, a screen came up asking for a "PIN or password to access the encrypted device memory" or something like that.
I had never seen anything like that screen before.
I tried restarting again, but this time, the phone just straight up would not power on. The device's status/power light was a steady blue, not blinking.
If I held down the power button for about 5 seconds, the light would briefly turn off and then go right back to the steady blue. The phone's screen remained blank.
I tried using a different battery, but it made no difference. The phone simply wouldn't boot at all and would not give any indication that it was accepting a charge. I tried holding down the volume buttons and home button in addition to the power button, but it made no difference. Couldn't even get the Samsung splash screen.
I tried connecting it to the USB port of my laptop and desktop PC. Neither device could detect the phone.
So, I'm left wondering, did my phone just suddenly "brick" itself or experience a sudden hardware failure? Is there anything I can do to salvage my phone?
Thanks.