yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] AssassinsLament:
TomTom GO works without risky bootloader mod.

EDIT:

Viper4Android installs correctly, but to get it to "process" you need to remove the deep buffer section in /system/etc/audio_policy.conf

remove:

deep_buffer {
sampling_rates 48000 | 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE
flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
}
[Android Head-Units] brunes:
Android M (6.0) is when Google added "Now On Tap" support to the OS. Above folks confirmed the Google Now app now responds with proper TTS audio. If someone can confirm that "Now On Tap" also works, that would be pretty cool. M is also when per-app granular permission control came out which is good from a security point of view.

M is also when they added automatic app and data backups, so in theory the NEXT upgrade after this all your apps and settings will come back...
[Android Head-Units] brunes:
So I took the plunge and installed this update. My review

- The only launcher it ships with is the crappy "new launcher". The "old one" is now totally gone. I installed Nova.

- No noticeable changes at all to any stock apps, all exactly the same.

- At first, the Google Now voice response did indeed work out of the box after I installed the Google app. HOWEVER, after doing all the auto updates in the Play store, it STOPPED working. I then tried rolling back Google Play services, the Google app itself, and many other things, and COULD NOT get it to work again. I think to get it to work I am going to have to hit the reset button and start over. Very annoying and frustrating.

- CarMediaServices under the "3368" code seems to have a few more options, but I am not 100% sure without a side-by-side compare.
[Android Head-Units] AssassinsLament:
I've installed most of my normal apps, and it's still working. Updated Google Play services also. So maybe it's some other app causing it to not work?
[Android Head-Units] brunes:
I uninstalled pretty much everything. The only other thing I can think of is I paired Bluetooth???

I've packed it in for tonight, will run some more experiments tomorrow.
[Android Head-Units] gtxaspec:
The pull down white text color issue is fixed with play music and other apps in 6.0. yay!

it seems the recovery was updated, i am unable to boot into the recovery menu from the last rom. see attached photo.
[Android Head-Units] AssassinsLament:
Paired with bluetooth also, seems to be working fine. Dunno... :(

-

Attached is a viper4android install script I quickly put together for the Android 6 Joying update. Just unzip and run viper.bat <ip address>

Must be rooted, must reboot after script, then must run viper4android and allow it root access and to install it's drivers, then should work after a reboot.
[Android Head-Units] tuuza:
Does the method 2 still work for root and SU?
[Android Head-Units] AssassinsLament:
Yes.
[Android Head-Units] xdamember2:
I may have had that. It's ok after a factory data reset.
[Android Head-Units] bogdi1988:
dammit :( i don't want to do yet another factory data reset hahahaa :crying::crying::crying::crying:
[Android Head-Units] xdamember2:
Of course. I've gotten to like it better after rooting and saving app settings with Titanium. I'm not brave enough to save system settings yet.
[Android Head-Units] BassRareba:
I just noticed that i used the 5.1 to 6.0 update file instead of the 6.0 to 6.0 one.

Now i know that MAYBE the difference is just that the 6.0to6.0 is just already properly renamed...but since even after two factory resets the issue is still there i just hope that's the problem and i can get away with it a proper firmware flashing.

I will try to use May 8's firmware as well...i'll cross my fingers :D

Anyway i wrote to Joying :)
[Android Head-Units] edit:
I updated from 5.1 to 6.0... then reflashed 6.0. to 6.0 (the same firmware version, the first one released) a few times, then updated from 6.0 first version to the 6.0, 8 May release, a few times... then updated again from 6.0 (8 May) to 6.0 (12 May) then noticed the screen brightness issue (not low enough when set to 0 for the 12 May firmware) so I went back to 8th May firmware, measured the screen brightness with an Lux Meter app and then upgraded to 12th May again to measure the screen with the same Lux meter app.

So I flashed the hell out of the device, wiped it countless times.... And it's perfectly fine as it should be.

I'd say you have a hardware problem, not 100% sure but all that you said leads me to believe so.

The way I see it you have 2 choices :

1. you either buy a spare part from China and get it in a week via DHL and repair the unit yourself if you know how to

2.or send the unit to China for free warranty repairs and it will take around a month and you'll have to live with a hole in the dashboard
[Android Head-Units] BassRareba:
It's what i thinked as well.

However before having my car without a radio for 3 months at least i will try ANYTHING in my power to not come to that
[Android Head-Units] edit:
Yes, of course, by all means ! Good luck !
[Android Head-Units] p33t-r:
So if I understand correctly - you fixed the GMaps muting issue with FM Radio?

I contacted Joying support with this issue, emailed them a few detailes.

It is obvious that there is a problem with muting audio channels/stream with FM radio. Seems that FM radio is using a different than "Media" channel to play, while Google Maps/TTS uses Media channel for sure. In my Navi/antiradar app that I use (Yanosik) there is an option to change the channel. With Media and Alarm channels there is a problem, with Notification and System channels everything is working fine.

I was wondering which Joying app sets the channels for Radio/Music player etc. and tells the system which channel to mute. I was thinking about exctracting the FM radio app from 5.1.1 software and putting it to 6.0, but I can't find the apk file in the zip files. I can't install the 5.1.1 now to exctract it from an installed system.

Or maybe switching the Sofia Server app will do the trick?
[Android Head-Units] gustden:
Can you share what you modified to fix this issue?
[Android Head-Units] xdamember2:
Here is my apk, it's based on the no-kill modified version. I did not test it extensively.
[Android Head-Units] gustden:
Excellent, seems to be working :)

So you are preventing the modification of any stream volumes to zero through ToolkitApp/setStreamVol()? Just wondering if this will affect anything else.

./app/ToolkitApp.smali =============

2216a2217,2218

> if-eqz p1, :cond_2

>
[Android Head-Units] BassRareba:
Now i'm in a state in which for some reasons the physical keys aren't working BUT the device turns on regularly.

However as soon as i go to car settings the screen becomes black but i can still use the device.

I'm starting to think this is definetly a software issue of some kind.

I made some videos with my phone...i'll post them as soon as they're uploaded
[Android Head-Units] edit:
If you are on android 6 make sure the MCU is up to date... can't think of anything else.

On settings, About device check the MCU Version, It must be built in 2017... if it's the 2016 version means it did not get update properly and maybe after update it gets back to life?

Updating the MCU erases everything on the unit so backup before if you need to.

After that wipe everything, flash again.
[Android Head-Units] xdamember2:
Yes, that is what I'm doing. It would make sense to check the stream parameter and only do this for the media stream, it seems to be called something other than Media in the SDK.

The only side effect I've seen is that possibly Xiialive doesn't mute during Skype calls, but that's easy to work around by pausing or stopping Xiialive. Or maybe someone wants to search for the specific function call that mutes during radio.
[Android Head-Units] BassRareba:
https://goo.gl/photos/ChKkgqFpVWHiraDi6

Maybe that's the case...you refered to this?
[Android Head-Units] gustden:
If you don't mind, I will pass this information to joying. I have been emailing with them about this issue for several days now. Hopefully with this they can figure it out.
[Android Head-Units] edit:
Yes, looks like you have the old MCU.

Try the new one, maybe it can solve your problem, I don't really think so but at this point I don't think you can loose a lot by updating the MCU.

I've updated my MCU manually as well and it says :

2017-03-08 19:16:46 JY_(NOR)_90_C9_7706_5009_CAN(All)_Newlap_AMP

---------- Post added at 09:40 PM ---------- Previous post was at 09:25 PM ----------

I will rant a little, sorry in advance for that, because I am struggling with this and it's a big problem for me.

I am trying to explain to them, through many emails by now, that in the 12 May firmware the brightness does not go as low as it did in 8 May firmware and it remains very bright.

How hard is to take 2 units from the shelf, flash 2 firmwares (8 and 12 May), one on each, set the brightness to 0 on both and compare them side by side and admit that there is indeed a problem? Oh man !

Do you think that you guys can help me please to tweak it somehow? To set the range so it will go as low as it was possible in the older firmwares until now?

Thank you
[Android Head-Units] xdamember2:
I don't mind, Joying should have as much information as possible.
[Android Head-Units] gustden:
Did they remove the "backlight current adjustment" in the May 12th release? ( password 5768 ) I am on the May 8th release and I can set the screen brightness to total darkness through this setting. I did notice that the settings are written to a file at:

/sdcard/customercfg/customercfg.txt

set-blduty-min=33

set-blduty-max=100

If you cannot set it through the panel, you might want to try directly in the file.
[Android Head-Units] shanetrainST:
Would it all be possible if Joying could get it own sub forum? Just like MTCD and B.

Sometimes it's hard to follow this thread
[Android Head-Units] edit:
I wrote about how they changed it for the worse here :

https://xdaforums.com/showpost.php?p=72310449&postcount=365

The new implementation ignores customercfg.txt completely. I edited customercfg and set set-blduty-min=5 and set-blduty-max=100 if flashed ok, it confirms at the end of the flashing process that it applied the brightness settings but I don't see the results.

My problem is that in my car the headunit is angled up, almost up to my eye level and that I don't tolerate well high brightness while driving.

Yes I could use an software to adjust the brightness but why fiddle with apps manually each time I turn on the headlights when I've seen that it is possible auto from the os.

I've emailed Joying daily since 12th of may but I haven't managed to convince them that there is an issue with the new brightness range implementation.

I admit that I am getting a bit desperate here because this issue is really bad for me and I don't see them making things right because they don't seem to understand what is the problem. My only hope is that someone here can find a way to adjust the range and lower the brightness down to what it used to be in 8 May firmware....
[Android Head-Units] mancavetoyz:
I have been wanting to use Viper4android but I can't get a clear explanation on rooting the device and getting the correct viper installed. I have done several searches they all say basically do this then this and walla. The only problem is they don't actually give a step by step instruction. Can anyone assist me? I have the Jeep Specific unit from Joying. with the Intel processor and the android 6.0
[Android Head-Units] edit:
I'll try to do a step by step tutorial on how to root and install viper... but it will take some writing... so I will try to post it these days... stay tuned
[Android Head-Units] mancavetoyz:
Thank you.
[Android Head-Units] surfer63:
My script at my github repo worked fine on 5.1.1.

For 6.0.1 it needs modifications. I hope to update tonight or this weekend to 6.0.1 myself. I will immediately root my unit and adapt the script accordingly.
[Android Head-Units] gustden:
So the setting for the 'backlight current' page is completely missing from the May 12th car settings? How can that be hard to understand :confused:

I did a diff of the SYU-2-C9-CMSettings-V1.0.apk (car settings) and it looks like the code in this area hasn't really changed between the 8th and the 12th.

Even if you replace the settings.apk, you should still be able to set the brightness by pulling down the notification bar 2x. When I turn my lights on/off the slider allows me to set different levels of brightness for day/night.
[Android Head-Units] edit:
What they do not understand is that the brightness range has changed from 8May firmware to 12 May firmware and even if you set the brightness down to the lowest possible (from the settings menu or from the notification bar)

At one point I began to think that I am seeing things and maybe I am the crazy one so I downloaded an Lux Meter app from playstore for my phone, flashed the 8May FW and measured the brightness at the lowest setting ( I turned it down from the Car Settings to 5% and turned the notification bar slider all the way down) and on white background the screen had around 40 Lux. Flashed the 12 May back, turned down the brightness to the lowest setting and the display read around 110 Lux.... so there is a big difference, you notice it pretty clearly.....

Is all about the range.For instance in 8 May firmware, in Car Settings you set the lowest point to be at 40%. So EVEN IF you turn the notification bar brightness slider all the way down it will NOT go to the lowest possible because you defined the lowest point being at 40%. What I was trying to explain to Joying is to set the lowest brightness point to 5% by default because with the new 12 May firmware you can't define manually the high or low brightness points from the Car Settings app. So they made one bad move, they removed the possibility to customize the brightness levels and they defined the lowest point to 30-40% brightness.

Can you help me please?

I hope I made myself understood... did the best I could to explain.
[Android Head-Units] gustden:
On my unit (May 8 release), I set the 'Backlight Current Minimum' to 33 . With this setting the screen goes completely black when I adjust the brightness slider all the way down. Defaulting it to 5 would cause issues on my unit, as anything below half brightness would shut the screen off completely.

With the May 12 firmware, what is preventing you from setting it lower? Is the panel missing or just doesn't work? Did they change the lower limit on the setting? That is what I am not understanding.
[Android Head-Units] surfer63:
:) I did the same and came to the same conclusion. Somehow this is done somewhere else.
[Android Head-Units] mancavetoyz:
thank you. i will try it tonight.
[Android Head-Units] BassRareba:
I managed to upadate the mcu by inserting a usb key and guessing when i should've removed it.

No luck. Everything was fine for 15 minutes and BOOM dark again!

I've some videos of the problem if you want to see it.

https://goo.gl/photos/NxK2CekQ8ABp3JRv9
[Android Head-Units] gustden:
I made a few changes to the car setting apk. There was code in it to hide specific items for certain models. I removed the hiding code completely, so you may see options that do not apply to our units.

Hopefully this makes the backlight adjustment visible on your unit.
[Android Head-Units] edit:
Oh man ! Thank you so MUCH ! Oh I hope it works ! I will go home, flash the 12May once again, test it out, and return with feeback!
[Android Head-Units] edit:
I am sorry to say but it does not work.

renamed the original file (added .old to the end) and pasted yours, gave it the same permissions (644), restarted the unit... In the launcher there now is an icon with an green android instead of the original icon. When I click it it says that the app is not installed. When I click on the app itself it says "parse error" :(
[Android Head-Units] dayanandgp:
Is this still the valid zip file viper4android or has there been an update? Thanks...
[Android Head-Units] edit:
Yes, it's still valid the old one... no new one yet.

But also have a look at my tutorial to use an older version of viper for a better EQ in my opinion.

https://xdaforums.com/showpost.php?p=72342543&postcount=415
[Android Head-Units] gustden:
I'm wondering if the file got corrupted somehow. I have had several files get corrupted using adb/wifi, then recopy the file it works fine. Did you use wifi to transfer the file or usb stick?

I installed on my unit and it worked fine before I uploaded it. Below is the md5sum for the original file. You can see if it is the same by running the following command on the unit.

busybox md5sum SYU-2-C9-CMSettings-V1.0.apk

cdd4dcac37398e233cd8e775c51e8f67 SYU-2-C9-CMSettings-V1.0.apk
[Android Head-Units] dominicanodcora:
i get errors:

C:\rootjoy\SuperSU_for_Joying_Intel>copy_install.bat 192.168.0.149

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to 192.168.0.149:5555

error: device offline

already connected to 192.168.0.149:5555

mount: Operation not permitted

47 KB/s (13788 bytes in 0.280s)

110 KB/s (14302 bytes in 0.126s)

39 KB/s (629 bytes in 0.015s)

113 KB/s (346536 bytes in 2.970s)

21 KB/s (99916 bytes in 4.510s)

77 KB/s (6539610 bytes in 82.857s)

16 KB/s (46416 bytes in 2.822s)

su: invalid uid/gid '-c'

su: invalid uid/gid '-c'

chmod: /data/supersu/install.sh: No such file or directory

/system/bin/sh: cd: /data/supersu: No such file or directory

Reboot your Head Unit NOW!

C:\rootjoy\SuperSU_for_Joying_Intel>
[Android Head-Units] edit:
try an unit restart, the moment it booted press the enter key to run the copy_install.bat 192.168.0.149 that you have prepared in the cmd box (with admin rights)

I get the kind of errors you showed if I let the HU idle a bit and it gets offline for some reason

And please don't paste that huge post of mine without editing it...
[Android Head-Units] dominicanodcora:
mount operation not permitted is that normal?

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

same error even after pressing enter once the unit booted up

C:\rootjoy\SuperSU_for_Joying_Intel>copy_install.bat 192.168.0.149

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to 192.168.0.149:5555

error: device offline

already connected to 192.168.0.149:5555

mount: Operation not permitted

34 KB/s (13788 bytes in 0.385s)

64 KB/s (14302 bytes in 0.215s)

19 KB/s (629 bytes in 0.032s)

55 KB/s (346536 bytes in 6.070s)

109 KB/s (99916 bytes in 0.888s)

68 KB/s (6539610 bytes in 92.578s)

196 KB/s (46416 bytes in 0.230s)

su: invalid uid/gid '-c'

su: invalid uid/gid '-c'

chmod: /data/supersu/install.sh: No such file or directory

/system/bin/sh: cd: /data/supersu: No such file or directory

Reboot your Head Unit NOW!

C:\rootjoy\SuperSU_for_Joying_Intel>
[Android Head-Units] edit:
I've copied via a stick, all went well, double checked everything, in fact I downloaded and copied again.

The checksum of the file is correct. Took a screenshot also... I can't detect anything wrong...

L.E: You took the SYU-2-C9-CMSettings-V1.0.apk (and modified it) form the 12 May firmware, right?
[Android Head-Units] gtxaspec:
Change the group to root.
[Android Head-Units] edit:
I just did... still no luck :(

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

I ran out of ideas... is like your unit does not have root at all... that basic, old and buggy supersu that the unit supposed to have does not allow for some reason mounting the system partition for writing....
[Android Head-Units] surfer63:
In the copy_install.bat file you can find the line

..\win-adb\adb shell mount -o rw,remount /system

Please change this to

..\win-adb\adb shell busybox mount -o rw,remount /system

If this is the issue then the toolbox binary is even more buggy then the one on the 5.1.1 unit (and note that the busybox binary on the Joying head units is a bad one also)

If this change doesn't work, I advise you to leave this specific line with busybox in place, but to first install the busybox binary.

You can find that one also in the zip in the parallel busybox-X86 folder.

If you have installed that one, then please try the SuperSU rooting again.

(Tomorrow afternoon I will upgrade to 6.0.1 to test myself)
[Android Head-Units] dominicanodcora:
I have root now. i used the install.bat from the first post 2nd link.
[Android Head-Units] gustden:
If a file has the wrong permissions when is attempted to be installed, just changing the permission will not fix it in some cases. You need to actually modify the file. I just tried this on my unit:

[MENTION=309187]edit[/MENTION]

FILE SET WRONG ( permission set to root/everybody ):

01-21 02:50:25.936 574 574 W PackageManager: Failed to parse /system/app/SYU-2-C9-CMSettings-V1.0: Failed to collect certificates from /system/app/SYU-2-C9-CMSettings-V1.0/SYU-2-C9-CMSettings-V1.0.apk

FILE PERMISSION CORRECTED ( permission set to root/root ):

01-21 02:56:23.941 538 538 W PackageManager: Failed to parse /system/app/SYU-2-C9-CMSettings-V1.0: Failed to collect certificates from /system/app/SYU-2-C9-CMSettings-V1.0/SYU-2-C9-CMSettings-V1.0.apk

FILE MODIFIED ( old file put back, reboot, new one re-installed ):

05-19 02:59:52.511 551 551 I PackageManager: /system/app/SYU-2-C9-CMSettings-V1.0 changed; collecting certs

From what I could tell. If there are issues installing the apk (such as having incorrect group), it will not try to reinstall it again until the file is modified.

You might want to put the old one back, reboot, then reinstall with 'root' for both owner and group.
[Android Head-Units] edit:
Thank you for taking the tine to test this but unfortunately it did not work no matter what I have tried :

1. I put the original file back and restarted the unit

2. renamed the original file to .old and put the new one in this time gave it the permissions and set owner root, group root

3. restarted.. NO luck, the same issue with parsing.

4. reseted the unit to defaults and tried again (step 2 to 3)... NO luck

5. reflashed the unit to May 12, again and tried step 2 to 3... NO luck again

The ONLY way I managed to run your modified CMSettings is to put the original file back, restart, put the new file in, gave it the same permisions and owner and run it (without restarting).

It ran fine, I've seen the missing brightness calibration menu, entered it, If I set the brightness down to 5 it tarkens the screen nicely, I press save, BUT the second I exit the menu the brightness reverts back to the brighter setting and that leads me to the conclusion that there is another setting elsewhere that overrides the Car settings. Maybe is not conclusive but this is the best I could do.

Later edit : I unpacked the Allapp.pkg, inserted the moded SYU-2-C9-CMSettings-V1.0 (deleted the original file), repacked everything back, reflashed the unit again.... but the Car Settings does not show up... so I ran out of ideas and options

---------- Post added at 02:35 AM ---------- Previous post was at 02:32 AM ----------

It's strange, for me it worked every time, and I've used it on the last 4 firmwares that I flashed at least 20 times....