Thanks a lot.
I cannot reproduce this problem on my head unit, please record a video for @SpeedFire-.
Hold your finger on an empty place. There could be a transparent widget. You can delete it.
I saw a transparent widget and now its gone, anyway to display those? Still have same issue. I'll keep trying
You can set any player in the Player Widget. Please see "Quick players" section of this widget.@SpeedFire- I do not know if after so many pages it is answered...
Is it possible to make the music player widget work with the Chinese radio player? It takes me to the Play Store and (obviously), it doesn't exist. I ask because (although I am rooted),
it is impossible for me to replace the radio player with PowerAmp (which is my favorite)
I can't reproduce the problem with the buttons. Can someone show it on video?I also confirm the problems with the buttons of the widget player also the circular shape has become oval and after the first standby the image is seen square with the circular sign above, and the test77 does not return to the test75, but the image in the album art only layout you can now see it
Sorry Andrey, False positive as I clean the cache and it work fine now !
I have also observed this issue.
No, it doesn't have to do with the cycling.
Thanks a lot, I will try it tomorrow.
Hi,@SpeedFire- As I already reported, the ANR errors of FCC sometimes are acompanied by crashes of Tasker and I emailed João Dias, the dev of tasker, about this. Here is what he replied me today:
"What I suspect is that the speedfire app may be sending a broadcast with too big a payload to Tasker and thus creating the crash. Do you think that might be it? Do you know the contents of that broadcast?"
Are there any other broadcasts besides ru.speedfire.flycontrolcenter.BT_ACTION being sent by FCC Launcher?
Maybe this could give you a clue about why FCC sometimes freezes with ANR errors?
Please give me some feedback, so I can forward it by email to João. Afaik he's not on xda, unfortunately.
Thanks. I will check.Hello @SpeedFire-. I have problems with auto brightness again. Each time the FCC is restarted (the main unit starts from the beginning), the auto brightness option is disabled. Then I have to enable it manually in the FCC settings menu. Next time it is disabled again. This problem occurs in versions from test70. The last version that works is test69.
This depends on your Android OS (some versions do not support split screen).
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.
Hi, thanks for your feedback.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").