yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] gustden:
What installer are you using? It looks quite a bit different than the one I used.

install.bat

@echo off

adb kill-server
adb connect %1
adb root
adb connect %1

adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /

adb shell "mkdir /tmp"
adb shell "mkdir /tmp/supersu"

adb push chattr.pie /tmp/supersu/
adb push install.sh /tmp/supersu/
adb push install-recovery.sh /tmp/supersu/
adb push libsupol.so /tmp/supersu/
adb push su.pie /tmp/supersu/
adb push Superuser.apk /tmp/supersu/
adb push supolicy /tmp/supersu/

adb shell chmod 0755 /tmp/supersu/install.sh
adb shell "cd /tmp/supersu/ && sh install.sh"

adb shell rm -rf /tmp/supersu

echo Reboot your Head Unit NOW!
[Android Head-Units] psxsnake:
I'm on fedora linux

Seems the command adb root doesn't work
[Android Head-Units] surfer63:
You are using my script, but the 6.0 version comes without adb over tcpip. So the script won't work. You first need to enable adb over tcpip, before you can use my script to root your 6.0 unit.

Do you know how to do that? It is explained twice in this thread but did you read it and do you know what you're doing?

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

No, it's one command earlier

error: protocol fault (couldn't read status): Connection reset by peer

As said: adb over tcpip doesn't work out of the box on the joying 6.0 version.

You need to download a terminal app, open it and use the command "setprop persist.adb.tcp.port 5555", and the reboot your unit.

Then the script will work.

gustden is still using the old script for the previous version of the supersu binaries.
[Android Head-Units] psxsnake:
Yes I did

and I chacked too if the 5555 port was up by netstat -na|grep 5555

is in listen on all IP

and if you see the second time connection is ok
[Android Head-Units] edit:
1. Launch PlayerPro

2. Go to settings

3. go to Headset section and enter it

4. Tick the "Active override"

That should solve your problems
[Android Head-Units] surfer63:
Please try with "sudo" or "su -c"
[Android Head-Units] hoang.pham:
we should still be able to use the modded apk for volume control since the DAC support is now inbuilt with Android 6 right?

it seems all signs point to upgrading to 6 and development will continue on modding 6 as opposed to 5.1?
[Android Head-Units] psxsnake:
What you mean?

adb sudo cp yyy xxx

?

but with sudo meand is rooted....and i should have password of root, no?
[Android Head-Units] TransAmMan:
Thanks! I'll give that a try today.
[Android Head-Units] AssassinsLament:
I'll update it once gustden updates his mods.
[Android Head-Units] surfer63:
If your user is not part of the group being able to access adb for some authorization levels, you might try to start the script with "sudo ./install.sh" to get root rights.

If your normal user is setup as part of the sudo group, you can use sudo which requires your own password.

To be able to set adb to root mode, you need those authorizations to do so. I don't know fedora well enough, but maybe that is what lacking a normal user. sudo would help in that case.

If you are on fedora, you can also make yourself root using the su command, which needs indeed the root password.

Finally, are you able to use adb over tcpip to other android devices like your phone?
[Android Head-Units] psxsnake:
I runned the script copy_install.sh (that one from github) from a terminal, as root if that you mean...

I wrote fedora before but i should say linux
[Android Head-Units] hongkongrr:
Where is the setting for this? I don't see it in the debugging menu.
[Android Head-Units] gtxaspec:
See
[Android Head-Units] AssassinsLament:
Don't forget to mention that you replaced your Settings.apk with the original 5009_20.zip one. lol, I was searching every where for it in the settings also and couldn't find it until I realized maybe you had already replaced your Settings.apk
[Android Head-Units] gtxaspec:
Ah yes, forgot to mention that. :)
[Android Head-Units] edit:
Does your new unit (6021) has a bigger cap than the last one (5009)?
[Android Head-Units] kampfschachtel:
I don't know but not huge, from the visible physical size I would expect max 2000pikoFarad.

But I don't mean replace it inside the unit.

I mean something like this: https://www.ars24.com/zubehoer/entstoer-material/6925/audio-system-e/cap-cap33?c=1000168 with a 33000piko farrad one.

Side effect of it is that is also cleans the power cable from distortions from the generator and other sources. THe powercap delivers the high current peaks as it saves them and delivers them if needed. need to be place as close to joying as possible.

The joying "eats" around 6-8 A when playing at volume level 28 of 36 now, at absolute full power undistored around 9-10A over preouts (the internal amps amplify too even they are not in use). If you look at the dimension of the red power cable of the unit and the cable length from battery to your unit the used 1,5mm cable is quite bad means of around 14V (if everything works perfect and your car battery is silghtly oversized) the joying gets around 12.8V and this is in an supercar which has a very good cable length as main battery terminal is around 1,5m away, in a normal car its around 5-7m cable length=worse. the minor "interrupts"/reduction of of voltage are not measurable without a Oszi but from my experience it goes down to 11.5V-11.8V, some peaks even below 11V as the resistance of the cable grows the more ampere is drawn.

So the power cuircuit of joying has to work a lot to get that sorted but its actually not very good at that, a 2000 piko cap has not much to buffer....

my experience:

I had the Audision DSP on the same power cable as the joying when installed in dashboard but I moved it now in the back as close as possible to the B&O amp and for this I used also a different power source for the DSP, the one that the B&O amp uses (a thick 30mm power cable direct from battery). Means the power cable to joying in the dashboard (the original from the Audi connector) has now less ampere to deliver=less resistance=less voltage loss and therefor joyng gets more volts=circuit needs to sort less and that resulted in more dynamic and was clearly hearable.

Next time I take the glovebox out I will route 10mm cable directly from the main battery point (you need to root a 4 or 10mm plus and a 4 or 10mm minus cable!!) to the joying but I expect I need then this cap too as the direct battery terminal delivers not a cleaned power.

Thats total overkill, a 4mm will perfectly do it but I have around 30m 10mm cable lying here but no 4mm, so I will use this. The powercap itself should actually sort it already but the 10mm cable will help the cap to reload faster=more buffer support and the effort to root the cable is near 0, main battery point is behind glovebox and direct shortest distance to joying is aprrox 60cm...
[Android Head-Units] tuff40:
Any of you guys from Queensland Australia. Wouldn't mind having a beer and a chat about this unit. Slowly making my way through this thread and it seems to be all over the place.
[Android Head-Units] edit:
Read my Q&A first...
[Android Head-Units] tuff40:
Legend, thanks for that.

That should get me started. Was almost going to give up on this joying head unit and then remembered that there were a few discussions on xda. After my 4.4 Kit Kat died and was replaced with the 5 I haven't been happy with how it operates.
[Android Head-Units] edit:
Man, you went above and beyond for the sound quality but to be honest I think I would do that too if I would have an R8 :)

For my Ford I feel comfortable with smaller mods.

Thank you for your thoughts !
[Android Head-Units] dyabolikarl:
I am
[Android Head-Units] tuff40:
Where snouts, I am on the gold coast. Will go over edits thread and if I get stuck and ur local might grab ya for a beer.
[Android Head-Units] dyabolikarl:
~25min E of brisbane CBD. I pretty much followed all the threads on here to get a usable product.

I don't really do any internet based stuff on the unit. Just torque and music.

Maps etc etc i have installed but rather use my phone as it's faster.
[Android Head-Units] tuff40:
Just wondering if anyone else has had problems with their android 5 or 6 connecting to obd2 adaptors. My kitkat unit worked perfect and now the newer 5 or 6 wont pair with 2 different obd bluetooth units. my phone and tablet work perfectly. when pairing, the hu will ask for the pin on one and will not except the pin and disconnects. the other unit will not even ask for a pin and just disconnect.
[Android Head-Units] rhino6303:
Here is what I do to connect to my adapter:

1. Change stock bluetooth pin to pin of adapter.

2. Create a widget/shortcut to the bluetooth settings on the main screen. This takes you to the android bluetooth menu where you can pair to the device.

This works on my Joying Android 5.1 HU which is non rooted and basically stock. It survives reboots as well.
[Android Head-Units] tuff40:
So I just tried this and when I try to open the widget it opens and then just closes straight away.
[Android Head-Units] TransAmMan:
On these newer units, on the radio you must change the pin to 1234 or obd2 adapter won't connect.

Clear joying Bluetooth from your phone.

In joying Bluetooth go into settings and change the pin to 1234, be sure to hit "confirm"

Now resync your phone and obd2 adapter with 1234 as pin.
[Android Head-Units] tuff40:
I tried that and did not work.

But I did try it after I installed the Bluetooth MOD and I had to revert back to the original. But from I understand it reverted it back to an earlier version which is now very unstable on my July upgrade.
[Android Head-Units] tuff40:
ok so i installed the extra tools 1.3 and the Bluetooth works. can now pair with the obd sensor after changing the pin. sofia installed, viper installed.

I ran into a similar problem with the radio mods where it deleted all radio icons but the radio was still playing in the background. i also noticed that when i restarted with the prompt after install it did not restart correctly. the radio still played while the screen went black and the android logo appeared. instead, i said not now and did a manual restart.

last thing the settings mod did not work for me, first i reinstalled the joying restarted the tried the android settings mod. it does the same thing as before. installs fine reboots and settings don't load and when u try to open settings it closes straight away.

thank you so much for the work you are doing, keep up the great work.
[Android Head-Units] surfer63:
Radio: This works via a 2-step approach. CarRadio.apk access the FM chip and controls it. Radio.apk is just the android frontend that "talks" to the CarRadio.apk. That's why it keeps playing on the last station as the CarRadio.apk still functions (but can't be controlled). Reinstall the default joying radio again, reboot, and try another time. The 6.0.1 joying ROM is very picky.

Settings: Reinstall joying version again, reboot, try to install the standard android settings again.

Note: if it is (only) about bluetooth you need OR Treels mod OR the android Settings app.

And please mention whether you are on 6.0.1. (I assume) or 5.1.1.

And if on 6.0.1: which ROM version?
[Android Head-Units] alexyie:
anyone know any app / floating widget that I can use to turn off the screen in one tap (or one tap to the app and next tap to turn off screen)?

the existing floating (touch assist) button had the "screen off" menu moved to 2nd page of the app, so it is very annoying (and difficult) to turn off the screen while driving.

I have tried "Screen Off" app from playstore, but it needs to be Device Administrator and then once i tap on the screen off the device crashed and cannot be turned on again before 1 unplug the fuse in my car
[Android Head-Units] iRawrz:
I just successfully rooted and followed the instructions to install Viper4Android and now I've lost all audio and volume controls. The headunit also reboots randomly every 10 minutes. The reboot and shutdown tile also do not work properly, they do nothing.

Any guidance or instructions on how to fix the audio and rebooting or how to do a full factory reset?
[Android Head-Units] Thaxyllis:
Upgrade to 6.0.1

Hello

I ask for advice. Recently I updated my Joying 2GB Intel Sofia with latest 5.1.1 (that was last version before 6.0.1). This version is pretty good beside that the unit on previous versions was going into dormacy after night. In this version its not doing that. After 2 days its still like after turning off ignition a minute ago, powers up instantly. Dormacy setting is turned on in car settings. Is it possible to make it work?

But here comes main question. Should I update to 6.0.1? Its one way ticket. Is it faster, better? everything works? Power antenna opens only when radio app is used?
[Android Head-Units] edit:
If you ask me, no. Although the latest firmware (7july) is pretty good but there are still various issues.

It's one way ticket, no turning back so my advice is to read carefully my Q&A and the Android 6 thread before upgrading.

If you rush into upgrading you might encounter problems with Android 6 that might make you regret the decision... and at that point there is nothing you can do about it.

I don't find it faster or better... but like I said before... you win some, you loose some.

Overall yes... but if you are the modding type, the android 6 has more quirks that drove a lot of people nuts (including me).
[Android Head-Units] danstah:
For the life of me I can't find the setting to turn on split screen (multiwindow). I've seen a screen shot of where it should be in developer options but it's not there for me. I'm running the latest update (Jul 07). Also trying to use Joying extra tools app to install android settings app vs the standard joying one but it would just keep force closing when trying to open. Anyone have any help. Maybe I'm just missing something

---------- Post added at 09:46 AM ---------- Previous post was at 09:28 AM ----------

Also seeing the same issues with the radio and setting on extra tools 1.3 and the July 07 update.
[Android Head-Units] edit:
Please read my Q&A and you will find out...
[Android Head-Units] danstah:
For others reference here's the link to the thread edit mentions

https://xdaforums.com/android-auto/android-head-units/intel-sofia-to-micro-tutorials-qa-t3616074

It looks like I was on the right path but when I went to replace the settings apk with the android one, however there are issues with doing that and the new update. Were you able to replace the settings apk on the July 7th update and enable split screen mode?
[Android Head-Units] edit:
The link is in my signature that's why I did not placed it in the reply.

Yes, I replaced the settings.apk, enabled and used the split screen mode.
[Android Head-Units] surfer63:
That is indeed how it should work. The Android Settings.apk should work on any 6.0.1 Joying version.

Anyway: I just released a new version that pushes the Settings.apk from the relevant 25 May or 07 July ROM version.
[Android Head-Units] halal:
Press and hold "Mute" button
[Android Head-Units] kampfschachtel:
[MENTION=309187]edit[/MENTION]: you write 7th July is very good, when I read all the threads it's the opposite: BT frequently disconnects, mods don't work....worst upgrade ever.

I need to reflash due to BT totally gone so I can do upgrade to 7th or reflash 25th...I just wanna have a stable running unit without the need to reflash it because something is gone or suddenly not working. BT must work as I need it for OBD dongle plus GPS external for driving logbook as I use car for bussiness.
[Android Head-Units] edit:
If you are refering to this post : https://xdaforums.com/showpost.php?p=73195188&postcount=1005

I said pretty good... means close to good.... so it's not good or very good and I also mentioned that there are still issues. On top of that I still advise people to stay on Android 5 and read everything there is to know about 6 and only then think really hard before deciding to update.

In the meantime I found a ugly bug, when the FM Radio app is in use the voice from Waze and Google Maps can't be heard anymore. So I can demote the 7July update from pretty good to bad.

It looks like you haven't used the first releases of the Android 6.... now those were indeed worse. All I can say is, if 7th update is really bad for you all you can do is take 1 step back... 25May release... if not... 1 more step back 12 May.

Use what suits you best till they come up with a more decent release. Because we don't have the skilled user power to make them better we have to wait and hope they will release a good (bug free) firmware at one point.

Current issues for me - if these are solved I will stop looking flashing new updates

1. the FM Radio issue specified above

2. the GPS speed displayed is not smooth but in 3.6km/h increments

3. BT disconnecting issue - I can't speak of that because I only use BT to data tether the unit and for me it works flawless this way (with [MENTION=6124077]doitright[/MENTION] tether app)

4. EQ section of the Viper4Android does not work anymore

5. Xiialive instability
[Android Head-Units] kampfschachtel:
Thanks. I was forced to use 6 as my replacement unit came with it installed even I told joying explicitly I want a 5 unit.

I would have stopped flashing with 25 March 5.1.1, done all want I wanted till my flash ROM chip died and unit needed to be replaced on warranty which costed me additional 150CHF.

I am stucked with 6, so I am looking for the best of the worst that's available. From all threads I read the 25th seems best so far.

Must are:

Apps/software

Rooted, viper, BT mod, google maps, xiinalive, dab+ realzulu version, Spotify, torque, Carly VAG pro, tablet talk (remote for phone to use OEM BT hands free kit), fartenschreiber pro (tax authority approved drivelog app with external BT GPS support), own bootanimation, Harry's lap timer=> all worked with 5.1.1

Hardware supported

Bluetooth: Carly OBD dongle (for Carly and torque app), external 10hz GPS Garmin BT Modul

USB out to DSP=> sucks with all 6 versions, RCA output is better.

With 25May continuous BT troubles causing nothing of my BT stuff works, apps disappearing or functions disappearing, instable, wifi disconnects with Spotify, SD card mess so eg Spotify offline songs get lost regularly...

Will try 7th July now...

Only 2 postiv about 6:

1) dab+ works perfectly, no cripples even with Google maps, how much is 6 and how much is realzulu's excellent work I cannot judge...

2) sound quality on level of external USB DAC, again how much is the better 6021 hardware and how much is 6 I cannot judge...

All other is worse with 6, a lot stuff unacceptable like BT, instability, xiinalive performance....
[Android Head-Units] edit:
I was happy using 25May till after 2 weeks encountered an issue : Each and every time I use the FM Radio app, no matter if I ran other apps with it or not the units shuts down instead of sleeping. The FM Radio app plays nice with Google Maps and Waze voice in this firmware but it's useless for me if it shutsdown my unit.

In the 7July I was happy that they made the Google App work so I can search addresses by voice, I can make traffic reports by voice in Waze.... but they messed up the FM Radio... so.

It's frustrating that they don't seem to bring an 100% functional and stable firmware after all this time.

I am not even getting in all the strange quirks that the unit has if you get into modding stuff.

All I can say is : start complaining via email to Joying, I write them every single day... since they refuse to release the code they are the only ones that can fix it.
[Android Head-Units] gessi2000:
Can you please explain how the Joying Extra tools helped to connect to ODB? I have same issue on my 8" headunit running 6.0.1 and trying to pair with ODB2 using pin 1234. I can confirm it works on my Android Smartphone but the Joying Bluetooth App tells me I am using wrong PIN!?

How can you change the Pin at all?
[Android Head-Units] Erik_DK:
Do tell me as well, Super SU from github.com/hvdwolf/Joying-RootAssistant/releases/tag/20170617-02 just says "Root undetected"

Edit: this post explains it much better: https://xdaforums.com/android-auto/android-head-units/how-to-root-joying-devices-t3614933

You have to run the SuperSU from a command prompt with administrator rights on your PC

Would it hurt to tell what's done on the PC and what's done on the unit?
[Android Head-Units] Clandaries:
Maybe someone can port the new DSP app from Joying?

They are not willing to ship their new devices from German warehouses to EU. So they can keep their new devices in China....

Maybe there is one who have those skills? ;)

Thank you
[Android Head-Units] edit:
It has a hardware component (the new amp) so in my opinion there's a pretty big chance it may not be possible

Rephrase this please because I do not understand what you mean... it's a contradiction between phrases... "ship new devices from German" but "keep new devices in China"

I am sorry to say but we don't have people with that kind of skills, time and determination. We had 2 but one did not show up for months and the other was banned from the forum so...
[Android Head-Units] Clandaries:
They sell from German warehoses or ship from German warehouses.

I have asked them to ship the new 7 inch the new 8 inch and the new 10.1 inch from Germany but they dont want to, or maybe...

So if i have to buy from China it will cost 400-500 Euro incl. tax and shippement, for those crappy china radios? Never. Then i buy Pioneer again or Kenwood or JVC or something else.

I love my android radio but i am not willing to pay so much money for a radio worth about 200 euro.

Greetings

Doublepost...
[Android Head-Units] edit:
I agree, I live in Europe too and buying from China gets really expensive because my country has high import taxes and VAT.

I think you should wait because I am sure they will bring them to Europe at some point... they need to sell as many as possible after all.
[Android Head-Units] 2hdass:
I was using the app to update the settings.apk, but then it removed all settings apps and now I have no settings app, and it seems like it is unable to download the settings.apk from inside the app?
[Android Head-Units] surfer63:
Please be more specific next time: Android version, ROM version. Did you try to reinstall the joying settings or not? Is your WiFi stable in the car?

Please attach the logs (/sdcard/JET-YYYYMMDD.log) to a post, or PM them to me.
[Android Head-Units] surfer63:
I found (another) bug in the 07 July version.

The PS text is suddenly missing in the Radio app.

Anyone else experiencing this as well?
[Android Head-Units] surfer63:
:o

I feel such a beginner!

After flashing I had forgotten to switch on RDS in the Radio Settings.
[Android Head-Units] Clandaries:
Hehe ;)

Is it worth to upgrade? i am at the 25.05.2017 version, and everything is working so far.

Thank you
[Android Head-Units] kampfschachtel:
Who had been banned from the forum which such skills???
[Android Head-Units] edit:
That would be [MENTION=6124077]doitright[/MENTION]

He is very skilled... If he sets his mind to it I have no doubt that he can correct almost all the problems with our unit... I am not sure that he is interested in doing that or helping us though...

---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------

Haha, noobie :)

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

I think it's a good idea to wait till the new firmware comes along... especially because what you have right now works