yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] level5music:
Also feeling the pain on the lack of live wallpapers. I use a full-screen setup with KLWP that has a clock, weather, media transport controls, wi-fi connection info and other goodies that I custom made and love for these head units. It's really my only disappointment with the ROM. I tried the command listed in the beginning of the thread, but it barks about read-only file system. So I mounted /system -rw and while the command did not fail, it also did not work. I tried moving the LiveWallpaper and LiveWallpaperPicker APKs by hand to /system/app and changing the permission but that also didn't work. I also tried installing them regularly and making them system apps via Titanium Backup, that also did not work. If I have LWs, this ROM would be perfect.
[FYT Android Head Units] surfer63:
I do not exactly get the "live wallpapers not working".

I went back to my old Sofia and installed the gtx v9a3 ROM.

I did the

su
mount -o remount,rw /system
cp -R /system/vendor/oem/LiveWall* /system/app

But then you have an "empty" system without live wall papers, only the apks who show the livewallpapers. At that moment you need to install the livewallpapers.

So I took the

/system/app/Galaxy4
/system/app/HoloSpiralWallpaper
/system/app/NoiseField
/system/app/PhaseBeam

out of the original Sofia ROM firmware zip and copied them onto the Sofia on the same location.

Reboot. And then I had 4 live wallpapers (and if you want more you can install them from the Play Store, like the sea fish or the aquarium, etc. etc.)

Then I took the "3Ddongtai_V1.8.apk" out of the oem folder of the original Sofia firmware oem folder and copied it onto my unit, and simply double-clicked it from the file manager to install, and I had those 3D livewallpapers working as well (with the moving birds nest and the falling leaves and those other useless animations :)).

If necessary I can deliver a compressed archive with a set of commands, but you can try yourself as well.
[FYT Android Head Units] level5music:
Turns out I WAS able to get the live wallpapers working. Here's what I did.

- Grab a copy of the stock ROM

- Pull the folders for /LiveWallpapers and /LiveWallpaperPicker (or similar, I may not have the names right). There are two versions in the stock ROM, one under a "20" subfolder and one under a "60" subfolder. They may be the same, but I'm not sure. If one doesn't work, use the other one; I can't remember which one I used.

- Copy these to /system/app

- I changed these at the folder level to CHMOD 777, using Solid Explorer but any file explorer app that can access Root should be fine. I can't imagine that you couldn't get away with 755 instead but I figure that given the closed environment of a car and the low reach of my hotspot, this risk is low or at least acceptable. I'll have to try 755 but I doubt it realistically makes a difference for my use case.

- Fully reboot

- Change to Live Wallpapers as usual

Totally worked for me in Nova Prime. As I stated in my previous post, I run a full dash screen with a large clock, weather/location, SSID/data traffic, music transport and hotlinks to apps within that I custom created using KLWP. Now that everything is working, I'll have to make a TWRP backup that way I can always restore back to perfection should something **** the bed for whatever reason.

I need to give some very large kudos to [MENTION=520205]gtxaspec[/MENTION] and his hard work here. The ROM is wonderful and honestly makes the hardware feel like a totally new head unit with the increase in speed and versatility with root apps and Xposed. I had planned to replace this unit due to the poor performance but it's been wholly re-vitalized thanks to your hard work. My only complaints now lay in the hardware (doesn't fit into the standard ISO mounting bracket for my 08 Nissan 350Z, and my NAVI button is stuck in but does still register a harder press); but as it stands I'll likely keep this one installed until I get a new car. Thanks again!
[FYT Android Head Units] kaluna00:
You are the man. Thank you very much! I took those folders out of the 60 folder. Pasted them into \system\app folder.. change the permissions. (you have to do for all child folders too)... And voila! You da man!
[FYT Android Head Units] PsychoMcSatan:
So did the same, but kept getting the "Stopped working" message. So I reinstalled the ROM. Saw that I was rooted already so copied the folders, changed permissions switched to Nova Launcher and rebooted. Installed a couple Live Wallpapers, but getting "App is not installed".

I switched to Google Now launcher, but still same problem. Froze the default Launchers with Titanium Backup, still same problem. Then I manually installed Live Wallpapers and Live Wallpaper Picker APKs (from the system/app/ folders) and no longer get "App is not installed", but get either "Stopped working message" or throws me back to desktop. Now even trying to go to System Reset under Settings gives me "Setting Stopped Working".

So what launcher you running, and how do you switch to it? do you just install (Nova or whatever), or choose under car settings, or do you freeze the default launchers? Too many ways to do things!!!!
[FYT Android Head Units] kaluna00:
su

mount -o remount,rw /system

cp -R /system/vendor/oem/LiveWall* /system/app

Have to run these commands through terminal emulator as well. Then copy and paste the live wallpaper and live wallpaper picker folders from the stock ROM into the systems app folder in the root directory. Change the permissions and make it recursive so it automatically changes child folders and objects. Reboot.. I am using Nova.
[FYT Android Head Units] lexuz:
Hello again.. I'm back with more questions.

My Intel Sofia unit screen is black and the lights don't go on. Android starts and USB gets power. I got a new screen from joying but it's still not working. Any ideas? I know it starts because I got static when changing (with the src button) to radio and my phone tries to connect to the radio via Bluetooth. On the Intel board I see lights flashing red repeatedly.
[FYT Android Head Units] surfer63:
The flat cable not correctly connected or damaged?
[FYT Android Head Units] lexuz:
tried with both screens (old and new) didn't worked. Only if it is the connection to the motherboard itself. Because I used 2 screens and 2 flex cables. I didn't noticed anything wrong with the motherboard I even took the Intel board itself to see the pins and all looked OK AFAIK.. But then again I only use a bit of logic thinking because I really don't know much about this. ?
[FYT Android Head Units] D4rk_Seraph:
Hello, I have a Winca S170 head unit with Sofia 3gr and 1gb RAM, this ROM is compatible with my HU?
[FYT Android Head Units] surfer63:
No, it is not. The hardware/MCU is ST based, it is not a FYT based unit.
[FYT Android Head Units] jcousindesign:
Is there anyway to have the phone app minimized during a call? I hate that when you're in a call, the Bluetooth phone app can't be minimized
[FYT Android Head Units] surfer63:
The app stays on the foreground. "Minimized" is a desktop functionality :)

Use the XFytTweaker or XSofiaTweaker xposed module to enable to put the app in background during the talk.

Or

Use Balloo BT mod which will shrink to a bar at the bottom of the screen during the talk

Or

(when navigating) Use a nav app which will/can take over the phone call and also displays it as a bar below the Nav app/screen and thereby not blocking your navigation.
[FYT Android Head Units] Sevennl:
hello,

I love that we have custom roms for our car units, specially to remove the bloatware that come with them.

Now for my question/request :

Is it possible to add an AROMA script to the installer to be able to remove even more stuff people don't need, as for me i would get rid of the youtube app for example.

And how does the UI look like, i've watched the video from the Q/A link but that is just 80% of filming a black screen.

I like to know how the setting screen is like, main menu and apps layout.
[FYT Android Head Units] surfer63:
The gtx-rom is no longer under development and we have seen gtx not here for a very long time (hope he is doing well).

If you want to modify something you really have to do it yourself, or do something like via adb

adb kill-server
adb connect <ip-address>
adb root
adb connect <ip-address>
adb shell mount -o remount,rw /system
adb shell rm -rf /system/app/youtube*
adb shell rm -rf /system/app/Youtube*

The last 2 lines because I have no idea whether Youtube is with upper-case or not and it matters on linux.

(my Sofia is on the bench and currently running a rooted stock rom)
[FYT Android Head Units] amon101x:
I only use google maps. And when Maps is giving directions it always lowered the radio sound. ;)

Tom Tom Go also worked in lowering the Radio volume. Dont know about waze though.
[FYT Android Head Units] surfer63:
Google Maps does this and iGo does this as these are the only 2 nav apps in the (original) navi_app.txt in the sofiaserver.apk.

TomtomGo can only do this if you have a nokill or customkeymod sofiaserver. Have you?

(same for waze)
[FYT Android Head Units] amon101x:
I went to Montenegro last summer driving from germany. I used Tomtom Go all the time because of the offline maps. I havent used a custom sofiaserver and still it lowered the radio volume afaik. Maybe because i set it as default Navi app.

But if you say that cant be possible without the updated naxi txt file from you. I may remember it wrong :D
[FYT Android Head Units] surfer63:
Sorry, you are right. The default navi app also shows this functionality.
[FYT Android Head Units] gtxaspec:
Confirmed bug, LED lights stay on all the time, though the unit does detect headlight signal as the brightness does change with the headlights. Can anyone confirm this works in the stock January ROM? I guess I never noticed the lights don't then off.
[FYT Android Head Units] joshnat:
[MENTION=520205]gtxaspec[/MENTION] any idea what happened to the canbus update files in the custom rom?
[FYT Android Head Units] gtxaspec:
McuUpdateAll.bin is normally copied by the stock recovery to /sdcard. I have added this routine in first-boot.sh for the next release of the ROM. You may copy this file manually from the stock January release, place it in /sdcard and this fixes canbus selection.
[FYT Android Head Units] hidroela:
oh i was force to do a fresh install.

flash January joying firmware

root unit using surfer63 method

install gtxaspec custom apk.

flash custom recovery

flash gtxaspec custom rom

install joying DVR apk

reboot head unit.

not luck it is not communicating with the camera.

what i am doing wrong.:confused:

note:every thing else if working just fine.:good:

also i go it working before i re flashed the unit.:crying:
[FYT Android Head Units] edit:
I installed Viper4Android 2.5.0.5 and with this settings it still does not work... popps and crackles and sound considerable slowing down in speed

Music player used XiiaLive Pro

The settings used :

Lock effect mode - Headset

Spectrum extension - ON - Strenght set to 0.50

FIREqualizer - ON - Set it on Classical

ViPER Bass - ON - 100HZ - +10dB

ViPER Clarity - ON - 3.5 dB

If you have any ideas please share.

Thank you !
[FYT Android Head Units] gtxaspec:
Ok, my next experiment is to try a different kernel, of all the 6.0 releases, do you remember which one was the best with viper?
[FYT Android Head Units] edit:
I wrote just so people would know what to expect....

The last firmware that really worked with Viper4Android was the one from 25 May BUT for 100% functionality you I HAD TO push the min clock to 600Mhz .... at least... in some cases (more modules enabled) I had to push it to 728Mhz.

As I remember that old firmware had issues with BT... lots of it... so just test to see what is changed from that firmware to the new one on the audio part if you can... if not.... I am fine with the December firmware that I found to be the most stable and finally free of BT issues.

The December firmware works fine if you have active cooling and enable only these 2 on Viper of course pushing the min clock to 600Mhz :

ViPER Bass - ON - 100HZ - +10dB

ViPER Clarity - ON - 3.5 dB

Anything more and you need to push the min clock a lot higher.... and for the units that don't have active cooling .... is just asking for trouble.
[FYT Android Head Units] gtxaspec:
Ok, that make sense, as my min clock is locked at 1040 (I have a 120mm fan) so when I test my results are diff from yours.

I'll extract the boot.img from the may release and try that.
[FYT Android Head Units] edit:
Yes, if you have your clocks locked at max speed, in your case 1040 almost all modules from Viper4Android will work EXCEPT on these scenarios :

1. if there is another app that needs a lot of cpu power like for instance Waze then you will start to hear popping and sound/music stuttering in the speakers

2. if your cooling is not the best your unit will heat up and you only need the unit to reach 60C and the clock will throttle to 900 and at that speed the sound issues will arise

Even if I have a pretty good cooling due to my dashboard layout on long trips with music steaming, Viper processing and Waze for navigating the headunit temperature reaches 52-60C and starts to throttle and that leads to sound issues.

What puzzles me is that I used my old unit (an dual core, RK3066 at 1.4 Ghz with 1Gb ram) just fine with the same apps (although older versions of course) and the Viper never had an issue and the clocks usually were always running at 600-800 Mhz... and I did not had any active cooling or any kind of additional radiator on the CPU... and this headunit with double the cores, ram and active cooling can hardly handle the same usage scenario.... this shows once again how badly the coding is on these units....

Thank you for looking into it... I hope you can find something !
[FYT Android Head Units] thingonaspring:
First - thanks to gtx and lbdroid for the work that went into this rom. I used to make roms for the old moto droid series phones, so I know first-hand how much work goes into this - it is appreciated.

Apologies if this is already covered elsewhere, but I have 2 questions.

1 - flashed v5test and the side-panel power/vol/navi/home buttons no longer work - they respond fine in the "button study" setting panel, but the system doesn't actually do anything when they're pressed. I have to use the onscreen home/back/volume controls instead.

2 - my bmw E87 has no true constant 12v and no ACC line, so every boot of the radio has to be a cold boot. I really can't be bothered to rewire my car to fix this, and I don't mind the wait while it starts up., but every time it resets the touchscreen beep sound so I have to disable it in "car settings". BEEP BEEP BEEP, every time I get in the car. Drives me nuts.

Joying's suggestion of custom.txt ro.fyt.amp_switch=0 does not change this behaviour. Nor does fgrepping the entire filesystem for that setting and changing every occurrence,

Does anyone have any insight into which APK/framework stores the beep sound so I can replace it with a silent wav/ogg/pcm and regain my sanity? Or some other method to truly disable the beep.
[FYT Android Head Units] gtxaspec:
You can change the governor to "performance" and that will lock your min clock at 1040 regardless of temp...and ituxd (temp monitor software built in to unit) will shutdown the unit if it reaches 100c. But with active cooling, like me with only a fan you shouldn't teach those temps.

I'll keep checking.
[FYT Android Head Units] gtxaspec:
The stored in volatile ram inside the MCU. They reset Everytime the power is fully cut, nothing on the Android side .

My unit doesn't have touch buttons, so I am not sure. Can any other users chime in, do the touch buttons work for you?
[FYT Android Head Units] andytuinman3:
Thanks for the rom gtx. I do seem to have 1 "issue".

If I enable gpsfix for the 1km jumps instead of 3. My Sygic app doesn't really get a good location. Hangs on the same spot and "refreshes" the location after 200 metres or so. And then stays on that location for a while. If I disable the gpsfix everything works as it should. Is this a known issue?
[FYT Android Head Units] surfer63:
Yes, it is a known issue. Sygic users on the German china-rns forum complain about the same issue between sygic and GPSspeedfix.
[FYT Android Head Units] thingonaspring:
Thanks gtxaspec - both answers make total sense.

On the beep - I could use lbdroid's wrapped-lib approach to log the commands to the MCU, looking for the beep-disable command, and somehow replay that on boot. Might be fun to try.

Or wire up a constant 12V line and fit a CANBUS adaptor, probably that is the best option.

The touch buttons thing might just be a keymap issue, or more likely it's some missing service. Will have a dig around and see what I can see.
[FYT Android Head Units] olivier2591:
Hello

I have the touch buttons, after the flash of the new rom (joying or gtx) you must set everything in the configuration menu. on my car radio it works very well (JY-UMS02N2)
[FYT Android Head Units] Salah.irsheid:
Hi

I am trying to install the custom

When i click "install custom" i have this massage:

"You must be running at least AOSP build"

What does it means ?

Thank you
[FYT Android Head Units] surfer63:
It says "You must be running the last AOSP build". (or something like that)

Download the January 2018 firmware, and carefully check which MCU version you need: the 5.20 or the 9.20
[FYT Android Head Units] thetangstr:
I have this unit

I was able to root and install custom, but when I click on install gtx, it just boots right back to the same OS. any idea? Do I need to install the Joy firmware first? Is there somewhere I can find the instruction for that? I've the file downloaded, how do I install it?
[FYT Android Head Units] surfer63:
Did you first install the custom recovery image and then try the install?
[FYT Android Head Units] thetangstr:
Yes, and now i'm stucked at the logo/boot screen...
[FYT Android Head Units] thetangstr:
how do I tell the version of rom that I have installed? MCU doesn't show the right information, I tried installing this and it went pretty fast so I don't know what rom I am on
[FYT Android Head Units] DjMcM:
Hi,

Please help me! This rom working for my head unit? Technical parameters:

My head unit is (not factory ROM):

Model:

A-MEDIA AUTO (1024x600)

Android Version:

6.0.1

Android security patch level:

Juni 1, 2016.

Baseband (?):

SF3GR_M-26.3_cpeg_rk-r2p_bc2-20160629_111639

Kernel Version:

3.14.0+

chun@hctr930 #9

Thu Apr 6 16:40:37 CST 2017

Build Nr:

sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.hct.20170424.112341 release-keys

MCU Version:

MTCD_LM_V2.55_1

Jun 23 2017 13:42:21

Serialnumber:

HCT69000560

CPU:

Genuine Intel(R) CPU@1.2GHz (x4)

Memory:

1924 MB

Thank you!
[FYT Android Head Units] surfer63:
No. It's not compatible. It is an MTCD MCU running on a intel Sofia 3GR.

This ROM is for a FYT MCU.

The HAL9K and Malaysk ROMs are for MTCD/E units on PX5 (or PX3).

So no option for a custom Rom unless you make it yourself.
[FYT Android Head Units] almanxa:
hello

I have this in MCU line

MCU: 2017-10-25 19:20:49 JY_(_R76)__90_C9_7706_5009_CAN...

can I update with this rom

thank you?
[FYT Android Head Units] Joe-Tech:
Hey guy's, please I hope someone can helping me out with my Tesla head unit link where I purchased it Here There's this white text box in the middle of the screen, I can't seems to get it off, please see pictures. Also this unit is a Sofia 3gr FYT but has 5.1.1 installed. Please is this ROM compatible with my unit? By the way the system is rooted, but every time I tried to install the custom.apk I got a parsing error. Any help would be appreciated.
[FYT Android Head Units] D4rk_Seraph:
The curious thing is that your Joying Extra Tools software and root runs perfectly on my HU and the helper apk installed TWRP with success. So I guess that my HU could have the same hardware of the Joying Sofia units. I would like to try to install GTX in my HU but I cant find the original ROM files to recover in case of a unsuccessful flash.
[FYT Android Head Units] surfer63:
Then it is indeed a FYT unit. I checked the data on the website and that mentioned it was a STT unit. so, obviously that was wrong.

What is GTX?
[FYT Android Head Units] D4rk_Seraph:
GTX rom
[FYT Android Head Units] surfer63:
:D Of course. Thank you.
[FYT Android Head Units] barnesk9:
I've been using this theme for a year or so now and there's always been one thing that absolutely annoys me and that's that the FM radio app starts whenever I reset the unit, is there any way to disable it or even remove it completely so that the system doesn't even look for it on startup or resume?
[FYT Android Head Units] surfer63:
I have explained this at least 20 times in several threads in the past years, so with some searching you should have found at least one answer, but OK: again.

The radio is not android but builtin hardware consisting of an AM/FM chip and the amplifier. When you "cold start" the unit, the FM chip and amplifier are awake in a few seconds and start outputting on the last selected channel/frequency.

Android takes 40-50 seconds to be "awake" and simply cannot influence this "hardware behavior".

To compensate for this, the android layer in the unit autostarts the radio app so that you can immediately switch it off, but the radio is only a front-end to the hardware and nothing more. And you actually do NOT switch off the radio, you only mute that audio channel as the hardware will always stay "ON" until deep-sleep, but then Android remembers your audio channel setting on wakeup.

So if you disable or even remove the radio app, it will not even be possible to "switch off" the radio, unless you start some other media player that will then get focus and make the Audio manager switch to the media player output.

So live with it or buy a non-android car brand unit of about 1200-2900 euros.
[FYT Android Head Units] xDaemon:
I getting this error! How to fix it? Thanks.

C:\gtx_installer>run_to_install.bat 192.168.0.19

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

* daemon started successfully *

empty host name

adbd cannot run as root in production builds

connected to 192.168.0.19:5555

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

error: more than one device/emulator

Reboot your Head Unit NOW!
[FYT Android Head Units] surfer63:
Are you trying this on a Sofia or on one of the new 9853i intels?

Only(!) use this on the Sofia units.

If you have a new Intel Airmont, look at "HowTo: Root Joying SC9853i Head Unit"
[FYT Android Head Units] xDaemon:
Sofia unit
[FYT Android Head Units] surfer63:
Weird.

The message "adbd cannot run as root in production builds" means that it is not run against a device with a userdebug build, but against a user build.

The Sofias en PX5s are userdebug. The new intel Airmont is user.
[FYT Android Head Units] xDaemon:
I followed you guide for rooting Sofia 3GR Intel, but nothing. I will try again.

Edit: I tried few more times, and still getting '' adbd cannot run as root in production builds '' is there any other way to root my unit, or do you know any rooted rom ? Thanks in advance.
[FYT Android Head Units] xDaemon:
I rooted my Joying , installed this rom, but got this Video

it just keep restarting . . . . . .
[FYT Android Head Units] xDaemon:
I left to reinstall for today, but when i start my car and Navigation was ok, but there is another problem : is staying on checking connection 20 and more mins on wifi. How long a have to wait or i have to do something? Thanks
[FYT Android Head Units] surfer63:
It is boot looping. Do you have a fan or cooler block installed?

I guess it gets too hot and can't finish the first full optimization.

Open the lid from the unit and try with a hairdryer (on cold) to cool the unit if you have nothing else.