Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
abenco said:
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
Click to expand...
Click to collapse
Oddly enough, the OTA update is the only thing that worked on mine.
Gizmoe said:
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
Click to expand...
Click to collapse
It really is weird. I'm back on MM now and its working fine. I guess I stay here until the next build comes up and then I'll see what happens.
Same issue here. stock rom, received OTA and now I have the excess battery use, and thanks to the post boss above, the same proximity sensor issue. Phone goes black in middle of call with no way to get back to the screen to hang up, change to speakerphone, etc. It stays black sometimes, even after the other party hangs up, requiring me to reboot. PITA.
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
You have to unlock the bootloader but thats pretty much it. After you flash you can relock it if you want.
I could fix that problem by removing the screen protector.
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
No not rooting. You have to unlock the bootloader and then fastboot flash a factory image. It's best to leave the bootloader unlocked too, unless you are going to leave it stock and never tinker with it again. But if you ever need to flash an image again or use twrp or anything fastboot related you will need an unlocked bootloader.
I have the same problem with my phone. Android 7.1 seems to fix this.
Enviado de meu Nexus 6P usando Tapatalk
I had the same problem, but fixed it by installing a sensor reset app from Play Store, then uninstalled the app.
Just talked to Huawei tech support. My 6P wasn't rotating the screen and whenever I was in a call, wouldn't dim the screen. Such a small feature but we all take it for granted. Anyway, she told me to enter recovery (Power+Volume Up) and "Wipe Cache Partition" rebooted and running like a champ. ?
Related
When I try to start the stock camera app it just hangs won't start. I've rebooted and still no luck. Is this a known issue?
I guess this isn't a popular issue. One I myself have though.
I RMA'd the phone and got a replacement. Except the replacement had a dead pixel, and now the replacement I have has a large dent near the fingerprint reader. Maybe the 4th time is a charm.
Same issue here running stock 6.0.1. It was working fine then suddenly just stopped. I've tried starting in safe mode and factory reset, and nothing. Any clever suggestions to fix this or I guess I'll ring to ask for a replacement tomorrow?
timtime said:
Same issue here running stock 6.0.1. It was working fine then suddenly just stopped. I've tried starting in safe mode and factory reset, and nothing. Any clever suggestions to fix this or I guess I'll ring to ask for a replacement tomorrow?
Click to expand...
Click to collapse
Could try manually Flashing the vendor.img from stock 6.0.1 image. I've read that fixes camera issues for some.
XxMORPHEOUSxX said:
Could try manually Flashing the vendor.img from stock 6.0.1 image. I've read that fixes camera issues for some.
Click to expand...
Click to collapse
Yeah I had the same issue where the camera just wouldn't open. flashing Vendor.img did the trick
Hi.
There are lots of issues about the note 4 not charging properly while switched on. I seem to have the opposite problem. I recently updated to Cpc1 firmware, and twrp 3. It works really well. Boots to download, recovery etc fine.
But if I plug the power lead in while it's off. The battery symbol appears but does not animate. The phone locks. And the only way to get it back to life is pull the battery.
This is hardly a big problem, and I'll live with it if nobody has a fix. But has anyone come across this before?
Thanks
Broomfundel said:
Hi.
There are lots of issues about the note 4 not charging properly while switched on. I seem to have the opposite problem. I recently updated to Cpc1 firmware, and twrp 3. It works really well. Boots to download, recovery etc fine.
But if I plug the power lead in while it's off. The battery symbol appears but does not animate. The phone locks. And the only way to get it back to life is pull the battery.
This is hardly a big problem, and I'll live with it if nobody has a fix. But has anyone come across this before?
Thanks
Click to expand...
Click to collapse
It seems to have started after COL3, it was occurring to users who were using my stock de-bloated ROM. I initially thought it had something to do with SuperSU.
If you could try to flash the stock firmware and not install a custom recovery or SuperSU and see if the issue still occurs?
OK. Phones originally a BTU so I pulled down N910FXXS1CPC1_N910FBTU1COI1_N910FXXS1COK1_HOME.tar.md5 as the latest BTU available. Charges normally while off. Manually rooted with auto root, re flash TWRP 3 and xposed. All is fine
So went back and looked at the version I had downloaded before. It was your partially de-bloated Stock-CPC1-signed.zip. Not sure what in the debloat causes it. Maybe Ill debloat by hand and see if I can work it out. If I get the problem back Ill let you know.
Hi guys. Over the weekend, I was running Android O beta, just to give it a spin and see how it was. Everything was working ok, but then I missed the good features of AOSP, so I decided to come back to it. So on Sunday night, I flashed back the previous rom, including the vendor, bootloader and radio as requested on the OP. But the problem was that the screen rotation wasn't working, no matter what I tried. I even tried other roms, to see if the problem was from the rom, but no, the problem persisted. I flashed stock again, and the problem was also there. I gave Google a call and they sent me some steps to go through and none of them solved my problem as well. So, I decided to flash back the O Beta, and voila, the problem was gone. My question, have I done anything wrong, any step that I may have missed? Or is it the drivers? Any help/suggestion is highly appreciatted
Did you factory reset or wiped data? It's sometimes necessary when downgrading.
I did yes. It was the first thing I did as soon as I got TWRP installed on it,because it was asking for the encryption key, to which it never what it was(tried my password and my lock screen code,but none of them worked,so just ended up wiping the whole data)
I've been given an OP2 64GB as a project from a friend to try and return to stock and working. It was running a custom ROM which wasn't working particularly well, so I did the full reload to stock 3.0.2 via the Qualcomm download described here by @fareed_xtreme which downloaded okay, booted up, and the touchscreen seemingly didn't work. I've come across that before where there's been driver or firmware mismatches, but then I realised that if I held my finger on the screen for between 2 and 4 seconds, it'd start responding, right up until I let my fingers up off the screen. I could do multiple scrolls by adding a second finger to the mix, and it'd keep responding until I let go, at which point I'd have to hold down for another 2-4 seconds to make it do anything. The digitiser is fine, I enabled the overlays in dev tools (painfully clicking item by item!), and it shows the traces fine. They don't show up at all as screen presses until said delay happens, which is very odd. It also responded fine in the recovery, which was plain odd.
After a while, I tried returning it to 2.2.0 courtesy of @fareed_xtreme's other guide, which then worked fine, booted up, had 2.2.0 installed, touchscreen worked fine. Did notice the baseband version claimed it was unknown, though I'm unsure if this was related to me having no SIMs in it. It did initially offer me an OTA upgrade to the latest Marshmallow, which I allowed it to do, and promptly had the same issues again.
I've tried flashing various ROMs - Resurrection Remix etc, to find they've got the same problem. Any Marshmallow-based ROM seems to suffer from this weird input lag. The capacitive buttons are fine, it's just the display. Also, weirdly, it works if I touch the screen just as I wake the phone with the power button - so I can hit the power button and immediately swipe the lockscreen off, but then it reverts to the previous behaviour.
I've tried re-flashing the firmware for the various ROMs (matching with the installed ROM obviously). I've also repeatedly wiped the system/data/cache partitions etc, and have backups of EFS via TWRP saved off the phone. I also spotted two threads on the OnePlus forums describing this exact issue here and here, both with no solution. I also noticed people have had similar issues long ago when they tried installing H2OS and then returning to stock, without doing the full qualcomm download, but they seemed to be mostly solved with the full ROM reload and a cache wipe.
My next step is to flash back to 2.2.0, and incrementally upgrade with the OTAs, see if it works, but I suspect the second I make the jump to 3.0.2, I'll lose the touchscreen again. I've left it OEM unlocked, and got TWRP and original recoveries available.
To be honest, worst case, I just reflash the phone back to the final 2.x version, at least it actually works then, but... I'd really love to know why I can't fix this, and what the actual issue is, if anyone out there knows. There doesn't seem to be much on here in the way of people experiencing the issue - either that, or my search-fu has repeatedly failed me. My gut feeling is something kernel/driver related, but I don't understand why it wouldn't get fixed with the full firmware download via QC.
Help me, XDA, you're my only hope!
N2A said:
I've been given an OP2 64GB as a project from a friend to try and return to stock and working. It was running a custom ROM which wasn't working particularly well, so I did the full reload to stock 3.0.2 via the Qualcomm download described here by @fareed_xtreme which downloaded okay, booted up, and the touchscreen seemingly didn't work. I've come across that before where there's been driver or firmware mismatches, but then I realised that if I held my finger on the screen for between 2 and 4 seconds, it'd start responding, right up until I let my fingers up off the screen. I could do multiple scrolls by adding a second finger to the mix, and it'd keep responding until I let go, at which point I'd have to hold down for another 2-4 seconds to make it do anything. The digitiser is fine, I enabled the overlays in dev tools (painfully clicking item by item!), and it shows the traces fine. They don't show up at all as screen presses until said delay happens, which is very odd. It also responded fine in the recovery, which was plain odd.
After a while, I tried returning it to 2.2.0 courtesy of @fareed_xtreme's other guide, which then worked fine, booted up, had 2.2.0 installed, touchscreen worked fine. Did notice the baseband version claimed it was unknown, though I'm unsure if this was related to me having no SIMs in it. It did initially offer me an OTA upgrade to the latest Marshmallow, which I allowed it to do, and promptly had the same issues again.
I've tried flashing various ROMs - Resurrection Remix etc, to find they've got the same problem. Any Marshmallow-based ROM seems to suffer from this weird input lag. The capacitive buttons are fine, it's just the display. Also, weirdly, it works if I touch the screen just as I wake the phone with the power button - so I can hit the power button and immediately swipe the lockscreen off, but then it reverts to the previous behaviour.
I've tried re-flashing the firmware for the various ROMs (matching with the installed ROM obviously). I've also repeatedly wiped the system/data/cache partitions etc, and have backups of EFS via TWRP saved off the phone. I also spotted two threads on the OnePlus forums describing this exact issue here and here, both with no solution. I also noticed people have had similar issues long ago when they tried installing H2OS and then returning to stock, without doing the full qualcomm download, but they seemed to be mostly solved with the full ROM reload and a cache wipe.
My next step is to flash back to 2.2.0, and incrementally upgrade with the OTAs, see if it works, but I suspect the second I make the jump to 3.0.2, I'll lose the touchscreen again. I've left it OEM unlocked, and got TWRP and original recoveries available.
To be honest, worst case, I just reflash the phone back to the final 2.x version, at least it actually works then, but... I'd really love to know why I can't fix this, and what the actual issue is, if anyone out there knows. There doesn't seem to be much on here in the way of people experiencing the issue - either that, or my search-fu has repeatedly failed me. My gut feeling is something kernel/driver related, but I don't understand why it wouldn't get fixed with the full firmware download via QC.
Help me, XDA, you're my only hope!
Click to expand...
Click to collapse
I would suggest you to open a ticket with OnePlus Support (Live Chat). Inform them of the touchscreen scenario (Do not mention about the Quallcomm Flashing or they may start giving you a hard time for taking matters in your own hands). They will schedule you for the process and hopefully, they may be able to resolve it possibly with a newer Stock Reset.
Cheers, I'll give them a shot!
Unfortunately got no dice there - they reflashed it with OnePlus2_14_A.27_161227 (annoyingly, didn't get the decrypted files due to a screwup with my file mirroring), but still had precisely the same issue, up-to-date, no working touchscreen. If I can't get it working, it's not the end of the world, it's more annoying me that I can't figure it out... suggestions of a ROM to flash that might work would be most welcome!
Hi! I have an issue with a 64gb Nexus 6p (running stock android 8.1, latest patch, unlocked bootloader)
The phone consistiently runs extremely slow (taking 5 minutes to boot) and animations heavily lag, to the point where they are displayed over the top of the phone (I can unlock my phone using my passcode while the phone is still displaying its boot animation, for example, as it has booted but the animation has not stopped)
Also, occasionally half of the screen flashes white, back to normal, white twice, then the entire screen goes black, at which point it then returns to normal. This stopped when I flashed Lineage, however I have since restored the phone to stock and it has come back.
So far, I have tried to:
reflash updates
install a seperate kernel
install different ROMs
but nothing has worked
Would anyone be able to help?
It seems to most likely be a board issue, but I am still holding out hope that it could be related to software.
Try flashing its original stock firmware no updates. Load nothing else. If it's still doing it, it's hardware.
Some rootkits can survive a factory reset but not a firmware reflash; pre Pies OS's are vulnerable.
blackhawk said:
Try flashing its original stock firmware no updates. Load nothing else. If it's still doing it, it's hardware.
Some rootkits can survive a factory reset but not a firmware reflash; pre Pies OS's are vulnerable.
Click to expand...
Click to collapse
I already have tried that, several times.
Guess it's a hardware issue, then - regardless, thank you very much for the help.
I wonder what specific part of the hardware could cause this issue. I remember reading a user on this forum at one point have a similar issue, however he unrooted his 6p and the issue went away.