Hi guys, got my OP3 a few days ago and been loving every bit of the speed.
I encountered something last night when I turned on the on-screen navigation buttons.
I noticed that the left "back" button does not register sometimes when it is pressed.
The vibration feedback did prop, just that the "back" action was not registered to the software.
I tried swapping the Navigation buttons to recent on the left and back on the right, both the buttons work flawlessly.
Anyone experiencing this issue?
there is a (500ms?) delay if you have custom double-tap actions enabled with the capacitive buttons, but I've not heard of any issues with the software (on-screen) buttons.
I don't believe there is a 500ms delay on the back software button. Is there a way to not use the pre-installed navigation and use a third party to test it out instead?
Is there a way that the back button could be reversing some background activities? I'm saying this because the vibration did prop but the back action will not register until I press it two or three times.
Little things, but annoying when it kept happening.
I tried the touch screen tester apps and they are all working fine on that particular area.
Found a similar issue on reddit. Tracking this issue on the OnePlus forum. https://forums.oneplus.net/threads/on-screen-navigation-back-button-bug.455730/
Hi all!. I have a strange issue with the nav buttons on my OP3, both capacitive and soft. Sometimes they don't respond, and I have to touch the (back, for example) button many times until it start respond again. It happens randomly and not always... Someone having the same problem?
Click to expand...
Click to collapse
https://www.reddit.com/r/oneplus/comments/4qvf3e/oneplus_3_bugs_megathread/d5jkmu5
Hi, yes you're not alone. Getting the same problem A LOT with the back key only when using the software nav bar. It doesn't matter if the keys are swapped from left to right. The only time it doesn't happen is when I use the hard keys.
I only got this new phone yesterday, but can't remember if this problem happened before I updated to 3.2.1 which I did after setting everything up. I've tried wiping the cache partition, which doesn't help, so now considering a factory wipe to give me a clean install of the latest software. Don't think it will help somehow... I may now be tempted back to my trusty Nexus 6p in spite of its big size. At least it works properly.
SpaceGooner said:
Hi, yes you're not alone. Getting the same problem A LOT with the back key only when using the software nav bar. It doesn't matter if the keys are swapped from left to right. The only time it doesn't happen is when I use the hard keys.
I only got this new phone yesterday, but can't remember if this problem happened before I updated to 3.2.1 which I did after setting everything up. I've tried wiping the cache partition, which doesn't help, so now considering a factory wipe to give me a clean install of the latest software. Don't think it will help somehow... I may now be tempted back to my trusty Nexus 6p in spite of its big size. At least it works properly.
Click to expand...
Click to collapse
Added you to the list. Please keep us updated if there's a fix.
Just to add, I factory reset the phone earlier and the back button problem hasn't completely stopped but is less frequent now - at least so far.
If there are any habitual OP3 nav bar users out there, can you confirm if this happened before the 3.2.1 update? Btw, tried running the phone in safe mode yesterday to check if an app was causing this, but it made no difference. Looks like a sure fire software bug to me.
Yea .... facing th same issue
Same issue on 3.2.1
I think we can pretty much confirm that this happens to most of us who uses the software back button.
The only temporary fix for this for now is to swap the buttons, the back button works flawlessly (if I recall properly) when it is on the right side.
So far the back soft key issue seems fixed on today's 3.2.2 update. Well so far so good anyway.
---------- Post added at 03:36 PM ---------- Previous post was at 02:44 PM ----------
Scratch that. It's still not fixed, just takes a while to reveal itself after the update. Back to the hard keys - sigh!
Sam L said:
Hi Everyone,
We've begun rolling out OxygenOS 3.2.2 for the OnePlus 3 today. Here's what's new in this update:
Improved notification management in doze.
Addressed alert slider/silent mode issue.
Disabled fingerprint sensor while in pocket.
Added NFC toggle in quick settings.
Improved noise cancellation in video recording.
Updated 4K video recording codec.
Added latest security patches and various optimizations.
As usual, the rollout will be incremental. We will do our best to get everyone covered as quickly as possible. Please give us your thoughts and feedback in the comments below!
Thanks
Click to expand...
Click to collapse
Updated to 3.2.2, issue still persists.
Judging from the fact that hardly anybody on this forum or the One Plus forums is talking about this bug, I get the feeling that it won't be considered a major priority for fixing in any upcoming software updates. Nevertheless I switched back to software buttons last night to see if I could figure out if there's any pattern to the back button problem. I now think it may be related to how quickly you tap the button. Basically, when I tap the back button very fast, where my finger makes contact with the screen for only the briefest of moments, it seems to work properly every single time. Therefore I'm wondering if the bug may be caused by a button trigger value that's way too short. If the tap is too long the button timer fails to register a successful tap. Er, if such a timer even exists of course - I'm no button expert.
I'm also aware this may be some kind of placebo effect and the button action is actually just as flaky as before, and it's merely a coincidence I haven't seen the bug when I'm making an effort to tap the key fast. However, I wondered if anyone could put this daft idea to the test. The best way to do it is to hold the phone with one hand while you use the index finger of the other hand to tap the screen. I've found that It's harder to tap fast with your thumb if you're using the phone one-handed.
And don't flame me if this doesn't work for you as I admit I may be totally wrong here.
SpaceGooner said:
Judging from the fact that hardly anybody on this forum or the One Plus forums is talking about this bug, I get the feeling that it won't be considered a major priority for fixing in any upcoming software updates. Nevertheless I switched back to software buttons last night to see if I could figure out if there's any pattern to the back button problem. I now think it may be related to how quickly you tap the button. Basically, when I tap the back button very fast, where my finger makes contact with the screen for only the briefest of moments, it seems to work properly every single time. Therefore I'm wondering if the bug may be caused by a button trigger value that's way too short. If the tap is too long the button timer fails to register a successful tap. Er, if such a timer even exists of course - I'm no button expert.
I'm also aware this may be some kind of placebo effect and the button action is actually just as flaky as before, and it's merely a coincidence I haven't seen the bug when I'm making an effort to tap the key fast. However, I wondered if anyone could put this daft idea to the test. The best way to do it is to hold the phone with one hand while you use the index finger of the other hand to tap the screen. I've found that It's harder to tap fast with your thumb if you're using the phone one-handed.
And don't flame me if this doesn't work for you as I admit I may be totally wrong here.
Click to expand...
Click to collapse
Well for me pressing it a brief amount of time or pressing the button for a long period of time doesn't make much of a difference.
The effects are too random for me and it's even harder to make a video out of this because of the randomness.
Why would you want to use on-screen navigation buttons on this phone if i may ask? [emoji12]
Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
Guys, I was fighting with OnePlus Support regarding the issue on the weekend, even captured a video demonstrating the bug. At one moment I just forwarded a conversation with TS to Carl Pei directly. Eventually got a response from both TS and Carl that their developers will fix this in the next update. Took a lot of nerves to get a proper answer.
odin13 said:
Why would you want to use on-screen navigation buttons on this phone if i may ask? [emoji12]
Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
Click to expand...
Click to collapse
For me at least there are a few reasons:
1) I often use my phone one-handed while holding a railing with the other hand standing on a busy train to/from work. I find it much easier to use the soft nav keys as they are about 2cm above the bottom of the device, which means I can support the phone more easily with my little finger under it. When I use the hard keys I really have to strain my thumb to use them and hold the device as they are too close to the edge for me. Using the on-screen keyboard is also easier for me swiping one-handed if it's also higher up.
2) I appreciate using the hard keys give the perception that the screen is bigger, but in many situations that doesn't make using the device any better, except there's maybe slightly less scrolling involved. Just because I can see more e-mails listed at once or see more text at the same time on a bigger screen, doesn't mean I can photographically read all of it in one blink.
3) I find the camera easier to use when I use soft keys as I can hold the 'chin' of the device. If I use the hard keys, I have to take care to avoid touching them by holding the thin edge of the device. Generally on devices with hard keys I accidentally press the nav keys a lot more.
4) In most cases, multimedia and gaming is not affected by soft keys, which just auto-hide so the game or movie can use the whole screen. As with the camera, I find it easier to play games when I don't keep hitting nav keys by mistake, which I do much more with the hard keys enabled.
5) Lastly, you could argue that Google intends Android to be used with soft keys. My last 4 nexus phones had them and a lot of other OEMs favour them. I guess that's what I'm most used to, and that's my main reason. I concede there are probably more people who've had Samsung devices than Nexuses, so they will no doubt prefer hard keys - maybe with the back button on the right. One of the great things about the OP3 is that in theory, it should work for every user's preferences.
Don't get me wrong, soft keys are not perfect. For some older apps they don't auto-hide - and with some apps that are up-to-date most notably the Chrome browser and Google maps and sat nav where the screen really is bigger with hard keys. The important thing is that if the OP3 has the option to use soft keys, they really should just work whether you like them or not.
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
FiMAX said:
Guys, I was fighting with OnePlus Support regarding the issue on the weekend, even captured a video demonstrating the bug. At one moment I just forwarded a conversation with TS to Carl Pei directly. Eventually got a response from both TS and Carl that their developers will fix this in the next update. Took a lot of nerves to get a proper answer.
Click to expand...
Click to collapse
If this is true and the big guy himself has responded directly, then you sir are a hero. Well done for your persistence.
SpaceGooner said:
If this is true and the big guy himself has responded directly, then you sir are a hero. Well done for your persistence.
Click to expand...
Click to collapse
Yes, that's the truth. I can not post external links or attach images as a proof because I'm a new member on XDA (usually use it in a read-only mode). It took two support agents of a first line only to create a case with a number. Then a long conversation via email.
FiMAX said:
Yes, that's the truth. I can not post external links or attach images as a proof because I'm a new member on XDA (usually use it in a read-only mode). It took two support agents of a first line only to create a case with a number. Then a long conversation via email.
Click to expand...
Click to collapse
I have no reason to doubt you mate, it's whether the reply actually came from Carl Pei and not one of his customer services people using his name. Either way, at least you've brought this issue to their attention and have got some kind of favourable response. Fingers crossed they follow this up like they told you.
It also shows that while people like me just moan and talk about the problem, you may have achieved a lot more with direct action.
Still no fix for this bug in 3.2.4. On screen back button still as flaky as before.
Related
Dear all,
I'd like to share a solution with the global HTC Desire community to the "buttons not working properly" issue.
My problem was that after a few months of use, some buttons of my HTC Desire began to not be as responsive as before.
It started by the "back button" and then the "home button" ; I had to push harder on it to get it work.
I saw several topics on this subject and no one proposed a solution that was really working.
Some people were saying that it was a software issue but as I had changed everything on my Desire since the first day I got this issue, I was sure it was hardware related.
I was about to follow the disassembly tutorial on youtube to have a look at the buttons more accurately but my father proposed to use a "moisture remover" before.
The product is this one but I'm sure some equivalent can be found:
MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
Basically, from what I understood, it helps to dry the parts where you use it (might help also from swimming pool issue...).
We turned off the phone, and used it directly on the buttons, trying to get the product inside (the buttons are quite loose so it was definitely feasible).
I turned on the phone 1min later and I'm still very impressed of the result.
Every button are now working properly (no need to press harder) and they react like the first day I got my phone. This is is very impressing and for all who might have the same issue than me I'd like to see if it works for everyone. It seems that my phone got wet some day (which doesn't surprise me at all) and the wetness never left, messing with the buttons.
Let us know if I'm right !
Cheers !
So, is it still working?
Thanks for the tip. Had the same problem with my year old Desire. I just tried this with some PCB & Flux cleaner from Maplin (£3.99) and so far it seems to working much better.
Will see how long it lasts.
hi all
same problem here
do you think that crc 2-26 will do the trick? http://www.google.it/search?q=crc+2...=mode_link&ct=mode&cd=1&sqi=2&ved=0CC4Q_AUoAA is it similar to what you used? i meanm is it a simple electronic pray (yet "liquid") contact cleaner?
i'm a little afraid of using that on the phone... i tried compressed air but didn't work
thanks
luca
Thanks, i got this issue with the volumebuttons
Hope this help to my phone's volumeUp button.
markus1540 said:
Thanks, i got this issue with the volumebuttons
Click to expand...
Click to collapse
Me too struggle to get it to go into recovery.
I'm based in Sydney, Australia
Following your advice I found a similar product in a Auto shop
I bought a can of Contacts Cleaner, non conductive, plastic safe and leaving no residue
AND IT WORKED PERFECTLY
THANK YOU SO MUCH
deakodude said:
Me too struggle to get it to go into recovery.
Click to expand...
Click to collapse
boot into fastboot (back & power)
Code:
fastboot oem gencheckpt
or from system
Code:
adb reboot recovery
My back button is starting to die too!
Will definitely look into the solutions posted in this thread!
I had this trouble and found an app called 'Button Savior' which displays an icon on the screen that when tapped displays a 'strip' of buttons onscreen (Home, Menu, Back etc)
It requires root for full functionality and as I am rooted I don't know what functionality it would have for un-rooted phones.
say it also works for the volume button? if I do not crush very strong does not work ... it is for what?
It has Home, Menu, Power, Back, Phone, Search and Camera buttons.
There is also an app callled 'Volume Widget' which allows you to put a widget on a screen to turn up or down the volume for Call/Music/Ringer etc.
tried it and it stained my screen....streaks shooting up when white
mattg said:
Thanks for the tip. Had the same problem with my year old Desire. I just tried this with some PCB & Flux cleaner from Maplin (£3.99) and so far it seems to working much better.
Will see how long it lasts.
Click to expand...
Click to collapse
Used this and worked a treat. did two attempts as didn't want to cover the phone, only the buttons which weren't working. Now my buttons are working like new.
nounours_32 said:
Dear all,
I'd like to share a solution with the global HTC Desire community to the "buttons not working properly" issue.
My problem was that after a few months of use, some buttons of my HTC Desire began to not be as responsive as before.
It started by the "back button" and then the "home button" ; I had to push harder on it to get it work.
I saw several topics on this subject and no one proposed a solution that was really working.
Some people were saying that it was a software issue but as I had changed everything on my Desire since the first day I got this issue, I was sure it was hardware related.
I was about to follow the disassembly tutorial on youtube to have a look at the buttons more accurately but my father proposed to use a "moisture remover" before.
The product is this one but I'm sure some equivalent can be found:
MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
Basically, from what I understood, it helps to dry the parts where you use it (might help also from swimming pool issue...).
We turned off the phone, and used it directly on the buttons, trying to get the product inside (the buttons are quite loose so it was definitely feasible).
I turned on the phone 1min later and I'm still very impressed of the result.
Every button are now working properly (no need to press harder) and they react like the first day I got my phone. This is is very impressing and for all who might have the same issue than me I'd like to see if it works for everyone. It seems that my phone got wet some day (which doesn't surprise me at all) and the wetness never left, messing with the buttons.
Let us know if I'm right !
Cheers !
Click to expand...
Click to collapse
Man, your father is a genius. It worked perfect for me, got myself a KONTAKT LR spray (easier to find in switerland) which does the job at 100%, my back button is working perfect now, the volume button is also like new. Thank you guys.
Yes !
nounours_32 said:
Dear all,
I'd like to share a solution with the global HTC Desire community to the "buttons not working properly" issue.
My problem was that after a few months of use, some buttons of my HTC Desire began to not be as responsive as before.
It started by the "back button" and then the "home button" ; I had to push harder on it to get it work.
I saw several topics on this subject and no one proposed a solution that was really working.
Some people were saying that it was a software issue but as I had changed everything on my Desire since the first day I got this issue, I was sure it was hardware related.
I was about to follow the disassembly tutorial on youtube to have a look at the buttons more accurately but my father proposed to use a "moisture remover" before.
The product is this one but I'm sure some equivalent can be found:
MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
Basically, from what I understood, it helps to dry the parts where you use it (might help also from swimming pool issue...).
We turned off the phone, and used it directly on the buttons, trying to get the product inside (the buttons are quite loose so it was definitely feasible).
I turned on the phone 1min later and I'm still very impressed of the result.
Every button are now working properly (no need to press harder) and they react like the first day I got my phone. This is is very impressing and for all who might have the same issue than me I'd like to see if it works for everyone. It seems that my phone got wet some day (which doesn't surprise me at all) and the wetness never left, messing with the buttons.
Let us know if I'm right !
Cheers !
Click to expand...
Click to collapse
Yes ! It really works!
I have a HTC Desire brown and my Home, Menu and volume down buttons were barely working.
I used MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
because the suggested product above is not available here in Belgium.
I removed the back panel and the battery. Then carefully sprayed some flux remover on the malfunctioning buttons, waited a minute and done!
Thanks so much to you and your dad for sharing this solution !
I can really recommend it to everyone with this problem.
Dell Venue pro
rudidu said:
My back button is starting to die too!
Will definitely look into the solutions posted in this thread!
Click to expand...
Click to collapse
nounours_32 said:
Dear all,
I'd like to share a solution with the global HTC Desire community to the "buttons not working properly" issue.
My problem was that after a few months of use, some buttons of my HTC Desire began to not be as responsive as before.
It started by the "back button" and then the "home button" ; I had to push harder on it to get it work.
I saw several topics on this subject and no one proposed a solution that was really working.
Some people were saying that it was a software issue but as I had changed everything on my Desire since the first day I got this issue, I was sure it was hardware related.
I was about to follow the disassembly tutorial on youtube to have a look at the buttons more accurately but my father proposed to use a "moisture remover" before.
The product is this one but I'm sure some equivalent can be found:
MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
Basically, from what I understood, it helps to dry the parts where you use it (might help also from swimming pool issue...).
We turned off the phone, and used it directly on the buttons, trying to get the product inside (the buttons are quite loose so it was definitely feasible).
I turned on the phone 1min later and I'm still very impressed of the result.
Every button are now working properly (no need to press harder) and they react like the first day I got my phone. This is is very impressing and for all who might have the same issue than me I'd like to see if it works for everyone. It seems that my phone got wet some day (which doesn't surprise me at all) and the wetness never left, messing with the buttons.
Let us know if I'm right !
Cheers !
Click to expand...
Click to collapse
Hi,
I had the same problem on my dell venue pro the letters E, I, D, L and X did not, even when I pressed so hard, but as you recommended I had to cleaned up and surprise...it worked and still doing.....thanks a lot!
thanks, working well also with deoxidizer for contacts (contact cleaner).
My desire is reborn!!!!!
nounours_32 said:
Dear all,
I'd like to share a solution with the global HTC Desire community to the "buttons not working properly" issue.
My problem was that after a few months of use, some buttons of my HTC Desire began to not be as responsive as before.
It started by the "back button" and then the "home button" ; I had to push harder on it to get it work.
I saw several topics on this subject and no one proposed a solution that was really working.
Some people were saying that it was a software issue but as I had changed everything on my Desire since the first day I got this issue, I was sure it was hardware related.
I was about to follow the disassembly tutorial on youtube to have a look at the buttons more accurately but my father proposed to use a "moisture remover" before.
The product is this one but I'm sure some equivalent can be found:
MicroCare MCC-DC1 - VeriClean™ Flux Remover - 10 oz Aerosol Can
Basically, from what I understood, it helps to dry the parts where you use it (might help also from swimming pool issue...).
We turned off the phone, and used it directly on the buttons, trying to get the product inside (the buttons are quite loose so it was definitely feasible).
I turned on the phone 1min later and I'm still very impressed of the result.
Every button are now working properly (no need to press harder) and they react like the first day I got my phone. This is is very impressing and for all who might have the same issue than me I'd like to see if it works for everyone. It seems that my phone got wet some day (which doesn't surprise me at all) and the wetness never left, messing with the buttons.
Let us know if I'm right !
Cheers !
Click to expand...
Click to collapse
how you that.. i too facing same problem.
Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,
urundai said:
Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,
Click to expand...
Click to collapse
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.
urundai said:
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.
Click to expand...
Click to collapse
If it is launching Different apps then it is the Quick launch that is the cause. You can see what Shortcut is associated with which app go here:Settings -> Applications -> Quick Launch
Most Launch with Search + any key. Perhaps your search button is stuck.
JB
Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?
If the random apps are opening, open the landscape keyboard and press the search button. If you accidentally press it and then you press a corresponding letter to open a certain app, it'll so that. And when you hit back, the phone thinks that you pressed the wrong letter key and has that quick open on. Just press search again. That's all lol
Sent from my SAMSUNG-SGH-I927R using xda premium
I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx
phatryan69 said:
Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?
Click to expand...
Click to collapse
I am on stock. It's just annoying when it happens at least once in 2 days.
I am thinking of rooting it and installing a custom rom to see if that takes care of it. Will keep you all posted.
I might turn on the debugging level in the logs as well to see if I can find out what's going on. Given that this happens only every two days or so, not sure if that will help much but let me see.
antonyfirst said:
I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx
Click to expand...
Click to collapse
I am on Rogers stock ROM. At this point, it certainly looks like something to do with the software (will be hard to find several of us having the same hardware problem).
dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
+1.
My keyboard stops working too, but this doesn't happen very often. I experience this about once in 3-4 weeks for now.
I have had this problem a few times as well (on stock AT&T).. QWERTY doesn't respond at all, reboot fixes it! Got me worried the first couple of times though
I continue to run in to this once in a while. I have tried pressing all kinds of keys (search, alt etc) with no success. At times, I see some of the keys working but not others.
Anyway, this looks like software / driver issue. Looks like reboot is the only cure so far.
Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse
I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result
In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.
tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?
tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.
jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers
superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time
Just got this and love it but two questions
After the firmware update I noticed the tab rebooted itself twice just sitting overnight. I know this because my tabs and phones are set to ask for my code to boot the OS. It didnt happen the next two days so should I be worried about this or was it just more update reboots? I know android always asks before reboots but maybe google was being sneaky.
The soft button placement annoys the F*** OUT OF ME!
I hate having them on the bottom corners and want them back in the middle like EVERY OTHER ANDROID DEVICE!
Is there a way to position these back to center so I can feel at home again?
thanks
You like them in the center so they're harder to reach when holding it? Lol
The only way I know to change the location is to root it, install Xposed and then Gravity Box.
Sent from my Nexus 6 using Tapatalk
I always hold it one handed so close together is actually better for me
Sent from my Pixel C using XDA Free mobile app
tevil said:
Just got this and love it but two questions
After the firmware update I noticed the tab rebooted itself twice just sitting overnight. I know this because my tabs and phones are set to ask for my code to boot the OS. It didnt happen the next two days so should I be worried about this or was it just more update reboots? I know android always asks before reboots but maybe google was being sneaky.
The soft button placement annoys the F*** OUT OF ME!
I hate having them on the bottom corners and want them back in the middle like EVERY OTHER ANDROID DEVICE!
Is there a way to position these back to center so I can feel at home again?
thanks
Click to expand...
Click to collapse
There are in fact multiple "possible spontaneous reboot"-sources even in the stock kernel; I'm trying to fix them all, Pokemon-style, in my custom kernel. V3-RC5 seems to be absolutely solid so far. If that's your thing, anyway.
cheep5k8 said:
There are in fact multiple "possible spontaneous reboot"-sources even in the stock kernel; I'm trying to fix them all, Pokemon-style, in my custom kernel. V3-RC5 seems to be absolutely solid so far. If that's your thing, anyway.
Click to expand...
Click to collapse
Yup did it to me again today. Never while using it. Im wondering if doze is causing it to shut off fully
tevil said:
Yup did it to me again today. Never while using it. Im wondering if doze is causing it to shut off fully
Click to expand...
Click to collapse
Just bugs in various drivers. Quite unspectacular, but problematic.
tevil said:
I always hold it one handed so close together is actually better for me
Sent from my Pixel C using XDA Free mobile app
Click to expand...
Click to collapse
This is a pretty beefy tablet to hold one handed, also having the buttons in the center would make it harder to use one-handed IMO since you would have to stretch to the center instead of the edge to press a button. To each his own I guess.
I also get random reboots. I've only had the thing for three hours, and aside from the three system updates (the latest to N2), it's rebooted seven times. Nine times, actually - two were caused by connecting an Xbox One pad, which I guess it doesn't like. The other seven were just random.
On the other hand, I really like the softkey placement. It reminds me of TabletUI, which I really loved and hated that Google took it away.
brando56894 said:
This is a pretty beefy tablet to hold one handed, also having the buttons in the center would make it harder to use one-handed IMO since you would have to stretch to the center instead of the edge to press a button. To each his own I guess.
Click to expand...
Click to collapse
Piecontrol... Barely used the normal buttons ever
i had two reboots the first day after updating to the 2nd n preview, but they've since stopped. those were the only two i've ever had.
also, i think you may be the exception as far as buttons go. most tablet users hated the buttons in the middle since we naturally hold it by the sides or bottom corners. you must have huge hands to be able to hold this thing on handed.
Considering that there's a giant piece of screen real estate dedicated to three buttons which are either in the middle or grouped at both ends, I can't see a good reason not to have all three buttons at both ends.
It makes sense to me that if the placement is important enough that Google would change it then it should also be customizable. I miss the old customization on some 4.4/5.0 ROMs where you could just add anything you want. I'd settle for the long press to switch to the last app.
I'm trying to find a way to place all soft buttons in one corner of my Nexus 9. Though i'm on CM13 it doesn't seem to have such an option for back/home/recent buttons.
I like pixel c buttons position
I've also got problems with the random reboots. To track the reboots I've installed the free app Boot Logs. So far, there were 7 reboots today. This problem occured after installing the may OTA update. Flahing back to the april update helps but is no permanent solution. The june update isn't helping either (according to people in this forum/thread: https://productforums.google.com/forum/#!topic/nexus/i7e4gsZxzEQ). I've contacted Google and will get a replacement - hopefully without this problem
https://www.xda-developers.com/samsung-good-lock-samsung-galaxy-android-oreo/
Works brilliantly, I live in UK, and have to use the quick short maker app, must have for stock roms
Installed them all, played about with them all, only one I kinda like is the recent apps one, but even that I'm beginning to get a bit sick of now, pretty much the same experience of when I tried it on either my S5 or S7, that also got uninstalled very quickly
MattJaO3D said:
https://www.xda-developers.com/samsung-good-lock-samsung-galaxy-android-oreo/
Works brilliantly, I live in UK, and have to use the quick short maker app, must have for stock roms
Click to expand...
Click to collapse
Blurred QS Bg is also in Goodlock?
Yep, blurred options are available
The new task changer is so good. If you quickly switch between the 2 recent apps by quickly double tapping there's no lag whatsoever. Old version had a little hiccup!
stevenl23 said:
The new task changer is so good. If you quickly switch between the 2 recent apps by quickly double tapping there's no lag whatsoever. Old version had a little hiccup!
Click to expand...
Click to collapse
Yea I liked it too but my muscle memory has gotten used to swiping left/right to clear recent apps and was constantly doing that instead of swipe up/down, so have reverted back
Think I'm stuck in my ways tbh, at least with Samsung, same reason I cannot think of anything I would like to use the Bixby button for, so it just sits there useless, maybe with a different manufacturer's phone I could change my habits
*Detection* said:
Yea I liked it too but my muscle memory has gotten used to swiping left/right to clear recent apps and was constantly doing that instead of swipe up/down, so have reverted back
Think I'm stuck in my ways tbh, at least with Samsung, same reason I cannot think of anything I would like to use the Bixby button for, so it just sits there useless, maybe with a different manufacturer's phone I could change my habits
Click to expand...
Click to collapse
Use bxactions!! I use it and if you give it increased control just by following the instructions (involves plugging into computer). It's so good because I've programmed it to launch google assistance, pause music, flightlight etc.
This is the last versión 1.0.00.27?
stevenl23 said:
Use bxactions!! I use it and if you give it increased control just by following the instructions (involves plugging into computer). It's so good because I've programmed it to launch google assistance, pause music, flightlight etc.
Click to expand...
Click to collapse
Like I said, I can't think of anything I would want to use the Bixby button for, I don't need another button for anything
I know about bxactions, I tried it (buggy) but even still there was no action I wanted to map that button for
Maybe if I lived in a cave it would be handy for the flashlight...
*Detection* said:
Like I said, I can't think of anything I would want to use the Bixby button for, I don't need another button for anything
I know about bxactions, I tried it (buggy) but even still there was no action I wanted to map that button for
Maybe if I lived in a cave it would be handy for the flashlight...
Click to expand...
Click to collapse
It's pretty buggy if you don't give it full control or whatever its called. Involves plugging in computer and executing a file on phone. Cause otherwise it launches bixby for a split second and is pretty annoying. And for the flashlight, sure you don't need it all the time but it dos have its uses once in a while. The better features for me is pause music, skip song and importantly launch google assistant instead of bixby
stevenl23 said:
It's pretty buggy if you don't give it full control or whatever its called. Involves plugging in computer and executing a file on phone. Cause otherwise it launches bixby for a split second and is pretty annoying. And for the flashlight, sure you don't need it all the time but it dos have its uses once in a while. The better features for me is pause music, skip song and importantly launch google assistant instead of bixby
Click to expand...
Click to collapse
Yea I executed that file with adb and the phone connected originally, I set it up via the instructions but it wanted to do something other than I told it to
The button is just in an awkward place for me, I press it whenever I pick up the phone, or press the power button, they've placed it in such a position that they get a load of stats saying it's being used 10x more than it really is due to accidental presses, similar to when Microsoft changed the X close button to OK Accept for upgrading to 10 and claimed it was a mistake
Above the volume up or above the power key would have been a better place, somewhere you only press it when you mean to
If I map it for flashlight or anything else I'm gonna get sick of constantly accidentally launching whatever I map it to
Maybe in 12 months when the novelty of a new phone has worn off I`ll start playing about with it but quite happy to have it do nothing atm
I never had the chance to try this on my S7, so it's a breath of fresh air on my S9. Trying everything now to see what I'll keep. So far the lockscreen options are nice indeed.
*Detection* said:
Yea I executed that file with adb and the phone connected originally, I set it up via the instructions but it wanted to do something other than I told it to
The button is just in an awkward place for me, I press it whenever I pick up the phone, or press the power button, they've placed it in such a position that they get a load of stats saying it's being used 10x more than it really is due to accidental presses, similar to when Microsoft changed the X close button to OK Accept for upgrading to 10 and claimed it was a mistake
Above the volume up or above the power key would have been a better place, somewhere you only press it when you mean to
If I map it for flashlight or anything else I'm gonna get sick of constantly accidentally launching whatever I map it to
Maybe in 12 months when the novelty of a new phone has worn off I`ll start playing about with it but quite happy to have it do nothing atm
Click to expand...
Click to collapse
True, the button is very easy to press, i have a case so less of a issue for me. Yeah i would root my phone but the disadvantages that arise greatly outweigh the benefits
Good lock has been officially released for the US galaxy store
Will it be available in the EU too?
ja-ki said:
Will it be available in the EU too?
Click to expand...
Click to collapse
Hopefully it will be, it's a good app, best for custom without root, the other apps are good also, the newer edge lighting has more effects, and also a routine app, one handed mode + and edge touch which I not used yet.
Thanks for the links! After installing all the apps I found that I preferred the way Samsung gave me my device!
However I've still retained one hand operation +, edge lighting plus and quickstar. The rest of the apps didn't seem to attract me much.
Thanks again!
Cheers!
Sent from my SM-N950F using Tapatalk
I really like it, bit more customisation is always a good thing.
I got the "Badlock" version here which doesn't need any other apps to be able to change settings etc. - https://forum.xda-developers.com/galaxy-s8+/how-to/lock-lock-2018-8-0-devices-t3804657
http://apps.samsung.com/appquery/appDetail.as?appId=com.samsung.android.goodlock
It's now out officially for UK
MattJaO3D said:
http://apps.samsung.com/appquery/appDetail.as?appId=com.samsung.android.goodlock
It's now out officially for UK
Click to expand...
Click to collapse
Don't tell me Canada got it before the UK... Eeek ??????
Sent from my Galaxy S9+ using XDA Labs