• 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

SpeedFire-

Senior Member
Oct 11, 2011
1,758
1,212
Moscow
Hi Speedfire, congratulations first of all for the launcher you created, as soon as I tried it I immediately bought the premium version understanding its potential, I later found the various bugs of the playstore version that were later corrected in the test versions available here :)

Hi!

I wanted to ask you something, having the version with the backup failed problem if I update to the latest test version the settings and themes set are kept or do I have to start all over again?

You can easily upgrade to the latest test version. Most (hopefully all) settings should be saved. I've completely rewritten most of the widgets in the test version but I expect more or less good migration. This is a very important part, so please describe your experience after upgrade to the test version. Please save screenshots of your current setup and then show what is changed unexpectedly in the test version (this will help a lot!).

I also wanted to know if the problem of the accessibility service disabled when waking up the standby (when the car is turned on) has been solved or is there a workaround to solve it? Currently I have to reactivate it every time to increase the volume of google assistant (i have PX5 ANDROID 10 no root)

This is an android limitation. You need to have a root to do this. As far as I remember I've try to include this re-activation for rooted devices but I'm not sure. Tasker can do this (but for rooted devices as well).

Also I don't know if it has been reported to you and it has already been corrected but with the playstore version I found that when you try to configure the reset of the buttons on the steering wheel, the recent window always opens or crashes instead of having to choose the buttons to remap .

Haven't heard about this issue. Please try the test version and report if it still exists.

Then if possible I would have a request, namely the possibility of adding an option to reset travel data automatically every day or week and maybe the possibility of saving them in a file for a report or statistics.

Trip data should be reset every day in the test version.
I always have no time to implement statistics for trips :) Please remind me later

Thank you very much for the support and availability you have towards us :)
Thanks!
 
  • Like
Reactions: dape16 and okij

pablosso

Senior Member
May 15, 2013
65
9
Krakow
Samsung Galaxy S10+
Have you tried the latest test version of the launcher?
I've tried the latest test version and still NavRadio+ stops playing after few seconds.

Problem looks like this:
I'm listening to Spotify or no music at all (whatever). I click the physical BAND button on HU, NavRadio+ turns on, there is a sound for 2-3 seconds and it's over, not playing.
But it's working only if I go to the desktop, on the music widget I have to select NavRadio+, run the application by pressing BAND and only then is it okay.
 

daemondee

Member
Jan 9, 2020
16
4
I noticed that in the latest test version (test69), the map does not show the speed limit. Also, the street name does not work correctly as it shows the same street name all the time.
 

kill_one

Member
Oct 27, 2010
17
7
This is an android limitation. You need to have a root to do this. As far as I remember I've try to include this re-activation for rooted devices but I'm not sure. Tasker can do this (but for rooted devices as well).
Is there an easy way to root my device (EUNAVI PX5 4 / 64GB A10)? And how are developer options activated? Why are other accessibility services like tasker or autoinput still active?

i updated to the latest test, it kept the settings but something changed in the widget view, the backup works locally and gdrive :)

below are the screens before and after the update

as you can see the text size and some icons were only del, also on the icons now there is the name but i think there is an option somewhere to remove it right? in the widget player there were no longer the names of the three applications, they came out after a few restart of the launcher but the text is much smaller than before, the compass skin was gone and I had to reset it in its options, the page selectors did not it works, maybe I have to delete and recreate them? also, when I change one of the 3 applications in the player widget, the text and the cover of the previous application remain

The key mapping crash is still there I made you some videos before and after, and I don't know if it's wanted but if you press the back button three times the launcher closes and asks me which app to choose as the new home launcher if you want to want enter as to close it or keep it always active? Thanks and nice the time bar in the new widget :) can you customize the color?

also i dont know if it can be done but run the possibility in the player of that when youtube comes in the background it keeps playing the video instead of pausing it and it would be nice if you could keep watching the video instead of the image in the contraption.

Update:

I fixed everything, fixed the dimensions and eliminated the text on the icons, rearranged the compass and the page selectors (in practice updating to test69 did not keep the settings for these widgets), I noticed that now you can customize almost everything for each widget! Great!!! As for the fourth player in the widget, can't you add an option to keep it always visible?
 

Attachments

  • IMG_20210921_194729.jpg
    IMG_20210921_194729.jpg
    3 MB · Views: 73
  • IMG_20210921_194720.jpg
    IMG_20210921_194720.jpg
    4.5 MB · Views: 65
  • IMG_20210921_194738.jpg
    IMG_20210921_194738.jpg
    3.7 MB · Views: 60
  • IMG_20210921_200459.jpg
    IMG_20210921_200459.jpg
    4.4 MB · Views: 53
  • IMG_20210921_200505.jpg
    IMG_20210921_200505.jpg
    5.1 MB · Views: 50
  • IMG_20210921_200513.jpg
    IMG_20210921_200513.jpg
    4 MB · Views: 45
  • IMG_20210921_202257.jpg
    IMG_20210921_202257.jpg
    2.7 MB · Views: 41
  • IMG_20210921_203345.jpg
    IMG_20210921_203345.jpg
    897.4 KB · Views: 37
  • IMG_20210921_203414.jpg
    IMG_20210921_203414.jpg
    4.6 MB · Views: 66
  • VID_20210921_195246.mp4
    100.9 MB · Views: 0
  • VID_20210921_200900.mp4
    45.4 MB · Views: 0
  • VID_20210921_200609.mp4
    230.3 MB · Views: 0
Last edited:
  • Like
Reactions: okij

okij

Senior Member
Oct 24, 2012
1,802
3,749
Düsseldorf
This log unfortunately doesn't show anything. I hope you will find something similar in all these cases so I can try to reproduce this.
@SpeedFire- One week after my last report, FCC became unresponsive again (this time on the latest test69) and the system prompted me "FCC Launcher not responding, do you want to close it Y/N", which I eventually did after driving for half an hour. During this time I didn't close FCC yet to see if it settles again, which it didn't. When e.g. swiping up and down the screen, it always took about a minute until FCC reacted and showed the next home screen. The Minimap also reacted only with a delay of about a minute when touching or swiping it. The Player widget didn't show any song updates and was unresponsive too. Eventually the situation became even worse, because for the last 5 or 10 minutes before restarting FCC, the home screen didn't show anything (like widgets) at all and also didn't react at all.

I attached a Logcat for you again and hope that you can find something this time.

Until 09:19 this morning, when I parked my car, FCC Launcher was perfectly working. After waking the head unit again at 10:46, FCC Launcher didn't react anymore. At 11:20 I eventually agreed to restart FCC launcher by pressing "Y" on the prompt, after which I had to choose FCC as home launcher again.

Also Tasker reported an error as notification ("can't deliver broadcast"), which might be related or just a coincidence, because this didn't happen last week when I had the same issue with FCC Launcher. Anyway, I also attached the report which has been auto-generated by Tasker and which I filed with some additional information, so I might send it to the developer of Tasker. Please have a look at it too.

Maybe the relation between the simultaneous FCC and the Tasker problems is that they both have to do with broadcasts and notification service!? Here are some related snippets of my Logcat:

Code:
09-22 10:50:08.980  2172  2172 E AndroidRuntime: FATAL EXCEPTION: main

09-22 10:50:08.980  2172  2172 E AndroidRuntime: Process: net.dinglisch.android.taskerm, PID: 2172

09-22 10:50:08.980  2172  2172 E AndroidRuntime: android.app.RemoteServiceException: can't deliver broadcast

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1745)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:106)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:193)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:6718)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

09-22 10:50:08.980  2172  2172 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

...

09-22 10:57:27.803   465  1940 W ActivityManager: Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 1206ms

Code:
09-22 10:57:53.940   465   483 W ActivityManager: Timeout executing service: ServiceRecord{32f6974 u0 ru.speedfire.flycontrolcenter/.AchievementNotificationService}

09-22 10:58:02.825   465   483 E ActivityManager: ANR in ru.speedfire.flycontrolcenter

09-22 10:58:02.825   465   483 E ActivityManager: PID: 1465

09-22 10:58:02.825   465   483 E ActivityManager: Reason: executing service ru.speedfire.flycontrolcenter/.AchievementNotificationService

09-22 10:58:02.825   465   483 E ActivityManager: Load: 7.93 / 8.09 / 8.44

09-22 10:58:02.825   465   483 E ActivityManager: CPU usage from 0ms to 8845ms later (2021-09-22 10:57:53.941 to 2021-09-22 10:58:02.785):

...

Code:
09-22 11:05:29.643   465   483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{432c9d1 u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

09-22 11:05:31.005   465   483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{8c9320d u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

09-22 11:05:32.628   465   483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{7ff362f u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

...

Code:
09-22 11:20:08.020   465   484 W ActivityManager:   Force finishing activity ru.speedfire.flycontrolcenter/com.android.fcclauncher.FccAlias

09-22 11:20:08.032   465   484 I ActivityManager: Killing 1465:ru.speedfire.flycontrolcenter/u0a115 (adj 0): user request after error

09-22 11:20:08.293   465   465 V NotificationListeners: notification listener connection lost: ComponentInfo{ru.speedfire.flycontrolcenter/ru.speedfire.flycontrolcenter.notifications.NotificationListenerLoli}

09-22 11:20:08.293   465   826 D NotificationListeners: Removing active service ComponentInfo{ru.speedfire.flycontrolcenter/ru.speedfire.flycontrolcenter.notifications.NotificationListenerLoli}

09-22 11:20:08.293   465   555 I WindowManager: WIN DEATH: Window{5df5391 u0 ru.speedfire.flycontrolcenter/com.android.fcclauncher.FccAlias}

09-22 11:20:08.311   465   476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.assistant_volume.FccAccessibilityService in 1000ms

09-22 11:20:08.311   465   476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 11000ms

09-22 11:20:08.311   465   476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.AchievementNotificationService in 21000ms

09-22 11:20:08.311   465   476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.FCC_Service in 30999ms

I also had a look at the Locat that @tonimontoia posted here today. Here are some of his crashes, interestingly also several related to broadcasts and notification service:

Code:
09-21 15:01:57.170   642  8517 W ActivityManager: Scheduling restart of crashed service com.mgoogle.android.gms/com.google.android.gms.cast.media.CastMediaRouteProviderService in 1000ms

...

09-21 15:01:57.173   642  8517 W ActivityManager: Scheduling restart of crashed service com.mgoogle.android.gms/org.microg.gms.gcm.McsService in 938568ms

...

09-21 15:01:57.314   642  8517 W ActivityManager: Scheduling restart of crashed service org.telegram.plus/org.telegram.messenger.NotificationsService in 1000ms

...

09-21 15:01:57.400   642  8517 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 1000ms

...

09-21 15:01:57.694   642  8517 W ActivityManager: Scheduling restart of crashed service com.spotify.music/com.spotify.mobile.android.service.SpotifyService in 1000ms

...

09-21 15:01:57.862   642  8517 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 1000ms

...

09-22 09:43:17.422   642  6534 I WindowManager: WIN DEATH: Window{be68033 u0 ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher}

09-22 09:43:17.469   642  6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.FCC_Service in 1780ms

09-22 09:43:17.470   642  6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 11780ms

09-22 09:43:17.470   642  6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.assistant_volume.FccAccessibilityService in 21779ms

I really hope that you can make sense of the Logcats and fix the FCC not responding / crashing issue, because currently this is a real problem and the reworked FCC should not be released until this is fixed.

Please let me know what you think and if we can provide any more infos.
 

Attachments

  • Log_2021-9-22_11-20-58.zip
    76 KB · Views: 5
  • [Tasker] Tasker - android.app.RemoteServiceException_ can't deliver broadcast.txt.zip
    868 bytes · Views: 4
Last edited:
  • Like
Reactions: rigattoni

jeff leggett

Member
Dec 15, 2009
13
10
Google Pixel 2
Same here. Just not in my car for very long right now. I do have occasional fcc freeze ups when head unit wakes from sleep. Usually no warning message. I have to reboot and choose FCC as home launcher again and all is well. Doesn't happen too often. Thank you to the developer and all the testers.
 
  • Like
Reactions: okij

taesden

Member
May 9, 2018
12
0
Hi, sorry if this are beginner questions. I have purchased fcc for my M.I.C. device with PX6 but I´m very unhappy with the hardware, so I´m locking for a new device to run fcc on it. My questions are focused to the compatibility:
I´m lokking for a

Joying newly 11.6 inch Single Din Autoradio 4G LTE Android 10.0 Car Stereo with 1920*1080

running with ARM Cortex-A57 and Cortex-A55 CPUs.

  • Is fcc compatible with this device?
  • Does fcc autoplay last player after sleep is working with my preferred players: Stelio Music Player, Retro-Player, Muzio Player. I´m verry focused to mp3 players, that´s the main reason why I want to use a Android device.
  • Does anyone nows a real FM radio app with individual thumbnails for each radio station?

Thanx for each help and advice!
 

okij

Senior Member
Oct 24, 2012
1,802
3,749
Düsseldorf
@SpeedFire- This morning at 07:37 FCC Launcher was unresponsive again after starting the car. When I parked the car yesterday evening at 19:05, FCC was working without problems, so this issue always happens after waking FCC from deep sleep.

This time there were no issues with Tasker, so the issues I reported last time don't seem to be related with FCC freezing.

On the 2nd prompt "FCC Launcher not responding, do you want to close it Y/N" I pressed "Y", set FCC as home launcher again and took the attached Logcat for you.

The ANR (Application not responding) is recorded in this snippet of the Logcat:

Code:
09-24 07:37:28.210   465   483 W BroadcastQueue: Timeout of broadcast BroadcastRecord{f43a770 u-1 android.intent.action.SCREEN_OFF} - [email protected], started 10001ms ago

09-24 07:37:28.210   465   483 W BroadcastQueue: Receiver during timeout of BroadcastRecord{f43a770 u-1 android.intent.action.SCREEN_OFF} : BroadcastFilter{4f16ec3 u0 ReceiverList{5505a72 2479 ru.speedfire.flycontrolcenter/10115/u0 remote:93fb7d}}

09-24 07:37:28.624   465   483 W ProcessCpuTracker: Skipping unknown process pid 17815

09-24 07:37:35.213   465   483 E ActivityManager: ANR in ru.speedfire.flycontrolcenter

09-24 07:37:35.213   465   483 E ActivityManager: PID: 2479

09-24 07:37:35.213   465   483 E ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50200010 }

09-24 07:37:35.213   465   483 E ActivityManager: Load: 11.2 / 9.11 / 8.44

09-24 07:37:35.213   465   483 E ActivityManager: CPU usage from 0ms to 6968ms later (2021-09-24 07:37:28.211 to 2021-09-24 07:37:35.179):

09-24 07:37:35.213   465   483 E ActivityManager:   130% 2479/ru.speedfire.flycontrolcenter: 116% user + 13% kernel / faults: 4298 minor 34 major

Between 09-24 07:37:19.128 and 09-24 07:37:28.210 there are several other ru.speedfire.flycontrolcenter related Logcat entries which you should have a look at. I don't know if they give a hint about why the FCC freezes occur.

That's all I can do for now to help you in tracking down this issue. Please let me know if I you need some more infos and good luck in fixing it. :)🤞
 

Attachments

  • Log_2021-9-24_07-40-00.zip
    81.6 KB · Views: 2
  • Like
Reactions: rigattoni

tonimontoia

Senior Member
Feb 18, 2009
412
41
C'è un modo semplice per eseguire il root del mio dispositivo (EUNAVI PX5 4/64GB A10)? E come si attivano le opzioni sviluppatore? Perché altri servizi di accessibilità come tasker o autoinput sono ancora attivi?

ho aggiornato all'ultimo test, ha mantenuto le impostazioni ma qualcosa è cambiato nella visualizzazione del widget, il backup funziona in locale e gdrive :)



di seguito sono le schermate prima e dopo l'aggiornamento

come puoi vedere la dimensione del testo e alcune icone sono state solo ridotte, anche sulle icone ora c'è il nome ma penso che ci sia un'opzione da qualche parte per rimuoverlo giusto? nel widget player non c'erano più i nomi delle tre applicazioni, uscivano poi dopo qualche riavvio del launcher ma il testo è molto più piccolo di prima, la skin della bussola era sparita e ho dovuto resettarla nelle sue opzioni, i selettori di pagina non funzionano, forse devo eliminarli e ricrearli? inoltre, quando cambio una delle 3 applicazioni nel player widget, il testo e la copertina dell'applicazione precedente rimangono
Il crash di mappatura dei tasti è ancora lì ti ho fatto alcuni video prima e dopo, e non so se è voluto ma se premi il pulsante indietro tre volte il launcher si chiude e mi chiede quale app scegliere come nuovo home launcher se si vuole potresti entrare come per chiuderlo o tenerlo sempre attivo? Grazie e bella la barra del tempo nel nuovo widget :) puoi personalizzare il colore?

inoltre non so se si può fare ma potresti inserire la possibilità nel player del widget che quando youtube viene eseguito in background continua a riprodurre il video invece di metterlo in pausa e sarebbe bello se tu potessi continuare a vedere il video al posto dell'immagine nel widget.


GRAZIESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

Update:

I fixed everything, fixed the dimensions and eliminated the text on the icons, rearranged the compass and the page selectors (in practice updating to test69 did not keep the settings for these widgets), I noticed that now you can customize almost everything for each widget! Great!!! As for the fourth player in the widget, can't you add an option to keep it always visible?
hi, who explains me how to get this music spectrum, I can't find it from any setting thanks
 

kill_one

Member
Oct 27, 2010
17
7
@SpeedFire- I also encountered problems with the player widget, in particular the cover and the text does not always update, also sometimes when I change player the cover and info of the previous player remain, it would also be possible to implement support for gif images to be put as a default cover ? Thanks and good job :)
 
  • Like
Reactions: okij and daemondee

Top Liked Posts

  • 1
    New test version: fcclauncher-3.442_test79.apk
    - Player widget not responding fixed
    - Brightness widget icon fixed
    Some optimisations for phones:
    - Screen orientation is locked in landscape by default. This can be changed in Settings
    - Incorrect text scaling fixed when rotated between portrait <-> landscape modes.
  • 8
    Here is a rewritten Weather widget (finally) as a separate widget: fcclauncher-3.442_test70.apk
    4
    Here is a new version: fcclauncher-3.442_test77.apk
    - Fixed redrawing widget when new layout is selected
    - Top / bottom layouts fixed (previously icons were too small)
    - Player widget layouts fixed
    - One fatal error fixed
    3
    Weather widget is finalised and old widget is replaced with the new one: fcclauncher-3.442_test71.apk

    Now that you finished the new Weather widget, I hope that you can soon fix the ANR bug, which is quite a show stopper at the moment. Please let me know if I can help you with testing.

    Let's try. As I said, ANR is a hard thing to identify.
    Can you please check your folder /data/anr/ and upload all reports from this folder?
    3
    @SpeedFire- I want to report that this morning FCC became unresponsive again after waking the head unit, so I had to force close and restart it. :(

    Since I reported this three times already, including Logcats and further details (please see posts #7,938, #7,969 and #7,975), I don't see a point in posting further Logcats. But please tell me if you need further logs.

    However, this issue is occuring about two times per week and is really annoying, so I hope that you can soon fix it.

    Honestly I'm quite disappointed that you didn't reply yet to my last two reports (#7,969 and #7,975) where I tried as good as I can to give you details and point to some parts of the Logcat.
    Hi!

    I saw these posts. Thank you!
    However I currently don't have much time to work on the Launcher. Moreover, I want to finally rewrite Weather widget first (which is difficult because it changes its data on click).

    Then I will get back to these reports.

    Thanks again
    3
    Thanks a lot, I really like the new customization options. :)


    OK, here we go.

    There were two ANR reports in the folder, both of the most recent FCC Launcher freezes from two days ago. I zipped and attached the reports for you.

    I hope that they help you to find and fix the cause of the ANRs.🤞

    Please keep us updated about how it's going on.
    Thanks for the report. Now I think that LogCat reports would be more useful. Please try to record a couple LogCat logs with ANR error on this version: fcclauncher-3.442_test72.apk
  • 53
    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