Hi!
I'm absolutely new here (and to Android and everything about it) and i've only made a couple of posts in the noob thread. I felt like this should be a thread of its own due to its abnormality.
I've only very recently rooted my phone (i9505, 4.4.2) a couple of hours ago using the towelroot method. I have not flashed any custom ROM yet however I do have some Xposed Modules installed.
i've only run across some problems like repetitive rebooting (fixed) and faster battery drain (hopefully fixed by tomorrow).
However, I have one problem that doesn't seem to have any solution whatsoever anywhere in the internet; it wasn't even mentioned once.
Whenever I open the stock camera app, the touch screen becomes completely useless. I cannot touch anything; the settings, shutter, view finder to focus, absolutely nothing. The camera itself is not broken, I can still take pictures with the volume rockers. Also, I know not the entire screen is broken because one of the modules I have installed is SwipeBack, which lets me swipe from a corner and it goes back and it still works perfectly fine.
I've tried rebooting the phone and force stopping the camera but nothing has worked.
The only suspicious thing I've done is backup and uninstall all the KNOX apps, which should be no surprise.
Now I'm not particularly bothered by this as I barely use the stock camera app anyway, or any camera app besides Snapchat. I don't use my phone for taking pictures much, but it still is quite annoying.
Is there any sort of fix to this?
Thank you very much in advance!
I have a Verizon Razr M with the latest OTA update. The bootloader is unlocked, TWRP recovery is installed, and the phone is rooted. I disabled the OTA reminder notifications and allowed wifi tethering. I have not installed any custom ROMs.
All of a sudden, the camera is not working. When I start the camera app, I get an error message that the camera is unable to initialize. I installed the google camera app, which also will not work. My flashlight app will also not work.
I cleared the cache and the dalvik cache and did several restarts.
Any idea what I screwed up and how to fix it?
Sounds like a hardware issue... Ensure the camera connector is firmly seated... I had one that did this after a small fall... The droid ultra does something similar and the resolution is to disable google now's "OK Google" detection... Try that first
We cannot teach people anything; we can only help them discover it within themselves.
dbreezy187 said:
Sounds like a hardware issue... Ensure the camera connector is firmly seated... I had one that did this after a small fall... The droid ultra does something similar and the resolution is to disable google now's "OK Google" detection... Try that first
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
I was afraid of that. It might be beyond my capabilities.
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.
Hy my accelerometer seems like dying. I used pixel live wallpapers (zion national park one) which used the accelerometer 24/7. It worked for a week and after it stopeed working (the rotation) and i tought maybe its because the app. Tried factory reset but did not work. Now I have to use a ****ty app to rotate my screen :/.
I search for some deep forum solution and maybe if you delete a cfg file in data/system and run an adb command it fixes, but you need root for that.
I hope the chip is not broken
Any help is apreciated
My galaxy note 5 is rooted, I have installed the Floyd One UI and trying to fix the Accelerometer bug on the T varient
Hi guys, much like other users I'm getting that stupid notification delay and when you grab the phone suddenly they all flood in. It seems related to doze, I'm not sure
https://forum.xda-developers.com/s7-edge/help/delayed-push-notifications-t3378852/page4
Apparently factory reset doesn't help. I'm wondering if a custom rom would help. What are the best ones out there and will certain apps (like banking or authentication ones) will still work on a rooted phone.
Thanks!