• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Fcc Car Launcher [official thread]

What do you want: a split screen functionality or a normal launcher behavior?


  • Total voters
    48
  • Poll closed .
Search This thread

okij

Senior Member
Oct 24, 2012
1,895
3,798
Düsseldorf
Since I didn't drive during sunset or sunrise with test84 yet, I cannot say if the bug of the not auto-changing day/night-theme in the Minimap has been fixed. Did you already look after it?

@SpeedFire- I now checked it and this bug is still existent in test84, i.e. the Minimap doesn't automatically switch between day and night theme. Also when waking the head unit from sleep, it doesn't change to the correct theme according to the time of the day. Only when opening the Minimap settings it switches instantly to the correct theme. Please have a look after this bug too, thanks. :)

hello, unfortunately again crash after a stop of a couple of hours I made the log because the anr I do not find The folder thanks
Which FCC version did you use when the crash happened?

The folder is /data/anr under file system root. You can use e.g. Total Commander as file browser to get there.

Edit: I had a look at your Locat file and there are also other processes crashing, e.g. com.android.gallery3d and android.process.media. Therefore I'm not sure if this is caused by FCC Launcher, but don't know much about reading Logcats and hope that @SpeedFire- will have a look at it too.
 
Last edited:

tonimontoia

Senior Member
Feb 18, 2009
441
45
@SpeedFire- I now checked it and this bug is still existent in test84, i.e. the Minimap doesn't automatically switch between day and night theme. Also when waking the head unit from sleep, it doesn't change to the correct theme according to the time of the day. Only when opening the Minimap settings it switches instantly to the correct theme. Please have a look after this bug too, thanks. :)


Which FCC version did you use when the crash happened?

The folder is /data/anr under file system root. You can use e.g. Total Commander as file browser to get there.
the latest version posted last night
 
  • Like
Reactions: okij

daemondee

Member
Jan 9, 2020
45
14
@SpeedFire- I now checked it and this bug is still existent in test84, i.e. the Minimap doesn't automatically switch between day and night theme. Also when waking the head unit from sleep, it doesn't change to the correct theme according to the time of the day. Only when opening the Minimap settings it switches instantly to the correct theme. Please have a look after this bug too, thanks. :)

I think this has something to do with the problem with Auto Brightness.
I tested the latest test version and sometimes auto brightness works properly and sometimes it doesn’t. In any case, only the auto brightness function should be checked in the brightness widget.
I have noticed that when it is not working, the widget icon does not appear at all, when Fcc is started. Then I just have to click on the icon and it works.
 
  • Like
Reactions: okij

okij

Senior Member
Oct 24, 2012
1,895
3,798
Düsseldorf
@SpeedFire- FYI, I had to drive a couple of times this weekend and test84 is still running smooth and without ANRs on my head unit, so I don't understand why @tonimontoia still reported ANRs with it. Did you maybe see something in his logs?
 
Last edited:
  • Like
Reactions: SpeedFire-

SpeedFire-

Senior Member
Oct 11, 2011
1,876
1,378
Moscow
I can't tell exactly what happens with your device based on your LogCat log however:
1) I see that fatal crashes are caused not by the Fcc Launcher but by the system apps (like media browser).
2) There are lots of errors that some system folders cannot be found / mounted.
3) Most other apps report errors.
This could mean that something bad is happening with your particular device. Maybe your SSD drive dies or there is no enough free space or memory. It is hard to tell exactly.

I would suggest you to delete test version and install the release version from Play Store. Then please write do you have any ANR error or not.
 
  • Like
Reactions: dape16 and okij

tonimontoia

Senior Member
Feb 18, 2009
441
45
I can't tell exactly what happens with your device based on your LogCat log however:
1) I see that fatal crashes are caused not by the Fcc Launcher but by the system apps (like media browser).
2) There are lots of errors that some system folders cannot be found / mounted.
3) Most other apps report errors.
This could mean that something bad is happening with your particular device. Maybe your SSD drive dies or there is no enough free space or memory. It is hard to tell exactly.

I would suggest you to delete test version and install the release version from Play Store. Then please write do you have any ANR error or not.
I will follow your advice, but I do not understand if it stops The memory does not continue The music even if fcc is stopped? for now thanks let's see with a format if I can solve something
 

okij

Senior Member
Oct 24, 2012
1,895
3,798
Düsseldorf
fcclauncher-3.442_test85.apk
- MiniMap day/night mode should be fixed
Thanks a lot! I just installed it, so I will see tomorrow if day mode is used automatically again.

Guys, please post again bugs that you see in test 85 version and which are not yet fixed.
Of course we'll do. :)

I just checked test85 quickly and it still has these two bugs that I reported on Friday:
  • Still existent bug: When placing an App as a widget, its first state on the homescreen is "Text only", whereas according to it's widget settings it should be "Right side text". Once it's manually changed, it works as expected, but the initial state should be correct too and must be fixed. AFAIR in the old version on Play Store, the App widget remembered the last used layout, e.g. "Right side text", as well as the used icon and font size, borders and so on. I think that it would be good if you change it like this again, because when users place a lot of App widgets, they don't have to always make the same settings again.
  • New bug: The text alignment is not working anymore in test84, at least in the App widget where I tested it. No matter if I choose left, centered or right alignment, it's always shown as centered.
 
Last edited:

shdwkeeper

Senior Member
Jul 22, 2021
79
7
I'm on test 83, and my auto brightness widget never stays visible on my screen it just disappears, it's like hidden. Also I have some apps that I drag and put on home screen but they disappear when my system restarts. I can put it back and it keeps happening. I'll try test 85 and see if this help.

UPDATE: happens on test 85 also
 
Last edited:

okij

Senior Member
Oct 24, 2012
1,895
3,798
Düsseldorf
fcclauncher-3.442_test85.apk
- MiniMap day/night mode should be fixed
Thanks, it seems to be fixed now: I sent the head unit to standby yesterday evening on night theme and this morning it correctly showed day theme. I haven't seen it switching during use yet, because I didn't drive at dusk or dawn.

I'm on test 83, and my auto brightness widget never stays visible on my screen it just disappears, it's like hidden.
This doesn't happen on my head unit (MTCE PX6 on Ansroid 9 Hal9k rom).

What kind of head unit are you using?
 

SpeedFire-

Senior Member
Oct 11, 2011
1,876
1,378
Moscow
I'm on test 83, and my auto brightness widget never stays visible on my screen it just disappears, it's like hidden. Also I have some apps that I drag and put on home screen but they disappear when my system restarts. I can put it back and it keeps happening. I'll try test 85 and see if this help.

UPDATE: happens on test 85 also
I saw this bug previously, but it doesn't happen to me on test85.
Can you show it on video?
What device do you have?
 

shdwkeeper

Senior Member
Jul 22, 2021
79
7
Thanks, it seems to be fixed now: I sent the head unit to standby yesterday evening on night theme and this morning it correctly showed day theme. I haven't seen it switching during use yet, because I didn't drive at dusk or dawn.


This doesn't happen on my head unit (MTCE PX6 on Ansroid 9 Hal9k rom).

What kind of head unit are you using?
Dasaita PX6
 

daemondee

Member
Jan 9, 2020
45
14
I'm on test 83, and my auto brightness widget never stays visible on my screen it just disappears, it's like hidden. Also I have some apps that I drag and put on home screen but they disappear when my system restarts. I can put it back and it keeps happening. I'll try test 85 and see if this help.

UPDATE: happens on test 85 also
@SpeedFire-
I tried test 85 and that's happened to me too. Brightness widget not shown after restart but it shows up, when I click on the screen, where widget should be. My device is CSN2. I can record a video this afternoon.
Also, because of this, the auto brightness funcition does not working. I think I can't record a logcat of this, because this is happening on head unit boot. Or do you know any option to record logcat on boot?

@shdwkeeper
Do you use auto brightness funciton? Does it works properly for you?
 

SpeedFire-

Senior Member
Oct 11, 2011
1,876
1,378
Moscow
On this version, the clock widget stopped working for me, the clock is updated only when the launcher is restarted, but even after restarting it always shows the same time. Recorded a video.

And even after sleep, the auto brightness function turns off.

This is really unusual. It looks like the Fcc Service (a background service which processes the data and updates widgets) doesn't work on your device.

I would suggest to delete the launcher and install it again.

Please also make sure you don't block anything in Fcc Launcher by third party apps (don't freeze it, don't block services etc.)
 
  • Like
Reactions: dape16

Top Liked Posts

  • 3
    Yes, I know. :)


    Yes, of course. Also double-checked with Titanium Backup, which shows that original Radio app is frozen.


    Both are enabled. But since FCC doesn't use metadata but only notifications according to @SpeedFire-, I disabled metadata for the testings I just did (please see below.)


    Thanks for the quick update. :) It fixes most, but unfortunately not all of the issues I had with the display of NavRadio+ data in the FCC Player widget.

    The remaining bug is that randomly I see the text "Not provided" instead of the station name, even though the NavRadio+ notification correctly provides the data, please see attached video.

    I didn't have such issues and cannot find the source of this "Not provided" title however I explicitly banned it in this new version: fcclauncher-3.442_test123.apk

    Another small issue that I would like to ask you or @KoTiX2 to fix is that the RDS data currently is displayed as "Artist" and the station freq and name is displayed as "Track" in the Player widget. I would like to have it vice versa (or an option to assign it one or the other way), because then it would be the same as DAB-Z data is displayed in the Player widget. I have "Artist" set in a bigger font size than "Track" and usually station freq and name are shorter than the RDS texts, so this assignment would make sense.
    This is better to be done on @KoTiX2 side
    2
    New test version fcclauncher-3.442_test122.apk
    - I noticed that TPMS widget didn't work well. Now it is fixed.
    - Hal9k updates are ignored when NavRadio+ is installed
    1
    fcclauncher-3.442_test121.apk
    The only change in this version compared to test120 is that I updated all the libraries to the latest versions and targeted the latest Google SDK 32 (Android 13?) instead of 31 (Android 12) previously.

    So we can identify bugs (if any) related to this switch.
    1
    New version fcclauncher-3.442_test120.apk

    Finally, ALL the remaining widgets are rewritten to the new format:
    - TripCombined widget rewritten
    - OBD widget rewritten
    - Contact widget rewritten

    ...

    Please test.
    fcclauncher-3.442_test121.apk
    The only change in this version compared to test120 is that I updated all the libraries to the latest versions and targeted the latest Google SDK 32 (Android 13?) instead of 31 (Android 12) previously.

    So we can identify bugs (if any) related to this switch.
    Thanks a lot for the two new updates and congratulations that you finished rewriting all widgets now! :cool:(y)

    I updated from test115 to test121 today and can give you the following feedback:
    1. The Bluetooth widget had adifferent layout after the update (bigger space between logo and text), but I could manually change it to its previous look again.
    2. Also the GPS Satelites widget had a different layout after the update (bigger space between logo and text), but I can manually change this as well again.
    3. The TripCombined widget doesn't show the 2nd texts and I didn't manage to get them shown by adjusting the settings. Please compare the attached screenshots from before and after the update. According to the widget settings (which are the same as before the update) the 2nd texts should be shown, but they aren't, so this seems to be a bug.
    4. The Brightness widget doesn't show the "A" anymore when automatic brightness is activated and I couldn't get the "A" to be shown by changing the widget settings, so this seems to be a bug.
    5. Besides this (not test121 related, but checked with test115 on my MTCE head unit) the Brightness widget still doesn't seem to update to the correct icon according to the time of the day, please see attached video. I took the video in the evening, so the icon of the Brightness widget should have been at low brightness already, but it still showed full brightness. Only after cycling through the brightness settings by tapping on the widget, the correct icon is shown, as you can see in the video. The auto brightness function of FCC itself seems to work well, only the icon display is wrong.
    I don't use the OBD widget (which doesn't work on my system) and the Contact widget, so I cannot give you feedback about them.

    Please let me know when you need any more infos or testing. I'm looking forward for the remaining bugs to be fixed, so you can release the new version on Play Store. :)
    1
    This is probably because Google Maps have some interesting bug/feature. It doesn't download new tiles while camera is moving. I leave some time (several milliseconds each second) when camera is not moving during which Google can download data. If mobile speed is not enough it may fail to download everything during this period. When you drag the map camera is not animated and it downloads the data.

    I saw that Google released a completely new Beta of their built-in maps SDK with new rendering capabilities. Now it is deprecated and will be part of a normal library update:
    So maybe I already switched to this new map SDK when updated Google Libraries.
    Today I also checked if the Minimap display bug is still existent in test121 and unfortunately it still is.

    Thanks to @rigattoni's tip I used Mock Location app to record a short video of how this bug looks like, please see attachment.

    As you can see in the video, the map tile ahead isn't fully shown, but just the underlying colored areas. Only when swiping the map (at 0:00:10 in the video), the missing information/layers are immediately shown.

    I actually don't think that this is mobile data (or the speed of it) related, because it also happens with map tiles that should be already in cache.
  • 6
    Happy New Year @SpeedFire- and all users of FCC Launcher! 🍾🥂
    Happy New Year everyone!
    You are what drives the app development and motivates to change it.
    I am really excited about our community!
    You are the best! Happy New Year! :love:🥳🎉
    5
    Happy New Year @SpeedFire- and all users of FCC Launcher! 🍾🥂
    4
    I tried this now on my phone (Galaxy A5 2017, android 8), clean installed test113, set up new player widget and it is the same as on my head unit. The logo is not fit correctly.
    Here is a fixed version: fcclauncher-3.442_test114.apk
    It turned out that album art was cropped to square by default.
    Now I've added an option to the Player widget settings (crop is now disabled by default)
    4
    Happy New Year @SpeedFire- and all users of FCC Launcher! 🍾🥂
    Yes @SpeedFire- You deserve it from the FCC community
    4
    I tried this now on my phone (Galaxy A5 2017, android 8), clean installed test113, set up new player widget and it is the same as on my head unit. The logo is not fit correctly.
    Thanks! I reproduced this on my Samsung device as well. I will investigate this.
  • 54
    Hi, all!

    Welcome to the official thread for FCC Car Launcher - a customizable auto launcher for android head units (Rockchip MTCB/MTCD+ and FlyAudio) as well as android smartphones/tablets.

    Its major features:
    - Full function launcher with supports of all standard third party android widgets
    - Deep integration with head units (MCU etc). My mission here is to implement as many functions in the launcher itself as possible. In case of Rockchip devices to get rid of most xposed modules (my deep respect to their authors, great job, but they sometimes slow down the device significantly) and replace them with the normal built-in functions.
    - Customization. The FCC Cat Launcher has some built-in customizable widgets which can help to make your home screen more personal (you can adjust widgets size, colors, features etc).
    - Built-in music widget with support of FM Radio (with ability to give names to radio stations), Spotify, Google Music, PowerAmp, PC Radio, Neutron and Stellio players.
    - One-click navigation widgets with quick route building (supports Waze, Google Maps, Yandex Navigator and other navigation apps).
    - Phone calls via connected phone using 'Ok Google call [name]' request or by clicking on built-in Contact widget.
    - Other features.

    FAQ
    1. I love MiniMap but can you put other navigation app there?
    Unfortunately this is not possible. MiniMap is part of FCC and is based on Google Maps API for Android. It is not another app (not even a Google Maps app), that can be just replaced within the FCC interface. Android does not allow to integrate third party apps (navigation apps) inside another third party apps (FCC Launcher).
    If your head Unit supports Split Screen (ie can display Two apps at the same time), this can be partially done with split screen.

    2. Is it possible to cache maps for MiniMap for offline use?
    - Yes. In the latest FCC Launcher beta version you can select Offline Mapbox map and download it to your device.
    - For Google Maps - No. Caching is directly prohibited by Google license for using Google Maps API (MiniMap). Moreover, Google even does not provide developers with such a caching API. Therefore you will need a constant internet connection to use MiniMap. The somewhat good news is that the map itself does some short-term caching on your device, so it saves some data (but not too much).

    3. Notifications are only popping up for a split second / flashing. How to fix this?
    That means that animations are disabled on your device.
    - Go to the device's Developer settings: FCC settings - System - Advanced - Developer settings (if it asks for code - it's "7890" for AllWinner T8).
    - Scroll down and change 3 parameters "Window animation scale", "Transition animation scale" and "Animation duration scale" from "Animation off" to "Animation scale 1x".

    4. Routing on Google Maps in MiniMap doesn't work. It asks for API key. What should I do?
    - Turn-by-turn navigation in built-in Google Map fragment is directly prohibited by Google. Therefore it is not possible to use it. .However if you have your own Google Developer account (Google Maps API key) you can use it to draw a simple route line on the MiniMap. Please note that it will NOT have any turn-by-turn data like distance to next turn or estimated time of arrival.
    I do not recommend to purchase Google Developer account just for this feature:
    - Google Developer account will cost money for you (a one-off payment) which is reasonable only if you really want to develop android apps.
    - Routing requests cost money. But currently Google provides a 200$ per month free usage for Maps, Routes, and Places every month which should be enough for individual usage.
    Links: Get API key, Pricing. Don't forget to enable Maps API and Directions API in your Google Cloud Console.

    Tutorial:

    Translation to your language
    Guys, many of you suggested your help with translation of the app to your native languages.
    I have setup a translation project on OneSky site.
    Here is the link: HELP TRANSLATE FCC CAR LAUNCHER

    Links:
    Release
    channel: https://play.google.com/store/apps/details?id=ru.speedfire.flycontrolcenter
    Beta channel: https://play.google.com/apps/testing/ru.speedfire.flycontrolcenter
    (I would suggest to stick with the release channel since beta channel can be really buggy sometimes and is intended for beta testers only)

    As a developer I will be happy to discuss with you any ideas or issues.

    Here is a couple of tutorials:
    1) Quick look on home screen setup process:

    How to write LogCat log:
    You need to have ROOT:
    1. Install LogCat Extreme LogCat Extreme
    2. Select VERBOSE level of details (very important) Video 1
    3. Write and send log: Video 2

    Initial setup (do this if you see black screen):
    Important checkbox during first setup:
    giphy.gif

    Please make sure to check that checkbox "Always allow FCC Launcher to add widgets..".

    Full setup process:
    giphy.gif
    11
    pity that the developer is not dedicated to solving several bugs of this fantastic launcher, too many bugs for daily use is not so good unfortunately

    How the Hell can you say that when @SpeedFire- has dedicated 100's , if not 1000's of hours developing this launcher, and for peanuts !!

    I remember a time last year when he was on vacation, and even then, each night he worked on FCC, fixing bugs and greatly improving what was already there.

    FCC is probably one of the most COMPLEX apps on Playstore.

    My understanding is that he basically developed FCC for HIMSELF, because he was not satisfied with what was currently out there, and was good enough to share his work with anyone wanting to try it.

    Because of technical complexities, this launcher is designed and developed for a limited number of Android systems, but that number is increasing all the time as he add new Units to those currently supported.

    If you go out and purchase some obscure, budget China unit, that is not supported, you cannot blame anyone but yourself, if then you experience issues.

    Just because you paid the developer a few dollars because YOU CHOSE TO DO SO does not mean that you OWN him, and can demand that he jumps at your every call ... it's not his work -- it's his HOBBY -- and you probably knew that going in .. so lighten up and stop giving him such a hard time.

    BTW, I am also a developer, and I can tell you, if anyone else got involved in this complex app, it would most likely get totally screwed up, and dye -- that is assuming one could even find someone who would be willing to put in the time for next to nothing, while having the technical ability to actually contribute anything to the project.

    Thank you @SpeedFire- for clearly the best Android launcher on the market, and for all your time and dedication in constantly improving it. It is very much appreciated I am sure by the majority of those using it, and you will always have my full support going into the future.
    10
    Guys!
    It seems that I've found the best solution for Normal / Split-Screen modes. Take a look:


    Here is a short demo of two modes in the alpha version:
    1) Normal mode - launcher does not support split screen (bad) but behaves as a normal launcher and is not visible in the list of recent apps (good).
    2) Split screen mode - launcher supports 50/50 multi window mode (good) but is visible in the list of recent apps (bad).

    Every user can select the preferred mode!
    8
    The app is now returned to the Play Store :)
    8
    New beta is out:
    - All skins are re-designed for 6x10 grid (instead of previous 6x7 grid). You need to re-apply skin if you want to switch to a new skin.
    - You can choose your favourite skin during first time setup process.
    - Time widget has new options to granually change Time and Date font sizes as well as to swap Time and Date positions
    - Re-written code for album arts in Player widget. Hopefully this will fix most issues.
    - Some other fixes.
    - For built-in skins Icons are automatically setup when put on home screen or moved (based on skins' settings for particular Icon slot).
    giphy.gif