Hi,
I'm sorry if it's a trivial question that has been asked million times before -- referring as an exact duplicate is also appreciated.
I have a Galaxy S5 device and I'm experiencing troubles with it with the following symptoms/scenario:
* The device works fine in general.
* The device screen gets totally black if the device turns the screen off after a certain period of time that's configured in Settings.
** The device seems to work though, and to react on awaking with the Power button. A: I assume it works behind the black screen because I can see the bottom buttons highlighted for a while. B: However, I'm not sure what happens if making screenshots the device using adb -- I haven't checked it yet.
** The device cannot reboot within a certain amount of time: up to 30 minutes (boot loop). When the period ends up, the device can boot again.
* If the device gets asleep after pressing the Power button, I can awake it and it works fine.
So, the general rule is to make sure that the device does not gets asleep itself and does not get into "coma".
The workarounds I could find so far:
* Install an app that merely does not let the device sleep so the screen is constantly turned on.
* Increase the sleep timeout up a reasonable amount of time (say, 10 minutes) and not forget to press the Power button within this period.
The question is: why does it happen and how do I resolve this issue? I mean: why does screen not get turned on when I try to awake it after it gets asleep itself?
Android 6, the stock firmware, no root.
Thank you in advance!
Are you using a 3rd app in order to gain in battery or performances?
fgth90 said:
Are you using a 3rd app in order to gain in battery or performances?
Click to expand...
Click to collapse
Thank you for the feedback. No, never: the scenario I described in the question can happen even after re-flashing a stock firmware (Android 5 or 6 --- the version does not really matter).
hurricane flow said:
Thank you for the feedback. No, never: the scenario I described in the question can happen even after re-flashing a stock firmware (Android 5 or 6 --- the version does not really matter).
Click to expand...
Click to collapse
Did you wipe everything before flashing your new firmware?
fgth90 said:
Did you wipe everything before flashing your new firmware?
Click to expand...
Click to collapse
Yes, absolutely.
hurricane flow said:
Yes, absolutely.
Click to expand...
Click to collapse
Hum...
When you screen off with power button, then screen on with power button after short time, it works, right?
---------- Post added at 09:20 AM ---------- Previous post was at 09:16 AM ----------
hurricane flow said:
Yes, absolutely.
Click to expand...
Click to collapse
What's your phone model and what's your firmware?
fgth90 said:
Hum...
When you screen off with power button, then screen on with power button after short time, it works, right?
Click to expand...
Click to collapse
Yes, it works when I turn off the screen with power button myself. I can turn on it later even after a long period of time.
But when the screen is off by Android itself (I mean after an inactivity period), then, when I try to turn it on, the device seems to work and even react the screen taps (I guess since I haven't check it with `adb shell screencap` yet). The only difference is that the screen is off in such case, so I can't see anything.
hurricane flow said:
Yes, it works when I turn off the screen with power button myself. I can turn on it later even after a long period of time.
But when the screen is off by Android itself (I mean after an inactivity period), then, when I try to turn it on, the device seems to work and even react the screen taps (I guess since I haven't check it with `adb shell screencap` yet). The only difference is that the screen is off in such case, so I can't see anything.
Click to expand...
Click to collapse
What's your phone model and what's your firmware?
Maybe you should try to flash a different firmware from sammobile.
Don't forget to wipe everything, including system of course.
Maybe cleaning your sdcard as well (but I don't know why it should interfere).
Is your problem recent, I mean only existing after your last firmware flash?
fgth90 said:
What's your phone model and what's your firmware?
Click to expand...
Click to collapse
Not sure if I'm giving all necessary info, but I hope it's what necessary:
Software version: G900PVPS3CQA2
Hardware version: G900P.04
Device name: Galaxy S5
Model number: SM-G900P
Android version: 6.0.1
Baseabnd version: G900PVPS3CQA2
Kernel version: 3.4.0-10090296 [email protected] #1 Tue Jan 10 14:50:06 KST 2017
Build number: MMB29M.G900PVPS3CQA2
fgth90 said:
Maybe you should try to flash a different firmware from sammobile.
Don't forget to wipe everything, including system of course.
Click to expand...
Click to collapse
I tried to flash another firmwares a few times, but if the device was fine with them, then the describe issue persisted, so it made me think that I was using wrong firmwares. It's hard to say if I have a wrong one now, but it works except of that issue...
fgth90 said:
Is your problem recent, I mean only existing after your last firmware flash?
Click to expand...
Click to collapse
No, it's not recent per se: I had a well-working device with stock firmware for very long period, and suddenly got a reboot and forever bootloop. Flashing a new firmware was the only way I could resurrect it more or less. But now the only issue I see is that the device falls into "coma" if I don't press the Power button. Well, it makes me think that something prevents the screen from turning on, and I believe it must be a software issue. ... Or not -- I can't tell, this is where my knowledge is running out.
hurricane flow said:
Not sure if I'm giving all necessary info, but I hope it's what necessary:
Software version: G900PVPS3CQA2
Hardware version: G900P.04
Device name: Galaxy S5
Model number: SM-G900P
Android version: 6.0.1
Baseabnd version: G900PVPS3CQA2
Kernel version: 3.4.0-10090296 [email protected] #1 Tue Jan 10 14:50:06 KST 2017
Build number: MMB29M.G900PVPS3CQA2
Click to expand...
Click to collapse
Had you got this update http://www.galaxys5update.com/sprint-galaxy-s5-update-g900pvps3cqa2-january-security-patch/
they talk about stability improvments?
fgth90 said:
Had you got this update http://www.galaxys5update.com/sprint-galaxy-s5-update-g900pvps3cqa2-january-security-patch/
they talk about stability improvments?
Click to expand...
Click to collapse
If I understood you correctly, then it's installed on the device according to the information is posted above. The same happened before I applied the update too, so probably this update doesn't change anything for that.
hurricane flow said:
If I understood you correctly, then it's installed on the device according to the information is posted above. The same happened before I applied the update too, so probably this update doesn't change anything for that.
Click to expand...
Click to collapse
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Good luck
fgth90 said:
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Click to expand...
Click to collapse
Great! Thank you very much! I never had an idea of another way of making the screen off except of "let Android do it" or "let me do it myself" -- a 3rd-party app is to the rescue! That's a brilliant suggestion to work around the issue since it made my eyes got open for totally another solutions. And let Android to be the last one in that screen off queue! Thank you!!
hurricane flow said:
Great! Thank you very much! I never had an idea of another way of making the screen off except of "let Android do it" or "let me do it myself" -- a 3rd-party app is to the rescue! That's a brilliant suggestion to work around the issue since it made my eyes got open for totally another solutions. And let Android to be the last one in that screen off queue! Thank you!!
Click to expand...
Click to collapse
Nice to notice it worked.
But remember it's half done.
Your problem is still present.
Good luck matey
Franck
fgth90 said:
Nice to notice it worked.
But remember it's half done.
Your problem is still present.
Click to expand...
Click to collapse
Absolutely, but I'm still impressed by the alternative you suggested. Thanks again.
It can be a Hardware problem, If updated to Latest firmware in correct region, And not worked, Is The Hardware causing this.
fgth90 said:
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Good luck
Click to expand...
Click to collapse
can i have that pm too? i have the same problem: https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-doesnt-wake-home-key-weird-t3556724
Related
Hi,
A new ROM for the TMOUS operator:
RUU_Schubert_TMOUS_1.54.531.02_Radio_5.51.09.29a_22.32.50.10U_by_ansar
see also thread: Windows Phone 7 Branded ROMs for Schubert
Till next version enjoy!!!
Regards, ansar.
ansar.ath.gr said:
Hi,
A new ROM for the TMOUS operator:
RUU_Schubert_TMOUS_1.54.531.02_Radio_5.51.09.29a_22.32.50.10U_by_ansar
see also thread: Windows Phone 7 Branded ROMs for Schubert
Till next version enjoy!!!
Regards, ansar.
Click to expand...
Click to collapse
hey ansar, nothing about unlocking tmobile version??
Okay.. this is driving me nuts.
I have the TMOUS HD7 synced with Zune and the ROMUpdateUtility is not able to connect to the phone.
I've tried this with Windows 7 and XP computers... both with admin and non-admin accounts.
Any idea what I'm missing?
Turn of the phone.
Then Hold power button and volume down.
You will enter the bootloader.
Wait till it says on the bottom USB and
Then launch the update app
Thank you for the tip! For whatever reason, all I saw was "Serial" the first time I went into the bootloader. It came up "USB" this time so I have it flashed now... thanks again
Dear ansar, pls kindly check ur download link, i can download ur rom from this link. If u can, upload ur rom to mediafire. Tks
Just an FYI, this new radio greatly improves battery life, but for me it added a major bug. When talking to someone the screen actually times out and if its been like two minutes and you pull the phone away to hang up, the proximity sensor doesn't register because the phone is "sleeping"... Flashing back to original tmous fixes, its a shame because i was getting like 5 hrs extra life on battery.
microhaxo said:
Just an FYI, this new radio greatly improves battery life, but for me it added a major bug. When talking to someone the screen actually times out and if its been like two minutes and you pull the phone away to hang up, the proximity sensor doesn't register because the phone is "sleeping"... Flashing back to original tmous fixes, its a shame because i was getting like 5 hrs extra life on battery.
Click to expand...
Click to collapse
I've actually been having that issue with the older version (and this is my 2nd HD7 as well with the same issue). The proximity/light sensors turn the phone on/off during a call properly, but after a minute or two of talking, the phone no longer turns on when I pull it away from my face. I don't know if this is by design or a bug.
Also: Is this just a radio update? Or is there more to it than this? Software? Updated WP7?
prjkthack said:
I've actually been having that issue with the older version (and this is my 2nd HD7 as well with the same issue). The proximity/light sensors turn the phone on/off during a call properly, but after a minute or two of talking, the phone no longer turns on when I pull it away from my face. I don't know if this is by design or a bug.
Also: Is this just a radio update? Or is there more to it than this? Software? Updated WP7?
Click to expand...
Click to collapse
Hi
It is present to all phones, at least for those i tested of.
A work around for me was the change of screen time-out setting in lock & wallpaper.
This version improves both OEM and Radio firmware.
Regards, ansar.
So is this then the latest ROM for the T-Mobile US HD7?
Yes, it's the newest. Also it improves battery life greatly. After flashing back to original and back to this one i've noticed that the proximity lock bug during phone call doesn't happen any more, seems random for when it happens on new flashes.
ansar.ath.gr said:
Hi
It is present to all phones, at least for those i tested of.
A work around for me was the change of screen time-out setting in lock & wallpaper.
This version improves both OEM and Radio firmware.
Regards, ansar.
Click to expand...
Click to collapse
I was able to install this ROM to my phone and it's been very good so far actually, thank you.
T-MOBILE
Hi, ansar.
Can i unlocked my T-MOBILE?
Thanks!!!!
I have to say, ever since using this newer ROM with the updated radios, my phone has lasted longer battery wise, and reception has even improved greatly. I get better data speeds, and there is even a slight improvement in overall performance of Windows Phone 7. It's all been pretty nice.
Thanks ansar.
Dumb question: But does flashing this erase all my stuff?
art0605 said:
Dumb question: But does flashing this erase all my stuff?
Click to expand...
Click to collapse
Yes, this is essentially a hard reset. Everything gets wiped and you start all over again.
prjkthack said:
Yes, this is essentially a hard reset. Everything gets wiped and you start all over again.
Click to expand...
Click to collapse
Ok, thanks for the heads up. Even though that's not I wanted to hear!
Final dumb question: If I purchased and installed an app prior to the hard reset, will I have to buy the app again after the process?
art0605 said:
Ok, thanks for the heads up. Even though that's not I wanted to hear!
Final dumb question: If I purchased and installed an app prior to the hard reset, will I have to buy the app again after the process?
Click to expand...
Click to collapse
I didn't have to. With the free apps I installed it actually notified me that I'd already purchased the app and asked if I would simply like to download it again.
art0605 said:
Ok, thanks for the heads up. Even though that's not I wanted to hear!
Final dumb question: If I purchased and installed an app prior to the hard reset, will I have to buy the app again after the process?
Click to expand...
Click to collapse
Your purchases and app downloads are tied to the primary Windows Live ID on your phone (the first Windows Live ID that you set up on your phone). So as long as you sign in with that same ID, you can redownload all your applications to your phone without charge. If you plug in your phone to your computer and sync it right after you hard reset, Zune will even restore all your apps for it so you don't have to go through the Marketplace manually.
Hello, as successful as I have been with this ROM I must note that it is a little bit buggy.
Today my phone rebooted for the first time since I've owned it for example. Also, I think it affects the 3G/2G selection process in a negative way. Normally I use ##3282# to set my phone 3G only but it seems to ignore the setting at times...
hi guys..
Got my new phone at the launching day.. everything runs perfect..
But yesterday and today i encounter a small issue..
please note that i have fingerprint scanner lock on my phone..
when i pressed the home button just to wake the screen, the screen didn't respond.. only the side buttons lid..
the screen remained black after the second press too.. then i pressed the power button once and the screen woke..
the thing was that when i pressed the power button after this incident the home screen game me a third option, apart from emergency calls (left) and alternative password (right), Unlock via Google placed to the middle..
this happened also today twice..
Any suggestions on this ?? did anyone encounter this ??
please note that i didn't use any other locking method except fingerprint scanner and the home button responds fine in any other case.. Thanx..
I randomly get unresponsive touches when trying to open an app in the app drawer folders. Haven't had the home button issue though
-Sent from Tapatalk
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
BigAl1044 said:
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
eyecon82 said:
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
Click to expand...
Click to collapse
same here I also switch this off and still same problem and format wipe data and cashe don't help
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
polish_pat said:
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
Click to expand...
Click to collapse
I've randomly noticed I can't click on an app to open it if it is in a folder I created in the app drawer
-Sent from Tapatalk
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
polish_pat said:
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
It gets pushed out in waves, so it may be a few days to a few weeks till you get it. Kind of a bummer
-Sent from Tapatalk
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
z89x23 said:
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
Click to expand...
Click to collapse
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
rciochin said:
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
Click to expand...
Click to collapse
I can confirm that i have similar issues too.
Sometimes (2-3 a day) the screen is not waking up from sleep state when i press the home or the power button.
The solution is that i need to press the power button to sleep the device and then press again or press the home button to wake up.
Not a big deal but i hope that this issue is not hardware related and a firmware fix will solve it.
Apart from this, it's really a great smartphone.
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
rciochin said:
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
Click to expand...
Click to collapse
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
thank you all for your replies.. its good to know that its not my device..
Hopefully with the new update they will fix it..
by the way yesterday i missed a call, do to that problem.. the phone was ringing but the screen was sleeping..
So i decided to chance my ROM, from EUR-Greece to NEE-Norther Countries.. Also did a hard factory reset after that.. Volume up + Power + Home.. Also deleted the cache partition..
I used odin.. No problems found.. and Kies recognizes the phone..
So i will check how this goes and get back to you..
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Hi
My build number is KOT49H.G900FXXU1ANCE
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
rciochin said:
Hi
My build number is KOT49H.G900FXXU1ANCE
Click to expand...
Click to collapse
i have the same.. on the NEE ROM
I dont think that was different on my EUR ROM..
z89x23 said:
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
Click to expand...
Click to collapse
I have the XEH G900FXXU1ANCE...
I was just thinking that the G900FXXU1ANCF is maybe a little bit newer, as the build number is higher (1186806) So that's a different rom for sure.
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
gee2012 said:
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Click to expand...
Click to collapse
I have tried factory resetting my phone but it doesnt help. Thanks anyways
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
I have added mot.proximity.delay=0 but i couldnt find ro.lge.proximity.delay=25. Is there any other way to fix this problem. I have to pull my battery out couple of times a day and its starting to get to me.
.
Click to expand...
Click to collapse
and now my mulitasking buttons are not working. any idea why?
snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I have the same issue... do you still get this issue? For me, sometimes, the screen does not wake up only the capacitive keys... I have to press the power button again to turn it off and then press power again to turn it on.
me too
Hi,
I'm having the same problem.
It was intermittent for a short while and a battery pull would fix it, now it's permanent.
I get capacitive buttons, I can boot into recovery or download.
I can hear touches on the screen and the annoying at$t boot sound is back since I used Odin to reflash to stock.
I think I have to take this phone to a service center and see if they will exchange it.
I'm worried that there may be traces of towelroot but from the thread that provides stock firmware and instructions for Odin it would seem that I'm good.
Has anyone had any luck with this issue or have any other tips to try?
I'm bummed because I just applied a glass protector and it looks like I'll have to get another.
Not to mention having to drive to the center.
Thanks.
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
For the record:
The at$t service center reflashed my phone and the screen works again.
IDK why flashing stock with odin did not work for me.
I can see from the post above mine that the problem might come back, I'll insist on a replacement if it does.
still getting the issue but for me I just need to press power 3 times for it to wake up; no need to remove battery
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Levus said:
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
Click to expand...
Click to collapse
how can i find out what mobo I have?
---------- Post added at 06:51 PM ---------- Previous post was at 06:05 PM ----------
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
Click to expand...
Click to collapse
just rooted going to try this one thx
You can use the samsung phone info app from the market...
I haven't solved this issue as well... Please,did anyone of u guys solve this problem? If u did,please,tell me what to do... My screen stays black,only capacitive buttons lights,and I must press power button 5,6 times to wake up the screen. It's really annoying... :/
No solutions yet ???? I have this problem too...
walidhiphop said:
No solutions yet ???? I have this problem too...
Click to expand...
Click to collapse
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
qubbus said:
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
Click to expand...
Click to collapse
I'm having issue even using Kitkat 4.4.2
ZaKaTRoN said:
I'm having issue even using Kitkat 4.4.2
Click to expand...
Click to collapse
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
knightrider558 said:
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
Click to expand...
Click to collapse
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
ZaKaTRoN said:
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
Click to expand...
Click to collapse
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
knightrider558 said:
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
Click to expand...
Click to collapse
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
ZaKaTRoN said:
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
Click to expand...
Click to collapse
hahah... but this solution worked for me
Well, dont't know why, but the double tap to "wake" the screen has gone bye bye...and I don't have a clue to solve that. Can someone give me a sugestion?
Thanks
Which Rom are you using?
I'm using the original version of the International Version YOG4PAS7DF
Kokujin33 said:
I'm using the original version of the International Version YOG4PAS7DF
Click to expand...
Click to collapse
Seeing the same issue on the latest OTA (YOG4PAS7DF, COS12, not rooted, 100% stock. A reboot fixes the issue, but comes back after some time. Guess we just have to live with it until the next update...
Same for me. A reboot is needed to have it back. I really hope COS 13 will be available soon.
Planet X said:
Same for me. A reboot is needed to have it back. I really hope COS 13 will be available soon.
Click to expand...
Click to collapse
Living with this issue for always.. I dont reebot phone, just go settings -> Screen -> Disable T2W and just block phone with power button. Unlock, go settings again and enable T2W, block again and then double tap on screen and phones wake. Always works. I have this issue almost every time someone calls me. I hope this will be fix on COS 13.
Regards from Chile.
Sorry people, forgot to post something. Well, after the reboot, the touch to wake came back and since then hasn't gone away yet, but your posts tell me it's a matter of (some) time . Oh well, I can live with that I guess. Thanks for the feedback people
My phone is having an issue where randomly it'll just stop responding. I'll go to turn on the screen or unlock with my fingerprint, nothing happens. Hold the power button down for 1+ minute, nothing happens. Plug into my computer, no recognition on my PC that anything was plugged in. Plug into the charger, no battery light. Is this thing dying?
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
agentfazexx said:
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
Click to expand...
Click to collapse
Hi... Already seen that scenario a few times with no apparent reason. Last week someone posted hee with the same issue. As you did, holding power button seemed to have solved the problem...
5.1 said:
Hi... Already seen that scenario a few times with no apparent reason. Last week someone posted hee with the same issue. As you did, holding power button seemed to have solved the problem...
Click to expand...
Click to collapse
Right but holding the power button down doesn't really do anything until I let it sit, at least with today's and yesterday's occurrences.
agentfazexx said:
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
Click to expand...
Click to collapse
You know there's really only one way to find out....go back to the stock rom for a while. You won't really be losing much, if anything. Nothing wrong with the stock ROM, rooted and kernel- it's rock solid. Between Google's backup/restore and TiBu, you can be back right where you were in an hour or so. You should have your answer within a couple of days. You may also want to install Accubattery to check your battery's capacity vs design.
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
jhs39 said:
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
Click to expand...
Click to collapse
Nope. ElementalX kernel and none of that other nonsense. Just sounds like a hardware issue since I'm holding the power button down for several minutes and nothing happens, then eventually the phone hard-reboots.
agentfazexx said:
Right but holding the power button down doesn't really do anything until I let it sit, at least with today's and yesterday's occurrences.
Click to expand...
Click to collapse
Supposing your profile is up to date, I'm running the same setup as you: PN Feb 2017 + EX Kernel 4.05... I've never had such problem...
As @v12xke advised, try loading a stock firmware and see if it happens again...
jhs39 said:
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
Click to expand...
Click to collapse
Does Franco or other battery saving apps cause device to lock up this way?
5.1 said:
Supposing your profile is up to date, I'm running the same setup as you: PN Feb 2017 + EX Kernel 4.05... I've never had such problem...
As @v12xke advised, try loading a stock firmware and see if it happens again...
Does Franco or other battery saving apps cause device to lock up this way?
Click to expand...
Click to collapse
They can.. Naptime can turn off your fingerprint sensor and make it hard to wake up phone. Greenify img system apps can have unintended consequences. Franco's kernel effects the responsiveness and performance of the phone because it is geared towards battery savings.
agentfazexx said:
Nope. ElementalX kernel and none of that other nonsense. Just sounds like a hardware issue since I'm holding the power button down for several minutes and nothing happens, then eventually the phone hard-reboots.
Click to expand...
Click to collapse
No (new) apps installed/updated lately?
Time to backup... Hoping you'll find an answer to your issue!
jhs39 said:
They can.. Naptime can turn off your fingerprint sensor and make it hard to wake up phone. Greenify img system apps can have unintended consequences. Franco's kernel effects the responsiveness and performance of the phone because it is geared towards battery savings.
Click to expand...
Click to collapse
I see... Thanks.
5.1 said:
No (new) apps installed/updated lately?
Time to backup... Hoping you'll find an answer to your issue!
I see... Thanks.
Click to expand...
Click to collapse
Nope, nothing new.
the same to you. ElementalX,what can i do?
zhxhwyzh14 said:
the same to you. ElementalX,what can i do?
Click to expand...
Click to collapse
What?
agentfazexx said:
What?
Click to expand...
Click to collapse
I think he meant "I have the same problem as you and I'm using EX Kernel". At least that's my translation.
zhxhwyzh14 said:
the same to you. ElementalX,what can i do?
Click to expand...
Click to collapse
EX kernel has nothing to do with your problem. First step is to hold only the power button down for two solid minutes to see if your phone reboots. This situation happens sometimes, but usually the phone reboots while your finger is on the power button. Often it starts and the phone behaves normally again. (Except in OP's case)
I'm having a similar problem after updating to 7.1.2 on the beta program.
Phone wouldn't reboot after installing 7.1.2, it took me a good few hours of pressing power + volume down to get into the stock bootloader/recovery? and started the phone that way. I then opted out of the beta program and reverted back to stock 7.1.1. While at work the phone died and after charging it would not start by pressing the power key, I had to do the whole 3-4 hr process of Power+volume down to get it to boot again. It's up and running now but I fear if it dies I will be in the same boat again with the 3-4 process.
It seems to me that the new update somehow messed with a proper shut down of the phone? It's to bad I really liked this phone up until this problem started.
Chewmasey said:
It seems to me that the new update somehow messed with a proper shut down of the phone?
It's to bad I really liked this phone up until this problem started.
Click to expand...
Click to collapse
Sorry to hear that. For the majority of others the 7.1.2 beta is working just fine, and in fact fixed a long standing BT car connection bug that was rolled out to the 5X and Pixels earlier. Maybe beta testing is not for you, but I haven't been able to connect my phone with my car since last October so I was determined to try it. I used a TWRP flashable version of the image. You may want to wait for the official Google OTA image whenever they get around to posting it... or just wait until it is out of beta.