yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] david.scivier:
I think you are the one who needs to calm down i asked a simple question. Which launcher will enable the defult stock mode linked apps to be changed. Bu stock mode apps i mean the ones linked to the NAV, Radio,music, aux in, Dvd modes which can be assigned to the phyisical buttons for control through the steering wheel.

I am well aware buttons can be added to the touch screen but i would loke control through the steering wheel controls for the apps i want to use. Specifically a different music app to the stock one!

I have tried NOVA... it doesnt.

As you had previously stated that a launcher will do it i simply asked which!

For your info i have a degree in electronics. And develope hardware for way more comlliacted systems than a car radio.... i work in avaiation!

Maybe if KLYDE was more.open as to the architecture of the units we could determine some of these things for real.

As you stated the power button does not turn the unit off... would it not therfore be possible in firmware to monitor the power button for activation to turn the unit on the same way as activation of the AAC input is monitored to "switch the unit on"

It would appear that you have a vested interest in the firmware of these units. And do not like a bad word said about them.

I purcahsed one to trial before a possible wholesale purchase.

I am not impressed with the negativity of some of the posts. This is a forum for asking questions, providing help , sharing experiance.

I am still in contact with the manufacturer regarding a large order. However based on the experiance of users in this forum i may abandon the KLYDE unit and move to one of the other manufacturers which are based on MTCD/E
[Android Head-Units] tigert10:
Hey just curious on your Pumpkin HU with CSN2 running FCC...when you turn the key on does the FCC Launcher automatically start? I can't get mine to start when I turn key on. If I press power button to turn radio off, when I press power button again it is instantly back on with FCC fully loaded but if I turn key off and back on usually the radio app launches and I have to press the home button to get FCC to launch and it takes a few seconds (probably 8-10). Just curious if you have this issue or if it is unique to my unit. Any feedback or help is greatly appreciated thanks!
[Android Head-Units] Mickey4Mouse:
i can't help but give feedback...

it similar with my CSN2 at least.

first of all, once used, all "music apps" stay more or less active in the background. So after a while of usage all apps (in my case: FM-Radio, DAB-Z, Power-Amp, BT) are "activated".

IF and just if the FM-Radio App has been "activated" before, it's launched when i start the car again, regardless which player was active during ignition off.

BUT after a while (when Fcc is up again as well) it switches back to the last used player.

If i haven't used ("activated") the FM-Radio since the last full boot (maybe it is sufficient to kill it from task list, not sure), it's NOT started then and the last player starts from the beginning (with a delay).
[Android Head-Units] stesofeu:
I just have upgraded my CNS2 device from Android 8.0 to 9.0 with a little shocking moment while first launch after switching off the device no updating process starts. But that seems to be a failure of the SD card I used. Finally it works (at least at my desk without any speaker...)

What I am looking for is a solution for personalling the status bar. I tried to activate UI Tuner but it doesn't work. Now I found an app called UI Tuner in the playstore. It is necessary to set up some adb commands to run the app. But how can I connect the device with my PC? I there a specal USB-cable necessary?

And one more issue: I've got an USB -ethernet adapter. But the device doesn't recognize it. Are those ethernet drivers not installed?
[Android Head-Units] Mickey4Mouse:
i need help, urgently!

my CSN2 seems to be broken, it shows a slightly distorted picture ON THE RIGHT HALF OF SCREEN ONLY!?!

i haven't tried a reset/restart so far, but everything else i could think of. The "software" restart (there is an app called restart which does nothing at all) never worked. In the past i used the "trick" to change something in the system settings, but since i can't type the password (126), i can't enter the system settings...

the device seems to be physically fine, at some App changes it shows a full screen for a fraction of a second but then it shrinks to half size again.

if there is no other method to force a reset, i have to unmount it or cut the battery (with all the hasle with relearning ABS etc., i really would like to avoid this just because of the damned radio).

i hope it's not a bigger issue and just a software hickup which can be fixed easily?
[Android Head-Units] _yuzo_:
[MENTION=10983381]david.scivier[/MENTION], [MENTION=2534110]rigattoni[/MENTION], both you are correct. No need to argue there. I asked Klyde about the same things in February. Still no reaction from them. And that's all about their vision of business.

Anyway I created this thread to cover more users and the knowledge base grows constantly.

Regarding the radio APP that bothers [MENTION=8828575]stesofeu[/MENTION] and [MENTION=10962079]Mickey4Mouse[/MENTION]: just close it completely by pressing back button in top right corner.
[Android Head-Units] _yuzo_:
press and hold a physical (NOT sensor) power or reset button for around 20 seconds. It should help. Take a photo of issue and unit if not.
[Android Head-Units] rigattoni:
Which app is in foreground when you start the unit?

[MENTION=7281201]_yuzo_[/MENTION]

I offered to correct the crap German translation for all menus, screens and whatever they deliver a couple of times now...

Nothing arrived until now and yes I asked not only Klyde. The same issues (other wrong spellings of course and different missing translations), I just got the message by Skype that they are not allowed to send the XML files... I offered to do it for free, just to get them updated correctly... no response.

And for no money in the word, I will extract them out of any app and send them the corrected files just for fun. For now I found no way to get a new configured app correctly signed and working.

So makes no sense to invest my free time to do their job.

The other problem is, that I sent 25 proper created problem reports, with logs, screenshots and exact description. I offered to speak with the manager of the development team... What do you think happend? Wright... nothing happened. I would be able to offer a Chinese translator if that would be necessary... no answer.
[Android Head-Units] tigert10:
It is the built-in radio app that starts when key is turned on. Grrrr... It's annoying.
[Android Head-Units] _yuzo_:
Use WI-FI and root for that. The way to connect running android on a head unit is not known. Most probably, there is no way for that as the hardware differs from the mobile phones.

Not sure about USB ethernet, but seems like I tried some and they were OK. Most probably it depends on the controller inside.
[Android Head-Units] stesofeu:
Regarding rooting Android 9 HU: I have to follow the link at the first page I think, or is it possible to use the Android 8 app, too?

Regarding ethernet adapter: Yes, I think so either cause I uses the adapter at a DASAIT HU and it works fine.
[Android Head-Units] _yuzo_:
The same story about Ukrainian and Russian. Sent the file in February with corrected and extended translation.

It would be great if you can share your experience with us, so maybe someone will modify and extend the standard app

That's all about the Chinese business, the are lazy and do not want to become better. Not only Klyde. I would say that Klyde is a bit better, as at least they give new firmware and fix critical things since I purchased a unit two years ago.
[Android Head-Units] _yuzo_:
I didn't test android 8 app on android 9. Please use the guide.
[Android Head-Units] stesofeu:
That would be really nice! But the link I think of is this one: root and that's in English. Do you think about another link?
[Android Head-Units] _yuzo_:
My fault, I've changed links long time ago. The first link was to 4pda. So yes, you can use that guide.
[Android Head-Units] rigattoni:
I always would use the plain ADB commands instead of using an app.

adb root
adb connect [IP-Address of the unit]
adb remount
[adb disable-verity] <-- * Normally not necessary only if you get the message that verity is enabled on your device.
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb shell /system/bin/su --daemon&
adb push rooting.rc /system/etc/init/rooting.rc

It works on 8 and 9 in the same way.
[Android Head-Units] stesofeu:
So just link in the HU in the same WIFI of the PC, start the windows terminal app and run the script above with the right IP-address of the HU? That's all? No further files needed?
[Android Head-Units] rigattoni:
You need installed ADB (use always the newest one) and SuperSU.apk and the SuperSU.zip

But the same procedure has been posted nearly 50 times within the last 2 years and nothing changed. Example

I would have a German setup process and I posted it some times now also at XDA. I just don´t have the English file anymore.
[Android Head-Units] stesofeu:
In German: that's even better for me! I will have a look... Thank you!
[Android Head-Units] rigattoni:
You got PM...

...otherwise have a look into this thread.
[Android Head-Units] david.scivier:
Circuit Schematic CSN2 PX5/PX6

Dear All

I have obtained the circuit diagram for the PX5 /PX6 (RX3399) unit from KLYDE ( I am reviewing to see whats missing, AUX AUDIO OUTPUT connector found not shown so far). I have emailed to _yuxo_ for uploading to the forum (thank you).

Kylde have confirmed the interface for PX5 and PX6 module is identical.

I hope this is helpful info for the forum members :):cool::victory:
[Android Head-Units] _yuzo_:
Thanks, David, for sharing that with us. Here is a link on my drive related to the mentioned schema
[Android Head-Units] tigert10:
radio app

Any way to get just the radio as a separate app to launch? The radio is part of the com.car.ui.MainApp and if I disable that all sorts of things don't work. I'd like to simply be able to run a launcher and still access the FM radio functionality but no one has a fm tuner app that will work with csn2 hardware that I can find. Am I missing something? Any way to separate the radio app out from the rest of that? It is over my head...any help or advice is greatly appreciated. Thanks!

---------- Post added at 03:08 PM ---------- Previous post was at 03:05 PM ----------

This is frustrating...similar to my issue for sure. Not sure of any workarounds...can't seem to find any threads but good to know I'm not the only one with issues.
[Android Head-Units] _yuzo_:
I told about that a few my posts ago: to avoid that, just exit radio app by clicking back button in the right top corner of the screen.

The way to separate radio app from CarUI.apk is not known for me. I'm not a developer.
[Android Head-Units] tigert10:
I appreciate your reply. It is just annoying because when using the stock launcher it doesn't have this issue. I wish there were different opinions for radio tuner apps. I know other mcu's have developers working on radio apps so maybe some day the csn2 will get some radio app development.
[Android Head-Units] stesofeu:
After lots of tries setting my Android 8.0 head unit to switch on the 360 degree camera of my NISSAN X-Trail manually I now have upgraded it to Android 9.0 and it works! In factory settings of canbus you can set up keymode to different numbers. Each one with the term "AVM" shows a by KLYDE called "assistive touch button" which is a round flying button of about 2 cm diameter on the screen. By pressing this button you are able to switch on the camera manually.

At special keymodes (e.g. key mode 6 AVM) you can also switch on the camera by using the driving wheel's buttuns (in this case hang up phone). My question is: does anybody know how to let dissapear this assistive touch on the screen but holding on the functionality of switching on the camera manually by pressing a wheel's button?

Update:

Found the solution on my own: in factory settings at the canbus section a new entry was added I don't know before called "car type 2".

Herein the 360 button can be hided. And it works!
[Android Head-Units] Ballysticc:
Ford Fiesta ST Android 9 PX5 Issues

Hi everyone,

Recently had the Android 10 PX6 2016 Head Unit installed into my 2013 Ford Fiesta ST model ZW-FFS13. Everything works on the headunit itself, however, the buttons on my steering wheel for volume up/down and skipping tracks do not work. Also, the Sony controls for the old head unit (also volume up and down etc) under the screen do not work either. Its meant to all work with the unit. I went into the canbus setting and found that mine was under "Focus_Ecosport&escape&carnival(Simple)". Is there a Canbus setting for the Fiesta that would allow these controls to work?

Thank you.
[Android Head-Units] Ballysticc:
CanBus Decoder

Hi all,

After the installation of my headunit into my 2013 Ford Fiesta ST the SWC and the Sony Controls under the screen on the dash do not work. I've checked in the "Key Study" section of the Canbus but nothing seems to be registering when I try to map it. I checked my CanBus Decoder (Which has a QR code on it) and the search showed results for a "Kuga 2017 and Focus 2015". Is this the correct decoder for my vehicle? Please see picture attached! Thank you. [IMG="Canbus Decoder"]https://imgur.com/a/yAwCkpu[/IMG]

FD-SS-05A

20200618

SW:V1.52.008BYPT5

P/N:1801300278
[Android Head-Units] _yuzo_:
Please post unit's firmware version. Most probably it is nedded to upgrade to the most recent and re-test afterwards.
[Android Head-Units] Ballysticc:
Thanks for responding, I checked with the seller and they said that it is the correct decoder. From what I remember my firmware version was from May this year. I just saw that there is a new version from July for PX6 so I'll download that and update it. Hopefully this fixes it!
[Android Head-Units] Ballysticc:
Ok, I just checked all my system information:

Model: PX6

Android Version: 10

Build Number: rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200619.120237 test keys

Kernel Version: 4.19.111+

MCU Version: MTCE_MX_V3.57_2 (23rd of June 2020)

I did just try to update but I did not get the prompt. I went into the settings and tried to click on MCU update and a pop up said "MCU file not found". Are you able to link me to the best firmware version and mcu version for my setup?

Big thank you for your help.
[Android Head-Units] _yuzo_:
This unit is not related to this thread. You have MTCE device.
[Android Head-Units] atalmatal:
Px5 dsp androi 10 update

Hi friend.this is real android 10 update link

https://we.tl/t-MFnQie39ib

---------- Post added at 04:45 PM ---------- Previous post was at 04:40 PM ----------

put the firmware (kupdate.zip + update2.bin ) directly to USB stick with FAT32

- press and hold power button or reset button in full touch device and power on unit by switching on ACC in your car or enable power +12V on both red and yellow wire in case you doing that on the table. On some units use reset button instead.

- once the update is started, release the button.

---------- Post added at 05:34 PM ---------- Previous post was at 04:45 PM ----------

Zlink app for carplay latest version

https://wetransfer.com/downloads/85...load_button&utm_source=notify_recipient_email
[Android Head-Units] Kimo2014:
Hello,can I install this in my unit plz ?
[Android Head-Units] rigattoni:
So this update is only possible with using the included MCU for the CSN2_D_*** units, right?

Has someone successfully updated from 9 to 10 with it, or is this just another fake 10?

I think there is still no possibility to update units without DSP!
[Android Head-Units] atalmatal:
Yes.you can

---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------

You can update without mcu update and only put kupdate.zip in usb
[Android Head-Units] rigattoni:
So this is a real Android 10 with which API?
[Android Head-Units] atalmatal:
this is build.prop

# begin common build properties

# autogenerated by build/make/tools/buildinfo_common.sh

ro.system.build.date=Sun Jun 28 11:58:15 CST 2020

ro.system.build.date.utc=1593316695

ro.system.build.fingerprint=rockchip/rk3368_Android10/rk3368_Android10:10/QQ2A.200305.004.A1/ken06281158:userdebug/test-keys

ro.system.build.id=QQ2A.200305.004.A1

ro.system.build.tags=test-keys

ro.system.build.type=userdebug

ro.system.build.version.incremental=eng.ken.20200628.120553

ro.system.build.version.release=10

ro.system.build.version.sdk=29

ro.product.system.brand=rockchip

ro.product.system.device=rk3368_Android10

ro.product.system.manufacturer=rockchip

ro.product.system.model=PX5

ro.product.system.name=rk3368_Android10

# end common build properties

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=QQ2A.200305.004.A1

ro.build.display.id=rk3368_Android10-userdebug 10 QQ2A.200305.004.A1 eng.ken.20200628.120553 test-keys

ro.build.version.incremental=eng.ken.20200628.120553

ro.build.version.sdk=29

ro.build.version.preview_sdk=0

ro.build.version.preview_sdk_fingerprint=REL

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=10

ro.build.version.security_patch=2020-05-05

ro.build.version.base_os=

ro.build.version.min_supported_target_sdk=23

ro.build.date=Sun Jun 28 11:58:15 CST 2020

ro.build.date.utc=1593316695

ro.build.type=userdebug

ro.build.user=ken

ro.build.host=dell

ro.build.tags=test-keys

ro.build.flavor=rk3368_Android10-userdebug

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=arm64-v8a

ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=arm64-v8a

ro.product.locale=en-US

ro.wifi.channels=

# ro.build.product is obsolete; use ro.product.device

ro.build.product=rk3368_Android10

# Do not try to parse description or thumbprint

ro.build.description=rk3368_Android10-userdebug 10 QQ2A.200305.004.A1 eng.ken.20200628.120553 test-keys

# end build properties

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.bionic.ld.warning=1

ro.treble.enabled=true

persist.debug.dalvik.vm.core_platform_api_policy=just-warn

dalvik.vm.lockprof.threshold=500

net.bt.name=Android
[Android Head-Units] Kimo2014:
Tell me if there any issue plz
[Android Head-Units] _yuzo_:
Dear friends,

I can confirm that Klyde started sending real android 10. But there are no instructions how to upgrade. The simple way as in case fake android 10 does not work there as the recovery should be changed as well. Most probably there will be some instruction similar to instructions for android 8 to 9 upgrade, but for now Klyde says that there is no way to do an upgrade :) I heard the same a year ago when android 9 apeared for our units :)

[MENTION=10983381]david.scivier[/MENTION], maybe you can also try to push Klyde? :D
[Android Head-Units] atalmatal:
i send this photo error when update and klyde says this instruction to update android 10

put the firmware (kupdate.zip + update2.bin ) directly to USB stick with FAT32

- press and hold power button or reset button in full touch device and power on unit by switching on ACC in your car or enable power +12V on both red and yellow wire in case you doing that on the table. On some units use reset button instead.

- once the update is started, release the button.

https://ibb.co/tLvLHJW
[Android Head-Units] _yuzo_:
Yes the error says that you have rr3368 while rk3368_Android10 processor is expected.
[Android Head-Units] david.scivier:
So we need to establish if there is a true diferance to the processor module or not and if not how the update is determining that the unit.is different.

I have asked KLYDE some questions. What isnthe date on the update files from KLYDE?

They sent me a ZIP a couple of weeks ago but I ignored it thinking it was the fake Android 10.
[Android Head-Units] _yuzo_:
There is no difference. There is some kind of "fool protection", the same story was with android 8 to 9 migration. On android 8 processor was marked as px5 and android 9 names it as rk3368. That is done in order to avoid the direct attempts to install android 9 on android 8 units, as it will cause bricking the devices. Internal storage layout differs for android 8 and 9. The same for android 9 and 10.

The date in the shared file is 202008061132.
[Android Head-Units] rigattoni:
I just downloaded the files and you can see in the metadata:

pre-device=rk3368_Android10

The Android 9 updates are listed in the related metadata:

pre-device=rk3399
[Android Head-Units] _yuzo_:
rk3368 for Android 9 PX5 units to be exact.
[Android Head-Units] dahool2008:
This Error is fixable.

1. Open the ROM File

2. Go into Folder: /your_path_to_the_file/kupdate/META-INF/com/google/android

3. Open the File "updater-script"

4. Edit the first row

getprop("ro.product.device") == "rk3368_Android10" || abort("E3004: This package is for "rk3368_Android10" devices; this is a "" + getprop("ro.product.device") + "".");

to

getprop("ro.product.device") == "rk3368" || abort("E3004: This package is for "rk3368_Android10" devices; this is a "" + getprop("ro.product.device") + "".");

build firmware package back again
[Android Head-Units] rigattoni:
I don´t know if just to edit the installer script is good enough...

Did you update your unit successfully?
[Android Head-Units] dahool2008:
[MENTION=2534110]rigattoni[/MENTION] no because at the moment [MENTION=408485]work[/MENTION]. Will show later into the block-devices for making by side android update script

/dev/block/by-name/dtbo

/dev/block/by-name/uboot

/dev/block/by-name/trust

/dev/block/by-name/boot

/dev/block/by-name/oem
[Android Head-Units] rigattoni:
Any news about the script? Did you find a way for getting A10 on our devices? Not that I need to do it, but as long the statement is online from others that there is an update...
[Android Head-Units] Novosmaxim:
Klude kd12108?

Hi, everybody. Can you tell us where you can find the latest firmware for - KLUDE KD12108?

Thanks

---------- Post added at 02:32 PM ---------- Previous post was at 02:28 PM ----------

just a search I couldn't find my device on the site.
[Android Head-Units] dahool2008:
[MENTION=2534110]rigattoni[/MENTION] the files are working-but testing on the android 10 dynamic partition update script to make it save from pie to Q
[Android Head-Units] stesofeu:
Regarding DISP button issue: I just managed it by upgrading to Android 9.

Regarding dab issue: do you use the right antenna? QQ as well as X-Trail may have to similar FAKRA ports: one is for gps and the other for DAB.

Regarding external monitors: there should be an app called video out.
[Android Head-Units] timknowlden:
Does anyone with a pumpkin dab single find the quality awful? It squeals on every channel very often.
[Android Head-Units] moldavite:
Not had an issue with mine since I changed to an external DAB aerial.
[Android Head-Units] rigattoni:
No issue with external antenna.

On some cars you need to change the antenna base to get it working, because most OEM antenna amplifiers filter out the upper frequencies needed to receive DAB+ with the OEM antenna.
[Android Head-Units] timknowlden:
Does that mean you had similar issues before?

I don’t have much use for DAB as mostly listen to FM, but as we all know the Chinese units are terrible for FM. Which is why I’d like DAB to be reliable. It’s a shame that the dab app also has to be manually opened on start up.
[Android Head-Units] stesofeu:
It depends to your launcher. I use the AGAMA launcher where you can set up apps to be started with the starting head unit (using a starting time delay).
[Android Head-Units] timknowlden:
Yeah it can launch it with agama but doesn’t auto play the last station. It also sometimes doesn’t launch agama automatically though it can launch on a settings page or reverse cam etc