yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
I need it to manually switch the BT connection between my head unit and two phones when pressing on the BT widget via my Tasker project which I posted here.

Why don't you want to add a separate option? IMHO it would actually be great if there was such an option for other widgets too, for users who want to automate some things via Tasker. Of course most users won't use it, but they also wouldn't mind to see an additional option.

If you really don't want to add a separate option, please hide it in the "-" list entry, like it was in the old BT/Wifi widget. I just noticed that in test75, you actually open the BT app and send the ru.speedfire.flycontrolcenter.BT_ACTION intent. This is not a big problem for me, since my Tasker project also opens the BT app, but it also doesn't make much sense (and possibly could lead to problems) if the BT app is opened twice in a row.

Please let me know if you need some further infos.
[Android Head-Units] SpeedFire-:
I've assigned this intent to "-": fcclauncher-3.442_test76.apk
[Android Head-Units] okij:
OK, that's fine then! :)

However, in test76 there are major issues with the App widget:

When setting the widget layout, the layout icons don't have the right description, e.g. the layout icon for Bottom text shows "Icon only", please see attached screenshots.

Even worse, with some of the layouts it's not possible to start the app which is associated to the widget anymore. With "Right side text" it's still working fine, but with "Icon only" or with "Text over icon" (both selected according to the layout icon, not to the wrong description) the associated app is not started when tapping on the widget.

I'm quite sure that this was still working in test75, because I have an App widget with "Icon only" layout which still worked fine on test75 but not on test76.

Please have a quick look after this, because users who use many "Icon only" App widgets run into real problems when installing test76. Thanks. :)
[Android Head-Units] VBA_Dev:
Hi @SpeedFire- have you noticed post #7,998? This issue is present for me also.
[Android Head-Units] bhudcser:
Yeah, the correct model has been selected (MTK 8827L). Do you think it's possible to save log and check why it is not working?
[Android Head-Units] SpeedFire-:
No. This will not help. This device requires "deep integration" which means that I need to purchase it and reverse engineer its software. As far as I remember I've already tried to integrate similar device remotely without any success (not every type of device can be deeply integrated).
[Android Head-Units] kill_one:
@SpeedFire- As you can see from the video, when I choose the Only Album Arts layout, the image is no longer displayed, if I change with the other layouts it returns to view

also is it possible to modify or remove that gray halo in the other part of the widget? I did not understand if it is wanted or a bug?

Thanks
[Android Head-Units] kill_one:
@SpeedFire- would it also be possible as a default cover to display an animated gif? Currently if If i uploaded a gif the image is static Thanks
[Android Head-Units] kill_one:
i encountered the same problem with test version 76, can you go back to test 75 by simply reinstalling the apk?
[Android Head-Units] okij:
Yes, you can. This usually works without problems between test versions, as long as there's not a too long timespan between them. But saving the current FFC config before downgrading cannot hurt.
[Android Head-Units] jeff leggett:
Idk if this helps anyone. It's just a quick fix for 95% of FCC force closings from wake. If you have custom ROM, under the section list of activities that start after boot you'll see a couple FCC launchers. Try adding the one that says ru.speedfire.flycontrolcenter/

com.android.fcclauncher.Launcher

I'm not in the car right now but I think that's the one that's working for me about a week so far. But I could be wrong.
[Android Head-Units] SpeedFire-:
I can confirm this bug. However, I currently can't fix it quickly - can't identify the exact reason of the issue.

Maybe it is worth to take some time and reconsider widget redrawing once again..
[Android Head-Units] okij:
That's good.

OK, then of course take the time you need to fix it.

To narrow it down, this bug seems to be occured only in the latest test76, so you could have a look at the changes you did after test75.

Today I also noticed a bug of the new Bluetooth widget: The connection status (with the name of the BT phone) often doesn't stick, but shows disconnected again (even though the pone is connected) and a while after this only "Active". So the new Bluetooth widget does not react properly to the BT broadcast intents, which was perfectly working with the old BT/Wifi widget. Please have a look after this too.

Thanks for this info! Currently I'm using test76 to try if the force close / ANR bug has been fixed and give feedback to @SpeedFire-. This will take some days because this bug usually happened one to two times per week on previous versions. If this bug should still occur, I will try as you suggested.
[Android Head-Units] SpeedFire-:
YES. There are such plans.
[Android Head-Units] mclellan83:
Are Joying units deeply integrated?
[Android Head-Units] kill_one:
Album art only in the widget player not visible is a bug or is this a problem that only I have? 😅 key mapping still does not work,

as soon as I can I try to log if it can help solve these two problems 😉🙂
[Android Head-Units] okij:
@SpeedFire-: This afternoon the ANR bug happened again, this time on test76, so unfortunately it is not fixed yet. I again attached the Logcat and ANR files for you to have a look.

I now added ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher to the list of activities that start after boot, as @jeff leggett suggested here:

I will try this setting for the next couple of days. From a dev's perspective, do you think it can help to stop the ANR errors?

From a first test it seems that this setting fixes the bug of the new BT widget which I reported today:

I woke the head unit two times from sleep after adding ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher to the list of activities that start after boot and both times the BT widget properly and stably showed the connection status of the connected phone.

Also, from a dev's perspective, do you think that this setting can have a good influence on the new BT widget too?
[Android Head-Units] ronenfe:
Hi. Will you be able to fix the playback of the FM radio in the background. This prevents users with all winner k2001n headunit from using this app. Or any other launcher.
[Android Head-Units] SpeedFire-:
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
[Android Head-Units] tonimontoia:
Player selections no longer work, much less the play, pause, etc. buttons
[Android Head-Units] okij:
Thanks a lot. :)

This version fixes the problems with the layout icons and descriptions in the App widget settings, as well as the not starting app when e.g. "Icon only" is selected, as I reported in post #8024. (y)

However, even with test77 I already had an ANR error, as was happening with all recent versions and I already reported several times. :( I again took the Logcat and ANR files for you, please see attachments.

This also means that adding ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher to the list of activities that start after boot, as @jeff leggett suggested in post #8032, unfortunately does not fix the ANR errors, because I added this yesterday and it didn't help.

These ANR errors are driving me nuts by now and I really hope that you can fix them soon!

Also I still have an issue with the new Bluetoth widget: After a phone is connected (which then also is properly shown in the BT widget), it sometimes happens that the BT icon changes again its status and only shows "Activated". This shouldn't happen, because the phone is still connected, and never was an issue with the old BT/Wifi widget. IMHO the new BT widget is listening to different (or more) broadcast intents than the old widget, so it reacts to some intent(s) which are not important or are wrongly interpreted. So it could be that the BT widget should not react to an intent "BT activated" if already a phone is connected, because in this case also BT of course already is activated. Please have a look into this.

I cannot reproduce this problem on my head unit, please record a video for @SpeedFire-.
[Android Head-Units] shdwkeeper:
Running into an error message that there is NO MORE room on the screen to add a widget, when there is a space to add a widget. Running test 77 with the Main Screen Widget, where the album art is in the middle of screen.

Thoughts?
[Android Head-Units] SpeedFire-:
Hold your finger on an empty place. There could be a transparent widget. You can delete it.

You can also add an additional screen by moving the widget to the very bottom of the screen.
[Android Head-Units] shdwkeeper:
I saw a transparent widget and now its gone, anyway to display those? Still have same issue. I'll keep trying
[Android Head-Units] daemondee:
I can confirm this issue on my CSN2 unit.
[Android Head-Units] kill_one:
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
[Android Head-Units] sanangel:
@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)
[Android Head-Units] mariodantas:
test77

in my case, weather widget when in current weather shows time until sunset !
[Android Head-Units] SpeedFire-:
Did you try to tap on the widget? It cycles through:

- Sunrise/sunset time

- Time to sunrise/sunset

- Current weather

- 3-hour forecast
[Android Head-Units] SpeedFire-:
You can set any player in the Player Widget. Please see "Quick players" section of this widget.

P.S. Long tap on the widget to go to its settings.
[Android Head-Units] SpeedFire-:
I can't reproduce the problem with the buttons. Can someone show it on video?

Maybe it occurs only for some specific layouts..
[Android Head-Units] SpeedFire-:
New test version: fcclauncher-3.442_test78.apk

- BT widget fixed: bluetooth states should be shown correctly

- Fixed the issue when launcher disabled Bluetooth on restart.
[Android Head-Units] mariodantas:
Sorry Andrey, False positive as I clean the cache and it work fine now !

Will clean the cache every time you release a test to avopid false positives !

Sorry again !
[Android Head-Units] okij:
I have also observed this issue.

No, it doesn't have to do with the cycling.

Sometimes the new Weather widget erratically shows the current weather icon on the left side, but the time until sunset (instead of the temperature) on the right side.

Thanks a lot, I will try it tomorrow. (y)

Do you have any new insights on the ANR issue? I'm getting tired of posting logs and anr files over and over again for each new test version, without even knowing if they help you.
[Android Head-Units] okij:
@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.
[Android Head-Units] daemondee:
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.
[Android Head-Units] SpeedFire-:
Hi,

The BT_ACTION broadcast is completely empty. It doesn't have any data included. It is just an empty broadcast with the action ru.speedfire.flycontrolcenter.BT_ACTION

I would suggest you to delete Tasker for a couple of days to make sure that this issue has nothing with the Tasker (I assume that the Tasker cannot be blamed for this issue - this is probably the Fcc Launcher which causes it, but it is better to confirm this).
[Android Head-Units] SpeedFire-:
Thanks. I will check.

Please provide some more details how to reproduce this. How do you understand that auto brightness is disabled?
[Android Head-Units] daemondee:
Thank you.

In the FCC settings - Display is the Auto Brightness option. I have this option turned on and it should be turned on until I turn it off myself. However, in newer test versions, the option does not remain on when FCC restarted. The last test version, where this option remain on when FCC restart, is test69.

I hope this will help you.
[Android Head-Units] kill_one:
I don't know if I did well (I put play on the log and then I performed the various steps then I went back to the log that I stopped and saved on sdcard) but these are the logs I generated with the test78 version, I also attach the videos of the problems that give, with the test78 the widget player no longer displays the covers or does not update them, the play button does not change state the player selection keys do not respond and often the fourth by default does not appear, then it behaves differently with the various layouts of the widget, the progress bar does not work and displays the square image instead of circular, also I tried to reassign the buttons on the steering wheel and now it no longer locks but returns but simply closes the settings window
[Android Head-Units] SpeedFire-:
Can you try to reboot your device completely? Looks like notification service was killed.
[Android Head-Units] okij:
Thanks, I forwarded this to the dev of Tasker.

I now disabled Tasker and will see if the ANR issue does not occur for the next 5-7 days. However, as you said you also have ANR issues on your setup, and also @tonimontoia reported them, e.g. here including a screenshot of it, so I'm quite sure that the ANR issue is not Tasker related.

Today I kept a look on the Bluetooth widget and it seems to be fixed in test78, thank's again!

This afternoon the graphical update of the Player widget stopped updating, but it was still reacting to button presses on it. I restarted FCC to get the Plyer widget working again. Please let me know if you want to see the Logcat, then I'll go to my car and save it for you.
[Android Head-Units] SpeedFire-:
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.
[Android Head-Units] daemondee:
@SpeedFire-

Thank you, I tried a new test version, but the Auto Brightness feature still doesn't work properly.

Since there is the new brightness widget available, two Auto Brightness options are available. One is in the FCC Settings - Display - Auto Brightness menu, and the other one in the brightness widget itself (long press on the icon and there is Auto Brightness checkbox). In the test69 version, I have both checkbox checked and when the FCC restarts (when I start the car) both also stay on and the brightness is set automatically immediately.

For newer test versions, after FCC restart, the Auto Brightness checkbox in the FCC Settings - Display menu is unchecked. So the FCC does not remember this setting. However, the Auto Brightness checkbox on the brightness widget remains checked, but apparently this checkbox doesn’t affect that, as auto brightness doesn’t work. If I want it to work properly, I have to either check Auto Brightness checkbox in the FCC Settings - Display menu or set the brightness widget icon to Auto after every FCC restart.
[Android Head-Units] SpeedFire-:
Hi,

Thanks for the report. What device do you have? I checked this on a Android phone and auto brightness option saves and applies correctly.
[Android Head-Units] daemondee:
I have CSN2 device. I also removed cache before test.

I don’t know what’s wrong, I hope you can figure it out. I just know that whenever I then go back to version test69, the auto brightness there works perfectly.
[Android Head-Units] okij:
Thank you!

I tried test79 and the Player widget and the Brightness widget are working fine on my MTCE device, but I didn't have problems with these in the last test release either.

Unfortunately a bug that has been fixed in one of the last test test relases is back: The App widget does not open the associated app if certain app layouts are chosen, e.g. the "Icon left, text right" is working fine, whereas the "Only icon" layout does not work.

Also I encountered a force close when adding an App widget. After the fc and restarting FCC, the app widget was placed correctly.
[Android Head-Units] ric69:
Hello fcc restart each time on last beta 79 after 10 sec or so . I tried to wipe cache on px30
[Android Head-Units] SpeedFire-:
New test version - fcclauncher-3.442_test80.apk

- Fixed icon was not clickable bug in some layouts

- Auto-brightness possible fix

- Old "BT and WiFi" widget is replaced with "BT only" widget - you need to manually add BT widget if you used it in previous test versions

- Some crashes fixed
[Android Head-Units] kill_one:
with the test79 it now crashes when I try to remap the buttons on the steering wheel.

I attach log
[Android Head-Units] tonimontoia:
i tried the wifi widget in settings, even if change mmm icon color is applied
[Android Head-Units] okij:
Thanks, as always! :)

I can confirm that the "icon not clickable bug" is fixed. Also I successfully placed and configured the new BT widget.

There still is a bug when placing App widgets: After placing, the layout is not correctly shown (e.g. only text instead of icon + text). Even after changing the layout in the Widget settings and pressing OK, the layout is not correctly shown, e.g. I set it to "Icon only" but it still showed only text. Only after resizing the App widget back and forth the correct chosen layout is shown.

The first time I placed an App widget and opened its settings, FCC froze and I got ANR errors. I attached them and the associated LogCat for you to have a look what went wrong.

I currently have Tasker disabled - as you asked me to -, so this ANR error cannot be Tasker related. I don't know if today it was the same ANR issue that I usually encounter after waking up the head unit, so please have a look and tell me what you think.

The second time I placed an App widget it went OK and I didn't get ANR errors.

Still I have the feeling that those ANR errors might be related to the reworked widgets.
[Android Head-Units] daemondee:
Thank you for the new version.

I tried the latest version and here are my findings about Auto Brightness on CSN2 unit.

At first I just installed the new version and Auto Brightness didn't work - the FCC didn't remember the setting after rebooting.

Then I played around a bit with the settings in the brightness widget and in the "Brightness - Select which levels to cycle through on tap" section I left only Auto brightness selected. Then I rebooted the head unit and the FCC remembered this setting. I tried it twice and it worked both times. :)

Tomorow, when I have more time, I will try to gradually turn on the other options. I will report to you.
[Android Head-Units] SpeedFire-:
I think you're right. I have a test android phone (Samsung) with Fcc installed. If the screen is locked for a small time (several minutes) there are no issues when I unlock it.

But sometimes when it is locked for several hours I also see ANR when unlocked. During this time there are lots and lots of records from Fcc in LogCat every second. Looks like there is some loop (circular reference) running constantly. I still need to find its cause and find out why it starts after a long time only.
[Android Head-Units] okij:
Thanks for your feedback!

Just please note that the ANR errors sometimes happen after parking the car over night, sometimes after parking for just 1-2 hours, so I cannot confirm a relation to the deep sleep time.

I hope that you can find and fix the root cause soon. 🤞

P.S. Please have a look into my today's logs, as I can see that they haven't been downloaded yet. ;)
[Android Head-Units] daemondee:
Hello @SpeedFire-

Today Auto Brigtness is not working again. I tried it several times with only Auto Brightness selected in the widget settings but it didn’t work.

I also noticed that the widget icon does not appear after FCC launch. I have to touch that space, where it's supposed to be, and then icon appears and auto brightness turns on immediately.
[Android Head-Units] okij:
@SpeedFire- Another bug that I noticed in test80 (and likely also happened in some test versions before) is that the Minimap currently doesn't automatically switch between day and night mode.

It only switches when opening the Minimap settings. Then it switches instantly, without pressing any button.

Please have a look after this.
[Android Head-Units] okij:
@SpeedFire- This noon I had an ANR error again with test80, with Tasker still disabled. :(

I ignored the first ANR message and FCC itself still worked, but e.g. the Player widget didn't update anymore and the Minimap became stuttery.

Then, after parking the car for ten minutes and starting it again, the FCC didn't show anything but the background image and I restarted FCC on the second ANR prompt. This was the usual behaviour I already experienced and reported many times when I had Tasker still enabled, so IMHO it's definitely not caused by Tasker and I will now enable Tasker again.

I saved and attached the ANR files and the Logcat for a last time for now. But please have a look at them, since maybe you can see something why first the Player widget froze and caused the ANR error at 2021-10-27, 12-59-51 o'clock. Maybe the Player widget is the culprit and a loop (circular reference), as you assumed, is caused by it and eventually causes the ANR of the whole launcher.

I will only provide further logs and ANR files if something seems different and worth mentioning.

Please tell me if I can provide you with any further infos, since this bug IMHO currently ist the worst issue of FCC and should be fixed as soon as possible, because it's a really bad user experience. (Yes, I know that we are on beta versions and that you said that ANR issues are hard to track down :) ).
[Android Head-Units] SpeedFire-:
Hi, thanks!

Here is the version for you. I fixed one bug which could cause excessive cycles in BT widget. But I don't know if it was the only one. I'm waiting for ANR on my test device (which takes time as you know).

Actually I think there should be more bugs causing ANR. But let's try this for now: fcclauncher-3.442_test81.apk

Update: ANR bug is still there...
[Android Head-Units] okij:
Thanks, I'll try test81 anyway.

Could the excessive cycles in BT widget possibly have caused the Tasker crashes on my device, because the BT widget can send a broadcast intent that my Tasker project listens to?