Related
So I know how one can get into the "Phone Info" section to find a button to "Turn Off Radio", which will turn off the phone radio, but still allow Wi-Fi and Bluetooth. That page can be accessed either by dialing "*#*#INFO#*#*", or by using the "Phone Info" activity shortcut in Better Cut.
What I would like to do, is create a toggle that would allow me to toggle the radio on or off, without having to get into the "Phone Info" page. Has anyone been successful with creating this toggle? I haven't been able to find anything through a search on here...or even a Google search. Basically, this would be another toggle, like airplane mode, but it would actually allow the Wi-Fi/Bluetooth to remain active.
Thanks!
kockroach said:
What I would like to do, is create a toggle that would allow me to toggle the radio on or off, without having to get into the "Phone Info" page. Has anyone been successful with creating this toggle? I haven't been able to find anything through a search on here...or even a Google search. Basically, this would be another toggle, like airplane mode, but it would actually allow the Wi-Fi/Bluetooth to remain active.
Click to expand...
Click to collapse
Google has specifically disallowed apps from doing this kind of thing because they were turning on data roaming and so on without telling the user. Although if you can turn it off with a feature code it might be possible that way, that is apps can dial numbers so ....
It is certainly possible... for a phone that has root. Look through the available terminal commands, and write an app to turn off the phone from the console.
Where is a listing of terminal commands? Realistically, I would think I should be able to find the "action" and "data" values that correspond to the "Turn radio off" button function, which would allow me to do this as a shortcut, rather than writing a program....which would be harder, as I do not have experience in that realm.
[Q] "package loader" doesn't allow "Install" option after update to 904
First of all, I've searched the forums and looked at the various topics it shows when I typed in the title for this post - definitely not a nube, I've flashed, bricked, unbricked, bricked, unbricked my phone 3 or 4 times, but this one has me stumped! Bare with me, I'm Danish, but I speak pretty good English... Mods - if this isn't where it should be, please publicly admonish me and put it where it should go.
Curious one: after I flashed my phone to 904, I now can't update anything "sideloaded" from Amazon or Slide-Me because the "package loader" (APK installer) refuses to let the "Install" button work. "Cancel" works just fine, of course.
(and yes, I know - now there's a 905 out there - but first things first, I've tried even after installing a 'virgin' 902 using Moto-Fastboot, but I got an assert failure on MTD:Boot)
I re-rooted my phone after flashing using "Motofail", which gave me access to all my backups and even though my ClockwordMod backup said the MD5 has didn't match I used Titanium Backup to try to extract files from it - and found that the MD5 doesn't match because there is no MD5 file there at all.
I was able to use the various options in Titanium Backup to replace all my apps, but at this point every time I try to install anything that's not from Google's Play Store I get to the point where the installer asks be to "Install" or "Cancel" and the install button appears available (not greyed out), but it doesn't work.
Has anybody else seen this? Can you tell me how you get around it, or what I need to do to fix it (other than trying to flash 905)??
One more thing: this new "Screen locked" button keeps showing up on my screen that was never there before - and it doesn't always ask me to swipe my pattern if that button is there. I've got Launcher Pro installed, JuiceDefender Ultimate and an alternative swipe screen, which I've already check, double-checked and triple-checked the configuration files for what might be causing the "Screen Locked" button to appear.
Update: the "No Install button working" problem just went away after two days - I didn't do a thing (that I know about). Weird - I've had this happen once before. Anyone have a guess as to the security lock bypass where it won't require my pattern to unlock, just a tap on the "Click to unlock" button? I have my security set to require a password any time the screen is turned off, so - that's my first guess, but setting it to "One minute" (same as the screen timer) does nothing, so I changed it back. I really do NOT like the idea of it just letting anyone pick it up and bypass my security lock! I know most people prefer it the other way (stay unlocked for a certain period of time without requiring you to keep putting you lock code/pattern in), but if I turn the screen off, I want it to prompt me for my pattern lock every time.
Found my own answer...
OK, not to the one about why "Package Installer" refused to work for a few days, but why I'm not getting the screen lock every time I turn my screen off any more:
It's "JuiceDefender Ultimate" - you need to set 's' ("Screen off") = 'l' ("Lock") time in the sliders under the "Timeout" settings on the Controls tab, and have your main settings set to lock on "screen off" instead of timed. The 'h' ("Home") setting in that same slider seems to have no effect on my device - anybody else observe differently? One things that always disappears when you flash is JuiceDefender's settings, even if you backup and later restore from /SDCARD or /SDCARD-EXT partitions. I don't know why - I suppose the subject for another question at some time in the future.
By the way, running the latest flash-only on device overclock to 1.2GHz (well, you do have to have Rummy's Toolbox so you can drop to Terminal mode and futz with the file) is the BOMB!!! Bio-***** is screaming along at 1.2GHz whenever I need the power. I'm in like (again)...
For the curious - it's right here: http://forum.xda-developers.com/showthread.php?t=1594804
I recently noticed the Google wallet app now allows me to enable tap and pay. I entered all my cards and have tried to use it at 3 different McDonald's. I open the app and it it says "Tap and pay ready" on the screen. I tap my phone and I get no response, nothing at the terminal. Of course the cashier always has no clue. I have confirmed my NFC is working as I can bump my phone to my wife's phone and get the buzz and ask for file transfer.
On the web you see a bunch of posts saying the Note 3 does not work - though most say that their "tap and pay" option is grayed out - Mine is not.
I am running a custom rom Android 4.4.2 Dynamic cat 2.0 .
Is there something the cashier is not doing?
Thanks
After upgrading to 6.0, i tried to turn on Now On Tap.
I know where the setting is- when i slide it to "on", I get the popup that says "Want any help with any screen? Turn on Now on Tap". When i click "get started" the slider goes back to off.
Anyone else seeing this?
bmwt said:
After upgrading to 6.0, i tried to turn on Now On Tap.
I know where the setting is- when i slide it to "on", I get the popup that says "Want any help with any screen? Turn on Now on Tap". When i click "get started" the slider goes back to off.
Anyone else seeing this?
Click to expand...
Click to collapse
I'm having the same issue with my Nexus 9. Can't find any solutions. I flashed the factory image twice now and wiped everything but the problem persists. :crying:
Getting it on Nexus 5
Working fine for me. Haven't done anything special. Just enabled it. Hit okay. Tried it out in Chrome. Went back to settings and still toggled on.
Sent from my Nexus 6 using Tapatalk
Okay, found it!
Apparently I can't use my Google App account ([email protected]) with Now on Tap. It works when I switched to my Google account ([email protected]). Hope that helps.
I'm having this problem too, and like you, I have a Google Apps account I'm using for my phone (I own the domain, and am the administrator). I'm going to have to look into this; either it may not be enabled for Google domains yet, or, it may have to be turned on, something I just found out with Google Maps (which was turned off in my Apps, so I couldn't access it until I turned it on).
I'll take a look, and if I find something, I'll post back.
---------- Post added at 10:40 PM ---------- Previous post was at 10:17 PM ----------
Okay, here is what I found for Google Apps for Domain Users.
For Google Now On Tap to work, the Web History service must be turned on in your Google Apps Domain. However, finding this is a real pain. Here is what to do:
The problem is the "x" to remove the filter is all the way on the right (in chrome).
1. Log In to your Google Apps admin control panel
2. At the bottom of your dashboard click on "More Controls", then "Apps"
3. Click "Additional Google Services"
4. Remove the Filter "Top Featured Services" by clicking on the "x" on the upper right side.
5. Scroll to the bottom and find Web History
6. Click the "On" Button
a. Select for all users; or
b. If you have various organizational units select which organizational unit
I am told this may take a bit to trickle down to one's phone (sometimes up to 24 hours to all users in the domain). I have made the change myself, but have not been able to turn Now On Tap on yet. However, others have reported this as what does the trick.
If I had not found this through a Google community thread, I'd have no idea how to do it. It's certainly convoluted and the admin control panel doesn't make it easy to find, nor would I have had any idea that this was the fix. I'll update everyone with my results once I've had time to see if the change takes effect.
ADDITIONAL NOTE: If you do not have the following setting enabled on your phone, you cannot turn on Now On Tap:
Settings->Search & Now->Accounts & Privacy->Google Activity Controls->Web & App Activity must be set to ON.
So far my attempts to google this answer have come up empty. I can open Google Maps driving mode with AutoShortcut no problem. But making it actually close is turning out to be impossible.
If I try to do a "Kill App", it doesn't kill the notification, leaving it in a bizarre half-open state. Has anyone found an intent or something that can actually kill this off properly?
Have you tried to run a Go Home action before killing the app?
Yes, unfortunately does not help at all. Even gave it ~3 second wait.
Vincent Law said:
So far my attempts to google this answer have come up empty. I can open Google Maps driving mode with AutoShortcut no problem. But making it actually close is turning out to be impossible.
If I try to do a "Kill App", it doesn't kill the notification, leaving it in a bizarre half-open state. Has anyone found an intent or something that can actually kill this off properly?
Click to expand...
Click to collapse
Try code run shell: am force-stop com.google.android.apps.maps & tick "use root". Change the package name if is necessary.
My device is not rooted, is that going to do anything?
Vincent Law said:
My device is not rooted, is that going to do anything?
Click to expand...
Click to collapse
Root is needed to run that command.
But did you try to kill another app with the method you've tried for google maps? Is it working?
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Vincent Law said:
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Click to expand...
Click to collapse
i am trying to "stop driving" using autonotification and cant figure it out. Can you please be more specific than "internal action" which internal action. What variable did you using for the stop driving button. I am trying to use autonotification query and action but i cant figure out which variable in the query to use for the action.
thanks
Vincent Law said:
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Click to expand...
Click to collapse
I'm new to autonotification - I have it set up to query for the "Maps" notification, and it's returning the %anapp variable correctly - I can even click on the notification and bring the focus back to the maps app - but how the heck do you fire this "internal action" to stop driving? I'm sure it must be obvious...
Bulldoguk72 said:
I'm new to autonotification - I have it set up to query for the "Maps" notification, and it's returning the %anapp variable correctly - I can even click on the notification and bring the focus back to the maps app - but how the heck do you fire this "internal action" to stop driving? I'm sure it must be obvious...
Click to expand...
Click to collapse
I just spent a few days trying to figure this out. Here is how I was able to get it working:
Create a new task / add these to a current task:
A1 - Add Action - Plugin, AutoNotification, Query. Tap Edit, Select "Maps" from Apps and under Advanced tap Internal Actions Big, tap the Tag icon. It should populate with %aninternalactions.
A2 - (Only needed for debugging) Add Action, Alert, Flash, tap the Tag and choose %aninternalactions, then edit to choose the first value in the array - %aninternalactions(1)
A3 - Add Action, Plugin, AutoNotification, Actions. Tap Intercept Action, tap the tag and choose %aninternalactions, then edit it again to - %aninternalactions(1)
To test, start driving mode and run the task manually. You should see the button GUID flash (if you enabled A2) and Driving Mode should end :good:
It works now
I figured out a solution.
Tasker gives you the advise to use ADB Wifi.
Here's what I did:
- enable and go to developer settings
- check ADB debugging
- check ADB while charging (only needed, if it stops working for you when you disconnect your USB cable. Try without first!)
- then run from your PC `adb tcpip 5555` to enable adb over wifi
- use Tasker Action "kill app", uncheck "Use Root".
Maps (or Driving Mode) can finally be killed this way.
Tried on Huawei Mate 20 Pro (LYA-L29) running Android 10 (10.0.0.214)
How are you able to open Google maps?
Mine opens for a millisecond then closes.
MSK1 said:
How are you able to open Google maps?
Mine opens for a millisecond then closes.
Click to expand...
Click to collapse
Hi, MSK1,
I searched for a long time for this solution, so maybe this one will help you out.
You can launch Google Maps directly into Navigation mode via using an intent.
You may find this one interesting. https://forum.xda-developers.com/showpost.php?p=46600949&postcount=3
Mine looks like this.
google.navigation:q=Zip+City,+Street+Number
Happy Driving!
Best Regards.
3di said:
Hi, MSK1,
I searched for a long time for this solution, so maybe this one will help you out.
You can launch Google Maps directly into Navigation mode via using an intent.
You may find this one interesting. https://forum.xda-developers.com/showpost.php?p=46600949&postcount=3
Mine looks like this.
google.navigation:q=Zip+City,+Street+Number
Happy Driving!
Best Regards.
Click to expand...
Click to collapse
Thanks.
I found an easier way.
I downloaded the "navigation shortcut" app from the play store.
When I launch this as an app from tasker then the navigation stays on.
Sent from my EVR-N29 using Tapatalk