Related
Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000 using XDA App
Mh? Why not pressing the home button during call.
Screen is enabled then...
Anyway MIUI got this option to switch it off.
Don't know if this setting is available in Stock ROMs.
screen should go back on when you move your head out of the ~5cm sensor radious. if it is not happening there are two possibilities:
- something wrong with firmware -> reflash phone with pure unrooted samsung firmware and check if problem persist
- someting is wrong with proximity sensor -> use warranty and send it to service center with proper description of the problem
Thanks for the replys the home button won't work as the proxy is up the spout had it checked the chip is blown, when u press the home key won't work as the phone is trying to find the proxy then eventualy it will crash and force close.
No software update will do it as its a hardware fault unless it turns it off so will have a look at the one you suggested.
There is def a stock version but i fear it is only on the s2 to turn blank screen off il check my bro's firmware, till then keep the suggestions coming in thanks....
Sent from my GT-I9000 using XDA App
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
SADист said:
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
Click to expand...
Click to collapse
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)? Is there a way of hardware disabling the sensor? the software testers report 0.7 mA leakage on a sensor (which is faulty anyways)
lusjash said:
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)?
Click to expand...
Click to collapse
You can do this:
Part of my m7 touch screen isnt working .. its kinda crazy cuz the phone never got dropped .. i saw that many people had that problem its between this two parts of screen that doesnt work theres a line that working..sometimes the touch isnt working at all !!
(when people call me sometimes).
its really disappointing cuz i like htc very much !
another problem that im having and saw that many people has it too : screen brightness always go maximum ! auto off for sure but still the brightness making problem tryed to reset the phone didnt help( not hard reset) it sucks to have a bunch of problems in a new phone ..
please please help me !
post.img.org/image/6naksobvx/
delete the dot in postimage ! sorry but this photo will help you understand and i have to share it !
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Val D. said:
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Click to expand...
Click to collapse
some times the screen back to full funcanlity
and please help about the other problem with the brightness .. its look like one of the sensors is broken in the phone .. maybe its the problem ?
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Val D. said:
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Click to expand...
Click to collapse
lollipop not root and other .. i deleted everything , did a soft reset not the hard type . no but i download lux to see if its help and it doesnt help either
The only thing left to try on a software side is factory reset the device. Many users report it clears various OTA Lollipop update bugs. The process takes about 10-15min, the OS will go through Android system update process again and the device will be reset to factory default state (don't forget to backup all your data). During the initial setup process don't restore your online account backup, make clean setup. Test the screen and digitizer before installing any 3rd party apps. Make sure your screen protector (if you have one) is not bugging the digitizer. If you have the same issues, then it's definitely hardware related (screen/digitizer assembly or connecting ribbon cables).
Hello everyone.
I am on build number EVA-L09C02B123
My screen is not very responsive in some areas, sometimes in more than a few areas. It needs a firmer press.
Is this an issue address in the 30+ firmwares, or is it my device? anyone else experiencing this?
Thanks
I only registered to confirm this issue on my P9 also!
I was starting to think my finger is failing
Just for correctness EVA-L09C432B136
evak2979 said:
Hello everyone.
I am on build number EVA-L09C02B123
My screen is not very responsive in some areas, sometimes in more than a few areas. It needs a firmer press.
Is this an issue address in the 30+ firmwares, or is it my device? anyone else experiencing this?
Thanks
Click to expand...
Click to collapse
same here on EVA-L09C150B121
I have a similar problem when I hold my phone in both hands. The palm of my hands are touching the screen because of the small bezel and that causes the touchscreen to be unresponsive in other areas. I'm also having the Vodafone version EVA-L09C02B123. Huawei should add some kind of detection like Apple has on the iPad since the Mini. That would fix it.
So it very well could be the firmware version.
I also had a Carphone Warehouse one at 131, and that worked like a charm. I guess we need to wait for Vodafone to roll out an update
I wrote already a mail to huawei regarding some issues, but i did not get an answer yet
JohnDaviz said:
I wrote already a mail to huawei regarding some issues, but i did not get an answer yet
Click to expand...
Click to collapse
it would be curious to see which model colours do which.
I have a white from CPW which was pre-scratched out of the box, with a hairline scratch visible against lamp lights - putting a tempered glass on hides this 100%. Still I wanted to return it, and get a black.
My black had terrible responsiveness issues. My white has none, they're almost not there. I think it could after all have something to do with the front panel's alignment to the digitizer.
It is so amazing that in this day and age we still have to worry about s**t like that (light bleeds, responsiveness, scratches out of the box)
I have this problem to and problem when change local memory to card sd. My phone freeze
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
L09 with 136 here (Titanium grey) and luckily I have no issues.
Good to know mate. I am starting to think this is a problem very similar to the Note 4 where in some units the glass panel was misaligned which required a firmer press on the back button.
I will try another dark from. Vodafone UK. They are on 123 version but the unit also costs 300 with them which is a steal
did anybody try to activate glove mode in settings? may be the display become more responsive
Good idea. I will try that.
I have some kind of theory.
When i turn display brightness up between 60-100% and start playing cpu intense games the following happens:
(Auto Brightness turned off)
1. Phone starts warming up significantly from the upside and continues to get warm until the bottom.
2. Display brightness suddenly starts changing (Thermal throttling!?)
3. Responsiveness decreases
4. Phone gets really really warm
(Auto Brightness turned off - between 30-50%)
1. Phone does not warm up so much. Still getting warm but okay.
2. Display brightness does not change anymore
3. Responsiveness much better with nearly no failures
I have the feeling that in B135 the phone was not getting as hot as in B136
Sometimes when i open phone and try answer to whatsapp, screen is very responsiveness.. And im using google keyboard.. Anyone got problem like this?
Having the same problem playing games. EVA L19 136. I'm sure it's a software bug. Waiting for an update...
Ragzn said:
Having the same problem playing games. EVA L19 136. I'm sure it's a software bug. Waiting for an update...
Click to expand...
Click to collapse
How did you installed 136 on EVA-L19? 130 seems to be the latest version
It was an update that came automatically when I updated the phone. I live in Romania.
I'm also having screen issues but it seems to be the opposite of what everyone is describing :
- Unwanted touches even though I'm not touching the screen. Can happen several times in a row in the same area
- Bad scroll detection : the device often recognizes the first touch of a scroll as a selection, or interprets a selection while scrolling
- Bad long-touch detection
I'm going to send the device back to Amazon but I'm fearing this is not an hardware issue and knowing Huawei is really sloppy when it comes to sorting issues, I'm thinking it might be best not to get a new P9.
PS: I'm on build B136.
What do you think ?
I think it's a software issue with B136. What model do you have? Does your problem happen at certain times or all the time?
I have P9 EVA-L09 bought in France.
It happens almost all the time but to a certain degree : sometimes it's very subtle, but sometimes the device goes crazy and starts taping on its own, opening links I didn't select, etc. Quite a nightmare.
Have you tried to Factory reset it? Or manually install some other verion of the official rom?
I am using xperia z3 compact since about 1 year. Now i suddenly got a serious issue that atonce my soft navigation keys(Back+Home+Recent Apps Buttons) has stopped working. First there was some trouble upon touching keys but after next day they stopped working at all and were just like dead. I made a factory restore but no use. Then i flashed a fresh copy of new downloaded firmware but problem still persisted.
But strange thing is that if its hardware problem then why these keys are working in "Gloves Mode".
I was on Android version 6.0.1 build: 23.5.a.0.575 at the time of problem occurred. Then i flashed build: 23.5.a.0.570 but no use. Please help.........
I solved this by going to back to kitkat
Same as same problem with you @libra857 . Really it solve the problem going back to kitkat? Thanks a lot @sparkys I'll try to do that. Thanks Thanks Thanks. BTW what firmware do you use?
the same problem suddenly i was Android version 6.0.1 build: 23.5.a.0.575 at never halted i put my phone on charger next morning found the problem i tried factory reset then downgrade to 23.4.A.1.264 but no thing solved it until i activated glove mode it helped me to use my phone but not solve the problem
Sparksys said:
I solved this by going to back to kitkat
Click to expand...
Click to collapse
Really? Then you upgrade or leave it at KK?
I've had the same issue for 2 months now, the nav bar doesn't work and also a small section of the upper screen doesn't as well. Download a screen test app and see for yourself.
If possible, take the issue to Sony Care and see if you can make them fix it. I've haven't had such luck and taking into consideration the rather expensive (around 150 bucks) and possibly pointless attempt at getting it fixed, I'm stuck with a partially ruined screen. I use LMT Launcher to sort the the issue partially.
Hi guys, I have the same problem on my Z3C. I just flashed it back to KitKat and it didn't work at all, in fact now I'm stuck at the first screen unable to chose between the languages because the soft keys screen part doesn't work. So I wouldn't recommend doing that.
had this problem too since 16 months old. to overcome I had activated assistive touch, auto-rotate and downloaded smarttouch (its free from play store). It was a hw prob and screen needs to be replaced.
another "fix": change the resolution from 720x1280 to 600x1000 (230 DPI). Looks crappy like my old sola, but at least I can use my phone. I use Window Manipulator.
found it here
http://talk.sonymobile.com/t5/Xperi...home-screen/m-p/1165534/highlight/true#M24637
can someone explain to me why this fix works?
I was playing around with my brother's z3c with same problem. To check if theres a hardware problem, I enabled "show touches" in developer options. I found out that the lower part of the screen (where the navigation buttons are) doesn't work. It missed the buttons by a few pixels. The "fix" SHP5 suggested works because it makes the navigation buttons bigger does getting inside the working part of the screen. The other work around (glove mode) works because it makes the touches bigger to compensate for the gloves does making the touches go inside the navigation bar area even when its detecting the touches a bit above.. This give me the idea of my workaround.
WORKAROUND:
-root
-install xposed
-install Xperia/AOSP NavBar module (z3c is not in the compatible devices but I tested and it works)
-enable module
-change navbar height to what works for you (mine is 120%)
-reboot
NOTE: might overlap other apps if nav bar is too high.
The phone is on 23.5.a.1.291 firmware. Root, Recovery and xposed are available in this firmware.
Please leave thanks if helpful....
It's not hardware! In recovery mode the keys are working without a problem! It just happened like this, I'm desperate...
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: