Related
Hey everyone, I've been having a little bug that I noticed after I received the 4.0.4 update. I don't know what I exactly do to cause this but my nexus takes random screenshots whenever I press my power button to unlock my phone. I have the pattern lock that I use and when I hit power it randomly vibrates and when I go check my gallery it shows that I just took a screenshot. At times, when my battery is low it seems to randomly vibrate again and take a screen shot and gives me the prompt screen for which app I'd like to use to complete the action... No, I don't press the volume down key when this happens and no I don't have any screenshot apps. I'm stock, non rooted... Anyone else have this issue?
Stuck volume key?
adrynalyne said:
Stuck volume key?
Click to expand...
Click to collapse
I'm having doubts that it would be that...sometimes it does it even when I don't touch the power off key..
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Do any of you guys run a rom that gives the ability to use the volume rocker to take screenshots? Have you tried reflashing your roms since you updated?
Sent from my Galaxy Nexus using Tapatalk 2
xterrain15 said:
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Click to expand...
Click to collapse
Upload it somewhere and update your post with the link.
sent from my i9250
Posting the bug report
docs.google.com/open?id=0BxAJdhmCAyirSDU2UEU5dTRyQzg
There it is.
I am about to try flashing the 4.0.4 update again, as I just downloaded the zip of it.
Screenshots are Volume Down + Power. Bug Reports with screenshots are Both Volume Keys + Power. Do you have a case on? I've seen many people having these issues that were due to a tight fitting case.
Case
I do have a case on, but I know that's not the issue, as the power button is not covered, and this often occurs without me being anywhere near the power button. It can happen in the middle of typing out a text message. A prompt appears asking what application I'd like to complete this action with, and if I check the gallery later, there will be a new screenshot of my messaging app.
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
ceribaen said:
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
Click to expand...
Click to collapse
AOKP allows you to set up any functions/icons to softkeys
Sent from my Galaxy Nexus using xda premium
nirco68 said:
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I have the exact same problem! No clue what's causing this. I'm on AOKP M5 on rooted Galaxy Nexus. I can't find any setting to disable bug report creation, nor can I find anything about bug reports in the settings at all. I really hope someone can figure out what's causing these spontaneous bug reports (plus screenshots) to be generated.
Same issue
I just received my 4.0.4 update on Galaxy Nexus, and I am having the same issue. It randomly takes a snapshot of the lock screen and generates a bug report. Have they added some new hardkey combination that is too easy to trigger? I do have a case on, but I have always had it on, way before the update.
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
I edited them and linked it to your post on rootzwiki,
I was in a hurry then and rushed up and pasted on the threads where there was no proper answers.
I have the same problem
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Drakonworld said:
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Click to expand...
Click to collapse
See my full explanation here http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123 (last post on the page). Simple answer, something is pressing all three buttons at once, be it a case or whatever. Either disable usb debugging to turn it off or see my link for instructions to disable just the bugmailer.
Sent from my brain using human to phone transport technology.
Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,
urundai said:
Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,
Click to expand...
Click to collapse
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.
urundai said:
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.
Click to expand...
Click to collapse
If it is launching Different apps then it is the Quick launch that is the cause. You can see what Shortcut is associated with which app go here:Settings -> Applications -> Quick Launch
Most Launch with Search + any key. Perhaps your search button is stuck.
JB
Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?
If the random apps are opening, open the landscape keyboard and press the search button. If you accidentally press it and then you press a corresponding letter to open a certain app, it'll so that. And when you hit back, the phone thinks that you pressed the wrong letter key and has that quick open on. Just press search again. That's all lol
Sent from my SAMSUNG-SGH-I927R using xda premium
I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx
phatryan69 said:
Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?
Click to expand...
Click to collapse
I am on stock. It's just annoying when it happens at least once in 2 days.
I am thinking of rooting it and installing a custom rom to see if that takes care of it. Will keep you all posted.
I might turn on the debugging level in the logs as well to see if I can find out what's going on. Given that this happens only every two days or so, not sure if that will help much but let me see.
antonyfirst said:
I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx
Click to expand...
Click to collapse
I am on Rogers stock ROM. At this point, it certainly looks like something to do with the software (will be hard to find several of us having the same hardware problem).
dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
+1.
My keyboard stops working too, but this doesn't happen very often. I experience this about once in 3-4 weeks for now.
I have had this problem a few times as well (on stock AT&T).. QWERTY doesn't respond at all, reboot fixes it! Got me worried the first couple of times though
I continue to run in to this once in a while. I have tried pressing all kinds of keys (search, alt etc) with no success. At times, I see some of the keys working but not others.
Anyway, this looks like software / driver issue. Looks like reboot is the only cure so far.
This is not Officially supported by CyanogenMod but I have brought this to you for your flashing pleasure.
THIS IS AN ALPHA BUILD AND WILL HAVE SOME ISSUES AS WITH THE OTHER AOSP ROMS!
THIS IS UNOFFICIAL CM9 FOR THE I927
KERNEL BUILT FROM OFFICIAL ICS KERNEL SOURCE
ROM BUILT WITH MY GLIDE DEVICE TREE
THIS IS COMPILED FROM SOURCE FOR THE GLIDE ON MY LINUX MACHINE, THIS IS NOT A PORT!
CM SOURCE HERE-CM-Github
Kernel source here-Kernel github
TeamGlide Github Here-TeamGlide Github
known issues:
wifi may be janky
keyboard may or may not work properly
autorotation broke when using physical keyboard.
APN may not be present on first boot. Enter new APN if so..
Any other issues please report here.
INSTALLATION:
WIPE DATA
WIPE CACHE
WIPE DALVIK CACHE
FORMAT SYSTEM
FORMAT DATA
FORMAT CACHE
FLASH ROM
FLASH GAPPS
ENJOY!
Download- CM-9 UNOFFICIAL-Glide
CM-9-Glide-Alpha-2
ICS Google Gapps
CM9-Glide-Alpha-3
great! this makes the glide the best keyboard phone for europe
many thanks for your effort!
Mine!
Well done !
My wife took her Glide to work!!! NOOOOO!!! oh well. Guess we'll have to wait till tonight
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Anyone who flashes, do some tests with wifi please. My Glide is a wifi only device so I definitely need that working good before I can flash. This is great dman, thanks so much for showing our little device and community some love!
Very nice! If I didn't have to depend on my phone I'd have this sucker flashed in a heartbeat to put it through its rigors. Been looking forward to a CM port for a while.
Here's some money, go see a star war.
downloading now, will be back with a logcat if anything unexpected happens.
Tyfighter said:
Here's some money, go see a star war.
downloading now, will be back with a logcat if anything unexpected happens.
Click to expand...
Click to collapse
Thanks bro.. that's why I love the glide community.. you guys are so appreciative.. and I appreciate you guys..
Sent from my SGH-I897 using xda premium
Working on grabbing a logcat, don't have my adb pc on hand, so I have to use an app for now and that's proving problematic.
But for now:
-everything boots up fine, but on both my two installs it says that my sd card is damaged (which a restore to my previous rom says its not).
-The power button is only functional when you hold it down to power off; no locking, no power menu.
-I tried adding an APN, but it didn't save (only tried once, as said before the hardware keyboard isn't functional and pressing a key on the soft keyboard caused it to "perma-vibrate". worried about potential damage from the extended vibration, I didn't risk punching in the APN again.
And I know this isn't useful without a logcat but upon opening the camera I got a 'could not connect to camera' error
edit: just flipped through the other thread and saw the suggestion to try a different kernel. going to try that now and see if that resolves anything
Further edit: using the Lite Kernel, I was able to get wifi working. Logcats are incoming. Now, from what I've been able to tell, its not just the keyboard giving the perma-vibrate, but certain other events are doing it too; moving stuff in the drawer or homescreen and unlocking the phone. Further weirdness is that it only happens about 75% of the time when moving icons.
Its amazing that i knew dman would make this phone amazing still has bugs but ofcourse it will good job
Sent from my SGH-I927 using xda premium
I'm making a new build.. think I fixed the keyboard issue... and power menu
Sent from my SGH-I897 using xda premium
Here is what I have after playing around with the ROM for about an hour and doing several power on/off
- No problems with the flashing or first boot
- Vibration does not seem to stop. Like another posted noted this is not limited to the keyboard but appears to occur for the unlock screen, long press, etc. I ended up having to pull the battery each time this occurred and went into the system settings and disabled everything I could find that uses vibration.
- No cellular signal. I tried to add an APN but it did not get saved onto the list. WiFi and bluetooth don't seem to turn on.
- The capactive keys don't light up.
- The physical keyboard does not light up or work.
- I thought that the power button turned the screen on/off at first... But it doesn't seem to anymore now that I have disabled the lock screen (to remove the vibration which occurs when unlocking). Now I'm not certain if the power button worked in the first place or not. Currently with the lock screen disabled the power button doesn't seem to do anything. If the screen turns off the only way for me to turn it back on is to open the slider.
- Screen rotation did not work during the initial Google account setup. I opened the slider and it went into landscape mode. Then I closed the slider and the screen remained in landscape mode. This was all occurring while the phone was continually vibrating so I'm not sure if this is related. Right now the screen rotation works fine after having turned off all the features that use vibration.
- Attempting to use the camera get a message of "Can't connect to the camera".
- Surprisingly the Torch app works and turns on the LED. However, shortly afterwards the phone froze requiring me to pull the battery.
- There are no sounds played when I go into system settings and try to change the notifications or ringtones.
Sorry if the list is a bit long. I'm not sure what is important and what's not but I wanted to post my experience hoping to help.
Thanks for doing this for our community. I've sent you a small donation which I know is nowhere near the value of your efforts... But please enjoy a few beers on me.
Ok, so here's a logcat of the second boot after installing. Perma-vibrate starts when unlocking and lasts a few seconds. I then tried to restore my APNs to trigger an attempt to access the storage.
On the first boot from this install, I did some poking around in Antek and found that not only is the external SD not showing up, but neither are any non-root directories on the internal.
google docs link because XDA was being finicky about the file/character size
https://docs.google.com/open?id=0B7ZF6qbivGeNeE1nb3ZiZERTTjA
edit: forgot to mention before that the capacitive keys light up on a different kernel, and also (I didn't even think to test sound) but some error info on that looks like its available in the logcat. Also, it should be noted that the perma-vibrate can be stopped short of a battery pull by clicking on the app drawer icon. Possibly there's another way, but that's the one I found first so that's how I've been doing it.
The log at won't load up.. says its not available
Sent from my SGH-I897 using xda premium
Strange, try this. Don't know why I didn't think to zip it before.
Here is a new test build.. Please report if any issues are fixed
CM9-Glide Alpha-2
The keyboard is working a little better now. The soft keyboard doesn't pop up when the slide is out and most of the buttons work. Alt, backspace, question mark, sym, .com, microphone, search, home and the middle dpad button are nonfunctional.
Power button and power menu are working. In fact, I was just able to use it to successfully boot to recovery.
Tyfighter said:
The keyboard is working a little better now. The soft keyboard doesn't pop up when the slide is out and most of the buttons work. Alt, backspace, question mark, sym, .com, microphone, search, home and the middle dpad button are nonfunctional.
Power button and power menu are working. In fact, I was just able to use it to successfully boot to recovery.
Click to expand...
Click to collapse
Nice.. we have progress.. made some more changes to see if we can get some more issues fixed
Sent from my SGH-I897 using xda premium
Alpha-2 build in OP for testing
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 encountered this bug where I'm unable to use ambient display or wake up the display without the use of power button. Everytime I lock the screen it becomes unresponsive even the quick gestures don't work.
I have performed a soft reset but the problem has persisted.
Many other users seem to be suffering from this issue.
My device is full stock, no root or 3rd party apps on it.
Can anyone help me this this issue?
All users are facing this... It's because of battery optimisation.
No issues here. I am able to use the gestures just fine. Even the tap to wake and pick up to wake is working fine. I am 10.0.3 build.
I'm also having issues on tap to wake.
Happens to everyone. It's a hit or miss. Battery optimization makes the phone go into deep sleep and cause this issue is what i too understand.
Ya i did happen couple of times for me hope this bug get ironed out soon.
Sent from my HD1901 using Tapatalk
Same issue here also
Started encountering the issue recently - 3 days into ownership of the phone ?
The only peculiar thing I can remember is changing the override force dark toggle yesterday. And now that I recall, I don't remember seeing the ambient display since then. ?
Confirming I also have this issue. Very frustrating
I can trigger a black screen by holding the phone in landscape and launching the stock camera app. Then I have to hold Vol+/- and Power to reboot and it works again.
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
piyush.bhandari said:
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
Click to expand...
Click to collapse
This worked for me at the first attempt . Thanks for the solution.
charan_55 said:
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
Click to expand...
Click to collapse
Wow! A use for my work-issued iPhone! Yay, seems like its working.