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
Related
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.
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
..
yeahman45 said:
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
Click to expand...
Click to collapse
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
vndnguyen said:
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
Click to expand...
Click to collapse
It's a hardware defect. Mine was like this too since 11th april. After changing the motherboard to the newer, 1.1100 version, the problem is competeley gone away. It's waking up every time correctly.
We had a topic about this earlier...
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
yeahman45 said:
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
Click to expand...
Click to collapse
I'm totally sure because i had this bug from the beginning. I was trying all firmware updates, factory reset, etc. It's not related to the fingerprint sensor or any app installed or not.
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
yeahman45 said:
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
Click to expand...
Click to collapse
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Levus said:
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Click to expand...
Click to collapse
anyone else can confirm it's a hardware issue? does it get worse with time? I still get it (but seems worse sometimes, where i need to press power button several times to wake it up) and i have tried a lot of suggestions
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
yeahman45 said:
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
Click to expand...
Click to collapse
anyone can report if it also happens with a non touchwiz rom?? I can't flash one as my phone is still under warranty
no one can't reply? so this issue is not common after all?
guys i am going to void my warranty to flash cm12... does it solve this issue??
adit said:
Re-activation lock only works when knox is 0x0 but that too can be bypassed by installing custom rom so...
Click to expand...
Click to collapse
I can not install custom in my own phone ...0x1...after install xtrolite 2.2....f...
Have someone solved the problem by flashing a custom kernel? Still getting the issue on latest lollipop rom
youtu.be/wbqOni008hc
Any solutions? I want to know is it software or hardware problem?
edit: Specs
Marshmallow 6.0.1 G900HXXSACQAA/G900HOJP1CPL1/G900HXXU1CPCA
Smart Launcher Pro 3.16.06PX
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Seems to be a standard problem. I have it too.
Internet forums are full of this problem.
Buy another phone than Samsung.
fgth90 said:
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Click to expand...
Click to collapse
I've seeb it alot actually. I mean the wake up problem. But noone seems to fix it yet. If anyone did please tell me
Has anyone test this with older Android 5?
The "Weird" Screen in Low Brightness is AMOLED Burn-in due to intensive use, My S5 Have this problem too.
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Thank you for all the answers guys.
Valmerost said:
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Click to expand...
Click to collapse
Just changed:
Force GPU rendering : on
Disable hardware overlays: on
edit1:it's better than before. I will feedback later. Also gonna try that camera trick
edit2: It's same again. Tried Home2 Shortcut the get the camera trick. It also didn't work because i want my phone to be locked and it doesn't work on locked status
Any other suggestions guys?
what ROM are you guys using? Have you tried a different one?
youdoofus said:
what ROM are you guys using? Have you tried a different one?
Click to expand...
Click to collapse
It's the stock ROM. No, I'm planning to try a new ROM today.
raiwulf said:
It's the stock ROM. No, I'm planning to try a new ROM today.
Click to expand...
Click to collapse
that would be a good place to start
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
raiwulf said:
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
Click to expand...
Click to collapse
if thats the case, then it might be a hardware issue
this is weird af, tons of people have this issue, no solutions yet
raiwulf said:
this is weird af, tons of people have this issue, no solutions yet
Click to expand...
Click to collapse
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
derAndroidler said:
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
Click to expand...
Click to collapse
baaahahahahaha!!! My fiancee has a OnePlus 2 and is a pretty big fan of it. The camera app for samsung TW is far superior tho
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
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
None of these problems here. All that tested and works fine. Phone is super fast after update. Oh and i didnt format the phone after update
klemen241 said:
None of these problems here. All that tested and works fine. Phone is super fast after update
Click to expand...
Click to collapse
Thanks for your reply! I hope somebody facing similar problems has overcome and provide suggestions.
But Sammobile blog has also confirmed these issues.
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
shuvadeep said:
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
Click to expand...
Click to collapse
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
***Update***
Yes this trick is working.
---------------
Also one more question I don't know if it's my phone or everyone is facing this issue. Whenever I switch on VoLTE calls (Screenshot Attached) my phone temperature increases and battery drains.
Nitin5556 said:
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Click to expand...
Click to collapse
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
gee2012 said:
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
Click to expand...
Click to collapse
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Nitin5556 said:
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
Click to expand...
Click to collapse
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
cbotadra said:
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
Click to expand...
Click to collapse
Yes the problem is there in the May update.
Samsung should do something about this.
Nitin5556 said:
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Click to expand...
Click to collapse
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
gee2012 said:
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
Click to expand...
Click to collapse
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Whiskey103 said:
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Click to expand...
Click to collapse
No, its possible that some users who do flash a rom with Odin could face some issues too but i personally don`t. I`am using the ABN bank app and i haven`t rooted for a long time now. I used to do it because of theming and getting updates/upgrades but nowadays i personaly don`t see a reason anymore to root anymore. So i can`t help you with your question.
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Virgo_Guy said:
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Click to expand...
Click to collapse
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
gee2012 said:
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
Click to expand...
Click to collapse
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Virgo_Guy said:
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Click to expand...
Click to collapse
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
gee2012 said:
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
Click to expand...
Click to collapse
Erase playstore cache and you won't even notice it for a while only to re-appear after sometime.
"Less noticiable" and "very much noticiable" in my usage in 1x & .5x respectively. In ASD5 build, this transition slips like a soap.