yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] stormrider57:
hi, people

I just bought a new android head unit with Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 64GB flash) by Sinosmart -for my Renegade with DSP

and the UI looks like joying, so my question is can i upgrade the MCU with joying 's MCU ??

EDIT:

can i root my head unit with this tuto ? because i want to try the joying extra tools to change the radio app ,mine look old and my RDS text is so tiny , I saw that there is nice radio app.

https://xdaforums.com/android-auto/android-head-units/howto-root-joying-sc9853i-head-unit-t3915530
[FYT Android Head Units] bambapin:
Hi [MENTION=2550900]surfer63[/MENTION], have you ever noticed if after ACC_OFF the usb devices are disconnected and then reconnected with the ACC_ON?

I ask because it seems to me that the broadcast intents of the USB connections/disconnections are whitelisted in the background execution limits of android 8, maybe it is possibile to use this thing to wake up the apps killed.
[FYT Android Head Units] surfer63:
Yes, the Joying does this indeed. It was always a big complaint of users using mass storage devices for music on USB. The USB remount took too long, so the media players started with empty libraries.

(sdcards are not unmounted and therefore OK for music and autostarting navi apps with maps on SDcard)

You mean the excempted broadcasts?

Lately I have been thinking about that as well (but I'm not an experienced programmer so it would certainly take a lot of time). It does mean though that a user needs to have at least on device on USB, whatever that is, otherwise it won't work.

---------- Post added at 08:49 PM ---------- Previous post was at 08:37 PM ----------

The point is not only that the CPU should be the same, also the MCU should be the same, which in this case needs to be a FYT MCU. FYT makes the Joying units and MCUs.

As far as I know FYT always has the characters "FY" in the MCU version. That should mean your unit is not a FYT unit and you can't use the Joying firmwares (but I could be wrong).

The only thing I can advise is to check the boot.prop build.prop in /system and check for occurrences of "fyt", like ro.fyt.sys.version or ro.fyt.platform or others.

If it is a FYT unit you can root it as described.

If it is not a FYT unit, it is dependent on the boot/root/flash/recovery mechanism and the build type (also boot.prop build.prop => "ro.build.type") whether you can use that method, another method or none at all.
[FYT Android Head Units] bambapin:
Yes that url :good:

I just tried, i think it worked but i'm not sure because i tested directly in the car... the headunit left my desk and now it is where it is supposed to stay :)

My goal was to restart the accessibility service because it gets disabled after ACC_OFF, it looks to me that the intent was actually broadcasted, since the arduino is itself an USB device, the app has been woken up to receive the intent and then my receiver restarted the accessibility service.

I'll check better tomorrow evening, indeed i updated the code on github if you want to have a look.

edit: sorry i have got another question [MENTION=2550900]surfer63[/MENTION], i noticed that the firmware totally lacks DRMs, neither Widevine L3, i suspect that is the reason because Netflix doesn't work without a patch. Do you know if it It was the same even in previous headunits?
[FYT Android Head Units] stormrider57:
thanks for advice but I can not see system, i must be rooted i think, but, I saw a FYT voice file ?!!:confused:

I just found that :

https://xdaforums.com/android-auto/android-head-units/manufacturer-mcu-t3695315
[FYT Android Head Units] merdok:
6.21 firmware was given, I have not installed it. Still on May public release.

https://drive.google.com/open?id=18mcocVcmqRL453Tu5oG8SizGERD1TWpq
[FYT Android Head Units] tangcla:
I presume it's for 1024x600 models?
[FYT Android Head Units] merdok:
Its filename suggests to support 1024x600 800x480 1280x720
[FYT Android Head Units] tangcla:
Oh. LOL

I hadn't clicked the link yet, until now :) :cyclops:
[FYT Android Head Units] merdok:
No worries.

If you test it out let us know. It got too hot to here want to play in car to update and set everything up. And too lazy to pull from dash.. Again and rebuild on bench
[FYT Android Head Units] julien_blanche:
It has been already tested and reported in this thread,

-bluetooth calling screen minimizing problem solved with navi key pressed during call

-steering controls with 3.rd party apps and carplay working

those are the standing out fixes..
[FYT Android Head Units] tangcla:
Pretty sure it was 6.12 that was covered earlier. This is dated 6.21, isn't it?
[FYT Android Head Units] dr_dre:
Mmh , im having troubles flashing any firmware.. i used several usb sticks ranging from 4 to 128 Gb after unzipping the contents on clean usb sticks.

The joying correctly recognises it ( mount message ) but no flashing or pop up or message appears. Is there something else i need to do ?
[FYT Android Head Units] tangcla:
I used a micro sd card to flash. I didn't have luck with a usb drive.
[FYT Android Head Units] surfer63:
I know hardly anything about how DRM is implemented on Android, or if it is implemented at all on the Joyings. There are no plugins whatsoever on the PX5 either (under /system/lib/drm; correct me if I'm wrong).

I do know that Netflix has always been an issue on the units, but I've never tried to use it on the car myself.
[FYT Android Head Units] Caroline_Don:
Which file did you update? I think there is a problem with your upgrade files. You need to copy all files in the unzipped folder to USB drive, not the zip files and folder.
[FYT Android Head Units] surfer63:
The standard file manager will not give you access to /system. Use a terminal application and go to the android/linux prompt.

Then from the prompt do a:

grep fyt /system/build.prop

If you get lines with fyt, you have a fyt.

If you don't get anything back, you do not have a fyt.

Edit: I edited my previous post. I suddenly realised/remembered I mentioned boot.prop instead of build.prop
[FYT Android Head Units] julien_blanche:
They published on their website along with the change log this time

-----Following is the updated file (2019-6-21) for Android 8.1 Intel SC9853i car radio with 2GB+16GB/4GB+32GB/4GB+64GB

Below problems have been solved:

1)When you are using the Bluetooth calling, you can also use the navigation.

2)Last and next song /pause the volume on Z-link function can be controlled by your steering wheel control.

3)TPMS app can be used normally.

----------
[FYT Android Head Units] tangcla:
I thought the new firmware doesn't wipe on flash, you lose the Google account settings but you keep the device settings.
[FYT Android Head Units] julien_blanche:
Actually you are loosing all installed apps with firmware update and reinstalling all of them and customization takes roughly one hour while sitting in car. I already posted their change log above. they published all devices firmware and putted build.prop date as 21.06. I guess they have made invisible minor changes in addition to 12.06 for (1024x600) and 17.06 (1280x480) devices firmware.
[FYT Android Head Units] surfer63:
I did have a look at your code and have a few questions/remarks.

I think you should make this a thread on its own, and not part of this "Joying Android 8.1 ...." thread. It is getting hard to keep track what is discussed about this topic.

Or do you prefer to have communication around this via the git issue tracker on your github repo?

In your code you also use the BOOT_COMPLETED broadcast. You know that with the Joying deep-sleep option, you will see that only on rare occasions? This is: only on reboots or power (dis)connects?

You use the "com.fyt.boot.ACCON" intent filter in your services. If it doesn't have serious consequences please also add the "com.glsx.boot.ACCON" for those users on Sofia that might want to start using your app as well. But this in turn would also require the "minSdkVersion 23" instead of "minSdkVersion 24" like you have now. My PX5 is on 8 so I have api level 26, but my old Sofia on the bench is on 6.0.1 and it would be handy to test there first. (I tried to build your code, but there are many "hurdles" in your app/build.gradle, so I need to dive a little deeper into it)

You have the method startAccessibilityService with the rooted system call: What does that actually do? Is it for the user to give access? Or the system to give access (as it is rooted)? Is it for the root_preference "OnlyBroadcast"? (sorry for my ignorence)

And for the rest: some of your code I can simply read (but not reproduce). Some other parts I do not understand. :) Waiting for my arduino micros to arrive somewhere mid next week to test.

Edit: You use the "getCurrentForegroundPackage()". I guess this still works if your have (for example) your navi app in the foreground and your media player in the background and you want to skip to the NEXT, as you automatically come to the last "if" statement in your MediaKeysMapper. But does this also work when your navi app is the foreground program and you are listening to the radio or some "generic_syu" program in the background?

---------- Post added at 02:30 PM ---------- Previous post was at 02:24 PM ----------

In your unpacked firmware zip/rar, you will find the "updatecfg.txt". It contains (for the 9853i)

pdatecfg.txt
test
twipe_data

Remove the line "twipe_data", and your data partition will not be wiped. This contains in /data/app all your (system) updates and your "later on" installed apps, and in /data/data all your app data, config and settings.

BIG WARNING: If FYT/Joying made big changes in the software, especially when related to preferences, this can lead to instable systems. Going from 12 June to 21 June, I don't think there are that big changes.

And you can always wipe your app settings (/data/data) to not loose your apps and updated apps, but only the settings and data (be careful with navigation apps which mostly define the maps as app data too)
[FYT Android Head Units] julien_blanche:
I am aware of the config file however since joying is not stating about whether update should be installed with deleting data or not nobody knows actually which action should be taken so just to be on the safe side i am putting twipe_all remark and making clean install. Actually we should report joying about this issue and request them to put relevant code in the config file to make easier update without hassle most of the time.
[FYT Android Head Units] surfer63:
That I fully agree!

Just like any (not too cheap) phone maker they should simply release sequential updates that really "update" instead of "wipe clean".
[FYT Android Head Units] FPSUsername:
Yep, just got one from Joying. So stupid of me not to check the screen resolution. It's 800x480. I would've wanted one with a resolution of 1280x720. I'm not sure if they only have that resolution at 10" screens, I have one that fits in a double din slot without extension (so ~7" screen). It's fast and smooth, the touch buttons are horrible, since it's difficult to use while driving. The UI looks ugly AF, just hope to find something better. Android auto works fine, just waiting for the new UI, since the current one supports nothing but google's apps.
[FYT Android Head Units] julien_blanche:
Hi, for the ui you can check this below new ui of joying launcher which belongs to 1280x480 devices but suitable also for other resolutions (1024*600, 800*480).

I've attached each resolutions screenshot just for the reference and apk file, if you like any icon pack you can just replace the icons with keeping the icons name as it.

https://drive.google.com/open?id=1epLC8OTKh_xXsZ9zEBpwd-TVoqpjTfHT
[FYT Android Head Units] bambapin:
Yes i agree, i answered you on this new thread [Joying for VW] Universal steering wheel controls with arduino
[FYT Android Head Units] julien_blanche:
Hi,

Yesterday during the head unit powered i unplugged the screen and repluged it and now i lost all touch. When i touch the screen nothing happens. Touch digitizer unresponsive. I connected a mouse and tried touch calibration without any luck. Touch screen resolutions also 0x0 on calibration screen. Any help ? Especially [MENTION=2550900]surfer63[/MENTION] ?
[FYT Android Head Units] FPSUsername:
My solution is to use a custom icon pack, I use One UI Icon Pack: S10 combined with Smart Launcher 5 and replaced its widget with a zooper widget. This is how it looks like, the only drawback I see is that the center of the icons stack isn't in the center of the sceen, but slightly below.
[FYT Android Head Units] surfer63:
Sorry, no idea. But what I would try is to decouple the unit completely from power to make it 100% "without power", and then reconnect.

And if all fails: contact Joying.
[FYT Android Head Units] rigattoni:
I found an issue in the firmware version 9853i 1024X600 800X480 1280X720 2019.6.21

The switch for external amplifier only works on cold boot. I used it for my ultra silent fan in the cover to cool down the CPU in car.

After updating I wondered about temperatures higher than expected. I regular have a CPU temp about 25-35°C.

Just now I switched to the antenna connection.

Benefit of connecting it like that is, that the power for the fan is disconnected when the unit reaches deep sleep mode, instead of powering off with clamp 15 directly. So there is a delay of about 50sec....
[FYT Android Head Units] lexuz:
Hello,

I have the 7 inch radio from joying spoken in this thread. ( 2gig RAM and 16gig ROM) and because I drive a Opel Astra H station I would like to put the screen ( and only the screen) higher on my dashboard. Is this even possible. I've seen cables for older units from joying to do this but not for this specific one.

On my Astra the radio sits so low that is hard to use it for navigation.?

Any help would be much appreciated and yes I've search the web as good as I can.
[FYT Android Head Units] surfer63:
Did you contact Joying already? They always delivered extension cables and are the first to ask for advise for these kind of things.
[FYT Android Head Units] lexuz:
Yes I did that. I got a really short answer: "no". But like I said, for another model they had it and I thought it's worth to try it here.
[FYT Android Head Units] yakupA:
Guys, i'm still hesitating to buy this unit since many issues ..but still it seems upcoming releases are resiolving them.

I'm hesitating between this one and Belsee PX5 for my Mercedes E220 (W211).

Julien, Skysurfer, what are your advices ? Shall risk to get this one or better avoid it ?
[FYT Android Head Units] surfer63:
I have never seen a user skysurfer here, but I'm afraid you mean me.

I hate to give advise, because I only have one unit: a Joying and in this case a PX5, not even an 9853i. I have no option for comparison other than "hear say" and my personal experience with 2 units from one brand (my previous was a Joying Sofia).

I had a tough time as well when deciding which one to pick. I went for Joying as it has relatively good support, but most important: the unit supports deep sleep and the unit is therefore (normally) awake within 2-4 seconds.

Literally ALL other non-FYT units need 25-45 seconds as they always come from cold boot (unless started again within 30-60 minutes because in that time-span they simply go in sleep mode and are awake < 1 second).

Being an impatient person that cold boot annoys me massively. When I turn the ignition I want the unit to be ready within 5 seconds. Only the Joyings FYT units do that (and the Funrover/Witson/KLG FYT units. Those reselleres that sell FYT based units). And very occasionally they also do a cold boot and also need ~45 seconds.

If not for this deep-sleep option, I would definitely buy a Dasaita: slightly better build quality and neater assembly quality, slightly better support, better (BT) call quality (but I almost never make calls). And yes: therefore slightly more expensive.
[FYT Android Head Units] merdok:
On the 6.21 firmware I still have waze have no audio / crash and no audio on GMaps.

No difference if I set all channels in the mixer to 1 and Navi set to 10.
[FYT Android Head Units] thomasorr:
Are you rooted?
[FYT Android Head Units] merdok:
Yes I am rooted.

If I missed a fix in here sorry. the search in Tapatalk is little challenged. Just fired up a notebook.
[FYT Android Head Units] thomasorr:
I had the same problem with all google voice feedback including Google maps, the solution is to completely uninstall root using magisk manager (the uninstall option in the app itself). So make all changes you need to using root then uninstall.
[FYT Android Head Units] julien_blanche:
I started to this joying journey with the wrong foot i guess,

-first i was having rear view camera image delay problem which is crucial for these head units that is almost the reason for their existence at least for me. I have contacted with support and they try to solve the problem by sending a board ( I paid $50 import fee for custom). When i connected my 10.25" screen to that board image colors were distorted and touch digitizer got broken.

Now all i have is a inoperative screen and defective amplifier board not to mention of wasted my time, patience and my money. I am try to communicate with them to solve issues but their response and english understanding so slow that almost i am talking to a wall.

I have 20 years of hardware experience and never experienced this kind of bad luck with any product.

I know some of users among us will say i am happy with these joying units and they're right but wait for it until happens to you. Imagine that since one month i barely used this head unit in my car and now all i have is regret.

Also when i researched about joying find out that joying screen issues are popular among the users like losing touch screen capability and so on...

Before jumping the gun imagine what would you do if you had these kind of issues ?

I said to many times and saying again stay away... get yourself a dasaita or any other px6 and be happy with the party quality (they are using wima audio grade capacitors) and the software support by devs..
[FYT Android Head Units] merdok:
Thank you! This solved my issue with Navi sound in both GMaps and waze.

Glad I didn't send them a support issue email.

Does the source mixer work completely normal after this? I didn't get a chance to test that
[FYT Android Head Units] julien_blanche:
By the way, most of you may know how to change boot logo and boot animation however to whom do not know i felt the need sharing again;

-If you want to change the basic car logo to a specific picture just adjust your picture resolution to match your screen as .png format and put inside of attached mycar folder and put that folder to the internal memory. Now you can go to the settings and you will see your picture at car logo screen.

-If you want to change stock google boot animation then you can use the boot animator program in the attachment. It is self explanatory. For instance you can make a video for your splash screen during boot. After you have finished with the program it will give you the bootanimation.zip file and either you can put that file to system/media folder or during the firmware update place it to the root of the usb drive and head unit will flash it automatically.
[FYT Android Head Units] fabien_m2002:
Hello

i am tired of install every month the new firmware which erase all my programs/data.

What are the pros/cons of the june firmware vs may one?

Thanks
[FYT Android Head Units] Cyarli:
Car radio Android 8.1 Intel Airmont eight-core 1.8GHz

Hi everyone, I have been following you for a long time, I need advice, I have an android 8.1 car radio, from a week it appeared on the screen of green writing, it would seem the bluetooth information, I tried to do a null reset, a reset of factory and nothing, the writings are superimposed, I think it is a bluetooth or hardware software, you have suggestions, I am attaching photos, thanks[IMG="[img]https://i.imgur.com/Q7VoVyV.jpg[/img]"],[IMG="[img]https://i.imgur.com/OWeCSVD.jpg[/img]"], [IMG="[img]https://i.imgur.com/HzBQcG8.jpg[/img]"]https://i.imgur.com/HzBQcG8.jpg[/img][/IMG]
[FYT Android Head Units] julien_blanche:
its been already explained a couple post above, reading would be helpful to get what you need..

---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------

Have you tried to boot the unit with latest firmware inside a usb drive ? It may update the system automatically, also feel free to contact with joying support they may help you.
[FYT Android Head Units] rigattoni:
This is something which should be answered by the seller.

Seems to be a hardware defect.
[FYT Android Head Units] PsychoMcSatan:
What's the easiest way to change DPI? I know I can use an app if rooted, but is there a way without root? It seems via ADB is possible, but I think root is required to enable ADB over wifi with this unit.

How about modifying the ROM so that it installs with a different DPI? I'm fishing for something simple, like adding a line to config.txt.
[FYT Android Head Units] Caroline_Don:
Hello friend,

You could make a video and send it to the joying support (info@joyingauto.com), they will help you solve. I think it's the problem of the software.
[FYT Android Head Units] surfer63:
It is not a joying. Joying will not help.
[FYT Android Head Units] Caroline_Don:
Maybe the touch screen is defective, you can contact the seller to replace. Thanks

---------- Post added at 06:56 AM ---------- Previous post was at 06:50 AM ----------

:confused:See the pictues, the UI looks like the joying's unit.
[FYT Android Head Units] julien_blanche:
they are sending me a new 10.1" 1280*720 screen to replace.
[FYT Android Head Units] yakupA:
<mod edit: translation>

See Julien, they are not that bad at Joying finally...

When I see their specs with 30% faster Intel CPU + built-in 4G + built-in DSP + fast boot ... That's quite a lot of arguments and issues will always be everywhere anyway ... In addition they send you a new screen, not so bad finally ..

<mod edit: original french msg>

Tu vois Julien, ils ne sont pas si mauvais finalement chez Joying...

Quand je vois leurs specs avec le CPU Intel 30% plus rapide + built-in 4G + built-in DSP + fast boot ...ça fait quand même pas mal d'arguments et des pbs y en aura tjrs un peu partout...En plus ils t'nevoi un nouvel écran pas si mal finalement ..
[FYT Android Head Units] julien_blanche:
Hi,

sorry i am not french, off course they are sending new screen cos unit is only one month old besides this shows us how bad they designed the unit and lack of quality. If you insist about getting one and joining the painful process feel free to buy one :)

PS: I spend extra $100 for shipping and import duties during changing of defective units. Total $550 for half working device not to mention mental tiredness..
[FYT Android Head Units] czarekurb:
Can I call or send message by a Google assistant with a paired phone?
[FYT Android Head Units] woodman:
Please always use english on XDA, as stated by forum rule #4:

I have edited your post myself with a translation as a courtesy. Seeing your posts history, you are not used to doing this, so I guess you know that already.

Thanks

Wood Man

Senior Moderator
[FYT Android Head Units] PaulBorges:
Magisk

root method can be used?:rolleyes:
[FYT Android Head Units] surfer63:
No, unfortunately not. At least not at this moment. To be able to flash Magisk, because that is what you actually do, you need a custom recovery like TWRP.

There is no TWRP for these units yet.

There is a TWRP app from Google Play Store. It has the option to upload the necessary files from your device to their build server. There it can "automatically" build a TWRP recovery image for you.

Note though that their queue is always full. I've tried for over 4 months for my PX5.

And of course the other way is to build it yourself, but that's very tricky and you can easily brick your unit.

You can also check https://twrpbuilder.github.io/downloads/twrp/ to see if someone else already built it, or had it built. But there is nothing for the intel airmont (a.k.a. 9853i) yet.

(and for those with PX5: Do not try the current two available PX5 TWRP recovery images)

and Paul: Thanks ! :good: