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.
I use CM7. My dialer buttons are temporarily unusable or frozen while on a call. There may be a connection to the proximity sensor becaue it MAY only happen after I pull my face away from the device.
This problem comes up often, in the following circumstances:
1) I am trying to hang up (end a call) the end button doesn't work for several seconds
2) I am trying to use the touchtone keypad and can't switch to it for several seconds
3) I am trying to switch to speakerphone but the button doesn't respond for several seconds
Please advise
Sent from my HTC Vision using XDA App
I think this is a known bug.
My advice is to post in q&a section with questions. This area is for the pimps that create stuff(me not being one of them). I guess you could post question in general section as that seems to be the new q&a section
Cheers
Sent from my HTC Vision using xda premium
Yea, this is definitely a Q&A type question and should not be in the development thread.
Happens to me ALL the time...It was never fixed in CM7. Works Well in MIUI or SENSE roms though. It is always a bother to tap the End Call button 10 times to end a call...
Thread moved to proper forum.
Does anyone know how to keep this off? It keeps coming back on, I believe when i go from silent to volume again with the volume rocker. I'm not rooted and don't want to be.
posted from my GS3
monkeefied said:
Does anyone know how to keep this off? It keeps coming back on, I believe when i go from silent to volume again with the volume rocker. I'm not rooted and don't want to be.
posted from my GS3
Click to expand...
Click to collapse
Not sure being rooted or not has anything to do with it. Mine has done this once (rooted) and not sure why yet. After disabling it hasn't come back and done it yet.
When in sound settings screen does the option recheck itself when you toggle the volume rocker?
Also, how long has it been since you rebooted the device? Might try unchecking and then rebooting and see what happens. Just a thought.
Just stating the rooting thing in case someone had some funky way to fix it that required rooting. And yes the option re-checks itself every time.
posted from my GS3
monkeefied said:
Just stating the rooting thing in case someone had some funky way to fix it that required rooting. And yes the option re-checks itself every time.
posted from my GS3
Click to expand...
Click to collapse
Might read through this thread if you haven't seen it already: http://forums.androidcentral.com/sprint-galaxy-s-iii/204714-touch-sounds-turning-back-itself.html
So from that thread it seems there are 2 possible causes for this glitch:
-switching camera modes (unrooted)
-turning off camera snapshot noise (rooted)
I'm not rooted and have no option for turning off the snapshot noise, so i toggled my camera from vid to pic and it did immediately re-check the touch sound option but only the first time. For several tries after it didn't do it, only the first. I did change my camera mode earlier which if it is the cause of this glitch then that kind of proves it. I will be mindful of it if I change camera modes for verification, but It seems weird to me the camera is tied to the touch sound option.
I can confirm that the camera will cause this to happen when you switch between still to video mode. I know that I have seen (heard) it happen under other circumstances as well but I have not been able to pin it down.
I do not know of a solution for the unrooted phone. I am rooted so I went in and replaced the sound files with a silent file to permanently disable the sounds.
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can disabled it in TouchWiz. I'm not sure you can in an AOSP rom, which your 4.4 rom is.
It could also just be a ROM bug that hasn't been worked out yet. I'd check the development thread for this rom and see if it's a known issue.
If it is, help the developers by posting a logcat of the problem in the develoment threads. (Because odds are no one else has)
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You didn't get a response in a development thread because development threads are not for tech support. They are for discussing development. Tech support questions (which this is) do not belong in development threads.
The rest of XDA isn't even for tech support. We are just happy to try and assist if you get stumped. And don't get me wrong, we are legitimately happy to try and assist you. But complaining that it's "usual that no one responds to you" is pretty rude. No one promised you tech support here. If you get help, it's because someone was trying to be nice, not because you are owed an answer.
If you are using an alpha release ROM it's YOU who should be providing tech support to the developers by giving them logcats of your error so they can review them and find out what is causing the conflict. That's how you can help add to XDA and assist the developers who are building cutting edge software for you and giving it away free as a gift.
If you aren't willing to put up with the proximity sensor errors, or to help the developers fix it by providing them with the logs of the error, then your best bet is to move back to a stable build of a 4.3 or 4.2 ROM for another month or two until the major issues with 4.4 are hammered out.
As for asking for help here, what else have you tried? Have you verified that the bug doesn't exist if you revert to a different ROM?
Have you done a full wipe and clean install of the 4.4 rom and tested for the bug immediately, before installing any other apps or user data? Since you are the only one having the issue this could easily be a conflict with some other app that you have installed. The full wipe and test is the best way to confirm that or rule it out.
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same scrap happening with me. The problem is the proximity sensor is always detecting something is in its proximity (most likely dust that got in through the ear piece grill). As a result, the screen turns off immediately when a call is answered, and in Android 4.4 the power or home button can not override this. Interestingly, in 4.3 the power or home button does in fact override the proximity sensor. Why the difference between 4.4 and 4.3 I'm not sure. As Skip Jack alluded to, in Touchwiz roms under settings>my device>call> "turn off screen during calls" can be toggled off to shut down the proximity sensor. If I could find a setting like this in stock 4.4, that would solve this issue.
I need to reflash a 4.4 rom and look for this setting, although I do not think it exists.
I've tried the "pressurized air into the ear piece grill" fix, but it didn't work for me.
Any other suggestions?
https://www.youtube.com/watch?v=zm4f2XjQLAM&feature=youtube_gdata_player
QUOTE=fateownzyou3;47870242]Well iv went thru the threads of the developme, section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent I rom my SGH-M919 using xda app-developers app[/QUOTE]
Canned air didn't work. So I took my phone apart as demonstrated on YouTube , and when I peeled back the proximity sensor and gesture sensor assembly (they're one piece, attached to the earpiece) i found little bits of sand and dust. A lot. I enjoy the beach in the summer. I cleaned the sensors and the screen area that they are housed in (the part of the screen they "look" out of) with a dry q tip. after putting it all back together its as good as new. *#0*# confirms all sensors now working. The vid above is what I used. You only have to remove sim, sd card, little screws, back speaker, side housing, and a small bracket (in that order) before disconnecting and peeling back the proximity/gesture sensors in order to clean.
You don't have to remove all that other stuff.
I am having the same issue since puttin on CM 11. In 4.1 there was a setting to turn the proximity sensor off but in 4.4 there isn't. I keep looking for an app or something else to trigger it but it is also driving me crazy.
It only happens when my protective case is on my phone, but I am the type of person that NEEDs a case on their phone otherwise itll crack or drown within a couple of days. Any help would be appreciative.
I am having the same issue. Just installed CM 10.2.0-jfltetmo
How do I get a logcat to post? Also, what other information would be helpful for development?
I don't think my issue is sand in the sensor... but I will post back after I open it up and check it out.
If anyone knows of a fix or way to access settings for the proxy sensor, that would be awesome! Also, isn't there a way to use the terminal session to read data from the sensor?
Thanks for any help provided!
Another idea for those who are stuck. I didn't find a way to disable the proximity sensor, but there is another way to hang up a call. If you go into Accessibility options, there is an option to hang up call with Power button. This way you at least have a way to hang up the phone call without having to pull the battery, etc. But it doesn't help if you need to enter additional numbers on the keypad unfortunately. But at least we can hang up now!
I've been having this issue as well which seems to be an aosp bug, but for the mean time, has anyone come up with a solution? Ive tried tasker actions to turn screen on during calls but it seems to be blocked due to the proximity sensor. I know that downgrading to 4.3 is an option but a workaround must be possible. If you find it, Post it.:good:
Edit: Came across this post. Haven't tested yet but it seems promising
Edit2: Wasnt able to get the app to solve the issue as others stated
Hardware fix for proximity sensor
The apps mentioned in this forum and others did not worked for me. My phone is not rooted; perhaps this is required. Apps that I tried are:
Proximity Screen Off Lite
Caffene
I did find the Phone Tester app very useful during the surgery.
I was able to desensitize the proximity sensor as follows. The sensor is made of an IR emitter and an IR detector. It is very sensitive. Small reflections from one side to the other will cause the sensors to show "near" instead of "far."
0. When you look at the Nexus 4 straight on (front camera on top right), of the two elements on the top left, the one more to the right is the IR emitter.
1. Open the phone and gently peel back the proximity sensor/headphone jack (2 + 9 screws; pry plastic and one flex).
2. On the hole corresponding to the IR emitter, apply two small squares of masking tape cut to 1.5 mm x 1.5 mm. Only cover that hole; you do not want to cover the ambient light sensor. The masking tape blocks enough IR to desensitize the system, but won't deactivate it.
3. Gently pry up the digitizer from the phone near the corner when the sensor is. Using a toothpick, apply a drop of superglue just inside the top left corner. Apply pressure and ensure that the digitizer sits firmly on the frame. This is necessary because a slightly separated digitizer will reflect the output of the IR emitter back to the sensor (think about standing behind a window about a foot versus having your nose up to it; you don't see your reflection when you are close).
All this assumes that you know your way around opening the phone and have the correct tools. Sharp objects, execessive force along any step can break your screen or the phone in a split second. If you are not comfortable with it, don't do this.
-PD
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
You only need to post your question once. You have it in a more appropriate thread already. Please don't dig up 5 month old threads to multi post your questions.
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.