yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] concept5400:
[MENTION=2550900]surfer63[/MENTION]

Thanks for all your help, I really appreciate it.

I am currently in the car with my laptop (Mac OS), trying to make it work but unfortunately I am unable to.

My head unit is JY-VL130N2.

The no kill part of the mod is working perfect, but remapping the buttons is not.

I have used install.sh to install the mod so all files are in the right place.

At first I have pushed unmodified launcher.sh to check how it will work.

My left side buttons (HOME, BACK, MUTE) were working, but I could feel the delay before key pressing and reaction (around 1 second).

My right side buttons (BAND, NAVI, MEDIA) were not working all all (I could hear the beep sound, but there was no reaction).

Then I have modified launcher.sh - I have deleted extra semicolon after 98) $pause - still the same.

Then I have added "$spotify" to every unbinded key - 28) 31) 32) 33) 34) - still the same, no reaction from my right side keys.

Then I have added "$waze" to 97) #ACC_ON - not working, waze is not starting on key on.

To be honest I can live without remapping the keys but I have to manually exit Waze before turning the car off so it won’t crash on next power on.

1. Is there a way to modify Sofia server apk so it will kill waze on power off but leave other apps untouched?

2. I have decompiled Sofia server app using apktool and added navi aps I am using to navi_app.txt, compiled and signed the app again (I followed this guide: xdaforums.com/showthread.php?t=2213985). Unfortunately after this modification and pushing this modified server app there was a disaster - notification bar were no longer functional, radio app was crashed and hu was pretty much unresponsive. I had to return to unmodified by me server apk from the mod. What have I done wrong?

3. My Radio APP AF (alternative frequency) function is working very bad. My favorite station is at 96.0MHz in my city (but in other cities close by it is at 93.0MHz or 94.9MHz). Whenever I turn on AF in my city, after a few minutes the Radio App change the station to 102.0MHz, which is totally different station (what’s worst it’s religious station wth praying instead of music ;() Not to mention RDS message of 102.0MHz is totally different. I have turned off all other setting (LOC OFF, PTY OFF, TA OFF) but still no help - every time I turn on AF function same thing happens.
[Android Head-Units] surfer63:
Navi is key 9

Media is key 33

Band is key 34

like

9) # NAVI - Start default navi app
$navi
;;
31) # DVD
;;
32) # EJECT
;;
33) # MEDIA - I start Rocket Player Free
$rpf
;;
34) # BAND - I use band for google voice
$gvc
;;

With regard to your questions:

1. I suppose so but I have no idea

2. do not sign. That is not working because you changed the apk, so the checksum doesn't work.

simply use "apktool -c b <folder of unpacked apk>" and push that one to your unit (from the <folder of unpacked apk>/dist folder).

3. Check whether you have selected the correct region in your radio settings.

Edit: What you can try as well from the android command line or via adb is to start the launcher script with the specific key like "/data/launcher.sh 9"
[Android Head-Units] concept5400:
1. Is there a way to modify Sofia server apk so it will kill waze on power off but leave other apps untouched?

I have managed it by returning un-modded Sofia-1-C9-Server-V1.0.apk and then modifing it - I have added navi apps I am using to navi_app.txt and apps I want to save from killing (spotify, radio, speed camera app) to unkill_app.txt and unkill_app_8700.txt

This way Waze is killed on "key off" and is bringed back on "key on" by the HU (Auto Start Navi option in Car Media Settings).

2. I have decompiled Sofia server app using apktool and added navi aps I am using to navi_app.txt, compiled and signed the app again (I followed this guide: xdaforums.com/showthread.php?t=2213985). Unfortunately after this modification and pushing this modified server app there was a disaster - notification bar were no longer functional, radio app was crashed and hu was pretty much unresponsive. I had to return to unmodified by me server apk from the mod. What have I done wrong?

I have skipped the signing and it worked, thanks.

3. My Radio APP AF (alternative frequency) function is working very bad. My favorite station is at 96.0MHz in my city (but in other cities close by it is at 93.0MHz or 94.9MHz). Whenever I turn on AF in my city, after a few minutes the Radio App change the station to 102.0MHz, which is totally different station (what’s worst it’s religious station wth praying instead of music ;() Not to mention RDS message of 102.0MHz is totally different. I have turned off all other setting (LOC OFF, PTY OFF, TA OFF) but still no help - every time I turn on AF function same thing happens.

Still no solution, my region is correctly set to Europe.
[Android Head-Units] Bingoboy1975:
Hello, does anybode know if it is possible to add steering wheel control (up & down buttons) to the DAB app?

https://xdaforums.com/showpost.php?p=71746968&postcount=125

I thought of, that the values of the up-&down buttons might be saved in a global variable and then it should be possible to implement these values in the dab app or am I wrong?

(I have an Erisin MTCD PX5 unit.)
[Android Head-Units] surfer63:
You are in the wrong thread. This is about Sofia 3GR units. Steering wheel control is not arranged per app but via some Android Server application on the unit. Try to search on "Malaysk custom rom" for example. Although I think they are not avaialbe yet for px5 units.
[Android Head-Units] ferni:
I updated my new JY-VL130N2 (Joying intel 2gb) unit to the 28/3 update today.

I then updated Busy Box and installed SU using https://github.com/hvdwolf/Joying-RootAssistant

Then i tried install.bat from the OP, it looks liked it worked but then i checked the files and noticed that Sofia-1-C9-Server-V1.0.apk looks like the original version?

I installed SSHDroid to get ssh access to make it easier to poke around, checking the sdcard version and the version in /system/app shows they are different and the one in /system is still the original one?

u0_a78@sofia3gr_car:/sdcard $ ls -la Sofia-1-C9-Server-V1.0.apk

-rw-rw---- 1 root 1028 1346752 Apr 21 11:10 Sofia-1-C9-Server-V1.0.apk

u0_a78@sofia3gr_car:/sdcard $ ls -la /system/app/Sofia-1-C9-Server-V1.0/

drwxr-xr-x 2 root root 4096 Mar 22 08:07 .

drwxr-xr-x 70 root root 4096 Apr 21 10:45 ..

-rw-r--r-- 1 root root 1265182 Mar 22 08:07 Sofia-1-C9-Server-V1.0.apk

I think maybe the remount of system as rw isn't working?

u0_a78@sofia3gr_car:/sdcard $ mount |grep system

/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 /system ext4 ro,relatime,data=ordered 0 0
[Android Head-Units] rnabi99:
Should this navi_app.txt file be in the zip? If so, I don't see it. I would like the ability to add apps to that file.

On a related note, I noticed you use ReadItToMe. When I tried using this app, the notifications get cut off after a second or so. Do I need to add this app to the navi_app.txt to get this to work?

One final thing, I really like your Torque layout. Is that exportable? If not, can you give me a quick rundown of what you have showing?

Thanks
[Android Head-Units] budwha:
I just installed readittome yesterday and noticed that it reads approximately 45 characters of the notification. .......maybe you are noticing the same thing. If the message is short it reads the whole thing. After 45 characters or so it cuts off the remaining words. ........I assume this is a limit in the way notifications are sent. I had the same problem using Tasker and Autonotification to read incoming messages. .....so it's not the readittome app.
[Android Head-Units] ferni:
Ok this is doing my head in. I can't get /system to mount as rw no matter what I do. I'm now trying the 14th March update instead (downgrading). But doubt it will make a difference.

I'm not sure I have got it to root properly, when i put ES File explorer on it won't let me write to /system

I'm reasonably good with windows, linux and iOS but new to Android and it's doing my head in.

---------- Post added at 10:23 AM ---------- Previous post was at 10:01 AM ----------

Ok I don't know why, but downgrading to the 14th March update(20170314.zip) has fixed it, /system is now mounting as rw no problems. Has anyone else tested the latest 23 March update to see if they can root it or mount /system as rw?
[Android Head-Units] edit:
Just a heads-up!

I am using the Mar 28 firmware, and I've just installed the V4.1 No Kill (with the launcher_simple.sh) from this thread and I am using the Time Control option from the Car settings app for the hardware keys backlight control.

If I did not stopped Waze before I turned off the car, when I turn it back on sometimes Waze crashes.

The BIG problem is that when it crashes, the unit is left in a strange state... it CAN'T go to sleep anymore, the hardware buttons remain lit up and the CPU does not cool down anymore.

Did some tests, turned off the unit and let it sit for 10 minutes, the backlight of the keys remained on the whole time and when I turned it on the CPU had the same temp as the moment I turn it off, it looked like it worked the whole time. Unfortunately I don't have any tools to measure the power drawn when it gets stuck like this but I will definitely test it because if does not get to sleep at all and it gets stuck it could be a big problem for some that leave their cars in the parking lot of long periods of time.

Restart does not solve the problem, using shutdown from the menu also does not solve the problem... the only way to make the unit sleep again is to cut the power off completely (disconnect it completely).

Also I need to mention that with the default Sofia-1-C9-Server-V1.0.apk I haven't encountered problems so It might be a bug in the app or a combination of factors.
[Android Head-Units] ferni:
Is it possible to symlink an app in android?

I just want to start BT Audio or Poweramp instead of the default music app, since my media key is coded (i'm guessing in Sofia server?) to start the default music app "am start com.syu.music/com.syu.media.act.Act_Music" if i could just remove that and instead symlink to the BT Audio or Power amp app that would be a pretty quick hack....

In linux it would be dead easy.. is it possible in Android?
[Android Head-Units] Polluti0n:
I believe this was discussed on page 33. I am not sure if the suggested fix work but assume it does.

-Polluti0n
[Android Head-Units] edit:
Thank you, I read that but no one actually said that after the Waze freezes the unit gets stuck and does not go to sleep anymore draining car battery big time.

While the unit is stuck the power drain is between 0.45-0.60A and the unit keys remain lit (that's the giveaway) all that with the keys off the ignition (sort to speak).

The only way I was able to resurrect it, except pulling out the cables is to restore the original Sofia-1-C9-Server-V1.0.apk, restart and then the HU entered sleep once again.

So Waze and V4.1-Custom-Keys-Mods DON'T go together well at all !

Probably the only workaround is to kill Waze every single time you send the unit to sleep
[Android Head-Units] gtxaspec:
They absolutely do, I use both and have no issues, and I use waze everyday!

Are you sure you didn't leave a second copy of the server apk?
[Android Head-Units] edit:
I think the script that pushed the moded one left the original there but added the ".old" to the original ".apk" extension... Is that an issue?

Keeping the original in the same folder even if it has the .old extension that android can't see as usable?
[Android Head-Units] surfer63:
This is fine.

You can't have two files with the extension .apk insiede one folder in /system/app or /system/priv-app

You can have many files in there as long as only one has the apk extension,

so Sofiaserver.apk, sofiaserver.apk.old, sofiaserver.apk.even_older and sofiaserver.apk.oldest is no problem.
[Android Head-Units] edit:
Thank you for the feedback.

If everything is fine what on earth could cause the unit to stuck in high battery drain wake mode?

The problems occurs only with the V4.1-Custom-Keys-Mods and right after waze crashes.

I am probably asking too much but can you please release a mod of the app that would close Waze each time it goes to sleep.

To be completely honest I have no idea how to do that. I read what have people wrote here but I don't know how to modify the scripts, unpack, repack...
[Android Head-Units] kampfschachtel:
Hi all,

maybe a stupid question but what happens if I install V3 mod with all the key mods as in the example script and my unit doesn't have a specific button eg DVD or Eject that is reprogrammed/added in the script?

I have the 10.1 universal sofia and it has no hard keys, only the touch buttons on the side of the screen. They have the same function as the hard keys on the 7 inch units but does the mod work on these the same way then the hard keys.

I actually like the example script as it is.
[Android Head-Units] concept5400:
[MENTION=309187]edit[/MENTION]

I hadn't found a way to kill Waze-only and keep NOKILL mod so I have figured out other solution - I have added apps I would like to save from killing to assets/property/unkill-app and unkill_app_8700 (Spotify app, Radio app, local speed camera app), I have added com.spotify.music to player assets/property/player_app then I have added apps I would like to be able to speak through Radio app to assets/property/navi_app

Last but not least, I have selected Waze as my navi app in Car Settings and then I have enabled auto start of navi app in Car Settings.

This way I have achieved exactly what I need - HU doesn't kill apps I am using, spotify starts playing immediately after turning on the ignition and at the same time each time HU goes to sleep Waze app is killed and restarted after each wake up, so Waze ain't crashing no more.
[Android Head-Units] edit:
How did you manage to edit those files "unkill-app", "unkill_app_8700" "navi_app" ? You used apktool to unpack then edit them in notepad and packed them back.... (I don't have a clue how to pack and unpack but I guess I have to learn)

That is a good idea, well done !

The only problem here is that the units does not stop playing for a while after you stop the car... for about 1 minute, this is how long it take to go to sleep after you turn off the engine (red wire off)
[Android Head-Units] ferni:
Since no buttons work at all I think best to check the basics... I had the same problem when I first tried, no buttons worked, but i'd forgotten to chmod the apk/sh file.

Are you sure you have the right apk (check the byte size on disk vs one you downloaded)

Are you sure you chmod the apk to 644?

Are you sure you chmod the launcher.sh to 755 and it is in /data ?
[Android Head-Units] edit:
Yes absolutly because other things work:

1. apps don't get killed like they used to with the default Sofia server

2. only waze gets killed everytime I turn off the car due to "am force-stop com.waze" inserted in launcher.sh

Yes I did. Double checked and triple checked.

I am absolutely sure, triple checked this one as well.

Somehow the launcher.sh is read given that Waze gets killed but I cannot map the left side buttons.

Maybe they have different codes than the ones posted in launcher.sh ?

I've tried everything I could think of but this launcher.sh problem is above me... can't solve it unless I get help.

Sorry for bothering guys !
[Android Head-Units] ferni:
Something else I read in here is that if you edited the launcher.sh in windows notepad it may have changed the new line char, which means it won't work on the android headunit... could this be your problem?

If so try using Notepad++ to edit the original .sh file and reupload or the dos2unix util to convert it
[Android Head-Units] edit:
I only used Notepad++ to edit the launcher.sh. I've noticed that the Notepad messes up the formatting so I did not use it.

As you can see I did my home work as best as I could but...

Thank you for your ideas!
[Android Head-Units] ant0ni084:
need help about original apk about keys and buttons

Hello everybody, can someone send me the original apk about keys and buttons for Joying Volkswagen 8 inches Intel Sofia 2GB autoradio please? I forgot to do backup :( . Thank you.
[Android Head-Units] surfer63:
For which ROM?
[Android Head-Units] ant0ni084:
For Android 6.0 rom, I did update some days ago.

Inviato dal mio MI 5 utilizzando Tapatalk
[Android Head-Units] surfer63:
Download link
[Android Head-Units] ant0ni084:
That's very kind of you, thanks a lot!
[Android Head-Units] ferni:
Try using the default launcher.sh file and only change one button/command?

Also try adb logcat -s MCUKEY while pressing a button and make sure you can see it calling your launcher.sh with the expected number ?
[Android Head-Units] windowsdan4216:
Don't suppose there is an updated Sofia-1-C9-Server-V1.0.apk for the new 6.0 update yet?

Wanted to update but can not live without the NOKILL on apps :D
[Android Head-Units] surfer63:
Follow the 6.0 upgrade thread. Already 3 mods published.
[Android Head-Units] windowsdan4216:
Ah I was looking for a thread on that! Don't suppose you could link? Can't seem to see it... ?
[Android Head-Units] surfer63:
Almost last post(#789) in the Roll-UP thread today.
[Android Head-Units] windowsdan4216:
I have the file now thanks .... however .... I have a big problem where adb willnot connect to the HU after the update!!!! :eek::eek::eek:

I'm at a loss ... connected on my home network or the phones hotspot ... doesn't matter ... script errors with:

Joying-RootAssistant-master\SuperSU_for_Joying_Intel>copy_install.bat 10.0.1.26
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 10.0.1.26:5555
error: device '(null)' not found
unable to connect to 10.0.1.26:5555
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
Reboot your Head Unit NOW!
[Android Head-Units] surfer63:
That has nothing to do with the script.

Joying Android 6.0 doesn't have adb over tcpip enabled, so that won't work out of the box.

On 6.0 you first need to download an android terminal application (jackpal is the best), open it and type on the command line "setprop persist.adb.tcp.port 5555" and reboot your unit.

Then you can use the script over your network.
[Android Head-Units] windowsdan4216:
Ahhhh. Amazing! thanks for saving me hours of head scratching and angst :D

---------- Post added at 08:06 PM ---------- Previous post was at 07:55 PM ----------

Hmm seem to have an interesting error from the script....

g_Intel>copy_install.bat 10.0.1.26
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 10.0.1.26:5555
restarting adbd as root
connected to 10.0.1.26:5555
172 KB/s (13788 bytes in 0.078s)
148 KB/s (14302 bytes in 0.093s)
7 KB/s (629 bytes in 0.078s)
191 KB/s (346536 bytes in 1.766s)
99 KB/s (99916 bytes in 0.977s)
152 KB/s (6539610 bytes in 41.995s)
55 KB/s (46416 bytes in 0.816s)
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!
[Android Head-Units] surfer63:
Weird. I have no idea what causes this. It must be a difference between 5.11 and 6.0.1. I'm not on 6.01 yet. The su binaries are different but for the rest it should (!) work the same.

Besides: This is the wrong thread. This is about the steering wheel mod, not about rooting your unit.
[Android Head-Units] surfer63:
The shell script contains:

adb kill-server
adb connect $1
adb root
adb connect $1

Please change that to:

adb kill-server
adb connect $1
# adb root
# adb connect $1

(or remove these 2 lines)

And please try again.

If that's the issue, then that's also the change between 5.11 and 6.0.1
[Android Head-Units] windowsdan4216:
I know it's the wrong forum so I'll leave it at this:

Thanks for all the help ... due to knowing terminal command anyway, I just did it manually to see where the problem might lay.

It's in the folder creation and copy commands ... already root so do not need 'su' + 'su -c' was causing problems ... was able to make it successful with:

..\win-adb\adb shell "mkdir /data/supersu"
..\win-adb\adb shell "cp /sdcard/supersu/* /data/supersu/"
..\win-adb\adb shell chmod 0755 /data/supersu/install.sh
..\win-adb\adb shell "cd /data/supersu/ && sh install.sh"
..\win-adb\adb shell rm -rf /sdcard/supersu
..\win-adb\adb shell rm -rf /data/supersu
..\win-adb\adb shell syn
[Android Head-Units] edit:
I just did that yesterday and the left side buttons match their codes... I am clueless.

But in your opinion does my script look ok? I mean is it constructed properly and the syntax is correct?

One odd side effect was that while I was using Deezer (streaming player similar to Spotify) the left side buttons acted like "play" so if I would pause the music I could resume pushing "BAND" or "DVD" or "RADIO".... very odd
[Android Head-Units] gustden:
Updated for Android 6. See first post.
[Android Head-Units] Astur_Torque:
Is version 6 suitable for 5.1 too?
[Android Head-Units] gustden:
Version 6 is built off of the 6.0 update. It looks like there are quite a few changes to the original file between the 2 versions.

If you are on 5.1 I would use the older version.
[Android Head-Units] surfer63:
BIG thanks again.
[Android Head-Units] Astur_Torque:
Hello!

i have an Opel version of Joying 2GB, but I am not able to program steering wheel botons, when I go into de app, they're all with 255 value, and if I press a steereing whell boton, the botton do its default function, and if I press the touch flash in pink but nothing happens... I don't know whats happening

Can anyone help me?

thanks

---------- Post added at 08:40 PM ---------- Previous post was at 08:03 PM ----------

I'm not very good on bash script, but I'll try this... where is located?
[Android Head-Units] gustden:
Yes root is required. You need to replace a system file to use this. You also need to update 'busybox' ( in the play store ) which will also require root access. BusyBox - Stephen (Stericson) Tools
[Android Head-Units] gustden:
Not currently, the modified apk file is only looking for key presses and the restore message. If I get time I can look into it, but not making any promises.
[Android Head-Units] sonof:
Thank you! You have made it all too easy for us :) Perfect job and made the head unit a couple times more safe to use while driving.
[Android Head-Units] gustden:
I was looking into this over the weekend, I did find the code where the unit gets put to sleep ( about 10 minutes after the ignition gets turned off ). Just wondering what kind of activities you want to run at 'ignition off'? For the illumination you might be able to set up tasker to trigger on the change in the display setting.

In the sleep code, I also happened to find the code that kills off all the apps when it goes to sleep. killAppWhenSleep(); I commented it out, built, and loaded it on my headunit. Kind of neat having everything exactly how it was when it was shut off, even pandora playing the same song at the exact same spot. Just wondering if there are any negatives. Thinking they must have done it for a reason...
[Android Head-Units] nico84:
I use PowerAmp. When the unit comes back from standby, PowerAmp starts the last track from the beginning. When I send the pause command to PowerAmp before the Unit goes into standby, PowerAmp will resume at the last state. Can you upload a version without the code that kills all apps? I can test it. I think it will resolve my problem too.

Edit:

I have not the Joying headunit. I have the Erisin with Intel Sofia. I can not found the original apk "Sofia-1-C9-Server-V1.0.apk" in /system/app/... Maybe it is different here....