yashsingh1/xdaforums huggingface dataset:
[Connected Car] andreasy:
Got the answer already. Same as the previous: "only Suzuki can provide a solution to this. We only provide the main hardware". As I expected but I had to try.
[Connected Car] mauriciomatos:
Thanks anyway, it was worth a try.
[Connected Car] 7virage7:
I guess the HU informs about it during update in upper right corner. Mine said that system: U2003. System in YT video of 850 to 1840 upgrade was U0320. Indian videos show like U0420. Probably this can be a information about different HW implementations.

Does anyone with working Android Auto have system: U2003?
[Connected Car] Muxeu:
Have sent email to my contact from Bosch too.

But I guess will receive the same answer
[Connected Car] mauriciomatos:
Yeah....I didn't pay attention to it when I updated my HU and that information doesn't appear on the display in any other way, I think.
[Connected Car] psijpkes:
Be ware I installed the latest version of AA (yes I am on AA and not on Mirror Link, I can use maps, waze etc. ), make sure you have the same. It is version Android Auto 2.5.7286

In case of issues it can also be your Phone, I used an Huawei P9
[Connected Car] MichelP75:
If you have kept the USB stick that you used to upgrade to the 1840 version, you will find that the SLDA has created a SpecialLogDirX directory containing the downloadPipe file

This file contains the entire update procedure

It ends with:

------------------------------​-------------------------><8

INFO Deleting the BlackList content

INFO Running project script prj_script.lua

INFO Running project script prj_script.sh

INFO BuildVersion.reg copied to persistent partition

INFO FCID write successful!!

INFO FCID value successfully set

INFO Configuration Version check: /tmp/iso/scripts/lua/config_sw​itch_recovery_mode.lua

INFO 0.10 == 0.10

INFO Version OK

INFO Set Recovery download inactive

ReadMagicArea1=0xFFFFFFFF 0x00000000 0x2342ABCD 0x00000001 0xFFFFFFFF

ReadMagicArea2=0xDEADBEEF 0x0000000C 0x2342ABCD 0x00000001 0xFFFFFFFF

erase flash adress =0x00160000 size=0x00020000

writing flash device done, OK

erase flash adress =0x00180000 size=0x00020000

writing flash device done, OK

INFO finalisation of System Download

------------------------------​------------------------------​---------><8

.
[Connected Car] Muxeu:
My pics of update from 840 to 850 and 850--> 1840

FW 840 had sytem U2003, 850 - U0320
[Connected Car] 7virage7:
Interesting. I updated from ver 850 and then my system was U2003. So same system value occurs for different SW version before update
[Connected Car] psijpkes:
Mine showed: U0320 AA is successful
[Connected Car] mauriciomatos:
There are so many variables....that's why it's so difficult to get to a conclusion on why it works for some people and it doesn't work for most.
[Connected Car] andreasy:
Same
[Connected Car] momsolito:
Upgraded 850->1840 on 2015 Vitara. AA does not work on Samsung S7 edge. Regarding cabel testing, if the phone is charging through the USB port then it should reach the AA so I don't think it's a cabel issue
[Connected Car] mauriciomatos:
In theory you're right. The thing is....there are many examples where people tried a bunch of cables and finally found one that works....so the cable is also a factor. Don't ask me why because I don't know....but it seems to be the case.
[Connected Car] psijpkes:
Which version of AA did you install ? See up, I posted a version that in my case does work.
[Connected Car] momsolito:
I installed the AA 2.5.728604 version witch is the 64 bit version of the latest AA.

Then i tried 3 different cabels and 2 didnt work at all except for chargning the phone and the last one, an old HTC cabel, found the phone but only through mirrorlink and not AA. So unfortunetly still no luck
[Connected Car] Muxeu:
[MENTION=8478793]psijpkes[/MENTION], [MENTION=633011]buscejo[/MENTION], [MENTION=8473423]szuliko[/MENTION], could you share your file /SpecialLogDirX/downloadPipe from instalation USB stick/SD card for logs compare. If you still have it
[Connected Car] Muxeu:
Looked into my installation log and 1840 installation files.

In line 2501 of file /container.iso/firmware/teseo/bin/swu_common_teseo_app_out.out can see:

_ZN36dp_tclKdsSuzuki_VariantConfiguration23u8GetAndroidAutoSupportERh

so can guess only Configuration "23" will get Android Auto support.

File /container.iso/scripts/sh/config_v850.sh has about 20 configurations (DTBID) of hardware:

#configuration for relevant variables
if [ -z $dnlid ];then
if [ -z $DTBID ];then
ai_sw_update_message_to_user "ERROR" "no Board-ID and no dtb-ID available!"

exit 1
fi
case $DTBID in
"19")
hwid_v850="jac_a"
usb_pwr_break=1
;;
"1A")
hwid_v850="jac_b"
usb_pwr_break=1
;;

"1B")
hwid_v850="jac_b2"
usb_pwr_break=1
;;

"2C")
hwid_v850="jac_b3"
usb_pwr_break=1
;;

"34")
hwid_v850="jac_c"
usb_pwr_break=1
;;
"1C")
hwid_v850="suz_b"
usb_pwr_break=1
;;
"33" | "3C" | "44" | "45" | "56")
hwid_v850="suz_sln"
usb_pwr_break=1
;;
"55")
hwid_v850="suz_sln_ug"
usb_pwr_break=1
;;
"1D")
hwid_v850="psa_a"
;;
"1F")
hwid_v850="psa_b1"
;;
"1E")
hwid_v850="psa_b1"
;;
"35" | "3A")
hwid_v850="psa_b2"
;;
"36" | "3B")
hwid_v850="psa_b2"
;;
"20" | "21" | "22" | "39")
hwid_v850="gmmy16_a"
v850nocrc=1
v850noreset=1

;;
"23" | "24" | "25" | "40")
hwid_v850="gmmy16_b1"
v850nocrc=1
v850noreset=1
;;
"30" | "31" | "32" | "41")
hwid_v850="gmmy16_b3"
v850nocrc=1
v850noreset=1
;;
"2B")
hwid_v850="mib2_a"
;;
"26" | "27")
hwid_v850="mib2_b0"
;;
"28" | "29")
hwid_v850="mib2_b"
;;
"37" | "38")
hwid_v850="mib2_c"
;;
*)
ai_sw_update_message_to_user "ERROR" "DTBID 0x$DTBID not supported!"
exit 1
;;

In the lines 798-799 of my installation log /SpecialLogDirX/downloadPipe:

[1004] [32mINFO[0m	DTBID '3c' found!
[1004] [32mINFO[0m	Using BoardID 0x0383 DTBID 0x3c configuration

so my HW named as DTBID '3c' and does not support AA.

This's my guess and that's why I would like look into logs of [MENTION=8478793]psijpkes[/MENTION] [MENTION=633011]buscejo[/MENTION] [MENTION=8473423]szuliko[/MENTION]
[Connected Car] 7virage7:
Good thinking. I guess you may be on something. I wonder if those logs from [MENTION=8478793]psijpkes[/MENTION] [MENTION=633011]buscejo[/MENTION] [MENTION=8473423]szuliko[/MENTION] would confirm that.

Secondly, do you think it would be able to force using AA configuration for other HW variants? Maybe file modification would result in security check fails during update :(
[Connected Car] Muxeu:
I'm not a coder, but don't think so.

The file /container.iso/firmware/teseo/bin/swu_common_teseo_app_out.out is compiled from source, we have just part of it.
[Connected Car] andreasy:
If this is true then it's very discouraging as it seems that there is no hope for it to work in the future due to hardware limitation. Your clue seems quite logical, unfortunately
[Connected Car] m00n61:
You can find an installation log from an AA active installation here:

https://pastebin.com/F5sTGN7N
[Connected Car] Muxeu:
Thank you.

From your log:

[984] [32mINFO[0m DTBID '3c' found!
[984] [32mINFO[0m Using BoardID 0x0383 DTBID 0x3c configuration

as mine.

So, my guess was wrong. It' good for us.

Maybe DTIB 23 requires special AA installation and I saw it in /container.iso/firmware/teseo/bin/swu_common_teseo_app_out.out

Will check your log for differents
[Connected Car] m00n61:
It was not my log but from a fellow Vitara owner who was luckier than us.

My guess is that our units include different USB controllers and this release does not have full support for all of them.

I have a Vitara from June 2016. Android Auto is installed from the Play Store.

After upgrade to 1840 AA is not working, ML is launched instead. If I disable ML and connect the phone I get - after some time- an USB comm error on the phone: " The connected device is unable to access data on this device, Please reconnect USB cable "

ML is working flawlessly and the cable is a USB 3.0 shielded and braided.

Just to make sure I have downgraded to Android 7.0 June security patch - that's what other users reported working - clean install with all security disabled and PlayStore-installed AA.
[Connected Car] Muxeu:
I see 4 main diff's in the logs:

1
m00n61
[703] [33mWARNING[0m	Skipping /tmp/swupdate//dev/mmcblk1p6/ffs/DPOIs - The file doesn't exist
[703] [33mWARNING[0m	Skipping /tmp/swupdate//dev/mmcblk1p6/ffs/lid - The file doesn't exist

mine
[704] [32mINFO[0m	Copying permissions and ownership for ffs/DPOIs's path from /tmp/swupdate//dev/mmcblk1p6 to /tmp/swupdate/dynamic_backup
[704] [32mINFO[0m	Syncing /tmp/swupdate//dev/mmcblk1p6/ffs/DPOIs to /tmp/swupdate/dynamic_backup/ffs
[704] [32mINFO[0m	Copying permissions and ownership for ffs/lid's path from /tmp/swupdate//dev/mmcblk1p6 to /tmp/swupdate/dynamic_backup
[704] [32mINFO[0m	Syncing /tmp/swupdate//dev/mmcblk1p6/ffs/lid to /tmp/swupdate/dynamic_backup/ffs

2
m00n61
[704] [33mWARNING[0m	Skipping /tmp/swupdate//dev/mmcblk1p6/pdd/datapool/005d/FCNavCopyDP.dat - The file doesn't exist

mine
[706] [32mINFO[0m	Copying permissions and ownership for pdd/datapool/005d/FCNavCopyDP.dat's path from /tmp/swupdate//dev/mmcblk1p6 to /tmp/swupdate/dynamic_backup
[706] [32mINFO[0m	Syncing /tmp/swupdate//dev/mmcblk1p6/pdd/datapool/005d/FCNavCopyDP.dat to /tmp/swupdate/dynamic_backup/pdd/datapool/005d

3
m00n61
/dev/sda1 on /dev/media/usbms1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

mine
umount: can't umount /dev/sda1: Invalid argument

4
m00n61
[1066]	Start USB ReEnumeration work around
[1066]	echo -n "gadget" >/sys/devices/soc.0/2100000.aips-bus/2184000.usb/ci_hdrc.0/role

mine
[1084]	Start USB ReEnumeration work around
/dev/mmcblk0p1 on /dev/media/usbms1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
[1085]	echo -n "gadget" >/sys/devices/soc.0/2100000.aips-bus/2184000.usb/ci_hdrc.0/role

1) The man had not installed any POI with his navi and lid (no idea what's it)

2) FCNavCopyDP.dat doesn't exist on his HU too

3&4) I have installed upgrade from the SD card and he from the USB stick.
[Connected Car] MichelP75:
I also have DTBID = 3c but I can not say anything because my Huawei Mate 8 is notoriously known to be incompatible AA ...

However one of my friends with DTBID = 3C and a new Huawei P10 lite works with AA without any problems ...
[Connected Car] mauriciomatos:
DTIBD = 3C here as well, so that's not it.

I can't reallly believe it but....could the choice between installing from SD or USB make any difference? I also installed using the SD card.
[Connected Car] MichelP75:
I tried both. The result is the same. Difference, the input device's address :

USB stick:

ReadMagicArea1=0xFFFFFFFF 0x00000000 0x2342ABCD 0x00000001 0xFFFFFFFF

ReadMagicArea2=0xDEADBEEF 0x0000000C 0x2342ABCD 0x00000001 0xFFFFFFFF

SD card:

ReadMagicArea1=0xFFFFFFFF 0x00000000 0x2342ABCD 0x00000001 0x5AA501CB

ReadMagicArea2=0xDEADBEEF 0x00000010 0x2342ABCD 0x00000001 0x5AA501CB
[Connected Car] mauriciomatos:
Thanks for checking. It would be very weird if it made a difference but hey....it's always good to be sure.

I guess the best way to have Android in our cars is to buy a Android system and have it installed :)
[Connected Car] szuliko:
I'm not sure if it is not too late but here is my log: https://www.dropbox.com/s/7w8adh11ftalyqe/downloadPipe.zip?dl=0

After 1000km with AA I can say that it works very well.
[Connected Car] MichelP75:
DTBID = 3c

Which brand and type of smartphone?

...
[Connected Car] szuliko:
Samsung A5 2016 (510F) with Android 6.0.1.

AA installed manually as it is not supported in my country (Poland). Version of AA is 2.5.7286 32bit arm.
[Connected Car] andreasy:
Guys have we isolated the possibility of phone incompatibility? For example I initially thought that the problem was android 7, so have we checked if for example any of the lucky guys has galaxy s7 edge with android 7 which we know it doesn't work?
[Connected Car] MichelP75:
One of my friends has a Huawei P10 lite on Android 7.0 that is perfectly AA compatible with the SLDA Bosch-Suzuki ...
[Connected Car] mauriciomatos:
And on the other hand I tried a Xiaomi with Android 6 and it doesn't work. So I don't think it's related to the version of Android. It can be related to the version of android together with the phone model but I think the problem is with Bosch SLDA. We either have different versions of the head unit or something is different in the software or wiring of the car, like different USB ports.
[Connected Car] psijpkes:
Huawei P9, Android 7.0, latest version of AA hand installed same build as mentioned by szuliko only 64 bit

And I fully agree with szuliko, it is worth the effort.
[Connected Car] brnrg:
Is possible a video tutorial from those who have AA and Waze on SLDA?
[Connected Car] ZorkyZ:
Does CarPlay work with 1840 version?

we use iOS and Android devices in house so it is important that we have both version available.
[Connected Car] psijpkes:
What do you want to have captured in such video, there is really not much to it. Just install Waze from Play Store, register your self. And that is it.

In AA when Waze was installed you can select either Google Maps or Waze, audio commands will be applicable to the last selected.

It is adviced to make favorite routes on your phone, like work home etc.

See also: https://www.androidcentral.com/waze-android-auto
[Connected Car] mauriciomatos:
Yes, CarPlay works fine.
[Connected Car] ZorkyZ:
Thanks [emoji1]
[Connected Car] rishi2504:
Hello,

I own a May'17 manufactured S-Cross that I bought 2 months back. I am also a member of some social networking groups who own Suzuki cars ( Baleno, Brezza, S Cross and Ciaz).

Apparently, all cars bought late in 2016 and after, failed to support Android Auto after the update to v1740(Indian update) here. I tried 1840 too, but 1840 update failed each time. I am currently running 750 again. All others who bought their cars earlier (2015 and early 2016) had no issues with Android Auto after update to 1740.

I have a theory:

- 750/850 run everything smoothly but no Android Auto

- Source code of 1740 is available from Bosch, which includes code for Android Auto compatibility ( hope I am not wrong here, as I haven't looked into the code myself)

- Update packages for 750, 850, 1740, 1840, etc.

Can we look at compiling the Android Auto modules only and flashing them in the update package format ?
[Connected Car] pitiless:
It seems those HUs have chance to AA which came with 830/730 or older originally. If your HU has 840 or 850 originally the AA will be broken with this update.
[Connected Car] szuliko:
Same observations on different forums (PL, RU, IT).

Yesterday my phone (Samsung A5 2016) received update to Android 7.0. Today I checked if Android Auto is still working - no difference to me, still AA works fine on my Vitara 2015 (came with 830 firmware).

Version 7 of Android probably is not an issue in our case.
[Connected Car] pitiless:
Mine is from March, 2016. Came with 840, no luck with AA. I cannot do anything than wait. I could upgrade to 1840 again, I got Hungarian voice commands with navi, but it was annoying me. Went back to 850 and English voice.

I have log from failed update as well, but left the PD in my car.
[Connected Car] buscejo:
Hello,

unfortunately I erased the USB stick that I used for update
[Connected Car] Muxeu:
Has anyone FW830? Would try downgrade to 830, factory reset and upgrade to 1840
[Connected Car] ZorkyZ:
Did enyone tried to upadte Maps using VIN number and marutisuzuki web page ?
[Connected Car] mauriciomatos:
As far as I know, it only works with VINs of Indian cars...and they probably only have the asia map anyway.

---------- Post added at 10:48 AM ---------- Previous post was at 10:22 AM ----------

I spent some time trying to find it but no luck. it would be nice to try that, yes, even if only to rule it out as well.
[Connected Car] ZorkyZ:
There is a rar file with 750 version which is maruti version of hu 830. I do not have enough posts to send a link but google will do it
[Connected Car] mauriciomatos:
The 750 wont work on European cars...at least that's what happens with 1740.
[Connected Car] ngonguyenminh:
1840

Hello. Today I updated 1840 for DVD Bosch Suzuki Vitara to 55% is unsuccessful. Many times. My DVD of Changan Suzuki (China) version 730.2

Please help
[Connected Car] Muxeu:
Changan Suzuki (China) has own verison of software as I know.

And last one is 730.2

If you don't have 730.2 files go to dealer and restore your software
[Connected Car] ngonguyenminh:
1840

192/5000

Hi, I'm in Vietnam. Vitara in Vietnam does not have a DVD but rather a CD, so there is no 730.2. I bought a DVD from Changan Suzuki (China) for installation. You have 730.2 help me. Thank you
[Connected Car] 7virage7:
I am affraid you are in the wrong thread. EU suzuki SLDA multimedia station does not have any optical drive (no dvd or cd). We perform updates using usb flash or sd cards.
[Connected Car] ngonguyenminh:
sory

Sory by the wrong language. My Suzuki SLDA information system as well as you, usb flash or sd card. My version is 730.2 by Changan Suzuki (China). I updated to version 1840 or 1740 or 850 failed, stopped at 55%. Agent I do not have version 730.2. So I need help
[Connected Car] 7virage7:
I didn't come across chinease variant update files, so I think you should contact your dealer
[Connected Car] brnrg:
Contact Suzuki dealer for restore your Chinese version.
[Connected Car] pitiless:
It won't work. I have tried. Wasted 2 hours with it. Went back to 850.
[Connected Car] hoangnova:
I tried to upgrade my DVD. Unfortunately, I can't manage to finish the update, it always fails at 54%, always for the same reason : "not supported swupd value: 3" (I tried with 2 different USB Keys and SDcards formatted in FAT32), I used all of the firmwares you shared (1740, 1840, 850,...) and the system showed when I try to upgrade my system is U2003. I searched on Google but still did not find a solution.

If you have any idea on what to do. OR Has anyone FW830, 730?

Now I can't use :(
[Connected Car] andreasy:
This is EU version as you can see in the FW name. Before flashing, you have to check what region/version your system is and flash the respective FW. You cannot flash different region file or you will break it
[Connected Car] Muxeu:
[MENTION=3717338]hoangnova[/MENTION] I think you have Changan Suzuki head unit like [MENTION=8482220]ngonguyenminh[/MENTION] and your original software version was 730.2.

So you should find version 730.2 (try to search on Chiness forums) or go to your dealer for restore.
[Connected Car] hoangnova:
Tks for your quick reply.

But how to exit upgrade mode?
[Connected Car] andreasy:
From what I've heard so far, you'll have to find a proper file, the one you had before most probably and use this to continue. I believe the system has no intelligence for roll back. If impossible, you may take it to the dealer but in such situation I don't know if they decide to void your warranty. Better search for your regional file
[Connected Car] ngonguyenminh:
830

Who can upload to me please firmware version 830
[Connected Car] 7virage7:
Man, you are the only one here with Chinease SLDA variant. 830 EU firmware will not help you. You need to find an update package dedicated to you HU and according to official bosch website it is ChangAn Suzuki (CAS) [Version 730.2] (link). Just to clear things up - following this link WILL NOT give you the update package, just version info.

I don't recall someone even mentioning it on xda before, so I guess you have to find it on some chinease forums or get directly from your dealer.
[Connected Car] pitiless:
Version 1750 spotted up at MirrorLink.

https://cert.mirrorlink.com/ProductListing/?MLID=CL170283

There is a new ChangAn version 0740 also.
[Connected Car] 7virage7:
Thanks for the info. It seems that for EU Suzuki the last version is still 1840. However from MirrorLink perspective all EU SW versions have the same HW revision (PP2). I still have hope for working AA, even though this site is ML relevant :)
[Connected Car] pitiless:
I think the existence of 1750 means they are working on it and have a progress if they do the certification. If it happens 2 weeks later for 1850 I don't care if AA will work.
[Connected Car] pitiless:
1850.2_170730_AI_PRJ_SUZUKI_UG_EU_SOP5_LINUX_17.0S03

https://cert.mirrorlink.com/ProductListing/?MLID=CL170284
[Connected Car] ZorkyZ:
But how to get a file ?
[Connected Car] pitiless:
All devices must be certified by MirrorLink if they support that technology. Bosch certifies these head units for each software version. The information above indicates that there is a new version which completed the certification process at MirrorLink. You know the new version number (1750.2/1850.2) and wait. But it means they probably fixed the issues and started the release process. Nobody told there are new files. Hope it will leak or the service centers start to update our HUs.
[Connected Car] 7virage7:
If they are in progress of certification process, it would take some time to release the acctual sofware. What is more, based on those visible in MirrorLink page - many of SW versions were not even listed by Bosch on their OSS page (maybe some betas). I guess we will find out in October/December if 1850 is something Suzuki wishes to show in public.
[Connected Car] m00n61:
Today I accidentally looked at the info page and found out it says "USB Not Connected" even though the phone was connected to ML?

I am on 1840, obviously. Question:

If AA works for you, what does it say in the info page( the one that shows after pressing for 10+ seconds on Settings?

Same question for those whose AA doesn't work.
[Connected Car] 7virage7:
It goes both ways for me. AA doesn't work if info page shows that usb is connected or not connected. But I must say that it often showed not connected even though the phone was charging.
[Connected Car] Zsoltee11:
Does the system (1840) play Flac? 850 no.
[Connected Car] mauriciomatos:
Nope, sorry. I just tried that for you and it doesn't recognize the files on the usb stick.
[Connected Car] ZorkyZ:
Updated to 1840. AA not working, mirror link not working.

Did you tried to click on settings after choosing connect on screen. There is an option to select AA or ML priority
[Connected Car] finne-larsson:
map data

Did anyone try to copy the new map data to an original sd card?
[Connected Car] 7virage7:
I tried. Original map sd card is write protected and I didn't want to sceew things up. I think 1840 update changed something up with nav also, becouse fuiding is better now, even with same maps as with 850. Or its just a coincidence...
[Connected Car] m00n61:
In charging mode it is not connected, data-wise.
[Connected Car] MichelP75:
I even tried to format it. Impossible ! The SD card is write protected at the software level. After formatting attempt, the "2015" map is intact and still works !
[Connected Car] 7virage7:
I know. I used data cable ane tried all connection modes (charging, MTP, PTP, MIDI). All what happened was charging.

What is more, when using AA emulator for developers on PC, it is not needed to change modes - phone connects automatically when USB is plugged.
[Connected Car] Jack_S:
I have copied of original maps from 2015 on a card with changed CID, they work perfectly on updated system, even support my native language (polish).

I try to put new maps 2017, downloaded from this forum, and system claims that data on SD card are incorrect :crying:. So it may work only with card that have CID compatible with new maps.
[Connected Car] MichelP75:
When you say "changed CID", do you mean modified by the principle used in the "goldcard" ?
[Connected Car] hoangnova:
Hello, i saw something from rfs.bsh.tar.bz2.bin\opt\bosch\base\bin\swupdatecon trol_out.out

who can help me?

I want to exit my dvd from the UPGRADE MODE. It is stucks in upgrade mode, cannot exit.

I tried to edit force.dnl to -r/--reset "system" but no luck.