yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] brunes:
These are really cool.

How are you guys doing this, just replacing images?

What I would REALLY love to do is make the font larger for the RDS text, and/or make the RDS text area larger. I do not understand why the developers of this app decided to make the RDS text impossible to read and put the frequency so large.

---------- Post added at 09:19 AM ---------- Previous post was at 09:11 AM ----------

Here is what I did - I bought an old junk Samsung Galaxy S2 on Kijiji (like Craigslist) with a cracked screen for next to nothing ( $25 )... I then installed MacroDroid on it and set it up as follows:

- When USB charge disconnected, turn on airplane mode

- When USB charge connected, turn off airplane more, turn on wifi tethering

I then plugged the phone into the back of the head unit via one of the USB ports on it, run into my dash.

When I turn on the car, the head unit activates the USB ports... the phone detects the charge, turns off airplane more and turns on wifi tethering, and charges. The head unit sees and connects to the wifi and tethers. When I turn off the car, the phone goes into Airplane mode, allowing the battery to keep it running for almost two weeks without charge. Have had this setup working for weeks, works very well.
[FYT Android Head Units] surfer63:
Updating/replacing images.

And for the text you modify the layout xml. That's what I did with the RDS PS text which I moved from top-left small to center-down large (my signature is leading to the repo with "clean" screenshots).

The RDS RT text is very buggy at this moment. I looked at that but can't improve it. I'm not a java/smali programmer.
[FYT Android Head Units] brunes:
Where are you guys getting the source code for the app?
[FYT Android Head Units] rnabi99:
OK, sorry I am new to this and did not know about busybox.

As a side-note, I Googled busybox to find out more about it and found a post that says that you can update busybox pretty easily using Titanium backup - what do you think of this method?

http://forums.androidcentral.com/motorola-droid-rooting-roms-hacks/8978-what-busybox.html
[FYT Android Head Units] surfer63:
I finished that this afternoon. See my signature for the link.

The screen look slightly different on the screenshot as I made the screenshot from an emulator, which means that the radio can't find any "radio hardware" and can't show the RDS data or frequency band (FM-1).
[FYT Android Head Units] ZoSo028:
What info is this based on? Will 6.0 be released as an update for the current 2gb sofia units or are you referring to new units sold running 6.0?
[FYT Android Head Units] rnabi99:
Thanks! I have been using the Blue version in the meantime and I love it. Is there any way to make the RDS text box bigger?
[FYT Android Head Units] artvoip:
https://www.youtube.com/channel/UCFrkbO6PkJJOR7c3zWiloVA official channel of Joying. And nothing about Android 6 today. Joying is funny company. Told about update and keep silence.
[FYT Android Head Units] bogdi1988:
IF anything comes it today, it will be later tonight when it's daytime in China. It's 3AM right now (18th). They open at 8 ish. IF they release anything they still meet their deadline because it's still the 17th here haha
[FYT Android Head Units] alda.cerny:
Chinese logic :laugh:
[FYT Android Head Units] artvoip:
I'm waiting not Android 6, but bug fixes. 1. ALL translations to Russian are just terrible, they were translated Bluetooth app like Blue tooth but in Russian :), + symbol is not working right now, I can't call +number... Sofia 3GR with 2 Gb RAM extremely slow with Play Store.... :mad:
[FYT Android Head Units] bogdi1988:
Tell me about it! Haha!

---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------

Dunno what you are referring to... Running the same Sofia unit with Play Store, Waze, Youtube, and a bunch of other apps in background and have 0 issues whatsoever. No slowdown at all.
[FYT Android Head Units] KamaL:
The only place where they stated April 17 was on the YouTube channel, nowhere else. None of the staff confirmed the date.

I don't expect anything from them
[FYT Android Head Units] artvoip:
I have iPhone 6s Plus, I have Xiaomi Mi Max. Just compare installation time of any app (like HereWeGo for example), you will wonder how it is slow on HU. Updating apps and installing new apps are very-very slow.
[FYT Android Head Units] KamaL:
Agreed, it takes forever. I think it's the storage transfer rates
[FYT Android Head Units] surfer63:
Of course. But this work was partly finished and I simply wanted to finish this the same like the others before starting something new.

However, with the new 6.0 version "officially" released 17 April (but nothing there yet), I will first wait to see if something changes in the new radio. And hopefully the RDS AF and RDS RT text will now correctly work.
[FYT Android Head Units] bogdi1988:
One tip I forgot to mention. To get a bit of "oomph" from the volume... go in the car media settings app, under the volume balance settings and bump everything to 10.
[FYT Android Head Units] Rottgrub:
I got a quoted date of the 17th from an employee, based on a support question I had. Have patience.

"ying huang 2017-04-14 23:20

Hi dear friend,we will release android 6.0 at next Monday,and we will send you a file to you upgrade at that time,and you can update it,maybe it will solve this problem,have a nice day!"
[FYT Android Head Units] bogdi1988:
Since they gave you that quote, you should email them asking where the update is. Or hit them up on chat...
[FYT Android Head Units] Rottgrub:
Honestly, I'd prefer to give them time they need to put out a stable and tested update, rather than rushing them into releasing something riddled with bugs. It's not like the headunit is non-functional without Android 6.

Have patience.
[FYT Android Head Units] bogdi1988:
They don't put it together. The factory that they get the boards from customizes the software for them
[FYT Android Head Units] artvoip:
Nothing was released yesterday and "soon" means not date. Chinese....
[FYT Android Head Units] bogdi1988:
LOL! So (sorry for the non-PC expression) that means April 17th on Asian time, so I would ballpark more like end of the month...

EDIT: see chat with their support in the attached image.
[FYT Android Head Units] artvoip:
They said "wait several days" ))))
[FYT Android Head Units] bogdi1988:
Yup! Kinda disappointed tbh...
[FYT Android Head Units] KamaL:
Always stay with low expectations with these companies :)
[FYT Android Head Units] bogdi1988:
Yea, but still. Usually like to keep one's word, OR something saying "sorry, date changed" you know what I mean? ;)
[FYT Android Head Units] merit40:
step by step procedure

Hi, somebody can post step by step procedure, how to connect pc to software to use, thank you.

How do you read the bootloader?

1) Read out bootloader from boot partition and store it temporarily on /data

root@sofia3gr_car:/ # dd if=/dev/block/mmcblk0boot1 of=/data/mmcblk0boot1.bin
[FYT Android Head Units] tbd@immigrantsong.de:
Adding another RED-YELLOW version based on your work. I've 3D'd the buttons. No photo as I don't have an emulator.
[FYT Android Head Units] tbd@immigrantsong.de:
A word of caution! If you require a step by step procedure on this there is a very high chance that you will hard brick the unit!

Do not do this unless you know what you are doing!

And don't come back ans say we didn't warn you.
[FYT Android Head Units] surfer63:
I think it will take some more time.

Currently someone (Bella) from Joying is doing an inventory on all bugs/issues on the official carjoying forum.

They are still taking in bugs.

Either they will need quite some more time for the release, or they will do a release (probably with some fixes) followed shortly by another "bugfix" release.

This is of course completely guessing from my side.
[FYT Android Head Units] edit:
Ok, I've spent my last 4 hours trying to make the Viper4Android to work but I get all kinds of errors and I am over my head with android scripts and all.

what I have done so far :

1. updated the OS to the latest version - 28 Mar 2017

2. rooted with the second method, the script worked like a charm

3. wanted to install Viper4Android but after this error "addprop.sh[25]: sed: not found" the script gave an error after each line

4. wanted to update the supersu because [MENTION=503463]AssassinsLament[/MENTION] advised to and tries with the script provided by [MENTION=2550900]surfer63[/MENTION] but got some errors

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

* daemon started successfully *

connected to 192.168.1.56:5555

connected to 192.168.1.56:5555

326 KB/s (13788 bytes in 0.041s)

412 KB/s (14302 bytes in 0.033s)

61 KB/s (629 bytes in 0.009s)

546 KB/s (346536 bytes in 0.619s)

536 KB/s (99916 bytes in 0.182s)

539 KB/s (6539610 bytes in 11.847s)

577 KB/s (46416 bytes in 0.078s)

mount: Device or resource busy

Reboot your Head Unit NOW!

5. tried to use an open hotspot from my phone, no ecryption, no pass, no go.

6. I am stuck.
[FYT Android Head Units] naplesbill:
I tried the script with similar issue. I ended up copying the apk to the system folder the script was attempting and it works.
[FYT Android Head Units] surfer63:
This "mount: Device or resource busy" happened to me as well yesterday when I was testing new "multi-menu all purpose" scripts. It happened because Google Play was in the background downloading/updating apps (I wanted to be efficient, so do more things at a time).

You can try again if you have the idea that "nothing" is downloading, installing, updating, etc. (this can also be you navigation app doing "things").

The current rooting script also remounts the root partition (/) to make a folder called /tmp. This is not necessary but I copied it from the initial script.

I will update the installation routing to get rid of this root partition remounting. There are much better ways of doing this.

(In due time these single purpose scripts will be removed and replaced by the multi-purpose menu script, for rooting, busybox, radio mods, sofiaserver mods, changing DPI, deactivating useless apps (TV, music player), etc.. That might be days or weeks. I'm not finished yet: If the android 6.0 release comes out any day, I might need more time, but I assume everything will stay the same.)

You should update the busybox binary for AssassinsLament script to work.

I do not have my original busybox anymore, but someone (@AssassinsLament ??) could/should test whether changing the last line in the "addprop.sh" should be changed from:

sed -i '/deep_buffer {/,/}/d' /system/etc/audio_policy.conf

to

busybox sed -i '/deep_buffer {/,/}/d' /system/etc/audio_policy.conf
[FYT Android Head Units] edit:
1. I've did a reset to defaults to get rid of the google account and reset everything (well, most of the settings) to be sure that Google Play store will be idle, not being able to update any apps or sync accounts.

2. tried your script but unfortunatelly it did not work

3. disabled google play services and ended the task, also did the same for google play store,

4. tried the script again... same error

Any ideas?

Thank you !

later edit : I've made an open hotspot on my phone but with no internet access to prevent HU apps (other then google's play store) downloading or upgrading or... anything... it did not work... I don't have any mode ideas

later edit 2 : What If I upgrade the SuperSU from Google store? Will it work or yours has some custom scripts tailor made for Sofia?
[FYT Android Head Units] merit40:
How do you read the bootloader?

1) Read out bootloader from boot partition and store it temporarily on /data

root@sofia3gr_car:/ # dd if=/dev/block/mmcblk0boot1 of=/data/mmcblk0boot1.bin
[FYT Android Head Units] edit:
I've reflashed the unit, started from scratch.

1. used your script to update SuperSU and this time it worked... your script does ROOT on the unit? because I did not ROOT-it prior to SuperSu update with your script.

2. I've made the modifications that you suggested on "addprop.sh" with an ".sh" file editor and ran manually the script to install Viper4Android, line by line and everything was fine till it got stuck here:

c:\1>adb shell "cp /tmp/viper/system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk /system/priv-app/ViPER4Android_FX_v2505"

cp: /tmp/viper/system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk: No such file or directory

3. I am stuck... again...
[FYT Android Head Units] naplesbill:
That was what happened to me. Just take the apk it lists there and copy it to the destination folder. That worked for me.
[FYT Android Head Units] edit:
I've copied the "ViPER4Android_FX_v2505_A4.x-A7.x.apk" to the "/system/priv-app/ViPER4Android_FX_v2505/" with RootExplorer but still no luck... i still get the same error
[FYT Android Head Units] surfer63:
Good to hear it worked. About 1 hour before this post (my post) I updated the root scripts.

The script copies the necessary files to the unit including an install script. On the unit that install script is started which does the rest of the work.
[FYT Android Head Units] Hilari0:
How does Android actually detect if ACC is present or not? Is it interpreted as plugging or unplugging a charger, or is there some other event?
[FYT Android Head Units] nase1970:
On my head unit (firmware: dec 2016) this tip doesn't work. When I'm touching on the screen while the backup camera is on, nothing happens. Is that a new feature in the january update?
[FYT Android Head Units] bogdi1988:
Yes. Feature present in January update.
[FYT Android Head Units] breevesdc:
Hello. I'm looking for help to resolve an issue that just started with my head unit today. I applied the customization for IMMERSIVE MODE (IM) found on the first page of this thread. yesterday. This morning, while driving my car, the head unit was acting weird. At first, it had sound (first couple of minutes). It then rebooted on its own and ever since then, it reboots about every 5 minutes. Additionally, the sound has completely disappeared. None of the apps produce sound anymore.

My question is, how can I back out the IM update that I applied using ADB? I can only recall one app that used IM. I assume that I can reset things back to normal and then uninstall/reinstall the app that uses IM so that it sets this setting properly. But I'm not sure how to resent things back to Android's natural state. Any thoughts would be appreciated.

FYI... I also installed the patch to stop the head unit from killing all apps when going into Sleep Mode. But I did that on Saturday and used the head unit for several hours after that. So, I assume that this script is not related to my current issue.

Thanks in advance.

Brian
[FYT Android Head Units] gustden:
The default setting for immersive mode is null. This can be reset as follows:

settings put global policy_control immersive.full=

I seriously doubt this is related to the issue you are having. If you continue to have issues, I would factory reset the device and reload the ROM. What your describing could even be a HW issue.
[FYT Android Head Units] derschnelle:
I installed nova launcher, but it wasn't recognized correctly. So I have to freeze the stock launcher via titanium backup?

I am a bit worried I will be left with a device and no launcher to interact after freezing the stock launcher...
[FYT Android Head Units] thedru13:
Did you try a factory reset? I don't have any issues with the nova launcher.
[FYT Android Head Units] derschnelle:
No, hadn't done a reset yet. But doing one now :).
[FYT Android Head Units] thedru13:
Hopefully that fixes your issue. I would be lost without nova launcher.
[FYT Android Head Units] derschnelle:
The reset didn't do the trick, but after installing the google now launcher it asked me to go to the settings and change the standard homescreen. There I could change to nova and now it's running fine.
[FYT Android Head Units] gustden:
Nova will not work properly on my system unless I disable the Joying launchers, even after a factory reset. UI3 also crashes and cannot be used as soon as I install nova.

Some reason, they don't play well together on my device. It's not really an issue for me, as I only use nova now.
[FYT Android Head Units] thedru13:
Wonder what is different. I am able to run UI3 and switch back to Nova with no issue.
[FYT Android Head Units] nase1970:
Updated to January-Firmware today. But I still can't see any settings, when tapping on the screen, while the backup camera is on. And now my graphical park-sensors are not shown any more. What have I done wrong?
[FYT Android Head Units] sonof:
See car media settings app for Radar switch to get back park sensors.

---

Apex Launcher works perfectly for me without the need to freeze stock launcher.
[FYT Android Head Units] nase1970:
Thanks, after reinstalling the canbus-protocol and switching the radar-switch on, the parking sensors are working again. But it's not possible to get the settings of the backup camera. Is there an item in the car media settings, that I didn't seen?
[FYT Android Head Units] bogdi1988:
Put car in reverse and touch anywhere on the screen while camera is on. Should bring up the settings.
[FYT Android Head Units] nase1970:
It's stange, but that is not working for me. Nothing happens, while touching the screen.
[FYT Android Head Units] CadillacMike:
i think i figured out what caused UI3 to go crazy on the Feb 22nd update.

On my initial install it was buggy and I couldn't see the home screen properly. I had to do a factory reset. Since then it has been fine. I have been just running Google Maps, Google Play Music, 1Weather, and Waze.

today I tried installing Android Auto, which causes the Google app to be installed. As soon as it was installed it did that weird thing where you can't see the home screen. I could still use the App switcher, and navigate back to the Play Store. I tried uninstalling Android Auto, and nothing changed. But when I uninstalled the Google app, and it went back to working as normal.

this Google app:

https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
[FYT Android Head Units] bogdi1988:
This issue was present in the January update for me also. I just ended up installing Nova launcher and then installing the Google app. UI3 freaks out when Google adds the search buttons in the app launcher.
[FYT Android Head Units] CadillacMike:
too bad, I really like UI3. I hate UI2
[FYT Android Head Units] edit:
It worked but I have a problem, when an app asks for root permision from SuperSu and the dialog box pops up on the screen I can't DENY or GRANT... I touch the buttons and nothing happens.

I had to set the SuperSu to GRANT every request it receives so I could make it work.

It's still not clear to me : Should I use your script instead of rooting the unit via method 2? Or shall I root it first via method 2 and then install your script to update the SuperSU?

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

OK, I managed to install Viper4Android ! Finally ! What an insane struggle ! It took me more then 8 hours to learn and test various scenarios so I can understand what is what... and I barely scratched the surface.

The problem with the script that [MENTION=503463]AssassinsLament[/MENTION] made is that has some errors... Maybe it had something to do with me, I can't really tell for sure... I am still learning.

So :

1. I extracted the contents from the zip file to the "c:\0"

2. Ran the script "c:\0\install.bat 192.168.43.03

3. did NOT worked gave me an error "addprop.sh[25]: sed: not found"

4. updated the SuperSU and made modifications to the "addprop.sh" as [MENTION=2550900]surfer63[/MENTION] advised me here https://xdaforums.com/showpost.php?p=71914086&postcount=574

5. ran the script again this time line by line and at this line :

c:\1>adb shell "cp /tmp/viper/system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk /system/priv-app/ViPER4Android_FX_v2505"

got this error :

cp: /tmp/viper/system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk: No such file or directory

6. checked with RootExplorer and realised that the file "ViPER4Android_FX_v2505_A4.x-A7.x.apk" was NOT in /tmp/viper/system/priv-app/ was in /tmp/viper/priv-app/ so I replaced the above line with this one

c:\1>adb shell "cp /tmp/viper/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk /system/priv-app/ViPER4Android_FX_v2505"

got no error

7. also modified this line from the script :

adb shell "cp /tmp/viper/system/etc/audio_effects.conf /system/etc"

with this one

adb shell "cp /tmp/viper/etc/audio_effects.conf /system/etc"

LaterEdit : I've attached the install.bat that I've modified that worked for me so you can inspect and better observe the changes.
[FYT Android Head Units] charnocc:
Yes, exactly like this.

If you need help with this step, you will most likely break your device. And in this case, this means bricking, creating a useless brick out of an electronic device, thus throwing some 100 Dollars out of the window.

With this warning upfront, i give you some pointers:

- What you basically will do is to read out the bootloader, change it, and write it back. If you make a mistake at any of this steps, you have created an expensive brick.

- Read about what adb is, what commands it provides, and how to connect to an adb device via wlan.

- Read about hex editing.

- Read how you can compare two binary files to check that you did not make any mistakes which will break your device.

- Then, if you understand every step of the list (which is already pretty easy step-by-step), decide if you want to continue with the process. Maybe ask if you understand the steps correctly, maybe decide that you want to start practicing with something easier - for example the radio mods or similar stuff which can be undone.
[FYT Android Head Units] AssassinsLament:
My simple install script does not have any error checking but it should work. The problem with the "sed" issue is because busybox is not installed or it's not installed correctly. My script also should upload the whole system folder, so the system path should work. Will check and update if it needs after Joying updates to Android 6.0, no point in updating until then.
[FYT Android Head Units] naplesbill:
After copy just reboot. No need to run script again. If you did you have to copy again and reboot
[FYT Android Head Units] CamryGuy:
Where is the promised Andoid 6.0 upgrade?

2 days late at this stage. ?
[FYT Android Head Units] edit:
I am in no position to argue that your script did not work. In fact I want to THANK YOU for the step by step explanations of your script.

My only curiosity is why in the first steps of the script the files were copied to "/tmp/viper/priv-app/" and NOT to "/tmp/viper/system/priv-app/" hence the error not finding the files later down the script.

For some here,very familiar with linux and android this problem would have taken 10 minutes to solve... but for me, 1st class noobie, it was a struggle.

---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------

Yes, they promised it for the 17 of April, but, as it turned out they aren't ready yet...
[FYT Android Head Units] CamryGuy:
Surprise, surprise.

No doubt there were too many bugs to release it.
[FYT Android Head Units] artvoip:
They didn't want to release beta to collect more info, they did't want to get help from community about translations. And as a lot of small companies, they don't think and just do. Say about release on 17th and then nothing
[FYT Android Head Units] edit:
Guys, I've encountered another big problem.

I tried to change de DPI from the default 160 to 220 and 240... Each time the unit did not boot after restart... it froze at the "android" screen for several minutes and it's engaged an automated wipe of some sorts... resetting everything to defaults on the unit.

the first time tried to change the DPI with an app from Play Store, did not work. I thought it's the app fault so the second time I've changed it in the build.prop directly by editing it with RootExplorer.... same outcome.

How do I change the DPI on this unit?