yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kramttocs:
Thanks for adding that! I knew my memory was missing something and it was bugging me - the different widget styles making some of those setting unnecessary. Like you said, that makes the setup even easier.
[Android Head-Units] NITRO1982:
[MENTION=4292729]SpeedFire-[/MENTION]

Hello from Germany, I use the GALA adaptive volume control from the FCC Launcher for my CSN2 unit. Would it be possible to set fixed values at fixed speeds instead of increasing and reducing the volume based on a fixed basic value? Background: after several GPS losses through tunnels in quick succession, the volume increases to an unbearably loud level. Turning the volume down doesn't help anymore, because the FCC keeps putting it up to a brutally loud value. The only remedy is to deactivate the dynamic volume control. With my last radio with fixed volume values at fixed speed values, there were never such problems.

Otherwise great app and best regards :)

not so important CSN2 things: BT and battery voltage widgets do not work.
[Android Head-Units] ric69:
New app launcher is really cool thanks a lot for your hard work [MENTION=1633144]speedfire[/MENTION]

Need a wallpaper in background or blur settings now ... I'm joking its perfect for now and I'm sure you have already thought to this :good:
[Android Head-Units] Scopesys:
Battery Voltage Widget does not work on my Px5 Eonon unit either, but I am pretty sure that is a failing of the unit, and not FCC.

But unlike a cell Phone or a tablet, the car has a Voltmeter on the Instrument panel, so for me, not Battery Voltage Widget is a non-issue.
[Android Head-Units] Mickey4Mouse:
thanks for the hints with a second player widget, that would never have came to my mind (too much fear about interferences between them).

i didn't add a second player in the past by my own, is there a skin out there with this solution built in? Anyway, i will give it a try, doesn't matter how it works, if it works ;)

but now to the interesting part of the evening (here in Germany):

since when is the GALA/adaptive volume working for CSN2 models???

THIS is why i changed to FCC but it didn't work, even the "simple" volume control widget is without any functionality.

[MENTION=9129546]NITRO1982[/MENTION]: do you have a DSP or "naked" modell (mine is without DSP, i wasn't aware of this when i bought it :( )

"unfortunately" we just had a typical german barbecue with a beer of course, so my test has to be postponed...

edit: the BT widget doesn't work on my CSN2 for sure (tested it with the latest beta version (installed from playstore yesterday evening)). And yes, the BT settings are correct, i was listening music via BT while the FCC widget said: unavailable
[Android Head-Units] NITRO1982:
I have a naked model without dsp from erisin px5/CSN2, with fake android 10 rom. Like i said the volume increases fine from basic level 9 in steps like +3, +3, +2 at speedwalls like 50kph, 70kph, 90kph...and reduces after a delay of 1-2 seconds if the speed decreases. BUT if i drive on highway with ~80kph and the gps come on off on off in some minutes FCC does not reduce the volume but increase even more. Example: in front of tunnel 80kph/volume level 16, after tunnel at same speed of 80kph the volume increase +3, instead of leavin the value of 16.

Greetings!

The Battery In status bar shows well, but i dont want the status bar active. My Car does not have a voltmeter.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION],

I´m not sure what that means, but on Fcc start always shortly the app name switches to "Packet Installer" instead of "Fcc Launcher" in the top bar.

When switching to split screen, in between the switch I can read "Overview.". The issue is the dot at the end of the "Overview".

Other visible issue is, that with switching to the split screen and back the player focus get lost. Music is still playing in background, but whether the player is set to active, nor song information are given until you activate the player on the widget under the album art.

Just to may answer your upcoming questions:

I use Tasker for toggling between split and back

I don´t open a new instance of Fcc

I just switch between Fcc pages (the page in split screen is special build for the split screen... and yes the split main screen looks terrible if it´s shown on not splitted screen)

...argh... every now and then you can´t add attachments in XDA...

Main screen in split screen

Main screen in normal mode

VIDEO
[Android Head-Units] Scopesys:
I agree with you, putting Text on the Player Widget Artwork, is hard to read, especially with some artworks, so I keep the Text separate,

I have 5 Player widgets on the same HOME page screen, and everything works fine.

Yes, I also thought that this was asking for trouble, but I was quite amazed that all 5 work fine at the same time, with no interactive adverse effects.

Also, a few of my other pages have the same " Player Widget: SONG" and "Player Widget: Artist" text at the top

Very strange: Suddenly, any Graphics that I upload as "Attached files" .. cannot be seen !!!

(EDIT: Now today July 18,2020 they are working again)
[Android Head-Units] Scopesys:
test -- Today Image attachments are uploading OK .. Go figure (Thanks to whoever fixed that )
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: I'm coming back to my post from June 28th

because I now solved the mystery. :laugh:

The thing is, there are two places to assing MODE actions:

FCC settings -> System -> Steering wheel keys -> User defined MODE action are stored in mode_intercept_app[1-3]

The MODE widget has its own settings (opened by long-pressing on it) which are stored in mode_app[1-3]

I forgot about the second place to assign MODE actions after making my FCC Mode Action app. Since I'm now only using the Mode Action app to cycle trough the modes, I deleted the MODE widget and never looked into its settings again until yesterday - assuming that the MODE actions can be assigned via the FCC settings.

But why are there two places to assign MODE actions? Is this a bug or a feature, i.e. do mode_intercept_app[1-3] and mode_app[1-3] have different functions?

If the latter is the case, please explain the different functions, if the first is the case, please fix (unify) it.

---

As I just wrote, if you use the MODE widget to set up the three players, the FCC Mode Action app is working fine.
[Android Head-Units] Mickey4Mouse:
i'm right back from a short test ... disapointed in all points :(

1) i would like to add a second player widget, if there was a player widget available, it isn't...

2) speed adaptive volume (still) doesn't work with my PX5 CSN2 (latest FW and MCU), even the volume widget is without any function

3) last i had the hope something changed regarding the missing bluetooth functionality, maybe the "unavailable" is just a cosmetic display error. But no, all other apps are able to use BT (Torque, BT-Music), not Fcc or any of its widgets like OBD2. For example Torque(lite) shows some basic data like revs but Fcc doesn't.
[Android Head-Units] rigattoni:
To be honest: the disapointment is no problem of Fcc...

What did you choose on setup?

CSN2, I think no you did not!

Because all issues you have (without no.3) are no issues, they work perfect.

No.3:

Come on... what is your problem with that missing BT-Icon and what issue are you aware that BT doesn´t work?

The only problem is, that the BT-stack settings are not yet implemented. So keep calm and stay tuned. It will be implemented soon or later.

So please take your time and get familiar with Fcc...

Here you can see my desktop on a CSN2 with Android 9, newest firmware and MCU... and what can you see there?

At least 4 player widgets,

the volume widget

automatic brightness widget

Satellite widget and some other stuff.

So... you are running in the wrong direction...

Argh... fu** once again no pictures visible. Please admin get that fixed.

https://www.dropbox.com/s/0wzselgqdvxlqkt/Regular_Main.png?dl=0
[Android Head-Units] Mickey4Mouse:
could we take over the agreement from the german board and you don't try to answer my posts, please?

it doesn't make sense at all. It was YOU who said: adaptive "volume definitely works", the next day: "no it doesn't work on CSN2", now the next 180 degree turn and it works again...
[Android Head-Units] rigattoni:
:D:D:D

Please... If you are not able and/or not willing to learn anything... This is your part. But don´t post such a nonsense.

I´m out.

...and be sure: If you start the same sh*t as in the German board, I will give the needed answers.

Unbelievable...
[Android Head-Units] Scopesys:
Better still, take your arguments and fighting/bickering to Private messages.
[Android Head-Units] okij:
Seems like I have to get some popcorn and read the German board... :D
[Android Head-Units] dnfm:
It seems the player widget doesn't work sometimes (whenever it feels like it), so sometimes I get album covers and notifications when songs change in spotify/my player/the radio stations, and sometimes I don't.

Also, it seems there's at least one program whose widgets don't work right. I have widgets for torque I use for putting obd2 stuff on my launcher. They work fine in nova launcher, but they don't show up at all in FCC (they just disappear)... BUT! If I start nova launcher, and then go back to FCC, they show up! But I can't move them, resize them, or do anything with them because they don't respond. Pressing on it and holding down just brings up the FCC menu instead of letting me touch the widget.

I'll make a youtube video so you can see what I'm talking about.

(The other issue I have is the bluetooth appearing as disabled on my csn2 unit, but I noticed in previous comments that that's still a work in progress.)

edit Of course now I can't get the player notification issue to happen because I'm trying to, but I was able to get a video of the weird widget issue. See this video:

https://youtu.be/NduriCet2O4
[Android Head-Units] Scopesys:
[MENTION=2171475]dnfm[/MENTION]

[MENTION=4292729]SpeedFire-[/MENTION]

I have not recently played about with]Torque widgets but that is exactly what they are -- TORQUE Widgets, not FCC Widgets.

FCC widgets are designed to have properties that can be edit in FCC. Non FCC widgets are just that-- WIdgets that are NOT FCC widgets, that while they can be placed on a "Screen" (potentially of any launcher), do not magically inherit all the editing properties that FCC Widgets have been designed to have.

I therefore believe like many other widgets, that the Torque Widgets need to be defined and set up in the Torque App,and then exported as a widget, and then placed on a FCC screen.

You can alter their size in FCC, but getting to the FCC resize mode is tricky, as the widget often wants to go to its "Torque WIdget" configuration screen.

You have to hold on the widget for a very precise time to catch the FCC Edit size mode. (Unlike other FCC widgets, where the Hold time is a lot less critical)

My " Historic ;)" car does not have Can-Bus, so most Torque gauges are of little use, apart from the GPS ones.

For a time I was using the Torque COMPASS, and seem to remember the limitations that it had,, looked Pretty, but Torque Widgets also seemed to upset FCC and cause running issues.

When Speedfire- added the FCC Compass, I stopped using Torque Widgets.

BTW: FCC does have some Can-Bus widgets features, but I don't believe they are fancy gauges like Torque.

UPDATE:

So I just tried Torque again + Torgue Widgets, and I found that on my system it seems to have EXACTLY the same issues as on yours.

Had to start another launcher, and go back to FCC, to see the widgets.

I was able to re-size them, but it is VERY tricky. You have to hold on the widget for EXACTLY the right amount of time, or you either go to the WIdget Setup, or to the FCC edit .

Re-starting FCC did not help to bring back the widgets to display.

Re-Booting did not help either.

Only thing to make them display, was to switch to another Launcher first, and then back to FCC.

I am reasonably sure that say, 1 year ago, this was not an issue, as I used the Torque Compass widget, and it always loaded and displayed fine.. but a lot has changed in FCC over the past year.
[Android Head-Units] okij:
Yes, this is still an issue.

[MENTION=4292729]SpeedFire-[/MENTION]: Please have a further look after this if you have some time.
[Android Head-Units] bixxewoscht:
Not able to buy Pro-Version

Hi [MENTION=1633144]speedfire[/MENTION].

I have one of the vertical screen FYT intel 5683i Units and I'm trying to use FCC with it. If i click buy pro version in the settings its just going back to the homescreen and nothing else happens.

I this still an issue because the app was renamed?

Or is something else going wrong?
[Android Head-Units] Scopesys:
Maybe try updating to the latest version on Play Store, and then try to purchase from that version

If that does not work, then that is something Speedfire- should be highly motivated to fix .. -- Lost sales !!
[Android Head-Units] bixxewoscht:
It is the newest version, I downloaded it from Play Store again today.
[Android Head-Units] Scopesys:
Then it Sound like this is something that Speedfire- will need to look into.
[Android Head-Units] mike.b.hole:
TPMS widget not showing numbers

Hi, this has worked for me in the past but after a head unit reset and re-install of FCC it's not working at all.

The TPMS app works fine but the TPMS widget on the home screen does not show the numbers just a -- where they should be.

Any setting that I am missing that will be causing this?

Cheers,

Mike
[Android Head-Units] roydestroy:
[MENTION=4292729]SpeedFire-[/MENTION]

I don't know if this has been mentioned before but after the change with the ability to have split screen with fcc, it appears in the recent apps dialog and this causes it to have some unwanted functionality. For example, I am using Poweramp as a background app for music with fcc. When I turn off my engine and then start it back up Poweramp only restarts playing in the background if I use the option fcc provides in order to restart player on launch. However if we have to have fcc relaunching every time the engine restarts (which we didn't need before) it cause some glitching with Poweramp since it probably presses play multiple times because fcc is restarting as well, which in turn causes Poweramp to skip tracks in the beginning. Also, if I chose not to have fcc relaunch when the engine starts (which works well with Poweramp and everything loads fine) then if my last app before engine off was a full screen app (ex. Maps or radio) it doesn't load fcc in the background which causes the wheel buttons not to function since I have them assigned through fcc. When you go to the fcc app like that it reloads the whole fcc interface and then everything works fine.

tldr: is there anyway to have an option to disable the split screen behavior? Some of us really don't need it and is causing us problems.

Thank you in advance.
[Android Head-Units] Scopesys:
Was this after updating FCC to a newer Fcc (after Google restored the app as Fcc to the Play Store) ?

Try removing the TPMS widget from your screen, and then putting it back in again ..
[Android Head-Units] Th0m4s88:
I found a small problem today. I'm using a Dasaita PX5 headunit with hal9k Android 8.0.

If I start the a2dp app as a quick player in the fcc player widget it stays minimized and the Bluetooth music from my smartphone starts but it won't react to my steering wheel keys.

I can more or less fix that problem by opening a2dp in full screen and minimizing it again. Then it starts reacting to the steering wheel keys.

If I start the app without using the fcc player widget it will react to my keys right from the start.

I guess the a2dp app needs to be started in the foreground to listen to steering wheel keys (as long as it was in the foreground one time it can be sent to the background and won't stop listening to the wheel keys).
[Android Head-Units] Scopesys:
There appears to be an ever increasing number of Widgets, whose APP need to be started before their widgets will works , which may make perfect sense, ?

If they have their own widgets, often it would seem, that the App gets started by the widget, but maybe not always, or maybe not specifically always in FCC.

FCC has an option to start a number of Apps when it loads, -- I tried this with Torque, to get the Torque Widgets to work, but FCC seems to start the Auto-Start Apps in the foreground. ?

Would it make sense, and if so, is it possible for FCC to start those Apps in background, or at least have the choice , to have them start up in background or Foreground. (Or maybe start in Foreground, and then get sent to background). ( I do not really understand all this, so maybe I am talking rubbish :confused: )
[Android Head-Units] Paul1965:
Have you tried adding a step to auto-launch in Fcc to go to the Home screen after the last app is launched? That's what I did, launching Torque then SqueezePlay and it works great.
[Android Head-Units] stephanko:
Hi! I upgraded my MIC AV8V5 (PX6 Rockchip) with ModInstaller and HCT4-Image (HCT4_RK3399_10.0_ota(2020/06/12) MX/WITSON) from Android 9 to Android 10, MCU-version: MTCE_TONE_V3.57_3. After that, I installed and configured Fcc-Launcher. Everything works great except the automatic brightness widget. When pushing the widget, itself changes but the brightness of the display remains the same.

In the android system app-settings, the Fcc-Launcher is enabled to change system-settings.
[Android Head-Units] kramttocs:
A couple pages ago I reported this and confirmed that if I went back to an older version it worked, upgraded, and it stopped. Wasn't sure if it had anything to do with the rename since it stopped right around that time. [MENTION=4292729]SpeedFire-[/MENTION]?

---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------

I think the auto brightness and the volume by speed features don't work on all devices. Would love to see this fixed though so it's more generic if possible. They don't work on my atoto s8 so I am creating tasker profiles to address it in the meantime.
[Android Head-Units] dnfm:
My working theory is that other launchers send some sort of intent to new widgets that causes it to do its initial update/start working that FCC doesn't.
[Android Head-Units] herobkse:
Hello guys,

Is it normal that my PX6 head unit takes about 2min to finish loading minimap + 5 widgets from a cold boot? I did not expect much time like that.

Is there any solution to reduce the loading time (e.g hide minimap, keep less widgets...).

Thanks.
[Android Head-Units] mike.b.hole:
Thanks for asking but, looks like a problem with the latest release that has been reported elsewhere.
[Android Head-Units] marcus82:
i think I've the same issue with ALEXA widget
[Android Head-Units] mike.b.hole:
Thanks. So it looks like we will have to wait for an update to the app then.
[Android Head-Units] bajoseph04:
Thanks for bringing this this topic again. I had reported this few times before but has gone unnoticed without any response. So finally gave up. I can live with this issue and if it's something unbearable I can also live with the default launcher. So not a deal breaker except that I paid for this app while it was functioning well and don't mind leaving it behind just like many other apps for which I pay and don't use at some point of time but still feel happy that I helped someone respecting their work.
[Android Head-Units] Scopesys:
Nothing to stop you from saving your current settings, and going back to an earlier version that you have have found more meets your needs.

Typically, whenever Speedfire- announced a new update , he posted a download link in the forum, so you can easily go back in the forum to a time of your choice, and get the version current at that time.

Note: when you install that earlier version, it will automatically check with PlayStore, and if you have purchased the App, it will turn on the Purchased features.

Then you can always install a later/current version when you read in the forum, that the issues you may have been having, have been addressed, and hopefully end up being fixed for you.
[Android Head-Units] okij:
Well said, but there e.g. is no FCC version with NavRadio+ support that doesn't have the drawbacks which have been introduced with the SplitScreen support.

So going back to an earlier version is not always a solution.

I still hope that [MENTION=4292729]SpeedFire-[/MENTION] implements an option to disable SplitScreen support, so that FCC fully acts like a launcher again (so e.g. not being shown in recent apps and by this not easily to be closed/killed.)
[Android Head-Units] Scopesys:
LOL.. yes the Addition of Navradio+ support was very nice -- I delete that part of the post (to keep it short & sweet) !! -- the part where I said that the big DISADVANTAGE of going back to earlier version, is that you loose any NEW additional feature that do work (ie NavRadio+ support)

"Split Screen" is a marvelously technical feature to have achieved in FCC, but having tried it, (even if it did work Flawlessly), I found it just adds too much confusion and a level of complexity, that I do not want to deal with , especially when I am driving.

Totally given up on the idea that an existing FCC screen should be "resized/distorted" and be squashed down to allow for split screen.

If I was to need a second APP, displaying and running in a Split screen Mode, I would want it running along side with a FCC split screen, designed to fit in it's split screen area.

Then I would want that SPLIT screen to split when that specific page was selected, and NOT be able to unsplit, no matter what I did on the APP side of the screen, until I intentionally left that FCC Split screen page.

And finally, a positive and 100% reliable way to tell the system which side of the split screen I was controlling, (Probably some sort of Visual Indicator on the FCC side)

It just gets too complicated, and require too much attention to control, especially when driving, so I am more than happy to always run in Full screen, and either be displaying FCC full screen, or a selected APP full screen.

Maybe there is an uncomplicated solution, but until there is, I am more than happy with a non-split screen, especially when it is so easy to switch between FCC screens and APP screens.

If I had a 12" wide screen display, I might think differently :)

Does not help that I am running Andriod 8, so I have to force the screen manually to Split screen

(I do not believe that FCC can do it programmatically - and I am not rooted, so forget Tasker )
[Android Head-Units] SpeedFire-:
Hello, guys.

In this version I tried to overcome Google's limitations introduced in Android 10 and 11 with regard to access to external storage (which affects backups). What is done:

- Now backups will be stored in /sdcard/Download/Fcc_Launcher/Backups/ folder. This folder should be accessible in Android 10+.

- Launcher will try to migrate old folder to the new folder when you try to backup or restore settings.

- Temporary backup folder required to zip/unzip backup files is now created (and then automatically removed) in the app's data folder not at external storage (this does not require any permission request).

- All other files are also moved to /sdcard/Download/Fcc_Launcher/ folder (for example offline MBTiles for MapBox).

FCC 3.420 v2

Please test Local backup / restore and Google Drive backup / restore with this version. If someone has an Android 10 head unit this test is especially useful.
[Android Head-Units] stephanko:
Just install over actual version?
[Android Head-Units] SpeedFire-:
Yes
[Android Head-Units] stephanko:
Backup over sdcard and Google Drive failed in my case.

All my sdcards (4GB, 16GB and 64GB) are not being recognized correctly by Android, so I think the issue comes from my installed image (HCT4_RK3399_10.0_ota...), but I don´t know.

Trying with Google Drive, error: "Fehler beim Versuch die Datei zu erstellen!, something like: "Error creating file".