I've been using both Tasker and Trigger over the years and I use Trigger to switch Airplane mode on at night and back off in the morning. This has been working fine for as long as I've had the phone. Phone is rooted and I just updated from BOG5 to BOK3 using the process here on XDA with Flashfire and now Trigger cannot enable or disable Airplane mode. It says it took the action but nothing actually changes with the phone.
I've tried things like removing the SU permission and re-granting the permission, I've made sure that SU is working - other root access apps seem to be working. With Tasker and Secure Settings plug-in, I can still change airplane mode but I haven't figured out how to have a variable schedule for weekdays vs. weekends like I can in Trigger.
Just wondering if anyone else is seeing anything similar or has noticed a behavior change for Airplane mode with BOK3?
oh well, I just went ahead and used Tasker to create an airplane mode task and that works. just didn't understand why airplane behavior suddenly changed.
Related
Kind of hard to explain what I want, but when I'm outside using my phone, and then come inside the house I want to keep the wifi on, but turn off the cell antenna to save battery (I find with just wifi on, the battery lasts a long time). I know I can do this by checking airplane mode, but then that turns off wifi, and I have to re-enable wifi, sort of a 3-4 key stroke that I'm wondering if I can do in one?
I've tried power toggles, but couldn't see the option for what I want to do with it.
You could use an app like Tasker, or Automateit (<---has free and paid version). You could have it execute a task when you enable AP mode that turns wifi back on. You can get pretty creative with the tasks as well. I haven't set it back up on my N4, but on my previous phone my need to enable/disable anything was nearly eliminated.
Thanks CMNein, I'll have a look at Tasker.
NFC tags.... I use Samsung Tectiles
You can Program a tag to go into airplane mode and turn wifi on
Sent from my Nexus 7 using Tapatalk 2
See if Plane Mode Tweaker works for the Nexus 4. https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.airplanemodetweak
It allows you to configure airplane mode so it won't disable wifi automatically. Also allows you to use bluetooth in airplane mode if it's locked.
I've read that apps to control airplane mode don't work, at least with the stock firmware.
http://forum.xda-developers.com/showthread.php?p=29219003
I'm still using an HTC Sensation, but I've got a battery of apps to automate turning airplane mode and wifi on when at home, and back off when away.
ziddey said:
See if Plane Mode Tweaker works for the Nexus 4. https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.airplanemodetweak
It allows you to configure airplane mode so it won't disable wifi automatically. Also allows you to use bluetooth in airplane mode if it's locked.
I've read that apps to control airplane mode don't work, at least with the stock firmware.
http://forum.xda-developers.com/showthread.php?p=29219003
I'm still using an HTC Sensation, but I've got a battery of apps to automate turning airplane mode and wifi on when at home, and back off when away.
Click to expand...
Click to collapse
Maybe time for you to join the N4 club.
https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5nbXN0eWxlcy5hdXRvd2lmaSJd
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
machostallion said:
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
Click to expand...
Click to collapse
Mendanbar said:
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
Click to expand...
Click to collapse
I had the same problems you described back in December when I was running the beta off of the devs site. All seemed fixed when it got released to the play store.
Currently I'm running the CM stock kernel. I haven't made any mods, no theming, etc. It was a clean install with full wipes of everything twice. I flashed it with TWRP 2.3.3.
It is odd that the system clock could be behind the widget clocks. I've seen it the other way around where the widget would be behind the system if waking the phone after being in deep sleep a while. It's more strange that I can't open llama at all when I'm on mobile data now. It will only open when on Wifi. I do have quite a few Wifi dependent actions but since they work fine on the stock rom they should in theory work on CM. Maybe I'll keep testing and try to get a logcat to show something for the dev
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Update: Twice yesterday, I got missed texts and calls (saw them via google voice site on computer). I checked my phone and saw that it was in airplane mode with wifi off. This doesn't even make sense, since wifi is set to only turn off "upon leaving home"
ziddey said:
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Click to expand...
Click to collapse
I have been unable to duplicate the system clock glitch. I don't use llama for any alarms but I do have quite a few time based events to control volume levels and screen brightness. . After further testing, llama seems to do most of the set actions about 80% of the time. Sometimes it will be one of the actions in a string doesn't stick and sometimes it will miss a time based event. For some reason it has consistently missed the event at 11pm when it's supposed to put the phone into silent mode and lower the screen brightness. That time event is based on being in my "home" area, however, usually at that time my other events have been triggered which puts the phone in airplane mode with Wifi. Keeping Wifi on after triggering airplane mode also doesn't happen quite often. I know JB changed the permissions for apps accessing and modifying airplane mode but since I'm rooted and llama was changed to support it, it should work. I think there may be needs to be an option to add additional delays between multiple actions that are triggered by the same event.
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
lilfleck said:
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid :good::good:
Hi Ho thunder cats!
so last time i tried this i fubared my device and had to restore. I have used tasker and secure settings to turn airplane mode to only control the CELL radio. i want to use airplane mode to only turn off the cell i want to kee BT and WIFI actice i cant stand and flipping HATE that it turns everything off , last time i was trying to edit in SQL database and almost got there before it just ded and had to restore ... i was upid and didnt back up ,
so i have serached , found TONS of good stuff however HALF THE APPS on the play store for THIS EXACT thing dont work for the note 3 , i have the mod in xposed > wanam to allow install of all play store but i still cant install or use these apps to turn off everything except the CELL via airplane mode ,
if someone knows how to do it for the tote 3 please tell me ..
*EDIT* close please ,
SOLUTION , seems to work , the tasker plus secure settings , had to manually select the settings one at a time and leave BT for last to remove PLUS reboot the device , now first test with WIFI and BT on airplane mode has left my head set connected plus wifi , will test further and hope this helps someone else who gets stuck on the same thing ,
link for the instrctions i found that helped me ,
http://br0sk.blogspot.com/2012/12/control-aeroplane-mode-with-tasker-on.html
*NOT MY WORK *
A rooted phone. It will not work on a non rooted phone since Secure Settings has to be installed in a non standard location.
Tasker installed
Secure Settings installed
When creating a task in Tasker you can now once again select what radios to disable when aeroplane mode is activated. Here is how to do it.
Open Tasker
Go to the task tab
Create a new task
Click the + sign to add a new action to the task
Click the plugin option
Click Secure Settings
Click edit button next to the label "Configuration"
Scroll down to the helper functions
Select Airplane Mode Radios
Tick the radios you want to disable when aeroplane mode is activated
Click the save button in the lower left corner(it looks like a floppy drive)
Repeat 4-8
Click Airplane mode
Tick the radio button for "on"
Click the save button
Now test the action by clicking the play button in the lower right corner
Watch the aeroplane mode icon showing up and the WiFi still staying active(if fyou selected to only turn off the radio in step 10)
Now you can use this task in any profile.
Closed at OP request.
I can't seem to get tasker to perform any tasks through Secure Settings. Can't get it to toggle air plane mode, change any of the location settings to off, battery saver, high accuracy, etc.
Am I missing something? The 6P is rooted and I know these tasks works because I imported them over from my last phone. Anyone with some tasker experience care to lend me a hand?
I just used Tasker/Secure Settings to test a few commands and they worked. I toggled "Show Touches" and Airplane Mode. I had not previously granted root to Secure Settings, so it asked for that when I executed the task, but it worked fine upon granting.
Maybe check SuperSU to see if it defaulted to deny if you didn't accept quick enough? I am on the latest factory image for the 6p, MDB08M.
Hope this helps.
fury683 said:
I just used Tasker/Secure Settings to test a few commands and they worked. I toggled "Show Touches" and Airplane Mode. I had not previously granted root to Secure Settings, so it asked for that when I executed the task, but it worked fine upon granting.
Maybe check SuperSU to see if it defaulted to deny if you didn't accept quick enough? I am on the latest factory image for the 6p, MDB08M.
Hope this helps.
Click to expand...
Click to collapse
Thanks, that's exactly what I needed to know. I went ahead and wiped the phone and reinstalled everything, it's now functional for me after the reinstall. Thanks again for testing it out.
I use both for toggling Location without issues. There is a beta version of Tasker on the developers website that may help you out.
Got it working by installing a fresh version from the Play store
Somewhat related.. apparently Tasker was removed from the Play Store last night.
http://www.androidcentral.com/tasker-has-been-removed-google-play-store
Hi, I'm running a rooted stock Oreo (version 8.0.0) and I've just discovered that when I turn flight mode on, if I then turn wifi on, I get the pop-up message "In flight mode" and the wifi icon in Quick Settings stays a light blue shade but Wifi doesn't actually turn on.
I may be mistaken but I thought this was working last year and I haven't done any updates to the phone.
Anyone have any ideas how to fix this?
Kind regards,
Mack.
Hi, I'm pretty sure you can use this:
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
One of the settings allows you to tune Airplane Mode.
Just to update - I think there must have been some kind of data corruption... I did a factory reset and it all worked correctly again.