Develop Bugs

[Q] Freezing

Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?

Seems like a software issue which can be easily remedied.

Username invalid said:
Seems like a software issue which can be easily remedied.
Click to expand...
Click to collapse
When I first got my new Nexus 7 I did notice some "freezes" and unresponsiveness. Touches that would go unrecognized (links in the browser, back button). did a factory reset and watched it in case I decided I needed to exchange it. But it is seemed to improve and I rarely run into the freezing.
I've so far not returned/exchanged it, but an still keeping an eyes on it.

I have most certainly experienced a heavy freeze period while typing on the onscreen keyboard. While typing in all the credentials on first set-up I experienced moments of almost 20 seconds of non-response, followed by all input entering as if it was lagged out network style.
Rooting and flashing a new rom, this has yet to happen. This is why I love Android so much... its community knows that it is Unix and treats it as such.

Yea mines freeze sometimes
Sent from my Nexus 7 using Tapatalk 4 Beta

yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta

jayochs said:
yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.

Gabik123 said:
Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?
Click to expand...
Click to collapse
I have seen this several times with the Swipe keyboard. Since going back to SwiftKey it has not happened.

Gabik123 said:
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.
Click to expand...
Click to collapse
I was wondering if its really the kernal that's causing the freezing. My N7 2013 right now freezes after about 15 minutes of turning it on, and the only way to unfreeze is by holding down the power for 10 seconds. My tablet will constantly do this after each turn on, but once I placed it in safe-mode there is no freezing. I am thankful that mine doesn't have the touch screen issue though! but this freezing problem is really driving me bonkers.

I nodded off for a few minutes the other day when I had FBReader up and when I woke up and tried to exit it was non-responsive. I get the impression FBReader forces the screen to stay on, but perhaps everything else goes to sleep anyway? That's the only freeze I can remember seeing.

Crazy Touch Screen Not Responding Bugs with my G3

So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot

I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk

@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.

deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).

^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.

Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.

@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?

I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96

Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.

This is happening when the screen is on right? Or is the screen turning off and then not turning I again?

You need to keep Knock feature on, someone already said this. That's why your screen is freezing.

Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug

icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...

Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...

Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...

icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?

Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.

Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.

Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!

Fingerprint scanner randomly not working

I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?

Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.

jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.

bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk

bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo

SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.

jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.

The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.

tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.

I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.

For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?

jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.

bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)

morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.

After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop

On-Screen Navigation (Back Button BUG)

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.

Good lock 2018

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