yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] nFiniti:
No. As far as I know from reading more about it on here and other places, Nobody has anything higher than Android 10 due to US Sanctions. Apps like Aida64 and CPU-Z are no longer reliable for gathering "real" information about such devices. Use a Terminal or ADB Shell and type the command "getprop | grep build.version.release"

Right now for support, I think a unit like a Dasaita is going to have the best aftermarket support since there is a very nice modded rom for them available.

Unfortunately dead links. I'm gonna PM You anyway. Fingers crossed.
[Android Head-Units] Squuiid:
Ah, my bad. That's annoying.
[Android Head-Units] CCJ22:
haven't attempted yet so I hope it does work
[Android Head-Units] CCJ22:
- Haven't tried yet and I agree. I am not hopeful.

-Before it didn't give two options (app info / split screen) so when you're driving at 65mph it use to be much easier to jump into split screen. Now you have to take your eyes off the road for longer.
[Android Head-Units] CCJ22:
I made a video

I have tons of video on Joying HU's on my channel.
[Android Head-Units] CCJ22:
Whoa, I didn't know this. I'd love to go back to the Dec firmware.
[Android Head-Units] CCJ22:
Would love to downgrade firmware. How does one roll back?
[Android Head-Units] nFiniti:
I tried asking Joying for the previous released update from the 1/06/24 for the 1280x720 screen. They wanted me to show a screenshot of my current update so They can determine the best update for me. So that means they wouldn't when they find out I'm on the newest update. I just told them I wanted the one before, I do not want the most recent one due to all the bugs. They responded that there was a bigger bug with the previous and that the file has been deleted.

Personally I haven't even tried messing with anything since flashing the rooted update over to prove it works, and ran a few terminal commands to verify its truly Android 10. It wont leave my bench until its running perfect for what I require to be perfect.
[Android Head-Units] nFiniti:
I honestly never seen that button on the top right corner. I've always just accessed split screen the normal android way. I didn't even use the device when I got it before updating it to the Glitch Update.
[Android Head-Units] CCJ22:
I think you would have preferred it.

It felt faster using split screen that way.

I'm working on a tasker automation that will let me hit a steering wheel button and auto go into split screen with predefined apps for the left and right side of the split screen.

This will save me a couple of seconds of fumbling around with my eyes off the road
[Android Head-Units] nFiniti:
That would be nice. I have too many buttons on my wheel that idk what to do with.
[Android Head-Units] nguyentt:
Sorry if I am doing this post incorrectly. I just joined to see if I could get help fixing a problem I have had with the qc 6125 chip android 12 Head unit (1280x800, 8gb/128gb with the knob) with the latest january 2024 firmware installed. I have it in a 2015 toyota highlander. Although the units fahrenheit, miles etc were able to be selected in the unit, It is in kilometers in the dashboard of the car, and I can't seem to change it. Does anyone have a similar problem? And has there been a fix?
[Android Head-Units] Squuiid:
Joying dashboard (Launcher) is garbage. There is no fix to get that to display Miles that I know of.
[Android Head-Units] nFiniti:
Using AppManager from the F-Droid repository will let you disable any app via root without removing it. I was going to try last night but fell asleep. I'll report back this evening.
[Android Head-Units] nguyentt:
It isn’t the launcher that I have the problem. That actually shows miles with the newesr firmware. It somehow is screwing up the display on the car’s physical dashboard where the odo reading is. I wonder if they fix the the carinfo app- that could fix the issue. Could be that it needs a canbus update. Do you know if there is an alternative to that app ?or if an alternatives come with different launchers ?
[Android Head-Units] Coatezy:
Did you get to the bottom of this? My car (2010 Saab 95) has a Hardon Kardon amp and was previously using a level converter with the high level outputs. I had some background noise like in your video which I could dial out using the level converter but not ideal, so I decided to give the RCA’s a go and ditch the level controller but I’m still getting the same noise. I’ve tried grounding the RCA’s to the chassis and GLI’s but still no luck.

If I turn on noise reduction on in the system factory settings the background noise goes until you begin playing a source and then it comes back until the source is stopped again. Interestingly when noise reduction is active and the background noise is not there the annoying system beep (if enabled) is very quiet so I’m assuming this setting is adjusting the units gain or something like that.

Spent ages 3d printing a facia adaptor to get this to fit perfectly so determined to get the sound right too. 😅
[Android Head-Units] nFiniti:
Disabling the Joying BT App via App Manager didn't have any positive effect. Just lost the Joying BT App lol. Still wont connect to any of my devices.
[Android Head-Units] McFlypants:
How to Connect the device to a Computer and use Fastboot? My device can't be found.

I got the boot.img and want to root it.
[Android Head-Units] nFiniti:
In System Settings you need to click the 3 dots on the right corner and change from Host to Device. You also need a Male USB A to Male USB A Cable (Both ends are USB A) and you need to open the top lid of the device to be able to press the two buttons on the mainboard.

If you are trying to root a 1280 device, just use the file I shared along with the entire Root How-To Instructions.

Link to post with updated root instructions: https://xdaforums.com/t/official-20...6125-android-12.4619495/page-17#post-89393607
[Android Head-Units] nFiniti:
So, I used F-Droid to download AppManager and via Root, disabled the Joying BT App. Well it didn't fully disable the Joying BT App. It left the BT Music Ability and the same window pops up when its disabled but less features like anything related to phone calls. It keeps the connectivity menu and BT Music tab but nothing phone related. But for some reason I cannot re enable it and cannot uninstall AppManager easily so I'm resetting the device. AppManager installs like a system app and it tries to take on App Installation (intent) and doesn't work. So it can be a very useful tool but don't ever let it open an app youre trying to install or open a zip file. It will fail every time, unless I'm doing something wrong.
[Android Head-Units] jm001:
Anyone have prior firmware

Release? I would love to try to see if it fixes the Blu tooth issue.
[Android Head-Units] Squuiid:
I have the 1080p releases but not 720p.

If interested DM me your gmail address and can share.
[Android Head-Units] zgow:
Is there a way to adjust the width of the rear camera parking lines? My car is a compact but the lines are way narrower than they should be.
[Android Head-Units] redlikemethodz:
Anybody having an issue with no 4g after wake-up? Sometimes when the HU wakes up it doesn't recognize the sim card installed. I have to reboot the unit to fix this. Any suggestions?
[Android Head-Units] Pulpster:
Have had the same issue for months. Even rebooting HU did not work. This is purely

guess work, but the metal piece that holds the sim in place is very flimsy. I believe

this makes the contact between the sim and the circuit board very loose. Four days

ago I fashioned a sim shape with very light cardboard thicker than paper and thinner than

a cereal box. I placed the sim shaped cardboard on top of the sim card and gently used

the metal part to lock the sim card in place. It's only been 4 days of success, but this

is better than the previous months with spotty success. Give it a try. Hope it works for you.
[Android Head-Units] Coatezy:
Update on my interference issues, I plan on buying a Helix DSP Mini but wanted to ensure I defiantly get no interference from the Toslink output, so I grabbed a cheap £12 DAC and confirm the output is crystal clear. So now it’s time to drop £300 on a DSP.

On another note, has anyone found a tempered glass screen protector for the 9inch screen with the volume knob? The preinstalled protector have a few bubbles and it’s very soft, I can already see small lines in the areas I swipe the most. I may have to just grab a genesis protector and not get the side with the knob.
[Android Head-Units] Gonzo_Gravy:
I bought an I-pad matte tablet film and trimmed it down to fit. It is designed for drawing, but I am happy with it. I re-calibrated the touch after installation. It cuts down on glare by 75%.
[Android Head-Units] CCJ22:
Dang that sucks :(

@Squuiid even with the older firmware how does one roll back to the previous firmware? Is it as simple as installing the zip like you would for an "update"? Or does this require root?
[Android Head-Units] Darkoz61:
It's the same procedure as doing an update.
[Android Head-Units] CCJ22:
Dude. Legend. I'd love to go back to the old multiscreen method
[Android Head-Units] nFiniti:
I'd love to roll back to at least try. I've yet to install the radio because I been trying to get it setup how I want it and not getting far. Every chance I get I say something on the Android or Joying FB Groups directly To Joying telling them they need to produce a fix/update for the known issues before moving onto new devices. And I mean every chance I get. Anytime they make a post about their snapdragon device, I make sure to mention all the known issues including the Spyware. I tell their potential customers to look elsewhere for a snapdragon unit like the Dasaita because Joying refuses to accept their device has bugs. 🤞
[Android Head-Units] Flame Red:
I replaced a year old Dasaita because it had problems with BT and AA and getting AA to start was a crap shoot. They could not fix their bugs either. At least Dasaita did not lie and say they were running Android 12.

So I figured I would try Joying and they seem to be even less responsive to problems. But at least AA comes up each and every time with the Joying, unlike the Dasaita, and that is what is most important to me.
[Android Head-Units] marchnz:
Did you consider a genuine google sanctioned Android Auto unit? These greyboxes are not Android Auto.
[Android Head-Units] nFiniti:
The Dasaita has some pretty awesome aftermarket support here on XDADev. Thats what interests me. I would be less inclined to be interested in another device if BT was 100% functional. I could care less for Android Auto or Carplay. I would have bought a different unit if I only wanted to use that. My roommate has the most recent FYT Joying 10.1 and he has connectivity issues with the CarLink? App and his iPhone. He has to unconnect and reconnect bluetooth. And for some reason it forces the device to output a hotspot and forces the phone to connect to that hotspot or else it doesn't work? So, he had to get a service on the device just so his phone had data while using the fake CarPlay. I have tried Android Auto myself just to check it out. But my main goal is to NOT be dependent on my phone. I offroad a ton and I want to stop, get out of my Jeep with my phone to take pictures while music remains jamming out and my offroad navigation is still working and the only thing that's linked to my phone is phone calls. I have a 256gb USB SSD with all my FLAC Discographies and around 80gb of offline map data.

Anyway, I could accept not being able to fully mod the device like I want. Which I will do regardless. But I cannot Accept Bluetooth Functionality Loss. Everyone thought the FYT Units had connectivity issues, but most didn't know about the loophole. A Loophole that no longer exists. So, until Joying fixes this and releases an update to please the angry customers, I will continue to Karen it up with them.
[Android Head-Units] itsttime206:
Hi there,

Thanks a ton for the awesome step by step! I'm super excited! I am not sure where I am failing, but I use qfil to backup the boot. It saves as a BIN file. I transfer that file to internal, patch with magisk, then bring it back to the computer. I then turn off the head unit, reboot qfil, and reboot the headunit using the two button method. After "reading" the new/patched boot and closing the dialogue, qfil attempts to reboot the device. I then unplug it, boot it up, and it *still* will not show via magisk that the new boot is there. Am I missing something? Thank you!
[Android Head-Units] kwhilden:
Hi All, I have the 13.3" Joying on the Feb 1st firmware.

I can't get the 4G to work on AT&T in the USA. Does anyone know if AT&T cellular networks should work, and how?

I've tried several different SIM cards from AT&T for tablets, hotspots, and even phones. None of them work, or were even recognized by the headunit.

Perhaps there's something else wrong with my headunit. Any troubleshooting advice would be appreciated.

Thank you!
[Android Head-Units] rs200z:
New firmware dated 17 May 2024 has been released.

Joying Android 12.0 Qualcomm Snapdragon System Update

新建网页 1 Joying Android 12.0 Qualcomm Snapdragon System Update Note: * This update is only workable for the Android 12.0 QCM6125 Qualcomm Snapdragon System

www.joyingauto.com
[Android Head-Units] Squuiid:
Wonder what’s new. No release notes with this one.

I’m reluctant to try as I’m still on the December release and all works great.
[Android Head-Units] Flame Red:
Well I bit. Same old buggy Joying software. I created a backup on a blank formated USB stick, the shoved the upzipped upgrade on to the USB, and inserted it in the Joying. It proceeded with the upgrade, and it kind of indicated that the user backup was restored.

It rebooted, and it was back to factory defaults, and it did not restore any of my stuff, no wifi, no installed apps, no setting changes.

I could not notice any changes, so if there are any, perhaps they are minor. I reinstalled all the missing settings, and apps and it appears the same as the January release to me. Kind of reminds me of security patch that comes out monthly on phones with no feature enhancements. What a shocker.
[Android Head-Units] Darkoz61:
Judging from the file name it seems the update has something to do with Zlink (Apple Carplay/Android Auto)
[Android Head-Units] falciott:
I had a previous version of a Joying radio, and once, I contacted support about being able to move the parking lines horizontally since I had seen a Pioneer unit able to do that. They didn't have that option, but after a while, I uploaded a new update, and lo and behold, with that version I was able to move the lines horizontally, useful, in case the camera is not really centered, and the lines need to be corrected on the screen. I picked up the new Android 12 unit a few months ago, and I finally was able to hook up the reverse camera, and to my disappointment, this camera won't allow me to adjust the horizontal offset. I just contacted Joying support, which by the way responds with a maximum of 5 words at a time, and they said it's not a firmware issue, it's the new camera. First of all, I didn't even get the camera from them, they couldn't possibly know what I have, second ..it's the same camera I used with my previous Joying, before I changed to this unit. Has any of you noticed that problem, if you did have an older Joying unit? In those units it was called "horizontal offset" such setting is missing in the newer radios, and that was an extremely important setting. Between myself, and me recommending Joying to friends, I'd say collectively we've purchased about 10 units, but I have to admit, considering the lack of effort I've been receiving from Joying support lately, and I've contacted them a few times, next purchase might end up being a brand name, especially since I've seen some pretty nice floating screens from them as well.

Anyway, just venting at the apparent lack of care or effort I've received from this company, definitely a 180 degree turn from the Joying I knew a few years ago.
[Android Head-Units] itsttime206:
Hey gang,

I followed the root guide here but I appear to fail on the last step of flashing the boot image. When I reboot to magisk it still doesnt show it as installed.

Does anyone have a video of the root guide posted above? Or a modified firmware update I can install? I have the 9in screen with volume nob. Thanks a ton!
[Android Head-Units] zgow:
Yes, the inability to move the reverse parking lines is a huge downer. I was so much better at reverse parking with the stock head unit.
[Android Head-Units] nFiniti:
Since I'm on the buggy Jan6 Update, I'll play with it. I aint got a care in the world at this point! What else could Joying screw up?

On my post where I rewrote the root procedure, I also shared a Rooted Jan 6 Update. Just download it from my Google Drive. https://drive.google.com/file/d/1CqRBuayavQmua56v_OFLGl-7TZ_jVtxA/view?usp=drive_link

Unfortunately it is the Jan 6 Update however, But from what I've read up, the same bugs from before exist in Jan 6. Just a few extras added.
[Android Head-Units] nFiniti:
I have a spent a few minutes on the new update and I've only noticed one decent fix. The "calltohome" Spyware has been removed. Or at least it does not pop up continuously anymore. I've left the device on for a little bit without internet and it's not popping up.

Next, the Bluetooth. No fixes to Bluetooth have been made. As before, I still can only connect to a phone. 2 OBD2 Devices including my OBDX Pro VT programmer does not connect. The Xbox Wireless Controller doesn't connect. The Logitech BT Trackball and mouse and keyboard do not connect.

The update is labeled ZLink, and I don't use carplay or android auto because it's worthless on an android device. But I know others use it. Unlike the previous version, it now has an activation pop up asking you to connect to the internet. Similar to the previous bug on the Jan6 update. You can view settings but when you try to use it, it has this activation popup. I never was hit with this on the previous version. And I don't plan to connect it to the web just yet so I won't be able to test it out any further. The ZLink version is 5.4.18

I'm honestly feeling I missed my opportunity to return this horribly defective and overpriced paperweight.
[Android Head-Units] JeffPrest:
There are a lot of people complaining about the BT restrictions like yourself for keyboard mouse etc but my need is to get a bluetooth headset / intercom to connect? Purely for microphone and speaker. I want to put a joying unit on my motorbike and use my normal helmet bluetooth. There are a few motorcycle headunits on the market but they only have AA or Carplay capability. Does anyone know a way to connect a joying to helmet intercom with BT.
[Android Head-Units] nFiniti:
Joying last night lied to me saying that they strictly say on their ad that these devices DO NOT work with anything but Phones and THEIR OBD2 Devices. Nothing else. After arguing with them about their many lies trying to get them to send me a shipping label (lol fat chance). I combed every word on the page for the QCM6125 Devices and there is no mention of anything besides it doesn't work with OEM Bluetooth Camera's. They basically told me to get F****** and will not be giving me a shipping label, and If I wanted to return it I gotta pay for the return. They said the reason was because this isn't a quality issue, and its mentioned in their ad. Which it clearly isn't.

Joying Will NOT be fixing the Bluetooth Issues. Maybe if more people complained. But even then I don't believe Joying cares for their customers wishes. How hard is it to NOT restrict bluetooth? Their excuse was it will make other things not work. Which is BS because the FYT Joyings can connect to anything I want. IF you use the loophole and go directly to the Systems BT Settings and not use the Joyings app.

Anyway, I tried doing what youre talking about with the FYT Device I had before. It would connect but no audio and when it was connected it killed audio from the Device itself. Even disconnecting, audio wouldn't come back. Had to restart the device to get audio back.

You'd think Bluetooth 5.0 that they advertise wouldn't be soo restricted right? Joyings BT AVRCP is only set to Verson 1.3. Version 1.5+ would allow for sharing of detailed information like Album Art etc.
[Android Head-Units] JeffPrest:
I think i have a fix. Link is below. If my joying radio will not pair up directly with this bluetooth device wirelessly then ill use it as an external bluetooth transmitting device. Im going to connect it directly into the raido using the RCA line outs and external mic connections and then bluetooth from the device to my helmet intercom. Hopefully it works straight out of the box. I may even need to reverse feed the speakers and mic. Its all low pre amp so cant see it being an issue. $15 and $6 freight is worth a try.

TSA6016 - Bluetooth Audio Receiver with Microphone Input (Apt-X)
[Android Head-Units] nFiniti:
Thats a good idea. I used to use a Motorola device that did the same.
[Android Head-Units] ForgedBlade:
Shark Fin antenna connection

Has anyone hooked up the 4g connection to a Shark Fin antenna? The other components are straight forward but trying to find a model that supports their 4g dual antenna setup.

Tia,

F
[Android Head-Units] andmatts:
Hi,

Have any one tested a usb / Bluetooth dongle?
[Android Head-Units] itsttime206:
Thanj a

Thanks a ton!! I tried following the root steps, but it never would appear after the fact with the magisk app.

The update worked perfectly! That's exactly what I was looking for! However, after it showed a successful update, I installed magisk and it does not appear. Am I doing something wrong? I merely installed the update, then installed magisk.apk and SuperSU.apk just check status and both show unrooted )-:

I really appreciate the help on this! (-:
[Android Head-Units] nFiniti:
Someone posted up saying they have. But they never explained how. You can't just simply plug one in and it works, just like a PC you gotta be able to switch which devices are being used. I tried myself and couldn't get it figured out.

The Update I shared with the Root has Magisk already as its part of the process.
[Android Head-Units] itsttime206:
Would I have screwed it up if I was on newer software when I installed it? Or would that be irrelevant?

I can see how you utilized the lock screen in order to get the organic notification bar (that was pure brilliance by the way!!) So truly, the software installed for me. But for some reason magisk is not showing up in the process, nor is Torq pro (which I can see in the installation zip file). So its doing an odd partial install? 😅

I'm actually super stoked to get this installed, because the status bar mod alone (and expandable desktop) is super cool!! Thank you!
[Android Head-Units] itsttime206:
One other thing: after downloading the update again and running the update about 6 times, finally magisk does show up. However, I get the following error: "abnormal state".

Any insights here would be highly appreciated!
[Android Head-Units] nFiniti:
Its okay. It still functions. Its just telling you that Magisk isn't supported as a system app.

As for TP, It shouldn't be automatically installed. Its uninstalled APK is located in a folder in the storage. I think its called Owner or something like that.

Just so you know, This specific rooted update you applied is the Jan 6th update that someone else performed the Magisk Mod to. I had nothing to do with it except I'm resharing it on my Google Drive. Besides the Magisk Mod, its a completely stock Jan 6 rom.
[Android Head-Units] itsttime206:
That helps a ton! I got it working! Thanks a lot!

It previously did some pseudo update then, but I reset and its good now. I greatly appreciate the help and insights!