yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] skezza:
So when they talk about clock speeds above, they're simply talking about the ramping from the governor? Not actually pushing the clock speed above the stock kernel settings? That's even funnier then, in such a dumb way. Running a CPU at full clock speed all the time will more likely have a negative effect than a positive. It'll run hotter, all the time, which means any thermal throttling will be more likely to kick in. It'll wear out quicker, because 'science'. It'll also consume more power for absolutely no reason. Brilliant.

While all the other stuff you've put there is perfectly valid, you are only vindicating my point. It's a complete waste of time, so unless people are doing it out of curiosity, really what is the point? Overclocking for the sake of overclocking. It's like what all the gamer nerds used to do at college when I was about 18. I've probably come across in a bit of a bad way here, but I wasn't knocking the Sofia chipset at all, I was just making a point that these Joying units have a bit of a rep for burning up, in particular when they're stock with no additional cooling. Why the heck would you want to run the risk of burning it up? You may well be right about the PX5 running hot but this is where the manufacturer needs to be relied upon. I bought an Xtrons with a PX5 and the temps have been decent so far. 50 degrees C after a few hours of sat nav and Spotify. The highest I've seen it go is about 70 and that was on a very hot day after I had hammered SPMC on it and had it using nav as well. Perhaps Xtrons have got the cooling right or thought about it? Perhaps they've put an appropriate heat sink on. I don't think there's a fan. I know the rear of the device is used for cooling as well, so perhaps they have a pipe to carry the heat away, like in many desktop PC's? In reality, that's where much of the focus should be, rather than blagging ridiculous clock speeds and trying to get Android P on for 'reasons'. Manufacturers should be putting cooling apparatus on these devices to ensure they don't burn up. That's proper engineering, not making Android 9.0 run on a phone made in 2008. Xtrons claim they have thought about it, although I've not disassembled it and I won't be any time soon. All about faith.

These chips are ultimately designed to run warm, a bit like the Raspberry Pi.

PX5 Datasheet: http://opensource.rock-chips.com/images/6/60/Rockchip_RK3399_Datasheet_V1.6-20170301.pdf

Maximum operating temperature should be 80 ℃ with an absolute maximum junction temperature below 125℃. When you think about it, that's damned hot.

Sofia: https://en.wikichip.org/wiki/intel/atom_x3/x3-c3230rk

Again a maximum operating temp in the 80's. I would not expect any issues longterm with it running at 70 or below. However one of the users with a Joying head unit mentioned his Sofia was running at almost a constant 85 degrees and he was having to underclock it to get temperatures below that and maintain stability. That to me, is a bad design and is asking for problems.

So back to my original point, why would anyone want to overclock them when they're known to be problematic?
[FYT Android Head Units] Redbullssg:
Why govern lock? I simplified, because Viper.... If you don't, Viper does not perform well, it skips, pops, and when it is govern locked, "over clocked" it remedies...

If a newer rom ran Viper4android, I'd use it. If a newer custom Rom ran Viper4android without throttle locking it, I wouldn't bother. But I would however, still add active cooling, either way.

For me, the most important thing about my car stereo is the music, and these units sound like complete garbage without Viper4android.

So there's why, I already stated that, and that I have active cooling and have zero worries about over heating..... It almost never reaches over 55c.

And battery consumption? This isn't a phone, tablet, laptop, it's a car stereo......
[FYT Android Head Units] skezza:
I would suspect the quality of audio is dependent on the DSP chipset and while software makes some difference, the greatest impact will be the DSP amplifier circuitry. Older units had no DSP and had poor audio. We now have two fairly common DSP's, the TDA7851, a 48w Mosfet jobby, and the TDA7560 which 'on paper' is an inferior chipset but provide much better audio. Mine has the TDA7851 and the audio quality is excellent for the money. I EQ slightly in the stock EQ but no need for Viper whatsoever. No, it won't fool an audiophile, but then the money we're spending isn't really premium money for good quality audio.

Feel free to record a video of your unit sounding garbage so I can understand perhaps the need for Viper. Right now, there's limited scope for this in my eyes, however with a worse chipset I can see why it would be useful.

I never mentioned 'battery consumption'. I mentioned 'power consumption'. Quick physics lesson, 'Conservation of energy' : the total amount of energy in any isolated system is always constant. Energy can neither be created nor destroyed, only transferred from one form to another. Do you know what an alternator does? Clearly not, because you'd know that by running the device intentionally harder to draw more power, will mean the alternator is worked (slightly) harder and therefore you'll use more fuel, both powering the device and because alternators are less efficient the harder they're worked (google car alternator efficiency curve). GCSE Physics eh? I doubt the consumption will be greatly affected, but there will be a small reduction over time...
[FYT Android Head Units] surfer63:
Viper did run well on PX3 models, so CPU performance itself is absolutely not the issue. If it needs full speed on the Sofia's that simply means that "something" is wrong on the Intel side of things. We already know it is in the SYU/FYT modified kernel used on the intel models. Edit: Viper also works fine on the Malaysk custom ROMs for the PX5 MTCD/E models, and before that on the PX3 models on android 5, 6, and 8.

And just like Skezza is mentioning in his reply: I also mentioned multiple times before (and 5 minutes ago again in one of the PX5 threads): Viper does improve the sound, but it doesn't make it good. The AMP in the Joying is just of too low quality. There is a thread about replacing the current AMP chip with either the better version of the current chip, or the 100% compatible and pin-compatible Pioneer chip that delivers much better quality, OR use an external AMP with or without a USB-DAC.

After my holidays (in 4 days now) I will work on rooting my PX5. Then I will install viper4Android, not because I want to use it, but simply because I want to test whether it functions on the PX5 with the almost standard ARM AOSP kernel.

(and also: the EQ on the PX5 has more channels than the 3-channel one on the sofia. I also have the idea that it is doing a better job then on the Sofia. But I'm not an audiophile at all)
[FYT Android Head Units] D3LTA:
V4A ??

What is the issues with V4A?

i just recieved my JY-UN138N2 unit as warranty replacement for my older JY-UN138.

Have used V4A on my older unit for 2 years without any issues.. but can't seen to get V4A running on the Sofia unit....

Tried the new V4A 2.6.0.5 from XDA Labs but that version locks up on "driver install"

can someone fill me in on details? so i don't have to read 116 pages

Maybe i can help to find a way to make it work.
[FYT Android Head Units] skezza:
Am I right in thinking the Joying's still use a TDA 7380 4x30w jobby?

That chip is pretty ****ty really. 30w is a really poor output and with it being rated so low, you're sleep walking into problems at higher volumes. You'll be pushing it too hard. The Pioneer upgrade looks very much worthwhile and not the most complicated of tasks. I would recommend that to everyone. If you can't do it yourself, take it an electrician, it's fairly straightforward soldering that is. The TDA7851 however is a much improved chip. Good to see they're finally getting audio, voice, etc into a good place. Taken long enough ;)

Viper4Audio really won't be needed soon.
[FYT Android Head Units] PsychoMcSatan:
I think an even better solution is to simply use the RCA outs to an external amp. Way better quality even with an entry level amp and much easier to install than soldering in a new chip.

I just searched Amazon for 4-channel car amplifier and you can get ones rated at 400W as cheap as $40. Can't vouch for the quality, but no way it wouldn't sound better than an on-board chip.
[FYT Android Head Units] surfer63:
You better go for 40W at $80. :)

---------- Post added at 04:32 PM ---------- Previous post was at 04:26 PM ----------

In the Sofia models they use the TDA7388. I did not look at my PX5 chip yet. As mentioned: I'm not an audiophile, although I am a "musicophile" (did I just introduce a new word in the English language? :))
[FYT Android Head Units] skezza:
Very true.
[FYT Android Head Units] Redbullssg:
I am using the rca outs, it bypasses the amp chip, which in both cases sounded like crap. My system is amped, all high end, running off the RCA, which does not use the amp, but shares the crappy stock EQ.

Viper... I'm happy with Viper.. If there were a solution, I'd do it, but there isn't, so, Viper with locked clocking it is.

I could try to swap chips out, but I am amplifying my system, and even then, I'd have to use the crappy 3 channel EQ. I agree RCA outs should be, what these aren't... So what's my solution you guys are saying... I should learn to rewrite code, to alter what nobody else has seemed to figure out, swap out my chipset. I wish I could... I didn't buy this head to do all that... What I have now is working for me... It sounds amazing compared to the way it did on the stock amp and EQ, externally amped on the RCA on the crappy stock EQ. The only thing different is Viper. My system is running cooler that it was before with nothing even running. So what's the issue...

I can agree that the chipset sucks, the EQ sucks, the 6021 over heats, and gets way to hot... I can't write the code, I don't even know where I'd start. What I could do, was use this rom, Viper, active cooling, and now happy with it, with no worry of damage...
[FYT Android Head Units] Ford_OutLaw:
Any tips or tricks to get it to boot? I have it hooked up to a PSU in the house and once I see the first pink I start a timer for 1:30 after that the pink stays solid. I then remove from power (Batt/ACC) wait a minute and start all over. Is the reset button more effective? Should I apply power to Batt give it 30 seconds then Acc? Or is it just luck that it boots in?
[FYT Android Head Units] gtxaspec:
Leave it plugged in...in a while (could be minutes to hours) it will boot
[FYT Android Head Units] Ford_OutLaw:
LOL so I have been my own worse enemy!
[FYT Android Head Units] D3LTA:
Viper does improve sound quality, no it's not hardware DSP but as software DSP it does the best job possible and I want it working on my Sofia unit.. so I guess I need to figure out some stuff.
[FYT Android Head Units] Redbullssg:
If you have updated to 6.0, so far the only way to run Viper is to run the V9a4test rom... So far so good for me... Not the best running, but the sound is great. Wish it were running on the latest rom.
[FYT Android Head Units] D3LTA:
Must be explainable why it's not working it can't be processing power
[FYT Android Head Units] surfer63:
It would certainly help if you would read more posts, like #1684, which is only 12 posts back.
[FYT Android Head Units] D3LTA:
I have seen the post.. nice info and it will probably run good on the PX5 units...

But it doesn't tell me why it will not run on our units.. the Sofia units are perfectly able too run V4A without issues..

What tell's you it's kernel related? Any source code or decompiled kernel source or debugging somewhere that shows this?

I'm not questioning you statement just want to know if it is something that can be fixed

Don't think there is any source code for kernel available ?
[FYT Android Head Units] gtxaspec:
It's not kernel related, it's a HAL related library that changed and broke it.
[FYT Android Head Units] D3LTA:
Okay that's clear, do you have info on that, any HAL librarys or info on your GitHub?

One other thing I want to verify

You flash back the stock recovery after flashing gtxrom in twrp

Why not leave it on for easy flashing? Or do i miss something

If I mess up my HU ROM, can I flash stock without a working android just like my previous HU?

Just put a sdcard in it with joying stock rom and power cycle it to start flashing?

Couldn't find any real brick info in this topic..
[FYT Android Head Units] Ford_OutLaw:
[MENTION=520205]gtxaspec[/MENTION] [MENTION=7993548]bigsteve01[/MENTION]

Got in, opened up custom.apk and verified the recovery. It was on stock. Reflashed the stock recovery verified again then rebooted. Stuck on the pink lights again. USB stick is plugged in with latest joying firmware. Now waiting for it to boot back in.... Can stock firmware be installed via TWRP as in selecting the 5009_60.zip?
[FYT Android Head Units] surfer63:
Sorry, that's correct. I mixed up the USB restrictions built into the kernel with the V4A issues.

---------- Post added at 10:56 PM ---------- Previous post was at 10:48 PM ----------

There was a lot of info on the several bricks that can occur, on the now removed carjoying forum. There was a thread containing a lot of info on the recovery, partitions, etc. and what should be done in case of several brick types.

(That all disappeared in December/January when Joying seemed to go through a bankruptcy followed by a restart of the company. This was never official but even Joying mentioned in some communication that they still had the data "of their old customers".)
[FYT Android Head Units] gtxaspec:
We flash the stock recovery in case something goes wrong during installation for safety, you can always recover back to stock.

I don't have info on which, I haven't had time to track down which library. It's one of them in /system/lib
[FYT Android Head Units] D3LTA:
Okay that's clear..

There are alot of them in system/lib, you don't mean the v4a*.so files right?

Any particular reason why you don't use magisk in rom?

If I change to magisk it would be easier to test and develop modules
[FYT Android Head Units] gtxaspec:
We are unable to modify the boot partition, which is a requirement for magisk.

The library .so files are the ones relating to the Android framework... Somewhere...in one or some of them...something broke audio.
[FYT Android Head Units] D3LTA:
Thanks for the info [MENTION=520205]gtxaspec[/MENTION], got some debugging to do.. maybe i can pinpoint the issue...

the fact that the units is in my car makes it harder then develop and debug a phone :)
[FYT Android Head Units] D3LTA:
[MENTION=520205]gtxaspec[/MENTION]

check out this folder

It is from the website

http://wiki.androidautoshop.com/categories/6174-software-updates

it contains Intel Sofia 3G stuff, same as from 4pda?
[FYT Android Head Units] Ford_OutLaw:
[MENTION=520205]gtxaspec[/MENTION] unit booted again. I uninstalled custom.apk then reinstalled from the link in the first post. Then reflashed stock recovery. Rebooted and pink lights cycle. Should I leave the stock joying firmware plugged in in hopes it will start flashing?
[FYT Android Head Units] gtxaspec:
Yes, I would do that. The stock firmware should upgrade your bootloader and hopefully will fix your issue.
[FYT Android Head Units] gtxaspec:
Yeah, it's mostly old junk files for HCT based MTCD devices...nothing to do with out units. The key will be to figure out which files we can bring over from the April 17 release to the latest Jan 18 rom to fix viper...I'm pretty certain we just have to figure out which libraries are causing the problem.
[FYT Android Head Units] Ford_OutLaw:
Have USB plugged in along with a GoPro watching. If anything strange happens I can just show you instead of trying to describe it.
[FYT Android Head Units] D3LTA:
Have you ever tried just to bring a load over to see what happens?

Maybe we can find some info on that here

https://github.com/Zackptg5/Audio-Modification-Library

Did you ever tried Dolby Atmos with the related libs, to see if that works?

I think it may be a combination of stuff thats why I'm curious if Dolby Atmos will work.
[FYT Android Head Units] gtxaspec:
i did copy the entire /system/lib from the old rom to the new one, it bootloops, and haven't had time to try one file at a time....that's probably the only way we will figure it out, but very time consuming.
[FYT Android Head Units] D3LTA:
can you provide me with a zip with the /system/lib from the old rom?
[FYT Android Head Units] gtxaspec:
https://mega.nz/#!PE1yCRzJ!Y4ta3ECfOdw6RxqhbW-j-8TylQ2ZK4pvFK9UiJHGlus
[FYT Android Head Units] D3LTA:
Thank you....

replaced some files that could be related... bootloop.. :(

how do i enter TWRP recovery now ?

found it
[FYT Android Head Units] IG_Vasilich:
[MENTION=520205]gtxaspec[/MENTION]

i managed to install TWRP on my HU (stock ROM from 01.2018). If i will do backup of all data in TWRP, can i later restore it after flashing your ROM? or TWRP backup works only on same ROM?
[FYT Android Head Units] D3LTA:
it will not work.
[FYT Android Head Units] gtxaspec:
Any ROM with twrp.
[FYT Android Head Units] IG_Vasilich:
mhh. who has the correct answer? as i have no idea how it works, and do not want to install everything from scratch again when testing new ROM, i would like to just restore it to the state as it is now (at the time of backup).

[MENTION=617090]D3LTA[/MENTION] have you had some bad experience with restore to different ROMs using TWRP?
[MENTION=520205]gtxaspec[/MENTION] as i said, i used your custom helper app to install TWRP. I assume it has installed the same version that GTX ROM has, so - should it be compatible?

thanks in advance to all answers!
[FYT Android Head Units] gtxaspec:
Yes, I use twrp almost daily for testing, and restoring back to my good backup. TWRP does work, it works great. If you need more guidance I am happy to advise.
[FYT Android Head Units] D3LTA:
If you wanna restore data and apps, install titanium backup in stock rom, backup app and data and just restore it in the gtx ROM.

So you only restore what you really need
[FYT Android Head Units] gtxaspec:
Titanium is slowwwwwww. TWRP takes like 4 mins to restore system and data partitions! It's useful for full system restore cause it works ?
[FYT Android Head Units] D3LTA:
Yes if you wanna do full backup and restore use TWRP, but for apps and appdata I always use titanium backup
[FYT Android Head Units] Ford_OutLaw:
[MENTION=520205]gtxaspec[/MENTION]

I left a usb with stock joying firmware plugged in. The unit took 21 hours to finally boot up but ignored the usb? I have not shut it down/rebooted. I have tried multiple USB drives and micro SD cards but the automatic firmware never starts?
[FYT Android Head Units] gtxaspec:
What's on the screen??
[FYT Android Head Units] Ford_OutLaw:
The home screen, everything works but when I plug in a usb or sd it detects the drives, I can see the files but it does not execute the update
[FYT Android Head Units] Redbullssg:
When I was trying to recover to the stock rom, it would not automatically start like before... I had to first make sure stock recovery is set in the Custom app. Then goto the system settings / backup recovery, and start the recovery there, with the usb or SD card plugged in... SD card worked better for me...

This was with V9a4test, I don't think I had that issue with a3, but not certain.
[FYT Android Head Units] Ford_OutLaw:
Click on settings then backup/reset and settings.apk crashes
[FYT Android Head Units] Redbullssg:
Okay, I do remember that on one of the roms... I think Gtxaspec has it set up to close it down if trying to go through system settings to do it on one of them. I think I remember reading that somewhere..

I had issues with trying to restore as well on one of the roms... I wish I knew what it was to finally get it to do it. I know I had zero luck with my USB flash drive... I could only do it through my SD card, and the only one that would work was my 32gb drive. I don't know if the others were to big or if there were errors on it... Before I started with the 32gb, I scanned it for errors and fixed, reformatted to Fat32 so I had a fresh start... Not sure if that was it or not...
[FYT Android Head Units] Ford_OutLaw:
I have tried multiple sd cards and USBs with different ways to format them IE using a router to format fat32, raspberry pi, my phone, the head unit itself even. I have tried 2GB, 4GB, 2-16GB, 32GB USB sticks even a 64GB stick reformatted to Fat32 with a 3rd party tool. Multiple sizes of MicroSD cards too. I have tried Copy/Paste and unzipping them strait to the root of the drives. I really don't want to "reboot" the unit because then its going to be another 18-21 hours for it to boot in
[FYT Android Head Units] Redbullssg:
Yep, pretty much what I went through... I wish I was more, analytical, when I was going through it... I was at first but by the 4th or 5th day of messing with it, I was just throwing anything at it... Wish I could help
[FYT Android Head Units] Ford_OutLaw:
I have different USB brand drives. The only brand of MicroSD I have are Samsung. Don't suppose you have had better luck with a different brand specifically with Joying?
[FYT Android Head Units] Redbullssg:
Mine is SanDisk..

But not sure if that has anything to do with it..

What rom are you on now?

I remember switching to Superuser as opposed to SuperSU.. I wonder if that may be it. I wouldn't know for sure...
[FYT Android Head Units] surfer63:
Make sure you only have one device inserted. If you have SD-cards with musics or maps or whatever, remove them (safely). Only insert the device you use to (try to) flash.
[FYT Android Head Units] Redbullssg:
Also, the unzipped files should be the only thing on the drive, and not in a folder. Though, you probably already know this...

Also, you must unzip to the drive, on a PC..

I have noticed if I do it on my phone, android would add files...
[FYT Android Head Units] Ford_OutLaw:
Freshly formatted so nothing on the drive. For years I have always used 7zip, I noticed in the Joying video he uses WinRar so once the unit boots back up (should be anytime now its been plugged in since 11pm) I will try WinRar.

Only one media inserted at a time
[FYT Android Head Units] D3LTA:
[MENTION=520205]gtxaspec[/MENTION] can we add init.d support? Not kernel init.d based but like universal
[FYT Android Head Units] gtxaspec:
As long as it doesn't touch the boot partition, which we can not modify...otherwise you can put stuff in /system/bin/install-recovery.sh at the end
[FYT Android Head Units] derekbunch:
Could you link me to the tutorial on how to change out the amp chip as you mention here?
[FYT Android Head Units] surfer63:
It's not a tutorial. It is a thread: https://xdaforums.com/android-auto/android-head-units/joying-sofia-chip-upgrade-t3589587

Another thread was at the now gone carjoying forum where they changed the TDA7388 for a TDA7851 (I think). I'm not an audiophile and only followed the topics because I read almost everything.
[FYT Android Head Units] D3LTA:
I figured.:)

Have add the following to install-recovery.sh

busybox run-parts /system/etc/init.d/

Working init.d
[FYT Android Head Units] surfer63:
Why do you want an init.d? What kind of services do you want to run? So, what did you put into the init.d folder?

It's not a multi-user server after all.
[FYT Android Head Units] D3LTA:
Want/need init.d support for sound mod, and after all all custom roms should have init.d support