yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] gustden:
Did you reload the ROM also? If something got screwed up on the system partition and/or MCU, a factory reset wouldn't fix it, where reloading the ROM might.
[FYT Android Head Units] breevesdc:
I did not reload the ROM. I will try that after work today and post the results. Thank you.

Brian
[FYT Android Head Units] chammock:
quick question, how did you enable adb on the usb ports. On my old unit this was done with "adbon" as the password but as these new units only allow numerical input that obviously isn't going to work. I have looked through the developer options and can't find an adb specific option. I have enabled USB debugging in developer options is there another option I need to enable or code I have to enter?
[FYT Android Head Units] Flavio:
Does changing the Canbus protocol wipe any App settings?
[FYT Android Head Units] gustden:
I did run across a 'hidden' setting activity that allows you to switch from usb-host to usb-device mode. I was able to create a shortcut to in from the 'activity widget' in nova launcher. Activity->Settings->usb settings.

Problem is, I have no idea what kind of cable is needed ( or if it even works). I know a straight USB-A / USB-A cable doesn't recognize anything.
[FYT Android Head Units] chammock:
Thanks for the reply gustden. Yes I am using a straight USB-A / USB-A cable so maybe that is the problem. There must be a simpler way to enable it than installing nova launcher.

Guys how are you all getting adb access, through a USB port? If so what cable are you using and how are you switching it on?
[FYT Android Head Units] gtxaspec:
ADB via WiFi. Unable to find a way to use adb via USB, even after changing USB mode. Need to investigate further how the usb is enumerated in the kernel and system
[FYT Android Head Units] derschnelle:
I have a short question about the sleep mode. When I enter my car, even after 2 days and start ignition the head unit starts and is up without booting. It just seems, as if the device doesn't shut down.

How is the behavior on your devices?

Thanks in advance!
[FYT Android Head Units] breevesdc:
Hello. I reloaded the newest ROM last night after getting home from work. The good news is that it seems to have resolved my issue of many apps not working, no sound and continual reboots every 5-10 minutes. I drove 30 minutes to work today with the unit performing normally and with no reboots. The only thing that is not working is the steering wheel keys are now non-functional (even if I try to program them in the Car Settings menu). Everything else seems to be working just fine.

I am concerned however about how this happened. I didn't do anything to the head unit that I would consider highly unusual or risky. I'm wondering if anyone has any thoughts or speculation as to what might have caused the problem. Here are the only things I did that I would classify as potential culprits:

I rooted the unit via the procedure documented on pg. 1 of this thread (2nd option).

I applied the patch to comment out the line responsible for killing many apps when the unit goes to sleep after ignition shutoff (also from pg. 1 of this thread).

I applied the update (via adb over http) to view all apps in Immersive Mode

I'm not experienced enough in Tasker to know if this could be a problem. But the only other thing I did that could be problematic is that I had a profile which launches a scene. This profile was based on "device boot" on my old unit. But since this unit does not actually shut down and start up, I added a new profile to launch the same scene on "screen on". But I didn't disable the other profile for device boot. So, it occurred to me that perhaps this was a problem because (perhaps) both conditions are true on reboot (device boot & screen on). And they would attempt to launch the same scene. I can't imagine that this could corrupt the system. But I mention it because I'm grasping for straws to explain how this happened. I'm concerned that I really do have a hardware problem and it will come back in a few weeks or months.

Any input would be welcome. And many thanks to gustden for the persistent replies. Much appreciated!

Brian
[FYT Android Head Units] Hilari0:
Is it possible to bring up the aux in camera view while still playing music? I have connected my rear view backup camera to both reverse cam input and the aux in which makes it possible to bring up the view even if I'm not in reverse, but of course it will mute everything else which is a little annoying..
[FYT Android Head Units] n7slc:
White Dot?

I've been looking all over and can't find where to disable that annoying white dot. OP, can you add this to the main post?
[FYT Android Head Units] thedru13:
Look for the app called touch assist. You can disable it from there
[FYT Android Head Units] Xaadi316:
hey while tinkering with the settings i found vehicle choice in advance settings ( password protected ones) so i went straight to toyota and unfortunatly cant find my car " prius" listed in it so i selected corrola instead and it did a mcu update ...... but NOTHING has changed or i cant notice any changes so far

so any idea wats that selection is about and any one can help me select the best mcu for my prius c ?

thanks
[FYT Android Head Units] n7slc:
I did this but now my HU is stuck sitting on the Android logo. It rebooted once and the little green android showed up with Chinese writing followed by another reboot and now stuck.

Soft bricked?

UPDATE: I got it sorted. Had to reinstall the new firmware and then re-root it.
[FYT Android Head Units] dayanandgp:
It simply changes the boot image to nice picture of your OEM.. :rolleyes: Nothing functional...
[FYT Android Head Units] amon101x:
Unfortunately the modded radio skins dont work for me.. If i flash them using the install.bat, the radio app gets deleted from the device and im not able to listen radio anymore.

I even tried to give the new joying radio apk manual read/write acess over ES File explorer and Root explorer.

If i copy the old (original) joying radio apk back to its place (system/app/Folder of the joying radio app) it works again after reboot (but only the not-modded radio)

Hope someone could help me with this. There were no errors shown in CMD

edit: after pushing the modded apk with your install script (and not restarting the device afterwards) and then giving it excute rights for every group ive been able to start the modded radio app, but after i restarted the device im again not able to start the modded radio (when i try to open it "App is not installed") even though radio is working in the background
[FYT Android Head Units] lions123:
After the update to Android 6.0 I changed my radio to the red-white one. It works fine, but after I had disconnected the battery cables, the radio was lost. Now I tried it to do it again, and I can see the /system/app/JY-1-C9-Radio-V1.0 with a terminal emulator, but there is no radio icon anymore to start the radio......
[FYT Android Head Units] Dragonlove:
Anyone have a solution for this? it happens each time the Dab app starts, running Android 6, didn't happen in the Android 5.1.1

[IMG="Dab Player"]https://dl.xda-developers.com/4/1/3/5/8/0/1/dab.jpg?key=8u8Ckn_hbd_b17zSdfcDRw&ts=1493750370[/IMG]
[FYT Android Head Units] bigsteve01:
I'm having exactly the same problem since updating
[FYT Android Head Units] psxsnake:
Send bug to joying.... remember this is a beta version
[FYT Android Head Units] bigsteve01:
I am also having the same problem with a USB dvb-t tuner

I will report the problem on the joying forum

Thanks
[FYT Android Head Units] ferni:
I have the NOKILL mod installed, but as you mentioned above that viper4android still seems to get killed unless you added it to unkill_app.txt ?

Is there an easy way to decompile and recompile the apk? someone posted a chinese exe that can do something like that in this thread or one of the other ones, would that work for the unkill txt?
[FYT Android Head Units] AssassinsLament:
There isn't an easy way, as the process is pretty complicated. I won't get too technical into the process, but I will give you an outline of how to do it, and you can research it yourself.

You need Java to be installed, then download the latest apktool. Then you decompile an apk by issuing the command:

java -jar apktool_2.2.2.jar d -b <filename.apk>

That extracts/decompiles the <filename.apk> into resources and smali code

Then with notepad++, edit the file inside the newly created folder <filename>/assets/properties/unkill_app.txt

When you're done, just run:

java -jar apktool_2.2.2.jar -c b <filename>

and it should recompile the apk, and you will find the new file inside the <filename>/dist folder
[FYT Android Head Units] gustden:
There was an additional call to killAppWhenSleep added to 6.0. It is in smali/chip/ChipSofia$1.smali that looked to be the issue.

I just made a new no-kill Sofia-1-C9-Server-V1.0.apk file for 6.0 with this removed. If someone wants to try it out and see if it helps. Working fine on my unit.
[FYT Android Head Units] surfer63:
In post #735 I wrote below:

I wrote this a couple of days ago. I continued my efforts. It now makes a difference between 5.1.1 and 6.0.1. That is: if the android version matters for the option.

See this short video on Youtube (Unfortunately none of the tried screen recorders work on the Joying unit, so a bad quality phone movie).

Note: I already gave root access to my apk. Otherwise you need to give root access to the apk during the first start (or after an update of the app) after the "Accept" screen.

Edit: I updated the movie. It contained copyrighted music which I completely did not realize when recording the movie. That part has now been muted.
[FYT Android Head Units] s|ck:
Hi, does anyone know how to disable the Radio App from starting up automatically on boot up? I don't use the radio and would like to disable it permanently.

I have root access and tried the "pm disable com.syu.radio" and "pm disable com.syu.carradio" but they keep re-enabling themselves after I reboot the unit.

Thanks.
[FYT Android Head Units] zorantoma:
This is briliant :) Looking forward to try it out my self when you release this tool.
[FYT Android Head Units] juandhi:
Awesome stuff. Thanks for all that you do.
[FYT Android Head Units] wanahave:
You can disable apps in "settings" , "apps". Tapp on the app you want to disable and see....... Here you can turn off and on the app. By disabling you won't see the radio app anymore. No root needed. Is standard android.

But I've read on the Joying forum that this only works after the 6.0.1. update and not on the 5.1.1 Android version!. I haven't tried it myself yet on the Head Unit.On my Android phone it works fine.
[FYT Android Head Units] surfer63:
That's what he mentioned in his first post with the rooted command "pm disable com.syu.radio".

Besides: on 5.1.1 you don't have that settings->disable menu unless you install the orginal Google settings.

Fortunately that menu came back in 6.0.1.

I think it is hardcoded in the SofiaServer or the SystemUI server.
[FYT Android Head Units] psxsnake:
So now i need to root ;) it's amazing work...
[FYT Android Head Units] georgebest:
About the RDS...why is so small and therefore useless?? In other head units like Erisin it appears in the centre of the screen as it should be. Is there a way to make it happen to joying HU as well??
[FYT Android Head Units] Astur_Torque:
How can I configure the total shutdown at less time or force totally shutdown? I installed the radio today and I am a bit dissapointed with these things
[FYT Android Head Units] CamryGuy:
What are you on about?

I said its not working. Would you like a screenshot? Wanker
[FYT Android Head Units] surfer63:
Please behave. You might be annoyed and you can share that, but that is no reason for scolding and calling names. Note also that this forum hosts a lot of non-native speakers who do their best to communicate in English. That might sometimes lead to "confusion" due to their wording.

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

Don't cross post. I answered your post in the other thread.
[FYT Android Head Units] windowsdan4216:
Can't seem to find anywhere about the fact that the new 6.0.1 update doesn't seem to take the Settings.apk pulled from the downloaded image and put in place of the crippled one anymore

When you launch after replacing and reboot it just force closes :crying:
[FYT Android Head Units] windowsdan4216:
OH MY GOD!

One of the main reasons for this unit is content capability...you can not install Netflix on 6.0.1! ? Not compatible with device!
[FYT Android Head Units] locometopa:
Excellent work!

Waiting for release.

Thank you!
[FYT Android Head Units] ant0ni084:
Hello, I've tried to install your radio mod but I get the message about analysis error package and I can't understand where I wrong. I've downloaded your complete zip file.
[FYT Android Head Units] surfer63:
Can you please post that error? on linux or on windows?

I have no clue yet.
[FYT Android Head Units] gustden:
Did you copy just the apk file? I copied the entire "Settings" directory to priv-app and it works fine for me.
[FYT Android Head Units] rnabi99:
Also, you may not need to do this anymore depending on why you were doing it. I posted a few days ago how to enable the Accessibility Services without changing your settings.apk, not sure if that is why you needed it.
[FYT Android Head Units] windowsdan4216:
I did just copy the Settings.apk and set the permissions to 0740 like my genuine 6.0 Settings.apk is.

I need it because I use another keyboard that can not set the settings for being a default keyboard as it can't get to the Settings.apk properly ... but mainly I require the VPN option in settings as I use 2 different VPNs a lot! My own for ftp and one to enable me to use Hulu (as I'm in the UK)
[FYT Android Head Units] AssassinsLament:
You need to copy the apk and the oat folder also and make sure all their permissions are right. Permissions should be 0644 for files, and 0755 for folders.

You can also just use my script to do it:

https://xdaforums.com/showpost.php?p=72107737&postcount=109
[FYT Android Head Units] shanetrainST:
Hopefully someone might be able to answer this.

I am running the latest joying android 6.0, with the modified BT apk & root & nokill server

I have this app that connect to an external Bluetooth device

The app alone connects via Bluetooth to the device and the app has it own 4 digit security code before it connects to the device, no pairing required.

After exactly 3 mins of the app being connected to the device it drops connection and reconnects, this happens every time.

Happy to donate for a solution

After it has reconnected it remain connected and does not miss a beat.

This disconnect/reconnect is really annoying

The app is

http s://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en

The device is

http s://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/

I am wondering if something in the Joying rom is causing the disconnect as it does not occur on any other android device I have used

happy to donate for a solution

EDIT - I have captured a HCIsnoop.log of the bluetooth errors and able to view them in wireshark

http ://www73.zippyshare.com/v/8SxO2rMx/file.html

My ALPconnect Mac Address is

FC:66:D7:53:D4:83

And the Joying Headunit Mac is

22:22:85:2d:f8:7b
[FYT Android Head Units] tuuza:
Can anyone else confirm this. Did you report this to joying?

Btw. You can just download the apk from web and update it trough play store if its legit.

For ex. http://mcdn.netflix.com/us/mobile/android/1142/netflix-3.1-41-1142-release.apk
[FYT Android Head Units] ant0ni084:
Ok sorry, because my English. I try to explain me better. I've downloaded your complete zip and I've installed it on C: in Windows., I've used CMD with administrator rights and started the file install.bat. It seemed be all right and when I rebooted the autoradio, radio app was the same of the original and I lost /system/app folder with all the original apps and I was forced to update again the autoradio. I can't understand where I was wrong.

Inviato dal mio MI 5 utilizzando Tapatalk
[FYT Android Head Units] surfer63:
what kind of command did you use to start the script? It almost looks like you never had a network connection with the head unit from your pc.

The script displays all kind of lines of text in the CMD windows. Please copy that and attach to a post.

Edit: example of unsuccesfull connection

+ adb kill-server
+ adb connect 2
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 2:5555
+ sleep 2
+ adb push JY-1-C9-Radio-V1.0.apk /sdcard/
error: device '(null)' not found
+ adb shell su -c am force-stop com.syu.radio
error: device '(null)' not found
+ adb shell su -c mount -o remount,rw /system
error: device '(null)' not found
+ adb shell su -c cp /system/app/JY-1-C9-Radio-V1.0/JY-1-C9-Radio-V1.0.apk /system/app/JY-1-C9-Radio-V1.0/JY-1-C9-Radio-V1.0.apk.old
error: device '(null)' not found
+ adb shell su -c cp /sdcard/JY-1-C9-Radio-V1.0.apk /system/app/JY-1-C9-Radio-V1.0
error: device '(null)' not found
+ adb shell su -c chmod 644 /system/app/JY-1-C9-Radio-V1.0/JY-1-C9-Radio-V1.0.apk
error: device '(null)' not found
+ adb shell su -c ls -l /system/app/JY-1-C9-Radio-V1.0
error: device '(null)' not found

Without that kind of output I can't do anything to help you.
[FYT Android Head Units] ant0ni084:
I've tried again. CMD with administrator rights, run file install.bat 192.168.0.100 (same network pc/autoradio) inside "blue" theme folder, nothing else.

C:\joying\Radio-Mod\BLUE_WHITE>install.bat 192.168.0.102

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

* daemon started successfully *

connected to 192.168.0.102:5555

restarting adbd as root

connected to 192.168.0.102:5555

455 KB/s (1544320 bytes in 3.312s)

-rw-r--r-- root root 1544320 2017-05-05 13:08 JY-1-C9-Radio-V1.0.apk

-rw------- root root 1544320 2017-05-05 13:08 JY-1-C9-Radio-V1.0.apk.old

"You need to reboot your device now."

Radio app doesn't work.

(package error in Italian language)

Inviato dal mio MI 5 utilizzando Tapatalk
[FYT Android Head Units] gustden:
I have been having many bluetooth issues on the 6.0 ROM with the connection dropping and reconnecting. If it happens during a call, the head unit reboots. I have sent the logcats and other dumps to Joying, hopefully they can get this resolved. It was rock solid on 5.1 for me. This is really my only complaint on 6.0.
[FYT Android Head Units] Skinzaholic:
Having the same issues here.
[FYT Android Head Units] surfer63:
Now I understand what you mean. The apk has already been installed and when you try to start it on the head unit it gives the package parsing error.

That is really strange. When I created my little preview clip 2 days ago, I used the eaxact same apks.

Please download the zipfile again ("Clone or Download" button) from the github site, and please try again. It seems that "something" went wrong with the zip file or unpacking of the zip file.
[FYT Android Head Units] midd33:
I installed the modified file after renaming the original. After rebooting, my Bluetooth options disappeared on my joying. The Bluetooth app is just gone. Rebooted this morning and got the same results.

I haven't been able to pair with my iPhone 7 Plus. I was connected to my ALP bluetooth module with the original app.
[FYT Android Head Units] lions123:
I have the same problem. I had copied the the single files from the github page (no zip). The installation is working, but I can't start the radio app. Also after loading the original radio app......
[FYT Android Head Units] surfer63:
Github is doing "something" to the files. If you simply download adb from github it doesn't function either on windows. If you do a git clone on windows, adb and the apks do not work correctly either.

On Linux everything simply works.

I think I will switch to releases, which you can download. It will also make clear when "something" has changed.

I will do that anyway when I have my apk ready.
[FYT Android Head Units] psxsnake:
Today I rooted my 6.0.1 using your script under windows it worked, only I removed "su - c"

and all was clean ad simple...

now waiting your app ;)

thanks for now
[FYT Android Head Units] surfer63:
The "su -c" is indeed redundant, also on 5.1.1

But on 5.1.1 it didn't make a difference.

Something in 6.0.1 changed (Android or Joying?), which causes a uid conflict as if it is not allowed to switch twice to root.
[FYT Android Head Units] amon101x:
yes tried it too with the same errors, says radio is not installed even though i can hear it in the background
[FYT Android Head Units] ant0ni084:
Nothing, I can't. It happens the same thing with bluetooth app, I've tried to replace it too but I get the same package error. I really don't know the reason. Can be it caused by my Android 6.0 version ?
[FYT Android Head Units] windowsdan4216:
Yes thank you. Copying the entire folder instead of just the apk file worked a treat :D

I did have to download the apk manually and the install worked fine. Not sure why the Google Play store does not allow you to install by default on 6.0.1 ?? :confused:
[FYT Android Head Units] lions123:
The original JY-1-C9-Radio-V1.0.apk from the Allap.pkg could be installed from my Mac and it is still running. The modified colored radio app still having a parsing error. I hope you can deliver your colored radio apps in another way. Thanks
[FYT Android Head Units] zazula:
The same problem.

The radio is playing in the background, but the icon is inactive.
[FYT Android Head Units] surfer63:
This is really strange. I tried itYesterday evening and it simply works.

Did you both download the zip?

And to make sure: Did you reboot after the install?

Every apk needs to be "optimized", which means it need to be precompiled (the odex files). For every new apk this normally happens on installation or startup of the unit. This is not a normal package manager installation, but simply a replace action. Rebooting the unit might really be the only solution in this case.

The layout has been changed. That might be the reason you can hear the radio app (as nothing changed there), but that you can't see it (as that changed).

So did you both reboot?

(And I will change that on my githubsite to tell users to reboot)
[FYT Android Head Units] amon101x:
I rebooted after installing your updated radio mod script. I downloaded your whole GitHub stuff as a zip file. When i copy the stock radio app in the system/app folder manually with root explorer (and replace your modded radio apk) it works again after reboot (but of course with the stock radio)
[FYT Android Head Units] lions123:
I tried it on my MAC and on Windows. I also downloaded the zip file, unpack all, and I did a reboot with the Terminal Emulator after all was copied to the radio. Still the original radio is running. When I select the copied radio app (FileManager) it response with a parsing error. No chance to install the RED_WHITE radio. By the way, I'm running on 6.0.1 Android version.
[FYT Android Head Units] windowsdan4216:
Major problem now. Every time I turn off the car it boots from fresh :crying:

After being off for only a couple of minutes.

Full boot with car logo and android bootup ... Not sure what would trigger this or how to fix it??
[FYT Android Head Units] PsychoMcSatan:
I think I have the same issue after installing the version of No Kill with just the SRC button assigned to Voice Search. Last three times I've gone for a drive, it's booting up from scratch.

I'll try again this afternoon and if it's still an issue, I'll try swapping back the original Sofia apk.
[FYT Android Head Units] windowsdan4216:
It didn't do it after I replaced the Sofia Sever file but now is a day later?? Wondering if something else has triggered it? Maybe replacing the Settings apk? Do you do that modification??