• 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,811
1,302
Moscow
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?
 

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
Weather widget is finalised and old widget is replaced with the new one: fcclauncher-3.442_test71.apk
Thanks a lot, I really like the new customization options. :)

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?
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.
 

Attachments

  • anr_2021-10-06.zip
    165.6 KB · Views: 7
  • Like
Reactions: rigattoni

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
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
 

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
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
Thanks, I will do so. I'm not sure if I can catch an ANR error in the next couple of days because I'm on holidays for the next week and so I'll have to drive less in my car. But I'll try to start the head unit for some extra times even when I don't have to drive, maybe I'm lucky.

Does test72 contain some extra logging? I'm asking because I already posted LogCats several times when the ANR happened.
 
  • Like
Reactions: rigattoni

kill_one

Member
Oct 27, 2010
25
8
I would also like to contribute to solve the bugs affecting my unit, to create the log the stereo necessarily needs the root? my px5 Android 10 has this specs:
Build: k3368-userdebug 10 QQ2A_200305.004.A1 eng.hct2.20201019.121348 test-keys
Kernel: 4.19.111+ # 2436
MCU: MTCE_LM2_V3.67d_1
Can I root it? If so, which working guide can I follow?
Thanks
 

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
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
Now using test 72 I just caught ANR errors again, sooner than expected. :)

I attached the according LogCat for you, as well as the three files from /data/anr/. It's three of them because only on the third prompt "application not responding" I restartet FCC Launcher.

I hope that this now helps you to fix this issue.

Also I would like to ask you again if test72 contains some extra logging?

Please tell me if you need further assistance.
 

Attachments

  • Log_2021-10-11_10-27-55.zip
    94.7 KB · Views: 5
  • anr_2021-10-11.zip
    298.5 KB · Views: 1

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
Now using test 72 I just caught ANR errors again, sooner than expected. :)

I attached the according LogCat for you, as well as the three files from /data/anr/. It's three of them because only on the third prompt "application not responding" I restartet FCC Launcher.

I hope that this now helps you to fix this issue.

Also I would like to ask you again if test72 contains some extra logging?

Please tell me if you need further assistance.
No, it doesn't contain any extra logging because I still have no good guess about the cause of ANR.
This could be unfinished launch of internal services (like the one that gathers players data NotificationsListener or the one that shows pop-up notification AchievementService).

I saw in your previous logs some log inputs from Tasker. Looked like Tasker tried to cancel some Fcc Notifications. But I'm not sure. Therefore I asked for more logs.

You can try to disable Tasker for a couple days to check this.
 
  • Like
Reactions: okij

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
No, it doesn't contain any extra logging because I still have no good guess about the cause of ANR.
This could be unfinished launch of internal services (like the one that gathers players data NotificationsListener or the one that shows pop-up notification AchievementService).

I saw in your previous logs some log inputs from Tasker. Looked like Tasker tried to cancel some Fcc Notifications. But I'm not sure. Therefore I asked for more logs.

You can try to disable Tasker for a couple days to check this.
I only use one Tasker project on my head unit, please see attachment. It automatically switches the BT connection to my private and my work phone depending on the week day and time, so I don't have to worry about having my private phone connected when I'm driving for my job.

It does not cancel FCC notifications or any other notifications, please have a look at my Tasker project.

The only direct connection it has to FCC Launcher is that it listens to ru.speedfire.flycontrolcenter.BT_ACTION to manually switch the BT connection between my two phones when I press the FCC BT widget.

You are correct that in some - but not all! - of my logs there are some inputs from Tasker too. But IMHO the culprit is FCC and not Tasker, because the FCC ANR issues started with one of the test versions of the reworked FCC Launcher and I had no problems before with those two apps working side by side.

I wrote an email to João Dias, the developer of Tasker, because sometimes Tasker crashes when FCC freezes, and he answered me: "Hmmm, judging by that logcat it seems that tasker was killed when another app attempted to send it a broadcast... Can that be it?"

So this might be related to the broadcast intent ru.speedfire.flycontrolcenter.BT_ACTION. Did you maybe change anything about the code when rewriting your BT widget, so this better should be reverted?

AFAIK João does not have a user account at XDA, but if you want to contact him to talk from dev to dev, you can do so via email to support (at) joaoapps.com. It usually takes some days before he answers. Anyway, I will mail him the link to my post here so he can take notice about our conversation in your thread.

Good luck and please tell me if I can be of further assistance. :)
 

Attachments

  • Switch_BT_Phones.prj.xml
    87.3 KB · Views: 4

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
I only use one Tasker project on my head unit, please see attachment. It automatically switches the BT connection to my private and my work phone depending on the week day and time, so I don't have to worry about having my private phone connected when I'm driving for my job.

It does not cancel FCC notifications or any other notifications, please have a look at my Tasker project.

The only direct connection it has to FCC Launcher is that it listens to ru.speedfire.flycontrolcenter.BT_ACTION to manually switch the BT connection between my two phones when I press the FCC BT widget.

You are correct that in some - but not all! - of my logs there are some inputs from Tasker too. But IMHO the culprit is FCC and not Tasker, because the FCC ANR issues started with one of the test versions of the reworked FCC Launcher and I had no problems before with those two apps working side by side.

I wrote an email to João Dias, the developer of Tasker, because sometimes Tasker crashes when FCC freezes, and he answered me: "Hmmm, judging by that logcat it seems that tasker was killed when another app attempted to send it a broadcast... Can that be it?"

So this might be related to the broadcast intent ru.speedfire.flycontrolcenter.BT_ACTION. Did you maybe change anything about the code when rewriting your BT widget, so this better should be reverted?

AFAIK João does not have a user account at XDA, but if you want to contact him to talk from dev to dev, you can do so via email to support (at) joaoapps.com. It usually takes some days before he answers. Anyway, I will mail him the link to my post here so he can take notice about our conversation in your thread.

Good luck and please tell me if I can be of further assistance. :)

I agree. Tasker is probably has nothing with this issue.

Here is a new version - fcclauncher-3.442_test74.apk
- Removed some parts related to old Bluetooth and WiFi widgets (could have possibly caused ANR).
- Wi-Fi enable/disable action is now a panel on Android Q+
- Icon widget text is automatically truncated if not fits (for left aligned text)
- PlayerInfo widget - quick player button is hidden if quick player is not set.
 
  • Like
Reactions: okij

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
Here is a new version - fcclauncher-3.442_test74.apk
- Removed some parts related to old Bluetooth and WiFi widgets (could have possibly caused ANR).
...
Thanks a lot, this sounds promising!

Unfortunately it seems that you have removed some part of the code which is still needed, because the BT state (connected to device xy / not connected) isn't updated anymore.

This also doesn't seem to work anymore for the Wifi state, although I'm usually not using the Wifi part of the BT/Wifi widget.

Please have a look after this. Thanks.
 

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
Thanks a lot, this sounds promising!

Unfortunately it seems that you have removed some part of the code which is still needed, because the BT state (connected to device xy / not connected) isn't updated anymore.

This also doesn't seem to work anymore for the Wifi state, although I'm usually not using the Wifi part of the BT/Wifi widget.

Please have a look after this. Thanks.
Combined BT/WiFi widget will not work and will be probably removed.
You need to put separate BT and WiFi widgets (both are rewritten).
 

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
Combined BT/WiFi widget will not work and will be probably removed.
You need to put separate BT and WiFi widgets (both are rewritten).
I would like to do so, but I just tried the separate new BT widget and noticed the following issues:
  • An option to send ru.speedfire.flycontrolcenter.BT_ACTION when the BT widget is pressed is missing so far. I need this option to switch my phones via my Tasker profile.
  • Also opening the Bluetooth app (when this option is selected in the widget settings) doesn't work (at least on MTCE device).
  • Resizing of the BT icon doesn't work, it always stays at the same (big) size. Btw, this also applies to the new Wifi widget.
 
Last edited:
  • Like
Reactions: SpeedFire-

tonimontoia

Senior Member
Feb 18, 2009
435
44
always crashing, I have decoupled the separate Bluetooth and Wi-Fi widgets but nothing changes, useless to post the log file so much it does not read it and so on
Screenshot_20211014-104504.jpg
 
  • Like
Reactions: okij

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
I would like to do so, but I just tried the separate new BT widget and noticed the following issues:
  • An option to send ru.speedfire.flycontrolcenter.BT_ACTION when the BT widget is pressed is missing so far. I need this option to switch my phones via my Tasker profile.
  • Also opening the Bluetooth app (when this option is selected in the widget settings) doesn't work (at least on MTCE device).
  • Resizing of the BT icon doesn't work, it always stays at the same (big) size. Btw, this also applies to the new Wifi widget.
Hi,

Please check this version. All of the issues mentioned by you should be fixed: fcclauncher-3.442_test75.apk
 
  • Like
Reactions: rigattoni and okij

bhudcser

Member
Nov 29, 2014
12
0
Budapest
Hi, I'm new guy in the FCC Launcher world, so I have some general questions:
* Is that possible to control brightness with this launcher? My radio is ff-5000 8227L and this function doesn't work.
* Is there any way to control FM Radio with the mini music player widget? I'm able to select some kind of "FM Radio" but it's doesn't work at all.
 

okij

Senior Member
Oct 24, 2012
1,855
3,768
Düsseldorf
Hi,

Please check this version. All of the issues mentioned by you should be fixed: fcclauncher-3.442_test75.apk
Thanks a lot! :)

I just checked it and found only one small remaining issue: When having selected "Open Bluetooth app" as action in the BT widget, it actually sends ru.speedfire.flycontrolcenter.BT_ACTION instead. In the old widget I had to select "-" to have ru.speedfire.flycontrolcenter.BT_ACTION sent.

Could you please add a separate list entry in the BT widget to send ru.speedfire.flycontrolcenter.BT_ACTION (e.g. "Send BT_ACTION intent")?

Also IMHO there does not have to be a separate list entry "Open Bluetooth app", because for this we can just select "Bluetooth" in the apps section of the list, or wouldn't this be the same?
 

SpeedFire-

Senior Member
Oct 11, 2011
1,811
1,302
Moscow
Thanks a lot! :)

I just checked it and found only one small remaining issue: When having selected "Open Bluetooth app" as action in the BT widget, it actually sends ru.speedfire.flycontrolcenter.BT_ACTION instead. In the old widget I had to select "-" to have ru.speedfire.flycontrolcenter.BT_ACTION sent.

Could you please add a separate list entry in the BT widget to send ru.speedfire.flycontrolcenter.BT_ACTION (e.g. "Send BT_ACTION intent")?

Also IMHO there does not have to be a separate list entry "Open Bluetooth app", because for this we can just select "Bluetooth" in the apps section of the list, or wouldn't this be the same?
I don't really want to add a separate option. Please tell me in which case do you need this BT_ACTION intent?
 

Top Liked Posts

  • 1
    t98 installed. Observations. Map is no longer flashing but took a very long time to find my position even with a 5 bar internet signal. The other minor issue that I have observed today is the clock shrank. It went down from 32pt to 24pt and the secondary line went from 20pt to 12pt. Also the Player widget normally displays DAB, FM and Music, but had decided to add Standard player. This disappeared after a restart but did come back again. It has stopped doing it now. A LogCat will be posted soonest. Thank you
  • 5
    Thanks, the initial App widget settings bug is fixed in test87. :)

    As I already mentioned yesterday, there's now a bug with the text alignment of App widgets, which doesn't stick and changes erratically when restarting FCC, please see attached video.

    On my main FCC screen that you see in the video, I have the widget text "Wetter" right aligned and "Radar" left aligned to have them next to each other but look like one text field. The same applies to "Mod" which I have right aligned and "Einst." which I have left aligned.

    At the start of the video, you see that they are properly displayed. At 00:14, 00:26 and 00:40 in the video you see different variations of these texts not being properly aligned, thus showing gapps between the texts.

    In the settings of these widgets, the text alignment doesn't change when this happens. Only the actual display on the screen is buggy.

    Please have a look after this bug. To reproduce it, you can use the backup which I sent you yesterday. The only difference in the video is that I placed an extra FCC Restart icon on the main screen.

    Edit: For some reason, I couldn't add the MP4 to the post, so I had to zip it.

    Can you please check this version: fcclauncher-3.442_test89.apk
    5
    Long time no see but I got back on the bleeding edge (test 85 from the beta version in the Play store) in the hope of some support for button binding and other goodies on the CSN2 platform. Alas that turns out not to be the case, but overall the test version seems to be a bit snappier and I have not noticed any regression bugs from the Play store version with the exception of the following:

    In the test 85 version when I hide the mini-map and then I display it again it stops tracking. Tracking resumes after interacting with the map in any way (for example, enabling the "north always up" option and then reverting to "direction of movement up").
    Hi, thanks for your feedback.

    This bug should be fixed in this version: fcclauncher-3.442_test88.apk
    I've also made additional changes to ensure proper Time widget updates
    5
    Faults are one thing but the constant efforts to fix them is first class. Thanks @SpeedFire-
    4
    fcclauncher-3.442_test85.apk
    - MiniMap day/night mode should be fixed
    4
    Several days of reconsidering of the widget update process resulted in this: fcclauncher-3.442_test84.apk
    1) Bug with layout not applied should be fixed.
    2) There was fixed another bug when some already deleted widgets were still in the update list.

    We probably need to check the existence of the ANR bug from the beginning, because several parts of the app were modified. Please check the performance of the app - are there any negative / positive changes?
  • 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