yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Redbullssg:
"A (digital) equalizer will not help if they use a cheap amplifier chip. That is why you should use an external amplifier, or a usb dac or an amplifier replacement chip, if your really want better quality.

That's also why I'm not really interested in Viper. It does improve the sound but it will never make it great as the amplifier chip is not good: garbage in = garbage out. (and that is far too negative, but it simply is not a very good amplifier chip). If you really want better quality check the threads that replace the amplifier chip with a better, compatible one."

[MENTION=2550900]surfer63[/MENTION]

I have 2 external amps install. A 300w rms 4 channel 2 ohm stable amp for my dash, door and deck speakers, and an 800w rms 2ohm stable to my 12" sub in my trunk. Without any of the added audio affect software, and only using the stock Joying HU's EQ, the highs are not present, the lows are muddy (the stock sub output is junk and very weak), and the over all sound is complete garbage, even with the external amps. All of the system is through the RCAs. The chip, as far as I know does not effect the low level outputs.

With PowerAmp, the system sounds amazing, even better than what Viper does for the other apps. All that I wanted Viper for, was to enhance the Radio, but now know that there isn't anything I can do about that. But my other apps like Slacker Radio, Spotify, Amazon Music, etc., all benifit from Viper.

But even still, with Viper, with Poweramp, the stock EQ still has to be set to get the sound I want, but is super limited with only a 3 band. It all works together, it's not ideal, but it's working. If I put the stock EQ at flat, the whole system, no matter what I do, sounds like garbage, loss in highs is very significant and lows are not present.

My guess would be, even if I put an external preamp EQ in before that external amps, and skipped the poweramp, and Viper EQs, the system would sound like garbage. It just doesn't generate the highs like it should. Almost like they purposely limited it.

My total goal isn't to have a loud ass system, but to have a complete, crisp, full range, clean sound, at all volumes, not at eardrum rupturing decibels. So far, I am pretty close with the ability to tweek each song individually and save, or album, or speaker set up, or over all in the EQ of Poweramp, and then just a general setting in Viper for everything else. It's loud enough....

Ideal would be to have that sound, coming straight from the source, before power amp etc., and not even need Viper...

The sad thing about these Android systems is that the manufacturers put the apps first, the function of a phone, gps, and everything else, but forget about what it is, it's a car stereo... Sound should be first thing...

I am curious, how the high level outputs would sound through my amps. And if the amp chip mod would improve it, but still, it's limited to that crappy stock EQ.... But if I could get a pre out, to a good preamp EQ, and skip all of the software, I'd be a happy man.
[FYT Android Head Units] edit:
It's not clear to me if the board has BT on it or it's just Wifi+GPS... Any ideas?

Thanks !
[FYT Android Head Units] gtxaspec:
You should invest in a USB DAC...look into it.
[FYT Android Head Units] Ford_OutLaw:
Not sure if your still having this problem. I just got my Joying Intel on Friday and had the same issue as your BUT using the Stock Joying Rom not the GTX. I was having the exact same thing as in your videos BUT I happen to just figure it out. I am using a BAFX connector from amazon with the pairing code of 1234. In the Joying Bluetooth pairing mode the default password was 0000 I changed that to the 1234 then repaired my connector and that fixed it.
[FYT Android Head Units] Redbullssg:
I've looked into them. They are too basic... Meaning only ones I have seen are either headphone only out, or just 2 channel. Then I would also loose my steering wheel control as well. The Joying head is already short a wet of pre outs as I see it.... I wish they were true pre outs as well. It's just weird.

I'm getting by, all I can do is wish with this head it seems... Maybe someday some company will build a open source Android head with sound quality in mind.
[FYT Android Head Units] gtxaspec:
Why would you loose steering wheel control? There are some 4 channel output DACs...haven't personally used them though.
[FYT Android Head Units] Redbullssg:
I will try that.... See what happens... I think you are into something.. It crossed my mind, but I didn't think of it again while I was in my car. I am betting that will work, thank you!

---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------

I haven't seen one with 4 channel. Maybe I didn't look hard enough. The volume is controlled at the DAC, so steering wheel control would be gone as far as that aspect. Not a big deal though.
[FYT Android Head Units] gtxaspec:
You can already control DAC volume using steering wheel with my ROM and xsofiatweaker!!
[FYT Android Head Units] Redbullssg:
I was not aware of that... I will research some DACs tonight... I just looked through Amazon for some, didn't really see one that would fit the bill... I'll do a little more invasive later. Thank you

---------- Post added at 09:49 PM ---------- Previous post was at 09:45 PM ----------

It worked! Lmao! Never had to do that before. Thank you.!

Though, I'm still a little weirded out that I never had to put any kind of pin in for my Phone. Or even use the Joying app to pair. I just hit pair on my phone and it did. Wonder, if anyones phone will do that... If so, I'm not sure I like that idea.
[FYT Android Head Units] Beatwolf:
I've also been having connectivity issues with Waze. They happen at random times, when I know there is an active internet connection. I'm on the main release from OP.
[FYT Android Head Units] IG_Vasilich:
[MENTION=520205]gtxaspec[/MENTION]

what SYU software is in your v9 ROM? i am asking this, because after updating from 80.17 to 01.18 stock Joying ROM i have found, that the new Radio app supports RDS text i don't want to loose when switching to your ROM...
[FYT Android Head Units] gtxaspec:
01/18 includes.
[FYT Android Head Units] sanangel:
I have tried to flash V9 ALPHA 4 again because I have not managed to remove the message "Android is starting" with each cold start of my unit and I get the error of the photo that I put next.

I followed the steps of the first post and I get the message of the following picture.

After this, I have to restart my unit from the reset button because it is a long time with this screen but without advancing anything ...

The truth is that if it were not for the message after the cold start after leaving Joying to sleep, the rom goes very well.
[FYT Android Head Units] gtxaspec:
You need to use the stock recovery to restore, or install custom recovery to reinstall the custom rom
[FYT Android Head Units] sanangel:
Do I understand that re-flashing the rom is not the same procedure as to install the rom from the original of Joying with the help of the custom application?

Would it be too much to ask me to do a guide on how to do it without having to reinstall Joying's rom and repeat the steps of the first post?

Because I think that the message "Android is being reinitialized" does not do it for any application installed after flashing. With what something will have failed in my flash and I think it is best to repeat it (unless someone has a better idea).

I do not want to look clumsy or a rookie. Nor do I want to fill the thread with stupid questions. I've been flashing roms since I had my first android device and I dislike asking and asking about things that will surely be pretty easy, but in this case I'm very lost ...
[FYT Android Head Units] gtxaspec:
Are you able to boot into the device successfully?? Or do you get stuck on the reinitiating screen?
[FYT Android Head Units] sanangel:
It starts and works well. The only problem is the one mentioned about the messages "Android is starting", which lasts a few seconds after each cold start.

But the rom works very well for me, that's why I do not want to go back to Joying's officer.
[FYT Android Head Units] gtxaspec:
Ok, it's supposed to display after each cold start. Are you having an issue with the unit not going to sleep and cold booting each time you power it on?
[FYT Android Head Units] sanangel:
It may be that (and see that you already told me in previous posts). What is the way to know if my unit sleeps well or does a restart?
[FYT Android Head Units] gtxaspec:
Instant power on, no wait time.
[FYT Android Head Units] edit:
I had the same issue... Even if it was enabled by default it did not worked... I had to disable it (the xposed module)... Restart.... Enable it... Restart again and it finally worked.... I guess it's a bug?
[FYT Android Head Units] micdesa:
Ijust installed it.-

It starts jst one times. Now the dispaly is black......how to recovery thanks......

Please help me.... radio cotniuosly reboot.....screen is black.....

The radio is unuseful.......
[FYT Android Head Units] gtxaspec:
More info please. What model radio do you have? What verison ROM did you have before installation?
[FYT Android Head Units] gtxaspec:
Copy thanks for the reports. I'll do some debugging for the next release on this.
[FYT Android Head Units] surfer63:
@gtxaspec

In another forum we discussed the total data wipe in the Joying ROM upgrades. The only reason for this, AFAIK, is that Joying/SYU do not have their settings correct. They (seem to) change it on every update and do not use a good default android update function for it: so they simply wipe the entire /data partition.

Otherwise you have an unstable ROM with crashing applications, rebooting rom, etc.

In "normal" updates/flashes this is not done.

You also format/partition the /data partition, probably because we took it automatically over from joying.

What if we just deleted the joying data in the upgrade script before boot.

This would leave all 3rd party and google apps data in place, like:

rm -rf /data/dalvik/*
rm -rf /data/data/com.syu*
[FYT Android Head Units] gtxaspec:
I'm working on implementing increment ota updates using the release tools from the aosp tree, I should have it working soon. I'll revisit the data partition as well.
[FYT Android Head Units] derschnelle:
I didn't disable it, at least I am not aware of it. Will have a look at it tomorrow morning, whether it is enabled or not.
[FYT Android Head Units] gtxaspec:
Are live wallpapers still a thing? I removed the built in livewallpaper picker...so they might not work.
[FYT Android Head Units] micdesa:
​

Hi my radio is not genuine joying but a generic one that use the Intel Sofia Chipset...

The old version of the ROM is a Androdi 6.0.1 Rom of the vendor. ( Tongtai supplier ). Below the link

https://it.aliexpress.com/item/7-20...6c76-4777-8f7c-53495d7470e8&priceBeautifyAB=0.

Is there anyway to reset it? I don't found any info about, but do you know if there is a Generic ROM for Intel Sofia Android Radio?
[FYT Android Head Units] ste2002:
Are you serious?

I believe, the stock FW is a good place for such things to rest in peace. :p
[FYT Android Head Units] surfer63:
We all know what terrible things happened after the famous words "it's alive!" were shouted.

:)
[FYT Android Head Units] gtxaspec:
I just asked because I saw someone on 4pda who couldn't get their live wallpapers to work =)
[FYT Android Head Units] st.trophey:
I can't add google offline speech recognition. there is no other except en language. Is it a gaps bug?
[FYT Android Head Units] surfer63:
Actually I couldn't care the least. For me they are useless. If others like it, I don't care.

====

I do have another request. The build.prop also contains the builder. For the january rom it is

ro.build.user=bsp

Could you change that to

ro.build.user=gtx

or whatever you prefer. The reason I'm asking is two-fold:

1. you are by now the builder (at least of this custom rom).

2. I can check it in my apk and adapt the menus. The Xposed framework install should really be removed. The "enable adb over tcpip" is not necessary anymore once you are on the custom rom (but users might want to disable it; don't know yet about this option), the install of the standard Android Settings.apk is no longer necessary, the music player mods can be removed from the menu, etc.
[FYT Android Head Units] gtxaspec:
root@sofia3gr_car:/ # getprop | grep gtx
[ro.build.user]: [gtx]

added to next release to /system/app/fyt_build.prop
[FYT Android Head Units] surfer63:
OK, thanks.

If you prefer something completely unused (to prevent claims from joying for example), you can also create your own props.

Something in the build.prop like

custom.rom.builder=gtx

In that case a "getprop custom.rom.builder" would give me "gtx"
[FYT Android Head Units] edit:
I am sorry to say it but i always found them useless especially on a car headunit... i always liked simplicity...
[FYT Android Head Units] derschnelle:
I just had a look, the module was enabled (ticked in), but didn't work, as the overlay-error still was shown. So I deactivated and reactivated the module, restarted and now everything works!

Thanks a lot!
[FYT Android Head Units] dyabolikarl:
Been on the rom since you uploaded it.

Been rock solid. I haven't hooked up my phone though so can't tell about the BT calling etc.

I have found one bug though which isn't related to your rom but to the xposed module for gpsfix.

When i start the car the speed jumps around randomly until i get out of the garage. When i navigate with Gmaps .. it keeps thinking i am turning left down every side street so it's constantly recalculating and changing routes. My friend who also runs the same rom and setup experiences the same thing. If you disable the gpsfix .. it goes back to normal. I have a log of the gps co-ords on way. So i guess i have to find the gpsfix author? I think it might be updating too fast for Gmaps. The way points seem to be on the footpath of the map too... so maybe that's a thing?
[FYT Android Head Units] Redbullssg:
It's more than likely an app that won't play nice when the HU tries to sleep, and can't, so the system shuts off. When you restart your car, the system reboots.

Mine does the same every once in a while if I have an app running in background. If I close them all out before I turn the car off, and say I only have Poweramp running, I don't have the issue. I haven't narrowed the app(S) down that causes it. Nor do I know how to prevent it. I know the nokill has something to do with it, but I don't really know how it is supposed to work.

---------- Post added at 01:25 AM ---------- Previous post was at 01:19 AM ----------

It should always just be instant on as soon as you start the car, and not go through the whole boot process, unless the car has been off for a long period, days, or weeks. The system monitors the voltage, and when it reaches a set low threshold, it shuts completely off. Or, if the system can't go to sleep, and draw a low current.

Im not really verse on this, but I know the basic. If I haven't explained this right, let me know.
[FYT Android Head Units] etrefal:
The audio controller used (BD37033) only has a 3-band EQ, that's where the limit comes from. But a couple of features of that chip's eq have not been implemented - you could control the frequency of the low-pass filter, the gain of the loudness function and the Q of the 3-band equalizer..
[FYT Android Head Units] btrax:
Hi guys, I experienced some problems with Waze app (with GTX v9A2)

If i did a long trip (more than 400 km - 250 miles), Waze is freezing or very lagy, like it can't load all the path and display it, and when I reduced near 200km, there is no problem. Is it possible that is a problem of buffer or something in the RAM. Did someone experienced this problem ?

Cheers :)
[FYT Android Head Units] Redbullssg:
How exactly? Because as I see it, that control manipulates the why everything sounds no matter what you do. And I would consider that the source... If the source was better, or more broad, the whole system would sound much better, and possibly not even need Viper or Poweramp. Maybe only to tweek.
[FYT Android Head Units] sanangel:
Thanks for your reply.

The truth is that I can not know if it is for some application. I have tried to restore factory settings and even so, with each new cold start, I still get the message.

That's why my intention is to flash this rom again. The problem is that having to install Joying's rom, to root and install this rom is a very long process due to my lack of time.

I understand that "nokill" comes pre-installed in the rom ?, is there any way to cancel or un-install it to know if that is the problem in my case?
[FYT Android Head Units] gtxaspec:
Nokill is not pre installed.

Download v9a3, extract to USB drive. use the custom app to install custom recovery, then put your flash drive with the installation files in the USB and then click install GTX. No need to re install the stock ROM.
[FYT Android Head Units] Redbullssg:
You will always get that message, no matter what, with a reboot, not a wakeup.. It is normal to see the message on a reboot... If you are seeing the message, your HU just rebooted. It should not be doing that every time. Heck it could be that your battery in your car is low voltage and it is trying to save battery.. I don't know that for sure, just an idea...

---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------

@gtxaspec is there a how to on the nokill? I have no knowledge on how that works.
[FYT Android Head Units] sanangel:
When I try to install custom recovery, I get the message:

2131427376

You must be running at least AOSP build:

Android/Sofia3gr_car_64/sofia3gr_car6.0.1/MMB29M/bsp12151541: userdebugrelease-keys

Installig will not proceed.
[FYT Android Head Units] gtxaspec:
Ok...that's a bug. I will release a new version tonight.
[FYT Android Head Units] sanangel:
I will wait then.

Thank you very much for your answers and your patience with me
[FYT Android Head Units] etrefal:
As I said: those features were not implemented by whoever wrote the equalizer code. The features are there, but not used. I guess someone could rewrite the equalizer code, but I don't see that coming, and unfortunately my programming experience doesn't include Android apps... yet.

---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------

NoKill is activated by default in Xposed though, if I remember correctly... I think I had to disable it when I activated Xposed as I didn't want it.
[FYT Android Head Units] Redbullssg:
Awe, dang, you got my hope up and all.......
[FYT Android Head Units] joshnat:
I think that message is quite common on custom ROMs, especially when Xposed is used, or custom apps are in /system. It usually lasts for just a few seconds on every cold boot and I've never heard of a way to get rid of it.
[FYT Android Head Units] Redbullssg:
Shouldn't be cold bitting every time either... I wonder if his settings is correct.
[FYT Android Head Units] joshnat:
True.
[FYT Android Head Units] sanangel:
I do not use that configuration, with each cold start of my car, Joying starts again (when I installed Joying in my car I had to put it that way because otherwise my battery would be consumed very quickly). I've been with my unit configured like this since the first rom Joying 5.1 and I've never had problems.

I do not know if the message "starting android ..." is by having Xposed installed here (if someone could confirm it by changing the configuration to make Joying turn off when the battery of your car is off for a time of more than 15 or 20 minutes and confirm it, it would be the way out of doubts). I have a Samsung Galaxy 10.1 tablet with an unofficial LineageOS 15.1 rom with xposed installed and, on that device, when restarting, no messages come out. The restart is clean after the bootanimation without any message.
[FYT Android Head Units] Redbullssg:
Well, if you've been cold starting it all this time, that will explain it. Android "starts apps" no matter if the operating system tells you it is or not. It doesn't affect the time at all. It is normal. What isn't normal, is the HU consuming battery with it in the other configuration... Perhaps it was the way you had it wired. Because it shouldn't be an issue.
[FYT Android Head Units] sanangel:
As I wrote in my previous post, I have Joying configured like this from the first rom that brought the factory device.

The connection of Joying with my Volkswagen Passat when installing it was through the iso connector that the factory unit brought when ordering it for use in a Volkswagen. I do not know if something similar happens to someone with a Passat or it is a thing of canbus problem (I think [MENTION=248778]surfer[/MENTION] had it removed).

Anyway, with the configuration that I have, it has never happened to me that with each boot I got the message "initiating android". In all my devices I have custom roms and, in no other happens to me ...
[FYT Android Head Units] doctorman:
Anyone has a way to bring this back to life

the FYT 6021 does not boot

Trying to install the Intel sofia original ROM from joying results to the error in the picture attached

Signature verification failed.

Tried both USB and SD card...
[FYT Android Head Units] Redbullssg:
I was having the same issue, so I bought a new 16gb SD card for the sole purpose of update files. Made sure it was already fat32 and It worked. I later had a smaller USB drive that was formatted to fat32 that I tried and it also had issues. I reformatted and checked it for errors, and it cleaned it up, and then worked again. The system seems to prefer SD card over USB for updating as well...

---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------

It's completely normal on the custom rom... It does the same on Joying rom, just doesn't let you know it's doing it... All Android do it, just not show the message all the time... My phone does
[FYT Android Head Units] doctorman:
Tried multiple SD cards,

just use windows to Format them?

any issue with quick format?

Also I am getting the stupid MCU Yellow bar error with the latest ROM, and the old ROMs are offline.

any solution for that?

---------

Update:

Tried full format, brand new 16gb SD card , fat32, even tried a 3rd party formating tool

there is nomething wrong

2 units:

1) Bricked unit; I get the error , I think wrong ROM was installed on the core and I need to flash it some other way, it is not taking the original Joying ROM

2) MCU Yellow Bar on top, which does not go away..
[FYT Android Head Units] Redbullssg:
Are you going trying to install the custom rom, or Joying stock rom.. Either way, you must go into the custom app and click "Restore Stock" and then verify to install the stock rom through the settings page (backup/restore), or click "install Custom" and then verify before installing the "install custom gtx rom" through the custom app.... If this is what you are dojng, I apologize.

---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------

Are you able to boot the device?
[FYT Android Head Units] doctorman:
I came across this custom ROM thread in a search to get rid of the MCU Yellow bar and MCU upgrade notice after reseting the unit on original ROM.

I was able to get rid of the MCU yellow bar by using the Root and xposed module XSofiaTweaker

but still I get the MCU upgrade notice after reset/restarting the device...

so I went ahead and installed the custom.apk

installed Custom ROM

verified Twrp installed and then installed the custom ROM 4.9 alpha 3

and the MCU yellow bar and the MCU upgrade notice are back...

====

I have a second unit that doe snot boot at all , I think it the wrong bootloader...
[FYT Android Head Units] gtxaspec:
On the custom rom, did you emable xsofiatweaker with the mcu bar fix?
[FYT Android Head Units] doctorman:
I did no see it installed, installed it and enabled it, it took care of the yellow bar but I still get the MCU upgrade page pictured in the last post