SM-G900H <<Bug List>> - Galaxy S 5 General

okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
-Camera takes pictures, some of them after being taken, are corrupted files.
Not sure why this happens but it happens.(Some users report this is due to the Music Player bug)
-Phone Lags on Wake-Up after using a 64gb Micro-SD. Not tested on 16 or 32gb ( using 32gb, no wake up lags )
Rare Bugs:
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting several times solves this. (HAPPENED ONLY ONCE) (The chances of getting this bug is the same as catching a shiny pokémon)(Some users report this is due to the Music Player bug)
- Headphonejack Bug: Contacts detect headphone still inside after submerged in water, to solve this issue: "There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole".
Well, Ultimately, this is to see if samsung can create the next update, fixing these issues...
Sent from my SM-G900H using XDA Free mobile app

fenchai said:
okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
-Camera takes pictures, some of them after being taken, are corrupted files.
Not sure why this happens but it happens. (the chances of this happening is like catching a Pikachu in the beginning of the game)
Not Sure if a Bug or not(Rare Bug)
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting 1X times solves this
HAPPENED ONLY ONCE.
(The chances of getting this bug is the same as catching a shiny pokémon)
I shall update this if any more bugs are known.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
maybe you have some issue..
i have the mobile from 16 April and i dont have any issue with my SM-G900H
neither camera neither power button..
P.S. i dont have galaxy players (deleted by root )

fenchai said:
okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
Not Sure if a Bug or not(Rare Bug)
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting 1X times solves this
HAPPENED ONLY ONCE.
(The chances of getting this bug is the same as catching a shiny pokémon)
I shall update this if any more bugs are known.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
These two are caused by the Music app having a memory leak...
Didn't had any issues taking pictures yet, overall I'm a happy camper.

drakester09 said:
These two are caused by the Music app having a memory leak...
Didn't had any issues taking pictures yet, overall I'm a happy camper.
Click to expand...
Click to collapse
not sure if I want to root it yet, i hate knox so much T.T want warranty but freeedom too.
well for now, there is no rom for g900h anyways, I will wait.
S5 music player is the only one that has built in streaming, so its a nice feature..
Sent from my SM-G900H using XDA Free mobile app

Tried it on two different devices and other users have had same results. Having a 64GB memory card causes the phone to take longer/lag to "wake up".
I have not tried a 128GB, but my 32GB is not as laggy. Best results is no memory card at all.

keysoh2 said:
Tried it on two different devices and other users have had same results. Having a 64GB memory card causes the phone to take longer/lag to "wake up".
I have not tried a 128GB, but my 32GB is not as laggy. Best results is no memory card at all.
Click to expand...
Click to collapse
Ok, will update post. Thanks for reporting

Hadphone jack lies that headphone is connected after 5 min. underwater trip. Repaired by needle after drying. Happend second time.

alexmeo said:
Hadphone jack lies that headphone is connected after 5 min. underwater trip. Repaired by needle after drying. Happend second time.
Click to expand...
Click to collapse
Can you tell me with details your solution?
Sent from my SM-G900H using XDA Free mobile app

fenchai said:
Can you tell me with details your solution?
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole.

alexmeo said:
There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole.
Click to expand...
Click to collapse
Thanks for reporting
Sent from my SM-G900H using XDA Free mobile app

"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk

enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
How often does this happen?
Did you listen to music via Sammy's music player before this happened?
How much battery did you have when it happened?
Sent from my SM-G900H using XDA Free mobile app

enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Did you switch to ART?
Sent from my SM-G900F using XDA Free mobile app

Ave666 said:
Did you switch to ART?
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
No.
fenchai said:
How often does this happen?
Did you listen to music via Sammy's music player before this happened?
How much battery did you have when it happened?
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
On one day it happens like 4 times.
Sometimes this happens and I haven't been using the music player.
Sometimes 20% or even 85% always different.
When this happens there were some times the phone rebooted.
when I get free time I will reset to default and see if it gets fixed.
Sent from my SM-N900 using Tapatalk

well this is a strange bug, make sure to check if any app is interfering. wipe and try again if possible.
Sent from my SM-G900H using Tapatalk

I had all this problem too, after using music player , some of my lictures in gallery broken.
Sent from my SM-G900H using Tapatalk 2

all bugs are cleared after a small update via ota from samsung. otherwise download and install new custom rom or official
Sent from my SM-G900H

I've got some kind of unresponsive buttons bug. Btw my version is G900F.
So, when i tried to woke it up, it worked, fingerprint unlock too but then, screen nor capacitive buttons were responding. All another buttons was and screen not. After 30 seconds it's fixed itself.

Only bug I have is that the fingerprint scanner occasionally stops working completely on the lockscreen (the animation will stop and all I can do is turn screen on/off with lock button until I can restart).
This occured on multiple firmwares, although perhaps xposed might be the culprit.

enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I can confirm this as well. It is quite frequent and very annoying. Whenever I receive any notification, I see the led blinking. I look to turn the phone on by the power button or home button, but only the capacitive LEDs light up and screen goes blank. At times I have had to wait for more than 30 seconds to get it back working or worst case I had to pull the battery and restart.
Very annoying bug since Kitkat. I now have the lollipop version installed (XXU1BOAD) in the hope that this dreadful issue is fixed.
Unfortunately it didn't. Samdung made this phone ****ty with the in house exynos processor. Please suggest some fix for this if anyone finds it.

Related

Touchscreen slowness

Ok so i am trying to determine what my problem is.. here are the symptoms. When i try and end a call i sometimes have to press multiple times or deliberately press and hold the end button and sometimes it doesn't respond pretty much at all. Also i am using go launcher and when i press icons that are in the dock bar they have the same issues. I also have similar issues when i text it's really annoying so is anyone else have similar issues?
Sent from my VS910 4G using XDA App
Same here. I've noticed that to hang up it takes a deliberate double tap. Also, the screen will sometimes become inoperable requiring a reboot. This has happened three times since first getting it. One note if that out happened twice stock, and once with decrapped 1.1
Any body else seen this?
Sent from my VS910 4G using XDA Premium App
I haven't seen it anywhere else, but I have seen the double tap on the end button to end a call. Seems to happen frequently. A "feature?"
Either way, it's annoying.
Running Go Launcher as well.
To me, it seems like it takes the screen a really long time to wake up from being off, in all cases - for example, dial voicemail and put the phone to your ear. When you get the prompt to put in your PIN, take it away and the screen comes on, try to punch the dialpad button immediately and it just won't work. I tried it as I was writing this and had to triple tap the button.
Same thing with the lockscreen (still on the stock lockscreen for now). The screen will wake up and it takes a second or two to even start to register finger swipes. It's really annoying...
Speaking of phone lockup, I received a call a few days ago and the phone froze - I couldn't answer the call, or do anything, all the while the phone just kept ringing. Had to pull the battery. I'm still on the stock ROM.
Me too! I had a call and it froze. Battery pull as well. Also, forgot to mention I am using open home launcher.
Sent from my VS910 4G using XDA Premium App
Yep it's a bug either in LG's function to turn on and off the screen in Android, or the kernel drivers that enable/disable the touchscreen. There is about a 1 second delay to it.
I discovered this lovely bug while porting the AOSP lockscreen mod.
I'll run some more tests to see whether it's an android bug or a kernel bug. I'm betting it's android (something like the screen being turned on before the touch controller has had time to reinitialize itself, or something more complicated like a race condition of some kind...)
Either way, with cm7 around the corner, I don't think it's that big of a bug
thecubed said:
Either way, with cm7 around the corner, I don't think it's that big of a bug
Click to expand...
Click to collapse
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
AndroidCraig said:
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
Click to expand...
Click to collapse
Since he is the one working on getting it ported over, I think he has the best idea, and the only rule of cm is no asking for etas ;-)
Sent from my VS910 4G using XDA Premium App

Home button lag in Android 4.4 (KitKat)

Open any app eg. dialer.
Press home button. There is a slight delay (the amount of delay seems to vary at random) and then it closes. Sometimes it's not noticeable, sometimes there's a half a second delay.
When it does happen, you can see the home button light up animation stuttering too.
Compare this with the back button.
Open app again
Press back button. It closes instantly every time.
This is repeatable, and happens with every app.
Edit:
There also seems to be added delay to the multitasking button.
When pressed at the home screen, it's there's a small amount of delay. When pressed inside an app, there's a one second delay.
Using ART runtime seems to fix the lag in home and app switcher buttons, though 4.3 did not have the lag and it was dalvik, so not sure what that means.
Pulling down the notification on lockscreen also lags. But I do have the transparent system bars mod so it could be that.
doesnt happen on my phone
hmm.. happens with me too. stock 4.4 with TWRP
You overreacting.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I see what he means.. I wouldn't call it lag, just delayed.
I did a screen record of it. It's so minimal I would never have noticed it until my attention was called to it
I have animations disabled
Not to sound rude but... this is a complaint? I get that the transition animation might look like crap and a tad choppy. In that demo at least, it does. But come on, just turn the animations off if they bother you. I've got an iPhone 5S, which is by most accounts the smoothest mobile experience, and clicking the home button takes the same amount of time (probably longer) because of the stupid fade in/out stuff.
If your complaint is a freeze up, then that's valid. But as an aside, I'm with you in that these animations are getting borderline cumbersome and stupid. The "lag" you see is Google's need to utilize these things.They used to be cool, like the first 1,000 times I saw them. Now they're just a lame hindrance to opening an app.
Sent from my Nexus 4 using xda app-developers app
Actually has nothing to do with transition animations.
It is the delay with the home button press being registered, before the animation even starts.
And actually in the video recording above, animations are off.
This is a regression. In 4.3 the home button was much more responsive, so yes it's a complaint. Actually, not really. I'm just putting the information out, and also want to see if others are experiencing the same.
I'd love it I'd you could stop watch these findings to display this massive regression.
Sent from my Nexus 4 using xda app-developers app
monkor said:
I'd love it I'd you could stop watch these findings to display this massive regression.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you can't notice the difference then more power to you. Stop posting in here.
Not to sound rude but... you're complaining about a complaint?
Out.
I was actually just hoping you would get out a stopwatch and show the difference with some stats...I mean maybe it is an issue.
Sent from my Nexus 4 using xda app-developers app
I am using factory stock with AOSP launcher (launcher3.apk from CM11) and ART enabled, don't have that problem, its very responsive.
Don't watch this if you suffer from epilepsy.
I guess sometimes there are 100ms delay, but its not abnormal. Delays tend to be because its trying to launch a new app.
I just tried Google Launcher and its not an issue either.
This should go without saying but... I'll throw it out there anyway. Because... Yeah...
For anyone watching the screen record I made.. You have to remember the overhead encoding video and writing to the Sdcard will have on the end result. ie: Performance in video may not be a complete accurate representation of real world use.
/I just wanted to use screen record and this looked like a opportune time.
I've noticed the same thing on both 4.3 and 4.4. Captured a video of mine and streamed it to Twitch since it's one of the few places that accepts and plays back at 60 FPS: twitch.tv/caiman86/b/479853664 (won't let me linkify it since I have too few posts)
Sometimes the home button is perfectly responsive and sometimes there's that strange hitch and delay when going home. The video showcases this fairly well.
morgante said:
I've noticed the same thing on both 4.3 and 4.4. Captured a video of mine and streamed it to Twitch since it's one of the few places that accepts and plays back at 60 FPS: twitch.tv/caiman86/b/479853664 (won't let me linkify it since I have too few posts)
Sometimes the home button is perfectly responsive and sometimes there's that strange hitch and delay when going home. The video showcases this fairly well.
Click to expand...
Click to collapse
That video shows the issue pretty clearly. Link (since you can't post a direct link)
Though I can't say I remember having this issue on 4.3. I could be wrong. My girlfriend has a Nexus 4 still on 4.3, so when I can get my hands on it (probably tomorrow), I'll confirm.
But even if it was in 4.3 and not just a new 4.4 issue, I still think it's worth reporting.
Also I don't actually know if this is specific to the Nexus 4. If anyone has a Nexus 7 or 10, could you please test if it happens.
Thanks.
Have you ever had a go on an s3? I had a go on my dad's and there's a huge wait after pressing home and anything happening, although admittedly this is because you can double tap home to open something (s-voice I think it was)
Sent from my Nexus 4 using Tapatalk
On S3 you must disable option (double home button klick action) in Accessibility.
On the iPhone it's almost instant whereas on Kitkat it's quite laggy.
Sent from my Nexus 4 using xda app-developers app
wilsonlam97 said:
On the iPhone it's almost instant whereas on Kitkat it's quite laggy.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Switch to ART and see the lag gone.
Tom540 said:
Have you ever had a go on an s3? I had a go on my dad's and there's a huge wait after pressing home and anything happening, although admittedly this is because you can double tap home to open something (s-voice I think it was)
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yep, it's because of the double tap command, not the same issue as this.
You are right. The delay is quite noticeable.

[Q] Severe wake up lag

I've had fairly severe wake up lag on my Note 3 since the beginning, 4-6 seconds is fairly common (6 seconds means it flashes the screen and blanks it out again, going back to sleep, but then I can wake it up again and it responds in 1-2 seconds). I've never seen this on my Galaxy SIII with the same set of apps, but as soon as I got the Note 3, I saw the delay. I've swapped out for a new one (different reason) and see the same behavior.
If it is not common, I'd have to attribute it to an app...but honestly this is a base OS function, no app should be holding the phone in deep sleep. Any ideas would be helpful.
KitKat appears to fix this
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Are you rooted? This MOD really helps the delay.
http://forum.xda-developers.com/showthread.php?t=2584013
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I don't got 4-6 secs lag, but I did have 2sec lag, and then took out my SD card and that fixed it for me.
pham818 said:
I don't got 4-6 secs lag, but I did have 2sec lag, and then took out my SD card and that fixed it for me.
Click to expand...
Click to collapse
So you no longer use an sd card in your phone? Seems like there should be a better way around than that...
rkub said:
So you no longer use an sd card in your phone? Seems like there should be a better way around than that...
Click to expand...
Click to collapse
i had a 64gb class 10 sd card i got for 15 dollars. 64 is kinda over kill for me. but yeah i 32 gb is enough for me, i still got like 18gb of free space left lol or something like that.
edit: but apparently the the guy up there said kitkat fixes that.
pham818 said:
I don't got 4-6 secs lag, but I did have 2sec lag, and then took out my SD card and that fixed it for me.
Click to expand...
Click to collapse
Wow, good call! My first Note 3 had the proximity sensor go bad, and then stopped recognizing my SD card. I figured the phone was just a lemon, so I transferred the SD card into the new phone and it didn't recognize it either so I just left it in. After you said this I removed the SD card and it's vastly improved, so far it's back to the normal 1-2 second lag max (so far).
I had the same thing with the sandisk card. replaced it with Samsung's version and its resolved.
Envy Life said:
I've had fairly severe wake up lag on my Note 3 since the beginning, 4-6 seconds is fairly common (6 seconds means it flashes the screen and blanks it out again, going back to sleep, but then I can wake it up again and it responds in 1-2 seconds). I've never seen this on my Galaxy SIII with the same set of apps, but as soon as I got the Note 3, I saw the delay. I've swapped out for a new one (different reason) and see the same behavior.
If it is not common, I'd have to attribute it to an app...but honestly this is a base OS function, no app should be holding the phone in deep sleep. Any ideas would be helpful.
Click to expand...
Click to collapse
If you are rooted, i would advise you to use the Vulpix Mod. It works!
http://forum.xda-developers.com/showthread.php?t=2584013
it has helped me greatly reduce the wake time. though, its been months since i flashed it and i believe the wake time to be gaining again.
The update to NB4 pretty much eliminated all lag. I can click the lock and wake button all day and it instantly goes on and off since the update.
I was running the Crash rom port yesterday and I thought my phone had died. I was receiving an important business call on my work phone and at the same time trying to wake up my Note 3 to see my notes for the call. I was pushing the home button and nothing was happening. I pressed the power button and it woke up. So kitkat did not fix it for me. Now I'm trying Knoxraid rom and am noticing a short wake up delay, I may try taking out the sd card. I'll report back this afternoon.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
im on knoxraid and i havent seen any wake up lag. make sure your sd card is out and s voice wake up commands arent on. those are the main causes from my experience

Unresponsive power button

Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Aruarian said:
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Click to expand...
Click to collapse
Sounds like a different issue.
Mine was a complete one of, switch made me suspect software asop issue.
Monitoring.....
Sent from my Nexus 6
Happened again, dead power button, woke by volume buttons, reboot, works fine again.
So this isn't intermittent, in that when it fails it won't work again until restart, which says to me software.
I'm now using this thread as log. To see if RMA necessary.
Chroma 5.1 22/03/2015
Sent from my Nexus 6
Happened again later in the day.
Sent from my Nexus 6
ben_pyett said:
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Click to expand...
Click to collapse
Do you have a screen protector covering the sensor? If so that's probably the issue, disable ambient display and see if you can reproduce the problem.
Sent from my Nexus 6 using XDA Free mobile app
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
ben_pyett said:
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
Click to expand...
Click to collapse
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Feature is disabled. ?
Sent from my Nexus 6
ben_pyett said:
Feature is disabled. ?
Sent from my Nexus 6
Click to expand...
Click to collapse
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
ben_pyett said:
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
Click to expand...
Click to collapse
Then short of backing up and doing a clean install I am out of ideas, sorry.
Sent from my Nexus 6 using XDA Free mobile app
Cheers. Literally only just did that for stable Chroma 22/03 version... Will wait until further versions come out and will consider doing that. Cheers anyway
Sent from my Nexus 6
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
happened to me today, like it was in a deep sleep and took ages for the power button to work.
Im on stock 5.1
Happened once 31/01 soft reboot resolved it
Still believe this is software.
ben_pyett said:
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
Click to expand...
Click to collapse
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I would get this issue on Chroma if I had enabled the option Display--Ambient Display--Overwrite Value.
See if thats enabled, and if so, try with it disabled for awhile.
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I was clean install on 5.1 but not since, although did import apps and data from TB not that it should impact it at all. Only ever run Chroma, jumped straight to it after initial unlock.
Fortunately volume keys always wake - so far.
Let me know how you get on - in this thread.
If I find it continues to happen then I'll consider clean install and then maybe even a replacement device.
Everything was fine after last reboot.
Immediately after plug in into charger, the power button stop working. First time experiencing this. Able to try this to guys?
Edit: I toggled 2 things.. Enabled / disabled ambient display overwrite defaults and screen on when plug / unplug charger..
Power button is working again without any restart.. @githyanki @ben_pyett

Recent Update

Anyone having any specific issues with the most recent update?
Well my wife has been using it the past couple days and got the update at work yesterday... Today she mentioned the Home button notification light doesn't seem to be working. (it was when I first started using the phone) I'm not sure if they are tied, or if she messed with a setting. If anyone else who got the update would like to test the notif LED on the Home button that would be cool.
hardware buttons issue
The notification light for me is fine but my hardware buttons are testy. sometimes I have to double press the buttons for it to respond. Other times the entire phone freezes for a minute or the buttons don't work at all. I think it was a bad update.
Some days later the phone stopped getting text messages until I restart it. Now it gets them hours later. I already cleaned out the cache. But did not fix it. This update is killing my phone.....
samsung_pro_blackbird said:
Anyone having any specific issues with the most recent update?
Click to expand...
Click to collapse
Sent from my ZTE Blade L3 Apex using XDA Free mobile app
No noticeable issues here yet.
No issues noted by me. It fixed some Bluetooth volume issues I was having so that's good.
The led notifications light on mine sometimes freezes on.
Sent from my A1P using XDA Free mobile app

Categories

Resources