yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] TT_Vert:
View attachment 4264575

View attachment 4264576

View attachment 4264577

View attachment 4264584f

Here are the logs. To turn on radio I opened the radio apk. To close I hit back button. I cycled through all 6 presets.

I've also attached the widget that works when you first put in on main screen. Then you reboot and it'll turn radio on but it will not turn it back off However every time I reboot the widget reverts back to original widget with
[Android Head-Units] TT_Vert:
I don't even see the roximo launcher in google play. Where can i find it?
[Android Head-Units] pa.ko:
Here it is. Can't post screenshot right now. As I said, on/off works fine for me.
[Android Head-Units] JSZESZE:
Upon trying the new release with the updated weather widgets. I ran into a few issues. 2 are new or at least they are features that I've never tried until just this morning. 1 has been an issue for a while.

1. Adding a Navlink widget is something I just tried this morning. I set my home address and used the minimap as the app. After selecting the icon to start the route, it just stays on calculating route.

2. Adding my API key to the weather widget always results in fcc telling me the API check failed. I can call the API key in the browser with no problem. I even created a new one to make sure and it is still the same issue in FCC

3. This issue has been present quite some time. It has just never been a deal breaker. When choosing an OBD widget, I can't select an OBD device. FCC tells me that Bluetooth is not supported by the device or it is disabled.

My device is PX5 4gb ram. It's the HotAudio model
[Android Head-Units] SpeedFire-:
1. Yes. There was a bug with routing. Fixed in 3.082: fcc launcher 3.082

2. I checked on my other API key - it works. For the avoidance of doubt you need to get it here: https://home.openweathermap.org/users/sign_up

3. You need to select it in OBD widget settings.
[Android Head-Units] JSZESZE:
Ok. I have the routing fixed.

The open weather API still doesn't work. I got my key from the link. Do I enter just the key? Or is there more that needs entered?

The OBD widget is now working. But for speed it displays a decimal and two digits. Is there a way to only display a whole number?

Are there any plans to add siding adjustments to the Bluetooth and wifi connection widgets
[Android Head-Units] Roerbakeitje:
Is there a way to have a compleet empty statusbar in all apps? I did try system UI that's not realy helpfull. I ask because i use overlays To have some fcc widgets in the statusbar
[Android Head-Units] SpeedFire-:
Hi guys,

I'm going on vacation today (a 2,000 km trip by car). And here is a gift for you (as I promised). 3.083 beta:

- NEW method to ASSIGN WHEEL BUTTONS on Rockchip! Native button assignment for FCC actions!

Uploaded to beta channel and here: 3.083
[Android Head-Units] Roerbakeitje:
Have a Nice vacation. Enjoy the moments .see you soon.
[Android Head-Units] Ben.suffolk:
Awesome, looking forward to trying that this morning!

Have a great time, and enjoy the driving :)
[Android Head-Units] faxerpelle:
FCC and Xtrons TE706PL

Trying to configure FCC (as premium user) on my Xtrons TE706PL HU, running latest MCU and stock Android 8 Oreo ROM.

The player widget doesn't work completely.

During wizard configuration I choose FM Radio, DAB+ and Standard Player (which I suppose is the stock media player coming with HU ROM) as 3 players setup and then the skin.

When I push mode button on steering wheel the HU automatically cycles through apps Radio->Standard Player->Video->AVIN.

The widget does not follow the apps. When moving from Radio to Standard Player it does not update. Or it updates just the first time.

I've also tried to configure the wheel buttons part inside FCC to "catch" mode button but with no success.

Any ideas?

BTW what's the difference between MTCD/MTCE/PX3/PX5 and PX5+ option at first startup? I normally choose MTCD/MTCE one.

Thank you in advance
[Android Head-Units] abagos:
I can confirm that the weather API does not work, I am on 3.080. I think that it's not working even without entering my API key because it's stuck to the same icon and temperature for days. It was working when I first enabled it, seems to have stopped after an update.

By the way, I have also created a new API key for testing, still doesn't work. I know that the keys are ok because when I send a request over a browser, I get the response.

A.
[Android Head-Units] Scopesys:
Have a great trip -- be safe. :)

And thanks so much for the "NEW method to ASSIGN WHEEL BUTTONS on Rockchip!" = hopefully Google Voice activated from a Wheel Button !!!
[Android Head-Units] SpeedFire-:
It seems that on some devices new Wheel Button Mapping caused crashes. I tried to fix this in 3.084 (uploading to Play Store).

Please check if it works for you.
[Android Head-Units] Ben.suffolk:
Mine was crashing, I'll try and update today, will let you know.
[Android Head-Units] jun81:
Works for me 3.085

Mtce kld px5 android 8.0

[MENTION=4292729]SpeedFire-[/MENTION] Enjoy your holiday!
[Android Head-Units] Xorit:
my car uses canbus codes for the mapping, which doesnt work with your new option.

Rockchip irkey does recoqnize almost all buttons but chaning the codes doesnt do anything.

was hoping for someone to come with a solution for this, but maybe you re on the right way.
[Android Head-Units] SpeedFire-:
Do you have any more details on how does it work exactly? Which built-in app is used to map canbus signals to irKeyDown broadcasts? Can you send me your Wheel Button Teaching app (apk)?
[Android Head-Units] Xorit:
no wheel study works, not the in-built one nor any other.

MTCTools can read the codes, but cant re-assign the buttons.
[Android Head-Units] SpeedFire-:
Which particular? MTCDTools or MTCETools? Pls give me a link to the version which works for you. How do you understand that it recognizes your buttons?
[Android Head-Units] Xorit:
sorry, wasn't specific enough.. try again:

MTCDtools on xda works, as via "create new binding" on a button press it shows the numbers e.g. 123, when I press a button.

Recoqnize = shows numbers/keycodes.

The only button which is shown in any wheel study is my manual added button for key2 on the board to have a way to enter recovery.

All the other buttons on the radio cluster don't show their keycodes to any android app besides MTCD tools.
[Android Head-Units] Scopesys:
I thought SpeedFire was going on vacation -- on a 2,000km trip.

He either has a VERY FAST car, and is back already, or he is the most dedicated Android App developer ever !! (not that I am complaining :P )
[Android Head-Units] SpeedFire-:
:)

Since I have split those 2000 km into 3 days I have some time in the evenings to check how new wheel button method works. One positive report so far. Good start.
[Android Head-Units] Scopesys:
Yes, for the 1st time, FCC is detecting my Universal wheel buttons, but it does not run the defined apps, after I have allocated them to the short & long press.

I am emailing you the Eonon GA2170b (px5) Wheelkey aps, extracted from the unit. Hope this helps.

---------- Post added at 04:45 PM ---------- Previous post was at 04:29 PM ----------

@Speedfire

Heads up.. something to know, for when you get back from vacation.

FCC is by far the Best launcher (we all know that)

PowerAmp may well be the best Mp3 Music Player ? (I think so)

FCC works fine with the current PlayStore version of PowerAmp.

FCC Player widget correctly display the playing artwork.

But, with the current PoweAmp beta, FCC displays just a small center part of the Artwork, and that artwork is very Fuzzy and appears to have an Out-of-focus effect.

Don't know if this is a PowerAmp error, or something that may be needed to be corrected in the FCC Player Widget.

Apart from that, I believe the Player Widget (which must be one of the most complex FCC widgets) has a number of issues to do with updating Artwork, and text, especially when switching between players.

Since the CAR HU is primarily an Entertainment Unit, and it's main function is to play Music (and navigate), getting the FCC Player widget working correctly would seem to be important, so I hope you can find some time, after your vacation, to take a look at this. :)

Geoff
[Android Head-Units] Ben.suffolk:
I have done a very quick test and the new version does not crash and intercepts the keys nicely :)

The bit that's a little odd is the mode key on the custom 3 apps. I have set up just 2, dab+ and zBox. It does switch between them as I see the app coming up, but then it instantly goes back to FCC. I think maybe it's because you wanted the switch to behave like a background switch between apps maybe?

Problem is that means I can't switch to an app and then change the station or start something playing on the phone.

As its only 2 apps I have got round this for the moment by having one launch on a short press and the other in a long press of the mode button. That's working just great and the original mode app does not get triggered, so the core button functionality is fully working.

Well done I think without FCC the android head unit would be horrible and a regrettable purchase, but all these improvements you keep bringing in make it usable and what you would expect a head unit to behave like
[Android Head-Units] Roerbakeitje:
I have a problem in fcc. Noting seems to autostart after sleep. I try different streaming players dont help. I also have set two apps in the settings to autostart that also wont start aftersleep.

Someone Els have this also?
[Android Head-Units] Ben.suffolk:
I might have that issue. I have my dvr app set to start so I can remember to check if it's recording or not (it's supposed to but often does not). I find that sometimes it starts in the foreground which is what I wanted. The times it does not I always start it myself from the menu , but next time I will check if it's running in the background. I expect as its a manufactures app it's in the whitelist so is probably already running in the background and that's why FCC does not start it in the foreground.
[Android Head-Units] Scopesys:
Now have steering wheel controls working . using a Universal Steering Wheel controller connected to China Eonon2170B ... Can now click button and trigger Google Voice -- FANTASTIC !!

Great Job SpeedFire
[Android Head-Units] Scopesys:
Spoke too soon -- now the Wheel Buttons are working well , I hear a major problem.

I do not think this is a FCC Launcher issue, but as others are getting Wheel Buttons to work, and are using it to control Google Voice / Assistant - here is my issue.

Google Voice is way way way too soft.

All the Audio Players and the Radio, and Video players all output audio at a similar level. So does Google Map ( set to the Normal level, ie not Soft or Loud), but Google Voice/ Google Assistant is way way low.

Even with the current player's audio paused, it is very difficult to even hear Google Voice, with the volume control set to a normal listening level for the other Audio Players. ( Note Google Map audio is fine)

ANYONE else experiencing this, or have a solution ???

(Running an Eonon GA2170B head unit -- China Px5)
[Android Head-Units] SpeedFire-:
Check settings "Setup Google voice action" in the Wheel button settings (the very bottom). There is an option to decrease Google voice volume. You may disable it.
[Android Head-Units] telexxingou:
Hello all..

i'm a very happy new user of FCC Launcher....

My unit is Allwinner T8 (iTopWay)

My Steering wheel is a Sony RMX4S working perfectly with this unit using TW settings....

But like many others, TW service is very limited to execute some functions/applications....

FCC Car Launcher Beta 3.85 is installed and working nice....

But FCC don't detect any action on this wheel when going into "Intercept button...."

I think it's because Allwinner and not Rockchip CPU.....

Can you confirm it ?

Anyway, thanks for your job !!
[Android Head-Units] SpeedFire-:
You're right. This is because AllWinner is not supported yet.
[Android Head-Units] telexxingou:
Ok ....

Do you use, and i suppose so, hook procedure to intercept button ? but in Rockchip firmware which ?

May be "dispatchKeyEvent" ?

I'm investigate my firmware to intercept the Allwinner button...

At this time, i've find some clue (like change Music, Navi,etc... apps in mode cycle) but not the final code to intercept wheel button.....

thanks
[Android Head-Units] HatManSan:
I am sorry but I cannot find any trace of Streetname on Google or PS. Can you provide a link please. Thank you
[Android Head-Units] SpeedFire-:
Actually not. I don't use hooks or any other xposed like methods. I use native methods to teach MCU. I link resistive codes from wheel buttons and map them to my custom irKeyDown codes (I introduced 7xx codes for FCC Launcher). After teaching MCU natively fires 7xx codes when wheel buttons are pressed. Then I just receive those codes and do users actions.
[Android Head-Units] SpeedFire-:
Hold your finger on any empty space in FCC Launcher -> select Widgets -> scroll first row of widgets (FCC widgets) to the left. You will find many FCC widgets one of which is Streetname widget.
[Android Head-Units] Roerbakeitje:
Talking of Widgets, would love to see a Google Voice FCC Widget, that displayed overlaid on the current screen (like Notifications), and just displayed (at a Minimum) a Animated Graphic of the Microphone Audio input in a small Box. (sizable, color changeable, changeable Text -- just like the common edit functions of most of the FCC widgets)... ( and a way to keep Google voice in the Background - when driving, one is not wanted to be distracted with a complex Google Voice Option screen.. one just want to know that google voice is responding.)

This would really set FCC in it's own class, above all other Launchers !! :o[/QUOTE]

Go to Playstore.

+Download google assistent . (Its a shortcut)

Next

+Download Overlays from Playstore.

Set It up as you whants It.
[Android Head-Units] Scopesys:
Thanks ... :good:
[Android Head-Units] Roerbakeitje:
Acoording to google voice. Did you play with balans settings of the volume? I have set all my channels of sound to low. And set the mainstream volume high And hear the Google voice ok now.
[Android Head-Units] ricardo026:
Tnx! looks great, going to test it today on my android 8.0 oreo, 8 core 2gb ram head unit
[Android Head-Units] SpeedFire-:
Some changes on the latest beta 3.086:

- Weather update fix

- Album Arts should be processed faster

- Speedlimits should flick less
[Android Head-Units] Scopesys:
Thanks for the suggestion.

I have been trying this with an app that is meant to assign a volume level to the current foreground app automatically, but it gets very complex, and does not work very well. And all this because GOOGLE seem to have dropped the ball on their Assisstant App.

If you are able to set ALL your other audio sources to LOW, and then the master gain to HIGH to get a balance, I can see that that could work, BUT that means that ALL other audio sources have to include independent volume controls ( which most don't) to compensate for just one Google Voice/Google Assistants having an INCORRECT low volume output, that cannot be adjusted.

GOOGLE should fix that APP, just like they finally did for Google Maps.

Users have been asking Google to do this for YEARS, and it still has not happened... (Sigh).
[Android Head-Units] Scopesys:
In my China Eonon Head unit, there appears to only be one Volume control that can be altered in real time: "Volume control", that affects both Music Players as well as Google Voice/Assistant.

In the Factory setup screen, there are different level seeings for things like TV, DVD, Bluetooth, system etc but after changing those preset values, the unit needs to re-boot.

I have played with them all, in different combinations, and no combination seems to be able to alter Audio Player Volume and Google Assistant Volume, independently of each other. I assume they are both on the same Audio Channel "Media".

Actually, so is the Google Map audio, but Google Map has its own internal Volume modifier soft/normal/loud, that allows it's volume to be adjusted with respect to the Music Players.

So, I, AND MANY OTHERS have asked that Google Voice/Assistant really needs its own volume modification control built into it (like Google map), but like so many others who have brought this up in the Google Assistant forums, we all seem to be totally ignored by Google.

REALLY MAKES YOU APPRECIATE just how responsive and helpful SpeedFire is with support of FCC :o
[Android Head-Units] Xorit:
- Weather update fix - API from OpenWeatherMap not recoqnized anymore :(

- Album Arts should be processed faster - not tested, only internet radio

- Speedlimits should flick less - yep, and more constant, not displaying "-"
[Android Head-Units] Joecool92:
Great Launcher.

Is it possible to integrate more from MTKD Devices like this: https://rsnav.com/ ? In my case i am interested in your brightness control. This device is not supportet and also have inverted Values there.
[Android Head-Units] SpeedFire-:
I need all system apk-s to find out how difficult it is to integrate MTK
[Android Head-Units] Roerbakeitje:
@ speedfire can you please taken a look at the app i posted. I have mailt dlthe dev off that app. But he we not at the app in landscape mode.

Maby you van reporduce the app acoording to set volume assistente .
[Android Head-Units] SpeedFire-:
Can you record a video to show how it works and what it should do?
[Android Head-Units] Roerbakeitje:
I make something photos.

Here you can control the output volume of your google assistent. Its a one time setup and works realy good.

Now the app is working i test it

as you see when load the app on a android radio its cropt together and you van not set anymore setting.
[Android Head-Units] Joecool92:
Should i pack it from my running system or can you get them out of the systemupdate: http://wiki.rsnav.com/Help:Software_Update ?
[Android Head-Units] SpeedFire-:
From your running system only.
[Android Head-Units] piercedpanda:
Updated this morning, but after a restart the weather widget is still not working for me
[Android Head-Units] Scopesys:
Many thanks .. I'll try it out this weekend.

However, Google still needs to put a local volume control into Assistant :)
[Android Head-Units] Roerbakeitje:
Yes i know . But that's what google not Will do. Its a great whay to control the output of google voice.

And maby when its inplemented in fcc its the only launcher that can control the voice output of the assistent.

[MENTION=9350973 ] All[/MENTION].

[MENTION=1633144]speedfire[/MENTION]

Found a error on my device . All of the permisions seems to be reset. Its not fcc related i know .

I set againg all permissions and after when het Comes back from sleep its reset againg . Its this a setting in device?
[Android Head-Units] WarSpaz:
I have a problem that started when i updated the app. When i turn off the car and start it again it wont resume the song like it sid before. Now it starts it from the beginning

Skickat från min ONEPLUS A6003 via Tapatalk
[Android Head-Units] sanangel:
[MENTION=1633144]speedfire[/MENTION] I can not get fcc to show notifications with every song change with poweramp. I have given permission to fcc car launcher to modify system settings and to mount on other applications and, even so, I do not get the notification...
[Android Head-Units] Scopesys:
I get notifications from Poweamp displayed on FCC, so it may be a setting in Poweramp to show Title/artist Notifications that needs to be turned ON ..(Poweramp has LOT of settings !!)

---------- Post added at 05:31 PM ---------- Previous post was at 05:26 PM ----------

@SpeedFire

Is FCC able to detect (or could it be programmed to detect) which Music Player/ radio is currently playing, no matter how that player was selected to be the current foreground player ??

I ask because if it can, then I have additional questions / requests.

If not, no point in asking :)

Geoff
[Android Head-Units] SpeedFire-:
I don't know how it will work BUT (3.089):

- Player widget style change: now you can select Album Art masks from a list.

- [beta] automatic Google Assistant volume control (see Wheel Button settings)
[Android Head-Units] SpeedFire-:
An improvement in 3.090 beta:

- [beta] Google Assistant volume control - OPTION TO AUTO-PAUSE/RESUME PLAYER
[Android Head-Units] Roerbakeitje:
Just wakeup here . Going to eat and than i gonna test It.

PS you have vacation lol.

---------- Post added at 09:50 AM ---------- Previous post was at 09:07 AM ----------

Ok test It. Sorry its not working :rolleyes: i hear no differents in sound volume .
[Android Head-Units] SpeedFire-:
Does it pause the music while Assistant is active? Just to check that it works and recognize the Assistant.

P.S. I used volume change in android Media stream. As it was done in apps you mentioned. I can switch to changing volume of head unit itself.

You can also send me a LogCat
[Android Head-Units] Roerbakeitje:
Yes i test It now also on my phone . It seems not tot work with the media stream but with master volume.

Also on phone fcc is not working the app works

---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------

Do i need root for catlog? My unit is not rooted Just running stock

Sorry Read to fast . I need root for logcat
[Android Head-Units] SpeedFire-:
The app changes MUSIC stream (media) not the SYSTEM stream. So it should work fine. Please also don't forget to disable old volume control method (it is below in settings - called "Decrease volume").
[Android Head-Units] SpeedFire-:
3.091:

- Switched to Head Unit's volume control for Google Assistant volume control function
[Android Head-Units] Scopesys:
Just tested 3.091 ... not quite there yet.

When google Assistant is activated, FCC seems to immediately set the MEDIA (or Master) volume to new level TOO SOON .. Music is still playing, and it gets set to that new (Louder in my case) volume, and for about 1 second, BLASTING your ears.

FCC needs a 1-2 second delay, if New Assistant volume is greater than current volume ( and maybe no delay if New Assistant Volume is less than current volume).

Then, the problem is that FCC is altering the reduced Background Music level, as a side effect of altering the Assistant Volume, which is not ideal.

IF Assistant volume is being Increased, so is Background Music, so the net effect is still that Assistant is lost in the Background music.

Unfortunately, it would be SO MUCH BETTER and cleaner, if Google put the control into the Assistant APP -- but that does not seem to be likely.

Lastly, there is an issue of restoring the Audio Volume when Assistant has finished talking .... setting this on a fixed time delay fails as there is no way to tell how long the response from Google Voice is going to be.

Google Assistant may know, but it is difficult for an external app to know, ie for FCC to know when Google Voice has finished speaking, especially if there is also background Music.

If the Background Music was totally Muted during assistant, then maybe there might be a way for FCC to detect a period of silence from Assistant, after it has detected Assistant talking, and restore the Audio at that point.

What is achieved so far is definitely increasing Assistant's Audio, but with too many undesirable side effects.

----------

Out of interest, what are the chances of being able to De-compile assistant, and inserting a Volume control directly into the Assistant Output Audio stream, before it reaches the Media Channel. I'd pay 10's of $s for that !!!

This would be a far Better solution for this issue than modifying the Media Audio for all Media audio (like both FCC and all other "assistant volume" apps)
[Android Head-Units] SpeedFire-:
Why don't you want to use auto-pause feature? It will exclude all the background noise from players.