Hi, recently Google integrated Google auto into Google maps and I went through the settings and I remember activating that damn setting. Now every time I start navigation or if the phone connects to car bt, DND switches on automatically. It's driving me insane. And since then I have been trying to find that setting again but I just can't! I tried to reinstall maps, Google app, Google auto.
Please help!
I noticed a few bizarre gremlins in this phone that I've never seen in any other device
Sometimes the YouTube video starts playing when I've already paused it etc and walked away from the phone
Sometimes it unlocks itself or the screen lock timeout doesn't lock the screen after 60 seconds like it's set to and it stays lit up
Yesterday I had fingerprint sensor unlock and today and let it charge overnight, today fingerprint unlock has unset itself and only the pin or face unlock is working
Very bizarre behavior I've never had from a phone before
Related
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Hey, I'm only posting because I had a very similar issue. What I did was go into display settings (while connected via USB) and changed the timeout to one minute (or whatever you want). For me, when I went to change the timeout, no item was selected by default. This happened to me after I installed WidgetLocker for some reason. I doubt I will help but I had a very similar issue...
xd_sjo said:
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Click to expand...
Click to collapse
There's an app for that. Search Google Play for screenwake or something. I dunno I'll search up the name for you tommorow
Sent from my Nexus One using XDA
Hi guys,
I've noticed that Tap2Wake function is just too sensitive. It doesn't use proximity sensor so my phone can be woken up even in my pocket. When this happen, it does some stupid things like launching walkman etc.
The only way I see to prevent this happening is to set different lock screen type (PIN, password or pattern).
Does anyone have any other ideas or solutions to fix that?
Yeah I just got this phone and was excited to use this feature but also found that it was turning on and activating random applications while in my pocket. I don't like enabling the lock screen so I'll need to come up with another solution. I turned the feature off for now. I'm going to play around with Tasker to see if it can control turning the tap to wake function on and off. If so, I'll have it turn the feature off whenever the phone is turned upside down (which it always is while in my pocket) if that's even possible.
Does none of the smart lock tools actually work with this phone? The trusted places option worked perfectly on my OPO, but with this phone, I'm always asked to input my pattern or fingerprint when I'm at home. It's not an issue if I'm just turning on the phone because the fingerprint is super fast, but sometimes I like to open a notification right from the lock screen, but I can't do that if the smart lock isn't working...
I am running OOS 4.0.3 and I an confirm that Smart Lock is working.
I have set a trusted device via Bluetooth, in this particular case my Bluetooth module in my car.
Here's what happens and hopefully this is what you expect.
When I am outside of my house and walking to my car, my phone is locked and requires my fingerprint.
I turn on my car and my phone pairs with my car, which then enables the Smart Lock feature.
I then turn on my screen on my phone and I see a Lock Screen but it is slightly different. The lock symbol located at the bottom has a circle around it indicating that the phone only requires a swipe to go to my home screen. It does not require my fingerprint or pin/pattern.
No matter what you do the Lock Screen is present when Smart Lock is functioning. So far I am ok with this.
If you are looking to never see the Lock Screen when Smart Lock is functioning then I am not sure if you can do that.
There could be a way using Tasker for example IF Bluetooth is Connected to Car, set Screen Lock timeout to never and that might prevent the Lock Screen from appearing.
WE would have to test this and I am not sure if Tasker can change the Lock Screen timeout.
I hope this helps.
MysticGolem said:
I am running OOS 4.0.3 and I an confirm that Smart Lock is working.
I have set a trusted device via Bluetooth, in this particular case my Bluetooth module in my car.
Here's what happens and hopefully this is what you expect.
When I am outside of my house and walking to my car, my phone is locked and requires my fingerprint.
I turn on my car and my phone pairs with my car, which then enables the Smart Lock feature.
I then turn on my screen on my phone and I see a Lock Screen but it is slightly different. The lock symbol located at the bottom has a circle around it indicating that the phone only requires a swipe to go to my home screen. It does not require my fingerprint or pin/pattern.
No matter what you do the Lock Screen is present when Smart Lock is functioning. So far I am ok with this.
If you are looking to never see the Lock Screen when Smart Lock is functioning then I am not sure if you can do that.
There could be a way using Tasker for example IF Bluetooth is Connected to Car, set Screen Lock timeout to never and that might prevent the Lock Screen from appearing.
WE would have to test this and I am not sure if Tasker can change the Lock Screen timeout.
I hope this helps.
Click to expand...
Click to collapse
It seems the trusted location is very spotty for me at the moment. Sometimes it works and others it doesn't.
I've got a similar problem. The phone never unlocks when I'm at a trusted location. It unlocks when I'm connected to a trusted Bluetooth though. I've set the location using both my address and by using the Google Maps screen. Nothing works.
I'm using a OnePlus 3T with the regular operating system.
Same here. Trusted location only seems to work for a few hours after adding/resetting a location. After that, it is no longer recognized. I did see an issue brought up in the Pixel forums about this issue, but clearly it's not confined to that device. Here's a few threads about it:
https://productforums.google.com/forum/#!topic/phone-by-google/KNrSoHOhb_Q
http://forums.androidcentral.com/go...art-lock-trusted-places-doesnt-seem-work.html
Hopefully they are still looking into the issue and will release a fix as part of Android O whenever that comes to the 3/3T. Or maybe it's something that OP could look into, but I doubt we'll get that fixed in a timely manner either way...
I have the opposite problem. Phone will always unlock without prompting for fingerprint or code, regardless of being in a trusted location or not. It's pretty annoying.
Sendt fra min ONEPLUS A3003 med Tapatalk
Screen lock doesn't work.
Hi! My problem kinda different. My OP3T screen lock doesn't work. I tried to turn off smart lock. Changing the screen lock type, still doesn't work. Even with fingerprints. So anybody can open my phone by swiping it up. Did somebody have the same problem? Should i upload the video of it and link it?
Anyone noticed theirs? Mine auto brightness is already activated, when I unlocked the screen it gets bright even when the environment is dark. But my auto brightness mode is working.
jhun80 said:
Anyone noticed theirs? Mine auto brightness is already activated, when I unlocked the screen it gets bright even when the environment is dark. But my auto brightness mode is working.
Click to expand...
Click to collapse
Yes it's annoying as all hell. Takes about a minute to adjust but it's blinding at night.
That happens cause I use iris. So in dark rooms, I just use the fingerprint.
If you don't mind the inconvenience caused by having to swipe first before using iris unlock, disable the "Iris unlock immediately when screen turns on" option in Iris Scanner.
The screen has to be brighter than normal initally in order to provide enough light for iris scanning (without the circles for guidance).
The screen is no longer brighter when using iris unlock later because it now requires you to position your eyes within the circles.
Personally, I'm perfectly fine with the brighter screen initially.
At home you can get around it by setting it as a trusted location and then go into display/navigation bar and switch "unlock with home button" to on. That way you can just press the home location and your phone will bypass security/lock screen and go directly to the home screen. That is you can if you're not hiding an affair or other skulduggery from your partner in which case you might want to skip this method. lol
Anyhow you will retain your set security method outside of the trusted location, in my experience I'll usually be trusted around the house and yard but much past it I wont be. This also makes it nice for when you're home with the phone next to you and you want to interact with it without picking it up, you press home and you're in.
Unlocking screen brightness on Android.
This is only an Android Oreo + ( Android 8.0+). I only have this issue with my newer phone which is Android Oreo. It happenes with whatever method I use to unlock my phone. It's an auto brightness setting but it's doesn't seem to be listed as any sort of brightness setting. It's not even in the developer settings. If anyone knows how to disable the unlocking brightness feature, that would be helpful.
This happens for me when I face recognition on so the camera can see my face in the dark. You can change this in Settings > Lock Screen and Security > Face Recognition > Brighten Screen. Turning Brighten Screen off should keep the screen dim in the dark but you'll probably have to unlock with your fingerprint or something.
Galaxy A70
Really annoying this brightness. Even try every thing to keep this brightness on manually set point but at time of unlock, it increase in the middle of the night. Please any one help. Is it a problem of software or hardware.
I haven't notice this at all...
The only problem with this glorious device
I'm on Note 10+ and this is the only issue with this device. In the last three months I've used Pixel 3 and Apple Max and they've both figured this out. The blinding light is terrible. Middle of the night, or first when you wake up.
SOLUTION - If you have fave face recognition:
- Go into settings, select Biometrics and security.
- Select Face recognition.
- Tap on the switch on the right-hand side to turn on/off.
I've searched far and wide and can't find a solution for this issue.
Here is what happens: for no reason that I can see (no new notifications), my screen turns on its own. My phone is just there on the table when this happens and I haven't touched it.
This happens whether the phone is plugged in or not. It happens in the middle of the night and wakes me up.
Things I came tried:
- turn on do not disturb and remove all exceptions.
- disable always on display.
- disabled all lock screen notifications.
- disabled a notifications.
Other things I've tried:
Lift to wake and all other things that could wake the screen.
Did a factory data reset and re setup my phone from scratch.
Nothing works. Can anyone please help me?
Thanks in advance.
I had the very same problem until a few days ago when this behaviour suddenly stopped. What changed? I had shutdown my Pebble watch and connected a Wear OS watch to my phone.
I don't know what the Pebble did, but it looks like it woke up my phone at random intervals.
Maybe it a bluetooth device you've connected?
I'm expeciencing sometimes this behaviour when listening to the music on bike with phone in pocked on back. I disabled all "smart" funcions like smart lock, pocket detecting, wearing detection etc and it stopped.
I think it is caused by new type of proximity sensor used in whole S10 line (so I think it is hw related). I read somewhere than it detects skin proximity even thru several layers of cloting.
It is behaving strange even during phone calls - when put phone down from my ear, it tooks several seconds until screen lights on.
it's one of the things that bothers me a lot about otherwise great phone.
facing same issue
I always loved Samsung galaxy s10. I bought it from my friend who used it for 10 months. I am facing the same issue first I thought it is because he used it for 10 months and some bug appeared but now I came to know its not just me. if anyone knows how to fix it then please post a reply. I really need to fix this
I haven't noticed that on my S10. It sounds like something is triggering it, but what. Do all of you use Bixby because I don't.