Hotspot Enabling not working

[Sprintrider]

I had a pair of rules that would work on my Sony Experia - detection of not being connected to the Bluetooth of my car head unit would turn off my phone Hotspot and my phone WiFi on; being connected to the Bluetooth of my car head unit would turn off my phone WiFi, and my phone Hotspot on. Hotspot switching now does not work on my Nothing 3a Pro. I can't see any permissions that Automation should have that it does not. Running the rule manually does switch on and off the WiFi. Has Nothing put a Hotspot controlling permission in a new place?

[jens]

As far as I understand it has nothing to do with permissions. The hotspot cannot be controlled officially anymore for a couple of years. The current implementation is a hack already and should generally work up until Android 15. From 16 onwards it doesn't work anymore.

I have not found a solution for this. If you know of another app that can do this on Android 16 and above, please let me know.

[Sprintrider]

[/img]The Delta apk from f-droid says it has an 'intent' that Tasker can use - and provides instructions in its settings. The description seems to suggest other automation apks might be able to use it too.

[Sprintrider]

I guess this information is not useful then.

[jens]

I really like making and maintaining this application. I've been already working on this app for 10-15 years now. I have received many different kinds of message from people about it. Most positive, some few negative. But there are extremely few that I perceive as demotivating.

While I highly appreciate useful information (I haven't checked if the above is) and patience from users to answer further questions that help to narrow down issues, I have to strongly oppose the nagging sub tone of your last message.

How much time do you think I have for this project? In good weeks we're talking about 1-2 hours, sometimes it's no time at all. Most issues require a lot of time to actually reproduce the issue, set up a testing environment that resembles that of the user who reported a problem and a lot more to find the cause and later testing. Some reports are not bugs per-se, but wrong configuration/usage. But I still have to investigate because sometimes those are indeed bugs.
Make that on average 1.5 hours I have to invest per message that I receive. I get at least 3 such messages per week. You do the math.

This message took at least 10 minutes of this time.

[jens]

In theory the mentioned app "Delta" should be usable to to remote control the hotspot (in combination with Skizuku). I've tried it and I can toggle the hotspot through the Delta UI. But after enabling the Tasker integration in it, I cannot remote control it through a broadcast.

To rule out possible problems in my own app I have sent the broadcast through adb:

Code: Select all

adb.exe shell am broadcast -a dev.shadoe.delta.action.START_SOFT_AP -n dev.shadoe.delta/.SoftApBroadcastReceiver               
Broadcasting: Intent { act=dev.shadoe.delta.action.START_SOFT_AP flg=0x400000 cmp=dev.shadoe.delta/.SoftApBroadcastReceiver }                                                                                                        
Broadcast completed: result=0

That doesn't have any effect, not in an emulator, not in a real phone. Until that is not working, trying it through Automation is pointless.

But an action to start another program with those options should normally work:
Package name: dev.shadoe.delta
Class full name: dev.shadoe.delta.SoftApBroadcastReceiver
Activity/action name (2 options):

• dev.shadoe.delta.action.START_SOFT_AP
• dev.shadoe.delta.action.STOP_SOFT_AP

[Sprintrider]

Thank you for your supporting this investigation. A shame calling Delta using Automation does not work.

[jens]

There's a question regarding the remote execution, but it remains unanswered: https://github.com/supershadoe/delta/discussions/139