Proximity sensor broke after update to Android 11 + OneUI 3.0 - Samsung Galaxy S10 Questions & Answers

Hi!
I have a Galaxy S10 G9730 (Snapdragon) and last week I've installed Android 11 + OneUI 3.0 via OTA. The phone started to give so much problems, battery drain, rotation sensor stucked until reboot, etc... I ended up hard-reseting it to solve problems.
All of them have dissapeared but proximity sensor is not working anymore, I tried some apps to test it but none of them detects anything. Also on phone hardware test "*#0#*" I didnt found anything to test proximity sensor.
So any of you had the same problem? Maybe it's some kind of hardware fail? I'm like 80% sure that it stoped working after that last update but not 100%....
Thanks guys!

Have you checked the Galaxy Store and Playstore for system apk updates?
If you could try reflashing it... it's very unlikely it's a hardware failure, at least with the proximity sensor.
May be a bad flash or it is the firmware which is probably the most likely.
I'm still running Pie because it's a lighter, faster OS that I find easy to use. The Q and especially the 11 "upgrade" would slow my 10+ down and reduce/destroy functionalities I use.

blackhawk said:
Have you checked the Galaxy Store and Playstore for system apk updates?
If you could try reflashing it... it's very unlikely it's a hardware failure, at least with the proximity sensor.
May be a bad flash or it is the firmware which is probably the most likely.
I'm still running Pie because it's a lighter, faster OS that I find easy to use. The Q and especially the 11 "upgrade" would slow my 10+ down and reduce/destroy functionalities I use.
Click to expand...
Click to collapse
Yes, everything is updated. Afer a reboot it worked again, but after some hours of use, proximity and rotation sensor started to fail again.
Android 11 update its a complete failure, I'm thinking about going back to android 10.

Rul3s said:
Yes, everything is updated. Afer a reboot it worked again, but after some hours of use, proximity and rotation sensor started to fail again.
Android 11 update its a complete failure, I'm thinking about going back to android 10.
Click to expand...
Click to collapse
That just sucks.
If you can tolerate it Sammy should eventually punch out an update for that issue.
It's possible you got a bad flash. Anymore I'm inclined to leave everything on the factory load if it's running well
I get damn tired of playing footsies with cactus...
Q isn't being well received as Google -tries- to kept its poor adoption rate secret.
11 is a real whack job. Google is on a losing streak. Lol their next OS will be code named Snake Eyes
It makes upgrading my hardware platform a big no go... no good OS available for the hardware.

Related

Please help. Nexus 6 rotates all images captured.

Hello..
Really hope someone can help me, as I'm starting to loose my patience
So whenever I take a picture ( have tried with Google Camera, snap camera + open camera) the images get rotates 90 or 180 degrees.
I have tried on 3 roms (stock + root) Sinlessrom (based on google) and a AOSP rom. All same result.
It just suddently started appening like 1 week ago, I did not flash anything, so maybe google updated something through the playstore?
Anyway, REALLY hoping for som help.
Nexus 6 international version.
This happened to me also, it is a Hardware Defect. Your gyroscope in your phone is broken, and your phone's warranty will allow you to get a free replacement.
slickromeo said:
This happened to me also, it is a Hardware Defect. Your gyroscope in your phone is broken, and your phone's warranty will allow you to get a free replacement.
Click to expand...
Click to collapse
Damn, is this really the only possible solution?
The weird thing is, whenever I reset my device it works for maybe 5 mins undtil all updates are downloaded, then its wrong again. Same if I downgrade google camera from 2.5.x to 2.4.x it then works for like 10 mins. No idea what is going on

Auto brightness not working correctly after 6.0.1 update

Several users (including myself) have pointed out that the automatic brightness doesn't work as before the 6.0.1 update.
Here are some of the reports:
kom-pakt said:
One of the few drawbacks I noticed just today is that the auto brightness seems a lot less responsive. For example it's very sunny today and most of the time when pulling the phone out of my pocket the display was still stuck on low brightness. It might just be a conflict with xposed or something else I'm running.
Click to expand...
Click to collapse
GFixx said:
I have a bug with automatic screen brightness, if I unlock the phone at the sun I do not see almost nothing
G800F ITV 1CQA1
Someone can confirm?
(GPS and Volume seems fine)
Click to expand...
Click to collapse
milad9896 said:
I also have this problem sometimes
Click to expand...
Click to collapse
So far I've tried running the phone without anything on it like Xposed or any apps beside the stock ones and it hasn't fixed the issue. What I do know is that it's definitely not a hardware issue since the light sensor works as it's supposed - you can test yours by entering the service menu by typing *#0*# from the dialer. I am currently running the German DBT firmware but I'm currently in the process of flashing the South East Europe SEE firmware which is different only in the security patch, so if the problem persists then I will know for sure it's not a DBT-only problem.
How many of you have this issue as well? Also, which version of the firmware are you running?
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Myke72 said:
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
Click to expand...
Click to collapse
I am currently running the South East Europe (SEE) firmware but I haven't tested it extensively so I can't say if it's any better.
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
So Samsung's solution for this is to use manual brightness? Really Samsung?
I have the same after upgrade to 6.0.1, it's unbelievable such a bug in official release
any fix for this?
I installed Auto Brightness app, but it seems Samsung display goes above 100% in sun, third party apps can't do it
Does anyone have realy bad battery Problems too? (See my thread...)
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
I have the same problem - I made a video of it below. It's a serious usability problem - makes it very hard to use in sunlight.
As a kind of workaround you can put your thumb over the light sensor as you wake it up, then it will wake up dim but still visible. Eventually it will adjust and brighten to match the sunlight. But this is slow and awkward and needs two hands.
The reply you got from Samsung is ridiculous. For a start, the stronger the external light source, the stronger the brightness of the device - they have it the wrong way around. Anyway, it is obviously a major usability problem and I can't believe they are dismissing it. (And manual brightness is not an answer of course.)
Phone specification:
Model number: SM-G800F
Android version: 6.0.1
Baseband version: G800FXXU1CQA1
Kernel version: 3.4.39-10294723 [email protected]#1 Wed Jan 4 12:03:16 KST 2017
Build number: MMB29K.G800FXXU1CQA1
SE for Android status: Enforcing SEPF_SECMOBILE_6.0.1_0033 Wed Jan 04 12:28:05 2017
It works fine on my G800H with latest Polish stock ROM
I don't use to write in the forum, but I must say 'me too'. If someone knows a working Marshmallow ROM for the G800F. The thumb "workaaround" is the only one working for me..
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
kom-pakt said:
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
Click to expand...
Click to collapse
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
alex3453 said:
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
Click to expand...
Click to collapse
Use the official Samsung website (for your region) to report the issue. Browse a bit and you'll find the form.
It's strange that the number of people affected by this issue seems relatively small, keeping in mind that XDA is a forum where a typical user is usually a power user. Also it's not a region-specific issue or caused by an app or something else. For example I thought that maybe Xposed is causing a conflict so I did a complete wipe and flashed a fresh firmware, used the phone like that without any apps for a couple of days but the autobrightness issue was still there. Tried a different firmware version as well but nothing helps. Again, it's definitely not a hardware issue - test yours by typing *#0*# from the dialpad to enter the service menu and test the sensor yourself.
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
ffoucault said:
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
Click to expand...
Click to collapse
bravur said:
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Click to expand...
Click to collapse
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
foulke said:
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
Click to expand...
Click to collapse
Did you try the basic stuff like reflashing the firmware and such?
kom-pakt said:
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
Did you try the basic stuff like reflashing the firmware and such?
Click to expand...
Click to collapse
No. I don't want to use Odin for the moment.
By the way I installed Lux, and it works fine.
I'm surprised you're happy with Lux, official Samsung can do much more brighter screen in strong sun then Lux
By the way, I removed Lux since. Because it requires too much app permission than I think it should (contacts...)
So I'm looking for an another solution
Good news!
Yesterday I jus tried to install the latest firmware available on sammobile (for G800F) - the one for nordic countries -.. and now the brightness control is working perfectly!
Seems that this 'not' problem was fixed in latests releases :good:

New firmware?

Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
echocae said:
Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
Click to expand...
Click to collapse
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Hawkysoft said:
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Click to expand...
Click to collapse
well if B is Beta.. then A.. is Alpha... so we need F.. Full Version...:laugh:
That looks legit and could be the new release. I wouldn't pay much attention to the letters. There's new builds of touch and camera firmware, which could mean lesser issues with the fingerprint sensor and the camera errors.
Apparently nokia said via Twitter that they had some one time issue in getting the security release on time. That we should expect a FM this week. Not sure if it is true. But I'm disappointed that they don't honor the Android One promise
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
My stable version has a F in the end
isopure said:
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
Click to expand...
Click to collapse
Yeah for the camera I don't mind to wait. But for the security updates I do mind to wait as this is a separate update that has nothing to do with camera
There is updateV.4.22C .Just instaling ( in Poland )
Netherlands as well
India!
Also in Spain.
New update build number
I just updated to the latest update, fingerprint enrollment hasbeen update, Its quite reliable and has a more success rate, still slow but I don't mind it since not tell me to press harder like before, hope it gets better with future updates.:laugh:
Never mind fingerprint. Camera is what most people bought this phone, and it was horiblle also ( I mean app ).Lot's of bugs
Any release notes?
Just applied update
Fingerprint reader is now perfect though aesthetically the small brackets around the thumbprint distract. Can't say anything about camera.
250Mb. Took a very long time to install over a fast wifi connection. I was afraid that I had bricked my phone.
United States. T-Mobile. Unlocked phone.
The bug in translation in Camera app still present (bokeh). Fingerprint sensor almost as ****ty as it was. I deleted all fingerprints and added four new. Press harder...
FP still ****.. maybe due to screen protector too thick...
Camera is improve littlebit Manual still have bug eventhou u set the shutter speed still go automatic
Pro mode is still buggy i think..When cam set to "ISO prority" ( ISO set on 100 ) assuming, that camera mesures exposition automatically, the time suppose to be selected in auto position, and it all suppose to give proper exposition. But when ISO is set , time goes itself to 1/33 sec, that gives total underexposition. Time has to set manually based on the display preview to have things to work. So does it mean, that in Pro mode exposition hase to be set manually, or it is another bug? Timer sound in Cam app ,still not working correctly
No... In pro mode everything is manual

mi 9 multi touch problem

My mi 9 seems to be able to only detect 1 finger. Completely wiped phone and problem still persist. Anyone with same issue or able to fix issue?
I have the same problem. Have you found any solution?
youtube.com/watch?v=dLa-oHLig7U
I have that same problem. Could you help
Happened the same issue to my Mi9. Multi touch was working normally but suddenly it stopped working while I was zooming on a web page. Then I made a factory reset but still didn't work. Today I updated to Miui 12 hopping the problem would be solved but still no success. I think this bug is related to Android 10 as I saw elsewhere someone rolled back to Miui 10/Android 9 and things got to normal. On the other hand this is not a hardware failure for sure since multi touch keeps working normally on apps running in game turbo mode.
So, has anyone found how to kill this annoying bug?
Thanks for any help.
ive been searching everywhere how to fix this. i already email xiaomi about this issue. still didnt find clue how to fix this bug. still hoping that xiaomi will fix this issue.
This issue is a shame for Xiaomi!
As far as I know the only solution is to downgrade to Miui10 and stuck on this version or take the risk to upgrade to Miui11 (not recommended for obvious reasons) or the fresh new Miui12. So far I've been using the "turbo game" thing to workaround the bug. I had to install some alternative apps from Google Play (such as Chrome Beta, other gallery app, Google Maps Go...) to use instead of the stock apps so I can use them with "turbo" and get pinch to zoom working. This is not the best way to solve the issue -- the ideal is to get multi touch back working again without the need to resort to any tricks -- however it works very well. Maybe one of these days I'll get some patience to setup the good old Miui10 again...
i also have this ghost touch on the upper part of the screen. it came same time as the multi touch issue. it cant even fix by game turbo. i cant even play games normally like moba or fps game. i dont know if its just me have this ghost touch issue. its a big shame for xiaomi flagship phone?
No news about this issue? Everything works fine with Pixel Experience in my MI9 but multitouch. I remmember I solved another problem (auto-rotate didn't work for the display) and I solved it flashing only last version of "persist.img".
Same here bro!
I bought my Mi 9 in February and everything worked well. I also upgraded to MIUI 12 with no problems at all, then suddenly multitouch stopped working.
If I flash Pixel Experience will the problem be solved?
03jack said:
Same here bro!
I bought my Mi 9 in February and everything worked well. I also upgraded to MIUI 12 with no problems at all, then suddenly multitouch stopped working.
If I flash Pixel Experience will the problem be solved?
Click to expand...
Click to collapse
No way, Installing PE doesn't solve the problem.
I'm going to try it with new kernels and FWs.
ommerus said:
No way, Installing PE doesn't solve the problem.
I'm going to try it with new kernels and FWs.
Click to expand...
Click to collapse
Let me know if it works
03jack said:
Let me know if it works
Click to expand...
Click to collapse
It doesn't work at all... nothing... so tired of this...
ommerus said:
It doesn't work at all... nothing... so tired of this...
Click to expand...
Click to collapse
Try to flash MIUI 10... I read somewhere it should work, because MIUI 10 is built on Android 9, which doesn't have this issue
same i have this issue, i tried miflash. the only workaround are miui 10 and game turbo method.
also i have this nonresponsive part of the upper screen, right where most game analog button placed. idk if this "dead touch" is connected to this multitouch issue
This was the first and probably the last Xiomi I bought. Back to iOS. Bought a second hand iPhone 11 in mint condition. Working rock solid! Crap Mi9!!!
renz555666 said:
i also have this ghost touch on the upper part of the screen. it came same time as the multi touch issue. it cant even fix by game turbo. i cant even play games normally like moba or fps game. i dont know if its just me have this ghost touch issue. its a big shame for xiaomi flagship phone?
Click to expand...
Click to collapse
Gnonymous7 said:
same i have this issue, i tried miflash. the only workaround are miui 10 and game turbo method.
also i have this nonresponsive part of the upper screen, right where most game analog button placed. idk if this "dead touch" is connected to this multitouch issue
Click to expand...
Click to collapse
Have the same problem here!!!
Upper screen DEAD
Annoying ghost touch on upper screen
Have to type multiple times because It keeps ghost touching...
Can't sell the phone, because of these issues...
Miss my Galaxy note
Is there a fix to this issue now? GameTurbo enhances the touch so that multitouch works. There must be a fix to this.

Pie update broke camera?

Hi there all, I'm a decently smart man and have tried just about everything I understand how to do to get my wife's camera back up and working correctly b the app is laggy AF when launching. Installed 3rd party camera and even the newest gcam port. No matter what one I use the app loads but the camera doesn't become usable for 20-30 seconds after. I've tried clearing the data and cache of app. I cleared cache partition. Factory reset and even tried using Google lens. Once the camera is up and running it's a decent photo taking device but truly when it was on Oreo everything was fine. Still soft and not perfect compared to iPhone and pixel but for what it is the v40 had shot decent photos. I don't know how to unlock bootloader and install a KDZ or TAR file if that's something I'll be needing to do.
I've searched reddit and XDA most say everything I've tried and most have worked for others sadly not my case. Thanks in advance for all help here.
I know LG bridge is a think just don't know if I can down grade the OS via that way. Long post sorry
You have to understand that an android operating system update by a manufacturer is **** and slows down performance or break the features. If your phone came in on android 8 then dont go to 9 as youll notice its slower, android 9 is smooth but the real test is when your using browsers and apps like games,facebook etc. Ive owned many types of android from BLU Studio, Samsung, LG, Acetel, and they are **** when going past the OS it came in on first day release.
In terms of downgrading the new LG UP is safe to try KDZ downgrade as if it detects a higher antirollback it will alert you and stop.

Categories

Resources