yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] hillbicks:
[MENTION=8992530]bersercci[/MENTION]: You should be able to use event -> monitor start as an indicator when tasker starts.

I have a question for you guys, since I will be in the same position once I get my HU in the next couple of days. Changing the default navi app:

- Does it change also the navi button on the HU to this app?

- What happens if you click on a location field in android (contacts for example), does it open the defined navigation app as well?

Thanks in advance.
[FYT Android Head Units] rigattoni:
You need to choose a trigger as BT connected, WiFi connected...something like that with a task as "Add Enter Task".

In this task you are able to start every app you want to get started.
[FYT Android Head Units] bambapin:
Instead of using the Navi app trick, you can try using this app to automatically launch other apps (tasker in your case, but you can choose more than one) at Boot or at ACC_ON.

If you have root you can also automatically restart the accessibility services that are disabled by the firmware when the head unit goes into deep sleep.

I do not guarantee that it will continue to work on all future versions of the firmware but for now it works :fingers-crossed:
[FYT Android Head Units] bambapin:
For those interested, this is the patched boot created from the boot.img of the 6.21 firmware and the last Magisk version.

There's always the problem of sound on Google apps... i've done some research and i'm afraid the problem is deeper.

Probably it is caused by some wrong modification that the Magisk installer/patcher does.

It seems to me that the impact is on the audio mixer and only indirectly on Google apps.

Does anyone have ideas on how to solve or what to check? It goes beyond my abilities :o
[FYT Android Head Units] surfer63:
I have been thinking of unpacking the original boot.img and the magisk boot.img and do a diff on it. First a "diff -qr" to check which files are different and then a "diff -u" for the text files.

But I don't have a 9853i and I don't have much time, so it is low priority.
[FYT Android Head Units] bambapin:
I did it, but the differences are in binary files so i stopped.

This is the diff output of the ramdisks, the kernel .gzs are identical

Only in patched_boot.img-ramdisk/: .backup
Files boot.img-ramdisk/init and patched_boot.img-ramdisk/init are different
Files boot.img-ramdisk/sbin/ueventd and patched_boot.img-ramdisk/sbin/ueventd are different
Files boot.img-ramdisk/sbin/watchdogd and patched_boot.img-ramdisk/sbin/watchdogd are different

the /init is much bigger in the patched boot.img because it contains the magisk files itself (or at least i think so)
[FYT Android Head Units] PsychoMcSatan:
[/COLOR]

Thanks for upload.

I rooted in order to update DPI (to 200) and then uninstalled Magisk in order to restore Google sound, rebooted, but sound is not restored. There were two options in Magisk for uninstall so I reinstalled and tried the other, but it required a backup file.

Do I need to restore original boot.img file? The Google apps confuse me and I'm not sure of the components required for GoogleVoice, but is there anything I can (re)install from the Play Store to try to revive my unit's voice?
[FYT Android Head Units] bambapin:
The only working option, as far as i know, is the "Complete uninstall", which i think you used.

The Magisk uninstaller should take care of restoring the stock system files so you shouldn't need the stock boot.img.

I would try to repeat the whole procedure reverting the dpi change, i have some memories of an incompatibility of google assistant with some dpi settings.
[FYT Android Head Units] CZ Eddie:
Have ya'll tried flashing a different Google Apps package to see if that fixes broken voice?

Or perhaps tried a beta version of Magisk?
[FYT Android Head Units] rigattoni:
Hmmm.... your app is installed, but I am not able to get the app started.

May I have overseen something?
[FYT Android Head Units] CZ Eddie:
Hmm, has anyone tried converting from Magisk to SuperSU yet?

SuperSU doesn't work for most Oreo ROM's but it does work for a few.
[FYT Android Head Units] surfer63:
Are you usning CarWebGuru?

If so long-press the app, select Explore, and select the Settings. That is the big disadvantage of CWG that does not support multiple launcher intents.
[FYT Android Head Units] bambapin:
You mean you are not able to start my app?

There are 2 activities (entry points) in the app, maybe your launcher shows only the default one and not the one needed for the setup.

If you are using CWG for example, long click on my app to open the context menu, then choose explore and select "FYTStarter Setup"

EDIT: [MENTION=2550900]surfer63[/MENTION] i didn't notice you had already answered :)
[FYT Android Head Units] rigattoni:
Thanks both,

I´m using FCC Car launcher, so I think I need to find some workaround, because a long click has complete different use cases.
[FYT Android Head Units] bambapin:
Try to install also this one, it will add another entry for the setup in the launcher.
[FYT Android Head Units] rigattoni:
Thanks, I will give it a shot tomorrow.
[FYT Android Head Units] bambapin:
Yes tried but i ended up in a soft brick :(
[FYT Android Head Units] CZ Eddie:
Uh oh. I tried root for the first time on my new Joying that I got today.

JY-UOS02N4GS 4GB+64GB-G

First, I updated it to 6/21/2019 app version (firmware).

Then followed the directions in the developer.zip file.

When I installed the newly created "lsec6521update" and "6521_1.zip, the Joying rebooted to something where it said "installing update" I think.

Then rebooted again but never came back up.

I've just got a black screen and the buttons on the left-side are lit up solid.

Already tried pressing the reset button.

And even tried removing battery power for 20 seconds (have it on my work bench).

No dice. It just stays at a black screen with the side buttons lit solid.

I'll research in the morning, but if anyone wants to save me some time by telling me how to fix this, I'd sure appreciate it! :good:

Hopefully this is just Joying's version of a soft-brick and there is some recovery method I'll find.

EDIT: I kept messing with the reset & power button until it somehow magically started booting.

It went to 5,4,3,2,1, then crashed & burned again.

So I threw the latest update on my MicroSD and inserted it into the Joying.

Then played with reset & power buttons again until it booted again.

This time it's booting to the system update.

Looks like I might be okay (cross fingers).

EDIT #2: Yep, I'm back at the desktop.

All my apps gone of course, due to the firmware re-update and starting over from scratch now.

A lot better than a hard brick though!
[FYT Android Head Units] bambapin:
Yep a lot better than a hard brick! I think this is the only advantage of not being able to change the stock recovery :)

Would you mind posting the created 6521_1.zip that didn't work?

I'd like to compare it to the one that worked on my unit to check if there are any differences.
[FYT Android Head Units] CZ Eddie:
Ugh, I already deleted it. Sorry.

So, my second try at rooting went without an issue.

Worked exactly as the directions said it would.

I am now rooted. :)

---------- Post added at 02:05 AM ---------- Previous post was at 02:05 AM ----------

...and now I know how to recover from a soft brick. lol :fingers-crossed:

I just attached the working zip btw.
[FYT Android Head Units] mihaita_us:
Is this method working only for joying ? Or for all HU who use the same platform/motherboard ?
[FYT Android Head Units] CZ Eddie:
EDIT N/M SORRY, WRONG THREAD.

I searched this thread for keyword "slow" but didn't find anything.

Is anyone else experiencing extremely slow Google Play Services?

App installs take foreverrrr to start downloading and the download itself is really slow too.

I somehow accidentally reset back to factory defaults after a Joying Apps mod gone wrong.

And still have super slow Google services.

Tried changing DNS to 8.8.8.8 and it's still slow.

I'm on the latest 6/21 firmware.
[FYT Android Head Units] bommelkopp:
Is there any chance to process the boot.img-patch on pc? Likely Linux?

Or anyother option: Is it possible to integrate the Magisk-boot-patch into a script to use in a terminal like termux?

That would make the every-month-update easier...
[FYT Android Head Units] bambapin:
You can use an android emulator, the default images x86-64 (API 27) from the android SDK should work.

Install Magisk on the emulator, upload the original boot.img to the emulator sd card, choose the uploaded boot.img from Magisk and you are done.
[FYT Android Head Units] bommelkopp:
Thanks, will try...

Next idea: Can i also use the Magisk on my mobile?

Running Ver. 19.3 and actual Mamanager...(7.x)
[FYT Android Head Units] bambapin:
It depends on how Magisk identifies the target architecture, i mean to choose the correct binaries. If it only looks at the boot.img maybe it could work, if it looks at the current environment (your phone), it will not work unless you have an intel based phone.
[FYT Android Head Units] chrisaw:
EXPERIMENTAL Fix for audio issues

Hey folks!

I'm not 100% sure this will fix the audio / Waze issues but so far it's running well for me.

What is this?:

- latest boot image patched with magisk

- ianmacd magisk build (includes various fixes for various devices)

- audio compatibility fix module (available from Magisk) but patched to not require hardware volume keys to install.

Installation Steps:

1.) Download and install 2019.6.21 build of firmware from: https://drive.google.com/file/d/18mcocVcmqRL453Tu5oG8SizGERD1TWpq/view?usp=sharing

2.) Download and install the following Magisk build from: https://drive.google.com/file/d/10OKgdgBqo47egPPV3VrYxCwRLjpucDqP/view?usp=sharing

3.) Install a file explorer (I recommend Solid Explorer but others will work too - FX is another good choice.)

4.) Once both the 2019.6.21 build of the firmware and Magisk is installed on your device - reboot and hit "Cancel" when it tries to reboot again. Then open Magisk and enter Modules, then click the "+" and select your module ZIP for "Audio_Compatibility_Fix_1.7.3_radio.zip" from the SD card. If Magisk force closes - it's because your file explorer isn't compatible - return to #3.

5.) Reboot the device once the module is installed and see if things work properly.

6.) If you wouldn't mind - report back on how things are working (or not working) for you!

Does this work?!:

In all honesty - I don't know 100% if this works or not so I'm not proposing this as "THE FIX" to all of the problems encountered - it's just my first attempt at a fix / workaround to avoid the strange audio issues.

How the hell do I undo this?!:

In order to undo this change - simply repeat step #1 as this will perform a full factory reset (losing all data sadly) and bring your device back to functioning normally (i.e. without root.)
[FYT Android Head Units] elabjer:
so, my HU is already rooted - do you believe I need to remove Magisk altogether and start from scratch? At what point do we flash the modified boot image?
[FYT Android Head Units] khurrraam:
I have a request, although it was being discussed in a different thread but since there are folks here who own the new device. Here goes.

My Android device got updated to Android 9, and now I can't use Android Auto on my Joying Android 8.0 (PX5).

Would it be possible to see if the Z-Link apk (from new Intel Joying) can work on the 8.0 (PX5).

If someone can extract the apk, be kind enough to share the APK, I would like to put it on mines and test it out.

Someone who invests in Joying hardware, shouldn't be artificially limited to updates to sell new devices, at least for CarPlay (I don't even know yet how PX5 will play out with iOS 13) and Android Auto.
[FYT Android Head Units] surfer63:
Don't crosspost in 3 threads at the same time.
[FYT Android Head Units] shazaani:
I did the above. My Waze freezes randomly after 10 or 5 minutes of navigation. Also no call audio works. It does not even display phone call info on head unit. Bluetooth music does work.
[FYT Android Head Units] rjanossy:
Hi,

I have exactly the same system info from my HU. My unit is a Lexxson GY-ZP7188 from Amazon.

Could you find any info regarding the compatibility with Joying models?

Could you go forward with updating FW, rooting, tweaking etc. ?

Regards,

Robert
[FYT Android Head Units] elabjer:
Does anybody know how to solve issues the missing DocumentsUI in the 6.21 FW on SC9853i is causing?

Edit: I've got it working by installing MiXplorer as a system app.
[FYT Android Head Units] jAZZ-MAN:
Hi, (this is my first post on forum... Welcome all people),

I have JY-UO135N4GS and i install "Joying sc9853i Root.zip" file form 2nd post. After this i lost microphone in call.

Anybody can help me?

Thanks for Yours time.
[FYT Android Head Units] jAZZ-MAN:
After put to radio new firmware (9853i 1024X600 800X480 1280X720 2019.6.21.zip) microphone work OK.

... but ROOT is gone. ;-(

Any idea how i get ROOT witch working microphone?
[FYT Android Head Units] satyavel:
Hi Robert,

I didn't get any reply about my question and was afraid to proceed to root it and end up bricking the HU. If you by any chance able to root it, please let me know.

Cheers,

Satya
[FYT Android Head Units] hawkjm73:
If you want to use the root zip instead of modifying the boot image yourself, you have to match up the root zip and the firmware you are using. The original post doesn't have the most recent. Look through the rest of the posts in the thread. Folks have been posting the root zips as Joying releases firmware. They generally specify the model and the firmware date the zip applies to. Keep in mind, though, the more recent firmwares have trouble with sounds for Google dependent functions. Google Play Music, for example, will not work at all with root at the moment. Try getting a matching firmware and root zip and see if your microphone works as expected. Otherwise, see if you can mod what you need to, then revert to an unrooted state.
[FYT Android Head Units] jAZZ-MAN:
Thank you for Your response.

I went to work today and the microphone did not work again on the original software.

I will do as You wrote and I will informYou about the results.
[FYT Android Head Units] Crimson Flam3s:
Hi guys, I did a Joying update for my unbranded 9853i headunit and now have the yellow bar overlay "ui and mcu does not match"

I have already rooted the unit, can I get rid of this message somehow with root?

I saw a fix regarding modifying a value "ro.build.fytmanufacturer line in fyt.prop " but that file doesn't even exist in the system/app folder and doesn't seem to be anywhere else.
[FYT Android Head Units] raffaele892019:
Root sp9853i

Hi guys. I purchased the android car radio award from prelingcar. I would like to root the device. can I use the joying one? Below is a list of product features.

Cpu sp_9853i_1h10_vmm

Ram 4gb

Rom 32gb

Mcu ts9v.4.3-156-411-a46181-190529

please help me as I will be forced otherwise to install my standard car radio again having various problems with the audio.

thank you so much
[FYT Android Head Units] helmi_zr1:
hello

Hi dear

have you fix the issue ?
[FYT Android Head Units] Crimson Flam3s:
Yes, I messaged the seller I purchased it from and they sent me the original custom firmware to reinstall.

Wasn't able to fix the Joying one.
[FYT Android Head Units] helmi_zr1:
sir

could you please share the frimwear for your unit with me it may can help me too
[FYT Android Head Units] runehasa:
Does anyone have a sure fire way to bring back google voice text to speech after installing root. Everything else seems to be working and tried applying the fix a few posts back but no luck. I mainly just want voice guidance back in both Waze and google maps. I did what I needed to with root which was to set the dpi to 161 so I dont really need it anymore if there is a way to remove it and regain voice. I tried running the uninstaller within the root program but it didnt bring it back. Only restoring the firmware which reverted my changes brought it back.
[FYT Android Head Units] Crimson Flam3s:
Do you have a link to the specific headunit you have?

I have
[FYT Android Head Units] helmi_zr1:
Sir

MCU version:

2018-07-19 16:02:17 SP_(R68)_26_C26DR68_6026D_CAN(ALL)_NEWLAP

here the unit

https://www.aliexpress.com/item/3295...3de94c4d0IEKFh

kindly support
[FYT Android Head Units] runehasa:
Tried contacting Joying support to ask them to natively change the DPI for these head units to 161. This would bring voice dialing without having to root breaking everything else in the process
[FYT Android Head Units] PsychoMcSatan:
I had the same issue, but found that Magisk didn't fully uninstall. Check if you have Magisk Manager still listed under your apps. If so, start it up. For me it said it needed to download some more files to continue the uninstall process, which it did, rebooted, and then it was truly gone, and Google Maps was talking to me again.
[FYT Android Head Units] Crimson Flam3s:
What broke after rooting the headunit?

---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------

This is a px5 unit, while I have the 9853i. It might get bricked if you custom install it.
[FYT Android Head Units] KillerFu:
Figured it out... They should list what update they are on some where... besides a picture.
[Other SmartWatches] simonsmh:
Guys who are using TicWatch C2:

I dumped all the image from the device which are required for the OTA in case someone need it, Chinese version only, PWDS.190212.008.

Chinese version only, PWDS.190212.008 and PWDS.190618.001.A1.

https://mega.nz/#F!4kE2zAoS!uoi8jZ0y_7k0dXJccd9LmA

Anyone who own a global version could also share with it here to save other's device.

Required images for OTA:

aboot.img

cmnlib.img

modem.img

rpm.img

tz.img

boot.img

keymaster.img

recovery.img

sbl1.img

system.img

vendor.img

How to flash:

0. extract the zip file.

1. fastboot flash <image_name> <image_name>.img
[Other SmartWatches] Syndor:
I hope someone can share the international version, thanks guys
[Other SmartWatches] Syndor:
THIS IS MY TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001

https://www.mediafire.com/file/c6cuj...CKUPS.rar/file

This is my stock copy, I backed up everything TWRP allowed me to, just in case.

I installed the Ticwatch C2 rom, and I'm getting pretty solid battery life, but I'm not able to update to PIE, since I get an error as I mentioned, even when I flash back to stock, and lock the bootloader, so we're confined to custom roms from now on, or to TWRP backups of PIE.

So if someone has a TWRP, or a stock firmware backup of some sort of PIE for the ticwatch c2, that would be amazing.
[Other SmartWatches] simonsmh:
That might because the OTA script check more than only boot, system or vendor partition, and that leads to the exception.
[Other SmartWatches] Syndor:
What else does it check for, can we fix it ?
[Other SmartWatches] simonsmh:
You should be able to get the error report and see which partition doesn't pass verification from the recovery log. Also I updated the list of images that OTA required.
[Other SmartWatches] maximzinchuk:
Link that you provided is not working, could you fix it please? My watch do not want to boot with custom fw :(
[Other SmartWatches] Syndor:
I'll reupload when I get home

---------- Post added at 05:57 PM ---------- Previous post was at 05:06 PM ----------

Here you go:

TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001

https://mega.nz/#!WthVGKIa!XoeOFs0HK28D4SdHJGpPxXO3xytf-djePefB4DvwAsc
[Other SmartWatches] Syndor:
Anyone has a backup of the international version yet? one that would allow me to OTA?
[Other SmartWatches] simonsmh:
Well you guys plz remember to backup before trying custom roms
[Other SmartWatches] V_tunes:
Anyone can share how to dump image ? I own a Chinese ver C2, and want to do a backup before flashing international FW.

THX
[Other SmartWatches] simonsmh:
I use dd under TWRP recovery. You can also use TWRP backup.

As some users report incompatible of international build. Also there is no Pie rom for our global C2.

Can you read Chinese? If you just want to use Google play, use this:

https://github.com/simonsmh/ticwatch-googleify
[Other SmartWatches] V_tunes:
Yes, I'm Chinese. So the things I can do is unlock BL first, then boot into TWRP to backup, flash TWRP, Magisk & install the github module, right ?

Thanks again.
[Other SmartWatches] simonsmh:
Yes exactly.
[Other SmartWatches] V_tunes:
Hi I tried to install the module from MagiskManager on the watch, it says not a Magisk module.
[Other SmartWatches] simonsmh:
解压后，将里面的文件用zip
[Other SmartWatches] V_tunes:
感谢回复，我安装这个module后重启，手表无法进行操作，不能打开应用列表，下滑也反应，感觉几秒手表会自己闪一下。:(
[Other SmartWatches] simonsmh:
[No message]
[Other SmartWatches] simonsmh:
你得重置手表重新配对

1. twrp双清

2. 刷magisk

3. 立即紧接着刷模块

4. 开机使用wear OS国际版配对
[Other SmartWatches] V_tunes:
感谢，弄好了。可以连接国际版wear os和上play store，但过了一会儿就不稳定了。4个边缘无法滑动，手表闪烁。
[Other SmartWatches] simonsmh:
deleted
[Other SmartWatches] simonsmh:
这是因为你不能在手表的小问商店安装wear os中国版程序更新。重置后禁用小问商店自动更新并只在play商店更新就可以了。
[Other SmartWatches] V_tunes:
好的，我再试试。

Update: 感谢！现在都正常了。
[Other SmartWatches] Foahhc:
如何在表上安装magisk模块？我尝试在magiskmanager上面点了“+”结果提示“”没有可处理此操作的应用“
[Other SmartWatches] game #1:
guys, can we talk English?

I got c2 Chinese and want to go international. thanks

upd. I have installed global rom from this thread by syndor.

1st. unlock bootloader

2nd. boot to twrp

3rd. restore rom by syndor.

4th. install magisk.

ps. haven't tried to update via ota.

pps. system updates don't install. red sign appears after rebooting and beginning to update the system. after power button reboot works fine except nfc. nfc setting doesn't show up.

after reinstalling magisk via twrp nfc came back
[Other SmartWatches] haivp3010:
Is this safe to flash from oreo international? My watch is the Chinese version but the seller flashed the international oreo rom before selling it to me. I really want to get the Pie update but OTA is not working and I couldn't find anyone sharing stock oreo for Chinese version. Janjan's rom is for international version only :(
[Other SmartWatches] V_tunes:
Hello guys, I got an OTA update notification these days, but I can't install it. I owned a Ticwatch C2 Chinese ver with Chinese ROM included google play store patch. I switch to original TicStore and disable google play store. There's nothing happens, no update at all.

C2 current status: system: H with Feb security patch (PWDS.190212.008)

Here is the OTA file link: https://drive.google.com/file/d/1QOQDQh7IqT3q95xeoKlo8G3A3MVp8vvK/view?usp=sharing
[Other SmartWatches] LeoBounce:
I spent the whole day trying to install Magisk module. WHen I try to add module in magisk on my watch - it tells me that: No application can handle this action. I can't find any working file manager for Ticwatch to be able to bypass this step. How can I solve this problem?
[Other SmartWatches] game #1:
you cant install magisk in regular way.

you need to root it and install via twrp.
[Other SmartWatches] nchmaster:
I need Ticwatch C2 stock rom global version :(
[Other SmartWatches] ChariotK:
I have an International Ticwatch C2. Can I flash the Chinese dump to get the Chinese framework and the Chinese AppStore?
[Other SmartWatches] nchmaster:
Can you share me the stock image for C2 global version
[Other SmartWatches] FMLIFE:
你好，我在刷完magisk以后在刷模块的时候提示错误：updater process ended with ERROR:1 Error installing zip file，请问这个问题遇到过吗，有没有什么建议，twrp版本不对？
[Samsung Galaxy S10+ Questions & Answers] citytrader:
I could suggest you to use BubbleUpnp + MXPlayer, I'm using it without any problems with my S10+ and my tablet, you will do all using DLNA without issues.
[Samsung Galaxy S10+ Questions & Answers] sephiroth_vg:
Thanks for the suggestion. I just tried it out Estrong -> Bubbleupnp -> Mxplayer pro but it still crashes in 10 minutes!
[Samsung Galaxy S10+ Questions & Answers] citytrader:
I don't know what you mean with " Estrong ", but I can watch a complete movie perfectly without issues, maybe you should do a factory reset
[Samsung Galaxy S10+ Questions & Answers] sephiroth_vg:
Estrong is a file explorer! How are you accessing your network files without it? :o