Phone has a large black rectangle and cannot see beneath it. It's responsive but can't see what you're clicking... Any ideas?
{
"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"
}
rabaker07 said:
Phone has a large black rectangle and cannot see beneath it. It's responsive but can't see what you're clicking... Any ideas?
Click to expand...
Click to collapse
My 1st instinct would lead me to think its a hardware issue but Id definitely try flashing another rom before I troubleshoot further.
You obviously factory reset or flashed a new rom. Was there anything that led you to do that...other than it's just a common thing to do around here?
Yeah, it's not my phone so I'm not aware of the background. They say that it's vanilla Android and was never rooted or rom'd.
Yes, when you can root and try new roms, then why not!? Isn't that why we get Nexus phones?
I'd like to spend time with the phone myself to see if I could fix it, but I'll have to buy it and could get struck with a lemon out of warranty.
rabaker07 said:
Yeah, it's not my phone so I'm not aware of the background. They say that it's vanilla Android and was never rooted or rom'd.
Yes, when you can root and try new roms, then why not!? Isn't that why we get Nexus phones?
I'd like to spend time with the phone myself to see if I could fix it, but I'll have to buy it and could get struck with a lemon out of warranty.
Click to expand...
Click to collapse
Well it's not clear to me what you're allowed to do on this phone but the least intrusive (simplest) thing I can think of that might work is
1. Hold volume down + power until bootloader comes up (like 5 seconds)
2. Navigate to recovery (if its really vanilla rom Im sure TWRP recovery is installed)
3. Press wipe > advanced wipe then check data, cache, dalvik cache
4. Reboot system
If that doesn't fix it it doesn't necessarily mean the phone is junk but you'll want to try something a little more intensive like flashing factory images. Its not at all difficult but Im not sure if you have adb installed on your computer.
--
KLit75 said:
Well it's not clear to me what you're allowed to do on this phone but the least intrusive (simplest) thing I can think of that might work is
1. Hold volume down + power until bootloader comes up (like 5 seconds)
2. Navigate to recovery (if its really vanilla rom Im sure TWRP recovery is installed)
3. Press wipe > advanced wipe then check data, cache, dalvik cache
4. Reboot system
If that doesn't fix it it doesn't necessarily mean the phone is junk but you'll want to try something a little more intensive like flashing factory images. Its not at all difficult but Im not sure if you have adb installed on your computer.
--
Click to expand...
Click to collapse
Yeah, problem is that I can't do any of this until I purchase the phone. I know my way around ADB so I could definitely install custom roms or factory images/radios/kernels, etc.
So are you saying that you believe this to be a software issue, and not hardware? I don't think replacing the screen will help, but it still could be a hardware issue in my opinion, i.e. bad circuits/connections, fried board, i/o failure or something similar. I wish I could find a similar situation but my research online and in XDA have been fruitless so far. Combined with the fact that I can't actually mess with the phone until I buy it makes this all the more frustrating.
I don't want to buy it unless I know I can fix it...
Thanks
rabaker07 said:
Yeah, problem is that I can't do any of this until I purchase the phone. I know my way around ADB so I could definitely install custom roms or factory images/radios/kernels, etc.
So are you saying that you believe this to be a software issue, and not hardware? I don't think replacing the screen will help, but it still could be a hardware issue in my opinion, i.e. bad circuits/connections, fried board, i/o failure or something similar. I wish I could find a similar situation but my research online and in XDA have been fruitless so far. Combined with the fact that I can't actually mess with the phone until I buy it makes this all the more frustrating.
I don't want to buy it unless I know I can fix it...
Thanks
Click to expand...
Click to collapse
Too many unknown variables to diagnose. If I had to play detective Id ask what the prior owner did.
Was it working ok before he factory reset or flashed a new rom?
Or was the issue present before he reset it?
I really have no idea and would definitely pass on buying it until I got more info.
I've spent quite a bit of time in the 6p threads over the past year & change, never seen a thread with this specific issue.
KLit75 said:
Too many unknown variables to diagnose. If I had to play detective Id ask what the prior owner did.
Was it working ok before he factory reset or flashed a new rom?
Or was the issue present before he reset it?
I really have no idea and would definitely pass on buying it until I got more info.
I've spent quite a bit of time in the 6p threads over the past year & change, never seen a thread with this specific issue.
Click to expand...
Click to collapse
Yeah, I've asked him for as much info as possible, and a number of specific questions, but he only answers a few vague ones. He says it's never had a custom ROM. By the screenshot, it looks like he tried a reset of some sort, as it's on the first page of the Setup Wizard. So that obviously didn't work. I guess I'll left with paying more for a 6p that doesn't have any problems I'm not willing to live with...
Thanks.
If anyone has seen this and/or has ideas on how to fix, please let me know...
Simple question: do you see this rectangle every time?
I'll explain: when you turn this phone on, you have the Google logo and the boot animation. Is this rectangle there? If yes, you have a hardware failure. If you don't see this rectangle in these screens, that's a good signal - try to navigate to other screens (bootloader and recovery, mostly) and see if you have the same result.
Related
Hello all and thanks for reading my thread.
I have searched high and low for this same issue, but found nothing similar anywhere unfortunately.
I have recently noticed that at all times, the screen seems to produce some horizontal lines which flicker often ... I am finding it hard to explain the problem itself, but I have not dropped the phone nor hit it or w/ever.
All I can think of is that I played a lot of this one game on it and it could have affected (overheat?) the GPU or something along those lines...
I am really not sure, but bottom line is that now I see all these issues on the screen, and camera and some games are off limits to use as they look very confusing...
Anyone has any idea what it could be?
G
Could you provide a screenshot?
It does sound like a hardware issue. I would send it for repair. They might even replace it. Maybe you could take a video of it happening.
(I assume you tried uninstalling the game and it didn't solve the problem. If your CPU is being overclocked try resetting it back to normal.)
Grant Barker said:
It does sound like a hardware issue. I would send it for repair. They might even replace it. Maybe you could take a video of it happening.
Click to expand...
Click to collapse
Yep, seems to be hardware issue only!!!
Gowardo said:
Hello all and thanks for reading my thread.
I have searched high and low for this same issue, but found nothing similar anywhere unfortunately.
I have recently noticed that at all times, the screen seems to produce some horizontal lines which flicker often ... I am finding it hard to explain the problem itself, but I have not dropped the phone nor hit it or w/ever.
All I can think of is that I played a lot of this one game on it and it could have affected (overheat?) the GPU or something along those lines...
I am really not sure, but bottom line is that now I see all these issues on the screen, and camera and some games are off limits to use as they look very confusing...
Anyone has any idea what it could be?
G
Click to expand...
Click to collapse
If I were you and and also had a warranty on my phone I would take that to the store and get that fixed
hero000 said:
If I were you and and also had a warranty on my phone I would take that to the store and get that fixed
Click to expand...
Click to collapse
Are screen issues/hardware issues fully covered by warranty? As I talked to an HTC support dude and all he said was we can book a repair and if it's not covered by warranty we'll send you a quote, £20 if you don't want the repair, if you don't pay either we'll get rid of the phone in 3 months...
So I don't wanna really send it off then find my parents get a £100 bill of which they don't know of :/
Most likely the lines are caused by a malfunctioning LCD. This can happen on its own or by physical abuse. Carrying your phone in your back pocket can cause this. If the phone looks great on the outside (no sign of big nicks from being dropped or warped from carrying it in your pocket) then HTC should find no reason to not fix it under warranty. Sometimes things go bad on their own.
Hey,
thanks everyone for your replies. I tried installing a different ROM (Cyan) on my DHD and it still seems to have the same issue, tried changing the cpu and gpu voltages, playing with temperatures etc, but to no avail..
I guess the LCD did go wrong, so Im sending it to Vodafone (UK) for repair. The only thing is that they will probably send me a refurbished phone if they cant fix it which wouldnt really be my first choice, but oh well! Could be worse I guess...
Thanks again for all the feedback
G
htc desire hd screen display scrambled
my desire hd has a display problem, the display has been scrambled when ever i touch edge of the phone. it will fix temporarily by pressing front and back together. hope can understand my problem,
Detail of my mobile
desire hd with gingerbread 2.3.3 (rcMix3d kingdom v1.9)
clockworkmod recovery v4.0.0.6
hboot-0.85.2007
microp-0438
{
"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"
}
@qqavatar: it's definitely a hardware fault, send it for repair...
My Indian Friend gave me this phone No power,
It has response on Power supply when i trigger the Power Switch button, so i thought
there is something wrong with the boot or program.
My Jtag tools (medusa, riff, ort, etc) are no use since when i search the net and read about S3 jtag, i read this thing is not
open on s3 and all my tools doesnt support this phone yet. So i decided to do the Sdcard tricks on reviving Dead phones.
I always have Failed to copy error. I read E.V.A'S contribution post related to S3. He gave me a lot of information about this phone.
After 2 days of software trouble shooting i Decided to check the phones mobo and check every part of it.
when i look in the microscope i found out that I'm not the first to repair this phone.
I decided to change the IC (the tampered one). The IC with the red mark.
But it doesnt help.
{
"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 dont know what this location jumper means
but out of curiousity I just try to remove it.
This phone has a bypass on EU location. I leave the 3 Location open.
When i inserted the battery
IT TURN ON!
hahaha
I know those location are not related with the power )
Its just happen or its my lucky day
I just want to tell a story about my experience on Bricked SIII
This is not a first time I recieved Dead S3
But most of them were not related to Software Issue so it can be easily fix.
What is the purpose of that 3 location jumper?
I did try to install different location, different language it doesnt affect the phones functionality.
I know samsung wont put it on the board without purpose but what is the purpose of that thing?
eyestrain said:
My Indian Friend gave me this phone No power,
It has response on Power supply when i trigger the Power Switch button, so i thought
there is something wrong with the boot or program.
My Jtag tools (medusa, riff, ort, etc) are no use since when i search the net and read about S3 jtag, i read this thing is not
open on s3 and all my tools doesnt support this phone yet. So i decided to do the Sdcard tricks on reviving Dead phones.
I always have Failed to copy error. I read E.V.A'S contribution post related to S3. He gave me a lot of information about this phone.
After 2 days of software trouble shooting i Decided to check the phones mobo and check every part of it.
when i look in the microscope i found out that I'm not the first to repair this phone.
I decided to change the IC (the tampered one). The IC with the red mark.
But it doesnt help.
I dont know what this location jumper means
but out of curiousity I just try to remove it.
This phone has a bypass on EU location. I leave the 3 Location open.
When i inserted the battery
IT POWER ON!
hahaha
I know those location are not related with the power )
Its just happen or its my lucky day
I just want to tell a story about my experience on Bricked SIII
This is not a first time I recieved Dead S3
But all most of them are not related to Software Issue so it can be easily fix.
Click to expand...
Click to collapse
I wonder what happens if you didn't replaced the IC and you just take the jumper off? Would it still be fixed?
Anyways this is Great Find! Might be helpful to ones experiencing SDS?
Sent from my GT-I9300 using xda app-developers app
if the SDS issue was a simple fix like this then it would be a miracle for those with "bricked" S3s.
thegh0sts said:
if the SDS issue was a simple fix like this then it would be a miracle for those with "bricked" S3s.
Click to expand...
Click to collapse
hahaha
Yeah, but i know its not related,
Just like I said on our local gsmforum i am being lucky
It will not fix any bricked s3 for sure.
I just want to share one of my experience on this kind of phone
Im sure its the IC which I replace.
By the way I want to know what is that location on board means?
I didnt put back the original by pass on EU
eyestrain said:
hahaha
Yeah, but i know its not related,
Just like I said on our local gsmforum i am being lucky
It will not fix any bricked s3 for sure.
I just want to share one of my experience on this kind of phone
Im sure its the IC which I replace.
By the way I want to know what is that location on board means?
I didnt put back the original by pass on EU
Click to expand...
Click to collapse
That IC is a power management IC by Maxell ?? correct me if I am wrong.
Hey guys
I hope you can help me, after 4.3 update my nexus starts working weird, like it has been possessed, suddenly it start playing by itself the screen starts moving and open some applications by itself....it recovers when i press the powen buttom two times, so it get back to normal. But this problem has started continuesly apprearing, sometimes im texting and then the phone press some buttoms by itself....so weird.
At the beginning i though i had a virus so i downloaded avast but the problem was still there, then i though mm it might by the image.
So i unlocked the bootloader and then, flash image 4.3, seems the problem was resolved but after 30 min it was there again.
I though OK maybe 4.3 its the problem, i flashed 4.2 but it was worst.
I was reading another post and it seems some users that has NEXUS 7 are experience the same issue:
http://forums.androidcentral.com/go...g-weird-after-thundershowers.html#post3054272
Well i have a NEXUS 7 2013 and its working good.
However my lovely NEXUS 4 has been possessed, anybody has experienced the same problem ?
I recorded video to explain the problem: http://youtu.be/R4GHnVA7ZHw
Thanks in advance for your help.
BR.
Did you just said possessed?
{
"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"
}
badboy47 said:
Did you just said possessed?
Click to expand...
Click to collapse
Yeah haha i dont know how to call it ? The screen start moving randomly and never stop moving, if you open the application list, then some of the application start loading without any touch, its like someone is playing with your device while you are using it haha.
joadchob said:
Hey guys
I hope you can help me, after 4.3 update my nexus starts working weird, like it has been possessed, suddenly it start playing by itself the screen starts moving and open some applications by itself....it recovers when i press the powen buttom two times, so it get back to normal. But this problem has started continuesly apprearing, sometimes im texting and then the phone press some buttoms by itself....so weird.
At the beginning i though i had a virus so i downloaded avast but the problem was still there, then i though mm it might by the image.
So i unlocked the bootloader and then, flash image 4.3, seems the problem was resolved but after 30 min it was there again.
I though OK maybe 4.3 its the problem, i flashed 4.2 but it was worst.
I was reading another post and it seems some users that has NEXUS 7 are experience the same issue:
http://forums.androidcentral.com/go...g-weird-after-thundershowers.html#post3054272
Well i have a NEXUS 7 2013 and its working good.
However my lovely NEXUS 4 has been possessed, anybody has experienced the same problem ?
Thanks in advance for your help.
BR.
Click to expand...
Click to collapse
Try an excorcism by doing a data factory reset in settings/accounts/backup and restore. if that doesn`t help reflash the factory image in fastboot.
gee2012 said:
Try an excorcism by doing a data factory reset in settings/accounts/backup and restore. if that doesn`t help reflash the factory image in fastboot.
Click to expand...
Click to collapse
Hi already tried all that.
First factory reset, then flash image 4.3 and 4.2 over fastboot.
Same issue.
Check the video i made http://youtu.be/R4GHnVA7ZHw
joadchob said:
Hi already tried all that.
First factory reset, then flash image 4.3 and 4.2 over fastboot.
Same issue.
Check the video i made http://youtu.be/R4GHnVA7ZHw
Click to expand...
Click to collapse
Your phone looks defective (hardware) and you need to take it in for repair. You can`t fix this bro. Good luck
gee2012 said:
Your phone looks defective and you need to take it in for repair. You can`t fix this bro. Good luck
Click to expand...
Click to collapse
Really, i was hoping someone was experiecing a similar issue, so weird
Thanks for the help.
does this happen only when you are plugged in or when unplugged as well?
simms22 said:
does this happen only when you are plugged in or when unplugged as well?
Click to expand...
Click to collapse
well i have not paid attention on that.
But the problem does not appear everytime, for example right now ive been playing with it for 1 hour no lag so far.
But from time to time it appears, weird.
It really looks possessed haha
Do you have a screen protector on your Nexus? Sometimes some of the cheaper ones can cause interference with touchscreens, making them do that. (Happened to my old Droid Milestone)
Draw a pentagram " anyone will do. A good one is the alchemy circle from full metal alchemist "
Sacrifice two ducks, a rat, and two hundred donkeys and start channeling your thoughts and summon tool guy "aka Satan"
In all seriousness did your phone get wet? And I mean that in a totally non sexual way....
Ouch it's really acts like possessed one, you need to call some priest (kidding) :silly:
If seriously, what version of android are you using? It is got wet, or it's just started suddenly to act like this?
You're not alone, well then again i did get a replacement lcd/digitizer so it could be a problem with that.
But without a doubt i'm getting the same symptoms as you, sometimes my screen touches itself and what not.
Power on/off does solve it too.
If possible enable show touch events under developer options that will help you track down if its touch events.
my N4 has recently started showing these signs without any specific reason, its not possessed but what i can understand is my device has got a horizontal strip in middle of screen which is non responsive to touch and the random touch events are tracked to that specific region only.
I have the same problem. I've got a brand new nexus 4 and its really jumpy and the best possible way to describe it is definitely possessed. Does anyone have any solutions or shall i just send it back and get it replaced?
Last night i left my phone in working condition but today when i woke up in the morning and turned it on, it started to open up apps automatically and began to touch anywhere it want despite where i wanted to touch. I restarted it 2,3 times and it worked fine. Then when i tried to turn it on through Knock on, it wont turn on. It turns off pretty well but dont turn on. I backed up all my data and did a factory reset but i still got that problem. Please help me out with this issue. Is it hardware or software i cant figure it out. I searched online and one of thread mentioned about testing screen so i tested it through QuickMemo and found out that a little strip was unresponsive(maybe this is the reason of Knock on failure). Again i am not sure if its a hardware or software issue. Please tell me if it can be sorted out through software way. Your help is really appreciated !!
P.S. QuickMemo image is also attached below
{
"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"
}
Amlish said:
Last night i left my phone in working condition but today when i woke up in the morning and turned it on, it started to open up apps automatically and began to touch anywhere it want despite where i wanted to touch. I restarted it 2,3 times and it worked fine. Then when i tried to turn it on through Knock on, it wont turn on. It turns off pretty well but dont turn on. I backed up all my data and did a factory reset but i still got that problem. Please help me out with this issue. Is it hardware or software i cant figure it out. I searched online and one of thread mentioned about testing screen so i tested it through QuickMemo and found out that a little strip was unresponsive(maybe this is the reason of Knock on failure). Again i am not sure if its a hardware or software issue. Please tell me if it can be sorted out through software way. Your help is really appreciated !!
P.S. QuickMemo image is also attached below
Click to expand...
Click to collapse
I wish I could help more, but I'm only guessing. From your Photo, it does appear to be a hardware issue, but if you don't mind going through it all, you might try doing a Hard Reset (AGAIN, sorry..) and see if that fixes it. It's very possible that a Hard Reset will cure the problem. Only thing is you will loose all of your data, so be sure to back it up and restore it.
I know that's a long process, but it would help you figure out if you need to send it in for repair or not. Also, likely LG would have you do the Hard Reset as part of their diagnostics before they had you send it in to them anyways.
You can also use THIS METHOD to return to stock and see if that clears the problem. If you still have that strip that does not respond, then it's likely a hardware issue.
SuperSport said:
I wish I could help more, but I'm only guessing. From your Photo, it does appear to be a hardware issue, but if you don't mind going through it all, you might try doing a Hard Reset (AGAIN, sorry..) and see if that fixes it. It's very possible that a Hard Reset will cure the problem. Only thing is you will loose all of your data, so be sure to back it up and restore it.
I know that's a long process, but it would help you figure out if you need to send it in for repair or not. Also, likely LG would have you do the Hard Reset as part of their diagnostics before they had you send it in to them anyways.
You can also use THIS METHOD to return to stock and see if that clears the problem. If you still have that strip that does not respond, then it's likely a hardware issue.
Click to expand...
Click to collapse
Thanks a lot. I went through diffrent threads and found out that many of LG users had this specific issue and they call it "Ghost Touch". Many of the users recommended their own techniques some of them were really weird. like one guy told to electricate the screen using a little thingi that comes out of a cigarette lighter (i know, weird) but many were claiming that it worked (again, shocked). Some of people told to open up the phone's back and place a two sided tape on LCD connector(yet again many of them claimed that it has worked well for them). But being a technical person i dont believe in these weird and illogical methods. What do u suggest? should i try one of these or not?
P.S. I am from Pakistan and you can't claim warranty to LG from Pakistan so sending my phone to LG for a repair is off the books
another thing.... i am running Lollipop FOTA at the moment. Will the hard reset also change the version to the stock version that came out of box? i.e JB
Amlish said:
Thanks a lot. I went through diffrent threads and found out that many of LG users had this specific issue and they call it "Ghost Touch". Many of the users recommended their own techniques some of them were really weird. like one guy told to electricate the screen using a little thingi that comes out of a cigarette lighter (i know, weird) but many were claiming that it worked (again, shocked). Some of people told to open up the phone's back and place a two sided tape on LCD connector(yet again many of them claimed that it has worked well for them). But being a technical person i dont believe in these weird and illogical methods. What do u suggest? should i try one of these or not?
P.S. I am from Pakistan and you can't claim warranty to LG from Pakistan so sending my phone to LG for a repair is off the books
Click to expand...
Click to collapse
Both of these MIGHT work. I personally would not shock my phone to try to fix it though. The tape thing might work because over time, the connections inside the phone can become loose. The tape is simply pressing the connections tighter. I have had this issue on laptops, and it might relate to your problem, IF it is a hardware issue.
Amlish said:
another thing.... i am running Lollipop FOTA at the moment. Will the hard reset also change the version to the stock version that came out of box? i.e JB
Click to expand...
Click to collapse
If you Hard Reset, it will reset to the current version installed on your phone. So, if you've used FOTA to update, you will refresh back to the FOTA version you have updated to, not back to the original stock version when phone was new.
SuperSport said:
Both of these MIGHT work. I personally would not shock my phone to try to fix it though. The tape thing might work because over time, the connections inside the phone can become loose. The tape is simply pressing the connections tighter. I have had this issue on laptops, and it might relate to your problem, IF it is a hardware issue.
If you Hard Reset, it will reset to the current version installed on your phone. So, if you've used FOTA to update, you will refresh back to the FOTA version you have updated to, not back to the original stock version when phone was new.
Click to expand...
Click to collapse
hello
so finally i did the hard reset
unfortunately did not work out well and the problem still persists.
Now do u suggest to try that tape thing?? If yes then please do give me any tutorial etc to do that(if possible). This would be of great help
thanks in advance !!
*Dial 3845#*802# > setting > update touch firmware
Hope it will work for you
Sent from my LG-D801 using XDA Free mobile app
Amlish said:
hello
so finally i did the hard reset
unfortunately did not work out well and the problem still persists.
Now do u suggest to try that tape thing?? If yes then please do give me any tutorial etc to do that(if possible). This would be of great help
thanks in advance !!
Click to expand...
Click to collapse
What I'm guessing they mean by the tape thing is finding the spot where the connection is not good, and using a piece of tape to put pressure on the connection when the back is placed back on. I don't have any way of knowing where that spot is. If it were my phone, I'd open it up and start putting light pressure on different spots to see if the screen starts working right. If/When you find the spot, place a small piece of tape that will apply pressure there when the back is placed back.
SuperSport said:
What I'm guessing they mean by the tape thing is finding the spot where the connection is not good, and using a piece of tape to put pressure on the connection when the back is placed back on. I don't have any way of knowing where that spot is. If it were my phone, I'd open it up and start putting light pressure on different spots to see if the screen starts working right. If/When you find the spot, place a small piece of tape that will apply pressure there when the back is placed back.
Click to expand...
Click to collapse
thanks again
I just followed Heisenberg's guide to rooting my Nexus 6P. I have rooted it using TWRP 3.2.1-0-angler.img recovery, Magisk v15.2 root, and Resurrection Remix Rom v6.0.0-20180319-angler.
Everything is working well and I am really enjoying the ROM. However, my microphone(s) are super sensitive and people say it sounds like I'm fumbling and dropping the phone or am in a wind tunnel. I tested this with the "recorder" app in RR and can verify that even the slightest shifting of my hand or touching/adjusting the grasp of the phone is greatly amplified and sounds like the phone is being manhandled. It's like the mic is too sensitive or has a gain that is turned up.
After researching, I edited the build.prop file to turn the persist.audio.fluence.voicecall=true value to "false." I also cleared the cache via TWRP as was also suggested. It made no difference. So, then I reverted back to stock everything using the flash-all command and the official Google latest images. After booting into the completely stock ROM, the problem is still there. My 6P is almost un-useable as a phone since even the phone pressing against my ear and shifting positions slightly will sound like it's being dropped and kicked across the room to the person on the other end!
I tried stock, resurrection remix, and lineageOS ROMs. I tried the old radio, and updated radio images. I tried editing the build.prop file's "fluence" references. I tried putting electrical tape on the rear microphone (which has helped a tiny amount). What am I missing? Has anyone else encountered this? Any help is appreciated!!
NOTE: This is definitely NOT the "too quiet" problem that seems to be commonly reported on the web. This problem is too sensitive of a microphone.
dre_2ooo said:
I just followed Heisenberg's guide to rooting my Nexus 6P. I have rooted it using TWRP 3.2.1-0-angler.img recovery, Magisk v15.2 root, and Resurrection Remix Rom v6.0.0-20180319-angler.
problem that seems to be commonly reported on the web. This problem is too sensitive of a microphone.
Click to expand...
Click to collapse
It's probably just the back mic below camera lense. Take a toothpick and carefully clean up any particles and lint. I couldn't really see most of it but after I did a couple sweeps the phone calls where perfect.
Exodusche said:
It's probably just the back mic below camera lense. Take a toothpick and carefully clean up any particles and lint. I couldn't really see most of it but after I did a couple sweeps the phone calls where perfect.
Click to expand...
Click to collapse
Thanks for the tip. Just tried that with a toothpick and didn't see anything come out. I also blew some air in there too. Problem still unsolved
dre_2ooo said:
Thanks for the tip. Just tried that with a toothpick and didn't see anything come out. I also blew some air in there too. Problem still unsolved
Click to expand...
Click to collapse
The only fix I can think of is wiping internal storage if you haven't already. Just make sure you backup all your pics, downloads,music etc. I've seen issues arise from pieces of files being left behind causing random issues. I've had bugs that no matter what I did would not fix but once I did some house cleaning all was corrected.
Exodusche said:
The only fix I can think of is wiping internal storage if you haven't already. Just make sure you backup all your pics, downloads,music etc. I've seen issues arise from pieces of files being left behind causing random issues. I've had bugs that no matter what I did would not fix but once I did some house cleaning all was corrected.
Click to expand...
Click to collapse
I cleared every checkbox that is available in the "wipe" menu of TWRP before flashing the ROM. I have indeed wiped the internal storage several times.
PS - Yes, I did back up all my important things before wiping!
dre_2ooo said:
I cleared every checkbox that is available in the "wipe" menu of TWRP before flashing the ROM. I have indeed wiped the internal storage several times.
PS - Yes, I did back up all my important things before wiping!
Click to expand...
Click to collapse
Ok seems like you covered it all sorry wasn't much help. I would work backwards from everything you've changed since previously where it was working. For example did you maybe update your radio and or bootloader. If it's hardware issue not much you can do unfortunately.
Exodusche said:
Ok seems like you covered it all sorry wasn't much help. I would work backwards from everything you've changed since previously where it was working. For example did you maybe update your radio and or bootloader. If it's hardware issue not much you can do unfortunately.
Click to expand...
Click to collapse
Would the radio influence this? Maybe I should flash back to the MM or N radio...
dre_2ooo said:
Would the radio influence this? Maybe I should flash back to the MM or N radio...
Click to expand...
Click to collapse
Not sure worth a shot. Also this thread is where I got most of my info.
Exodusche said:
Not sure worth a shot. Also this thread is where I got most of my info.
Click to expand...
Click to collapse
Okay, I just tried a variety of angler radios and all of them have the same results... :/ May just have to end up getting a new phone come November
dre_2ooo said:
Okay, I just tried a variety of angler radios and all of them have the same results... :/ May just have to end up getting a new phone come November
Click to expand...
Click to collapse
Yeah man that sucks was hoping. Last thing if you haven't already is try without a case. Some have had luck rolling naked.
Yeah it does suck. I rooted it and put a new battery in it in an effort to keep it longer into the future since Google will stop security updates in November. I just cannot see how this issue is possible, even when reverting back to stock!
What if I was to just completely remove the rear microphone???
dre_2ooo said:
Yeah it does suck. I rooted it and put a new battery in it in an effort to keep it longer into the future since Google will stop security updates in November. I just cannot see how this issue is possible, even when reverting back to stock!
What if I was to just completely remove the rear microphone???
Click to expand...
Click to collapse
Try the magisk module. Microphone fix
lil_ith said:
Try the magisk module. Microphone fix
Click to expand...
Click to collapse
Thanks for the tip. I installed the mic fix in the Magisk module.... still unsolved!!! This is crazy. I'm starting to think it's a hardware issue that MAYBE just maybe coincided with the root. Odds are low, but what else could it be???
dre_2ooo said:
Thanks for the tip. I installed the mic fix in the Magisk module.... still unsolved!!! This is crazy. I'm starting to think it's a hardware issue that MAYBE just maybe coincided with the root. Odds are low, but what else could it be???
Click to expand...
Click to collapse
I honestly don't know. I'll keep an eye out for you and let you know if I hear of anything you could try. You might be able to disable the one you need to with mixer_paths. But I wouldn't know how to
This same issue started happening to me. It seems to only occur when I'm using the speakerphone.
So annoying! I have been searching for a solution for the past 2 days with no luck.
Does this problem occur for both handset calls and speakerphone calls, or only one type of call?
Hope we can find a solution!
Cheers,
B.D.
I have finally solved this issue! I tried everything from changing ROMs to cleaning out the microphone hole to modifying the build prop. Nothing seemed to have worked, and I was about to ditch this phone. And then I tried:
1) Ensure you are rooted with TWRP recovery
2) Flash ElementalX for Nexus 6P in recovery
3) Reboot, install Ex Kernel Manager
4) Reduce your microphone gain:
{
"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"
}
If my solution works, please give thanks! :good: