Develop Bugs

Rogers SGH-I747M: Screen turns on by itself after pressing power button

I've done a search for this problem, but haven't found a solution to this yet.
I'm running the stock rom w/root. It didn't do this when I first got it, but it's doing it more and more as time goes by. It's starting to drive me nuts, especially at night since my phone is my alarm as well. Doesn't seem to matter if the phone is charging or not.
The screen will flicker on and off a few times in a row, then stay dark for awhile then resume the on/off behavior out of nowhere. I'm not receiving texts or emails when this happens.
I have checked my account syncs, and nothing is set to automatic. Never had this behavior on my SGII LTE running ICS.

blanchardc said:
I've done a search for this problem, but haven't found a solution to this yet.
I'm running the stock rom w/root. It didn't do this when I first got it, but it's doing it more and more as time goes by. It's starting to drive me nuts, especially at night since my phone is my alarm as well. Doesn't seem to matter if the phone is charging or not.
The screen will flicker on and off a few times in a row, then stay dark for awhile then resume the on/off behavior out of nowhere. I'm not receiving texts or emails when this happens.
I have checked my account syncs, and nothing is set to automatic. Never had this behavior on my SGII LTE running ICS.
Click to expand...
Click to collapse
Your title made me chuckle.
I did experience some random screen wake ups while on stock that sort of just resolved themselves. Try rebooting, and then try to uninstall any new apps you've installed to see if one is causing this.

TheFiveDots said:
Your title made me chuckle.
I did experience some random screen wake ups while on stock that sort of just resolved themselves. Try rebooting, and then try to uninstall any new apps you've installed to see if one is causing this.
Click to expand...
Click to collapse
Thanks for the suggestion. Rebooting was obvious as I've done that many times. I did go through a bunch of apps and removed them, then reinstalled one by one. So far the problem has gone away, I've yet to identify which app might have caused it though.

Fingerprint sensor not working occasionally

I've been recently getting some instances where I would lock the phone and the fingerprint sensor won't respond to my finger.
This really started when I changed my lock to pattern swiping. Anyone have the same issue? I rebooted and changed it back to pin lock and it seems to be working all the time again, but I don't know what caused it in the first place.
Thoughts?

How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint

jbdan said:
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
Click to expand...
Click to collapse
It's not that it doesn't recognize my fingerprints, but it doesn't recognize fingerprints in general. So when I put my finger on it, it doesn't do the double buzz, it's just non responsive.

this happened to me yesterday several times. And i received phone yesterday... . I have two prints. Left and right index fingers. It didnt fail, just was as my finger wasnt in the reader
MDB08L

experienced the same thing this morning. phone was plugged charging and finger print would not detect, had to manually hit the power button then it worked. i find there are a lot of issues when the phone is charging though, screen sometimes becomes very unresponsive while charging. i think there was a similar thread about that as well.

Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.

ajmalott said:
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
Click to expand...
Click to collapse
Any luck? I did a system wipe after unlocking, and flashed new factory images but still happening.

No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.

ajmalott said:
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
Click to expand...
Click to collapse
I was able to find a bit more about this issue. When it happened again, I pressed the power button and quickly checked the fingerprint icon at the bottom of the lockscreen and it turned red and said "fingerprint hardware not available" for a split second before turning white again. I searched that error message and got this thread https://www.reddit.com/r/nexus5x/comments/3pm3lv/fingerprint_hardware_not_available/
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.

jadesocket said:
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
Click to expand...
Click to collapse
I'm not much of a tinkerer, but I'll give this a shot. If it clears it up then okay, but if it happens again I'll probably RMA too. Not willing to put up with such inconsistencies on a brand new phone with such a highly touted feature.
Unrelated, this is actually already my second Nexus 5X. The first one I received would not take a charge, and I didn't have another USB Type-C cable to test, so they sent me an entirely new package. If wiping cache doesn't do it, I'm really not sure if I should bother with a third Nexus 5X. Kind of disheartening. I really enjoy the device otherwise.

So far so good for me, Let me know how it goes for you!

jadesocket said:
So far so good for me, Let me know how it goes for you!
Click to expand...
Click to collapse
Still happening today.

ajmalott said:
Still happening today.
Click to expand...
Click to collapse
That's a bummer. It actually happened again today for me too.

jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that

ajmalott said:
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
I had hope Looks like RMA imminent for me. I put that glass screen protector on so well...

ajmalott said:
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
Lots of apps updated in the past week. The problem hasn't resurfaced for a whole 48 hours now. Hoping I can put this behind me

jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.

It happened to me too, stock phone, no third apps installed. I will keep an eye on this.
off-topic: the discoloration of the back of the phone it's very bad!

ajmalott said:
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
Click to expand...
Click to collapse
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.

jadesocket said:
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
Click to expand...
Click to collapse
Did a factory reset, and the problem came back almost immediately. Google tech support wanted me to reinstall OS entirely, but I don't have the right cable (type C to type A) to hook up to computer, so they just gave RMA. Got the new one on Friday, so far so good. But then, with the last phone, the issue didn't appear until after a week or two. Fingers pressed. Tech support really seemed to take my case as a rarity, and they were unable to recreate it with their own device. Here's hoping it's just limited to a few devices.
P.S. Off topic, but Google support wouldn't give me anything for the Black Friday deal. I asked multiple times in multiple ways. Oh well.

Touch input temporarially stops working until after phone goes to sleep

Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?

superbelt said:
Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?
Click to expand...
Click to collapse
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?

TheMadScientist420 said:
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?
Click to expand...
Click to collapse
Hey, thanks for the reply. So I did what you said. I ended up doing a factory restore of my device.
I have had this phone since about a month after it was released two years ago. I rooted way back then, did not install any rom over it yet... and then a few weeks later my kid went and clicked through a software update one day and removed my root, so I just left it go.
Anyway, I did the full factory reset, and started setting my phone up again, and a couple times the problem resurfaced. No apps from the store yet installed, the phone just stopped responding to any touch inputs. I wait for it to go to sleep, and then wake it up to use it again.
This sucks, I guess this is forcing me to upgrade when the G5 releases. But any ideas still? I dread being stuck with the phone being buggy like this for another two months or so. It's not app related, it doesn't SEEM to be hardware based, since everything works perfect up until it just locks up. The problem happens with different batteries I use. There doesn't appear to be any physical damage to the phone at all.

Verizon S8+ Bugs and Issues

Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16

Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.

Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?

*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.

brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.

I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.

Phone constantly locks and sometimes unlocks

Hi, i have a big issue with this phone, i bought it like 2 weeks ago.
Since the 2nd day of use, i started to experience this issue, sometimes and usually when im not using wifi but mobile data, the screen goes to lockscreen, if i try to unlock it will lock again and that happens a couple of times, maybe 2, 3, 4, 5 times, sometimes i have to press lock button and try again. its really annoying, because somtimes it doesnt happen in a lot of time and then after 1 hour in the street and while im using it it locks and unlocks like crazy.
i did a soft factory reset but didnt work, i even tried in safe mode and it still happens.
yesteday i noticed that it even wakes up for no reason, that happened while i was driving in a highway, it suddenly wakes up like if i touched it, i disabled every feature about auto waking (like 2 touch, motion detection) but it still happens.
the only thing that makes it stop is if i switch airplane mode, so i guess maybe its something related to network (not wifi or location or mobile data because i disabled those and still happened), but when it is in airplane mode it will work fine, obv thats not a real solution.
i tried disabling and uninstalling a lot of apps but i cant figure out whats making this, im pretty sure its software problem, something related to network but i dont know.
do you have any ideas? even if i take it to tech service it will be hard to show them because sometimes it doesnt happen in hours.

anybody has an idea what could be causing my phone to lock for no reason while using it on the street?

Your phone gone kaboom

I have same problem, the problem is caused by the weak signals,which means that your phone connectivity is constantly changing, for example on a highway or in a basement. Solutions I have none, just waiting samsung to make a fix

Yes, thats exactly the problem. When signal is weak the phone locks or unlocks. I asked for a new phone at the store and they gave me a new one.
Look
htt ps://r2.community.samsung.com/t5/Galaxy-A/Samsung-a50-locks-and-unlocks-automatically/td-p/1701267
Are you having this issue?
htt ps://photos.app.goo.gl/5veszyLb4UGJZRV9A
(Delete spaces in link between htt and ps)
Btw i don't think this is a software problem because if it was a software problem all phones would having this issue. I think it's a problem with some hardware failing in some phones. IMEI of failed phone is 356711101439414 check if yours is similar