It happens to me quite a bit when i open up the keyboard..sometimes i'll get just a "t", lots of times "ty." I don't think it's a coincidence that they happen to be the 2 top most centered keys, but I don't think the casing is rubbing and pressing the buttons. Is anyone else experiencing this? It is pretty annoying cause you always have to delete them before you type anything
i get them as well since i last updated (CRC r11.0)
same rom as me...
hmmm....better check in that thread
Mine does it as well using TNT's Rom. I don't think it's rom related, as every ROM I've used has done this.
It may not look like it, but I'm betting your casing it rubbing. I know mine is by using dry erase marker and seeing the transfer on the T and Y keys.
Good luck
lol.. i get them also.. but it only happens sometimes...
im using FARIA-R32-XDA2 rom
Yea, sitting here playing with mine, you're right, only sometimes. Seems it depends how I open the slide, how it torques, etc.
TY
No... It never hppened to me, actually... No matter what ROM I use...
I wish I could help.
Iim sorry...
Cheers.
Your phone is thanking you for installing a new rom! TY!
TY
Hello Together,
I think it is a hardware problem. When push with your thumbs on the bottom of the screen while you slide out the keyboard (this is my normal methode to slide it out) you push the characters T and Y because they are in the middle of the upper row.
I wonder if it is possible to lock the buttons (in software) till the slider is out completely (when the screen rotates). Does anyone know a register or software solution?
Greetings Pudl
yes its a hardware problem...your keyboard cable is a bit loose probably...
you have to take your phone apart to fix that
its the bottom left ribbon cable with a flat silver plate that u need to unplug when u seperate the motherboard
and the screen rotation is activated by some magnetic thingy if i remember correctly
hehe,i also think it's the hardware problem
Capacitive Touch acting up ever since OTA update w/ unlock pattern &Onscreen Keyboard
Has anyone else had problems with their touch input since the OTA update? When I enter my unlock pattern, there a 33% chance it gets screwy with my input, and I must hit the power button to enter it into standby, then turn it back on again in order to get it working.
Also, sometimes when I use the second function letter keys on the onscreen keyboard, (example "k" is also "?" if held down for a second) the second function key does not appear. Upon holding, it just shows the hovering letter ("k" for example) and then it disappears while still holding down.
This happens I'd say 50% of the time.
Anyone else having these problems?
Can a MOD please move this to the EVO 4G General Section, my bad
Can a MOD please move this to the EVO 4G General Section, my bad
Thanks!
Anytime I run a custom rom based off the ota my screen acts crazy..
Sometimes it has a mind of its own and starts pressing stuff by itself..
I've heard others mention it also but apparently not enough people for anyone to look into it though.
MrDSL said:
Anytime I run a custom rom based off the ota my screen acts crazy..
Sometimes it has a mind of its own and starts pressing stuff by itself..
I've heard others mention it also but apparently not enough people for anyone to look into it though.
Click to expand...
Click to collapse
Thanks for your input!
I am running stock though, weird huh?
I'm not too worried, the Froyo update should fix it
kyelerner said:
Thanks for your input!
I am running stock though, weird huh?
I'm not too worried, the Froyo update should fix it
Click to expand...
Click to collapse
mine isnt stock but it is the same ota as you version wise so it has to be something in there.
mine does this too!!!!!!!
My hardware buttons on the bottom, back home and menu have quit working. I have a hairline crack on the bottom right, but has been working fine with it on there. I flashed the AOSB rom but, i wouldn't think it has anything to do with it not working?
my question, and I believe I know the answer, would flashing back to stock in any way work to fix this problem?
octonaut said:
My hardware buttons on the bottom, back home and menu have quit working. I have a hairline crack on the bottom right, but has been working fine with it on there. I flashed the AOSB rom but, i wouldn't think it has anything to do with it not working?
my question, and I believe I know the answer, would flashing back to stock in any way work to fix this problem?
Click to expand...
Click to collapse
It sounds like it is mechanically broken to me. Can't say for sure, but when a symptom like that appears after mechanical damage, there is a significant possibility that the two are related.
tferrari said:
It sounds like it is mechanically broken to me. Can't say for sure, but when a symptom like that appears after mechanical damage, there is a significant possibility that the two are related.
Click to expand...
Click to collapse
what I dont understand, is the buttons worked after it cracked?
So what would change?
octonaut said:
what I dont understand, is the buttons worked after it cracked?
So what would change?
Click to expand...
Click to collapse
It's entirely possible that the malfunction happened some time after the ''crack''. (Due to using the device while it is damaged) If you haven't already, you can try going back to stock rom. If the buttons still don't respond, it's unfortunately an hardware issue.
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.
I have the official samsung keyboard and periodically get repeated keys (c key seems to be a consistant problem). Anyone have any ideas if this is a software problem or hardware? Note, Samsung is NOT giving me the latest patches for some reason. I am in NZ. Anyway to get the latest???? VPN doesn't seem to work either.
Details
SM-T830
T830XXU2ARJ3/T830OLM2ARJ3
Do you mean onscreen Keyboard or Keyboard case?
If you mean Keyboard Case then I suggest you return it and get a new one.
If you mean onscreen Keyboard then something wrong with the touchscreen...either hardware issue or something on the surface of the touchscreen causing it.
Usually sweaty palm can cause accidental/repeated touch.
d4rkkn16ht said:
Do you mean onscreen Keyboard or Keyboard case?
If you mean Keyboard Case then I suggest you return it and get a new one.
If you mean onscreen Keyboard then something wrong with the touchscreen...either hardware issue or something on the surface of the touchscreen causing it.
Usually sweaty palm can cause accidental/repeated touch.
Click to expand...
Click to collapse
keyboard case. I will look into returning. Thank you.
d4rkkn16ht said:
Do you mean onscreen Keyboard or Keyboard case?
If you mean Keyboard Case then I suggest you return it and get a new one.
If you mean onscreen Keyboard then something wrong with the touchscreen...either hardware issue or something on the surface of the touchscreen causing it.
Usually sweaty palm can cause accidental/repeated touch.
Click to expand...
Click to collapse
I just returned the keyboard and I am having the same problem on the new keyboard. Do you think this is a software problem or a hardware one?
conzar said:
I just returned the keyboard and I am having the same problem on the new keyboard. Do you think this is a software problem or a hardware one?
Click to expand...
Click to collapse
I think the problem is Samsug Dex and not the keyboard. I have disabled dex and am able to type without the repeating key problem. So my conclusion now is that its a software issue and its a problem with Samsun Dex.
Repeating letters
Had the same problem after taking phone to Samsung FixIt store for another problem. Sent phone back to Samsung. They fixed it.