Screen timeout not working - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Figured I'd cross post this as it seems to be an issue for a few people. ( http://forum.xda-developers.com/showthread.php?t=1951699 )
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!

I just started having the same issue. I was using Black Jelly's JB ROM for like 2 weeks without the problem then I flashed the LK3 modem and it started happening. I did a full wipe and flashed the ROM from this thread - http://forum.xda-developers.com/showthread.php?t=2034844 last night and I'm still having the problem. My touch key lights stay on all the time too along with the screen not timing out.

My S3 has been stock from day one. I also got mine a few days after it was released, starting to wonder if its a hardware issue?

I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.

I've noticed it on a replacement S3 I got when it wasn't an issue with the prior one. The new one (as with the old) is stock, updated to JB when I got it. GFs phone does the same.

geiswiz said:
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
Click to expand...
Click to collapse
This is interesting. I've been noticing this issue ever since I updated to 4.1.1 some weeks back, but had not considered any connection with missed calls. Among the dozens of reports I see online (with not a single one resolved), I found another thread that mentions it happening after missing a call (or receiving an SMS).
I completely wiped my phone and flashed a stock 4.1.1 rom two days ago and noticed this happening again while sitting at my desk today. I did miss a call earlier, so I think there is something to that suspicion; I rebooted the phone and sure enough the screen and touch keys timeout as they should. I just received a text and that didn't trigger the issue, but I'll have to wait til I get another call to know for sure, or until I get home and have the time to test it.

Ok, yep, it definitely is somehow triggered by missing a call, but it seems to only happen some time later after the last reboot. I had rebooted my phone yesterday, missed a call not too long after, and the keys and screen would shut off normally. But I just missed a call right now and sure enough it's acting up again...

Related

Speakerphone issue driving me nuts

I recently purchased a Dash used. I found this site and reflashed using the most recent kavana build. After about 2 days it switched to speakerphone always being on. I reflashed it that night again using the same ROM. Did it again later that night.
I reflashed back to the regular Tmobile ROM and realized it sucked and that I couldn't stand to use it.
So I tried the Ricky's rebuild and it worked fine all yesterday and about 5 minutes ago the same issue popped up.
It seems to be a software based problem because it's fine for a while after each reflash.. so I'd hate to pay my insurance for a new one when it might be a software issue.. anywhere in the registry I should look?
Does it goes to speaker imediately when you answer the phone? Holding down the answer button for 2 seconds swithes the phone to speaker mode.
it occurs on outgoing calls as well so unfortunately I have just removed that from the list of possibilities I believe
This is a weird problem that I have read about on multiple sites..
Seems the only answer I have ever seen was a phone replacement.
I am very curious as to what causes the problem.
Have you tried flashing the Vanilla rom?
haven't tried the vanilla rom yet...
when i went on lunch break i checked my voicemail and it's back to regular mode... this is annoying

Weird problems sending or receiving texts...

I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
rickyx32 said:
I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
Click to expand...
Click to collapse
I think you should try your SIM in other phone and check your problem might be issue with your Carrier.
Regarding the Auto Sending of SMS, I was facing that problem sometime ago and have been trying to find why it was so.
A factory reset will solve that problem.
I noticed that there were some GO Launcher themes that caused that problem to occur. (although I m yet
Also, u can use an antivirus. F-Secure recognized that virus and removed it.
I still dont know which app caused that problem though.
rickyx32 said:
I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
Click to expand...
Click to collapse

Lost My IMEI & Serial Number - How I Fixed It

I ran a couple of searches on Google( and in this forum) to try and find the original thread about this issue, however I didn't find it so I'm posting here in case anyone else can be saved by this fix.
First, some background:
I have been running CM10 Nightlies for almost a month now, also using the leaked Jelly Bean radio version T999UVLI2 with absolutely no problems. Everything was working great, data, ROM, etc. (Prior to that I was on Stock ICS, rooted. Had not run any custom ROMs whatsoever).
I noticed after flashing the latest CM10 Nightly (Oct. 14) that my phone had started acting a little weird - nothing drastic mind you, just a few glitches here and there. The weird thing was, all of the previous nightlies I had flashed pretty much worked flawlessly for me, minus a volume issue when in-call which was a known bug. I had done a clean flash as I always do, so I attributed the glitches to a possible bug or two in the latest Nightly and figured it would probably be resolved in the next release. No big deal.
Yesterday afternoon, after reading a thread that is tracking all available T-Mobile radios by region (to see what works best in your area) I saw someone who posted that the T999UVLI3 radio gave them the best speeds, and they happened to live in the same exact city as I do here in Southern California. So I decided to flash the new radio using Team Sonic's Modem flasher, which I used in the past to flash the LI2 radio that I was currently on. I flashed the T999UVLI3 radio and found that it did indeed provide better data speeds than the LI2 radio, so I was pretty happy about that. Used my phone all day/all night with no problems, everything was great.
I always leave my phone plugged in at night so that I have a fresh charge in the morning - this morning I turned off my phone while it was still plugged in as I leave it off during the drive to work to save a little battery before I start my day. Typically I unplug it first and then turn it off, but not always. So nothing really out of the ordinary there.
I get to work and turn on my phone, and all of the sudden I notice that I have no bars - at all. It doesn't say "T-Mobile" at the bottom of my lock screen. I figured it was just taking it's time booting up, which would be very weird as it never does that, but I waited. And waited. Nothing. Now I'm starting to get a little worried.
Went into settings and checked "About Phone" and it said my Baseband version was "unknown". Oh crap. IMEI, unknown. Serial number, unknown. GREAAAAT
For the life of my I couldn't imagine how this could happen when I didn't even do anything from last night to this morning. I started going over everything I had done recently to my phone.. the power off while plugged in, the nightly update to the Oct 14 build, then it hit me.. the new radio version. Maybe that was it
In a desperate attempt I booted into recovery and ran Team Sonic's Modem Flasher and flashed back to T999UVLI2. Rebooted the phone and... BAM! Back to normal. W...T...F..?
If anyone loses their IMEI, before going through the entire injection fix process, try reflashing a radio. Worked for me!
Any theories on why this happened? Many people have been using the T999UVLI3 radio, I believe without any issues.. but I could be wrong. Anyone flashed that radio and lost their IMEI?

[Q] process com.android.phone not responding..

im currenty using liteROM 0.9.0 first 3 days work fine, but after i found this problem.. can anyone help me..
+1.
My phone.android repeatedly shut down in Gingerbread. Only fix i could find was upgrading to ICS.
when arldft
Hmmm.... that is weird, i´m also using LiteRom 0.9, never had that issue, first time i flashed the custom rom i did see that message a couple of times, but no big deal just reeboot and no probs. after that though i decided to install the rom from scratch, never had an issue with it since. only problem ive had is the toggle for gps sattelites and mobile connection giving me some issues, nothing a reeboot cant resolve.
my advice would be to backup all your info & apps and start from scratch. or boot to CWM and fox permissions.
hope i helped
I had similar issues with GB. I was using the latest Osimood rom. Upon receiving a call, my phone screen would go blank (the way it normally does when switching to a call) but then it would freeze. The ringtone would not ring and after a few seconds of this, the phone would go back to the last app and the network signals would be gone. After a few more seconds, the network signals would be back. The same thing would happen if I received another call. The only fix was to reboot the phone.
The annoying part was that there would be NO way for me to tell who was calling me since I would never see their name and no entry would be made in the phone log. I didn't have any success with treating that problem. While it didn't happen very often, the few times it did would be very annoying since I'd often find out several hours later that I had missed an important call.
I've just switched to Pacman rom today in the hopes that this was a rom issue and will be gone now. Let's see.

Question Every 3-4 days I must reboot

Ok, so like the title says, every 3-4 days I must reboot my phone.
When I play games, the game icon will show up in the lower right corner, I have everything for the game stuff turned off. I can click on the icon and it will ask me to turn on. I back out and it's gone for a few minutes. Mostly until I swipe back, then it will reappear. I can reboot the phone and it will work fine again for a another 3-4 days.
There are other instances that force me to reboot as well, one happened last night. I was scrolling through a local news app and the touch stopped working. I could not scroll up or down, and swiping back did not work. I had to lock the phone and just as the screen went dark, the phone scrolled in the directions I did and it backed out. This only happened when I hit the lock screen.
Is there a fix for this? Has anyone else experienced this?
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Mine does not reboot or shutdown on it own, not once... I have to reboot every so often to keep it functional.
@thepersona My phone doesn't auto reboot either. I'd say do a backup and run https://flash.android.com/welcome to fully Factory Reset the phone and see if that helps (Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Like the OP I do have to reboot my phone about every 3-4 days, but I don't attribute that just to Google Android, coders have become lax on how tight they keep their code, and I say that because in Windows 10 and Windows 11 you have to reboot every few days as well or see an increase in weird issues.
card13 said:
@thepersona Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Click to expand...
Click to collapse
Just to clarify this, most carriers prevented the December update from releasing as Google has asked them to prevent it from going through, primarily due to an issue with calls dropping.
I always manually update my phone, however, I noticed the call dropping bug one day for about an hour straight.
But aside from this meaningless info, I agree with what you said: Attempt a factory reset and see what happens. I turn my phone off every night and charge it, so I don't notice any issues similar to what OP has mentioned.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
wilpang said:
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
Click to expand...
Click to collapse
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
thepersona said:
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
Click to expand...
Click to collapse
Yeah I was lucky and it was only once a week which was tolerable!
Something is definitely not right, hopefully is not a dodgy app but that would be preferable than something unfixable.
Ok guys you are missing my point and question. I DO NOT have the random reboots most have, but I have other issues that no one seem to have. Example, I listen to Spotify over night, I fall asleep to music, but 2 days ago it would randomly pause. At first I thought it was do not disturb that I just turned on, on my watch. It was not. Then I thought I may have been hitting my watch, I took it off and it still paused. I rebooted my phone and it's been fine since, no random pauses. Another example is, I play a game but I have the game dashboard turned off, but there times where the icon will pop up in the lower right. When I go into the settings for it, it shows it's off. When I go back to the game the icon is gone for a few minutes then it reappears. The only way for me to get it to stop showing for a few days is to reboot my phone.
I know you shouldn't have to reboot your phone every few days, and by few I mean sometimes it's 3-4 times a week. That tells me something is wrong.
Are you on the November or December update?
If November, I would try the December one.
Rooted or not rooted?
Either way, I would try a factory refresh and don't restore your apps from backup. Manually install only your most critical apps and see if you have the problem. Even better would be not install any additional apps at all and see if the problem happens. If it doesn't happen, install another small group of your most important apps and test again for long enough. Etc.
If you try thre update and/or factory reset, you could try restoring your cloud backup as normal and see if you have any problems still, but if you do, be prepared to factory reset and try like I mentioned in the above paragraph.
Until you can narrow down if the phone has this problem on the December update before you even change settings and add your favorite apps, then you won't know if it's the phone itself (possibly hardware problem), an app you have installed, a problem particular to a combination of factors including if you're on the November update, or what.
Good luck! Please let us know what happens.
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
darbylonia said:
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
Click to expand...
Click to collapse
Awesome!!! This is the kind of news I like to hear..... Just waiting for att to send it through. I checked this morning as my work Verizon Samsung phone got an update.

Categories

Resources