yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ozgurliman2:
Fcc Car Launcher on Recents

Hi,

Is there a way to remove fcc car launcher from recents?

I have a task to clean everything from recents and it also resets fcc because of this.

Also is it possible to remove it from the Status bar?

Thanks
[Android Head-Units] kramttocs:
It's my understanding that this is due to the switch to an app vs a true launcher to support split screen. You'll see in the last couple of pages that it is a fairly frequent request to make that configurable.

Until that is done (if it is done), I don't believe there is a way. I think you'd have better luck with finding a way to make the cleanup task exclude fcc.
[Android Head-Units] bajoseph04:
I tried using macdroid which could hide any app from recent apps but seems doesn't work with a launcher... may be any others can try.

---------- Post added at 06:28 AM ---------- Previous post was at 06:26 AM ----------

Unless you use Navradio+ you can use the above version 3.362v14 which won't show up in the recent apps. This version was just before the introduction of split screen and works pretty well for me.
[Android Head-Units] HatManSan:
Headunits with 10.25" displays with 1920x720 displays are coming, hopefully by Christmas. will FCC scale or does it support other resolutions currently? Thanks
[Android Head-Units] Bob_Sanders:
720p is here already. I have one. It's 1280 though, not 1920
[Android Head-Units] TT_Vert:
Same, did this get resolved for anyone? It copies database and when It gets to about 95% on bar while uploading it just sits there. When trying to restore it'll get to 5% when trying to check google drive for possible data it can use. I ensured I can sync google drive w/ this device. Anyone know the last version where backup worked? I went back to 3.362v14 but it still doesn't backup to google drive. I've been getting some weird behavior out of fcc lately and want to perhaps revert back some.

Dave
[Android Head-Units] swyner:
After testing this version it DOES show up in recent apps at least on my Tesla style screen. It’s behaving no different than the most recent version where it doesn’t properly load from hot boot. Will go back in this thread and see if there is another version that is correct
[Android Head-Units] pr0l4m3:
#bugreport #bug #mediaplayerwidget

https://www.youtube.com/watch?v=iy51MQV4gJA&ab_channel=DamianMachliński

As on video still its problem with last beta and previous version with song widget, information about title and artist are no refresh, only album cover. On navradio working good, on poweramp working good, on stock player in android headunit working bad.

testing on:

- Android 9.0 Halek ROM

- Android 9.0 Stock ROM

- Android 10 Stock ROM

Headunit spec: PX5,4GB RAM,last version android 10.
[Android Head-Units] Scopesys:
No posts from [MENTION=4292729]SpeedFire-[/MENTION] for 2 month now :crying:

Hope he is OK .. or maybe a very long, well earned vacation.
[Android Head-Units] kramttocs:
It is strange. His profile shows he was online yesterday so maybe he is taking a vacation but silently monitoring the thread.
[Android Head-Units] bajoseph04:
OK. Please try the stable version here..

https://m.apkpure.com/fcc-car-launc...enter/download/3362-APK?from=versions/version

Seems to work much better.
[Android Head-Units] okij:
It's the same in the FCC thread of the Russian 4pda forum (see link via Google translate), also there they are wondering where [MENTION=4292729]SpeedFire-[/MENTION] has gone.

It would be kind to get at least a short info from him... :rolleyes:
[Android Head-Units] bRkiX:
still the same...not launcher..

any older version guys?

cant find it on up2down and similar sites
[Android Head-Units] Scopesys:
Just go back through the forum and look at Speedfire's announcements and links to updates.

Go back as far as you need.
[Android Head-Units] okij:
Last stable FCC version without split screen support (not showing up in recent apps)

For those who are interested, I just did a small research on this thread about the chronology of split screen support in FCC:

The last stable version without split screen support was FCC 3.364v2, includes the fix for the crashing Google Maps SDK and was posted by [MENTION=4292729]SpeedFire-[/MENTION] on 24th April 2020:

On 30th April 2020 [MENTION=2534110]rigattoni[/MENTION] asked here for split screen support.

On 7th May 2020 [MENTION=4292729]SpeedFire-[/MENTION] posted here a video of an early alpha with split screen support.

On 8th May 2020 [MENTION=4292729]SpeedFire-[/MENTION] posted here FCC 3.365v2 as a first alpha version with split screen support.

So all users who want to use a stable FCC version without split screen support that acts like a normal launcher (i.e. doesn't show up in recent apps and doesn't do extra screen refreshes when hitting the home button, which are caused by the hacky split screen implementation) should use FCC 3.364v2. :)

Users like me who want to use the (still work-in-progress) integration of [MENTION=2734955]KoTiX2[/MENTION]'s NavRadio+ in FCC Launcher need to use the latest FCC v3.440 from Play Store, since the NavRadio+ support was developed in parallel with the split screen support and isn't available separately.
[Android Head-Units] bRkiX:
so thanx [MENTION=2534110]rigattoni[/MENTION] for all the trouble ???
[Android Head-Units] okij:
Well, he couldn't know if and how [MENTION=4292729]SpeedFire-[/MENTION] would implement his request. ;)

What bugs me is that an app that is called "... Launcher" (and for which I paid the full version) now technically isn't a launcher anymore. :mad:

I really hope that [MENTION=4292729]SpeedFire-[/MENTION] soon starts participating on this thread again (not just reading it) and fixes FCC by adding a switch to make it act like a real launcher again.

Otherwise I'm about to revert my 5 Star rating on the Play Store, where I explicitly praised his great support here on XDA, which was really exemplary. By now I think that it's a shame to not even leave a note here when vanishing for 2+ months, leaving his community (respetively his paid customers, if you see it from this point of view) in uncertainty. Edit: See post #7015.
[Android Head-Units] rigattoni:
:confused: phhh...

Yes, that he just has a look on nearly a daily base without writing a word leaves some bitter taste.

But may be there is a good reason for him to not write in here. We should stay calm and give him the time he needs.
[Android Head-Units] okij:
Just got some info from SpeedFire

Hey, [MENTION=2534110]rigattoni[/MENTION], [MENTION=9325785]Scopesys[/MENTION] and @ all other users here on this thread:

Today I wrote to [MENTION=4292729]SpeedFire-[/MENTION] via Telegram and just got the following reply, which he allowed me to post here:

I think that I can also speak for the other users on this thread that we are happy that you are fine and it's great to see you soon back here. :cool:
[Android Head-Units] rigattoni:
Thanks for the information.

I appreciate that he gave some update. :highfive:
[Android Head-Units] okij:
Poll: What do you want: a split screen functionality or a normal launcher behavior?

@ all FCC users on this thread:

Since today I was able to contact [MENTION=4292729]SpeedFire-[/MENTION] via telegram, I also asked him if he would be able to add a setting to make FCC a normal Android launcher again, i.e. disable split screen support for users who don't need it. He answered me:

I also asked him if he could maybe keep two different versions of FCC, but - as I guessed - this would be too much work to maintain.

Because of this situation [MENTION=4292729]SpeedFire-[/MENTION] now added a poll to this thread which is going until 2nd November 2020.

Please leave your vote on the poll, so [MENTION=4292729]SpeedFire-[/MENTION] knows if the mayority of the users prefer split screen functionality or normal launcher behaviour.
[Android Head-Units] kramttocs:
Glad to hear from SpeedFire!
[Android Head-Units] okij:
[Sorry, this post was first auto-added by the xda forum software to the poll announcement. I didn't want o mix the two posts up.]

FYI: I just voted for normal launcher behaviour, because [MENTION=4292729]SpeedFire-[/MENTION] needed to use some tricks for implementing split screen support, which make FCC not act like a normal Android launcher anymore.

On my PX5 head unit, this not only leads to FCC being shown in recent apps, but also to some other strange things like additional refreshes when pushing the home button and some flickering in the status bar where the name of the foreground app is shown.

I personally don't need split screen support on a launcher and rather prefer FCC to be as stable as possible.
[Android Head-Units] bajoseph04:
So I assume a switch in the app to enable the split screen functionality (for those who need that with the limitation) is not possible.
[Android Head-Units] okij:
Yes, exactly.

As I wrote, I asked [MENTION=4292729]SpeedFire-[/MENTION] if he would be able to add a setting for this, but he answered that it can't be done via a setting.

I guess that it has someting to do with the manifest file for the app or some other setting which must set before compiling FCC and which decides whether it behaves like an Android launcher or like a normal Android app.
[Android Head-Units] sousa_2005:
hi.

very strange thing happening to me:

Fcc radio frequencies, doesn't not match the original from FM radio app...

for example, FM radio says: 91.20 and FCC shows 256.82...

please, see the photo attached ...

anyone with this?
[Android Head-Units] TT_Vert:
Does anyone know if the google drive backup fix is something that is in the works to be fixed? Latest update didn't fix that. That's a really nice feature I'd love to have back. Especially since my SD backups somehow got borked so I am having to rebuild manually since my google drive backups are so old now.
[Android Head-Units] sousa_2005:
anyone with this problem?

tried 2 versions of FCC...

this happened after updating my SO in my headunit
[Android Head-Units] okij:
No, so far I didn't read about such problem on this thread.

What is SO?

Also, please write what MCU type and version your head unit is running on, so that users with a similar device can give you some feedback.
[Android Head-Units] vidiart:
I have the same problem with radio freg. No 101.3 bat something alse MTK 8227L with 2 giga ram 16 rom android 10?
[Android Head-Units] parisisal:
Hi Guys,

Could I ask you an update about NavRadio integration ?

I'm still having issue, i've to start the app many times on each car trip.
[Android Head-Units] kramttocs:
Is it force closing? If so have you sent a logcat to both devs? Might help them figure it out.
[Android Head-Units] Paul1965:
I now have FFC installed on a new EONON head unit running Android 10. Everything works great, but I would really like to reduce the gap from the bottom of the widgets to the bottom of the screen. I've tried dragging them lower, but all that does is force them to a 2nd page. I want to maximize the size of the map and still display the widgets at the very bottom. Does anyone have any suggestions?
[Android Head-Units] KoTiX2:
In last update of NavRadio I fixed the start service in background and other problems that can help a better integration in FCC.

Now we need a new version of FCC that start/stop the NavRadio service instead of launching the activity.

I sent a message to [MENTION=4292729]SpeedFire-[/MENTION] about this and I hope to have a reply sooner or later.
[Android Head-Units] HatManSan:
Purely inquiring after his welfare. Has anyone heard from FCC's creator at all?
[Android Head-Units] okij:
He's fine, please see my post #7015. :)
[Android Head-Units] KoTiX2:
NEW FCC version with NavRadio+ handling fixed

I'd like to say "thank you" to [MENTION=4292729]SpeedFire-[/MENTION] for his help making my app working with his FCC Launcher:

All the previous issues with FCC likeswitching between other players and NavRadio+, the start of NR+ in background, the audiofocus etc.. are all sorted out

The new version of FCC that can be downloaded from here: https://drive.google.com/file/d/1kebVx2gEj_9AZKEZd0cwY6r4GHZn_CBo/view?usp=sharing

It must be used in combination with NavRadio+ new version 1.89 that is coming up on playstore soon.

Older versions of NavRadio+ or of FCC will not work!

Thanks also to [MENTION=4916555]okij[/MENTION] who tested this releaseand reported me this:
[Android Head-Units] parisisal:
Hi,

i've installed the last version.

It works good, but a issue is still present : the music stops only one time after a cold start.

1) The Unit starts

2) Starts andorid

3) FCC Starts (all the widget are empty)

4) Manually I click on NavRadio+

5) Radio music starts

6) I press Home Button to show the launcher screen

7) The widget are filled by the radio info

8) The music stops << ISSUE >>

9) I click again on NavRadio

10) The Music Starts again

11) Click on Home Button

12) The widgets are updated with the radio info

13) The music continues to play (GOOD)

The issue is only at the first start of NavRadio.

I did a video : https://www.youtube.com/watch?v=-sh54eAkAxo

Thank you very much,

Salvo
[Android Head-Units] KoTiX2:
Which rom do you use?

I just tried on my unit and it's working fine.
[Android Head-Units] parisisal:
Stock ROM. I didn't performed any mod on my device.

Thank you,

Salvo
[Android Head-Units] dape16:
Thanks for work, both [MENTION=2734955]KoTiX2[/MENTION] and [MENTION=1633144]speedfire[/MENTION] but I still have the same problems, when running NavRadio+ 1.8.9 and your attached version of FCC (displays as 3.440_test). I use Hal9k 4.2.0.

I don't use any music player widget, just start the apps from icons on the FCC home screen. When starting NavRadio+ the app will either display for one second and close before starting, or start playing but then close, or keep running in the foreground and playing but close and stop playing in the background when switching to FCC home screen or directly to another app. It takes 4-5 tries before it will keep playing in the background.
[Android Head-Units] KoTiX2:
Be sure that you never run the original radio app or that fcc switch to fm radio itself.

Possibly make a video showing what happen and if you can send me a logcat.

EDIT: nevermind I found the problem. The fix will come soon ....
[Android Head-Units] herobkse:
Hello [MENTION=7644930]nimslo[/MENTION],

Could you please let me know how you can setup the route widget working with Sygic ? It's not working for me. I follow the steps below:

1) In Minimap settings > Set routing = Sygic

2) Add Route widget to homescreen

3) Add a destination in Minimap, for example: Work

4) Select Work destination on Minimap > Sygic is opened and route is tracing

5) Come back to home screen but the Route widget does not show any information

Is there any addtional step to be done ?

Thanks.

Tommy
[Android Head-Units] KoTiX2:
Here is another improved version of FCC (3.440_test8) that fix some of the issues with NavRadio+:

https://drive.google.com/file/d/1ptI1exyH01eeu_pP9Titth4GV2djrvo-/view?usp=sharing

It need NavRadio+ version 1.91 that is available on playstore.

Please test it and report any issue.

Tnx [MENTION=4292729]SpeedFire-[/MENTION] again for his help ;)
[Android Head-Units] dape16:
I have tried them today and so far everything is working 100 %. No more unexpected closing of the NavRadio+ app or stopped background playing.

Fantastic work, thanks a lot.
[Android Head-Units] okij:
Thanks a lot [MENTION=4292729]SpeedFire-[/MENTION] and [MENTION=2734955]KoTiX2[/MENTION] for the new test versions!

I've tried them today and also on for me they again are a big improvement, but not 100% perfect yet. ;)

As [MENTION=315511]dape16[/MENTION] already wrote, there is no more unexpected closing of the NavRadio+ app or stopped background playing, but I still have some issues when switching between players.

My setup is this: I have set DAB-Z, NavRadio+ and GoneMad Music Player as the three players in the FCC Player Widget. Also I have set the same three players in the FCC Mode Widget (correctly picked from the list "Start Players in Background").

My experience is that switching the players via the FCC Player Widget works really well now (let's say to 99%, the other 1% being minor cases of having to press on a player icon a second time to start it).

The problems start when I use the FCC Mode Widget to cycle through the three players. Then it often happens that either a player doesn't start or that the player is skipped and instead the next one starts playing.

It seems to me that the FCC Mode Widget still directly accesses the FM radio hardware, which then interferes with the other players. I observed for a couple of times that e.g. when cycling from GoneMad Music Player to DAB-Z there is no audio, but instead the FCC Player Widget shows a FM frequency like "99.20" (which isn't caused by NavRadio+, since it always shows the station name).

Interestingly, after using the FCC Mode Widget and getting these glitches, also the switching of players via the FCC Player Widget isn't stable anymore and leads to such problems.

So my conclusion is that probably all according bugs have been fixed in version 1.91 of NavRadio+ and that also most (if not all) according bugs have been fixed in the FCC Player Widget, but that the FCC Mode Widget still needs some love and debugging. [MENTION=4292729]SpeedFire-[/MENTION] :fingers-crossed:

For what it's worth, I took a LogCat after fiddling around with the new test versions this morning and this evening and attached it to this post. Maybe you can find some crashes or some other useful information for fixing the remaining bugs.

Thanks again to both devs for working this well together on fixing these issues! You made a huge progress in the last couple of days and the NavRadio+ / FCC Launcher integration is becoming close to perfect. :highfive:
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION] and [MENTION=2734955]KoTiX2[/MENTION]:

This morning I didn't use the FCC Mode Widget, but also when switching players just with the FCC Player Widget it happened that a FM frequency like "99.20" was shown in the display of the FCC Player Widget. When I then tapped on the graphic field of the FCC Player Widget, the stock FM Radio app opened! So there are still some interferences with the stock radio which have to be fixed in the FCC Player Widget too.

P.S.: Also disabling (freezing) the stock FM Radio app doesn't fix this, i.e. of course then stock FM Radio app cannot be opened anymore, but it still happens that afte switching players a FM frequency in the display of the FCC Player Widget.
[Android Head-Units] dape16:
I was not able to disable the stock FM Radio app (button greyed out). What I did was that I went into factory settings and selected NO for FM Radio, and then used a root file explorer to delete the stock FM Radio apk. Now there is no trace left. :)
[Android Head-Units] KoTiX2:
To disable original radio you have to go to factory settings.

There is no need to delete it. Disabling it should be enough. Maybe do a reboot after that.

BTW I'm curious if this happen even if you don't use/set NavRadio as player widget..
[Android Head-Units] okij:
Today after work I did the following test:

I unfroze the stock Radio app in TitaniumBackup.

I disabled the radio in the facory settings and did the mandatory reboot (at 17:56 in the attached LogCat).

I checked again in TitaniumBackup and saw that the stock Radio app was frozen again, therefore I assume that disabling it in the factory settings does also just freeze the Radio app.

DAB-Z started playing after the reboot, since it was the last player before the reboot.

Then I switched the players via the FCC Player Widget in the following order: DAB-Z (was already playing) -> NavRadio+ (started to play fine) -> GoneMad Music Player (started to play fine) -> NavRadio+ (didn't start to play, instead I saw "Radio 99.20" instead of "WDR2" in the display of the FCC Player Widget)

While "Radio 99.20" was shown, I tapped on the graphic field of the FCC Player Widget, but no player was opened, so I assume that FCC wanted to open the stock Radio app, which didn't work because it was frozen.

I attached the LogCat for you and [MENTION=4292729]SpeedFire-[/MENTION] to look at. Everything I described happened before 18:00 o'clock.

Yes, this way we might see if it's rather caused by FCC or by NavRadio+. I will set a different 2nd player tomorrow (maybe I'll just set DAB-Z as 2nd player too) and check if I can still provoke this bug. ;)

Edit: Can you download my LogCat? When I try it, I only get "404 Not Found", same with the one from yersterday - strange. Please tell me if I have to upload it somewhere else.

Edit 2: I uploaded it now on MediaFire: logcat_2020-10-22_18-19-12.zip
[Android Head-Units] KoTiX2:
Cannot download it.
[Android Head-Units] okij:
Hm, xda attachments became a bit crappy lately. :silly: It's really time that they start using the new forum software.

I uploaded it now on MediaFire: logcat_2020-10-22_18-19-12.zip
[Android Head-Units] ab1702:
I get these same problems on my unit which is a px5, however I don’t have navradio installed on the unit but I do use dab-z a lot.
[Android Head-Units] okij:
Today I did a test where I didn't set NavRadio+ both in the FCC Player Widget and in the FCC Mode Widget (I subsituted it with A2DP). And of course I had the stock Radio app disabled, so it couldn't interfere with my tests.

The result is that even after switching back and forth between the players for dozends of times, I couldn't provoke the bug that I described yesterday, i.e. I never saw "Radio 99.20" in the widget display and (from what I can recall) also the playback of the players went flawlessly.

After this test I set NavRadio+ again in the FCC Player Widget and I could reproduce this bug after only a few (less than 10) switches between the players.

[MENTION=8476598]ab1702[/MENTION]: I strongly assume that you then use the stock Radio app!?

My theory is that it doesn't matter if the Radio chip is being used either by the stock Radio app or by NavRadio+, because this bug can get triggered by both.

[MENTION=2734955]KoTiX2[/MENTION] and [MENTION=4292729]SpeedFire-[/MENTION]: From my results and from [MENTION=8476598]ab1702[/MENTION]'s comment I think that it's rather likely that this bug is caused by FCC, but I would like to ask you both to further investigate it, since it somewhat spoils the otherwise great experience of the NavRadio+ / FCC Launcher integration. :fingers-crossed:
[Android Head-Units] ab1702:
I don’t normally use the stock radio but I did use it for about an hour one day last week. I also don’t have the Stock radio as one of my quick players in player widget. Since that one hour of use I then started getting the problem that [MENTION=4916555]okij[/MENTION] described above Even though I never used the stick radio again.

I have now managed to stop this behaviour of fcc. I had to close all my apps off and then reboot the unit. Since doing this I haven’t seen the problem again as I haven’t used the stock radio again.

I do also see the problem of changing between quick players and sometimes having to press multiple times for it to change players. If using the mode button on the steering wheel sometimes it doesn’t change player at all if that player hasn’t been used yet.
[Android Head-Units] royalhawk2002:
I installed this launcher on my Erisin px5 head unit with Rockchip processor and s32f0 MCU. Which HW do I need to select in the initial settings? Tablet?

Second question: I have Google minimap activated in the home screen. If I setup a navigation itinerary in Google Maps nav, I cannot see the same in the minimap also if I have enabled "Calculate itinerary also in minimap", what I am doing wrong ? I have also Sygic, is there any possibility to use minimap for the routing directions ?

I bought the Premium version

Thanks for your help