yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] julien_blanche:
I already wrote detailed how to update on above post, delete all downloaded firmwares on your computer, download below two firmware's and start from scratch;

https://drive.google.com/file/d/18mcocVcmqRL453Tu5oG8SizGERD1TWpq/view (twipe_all) change in config file-21/06/2018

https://drive.google.com/file/d/1_Hfn-vFb0MDqeWOzqC9Jn3JI2HRj3F_0/view (twipe_data) don't change in config file-14/08/2019

it will work for sure..
[FYT Android Head Units] DustoMan:
Hey [MENTION=2287433]julien_blanche[/MENTION] wanted to let you know that this small update worked perfect on my unit. It's the JY-UO138N4G. Update prompt popped up, flashed then upon reboot the front panel lights switched colors and I could change them again. [emoji106]
[FYT Android Head Units] akuma148:
Is Google voice feedback working for anybody with the newest update with the led light fix, after root? I read in the earlier posts that it was working after root, but mine isn't and I have Google Assistant installed.
[FYT Android Head Units] vii:
Does any one know that what chips model of Rohm dsp installed ?
[FYT Android Head Units] elabjer:
Julien, could I bother you to check if you're able to set lights to 100% red colour? I'm really reluctant to go thru the whole downgrade process and reinstall again if it's not working as it should. Thanks
[FYT Android Head Units] seb21:
I was unable to set pure red in my unit .

Red 255 , blue and green about 10 , but maybe i have no skill to set specific point on small color wheel with my finger.
[FYT Android Head Units] elabjer:
Lol, yeah those colorwheel skills are in short supply lately :p

This setting of RGB [MENTION=8690982]255[/MENTION],10,10 seems the same as prior to "fix", but alas - do LEDs light up really red, or are they more pinkish?
[FYT Android Head Units] akuma148:
I can confirm that 255, 10, 10 or something close to that (I think mine was 255, 12, 10) is the same as the previous Red. Just don't use the premade "Red" button or else it will be pink.
[FYT Android Head Units] c0rnelone:
Thanks, it worked.

Now sometimes im facing reboots when using zlink. That could be my USB connection that is no very stable.

Does anyone use Head Unit Reloaded? I tried but the screen its just black. I have the video with brake deactivated. That is the last thing that i need to be working for get rid of the USB cable. HUR never worked for me, its not something of this update.
[FYT Android Head Units] julien_blanche:
It says 255.13.8 but looks regular red to me that i could not notice any difference.
[FYT Android Head Units] SpoonerPS3:
I've been using it lately and is working good. I remember something in the settings like "software decoder" that you should enable if you have black screen.
[FYT Android Head Units] dfal47:
Anyone but me getting jitter on USB audio?

Also is there a work around or fix for the volume slider not controlling audio volume on USB?
[FYT Android Head Units] Guyzer73:
Hi there,

Finally getting the stereo sorted, however, I have a couple of niggles that I can't seem to resolve:

1. SWC are programmed but randomly drop and need reprogramming...

2. The screen doesn't dim when the lights are on...

The matter with the SWC I'm at a loss at, and assume it's a problem with the clock spring which I'll get checked. But could it be something else??

For the screen brightness, I just can't find the setting, or at least the English menu descriptions don't help. Could someone point me in the right direction please??

Finally, is there an option to select what programme open automatically when waking from deep sleep?? Currently, I find that if Waze (designated Navi App) is open when the HU goes to sleep it opens automatically, as well as the last used media app, usually Google Play Music. What I would like or hope there is a setting is to be able to select if only System Apps (Radio) open or System and 3rd party Apps open. I also don't want Waze or other programmes opening from deep sleep, only a media app.

Am I missing something in the settings menu or is this not possible??

Cheers

Guy
[FYT Android Head Units] c0rnelone:
Today I rooted the HU and install HUR and activated software decoding. It did something more than before, it started to blink between white and black. But definitely was not working.

I have a non rooted oneplus 6 and i activated start unit server.

Maybe i will take a log and send it to the developer.
[FYT Android Head Units] edcam33:
Can someone be so kind and enplane how to do a twipe_all in config file and then with twipe_data in config file.
[FYT Android Head Units] surfer63:
HWGet_info.apk: Is my XYZ unit compatible with a Joying?

Cross posting over several threads (sorry).

We regularly see questions like:

Is my unnamed/some brand unit compatible with the Joyings?

Can I use the Joying firmware to flash my unit?

I have some brand/unnamed Intel Sofia 3GR / Rockchip PX5 / Intel 9853i unit. Can I .....?

etc.

Sometimes with pictures of system info or details about MCU/hardware/etc/ which might not be so informative as they think.

For that reason I made a quick & dirty apk HWGet_info.apk that does exactly this: Check whether it is a FYT unit or not.

You can also see it in my signature under my posts: " Is my "some brand"/unnamed unit compatible with Joying (rooting)/JET-apk? Use the HWGet_info.apk."

So to all regular readers and experienced users: If you see this question, simply give them the link and ask them to post the resulting zip (and a slightly experienced user can see for him/herself).
[FYT Android Head Units] julien_blanche:
twipe_data: option comes as default with firmware updates and it should be used always if there is no any issue exist on system, it basically updates current applications without wiping your app data and prevents data losing for example: it it being installed like your iphone or android update without any app data loss

twipe_all: options should be used if you are experiencing any unstable situation with applications or abnormal behavior and will erase your app data

for instance; if you use twipe_all option when installing 14/08 update you will lose zlink app hence 14/08 update contains only zlink update package not full standalone installer

hope it helps..

cheers.
[FYT Android Head Units] Aadieu:
More intel?

How very disappointing.

Imho go cheap with Mediatek or go big and good with Qualcomm Snapdragon or Samsung Exynos

PS it really is a sad, sad little chip for junky 3rd world economy smartphones. With known heat issues and prehistoric benchmarks.
[FYT Android Head Units] le_p:
For clarification, should the command be entered in the "config.txt" or "updatecfg.txt" file? Thanks
[FYT Android Head Units] surfer63:
It should be in the updatecfg.txt (hence the name of the file).

The config.txt gives you the ability to add/change properties.

=================================================

In relation to the config.txt and setting properties:

Currently the 9853i units are delivered as "user" builds instead of "userdebug" builds. This reduces quite some options like for instance the use of adb, be it over usb or tcpip.

So what if you would add the following to the config.txt and then flash the unit:

persist.adb.tcp.port=5555
ro.build.type=userdebug

Would it be more customizable and would it allow adb over tcpip? After all the adb daemon is simply part of the system.
[FYT Android Head Units] julien_blanche:
Is it just a theory or would it be possible to convert system to userdebug build by changing just a command ? I guess nobody knows before try. If i have time will try it.
[FYT Android Head Units] yzf750:
And I paid 285 bucks for mine off joyings ebay store. But guess what...it plays radio, has 4g internet with my sim in it, responds to all my google voice commands, plays mp3s, has an ok dsp system, integrates awesom with my oem backup camera and maybe...just maybe needs a reboot once a month. whats your point? Should I go pay a 1000 or so for an alpine or other unit that doesn't do 40% of what I can make this one do. :) My last sofia joying went almost 3 years in my car too.
[FYT Android Head Units] surfer63:
I do not know either. Probably it is also compiled into the kernel. In that case it would not work (but I can't try myself).
[FYT Android Head Units] kpitao:
Can you tell us about this "American Mental Box" ; model number? brand? where to get one/

Thanks
[FYT Android Head Units] surfer63:
Hi Aadieu (or how should I call you this time ;) ?)

How is your "RFC / Feeler: AOSP custom car radio" project going?
[FYT Android Head Units] rigattoni:
My mother always said: "Don´t feed the troll!"
[FYT Android Head Units] spiker88:
Got it directly from joying. See this post and the responses

https://xdaforums.com/showpost.php?p=80157681&postcount=986
[FYT Android Head Units] bambapin:
Just a guess... but it won't be that "Mental Box" is a typo of Joying and they actually wanted to say "Metal Box" (the case)?
[FYT Android Head Units] elabjer:
sorry, missed your post previously.. I installed dual heatsinks w/ Noctua fans, same as Theo164 describes on Pg 53. It's VERY effective, even with fans running at reduced RPM (for nearly completely silent operation.. I used Noctua's bundled "low-noise adapters"). The unit runs 20-30 degrees cooler with fans, never exceeding 60 degrees even at constant full load.
[FYT Android Head Units] thierry34:
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------

[/COLOR]

No problem. Thanks for your answer. I buyed rads. I'll do the same Thing. But i have a 1 din. I'll take thé dremel ! :laugh::laugh::

finally, i test with only rads. Temp max with music, waze, torque 70 °max. I think it's good.

other point, i order 2 fan 40x40. this afternoon, the temperature was mounted to 78 degrés !!!!! with the rads mounted on the processor !! and waze had freezed ....
[FYT Android Head Units] breevesdc:
Hello. I have installed the latest firmware and rooted my unit successfully twice. On both occasions, after rooting and installing some extras (FYTweaker and Joying Extra Tools), two applications cannot access the internet... Chrome and Google. All other apps (including other Google apps) can access the internet just fine. And the unit otherwise behaves normally. The loss of internet connectivity only occurs after rooting and installing the tools.

The only reason I want to be rooted is to use the no-kill alteration so that apps are not killed when going into deep sleep. Does anyone know how I can do this without rooting? If not, can I do it without using the extra tools?

Thanks very much for your advice on this.

Brian
[FYT Android Head Units] surfer63:
FYTtweaker seems like something I made, but I never released that one. So are you sure? Or are you using FYTHWOnekey?

Anyway, both tools have nothing to do with internet or Chrome or Google.

So if any, it is either the nokill mod, which technically has nothing to do with internet either, at all, or the rooting, which also has nothing to do with internet.

Anyway, if you undo the rooting as also described in that "howto rooting" thread, the nokill mod will still remain on your system.

Although I still deliver the nokill mod, I'm absolutely not a fan of it and definitely do not use it myself. Why do you need it?
[FYT Android Head Units] Aadieu:
Wrong troll, dude.

I'm an authentic n00b with a week-old 10" Atoto in my Ford truck, a few Sammy tablets (tab 7.7 - loved until it started dying after heavy use and abuse, dropped dozens of times attacked by dogs etc; tab s 8.4 - loved, smashed up screen after dozens of drops and tired battery alas; tab s3 - hate, bulky, bad grip, crashy, st00pid 4:3 screen), and a drawerful of various degrees of dead cheapo phones. Make that dropped/stepped on cheapo phones, btw, not hardware/software issue dead. All them Blus, ZTEs, LGs, etc performed as advertised until getting destroyed by yours truly's own clumsiness

Researched those cheapo phones back in the day and found out that the Mediatek SOCs cost a whopping $3 / ea. For quite functional octacores with better power scaling and functionality than Intel crap.... if a $3 processor in a $70 phone in 2014 could get sh!t done (audio video navigation etc), surely the newer versions 5 years fresher can be quite satisfying too.

Their main barrier to US market back in the day was the wrong LTE bands (or no LTE) on most of em, which for head units is a bit less of an issue

And as to Qualcomm Snapdragons and Sammy Exynos, well, they whoop Intel like a redheaded stepchild....no further explanation needed
[FYT Android Head Units] breevesdc:
Hi Surfer. Thanks for the reply. I'm definitely using FYTweaker. Are you saying that it's not compatible with the 9853i units? I'm sorry for being such a noob. But I was confused on this point. The rooting works. The tweaker works to turn on the nokill mod. But at some point, only Chrome and Google lose the ability to access the internet. By the way, they work again for a while if you reboot the unit. But eventually they stop working again.

Why I need the nokill mod... I drive a lot and I don't like the way the apps get killed if I'm at a location for 15 minutes or more and return to my car. For example, if I program a route in Google Maps with 3 or 4 destinations, by the time I get back to my car after reaching the first destination, Google Maps has been killed and I have to program the next stop. So, I'm stuck programming them one by one when doing them all at the beginning would be easier. It's only one example of the inconvenience of the killall approach.

If I understand you correctly, I can root, use FYTweaker to activate the nokill mod, and then unroot. And any damage from rooting (if the rooting is what's breaking things) will be reversed. I'll give that a try. Thanks a lot for your response (and the great tools you've developed over the years).

Brian
[FYT Android Head Units] surfer63:
Now I get it. You are using XFYTtweaker with the builtin nokill functionality. That's the Xposed modules version. That one does not work on the 9853i as Xposed itself does not work on Android 8.1 Intels.

But also that one should not influence the internet behavior of Google and Chrome either. Especially not as it can't work on the 9853i.

You really have a strange issue

.
[FYT Android Head Units] tangcla:
Hey all, back from holidays. Is the 8.14 (back light fixed version) firmware still recommended to use, or should I stick with 6.12?
[FYT Android Head Units] breevesdc:
Perhaps I am associating 2 things that are not actually related. I have seen others posting to this thread that they lost the ability to load pages in Chrome without necessarily mentioning rooting or XFYTtweaker.

I will do some testing over the weekend. But given that I'm running the latest ROM for weeks now with no issue, I doubt it's related to the ROM. I'm guessing that it's the way I'm rooting. I will report back on my test results. Thanks!

Brian
[FYT Android Head Units] le_p:
Yes, this version is working for me (ie, fixes the light issue and appears to be stable), but I've only been on this version for ~3 days.
[FYT Android Head Units] CZ Eddie:
Has anyone returned their LCD screen to Joying for warranty replacement?

Was it a quick turnaround or did you have to wait forever?

My screen was not "as described" as far as logo goes.

And the left-side buttons to press for volume, back, home, etc, are all a little off.

So I have to press like a mad-man to get the buttons to register my button-press.

Fixing to pack up the LCD and send it to Joying.

Really don't want to be without a screen for 2-3 weeks though.

I'm also disappointed with brightness and hopeful a new screen might somehow be brighter.
[FYT Android Head Units] elabjer:
oh man, I've updated to 8-14 again and it's the same BS pinkish colour ?

my unit is JY-UO135N4GS, the one w/ hardware push-buttons. no way to set the LED backlight to red. I'll try to find out where this setting gets written on the unit and change it manually.. has anybody any idea how to tackle this? is there any "file change observer" app, or method in general, that would help me pinpoint the config file this "lantern setting" gets written to?

EDIT: upon updating and reboot, my LCD colors became completely washed-out, much more than they were on my 1st update to 8-14.. it looked truly horrible. But then I went into factory settings and found that screen settings (where you can basically adjust gamma) got totally mangled up (sliders showed "default" positions, but when I moved them, the colour rapidly changed.. seems slider positions aren't reflecting the actual values set). I got my LCD colours back to normal when I adjusted the VCOM setting to 30.
[FYT Android Head Units] julien_blanche:
I have replaced my lcd screen due to capacitive touch sensor got broken. You can pay them $100 for deposit and have them ship the lcd to you, once you got the product then you can ship yours to them. Finally when they got your lcd they refund your $100 deposit back to you. That process will take depends on shipping companies however you get your lcd and your money in the end.

Capacitive touch panels have lower sensitivity in joying products when you compare them with other mtcd/e units and there is nothing we can do about it.

How did your update ? and have you reset color settings by pressing white ellipse arrow and tried the set color with your finger manually ? I am afraid that side panel color setting stored in mcu file and nobody know how to edit that file, there is a way to edit for mtcd/e units mcu but not joying mcu files yet.. For the last resort you can try to set things up from scratch if you end up dead end. Nobody but you have this problem after update by the way..
[FYT Android Head Units] elabjer:
Down the Joying rabbit hole..

I had free time today and decided to tackle this button illumination to the full extent of my abilities. First I tried detecting where the RGB setting gets stored in shell, but I couldn't get that work, so I did the next best thing - I decompiled the com.syu.settings app. Having seen what I've seen there I wish I wouldn't have, LOL

I tracked the saving of the config thru the classes and finally found it's dumped as a json in data/data/com.syu.settings/shared_prefs/CMSettings.xml file. After I figured out how the bit-shifting of the colour value works I successfully changed it to a value that would get read back as 255,0,0, but to no avail - I could not get the system app to refresh the LED to this "fixed" value. If I toggled anything in the colour wheel dialog it would revert back to the same 255,11,12 value at the very perimeter of the colour wheel.

By further studying disassembled code I realized they've programmed the whole colour selection logic upside-down.. instead of representing the underlying RGB value on the colour wheel it is actually the wheel itself, and the selector's xy coordinate, that "drives" RGB values. I looked for the colour wheel drawable in resources and sure enough - it's a png that doesn't have 255,0,0 at the very perimiter. So their code actually works, despite how moronic it is ?

Seems that the only fix for me would be to simply replace the colour-wheel with a corrected version.. I did, but I can't get the recompiled version to work. Is it because it's a system app and I don't have the correct key to sign it? Can someone provide any insight into this? How can I decompile and recompile com.syu.settings apk to work? Maybe [MENTION=2550900]surfer63[/MENTION] ?

EDIT: final LOL - I just figured out that if I set the colour selector at the very perimeter, getting RGB 255,11,12 - which is pale/pinkish red, then quickly toggle the AUTO button, I get a proper 255,0,0 red button backlight. The only problem is - it doesn't survive a reboot. It reverts to the damn pinkish red. FML

I doubt that. There's nothing unusual about the way I perform an update. It works fine for me in 6-21, but not in 8-14. Did the upgrade/downgrade twice now. No luck. Besides - its pretty obvious it can't work as it should considering the way they implemented this.. the colour wheel bitmap they sample to retrieve the RGB value doesn't have a 255,0,0 pixel at the perimeter.
[FYT Android Head Units] elabjer:
Yes, I used jadx-gui to get readable java code, but in the end I didn't make any changes to the code - only replaced a single resource asset (the colour wheel png)

I installed the framework-res, of course.

This might be the culprit. I didn't use the apktool in CLI directly, but a GUI (EasyAPK Tool). I suspect it doesn't use the -c parameter.

What I ended up doing is first a wipe_all downgrade to the April firmware, to get the old MCU version back, then upgrade to 6-21 and then to a modified 8-14, where I removed the MCU update binary and replaced com.syu.settings with 6-21 version. All seems to be working perfectly (although I haven't had time to thoroughly test it yet).. essentially I've got the 8-14 ROM w/ 6-21 MCU and settings app. And a proper red button LED colour ?
[FYT Android Head Units] seb21:
You don't need to recompile the whole apk. Open it (do not unpack it) with zip and replace "set_rgb.png" with your version.

When you copy back the setting.apk to device you will need to check the permissions. Make sure that executable bit is set.
[FYT Android Head Units] Guyzer73:
Morning All,

In parallel to having emailed Joying help desk, I thought I'd ask here also as it may be quicker :D

Basically, whenever the HU boots loads from deep sleep the HU automatically opens the latest Media App and now also the latest other App that I had open, in most cases this is HUR. Is there a way to stop this? I've checked the settings and once again can't find a suitable setting....

Beginning to regret getting this HU, settings are so confusing and sometimes duplicated in different sections??? Plus some basics from the likes of Seicane are sadly missing :mad: Oh well better get used to it...

Cheers for any tips.

Guy
[FYT Android Head Units] julien_blanche:
Replaced color wheel only and it worked, running latest firmware along with the latest mcu.
[FYT Android Head Units] elabjer:
so, you just replaced set_rgb.png in com.syu.settings, as [MENTION=9736252]seb21[/MENTION] suggested?
[FYT Android Head Units] julien_blanche:
Yes, unzip the settings.apk with apktool and replace the png file (be careful with the resolution) then zip it again and place the apk file in oem/...settings/ folder and set the file permission rw-r-r.
[FYT Android Head Units] breevesdc:
Hi. A quick update. I rooted on Friday. The procedure I used to root my device was to put the lsec6521update file and the 6521_1.zip file attached to this post on an empty USB stick. I plugged it in. It detected and installed the update rooting the device. After rooting, Chrome worked fine on Friday and part of Saturday. But today, it could not access the internet until I rebooted the unit. All other applications could still access the internet just fine. So, it was exactly the same behavior as before. But this time, I did not install any tools after rooting. So, this seems to be the result of the rooting itself.

I'd like to install FYTweaker, install the nokill mod and then unroot. I'm hoping that this will get rid of the Chrome internet access issue. But I'm not completely clear on how to unroot. I've read through many forum posts on this topic and I'm still not clear on the procedure. Can anyone point me to the right instructions on how to unroot?

Thanks very much!

Brian
[FYT Android Head Units] seb21:
Open Magisk Manager ,tap the “uninstall” button at the bottom of the home screen.You will be greeted with the option to “restore stock,” “complete uninstall,” or cancel the procedure. To remove Magisk and all modules, tap “complete uninstall".
[FYT Android Head Units] breevesdc:
Thanks very much! I will try that.

Brian
[FYT Android Head Units] marcus82:
Hi guys, does anyone know the password for developer options?
[FYT Android Head Units] le_p:
Try 3368
[FYT Android Head Units] marcus82:
thanks I'll try
[FYT Android Head Units] marcus82:
It doesn't work

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] julien_blanche:
there is no password for developer options, available passwords as follows;

3368 for settings

8086 home launcher

5768 menu backlight