Related
It seems that with this new build of TomTom 7 smartphones are supported now !!!
The problem with earlier releases was that you couldn't scroll down to select the second, third etc line. This now works. Great news. but...
I installed it on a HTC Tornado (qtek 8310) and it works fine. The problem on the S710 is again the backlight going off after a while. Dit anyone try this new version already and do you have the same problem with the backlight?
I know there was a program called Kahuna TTn6 Focufix.cab to keep the focus on the program. maybe this works? I will try to find this program and see if it helps. Maybe we have to modify the key HKCU\Control Panel\Power\Display again?
I hope some of you can help me find a sollution, so we all can use the newest TomTom version on our Vox !
I found the TTn6 Focufix.cab, but this doesn't work.
I did find a workaround: I set the display time-out when on ac power to never. This works. So when I am in the car the battery is charged and the display stays on.
TomTom 7.915 on Fireburner custom ROM 1.0
I am using TomTom 7.915 since I install the custom ROM from fireburner.
This release works on S710 but with same limitation/problem, but you can select the different icon of the menu without any problem. The navigation can be vertical with the phone close, or horizontal if you have the keyboard open.
These are the Four main problem I have found, and the solution I have use to work around:
1. Backlight going off. When I am using it I plug the phone with the power supply, otherwise battery go away immediately after you arrive at destination or when you are close to it. I solve this problem in the "Settings"+"power Management", and select "never" in "Display time out on AC"
2. Backlight always on after use TomTom. I run an application free that you can download from http://www.tgmaker.com/mobile/
3. Input a destination. The two keyboard of the S710 works, but only with number when present. I means that with the number keyboard TomTom take only the numbers, and with the Qwerty will take the letter if they are alone and the numbers if on the key have both. Same problem was in Opera mini, and you can solve in the menu settings.
Sol. A
I solve this problem saving a contact with the address, and select the destination to contact.
Sol. B
You can browse all the city and the street, you must have a lot of time, or if you know the ZIP code the search became faster.
Sol. C
Fakecursor works but are more the disadvantage that the benefits. When you run it you can use only it, and all the shortcuts with the keyboard doesn't work. I prefer plan the destination and recall them after.
4. Selection: When in the display you have only two possibility there are no problem, but when they are more, the option in the middle are difficult to select. I have find the possibility to select using shift+same key, but I found it very uncomfortable.
Now a challenge to the expert!!
My colleagues use TomTom 7.915 on Experia X1, and you can select all the function using only the keyboard. I have seen also a Touch Pro working very fine with it. The two device have different layout (4 and 5 lines) and the software is working perfectly. I was thinking that most probably TomTom call some driver install on the device for the keyboard layout and allow the software to run properly. My device have a fb custom ROM, and I have a stupid idea which maybe work! If we save the driver of the S710 with the same name of the driver TomTom is looking for the layout keyboard, may be we can use both the keyboard.
I know is a strange idea, but I cannot test since I don't know which driver TomTom is looking for when start up.
Bye
are you sure of number 2? I know that tomtom mobile 5 makes the reg key value HKCU\Control panel\Power\Display if it doesn't exist and set the value to 0 after closing tomtom. I don't think tomtom 7 has the same behaviour. Can you try removing the Display value and see if tomtom 7 creates it again.
number3: I didn't have this experience. I do use another rom. Maybe it has to do with enabling the T9 setting of the keyboard? I can use the number keyboard to make letters and select the right city and street.
number 4: good point. I hope somebody knows this
did some more tests just to be sure:
1. problem is the display goes out after a while. workaround is to set the display timeout in the poweroptions to never when on ac power.
2. tomtom7 doesn't make the value Display after closing, so the ptoblem doesn't exist. (there may be other programs that cause this problem, but it is not related to tomtom7)
3. when using the number-keypad all works fine. when using the full-keyboard there is a problem with the keys also used for numbers (like E R T Y). you get numbers when pressing these keys... I like the idea of whanging the keyboard-layout/driver somehow...
4. I don't really understand what you mean. selecting what?
walram said:
I found the TTn6 Focufix.cab, but this doesn't work.
I did find a workaround: I set the display time-out when on ac power to never. This works. So when I am in the car the battery is charged and the display stays on.
Click to expand...
Click to collapse
TTn6 Focufix is to prevent Tomtom 6 to go back to today screen on smartphones after a while
walram said:
did some more tests just to be sure:
1. problem is the display goes out after a while. workaround is to set the display timeout in the poweroptions to never when on ac power.
2. tomtom7 doesn't make the value Display after closing, so the ptoblem doesn't exist. (there may be other programs that cause this problem, but it is not related to tomtom7)
3. when using the number-keypad all works fine. when using the full-keyboard there is a problem with the keys also used for numbers (like E R T Y). you get numbers when pressing these keys... I like the idea of whanging the keyboard-layout/driver somehow...
4. I don't really understand what you mean. selecting what?
Click to expand...
Click to collapse
Dear walram
I am sorry but I discover that I was running the TTN7.910.9185_vga_black for the Diamond.
I download the new version and I confirm that is working on S710.
1. Ok I have done the same
2. You are right for this point, no need tools for the backlight.
3. Number-keypad all works fine in this version, problem with the qwerty keyboard is still present.
4. In version 9196 the graphic is totally different, in not just a matter of resolution and I believe was developed for specific device. If you press center key pad 6+5 you can see the version of Tomtom , and you have 3 possibility
- copyrigth
- account
- done
I am not able to select Account.
During the installation I was not able to select the correct com port, since look like the cursor was not enable to move, or this version was designed for COM9. I copy the *.exe and *.chk file on the old installation and is fine.
I believe that this version take out from the lolite is the most suitable for the s710. Then finally for who love TomTom, at least they should try it, since interface is almost the same of 5.2 for SP and the overall function looks ok.
If I found bugs or problem I will post later in this section.
Bye
i see what you mean with point 4. I don;t know a sollution for that, but i think you don't really need it for daily use. i could select the right com-port (com 6). installed it on 5 devices already, no problem.
the only bug i found so far is when starting the demo for a route the buttons are switched. so the "ok" and "cancel" are switched. just that you know...
it would be nice if somebody can fix the full-keyboard layout problem... it seems a problem with the s710?
it would also be nice if somebody can write a simple program that creates the registry key to keep the display on when the program is running, and delete the key when tomtom is closed. anybody?
i could select the right com-port (com 6). installed it on 5 devices already, no problem.
Click to expand...
Click to collapse
I'm NOT a big fan of TOM TOM but I've tried for the first time to figure out this problem and so far I totally agree with Dom_LC
COM selection is locked IMHO. I've tried to edit navigator.cfg to use COM7.... DONE...but it was useless
then I tried to add COM9 to my Bluetooth outgoing ports...it was selectable but obviously the system was unable to create the port.
I tried also to mix data file with the exe to see wath's what ...useless.
Tried fakecursor and eCursor...they worked everywhere but in the COM selction MEnu.
well, that's kind a strange isn't it? can you use the up and down-button when selecting a city and when selecting a road? are you using version 7.915 and not 7.910?
Sure! and I'l tell you something more interesting also when composing the destination I can't scroll from the vorious suggestions that are indexed along when you are typing (the only that is always selected is the first in the list as for the COM ports)...so the only way is to write the exact name
interesting. so maybe there are more versions of the 7.915 around? something to do with the rom?
anyway i can scroll from the vorious suggestions everywhere. Maybe i should send you my version and see what it does on your vox.
I had the following files:
ttn7.915.9196.qvga_black.cab
ttn7.915.9196.qvga_blue.cab
ttn7.915.9196.vga_black.cab
i installed the middle one.
a did find a bug, so it seems. How do you select a differect country when typing a city? On a PDA you can select the country on the right side of the screen. but how does it work on a smartphone? eg. I am from the netherlands and the only city's i can select are from the netherlands. In earlier versions of tomtom all city's of europe were in the same list. can anyone confirm this bug?
Yep Walram, this bug is on my StarTrek too, TT started in Belgium for me and i had no clue how to change the country to Netherlands, so i navigated to one of my dutch contacts and that did the trick, so, maybe a bit odd, but you could add a fake contact in the country of your choice to end up over there.
Nevertheless....this is an inconvenient bug since it doesn't allow you to travel or plan through whole of Europe
i wonder if the selection of country is in the map or in the application. eg. if we install an old map (version 7 or 6) do you get 1 list with all city's of europe?
so tomtom has some work to do again to fix this bug.
if you remove the mapsettings.cfg in the map-directory before starting tomtom you get the question once to wich country you want to navigate
so, a little, workaround. you also loose your home adres and favoutites i guess...
but it works... just that you know
well, that's kind a strange isn't it? can you use the up and down-button when selecting a city and when selecting a road? are you using version 7.915 and not 7.910?
Click to expand...
Click to collapse
I tried blue and black version. I think it was black wich did not let me select something with the up and down keys. So try both versions.
By the way installation failed every time on my Vox (Rose v.0.4)
So I extracted the files with win ce extractor, putted them on the root of the SD card and all went well.
Ierlanfdan said:
I tried blue and black version. I think it was black wich did not let me select something with the up and down keys. So try both versions.
Click to expand...
Click to collapse
I Can Confirm that! Smartphone users can take advantages ONLY from the blue one! And this ends my adventure with tom tom.
help
i have a vox with original ROM (mobile 6) and i can't install the tomtom... it start the cab and suddenly stops and go back to home screen...
does anyone can help me... I've tried the qvga version black and the ttn7.915.9196.qvga_blue_cuckoo.cab. both do the same thing.... they start and suddendly stop...
the install bar doesn´t move, and the waiting color circle disappears and go back to home screen...
can you put here the link to the version you have for me to try??
thank you and sorry for my bad english....
It's for PPC, you can't instaqll on a Smartphone, so you have to use this method
http://forum.xda-developers.com/showpost.php?p=3224919&postcount=776
TheBo said:
It's for PPC, you can't instaqll on a Smartphone, so you have to use this method
http://forum.xda-developers.com/showpost.php?p=3224919&postcount=776
Click to expand...
Click to collapse
i try it but i can't copy the shortcut.... said i can't do it... any alternative method to copy it...
thank you...
The newest version of TomTom Navigator supports non touch screen devices.
I stumbled in this information by accident and thought it would be usefull over here.
I've tested it on a HTC StarTrek (qtek 8500 etc) with a WM 6.1 standard ROM and it works like a charm with the newest maps.
No more FakeCursor needed, you can scroll and use numeric keypad
Version is: 7.915.9196.
Because of slightly warez related.....google is our best friend.
How I combined 7.450 and 7.915 to get it working on my SAMSUNG JACK i637
Hey guys, I bought a Samsung JACK (637) a couple of months ago and really wanted to install a GPS software to use with my Bluetooth GPS receiver. So I spent a lot of time searching and researching my options. Since I used to use TomTom on my iPaq 2495, I decided to go with that.
I found that I had to spend MORE time on figuring out the RIGHT version of Tomtom Navigator and the combined MAP than I anticipated.
TO CUT TO THE CHASE, after experimenting a few version (6.xxxx, 7.450.xxxx, 7.910.xxxx, and 7.915.xxxx) I realized that the 7.450.9028 version works best but NOT without the following FLAWS:
7.915.9196 - Scrolling works for the menu items but NOT for useful features such as searching for address, and POIs, and even setting up the COM PORT for the GPS.
TO SOLVE THIS PROBLEM, I combined two versions: the 7.450 and 7.915. Here's HOW:
The problem with 7.450.9028, at least for me, was that:
Searching for POI using the 'ANY CATEGORY' option yields 'NO POI FOUND' all the time.
It couldn't search through the POI database using KEYWORDS. The version of map I tried is 720 and it sure isn't the problem.
So, I made my OWN version:
1) Install 7.450.9028 on your PDA/SMARTPHONE
2) Copy the Navigator directory from /Program Files/ on your device to your Hard Drive.
3) Remove TOMTOM from your device.
4) Install 7.915.9196 on your device.
5) Replace all files except "TomTom Navigator.exe" in Navigator directory of the new installation with those in the Navigator directory indicated in step 2).
6) DONE
I now have a version of Tomtom with the 7.915 main program file and the 7.450 system files.
Now I can search POIs by keyword AND scroll with my UP and DOWN buttons.
These are instructions I think might be useful for at least some people. But I leave you to buy your own copies of the program and MAP so don't ask me for them.
I haven't tested with the more recent 840.2563 maps but I foresee for this to work with it, too.
That's interesting - also stumbled over the sudden "smartphone mode" in the latest version when playing with KS20 and my old Vox back and forth. I noticed though, that the menus in the "smartphone mode" are different from the normal "touchscreen mode".
Especially:
- no (direct) option to delete a route (plan a new route and abort when it starts to calculate immediately instead)
- useless menu to "manage phones"
It looks as if TT is in some mode intended for onboard car device.
What happens if you use the "manage Phones" menu (2.4)?
Your merged TT Versions should relate to the data.chk file (the other big file aside the TT.exe) - so maybe there is easier way to get it replaced. Merging data.chk and TomTom...exe with different versions did not work for me though, but you brought back the attention that it actually works as well (with minor quirks).
Just re-checked if everything works allright with scrolling on the VOX and Tornado - and it does (my Tornado is on WM6 cooked ROM, so not WM5) and the VOX is with Stock ROM 6.0 - so no problems with scrolling here.
The 7.915 had other side-effects, if I remember right like disconnecting BT-GPS in background, so you can't use it as "voice only". Will have to actually use it in real life to see if it works as reliable as the TT5.2 does (depite the maps are getting really outdated...)
tobbbie said:
That's interesting - also stumbled over the sudden "smartphone mode" in the latest version when playing with KS20 and my old Vox back and forth. I noticed though, that the menus in the "smartphone mode" are different from the normal "touchscreen mode".
Especially:
- no (direct) option to delete a route (plan a new route and abort when it starts to calculate immediately instead)
- useless menu to "manage phones"
It looks as if TT is in some mode intended for onboard car device.
What happens if you use the "manage Phones" menu (2.4)?
Your merged TT Versions should relate to the data.chk file (the other big file aside the TT.exe) - so maybe there is easier way to get it replaced. Merging data.chk and TomTom...exe with different versions did not work for me though, but you brought back the attention that it actually works as well (with minor quirks).
Just re-checked if everything works allright with scrolling on the VOX and Tornado - and it does (my Tornado is on WM6 cooked ROM, so not WM5) and the VOX is with Stock ROM 6.0 - so no problems with scrolling here.
The 7.915 had other side-effects, if I remember right like disconnecting BT-GPS in background, so you can't use it as "voice only". Will have to actually use it in real life to see if it works as reliable as the TT5.2 does (depite the maps are getting really outdated...)
Click to expand...
Click to collapse
I'm strictly using the PPC version of TT so there is no such option as “smartphone mode".
The hybrid 7.915 is pretty stable right now except for the "Start-up Preferences" that would always lead to a crash with "Not enough memory" error.
I also found that if you selected your STATE when inputting your HOME LOCATION during initial setup, TT will remain locked to that state (i.e.: only addresses in your specified state will be indexed during searches). The solution I applied was to simply do a "RESET FACTORY SETTINGS" (under Preferences) and select USA when selecting a HOME LOCATION.
It's frustrating to see that TT has yet to come out with a version that is compatible with all smart phones. I guess we shouldn't put all the blame on TT when manufacturers constantly come out with new ways to confuse us with unique button mapping schemes.
I didn't have problems with bluetooth. I think you're talking about automatic disconnections caused by the time-out setting in the phone. On my Samsung JACK, I basically set my phone to never dim the screen nor go back to home screen unless I manually LOCK the keypad. I can even use my BT headset and BT GPS receiver simultaneously connected to the phone. Now, the only time my GPS disconnects is when i get an incoming call. An inconvenience to say the most and hardly an annoyance. The only annoyance is that the battery would be drained if I forget to lock the keypad or if I leave an unanswered call log unattended (screen always on).
CHEERS!
What I mean is that the menus that the very same program (installed on just ONE microSD card) shows are different when I start it on my smartphones (HTC Vox/S710 or HTC Tornado) or on my PocketPC (LG KS20). You may not have noticed this as you are using it on a non-touchscreen device (aka "Smartphone") only.
I cannot do a side-by-side compare easily as the card can only be in either one or the other device...
A sure proof for this is that there is a menu "manage phones" (translated from my German version) on the second page of the main menu. On the PocketPC this is not present.
Also the item "delete route" (PPC on the 3.rd page) is not there when I start it on the smartphone.
Last, the smartphone menus show a digit (1,2,3,5,6) aside a list-like menu item while on the PPC this is a 2x3 icon layout and no digits shown.
Dropping the BT connection if sent to background does not happen on my PPC as well, but this is using a different BT-stack (Widcomm/Broadcom) while my smartphones use the Microsoft BT-stack.
Can you please tell about the menu specialties that I desribed - do you see these as well?
tobbbie said:
What I mean is that the menus that the very same program (installed on just ONE microSD card) shows are different when I start it on my smartphones (HTC Vox/S710 or HTC Tornado) or on my PocketPC (LG KS20). You may not have noticed this as you are using it on a non-touchscreen device (aka "Smartphone") only.
I cannot do a side-by-side compare easily as the card can only be in either one or the other device...
A sure proof for this is that there is a menu "manage phones" (translated from my German version) on the second page of the main menu. On the PocketPC this is not present.
Also the item "delete route" (PPC on the 3.rd page) is not there when I start it on the smartphone.
Last, the smartphone menus show a digit (1,2,3,5,6) aside a list-like menu item while on the PPC this is a 2x3 icon layout and no digits shown.
Dropping the BT connection if sent to background does not happen on my PPC as well, but this is using a different BT-stack (Widcomm/Broadcom) while my smartphones use the Microsoft BT-stack.
Can you please tell about the menu specialties that I desribed - do you see these as well?
Click to expand...
Click to collapse
Are you saying that two different interfaces are supported by the same TT version?
Yep, the menu items are numbered exactly like you said.
On Main Menu - page 3, 'Delete Route' option is absent.
Also, I actually never noticed that there is in fact a Manage Phones option on Page 2 of 3. I'm not sure what this option does on my phone because all it does is bring a screen asking "Do you want to connect to "?".
I did use TT Navigator v6 on my HP iPaq hx2495 before. The installation was for touch-screen PPC but I really can't remember all the details. I could go back and have a look, though and even try to run my "hybrid" version on it through an SD adapter.
By the way, I have a 4hz Bluetooth GPS but my TT MAP is being updated at 1HZ. Is there any way to change this setting in TT? 7.450.XXXX used to update the map at 4hz. Perhaps it's not supported by 7.915.xxxx?
hi all i cant seem to get a signal on my hd2, with any headphones plugged into the socket so i was wondering if id have better look with another app, or wont it make a difference,
ps. at home (Nottingham, uk) i get a minimal signal and at work in large building i struggle to even get a remote signal at all
i have the same prob on mine, uk also.
The same.
Best thing to do is to report the problem to HTC support, so we can get a hotfix.
I also have the same problem - awful FM reception
Here is the link for HTC UK Customer Support - I suggest we all mail them with the problem.
http://www.htc.com/uk/CS_Mail.aspx
Hi guys,
I am experiencing the same problem but the thing is that I am in Germany not UK and I get just 2 radio stations!
Could not get any radio stations with the supplied headphones plugged in.
Tried using my big headphones with a 3m lead.
Picked up all stations crystal clear. All well and good, but hardly practical to carry them round with me when out and about
+1
I'm in Luxemburg. 2 stations with HTC HD2 / 12 stations with old Samsung OMNIA
same problem here in italy...
no problem here in Austria ... radio reception is very good, I get all local stations
everything's fine here !
all stations receive !
French country !
All station work ok where I am in the UK if I tune them manually using in ear headphones but doing the auto scan and save it detects nothing
no stations in norway
i get all the stations here in norway. maybe u should try new headphones.
no radio stations in the netherlands. i mean with the HTC HD2 of corse !!!!
radio suffering
Radio sometimes locks the device in turkey
no radio stations in sweden
+1 (Croatia)
mine seems to just keep loading and loading and loading.. never has frosen yet though.. also in norway.,.
Hello
after several posts with Customer Support of HTC and with full and yes full explaining exactly this problem with auto scan, I get this answer
=============================
Thank you for contacting HTC ,
Dear Mr. *****,
Regarding the issue you're facing with the handset, kindly follow the instructions below:
Kindly confirm that you have followed the instructions below to save the channels:
To save FM stations as presets
1. Tune in to the desired FM frequency, and then tap Presets.
2. On the Presets list, tap that appears on the desired preset number where you want to save the FM station.
Tip Tap to remove a favorite FM station from the list.
3. When done, tap OK.
To listen to a preset FM station
On the FM Radio screen, tap the station preset button. If the station preset button is not on the screen, tap Presets, scroll through the list of preset stations, and then tap the station you want to listen to.
If you've followed the steps above and still the issue persists, please perform the troubleshooting below:
1) Kindly Check if the device has enough Free Memory to run (at least 5MB)
Please go to : Start> Settings> Menu> All settings>System> Memory,
If there is less than 5 MB free in each category, you need to free up some memory by removing files from the device or by shutting down programs that are not actively in use.
To Free up the program memory
Please go to : Start> Settings> Menu> All settings>System > Task manager> Stop All.
Free up the Storage memory
Please go to : Start> Setting> Menu> All settings>System tab> Managed Programs. Remove programs.
Once memory has been freed up, kindly re-test.
2) Please check if this issue has occurred after using any 3rd party applications. If yes, please remove the 3rd party software and retest the device.
3) Kindly perform a Soft reset to the handset by removing the back cover and pressing the reset button.
Incase any of the troubleshooting above doesn’t solve the issues you’re facing with your device kindly perform the following:
Please backup all data on the device by synchronizing to a computer, My phone application, or using a data backup program using a memory card, afterwards, perform the Cold-boot (Hard-Reset) and retest the device.
To perform a Hard Reset:
3. Start>Settings>Security>Factory data reset
4. Press 1234 and press yes
Caution: this process will erase all the information from the phone memory
=========================
and that is the solution, don't use auto scan because there is no auto scan with some devices
any suggestion
FM radio...
In Switzerland, everything's fine.
But I'm searching for another FM radio tuner (free of course) to replace the poor native that comes with HD2. Before I was using Power Radio on Blackstone but with Leo it doesn't work.
Does anyone know a good FM Radio (not Internet) for my little (I mean giant !) Leo ?
-----------
thanks and sorry for posting here
This mod is not developed / maintained anymore.
The mod is based on an (now) old version of the Pioneer AppRadio app that does not support the latest Android versions and head units.
If it works then it works but if not then you are on your own. There is no support. Also the ARUnchained GPS Injector app is not developed anymore.
To use AppRadio Unchained please get the paid version from the Play store called ''AppRadio Unchained Reloaded".
For details see here: AppRadio Unchained Reloaded
If you don't want to root your phone and have Android 7 or higher there's AppRadio Unchained Rootless
Old information:
=================================================================================================
The Pioneer AppRadio is a radio with a 7" touch screen. Android devices can be connected via HDMI and shown on the screen.
Touches and keypresses are sent back to the Android device via Bluetooth. The radio has a GPS receiver and data is sent
over Bluetooth as well. In essence a very nice concept.
To connect to an AppRadio there's a Pioneer AppRadio app available in the Play store. The Pioneer AppRadio app
is however quite restrictive. It allows only to run a small number of apps that are approved by Pioneer. These approved
apps can interact with the AppRadio app because they have a built in Pioneer SDK. The number of useful apps is small.
For details look here: Pioneer Appradio Knows website.
The goal of this project is to modify the Pioneer AppRadio app in such a way that it allows full mirroring.
This means that any app can be used and controlled using the touch screen and keys on the headunit.
Also any application can receive GPS data from the AppRadio.
Setup guides by RogerH
Pioneer AppRadio with Nexus 5
Setting up Pioneer AppRadio with Android Stick
Links
CNET article that gives a nice overview
Video from Steven Solazzo
Video from SinisterC6
Video from Neil Fontamillas
Video from M Sylvester showing AVH-4000NEX working
Video from M Sylvester showing AVH-8000NEX working
Video from M Sylvester showing Samsung Note 3 hardware setup
Video from Pascal H showing ARU in action in a Porsche 997 Turbo (in French)
Current status of the AppRadio Unchained Mod (free)
Beta release 6 is available for testing.
You can download it from here: arunchained0.16.apk
For Android HDMI sticks there's a special version available.
You can download it from here: arunchained0.15stick.apk
Current status of AppRadio Unchained Reloaded (has built in GPS Injector) (paid)
In addition to the AppRadio Unchained mod of the Pioneer AppRadio app, a completely Pioneer-less app was developed.
Basically it allows you to connect to your AppRadio in a faster and easier way without the need to use Tasker.
For details see here: AppRadio Unchained Reloaded
Current status of the ARUnchained GPS Injector (to be used with the AppRadio Unchained Mod) (paid)
GPS injection on system level using mock locations is available in the playstore here: ARUnchained GPS Injector
For GPS Injector details go to the FAQ here: ARU FAQ
Please fill out the survey here: ARUnchained GPS Injector survey
Navigation apps that already have AppRadio support like Waze and Navfree still work using the HU GPS. If you only use those apps then you don't need ARUnchained GPS Injector.
Head unit models that have built in navigation like AVIC-Z150BH, AVIC-F50BT and similar are not supported as Pioneer does not support sending of GPS data to the android device. If you are unsure, a test that can be done is to install Waze, if Waze can use the GPS of the head unit, ARUnchained GPS Injector works as well.
Release notes beta release 6
Rotation locker only active when HDMI connected.
ARU menu also available when not connected from Settings / Help menu.
Rotation locker and Start GPS Injector are now separate options.
Release notes beta release 5
Right part of the screen not reachable on Nexus 5 issue fixed.
Touch made more accurate for all phones.
Release notes beta release 4
Start / stop GPS Injector service when bt connected / disconnected.
SWC extended with ff & rw (to be tested by M.a.s.e-> doesn't work)
Play/Pause of HU quick menu bar now working.
Release notes pre-beta release 3
Steering wheel controls are working now.
For details go here: ARU FAQ
Release notes pre-beta release 2
Multitouch implemented.
Hardware keyboard issue fixed.
Options menu available.
Rotation locker.
Invert XY-coordinates. -> Does not work 100% yet.
Release notes pre-beta release 1
Radio buttons are working now.
Alternate method for setting uinput access rights fixed.
Release notes pre-beta release 0
Root access is required so your phone must be rooted.
For now it only allows using the touch screen.
Only single touch is supported.
Keys from the radio don't work yet.
GPS from the radio doesn't work yet.
Steering wheel controls don't work yet.
Users have reported it working on AppRadio 2, AppRadio 3, AVIC-F950, AVH-X8500BHS and AVH-X8550BT.
Disclaimer: Use at your own risk. Basically if it damages anything (you / your phone / your radio / your car or whatever),
don't blame me.
Donating
If you like my work and want to donate something, click on the "DONATE TO ME" button. However the first page will show in Dutch ( I guess because I am registered there).
Two solutions:
1) In another browser window logon to Paypal first. Then press the "DONATE TO ME" button here.
2) At "Donatiebedrag" enter the amount in US$ you want to donate, at "LOG IN OP PAYPAL" enter your logon details. After logon the language will change to your local language.
FAQ
For FAQ go here: ARU FAQ
Common issues and solutions
For an overview of common issues go here: Common issues and solutions compiled by stewbuntu
For help on what hardware to use you can also go here: Appradio forums It's basically the ARLiberator forum but has information about how to setup your hardware too.
Compatibility list
This app is compatible with any AppRadio that is supported by the original AppRadio app.
Details of supported Android devices:
Please fill out the survey here: ARUnchained survey
You can also report the issues that you have.
See attached ARUnchainedSurvey03.zip file for results of the survey. It's a zipped pdf file (had to zip it because of pdf size limitation on XDA). It gives a good overview of what phones/radios are working with ARU.
Old releases
Beta release 5 is still available in case 6 doesn't make you happy: arunchained0.15.apk
Beta release 4 is still available in case 5 doesn't make you happy: arunchained0.14.apk
Pre-beta release 3 is still available in case 4 doesn't make you happy: arunchained0.13.apk
Nice work! I can't wait to get home and test it out.
In the other thread I saw that someone had a S4 working with the AR3 using your app, so you have me really tempted to upgrade from the AR2 If you get GPS working on the AR3 you can definitely count on a donation from me.
FAQ
ARUnchained GPS Injector
The ARUnchained GPS Injector app has two parts inside. One is the GPS service and one is the UI activity.
The service is the part that injects the GPS data into mock locations. ARU 0.14 and up will start this service automatically when a bluetooth connection is made to the HU (at the same moment that the rotation locker is started). The GPS service is stopped when bluetooth is disconnected.
The UI activity is started when you start the ARUnchained GPS Injector app from the launcher. It shows the status of the GPS service and also the actual GPS data. The purpose is to be able to check whether the service is working properly. With the start / stop buttons the GPS service can manually be started / stopped.
For the GPS service to work Mock locations has to be enabled. To use the phone built in GPS, Mock locations has to be disabled. It can become tedious to set this manually so ARUnchained GPS Injector has an auto on/off Mock locations feature. In order for this to work ARUnchained GPS Injector has to be converted into a system app.
This involves moving "mars.area51.arunchainedgps.apk" from "/data/app" to "/system/app". This can be done with root explorer for instance. Set permission to rw-r--r-- and reboot your phone. On Android 4.4 (KitKat) you should move the apk to "/system/priv-app" folder instead.
For pre-KitKat Android versions converting to system app can be done using Titanium backup:
Open Titanium Backup
Search for ARUnchained GPS Injector
Long press and choose convert to system app
Reboot phone.
Converting to system app using free ES File Explorer
1. Make sure in ES File Explorer, Root Explorer is enabled and Mount R/W is on RW
2. Copy pkg.apk in /mnt/asec/mars.area51.arunchainedgps-1 to SDCard and rename it 'mars.area51.arunchainedgps-1.apk'
3. Install 'mars.area51.arunchainedgps-1.apk' from SDCard
4. Move 'mars.area51.arunchainedgps-1.apk' from 'data/app' to /system/app or /system/priv-app on 4.4.x
5. In /system/app or /system/priv-app select 'mars.area51.arunchainedgps-1.apk' and in menu select Install.
6. After install reboot
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARU and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
On my Samsung phone not the whole screen is shown but a part is cut off
A) The default Samsung launcher doesn't handle landscape well. The solution is to install an alternative like Nova launcher.
On my Samsung phone touch stops working after calibration
A) Verify your phone is rooted properly.
B) On Android version 4.3 and higher Samsung has Knox security and SELinux is in enforcing mode.
This somehow prohibits accessing the /dev/uinput device which is required to be able to input touch/key events on system level.
In order for ARU to work Knox has to be disbled and SELinux has to be in permissive mode.
Possible fix 1:
First install an app called Android Terminal Emulator then open a terminal and type
the following lines pressing enter after each line:
su
pm disable com.sec.knox.seandroid
Now wait a bit till knox is killed and finally type:
setenforce 0
If this works, you have to do it every time you reboot your phone. It can be automated with Tasker for instance
Possible Fix 2:
Install the Xposed framework and the Wanam module.
At Security hacks tick " Disable Knox notifications" and "Disable SEandroid".
Reboot.
Possible Fix 3:
If the other fixes don't work and your bootloader isn't locked you can try to install a custom kernel that has Knox disabled and SELinux in permissive mode by default.
Keyboard use
It's not necessary to install Car Keyboard. Only the original Pioneer AppRadio app needs that.
Note that the virtual keyboard created by ARU is sometimes incorrectly detected as a hardware keyboard.
This prevents the software keyboard to be shown and makes it impossible to enter anything.
To check / set the keyboard settings:
Click the menu button on ARU.
At the right bottom click on "Change input method"
A pop-up is shown that CarKeyBoard has to be installed. Ignore it by clicking OK.
The dialog for selecting the input method is shown.
Make sure hardware keyboard is switched off.
Use of the hardware buttons:
The home, menu and back button now work as advertised.
To go back to the native interface you have to open the AppRadio app manually and then press the home button.
To go to the AppRadio app easily, swipe down the status bar and click the AppRadio notification.
Fast option to go back to the native interface: Double click the home button, touch the blue bar in the middle with 4 squares on the left.
Release notes pre-beta release 2
Multitouch implemented.
Multitouch works now. AppRadio 3 has a bug which makes it a bit unpredictable.
Hardware keyboard issue fixed.
Sometimes the virtual keyboard created by ARU was incorrectly detected as a
hardware keyboard preventing the software keyboard to be shown. Fixed now.
Options menu available.
The options menu can be reached from the app's main screen. There's now an additional ARU
option sub menu available with two options:
Rotation locker.
Invert XY coordinates.
When in AppRadio Mode homescreen, select menu button, select ARU, there you will see the ARU feature options...only accessible when connected to HU at this time.
Options can be set but will only become active after force stopping the app and then restarting it.
Go to Settings->Apps->AppRadio Unchained and do a Force stop. After that just start ARU again
and the options will take effect.
Rotation locker.
Forces rotation to be in landscape when enabled.
Locker becomes active when a bluetooth connection is established with the radio.
Locker is deactivated when bluetooth is disconnected.
Invert XY-coordinates.
Necessary for some tablets and HDMI sticks.
Currently this options doesn't work well. Somehow it will switch mode during calibration, giving
incorrect calibration results. After that touches are at the wrong position meaning app is useless.
Will look into it soon.
Release notes pre-beta release 3
Steering wheel controls
Steering wheel controls are working now.
Currently supported are: previous track and next track.
There might be more but I couldn't get it out of my radio.
Of course there's volume, mute etc. but that is handled directly by the radio
and never sent to the phone.
In case there are commands sent by the radio to the phone besides the ones already implemented the logcat will contain this:
Don't know how to translate RemoteCtrlInfo = <number>. Let me know the number and what remote control command you were
issuing and I can add it.
Hell yeah man! Thank you! will test soon on my AR3. If you have that bitcoin address set up I'll send you like $20 worth of btc for this mod.
great... waiting so long for getting AR3 support...
will test it today and donate as well...
Gesendet von meinem Nexus 7 mit Tapatalk 4
Original Hack Bounty Crew:
--------------------------------------------------------------------------------------------
$200 lpasq (xda) Confirmation number: 7D019513V95549722
$100 drawblood (appradioforum & xda) Donation made per post on AppradioForum
$50 ofarrell.g1 (xda)
$50 evillela2001 (xda) Confirmation number: 3NF91232VR227492L
$50 Meldoon (xda)
$25 rs2k (xda) Confirmation number: 8R358541KC016842T
$25 jj69chev (xda)
$25 leobg (xda) Confirmation number: 8TE693651C300254U
$25 tnuts22 (xda) Paid
--------------------------------------------------------------------------------------------
$550 Committed - U.S. Dollars
($425) Confirmed Donated
==============================================
$125 Due
hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597
Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.
Your phone has to be rooted for this app to work
tmp_do said:
hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597
Click to expand...
Click to collapse
I think it may be due to code obfuscation stripping a bit too much code. Thanks for the report.
Droid Bionic
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.
gbual said:
Your phone has to be rooted for this app to work
Click to expand...
Click to collapse
It is rooted.
jdbaldi said:
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.
Click to expand...
Click to collapse
Don't pay me too early, the app is not even finished. I might take the money and run......
J/k, I will finish everything.
And I have to add, thanks a lot for the donation!
Area51© said:
Compatability list
To be done.
Click to expand...
Click to collapse
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
enjoimadcow said:
Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.
Click to expand...
Click to collapse
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.
Area51© said:
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.
Click to expand...
Click to collapse
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Phone side is same as I get. AppRadio side I can't compare I have an AR2.
On the phone side I only get that Bluetooth icon with the 6 dots. I think the other is because you have Bluetooth streaming.
lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
Thanks.
This link got me into the design mode somehow. Do you have to give everybody access before they can enter data?
Maybe a field to state working or not working and if not, why not would be nice.
Will look at it later, my gf wants me to watch the last episode of Dexter now.
lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
I tried it again but now I got a message that the file is in the owners bin. When I clicked the link, I entered into design mode or something. I had to click "View live form" to enter data. But it seems someone else entered data in design mode and replaced all the titles with the answers he wanted to give. Do you have a copy? Maybe need another link to go to the View live form mode right away.
enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Have you paired the radio to the phone under Bluetooth settings? Also - check if phone is "selected' on the connection tab on the radio itself (I recommend auto connection to be set to ON)
The Problem: On many non-Samsung phones, all calls, even when answered on the phone itself, get sent to the watch's speakerphone, requiring the user to manually switch the sound back to the handset every time a phone call happens. As a side problem, the watch conflicts with other Bluetooth devices capable of of being used for calls, like car stereos and headsets. Several threads on xda and elsewhere discuss these issues; however, the only solution posted is to disable the "Phone Audio" profile of the watch in settings. This is sub-optimal because it completely disables the ability to use the watch as a phone speaker.
The Solution: I have put together a series of Tasker profiles and tasks that utilize the BlueTask plugin to control the connection of the Gear S3. A convenient detail about BlueTask's disconnection method is that it only seems to affect the "Phone Audio" component of the Gear S3, leaving all other functionality untouched during a call. I use the proximity sensor to determine whether or not the call is being made/answered on the phone itself vs the watch. The assumption is that if you leave you phone in your pocket, bag, or face down on the desk, then you answered the call via the watch. I understand this is not a perfect method for determining which device is answering the call, but it works pretty well in my testing. In addition, an exception is made for when a wired headset is hooked up to the phone, as one may leave their phone in their pocket while answering using such a headset. Finally, an additional profile I call the "Car profile" will automatically disconnect the watch and disable its Tasker profiles while connected to specified Bluetooth devices like a car stereo, Bluetooth headsets, etc.
Setup:
Re-enable "Phone Audio" for Gear S3 if you previously disabled it (Settings>Bluetooth>Gear S3)
Install Tasker (if you haven't already)
Install BlueTask
Go to Tasker>Preferences>UI>Beginner Mode. Disable it (if it is not disabled already).
Go to Tasker>Preferences>Monitor>Display Off Monitoring>Proximity Sensor. Set it to "Yes"
Download the Tasker project attached to this post to your phone
Import the project into Tasker (Press and hold the home tab in the bottom left corner of tasker and then click Import)
Enter the new "Bluetooth" project and open "Car Profile" in "Profiles"
Delete the Dummy MAC address in the Profile and replace it with the MAC addresses of any car stereos and/or bluetooth headsets you use with your phone. If you have multiple of such devices, separate each address with a "/" (the magnifier glass icon does this for you). If you have no such devices, feel free to disable or delete this profile.
Open "Disconnect Gear S3" in "Tasks"
Open the "BT Connection" action
Replace the dummy information with your Gear S3's Name and MAC address
Repeat steps 10, 11, and 12 for the "Connect Gear S3", "Car Mode", and "Exit Car Mode" tasks.
Complete!
Let me know if this works for you. Also, suggestions for how this project could be improved are welcome.
Its works fine on #LGV20 so no need for this fix.
Sent from my LG-H990 using Tapatalk
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
OneRealDaniel said:
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
Click to expand...
Click to collapse
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Beginner mode
MehStrongBadMeh said:
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Click to expand...
Click to collapse
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
OneRealDaniel said:
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
Click to expand...
Click to collapse
Thanks for letting me know about that, I'll add that to the steps.
Hi i downloaded the App but seems it doesnt work for me. I set it up according your instructions but still no change. But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic? That once someone picks up a call that it select this option right after.
Added 2 screenshots one from the Standard run and one of the option to select an audio divice when making a call.
Thx for any help.
Edit: Works Now thx alot i had an incorrect name set for the device... i will test it if it works always but so far so good. thx alot
Jafabibe said:
But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic?
Click to expand...
Click to collapse
I wanted to use this system as part of the automation workflow. The problem is that, when dialing someone, it switches the audio output when they pickup, instead of during Phone Offhook (the moment you hit dial). As a result, I can't detect the actual moment the audio device is switched, so I disable the watch audio entirely to prevent it from from happening.
Hello guys. I have non rooted stock nexus 5x. I have followed steps from first post but I always get error (attached).
Please any ideas what's going on?
Edit: Sorry guys. Please ignore it. I have added wifi mac for gear instead of bluetooth mac. I'm going to test it.
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
GabrielAK89 said:
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
Click to expand...
Click to collapse
Probably install Bluetask as per the instructions.
I solved the problem using Macrodroid.
GabrielAK89 said:
I solved the problem using Macrodroid.
Click to expand...
Click to collapse
Can you tell us, the other users, what you did to get it solved ?
As we are in a forum, others can benefit using your solution.
So please share.
I just got my Nokia 8 Sirocco, and I thought it was bad BT performance on my new device, when it probably is my Gear screwing me over. Thank you for this Tasker-project, I've just finished setting it up, and l am looking forward to seeing is effect!
Unfortunately, the macrodroid way don't work anymore for me.
Don't know why.
I am retrying the Tasker way. I get the error:
12.53.42/E FIRE PLUGIN: Connection / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
12.53.42/E Connection: plugin comp: com.balda.bluetask/com.balda.bluetask.receivers.FireReceiver
12.53.42/E add wait type Plugin1 time 60
12.53.42/E add wait type Plugin1 done
12.53.42/E add wait task
12.53.42/E Error: 2
Does anyone know what it means?
LE: When i am in the car i don't get this error. Everything seems to be with green dot. But the magic never happen. The tusker is not triggered. Should i make other settings to work?
I also tryed Bluetooth auto connect. Bad luck with that also.
Hi!
I've been meddling with Tasker for the past few days and discovered that choosing the Headset profile to connect to and disconnect from the Gear S3 works better for me.
I've started out with MehStrongBadMeh's guide and tasker xml file (many thanks by the way!), but found out my phone was unable to connect the Gear S3. It disconnected OK to connect the car bluetooth, but would not reconnect Gear S3. Running the task also gave errors as reported by few others on this thread.
But everything seems to be in order when Headset profile is selected for Gear S3. Will test out extensively and will report back if I need to change anything else.
I believe I created that xml was created before bluetask handled specific profiles, hence the need to explicitly set headset now. I don't actually use this profile anymore, as calls started being routed properly when I updated my HTC 10 to Oreo (and continue to be routed properly on my OnePlus 6).
Just wanted to say a massive thank you for this. I have just bought the Galaxy Watch and have a Samsung S6 Edge with lineageos. I was having the issue where everything was being rooted through the watch. Your guide has got this working as it was designed.
My notes would be for anyone trying this - do not change the device name as it doesn't seem to work (i am guessing this is referenced in other profiles) - just change the mac address to your watches Bluetooth mac address.
Any update on this I still get an Error 2 and it never seems to connect on its own to my car audio
Solved with MacroDroid:
Trigger: Call active (any contact)
Action: Kill application Galaxy Wearable
Constraints: Trigger fired Call active
AND In call
App Alive BG Galaxy Wearable