yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] luciusfox:
If it doesn't work, then the package is either incompatible, or the permissions are wrong, or there is a lingering odex file in /system/app/PACKAGE/ or /system/priv-app/PACKAGE/
[Android Head-Units] surfer63:
The package often mentions as incompatible ("There is a Problem Parsing the Package"). Then you re-install the original, boot again, and again install the modded app: et voila, it installs correctly. Really not reproducable. And as mentioned: it installs nicely for 95% of the users, but not for some users.

I check and set both permission attributes and user:group attributes in my apk/shell script combi.

I had it myself with one of my radio mods. I could not install it. Not via my apk, not manually over adb where other users installed it without problems. And suddenly one day it installed.

I also checked md5sums and sha1sums: all identical. No difference between the one on the website, the downloaded and the pushed into place apk.

I checked the entire system for the known mods of lingering odex files and the like. All the Joying (jerking) Allap.pkg apps do not install odex files in the /system area, only in the /data area.

All the apps out of the 5009_60.zip come with their precompiled odex files in the oat/x86 folders under the /system/app/package/ and /system/priv-app/package/.

Any clue here to improve the process is welcome.
[Android Head-Units] luciusfox:
That message isn't a compatibility message. Its a parser message. Sounds like it may be attempting to parse the file at the wrong time -- too soon?

For instance, if the apk file is unreadable by the package manager at the time when the package manager sees the file appear. That would make it "unparseable".

So think about your installation process;

What are the permissions on the file at the moment it is created? I.e., before you chmod it to the correct permissions. Is it 700? If so, the package manager won't be able to read the file, even though it knows that it is there.

Also think about the file creation process. Does it create the hard link and then fill it in with data? I.e., is it possible that the package manager is trying to read the file before it is all there?

Note: Android's default umask is 077, which corresponds to permission mode 700. Now you want the file to be created with permission 755, which would correspond to a umask of 022. So consider setting the umask before creating the file.

About the hard link creation, consider writing the apk file under an invalid filename, such as "data.dat", and then create a hardlink to that file, and then removing the "data.dat" hardlink.

So maybe this would work;

# umask 022

# cp FILE.apk /system/app/WHATEVER/data.dat

# ln /system/app/WHATEVER/data.dat /system/app/WHATEVER/WHATEVER.apk

# rm /system/app/WHATEVER/data.dat
[Android Head-Units] surfer63:
I will try.

Note though that I copy the apk to an org file. Then I copy in the new one. Really nothing happens at that time. pm does not do anything at that moment. And by copying it automatically gets the 0644 attributes.

I don't know the difference right now, but does your hardlink not simply overwite the original? Like my copy (after backup) also does?

After the copy in, "nothing happens". Only at the moment of reboot the package manager either optimizes the apk or it gives the parse error.

The default permission for the apk is 0644 though. For the folder it is 0755.

The mode 0700 and umask 022 is for the "linux" part of android, AFAIK. ( /system/{bin, lib, etc, usr, xbin} )

The apk part more follows the Free*BSD derived permission structure of the Mac OS/X bundle packaging structure (again AFAIK). No, it's not.

Anyway. I will certainly try your approach.

What I will also try is not to copy the original to an <name>.apk.org, but to move it.
[Android Head-Units] tangoman99:
Has anyone else had an issue with the Google Maps "Drive" Widget.

I've uninstalled and reinstalled Maps 3 times now - the first time to get it working which it does fine now, but when I look for the "Driving" widget it's not there! In fact there are very few widgets showing up - I installed Poweramp and put that widget on my desktop so SOME widgets appear.

Any thoughts? I have no problems doing the same on my phone or tablet - just the Joying unit.
[Android Head-Units] DBestman:
Which launcher?
[Android Head-Units] tangoman99:
Oh the Stock one - Intel Sofia Unit running Android 6.01
[Android Head-Units] krasykp:
Hi there,

i tried to find info, but i did not find answer if 6.0 is better or not for intel head units

I have a JY-VL130N2 with Android 5.1.1 and wondering if is good idea to update to 6.0 or not. With 5.1.1 the device is working smooth and fine. What is your opinion?

Thanks in advance :)
[Android Head-Units] newell63:
Hi everyone.

Same question for me....

I'm in firmware 08 december Android 5.1.1

Mandy of Joying don't recommanded to update to 6.0.1 and even any other firmware 5.1.1 .... any ideas ?

Thanks
[Android Head-Units] ch_swat_89:
Hi there

I installed the velvet.apk. Works now from every screen.

But: I can't install the offline langauges. It only says: No language package aviable for your language (german or english).

Any idea?

Regards
[Android Head-Units] swavey:
Speaker cut out error in Chinese

Has anyone experience their speakers cut out at high volumes where the navigation bar turns green and displays Chinese letters? It's almost like the amp over heats or something. Also, has anyone got Netflix to work? It doesn't show up in the Google Play store but I haven't tried downloading the apk to install that way yet either.
[Android Head-Units] luciusfox:
1) Mandy is a moron,

2) Mandy is a moron,

3) The kernel on that build is actually better than subsequent builds in that USB isn't (intentionally) crippled, but this is just dumb luck on Mandy's part for recommending this build,

4) Mandy is a moron.
[Android Head-Units] JobKlimop:
Installed it through Apkmirror, works like a charm:D
[Android Head-Units] swavey:
Thanks man I'll give it a try
[Android Head-Units] CadillacMike:
do you have the unit with the internal amp? mine did that, I had to turn off the "Loud" option to make it stop
[Android Head-Units] swavey:
Yeah. I think that's what causing mine too. I turned it back on and it started again.
[Android Head-Units] CadillacMike:
yup, turn off Loud, and mess with the EQ, you can make it sound good and not get that error
[Android Head-Units] swavey:
Yep. It stopped once I fine tuned it. I also got this response for the illustrious Mandy.

As when you put your the volume level too high, the power will be too big which the front speaker will can not undertake, then it will cut out

That Chinese word means "the front speaker overcurrent"

So pls do not volume up too much

Brest regards

Mandy

I'm running CT Sounds Meso 6.5 throughout the car. I didn't think this little amp could overload them. Was actually afraid it wouldn't push them enough but I'm very happy with the sound so far. Don't have my sub hooked up yet but you can't tell cause these things bump pretty hard for Mids.
[Android Head-Units] kjcsg:
Has anyone else had issues with viper4android after the 7 July update? It only works with spotify in compatible mode whereas before it worked in normal mode and if I enable the v4a equalizer the songs stutter and crackle plus play very slowly. Anyone else have these issues?
[Android Head-Units] tangoman99:
Having an issue with Tasker on my device which is one of the newish Intel 2Gb units.

I have my phone Tasker set to enable WiFI Tethering once a Bluetooth connection to the car is made - this works nicely - I get in my car and turn the key, starting my HU up, it connects to the phone, whcih then provides a Tether, and the HU then connects to the tether.

The problem is that I set up tasker on my HU, to start Speedcams using the WiFi connection as the Trigger. Unfortunately Tasker seems to be shut down when the unit goes to sleep.

I'm using the steering wheel customisation from here - can I use the script in this to restart tasker on a resume, or to prevent tasker from going to sleep in the first place??

How have others solved this problems?
[Android Head-Units] newell63:
Sorry for my bad english but, you want to say that android 6.0.1 will be better than my current 5.1.1 (december 08) ?

Anyone else for feedback (stable, rapid) of 6.0.1 vs 5.1.1 ?

Thanks
[Android Head-Units] bgroper:
Who or what is Mandy ?
[Android Head-Units] newell63:
Mandy is the contact of joying by mail (carjoying@gmail.com)
[Android Head-Units] luciusfox:
EVERY SINGLE BUILD that they've released is broken and buggy. You need to figure out which one will present the fewest problems *for you*.
[Android Head-Units] swanie2000:
I use Tasker on my Joying to solve a couple of bugs on my install as well. I found you need to have Tasker enabled in the "Settings --> Accessibilities" menu, to keep it active. Joying crippled the settings menu, and removed this setting.(only Joying knows why?)

If you are using the stock Joying "settings.apk" you will not have this option. You need to replace the stock Joying "settings.apk" with the stock ASOP version, after doing this, you will have the option to keep Tasker running in the accessibilities menu.

Surfer63 made this task really easy in his custom Joying Extra Tools apk.

https://xdaforums.com/android-auto/android-head-units/joying-extra-tools-apk-apk-to-help-t3628200
[Android Head-Units] tangoman99:
Many thanks for that - I have Surfer63's apk installed already so will look at it once the unit is back in the car - I'm busy drilling holes in it for the fan at the moment :D :o
[Android Head-Units] dyabolikarl:
If you see the source code you will know why it's terrible.
[Android Head-Units] mensand:
Hi i have a problem with FM radio not staying on current station. It constantly sees the next station and jumps to that for sometimes a minute sometime 10 minutes. I've already installed a signal ampiler. I've seen the sensitive setting but don't know what to put it on. LOC and AF tested. Somebody has a idea to try to fix this?
[Android Head-Units] surfer63:
You have the source code?

Or are you simply talking about decompiled smali code? Because that is something entirely different.

Also unzipped apks, using dex2jar and viewing the code with jd-gui or the like is still not the real java code.

But having the real source code would be great.
[Android Head-Units] newell63:
which version ?

You put manual sens to on, and AF to off.

For me it works, the radio stay on the current even if the signal is bad.

Try it.
[Android Head-Units] dyabolikarl:
Just the decompiled APK byte code. So probably not real source but you can see what everything is doing.

It's all decompiled back to JAVA though... So not sure if you could compile it back.

I find it interesting there is modules for tire pressure management etc.

Still don't know if it would compile (i'm not sure about the whole reverse engineering thing)

I wanted to try to import it into android studio. Not sure how to run it in emulation tho either.

[IMG="https://i.imgur.com/umozq6x.jpg"]https://i.imgur.com/umozq6x.jpg[/IMG]

Source looks ok.

[IMG="things"]https://i.imgur.com/pQ234aO.jpg[/IMG]
[Android Head-Units] surfer63:
There are a lot of people who already tried to recompile that. It will not work.

You have to check the java, build something yourself new also in java, compile your own java, decompile that to smali, and add that smali code manually to the smali code of the decompiled apk. And then finally recompile the apk.
[Android Head-Units] Guangor:
Hi everyone ... which version is more stable for you? I am on the 7th of July and I have problems with the gps I constantly miss the signal and I do not know what it can be.I checked everything and it seems to be okay I do not know if any application that installed can interfere because when I do a reset the unit works perfect for a few days and then fails again ... thank you if anyone can help me please
[Android Head-Units] edit:
Downgrade to another version and test again... If it behaves the same it would indicate an hardware issue. I did not have any issues with GPS on any firmware...
[Android Head-Units] Sergio45:
I am having this issue for almost one month and i think its a issue with the GPS antenna. When i move the cable or the antenna the GPS signal come back or dissapeared. I think the high temperatures and the sun damages my antenna (the queality of the antenna is really basic) so i ordered another one to test and solve the issue.
[Android Head-Units] Guangor:
Ok thanks

---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------

I've already been checking the antenna and it does not seem to be. . Joying tell me that it directly dies the cable to the plate and if it continues to fail I will be sent a new motherboard
[Android Head-Units] fabien_m2002:
Hello,

i can see on JY website, new firmware release but dated Sep,1st,2017!?

https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html
[Android Head-Units] newell63:
Yes because it's an update to improve system and apps.

It don't update the version to 6.0, the update is the same for 5.1.1 and 6.0
[Android Head-Units] BauBau94:
Anyoane download the last update from 1 september? and put in on car? how it works? any improvements ? bugs?
[Android Head-Units] Ahmad Quidemat:
I did , Things I've noticed so far:-

1- When placing the original Settings.apk , Developer Options menu won't open , it will keep crashing.

2- You can use "OK Google" from any screen , no mods needed , BUT , once you do that , no one can hear your voice in Bluetooth Phone Calls , Sound recording using third party apps is working fine though , I had to disable it after all.
[Android Head-Units] KeiserSozeyFr:
Do you know if "Ok google" from any screen only works for english language or for any language ?

It could be a good news for me as I don't use the built-in bluetooth hands-free function.
[Android Head-Units] merdok:
Weird thing happened today.. Has been like a month since any new software or modifications (dpi, no kill+voice search) and about a week since ran software updates.

Today I get in my car and home button now shows 'recents' hitting it twice executes the kill all apps from that screen.

Reboot and get the same thing. Car launcher loaded properly after reboot.

I accidentally forgot what level the reset button did, and killed my source of music on way home. [emoji58]

Any clue what could have mapped the home button to recents?
[Android Head-Units] Ahmad Quidemat:
I've tried it with Arabic for a while , it used to recognize my speech.

What language are interested in , maybe I can try it out for you?
[Android Head-Units] sweetnothings:
Hey, i am wondering if anyone else is still interested in using voice dialing (google) with the joying Bluetooth phone app?

After i invested little time on research, i found out that it is easy to get this to work.

If enough of you guys are interested, maybe [MENTION=2550900]surfer63[/MENTION] will add this to his "Joying Extra Tools" app.
[Android Head-Units] ste2002:
Hi sweetnothings, can you please share how? What else (apart from working "OK Google") is needed?

I've only had a success if I added a numerical prefix to a phonebook entry so "Home" would become "01 Home". Then HU's BT dialer was successfully invoked by "OK Google" then "Dial zero-one".

Without a prefix when I say "Dial Home", Google app correctly identifies phonebook entry (showing attached phone number) and pretending it is dialing, but HU's BT in that case does not pop up.
[Android Head-Units] surfer63:
Please share how you did it. If enough users are interested I'm willing to do this, but I like to know what I have to do before I say yes.
[Android Head-Units] PsychoMcSatan:
Sorry if it's a noob question, but what is the process for enabling full android settings? I see an apk as well as an "oat" directory in that 5009_20.zip. Is that the full, non-Joying version? If so, just copy that to priv-app on the radio?
[Android Head-Units] hongkongrr:
Can you please tell me where I can get the setings.apk with that setting? Also where to put it? Much appreciated :)
[Android Head-Units] gtxaspec:
extract 5009_20.zip

5009_20/System/Priv-App/Settings

Files must must be pushed to the unit in the same structure

System/Priv-App/Settings/
[Android Head-Units] AssassinsLament:
Settings replacement script

Here's a quick dos batch script for anyone wanting to switch their Settings.apk

Unzip, run settings.bat <ipaddress> from a dos prompt and then reboot.

After rebooting, the Settings screen will be the original one, but don't forget you must enable developer options.
[Android Head-Units] timnop:
Google Voice and Nova Launcher

Hello,

Yes, I am a noob to the Joying HU, but I have accomplished a lot with my new HU so far. I have installed, 6.0 right after installation, so I am not familiar with all of the tweaks that were established for 5.1 although I read through the roll-up thread quite a bit. I have successfully rooted it using the adb script, thanks to the author.

I have seen reference that the google app causes problems with UIC 3? I saw it first hand and had to uninstall google.

I have also seen that the Joying launchers may need freeze or removed in order for other launchers to work, which I have also seen first hand. When I change to the nova launcher, it reverts right back to stock launcher. Can someone explain what I need to do in order to use the Nova launcher and enable google voice commands?

I will also be installing the Torque app to connect with my ODBII.

What are some of the other favorite apps that I should consider?

Thanks in advance! :)
[Android Head-Units] edit:
A possible solution :

I've switched the Settings.apk that comes with the unit with the original one that has more options and a white theme (annoying in the car at night) and I have an HOME section where you can set the Nova Launcher as you default launcher.
[Android Head-Units] swanie2000:
So I went ahead and tried out the ApkPack.exe program you pointed to, and the image to understand chinese was very helpful, thanks!

I copied the Allapp.pkg file to a clean directory folder.

I then used the ApkPack.exe program to point to this file, and unpack it.

Next I opened "fyt_build.prop" file, and added 1 line of code to the bottom. (service.adb.tcp.port=5555) .

Then I clicked on the repack button, and the program packed it all back up.

Here's is the question.

Original file size was 321,991 Kb

New file size was 259,083 Kb

I added to one file, and the result was 62,908 Kb smaller?

Quite possibly, I did something wrong? I am using Windows 10 Pro 64bit.

Not sure I trust the new file that is 63Mb smaller.

Is this normal?

Also, is it OK to remove APK's that I don't want, and add APK's that I do use into this Allapp.pkg file? If so, it would make for a pretty nice way to auto load programs during the flash.

Swanie
[Android Head-Units] gtxaspec:
When you extract that there's one or two apks that don't get extracted. I believe it is Google Maps but it's okay you can install that from Play Store. Your file will install correctly. Yes you can remove APK as long as you don't remove the core joying and Sophia apks that enable functionality.
[Android Head-Units] hongkongrr:
After I tried to do this including trying AssassinsLament's script. Settings keeps crashing when I open it :( Any ideas? I also tried to clear the app data but it doesn't help
[Android Head-Units] AssassinsLament:
Probably got some of the files mixed and matched. Try deleting everything inside the /system/priv-app/Settings folder and re-run my script again.
[Android Head-Units] yokala:
Hello,

Can someone tell me what is the difference between ULS01N2 and UMS01 ?

They seems to have the same hardware, the only difference I see is the version of Android. Can someone confirm that ?

Thanks !
[Android Head-Units] Orisai:
Is it possible to create a settings.apk with all original Android settings unlocked, plus the Car Radio specific ones?
[Android Head-Units] AssassinsLament:
That would be pretty difficult as we do not have their source code.
[Android Head-Units] fabien_m2002:
Hello,

with this new firmware, i can make vocal command 'Call someone" and Google suggest me to call with Bluetooth! But it cannot dial through my paired smartphone.

What's wrong?
[Android Head-Units] surfer63:
That is indeed not possible at all.

Next to that: both package names are com.android.settings, which means you can't install them next to each other.

I'm trying to rewrite one (with a lot of copy&paste) from one packagename to another, but this needs to be done as well in all smalis.

This would then result in 2 separate Settings apks on your unit: far from optimal, but at least you can have both on one unit and use the settings from the relevant apk.

So far 2 not working google settings and one with limited amount of settings, but I should get it working relatively soon (I'm a naive, positive person and still have faith )

But I will now focus on the 6.0 version (and some other stuff I'm working on).
[Android Head-Units] gustden:
There are 2 places to set the launcher in the Car Media Settings. The fist tab at the bottom allows you to select between the Joying or other installed launchers. If you are using Nova, you need to select it here.

There is also a setting under the password protected page. This allows you to choose between the 3 different Joying launchers ( Advanced Settings Password: 3368, Menu password: 8086 )
[Android Head-Units] wanb1i:
In 5.1.1 I installed Titanium and froze all the launchers except NOVA to prevent this, simple really.
[Android Head-Units] xdamember2:
Even after re-flashing the Marshmallow update, no rooting and minimal installs, I cannot hear anything from Maps. All I get is muting of any other audio. Is there a required setting?
[Android Head-Units] gtxaspec:
Same here, needed to update all apps and carrier services. Make sure your maps is updated as well and set as default Navi app. Try that
[Android Head-Units] xdamember2:
Problem solved, I had to download the Google TTS voice data.
[Android Head-Units] surfer63:
If enough users are interested I can add the apk to the tools apk and push it t the unit.

But I can't build this app. I make my apks in appinventor 2, which is is graphical way of programming, not in java or C.
[Android Head-Units] gustden:
I just loaded the Sept 1 release yesterday, the install went very well. A couple things I have noticed upgrading from the May release:

- Bluetooth tethering seems to work better - connects reliably/no disconnects - test shows 1.4Mbs ( previous version was .8Mbs )

- The backlight current adjustment panel is back on my unit, so I can now lower the night brightness all the way to black ( this was missing and/or broken in previous versions )

- GPS is stable, no random loss of GPS signal ( yet anyway )

These were my only issues I had with the May release, so it is an improvement for me. Its only been a day, but no major bug so far.
[Android Head-Units] ricanbandit:
Thanks! I will be doing this tonight when I get home from the grind. BT tethering has been a pain in the ass, especially since the July release has rendered my Tidal app useless, so I was streaming from my phone but would drop off so badly.
[Android Head-Units] shanspidie:
How do have the Bluetooth tethering working? I have it enabled on my Bluetooth settings for the device. Is there any setting that we need to make on the headunit?
[Android Head-Units] gustden:
Try this thread - Number 17

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

I did have to install the 'ASOP Settings.apk' to get access to the bluetooth panel of the settings. Item 16 in the same thread.
[Android Head-Units] warata:
The new firmware is very unstable, suddenly stops and automatic wipe data recovery begins, my time and effort are also wiped out.:(

Does anyone have the same experience?
[Android Head-Units] ste2002:
warata, did you do full reset (from Android menu) prior to installing? The first time when I installed Sept FW without prior full reset, I got unstable system. The reflashing after a full reset was quite successfull.