yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kampfschachtel:
thank you for the fixed versions.

to 1) I have the busybox mod running and it install seamslessly, also stated in my signature. It is the one provided by surfer69. I read a post from someone here who had the same issue with the version of surfer69 and Viper, so its maybe just a different version.

to 2) The script is downloaded from https://xdaforums.com/showpost.php?p=71317345&postcount=101

that is also the link provided on the summary of page 1 of this thread and of gustden summary thread on page 1 too.

Will correct it on this thread and provide link to your previous post.

Will try it today to install and give feedback:

now suddenly the joying cannot be conntected via ADB over wifi.

if I try busybox to install via adb I get

connecting ADB over wifi

no order "ADB" found or wrongly spelled

if I try to install V4A I get

adb connect to 192.168.43.135

unable to connect 192.168.43.135:5555

how to fix this? After superSu install, I reboot and installing Titanium backup and run a backup. then reboot again and then install via adb the "wrong" V4S. all was working fine and now I just started joying and nothing over adb works anymore...
[Android Head-Units] kampfschachtel:
so next problem appears:

wanted to get your files via adb over wifi to the joying like I done yesterday BUT no ADB is suddenly avaliable on the joying...

did the superSu rooting yesterday and after reboot installed and run titanium backup. then reboot again.

then I install via ADB over wifi the V4A as you can seen above. didn't change anything since then...

now I started joying again and no ADB on joying avaliable...how to fix this?

Installed adb-win again on to make sure it is on the notebook and running...

busybox 192.168.43.135 returns:

connecting adb over wifi

unkown order "adb" or wrongly spelled
[Android Head-Units] surfer63:
I assume you mean adb instead of busybox.

After sleep the tcpip stack is sometimes notworking correctly. Reboot your head unit and try again.
[Android Head-Units] AssassinsLament:
The "no order ADB found or wrongly spelled" is because I didn't include the adb files inside the busybox install zip. I assumed people had adb already, but if you don't, just copy the three files (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll) into the extracted busybox install folder. Those adb files can be found in the Viper install zip.

Like surfer63 says, sometimes the adbd server doesn't work correctly, so best thing to do is to restart it. Download my ADB over WIFI app and install it, and you can use that to restart it. I suggest you keep that app installed also so you can enable and or disable adb over wifi for when you aren't going to use adb because with adb over wifi open all the time, anyone can basically connect to it if they know the IP address.

https://xdaforums.com/showpost.php?p=71616884&postcount=273

So download and install my adb over wifi app, then run the app and it will show you if adb over wifi is currently enabled. If it is, toggle it off then back on. If it's not enabled, then just enable it. Once you toggle it, it will restart the adbd server and you should be able to connect to it as long as you have the right ip address.

EDIT:

the bolded line above, even if you install adb for windows, you also need to make sure it is in your "path" so that you can call adb from any folder. To test this, just open up a command prompt and type in adb, and hit enter. If you get command not found, then it's not in your path. But to make it easier, again, just copy those three files I listed above into the busybox extracted folder and it should work.
[Android Head-Units] kampfschachtel:
thank you for your help.

Will try and report back how it worked.

Will make sure win adb is in the right path.

do you by any chance know how to change the bootanimation on our 5.1.1?
[Android Head-Units] AssassinsLament:
I recall someone posted how to do it, but I don't recall which thread it was in. So you'll have to search all the Joying 2GB threads for how they did it. Sorry.
[Android Head-Units] surfer63:
That is really simple. Simply change the bootanimation.zip in /system/media. You will also find an updateanimation.zip. leave it as it is.

So your own dowloaded custom bootanimation should also be called bootanimation.zip

adb kill-server
adb connect <ip-address>
adb push bootanimation.zip /sdcard/
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/media/bootanimation.zip /system/media/bootanimation.zip.org"
adb shell "su -c cp /sdcard/bootanimation.zip /system/media/"
adb shell "su -c chmod 0644 /system/media/bootanimation.zip"
[Android Head-Units] alessondanilo:
Help

Sorry for my English

But I tried changing the Bootanimation system with my custom file and unfortunately it did not work. :(

It enters a black screen and does not display bootanimation.

I've done everything, assign permissions and it does not work.

You could look at me what's wrong?

I wish these images were loaded at first.

Thank you very much!

Url:

mega.nz/#!r5BATCbA!roJmws1mhegqM_IN1WLo2I8skaRROouHB7YV-dyLrzA
[Android Head-Units] surfer63:
That bootanimation looks technically spoken correct, but it is a very big bootanimation. The original is 630KB. Yours is 10.7MB, or other said: 107000 KB.

I think your system boots faster than it can load the entire bootanimation. Probably that is why it stays black until the home screen is loaded.

Please try to:

adb kill-server
adb connect <ip-address>
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/media/bootanimation.zip.org /system/media/bootanimation.zip"

This will copy the original back (unless you ran the script a couple of times thereby overwriting the original with your own several times).
[Android Head-Units] alessondanilo:
Thanks for the quick response!

I returned to the default bootanimation, now yes it starts normal.

I did this bootanimation with Photoshop and all the images saved in PNG format are gigantic, these images have a clear background.

Is this the problem?

Is there a way to make these images smaller in size?
[Android Head-Units] georgebest:
About the RDS...why is so small and therefore useless?? In other head units like Erisin it appears in the centre of the screen like it should be. Is there a way to make it happen to joying HU as well??
[Android Head-Units] surfer63:
There are lots of issues with the RDS in Chinese units.

The Joying displays the RDS PS text (8 character radio station name) and tries to display the RDS RT text, alternating in the same field. This last RDS RT text is incorrectly coded in the Radio apps.

The RDS AF function is plain wrong coded, that is: they did not understand what they had to code. AF (Alternative Frequency) allows a receiver to re-tune to a different frequency of the same radio station when the first/current signal becomes too weak. The functionality in the Joying head units is: "Find the strongest frequency, whatever it is, and tune into it." This means that if your current tuned-in radio station gets a little weaker, it starts randomly switching to the strongest frequency of any radio station it can find. (I assume the basis for this error is a wrongly translated English specification sheet, although I already pointed Joying to correct Chinese documentation (which I can't read)).

That with regard to the coding of the Joying (and other Chinese brands) Radio app. It is very, very bad.

W.r.t. the position and size of the text: you can take a look at my mods. They are for 5.1.1 ROMs. I did not check for the 6.0.1 ROM yet but I assume the Radio apk is exactly the same.
[Android Head-Units] georgebest:
Thanks for your reply. So I can install any of these layouts? Should I root my device? And the RDS text will be rolling on screen?

On my friend's Erisin unit , he told me that some stations show 2 RDS texts
[Android Head-Units] surfer63:
If you are on 5.1.1 you can install.

And I can't fix the RDS RT as it is deep down in the code and I don't have access to that code (I'm not a java programmer anyway)

So no rolling RDS RT text. When avaliable, 8 of the 64 characters are "rolling". They use a 32-character buffer consisting of 4x8 bit characters arrays as they even use the old 32-character RDS standard instead of the current (for years already) 64-character standard, so they only get half of the RDS RT.

With regard of that 2 texts on the Erisin: I assume those are probably 2 buffers of 32 bit characters to comply with both the old 32-character standard, as well as the current 64-character standard. Now that is nicely done :)

Most radio stations still limit the RT to 32-characters to support the "very old" system, but even that old standard is incorrectly implemented in our Joying

As mentioned: it is terribly bad programmed.

Is there somewhere a ROM of that Erisin containing both the apk and necessary libraries? And what receiver/radio chip is used, also the Philips TDA7786?

If so I would very much like to have a look at it.

Edit: will not work. Please forget I asked.
[Android Head-Units] georgebest:
Do I have to root it first? Or I can install it without rooting? And then how can I take it off if I want to go back to the factory radio?
[Android Head-Units] surfer63:
The Sofia units are "semi-"rooted. Using adb via the scripts you can install them without further rooting it.

I did not even think of restoring the factory radio :), but as such it sounds very reasonable.

I will simply add it as another version so that you can use the scripts to install a mod or reinstall the default.

Edit: I just did add the stock radio app.
[Android Head-Units] alessondanilo:
Thanks man!

I found the problem, it was not a question of size, the problem was in zip compression.

I discovered that you can do a boot animation of up to 200mb, you will not have problems running if it is not compressed with compression.

The Joying device only accepts image files in png format starting at 0001. You should only "store" in a zip file and then set the permissions.

This is the tip for anyone who has the same problems as me!
[Android Head-Units] kampfschachtel:
thank you. getting slowly professional with all this adb programming:eek: just kidding:laugh:

Worked after I installed the adb app and started spotify (before it said sd card offline, starting spotify fixed it)
[Android Head-Units] kampfschachtel:
I done all what you said, adb works now after I changed superSu settings to prompt instead of grant

used both files you provided

but it still seams to be the wrong busybox version.

Busybox install went well without mistakes. Rebooted device.

when installing Viper he cannot find the audio effect files. ignored it and Rebooted device

after that starting viper he asks for online update of drivers, said ok but doesn't work.

when I switch to vipers menu and say install drivers it say busybox install is wrong or broken...
[Android Head-Units] AssassinsLament:
Which android version are you using? And which of my script are you using?

Can you run each command in my script one by one and show the output so I can see what's going on?
[Android Head-Units] AssassinsLament:
Added gusten's 6.0 CustomKeys + NoKill + USBDAC.

https://xdaforums.com/showpost.php?p=72107360&postcount=127

USBDAC mod gives you control of Android's native sound volumes for people who are using usb dacs instead of Joying's outputs.

!!IMPORTANT!!

To enable usbdac volume control, you must create a file "usbdac" on the root of your sdcard. Example:

/sdcard/usbdac

You can do that with either an android file manager or the adb command:

Code:

adb shell touch /sdcard/usbdac

To disable usbdac volume control and set it back to normal, just remove the /sdcard/usbdac file.

Code:

adb shell rm /sdcard/usbdac
[Android Head-Units] surfer63:
Thanks for this (although I don't use it myself).

Somewhere in one of your other posts, which I can't find back, you wrote something about a folder to create on /sdcard to make it work, and to remove that folder if you switched back to the original internal DAC.

Can you explain a little about that? Is it still necessary? and if so: could you add it to that post?
[Android Head-Units] AssassinsLament:
Sure thing!
[Android Head-Units] kampfschachtel:
I am on 5.1.1 with the 14th March release. I used the scripts you provided 3 posts before this one.

BusyBox is only moving 2 files

Viper: everything runs well till mv audio effects...., cannot mv Audio, audioffects .....doesn't exist

If that already helps....

Will run Viper step by step and post here.
[Android Head-Units] AssassinsLament:
I think I found the issue. I re-wrote the script and minimized the paths so it was less confusing. Sorry for the issues! I updated the link.
[Android Head-Units] kampfschachtel:
No need to apologize, I owe you a lot for all the mods which made the joying actually useable for my project.

Updated busybox and Viper, both work know perfect:victory: thank you so much for your patience and support.

Wow and holy moses with Viper the sound is night&day to before, this is a must-have for everyone with this unit. More dynamic, more stage and much clearer sound. Louder too but the joyings preamps are then at their limits and i got much more distortion...my Audison DSP will fix this as it has 4V out per channel. Cannot wait to hear the difference with the DSP and Viper installed. Performing final install in the R8 at the moment, making all the bezels and rounting the cables nicely...

Didn't have much time to try all the settings, just enabled the master power and EQ but left all flat so far plus played a bit with the limiter/output gain power.
[Android Head-Units] bogdi1988:
Do my chip swap hack and you'll definitely love it! ?
[Android Head-Units] kampfschachtel:
you mean the amp swap to the pioneer amp chip ?

I have a full active 11 channel B&O system with approx real 1000W in my R8;)

just have it running at the moment over joying preamp and chinch output to the B&O amps as I am routing the Spdif cables at the moment and performing the final install. When this is done I bypass the internal DAC of joynig via USB out to Spdif adapter and go via SPDIF fully digital to the Audison Bit one DSP which does the Digital to analog conversion and delivers superclean 4 V per channel preout into my B&O amps.
[Android Head-Units] bogdi1988:
Damn! Overkill! ?
[Android Head-Units] AssassinsLament:
Viper Settings (Example)

Here are some settings I use. Each car, is different because they have so many variables (headunit, speakers, power, etc) in how your car system will sound, but this will be a good example for you guys to try.

First off, download these irs files from here. Extract the above zip file to the root of your sdcard (internal). It should look like this "/sdcard/ViPER4Android/Kernel" and have Dolby irs files in that folder.

Now run Viper4Android and lock the effect to "headset" as it has the most features. Don't worry, even though you are technically on speakers, locking onto the headset effects will still work. Then enable viper for the headset tab.

Then enable "Spectrum Extension" and Set the strength to 0.5, then enable the "Convolver" and Tap "Impulse Response" and select "Dolby Pro Logic 1.irs" (file was downloaded above) and set "Cross Channel" to 80 percent.

Enable "Dynamic System" and select "High-end Headphone(v1)" for Listening Device, and 24% for Dynamic Bass.

Scroll all the way down to Fidelty Control and tap "Enable ViPER Bass" to enable it. Set "Select Bass Mode" to Natural Bass and set "Set Bass Frequency" to 100 Hz and set "Select Bass Boost" to 12.0 dB. Now enable "ViPER Clarity", set the mode to XHifi and "Select Clarity" to 14.8 dB. (these settings can be up to you depending on how much bass or highs you like. I actually only have my bass boost at 3 db and Clarity at 6 db)

That's all I do to my system, but take this as an example only, customize it to your liking and don't forget to google for more settings and examples.
[Android Head-Units] ztbishop:
Pioneer PA2030A specs ?

Regarding the Pioneer PA2030A

This is 4 x 60 Watts Peak?

Any ideas on RMS?

More importantly, what ohms?

I may look for some mid-level aftermarket 6.5 speakers to replace stock. With four speakers would I want 4 ohm or 2?

And this would be a max 60W per speaker? (4)

Has cooling been an issue?

Would it still be worth Root + Viper, after installing the chip?

Thanks!
[Android Head-Units] bogdi1988:
Not sure on Ohms.

There was a post around that talked about Ohms and Pioneer vs the other chip that's available.

Cooling - no issues whatsoever

Root + Viper - might be worth it. I added it yesterday just in case and you can tweak the audio further. However the benefit is Pioneer is the quality of audio and lack of distortion at really high volume ;)
[Android Head-Units] ztbishop:
Thanks for this. If I tend to not listen at high volume, the benefit might not be so great then?
[Android Head-Units] bogdi1988:
Yea, but then why would you care about RMS and peak power? ;)
[Android Head-Units] ztbishop:
Haha, because I'm a newbie. I figured matching them closely would give better sound quality but I'm probably just over-thinking things at this point.
[Android Head-Units] bogdi1988:
For me the chip swap was totally worth it. Overall the unit sounds a lot better!
[Android Head-Units] HVB83:
Especially when using Viper, having some extra grunt provides benefits. Adding bass will eat power and even if you don't listen at high volumes, that will translate in more control and a much better sound.

I do find it to be a lot of risk however, considering that Joying supports an external DAC. Your signal quality will improve significantly and a cheap amp on Ebay will already be more powerful than this internal chipmod.
[Android Head-Units] kampfschachtel:
The chips are 4 channel so it is a load of 4 ohm per channel if your speakers are 4 ohm. But there are a lot 2 Ohm speakers out there too;) and the Pioneer can drive 2 ohm loads too

Specs (google helps here;) )

4x60 W / 4 ohm maximum.

4x40 W / 4@14.4V,1kilohertz,1%of distortion

4x90 W / 2 ohm maximum.

4x65 W / 2@14.4V,1kilohertz,1%of distoration

so RMS/real watts on 4 Ohm will be likely 25-35W, 2 Ohm around 4x40W as power supply in the joying is not that great.

I would recommand also an small 4 channel amp (on ebay you find a good well knwon top brand amp with 4x50W used for max. 100$ ) and a DAC, it costs 10$ and you bypass the internal crappy low quality DAC Chips and preamp;) as just replacing the output amp chip is still garbage in=louder garbage out.

Chip mod is still a good one if you can solder and only invest 10$. Be carfeful and get an original pioneer one, around 10$. if lower priced its a most likly a copy and they are 99% crap.

And yes Viper is a must in this unit, doesn't matter if with original internal amp, upgraded pioneer chip amp or an external DAC+DSP+multi-channel amps+ 11-channel full active 5.1 speaker setup as I have it. Actually the better your systems and amps are the more viper improvement is noticeable as I experienced. Be careful with the bass boost, +6db is already double power needed and the internal chip amps will distore as they don't have enough power.

It helps in all dimensions from dynamic, more output, more clearly, more room, more stage.....as it decodes the signal (instead of legacy Andorid audio decoding) and manipulates it digitally before it goes into the internal DAC and via USB out. If it doesn't sound better with Viper you have the wrong settings in Viper!

Also play with the settings and google for different settings/add ons (whole community for Viper out there), as explained in some posts before.
[Android Head-Units] kampfschachtel:
double DIN case with sofia/intel 2GB/32GB for sale, cheap upgrade for your old lower Spec 1GB or 4.4.4 universal unit with 8inch or 10.1inch detachable screen

will change from the 2 Din Unit to the 1 DIN Unit case ( to install the DSP above the 1 DIN case in the double DIN space) of the 10.1 joying. Its the new 2GB/32GB, see here https://www.carjoying.com/android-5...bluetooth-backup-camera-car-stereo-radio.html

So if somebody has a lower Spec 1GB or 4.4.4 universal unit with 8inch or 10.1inch detachable screen this is a cheap upgrade for you.

Comes with 5.1.1 last updated version, rooted, with busybox and Viper mod for perfect sound.

Its just the metal case with all electronics in it (no wires/Screen/MIC), unopened and still with garantuee (bought on 17. March 2017). Just replace your metal case with this one, attach your already installed wiring (it is the same) and your screen and you are good to go.

Asking for 200Euro shipped in Europe, worldwide on request and additional shipping cost.
[Android Head-Units] dpredster:
Thanks [MENTION=503463]AssassinsLament[/MENTION] for viper files and tip. I am finally enjoying music from my head unit and 4x400 rms amp.
[Android Head-Units] hoang.pham:
will you be updating to gustden's V6.1?
[Android Head-Units] ztbishop:
I'm curious how those of you with a separate Subwoofer amp are going about things? Have you found a DAC with two outputs (add an in-line volume slider) ?
[Android Head-Units] hoang.pham:
My DAC feeds a DSP. I then use the DSP remote to control the volume and sub. Otherwise you would need a sub remote capable amplifier.
[Android Head-Units] kampfschachtel:
I do the same with DAC via Spdif out into DSP and with DSP remote I can Fader and Control Sub Volume. You can get Used top notch DSPs around 250-300Euro like Audison Bit one or Helix DSP.

Other solutions for a DAC with 2-channel stereo out

- 5 channel amp with 2-Channel stereo input (creates internally all the other channels) and remote control for sub

- 4 channel amp with 2-Channel stereo input with remote control and a preout for sub

- Mosconi ( maybe other manufacturer too, just Google) DSP amps with Android app installed on Joying (eg Mosconi one DSP4.100) . 4-Channel DSP Am with a processed Sub pre out and Remote is done via

App, the luxery version.

- sub amp with App configuration, app installed on joying

- if you have a sub amp and nothing of above you can get an rca-inline volume control. Look for Tablet gadgets here as with OTG cable out some tablets have no volume control.
[Android Head-Units] HVB83:
I've had the Behringer DAC on my C500 for a couple of weeks now, but use it probably once every few days, since it's a hobby car. Yesterday I very clearly noticed jitter/very short interruptions of the sound, sometimes every minute, sometimes every 10 seconds. I use Poweramp as an audioplayer and as far as I know I haven't changed anything in the configuration or done updates to the unit. The only thing I've changed was install a longer usb-cable for my external hdd (which stores the audio files) and perhaps the usb-cables for USB DAC and HDD have been switched during that.

Any suggestions on what might be the reason for this?
[Android Head-Units] kampfschachtel:
Exactly what you wrote causes the problems: longer and maybe cheap USB cables.

the cheap dac like Behringer or what also I use as USB to Optical adapter have a very low damped and isolated input circuit and the longer the USB cable the higher is its resistor value is and therefor the lower is the input damp which results in distoration or even bytes get lost=jitter. The same for the HDD and its even worse there due to it uses much more power then the USB DAC.

I have from joying to USB DAC a 15cm USB cable and then 2m optical cable to the DSP as here length doesn't matter at all.

Also if you have powered USB Hubs in the signal path the power supply should be attached to the same power circuit then your radio or the minus should be isloated otherwise you get unclean ground differences in which causes jitter.

Had my hubs powered too but took power supply off, sounds better and joying is fine with delivering what the DAB+,USB DAC, small SSD and 2 phones.

Another reason is that when you use dormacy mode a lot temp data is stored and several unclean or deffective processes collect together which results in performance problems and the decoding start to get disturbed which causes the jitter problems too.

That why I don't use the dormacy mode, had similar problems when I used it as test for a week now. clean shut down and clear new start helps a lot to have it performing well.