yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Hilari0:
Did you wipe it when you upgraded to the sep1 update? That might fix some issues if you didn't I've had issues which were fixed with a wipe on this unit before, though I've stayed at the last 5.1.1 version for now, waiting until 6.0 is less buggy.
[Android Head-Units] edit:
I guess you don't know me... read my Q&A to get to know me better :)

---------- Post added at 07:24 PM ---------- Previous post was at 06:51 PM ----------

Update : I am using only 2 things right now on Viper

Viper Bass set to 100Hz Natural and +8dB

Viper Clarity set to Natural and +8dB

And the unit does an annoying poping sound and also distorting like crazy with XiiaLive Pro.... but not all the time... there are times when it works ok.... but if you use it long enough you will encounter sessions of pops and distort that can last as long as 3-5 minutes... then works again just fine....

Without Viper I can't really have a decent bass in my car, the default Joying EQ Bass settings push up a lot in the midrange .... the bass goes way too up for my taste..... I like a lot deeper bass that my speakers can deliver just fine without dawning up the mids with too much bass.

Wasted so much time today.... back to 7July firmware...

UNFORTUNATELY the 7July is probably the LAST one with decent usability for the ones that use Viper4Android and can't live without it :(
[Android Head-Units] Hilari0:
Yeah, didn't know you were one of the gurus on the Joying unit.. :)

I see you're having some issues with Xiia, I'm not using that. If you take away the issue with Xiia, are there other issues on the unit with Viper? I haven't actually installed Viper yet, as I mainly use the built in EQ to dampen the mid and put a mild boost on treble to make up for weak OEM speakers, then I use an external crossover to drive the factory subwoofer and I set the desired sub level through that one, so I am not sure if Viper can give me something I don't already have.

Instead of Xiia, I'm using TuneIn. Does the same issues apply for TuneIn as Xiia? Different apps, but I suppose they deliver similar content so not sure if it's implemented in a similar way in their respective apps.
[Android Head-Units] superdave:
Now that I have a modified boot with USB Ethernet adb going I am abe to see what's going on when trying to install Xposed. Turns out topjohnwu's oatfix is all that is needed I have v87 working on my 6.01 unit.
[Android Head-Units] edit:
Guru's a bit much but thank you :)

Well, before I decided to buy my unit I started to read all there is to read about it. After I bought my unit I started to test all there is and learn what I can.... so I had no choice but to adapt and try my best to make this unit my own and customise it to my liking.

Then I thought that the best way to give some back to the community is to write what I learned.

The issues are not only with Xiia, are with PowerAmp as well but with Xiia does happen more often and for longer periods of time. For me not being able to use Viper is a big problem so I did not test any further because if 2 of my most used apps are behaving this way probably all are more or less.

I am not a fan of TuneIn, they are really into making as much money as possible no matter the cost to the user. I bought the "pro" version and even that one had ads to their new programs that I had to close daily if I wanted to get to the app... really annoying. The interface was never a great one for in car usage due to the menus being white and at night time it's bad. The dedicated car interface I did not like either but the main issue with the TuneIn is that at one point they broke the way the sound is handled when the audio focus is partially lost (gps app giving away a message). Wrote them, they told me that they knew about the problem, I've waited for 4-5 releases over a period of months, nothing happened, wrote them again, told me the same thing, nothing happened... bad support, I've moved on.

Talking about support, the Xiia also does not have a great support, wrote them about an issue 6 months ago.... they released to 3 updates since then... the issue is still there... the issue being if the app looses audio focus completely (you press play on another music player) it continues to steam in the background eating away precious data instead of stopping.
[Android Head-Units] gtxaspec:
xposed finally. Time to roll a custom Rom for this once the MCU stuff is done... Great work!
[Android Head-Units] edit:
Just flashed the 7July firmware to discover that it does not work at all with the nolag version of the No-Kill Custom keys mod made for 1 Sept firmware :(

Oh maaan :(
[Android Head-Units] surfer63:
And why did you flash the 07 July instead of the 1 September? I can't think of any reason to prefer 07 July over 1 September.
[Android Head-Units] ste2002:
I believe it was a scientific roll-back experiment by edit, who previously reported on installing 1st Sept firmware.
[Android Head-Units] edit:
this was my short impression on the 1 Sept firmware, please read this : https://xdaforums.com/showpost.php?p=74240733&postcount=1248

I like to put in writing all my tests and experiments outcome so I can save others of hours of wasted time...

The problem with this unit, I said this in the past and I will said it again is the lack of people with skills and time to help others. Like for instance with the Viper4Android that it's a must for me to be able to have a decent sound in my car, since Android 6 it's functionality got worse and worse and no one can help us because the few guys that maybe have a shot of getting the unit to accept it via a patch/mod/fix does not have interest in the software in the first place so it will never happen (I say never because it's been months since Android 6 showed up). Of course I am not pointing fingers or blaming anyone here, is just the way it is. What people on the forum do not realise sometimes is that fixing, patching, reverse engineering takes a lot of time and I understand that some do not have it and some even if they have it they want to focus it on the issues that are affecting them instead of the things that are affecting others. Now with latest firmware, split screen not working, Viper barely working.... I still don't recommend an update from 5.1.1
[Android Head-Units] petro_ionut:
Waiting for a info to install, thanks gor tour work!
[Android Head-Units] edit:
Replying to myself here to update it :

So, what I think it happened :

During the wiping 1Sept and reflashing back to 7July firmware something happened and the Play/Pause, Next, Prev. Radio, Media, DVD buttons did not work. I presumed that was because I used the No-Kill custom keys that was made for the 1Sept release of the firmware.

Then I put the original Sofia back and... nothing... flashed back 1 Sept.... still nothing.... nothing worked... so a lot of testing and trying everything... I found out that somehow the option "MCU Panel Key" from the CarSettings was OFF.... I never knew what was doing until now... so the NoKill Custom keys mod made for 1 sept firmware actually might work on 7 July firmware...
[Android Head-Units] surfer63:
[MENTION=309187]edit[/MENTION]: For viper4android on 6.0.1 could you try (after the install of viper):

adb connect <ip-address>
adb root
adb connect <ip-address>
adb push viper_build.prop /sdcard/viper_build.prop
adb shell

mount -o rw,remount /system
cp /system/build.prop /system/build.prop.orig
cat /sdcard/viper_build.prop.txt >> /system/build.prop

use the attached "viper_build.prop.txt"

Check if your original build.prop is extended with the viper settings (cat /system/build.prop).

If so, reboot and check.

If necessary you could always copy the orginal build.prop back. (cp /system/build.prop.orig /system/build.prop)
[Android Head-Units] superdave:
I put the update file on my repo https://github.com/superdavex/joyingsofia

You could either install it with the new test keys recovery/TWRP or manually install it. Without the new recovery if something goes wrong you would have to reflash stock though.
[Android Head-Units] edit:
Did all that you wrote, made sure that the contents of the "viper_build.prop.txt" file was inserted into the build.prop, restarted but unfortunately nothing was changed for the better. :(

With or without your mod :The STRANGE thing is if I ENABLE the Viper EQ it works perfectly, the sound is perfectly fine AS LONG AS I KEEP MOVING my fingers across the screen... like scrolling... in any direction... no matter the screen or app or there is an page that can scroll... simply rubbing the screen makes Viper work perfectly.

Thank you very much for the help !
[Android Head-Units] Hilari0:
Well, I think for the time being I'll stick to the last 5.1.1 version. I don't have any issues with it, and from what I can tell, updating to the latest 6.0 doesn't really bring anything new to the table over the last 5.1.1 version. Perhaps there are some benefits in security, but I don't think that has much to do with a car head unit. At least in my case, I never use it for web surfing or anything, I use it for radio, spotify and maps/gps and calling through BT, so it sees very little exposure to security threats.
[Android Head-Units] petro_ionut:
Can i try to install xposed with Flashfire, it will boot after that, without twrp?!
[Android Head-Units] edit:
If you update to the latest 1Sept androi 6 firmware :

1. Your bluetooth tethering speeds (if you use tethering via BT like I do) will be cut by 60-65%

2. the split screen feature that is built in android 6 and might be useful for some (although is more like a beta feature in android 6) does not work anymore "thanks" to Joying

3. if you use Viper it is severely crippled now and it worked so nicely in android 5

4. if you use the NoKill Sofia mod the media buttons does not have lag anymore on android 6 latest firmware thanks to [MENTION=5941858]Gusten[/MENTION] after he revised his mod - in android 5 never had lag with any release

5. Waze getting stuck if it's active while going to sleep

the only bugs corrected that I can think of from android 5 to 6 are the notifications that are display corectly now... not that white text on white background...

When and if the issues above will be corrected I will probably start advising people to upgrade.

As far as security goes, since is not secure at all like all the Chinese headunits I decided to have it;s own Google account that has nothing on it. I bought a few apps that I need and use and that's it. I don't browse with it, don't play games, don't install or test various apps with it.
[Android Head-Units] ste2002:
Does "OK Google" feature work on 5.1.1 ? Is 5.1.1 compatible with Google apps package?
[Android Head-Units] superdave:
If you use the version from my report it should. There is nothing in my boot that makes it work differently. I would have a stock flash ready just in case though.
[Android Head-Units] petro_ionut:
That will be awesome, i install tomorrow and let you know! Thanks alot...
[Android Head-Units] Hilari0:
Ok, point taken... :) It's really sad how poor software development from Joying's dev team is ruining this head unit. Save from the overheating issue which is somewhat easy to fix, it's a pretty nice head unit. Especially for the price.
[Android Head-Units] petro_ionut:
Flashfire gives an error when searching for the file, so no luck!
[Android Head-Units] petro_ionut:
I will try to install TWRP from [MENTION=238068]superdave[/MENTION] repo, then his xposed, then app settings module to modify dpi only for waze and other!
[Android Head-Units] bogdi1988:
Is the unit doing any file transfers in the background when it's popping and distorting? I have issues similar with the May update and that happens when it's updating apps from the Play Store in the background - the unit works like **** then...
[Android Head-Units] lob3s:
So I just installed my Joying sofia head unit this weekend and I have a quick question regarding a firmware downgrade. My head unit shipped with the May 25th - 5009 MCU and the September 1st 6.0.1 firmware update. Is it possible to downgrade this firmware to the April 27th release? I'm running a USB DAC and the last release of the USB DAC volume control mod is made for the April 27th firmware. It'd also be nice to get Viper4Android working, and I'm having a hard time getting it working on this firmware release. I've noticed people downgrading their firmware in this thread, but is my request possible since I'm trying to downgrade the firmware to a version prior to my MCU update?

Thanks everyone!

__________________________________

EDIT: so I performed the downgrade and it was successful! My firmware downgraded, but it seems the MCU was not- still at the May 25th MCU.
[Android Head-Units] edit:
You can downgrade from any android 6 release to any android 6 release. You cannot downgrade from Android 6 to 5. Not all the firmware have MCU updates in it and most likely the 27April Firmware does not have one but as long as it's stable you can keep the current MCU version.

I did not encounter issues running old firmware with the latest MCU update.
[Android Head-Units] edit:
Nope, nothing happened in the background and I was testing the unit for at least 5-6 hours. There was only 1 app running at a time and that was the music player, no GPS app running or other piece of software, except the Viper that runs all the time in the background and the music player was not in the background while the popping occurd.

I had to downgrade to 7July that does not exibit the same issues but the Viper functionality is still limited compared to Android 5.

From the looks of it I will be stuck on 7July version for a long time if not forever because I can't picture this unit without Viper :(
[Android Head-Units] lob3s:
Good to know. Thanks for help!

I just performed the USBDAC SofiaServer mod (main reason I downgraded) and I still don't have volume control of the DAC. Is it possible that the SofiaServer mod doesn't work because I'm running the newer MCU update? Not exactly sure where to go from here.

On the bright side, I should be able to get Viper4Android working now.
[Android Head-Units] RoNeReR:
u create the USBDAC file on internal storage?
[Android Head-Units] lob3s:
I created a USBDAC folder. Should it be a folder or a file?

I also applied the audio_policy.conf mod, as well as the 4-27 USBDAC SofiaServer mod. Should I revert back to the stock audio_policy.conf and retry just the USBDAC mod?

Thanks for the help!
[Android Head-Units] RoNeReR:
need to be a file, on root of internal storage.

i use the july firmware with the 4-27 USBDAC SofiaServer mod no other change to audio_policy and it work great.
[Android Head-Units] luciusfox:
Yes you can.

The downgrade restriction was strictly joying being dumb.

And yes, they added this idiocy into their recovery images as well.

Use of superdave's test keys modified recovery will permit you to install customized update zips.

So yeah, no problem to modify the update.zip for 5.1 to trick the recovery and install... or use the "temporary twrp". Whatever. Easy.

---------- Post added at 02:47 PM ---------- Previous post was at 02:26 PM ----------

The MCU has no involvement with audio whatsoever. The only function it has that even remotely approaches audio, is that it relays commands to the AMFM radio.
[Android Head-Units] edit:
My dear Luciusfox,

I asked you before and I will do it again, again and again : Stop looking at problems and give answers, from your point of view, of a highly skilled programmer when a lot of the people here do not have 5% of your knowledge and experience.

Yeah, I have no doubt that for you downgrading is a piece of cake, if you set your mind to it you probably do it in an hour top..... for me (and a many others), is like asking me to rebuild an Ferrari Enzo engine when my only skill in life that I am great at is to design buildings.

When someone will test and succeed downgrading an Joying HU from android 6 to 5 and make an step by step tutorial that anyone can follow without bricking their units (or make a tool of some kind) I will tell everyone that downgrading is possible....

Till then, NO, it's not possible... for the average Joe that I keep talking about.
[Android Head-Units] lob3s:
Well that's good to know. A little bit over my head, but good to know if I need to go back to 5.1.1 to get my DAC working in stereo.

It's great to see all the dev working going on with these Intel Sofia units. Makes me very happy with my purchase :D

---------- Post added at 01:25 PM ---------- Previous post was at 12:27 PM ----------

Okay. Before I had my usbdac file on the root of the external SD card (I misinterpreted /sdcard/ as /mnt/external_sd and not the internal storage, stupid me). Created the file via ADB (was using a file explorer before, used ADB this time just to be sure). Performed the mod, and its working!

I still have two small issues, but I think at this point its the hardware of my DAC that's not playing nicely with Android 6.0. My sound is outputting in mono, which seems to be a common issue with many DACs in Android 6.0. I ordered another DAC- a SA9027 + ES9023 based DAC that is supposed to be compatible with Android 6.0, but it won't be here for another couple weeks (shipping from China). In the mean time I'm using USB player pro to get sound in stereo, so far so good.

Another small issue I have, which really isn't a big deal at all, is that the toast volume notification that appears on the screen doesn't correspond to the volume output 100% correctly. So when the volume bar is at 1/4, my DAC is actually muted. This isn't a huge issue to begin with though, so I'll just disregard it.

Thanks so much for the help, RoNeReR!
[Android Head-Units] tOz666:
How can you run this temporary TWRP? I'm interested in nandroid backup the unit (and be able to restore the backup)
[Android Head-Units] zeroasylum:
Need Some advice on unit stability

Hi all,

I hope I have put this in the right thread. I purchased a AU-JY-UL135N2 in March this year. It was fine for the most part but I developed issues with it recovering from sleep mode and crashing. Ever since I have updated the unit to android 6 (September 1st release) it is constantly crashing and unstable. I get messages that services have stopped and it never recovers from sleep mode without freezing. I have flashed it several times with no change in its behavior. I have followed the procedure from the FAQ number 7 several times with no luck. It regularly give the message “Has not been fully launched 3 times,the machine self-test, it will automatic restart after!””. Also some mornings when I start the car it will reboot and do a complete factory reset. Is this a hardware or software issue. What do people think is it a hardware or software issue. Advice please.

Thanks

Zeroasylum
[Android Head-Units] RoNeReR:
ro.config.media_vol_steps=30

add this line to build.prop to get more steps on volume,

i use hifimediy sabre u2 dac. i dont have any problem with stereo.

my problem is the volume too loud even on lowest option, so the solution for me is use the volume on my sound processor(jbl ms8).
[Android Head-Units] lob3s:
Sweet, I'll try editing my build.prop. Thanks!

The DAC I have coming in the mail is also based on the ES9023 found in your DAC, so I think I should be able to get stereo sound on Android 6.0.
[Android Head-Units] Need4Camaro:
Guys I need serious help here.

I'm still using 5.1.1 and Joying is requesting that I upgrade to Version 6 and the reason is because I am having problems with my GPS. When I am driving, my GPS completely loses signal, ALL my navigation apps stop working, google maps, waze, ect. They all start going beserk for no apparent reason, switching my location all over the map when I haven't moved anywhere, Waze telling me Im going over 100 MPH when Im not even moving. I bought a new GPS antenna and replaced it and even relocated it and it did not help. Will upgrading to version 6 be worth it, and will it fix this issue?

I have already modded my 5.1.1 to accept Ok Google commands and modified the bluetooth app.. will I beable to do this on Version 6?
[Android Head-Units] ste2002:
Need4Camaro, do you have any custom processor cooling? Some owners reported bad GPS when chip overheated.
[Android Head-Units] alessondanilo:
I've been looking at this topic and it seems to be possible to go back to Android 5.1.1

https://xdaforums.com//android-auto/mtcd-discussion-questions-development/mtcd-intel-sofia-units-wifi-3g-t3533154/post73885838

I needed to do a downgrade, because I'm having a lot of problems in version 6.0
[Android Head-Units] luciusfox:
Don't install that, its for an MTCD.

Install custom keys recovery.

reboot with temporary twrp.

Install 5.1 update.zip.

Easy.
[Android Head-Units] Need4Camaro:
I do not. Is this necessary? If so..how would I do it?
[Android Head-Units] luciusfox:
oh my god, its so hard to install a custom recovery.
[Android Head-Units] Need4Camaro:
Can you please show me where I can get the latest 5.1.1 update? I cannot find it anywhere on Joying's site.
[Android Head-Units] alessondanilo:
Could you provide me the 5.1.1 update link?

I'm going to downgrade today.
[Android Head-Units] luciusfox:
It is absolutely necessary to add cooling. Not just to make GPS work (I cannot confirm if it will have any impact on GPS at all), but to actually keep the CPU operating within its designed thermal limits, the upper most of which is 85 degrees C, yet as these things ship, they easily reach 100 degrees C.

Also, adding cooling will make them significantly faster, since keeping it under 60 will ensure that you are able to run the CPU at full speed, rather than throttling all the way down to 416 MHz.

How? Go to amazon, find an aluminum heat sink that is approximately the same size as the aluminum plate on the top of the SoM, get some arctic aluminum or silver thermal epoxy, and also a 5 volt fan. Use the thermal epoxy to glue the heat sink to the SoM. Screw the fan to the heat sink, and wire it up to one of the USB wires.

For best results, do NOT reinstall the radio's metal cover. Leave it open to allow the hot air to escape from the box.

---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------

its on the manufacturer's website in the "blog" section.
[Android Head-Units] alessondanilo:
Okay. But as far as I know twrp only installs files in zip format. Will the 5.1.1 update be read correctly by twrp?
[Android Head-Units] superdave:
After my unit was on for several hours the GPS would always crap out. Complete signal loss. I can't see how that could have been anything but overheating. After the system was off for a bit and it cooled down the signal would return. Nothing else changed. I was also on 6.01 and it did not make a difference. My hardware is crapped out right now, but, I wouldn't use it again without putting cooling on it. Even with the lid off it still overheated.
[Android Head-Units] luciusfox:
It *IS* in a zip format.

Its a regular old "nothing special about this" android update.zip.

Download their stupid archive, extract it, and find the 5009_20.zip <-- that is your file. Regular old every day Android update.zip.

You may need to take out a line from the updater-script though, near the bottom, the line starts with "intel_install_firmware_update". It will give you an error if you don't take it out, but probably doesn't matter, since its the last thing the updater-script actually does.

When you're in twrp, you will also want to perform a full data wipe.

And when you finish the install through twrp, reboot to recovery again to install the joying update the "normal" way, since the twrp update will leave out the allapp.pkg, which means that it will keep rebooting itself due to no heartbeat signal to the MCU.

But personally, I wouldn't bother dropping version to 5.1.

They're ALL buggy as heck.

But there is big work being done specifically for 6.0.