yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] derschnelle:
I just tried to change the permission settings for maps etc but it wouldn't let me because of active overlays. Even with all overlays deactivated I couldn't do anything.

Has this issue been here before?
[FYT Android Head Units] gtxaspec:
Yes, that is why the Xposed module is included, it is a bug...the latest opengapps services detects overlays do to two of the stock joying apps forcing overlays permanently You can disable overlays on UIServer and MainServer apps and the active overlays prompt will go away, or just make sure the Xposed module is active.
[FYT Android Head Units] derschnelle:
Oh thank you very much, I must have missed this in the thread.

Maybe we could add it to the FAQ-section on the first page?
[FYT Android Head Units] gtxaspec:
The Xposed module should be enabled by default... Did you disable it or was it just not working for you?
[FYT Android Head Units] jesmon:
Ok so yeah, confirmed that google Play services and bt streaming have an issue. Disable google Play services and bt streaming works fine.

However good news is I enabled google play services, used google play music on the unit (not bt stream) and viper works 100%. Well done!! They fixed the Google Play services issue in the December update if that helps troubleshooting.

Everything else works really well, it feels quicker than 9a2 to me.

Thanks again GTX, I will use Google Play music on the head unit for the time being.
[FYT Android Head Units] hardykalyan:
Hello Jesmon... can you make a flashable zip for the fix and post it so that others may use it... thanks for tge feedback of the rom btw...
[FYT Android Head Units] gtxaspec:
The fix is figuring out why play services is causing a problem...even with the newer version of gapps that I include...so it must be something else...
[FYT Android Head Units] hardykalyan:
I gonna test and update you on Friday... i suppose this might be also coming from the launcher joying designed..... guess they kinda created few variables for their launcher, that is messing with bt...jesmon, can you set your default launcher to one of joying launchers and see if the problem is resolved... Thanks
[FYT Android Head Units] gtxaspec:
No, not launcher related. I also have the issues and I removed all stock launchers.
[FYT Android Head Units] Astur_Torque:
This ROM is great.. waaaaaaaaaaaaaaaaaaaaaaay faster than 5.1 one

I have few questions

-Which music player are you using?

-With Canbus is imposible to customize buttons (I have an Opel Corsa D)

-With Poweramp, the next/prev song delays a bit when start the car, then it presses in a row as many times I press

-Canbus and text messages to DIS (We have to find out how it works to forward strings)

-With Viper4Android not BT streaming, at the moment (in 5.1 it crashes directly)

-I have to set up everything, but I think I'll be with this version quite a little time

-Let's see how it behave, I will report you everything gtx, even if I am a pain in the ass
[FYT Android Head Units] gtxaspec:
Lol thanks for the feedback...download xsofiatwealer from the Xposed repo...to customize buttons.

I use Google play music and vlc personally.

Get a fan and enable performance mode...even faster.
[FYT Android Head Units] Astur_Torque:
I have a fan, i have to activate performance gobernor then...

Google play is very skinny of options to me... vlc is excelent for videos...

I need more time to deal with this incredible rom, thank you for your great effort

i hope we’ll find the way to control canbus txt hehe

Enviado desde mi iPad utilizando Tapatalk
[FYT Android Head Units] Astur_Torque:
I have a fan and i know when it sleeps... I am noticing that sometimes doesnt go to sleep, what could be?
[FYT Android Head Units] jesmon:
The fan keeps going? What wire did you hook the fan up to? I think the when you turn the key off it kills the screen but the unit can keep processing for 5 or so minutes. If it's still going after 15 minutes then you may have hooked the fan up to a continuous 12v instead of an accessory 12v
[FYT Android Head Units] surfer63:
That is correct. After switch off my fan runs for 4 minutes and then the entire unit goes to "deep sleep" and the fan also stops.

Unless you indeed connected it incorrectly.
[FYT Android Head Units] IG_Vasilich:
Where have you connected the fan to? AMP CONT?
[FYT Android Head Units] surfer63:
Sorry. stupid. It's connected to USB. It's a 5V fan.

For the answer as such it doesn't make a big difference.

When switching of the unit, the screen is immediately switched off. The android part is a bit later shut off (You can check that with a media player and nokill. Without settings for ACC_OFF/ACC_ON, it plays a bit further before going to sleep).

After 4 minutes everything is in "deep sleep".

That is in case no apps have a wakelock keeping the CPU awake, because that will also keep other things awake including the fan.

So in the case of apps having wakelocks, the MCU simply shuts down after 15 or 20 minutes or so resulting in a cold boot.

In case you have a 12V fan connected to continuous 12V, then that one will even continue after 15-20 minutes after the MCU has killed everything.
[FYT Android Head Units] Astur_Torque:
Before install 5.1 it went sleep in less than a minute, now I don't know how many minutes... but when I start the car, the unid had a full shutdown (not in the sense of lose all the memory of course, but I don't know why it doesn't stand by.. (sleep is activated instead of full shutdown)

edit:

Maybe this is the reason:

"That is in case no apps have a wakelock keeping the CPU awake, because that will also keep other things awake including the fan.

So in the case of apps having wakelocks, the MCU simply shuts down after 15 or 20 minutes or so resulting in a cold boot."
[FYT Android Head Units] gtxaspec:
Disable the no kill function, which is enabled by default in xsofiatweaker, if you enabled it.
[FYT Android Head Units] jesmon:
You can try downloading a wakelock detector let it run for a while and see what is stopping the unit going to sleep.
[FYT Android Head Units] Astur_Torque:
Thanks I'll do

Enviado desde mi Oneplus 5 mediante Tapatalk
[FYT Android Head Units] prmah:
Can i connect the fan with amp out ?
[FYT Android Head Units] Astur_Torque:
I don't know if this will be useful for you, but I think CANBUS messages come from Sofia-1-C9-Server-V1.0\classes.dex

or no.. I don't know
[FYT Android Head Units] derekbunch:
Can anybody link me to a tutorial thread for adding a fan to my unit?
[FYT Android Head Units] gtxaspec:
You can use jadx or a similar decompiler program to translate the app into readable Java files... Keep digging
[FYT Android Head Units] Astur_Torque:
Thanks... Lets see what there is under the hood.,

Enviado desde mi Oneplus 5 mediante Tapatalk
[FYT Android Head Units] etrefal:
You could look here:

https://xdaforums.com/android-auto/android-head-units/inside-look-joying-android-head-unit-t3546872
[FYT Android Head Units] surfer63:
There are 2 apks arranging the CANbus communication: the SofiaServer and the CANb.us apk . Inside the SofiaServer you will find all classes for all auto/can bus brands/combinations. They are a top abstraction layer to the real interface classes below that.

With jadx you can analyze them
[FYT Android Head Units] Astur_Torque:
I have one problem... when a sound from other application sounds, the music of Poweramp stops for a sec and then continues... Can I solve this issue?
[FYT Android Head Units] wanb1i:
There's a setting in Poweramp settings/audio/focus/short audio focus un check that.

---------- Post added at 02:27 PM ---------- Previous post was at 02:00 PM ----------

I love the ROM! It runs well and smoothly. I have one issue though, I use an app called CPU Monitor to monitor the temperature of the CPU. It has a widget that sits in the notification area that can be moved wherever you want it within the notification area. It works great after a reboot, but if the system goes to sleep it still displays, but it doesn't show the correct temperature (it will show 30°C). I also use COOL TOOL to monitor CPU usage/frequency & network via it's widget. This app has no problems with the system going to sleep. So I'm hoping there is an easy fix for this or perhaps some other app that can be used instead to monitor the temperature that also has a widget and can survive the system going to sleep?
[FYT Android Head Units] gtxaspec:
Xsofiatweaker can display temp on the status bar by the clock... Like that?
[FYT Android Head Units] wanb1i:
Yup, love it! However, I can't find it in SofiaTweeker! I looker through all the options and didn't see it....
[FYT Android Head Units] surfer63:
Which version do you have? We are now on version 1.24.

Did you check the Xposed Installer for updates? And if you do in the Modules screen, do not forget to "swipe down" to refresh the content from the xposed repo.

It is in the first ON/OFF settings screen, but this one requires a soft reboot after setting it, as it needs a fresh start from the systemui.
[FYT Android Head Units] wanb1i:
I'm on v1.11, but I only see 1.15 available for download w/settings set for experimental.
[FYT Android Head Units] surfer63:
In that case I would simply download it directly: http://repo.xposed.info/module/org.hvdw.xsofiatweaker
[FYT Android Head Units] wanb1i:
Thanks! :good:
[FYT Android Head Units] Astur_Torque:
thanks a lot!

---------- Post added at 11:33 ---------- Previous post was at 11:30 ----------

I have a question.. buttonmod and nokill mod are deprecated? Is it better to use XServedMod instead, right?
[FYT Android Head Units] surfer63:
Yes, it is better to used the Xposed modules for several reasons.

The XSofiaTweaker can do a lot more than than the Gustden mods by now.

The Xposed modules do not require adaptations to the SofiaServer so we do no longer need to maintain a Sofiaserver mod for every firmware release

The XSofiaTweaker is faster than the "Gustden-mod + launcher.sh" combination.

The XSofiaTweaker can be maintained more easily by multiple people as the java is clear and simple (because I'm a simple, beginning java programmer), and there is no need to dig around in complex, unreadable smali code from a decompiled sofiaserver

The XSofiaTweaker has also 2 functions that "touch" the CANbus without even having touched the CANBus.apk (apart from analysing which function to hook: thanks to [MENTION=7838245]realzoulou[/MENTION])

(And finally: this question should actually be asked in the XPosed modules thread to keep [MENTION=520205]gtxaspec[/MENTION]'s thread clean.)
[FYT Android Head Units] Astur_Torque:
The little i read inside these apks is a real caos... I couldnt find any about display canbus text... These chinese people dont put a comment line not even killing them xd

About xserver, i have to study it very well your tutorials to know how to customize my radio perfectly... As you know I'm new with this rom after a looong time with 5.1 xd

Enviado desde mi Oneplus 5 mediante Tapatalk
[FYT Android Head Units] gtxaspec:
confirmed the bluetooth audio streaming bug...looks like it just cuts in and out randomly...aside from this...anyone else who tried it find any other bugs compared to alpha 3?

edit-

i think i fixed the bt streaming audio issues, any other bugs before a new alpha?
[FYT Android Head Units] jesmon:
I'm having issues of Google Play music pausing randomly and needing to manually press play to resume. Not sure what is stopping it (I have Waze open but it generally works fine) one issue with waze and play music I am having is it will quieten the music for nav but doesn't always return the music to full volume, the next nav instruction when finished normally fixes the problem until the next time it does it.

Might just be software issues and not the rom at all.
[FYT Android Head Units] ptolomeo:
How can I check the ROM version currently installed?

Hello, I tried to install the ROM (upgrade from v.6 to this v.9.3a) :)

1.- I installed the Custom.apk,

2.- I clicked in the 'Install Custom'. Ended OK.

I didn't see any button of 'REBOOT TO INSTALL GTX ROM', so I rebooted to TWRP, and flashed the XXX_GTX.zip file

Apparently I have the new rom installed, but couldn't confirm it, as I haven't found it anywhere in the firmware info options.

Is there any way to confirm the ROM version I have currently installed?

Thank you in advance.
[FYT Android Head Units] surfer63:
Inside /system/app there is the "fyt_build.prop" file. Inside it you will find

ro.build.user=gtx
ro.build.user.version=9a3

Version dependent on ROM version
[FYT Android Head Units] lexuz:
Hello, Just rooted my unit and eager to test this rom. Does Bluetooth calling work good? On my citroen C1 with the joying unit people can't a seem to hear me because the sound is really distorted.
[FYT Android Head Units] carter.w.jason:
Was just testing the voice quality the other day, works "ok", sounds like a cheap Chinese speakerphone, but that is what it is. I don't have anything I would call a distortion issue.

My setup; Using external mic, front mic has been removed. Using "Front Mic" option in Car Settings.
[FYT Android Head Units] lexuz:
I did a test yesterday with the same setup and the sound was fine, engine was on but on a parking place. Today I will try with driving to see if the issue was just " road noise". If you ahave a external speaker connected the unit will always used that one afaik. This is something I've red on the old joying forum.

I don't know if I did something wrong but the unit is working worst now. A couple of freezes and a full restart of the unit. Maybe It needs to see the down.
[FYT Android Head Units] jesmon:
Hey GTX, what's the plan for the future of the rom, will you focus on the July framework and cut away the other version?
[FYT Android Head Units] etrefal:
Got something strange here: I was trying to setup a shortcut using a swipe gesture with Nova Launcher - sorry, I'll probably be wrong about the terminology... I want to get a shortcut to get me to the so-called "Ehernet" settings so that I can get my USB tethering working. when I need it. I'm able to create the shortcut, but when I use it I first get a window telling me that the Settings app has crashed. After that when I use the shortcut I get a white window flashing briefly on the screen that goes away immediately - but I can never get to the Ethernet settings that way.

I'm on v9A3 of [MENTION=520205]gtxaspec[/MENTION]'s ROM - I don't think it's related to the GTX ROM though, as I think I had the same problem with the original Joying July ROM before. At the time I thought I had done something wrong, which is still possible. Can anyone make this work at all?

Thanks!
[FYT Android Head Units] gtxaspec:
Are you using a USB Ethernet adapter???
[FYT Android Head Units] Astur_Torque:
Will we be able to fix the BT issue without wiping data?
[FYT Android Head Units] User1977:
Is there any chance to change the status bar to a normal one like Samsung devices has (without soft buttons and showing notifications on the left)? What about hiding the buttons with "qemu.hw.mainkeys = 0" in build.prop?
[FYT Android Head Units] etrefal:
Yes I am, this one: https://www.amazon.ca/gp/product/B00MYT47EA/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 which has an ASIX chipset.

One thing I should've mentioned in my original post: If i go through the motions and get manually to that menu, it works fine. It's just the shortcut method that doesn't. It's Settings->More->Ehernet I'm trying to bring closer - easier to reach.
[FYT Android Head Units] gtxaspec:
Ahh No clue about shortcuts...
[FYT Android Head Units] User1977:
What about changing the DPI? Will this deactivate the tablet ui automatically? It's safe to change the DPI or can it cause a bootloop?
[FYT Android Head Units] gtxaspec:
Safe to change
[FYT Android Head Units] User1977:
Yesterday I have played a little bit with XSofiaTweaker but I don't changed anything in the section "Define apps or actions when the contact/unit is switched ON or OFF; or when coming out of resume" but now, everytime I switches the unit on it starts playing my media player even when I haven't played it before I turned the engine off. This is a very nice feature but how can I deactivate it when I want to get rid of it? Any idea where it comes from?
[FYT Android Head Units] lexuz:
How to use Google voice to dial a contact? I tried to do what is on the first post (q&a) but I can't seem to find the option the Hamburger menu.
[FYT Android Head Units] surfer63:
This is due to the fact that nokill prevents the mediaplayer from being killed, so it simply continues where it stopped after "getting awake" again.

If you want the meidaplayer not to start automatically again, use on ACC_OFF the option "system call" and for the text entry "input keyevent 127". This is the android event for "pause active mediaplayer".

I use the same command as well, as I don't want the player to start automatically again.

If you do want that, use for ACC_ON the "system call" option with "input keyevent 126" (play).

Anyway: Next time first read post 2 (Q&A) which explains this.

---------- Post added at 10:09 PM ---------- Previous post was at 10:03 PM ----------

I do not exactly know what you mean. Also: using OK Google is something else as voice feedback from Google voice, the feedback that is enabled by not muting channel 4.

The example in the the 1st and 2nd post describes how to start the Google voice search, enabling you to "speak now". Then you could say "bel pipo de clown" or also in english "dial Linus Torvalds" (if he is in your contacts).

The example is not how to enable Google Voice, it is to couple the command to a button.
[FYT Android Head Units] lexuz:
Bel Pipo de clown, dat is een goeie?.

If I try to call someone with the app I always get " cannot call right now" from within the app. That's is why I thought about the q&a section. Not a big deal for now anyway.?
[FYT Android Head Units] gtxaspec:
Change your dpi to 161 orbgreater.
[FYT Android Head Units] wanb1i:
I have a similar, but different issue. I have V3a installed with the "Speech" SW Button set to Source and with the tweeker set to enable google voice on the press of the Source key. When I press the Source (Speech) key nothing happens. This used to work in the previous version, but I can't get it to work in V3a. What am I doing wrong? I don't know what the DPI setting is, I haven't changed it, if that matters?
[FYT Android Head Units] surfer63:
Which XSofiaTweaker version are you on? V1.22 and V1.23 contained a bug with regard to the Source/Mode button.

V1.24 fixed that.
[FYT Android Head Units] lexuz:
I've changed the dpi to 180 and followed the instructions on the first page. That did the trick I can now use voice search to call my contacts and even say to Sygic to drive me home. Even if I would only count this feat. this rom is already better than the original. Nice work to all involved.
[FYT Android Head Units] jesmon:
Out of interest, what was the solution?
[FYT Android Head Units] Astur_Torque:
A bug: Every now and again when I use the phone call, it shuts down completely

Not a bug but estrange:

The ROM is way faster than the original one... however, it takes longer to switch to backcamera than 5.1 in which it was instantaniously
[FYT Android Head Units] im0nKeY:
At first, thank you for your work.

I don't know exactly the definition of the "bluetooth audio streaming bug", but I installed your custom ROM for the first time. I updated to the newest Joying FW and then installed your Custom ROM. Everything is working fine, except for BT calling. I can pair the phone and make calls, but the called person can't hear me, only strange noises which sounds like feedback. I repaired the phone, reset the BT settings on the HU and removed the Viper Drivers, nothing helped.

Is this issue known? And what can I do?

Greetings

im0nKeY
[FYT Android Head Units] hidroela:
i don't know if this is your case but I was having the same problem that you are having and the issue was a custom ROM on my phone with some Bluetooth bug on it. i switched to other custom ROM and that was it.
[FYT Android Head Units] im0nKeY:
Not impossible. I'm using a Xiaomi Redmi 4 with LineageOS, but it was working with older Joying Stock-FWs on the HU.
[FYT Android Head Units] hidroela:
i don't know if this is your case but I was having the same problem that you are having and the issue was a custom ROM on my phone with some Bluetooth bug on it. i switched to other custom ROM and that was it.

well good luck finding a solution.
[FYT Android Head Units] gtxaspec:
Download xsofiatweaker, and enable the module and reboot. It's usually caused by ok Google everywhere, but if you have some third party app that always listens, will also happen.
[FYT Android Head Units] PsychoMcSatan:
Just installed alpha4 and running great... except still haven't been able to get Live Wallpapers running. Successfully used "cp -R /system/vendor/oem/LiveWall* /system/app" and rebooted, but still getting 'app not installed'. Manually installed Livewallpaperpicker.apk like user above, but like him, just crashes when trying to enable a live wallpaper.

One odd thing I noticed is that under settings->display->wallpapers, there is the choice for "Live Wallpapers", but also "Wallpapers" is listed 3 times. Each of those three presents with a choice of different stock wallpapers. I also have Nova Launcher Prime running which offers only some of those choices.
[FYT Android Head Units] wanb1i:
I have the same problem, I use Project M Pro for a live Wp that dances with the music. Ever since installing this ROM (which I love) no live wallpapers.
[FYT Android Head Units] Redbullssg:
I might as well bring this to this thread... Im having problems installing, and probably not doing something right... I rooted my HU, Downloaded v9 Alpha 3 and extracted the files to my cleaned thumb drive(128gb).

Already had v4_9 custom.apk installed on the HU... I think I screwed up. Everything seemed to be going really well.. Looked like the video at the beginning of the thread, had the new boot screen. Didn't show any errors, said it was optimizing apps, like 30 of them I think, and then thought it was done and then I got this screen saying "Unfortunately, Google partner setup has stopped." and just hung there, I hit ok... There were no apps, and no buttons, just the drop down where, I rebooted and it looked like it booted normally, the same way it did before, but after it was doneb there is nothing but a blank screen with a pull down again... So I hit the RST button, and it went through the boot again, and now it says Android is starting" Starting apps", but has been hanging here for about a half hour... I reset a few times, and the same thing.

I'm afraid I didn't have something right, like the custom-master on the HU or something... I can't remember... Or should it have been on the thumb drive with the v9 rom? What did I do wrong? Where am I supposed to have the custom-made file?

Anyway, after many attempts, I finally got the newest JOYING update to install, and now I am back to stock...

Would the HU still be rooted, or do I have to go through that process again? Sorry, I'm a newb, I have never rooted anything before so I don't know these things.

I want to do this right, and install the V4 test rom so Viper4 works... That was my whole goal....

Can someone please help
[FYT Android Head Units] gtxaspec:
Start again, use a different flash drive. Start from the beginning,install custom, etc

Units are picky and sometimes can lead to corruption during install.
[FYT Android Head Units] Redbullssg:
I want to be straight next time... I will get a new card or flash drive. I am back to root access and have the V4_9 custom.apk installed, as well as Joying Extra Tools.apk. Where am I supposed to put the custom-master.zip(source code) the second file under V4_9 on first pag , am I supposed to unzip it somewhere?
[FYT Android Head Units] surfer63:
Also make sure you have only ONE external mass storage device in your unit.

so if you use a usb-stick , first unmount your sd-cards before starting the flash.
[FYT Android Head Units] evo1234:
Hi guys, can you suggest a unit for Nissan Qashqai 2015 ?
[FYT Android Head Units] Redbullssg:
Yes, only have one in. But want about my question as to what to do with the custom source code zip?