yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] budwha:
I have installed the mods from this forum and am very happy with my HU now. Thanks to everyone for sharing their hard work.

I do have a couple issues that I would like to know if anyone else has noticed. ......

1........occasionally after starting my truck the steering wheel buttons completely don't work(after restarting

they work again) ......they either work flawlessly or not at all

2.......occasionally after starting, the radio stations don't work. ........all I get is static. ....doesn't matter what

station I tune to.

This has nothing to do the mods because it did this even before changes were made. I'm using the March 14th update.
[FYT Android Head Units] testrz:
Hello,

I've tried with a Joying JY-ULS01N2 (Intel SoFIA 3GR CPU) with the latest firmware (Android 5.1.1 Lollipop, March 28), unfortunately the solution didn't worked for me. I've done all the procedure and I can confirm that the serial is now "0123456789012345" on my HU, however I've tried to install tomtom go mobile latest version and I still get the "app cannot connect" error message.

I'd like to reduce the serial to 12 char (i've read somewhere that this is the max lenght accepted by tomtom), can i do it with the same procedure? Or am I risking a brick?

Thanks and regards!
[FYT Android Head Units] realzoulou:
The risk is the same. 16 or 12 characters does not matter.
[FYT Android Head Units] charnocc:
Can somebody confirm that after the serial change in the bootloader tomtom go is working? For this i'm willing to take the risk.
[FYT Android Head Units] testrz:
The thing which worries me is that I've seen another string "012345679012345" few bytes away from the serial string (it was already there and I haven't changed it). I'm wondering if there is a double check of some sort (and if there is no corrispondence between the two strings then hang forever). What do you think?

Thanks and regards!
[FYT Android Head Units] realzoulou:
I saw the other 16 characters as well, but I have no clue what this is used for. Sorry.
[FYT Android Head Units] tbd@immigrantsong.de:
See here: https://xdaforums.com/showpost.php?p=71694326&postcount=343

Works as a gem.

Do you have a stable internet connection? Otherwise it sounds like the install failed. Check that you really got the install right by repeating the initial step:

root@sofia3gr_car:/ # cat /proc/cmdline

androidboot.bootloader=1639.400_M1S1 androidboot.serialno=0123456789012345 [...]

---------- Post added at 11:30 AM ---------- Previous post was at 11:17 AM ----------

A few minor corrections, you mixed your units a bit:

96mA *24 hours = 2.304 AH daily draw.

2.304 AH * 7 days = 16.128 AH

Starting from a battery with with 72AH this leaves ~56 AH rest capacity after one week, 40AH after 2 weeks.

However, I believe the units shuts down totally after a certain time and should draw near zero after that. This time is seemingly more than 24 hours, but as I have observed less than a week. It would be interesting if someone would measure this residual current.
[FYT Android Head Units] charnocc:
Thanks, then I will try at the weekend :)

I have made some measurements, directly with the multimeter (not with this parasitic trick shown in the video posted...), and I got values around 0.015A for standby and 0.003A for shutdown, so significantly lower. When powered on (without sound) I got around 0.8A. The standby / shutdown process after I removed the key took about 2 or 3 minutes.
[FYT Android Head Units] edit:
This is a HUGE difference... with these numbers I can leave my car in the parking lot for a month and it will start with no problems.

As a guy who does not know how to measure the current drawn now I am a bit puzzled... what set of numbers I should trust :)

Better yet... when my unit arrives, I will ask a friend to teach my and I'll post my findings (numbers)

Thanky you [MENTION=6361270]charnocc[/MENTION] !
[FYT Android Head Units] tbd@immigrantsong.de:
This sounds more realistic, though your masurements may be on the low side. The other method is very "guessy", a factor 10 error more than likely realistic.
[FYT Android Head Units] testrz:
I've launched TomTom again this morning, and this time everything worked! Onestly I don't understand why, I've only switched on the HU again and started TomTom after about 14 hours and it worked (no changes since yesterday after I've modified the serial with your procedure, I was under wifi coverage too so connection was fine).

So yes, I can confirm that this procedure is working perfectly with a Joying JY-ULS01N2 (Intel SoFIA 3GR CPU) HU with the latest firmware (Android 5.1.1 Lollipop, March 28). Now my serial is 0123456789012345 (16 digit long) and TomTom is starting and working well (latest version, downloaded yesterday).

I can't thank you enough for sharing your knowledge and providing this solution! Many many many thanks realzolou!

Thanks and regards!
[FYT Android Head Units] charnocc:
Maybe a third person can also make some measurements? In my car it was easy: I have removed the fuse for the car radio, and made the measurement there. I have a UL-135N2, btw.

Thank you for your feedback.
[FYT Android Head Units] Tubra:
My readings seem to be accurate as my battery had trouble a few days and my car was difficult to start. I re-checked and the Joying is drawing around 125mAh when the car is off. It would really be nice to know exactly how much power this thing is supposed to use when off. The battery health is ok. I checked for any bad wiring and there seems to be none so far. My next lead is to check out the blue 12v wire, as I have my remote wire hooked up to the amp from the antenna. I'm going to try disconnecting it and see if it makes any difference.
[FYT Android Head Units] OcGomes:
Hello Guys

Did you try to connect the xbox 360 joystic? I have a wired xbox360 controller and is not working on joying.

Thanks
[FYT Android Head Units] rnabi99:
Did you get the link I posted?
[FYT Android Head Units] aaron19953:
All the talk battery drain from storing a vehicle for weeks / months, why not just purchase a battery tender and forget about it ? Seems like simple insurance to me

https://www.amazon.com/Deltran-Battery-Tender-021-0128-Charger/dp/B00068XCQU
[FYT Android Head Units] grumetecap:
Hi, thanks in advance for your awesome work

I have some problems with this unit... And I'm finding it difficult to fix it,the first is the rotation of the screen, i found this

"Phone / Tablet view on apps - No app needed - Change from 160dpi -> 161dpi gives" phone "view of many apps instead of" tablet "with no noticeable size change to other things.

> Wm density 161 # (phone mode apps)

> Wm density 160 # (original tablet mode apps) "

But i don´t know how to made it,need a windows computer to make this change? There is no other way to do it?
[FYT Android Head Units] edit:
Can't talk about other people but my following issues are:

1. I have back problem and lifting such a heavy battery is a big problem

2. Taking the battery out of my car is a pain in the butt... I need to dissamble the air filter and other parts to get to the battery

3. I live in a building with lots of stairs and no alternative

4. I dont have a garrage so i can't charge the battery while it's in the car

5. I need to follow a specific procedure to take it out and to put it in (takes time) and i have to set after things like windows and other bits

I'd rather install a small switch that cuts the HU permanent +12V wire when I'm away for more then 1 week... But I hope it will not be the case
[FYT Android Head Units] surfer63:
Yes, I have. But I'm quite busy at the moment with all kind of things like trying out scripts and possible an apk.

---------- Post added at 09:09 PM ---------- Previous post was at 09:06 PM ----------

Currently you need adb from a computer.

Or you root your system with SuperSU adding policies again (see my signature) so you can give other apks root access like a terminal emulator, and then you can do it from the unit directly.
[FYT Android Head Units] aaron19953:
Ah, yes, very good reasons indeed!

As far as wiring a battery tender, they have a pigtail that stays connected to the car so you only need to access the battery once, but with no garage that's going to be tricky. Adding a switch shouldn't be difficult but would require removing the head unit again. I'd go for just yanking the fuse personally.
[FYT Android Head Units] grumetecap:
[/COLOR]

Currently you need adb from a computer.

Or you root your system with SuperSU adding policies again (see my signature) so you can give other apks root access like a terminal emulator, and then you can do it from the unit directly.[/QUOTE]

Ok, i install adb then i have the device on the list and after this a have to write > Wm density 160 # ?

Moreover my unit just let my use poor resolution in the youtube videos, it looks like web version ¿? and i don´t know where i can change the buttons color light :eek:

I am thinking of returning the unit, however I had read that this was the best right now....
[FYT Android Head Units] tbd@immigrantsong.de:
Then something is wrong with your wiring. Actual residue current is much lower, as others have measured. If you're still using that fuse voltage drop your fooling yourself. Insert a 10 Ohm resistor in place of the fuse and measure the voltage drop (1V = 100mA).

BTW. I have the unit in my Lotus, which has a small 54AH battery and have no issues.
[FYT Android Head Units] derschnelle:
I just tried to connect a webcam to my HU, but no app I tried was able to detect it.

The webcam is a UVC cam (https://www.amazon.de/gp/aw/d/B01MY...UVC+Kamera&dpPl=1&dpID=41cMwwJBuPL&ref=plSrch).

Do I need to configure the webcam or the usb port?
[FYT Android Head Units] surfer63:
There are many, many excellent articles on the web about adb. Please search ("adb howto" or "easy adb", etc.).

What is poor resolution? The resolution is 1024x600 and that is exactly what you get. So please specify. You are too vague.

You can only change the color of the buttons with your head lights on. Then the color settings appears in your settings (headlights on -> start the settings)

---------- Post added at 11:03 AM ---------- Previous post was at 10:53 AM ----------

Webcams never work nicely. They put a huge burden on the unit. The reason that specific dash cams are sold is that they have their own chipset doing the video encoding and saving the video locally on an sd-card in the dash cam.

The Joying Dashcam apk only controls (!) the dashcam and can show you a live image (that means: no encoding at all)

Another issue is the flooding of the USB controller. The Joying units come with only one USB-2 controller. As such even a HD-stream could run over USB-2, but USB-2 (and USB-1) are half-duplex, which means that only one signal can run in one direction at the same time.

If some other USB device is doing "something", your video stream will/might be broken.

However, if you want to use a webcam go for usb port 5. The first 4 are "reserved" by Joying and this is hard-coded. But recording at 1280x720 will be limited to 1-3 fps while at the same time your unit will struggle to survive. And you can forget about 1920x1080

A real dash cam allows you to record up to 30 fps without issues.
[FYT Android Head Units] derschnelle:
Thank you very much for this detailed answer. As you suggest, I think I will switch to the original one from joying.

Do you know if it is possible to use other apps than the DVR-app with joying dashcams? I would like to use the "my drive assist" app from Bosch with it.
[FYT Android Head Units] phatass_dk:
Hi guys,

Was hoping for your assistance once again.

I have the VW-specific 9" Sofia unit in my 2015 VW Polo BlueGT.

I am using the Joying 4G dongle with a SIM card to share its WiFi. It's working pretty poorly and the connection between dongle/HU as well as dongle/4G is rather terrible. The WiFi and 4G connection drops a lot.

I have a quite decent Huawei USB dongle (w/o wifi) that I'd like to use instead. I've tried to use PPP Widget 3 to connect it but with limited success. With PPPW3, I have to press "connect" each time the HU starts and every time the connection drops. The auto-connect/re-connect function doesn't work.

Is there any way to connect the USB dongle directly though the Android UI?

Other ideas?

P.S.: "phatass_dk" is an idiot with an iPhone. :)
[FYT Android Head Units] surfer63:
Joying currently sells a 720P dash cam but is already spreading videos of their new 1080P dash cam.

It might be worth to wait for that one or contact Joying when they will start to deliver that one (maybe at the same time as Android 6.0 together with a new apk?)

I do have the same question :) I'm also looking at several ADAS solutions to make the driving more safe.
[FYT Android Head Units] tbd@immigrantsong.de:
I returned the Joying dongle as it is absolute junk. A chinese clone of a chinese clone (check the IMEI-number, you'll be surprised).

Instead I bought a HUAWEI E8372-w WiFi/WLAN LTE Modem, which works as a charm! Both nits are actually standalone USB routers, which take no more than +5V power through the USB bus.

BTW, the Huawei was also cheaper.
[FYT Android Head Units] KamaL:
Good to know. Where did you get it from? Any link?
[FYT Android Head Units] tbd@immigrantsong.de:
Amazon (Germany)
[FYT Android Head Units] Ejpi16:
Works great, thanks!
[FYT Android Head Units] SebbiSt:
Hello,

I own the JY-VL130N2.

Its really annoying to spend so much time inside my car while it is doing an update, refreshing maps, downloading offline playlists and so on...so I am searching for a way to keep it running without ignition (VW Golf VI) . Is connecting the red wire of the harness (the one which is normally disconnected) a good idea? Is the unit then always running?
[FYT Android Head Units] nk33:
This is why I aint done the update yet.

To be honest, the main reason I wanted the update was for the bluetooth… but using the blueballs.apk sorts this out for me anyway.

All my tunes are on usb so no need to download playlist.

Also the bluetooth tehering apk that is also in the OP works fantastic… I can finally break more into my 24gb monthly phone data!
[FYT Android Head Units] edit:
The easy way is to buy a second harness... take the unit out of the dash, bring it in, install it to your desk and connect it to a 12V power supply... Do all the updates, installs and configurations in the comfort of your home and high speed wi-fi. After everything is tested, put the unit back into the car and this is it... all done, with a little bit of work.
[FYT Android Head Units] artvoip:
Hi all! There is some good (for my opinion) new launcher named CarWebGuru. The author of this apk is always in touch. But, to implement steering wheel keys in build-in music in launcher, he need to know keys codes. I'm not Android developer, so, tried to describe what he need only. Please help here and I will post the codes to him. Thanks in advance :)
[FYT Android Head Units] SebbiSt:
thats a good idea too! How strong has the power supply to be? is 12V 3A okay?
[FYT Android Head Units] edit:
That should do it.
[FYT Android Head Units] surfer63:
That's OK as long as you don't use audio at high levels over big speakers. I had my unit for a month on a 2A power supply with only a front-left speaker connected.
[FYT Android Head Units] nyogtha:
Anybody have backup camera set up with this?

Had a go today, but can't seem to find the correct canbus setting for my Skoda Fabia. The setting I've used so far (vw compatible something something low) works great with everything else, including parking sensors, however it does not appear to recognize my camera and nothing happens when i go into reverse. If I switch canbus driver to xp, the camera will come on when i go reverse, but parking sensors will no longer work.

I also discovered (too late) that splicing into the reverse light power results in flickering image due to variable voltage, so need to find somewhere else to connect to. Meh.
[FYT Android Head Units] charnocc:
Can you provide the direct link?
[FYT Android Head Units] grumetecap:
Installed adb on my mac like here

https://xdaforums.com/showthread.php?t=2564453

Allow debugging of the USB but when I search for devices it does not find...i tried another usb cables without success. Now i will try this command:

> echo "0x04e8" >> ~/.android/adb_usb.ini

> adb kill-server

> adb devices

Changing the Vendor ID "0x04e8" to the correct value of our unit but....Which is the vendor ID of our units?
[FYT Android Head Units] nyogtha:
Ok so I figured this out. At least I think so. When I bought the unit I didn't have a camera so I cut the orange wire as per the instructions. After reconnecting it the camera switches correctly. I also moved the power fron the reverse light to the ACC connection to the head unit. There is still a very slight flickering, but a big improvement!
[FYT Android Head Units] alda.cerny:
on the Boy ka's Youtube site https://www.youtube.com/channel/UCFrkbO6PkJJOR7c3zWiloVA is info, that update from Android 5.1 to Android 6.0 will be available on 17th April 2017
[FYT Android Head Units] bogdi1988:
Hopefully they fixed some of the issues on this release such as the stupid stand by kill app
[FYT Android Head Units] rudix78:
Do you know if on rooted device we can install PCV startup builder that works excellent on RK3066 and RK3188 head units (it modifies install-recovery.sh)?

https://play.google.com/store/apps/details?id=com.pcv.installrecovery.builder

I would like to use it for early start of services and apps.
[FYT Android Head Units] artvoip:
He promised normal equalaizer in march 2017, means it was "released" 14 days ago. Did somebody see it?
[FYT Android Head Units] KamaL:
At least it's the first time they mention a specific date
[FYT Android Head Units] thedru13:
I thought you needed the amp they are selling to use that new feature but I could be mistaken.
[FYT Android Head Units] bogdi1988:
That was released in March - the equalizer comes with their junky F100 amp that only works on VW cars.
[FYT Android Head Units] artvoip:
ohhhh... so, they are cheaters.... didn't say nothing about it will work only (!) with their amp. Chinese are chinese in all things...
[FYT Android Head Units] italianceramic:
Android 6.0 will be released on 17 April.
[FYT Android Head Units] edit:
I guess all the mods have to be updated.. hope it is possible and all goes well.

Later edit : just out of curiosity, why do you want an Android 6.0 on the unit? Will it bring some major advantages over 5.0 or you are hoping for a better firmware overall?
[FYT Android Head Units] gustden:
Not sure if we will gain anything. My unit is working perfect / rock solid stable. It hasn't even been rebooted for weeks :) Wish I could say the same for my phone running Nougat!

I'm always very hesitant to upgrade a device that is working perfectly. Many times newer != better.
[FYT Android Head Units] derschnelle:
Improved security?
[FYT Android Head Units] edit:
No, from what i have read on these forms the security on these units is extremely low no matter the firmware. Most are easy to root (like entering a code for instance) and since the updates aren't that frequent and stop as soon as the manufacturer decides that the unit is stable, I'll say it's pretty vulnerable in the long run because major and critical bugs are found often.

I try to avoid browsing on the unit because often zero day exploits don't need user interaction to deploy the payload... I just stick to the basics, navigation, music, online radio and podcasts.

---------- Post added at 05:58 PM ---------- Previous post was at 05:38 PM ----------

Just received my unit but unfortunately i don't have time to dive in till Monday. Hope i will be able to follow all the moddings without asking questions. Once I'll have an stable working unit I'll put it in the dash and enjoy it... it's all i want to be honest. Android 6.0 will definitely need some time to get stable on this unit, i doubt that they will get it right from the first firmware that they will release.

Like with current unit that i own... Took me a while to iron out all the bugs but unfortunately i still have one that drives me nuts... Volume knob stops working after a while when i am using Waze. The problem is that a few months after i bought the buzz was gone on the forum and i could not get a new firmware that would solve my problem.

Hope I'll have a better luck with this one :)
[FYT Android Head Units] rnabi99:
I spent a couple hours trying to get this to work, but I could never get the addprop.sh script to run, it kept erroring out saying "sed: not found". Did anyone else have this issue?

Below is the output from the batch file.

...\ViPER4Joying2GB>install.bat 192.168.43.99

...\ViPER4Joying2GB>adb kill-server

...\ViPER4Joying2GB>adb connect 192.168.43.99
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.43.99:5555

...\ViPER4Joying2GB>adb root
adbd is already running as root

...\ViPER4Joying2GB>adb shell "mount -o remount,rw /system"

...\ViPER4Joying2GB>adb shell "mount -o remount,rw /"

...\ViPER4Joying2GB>adb shell "mkdir /tmp"
mkdir failed for /tmp, File exists

...\ViPER4Joying2GB>adb shell "mkdir /tmp/viper"
mkdir failed for /tmp/viper, File exists

...\ViPER4Joying2GB>adb push addprop.sh /tmp/viper/
1 KB/s (1173 bytes in 1.000s)

...\ViPER4Joying2GB>adb push system /tmp/viper/
push: system/etc/audio_effects.conf -> /tmp/viper/etc/audio_effects.conf
push: system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk -> /tmp/viper/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk
2 files pushed. 0 files skipped.
437 KB/s (3787102 bytes in 8.452s)

...\ViPER4Joying2GB>adb shell "chmod 0755 /tmp/viper/addprop.sh"

...\ViPER4Joying2GB>adb shell "cp /system/build.prop /system/build.prop.viper"

...\ViPER4Joying2GB>adb shell "cd /tmp/viper/ && sh addprop.sh"
addprop.sh[25]: sed: not found

...\ViPER4Joying2GB>adb shell "mkdir /system/priv-app/ViPER4Android_FX_v2505"
mkdir failed for /system/priv-app/ViPER4Android_FX_v2505, File exists

...\ViPER4Joying2GB>adb shell "chmod 0755 /system/priv-app/ViPER4Android_FX_v2505"

...\ViPER4Joying2GB>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

...\ViPER4Joying2GB>adb shell "chmod 0644 /system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk"
Unable to chmod /system/priv-app/ViPER4Android_FX_v2505/ViPER4Android_FX_v2505_A4.x-A7.x.apk: No such file or directory

...\ViPER4Joying2GB>adb shell "mv /system/etc/audio_effects.conf /system/etc/audio_effects.conf.viper"
mv: rename /system/etc/audio_effects.conf to /system/etc/audio_effects.conf.viper: No such file or directory

...\ViPER4Joying2GB>adb shell "cp /tmp/viper/system/etc/audio_effects.conf /system/etc"
cp: /tmp/viper/system/etc/audio_effects.conf: No such file or directory

...\ViPER4Joying2GB>adb shell "chmod 0644 /system/etc/audio_effects.conf"
Unable to chmod /system/etc/audio_effects.conf: No such file or directory

...\ViPER4Joying2GB>adb shell "rm -rf /tmp/viper"

...\ViPER4Joying2GB>echo Reboot your Head Unit NOW!
Reboot your Head Unit NOW!
[FYT Android Head Units] bogdi1988:
I tried Viper4Android a while ago on mine and I got tired of it quickly. Honestly not worth the hassle as the audio improvement is minimal...
[FYT Android Head Units] AssassinsLament:
Update/Install busybox
[FYT Android Head Units] surfer63:
[MENTION=505234]mabi[/MENTION]99: See my signature for a script to update your busybox.

[MENTION=503463]AssassinsLament[/MENTION]: better alter your mkdir statements to "mkdir -p" statements. The "-p" does not give an error when the folder already existst.