I'm not sure if anyone can help here, but I'm new to having an S2, so I have no idea on this stuff yet.
Anyway, so NFC will not turn off. If I go to it and select it to turn off (green dot is there), after 10-15 seconds it will show that it is off, however, when I back out and look at the previous screen, under NFC it says ON. Sure enough, when I select it again, the green dot is back... Obviously not a huge deal, but I will likely never use it, and I'm hoping it being off will help with battery life.
I also noticed you can't turn connections on/off with the Gear manager on a phone. Is there a better app to manage the Gear with? Something that gives more functionality and control?
Please and thanks!
I was told after the last update you can't turn NFC off. My acts just like yours.
Mine is the opposite problem - i can't turn mine on!
It has the same scenario. Turn on NFC, it freezes for 10 seconds, then it is still off
I have the same damn issue and its annoying me.
Related
Had to use Google Nav to get across town tonight, after sunset. I usually drop the phone in my center console after it locks location and begins giving directions. On my old Moto Droid, I could turn the screen off and just listen to the voice directions.
On the Thunderbolt, it seems to keep the screen on, regardless of what the time out is set for. If I hit the power button, the screen turns off, then powers back on in a second.
This is just a complete waste of battery. If I was sitting the phone in a car dock, it'd be different, but this is a waste. Anyone experiencing this, or know how to get the screen to turn off when Navigation is active?
idk if this works but have you tried hitting the home button to get out of google nav (while it's still running) then hit the power button?
I have experienced the same feature. It doesn't bother me too much though cuz I have my phone plugged in.
I bet the above idea works.
this is not a signature I type it in every time maybe sent from my phone or my computer
Bateluer said:
Had to use Google Nav to get across town tonight, after sunset. I usually drop the phone in my center console after it locks location and begins giving directions. On my old Moto Droid, I could turn the screen off and just listen to the voice directions.
On the Thunderbolt, it seems to keep the screen on, regardless of what the time out is set for. If I hit the power button, the screen turns off, then powers back on in a second.
This is just a complete waste of battery. If I was sitting the phone in a car dock, it'd be different, but this is a waste. Anyone experiencing this, or know how to get the screen to turn off when Navigation is active?
Click to expand...
Click to collapse
It only keeps the screen active if you are in the navigation program. Just back out, or go to any other screen and it will turn the screen off normally. Working as intended.
akanatrix said:
It only keeps the screen active if you are in the navigation program. Just back out, or go to any other screen and it will turn the screen off normally. Working as intended.
Click to expand...
Click to collapse
Have to test this. Thanks.
I have experienced the same issue with the thunderbolt. The screen stays on weather I have the phone plugged in or not.
I see hitting the home button as more of a workaround than a solution here. It's easier for me while driving to turn the display on and off with one physical button.
I'm hoping that cyanogenmod will fix the issue when it's released but I feel like there should still be a way to set the screen to stay off when the power button is pressed in navigation.
I think its a feature, keep screen alive. As mentioned, going to home screen allows you to put it to sleep, but you cannot while navigation is active.
I can see your point though, keep it off, then a quick on shows you where you are without the need to open the app from the tray.
Please help me guys... my xoom , i bought it new,its about 2 weeks ago, and i've just installed adobe reader and evernote from playstore, but.... now, after i press the power button in the back, it goes off, and i want to turn it on again, so i press the power button in the back again, but its "too long to turn on", i have to wait about 3 mins, i'm getting frustated with it now, so how can i make it right??
please help me guys... very need your help...
I'm afraid there probably isn't anything wrong with your Xoom.
Newer Android devices have a feature, lets call it "Quick Boot"...which allows a device to be turned on in seconds! But what is actually happening is, the device is never properly off. The RAM is stored, and when the device is turned on again, it resumes...sort of like your computer hibernating.
You can check this out by comparing the boot times of turning a device off and on, and rebooting...where everything is shut down. Rebooting should take about 50 to 100% longer.
The Xoom however is ever so slightly too old to have this Quick Boot feature. When you turn the Xoom off, it is off properly. And when you turn it on, it has to load everything fresh.
Give it a chance though. The Xoom might be getting on a bit now, but it is still a great device. And if the boot time is annoying you so much...simple...don't turn it off!
I've had an odd problem with my 820 almost since getting. I'm hoping one of you geniuses have some advice.
When I turn it on it works perfectly, sometimes for hours. Then the screen goes blank, and then random pixels begin to appear, starting at the top of the screen. Outdoors rather than random pixels the screen goes almost totally green. Strangely, if part of the screen is obscured the green only covers rhe exposed area.
Pressing the on button repeatedly usually brings back the lock screen and reset (on+down) fixes the problem for another few hours.
By the way, eventhough I can't see the screen the touch sensor works. For instance I can hold theon button and then swipe downwards to turn off the phone. I can also answer and hang up using earphones.
My daughter who purchased the phone said it worked fine until the amber update. I had hoped the black update would fix the problem but no change. I found some posts from people with the same problem who sent the phone in to be fixed and got it back in the same condition. I really don't want to go through the hassle unless I expect to get it back fixed. I'd rather try fixing it myself.
My question is whether this is a firmware problem an whether it is likely that re-installing the stock black rom would do any more than the ota install that occurred automatically did (or didn't do).
Any ideas?
Nobody?
By the way it seems to happen only, or mostly when in standby.
I installed an app that displays a clock and doesn't allow the phone to go into standby mode,
and the problem doesn't appear to occur (unless I forget to leave the app on top).
I would set the phone to standby = "never" but the option isn't available on my phone, though
I understand that there are those with the standby = "never" option.
Any idea if I can set standby = "never" with keyboard commands, perhaps?
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
I noticed that after using the phone for a few hours, the screen will stay on unless I specifically hit the power button to turn it off. The screen off time is set to 15 seconds.
If I reboot it, it will go back to normal, i.e. turning the screen off by itself.
Any one experience this? Some app bug? How to fix it?
Hmmm. Is "Smart Stay" on or off? Do you have Dev Options enabled? If so, is always on while charging option on? All I can think atm.
Sent from my SM-G955U using Tapatalk
tedlin said:
I noticed that after using the phone for a few hours, the screen will stay on unless I specifically hit the power button to turn it off. The screen off time is set to 15 seconds.
If I reboot it, it will go back to normal, i.e. turning the screen off by itself.
Any one experience this? Some app bug? How to fix it?
Click to expand...
Click to collapse
Have you disbled any services or packages with Package Disabler Pro?
I don't have any of these mentioned issue, and I am still trying to pin point which app is the trouble maker.
Call Samsung support, and they said if I have bluetooth device as "trusted" home/location, they have seen such issue, and want me to turn off these "home" indicator Bluetooth connection.
I effectively turned off the Bluetooth wireless, and this afternoon, after a close to 2 hours meeting and was irritated to find out the screen has been on all the time.
I am going to find a good startup manager and disable APP one by one to see which is the bad boy.
thanks