Related
Anyone figure out how to have a lock screen and use touchless controls... you know... touchless? Giant gaping hole by Moto.
Whoa - documentation here https://motorola-global-portal.cust...a_id/94881/p/30,6720,8696/action/auth#privacy
This implies we have the ability to do this but I'm not seeing the setting anywhere???
How do I use Touchless Control with the lock screen?
Touchless Control now includes two new features to make using Touchless Control with the lock screen easier. The first is voice pin entry. If you use a numeric pin code you will be prompted by Touchless Control when you encounter the lock screen to speak your pin. Simply say your pin code to unlock the phone to complete your request. The second feature is to allow the Google application to run in front of the lock screen without needing to unlock the phone. This feature requires you to agree to the terms and conditions before you use it. Enabling the feature can be done by agreeing to the notification or turning the feature on manually within Settings -> Touchless Control
Using Open Mic+ seems to be a viable alternative. Does it use the low power core from Moto though?
km8j said:
Anyone figure out how to have a lock screen and use touchless controls... you know... touchless? Giant gaping hole by Moto.
Click to expand...
Click to collapse
It's a necessity that it will not work as you want it if you secure your phone (there's really no way to have your phone be secure and has full access to the touchless controls). Your best bet is to buy something like a Cobra Tag alarm and use it as a trusted bluetooth. Turn it on/carry it with you whenever you don't want to have to unlock your phone. I use my car's bluetooth to keep my phone unlocked while driving. It works great because you can wake the phone up and tell google now to navigate somewhere or ask about the traffic all without touching your phone. I think the trusted bluetooth is another great feature that Motorola included that separates it from other phones out there currently.
I've also been beta testing the new SkipLock app for it's developer. It allows you to disable the lock screen when you're connected to trusted wifi points like at home and work. I've been using it a couple days and it has been working well.
http://forum.xda-developers.com/showthread.php?t=2523069
dustPile said:
I've also been beta testing the new SkipLock app for it's developer. It allows you to disable the lock screen when you're connected to trusted wifi points like at home and work. I've been using it a couple days and it has been working well.
http://forum.xda-developers.com/showthread.php?t=2523069
Click to expand...
Click to collapse
Egh this doesnt really solve issue because you could be at the office all day long. You dont want your phone unlocked there.
km8j said:
Egh this doesnt really solve issue because you could be at the office all day long. You dont want your phone unlocked there.
Click to expand...
Click to collapse
NFC tag on your desk?
shempmalone said:
NFC tag on your desk?
Click to expand...
Click to collapse
still too many use cases where this doesn't apply...
moto missed the ball here. this should be user changeable option. there is no security concern here. you dont have to give someone access to the messaging app, just send the damn message.
I use tasker + secure settings to keep my phone unlocked when within range of both my work or home wifi. I feel secure enough at work that I'm not too worried about having it unlocked. Anything extremely sensitive is locked up anyway. I also use my truck's BT as a trusted device which keeps it unlocked there as well.
So basically my phone is unlocked unless i"m not in my normal places.
Dmtalon said:
I use tasker + secure settings to keep my phone unlocked when within range of both my work or home wifi. I feel secure enough at work that I'm not too worried about having it unlocked. Anything extremely sensitive is locked up anyway. I also use my truck's BT as a trusted device which keeps it unlocked there as well.
So basically my phone is unlocked unless i"m not in my normal places.
Click to expand...
Click to collapse
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
mechanical tool said:
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
Click to expand...
Click to collapse
I've been using this setup for a while. I'm sure I didn't just figure it out but saw it somewhere but I don't have any idea where. The only gotchya is that with 4.4 you need to use the beta version of secure settings.
I use pattern lock, so I just create a task when connected to wifi to disable pattern lock. Secure Settings does need to have the 'helper app' installed too.
mechanical tool said:
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
Click to expand...
Click to collapse
Here's the two Tasker projects I've been using to unlock my device while connected to a "safe" Wifi network. One of the projects maintains a set of variables that can be used as states or referenced within tasks. The other project handles the locking and unlocking, and depends on the first project. It's was working fine on my Galaxy Nexus for a long time, and appears to work fine on the Moto X as well.
There's a lot in the "states" project that's not needed for locking/unlocking, but it comes in handy for other things. You can probably just change the "Wifi Connected" state to a "Wifi Near" in the myTRUSTEDWIFI profile, and get rid of the Wait action and uncheck the "if" box in the remaining action in the exit task.
Yes!!!! New version of touchless control fixes this!!!
Sent from my XT1053 using Tapatalk
the Network to 2G when you get home. I am having trouble getting phone calls at home with WIFI on and LTE enabled. There is some kind of issue with some phones that seems to send phone calls directly to voicemail when you have bot WIFI and LTE enabled at the same time. I have never used Tasker, would that be possible to set up this way? Do you guys know of any app that will do that automatically. Thanks in advance for help or feedback.
Tasker?
Sent from my SAMSUNG-SGH-I527 using Tapatalk 2
x2h said:
Tasker?
Sent from my SAMSUNG-SGH-I527 using Tapatalk 2
Click to expand...
Click to collapse
It looks like learning tasker would be my best bet to do what I need. I have been reading up and watching some videos on tasker and it is an amazing tool. A lot to learn but for the simple tasks that I want it sholuld not be to hard to setup. Thanks for the reply
Tasker won't switch your lte on and off with the stock Rom, but it will control WiFi and Bluetooth, and you will be able to set up a location based profile to do it automatically.
Solutions Etcetera said:
Tasker won't switch your lte on and off with the stock Rom, but it will control WiFi and Bluetooth, and you will be able to set up a location based profile to do it automatically.
Click to expand...
Click to collapse
Okay, I have been looking over Tasker, it does so much it quickly intimitades new users like me lol. Thanks that answers my question and I appreciate your post.
I had the same problem with Tasker. Even with some of the tutorials, they steps they used must have been for an older version as they didn't even match what I was seeing on the screen.
If you want to try a much simpler interface try out Locale. Its the same concept, but the interface is a LOT easier to understand for newcomers. I have mine set using location to turn on WiFi/off BT/set ringers to 10% volume/check into FourSquare when I get to work, turn on BT/off WiFi/Open Google Listen & GasBuddy when I get in the car and such. Most of the plug-ins you can use with Tasker can also be used with Locale too.
However, I suspect what you are wanting to do would require a plug-in as it is a sort of advanced procedure but maybe if you find some app that will allow turning off 4G, you could at least have it open the app or toggle to turn it on and off as you leave home - if you can't have it happen automatically.
fish1552 said:
maybe if you find some app that will allow turning off 4G, you could at least have it open the app or toggle to turn it on and off as you leave home - if you can't have it happen automatically.
Click to expand...
Click to collapse
My understanding is that Google, since Jelly Bean, has pulled the API's for turning off radios and GPS (just as they have with battery stats in 4.4) in the interest of more secure devices. So without root, and in some cases something other than the stock rom, programmatical access to these settings is no longer possible.
fish1552 said:
I had the same problem with Tasker. Even with some of the tutorials, they steps they used must have been for an older version as they didn't even match what I was seeing on the screen.
If you want to try a much simpler interface try out Locale. Its the same concept, but the interface is a LOT easier to understand for newcomers. I have mine set using location to turn on WiFi/off BT/set ringers to 10% volume/check into FourSquare when I get to work, turn on BT/off WiFi/Open Google Listen & GasBuddy when I get in the car and such. Most of the plug-ins you can use with Tasker can also be used with Locale too.
However, I suspect what you are wanting to do would require a plug-in as it is a sort of advanced procedure but maybe if you find some app that will allow turning off 4G, you could at least have it open the app or toggle to turn it on and off as you leave home - if you can't have it happen automatically.
Click to expand...
Click to collapse
Thanks I will check out Loacle and see if I can figure out anything.
Solutions Etcetera said:
My understanding is that Google, since Jelly Bean, has pulled the API's for turning off radios and GPS (just as they have with battery stats in 4.4) in the interest of more secure devices. So without root, and in some cases something other than the stock rom, programmatical access to these settings is no longer possible.
Click to expand...
Click to collapse
Okay, that may be part of my trouble no root yet. This is the first phone I have not rooted since coming to android. I probably should have gotten the Dev Moto but I was stubborn and wanted to pick my design:silly:
Tasker should be able to do some of what you need, but as others have mentioned you will at the very least need root to get it working.
Solutions Etcetera said:
My understanding is that Google, since Jelly Bean, has pulled the API's for turning off radios and GPS (just as they have with battery stats in 4.4) in the interest of more secure devices. So without root, and in some cases something other than the stock rom, programmatical access to these settings is no longer possible.
Click to expand...
Click to collapse
On the stock Moto X (XT-1053) you can turn GPS on/off via Tasker without root or using Secure Settings. It was a delight to see this, and not get the GPS nag screens I've previously gotten on a SGS3 (Verizon). Would have to play around, but you might be able to execute an activity or shortcut in Tasker that brings up the settings screen where you can choose 2G data and then script a screen tap in just the right place. Essentially automating the actions you'd take doing it manually. Not as pretty as a direct setting, but Tasker can execute this kind of thing very fast so it's of little bother to see it flash by on your screen.
Not on mine!
http://solutionsetcetera.com/stuff/Screenshot_2013-12-25-04-34-39.png
Solutions Etcetera said:
Not on mine!
http://solutionsetcetera.com/stuff/Screenshot_2013-12-25-04-34-39.png
Click to expand...
Click to collapse
Hmm, that does it for me. I think I will give in to the desire to get root and maybe than I can use Tasker for what I need. Thanks for the input:good:
NFC tags?
Solutions Etcetera said:
Not on mine!
http://solutionsetcetera.com/stuff/Screenshot_2013-12-25-04-34-39.png
Click to expand...
Click to collapse
Which vendor version of the Moto X are you using? Would be in character for a vendor like Verizon to neuter a useful feature.
larry62 said:
Which vendor version of the Moto X are you using?
Click to expand...
Click to collapse
T-Mobile. But I see the same behavior on my Nexus devices. As the dialog I posted states, this is an Android imposed limitation.
Solutions Etcetera said:
T-Mobile. But I see the same behavior on my Nexus devices. As the dialog I posted states, this is an Android imposed limitation.
Click to expand...
Click to collapse
OK - Just made a task which turns on GPS waits several seconds and turns it off. Verified it was actually on/off when it said it was on. I'm running 4.2.2. My son "upgraded" to 4.4 on his Moto X, and Tasker GPS manipulation doesn't work on his. I didn't root, and verified as much with root checker, so it seems this is an "upgraded" feature in 4.4.
I'd consider rooting, but do like some of the Moto rom features so don't really want to move to an alternate rom & not wild about losing warranty. Maybe a little off topic, but if you root 4.2.2 and latter upgrade to some 4.4.x release, will you end up losing root?
larry62 said:
OK - Just made a task which turns on GPS waits several seconds and turns it off. Verified it was actually on/off when it said it was on. I'm running 4.2.2. My son "upgraded" to 4.4 on his Moto X, and Tasker GPS manipulation doesn't work on his. I didn't root, and verified as much with root checker, so it seems this is an "upgraded" feature in 4.4.
Click to expand...
Click to collapse
Interesting... My recollection is this was disabled under JB on my Nexus 4. I didn't have 4.2.2 on my Moto X long enough to test.
Can you toggle airplane mode using tasker?
Off topic for here but a quick question. Would this be a good root quide to use. It seems pretty straightforward to understand and do. http://theunlockr.com/2013/12/11/root-motorola-moto-x-running-android-4-4-kitkat/ That site has been around and I think it is reputable but wanted to check.
Dunno, but I am not sure you're gonna be able to toggle LTE even if rooted. At least the description of Secure Settings suggests you can't without a custom rom.
If you turn off mobile data, does that solve your incoming call issue?
http://liliputing.com/2014/07/google-brings-chromecast-screen-mirroring-android.html
I would love to be able to wirelessly mirror my Rooted but locked Moto X on 4.4.3 to the chromecast. It seems like it's working on devices about as fast as the moto x so I would imagine they just have it disabled for devices not officially supported. Would there be a way through Xposed or some other method to enable this feature? THANKS!
Is it possible it's in the 4.4.4. Code?
Spacemonkie4207 said:
Is it possible it's in the 4.4.4. Code?
Click to expand...
Click to collapse
I think it's supposed to already work with devices that are still on 4.4.2. It seems more to do with the new version of the chromecast app itself (version 1.7). I just don't know how to trick it into thinking the moto x is a supported device. Maybe just a build prop tweak would be enough?
atomb said:
I think it's supposed to already work with devices that are still on 4.4.2. It seems more to do with the new version of the chromecast app itself (version 1.7). I just don't know how to trick it into thinking the moto x is a supported device. Maybe just a build prop tweak would be enough?
Click to expand...
Click to collapse
I'm sure they will add support. Probably just started on Devices that are in high demand.
atomb said:
http://liliputing.com/2014/07/google-brings-chromecast-screen-mirroring-android.html
I would love to be able to wirelessly mirror my Rooted but locked Moto X on 4.4.3 to the chromecast. It seems like it's working on devices about as fast as the moto x so I would imagine they just have it disabled for devices not officially supported. Would there be a way through Xposed or some other method to enable this feature? THANKS!
Click to expand...
Click to collapse
Guys, see here: http://forum.xda-developers.com/moto-x/general/chromecast-mirroring-moto-x-t2810937
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Enviado desde mi XT1053 mediante Tapatalk
As this topic is on Screen Mirroring, can anyone successfully connect a rooted X to a smart TV? I have been trying to connect it with my W6 series Bravia for past half an hour and could not be able to. It just says connecting but never connects! I am not talking about the Chromecast feature here, but the built in Miracast of X which can be found under Display.
S4 had the same problem when I rooted it, wouldn't connect, but with stock kernel S4 did connect fine. Anyone?
devilsdouble said:
As this topic is on Screen Mirroring, can anyone successfully connect a rooted X to a smart TV? I have been trying to connect it with my W6 series Bravia for past half an hour and could not be able to. It just says connecting but never connects! I am not talking about the Chromecast feature here, but the built in Miracast of X which can be found under Display.
S4 had the same problem when I rooted it, wouldn't connect, but with stock kernel S4 did connect fine. Anyone?
Click to expand...
Click to collapse
My rooted X works perfectly with my Netgear Push2TV (this is branded to use "WiDi", which according to wikipedia is 100% compatible with "Miracast"). It comes in very handy for presentations.
I always have multiple people asking me "How did you do that with your phone?!?!" after the presentations
samwathegreat said:
My rooted X works perfectly with my Netgear Push2TV (this is branded to use "WiDi", which according to wikipedia is 100% compatible with "Miracast"). It comes in very handy for presentations.
I always have multiple people asking me "How did you do that with your phone?!?!" after the presentations
Click to expand...
Click to collapse
Great. My router is Netgear too! So why isn't it working with mine? Do you have Xposed installed? Also what kernel do you use?
I guess I have made Screen Mirroring my enemy in past life.
devilsdouble said:
Great. My router is Netgear too! So why isn't it working with mine? Do you have Xposed installed? Also what kernel do you use?
I guess I have made Screen Mirroring my enemy in past life.
Click to expand...
Click to collapse
My router is not netgear...I don't have a smart TV, so I'm using a "Netgear Push2TV" device which just plugs into the HDMI port of any TV and is made specifically for WiDi / Miracast (you can google it if interested - it's actually been out for several years now).
Yes, I'm using Xposed. I'm rooted with several root apps, but using the Stock ROM / kernel.
When I first connect my phone to the "Push2TV", the Push2TV displays a 4 (or 6?) digit code on the screen and asks me to enter it on my device. The phone pops up a number pad and I enter the code. A few seconds later, screen mirroring is ON.
I also want to add that though I've seen some reports of the "Chromecast" method resulting in choppy video and/or no sound, the built-in mirroring has worked flawlessly for me. Sometimes I use the "Xfinity TV-Go" app to stream television episodes to the TV. You can't tell that it's not being played directly from the TV. Picture and sound have both been excellent.
samwathegreat said:
My router is not netgear...I don't have a smart TV, so I'm using a "Netgear Push2TV" device which just plugs into the HDMI port of any TV and is made specifically for WiDi / Miracast (you can google it if interested - it's actually been out for several years now).
Yes, I'm using Xposed. I'm rooted with several root apps, but using the Stock ROM / kernel.
When I first connect my phone to the "Push2TV", the Push2TV displays a 4 (or 6?) digit code on the screen and asks me to enter it on my device. The phone pops up a number pad and I enter the code. A few seconds later, screen mirroring is ON.
I also want to add that though I've seen some reports of the "Chromecast" method resulting in choppy video and/or no sound, the built-in mirroring has worked flawlessly for me. Sometimes I use the "Xfinity TV-Go" app to stream television episodes to the TV. You can't tell that it's not being played directly from the TV. Picture and sound have both been excellent.
Click to expand...
Click to collapse
Oh I get it, it's a device like Chromecast or sort. I guess it's the kernel, I am on Faux's. Let me see if it works with stock kernel. Do you happen to have a zip of stock kernel?
I get that four digit code thingy, I did that when I had the S4 and it used to connect successfully.
See also...
See also:
http://forum.xda-developers.com/moto-x/development/cast-moto-x-screen-to-chromecast-t2812322
devilsdouble said:
Oh I get it, it's a device like Chromecast or sort. I guess it's the kernel, I am on Faux's. Let me see if it works with stock kernel. Do you happen to have a zip of stock kernel?
I get that four digit code thingy, I did that when I had the S4 and it used to connect successfully.
Click to expand...
Click to collapse
Hmm, I've never used a custom Kernel, but boot.img contains the Kernel. I bet that is your issue. You should be able to download the SBF for your carrier, extract "Boot.img", and fastboot flash it.
I suggest making a backup first, just in case something goes awry.
Let us know if that does the trick.
samwathegreat said:
Hmm, I've never used a custom Kernel, but boot.img contains the Kernel. I bet that is your issue. You should be able to download the SBF for your carrier, extract "Boot.img", and fastboot flash it.
I suggest making a backup first, just in case something goes awry.
Let us know if that does the trick.
Click to expand...
Click to collapse
Lol, thanks mate. I did extract the boot.img some days back from the ROM and I flashed it via Fastboot, everything went fine and I even got the stock kernel back, but WiFi would not turn on, and without WiFi I can't do this test. I guess something is missing from the boot.img file, something else needs to be flashed as well, just don't know what.
I am giving up. I will format the phone when 4.4.4 will be released and that time I will check if Screen Mirroring works or not, it should, just for the peace of mind, then I will have to flash custom kernel and then it will stop working again.
I've got a Verizon DE, 4.4.2 rooted, running Faux 007m. I can use wireless display (screen mirroring) through my Netgear PTV2000 or my miracast enabled Samsung TV without issue.
Sent from my XT1060 using XDA Free mobile app
When turning on tethering though the system (not a separate app), I'm seeing a message along the lines of 'Verifying subscription with T-Mobile servers'. I never saw any message like this on my 2013 Moto X. Tethering still activates, but I'm worried about this causing any issues later.
Is anybody else seeing this? Any issues?
I'm on the $30/mo plan with a Moto Maker pure edition.
I see the same thing. It's normal.
My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.
nishmaster2k said:
My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.
Click to expand...
Click to collapse
I had that warning once. A restart fixed it. It was odd because I decided to call in to tech support first, then while on the phone I restarted my X and it started working again, hah.
nishmaster2k said:
My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.
Click to expand...
Click to collapse
That's disturbing. I was thinking of getting this phone, but I don't want to give up tethering. I'm assuming a custom ROM (Cyanogen, etc.) would solve the problem?
Have you tried to see if this also makes USB tethering stop working?
Might be plan dependent
Does your plan include tethering?
Sent from my Nexus 7 using XDA Free mobile app
I thought all T-mobile plans supported tethering up to the LTE data limit per month?
Note10.1Dude said:
I thought all T-mobile plans supported tethering up to the LTE data limit per month?
Click to expand...
Click to collapse
I think all the new simple choice ones do.
I'm still using my Pure on Tmo, and tethering still works.
I thought if you had a stock rom or something like Cyanogen, they couldn't really block (or detect) tethering, regardless of plan, carrier, etc. Is that incorrect?
Yeah, the plan includes tethering. I've check my usage and I now see it split between "data" and "mobile hotspot usage" (see attached screenshot). On my 2013 moto x I've never seen the hotspot usage and any data used while tethering just fell under the "data" label - same as any other data on my line. I read something (forget where) about there being a change in 4.4.4 (for 2013 moto x) which tags data used by the hotspot as such. I assume this is how t-mobile can tell the difference.
techie91 said:
Yeah, the plan includes tethering. I've check my usage and I now see it split between "data" and "mobile hotspot usage" (see attached screenshot). On my 2013 moto x I've never seen the hotspot usage and any data used while tethering just fell under the "data" label - same as any other data on my line. I read something (forget where) about there being a change in 4.4.4 (for 2013 moto x) which tags data used by the hotspot as such. I assume this is how t-mobile can tell the difference.
Click to expand...
Click to collapse
I hate stuff like that. Carriers and manufacturers shouldn't be able to control and monitor how people use their devices so much. This does make me hesitate about the Moto X. I'm used to Nexus devices where I have a lot more control over things like this, even if it requires a custom ROM.
I agree. It really has me rethinking my decision to hold on to the x. Might move to the nexus when it releases.
Yeah, I'm feeling torn. The 2nd Gen. Moto X is about as close as anything has gotten to what I'm looking for in terms of hardware (if it only had OIS). And of course it is a near stock experience that can be modified with xposed to have features found in custom ROMs. But for the under the hood, keeping the user in control, and privacy stuff, I just trust Cyanogen and other ROMs more. And yet if the 1st Gen. Moto X is any indication, custom ROMs will break some of the unique features on the Moto X, like active notifications and always listening voice controls. On the other hand, if the next Nexus really has a 6" display, I just don't know if I want an enormous phablet. So it's a hard choice.
I had this trouble as well on the prepaid unlimited data plan. I should be entitled to 2 1/2 GB of tethering. I tried three or four times and restarted the phone and it eventually went through with no extra tinkering on my part. Good luck!
After a week of not having tethering, I tried a few things and got it working! I don't have tethering on my T-Mobile plan, and every time I tried to enable wireless tether in the settings menu, I got the T-Mobile verification failed. But that's all good, now.
So here's what I did:
1) Unlock Bootloader, Custom Recovery, Root (Basically, just get root access on your phone)
2) Download the Xposed Module "Xtether" and activate it. This gets rid of the verification message, but tethering still didn't work, it just got the wifi tether to turn on.
3) Download SQlite Editor from the app store
4) Go to Settings Storage (the one that has "com.android.providers.settings" at the bottom > settings.db > global
5) Add "tether_dun_required" with a value of "0"
6) Go to your APN settings. Create a new APN entry, and set it up the same as your fast.t-mobile.com one, except use IPV4 (IPV6 will not work)
7) Reboot, and you're good!
Wrote this hastily, so if you need clearer instructions, just ask!
Thanks for the explanation Moose8106.
So am I correct in understanding that the tethering function built into AOSP Android (and normally available on Nexus devices) is deliberately modified in the stock Moto X ROM to allow carriers to scrutinize (and possibly limit) how you are using your mobile bandwidth?
2104
cb474 said:
Thanks for the explanation Moose8106.
So am I correct in understanding that the tethering function built into AOSP Android (and normally available on Nexus devices) is deliberately modified in the stock Moto X ROM to allow carriers to scrutinize (and possibly limit) how you are using your mobile bandwidth?
Click to expand...
Click to collapse
I don't think it's deliberately modified for the Moto X ROM. I believe it's a restriction of AOSP Android: danielpocock.com/android-betrays-tethering-data
Tethering worked fine on my Galaxy Nexus and when I upgraded to the Moto X 2014 Pure I thought Motorola had applied this tethering restriction but further investigation led me to believe that even the Nexus devices have this issue.
aaronbc said:
I don't think it's deliberately modified for the Moto X ROM. I believe it's a restriction of AOSP Android: danielpocock.com/android-betrays-tethering-data
Tethering worked fine on my Galaxy Nexus and when I upgraded to the Moto X 2014 Pure I thought Motorola had applied this tethering restriction but further investigation led me to believe that even the Nexus devices have this issue.
Click to expand...
Click to collapse
Hmm, I've never had an issue on my Nexus One or my current Nexus 4 (though I'm still--lamely--using Jelly Bean, maybe KitKat introduces a problem). Well, accept that I find I have to change the DNS servers to OpenDNS on my laptop or otherwise I have problems connecting when I tether over USB.
cb474 said:
Hmm, I've never had an issue on my Nexus One or my current Nexus 4 (though I'm still--lamely--using Jelly Bean, maybe KitKat introduces a problem). Well, accept that I find I have to change the DNS servers to OpenDNS on my laptop or otherwise I have problems connecting when I tether over USB.
Click to expand...
Click to collapse
I believe this feature came on an update. It might have been 4.4.4. On Nexus 5, if you didn't want reporting tethering to the carrier you needed to modify the "tether_dun_required" line to 0. This being a Google Play purchased Nexus 5. Here's more info in the Nexus 5 forums.
http://forum.xda-developers.com/google-nexus-5/general/fix-nexus-5-tethering-block-t2581035
So, nothing to do with Moto X itself. I haven't tried it yet but yea, this method should also work on the the Moto X.
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
aalupatti said:
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
Click to expand...
Click to collapse
+1
A dev should be able to whip something up sooner or later.
No.
aalupatti said:
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
Click to expand...
Click to collapse
Unfortunately:cyclops:, they consider that a security issue. So unless you use a hack, you are SOOL.
I suppose it is a bit of a risk but the range of NFC is so limited. Too small to penetrate one's pocket or read from a distance. The only thing I used it for was in the car to toggle WiFi and Bluetooth which kicked off a chain reaction to start/stop Pandora streaming. Now I have to wakeup the phone first to scan NFC and connect BT. Not that big an inconvenience but I did like the option.
Sent from my Nexus 6 using Tapatalk
I guess its only a matter of time before a Dev figures this out.
Sent from my Nexus 6 using Tapatalk
Or someone fixes xposed for art.
Sent from my Nexus 6 using Tapatalk
vvveith said:
Unfortunately:cyclops:, they consider that a security issue. So unless you use a hack, you are SOOL.
Click to expand...
Click to collapse
It's no more a security risk than being able to enable "Ok Google" when the screen is locked. Not being able to to use NFC when the screen is locked has always annoyed me and was glad Xposed allowed me to do it with KitKat, alas no more. Even my work Blackberry, any current BB10 model and supposedly the most secure of the OSes, allows me to enable NFC when not locked.
Lost in translation?
Taomyn said:
It's no more a security risk than being able to enable "Ok Google" when the screen is locked. Not being able to to use NFC when the screen is unlocked has always annoyed me and was glad Xposed allowed me to do it with KitKat, alas no more. Even my work Blackberry, any current BB10 model and supposedly the most secure of the OSes, allows me to enable NFC when not locked.
Click to expand...
Click to collapse
We are not talking about being able to enable NFC when the screen is not locked. We are talking about having NFC enabled, and the device is sleeping with screen off, not being able to have NFC detect tags or what not without first turning screen on then also unlocking the device. I think you know this but just must of typed it wrong. If not, NFC works great with screen on once past the lock screen. I never disable NFC, I use it the same as the previous post. Getting in car, turns on bluetooth and then launches Pandora and GPS.
With the new Android Auto app and a supporting head unit, all you have to do when you get in your car is plug your phone into a USB port and everything else is automatic. Yeah, one great thing about Nexus 6 and mobile hands free tech.
vvveith said:
We are not talking about being able to enable NFC when the screen is not locked. We are talking about having NFC enabled, and the device is sleeping with screen off, not being able to have NFC detect tags or what not without first turning screen on then also unlocking the device. I think you know this but just must of typed it wrong. If not, NFC works great with screen on once past the lock screen. I never disable NFC, I use it the same as the previous post. Getting in car, turns on bluetooth and then launches Pandora and GPS.
Click to expand...
Click to collapse
You're correct, it's a miss-type and I wrote "unlocked" instead of "locked" - corrected.
I too also always keep NFC enabled, but having to unlock the phone is a real nuisance, thankfully as I also keep Bluetooth on now I can set my in-car to be a trusted device that disables the lock, so once the the connection is made I know I can just tap the phone without worrying. But now I don't even do that as I get Tasker to detect the connection and do it for me
I'm bumping the hell outa this thread. Just bought 20 of my first NFC tags to use various places just to find out NFC is disabled when the screen is off!? Mega-fail.
Anyone find any way to do this or is there a ROM that supports this yet that anyone knows of?
HixVAC said:
I'm bumping the hell outa this thread. Just bought 20 of my first NFC tags to use various places just to find out NFC is disabled when the screen is off!? Mega-fail.
Anyone find any way to do this or is there a ROM that supports this yet that anyone knows of?
Click to expand...
Click to collapse
i just wake up the device with s2w and then use NFC for various actions including unlocking the screen ( i use a pw due to exchange enforcement )
+1
Anyone have any luck getting this working?
I've tried the Xposed module and can't seem to get screen off detection working.
I'm on 5.1.1 (LMY48I)...
Im in the same boat as Jazic... any updates here?
no way?
You would think this functionality would be natively inherent...
This should be at least a quasi-option.
Like you should be able to enable NFC while screen is asleep to a white-listed tag, and be able to set it to wake up screen or not, and be able to unlock phone or not.
So long as a white-list is required it's not a security risk.
It would also be cool to be able to set up app specific UI macros to initiate from NFC.