yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Completely different question.

I removed my CAN bus 2-3 months ago but decided to reconnect it today. I could not reconfigure it as it could not find MCU updates.

Can I simply take the original 26 Jan Joying stock ROM, including that mcu, make a zero bytes 5009_60.zip and do a initial MCU flash only (of course with original stock recovery).

Or doesn't that work anymore once on the GTX?

==

Edit: Or is there even a simpler method?

==

Edit 2: This is a weird error anyway. I am on the latest 9.20 25-10-2017 MCU anyway. Stupid Joying or stupid Joying translations.

==

Edit 3: I just examined the CarSettings apk.

Upon selecting a new can bus profile it does this:

public class DownLoadMCU {
static String AUTHORITY = "com.syu.car.db.DataProvider";
public static final Uri DATAS_URI = Uri.parse("content://" + AUTHORITY + "/datas");
public static final Uri DATA_URI = Uri.parse("content://" + AUTHORITY + "/data/#");
public int loginId;
public int platId;

public DownLoadMCU() {
Cursor c = App.mContentResolver.query(DATA_URI, null, "k=?", new String[]{"loginId"}, null);
if (c.moveToNext()) {
this.loginId = Integer.parseInt(c.getString(2));
c.close();
Cursor cName = App.mContentResolver.query(DATA_URI, null, "k=?", new String[]{"platId"}, null);
if (cName.moveToNext()) {
this.platId = Integer.parseInt(cName.getString(2));
}
cName.close();
}
}
}

It actually tries to download something and that is also what I vaguely think to remember.

Did anyone try to select another protocol since the Joying websites went down?

Download could also be from some internal location by an app that is the "com.syu.car.db.DataProvider" provider.
[FYT Android Head Units] szpynior:
Can someone give a link to rom version 7?
[FYT Android Head Units] gtxaspec:
you're unit's MCU should be OK, no changes needed. what you need is McuUpdateAll.bin in either /sdcard or /system/mcu

this is used by cmsettings apk to select the vehicle.
[FYT Android Head Units] surfer63:
Thanks. Will do tomorrow.

(But is it missing from your ROM?)
[FYT Android Head Units] gtxaspec:
Missing from v1 to v5. Back in now.
[FYT Android Head Units] surfer63:
Still on V4. Wanted to update today but had a flat battery. No idea why. Nobody touched the car for the last 7 days and it had driven 130 km on that day.

(And somehow I can't press the Thanks button)
[FYT Android Head Units] jesmon:
Love this idea of this, installed V8 but have a few issues. GPS bearing still seems to be off I was driving backwards down the road, my steering wheel buttons are intermittent at best (VW canbus). Unit shuts down everytime I turn the car off, and has a notification during start that it has failed to boot 3 times so will run checks... Really love the idea of it and look forward to the future versions, thanks for your effort!!!
[FYT Android Head Units] gtxaspec:
Clean install or dirty flash? Your experience is not as it should be. The GPS issue is due to an old Xposed module.
[FYT Android Head Units] jesmon:
It was clean install from stock Dec (rooted using joying extra tools).

I enabled the gpsfix in xposed, is that not required or do I need to update it? I might give another clean install a go if you think it was a dodgy install...
[FYT Android Head Units] dyabolikarl:
The one in xposed is V1.0 of the gpsfix. JET tools has the 1.1v which will fix our issue.

Unless the depository has updated since then of course (haven't checked)

---------- Post added at 03:09 AM ---------- Previous post was at 03:05 AM ----------

Reporting my issue with the random chimes. It was bluetooth. I had a hard reboot on key on the other day. It for some reason deleted my BT pairings. So it was my phone asking to pair on key on.

Since then it's been OK. Still keen on updating from v5 to newest one day. Still scared of that Dirty though. Maybe I'll reflash again when Final Version comes out hahah.

I will need to visit the LED off option for the lights staying on though.
[FYT Android Head Units] gtxaspec:
Final soon! Lots of fixed including the LED issue.
[FYT Android Head Units] jesmon:
I tried another clean install of V8 and still have canbus issues, it seems to lose the car model settings a lot, I can't set the car model either it just goes back to the menu screen when I select a different model. I tried dirty flashing over the clean install but no change. I can volume up or down

My temps are sitting up around 100celcius!

Not sure if it is fully wiping when installing as I still have my radio stations after format (everything else seems to be gone).

I have the 9 inch screen with no volume knob so I really need my steering wheel controls, I will go back to stock and give it another go on the next version :)
[FYT Android Head Units] pilotbob3:
I think I might have made a big mistake and wondering if anyone has any thoughts on how to fix.

I had installed V6 and was working just fine, except any program I loaded that required location had the overlay issue. I couldn't figure out how to fix this, so I stupidly tried updating xposed from the xposed installer. Of course I neglected the warning about not to do such a thing.

The unit rebooted, and went to the Android circles animation endlessly.

I tried the multiple rebooting until the 3rd time error message came up, and had the v6 usb stick inserted and it complained about an error. I then read that the recovery would expect a stock Joying rom, so I loaded a stick with the stock, tried multiple reboots, but it would never load it.

So, I'm stuck in the Android dots animation. Can someone let me know if there is a way out?

Thanks in advance,

Bob
[FYT Android Head Units] gtxaspec:
Just keep hitting reset, with the joying stock rom. The system will boot and reinstall the joying factory image. V8 fixes the overlays issue.
[FYT Android Head Units] RoNeReR:
hello gtxaspec,

today i try to change mcu for another vw mcu type.

unfortunately i end with yellow overley bar on top of headunit with "MCU 漢字漢字漢字".

i try back to xp > vw > all. but the error not go away.

the mcu is actually changed and everything working include car info app and steering remote control.

there is anything to hide this annoying message?

thank u for your work amazing rom.
[FYT Android Head Units] jesmon:
I just tried going back to stock (which works, but I can't get xposed to work properly) and then installing your rom again using a different usb and still have issues with my steering wheel controls and canbus in general not performing properly, car info sometimes says no data and other times has a terrible refresh rate maybe 20+ seconds.. the unit is still turning itself off instead of sleeping ,I had a looking at logcat and noticed a bunch of mcud inputs fairly frequently (without me touching anything) is that normal?? I tried to get the logcat onto my computer but it kept corrupting itself, will try after work tomorrow.
[FYT Android Head Units] Stail:
Still got overlay problem on v8.

December update to yours, xposed hangs everytime

Updated newest stock and then to yours, xposed hangs.

Disable, reboot, enable, reboot doesnt help.

Cant install joying extra tools because i cant access files. File managers whines about overlay.

Any suggestions?
[FYT Android Head Units] doraimontv:
Hi.

I have a radio VW jy-vm131n2.

Photos attached

I can not install GTX. Give an error

Photos attached

Any ideas? I really want to try GTX

Thank you!
[FYT Android Head Units] farmerjohn:
Are you on December or January Stock Joying ROM? Please read the first post carefully.
[FYT Android Head Units] amon101x:
are you atleast on the december joying Rom?
[FYT Android Head Units] farmerjohn:
Try disabling UIServer and MainServer apps in the overlay settings. Those are system apps so you first have to press the 3-dot-menu to make them appear in the list.
[FYT Android Head Units] Stail:
It says on the first page with big letters.

Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM.

Update stock rom and try then.

---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------

Tried that too. Didnt help. Still whines about overlays.

Now back on stock.
[FYT Android Head Units] Astur_Torque:
I'm still on 5.1 xd

When it tottally deserves, it will install this

By the way.. joying page is off?
[FYT Android Head Units] pilotbob3:
I've reset at least 30 times. Every third time it says " Has not been fully launched 3 times, the machine self test, it will automatic restart after! "

It then reboots to the same Android dots animation. Any ideas on how to force the loading???
[FYT Android Head Units] pilotbob3:
Sorry to bother you all, solved my problem. Just in case anyone else will find this of value:

1. I had an SD card inserted. For some reason this interfered with the boot. When I removed it, the third reset worked.

2. For some reason, a previous boot corrupted the USB stick. I reloaded and the reset was successful.

Now awaiting gtx's great work to fix the overlay issue :)
[FYT Android Head Units] doraimontv:
Hello

Thanks for the help.

I installed: 2018_01_JY_1024x600_MCU9_20 and then install: GTX ROM.

All right, but when backing down for the first time and activating rear camera, when I reverse the screen loses the lighting and turns black.

Everything works, but I do not see anything on the screen. Screen without lighting.

When I light up with a flashlight, I see the screen.

Now, radio reset, the screen is ok, but a few seconds again black screen.

The same happened with: 2018_01_JY_1024x600_MCU9_20 and with GTX ROM.

Any solution?

Thank you!
[FYT Android Head Units] ArtiP:
Hello

Can someone put a link to v7?

Thx
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION], do you or, if anyone else has the output for 6021 SoM of:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

and

/sys/fytver/platform

thx!
[FYT Android Head Units] jesmon:
Logcat is getting constant activity manager: unable to start service intent (act=com.syu.unicar.toolkitservice) not found... Could this be preventing the boot completing and pushing my temps up too 100c and messing with my steering wheel controls???
[FYT Android Head Units] gtxaspec:
No, that's the same problem the stock firmware has, if you disable the included launchers (com.android.launcher3, com.android.launcher2, com.android.launcher4) the errors go away. I'll be releasing v9 soon which has tons of updates and fixes.
[FYT Android Head Units] charnocc:
Hi,

I tried installing this ROM, but after installation the ROM does not seem to boot.

Steps I did:

- Install current ROM from joyingauto.com (unzip to SD card, reset device)

- root (Using https://hvdwolf.github.io/Joying-RootAssistant/rooting.html)

- install custom.apk

- in custom.apk: install custom recovery

- unzip gtx-rom onto SD-Card, insert SD-Card. On popup cancel automatic installation

- in custom.apk: click "install gtx"

- installation seems to work. At the end, I read the message "remove media, reboot in 15 seconds".

- Remove the media

- Device restarts.

- The carjoying logo appears. The top part of the screen is distorted.

- The carjoying logo disappears for some seconds, then reappears.

- After some time, the carjoying logo disappears for good, a terminal appears. On the last line I can read in red: "Error wait here..."

Does anybody have an idea what I did wrong? My device is JY-UL135N2.

One thing (which I don't think should lead to this problem) is that I don't know where to find which MCU version I have to install (when downloading the original image).

Thank you for your work!

Christof
[FYT Android Head Units] surfer63:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
416000 600000 728000 900000 1200000

and

cat /sys/fytver/platform
5009
[FYT Android Head Units] ptolomeo:
What are the differences between v.7 and v.8? In the Changelog I've only seen changes in the installation method, TWRP things... but nothing of the actual ROM. I guess that if I have v.7 I don't need to upgrade it to v.8, right?

I have a couple of questions:

1.- Gusden nokill hack or Xposed nokill module? Which one is better (Basically I want it to keep Sygic alive).

2.- Is there any posibility to have Sygic sound even if it's in background?
[FYT Android Head Units] szpynior:
has anyone tried to connect the modem to usb. On stock huawei he worked with ppp here, unfortunately not.
[FYT Android Head Units] surfer63:
1. No difference.

2. It needs to become part of the navi_app.txt. The SofiaServer comes with an internal mini list only containing Asian nav apps. The older mods contained a long extended list with about 20 more. It would have been nice if the SofiaServer delivered in the GTX ROM would come with this extended list as well.

And at the same time I'm still looking in making this a user-modifiable option where it loads it from my XSofiaTweaker.
[FYT Android Head Units] overkillthemighty:
I was going to install this ROM, but I am on too old of a stock ROM, can someone get the newest Joying update mirrored and linked on the first post? I am having a hard time finding it myself. If not can someone shoot me a link or post one? (I am somewhat limited on time and I did not see a link in this thread, so sorry if there is!)
[FYT Android Head Units] charnocc:
The new website of joying is joyingauto.com. You can find the updates in the blog.
[FYT Android Head Units] farmerjohn:
It's in the Q&A, third post in this thread that is, I think.
[FYT Android Head Units] 5p4rtan:
Hi!

I tried your rom, but had overlay problems.

When I treid to restor the stock firmware (loaded stock recovery and used usb stick with orginial FYT SOFIA 1024x600 2018-1-26 version for VM131N2D)

During installation I get

Last copy navi fail!

E:unknown volume for path [/mnt/external_sd]

I guess I missed something before loading the original fw

Can someone help me? Im really desperate atm...
[FYT Android Head Units] gtxaspec:
format the USB drive and try again. i had a problem during testing where the stock install refused to boot properly, really weird, turns out the file system was corrupted. re-formatted, copied stock back, and stock firmware installed fine. if that doesn't work try a different usb drive.
[FYT Android Head Units] cihanoez:
Delete
[FYT Android Head Units] 5p4rtan:
Thanks for your immediately reply.

Yes its really weird. It seems like everytime I reboot or reinstall the firmware something different happens.

Yesterday, I was on a fresh install and beside a MCU Update warning which I solved due to a manual MCU update, I got to a fresh ,working build.

Today when I try to start it takes ages to boot into a black screen and a restart with android bot animation and the text "erasing"

After a reset im again on a fresh system.

It seems that there is still something wrong...

My device infos are:

CPU:	Mali-450 MP4

Firmware	1024x600 2017-12-15 17:45:46

MCU Version:	2017-10-25 18:18:10 JY_/R68(__90_C9_6686_5009_CAN(All)_Newlap_AMP

DigitalAmp Version:	2017.04.13 21:00:14 NOR AMP_Q_V2.00

CAN Version:	Unknown

Serial number:	00000000

Maybe I flashed the wrong firmware, but last time It worked well (before going to custom I installed the January Update).

Now that I have access to the system. Can I do some partitition diagnostics? Maybe the recovery partition is corrupt or something like that?

EDIT:

I tried the joying chat and asked for the correct firmware.

They gave me the January update for SOFIA with MCU 9.20.

I will try that but I am I right to better go back to the December build?

EDIT2:

Im now on the January Update.

Update was more or less successful.

After setting the Car Model I got this:

[IMG="MCU error"]https://www2.pic-upload.de/img/34990109/20180313_102446.jpg[/IMG]

Here are my System Infos:

[IMG="System Info"]https://www2.pic-upload.de/img/34990111/20180313_102517.jpg[/IMG]

EDIT :

I got everything running now!

As gtxaspec mentioned, be sure to have a proper USB device.

First I used the wrong MCU version but regardless it should have been another fault.

After a lot tries and resets with errors and weird behaviour, the firware got flashed and I endet up with the MCU error due to the wrong MCU version firmware.

Subsequently I flashed the correct firmware and everything is fine now, beside im on the January version now.

However I cant notice any errors so far.

So my assumption is, getting all theses errors e.g. "navidatatmp errror!" came from the USB drive.

Even flashing the wrong MCU version ROM would work but with MCU error after installation.

I was instructed to use the left USB port of my HU (the one without the Wifi and GPS cable beside) and I full formatted my USB stick.

Hope that helps other with the same problems.
[FYT Android Head Units] karazz:
I'm looking into upgrading my device with this rom. Currently my device is still on the 20161206 version which was installed when I bought this device. To do a upgrade I need to know my MCU version for the correct firmware. Unfortunatly I cannot find my MCU version anywhere in the device. It's not shown on the about device page as shown in the post above.

Regarding the MCU version, how important is it? What are the risks when installing a firmware with the wrong MCU version? And what about upgrading the MCU firmware itself, can I safely upgrade without knowing which MCU firmware I'm currently at?

Thanks
[FYT Android Head Units] warata:
Recently JOYING moved to a new server.

https://www.joyingauto.com/blog/tag/joying-intel-sofia-android-car-stereo-software-update/
[FYT Android Head Units] 5p4rtan:
im not a Pro, but went through a lot of scenarios during my update.

What I experienced is, that the wrong MCU results in a MCU error like in the picture of my last post (Yellow Bar on top of the screen).

I contacted joying and the appologized, they gave me the wrong firmware (wrong MCU version).

So I installed 9.20 first, got the error above and flashed 5.25 after that.

Now everything is fine.

If I understand it correct, the MCU is (just) the bridge between the car and the HU.

https://xdaforums.com/android-auto/.../comprehensive-updated-mcu-list-mtcd-t3476880

So I presume due to my experiences and my information that nothing "should" happen.

But what I know is, with this OS a lot "weird" things could happen anyway :D
[FYT Android Head Units] hidroela:
[MENTION=520205]gtxaspec[/MENTION] is the custom apk on GitHub up-to-date.

thanks in advance
[FYT Android Head Units] gtxaspec:
No, I will post changes shortly
[FYT Android Head Units] gtxaspec:
Source updated.
[FYT Android Head Units] RoNeReR:
[MENTION=8801734]5p4rtan[/MENTION] the solution is simple, u need to install default file manager. ( com.syu.filemanager ),

after that u need to upload "STM8UD.BIN" to the device. ( take this file from stock joying update firmware ).

now with the default file manger u can press on browse button on mcu screen.

mark the file "STM8UD.BIN" and press upgrade.

after that the headunit will reboot and go to the car setting and choose your car canbus.
[FYT Android Head Units] gtxaspec:
Which option are you using? MCU update ??
[FYT Android Head Units] RoNeReR:
i hope its more clearer:

1. install com.syu.filemanager

2. copy the file "STM8UD.BIN" to the headunit. ( u can find it on stock firmware )

3. press the magnifying glass on Mcu Upgrade screen. ( the one that popup every startup when u have the yellow bar error )

4. mark the file "STM8UD.BIN" and press update or upgrade ( cant remember which label there )

5. press Mcu Update button on bottom. the headunit will reboot in end of procedure. ( the yellow bar will disappear )

6. go to car setting >3368 > Canbus Protocol > choose your car canbus.
[FYT Android Head Units] 5p4rtan:
Thanks for this instruction.

Yes, what you describe is a manual MCU Update. I guess this should work. I tried this erlier but with the wrong STM8UD.BIN because I took it from the wrong ROM (joying gave me the 9.20 as I needed the 5.25 - mistakes happen).

You could also flash the whole ROM (with the correct MCU version) because the MCU is updated during the flash process as well.
[FYT Android Head Units] danstah:
Noticed an isssue on my install of V8. When I got to settings and click on backup and reset the settings apps crashes and continues to every time selected. This was a fresh install from a factory resetted Dec Joying ROM. Any one else seeing this?
[FYT Android Head Units] gtxaspec:
Always had that problem with the Android settings, as way back as I can remember. Unknown why this doesn't work, as I haven't looked into it yet.

I will look into it tomorrow.
[FYT Android Head Units] Astur_Torque:
what's the difference between MCU 5.0 and 9?

Any useful improvements?

I'm still on 5.1 (22nd of May 2017) XD
[FYT Android Head Units] gtxaspec:
9 has support for the digital amp models. That's it.
[FYT Android Head Units] Hunmondeo:
If I have VM130N2D with built-in Digital Amplifier, I will need to use MCU Version 9?? Because in "about device" MCU version is 2017-05-25 ...so it's a little bit confusing :(
[FYT Android Head Units] ptolomeo:
Hello, I installed the SofiaServerNoKill Xposed module and now, everytime I turn on the car, the Head Unit boots from the beginning.

I tried to deactivate/activate it and reboot, and it keeps doing the same thing.

Any incompatibility issues between NoKill xposed module and GTX v.7 ROM?

Will the JET NoKill installation make any difference?

Thank you in advance.
[FYT Android Head Units] 5p4rtan:
Same thing here, but im on the original January ROM so maybe its not a specific GTX Custom problem.
[FYT Android Head Units] ptolomeo:
I've been searching and found another thread:

https://xdaforums.com/android-auto/android-head-units/xposed-4-xposed-modules-to-tweak-intel-t3748009

It says:

Note: Some apps prevent the unit from going into deep-sleep. The old SofiaServer simply killed these apps. This module doesn't do that. The MCU detects the apps keeping the CPU cores at higher frequency and can completely switch off the unit, resulting in a cold-boot upon switching on the contact. That is not the fault of this module. It is the fault of these bad behaving apps.

However, before upgrading to v.7 I had installed the Gustden modified SofiaServer using the JET, and didn't have these issues... I will try to uninstall the Xposed Nokill module and install the Gustden mod again... Will report back in a couple of days...
[FYT Android Head Units] surfer63:
GMaps, Poweramp, Tasker and a few others are bad behaving apps.

Note that I made the sofiaServer Nokill for January/December (of course based on [MENTION=3076686]gustden[/MENTION]s and [MENTION=7838245]realzoulou[/MENTION]'s work) AND I made the nokill xposed module. Of course they are not 100% identical, but they do exactly the same!

Better install wakelock detector (or another), to see which apps prevent your unit from going into deep sleep.

and note that it can also be a Joying app that was killed otherwise.
[FYT Android Head Units] 5p4rtan:
For me I just need the NoKill Mod for starting some Apps on Resume from Standby. One was Bluetooth Auto Connect but it seems the reconnect of my phone works now pretty well.

The other was the start of a radar warning app, but I could also start this manually.

So maybe its more clever to uninstall the nokill for me. Nevertheless great work you are all doing in tweaking joyings ROM! :good::o