Related
Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased
strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart
Keefo said:
strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart
Click to expand...
Click to collapse
Dammit, I thought I said what phone I was using...I'm on the HTC Arrive. It hasn't done it since I've posted..I highly doubt it'll happen all the time (probably won't ever happen again)..just wanted to mention it.
This happened to my arrive right as it was done updating on the screen that says the update is done...the close button wouldn't work, but I remember reading this thread so I waited it out and it started to work after like 2 min
I am having the exact problem on my HD7, only seems to occur if I am listening to music. The lock screen appears, but I cannot swipe.
Mine doesn't always come back and I have to remove the battery.
I have the same issue every once in a while. I'm not on Mango though, I'm running NoDo on a HTC Surround.
It's happened about 5 times in the last six months.
I've had the same issue since before NoDo. The quickest fix is to try turning the screen off and then on again, sometimes it takes a few attempts but it normally works.
haven't noticed on dvp or anything I wonder if its a htc thing...
I haven't noticed it, though I did get the red screen associated with changing the reg entries to get 32 bit color one.
Interesting side not, when I was updating to Mango, on one of the reboots I got the red screen and thought I was screwed, but the update process continued and on the next reboot it was normal again...
ms79723 said:
Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased
Click to expand...
Click to collapse
nope havnt come across this yet on my Samsung Focus. The only issue seems to be the increased boot up time(phone stays on d Samsung logo screenfor a long time) but I am quite sure its due to Samsungs crappy bootloader and besides I hardly have to reboot WP7 ever anyway
Hey, has anyone else noticed that weird icon where your signal and data icon should be?
Idk if its the new icon for no signal or what...but when I unlocked my phone, I saw an icon that looked like the copy and paste icon where my signal and data icon should be.
I must say I'm noticing this on third party apps a lot, I don't know whether it's because they are downloading data from the Internet or what but it's happening quite a bit at the moment. LG Optimus 7 btw.
Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.
i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!
I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.
Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.
I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.
Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App
Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.
I went to root+stock kernel and the problem is gone and LOS is gone to
txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
It may be hardware related but it could also be an app that you are installing on each rom. Try a new rom and don't install anything for a few hours and see if it still happens.
Sent from my SGH-T989 using xda premium
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
SOD? whats that?
sleep of death
i think its related to the wi-fi being on while charging , just fully charged it and left the phone on the cord for an hour after charging and it never went off. ran it down to 90% and turned wi-fi back on and hooked it up to see if it does it again
that has happened to me with other phones, like Nexus S, I9000, Moto XT720
so it's definitely not hardware related AFAIK
the way i narrowed it down to has always been a ROM problem
after I flash clean up, or load a more stable ROM the Sleep Of Death goes away.
i had a lot of that with the recent "stable" CM 7.1 for Nexus S
flashed to a newer nightly unstable and it fixed the "stable" problem LOL
well i just got my new phone in yesterday and so far no random reboots or SOD's ,phone seems a little faster than my previous got 3700 quads stock unrooted and over 15megs download and almost 3 upload , i think i got a better device this time and im pretty sure it was a new one and not refurbished, im gonna run it stock for a couple days just to see if any problems re-occur, i was having them on my first phone before i rooted ,thats why i decided to root and install custom roms
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Are you using automatic backlight?
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Sounds to me like it is really a hardware issue... while it's understandable that you don't want to wait for a new phone to arrive, it is better than ending up with a dead backlight...
It really was a hardware issue, took another one back after a month and it works great.
Thanks for your help guys
hi folks
my note 2 doesn't wake up sometimes. it still shows notification LEDs during its sleep, but cannot wake up unless I take the battery out and put it back in. I experienced this on Friday and Sunday, but not on Saturday in between..
I tried the battery on my wife's Note 2, and no problem there...
I tried a different custom ROM, but experienced it there as well.
Is this a hardware issue, or could going back to stock rom solve this? Or is there another way?
Help please!
same issues on mine, the alarms didn't go off this morning because it wouldn't wake up. tried linage and nuclear roms. I just came on to find an answer!
It takes 10 seconds to unlock at the best of times (black screen until then)
Hey, thanks for your answer, but what do you mean
turnah said:
It takes 10 seconds to unlock at the best of times (black screen until then)
Click to expand...
Click to collapse
- did you manage to unlock from the black screen WITHOUT taking out the battery?
Do I just have to wait for it to wake up? But calls are not received and alarms do not sound while it is sleeping.... right?
omermaras said:
Hey, thanks for your answer, but what do you mean - did you manage to unlock from the black screen WITHOUT taking out the battery?
Do I just have to wait for it to wake up? But calls are not received and alarms do not sound while it is sleeping.... right?
Click to expand...
Click to collapse
I heard a call come in but the screen didn't wake up to answer the other day, 8/10 times it eventually unlocks after frantic clicking of the home and on buttons but the only answer is to take the battery out if that doesn't work. Its at least once or. twice a day I end up removing the battery.
Would be great if someone knew of a rom to get around this. initially they work great but get slower after a few hours.