yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
I'm currently working on an apk that does the installation of quite some mods from within the apk from the head unit itself: no adb necessary anymore apart from the first rooting.

The prerequisite for this apk therefore, is that the unit needs to be completely rooted with SuperSU (or another one).

The apk downloads the necessary modded apks + additional files, and then installs them.

Currently very, very alpha.

The reason I'm already "presenting" it with a couple of screenshots is because I want to know if "people" are interested. (I'm quite capable myself to handle everything with adb from the command line :cool:. This is just some playing but I won't continue if nobody's interested).

"2017-04-29_screen01.jpg" is the main screen.

"2017-04-29_screen02.jpg" is a standard disclaimer you get upon startup. (It means: whatever happens, it is always your fault :) )

"2017-04-29_screen03-RadioMods.jpg" is what you see if you select Radio Mods option from the main screen.

"2017-04-29_screen04-Viper4Android.jpg" shows the screen if you select Viper4Android (the app is loaded with text screens as these are not standard actions).

2017-04-29_screen05-viper4android.jpg" shows the download progress.

"notrooted.jpg" is what happens on startup if your unit is not rooted yet; when click OK to get back in the main screen you see the same gray disabled buttons as in the "nojoying.jpg")

"nojoying.jpg" shows you what happens on startup if your run it on a non intel sofia 3GR unit (my phone in this case)

Edit: If you select "No way!" in the disclaimer screen, you also only get the two options active in the main screen.

Edit2: I try to give everyone the credits he/she deserves.
[FYT Android Head Units] rhino6303:
I think that would be pretty cool. It might alleviate some of the repeated questions as well.
[FYT Android Head Units] Skinzaholic:
Sounds great to me. I'm interested
[FYT Android Head Units] Rottgrub:
I'm not usually a big "unified tool" guy when it comes to phones and tablets, since those are easy enough to configure from the comfort of your desk, or couch, whatever. With the car head-unit though, anything that simplifies setup is welcome. Last thing I need is more time sitting in my car with my laptop, not actually going anywhere. =)

Thanks for the tool!
[FYT Android Head Units] AssassinsLament:
I think it only loads after the boot process is fully finished, which is maybe two or so minutes after the screen appears. (this is after a full reboot) Just wait for a couple of minutes and check if it's on.

On a wake up and not reboot, the issue could be that viper4android is being killed by the system.
[FYT Android Head Units] naplesbill:
That tool would be awesome in this case. Especially since you have to redo them all every time you upgrade the software.
[FYT Android Head Units] merit40:
It also happens to me:(
[FYT Android Head Units] edit:
That App that you are working on is pure gold for lots of users (me included although I learned some things because I had to) that don't handle programming, scripting and other low level android stuff !

I appreciate your work. When I joined this the club and bought the Joying Sofia I had to learn some things in order to be able to modify it. I learned some things quickly but Some things were pretty complicated.... I still struggle to modify my keys and apps script...

In the name of the all the actual and future users that will use it (and will not use the thank you button) THANK YOU VERY MUCH !
[FYT Android Head Units] bogdi1988:
Nicely done! Definitely interested!
[FYT Android Head Units] budwha:
I would be very interested also........would this work for all Joying ROM's or just for March 14th version?
[FYT Android Head Units] wanahave:
Thanks for this great mod! I didn't like the stock radio app of Joying. But the blue-white fits much better in my Lancia Delta.

Personally I would love to see that the frequency font size would be even smaller (as big as the FM-1 and MHz) and the RDS radio station name bigger. Don't know if this is possible.

Regards,

Wanahave
[FYT Android Head Units] sanangel:
That's a great job.

If you want to translate to Spanish language, I can help you.
[FYT Android Head Units] surfer63:
It is too early to say that.

ROM and android version independent: installing busybox, do the upgrade of the installed SuperSU and its libraries, install the radiomods, setting DPI, deactivating apks, enabling/disabling adb over tcpip.

ROM version dependent (to some extent): SofiaServer mods

Android version dependent: Google settings vs. Joying settings, viper4android.

I already builtin android version "recognition", but I don't use it yet.

Currently installing busybox, radio mods and viper4android works. Rooting has a small error but I haven't found it yet. Enabling adb over tcpip works (necessary for current 6.0 ROM), but I want it to be an ON/OFF function: Switch it off for security reasons, switch it on when you want to use it(*), which should be hardly ever if this apk will work OK.

I'm still building, but I wanted to know if people were interested.

It seems you all (at least the ones who responded) are interested.

Now I will continue with this project, but I will not release anything yet.

*: Note that adb over tcpip is actually a terrible security hole! You only need the ip-address to connect and get full root control over your device. I actually wonder whether this is is a bug by Joying in the current 6.0 ROM, or a carefully decided design change to improve the security of the units.

---------- Post added at 09:29 PM ---------- Previous post was at 09:24 PM ----------

Thanks, but way too early :D

I first need to make it a fully working version.

---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------

That's very easy to do, but I'm currently working on other things.
[FYT Android Head Units] wanahave:
I'm definitely interested! Was involved in modding HTC firmware in the past, so I like things you're doing.:D

---------- Post added at 09:42 PM ---------- Previous post was at 09:32 PM ----------

LoL. Sure it was not a request, although it would be nice someday.

Maybe I can do it myself if I know which file within the apk I need to adjust. I've been a themer a few years ago (BinDroid) so I know how to unpack and repack.
[FYT Android Head Units] joshnat:
[MENTION=2550900]surfer63[/MENTION] an all-in-one apk would be a huge service to the community here. I don't mind working over adb but it would make things so much easier to do them right on the HU.
[FYT Android Head Units] psxsnake:
[MENTION=2550900]surfer63[/MENTION] I'm on your train too... really interested on this .... really thanks
[FYT Android Head Units] ferni:
Ok so good to know it's not just me.

[MENTION=503463]AssassinsLament[/MENTION] This is after a wake up, not a reboot. And i'm running [MENTION=3076686]gustden[/MENTION] NoKill mod so don't understand why it would be getting killed?

Any ideas?
[FYT Android Head Units] AssassinsLament:
Sorry, I'm not too sure as I haven't payed too much attention to viper4android yet, but I'll test it out when I have time. How did you install viper? I think android also kills apps sometimes too, so it's best to install viper into /system/priv-app, which my zip file does (if you used it to install).
[FYT Android Head Units] ferni:
I used your script to install it :)

I'll have to check to see where it has installed it because i've had trouble using some of these batch file installs, and ended up ssh in and manually doing most of the steps
[FYT Android Head Units] surfer63:
Android 6 (and 7) use "Doze" and "App standby". These will also "kill" apps. I'm not yet on 6 on my head unit, so this is theory based on my phone.

You might check Settings -> Battery; Use the "3 dots" top right. Select "Battery optimization".

You might set Viper4Android to "Don't optimize".

Maybe that helps.
[FYT Android Head Units] ferni:
I'm still on 5.1.1 but i'll check for this in 5.11 thanks
[FYT Android Head Units] edit:
BIG problem on the old Android 5 firmware.

Normally the unit goes to sleep after 50 seconds from the moment you turned off the car (red wire disconnected) and in sleep mode it drains very little battery 0.012 A (as I've shown in another post).

The problem is that from the moment you use Waze (i'll explain later how to replicate the issue) something happens that the unit does not enter sleep after 1 min but instead it stays awake for 5 minutes draining between 0.40-0.60 A Somehow the unit has a fail safe and after a 5min the unit does something to force sleep.

Another problem is once this issue occurs even if you restart the unit or let it go to sleep several times it does not recover (get's back to it's default ways of 1 min sleep). I've tried several times last night. After 2 restarts and 4 "drives" the unit did not return to it's normal way of sleeping. If the failsafe does not put your unit into sleep mode after those 5 minutes you are definitely not gonna start your car in the morning.

How to replicate the issue :

The easiest way I've found was to use the default Sofia-1-C9-Server-V1.0.apk start a music player and Waze... then turn off the car... and in first 30 seconds start the car again for 10 seconds.... then turn it off..... wait 20 seconds... start it again. So if you interrupt the sleep timer and Waze is active (even without any route set in) the issue shows up. This worked for me each time. In real life it translates to this : if I drive, Waze working and music is playing and for some reason my car engine stops and I start it immediately and drive away after a few seconds.... BAM... the issue starts.

I've tried with the Sofia-1-C9-Server-V1.0.apk from the V4 (NO KILL) and it behaves the same

If someone could help me identify the problem it would be great.

Later edit : I managed to get the unit stuck using the Igo app included with the unit... Started the unit, plotted a course, opted for the HU to simulate the navigation, while the Igo simulated the driving I turned off the car... then after 10 seconds started the car again.... let the Igo popped up still running it's simulation... then turned the car off again..... and that was it... it got stuck and was draining between 0.55 and 0.68 A for 4 minutes and 50 seconds.

Tried the same with Google Maps but Google Maps works ok. I could not get the unit stuck using it.
[FYT Android Head Units] ohhdangnickson:
Guys I need help adb root via wifi failed this is my first Android head unit I have the JY-UL135N2 2gb ram 32gb rom can anyone help it came with the February 22nd update installed when I got it
[FYT Android Head Units] nexxusty:
I cannot tell if you are trolling or not?

If not... you have to be kidding.... 0.55/0.68mAh is nothing.

Example. Millions of people charge their phones in their car when it is off and the battery in the car is fine.

Nothing to worry about whatsoever.
[FYT Android Head Units] AssassinsLament:
I've tested some and it's been working fine for me, although I am on the latest android 6.0.1, I tried gustden's updated NoKill mod plus I tried the regular Sophia Server apk with viper4android and PowerAmp listed inside the unkill_app.txt. When I didn't list those apps in the unkill_app.txt, I had to manually restart PowerAmp and Viper4Android.
[FYT Android Head Units] CamryGuy:
Brilliant! Yes Please!

---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------

They are bragging that Tom Tom Go works on the 6.0 update on their fb page. Can anyone confirm? Thank you.
[FYT Android Head Units] edit:
Later edit: My units were off but you did not notice that someone else did so I got back and corrected all my posts. And no, I am not trolling.

I meant 0.55-0.68 A and NOT 0.55-0.68 mAh. Sorry

I just wanted to raise awareness of a potential problem because there are many more reading then writing or participating to threads.

Have a look at the bigger picture... yeah, probably 0.55-0.68 A feels like it's nothing but in a car is a BIG problem because that drain cannot be controlled by the car computers and leads to dead battery FAST. Let me explain. You see, there are several aspect to consider. When you charge your phone, that output is controlled by most modern car computers so if the car is off and you leave your phone to charge at some point (depending on the car) the car cigarette lighter socket it's cut off from the battery power to protect the battery... My Ford leaves it on for 15 minutes after I turn off the car and there is no door activity. The Headunit on the other hand it's not power managed by the car because usually have build in power management and communicate through CAN with the rest of the car. In all of todays modern cars you cannot leave your headunit turned on for longs periods of time at some points it will be cut of or you will be asked to turn on the engine. This Chinese HU does not communicate though CAN and although they do have some sort of power management it does not inspire me confidence when a simple GPS application messes it.

Yes, 0.55-0.68A is a lot and if for some reason the Chinese unit power management fail safe fails and the unit will draw continuously that amount of power it will kill your car battery in 4-7 days (depending on the battery age and power)... while you are of course in a nice holiday with your family :)

If you don't see the reasoning in what I have written and you feel again for some bizarre reason that I am trolling then please don't bother to reply.
[FYT Android Head Units] AssassinsLament:
It is... but the funny thing is that the solution for it was posted here by one of the many bright users. And it was brought up to their attention and yeah... "they fixed it"

:laugh:
[FYT Android Head Units] gtxaspec:
[MENTION=309187]edit[/MENTION], if you look at the logcat's, no matter what about 15 minutes in the unit goes to sleep. I always thought that was the cutoff. Actually I wish someone would modify the server APK to disable sleep, I have extra battery to power the unit so I wish I could keep it on 24/7 and use it as a DVR as well as other stuff. 2006 Audi a4.
[FYT Android Head Units] edit:
Interesting idea but if the unit will DRV it will drain a lot more then 0.55-0.68 A... probably 1 Ah or even more... tricky if you don't use your car daily for quite a number or miles/km (to give it time to recharge).

I drive very few km per day and I leave it frequently in the parking lot over the weekend and even more sometimes.

Sorry but I don't have the skills needed to check logcat's.... if you a nice enough to give me a hand and point to some info that would be great. I am curious what happens in those 5 minutes after you turn off the unit (key off) after you have used Waze/iGO.

Maybe it's by design, God knows.
[FYT Android Head Units] psxsnake:
Confirmed [emoji6]
[FYT Android Head Units] sweetnothings:
Please keep discussion in a friendly and kind way!

Assume a small car battery has 40Ah, because of age and you will need power to start the car after, lets say we can consume at min. 10Ah.

lets further say the unit drains 1 instead of 0.68mA

10Ah are 10'000 mAh so 10'000 mAh / 1mA = 10'000 h = 416 days so that would be over 1 year

i would wish i would be able to have holidays for about 1 year :)

Always be carefull on using physical units...
[FYT Android Head Units] CadillacMike:
The notification for Spotify are fixed in the 6.0 update:

[IMG="Spotify notification"]http://uploads.tapatalk-cdn.com/20170501/b608e4b076c0c19bcbe08b0f65f3cca3.jpg[/IMG]
[FYT Android Head Units] brian8179:
I just updated my Verizon Galaxy S6 to 7.0 nougat, and my head unit no longer auto tethers to My phone. I was using the BluetoothTeathering.apk pinned to the beginning of this thread. Has anyone else had this issue or does anyone have any ideas?
[FYT Android Head Units] rnabi99:
I know this is not the same, but I have a T-mobile Galaxy Note 4 and I could never get the BluetoothTethering.apk app to work for me. I had to use pdanet bluetooth tethering, so worst case you could try that. The downsides are that it is a paid app, and it does not run automatically without some hacking via Tasker and AutoInput.
[FYT Android Head Units] edit:
And you read my last 100 posts and you felt that you had to say this, oh man.... this is sad. I'll put you on my ignore list for safe keeping.

Because what he wrote makes no sense to me, this is my math :

Scenario 1 : new battery fully charged 75A, unit drains 0.012 A (off, deep sleep), how long the battery can last ? ( Ideal scenario, assuming that there is nothing else draining the battery like a car alarm, car computers)

(0.012 A x 24 h) x 30 days = 8.64A x 7 months = 60.48 A - at this point i doubt that your car will start.

My conclusion is a 0.012 A drain is great unless you want to abandon your car for 7 months :)

Scenario 2 : Let's say the unit gets stuck, it does not go into sleep mode at all and draws 0.60 A (let's make the unit round)... and the car is in the garage for 5 days... and your car battery is old and can hold only 60A

(0.60 A x24 h) x 5 days = 72A drained by the unit in 5 days...... and your car battery is only 60A... - Good luck starting your car!

My conclusion is : I hope the unit goes to sleep or else you will be in for a surprise on your first 5 days Holiday :)

This evening I discovered another anomaly with the unit power draw:

I used a Bluetooth Tethering and XiiaLive Pro app to steam an internet radio station. I turned off the unit and watched the battery draining and I was surprised to see an 0.03-0.04 A drain... when I expected 0.01 A.

Made a lot of tests, closing a lot of apps to find out where the drain comes from and it turns out that if you press PAUSE on the XiiaLive app instead of STOP it leaves the unit in a certain state that makes the HU draw more power when it's in sleep mode.

I waited for 45 minutes and it was still fluctuating between 0.03 and 0.04 A.
[FYT Android Head Units] PsychoMcSatan:
I think your units are off.

When you say the radio draws 0.60 mAh, I think you probably mean mA which is current (rate of electrical flow). However, 0.60mA is extremely tiny and I don't think multimeters would even display such minute measurements, so I think maybe you mean 60mA. There will always be some drain on car batteries, and google seems to indicate that you generally want to keep it under 50mA total. Therefore, if you are indeed reading 60mA, then yes, it is in the range of being a concern. It would likely take a month or so to completely drain a full car battery, but other drains plus short infrequent drives could leave you undercharged.

I am a bit concerned if improperly closing apps could be creating a draw of 60mA in my car. Are you able to confirm the measurements, paying close attention to units?

That other case of 0.03mAh is probably fine, if it is actually 3mA. That's completely acceptable for a radio in standby.
[FYT Android Head Units] gtxaspec:
I have left my joining Android unit in my Audi in sleep mode for over 2 weeks while I was on vacation and when I came back the unit and the car started just fine keep in mind I also left my 4.2 amp USB charger plugged in and on my car so I'll let stay on 24/7 and all was well
[FYT Android Head Units] edit:
Yes, my units were off. I meant 0.60 A. I will go back and correct all the mistakes.

You are the only one that caught that... the rest decided to call me a troll

Thank you!
[FYT Android Head Units] akuma148:
I finally got it to work. It turns out ES File Explorer is the problem. Using it to either transfer files or fix permissions, causes it to not work right. I switched over to Root Explorer and that got it working right. Thanks for the help.
[FYT Android Head Units] CamryGuy:
Well its not working for me unfortunately. Still unable to connect. Im on 6.0.1
[FYT Android Head Units] psxsnake:
please dont do cross posting...

If you are on Sofia Joiyng, it work
[FYT Android Head Units] edit:
Later edit :

I do apologize for the mistakes made... I meant A but wrote mAh ...

I am not working on a daily bases with these and they got somehow mixed in my brain and came out wrong

I got back and modified all my posts, the numbers were correct I only labeled them mAh instead of A.

So the numbers are :

(All the numbers were tested on the Android 5.0.1 28 Mar 2017 Firmware)

1. Booting/rebooting (with all the apps installed) : 0.7 - 1.05 A

2. Idling after boot : 0.60-0.80 A

3. Sleeping : 0.012 A

3. Normal shutdown (takes 50 seconds to go to sleep after the engine is off) : 50 seconds of 0.55 and 0.70A drain after those 50 seconds it sleeps at 0.012 A

4. Waze/Igo shutdown : from the engine off it takes 5 minutes to get to sleep and during that time the drain is fluctuating between 0.55 and 0.70A. After those 5 minutes the drain get to an decent 0.012A

The thing that worried me is that if the unit for some reason fails to get to sleep after those 5 minutes it could be a problem.

5. XiiaLive Pro app issue. If it's not stopped and only paused makes the unit drain 0.03-0.04A (while sleeping) instead of the usual 0.012 A. Yes, it's not a big deal but it's almost 4 times more drain just from a little app.
[FYT Android Head Units] charnocc:
Thanks for coming back to facts about the current draw :)

One other observation: I activated sleep. When I leave the car for a long time (Over a week?) the unit is not in sleep mode anymore, but will restart. I have read somewhere that the unit will shutdown after about a week of sleep time to minimize current draw.
[FYT Android Head Units] ferni:
Where is the unkill_app.txt ? I haven't added anything to it so that sounds like why i'm having the issue?
[FYT Android Head Units] AssassinsLament:
If you have gustden's mod installed, then unkill_app.txt isn't necessary. If you don't have gustden's mod installed, then any app that isn't listed in unkill_app.txt is killed at sleep. To edit the unkill_app.txt, you need to decompile the Sofia-1-C9-Server-V1.0.apk file and find it in the assets/property folder. After editing and saving the file, you must recompile it again and replace the old Sofia-1-C9-Server-V1.0.apk
[FYT Android Head Units] dayanandgp:
Did your try car launcher? I really liked it except part where we cannot add our own widgets ?
[FYT Android Head Units] thedru13:
This is why I like nova launcher. Can not only add widgets but with kwlp I can create my own.

Spotify widget i created.
[FYT Android Head Units] breevesdc:
Thanks for your suggestion. I tried doing a factory reset and it did not resolve the issue. The head unit still reboots every several minutes and many of the apps are non-functional (you tap them and nothing happens) including PowerAmp and even some of the stock apps. When you tap the radio, it launches the app but with no sound. And when you attempt to change the channel from the default 87.5 frequency to something else, the channel changes to "0" and nothing happens. Also, the "power off" and "standby" buttons in the drag down menu do not work anymore. I'm feeling like this is a hardware problem as has been suggested. And I've asked Joying for a warranty replacement. Only 2 weeks old. :(

Thanks for your reply gustden.
[FYT Android Head Units] CadillacMike:
i never cared for Car Launcher
[FYT Android Head Units] KlaverBoer:
So this is the reason why my UI3 crashes every time. I also installed the Google App. This problem was already in the 4 jan version.

---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------

I had the same issue with my Skoda Octavia. I also have parking sensors in the back and front. I had this issue when i used the XP Low canbus protocol. When i changed to the XP protocol it fixes the issue for my car. When i now turn on the sensors, by putting the car in reverse or pressing the button, the graphical screen stays on as long as the parkingsensors are activated.

Maybe it will also fix your issue.

I also have an other problem with my parkingsensors. The one at the back are working fine just like the left and middle one at the front. But the right sensor at the front will only display something when the right back sensor is activated. I already received a new canbus adapter from Joying but the problem is still there.