Wi-Fi hotspot DHCP doesn't function when triggered by Tasker, but works fine when manually triggered (Pixel XL 7.1)

[James Levac]

Not sure if this topic will gain much traction, but I've been able to identify and confirm with another pixel owner that this occurs as described herein.  

Basically my situation is that I have a tasker profile setup such that when my phone connects to my car's bluetooth, the mobile hotspot is turned on to also provide wi-fi to the deck (Carjoying deck on Android 5.1.1).  This setup worked fine using my last device (Moto X Force on Android 6.0.1).  With my new Pixel XL running Android 7.1, the mobile hotspot is enabled but the headunit's wifi menu gets stuck at 'Obtaining IP Address', and eventually fails to connect.  Nothing on the car stereo resolves the issue (cycling the wifi radio, forgetting/reconnecting to the AP, rebooting the car stereo, etc..).  However, manually disabling the mobile hotspot and re-enabling it causes the deck to immediately connect without issue.

The only remedy I've found to consistently resolve this is by statically assigning both the IP address and default gateway on the car stereo.  It then connects to the hotspot fine whether triggered by tasker or not, but returning the settings to DHCP causes the issue to resurface.

As stated, I've verified that this occurs on a second Pixel device, but whether or not the issue is with the Pixel or Nougat specifically is undetermined (as I don't have access to any other nougat devices).  Unsure if there is anything that can be resolved with Tasker or if this is an issue with Android.

[Eduardo Cerqueira]

I have the same issue with my Pixel and Tasker turning on the Wi-Fi hotspot. I have found that setting a static IP works for most devices, but it will not work with my Nexus 7 2013 running Andoird 6.0.1. It gets stuck in a loop Connecting -> Connected with no internet access -> Disconnect -> repeat. I guess I'll be manually activating the hotspot for now.

[Sam Quinn]

I am also having this exact issue on my Nexus 6P on 7.1.1. Just as Eduardo said bellow my Nexus 7 goes into a connecting loop with a static IP set. I have not tried a static IP on my Nexus 9 yet, I hope it works because that is used as my car deck.

[Gareth Phillips]

I'm getting the same on a Nexus 5x. I stumbled upon tasked this week and use it to enable my hotspot when the Bluetooth pairs with my car. Hotspot appears to be on, and devices can see it, but cannot connect to the internet reporting no internet access, apparently due to lack of IP address. Manually enabling the hotspot feature works fine

[Gareth Phillips]

Setting a static IP in the same range, or even the exact same IP as the hotspot assigned last time I manually enabled it, does NOT work for me.

[James Levac]

Can confirm that the fix of statically assigning the IP address also stopped working for me shortly after applying it.  Seems that this wasn't a stable fix after all.  I contacted Google support and they are pointing the finger back at tasker.

On Fri, Nov 11, 2016 at 12:16 PM, Gareth Phillips <gar...@phillips79.co.uk> wrote:

Setting a static IP in the same range, or even the exact same IP as the hotspot assigned last time I manually enabled it, does NOT work for me.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Pent]

Can confirm that the fix of statically assigning the IP address also stopped working for me shortly after applying it.  Seems that this wasn't a stable fix after all.  I contacted Google support and they are pointing the finger back at tasker.

Not surprising, since their OS doesn't provide any API for tethering control and Tasker has to
do it all with guesswork and hidden functions.

(I didn't get to looking at this issue yet)

Pent

[Pent]

(and I don't know when I'm going to have a 7.1 device)

Pent

[Steven Rodriguez]

Same here.  I reported this exact issue to the developer of Tasker last week, thinking it was a problem with his app.

On Tuesday, November 1, 2016 at 1:10:11 PM UTC-4, James Levac wrote:

[Peter Pliquet]

I do have some issues with Tasker and Android 7.1 too...

1. Tethering shows up, but connection does not work. Stucks in obtaining IP-Address.
2. Volume settings are not overtaken. I have some different tasks where I need muting or setting the volume to special settings.... Does not work at all.
3. Switched off actions are used if Tasker starts automatically the dependent task. Could verify that with a "Say"-action... Manual started tasks work without the deactivated action item.

Hopefully you are able to get this back working.... Tasker is one of my most used app with tons of different important tasks for every day usage.

[Pent]

1. Tethering shows up, but connection does not work. Stucks in obtaining IP-Address.

OK, but could you please post the other problems on a different thread so we don't
dilute this one.

Thanks!

[Peter Pliquet]

Ok will do later. Thanks for pointing this out. My fault... :(

By the way to give a short workaround for getting tethering working:
From my side of view, this is a bug in Android 7.1 instead of Tasker.

But what you should try is:

1. Switch Wifi to off with a tasker action.
2. Put in a sleep for at least 2 seconds to give Android the chance to switch wifi off.
3. Use Secure Settings to activate Tethering.
4. Follow up with your actions as before.
   

This workaround is working fine.Tethering is completely registered in Android. The IP-Address is submitted in time and works correct.

[Gareth Phillips]

WiFi tether in the "net" options is now red / unavailable on my 5X when I try to create a new action?

[Steven Rodriguez]

I've tried your work around but unfortunately it isn't working for me DHCP still will not issue an IP address with secure settings activating the tethering

[Peter Pliquet]

Hmmm... strange.
I tried it yesterday a couple of times in my car and it worked perfect... until tonight when driving home. I had to reboot my phone and since then my work around does not work anymore...
F**k
@Pent:
I could store traces if that helps?
...added to this posting....

Thanks,
Peter

[Jorge d'Argence]

I have the same issue. I did some traces and compared the output of the debug between activating it via the Nougat system interface vs Tasker.

When doing it through tasker, the BOLD entries are missing:

11-20 16:52:20.143   579  1085 D TetherController: tetherInterface(wlan0)

11-20 16:52:20.219   579  1085 D TetherController: Setting IP forward enable = 1

11-20 16:52:20.221   579  1085 D TetherController: Starting tethering services

11-20 16:52:20.222   579  1085 D TetherController: Sending update msg to dnsmasq [update_ifaces|wlan0]

11-20 16:52:20.222   579  1085 D TetherController: Tethering services running

11-20 16:52:20.235  1086  1086 D Tethering: got Sim changed to state LOADED, mSimAbsentSeen=false

11-20 16:52:20.236  1086  1105 D ConnectivityService: requestNetwork for uid/pid:1000/1086 NetworkRequest [ TRACK_DEFAULT id=192, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]

11-20 16:52:20.238  1086  1105 W NetworkIdentity: Active mobile network without subscriber!

11-20 16:52:20.239  1086  1105 D ConnectivityService: requestNetwork for uid/pid:1000/1086 NetworkRequest [ REQUEST id=194, legacyType=4, [ Transports: CELLULAR Capabilities: DUN&TRUSTED&NOT_VPN] ]

11-20 16:52:20.254  1086  1429 D ConnectivityService: Switching to new default network: NetworkAgentInfo{ ni{[type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: fast.t-mobile.com, failover: false, available: true, roaming: false, metered: true]}  network{132}  nethandle{566952119006}  lp{{InterfaceName: rmnet_data0 LinkAddresses: [XXXXXXXXXXXXXXXXXXXXXXXXX/64,]  Routes: [::/0 -> fXXXXXXXXXXXXXXXXXXXXX rmnet_data0,] DnsAddresses: [XXXXXXXXXXXXXXXX,] Domains: null MTU: 1500 TcpBufferSizes: 786432,1572864,3840000,786432,1572864,3840000}}  nc{[ Transports: CELLULAR Capabilities: SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN LinkUpBandwidth>=51200Kbps LinkDnBandwidth>=102400Kbps Specifier: <1>]}  Score{10}  everValidated{false}  lastValidated{false}  created{true} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} }

11-20 16:52:20.269  1086  1442 I GnssLocationProvider: WakeLock acquired by sendMessage(5, 0, null)

11-20 16:52:20.269  1086  1442 I GnssLocationProvider: WakeLock acquired by sendMessage(6, 0, null)

11-20 16:52:20.270  1086  1098 I GnssLocationProvider: WakeLock acquired by handleInjectNtpTime()

11-20 16:52:20.271  1086  1098 I GnssLocationProvider: WakeLock released by handleMessage(5, 0, null)

11-20 16:52:20.271  1086  1429 D ConnectivityService: Sending CONNECTED broadcast for type 0 NetworkAgentInfo [MOBILE (LTE) - 132] isDefaultNetwork=true

11-20 16:52:20.271  1086  1098 I GnssLocationProvider: WakeLock released by handleMessage(6, 0, null)

11-20 16:52:20.277 16923 16923 I EthernetIfaceManager: Received Intent: android.net.conn.CONNECTIVITY_CHANGE

11-20 16:52:20.278 16923 16923 I EthernetIfaceManager: Received Intent: android.net.conn.CONNECTIVITY_CHANGE

11-20 16:52:20.281  1086  1425 D WIFI    : got request NetworkRequest [ TRACK_DEFAULT id=192, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 10

11-20 16:52:20.281  1086  1425 D WIFI_UT : got request NetworkRequest [ TRACK_DEFAULT id=192, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 10

11-20 16:52:20.281  1715  1715 D PhoneSwitcherNetworkRequstListener: got request NetworkRequest [ TRACK_DEFAULT id=192, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 10

11-20 16:52:20.282  1086  1443 D Ethernet: got request NetworkRequest [ TRACK_DEFAULT id=192, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 10

11-20 16:52:20.285  1086  1425 D WIFI    : got request NetworkRequest [ REQUEST id=194, legacyType=4, [ Transports: CELLULAR Capabilities: DUN&TRUSTED&NOT_VPN] ] with score 0

11-20 16:52:20.285  1086  1425 D WIFI_UT : got request NetworkRequest [ REQUEST id=194, legacyType=4, [ Transports: CELLULAR Capabilities: DUN&TRUSTED&NOT_VPN] ] with score 0

11-20 16:52:20.286  1086  1443 D Ethernet: got request NetworkRequest [ REQUEST id=194, legacyType=4, [ Transports: CELLULAR Capabilities: DUN&TRUSTED&NOT_VPN] ] with score 0

11-20 16:52:20.288  1715  1715 D PhoneSwitcherNetworkRequstListener: got request NetworkRequest [ REQUEST id=194, legacyType=4, [ Transports: CELLULAR Capabilities: DUN&TRUSTED&NOT_VPN] ] with score 0

11-20 16:52:20.289 23653 23653 I dnsmasq : started, version 2.51 cachesize 150

11-20 16:52:20.289 23653 23653 I dnsmasq : compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP

11-20 16:52:20.289 23653 23653 W dnsmasq : warning: no upstream servers configured

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.49.2 -- 192.168.49.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.48.2 -- 192.168.48.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.47.2 -- 192.168.47.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.46.2 -- 192.168.46.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.45.2 -- 192.168.45.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.44.2 -- 192.168.44.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.43.2 -- 192.168.43.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : DHCP, IP range 192.168.42.2 -- 192.168.42.254, lease time 1h

11-20 16:52:20.289 23653 23653 I dnsmasq : read /etc/hosts - 2 addresses

11-20 16:52:20.922  1086  1105 I Tethering: Finding IPv4 upstream interface on: {InterfaceName: rmnet_data1 LinkAddresses: [X.X.X.X/25,]  Routes: [0.0.0.0/0 -> X.X.X>X rmnet_data1,] DnsAddresses: [10.177.0.34,10.177.0.210,] Domains: null MTU: 1500 TcpBufferSizes: 786432,1572864,3840000,786432,1572864,3840000}

11-20 16:52:20.922  1086  1105 I Tethering: Found interface rmnet_data1

11-20 16:52:21.355  1086  1105 I Tethering: Finding IPv4 upstream interface on: {InterfaceName: rmnet_data1 LinkAddresses: [X.X.X.X/25,]  Routes: [0.0.0.0/0 -> X.X.X.X rmnet_data1,] DnsAddresses: [10.177.0.34,10.177.0.210,] Domains: null MTU: 1500 TcpBufferSizes: 786432,1572864,3840000,786432,1572864,3840000}

11-20 16:52:21.355  1086  1105 I Tethering: Found interface rmnet_data1

Whatever hack Tasker is using to enable the Hotspot is not triggering all the actions required to make tethering work. I'm on T-Mobile and public IP addresses have been masked.

[Matej Drobnič]

Somebody on reddit has figured out ip_forward option is disabled when tasker toggles tethering: https://www.reddit.com/r/tasker/comments/5ag66i/wifi_hotspot_on_nougat/d9pkmgn/

Could it be something linked to that?

[Jorge d'Argence]

I saw that post yesterday, and when checking this on my Pixel, I noticed that both Tasker and the System set the ip_forward value correctly, as shown in the debug I posted. I confirmed by looking at the value while hotspot was enabled under both circumstances.

[Brad Daniels]

It doesn't set ip_forward for me. After enabling the hotspot in Tasker either through the regular Tasker hotspot task or the Secure Settings plugin, I opened an ADB shell and ran

cat /proc/sys/net/ipv4/ip_forward

and it returns a 0. When I enable the hotspot in settings it returns a 1. 

[Peter Pliquet]

Guys, this seems to be an Android issue, not an issue on Tasker side...
Nougat has an additional setting for system profiles.
Predefined are Automobile, Default and Silent.

If you use Automobile and edit the settings for this profile to activate tethering when connected to BT in car, you get the same result.
Tethering seems to be activated, but no IP address is provided.

I think we need to blame Android to get rid of this issue...

[Jorge d'Argence]

Definitely a 7.1.X issue, since I was using this on 7.0 on my 6P before without issues.

For now I am using a workaround with Autotools that "clicks" on the Hotspot tile through Quick Settings. 

How do you edit the Automobile profile to turn hotspot on?

[Peter Pliquet]

Nothing easier than that...
Go to settings, open the system profiles and click on the right gearwheel icon.
Each single setting can be adjusted in there...
A bit down there is a setting for "portable Hotspot". There you can choose between leave unchanged, turn on or turn off.
As trigger I use the BT connection to my car stereo.

These system profiles are really powerfull... It seems that you can get rid of a lot tasks which are done by tasker now.
...if it would work as expected.... May be I switch back to 7.0 if the issue does not exists there.

[Jorge d'Argence]

I know that I was using the Tasker Hotspot function on 7.0 with my 6P. I only had it running DP 7.1.1 for a day or two before my Pixel arrived, so I never tested the Hotspot and Tasker with it.

I don't see these system profiles in my settings. Are you using a 6P with a stock image? Or something else?

[Peter Pliquet]

I´m using Cyanogen mod 14.1 on my G4.
Seems that there is a difference ... :)

[Peter Pliquet]

Okay, flashed back to CM14.0 based on Android 7.0 and the issue is gone. Tasker works as expected.
I apologize for pointing on Tasker!
Tasker is the best tool I ever used.

[Steven Rodriguez]

Can you please provide the steps that you used to configure the autotools Tasker plugin to toggle the hotspot please? I'm looking at the plug in and I don't see anything in the actions that would activate the settings menu and simulate pressing the hotspot button.

[Jorge d'Argence]

Here is a quick copy of what I have in my start task:

AutoInput Global Action: Quick Settings

AutoInput UI Query: Only Visible: False, Only Clickable: True, Check Screen State: False

AutoInput Action:  Type: Text, Value Hotspot, Action Click, Is Tasker Action false, Check Screen State false

Status Bar: Set Collapsed

I have noticed that it doesn't always turn on with the screen off, so I need to tweak this a bit to make sure it always run. I just added Secure Settings: Screen & Keyboard Lights on for 10 seconds at the beginning of the task.

The exit task is a lot easier, you can use the Tasker Hotspot Off function to turn it off.

[Steven Rodriguez]

Thank You, I see my mistake, I was trying to do this with autotools not autoinput

[Matej Drobnič]

Yes, Android 7.1 fucked these settings up, but these were never part of the offical API. So issue is on the side of the Tasker and  it is up to Tasker (and CM for the CM's profiles) devs to fix it.

Does anybody know any good 3rd party tethering app that works on 7.1 and can be toggled with Tasker? Can be root.

[Steven Rodriguez]

Did this get fixed in 4.9? I don't see it specifically mentioned in the changelog but the developer did say "Android 7 bug fixes"

[Pent]

No.

Pent

[Pent]

I still don't have a phone with 7.1.1 to investigate this alas, only a tablet.

Could someone with this problem please check that Tasker has the modify settings permission.

You can search for 'modify' in the Settings app, or e.g. on my N5 it's in
Android Settings / App prefs / click Cogwheel at top / Modify System Settings.

Thanks,

Pent

[Nir Tasher]

I have this issue with Pixel XL 7.1.1. and Tasker. Takser has "Modify settings" permission. I've also tried exporting the hotspot task as an app using app factory and it has the same results - not working.

Nir

On Tuesday, November 1, 2016 at 7:10:11 PM UTC+2, James Levac wrote:

Not sure if this topic will gain much traction, but I've been able to identify and confirm with another pixel owner that this occurs as described herein.  

Basically my situation is that I have a tasker profile setup such that when my phone connects to my car's bluetooth, the mobile hotspot is turned on to also provide wi-fi to the deck (Carjoying deck on Android 5.1.1).  This setup worked fine using my last device (Moto X Force on Android 6.0.1).  With my new Pixel XL running Android 7.1, the mobile hotspot is enabled but the headunit's wifi menu gets stuck at 'Obtaining IP Address', and eventually fails to connect.  Nothing on the car stereo resolves the issue (cycling the wifi radio, forgetting/reconnecting to the AP, rebooting the car stereo, etc..).  However, manually disabling the mobile hotspot and re-enabling it causes the deck to immediately connect without issue.

The only remedy I've found to consistently resolve this is by statically assigning both the IP address and default gateway on the car stereo.  It then connects to the hotspot fine whether triggered by tasker or not, but returning the settings to DHCP causes the issue to resurface.

As stated, I've verified that this occurs on a second Pixel device, but whether or not the issue is with the Pixel or Nougat specifically is undetermined (as I don't have access to any other nougat devices).  Unsure if there is anything that can be resolved with Tasker or if this is an issue with Android.

[Abdullah Alahdal]

I do not have problems with hotspot, I'm running customized rom (Pure Nexus, Android 7.1.1 on Nexus 6)

[Pent]

This sounds more and more like a ROM issue from these two posts:

>Guys, this seems to be an Android issue, not an issue on Tasker side...
>Nougat has an additional setting for system profiles.
>Predefined are Automobile, Default and Silent.
>If you use Automobile and edit the settings for this profile to activate tethering when connected to BT in car, you get the same >result. Tethering seems to be activated, but no IP address is provided.

On Wednesday, 18 January 2017 20:45:11 UTC+1, Abdullah Alahdal wrote:

I do not have problems with hotspot, I'm running customized rom (Pure Nexus, Android 7.1.1 on Nexus 6)

Pent

[James Levac]

It's an issue specifically with the factory image.  3rd party ROMs seem not to be affected.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Matej Drobnič]

No, I also had this issue with CM14.1 ROM.

On Wednesday, 18 January 2017 21:27:21 UTC+1, James Levac wrote:

It's an issue specifically with the factory image.  3rd party ROMs seem not to be affected.

On Wed, Jan 18, 2017 at 1:21 PM, Pent <crafty...@gmail.com> wrote:

This sounds more and more like a ROM issue from these two posts:

>Guys, this seems to be an Android issue, not an issue on Tasker side...
>Nougat has an additional setting for system profiles.
>Predefined are Automobile, Default and Silent.
>If you use Automobile and edit the settings for this profile to activate tethering when connected to BT in car, you get the same >result. Tethering seems to be activated, but no IP address is provided.

On Wednesday, 18 January 2017 20:45:11 UTC+1, Abdullah Alahdal wrote:

I do not have problems with hotspot, I'm running customized rom (Pure Nexus, Android 7.1.1 on Nexus 6)

Pent

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Steven Rodriguez]

Does anyone know how to contact the Tasker developer to find out what the status is on correcting this? The work arounds are not consistent and there are lots of other devices running Android 7 now so if it's affecting those devices as well there's probably a good chance he has a device on nougat now he can test with to fix this.

[Abdullah Alahdal]

The developer is three posts before yours 😉

[Steven Rodriguez]

Oh I did not realize that Pent was the developer.

[Roberto Taormina]

Hi guys, 

I have the same trouble in my Nexus 5 with Pure Nexus 7.1.1.

So for now there isn't a way to fix that ?  

We need to wait if Pent can be fix in tasker?

[Ryan Tucker]

Just wanted to add that I'm having the same issue on my Galaxy S5 running Zephyr-N (rooted android 7.1.1), so it's not just a Pixel issue.

The same tasker settings used to work on the stock 6.0.1 ROM, and using the android settings menu or the quick settings in the top draw enable the hotspot with dhcp successfully in 7.1.1.

[Gabe]

I also have this issue with my Pixel XL running the latest Pure Nexus ROM... 

On Wednesday, January 18, 2017 at 3:27:21 PM UTC-5, James Levac wrote:

It's an issue specifically with the factory image.  3rd party ROMs seem not to be affected.

On Wed, Jan 18, 2017 at 1:21 PM, Pent <crafty...@gmail.com> wrote:

This sounds more and more like a ROM issue from these two posts:

>Guys, this seems to be an Android issue, not an issue on Tasker side...
>Nougat has an additional setting for system profiles.
>Predefined are Automobile, Default and Silent.
>If you use Automobile and edit the settings for this profile to activate tethering when connected to BT in car, you get the same >result. Tethering seems to be activated, but no IP address is provided.

On Wednesday, 18 January 2017 20:45:11 UTC+1, Abdullah Alahdal wrote:

I do not have problems with hotspot, I'm running customized rom (Pure Nexus, Android 7.1.1 on Nexus 6)

Pent

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Roberto Fabrizi]

Same here, stock rooted n5x 7.1.1

[muttley]

Same issue here: d802 LineageOS 7.1

Anyone have understand if the issue depend from tasker or android?

There are some workaround? 

I have autoinput (free version)

[Ryan Tucker]

I'm trying to find workarounds for this (other than autoinput).

So far I've added a shell command to turn on ip forwarding, but I still can't get traffic through (I've got a static IP on the client as dhcp still isn't working).

I know a little about linux, but not android specifically. I can't find references to dhcpd, does anyone know where we can start looking for ways to start it on android? I'm also curious why I can't get traffic through with a static and ip forwarding enabled... still investigating but suggestions are appreciated.

[Steven Rodriguez]

Pent, can we get an update on this please?  Are you actively trying to fix this?

[Pent]

 

 Are you actively trying to fix this?

No.

a) it looks like an Android bug, see previous post
b) enabling the hotspot is a single API call. I don't know
what I would be able to do to affect how Android responds to that
call

Pent

[Pent]

Not to say I will never look at it... I just think working on other stuff is more
useful at this time.

Pent

[James Levac]

Thanks for your replies Pent, but are you aware of or is it possible to get this bug on Google's radar?  Surely an email from you would be taken a little more seriously and be far more descriptive than what any of us as individuals could put together.  I don't know if I speak on behalf of everyone in this thread, but surely there is overwhelming appreciation for your continued hard work, and as someone who has been a Tasker user since it's initial release I'm personally humbled by your involvement in this thread.  I'm glad we have seemingly been able to pinpoint the issue, and I'm not surprised it's not easily resolvable, but anything you can do to even help push this forward a little would be appreciated.

Personally I had been using this function to activate my phone's wifi hotspot when it registers a connection to my car's bluetooth, such that my car's devices (car deck, dash cam, etc..) could gain internet connectivity.  It's highly convenient to have this happen automatically, and since having lost this ability so long ago I've yet to find an equally convenient replacement method.  As just a single user just trying to provide feedback on how I use your application, I find this function highly useful and disappointing to have been lost.  I appreciate though that this is at Google's doorstep, I'm just hoping you might be willing to assist by advocating on our behalves, if you haven't already.

Regardless of this issue, thank you for your continued development of such useful software.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Pent]

James, the problem is that this is a private API call. We are not supposed to be using it.
Google are going to have zero zeal to look at it. There's a good chance if it comes to their
attention it will have a system permission slapped on it.

Users complaining about the scenario where it doesn't work within Android
 (the Automobile system profile) is going to be more effective.

Pent

[James Levac]

Thanks for your response Pent, if we're not actually supposed to be using that API call then that's an answer/reason I can absolutely live with.  I think that's just what wasn't clear for me, but now it is.  Thanks again for your time.

--

[muttley]

Thanks also by my side, Pent!

Could I ask if ever someone will find a an alternative solution (or a workaround), to submit here (on this thread) the solution found?

I'm in the exactly situation of James, I mean that used this function to enable the HotSpot in my car when bluetooth connecting to my car audio system.

Thanks again!

On Monday, 27 February 2017 20:14:57 UTC+1, James Levac wrote:

Thanks for your response Pent, if we're not actually supposed to be using that API call then that's an answer/reason I can absolutely live with.  I think that's just what wasn't clear for me, but now it is.  Thanks again for your time.

On Mon, Feb 27, 2017 at 12:08 PM, Pent <crafty...@gmail.com> wrote:

James, the problem is that this is a private API call. We are not supposed to be using it.
Google are going to have zero zeal to look at it. There's a good chance if it comes to their
attention it will have a system permission slapped on it.

Users complaining about the scenario where it doesn't work within Android
 (the Automobile system profile) is going to be more effective.

Pent

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Steven Rodriguez]

Ditto, I use this functionality several times a day for the exact same reason. I really need it back one way or another. I tried the auto input solution to simulate the button press and no matter how many pauses or tricks I try to implement it still doesn't work consistently so I can't even call that a solution.

[Matej Drobnič]

Pent, check out this blog post: https://brady.thtech.net/2017/01/23/automated-hotspot-control-on-the-nexus-5x-continued-android-7-1-1/

Unfortunately, this method for some weird reason requires MANAGE_USERS permission which is system-level permission.

[John Doe]

From the latest link posted it's clearly a modification in Android source code. Any ROM based on AOSP is affected. There's nothing Pent can do (or other developers). You have only two options: simulate tap on the screen or use root.

[Matej Drobnič]

I have root and tethering through Tasker still does not work. There is no way at the moment to simply enable tethering through Tasker even if you have root and Xposed and everything.

[John Doe]

if you have root, you can create a task using Java code as the link you posted. Export the task as app, add the needed permissions, move the app in the system folder. In this way you create a system app. It should work

[Gabe]

Thanks so much for this. For everyone wondering, you install it in system/priv-app/. Once that's done it'll show up as a plugin for tasker where you'll have the option to enable/disable the hotspot. If you fail to copy the APK to system/priv-app/ it won't have the correct permissions, and will NOT work.

[Matej Drobnič]

I have quickly whipped up simple plugin based on above method: https://play.google.com/store/apps/details?id=com.matejdro.taskertethercontrol

It requires rooted phone to work.

[Sam Quinn]

THANK YOU! This fixed it for me.

[Evan Langlois]

Thanks for this. Ill give it a try. My initial diagnosis was that the dick service wasn't getting started. Sure enough, one of the main differences in manual vs tasked activation is dnsmasq being started when using the quick tile. I would think that starting dnsmasq manually via shell command would be a start. I just haven't had time to play with it yet.

[Evan Langlois]

Uhmm ... that was supposed to say DHCP service!!   Silly Android autocorrect, sorry.

Maybe it's a new Nougat feature!

[m4gh...@gmail.com]

This toggle plugin works in so far as it turns on the Hotspot, but it will not turn it off.  Likewise, if WiFi is already on, it will not start the hotspot.  

This is almost a deal-breaker for me with Nougat.  Probably time to look at going to another OS.

[Matej Drobnič]

Sounds very weird. Are you running custom ROM?

[Evan Langlois]

Mine goes on and off just fine.   And if Wifi is on, Hotspot will not turn on because Android doesn't support LTE and Wifi at the same time.  You can only HotSpot your LTE connection, not your Wifi.  Just add an entry to your tasker profile to turn off your Wifi and switch to LTE.  I use it in my car so that when my car's bluetooth is detected it turns on my HotSpot.  By the time I get to the car, my Wifi is gone and the phone has already switched to LTE.

Another OS?  Like what?

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Matej Drobnič]

For me, enabling tethering automatically turns off wifi. Maybe it is carrier-related?

[Kay-Michael Voit]

Are there any news on this? I still seem to have the issue on Lineage 14.1. As far as I noticed, it has not been mentioned that, at least in my case, the interface does not come up. "ip -4 addr" in the terminal does not show the 192.168.43.0/24 net. That is why static ips do not work.

[Evan Langlois]

https://play.google.com/store/apps/details?id=com.matejdro.taskertethercontrol

On Oct 26, 2017, Kay-Michael Voit <kaym...@gmail.com> wrote:

Are there any news on this? I still seem to have the issue on Lineage 14.1. As far as I noticed, it has not been mentioned that, at least in my case, the interface does not come up. "ip -4 addr" in the terminal does not show the 192.168.43.0/24 net. That is why static ips do not work.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

-- Sent with K-@ Mail - the evolution of emailing.

[Roberto Taormina]

This addon doesnt works very Well, sometimes

Il 26 ott 2017 21:41, "Evan Langlois" <uudr...@gmail.com> ha scritto:

https://play.google.com/store/apps/details?id=com.matejdro.taskertethercontrol

On Oct 26, 2017, Kay-Michael Voit <kaym...@gmail.com> wrote:

Are there any news on this? I still seem to have the issue on Lineage 14.1. As far as I noticed, it has not been mentioned that, at least in my case, the interface does not come up. "ip -4 addr" in the terminal does not show the 192.168.43.0/24 net. That is why static ips do not work.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

-- Sent with K-@ Mail - the evolution of emailing.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Evan Langlois]

You need root to make it install as a system app.  Its the only option I know of!

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Stas Voznuk]

Try https://play.google.com/store/apps/details?id=com.matejdro.taskertethercontrol&hl=uk&rdid=com.matejdro.taskertethercontrol&pli=1

Nougat + Tasker Tethering Control runs the first start, then Tasker

miss the launch!

вторник, 1 ноября 2016 г., 19:10:11 UTC+2 пользователь James Levac написал:

Not sure if this topic will gain much traction, but I've been able to identify and confirm with another pixel owner that this occurs as described herein.  

Basically my situation is that I have a tasker profile setup such that when my phone connects to my car's bluetooth, the mobile hotspot is turned on to also provide wi-fi to the deck (Carjoying deck on Android 5.1.1).  This setup worked fine using my last device (Moto X Force on Android 6.0.1).  With my new Pixel XL running Android 7.1, the mobile hotspot is enabled but the headunit's wifi menu gets stuck at 'Obtaining IP Address', and eventually fails to connect.  Nothing on the car stereo resolves the issue (cycling the wifi radio, forgetting/reconnecting to the AP, rebooting the car stereo, etc..).  However, manually disabling the mobile hotspot and re-enabling it causes the deck to immediately connect without issue.

The only remedy I've found to consistently resolve this is by statically assigning both the IP address and default gateway on the car stereo.  It then connects to the hotspot fine whether triggered by tasker or not, but returning the settings to DHCP causes the issue to resurface.

As stated, I've verified that this occurs on a second Pixel device, but whether or not the issue is with the Pixel or Nougat specifically is undetermined (as I don't have access to any other nougat devices).  Unsure if there is anything that can be resolved with Tasker or if this is an issue with Android.

[Stas Voznuk]

YES!

пятница, 27 октября 2017 г., 0:05:52 UTC+3 пользователь Roberto Taormina написал:

This addon doesnt works very Well, sometimes

Il 26 ott 2017 21:41, "Evan Langlois" <uudr...@gmail.com> ha scritto:

https://play.google.com/store/apps/details?id=com.matejdro.taskertethercontrol

On Oct 26, 2017, Kay-Michael Voit <kaym...@gmail.com> wrote:

Are there any news on this? I still seem to have the issue on Lineage 14.1. As far as I noticed, it has not been mentioned that, at least in my case, the interface does not come up. "ip -4 addr" in the terminal does not show the 192.168.43.0/24 net. That is why static ips do not work.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

-- Sent with K-@ Mail - the evolution of emailing.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/Rf75hoZjDTo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[2temp...@gmail.com]

I tried Nougat+ Tasker Tethering Control for about a week, but ultimately had to give up. On my SlimROM 7.1.2 Nougat, I used the magisk module Terminal App Systemizer to convert it to a system app & I'm using the Automate app to control Nougat+ Tasker Tethering Control. Sometimes it works as expected, other times it takes 30 sec to 1 minute to complete it's actions. I'm now using quick settings pull down & tap automation to turn hotspot On with the Automate app.