Question Proximity sensor not working - Samsung Galaxy S21 Ultra

Have had my S21 Ultra for a couple of days, now. All good, except for one thing - my proximity sensor does not seem to work. I have tried a couple of sensor test apps and they confirm that it is not working.
Have I done something really stupid with settings (always possible !) ? Or do I maybe just have a defective phone ?
Any suggestions as to what I can do to resolve this ? Don't want to have to send the phone back !
Many thanks in advance.

Sorry for the blatant bump, but keen to know if anyone has any thoughts on this. Has anyone else experienced problems with the proximity sensor on the S21 Ultra ?
Many thanks

As much of a pain as it is, return and get a new one. If it fails the tests it's dead.
Make it Samsung's problem child...

blackhawk said:
As much of a pain as it is, return and get a new one. If it fails the tests it's dead.
Make it Samsung's problem child...
Click to expand...
Click to collapse
Thanks, @blackhawk - sadly I think that you might be right about that. Was just hoping that someone in the fabulous community might have a brilliant solution !

wilsojer said:
Thanks, @blackhawk - sadly I think that you might be right about that. Was just hoping that someone in the fabulous community might have a brilliant solution !
Click to expand...
Click to collapse
You're welcome. Someone here very well may have a fix but it should have been right leaving the factory.
At least it's an obvious constant issue. Intermittents ones are the stuff nightmares are made of

Are you sure it has a proximity sensor? I dont see it in the specs on GSM arena. Also I installed CPUZ and looked at the sensors tab and it doesn't show any value for proximity sensor. I dont think the S21 ultra comes with a proximity sensor. There's only a camera on the front rest all of it is screen right?

eldrid said:
Are you sure it has a proximity sensor? I dont see it in the specs on GSM arena. Also I installed CPUZ and looked at the sensors tab and it doesn't show any value for proximity sensor.
Click to expand...
Click to collapse
It does. Not sure where but it needs that input to function properly.
Archived - Samsung Community
us.community.samsung.com
I don't recommend a factory reset unless you did a firmware update. Find to root cause otherwise it will likely reoccur.
Check all relevant settings and disable all power management.
Clear system cache on the boot menu.
Try a hard reboot (not reset).
Try in Safe mode.
It may be purely hardware... especially if it did this out of the box.

blackhawk said:
It does. Not sure where but it needs that input to function properly.
Archived - Samsung Community
us.community.samsung.com
I don't recommend a factory reset unless you did a firmware update. Find to root cause otherwise it will likely reoccur.
Check all relevant settings and disable all power management.
Clear system cache on the boot menu.
Try a hard reboot (not reset).
Try in Safe mode.
It may be purely hardware... especially if it did this out of the box.
Click to expand...
Click to collapse
Thanks (again) @blackhawk. Yes, I do believe that it has a proximity sensor. According to GSMarena:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will try each of your suggestions and see if I can get this working. Not sure if it did this straight out of the box as I didn't test it. I updated the software after the initial set-up as it told me that I needed to do the software update. Wonder whether that caused it.
Will try the different tests and will report back !

wilsojer said:
Thanks (again) @blackhawk. Yes, I do believe that it has a proximity sensor. According to GSMarena:
View attachment 5206523
I will try each of your suggestions and see if I can get this working. Not sure if it did this straight out of the box as I didn't test it. I updated the software after the initial set-up as it told me that I needed to do the software update. Wonder whether that caused it.
Will try the different tests and will report back !
Click to expand...
Click to collapse
Yeah it does. My bad, looks like I missed it. I also did a test call and the screen does switch off when i hold it against my ear. So most likely a defective unit.

wilsojer said:
Have had my S21 Ultra for a couple of days, now. All good, except for one thing - my proximity sensor does not seem to work. I have tried a couple of sensor test apps and they confirm that it is not working.
Have I done something really stupid with settings (always possible !) ? Or do I maybe just have a defective phone ?
Any suggestions as to what I can do to resolve this ? Don't want to have to send the phone back !
Many thanks in advance.
Click to expand...
Click to collapse
Test apps apart, if the phone call screen doesn't turn off when you put the phone to your ear, then there's definitely a problem. Especially that there's no special setting which can completely block the proximity sensor.
If you suspect a misconfiguration, then a factory reset can probably help.

DaReDeViL said:
Test apps apart, if the phone call screen doesn't turn off when you put the phone to your ear, then there's definitely a problem. Especially that there's no special setting which can completely block the proximity sensor.
If you suspect a misconfiguration, then a factory reset can probably help.
Click to expand...
Click to collapse
The clock on a clean return is ticking. If a factory reset clears it but it returns after 10 days the return option is gone. Be stuck right where he started with less options.
It could be something added after unboxed or not... tough call.
File corruption can indicate a bigger issue maybe a bad flash or hardware. I find it troubling that's it's on a completely hidden basic function.
I would error heavily on the side of caution.
Aside from a boot loop (2x) I never -needed*- a factory reset to solve any Android issue.
Most techs go with the reset nuke option because it's easiest fix for them not you. The root cause is still there waiting to be triggered again... been there, done that.
*excluding the been there thing (that 10+ was returned but the replacement did the same thing; it was a settings glitch), one reload due to possible virus infection and OS refreshes for heavy abused loads.

Hello
I dial *#0*# and under widget sensor it doesent even says proximity sensor.
Can somebody check if they have the same?

Sorry for not getting back earlier - yesterday was a tough day at work !
@Tine21 - I agree that it doesn't reference a Proximity Sensor, but everything that I am reading online is that the S21 Ultra definitely has one.
I eventually got in touch with EE and asked for a replacement. Have to say, they were excellent and I had a courier the next day arrive, pick up my old handset and deliver me a brand new one. Having tested this out, it definitely shots off the screen when I am on the phone and I put the phone to my ear, so there absolutely has to be a Proximity Sensor and, with the new handset, this is working fine.
Sadly, I can't get the "wave to phone to wake screen" functionality working, but that is a minor issue. Also, bizarrely, the sensor test apps that I am trying do not pick up any movement on the sensor at all. No idea whether this is the fault of the apps or what, but seems a little odd.
The main thing is that the screen goes off when I pick up a call and put the phone to my ear, so that is good enough for me right now. Might look into the "wave" functionality later.
Many thanks to @blackhawk and all the others for help and advice - this is why we all love XDA forums so much !

@wilsojer Great that you fixed your problem
I was reading a lot about it and apparently, with these new infinity O screens, a lot of people have problems with proximity sensor
I think that screen ON/OFF function during calls works with front camera, gyroscop and touchscreen like on samsung 20FE
That is why you dont get any response from sensor app, but this is only my opinion

I am afraid, there is no Proximity Sensor in the s21*. The phone detects the "answering call to the ear" gesture by using 3D accelerometer(s). Try to answer the call while laying down on the sofa or slow moving the phone to the ear - the screen will remain active and your ear will press everything on the touchscreen..
Hope I am wrong.

@78apb What you say would make sense as to why I can't get any of the sensor apps to recognise it, but if you go to Samsung's own website (https://www.samsung.com/global/galaxy/galaxy-s21-ultra-5g/specs/) and go about 2/3's of the way down the page to the "Sensors and Buttons" section, it definitely states that it has a Proximity Sensor.

@wilsojer then it should be in *#0*# menu, but it doesnt...

@78apb - yes, I quite agree. Think I might try and take this up with Samsung direct - and, no, I won't be holding my breath for a reply ;-)

78apb said:
I am afraid, there is no Proximity Sensor in the s21*. The phone detects the "answering call to the ear" gesture by using 3D accelerometer(s). Try to answer the call while laying down on the sofa or slow moving the phone to the ear - the screen will remain active and your ear will press everything on the touchscreen..
Hope I am wrong.
Click to expand...
Click to collapse
I think you are right I dont see the proximity sensor at all and if i put my hand covering the whole upper screen it still doesnt turn off the screen, so i think it depends also on acceloremeter and gyrometer

I found something that maybe will help us. If you dial *#77692# you will go directly in to the proximity sensor menu and you will see that it is turn OFF. You can turn it ON and it is working but in a few second will go OFF again and i dont know why. But at least we know it is there and it is working.

Related

[Q] Brightness Issue

Hello Guys,
I bought my HTC One from Dubai (Middle east) version 20 days ago, every thing was perfect with the mobile,
Today, the brightness of the mobile went to the highest mode automatically, I tried to reduce it but it hasn't been reduced technically, is there any solution for this ??
Thank You
I just came in here hoping that someone might have had similar to my issue and this seems fairly close.
At least once per day i have to restart my phone because the bightness seems to go so high that i cant control. If i change it, it does not change the screen brightness.
With a restart, it seems to reset the screen back to the regular brightness.
It is getting so annoying have to restart the phone at least twice a day.
I think its a software issue given the fact that it sorts itself with a restart, not sure what to do apart from a hard reset.
If anyone has any ideas or has seen this before, within a thread or not, advice would be appreciated.
Thanks :good:
trigger365 said:
I just came in here hoping that someone might have had similar to my issue and this seems fairly close.
At least once per day i have to restart my phone because the bightness seems to go so high that i cant control. If i change it, it does not change the screen brightness.
With a restart, it seems to reset the screen back to the regular brightness.
It is getting so annoying have to restart the phone at least twice a day.
I think its a software issue given the fact that it sorts itself with a restart, not sure what to do apart from a hard reset.
If anyone has any ideas or has seen this before, within a thread or not, advice would be appreciated.
Thanks :good:
Click to expand...
Click to collapse
for me even with restarting it doesn't work, some time I leave the phone for one hour then I come back to it and find it's brightness adjustment working, then eventually it goes to the highest brightness mode without any ability to adjust it and so on!
some times the Phone responds and adjust the brightness correctly (when I leave the phone and come back to it in an hour), then eventually it goes to the high brightness mode again without any ability to adjust it again and so on.
I'm afraid it might be a hardware problem since it's not happening with other users according to the reviews online !
Some people have been reporting defective light sensors. This basically causes the phone to believe you're in direct sunlight, turning off the button lights and setting the screen brightness to max. If your button lights do not light up when this happens, even when indoors, then you have a defective device. Contact HTC.
sauprankul said:
Some people have been reporting defective light sensors. This basically causes the phone to believe you're in direct sunlight, turning off the button lights and setting the screen brightness to max. If your button lights do not light up when this happens, even when indoors, then you have a defective device. Contact HTC.
Click to expand...
Click to collapse
Thank you for you reply,
but in this case will this happen even if I'm using the automatic brightness mode ??
Thank you
This is a hardware problem. Auto brightness relies on the light sensor. If the light sensor is broken, then the Auto-brightness feature will malfunction.
From http://www.digitaltrends.com/mobile/htc-one-problems/ :
Problem: Proximity sensors not working
A few people have reported that their sensors aren’t working correctly. You may notice that the capacitive buttons don’t light up and this could actually be a sign that the sensor isn’t working. Try covering the sensors (top left) with your finger and see if the capacitive buttons light up. You can also test the sensors using a free app called Android Sensor Box.
Solution: If they aren’t working then it’s a hardware fault and you’ll have to return the phone and get a replacement.
Click to expand...
Click to collapse
Seriously, if you don't like the way your phone is behaving, contact HTC. They will fix it.
I have done the factory reset now and the same thing happened
tareknet89 said:
I have done the factory reset now and the same thing happened
Click to expand...
Click to collapse
Hardware issues can't be solved by a factory reset. You MUST send the device in for repair or replacement.
sauprankul said:
Hardware issues can't be solved by a factory reset. You MUST send the device in for repair or replacement.
Click to expand...
Click to collapse
yes I was just trying to make sure that it's a hardware problem, now I'm contacting htc for help.
Thank you very much I really appreciate it.
Try this. This app will keep your brightness at the level you set it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent using my HTC One from that FBI van parked down the street.
ghostryder12 said:
Try this. This app will keep your brightness at the level you set it.
Sent using my HTC One from that FBI van parked down the street.
Click to expand...
Click to collapse
from the time I installed this app all the problems are solved even without using the app!!!!
wasn't it a hardware problem !
tareknet89 said:
from the time I installed this app all the problems are solved even without using the app!!!!
wasn't it a hardware problem !
Click to expand...
Click to collapse
Sweet. Maybe the apk itself shook something loose.
Sent from my HTC One using Tapatalk 2
ghostryder12 said:
Sweet. Maybe the apk itself shook something loose.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I don't know, even with factory reset the problem wasn't solved, that's strange
Thank you very much :good:
tareknet89 said:
I don't know, even with factory reset the problem wasn't solved, that's strange
Thank you very much :good:
Click to expand...
Click to collapse
Dude, I'm just glad you got it working again.
Sent from my HTC One using Tapatalk 2
Mine doesn't seem to have solved itself with that app
I tried putting my fingers ovetthe proximity sensors and it changed the screen back to normal from the original really bright problem.
Should I contact my network and ask for a replacement? That sounds like a hardware issue to me.
Also, whilst on this, what's the nearest to back up everything? HTC Backup? Does that work well? I'll need to back up launcher settings etc too I guess?
Sent from my HTC One using xda app-developers app
App called Lux Light also works very well.

[Q] Smart Saving Bug - Anyone else seeing this?

Hello, guys. I am encountering what I think is a very weird bug with Smart Saver. I'm hoping that some other people can test this on their systems and if, it's just me, I'm going to return mine for a new unit.
With Smart Saving enabled, the screen will automatically increase and decrease brightness constantly as different pages and app's come up. In my case, the screen seems to flicker almost every time I swipe and I can't stand it, so I disabled Smart Saver. The icon is OFF on the pull down status panel and it's turned off under settings. However, whenever I reboot, I still encounter the screen flickering and dimming constantly (although it seems to be to a lesser degree). If I pull down the status panel, turn Smart Saving On and then off again, the problem goes away until I reboot the system. This is at least encouraging me that maybe it's just software and I can deal with it for a month or so.
Here's what I want someone else to test for me. Turn Smart Saver off. Turn the tablet off and then on again. Pull down the status menu and carefully watch the screen. The open portion of the home screen will dim once (which is normal). On my system, after about another 1/2 second or so, the screen will flicker or dim again slightly. It does this every time, but it might be hard to notice unless you are looking for it. When side scrolling between home screens, sometimes brightness will increase slightly and other times it will decrease. Pull down status panel, turn on smart saver, turn it off again and the problem goes away.
Help, please? Mine is a US model if that makes any difference on build 10.14.1.47.
Thank you very much in advance.
Did you download the used 10.14.1.47 manually from Asus website or was it an auto update from the device itself.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
Manually from the website.
I kinda have the same problem, though on my tab it is only the auto brightness that sometimes will increase/decreased constantly. Disabling Smart Saving or auto brightness helps in my case. I only have the problem when i'm in a room where there's light but the room isn't totally bright, and the tablet is with its back to the light source.
Others can correct me if I'm wrong but the 10.14.1.47 isn't being pushed through the device itself. I'm finding most people are downloading it manually from Asus website. . My estimation, I think Asus is aware that the update has some issues, thus not force updating it through the device until they come out with the latest fix.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
You might be right about the update. Although I was thinking more people should have this issue. Maybe they aren't rebooting their tablet often enough to notice it as once I enable/disable Smart Saver, the problem goes away until I reboot. That is a satisfactory work around, but I was hoping for confirmation from at least one other person seeing the same thing in terms of returning the device. Amazon has decent return terms, so I'll probably wait until the next update and see if that fixes it. Thanks.
I'm on .47 and I have the same issue as well. I also noticed that the brightness will increase 2-3 steps every time I bring up "settings". This is regardless of auto-brightness on/off, smart saving on/off, outdoor mode on/off.
Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...
Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.
Did someone contact the asus-hotline?
derekk1 said:
Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.
Click to expand...
Click to collapse
Same thing here, bought the unit in the US and also experiencing the same awkward behavior. This would actually go away when Auto Brightness is turned off.
I am also getting issues when docked. Sometimes after some time (maybe a couple of hours) as soon as I tilt the tablet to its normal position, I would find it completely off. Had to turn the device back on a couple of times now.
These are too many annoyances for such an expensive unit.
Hope they fix the Auto Brightness setting at least.
Disabling Asus Splendid app in settings -> apps seems to stop this behavior.
vBoedefeld said:
Disabling Asus Splendid app in settings -> apps seems to stop this behavior.
Click to expand...
Click to collapse
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:
Yezariael said:
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:
Click to expand...
Click to collapse
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2
efgyy said:
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2
Click to expand...
Click to collapse
In Switzerland it was OTA :good:
Either download right version from asus.com or wait a bit, I guess it will not take long until it's rolled out everywhere...
Yezariael said:
Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...
Click to expand...
Click to collapse
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.
calimocho said:
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.
Click to expand...
Click to collapse
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:
Yezariael said:
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:
Click to expand...
Click to collapse
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)
calimocho said:
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)
Click to expand...
Click to collapse
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xRevilatioNx said:
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
Click to expand...
Click to collapse
Absolutely. It's just really freaking annoying.
I have it right here in a bright office with fluorescent lights, which I would think would vastly marginalize the amount of light reflected from the display itself back into its ambient light sensor. Merely dropping down the notification column causes visible shifts darker (when coming from a light background) in steps, over several seconds. (and it's in the dock on the desk, so the device isn't moving at all)
So my argument is the algorithm used to determine the backlight of the screen puts to much weight on the white balance of the screen. It's distracting and annoying. And it would be one thing if this only happened on "Auto Brightness," which it does not.

Root and TWRP accomplished

So I just want to give a little status update with proof of what we have going so far. I am still trying to work out the bugs but I have managed to get root and TWRP on the Lg G Watch R (lenok) using much of the same files from Dory the original g watch because almost all the hardware is the same. All I had to do was open their recovery file and throw in our zImage and it booted, and I was actually quite surprised bahaha. And once we have TWRP we can flash anything we want, such as the SuperSU package from Chainfire which enables root for us. But because this is wear most of the rootey things will just allow us to access system files such as say the vibration motor. And I can tell the vibrataion motor on this device is weaker than it is capable of doing because on TWRP the thing's vibration was SUPER strong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
subscribed - looks promising, well done
My next step will be to find a good vibration boost setting and implement it. I can tell it has a very capable vibration motor and can match the Pebble in strength and duration.
Great work! Looking forward to seeing what develops.
tonu42 said:
So I just want to give a little status update with proof of what we have going so far. I am still trying to work out the bugs but I have managed to get root and TWRP on the Lg G Watch R (lenok) using much of the same files from Dory the original g watch because almost all the hardware is the same. All I had to do was open their recovery file and throw in our zImage and it booted, and I was actually quite surprised bahaha. And once we have TWRP we can flash anything we want, such as the SuperSU package from Chainfire which enables root for us. But because this is wear most of the rootey things will just allow us to access system files such as say the vibration motor. And I can tell the vibrataion motor on this device is weaker than it is capable of doing because on TWRP the thing's vibration was SUPER strong.
Click to expand...
Click to collapse
Awesome work, did you tried to relock your bootloader and was you able to grab a complete dump/backup of the Device befor testing the recovery? Coz there is no factory image yet
bluedragon1982 said:
Awesome work, did you tried to relock your bootloader and was you able to grab a complete dump/backup of the Device befor testing the recovery? Coz there is no factory image yet
Click to expand...
Click to collapse
We have stock boot, system and recovery already pulled. That's the bulk of a factory image. I don't plan to relock bootloader so I haven't tested that.
thanks for your work, tonu!
I'v seen that you are investigating various switches and tweaks - I was hoping you could look into the power-saving settings, maybe there is a way to solve the 2 minute bug
2k4ever said:
thanks for your work, tonu!
I'v seen that you are investigating various switches and tweaks - I was hoping you could look into the power-saving settings, maybe there is a way to solve the 2 minute bug
Click to expand...
Click to collapse
I thought the two minute "bug" was a feature to save battery and avoid screen burn. I will look into it but I think it lies in frameworks and I dont wanna go messing with them.
Maybe wear lollipop will change it.
tonu42 said:
I thought the two minute "bug" was a feature to save battery and avoid screen burn. I will look into it but I think it lies in frameworks and I dont wanna go messing with them.
Maybe wear lollipop will change it.
Click to expand...
Click to collapse
It maybe save battery - but a watch that purposefully displays a wrong time I wouldn't call a feature - and if it is at least let me turn it off @google
and it actually should make burn-in worse as the same image is displayed for a longer time
finally, from what I've read, the other AW watches don't have this "feature"
I wouldn't ask you to mess with the frameworks, but maybe the problem arises from a wrongly set power-saving switch or somthing
And yes, I'm hoping that Lollipop will fix it but I wouldn't mind a fix if you are willing and interested to look into it
thanks and good luck!
2k4ever said:
It maybe save battery - but a watch that purposefully displays a wrong time I wouldn't call a feature - and if it is at least let me turn it off @google
and it actually should make burn-in worse as the same image is displayed for a longer time
finally, from what I've read, the other AW watches don't have this "feature"
I wouldn't ask you to mess with the frameworks, but maybe the problem arises from a wrongly set power-saving switch or somthing
And yes, I'm hoping that Lollipop will fix it but I wouldn't mind a fix if you are willing and interested to look into it
thanks and good luck!
Click to expand...
Click to collapse
I've found some things that might point me in the right directions, idk if it will work but you can try to turn off ambient burn in protection all together, while I really do not recommend this on an led display it might fix it. I would estimate after a year or so the burn in would be pretty visible and might affect colors.
tonu42 said:
I've found some things that might point me in the right directions, idk if it will work but you can try to turn off ambient burn in protection all together, while I really do not recommend this on an led display it might fix it. I would estimate after a year or so the burn in would be pretty visible and might affect colors.
Click to expand...
Click to collapse
thanks, but I really wouldn't recommend doing that
besides, from what I can tell, the burn-in protection isn't the problem, as the watch face shifts around as it should, so the screen is redrawn, but the time is not updated simultaneously
2k4ever said:
thanks, but I really wouldn't recommend doing that
besides, from what I can tell, the burn-in protection isn't the problem, as the watch face shifts around as it should, so the screen is redrawn, but the time is not updated simultaneously
Click to expand...
Click to collapse
Thinking about it its a really weird issue. The system knows the correct time because the ambient protection uses the current system time as a sort of random number generator, it takes the system time in milliseconds divides by 60000 and uses that as a variable to shift the screen. Now on the shift I dont know why they didnt make it change the drawn time..... too weird.
tonu42 said:
Thinking about it its a really weird issue. The system knows the correct time because the ambient protection uses the current system time as a sort of random number generator, it takes the system time in milliseconds divides by 60000 and uses that as a variable to shift the screen. Now on the shift I dont know why they didnt make it change the drawn time..... too weird.
Click to expand...
Click to collapse
simple: its a bug
one reason could be that the cpu gets throttled so much that the update doesn't get out
I'v noticed that sometimes the minute hand jumps two minutes, first one and than a second later the hand moves again
and to me it seems to build up: if not activated for extended periods, the time seems to fall further and further behind
Our watch has some extensive power-saving features - at least LG claims that power consumption falls to 10% when in always on mode
I suspect that that's too much, as the other AW watches don't seem to have this problem
@tonu42 hey mate! was randomly checking your tread and saw that you have the twrp gui offcenterd issue like the moto360 tread witch im currently fixing.
i quickly realize that theme should work on both the moto360 and LG G Watch R! So once if i get fix, both should benefit from it!
Moto360 TWRP tread: http://forum.xda-developers.com/moto-360/development/unofficial-twrp-2-8-1-0-moto-360-t2966750
More info what is currently fix and Need to be fixed (including pictures) : http://forum.xda-developers.com/showpost.php?p=57573277&postcount=48
Fell free to add me on G+
mkaymuzik said:
@tonu42 hey mate! was randomly checking your tread and saw that you have the twrp gui offcenterd issue like the moto360 tread witch im currently fixing.
i quickly realize that theme should work on both the moto360 and LG G Watch R! So once if i get fix, both should benefit from it!
Moto360 TWRP tread: http://forum.xda-developers.com/moto-360/development/unofficial-twrp-2-8-1-0-moto-360-t2966750
More info what is currently fix and Need to be fixed (including pictures) : http://forum.xda-developers.com/showpost.php?p=57573277&postcount=48
Fell free to add me on G+
Click to expand...
Click to collapse
Sounds good, I could figure out how to make it look nice on device but I just don't have the time. Full time student and work almost full time, not enough time in the day. Hopefully over the next week I plan to pump some other stuff out related the GWR.
tonu42 said:
Sounds good, I could figure out how to make it look nice on device but I just don't have the time. Full time student and work almost full time, not enough time in the day. Hopefully over the next week I plan to pump some other stuff out related the GWR.
Click to expand...
Click to collapse
no worry man and nice to meet you by the way. im also im the same position ish but do have time but dont have job atm.

General Proximity sensor realy sux!!!

The proximity sensor realy sux on rhis phone, it always turn on when i have the phone on the ear, and there is no fix for it.
I am realy thinking about selling the phone is so anoying!!!
I have same problem, still hope that an update will fix.
The proximity sensor on these devices are ultrasonic rather than infrared. They either use this method to save space or because of issues of "seeing" through the screen, although there are infrared proximity sensors that work behind the display.
They work by emitting a high frequency sound (too high for us to hear) from the earpiece and then listening for that sound in the microphone, and by working out how loud the sound is and what delay there is they can work out if the phone is up against our head, but they are not as accurate or reliable as infrared sensors.
The proximity sensor is only activated when the phone is in a vertical position as it would be being held to the ear. If it isn't very reliable it might be worth calibrating the compass as this may help the device knowing which way up it is.
It works okay on my device.
Hope that helps.
Use "call proximity sensor fix"..I have same trouble my rom is EU Vodafone.
It doesn't have a hardware proximity sensor, Xiaomi use ai to make virtual sensor. I don't know how it work but it really sick.
oouline24hr said:
It doesn't have a hardware proximity sensor, Xiaomi use ai to make virtual sensor. I don't know how it work
Click to expand...
Click to collapse
Imo is so simple to use a front camera as hardware sensor...
krzywojc said:
Imo is so simple to use a front camera as hardware sensor...
Click to expand...
Click to collapse
No, screen still turn to black even i covered front cam with masking tape.
I think they use gyroscope for motion detect.
oouline24hr said:
No, screen still turn to black even i covered front cam with masking tape.
I think they use gyroscope for motion detect.
Click to expand...
Click to collapse
I know that is not a camera but I mean that will be beter to use it for turning off during calling. That was the way of working of the normal sensor in other phones.
krzywojc said:
Imo is so simple to use a front camera as hardware sensor...
Click to expand...
Click to collapse
They can't use the camera as a hardware sensor as it uses a lot of power, not necessarily the sensor itself, but the imaging system on the SoC needs to be powered up, and it is a lot of data being processed just to try and use it as a proximity sensor.
True proximity sensors use a pulsing infrared LED and an infrared sensor, and the infrared bouncing back from something in close proximity can be detected, and this is very reliable.
Because the screen only has a small hole for the camera with narrow bezels, the proximity sensor has to be placed behind the OLED display, and Xiaomi for some reason has not gone down this route on this device. It is possible to have a normal proximity sensor behind the screen and for it to be tuned to work, as many devices do this already, but perhaps for cost or licencing reasons or to save space behind the screen they have not done this.
As far as I'm aware, the proximity sensor is a virtual sensor by detecting if the phone is held vertically, and using an Ultrasonic sound from the speaker being picked up by the microphone, it attempts to work out if near a face or not. If you hold your phone such that it isn't vertical against your face, the sensor will likely assume the phone is not against a face and so will not turn off the display.
On my 11t pro i did not see problem with sensor
I have the same problem....i think ill sell that phone...
Xiaomi is using ultrasonic proximity sensors on majority of their phones. Some users experience issues with it, some don't.
It all comes down to how you hold your phone while talking.
Selling this **** phone, so mad at the sensor ****, wtf is this, if Xiaomi cant fix it with the software then its useless.
Is it ok for the consumer to pay money for a phone that is crappy, i will not take that ****....
When I moved to miui eu The problem is gone, I don't know what is the cause of the problem in the original system, perhaps you have googled to contact
wait, i thought 11T and 11T Pro did have a hardware proximity sensor?
usually kimovil differentiates between 'proximity sensor' and 'ultrasonic-proximity' which they also did with these 2 devices. kimovil is the first thing i check if i see a new phone i like.
monkeytown said:
wait, i thought 11T and 11T Pro did have a hardware proximity sensor?
usually kimovil differentiates between 'proximity sensor' and 'ultrasonic-proximity' which they also did with these 2 devices. kimovil is the first thing i check if i see a new phone i like.
Click to expand...
Click to collapse
They just grab info from many store website compare and rearrange to theirs website with filled micro details. So basically they doesn't know what's really inside the phone. I think they doesn't even have a hardware in there hands.
oouline24hr said:
They just grab info from many store website compare and rearrange to theirs website with filled micro details. So basically they doesn't know what's really inside the phone. I think they doesn't even have a hardware in there hands.
Click to expand...
Click to collapse
oh no, it seems to be true
checked some more websites on this topic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This app has fixed this issue for me. Just set permissions and then all sorted. I stopped notifications because I don't like the permanent notification showing its running, but that's personal preference.
Have that app instaled, it helps but it still turns on the screen when i use the phone..

General New trial update adds lots of great split screen features!!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow.... Finally the update for multi-tasking
what does the update ade for multi tasking? And can you finally use custom icons on default launcher? I'm on x fold 2 and haven't gotten anything like that...
Unfortunately, the update is not yet displayed for me
It's currently out for me. If it isn't out yet, reboot your device and try again.
That being said the software experience is really REALLY similar to the vivo x fold 2. Just as snippy and I've been waiting on the implementation of the dock for a year.
For those with the original vivo x fold, there may not be a huge reason to upgrade given these fresh quality of life upgrades. Especially if you have a vivo x fold with a boot loader unlocked (or if you joined the developer beta/public beta in winter last year). I wish this came out last year like the Samsung ones but I can't really complain.
I still find it a pity that WhatsApp notifications are not displayed on the lock screen/always on screen
NeoGoku123 said:
I still find it a pity that WhatsApp notifications are not displayed on the lock screen/always on screen
Click to expand...
Click to collapse
I can see them with the app AOA: Always on display
I used that app, AOA, a few days ago and it worked great and then the next day never came back on. No matter what I did, even reboot the phone, it never appeared again. I turned the app off and on, I even locked it to the home screen so it didn't get shut down and nothing. Any ideas?
I tried the update. Like it. Only Battery seems to take a hit. Maybe it needs time.....
Cloverfield_33 said:
I used that app, AOA, a few days ago and it worked great and then the next day never came back on. No matter what I did, even reboot the phone, it never appeared again. I turned the app off and on, I even locked it to the home screen so it didn't get shut down and nothing. Any ideas?
Click to expand...
Click to collapse
Exactly the same issue for me with AOA. Never shows up even though I pinned it, set auto start, and battery mgmt to max. I also turned off Vivo's always on display, and all I see the fingerprint scanner image.
gkarkala said:
Exactly the same issue for me with AOA. Never shows up even though I pinned it, set auto start, and battery mgmt to max. I also turned off Vivo's always on display, and all I see the fingerprint scanner image.
Click to expand...
Click to collapse
I managed to get it working again today by turning off the custom time (I had it turn off 10pm to 5am). I ticked the ALWAYS ON box and now it's working again. For now...
Cloverfield_33 said:
I managed to get it working again today by turning off the custom time (I had it turn off 10pm to 5am). I ticked the ALWAYS ON box and now it's working again. For now...
Click to expand...
Click to collapse
Did not work. I never setup custom time, and just verified. Do you still see the fingerprint icon?
gkarkala said:
Did not work. I never setup custom time, and just verified. Do you still see the fingerprint icon?
Click to expand...
Click to collapse
No but even when I had the finger print button on on AOA, it didn't do anything, it was just there for show.
Cloverfield_33 said:
No but even when I had the finger print button on on AOA, it didn't do anything, it was just there for show.
Click to expand...
Click to collapse
okay. then somehow Vivo is killing the AOA process when I turn off the display.
gkarkala said:
okay. then somehow Vivo is killing the AOA process when I turn off the display.
Click to expand...
Click to collapse
I was stumped too. Was just about to delete it till I tried my fix. The stock aod is nice however can't get notifications for anything but phone and messages and the battery percentage is too small to see properly. I like the upside down purple triangle effect though and will go back to that if AOA fails again.
Cloverfield_33 said:
I was stumped too. Was just about to delete it till I tried my fix. The stock aod is nice however can't get notifications for anything but phone and messages and the battery percentage is too small to see properly. I like the upside down purple triangle effect though and will go back to that if AOA fails again.
Click to expand...
Click to collapse
Agree. Vivo's software philosophy is strange: no matter whether it is focused on Chinese or global users. Some of the restrictions does not even make sense even for the Chinese market.
But, damn the hardware is excellent! I am so sick of the narrow screen of Samsung Fold, I am tolerating the UX issues of Vivo. I also got Oppo Find N2, but that software is worse than Vivo.
gkarkala said:
Agree. Vivo's software philosophy is strange: no matter whether it is focused on Chinese or global users. Some of the restrictions does not even make sense even for the Chinese market.
But, damn the hardware is excellent! I am so sick of the narrow screen of Samsung Fold, I am tolerating the UX issues of Vivo. I also got Oppo Find N2, but that software is worse than Vivo.
Click to expand...
Click to collapse
Agreed. I was with Samsung since 2016 before this phone and my lost phone was the z fold 2 which was an amazing phone don't get me wrong but that narrow outside screen annoyed me more and more as the years went on. The fold 5 is going to he just as poor and the pixel fold will be too short and have problems of its own, plus just as expensive. Vivo was a no brainier, hundreds cheaper, amazing inside and outside screen, ridiculous battery life and charging speed, 1800 nits brightness plus much more. The software is definitely a learning curve and like you said, some things don't make sense at all. I'm struggling with notifications and I still, no matter what I do, can't get floating notifications for WhatsApp when I'm using the phone. If phone is on standby I get the message preview on lock screen, dark mode or not but when using the phone all I get is the icon at top left. I have every setting to allow notifications, I'm so stumped. Weirdly I'll get the message preview if I already have a WhatsApp message unread and then someone else sends, me a message. I get a line from each new message then. Very frustrating.
Cloverfield_33 said:
Agreed. I was with Samsung since 2016 before this phone and my lost phone was the z fold 2 which was an amazing phone don't get me wrong but that narrow outside screen annoyed me more and more as the years went on. The fold 5 is going to he just as poor and the pixel fold will be too short and have problems of its own, plus just as expensive. Vivo was a no brainier, hundreds cheaper, amazing inside and outside screen, ridiculous battery life and charging speed, 1800 nits brightness plus much more. The software is definitely a learning curve and like you said, some things don't make sense at all. I'm struggling with notifications and I still, no matter what I do, can't get floating notifications for WhatsApp when I'm using the phone. If phone is on standby I get the message preview on lock screen, dark mode or not but when using the phone all I get is the icon at top left. I have every setting to allow notifications, I'm so stumped. Weirdly I'll get the message preview if I already have a WhatsApp message unread and then someone else sends, me a message. I get a line from each new message then. Very frustrating.
Click to expand...
Click to collapse
Exactly the same issue for me for Whatsapp messages. No floating message notifications.
gkarkala said:
Exactly the same issue for me for Whatsapp messages. No floating message notifications.
Click to expand...
Click to collapse
OK so it's not just me. It's so weird isn't it. Hopefully it's something that can be fixed soon.
Google messages notifications works in dark mode now

Categories

Resources