Hi,
Just picked up a Moto G4. Came from a S4 with KK, so MM is fairly new to me (have brief experience with LP). I use Chompsms because it automatically turns data on/off to receive/send mms...however, I've found that feature doesn't work any more since LP (Google removed the API to allow 3rd party apps to control data toggles).
I had LP briefly on my S4 but didn't like the battery life so went back to KK. However, when I was on LP, my Wanam module had a feature that forced the data on/off for mms, so all was right with the world. Unfortunately, Wanam doesn't work on the G4. Is there another module that will do what I want?
Thanks
P.S. Thought of something else...I'm using Tracfone AT&T service. The lockscreen displays "Home". Any way for it to correctly display "AT&T"?
Related
I'm running SlimKat 4.4.4 build 7 on a rooted Galaxy Nexus, T-Mobile as carrier. NFC is turned on in settings.
When I open Google Wallet, there's simply no mention of Tap & Pay or NFC anything.
I tried uninstalling Wallet. I tried clearing data for NFC in apps. Battery removal. Disabling root in settings. And of course reboot. In no particular order. I can't think of a way to test NFC function besides Wallet, but I assume NFC is functional.
Previously, I used Wallet occasionally on this phone (a year ago?), I think with a Slimrom rather than Google's ROMs.
I know Google cut back Tap & Pay eligibility earlier this year for security reasons, but I didn't expect "KitKat only" to exclude custom ROMs. Google's silent on that on their website. Google's phone tech support people seemed to think it was the rooting that blows it up, but they sounded less than confident about that.
Should it work for me? Can anyone suggest a fix?
I'm using the latest LP nightly (3/27/15) and have had problems RECEIVING texts only since about the 3/19 build. Sending them works out fine, and I do eventually get the texts either later in the day or when I reboot the phone. I do use Textra, but seems irrelevant, as the stock google messaging app isn't receiving them in a timely fashion either. I'm on a Google Nexus 5 (hammerhead). I do notice upon boot and intermittently the warning at "unfortunately com.phone.android has stopped". Wondering if this is related. I WAS using ElementalX kernel for a bit, and thought that might be the problem. So this morning I flashed the nightly without flashing the custom kernel. Still the same problem. I also use Xposed framework, however left that off as well just for a test. Same results. Is this a known bug? Any other information that I could provide to help?
In case a list of the xposed modules I use would be helpful, here they are.
enable ambient display xposed
force pandora rich notification
pandora patcher
greenify
lolistat
statusbar download progress
Been a long time Pacrom user and don't wanna give up on this rom as it's always been dependable, feature packed and the best in terms of battery life. Thanks for any help in advance.
EDIT: Also, for further clarification, I do have multirom with CM12 as my secondary rom. The texts are coming in fine there. Hence why I'm convinced it's a problem with the rom and not my carrier or hardware.
I'm afraid that I never noticed if this was an issue caused when upgrading to MM or something with the Note 4 as I moved straight up from the Note 3, and installed MM straight away. I'm running stock firmware, and I'm rooted with xposed running.
I'm using the No Lock Home Xposed mod and when I'm connected to one of my chosen Wifi networks I no longer need to use the fingerprint scanner (the phone stays unlocked) but I ALWAYS have to swipe when the device is woken. And when I unlock with the fingerprint scanner.
I've tried altering all kinds of settings but to no avail. In the greater scheme of things it's not a big issue but it is rather tedious!
Any suggestions? And yes, I've tried it with the Xposed mod not activated
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.
I've been looking around these forums for quite a while now, hoping to find a near-stock ROM based on the latest NPN25.137-83 North American firmware that has integrated notification LED support. Unfortunately, I haven't been able to find anything.
This ROM is the closest thing I can find to what I'm looking for. Very nearly stock - just zipaligned, debloated, deodexed, a simple camera mod, and the LED enabled for notifications. The only downside is that it's not based on 137-83. Considering the March security patch, it seems to be based on 137-67 at the latest. And the developer of the linked ROM apparently has no plans to integrate the August security patch or the rest of the 137-83 firmware (a big problem for me considering the Verizon VoLTE bugs on 137-67).
There are other solutions too, like the Moto LED enabler app, but it's not that reliable. The blinking follows some sporadic and unappealing pattern, and it sometimes likes to stop blinking entirely after a while. The list of apps that enable the LED also seems to periodically reset itself.
So, my question is as follows: would someone release a ROM similar to the one I linked with the latest firmware and patches? Or perhaps can we just get a TWRP flashable zip to enable the LED for notifications? I'll gladly pull some weight on this if someone can point me in the right direction. Thank you!
Would really like to see this implemented as well, Paranoid Android rom I tested a while back also had this implemented very well, even works with screen on.
I'd like this as well.
I tried with Tasker but, due to deep sleep, it stops to work after few seconds of screen off (it works fine only enabling the option "Keep Device Awake" but battery drains quickly)