Related
i need help, my screen turns of then it never turns back on, only the soft keys turn on, i was thinking it was because i flashed the newest radio, but i dont know, someone please help me
Jelly Nugget said:
i need help, my screen turns of then it never turns back on, only the soft keys turn on, i was thinking it was because i flashed the newest radio, but i dont know, someone please help me
Click to expand...
Click to collapse
radio shouldn't do this, but it could have been an corrupt download or something, you could try going back to the old radio to see if it helps.
I'm assuming you are rooted?
running which ROM?
I'm pretty sure that if you had a bad radio flash your phone will be permanently bricked.
I'm assuming you can boot it right?
shoman24v said:
I'm pretty sure that if you had a bad radio flash your phone will be permanently bricked.
I'm assuming you can boot it right?
Click to expand...
Click to collapse
yes it can boot up, just when i lock the screen it doesnt work,
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
andybones said:
radio shouldn't do this, but it could have been an corrupt download or something, you could try going back to the old radio to see if it helps.
I'm assuming you are rooted?
running which ROM?
Click to expand...
Click to collapse
noo, it wasnt corrupted, i did flash the old radio, and still no dice, i called asurion, and told the guy i was rooted, he didnt mind, because he was too. lol but yeahh, they are sending me a replacement.
EDIT- and yes im running CM7, but i tried miui and it still does it.
Well, if the phone is able to turn on like you state, I'd say maybe there's an issue with your ROM, maybe a kernel or mod you flashed?
If you had an issue with the button, the phone would not power up. Unless you have to press it really hard?
Maybe you want to do a clean install of a Sense ROM or a clean install of CM7
Jelly Nugget said:
yes it can boot up, just when i lock the screen it doesnt work,
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
noo, it wasnt corrupted, i did flash the old radio, and still no dice, i called asurion, and told the guy i was rooted, he didnt mind, because he was too. lol but yeahh, they are sending me a replacement.
EDIT- and yes im running CM7, but i tried miui and it still does it.
Click to expand...
Click to collapse
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
tylerlawhon said:
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
Click to expand...
Click to collapse
+1 too many megahertz
From this, it sounds like it's not able to handle the speeds.
Don't overclock.
tylerlawhon said:
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
Click to expand...
Click to collapse
actually, i underclocked to 806mhz on all my roms to save power.
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
shoman24v said:
Well, if the phone is able to turn on like you state, I'd say maybe there's an issue with your ROM, maybe a kernel or mod you flashed?
If you had an issue with the button, the phone would not power up. Unless you have to press it really hard?
Maybe you want to do a clean install of a Sense ROM or a clean install of CM7
Click to expand...
Click to collapse
ive done a clean install of all the ROMs, like Incredible 3D, Incredible HD, CM7, OMGB, OMFGB, Virtuous, and still no dice on anyone of them.
flash an ruu just to make sure its an actual problem with the phones screen and not you screwing something up by flashing something.
Sent from my Incredible 2 using XDA App
Jelly Nugget said:
actually, i underclocked to 806mhz on all my roms to save power.
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
ive done a clean install of all the ROMs, like Incredible 3D, Incredible HD, CM7, OMGB, OMFGB, Virtuous, and still no dice on anyone of them.
Click to expand...
Click to collapse
That could be your problem if you're not undervolted. (Someone correct me if I'm wrong. It just makes sense in my head lol)
Too much undervolting can cause issues too.
shoman24v said:
Too much undervolting can cause issues too.
Click to expand...
Click to collapse
I figured as much, cuz if you UV too much, you wouldn't be sending adequate power to the CPU, causing it to not work.
times_infinity said:
flash an ruu just to make sure its an actual problem with the phones screen and not you screwing something up by flashing something.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
how would i do that? if i can can i get a link please?
Jelly Nugget said:
how would i do that? if i can can i get a link please?
Click to expand...
Click to collapse
The only one I've been able to find for you, is the newest RUU, and it has to potential (or so it sounds) to take your root.
http://forum.xda-developers.com/search.php?searchid=91685359
This is the latest RUU update for the VivoW
I don't know if RUU'ing will fix it.
Were not 100% clear on the issue. My understanding is that the phone only has issues powering up when the screen is asleep. He's undervolted, which can be an issue.
What I'm curious to know... do you have any issues powering up the device when it's completely off? Any issues with the power button when navigating in HBOOT? If there is no problem with those, I'd believe it's maybe the way the phone is set up.
I'd try to flash a 100% stock ROM with no modifications and see if it's still an issue.
tylerlawhon said:
The only one I've been able to find for you
Click to expand...
Click to collapse
Haha I love it..doing his work for him
Sent from my Incredible 2 using xda premium
shoman24v said:
I don't know if RUU'ing will fix it.
Were not 100% clear on the issue. My understanding is that the phone only has issues powering up when the screen is asleep. He's undervolted, which can be an issue.
What I'm curious to know... do you have any issues powering up the device when it's completely off? Any issues with the power button when navigating in HBOOT? If there is no problem with those, I'd believe it's maybe the way the phone is set up.
I'd try to flash a 100% stock ROM with no modifications and see if it's still an issue.
Click to expand...
Click to collapse
yes, i flashed the ruu, and it did take root. it boots, but when i lock the phone, it still doesnt turn on. it does navigate fine in recovery.
Jelly Nugget said:
yes, i flashed the ruu, and it did take root. it boots, but when i lock the phone, it still doesnt turn on. it does navigate fine in recovery.
Click to expand...
Click to collapse
The exact same issue came up for me about a week ago. I could boot an aosp rom, but like you when I lock the screen and go to unlock I get a black screen with only the soft keys. I still have no solution. But if you take out your sd card and boot up it shouldn't do that anymore so i think it has to do with the sd card or something on it.
Sent from my Incredible 2 using XDA App
I'm having the exact same problem. Only happens on aosp roms, sense roms work fine. Boots up fine with cm7 or miui (a little laggy actually) then when screen is turned off, only softkeys light up... can't unlock
edit-----
Tried to remove the sd card upon boot, like previous post suggested. Still wouldn't unlock on cm7..... even with sd card not installed.
This happens the first time i turn the screen on after a power up/reboot (MIUI + JDKernel/tiamat). Screen does its CRT animation and goes black. Easily fixed with a couple presses of the power button, but now you got me worried it won't always be that simple...
Sent from my Incredible 2 using XDA App
i am on lollipop stock 5.0.2 rooted and BL unlocked.
i recognized one issue: during a call 90% of all time when i move the device away from the ear
the quicksettings are opened.
How can i disable quicksettings during a call?
This issue is very annoying.
This happened to me more than once too. I'd love a solution!
Not sent by me.
moonryder said:
i am on lollipop stock 5.0.2 rooted and BL unlocked.
i recognized one issue: during a call 90% of all time when i move the device away from the ear
the quicksettings are opened.
How can i disable quicksettings during a call?
This issue is very annoying.
Click to expand...
Click to collapse
during a call and press power button.
screen goes off and you avoid this annoying issue.
its not the best solution but it works.
i have excacly same issue with quick settings. I think its a proximity sensor issue. On KK i hade also same situation but there was one different thing, the statusbar was sliding up back but here it drops down and persist heh. Maybe someone else could post here if also had such an issue. I have also from time to time when i need to dial something while calling that even when my screen goes black i can hear sound of dial pad heh its very annoying thing.
Screen
Is this an issue everyone with this phone has? It's driving me crazy.
+1. I had it on stock. Now I'm using Rockz1L - same issue... Does all of you use screen protector? I do. Would try to get rid of it and check if that's the cause, but I don't want to experiment without a reason.
AseDance said:
+1. I had it on stock. Now I'm using Rockz1L - same issue... Does all of you use screen protector? I do. Would try to get rid of it and check if that's the cause, but I don't want to experiment without a reason.
Click to expand...
Click to collapse
So you flashed a custom rom and you still have the proximity problem?
---------- Post added at 01:37 AM ---------- Previous post was at 01:31 AM ----------
halothirteen said:
So you flashed a custom rom and you still have the proximity problem?
Click to expand...
Click to collapse
Also can you try a diffrent rom? It looks like Rockz1L is based off the stock rom and therefore would still have the same bug. Would appreciate it if you could confirm this with a different rom like CM 12.1.
Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?
Brainium said:
Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?
Click to expand...
Click to collapse
both panels should be supported by twrp...at least when they came originally from htc.
seems the sharp panel you got its another revison/running an incompatible driver.
j to the 4n said:
both panels should be supported by twrp...at least when they came originally from htc.
seems the sharp panel you got its another revison/running an incompatible driver.
Click to expand...
Click to collapse
That may be true, but why would it work in the ROM, but not in the recovery? Would it be possible to take the driver out of the ROM and put it into TWRP?
same here, works in ROM, not working in twrp
Did this ever get figured out. I have the same issue!
was rooting a friends phone, everything went well...got to twrp. no touch. turns out he has sharp panel as well... is this a twrp issue or just a driver issue that we are SOL with?
I have the same issue too!
Brainium said:
Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?
Click to expand...
Click to collapse
Have you worked it out yet? Thanks.
mybnr34 said:
Have you worked it out yet? Thanks.
Click to expand...
Click to collapse
I had the same issue. Cracked my screen, had it replaced in an unauthorized service center. Came back, no TRWP touch response. Funny enough, even an update with a RUU did not work and would fail every time.
Sent to HTC for repair, they changed the screen for another one. Still didn't work. Sent the phone back again, they supposedly reset the phone to factory settings and "connected connector (A102)". That's at least what the service protocol says. Screen works perfectly after that.
Another side effect, when the TWRP was not working was, also double-tap to wake in android and camera launch shortcuts also didn't work.
mybnr34 said:
Have you worked it out yet? Thanks.
Click to expand...
Click to collapse
No. I ended up just getting a new phone through Verizon.
guys anyone found a solution for this?
i change my htc 10 screen too for a one that i bought in alliexpress and no luck with twrp
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
madzur said:
I had the same issue. Cracked my screen, had it replaced in an unauthorized service center. Came back, no TRWP touch response. Funny enough, even an update with a RUU did not work and would fail every time.
Sent to HTC for repair, they changed the screen for another one. Still didn't work. Sent the phone back again, they supposedly reset the phone to factory settings and "connected connector (A102)". That's at least what the service protocol says. Screen works perfectly after that.
Another side effect, when the TWRP was not working was, also double-tap to wake in android and camera launch shortcuts also didn't work.
Click to expand...
Click to collapse
hi, what means this?
---------- Post added at 03:26 AM ---------- Previous post was at 03:25 AM ----------
mybnr34 said:
I have the same issue too!
Click to expand...
Click to collapse
you also broke your display and replace it?
dentedilupo said:
guys anyone found a solution for this?
i change my htc 10 screen too for a one that i bought in alliexpress and no luck with twrp
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
hi, what means this?
---------- Post added at 03:26 AM ---------- Previous post was at 03:25 AM ----------
you also broke your display and replace it?
Click to expand...
Click to collapse
Hi. This is something that was listed on the service protocol. I have no more details about this. That's why I wrote it here, hoping maybe someone has an idea.
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
angka8 said:
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
Click to expand...
Click to collapse
I found it wasn't great in the dark, I assume it uses the light sensor to determine if in pocket etc
Sent from my Google Pixel XL using XDA Labs
I have noticed the same thing. It isn't 100% consistent.
FWIW: Mine seems to be very consistent if I triple tap. Perhaps the first tap wakes it up if it's in a deep sleep?
Hopefully fixed in the December update.
JAYNO20 said:
Hopefully fixed in the December update.
Click to expand...
Click to collapse
No change for me.
cam30era said:
No change for me.
Click to expand...
Click to collapse
Has been working consistently for me so far. Will post back if that changes.
---------- Post added at 03:07 PM ---------- Previous post was at 02:26 PM ----------
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
JAYNO20 said:
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
Click to expand...
Click to collapse
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
cam30era said:
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
Click to expand...
Click to collapse
Makes no sense. I'm glad we are seeing the same issues though, at least it's consistent there
I'm having the same exact issues. Tap not working consistently and sometimes the lift doesn't work either. Hmm.
It's worth noting I had the same issues with the Elemental kernel before this ddtw option was available. The ddtw option was just as inconsistent for me.
Neither working at all for me.
Update: Seems to be working fine now.
if you have a screen protector that might cause the issue
if it still doesnt work without screen protector reflash the factory image
The update seems to fix the issue.
Update: the issue still there. But much less frequent
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
I have noticed that is works better if the screen is locked. So if your phone doesn't lock for 5 or so minutes, it may not work until after that time. Try to set your phone to "Power button instantly locks" and then try it. Mine was not working at all, but when I locked the device sooner, it started to work consistantly. Might not help you, but fixed it for me.
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
GCbard said:
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
Click to expand...
Click to collapse
It's an option with the newer OTA.
clockcycle said:
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
It's an option with the newer OTA.
Click to expand...
Click to collapse
Where is this option located? I'm on the November update. Is this with the December update?
GCbard said:
Where is this option located? I'm on the November update. Is this with the December update?
Click to expand...
Click to collapse
December OTA. Same location as other Moves/ gestures.
FWIW: what I've noticed is that if my phone is sitting on something, DTTW works 100% of the time. If I have it in my hand, it's very sporadic.
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
cjvphd said:
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
Click to expand...
Click to collapse
I am also having this issue after the screen has been off for a while. Anyone have a solution?
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
italia0101 said:
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
This has been my experience today.
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Do You have Greenify installed?
Globus.gd said:
Do You have Greenify installed?
Click to expand...
Click to collapse
No.
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Globus.gd said:
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Click to expand...
Click to collapse
What is greenify? And should I have it?
http://greenify.wikidot.com/
italia0101 said:
I also have this issue, [...]
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
cjvphd said:
This has been my experience today.
Click to expand...
Click to collapse
Hey guys,
same for me since today. Until some hours ago all was working fine.
But why you think it's related to dimmer/light. Because for me there is no difference when I turn on the light in room or change the timezone in settings. For now it's just not working (like broken)
I rebooted (also turned off and on) several times, turned off and on the inactivity display settings and some other tests, but nothing helped.
CHEERS
bjs339 said:
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Click to expand...
Click to collapse
Like for some others in the thread the factorymode won't be opened via *#808#
But I see the process installed and running when searching for it in settings. Maybe there is something crashed in bg?!
CHEERS
---------- Post added at 12:40 AM ---------- Previous post was at 12:05 AM ----------
UPDATE
Suddenly it began working again...
No changes in location, lighting or whatever (except 39 minutes).
But not I can confirm this laggy working of this function. No idea why...
Last days it worked like 10/10 but now maybe 4/10.
CHEERS
Launching the camera in landscape mode seems to trigger it for me occasionally.
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
A through clean up resolves the problem for my phone
i am facing the same issue with my phone. sadly i have noticed it is a reoccurring problem and it has something to do with the sensors. i tried all the fixes like toggling tap to wake, toggling face unlock assists light, clearing the cache and app data but nothing helped my case. factory reset is of no help either so i'd say don't even bother with that.
what really helped me fix this issue multiple times was something rather unexpected. what you should do is take off your phone's cover, get a wet towel, and thoroughly clean the phone all around, being especially thorough around the front facing camera and the top two edges. I give it extra attention around the front side being careful of the top speaker and after a couple of cleans and wipes both tap to wake and lift to wake starts working perfectly fine. then i put on the cover and voila it all good. Give it a try and let me know if it helped resolve this issue for you.
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Flamehell said:
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Click to expand...
Click to collapse
Hey!
The (single) tap to wake funktion will show up the ambient display, so that u can see clock, messages and use the fingerprintsensor if u want to enter.
It's a quick awake of screen to see Infos with minimal usage of display resources.
DT2W (double tab to wake) is the same as pressing the power button. So this will fully turn on screen into the lockscreen and also activate the face recognition. (for sure fingerprintsensor can be used, too)
BUT you can only activate one of those things and it will automatically turn off for example tab to wake if you activate DT2W.
Personally I like to use the single tab awake for ambient display, as I always can full activate by power button, which would be a dublicate function then.
CHEERS
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
First ppl with new update (only some hours, max a day of usage) reported in OP Forum that they didn't have any problem for now.
So seems to fix this screen awake problem.
CHEERS