I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.
ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk
ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.
ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app
SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.
magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.
i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.
M9 just came out. Only in a matter of time we get the ota for the next update
jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app
Related
TF101 bug list.
Firmware : official 3.2
Model: TF101 16GB
1. Static(photo) shifted to left by 2/3. The right side became black. No problem for live wallpapers.
2. Short cut on home screen became black. Widget content is also black. Became normal after reboot.
3. If apk calls YouTube apk. The screen became half dark but not freezed. But TF101 YouTube apk still work fine.
4. Sometimes got messed lines on screen lower part. Disappear after running other apk.
I dont have any of these bugs with Prime 1.7.
Firmware : official 3.2
Model: TF101 16GB
Gallery: Forced close when view detail of a picture.
i-boy said:
Firmware : official 3.2
Model: TF101 16GB
Gallery: Forced close when view detail of a picture.
Click to expand...
Click to collapse
Yep, happens every time.
matika said:
TF101 bug list.
Firmware : official 3.2
Model: TF101 16GB
1. Static(photo) shifted to left by 2/3. The right side became black. No problem for live wallpapers.
2. Short cut on home screen became black. Widget content is also black. Became normal after reboot.
3. If apk calls YouTube apk. The screen became half dark but not freezed. But TF101 YouTube apk still work fine.
4. Sometimes got messed lines on screen lower part. Disappear after running other apk.
Click to expand...
Click to collapse
Number three isn't related to YouTube specifically, it happens any time you're supposed to receive the prompt to select an app to complete a given action, if you're docked or locked in landscape orientation, and haven't rotated the screen since the last reboot. The workaround is to enable screen rotation, then turn the device to portrait orientation until the screen rotates. (You can do this while the screen is half-dimmed). The prompt will immediately start working properly again, until the next reboot.
One problem not on your list is that the weather widget still randomly adds a half-line of blank space before the location, causing the temperature line to be cut off at the bottom. Also, the new "Last update" line places AM/PM after the date / before the time, rather than after the time where a native English-language speaker would place it.
Additional bug (possibly) - microphone
When chatting on Google Video Chat, and having headphones plugged in, the person on the other end can barely hear me. Take the headphones out and its much better.
Tried using the app called Voice Record which has sound level needle and tested the same situation with the same outcome. Mic is good without headphones plugged in, but once they are, the mic goes to like 2-5% input level.
Tried same on a friends TF with same outcome. Not sure if this is an OS issue or hardware/driver thing
billsull said:
When chatting on Google Video Chat, and having headphones plugged in, the person on the other end can barely hear me. Take the headphones out and its much better.
Tried using the app called Voice Record which has sound level needle and tested the same situation with the same outcome. Mic is good without headphones plugged in, but once they are, the mic goes to like 2-5% input level.
Tried same on a friends TF with same outcome. Not sure if this is an OS issue or hardware/driver thing
Click to expand...
Click to collapse
Interesting, had you tried on earlier releases (3.0, 3.1?)
knoxploration said:
Interesting, had you tried on earlier releases (3.0, 3.1?)
Click to expand...
Click to collapse
I have the exact same issue (prime 1.7), and I'm pretty sure it wasn't here before on prime 1.6.
I have one issue with 3.2:
When I am trying to open file which could be opened with couple of programs screen become darker, but no table with programs to choose.
The same with all ROM's (Prime, Rewolver, original). When downgrading to 3.1 all works well.
Do anybody experiencing the same issue? Mine is B50
rukinis said:
I have one issue with 3.2:
When I am trying to open file which could be opened with couple of programs screen become darker, but no table with programs to choose.
The same with all ROM's (Prime, Rewolver, original). When downgrading to 3.1 all works well.
Do anybody experiencing the same issue? Mine is B50
Click to expand...
Click to collapse
Rotate screen
rukinis said:
I have one issue with 3.2:
When I am trying to open file which could be opened with couple of programs screen become darker, but no table with programs to choose.
The same with all ROM's (Prime, Rewolver, original). When downgrading to 3.1 all works well.
Do anybody experiencing the same issue? Mine is B50
Click to expand...
Click to collapse
same here... all videos, mp3 etc
rukinis said:
I have one issue with 3.2:
When I am trying to open file which could be opened with couple of programs screen become darker, but no table with programs to choose.
The same with all ROM's (Prime, Rewolver, original). When downgrading to 3.1 all works well.
Do anybody experiencing the same issue? Mine is B50
Click to expand...
Click to collapse
Yes, I have this problem too, maybe I installed a file manager app and the app clash with the build-in file explorer.
When I click the file name of a avi file, the screen becomes darker without pop up a app selecting windows. It seems that the system hangs when a file tries to link with a corresponding app.
Will this happens with the use of the build-in file explorer only?
On my mail, if i hit on a link on a message..screen goes dark also, the post above said rotate screen, now it works when rotated...bug!!! Also, on stock browser doing a entering of info on screen, like a Google search, damn cursor gets removed of edit box. Another bug...I found...decaf coffee taste crappy...hopefully the upgrade the taste...
rotating screen really helps.
Thanks.
This bug doesn't efect any software installed. I have made fresh install with no any software Stock ROM with Nwflash. Bug comes after second reboot. no mater which ROM you are using.
With elder ROM's based on 3.1 no problem.
Anyway rotating screen helps.
Sent from my Transformer TF101 using Tapatalk
Touch screen most of the time, unresponsive (takes alot of tapping for a respond), usually happens at the lower part of the screen,
Is it just me?
Was the 3.2 wifi issue solved with latest update patch, wifi drops out unless you designate static ip?
No problems with touch screen and WiFi for me.
I brought my transformer to Asus service center in my country, to complain about the white spots in the middle of the screen, they have agreed to replace my screen, is that right?
I thought they would replace the whole unit, hopefully the new screen will fix the responds issue
checkbox111 said:
Was the 3.2 wifi issue solved with latest update patch, wifi drops out unless you designate static ip?
Click to expand...
Click to collapse
I have never seen that issue. My wifi is solid.
Sent from my Transformer TF101
life64x said:
On my mail, if i hit on a link on a message..screen goes dark also, the post above said rotate screen, now it works when rotated...bug!!! Also, on stock browser doing a entering of info on screen, like a Google search, damn cursor gets removed of edit box. Another bug...I found...decaf coffee taste crappy...hopefully the upgrade the taste...
Click to expand...
Click to collapse
Hey thanks for this tip. The dark screen-pick app thing sucks and was making me insane. I definitely have this same bug on stock 3.2 with root. Other than that, I haven't had any major bugs except maybe standby battery life not being as good as before 3.2.
Hello,
I am not allowed to post in the developers thread and advised to ask here.
I have used Xylon-Rom before, did today a clear installation (factory reset, cleared all caches + data) and have some issues with the actual b2-build:
-white statusbar -> when trying to change it, xylon settings crash.
-Xylon PIE -> can't get it to work. When enableing it, nothing happend.
-Customizsation of Notification light -> where are the settings for it?
Thanks if someome can give me some advises.
Regards
Robsterboy
Hey there man, the white status bar is a known issue in the latest stable and sadly there is no simple fix for it, I'd advise just waiting for the new release which is bound to be any day now.
Once you've enabled pie did you switch to expanded desktop mode? It can be difficult to get pie to appear with the navbar still there.
Edit: the led settings are at settings->XY tools->and then LED at the bottom
Sent from my Nexus 4 using xda app-developers app
I read so many complaints and issues with this ROM.
I just got my Nexus 4 last week. I rooted it right away, and installed Xylon 02-23 build, with Matrix kernel v7.0
I have zero issues at all. No problems, not one reboot in a week, no FC. No status bar problems. Maybe I got lucky, but everything just works as expected.
Battery life, with this kernel has been great. On average heavy use workdays 12 - 15 hours total usage, with constantly getting 5h On Screen time each day. On weekends with WiFi getting a full day easily.
Sent from my Nexus 4 using xda premium
Some of the issues are hard to spot cause you don't realize they're issues, ROMS like Slimbean and Paranoid Android are rock solid, some of the issues I encountered last I used Xylon were a memory leak (RAM would get used up and wasn't coming back at a certain point, either that or the recents RAM wasn't reporting properly), Mixcloud wasn't streaming music with the browser, PIE implementation is buggy and is invisible at times (same as Carbon and Rootbox) etc worst is the dev is a ghost in his thread
Thanks Sliming,
LED now works fine
Okay. Now have to wait until new Beta will be released.
Regards
Robsterboy
Hi guys i got some freezing issues, anyone got an idea what could it be? i'm totally new to Android/tablets, so other then this info, i don't know what else to say, or explain the issue better, it just freezing for like 5 sec, and after it works normal, its random freezing. I hope anyone can help me, thanks.
Is it when you update or install apps?
This is normal, the OS can freeze for a few seconds during write operations.
nex86 said:
Is it when you update or install apps?
This is normal, the OS can freeze for a few seconds during write operations.
Click to expand...
Click to collapse
What do you mean by normal it doesent happpen during instal, its random during surfing for example not conncted to installation imho.
dazed1 said:
Hi guys i got some freezing issues, anyone got an idea what could it be? i'm totally new to Android/tablets, so other then this info, i don't know what else to say, or explain the issue better, it just freezing for like 5 sec, and after it works normal, its random freezing. I hope anyone can help me, thanks.
Click to expand...
Click to collapse
What ROM and kernel are you using? Are you over clocked?
hagensieker said:
What ROM and kernel are you using? Are you over clocked?
Click to expand...
Click to collapse
No overclock at all, Kernel - 3.4.0-g9e52a21
Build number JSS15R all stock here. No custom ROM's..
I experience the same BS on an all stock WIFI model (2013.06 date code). Thought it was JB 4.3 teething pain but my Note 3 running 4.3 doesn't do it. Have mainly noticed it playing Great Big War Game where it'll randomly freeze the whole tablet once per launch for about 10 secs where nothing responds (show touch, home, switch task, etc.) then it'll either return to normal or prompt with dialog to wait or close. Have also had it happen in Modern Combat 3 along with the random app close that, again, doesn't affect Note 3. Haven't seen newer apps affected so perhaps it's a software issue and is fixable but it's irritating nevertheless considering it's a Nexus device and after correcting the touch issues with ts10 firmware update. Going to try reflashing the stock image to see if it fixes it otherwise looking forward to dumping this Asus for a Note 10.1 2014 LTE. My Note 10.1 2013 and Note 2 have been 100% solid with never a crash, hang or touch issues.
I had freezing problems when i was trying out the TS20 fix. TS10 seems to yield erratic behaviour randomly after each reboot.
Ever snce i've been testing the ones between TS10 and TS20. TS16 works better for me than TS18 - just being more responsive but both has no reboot issues. Am testing TS14 now and it seems better than TS16 but i needed more time to run it. None of the 14,16 and 18 has given me any kind of freeze after 24hrs of testing on multi-touch intensive apps.
You might wanna give 16 a try... i will be posting a more detailed update in sfhub's thread when i'm done with TS14 and TS12 testing.
Cheers
Thanks for the answers guys, but this is really new to me, i got no idea what is TS 14, TS 18 or TS16, can you guys explain me a bit? thanks.
I had the same issue. Please see my observations at post: http://forum.xda-developers.com/showthread.php?p=46082214#post46082214
However, I have recently tried to uninstall all apps (backing up with titanium backup) and installing back in bunches. With only the apps/games I use daily, the issue appears to have subsided, and I am trying to slowly bring apps back to see what the issue is.
Original post for consolidation purposes:
When it happens: Touch intensive Games (drastic, MMOJ, Dumb Ways) appears to be when the 3D GPU is NOT in use, netflix, when paused for a short while.
What happens:
1. Screen does not update display appears frozen
2. No response from nav bar icons
3. Power, volume buttons give no response.
4. If audio was playing right before it froze, it will keep playing as if nothing wrong.
5. If I hit the power button or the nav button then let it sit for a few minutes, suddenly it will react to every press I did in quick motion and go back to normal.
5a. I had show touches enabled, which showed a random number of the frozen touches working in quick succession when it "unfroze"
6. Sometimes requires a hard restart with no response.
When it started: Right before the Q update starting rolling out, did not have issues out of the box.
Purchase date and location: Right around the time of launch from best buy, 32 GB 2013 version
Troubleshooting steps: Safe mode (doesn't appear as often), full factory restore to the Q image when the R image started rolling out. Issues were gone for a short timeframe, then returned
Config information: Stock, latest firmware version, rooted via TWRP (latest version installed), and SU.
Observation: Appears to occur in select situations, and I believe I always have a GMAIL notification right when it un-freezes.
Let me know what you think and if it should be merged with a different topic, didn't see anything about it un-freezing when it was frozen or audio still playing.
Click to expand...
Click to collapse
Please refer to this thread for a fix:
http://forum.xda-developers.com/showthread.php?t=2428133
The fix from the thread above helps with many touchscreen issues including freezes.
At least it helped with mine. I was experiencing freezes and so called "sticky touches" (like when you short tap on something and the device interprets it as a tap and hold).
My device came with pre-Q and went through three OTA updates. After reflashing with factory R image minus wiping data (remove -w from flash-all.bat file) and with ts10 all appear to be better so far. Modern Combat 3 still randomly closes but it could be Gameloft's crappy coding. Need to run it for a few more days to confirm but reflashing factory R image with ts10 offer the best experience so far.
Mine does too now in addition to the already random reboot. The freezing happens when I try to input text on the keyboard.
Sent from my Nexus 7 using xda app-developers app
Has anyone faced similar issue? Here's bit of background. I was using Liquidsmooth custom ROM with navigation bar disabled and pie controls enabled for navigation. I used to to enable pie control to swipe from bottom border.
So, the day I got system update available notification (for 4.4.3), my pie control stopped working from bottom border. Just a coincidence I think. It was still working from other trigger positions though. I also had this incredible urge to see new update of Kitkat. So, I just got Google factory image of 4.4.3 & flashed it. Everything done, I got to home screen only to find out my navigation buttons are not working. That area is completely dead. Those buttons will randomly start working for some time. Only for a minute or so.
So I went back to the latest version of Liquid Smooth ROM. Pie control from bottom border & navigation bar is not working. Tried going back to stock 4.4.2 & take a 4.4.3 OTA. Still no go.
And to me, it seems a software issue since navigation buttons work in landscape mode. And the area where navigation buttons are in portrait mode also works fine for everything else. So, it's not as of that part of touch screen is dead.
So, to cut long story short, please help me out here guys!!! :crying::crying::crying:
Regards,
Mrugesh.
Did you find a solution to this? I know of a Nexus that also started having this problem and no clue how to fix.
Sent from my SM-T320 using Tapatalk
No clue dude... No resolution... I'm just using my Nexus with pie controls whichever way I can.... Thank God it's a Nexus. Else I'd have been screwed by now buddy.... But surprising to see no resolutions from XDA.
Sent from my Nexus 4 using XDA Free mobile app
Spoke to google support and they told me to return it for another device.
Sent from my SM-T320 using Tapatalk
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.