yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] rigattoni:
That seems to be related to the home button implementation of some firmware version. On some devices the home button does not get FCC back from background, instead a new instance is created with FCC.

I am fighting with this issue too on my new device. :crying:

By the way [MENTION=4292729]SpeedFire-[/MENTION] , is there a chance to get the split screen integration with the possibility to decide on which side the split app comes up? Just now, the split app is on the left side and FCC is running more or less stable on the right side of the screen.

What I miss is a button to split the screen... ;)

I created a split button myself with Tasker to split and go back to full screen as toggle button. Works so far, but FCC in this case is always at 75% screen width and I did not find a way to push it to 50% as I would prefer.

If someone is interested to get the toggle script, just ping me. An icon is included,

Just now the script toggles to TomTom and FCC and back to FCC. If you use other navigation software, you need to adapt the script yourself.
[Android Head-Units] Ericang:
Is there any chance that my request for the left and right panel to include widgets placement be addressed please ?
[Android Head-Units] Scopesys:
What I miss is a button to split the screen... ;) +1

[MENTION=4292729]SpeedFire-[/MENTION]

But even more useful would be able to define any give new SCREEN to be a split screen, along with defining the app that runs with it (on the left or right)

Then all one would need to do is either Vertically swipe to the desired Split Screen Screen, OR use a PAGE Widget button to directly select that split screen.

The other BIG ADVANTAGE of screens that are created as Split Screens, is that their design can be optimized to have the FCC side run in the reduced split screen area, rather than trying to Compress and "programmatically" resize a normal Full Screen, into one side of a Split screen.

I've suggested this a few time, because I think it is a needed option and way to use split screen.

Without Pre-Defined, easily accessed Split Screens, I cant see using split screens, if to use them, I have to be distracted while driving, to mess about with manually splitting a screen, using the normal manual Android screen splitting methods, ending up with a FCC side that looks squashed down and difficult to read and use.
[Android Head-Units] rigattoni:
I just did it the way I show in the attached video for now.

The first part shows the solution with my Tasker script and the 2nd part shows the misbehavior of the implemented version...

It´s a bit laggy because I use scrcpy to work remote from my laptop on the unit. ;)
[Android Head-Units] ric69:
"Run in split mod in app's settings" seems broken since last update when FCC is full screen. Waze is opening in full screen and minimise. Also FCC is restarting in full screen.

But no problem when split screen is 50%.

+1 for idea of a split button or a widget :good:
[Android Head-Units] SpeedFire-:
Please try: FCC 3.365 v15
[Android Head-Units] SpeedFire-:
So you seems to have a FlyAudio device. Yes, in this case you only have an option to assign two custom actions (for single and double clicks).

Rockchip devices have more options for button remapping.
[Android Head-Units] Sacdroid:
Yes, i am using a FlyAudio device. It will be useful if you can fix the A2DP display in the widget.
[Android Head-Units] SpeedFire-:
Unfortunately A2DP information cannot be displayed on the widget because FlyAudio does not share this information.
[Android Head-Units] Sacdroid:
Understood. A long note follows, please bear with me

Right now the 'Player + Radio' widget works mostly but a little weird. I will try and explain. I use it to toggle between Radio, A2DP and an Indian Music app called 'Gaana'. This is the behaviour i see

- When Radio is selected on the widget, the HU switches to playing the Radio in background (last played channel) but does not show the channel information. The single Radio widget does work fine and shows the correct channel. Do i need to set the FM channel names for this to work ? i have not tried changing channels using the widget. Will try. I question... is it possible to skip channels and make the widget jump to channels only in the selected channel list.

- If I set the main application on the widget to 'Unknown ' the widget picks up the 'Ganna' app after i start it but does not show the song info. The Previous/Next/Play-Pause work as expected. It keeps showing some static song info in the display (not sure but i think it was the first song i played through the widget)

- If i set the main app to A2DP when i switch to Gaana app using the widget it shows the song info correctly. The song info changes when i move songs. The issue in this setup is that on bootup the launcher always start A2DP and i have to switch to 'Gaana' app. The Play/Pause button show incorrect info , as i guess its showing the state of A2DP stream.

Is it possible to try and fix the behaviour of not showing the song info when Unknown is selected. The launcher pulls the same information but only when the widget is set to A2DP.

Other minor things

- The mini map does not show the street name. Is it a limitation with the provider not supporting street names in India ?

- Is it possible to trap events from the notification generated by the navigation app (google maps) and display them in a separate widget on the main screen (things like next turn, ETA etc..) and maybe even overlay on the mini maps.

Something that new users might find helpful.

- you might want to provide some packaged screen layouts. Can help new users get started quicker. Having said that i just wanted to add that i personally found it very easy to setup. But i like the app a lot and would like to see it get better packaged as well.
[Android Head-Units] Roerbakeitje:
Almost everything seems start good by first boot.

The music starts ok. Only don't display the the good title and not hylight the the player buttons.

I have set status bar hidden. When push on my steering wheel. A button . The status bar is not hidden any more . When push the home button than its gon again.
[Android Head-Units] SpeedFire-:
Wow, what a detailed report! Thank you!

I will try to answer some of your questions:

1. Regarding player. 'Unknown player' is kind of a temporary options for those players which are not officially supported by FCC Launcher. It may not work as well as supported players. But I will look at this again. Could you please send me a link to your music app (or attach apk if possible).

2. Mini map uses two sources - built in android geocoder and OpenStreetMap. If nothing is found - then it seems there is no information in both of these sources. In other cases you need to start moving to get the street name.

3. Even if it was possible to get turn-by-turn navigation notification, there is a significant risk for the launcher, because of the licence restrictions for custom implementation of Google map (it is prohibited to use it for routing or navigation). Even my current implementation is questionable in this case and I would prefer not to increase this risk.

4. Pre-defined layouts is a good idea and I am thinking about this. Thank you.
[Android Head-Units] SpeedFire-:
1. Yes, we have some issues with music autostart for some players, trying to find the source.

2. You're just in time. Exactly this will be fixed in the next beta. We will have a very nice full screen mode. No jumping status bars, no reaction to volume change - looks very good!
[Android Head-Units] SpeedFire-:
New beta is uploaded to the market:

- Completely rebuilt Full Screen Mode (previously called as 'hide statusbar'). No more 'jumping' status bar. No weird reaction to volume change. Stable full screen behaviour.

- Wheel button small fix (previously Back action was called even if no action was assigned).

- Some other small fixes.

Beta: beta-2.458

And here is a small experimental file:

FCC Starter for Rockchips. This small file could potentially help to run FCC Launcher earlier after wake up. Please test and respond if you have noticed any change (I will consider to upload it to the market if it really helps): FCC_RockStarter_0.25.apk
[Android Head-Units] Sacdroid:
here is the link to the app on playstore : https://play.google.com/store/apps/details?id=com.gaana

Can you also please look at Radio channels not being displayed in the player+Radio widget.

I will try out the new beta tomorrow. Have seen minor issues with the status bar, will be good to use full screen. Have a few enhancement requests

- Add App drawer button in the right panel. Maybe make the right panel customizable. Include/Exclude standard apps (Maps, Settings, App Drawer, Voice Search), Include Custom Apps, Change width of the panel. Would love to use it like a dock (having Screen Off, AppDrawer,Settings, Maps)

- Add the trip parameters to a single widget and provide an option of including the stationary time in the calculations.
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

By the last beta is it useful to remove fcc starter ? Before use rockchip edition?.
[Android Head-Units] SpeedFire-:
FCC Starter (from the market) was for FlyAudio devices and not Rockchip. So this app did nothing. Yes, you need to delete that old app.
[Android Head-Units] Roerbakeitje:
Rockchip starter service is running great. I can use waze also again. Fcc is recovered faster that before.

It's good to have this on the pkaystore.
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION] little question the starter rockchip is it autostarts on boot?

The player autostart last player is Theresa a fix coming.
[Android Head-Units] Petrovych:
Fixed, not published yet.

Отправлено с моего SM-G950U1 через Tapatalk
[Android Head-Units] SpeedFire-:
Just uploaded a new beta:

- Players autostart fix for Rockchips

- Changes to button press effect in Player widget (you can also select accent color for pressed state)
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

Now the button image is set at center of pattern .

Is it possible to set it to fill pattern?

I have some button image that can connect to each other . Now I have some emty spaces between it.
[Android Head-Units] Prometheus_au:
Does this launcher work with Intel Sofia processor head units?

Looks great!
[Android Head-Units] Petrovych:
There is no official support, but in general it should work. The main feature of the launcher is a deep integration with the Platform - direct calls, buttons interception etc. These functions maybe will not work and only author could provide more details.

Отправлено с моего SM-G950U1 через Tapatalk
[Android Head-Units] davidbemenderfer:
External Devices

Would it be possible to add signal outputs to control external devices? I attempted this by developing with an oDroid XU-4 but could not get the quality that I am looking for. Examples would be to have either 5 V or 3.3V signals to control windows, locks, seat heaters, etc. Any thoughts?
[Android Head-Units] SpeedFire-:
This is an interesting idea. If I understood you correctly this is, however, more dependent on your signal processing unit. I don't think launcher (or any other third party android app) can directly send an electric signal to some outputs (btw where do you want to connect it to?).

What I can do is to create a widget which will send custom broadcasts to the android system. But your device will need to be able to receive them, process and generate a signal.

Maybe MCU unit on Rockchip device may generate some kind of compatible signals which you can use. I mean you can theoretically connect your slave device to your dvd drive contacts (for example) and send a command in android to open/close dvd disc. This should generate an electric signal on those contacts. Is this what you are trying to do?
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Thanks for adding the Background STYLE to the page widget.

However, this has highlighted a difference between setting a Background Style to an APP Button , and setting on for a Widget that displays as a button.

In words, the difference is that you can set a different background color to the APP background Style, and a different background color to the same widget without the Style.

So the color set when the background style is active, it only sets the background color of the Style (the actual button), while the Background color where the button sits (set with no style selected), remains the color that was set when the App did not have a style.

Yes.. complicated to explain .. so I made a video, that shows the difference between making a background styled APP Button, and a background Style Widget Button, and how the WIdget Button does not end up with the same desired button shape & coloring as the APP button.

https://drive.google.com/open?id=13XjVvXnhdOEygZn1jEupZsdheaj5gTx7

Basically, when Background style is not set, the background color is set for the whole Rectangular area occupied by the APP area on the screen.

Then when add a background style, the background color (say different color), only acts on the active (Button shape) of the background style.

This is so with an APP, but not so with a widget, where the background style color acts on the while area occupied by the APP Area on the screen.(and not just the button style)

A lot easier to understand when you watch the Video !!!

Actually, when you get the Splash Screen for the Video, before you run it, you can see the APP button on the right (as desired), but on the Widget button on the left, one cannot achieve the corners being the screen background color, so you loose the rounded button effect.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

I found 3 additional points which needs to be looked at:

The button size is slightly different as you can see in this screenshot. The splitscreen button is an app button and GPS info is a widget. The weather widget has the same size as the app button. I pulled a yellow rectangle to visualize the difference...

The weather icon has a fixed size and cannot be centered... or moved to match the button size.

Widget icons can not be resized.

View attachment 5024701

View attachment 5024703
[Android Head-Units] tonimontoia:
congratulations rigatoni I like this skin compliments, I don't know how to do it like this
[Android Head-Units] SpeedFire-:
Yes, video was very easy to understand! I hope I've fixed this.
[Android Head-Units] SpeedFire-:
Here is a new beta FCC 3.365 v16:

- Fixed issues found by [MENTION=9325785]Scopesys[/MENTION]

- GPS widget size fixed

- Weather widget icon size can be changed now
[Android Head-Units] rigattoni:
Weather icon can be resized... :good:

But it sticks at the left side of the button. Centered would be nice. Or at least a setting to move the icon and text.

...sorry forgot to add the screenshot...

View attachment 5024847
[Android Head-Units] Scopesys:
FIXED -- Thanks ..
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

I have found a strange behavior:

Yesterday I added a screen with some OBD widgets from Torque Pro and 1 OBD widget from FCC.

I then deleted the complete screen so I would expect that all widgets should be deleted too.

Now, I get a toast message every minute: "OBD2: No bluetooth dongle choosed".

I deleted Torque to check if the toast is from Torque, but it seems to be from FCC.

Could you please have a look at this behavior?

Attached the current backup which shows this behavior.
[Android Head-Units] Scopesys:
back in Oct 2019, another FCC user reported the same thing, and got the reply from Speedfire- to just delete all the OBD widgets and then reboot.

It was not clear that that actually solved the issue back in 2019, but it does indicate that your issue may have been around for some time, and is not a recent bug addition.
[Android Head-Units] rigattoni:
Yes, if there would be any OBD widget, that would help... but unfortunately there is none on the screen. I checked it with showing layout bounds in developer options... there is none! :confused:
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: After KoTiX2 released NavRadio+ 1.57 on his beta channel five days ago with initial support for FCC launcher and informed you about this, he now released version 1.58 officially on Play Store:

Unfortunately we didn't get any reaction from you yet about implementing the necessary workaround in FCC, as you announced in post #6070.

I know that you are also working on other things like better split screen support and widget adjustments, but to get no reaction from you about NavRadio+ support within severel days is a bit frustrating. :(

There are by now at least eight XDA users who asked for NavRadio+ integration in FCC ( [MENTION=378852]dagosjt[/MENTION], [MENTION=1976910]roydestroy[/MENTION], [MENTION=682191]liamstears[/MENTION], [MENTION=10002693]SoberXDA[/MENTION], [MENTION=8107381]parisisal[/MENTION], [MENTION=3459832]Tbizzness[/MENTION], [MENTION=2139269]RolandE1204[/MENTION] and me) and surely there are more FCC and NavRadio+ users who are not on XDA but would like to use the combination of these two great apps.

So once again: Please! :)
[Android Head-Units] Scopesys:
Date-time widget editing Bug

When entering editor of this widget, with the time disabled, the date picks up the font size of the Time, and not the day when entering the editor.

Attached is a "Video" ... showing this ... (yes, with Covid-19 floating around, plenty of time at home to play with Moviemaker !!)

https://drive.google.com/open?id=1i08WCEEd_zjJnAIi-KBUQYAVazFCFr6T

Just to clarify (after re-watching the video), The Time Display in the background, when entering the editor, is being resized to the time font size, NOT the actual time SLIDER, which remains correct --

but if it does display the bigger time font size, if you do not move the date slider, before exiting the editor, the date will be set to that Time Font slider value,

If you were using BOTH the Time & date to display in a single widget, this would be an even bigger issue, as you may well not want them the same size, leading to all sorts of confusion and apparent font size changes when entering the editor.

Come to think of this, I have seen this happening when editing the widget on a screen where both the Time & Date were displaying in the same widget.

After editing the widget (for whatever), suddenly on the Screen, the Font size had jumped to something different, even if i had not edited any of the font parameters !!
[Android Head-Units] bajoseph04:
It looks like with the latest XDA beta builds, I could see the previous issue where the FCC splash screen popping up every time you press the home button has recurred. I'm not sure if this is after the introduction of the split screen since I don't use it. The latest beta build in the play store works perfectly. So I had to uninstall the XDA beta and go back to the play store one. So I would request [MENTION=1633144]speedfire[/MENTION], please don't push any of these builds to the store unless that are stable enough.
[Android Head-Units] parisisal:
I totally agree.

FCC currently is the best launcher (i've the paid version).

NavRadio+ is the best radio player.

Currently i'm using both without integration, I also noticed that FCC puts in background NavRadio+ :

- on launch

- sometimes when a I change a station

Salvo
[Android Head-Units] rigattoni:
I just restored FCC to a former backup and restored again the one from yesterday.

Issue is gone.
[Android Head-Units] Scopesys:
With all this Forum Chat about NavRadio+ being so "Good" -- "THE BEST", I broke down purchased it today.

1st Impressions were that it was not that great ... sorry. (That's 2 hours of my life I will never get back !!)

Apart from that fact it does not integrated well in FCC (yet), It's display did not seem all that great to me. :(

(1) No real options to alter its layout.

(2) No radio station logo's for my USA state ( Maryland), so I tried a few from another State, and was not impressed with their quality of design.

(3) Tried to use my Logos that I had done for FCC ( 500 x 500 jpgs). It seems that trying to load a jpg as a logo into NavRadio+ causes it to CRASH.

(It seems that the NavRadio+ logos NEED to be PNGs ??? ) PITA

Then, at the end of the day, assuming that it gets fully integrated with FCC, I cannot see it offering anything EXTRA worth having, over the Head_Units default radio APP.

The only thing it seems to add, is a "Vertical" PRESET Radio Station list. assuming one opens the app in Full screen.

Even when I did get one of NavRadio+'s distributed Logo attached to a local radio station, it was not impressive in the APP's display, and also did not display the correct size in FCC. (Which might be fixed in due course).

And then for some reason, when NavRadio+ had issues, (maybe Crashing), FCC went back to using the head units default radio App ... GO FIGURE.

Anyway, returning to the head unit's Default radio App was a "breath of fresh air", as it works well, and really does everything one can want.

Well done to the NavRadio+'s developer for getting his app to work with a number of head units Radios, but the actual APP leaves a lot to be desired, and really does not add that much to the Radio ( In my opinion .. others may think differently )
[Android Head-Units] nimslo:
Route Widget: Bug if using Google Maps

[MENTION=4292729]SpeedFire-[/MENTION]: unfortunately, for about a year, the "Route" widget, which should show the driving instructions of the navigation software on the FCC launcher screen, does not work properly if using Google Maps. The text instructions are displayed correctly, but instead of an arrow showing the next driving operation, there is only the general navigation logo. (If using Sygic, the widget works flawlessly.)

Probably the bug is caused by a software code change of Google Maps: other car launchers and HUD apps initially had the same problem. But these other apps got fixed meanwhile, not so FCC launcher. The error occurs on my car radio with Android 6.1 as well as on a smartphone with Android 7.1, that I used for test purposes. Uninstalling and totally new installing the latest regular Play Store version 3.362 of FCC, without using a previous backup, has been unsuccessful. The bug is still not fixed. I really like the FCC launcher,I like it very well. I also paid for the premium version and I don't want to switch to another launcher. But it should work minimum like it used to work when I bought it. For many users It is really great, that you have developed so many new features which can be used at no additional cost. But for me, it would be even better if the "old" feature "Route widget" finally would work again. I would appreciate it very much, if you would pay attention to this matter.