Database Info

General [Review] Joying PX5 2GB+32GB on Android version 8.0.0 (FYT unit)

Joying got in contact with me and asked me if I would wanted to test one of their new PX5 2GB models on Android version 8.
I decided that I wanted to do so, so I received for some 28 euros a Joying JY-VO130P2.
So what is it:
8" screen 2DIN unit for VW/Skoda/Seat/Audi
ARM Cortex based ARM V8, 1 processor 8 A53 cores (4 running at 1.5 GHz, 4 "low energy" running at 1.2 GHz)
FYT based SOM
2GB internal memory (RAM)
32GB storage (ROM)
Android version 8.0.0
particularities: DVD-player
I made a video review of it which you can find here:https://youtu.be/MH1snfDIU5A
The Good:
seems minimally faster than the Sofia 3GR
FYT/syu software the same as on Sofia 3GR.
Android 8.0.0, longer support
Android 8 supports split-screen functionality out of the box.
Improved radio reception (but needs to be tested over longer period)
Improved sound quality (I think, but I forgot to mention in the review)
The bad:
Too high temperatures of the cpu
No user configuration of buttons
FYT/syu software the same as on Sofia 3GR (I mean that some "weird" things are still there on the PX5 as well)
FYT/syu applications (radio, bt, music player, etc.) do not support split screen (and it is so simple to enable this)
No Android 8 Automotive integration
Chinese translations could be improved using on-line tooling like weblate.org or crowdin.com (or others) by using the user community.
The really bad:
Too high temperatures of the cpu. It really needs better cooling.
Update Sun 13 May 2018:
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
See update Fri 18 May
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Update Tue 15 May:
The Google Assistant with spoken searches does not work.
When trying to use the voice search function (clicking the microphone in the search bar), It shows very shortly the 'Speak now' indicator before it turns into an error message that mentions "No internet connection". I checked very carefully and my internet connection is fine. I tried with 2 home WiFi networks and via hot-spot on my phone. All internet connections work fine, but Google search still gives this error message.
Update Fri 18 May:
See post #44
Update Wed 23 May (test of Android auto):
See post #54
Update Sunday 10 June:
See post #77
- OK Google solved.
Update Tuesday 12 June:
Some update about the BT app erasing your Google contacts: Joying is now working full steam on it. Another user made a nice video on youtube about it

Thanks a lot for your great review video!
Huh, 17 minutes... but it's definitely worth watching it fully till the end.
You spent a huge amount of effort and Joying still took 28 EUR from you? They should be ashamed!
So, the Joying Intel Sofia users (like me) will loose your support now? You state at the end of the video that you plan to continue using it in your car.

Interesting review, it addresses many of the questions I had regarding the new Joying PX5 units. Thanks!
Now as @realzoulou mentions above, I hope we won't lose you on the SOFiA platform! Your work on JET and on XSofiaTweaker is central to the success of those units.

I spend a day thinking whether I wanted to spend that money, because I really didn't. Finally I did agree because I thought: "then I have a spare unit for 28 euros".
Like I mentioned: the user layer software (the apks) is the same on the Sofia and the PX5. I already decompiled it in both apktool and jadx.
I can continue the XSofiaTweaker the same way for the PX5 as for the Sofia. Same for the JET apk with some small internal changes (if Sofia then, else ..)
I already made a nokill main server (=sofia server on Sofia) using the exact same steps as on the Sofia (and as explained by @realzoulou) and I replaced the radio mod.
Android 8 for this device is that new that there is no firmware to download yet.
I don't think rooting is a problem, but I'm not going to do/try that without firmware that allows me to reflash. Same for Xposed.
I will program the option to user-select the delay time for double/triple tap today (for Sofia), or at least early next week. However, I think XSofiaTweaker is now almost ready.
I think no new developments will come out for Android 6, so no further developments are necessary either for JET. Mods can easily be added as I simply upload them and use an xml to configure installation. Upload it, add a line to the xml, simply recompile: done.
I like to tinker, but I'm also a simple user that doesn't need that much. Especially when (or more probably: if) Joying/FYT/syu will make more hardware buttons and steering wheel buttons user configurable, there is even less need for special apps. (And I think I forgot to mention that GPS speed indication is correct on this units, but that should actually not be necessary to mention: it should simply work)
I just read on this forum Yesterday that on the standard Joying when you press the Navi button, the assigned (Navi) app will be started. If you press the button again, the previous app will be brought to front. Pressing it again the Navi app will be brought to front again. Etcetera. I did not even know that, but it is very handy. Of course that no longer works in the XSofiaTweaker (or in Gustdens mods).
Only that little overheating barbecue inside is worrying me.

https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?

RoNeReR said:
https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?
Click to expand...
Click to collapse
No it is not suitable. The 2GB-RAM/16GB-ROM and 4GB-RAM/32GB-ROM models are NOT FYT based and NOT compatible with the 2GB-RAM/32GB-ROM models.
The version I have is a FYT based 2GB-RAM/32GB-ROM version. There is no Android version 8 firmware for it yet.

Update Sun 13 May 2018
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
(also added to first post)

There's a 4gb version now on the joying website that is FYT based...
Probably will pick one of these up as a spare, at least the SoM, if anything to test or generate a rom, and get Xposed working on this!
Once root is ahcieved, the manifests can be changed, the program only needs to be granted root, and it'll work fine.
Questions:
Did you look at the clock speed? Is it variable? What governor is used?
What is the three lines present in the system bar do?
Did you open the unit? Haven't found any photos of the interior of the new units yet.

gtxaspec said:
What is the three lines present in the system bar do?
Click to expand...
Click to collapse
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.

carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the fyt model right?

gtxaspec said:
You have the fyt model right?
Click to expand...
Click to collapse
Correct

carter.w.jason said:
Correct
Click to expand...
Click to collapse
Are you able to get us some pictures of the internals?

@gtxaspec

Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.

gtxaspec said:
Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.
Click to expand...
Click to collapse
Yes, should be 6.0, what ever is stock. I'm down to try a custom ROM. I've felt like this is the better unit, if it could be tamed.

Update Mon 14 May
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.

surfer63 said:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
That's a bug in the SYU dialer app, it never went away. The solution is to use Xposed app settings to deny contacts write permissions. Ouch.

gtxaspec said:
Did you look at the clock speed? Is it variable? What governor is used?
Click to expand...
Click to collapse
Overlooked this one. Will check tonight. It is variable from 216 MHz to 1.51GHz, but I will look at the specifics tonight.

surfer63 said:
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
I have this bug on the 7.0 Android as well - this annoys the **** out of me!

Zeze21 said:
I have this bug on the 7.0 Android as well - this annoys the **** out of me!
Click to expand...
Click to collapse
I reported this bug immediately to Joying, like I did last year and like other users did as well: users from the XDA forum as well as the previous carjoying forum.
Joying reacted really surprised on my mail.
That surprised me again a lot (with some other emotions as well).

[Joying for VW] Universal steering wheel controls with arduino

On Joying headunits with CAN Bus, it is not possibile to use resistor based USWC: this thread aims to overcome the limitation by using an Arduino MICRO connected to the receiving unit of the USWC and to the headunit via USB to simulate a hardware keyboard.

reserved 1
Github repository: https://github.com/MobeedoM-opensource/android-auto

reserved 2

reserved 3

surfer63 said:
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?
Click to expand...
Click to collapse
Yes i know thank you, i noticed that for some strange reason the firmware deactivates the accessibility service even at reboot (at true boot not only with ACC_OFF).
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)
Click to expand...
Click to collapse
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefere.
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"?
Click to expand...
Click to collapse
An accessibility service cannot be started programmatically in android, the user must manually activate it with the switch in the accessibility services section.
That command is used to simulate the behavior of the user who changes the state of the switch, it requires root and it is not granted to work on all roms.
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?
Click to expand...
Click to collapse
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.

bambapin said:
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefer.
Click to expand...
Click to collapse
I know about the implicit intents, but on a Sofia on Android 6.0.1 (api level 23) they should still work.
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
So no issues anymore.
(Of course I had set compile version to 27 in the build.gradle, but I ran into "missing" xmls, which I first blamed on being not committed to the repo (your fault, not mine of course ), but which turned out to be part of sdk 28 and up, so still my fault ).

surfer63 said:
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
Click to expand...
Click to collapse
Ah yes, the private.gradle... it contains my private keys passwords so i preferred not to publish them on the internet .
Indeed that file must be placed next to the app build.gradle with this content:
Code:
ext {
my_keyAlias = 'YOUR_KEY_ALIAS'
my_keyPassword = 'YOUR_KEY_PASSWORD'
my_storeFileName = 'YOUR_KEYSTORE_FILEPATH'
my_storePassword = 'YOUR_KEYSTORE_PASSWORD'
}

bambapin said:
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.
Click to expand...
Click to collapse
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?

surfer63 said:
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?
Click to expand...
Click to collapse
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).

@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.

bambapin said:
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).
Click to expand...
Click to collapse
I do indeed think that the SYU apps do nothing according standard Android rules, so the MediaController would only be helpful for any other app. I do think you need to check if "some" SYU app is active by using something like "this" or by checking the com.syu.ms apk (via jadx(-gui)) or so, because that one also checks on several places whether one of its own SYU app is active or not, and on top or not.
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.

surfer63 said:
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.
Click to expand...
Click to collapse
Yes, it is the bottom, when it is inserted it rests on the 4 pillars and leaves enough space below, there will be almost 1cm from the arduino.
The only negative thing i noticed is that with the arduino so close to the antenna the reception distance of the buttons is a little lower than before, but they still work.

bambapin said:
@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.
Click to expand...
Click to collapse
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.

bambapin said:
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.
Click to expand...
Click to collapse
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}

surfer63 said:
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}
Click to expand...
Click to collapse
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?

bambapin said:
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?
Click to expand...
Click to collapse
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.

surfer63 said:
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.
Click to expand...
Click to collapse
Don't know, i thought of your JET because i see it as a great collection of tools dedicated to Joying head units.
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, it could be an additional tool that allows you to schedule actions to be performed on wakeup without without the need to set Tasker as an NAVI app and without Xposed, since it still doesn't work on SC9853i.
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .

bambapin said:
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, ...
Click to expand...
Click to collapse
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
bambapin said:
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .
Click to expand...
Click to collapse
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?

surfer63 said:
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
Click to expand...
Click to collapse
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?
Click to expand...
Click to collapse
Internal, stored in the shared preferences.

bambapin said:
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Click to expand...
Click to collapse
No other apps, only my own FytHWOneKey.
I did see the xml, but did not understand it and wanted to ask later. Those vendor id's / product id's: Are those from your usb devices or are they from (internal) Joying devices?
I can only find one vendor-id in the USB device database.

Question Joying / Isudar - Annoying application autostart [Resolved]

Hello everyone.
I'm writing a new thread because I couldn't find answers in the specific device threads, and the problem is with two different ones.
I own two devices - a Joying Intel Airmont SC9853I and an Isudar QLED UIS7862.
I have a strange problem on both devices, which is that applications automatically start up when the device is rebooted or woken up.
At the moment the problem is with Youtube or Spotify and system settings.
On the Joying device, Youtube starts up every time.
I have to close Youtube to continue using the device.
On the Isudar device, the settings app starts by itself.
Interestingly the settings open right away in the Fabric section.
Normally Fabric section requires 123456 code to access it. After the settings app starts up by itself, it doesn't ask for the passcode.
If I enter any other settings section and return to Fabric the app already asks for the passcode.
It wasn't that way from the beginning. It happened on its own over time.
Maybe I set something by accident but I have no idea what.
I think I already read the whole Internet looking for a solution but unfortunately I did not find one
In the case of Isudar restoring factory settings did not help.
Please help me because I am out of ideas.
Thank you in advance.
--- Edit ---
To all who have had/have the same problem.
The reason for the confusion was a flash drive with music on it.
After disconnecting it, the settings application stopped launching itself. Perhaps it will be similar with Youtube. I have not checked that yet.

Most (if not all) FYT try to open the last used media app. In my case when i last had Spotify, Youtube, DAB-Z or PowerAmp playing, it will open the last one again. I've read something about that here and did a little "app exploring" using APK Editor Studio and found a file listing media apps. So if the system has one of these apps running and it is listed as a media app to the device, it will try to open it up again when you start your car the next time.
It is trying to mimic your OEM radio that remembered if you had radio playing, CD, AUX or whatever and return to that same state.

PieterD82 said:
Most (if not all) FYT try to open the last used media app. In my case when i last had Spotify, Youtube, DAB-Z or PowerAmp playing, it will open the last one again. I've read something about that here and did a little "app exploring" using APK Editor Studio and found a file listing media apps. So if the system has one of these apps running and it is listed as a media app to the device, it will try to open it up again when you start your car the next time.
It is trying to mimic your OEM radio that remembered if you had radio playing, CD, AUX or whatever and return to that same state.
Click to expand...
Click to collapse
Do you mean the "player_app.txt" inside the "assets/property" folder inside the com.syu.ms apk?

Most (if not all) FYT try to open the last used media app.
Click to expand...
Click to collapse
This can also be disabled by setting a property
Code:
ro.build.go_lasttop=false
I found that on a site by @gordgelin.
I have the extended ms apk for the uis7862 already created, but not tested (as I still didn't receive my uis7862). It contains a whole lot more media players than the standard one for those who want to mimic the standard autoradio behaviour. But I also want to share it with the "do not play last media player" patch which I actually "stole" from @gordgelin. (But I also saw many of my findings, mods, apks on 4pda, so I do not feel guilty). I only want to give credit to whom deserves the credit.

surfer63 said:
Do you mean the "player_app.txt" inside the "assets/property" folder inside the com.syu.ms apk?
Click to expand...
Click to collapse
Yes, that's the one i'm talking about.

zmylna said:
Hello everyone.
I'm writing a new thread because I couldn't find answers in the specific device threads, and the problem is with two different ones.
I own two devices - a Joying Intel Airmont SC9853I and an Isudar QLED UIS7862.
I have a strange problem on both devices, which is that applications automatically start up when the device is rebooted or woken up.
At the moment the problem is with Youtube or Spotify and system settings.
On the Joying device, Youtube starts up every time.
I have to close Youtube to continue using the device.
On the Isudar device, the settings app starts by itself.
Interestingly the settings open right away in the Fabric section.
Normally Fabric section requires 123456 code to access it. After the settings app starts up by itself, it doesn't ask for the passcode.
If I enter any other settings section and return to Fabric the app already asks for the passcode.
It wasn't that way from the beginning. It happened on its own over time.
Maybe I set something by accident but I have no idea what.
I think I already read the whole Internet looking for a solution but unfortunately I did not find one
In the case of Isudar restoring factory settings did not help.
Please help me because I am out of ideas.
Thank you in advance.
--- Edit ---
To all who have had/have the same problem.
The reason for the confusion was a flash drive with music on it.
After disconnecting it, the settings application stopped launching itself. Perhaps it will be similar with Youtube. I have not checked that yet.
Click to expand...
Click to collapse
I had the same issue , the reason is exposted cfg files on the usb , once the system starts and detects cfg on an usb , it launches factory settings . so the solution is (remove exported cfg files from the usb )

Zakikeb said:
I had the same issue , the reason is exposted cfg files on the usb , once the system starts and detects cfg on an usb , it launches factory settings . so the solution is (remove exported cfg files from the usb )
Click to expand...
Click to collapse
It is exactly as you write

Question Advice on how best to use a joying head unit!

Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?

I do 1 and 3 on mine, but with CarPplay.
Reason being: CarPlay nav is more "on the road friendly" in that the UI is designed to be used while moving.
Native functionality is good when I want the unit to do the stuff while I just BlueTooth sound from a different device.
My one issue is that if I have data turned on and enable CarPlay, my phone uses the head unit as a hotspot which isn't ideal.

thestraycat said:
Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?
Click to expand...
Click to collapse
I believe you mean FYT UIS7862 based unit. Joying is a made up brand.
3. Pseudo Android Auto- reality is it is a hack that will eventually frustrate as google and phone manufacturer release updates. These units are NOT Android Auto.
Re. Custom ROMs. None exist and are not needed.

Question M200s Mekede? Or Winca...... No text notification sounds

System Specs
Baseband Version
FM_Base_18B_W21.12.3|sc9873A_modem|03-24-21 03:14:08
MARLIN3E_TRUNK_W21.13.3|uwe5623_marlin3E_usbhub|03-31-21 01:19:48
Build Number
QP1A.190711.020 release-keys
System Info
App 1280x720 2021-11-10 09:57:06
CPU Info
CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version
2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
Bluetooth Version
BLINK_2161_RELEASE/2021:09:14:19:38:05_blink
Hi there, trying to figure out why no sound is made from the head unit OR the phone when connected through bluetooth.....Not running Android Auto (disabled app).
Is there something simple I'm missing? 1st dive into these android head units, Any help is greatly appreciated.
Thank you!
Mekede or Winca or ???
****added hwinfo pics

Only solution I've found is to disable Sounds option in bluetooth access on the phone AUDIO and MESSAGE ACCESS. This at least allows the phone to make it's notification sounds while connected to head unit.....phone calls still get routed to head unit.
Doesn't seem there's any working method to have a notification on screen/with sound with this head unit....for now this will do

Update......it appears setting the unit's bluetooth Version to AVRCP 1.6 (in developer options) allows for app notifications to sound through the head unit.....No on screen toast etc, but I'm happy with the notification alerting audibly

Added info/pics
What unit is this?
What can i do/what can't i do?
Can/how can i root it ?
I've been reading but it is all just a blur of info to me at this point......anyone care to help clear the clouds for me??
Thank you in advice!

Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.

surfer63 said:
Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.
Click to expand...
Click to collapse
Thank you for clearing up some questions i had! It really helps me out. As to notifications, mainly it'd be nice to receive sms messages w/pop up on screen (not required, but it would be convenient)
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
I think however most of what I'd like to do is run through different firmwares , for instance (not sure if available) but I'd like to try different firmwares with different camera apps, for instance current firmware has a Front Camera app....but nothing to manually view the rear cam....i believe, could be wrong, that some firmwares might even have a camera dvr app built in .....features like that which are missing....i tried a 3rd party dvr app from playstore but they all seem tailored to using cellphone cameras so its hit or miss as to if the apps even recognize the cameras......
Had one app that recognized front camera and it would record, but even switching to reverse would stop the recording and not resume.
Most of what I'd like to do may just be out of range of potential for these units....I'm really trying to feel out the limits and expectations.
Thank you 1000 times !!!
I appreciate you taking your time to answer my posts and helping to educate me on these devices.
I'll be reading back and forth through these post until i feel comfortable enough to start tinkering (and grab a factory firmware in case i mess up )

louforgiveno said:
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
Click to expand...
Click to collapse
Viper might work nicely on a phone without DSP.
However, all these units come with a highly modifiable DSP nowadays. You don't need Viper (from my point of view).
And indeed, to prevent usage of Viper, you can now only use it when rooted.