samedi 30 juillet 2016

[Request] Tasker Disable Bluetooth & The ballad of getting my car stereo to work

Hey everyone,

You may have seen my previous BT Issue and potential solution posted here a couple of days ago. The gist of it was:

Quote:

If my car is in the 2nd key position (Accessories, stereo, etc is ON) and the phone is connected via Bluetooth. If the car is then started, power cuts out for a second, the stereo reboots. On LL my phone would automatically reconnect after a couple of second, since the upgrade, something during the reconnect glitches. After this, I have to reboot the stereo AND the phone to get them to connect to each other properly.

After exhausting many other options, I feel as though it is possible that the stereo reconnects "too early" in MM, causing some kind of BT error. I can turn off auto-reconnect on the stereo, and perhaps if I let MM handle it, it would be better.

Anyway it seems like my STEREO is not reconnecting too early, but the PHONE is trying to connect to it too early. The stereo turns on so fast, I feel as though the phone didn't fully disconnect, causing some sort of glitch where I have to restart it. My car profile's exit task always runs successfully however

Then I thought I had the perfect idea : I have a state profile (bluetooth connected to car stereo) with enter/exit tasks. My idea was to use the exit task, turn off BT, wait 5 seconds, and then turn it back on.
For some reason, I am having NO luck with this. It just simply doesn't turn off bluetooth. The icon does not disappear. The command is the first one before WiFi On. I attached a log, and lo and behold, the command is not even in there for some reason. HOWEVER, when I manually run it using the "play" button, it executes as expected.

Does anyone have any ideas? The basics would be to turn bluetooth off, and then back on as soon as the connection is lost. The problem is that it must execute quickly, before the stereo turns back on (Which takes a couple of seconds at most)

HERE is a picture of the exit tasks (Turning Bluetooth back ON is cut off, but it is the last one)

The log is below. The bolded parts are part of other profiles. As you can see in the log, it does not even acknowledge the existence of the BT off task. I have obviously deleted, re-created the task, even set an IF statement to turn BT off if %BLUE = on, but that still resulted in nothing

Quote:

20160729 10.30.04 P Inactive ID4 Car Profile
20160729 10.30.04 P Active ID17 Auto Off Unpaired Bluetooth
20160729 10.30.05 E Start ID0:0.0 TaskService
20160729 10.30.05 T Running ID-86 System
20160729 10.30.05 T Running ID5:2 Car Profile Exit
20160729 10.30.05 A OK ID-86.1 Anon.BT Voice Volume
20160729 10.30.05 T Running ID15:3 Anon
20160729 10.30.05 A OK ID-86.2 Anon.System Volume
20160729 10.30.05 T ExitOK ID-86 System
20160729 10.30.06 A OK ID5:2.1 Car Profile Exit.WiFi
20160729 10.30.06 A OK ID5:2.2 Car Profile Exit.Silent Mode
20160729 10.30.06 A OK ID5:2.3 Car Profile Exit.Media Volume
20160729 10.30.06 A OK ID5:2.4 Car Profile Exit.Notification Volume
20160729 10.30.06 A OK ID5:2.5 Car Profile Exit.com.intangibleobject.securesettings.plugin\n* **\n*!&$*;com.intangibleobject.securesettings.plug in.Activities.TabsActivity
20160729 10.30.13 A OK ID5:2.6 Car Profile Exit.Wait
20160729 10.30.13 A OK ID5:2.7 Car Profile Exit.Ringer Volume
20160729 10.30.13 T ExitOK ID5:2 Car Profile Exit
20160729 10.32.47 A OK ID15:3.1 Anon.Wait
20160729 10.32.47 P Inactive ID24 BT Raise Idle CPU
20160729 10.32.47 A OK ID15:3.2 Anon.Bluetooth
20160729 10.32.47 T ExitOK ID15:3 Anon
20160729 10.32.47 P Inactive ID17 Auto Off Unpaired Bluetooth
20160729 10.32.47 T Running ID26:4 CPU Down Idle
20160729 10.32.47 T Running ID16:5 Anon
20160729 10.32.47 A OK ID26:4.1 CPU Down Idle.CPU
20160729 10.32.47 A OK ID16:5.1 Anon.Bluetooth
20160729 10.32.47 T ExitOK ID16:5 Anon
20160729 10.32.47 A OK ID26:4.2 CPU Down Idle.CPU
20160729 10.32.47 T ExitOK ID26:4 CPU Down Idle
20160729 10.32.48 E Stop ID0:0.0 TaskService

Any ideas or help, XDA?


from xda-developers http://ift.tt/2aoPYFG
via IFTTT

Aucun commentaire:

Enregistrer un commentaire