My phone does not seem to adjust the screen brightness, when automatically adjust brightness is ticked.
I have to untick and retick it to get it to adjust.
Anyone else experience this?
I am running the latest OTA
Yep. Me too. Since the last update 2 months ago.
Sent from my SM-G935F using Tapatalk
I'm sure you rebooted numerous times already, but mine did that also and just need a reboot to fix.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Related
My was working fine. Then it stopped after about two hours of working.
Sent from my T-Mobile G2 using XDA App
What "unlock sound".
Mine never worked before the recent OTA update and started working there after.
Hasn't stopped working, yet..
nandesho said:
Mine never worked before the recent OTA update and started working there after.
Hasn't stopped working, yet..
Click to expand...
Click to collapse
Mine no longer makes the sounds. There were nice while it lasted.
Sent from my T-Mobile G2 using XDA App
nandesho said:
Mine never worked before the recent OTA update and started working there after.
Hasn't stopped working, yet..
Click to expand...
Click to collapse
Same here...I didn't even know the sound existed till I got the OTA update. Hopefully it has fixed some of the other kinks in my phone or I'm exchanging for my third G2.
Sent from my T-Mobile G2 using XDA App
Mine works fine when I have the option checked but since I don't care for it I turned it off.
Mine is working
Sent from my T-Mobile G2 using XDA App
check: Settings -> Sound
There's a checkbox for "Screen lock sounds".
ddgarcia05 said:
My was working fine. Then it stopped after about two hours of working.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
This is interesting. My auto brightness had a similar thing happen: it was finally behaving properly for a short time, but then started setting the screen too bright for the circumstances again. I haven't had a chance to check the logs to see what light sensor readings are triggering brightness changes since it stopped working properly again. I do know that while it was working properly higher light sensor values were required to increase the brightness than before the update. I wonder if these issues are related.
Hosermage said:
check: Settings -> Sound
There's a checkbox for "Screen lock sounds".
Click to expand...
Click to collapse
Yes, I know to change my settings. I just doesn't work for me even after reinstalling the updates. I've also tried reverting back to my stock launcher.
It doesn't even work for me. I'm not on the OTA yet neither, with the stock launcher.
xdviper said:
It doesn't even work for me. I'm not on the OTA yet neither, with the stock launcher.
Click to expand...
Click to collapse
The ota was suppose to fix it.
Sent from my T-Mobile G2 using XDA App
Mines working fine now after the OTA.
Sent from my T-Mobile G2 using XDA App
It only started working for me after the OTA and hasn't stopped working for me since.
its working for me after the update. It never worked prior to.
Mine also works now after OTA "manual" update. Going on day and a half after update and still working.
Mine work.
I opened up the OTA zip, and the sounds are in there in the \system\media\audio\ui folder, so that was clearly some sort of update. In the Settings -> Sound -> Volume section is Use Incoming Call Volume for Notifications checked? Also, what is your media volume? If these are correct, then I have no idea.
Mine are no longer working. Worked for a bit and then randomly spouted stopped. Not sure what's going on
It seems loading up maps and using the turn by turn navigation brings my lock sounds back
Sent from my T-Mobile G2
Mine doesn't make the sound.. it never has, but I didn't get my ota yet
Sent from my T-Mobile G2 using XDA App
k I'm having some issue with this setting. everytime I change the setting to sleep when screen turn off. by the end of the day or even couples hours later. it changed back to never by itself. so my question is, is there a master setting for this? oh yeah using froyo 2.2
Sent from my GT-I9000M using Tapatalk
not sure bout a manual setting buut theres apps out there that will do this, maybe they will override froyo's setting for ya
and which one will it be? Haha
Sent from my GT-I9000M using Tapatalk
you could try Juice Defender,, just look around mate im sure theres a few out there.
You also have the choice of backing up your data and factory reset the phone .
jje
The screen turns on randomly. No notification. No rhyme or reason that I can spot so far. The Always On Screen is set to off. The "Keep screen turned off" is enabled, though enabling it hasn't helped. The screen still turns on randomly. I'm running PB5. I didn't have this problem running the version it shipped with. This seemed to start immediately after I updated to PB5. I had the phone for a little over a week before I updated.
quarky42 said:
The screen turns on randomly. No notification. No rhyme or reason that I can spot so far. The Always On Screen is set to off. The "Keep screen turned off" is enabled, though enabling it hasn't helped. The screen still turns on randomly. I'm running PB5. I didn't have this problem running the version it shipped with. This seemed to start immediately after I updated to PB5. I had the phone for a little over a week before I updated.
Click to expand...
Click to collapse
Idk why it's happening, but mine is doing the same thing. I've had mine since March 1 and mine just started with new update too. And my battery has tanked since then too.
Sent from my SM-G935V using Tapatalk
quarky42 said:
The screen turns on randomly. No notification. No rhyme or reason that I can spot so far. The Always On Screen is set to off. The "Keep screen turned off" is enabled, though enabling it hasn't helped. The screen still turns on randomly. I'm running PB5. I didn't have this problem running the version it shipped with. This seemed to start immediately after I updated to PB5. I had the phone for a little over a week before I updated.
Click to expand...
Click to collapse
jagrave said:
Idk why it's happening, but mine is doing the same thing. I've had mine since March 1 and mine just started with new update too. And my battery has tanked since then too.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Oh good....... then I'm not imagining things. It's happening to more people than just me[emoji15]
Go to settings, accessibility , dexterity and interactions , easy screen turns in and see if it is set to on. I just toggled it on and off and haven't had the screen randomly turn on yet. Fingers crossed [emoji108]
Sent from my SM-G935V using Tapatalk
lahegry said:
Oh good....... then I'm not imagining things. It's happening to more people than just me[emoji15]
Go to settings, accessibility , dexterity and interactions , easy screen turns in and see if it is set to on. I just toggled it on and off and haven't had the screen randomly turn on yet. Fingers crossed [emoji108]
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
That setting wasn't on. That's not it but definitely worth checking.
There is a thread on reddit about this and they haven't figured it out either.
Mine is doing the same thing. I hate it when it does it in my pocket and causes problems.
In my case uninstalling Facebook solved issue
Clean flashed the other day. Somehow lost that option to select wifi networks from within the quick settings menu. Can't seem to find the option to re-enable that feature.
Help, please.
Sent from my Nexus 6P using Tapatalk
Can you slid the notification bar down twice then hit edit?
Or hold the settings down for ten seconds to enable system UI changer?
Sent from my Nexus 6P using Tapatalk
No system ui runner option. Yes, I can edit the panel , but I don't see an option for expanded wifi
Sent from my Nexus 6P using Tapatalk
Any ideas, anyone?
Sent from my Nexus 6P using Tapatalk
Droid_JD said:
Any ideas, anyone?
Click to expand...
Click to collapse
Sorry to tell you but sounds like you are probably going to have to flash the ROM again. Sometimes weird unexplained bugs pop up in the OS when flashing. I once had the DND toggle stuck in On position after flashing just a stock image of a new security update from Google. No matter what it wouldnt turn off. So I had to reflash again.
Took me a coupe of days, but I finally had a chance to clean flash. The wifi QS toggle became available, but after a couple of boots I lost the toggle again. Not sure what I have on the phone that could bee doing that. Very strange
Sent from my Nexus 6P using Tapatalk
Droid_JD said:
Took me a coupe of days, but I finally had a chance to clean flash. The wifi QS toggle became available, but after a couple of boots I lost the toggle again. Not sure what I have on the phone that could bee doing that. Very strange
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok, well I'm officially an idiot.
To enable the quick toggle with WiFi networks, the WiFi QS needs to be in the top row, with "enlarge top row" enabled.
Now that I figured that out, it's time to start on "turning left"...
Hope this helps someone else out
2-2.5hrs SOT SM-G935FD.
A month old. Problem started 2 weeks ago.
Have uninstalled all bloatware through ez disabler,
WiFi off everywhere in settings,
location history off and Google disabled,
wiped cache,
using greenify for aggressive doze,
Nothing worked so far
Need help
Warlocks such as ssp wake lock, ssp sensorhub, 13960000.decon, power manager service display, and power manager service wake lock are each getting about 4hrs worth of wake lock minimum
I'm guessing you disabled something that another app is relying on, and is now forever cycling on calling on that app repeatedly. First thing I'd do is restore everything back and see what happens.
Sent from my SM-G935F using Tapatalk
Well I can't possibly think of anything, but my phone never seems to rest. Even when it's sitting in my pocket it gets hot and drains
chanchan05 said:
I'm guessing you disabled something that another app is relying on, and is now forever cycling on calling on that app repeatedly. First thing I'd do is restore everything back and see what happens.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Another thing is that even in Safe mode the problem persists.
Safe mode doesn't reenable the stuff you disabled. As I said, enable everything back and restart. See if the problem goes away. That means you disabled something you shouldn't have.
Please tell me you know exactly what each thing you disabled was and you know what dependencies they have. Anything you don't have those answers for, you have no business disabling.
Sent from my SM-G935F using Tapatalk
Alright, I'm doing a factory reset tomorrow and I'll get back with the results. Not too optimistic.
Can that be the sole cause? Or can there be some problemd with the firmware or system apps?
yash0602 said:
Alright, I'm doing a factory reset tomorrow and I'll get back with the results. Not too optimistic.
Can that be the sole cause? Or can there be some problemd with the firmware or system apps?
Click to expand...
Click to collapse
Can't say unless we know what exactly you disabled (need a whole list) . We need to rule that one out first because the phones isn't running the same services as what is expected of stock. Then finding out what's causing the wakelock to see which one needs to be reenabled.
Well a factory reset is the fastest way. The incremental reenabling is slower but you won't need to redownload everything.
Sent from my SM-G935F using Tapatalk
chanchan05 said:
Can't say unless we know what exactly you disabled (need a whole list) . We need to rule that one out first because the phones isn't running the same services as what is expected of stock. Then finding out what's causing the wakelock to see which one needs to be reenabled.
Well a factory reset is the fastest way. The incremental reenabling is slower but you won't need to redownload everything.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I have re-enabled everything from EZ disabler but no difference has been made. I'll do the factory reset soon.
I was hoping Nougat would fix it, but I can't wait that long