Hello,
I have a Samsung Galaxy s6 Edge G925F with custom rom, i have a problem with my sensor.
I turn my auto-brightness in ON and nothing chang, it's always stay at the same level of brightness, i tested it, if it was a hardware problem with calling "*#0*#" but not, it work perfectly in that.
and for the proximity sensor, when i call someone, the screen turn automaticaly in black, same think, i tried to test hardware, it's work, when i call someone with What's App for exemple, it's work, but it's not work with phone dialer.
(Sorry for my bad english, i'm french)
Can someone help me ? I tried an other rom, same problem, other bootloader / modem, same again.
Same issue here! Don't know what the problem is. Sensor is working when being tested, but somehow system is not receiving that info. Factory reset did not help either. I am on stock everything (5.1.1).
and you have no problem with brightness in mode auto ?
Auto brightness is not working either. It is always at same output value, no matter what I do. And also navigation buttons are not lighting up anymore.
Phone is all stock. Not sure if I should try with other roms...
Sent from my Nexus 6 using Tapatalk
Oh, we have the exact same problem, I just noticed that, my softkey lighting doesn't work too.
Have you got a problem like that, you put your headset's jack into your phone, and It's not detected by your phone ? İ have that issue too, I bought a jack, dock replacement for replace this part, I will tell you what happening next.
I saw your thread, did you disassembly your s6 ? By you or other guys.
If you find any solution to this problem please report it here and I will do the same. Hope we will be able to fix it .
Sent from my Nexus 6 using Tapatalk
Emzelim said:
Have you got a problem like that, you put your headset's jack into your phone, and It's not detected by your phone ? İ have that issue too, I bought a jack, dock replacement for replace this part, I will tell you what happening next.
I saw your thread, did you disassembly your s6 ? By you or other guys.
Click to expand...
Click to collapse
I just checked this, and unfortunately it's not working...not recognized by the phone . Guess it's identical problem.
I did not touch any internals...just sent this phone for repairs, but they did not fix it because they found out that someone was already open it before. Now I do not know what to do.
Sent from my Nexus 6 using Tapatalk
Okay, then, The Phone was already opened before, I will tell you if I found something for that.
Emzelim said:
Okay, then, The Phone was already opened before, I will tell you if I found something for that.
Click to expand...
Click to collapse
Yes, as I wrote in my original thread phone had a problem with faulty battery. It was refurbished phone and seller stated that it has 2 years of manufacturer warranty, but as it turned out warranty was void because someone damaged that battery before and tried to fix it with some tape.
btw. everything else was working fine before we sent the phone for service. When they returned it all these problems started. I have ordered new battery and will replace that by my own I guess because Samsung is not responding to our messages. I guess my girlfriend will have to live with these issues if we are not able to fix them...
if you think your auto brightness is not working check out this app. If that doesn't work then your sensors are faulty/defective and contact Samsung support or your authorized reseller
https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
paviol said:
if you think your auto brightness is not working check out this app. If that doesn't work then your sensors are faulty/defective and contact Samsung support or your authorized reseller
https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Click to expand...
Click to collapse
As we mentioned already...every sensor checking app is reporting that senors are working just fine. I removed the battery so can't try this app right now, but will definitely check as soon as I can, thanks.
Update regarding my situation: Since everything failed to fix this device or receive our money back, I decided to open the phone and check if anything else is wrong with it (besides battery) and guess what...audio jack port was completely broken. Plugging in headphones was working before it went to official repair centre, and now I know they broke it. But still I can't do anything about it because Samsung is refusing to fix it. My best bet is to replace that part together with battery and live with other issues.
Worst service I have ever experienced...
Ok so, I will receive this replacement part (jack) this week, I hope it will fix the other problems too.
I'll tell you what happen after that.
Emzelim said:
Ok so, I will receive this replacement part (jack) this week, I hope it will fix the other problems too.
I'll tell you what happen after that.
Click to expand...
Click to collapse
Please do! I also ordered whole usb connector board with headphone jack on it. Let's hope it will work.
btw. I just contented old battery back and tried this app. It is working great, so sensors are fine.
Hıı, I have A good news for you, I just replaced the usb, Jack part and all is working back, proximity sensor, auto brightness control and jack.
Good luck for you ?
Emzelim said:
Hıı, I have A good news for you, I just replaced the usb, Jack part and all is working back, proximity sensor, auto brightness control and jack.
Good luck for you ?
Click to expand...
Click to collapse
Same here! Just replaced and packed everything up few minutes ago. Working great!! Finally! I'm glad we managed to fix this one ...
Just dry up the edges. Try to blow the corners. It is just a little bit wet because the corners have little gaps that let water and dust in. I blow dried my phone and it fixed the problem. If you try to wipe screen with water and it gets inside the edges, problem comes back again
Ich have the same problem. But how can it be a hardware issue when the sensors are working in test module? I don't want to send it in :/
Mine was having this exact problem and was solved by an update I didn't know existed. Go to where you find your updates and download any available. Mine worked great again afterwards. If that doesn't work, Try clearing your cache partition.
prov1kenobi said:
Mine was having this exact problem and was solved by an update I didn't know existed. Go to where you find your updates and download any available. Mine worked great again afterwards. If that doesn't work, Try clearing your cache partition.
Click to expand...
Click to collapse
we are already finishing the year 2017 and apparently samsung continues to present the same defects !! Were you able to solve your sensor problem? Please take a look at my post and please help me!
https://forum.xda-developers.com/galaxy-s8/help/sensors-android-update-please-help-t3721874 join please <<<<<<<<<<<
Related
sometimes upper part of my sola does not responds and it is an temporary problem
whenver this touch problem occurs
I clesn the screen with cloth and it works fine.
can anyone have solution for this problem?
and hardware of the phone is not the problem I think.
screen shot for touch screen service test..
Sola
shailen007 said:
sometimes upper part of my sola does not responds and it is an temporary problem
whenver this touch problem occurs
I clesn the screen with cloth and it works fine.
can anyone have solution for this problem?
and hardware of the phone is not the problem I think.
screen shot for touch screen service test..
Click to expand...
Click to collapse
Me too i have the same problem but mine is the lower part near at the delete icon for keyboard. Please help. I installed swiftkey3 but still. sometimes it responds sometimes it dont.
AllanCaladiao said:
Me too i have the same problem but mine is the lower part near at the delete icon for keyboard. Please help. I installed swiftkey3 but still. sometimes it responds sometimes it dont.
Click to expand...
Click to collapse
I had the same problem with ICS, but i downgrade to GB. First I did the "sunbath", and works, but some apps started to crush. So I decided to go back to GB. Until now, it works flawless. I lose a couple of functions, but it's better than the "sunbath".
UPDATE1: After a couple of weeks the problem came back. Anybody, got a solution other than throw to the garbage the phone?
UPDATE2: Well, I really don't know what makes appears the touch screen problem again, but since I install GB, I got only once that the screen didn´t work and only for a short time. I've been using for a couple of days and I didn't have any trouble at all. I'm guessing that is like a bug software problem, but if someone find a final solution, please post it.
Hey!
Hey guys. I also have the same problem. My service test in touch screen was so terrible. Also behind delete button in keyboard. Lower part right side of the screen. What shall we do?
Additions.
Haha. I forgot the attchmnts
same problem
Same Problem here to.
Anyone know something about this problem?
Anybody got a workaround?
Thanks
Another one with the same problem, mine in the low right side of the screen. Im using the glove mode otherwise its impossible to use it. Somebody with JB, which disables glove mode, has resolve the problem??Im asking this because while its not responding, I restart the phone an enter CWM, and there, its responses perfectly.
So, somebody with this problem, has flashed the any port of JB and resolve this issue??
ok, I´ve tested with JB and it became more responsive but also having the problem.
I left the phone with direct sunligth and now it is ok WTF!!??
have you tried calibrating it? there's an app at the play store if i'm not mistaken..
I have tried everything but 1 thing worked. Sunbathing your sola will recalibrate touchscrren. I dont know how it work but it sure does the job. I'm afraid i have to sell my phone cause i dont want any problems. Now i'm using galaxy s3 mini
Sent from my GT-I8190 using Tapatalk 2
SunBathing Works!!!
Hi, Sunbathing really works as a last effort for Xperia Sola
It fixed mine and the time needed for your phone under the sun is approx..1 hour
Dont worry about the battery
Hi guys,
hope you'll be able to help me out with this. Under Diagnostics-->Orientation--> Accelerometer, my brand new Xperia Z4 fails the test since it won't vibrate while shaking the device! Now, vibration itself works fine it's just won't do it in that particular test. Does it mean I've got a faulty device? Can you kindly check if the same problem exists in your devices.
Also, when I've got my music/youtube on and changing orientation, audio seems to cut off for a split second during the transistion. Is it releated you think?
Thanks so much for your help in advance!
And 1st i thought mine was too.. Try shakin itnevery way possbile.. Got mine to vibrate
bosou said:
And 1st i thought mine was too.. Try shakin itnevery way possbile.. Got mine to vibrate
Click to expand...
Click to collapse
I've tried that with no luck unfortunately. What about this other "audio-orientation" issue I've got? This is my first Sony device so I don't know whether that's something normal or not?
Ketman78 said:
I've tried that with no luck unfortunately. What about this other "audio-orientation" issue I've got? This is my first Sony device so I don't know whether that's something normal or not?
Click to expand...
Click to collapse
This audio issue is software bug, i have it too. And for accelerometer i got failed couple of times, but it's working. If it doesn't work you would not be able to rotate screen orientation.
HooLIMAN87 said:
This audio issue is software bug, i have it too. And for accelerometer i got failed couple of times, but it's working. If it doesn't work you would not be able to rotate screen orientation.
Click to expand...
Click to collapse
I'm glad the audio issue is a software bug. It's a bit annoying but hopefully it'll be addressed in the future updates. I can live with that...for now As for the failed test, you think it's really nothing to worry about? The auto-rotation works just fine but why it won't vibrate during the test? You reckon that's the diagnostics issue, another bug perhaps? I just wonder if that's a common issue, that's all?I hope you guys will let me know
Ketman78 said:
I'm glad the audio issue is a software bug. It's a bit annoying but hopefully it'll be addressed in the future updates. I can live with that...for now As for the failed test, you think it's really nothing to worry about? The auto-rotation works just fine but why it won't vibrate during the test? You reckon that's the diagnostics issue, another bug perhaps? I just wonder if that's a common issue, that's all?I hope you guys will let me know
Click to expand...
Click to collapse
Yeah, tried same app on my phone failed couple of times and suceeded finally. Nothing to worry at all, probably one more bug.
HooLIMAN87 said:
Yeah, tried same app on my phone failed couple of times and suceeded finally. Nothing to worry at all, probably one more bug.
Click to expand...
Click to collapse
I've tried for the millionth time and it finally vibrated then it wouldn't again! Well, I'm telling you it was far from shaking it gently . Like you said, it must be another bug!Thanks for your help mate. Much appreciated!
If you still have got any other thoughts drop a line
After last official update (7.3.2.0) on Redmi Note 3 Snapdragon I got issue with vibration.
Button and keyboard vibration randomly stops working 5-10-15min and then works again.
Anybody else?
Nobody else have this issue after last update?
it can be an update issue?
I also face the same problem. How can we resolve this?
My mobile vibration gone completely please help me
Thanks
Issues with official updates, are better discussed in miui thread, I guess?
Think your problem is the same as mine. Motor stop working randomly and start doing is job again in the same way.
Thought was a software problem, realized is an hardware one since i noticed that, when he stop vibrating, if i shake the phone, hes starting again.
giulpip said:
Think your problem is the same as mine. Motor stop working randomly and start doing is job again in the same way.
Thought was a software problem, realized is an hardware one since i noticed that, when he stop vibrating, if i shake the phone, hes starting again.
Click to expand...
Click to collapse
Same problem with me, how you solve the problem?
ansariabdulla1994 said:
Same problem with me, how you solve the problem?
Click to expand...
Click to collapse
You can send your phone in a xiaomi center. I saw you are from india, so you should have no problem. I'm from italy, this means i've to sent it back to china and wait a life to get it back. This is why i didnt resolved the problem and i lost interess on it
Think i'm going to wait the expire of the warranty and try to fix it by my own: i saw some videos and already tried to open the device, it shouldn't be difficult
giulpip said:
You can send your phone in a xiaomi center. I saw you are from india, so you should have no problem. I'm from italy, this means i've to sent it back to china and wait a life to get it back. This is why i didnt resolved the problem and i lost interess on it
Think i'm going to wait the expire of the warranty and try to fix it by my own: i saw some videos and already tried to open the device, it shouldn't be difficult
Click to expand...
Click to collapse
I solved it myself ?
ansariabdulla1994 said:
I solved it myself
Click to expand...
Click to collapse
How? U changed the motor?
giulpip said:
How? U changed the motor?
Click to expand...
Click to collapse
No, the problem was because of loose connections so I reconnect the motor strip and also put a piece of paper inside the motor slot and tighten the motor. Now it is working fine.
ansariabdulla1994 said:
No, the problem was because of loose connections so I reconnect the motor strip and also put a piece of paper inside the motor slot and tighten the motor. Now it is working fine.
Click to expand...
Click to collapse
Smart move the piece of paper. I'll try it when I come back from holiday. I'll let you know.
giulpip said:
Smart move the piece of paper. I'll try it when I come back from holiday. I'll let you know.
Click to expand...
Click to collapse
Thanks
ansariabdulla1994 said:
Thanks
Click to expand...
Click to collapse
News? Still working with the paper? I appreciate if u post a pic of your work..thank youuu
Sent from my Redmi Note 3 using XDA Labs
giulpip said:
News? Still working with the paper? I appreciate if u post a pic of your work..thank youuu
Click to expand...
Click to collapse
Still working, but for sending a pic, i have to reopen the phone.
Will post the picture whenever a got the time to reopen the phone
ansariabdulla1994 said:
I solved it myself
Click to expand...
Click to collapse
I have same issue on my Mi4c. How have you solved it please?
xburda said:
I have same issue on my Mi4c. How have you solved it please?
Click to expand...
Click to collapse
I opened up my phone.
If you are not an advance user or don't have experience how to deal with phone hardware, I recommend you to go o service centre.
Otherwise you want to do yourself then first of all you have to check that if the motor is working or not. If the motor is working then you have to check the connection points the problem with me was because of loose connections and the motor was not tighten. Just check these points and you are good to go.
PS :- I always recommends to go to service centre because opening the phone voids the warranty
This is my situation.
(If the video doesnt work, follow the link https://youtu.be/bzCTTU_iF6w directly).
ansariabdulla1994 said:
I opened up my phone.
If you are not an advance user or don't have experience how to deal with phone hardware, I recommend you to go o service centre.
Otherwise you want to do yourself then first of all you have to check that if the motor is working or not. If the motor is working then you have to check the connection points the problem with me was because of loose connections and the motor was not tighten. Just check these points and you are good to go.
PS :- I always recommends to go to service centre because opening the phone voids the warranty
Click to expand...
Click to collapse
How to check if motor works?
My phone is making a clicky sounnd when i shake it
way back Google has acknowledged this issue and hoping it will be fixed in Android 7.0 update, but still there. This issue seems to be related to the noise-cancelling mic found on the back of the device.
I know some people posted some workaround such as covering up the mic fixes the issue, or persist.audio.fluence.voicecall=true, and changing it to false in build.prop (if rooted, which I am not).
I know there are tons of post related this (searching Google gives many of them), I was just wondering if anyone seen any improvement after 7.0 update or pretty much the same or any other workaround that worked for you..
share your thoughts and findings would be great..
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Smallsmx3 said:
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Click to expand...
Click to collapse
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
jazzespresso said:
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
Click to expand...
Click to collapse
Did you get it from Google?
Smallsmx3 said:
Did you get it from Google?
Click to expand...
Click to collapse
No. I got it from BestBuy couple months ago...checked with Google, and re-turn period is over for this phone, and BestBuy has 90 days return, which is also over...
and I know noise cancelling mic. is there for a good reason, but it is better people can hear me when I speak is more important, so I am planing to put a small tape on mic back of the phone and give a try and see if any improvement...
other than, I really love my Nexus 6P, but this small annoying issue really really bothers me..
If it's a hardware issue why does it work fine when your in speaker phone? At least mine does.....
Sent from my Nexus 6P using XDA-Developers mobile app
Mine also works fine in speaker mode, using the handset speaker everyone always complains about the quality
Sent from my Nexus 6P using Tapatalk
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
mrsean said:
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
MedicStuder said:
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Click to expand...
Click to collapse
You just quoted someone that said he fixed his in safe mode and then you said it's for sure a hardware issue......?. It could be a hardware or software issue depending on you situation. I believe mine is software because it works great in speaker phone.
Sent from my Nexus 6P using XDA-Developers mobile app
skw5115 said:
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hello there!
Same problem here, opposite side is always telling me, that I sound like from garbage/drain or some pipe and also opposite side has echo of it's voice, so practically they hear only themselves with echoes and me very bad or not at all...
I'm using my 6P with Spigen Rugged Armor, and I also tried to make calls without it, and it looked like it's better, so I tried another cover case - Nilkin Perfect Fit, same problems as Rugged Armor and now for the third time, I'm trying Spigen Thin Fit and don't be surprised, it's all the same. So again I tried to use phone without cover and problems appeared same as with cover, so there is no straight connection between cover and these problems in my opinion!
I was preparing to make a ROOT and disable back microphone, but I've read some posts about it and decided to try RMA first, I will come back, how it will end up.
I have the same problem, but only when using the internal mic. Other end says I sound muffled, and I'm only 10" away from the mic. I have to be about an inch or so away and NOT on speaker for them to understand me. I can hear them clear as can be. I have the Unicorn Beetle case, and the noise canceling mic isn't covered, or dirty. I'll try a reboot into safe mode, call, and reboot again. Of course, it could also be just certain people are having a hard time hearing me. I'll see what I can come up with.
Originally Posted by mrsean
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
This worked for me. Thx!
For those who sufferef from muffled voice/bad microphone, try loose the screw at the bottom back of your 6p, you have to open the cover first by using guitar pick/cutter>loose the screw (centre)>put the cover back> completed. No complaint from the other end at all.
Stock 6p, dp4
Solution- Safemode restart...
Thanks guys..I just tried the Safemode restart and it worked perfectly. Then restart in normal mode and the interference could be heard again..so it's one of the apps..not the handset. Thanks again, saved a lot of hassle by avoiding the RMA nightmare.
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
EvoX2008 said:
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
Click to expand...
Click to collapse
Turn the "speaker" line back to true.
Geezerooo said:
Turn the "speaker" line back to true.
Click to expand...
Click to collapse
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
EvoX2008 said:
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
Click to expand...
Click to collapse
Did you reflash the correct vendor?
First, sorry for my bad English!
My V10 H901V20L now the sencond sreen turns off with the main screen too. Means when I turned off the main screen, the second screen went off too, and I can't do anyting with the second screen too. I have tried so many ways ( like turn OFF and ON again both in Settings > Display > Second Screen, flash many differentce roms after 4wipes) and it doesn't work.
I have searched in forum but seem like noone have a solution for this issue.
So can anyone help me!
I have followed this thread and enter "signboardtest", but seem like its not a solution for me.
https://forum.xda-developers.com/lg-...uired-t3253752
And I have tested my proximity sensor, it works nomarly. So I can't find out what is the problems with my V10.
Settings > Display > Second Screen > Turn ON Both Options
Double0EK said:
Settings > Display > Second Screen > Turn ON Both Options
Click to expand...
Click to collapse
Yes, I have tried turn both off and on again. But I didn't work.
You can flash tot
China user
andy_zhang said:
You can flash tot
China user
Click to expand...
Click to collapse
Yes, for sure, I had tried with stock rom .TOT, but it doesn't work too.
update : I had updated KDZ V20J and V20L thru LGUP but it didn't work too. Can anybody help me pls!!
Anybody have any ideals about build.prop. Did this file control the second screen?
Can anyone tell me that is the problem with the hardware or solfware pls!!
Looks like a hardware issue, might want to replace that screen
Sent from my LG-H901 using Tapatalk
luisoman2000 said:
Looks like a hardware issue, might want to replace that screen
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Can you expland me more. Cause the sencond screen works perfectly when the main screen ons.
You already tried wiping and several roms, so it is definitely not a software issue. If it was software the screen would have worked with at least 1 of the roms you tried.
Sent from my LG-H901 using Tapatalk
luisoman2000 said:
You already tried wiping and several roms, so it is definitely not a software issue. If it was software the screen would have worked with at least 1 of the roms you tried.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
You are the men. Cause I still cant believe that is a hardware problem, I had gg for it but seem like no one had the "deepest" problem like me
tuilakhang said:
You are the men. Cause I still cant believe that is a hardware problem, I had gg for it but seem like no one had the "deepest" problem like me
Click to expand...
Click to collapse
Guys HEEEEEEELLLLPPPPP!!!
I have exactly the same problem! Surely someone knows what could cause this? Why does the backlight go off with the main screen??? The display is working, because if you shine light into it, the date/time/notifications are there it's just that the backlight is going off!!!! Surely this is software?
I've factory reset and it made no difference but that doesn't roll back to LP... I just upgraded this phone to the latest software when I bought it so don't know if it had this issue from new.
Sorry to take over the thread, will delete and start a new one if people would prefer.
Don't see how it can be hardware at fault???
Thanks in advance for any help?!
kennish said:
Guys HEEEEEEELLLLPPPPP!!!
I have exactly the same problem! Surely someone knows what could cause this? Why does the backlight go off with the main screen??? The display is working, because if you shine light into it, the date/time/notifications are there it's just that the backlight is going off!!!! Surely this is software?
I've factory reset and it made no difference but that doesn't roll back to LP... I just upgraded this phone to the latest software when I bought it so don't know if it had this issue from new.
Sorry to take over the thread, will delete and start a new one if people would prefer.
Don't see how it can be hardware at fault???
Thanks in advance for any help?!
Click to expand...
Click to collapse
this is what exactly happen to mine. But I had searched for it for months, and didn't have any solution. Only roll back to LP I didn't try.
tuilakhang said:
this is what exactly happen to mine. But I had searched for it for months, and didn't have any solution. Only roll back to LP I didn't try.
Click to expand...
Click to collapse
This is crazy... it's probably something simple to some of the guys on here?. Oh well I'll just see if the seller will accept that it's faulty and send me another one. How did you get sorted or didn't you?
kennish said:
This is crazy... it's probably something simple to some of the guys on here?. Oh well I'll just see if the seller will accept that it's faulty and send me another one. How did you get sorted or didn't you?
Click to expand...
Click to collapse
Unluckily, I got this phone from my friend and it broke after a few time, so I can't send it back to my friend and have to find a solution.
Some say that an harware issues. But I cant get it. The second screen works perfectly with the main screen, but lights out. @@
tuilakhang said:
Unluckily, I got this phone from my friend and it broke after a few time, so I can't send it back to my friend and have to find a solution.
Some say that an harware issues. But I cant get it. The second screen works perfectly with the main screen, but lights out. @@
Click to expand...
Click to collapse
That's bad for you... unlucky.
Can you recall what (if anything) may have caused it to stop working? I'm wondering it mine went bad after LG bridge software update and restore from previous V10 (H961N).
Sent mine back and got another coming this week.. fingers crossed this time. Might update it the same but maybe not restore? or not restore settings at least?
Got my new one. Working fine except it's maybe a tad dimmer compared to my previous V10s second screen. There's definitely variation as it won't go off with my finger over the proximity sensor whereas my brothers one does (this just dims right down). A piece of cardboard or paper shuts it down. But most importantly, it does go off in my pocket... or else the wifi, sound, flashlight etc would be getting switched the whole time.
I solved this problem by checking PINs on mainboard for the second Flex Cable for LCD of LG V10, see the video, READ comments here https://www.youtube.com/watch?v=hpeVAqgU94s, so in my case one of three PINs was folded little, so one PIN contact didn't touch the second Flex Cable and this caused the problem...