yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
This version has much better chances to fix ANR. Please try this one: fcclauncher-3.442_test82.apk

Answering your question - I don't think BT widget could cause this. It was probably some stack overflow because of some cycle in the Fcc Launcher. It consumed all resources so nothing worked and even broadcasts were not delivered.
[Android Head-Units] okij:
Thanks a lot, I'll check test82 then. (y)

In case I should still get ANRs, do you still need log files or just normal feedback?
[Android Head-Units] SpeedFire-:
Logs may be useful
[Android Head-Units] SpeedFire-:
Finally, I don't see any ANR error on my test device after a full night on test82. Which is promising.

Update: Oh no, caught ANR right after writing this message :(
[Android Head-Units] SpeedFire-:
Another important bug is fixed here: fcclauncher-3.442_test83.apk

Widget instances were added several times (on each launcher resume) so there were excessive updates. Now they are added only once. I don't know if this will fix ANR but this will definitely help with overall performance.

Update: works good so far!
[Android Head-Units] tonimontoia:
'maybe I understood the reason that crashes, whenever a player that has not been closed is started, but I have disabled the option not to restart
[Android Head-Units] okij:
Yep, I also caught an ANR this morning with test82 just one hour after installation, please see attached files.

When the ANR happened, FCC was in service mode (= pin lockscreen). I don't know if this is of interest for you, because I assume that the launcher screen (with all its widgets etc.) is still active in background anyway.

Thanks, I installed it right away and will see how it behaves in terms of ANR.🤞First impression is that the GUI runs a bit smoother.

An interesting theory that @SpeedFire- should have a look at.

I personally have configured FCC to restart the last used player after sleep, but at the same have configured Hal9k Mod4 to close players during sleep. The players are not configured to survive sleep, because they didn't resume properly after sleep when I tried this one to two years ago.

You wrote "whenever a player that has not been closed is started", but that's not the case here because my players get closed.

Nevertheless I get ANR errors, so I think that the reason for the crashes is something else.
[Android Head-Units] SpeedFire-:
Thanks for your reports. Please test version 83. For me no ANR errors so far. Works better than before.

So I really hope that the bug is fixed (fingers crossed). Let's see how it goes for you.
[Android Head-Units] okij:
Yes, I have installed test83 and will test it. This will take up to a week, because I usually got the ANR errors once or twice a week, just in the last two weeks they occured more often.

My fingers already hurt from crossing. ;) I also think that the repeatedly adding of widget instances could have lead to ANR errors, so I'm optimistic and I also really hope that the bug is fixed now. 🤞

Can you tell when you implemented the code to add widget instances on each launcher resume? This must have been while rewriting the widgets during the 3.442 test series, is this right?

Did you take notice of my other two bug reports that I posted in the last couple of days?

I checked this issue in test82/test83 and it is still existent.

AFAIR this I didn't observe this issue in test82/test83 yet. Did you fix it?
[Android Head-Units] SpeedFire-:
This bug existed in all 3.442 test versions. The more widgets were rewritten the more instances (of these rewritten widgets) were added. Therefore this bug may become more severe in the latest test versions in which almost all the widgets are rewritten.

I tried to reproduce it but with no luck. All works fine on my test android phone and PX5 unit. Can you show it on video?

I fixed something related to day and night themes but for another reason. I hope this also helped with this bug.
[Android Head-Units] kill_one:
@SpeedFire-

with the test80 you did a great job! The widget player works well the covers always update the text, even when I change between poweramp and spotify for example it never stops and even when I wake up from standby, I found, however, when I press the play button (only the remote control on the steering wheel) and it pauses when I play again, the music of the poweramp always starts even if spotify is selected, if I do it from the widget keys it does not. Then if I launch navradio after a while the radio stops and it is no longer heard I have to change the player and then put it back to listen to the radio again then it works fine.

Then as you see from the photos now when I add a new page selection widget it has a different icon and font, how can I put the same one as before?

Did you also solve the crash of the steering wheel button remapping with test83?
[Android Head-Units] okij:
Yes, that makes sense.

Please see attachment.

Unfortunately the Minimap didn't aututomatically switch from day to night theme at dawn this evening, so this bug is still existent. Only when I opened the Minimap settings it switched instantly, like I've observed before. It might be that some background task to change it automatically at dusk and at dawn doesn't seem to work right now.

Also it seems (not quite sure about this though) that the auto display brigtness (and its according widget icon) currently doesn't automatically change. Maybe these two issues are related.
[Android Head-Units] tonimontoia:
always the same when a player starts after being at rest, and sometimes even just unplugging the machine and restarting the dasaita crashes, but sometimes the player crashes alternate
[Android Head-Units] okij:
@SpeedFire- A first intermediate feedback for test83 after using it for one more day: So far no ANRs and the launcher still feels very fluid, better than the versions before. So I'm still very optimistic! :)

The weather icon still has a bug in test83 that has been reported by @mariodantas and confirmed by me before:

Today I've catched a screenshot of this issue which I attached to this post.

Please have a look at this if you have some time. IMHO it's not high priority, whereas the issues that I reported yesterday in post #8,093 are more important to fix.
[Android Head-Units] SpeedFire-:
How is your test going on?

Regarding your bug with app widget put on screen and not changing its layout. I reproduced it and found the reason but can't fix it yet. It is really weird. The widgetID of this new widget is successfully added to a list array when it is put on screen however later the same list array doesn't have it. Only the app restart currently helps. Maybe multi-threading is the cause. I will keep trying to fix it.
[Android Head-Units] okij:
Last weekend (from Saturday to Monday) I didn't have to drive in my car, so there's not much update I can give. This morning I started the car two times and didn't have ANR issues yet with test83 and FCC works fluid. So it still looks good so far, but please give me some more days to test. :)

How about my other bug reports (1. day/night-theme in Minimap doesn't automatically change; 2. Weather widget erratically shows current weather and time until sunset)?
[Android Head-Units] SpeedFire-:
Thanks

I am currently working on that bug with the app settings...

Btw I wasn't able to reproduce the bug with weather widget. Are there any suggested steps to reproduce it?
[Android Head-Units] okij:
Sorry, not that I know of. AFAIR it happened shortly after cycling through the different views.
[Android Head-Units] schloram:
Hi,

sorry for interrupting. :)

I stumbled over the FCC launcher last week after I tested a few other launchers for my Android 10 head unit.

First of all: This app has everything of the other apps I tested combined. Thanks for your effort in bringing us an almost perfect launcher. :)

I was reading through some of the posts here and figured that some of the bugs I discovered in the newest Play Store version were already fixed in some test versions uploaded in this thread.

My question now is: When will these test versions result in a proper release to be downloaded via Play Store?

Thanks
[Android Head-Units] okij:
Ok, here are reliable steps to reproduce it:

Cycle trough the widget until the current weather is displayed.

Wait for max. 1 minute.

Next to the icon, now the time until sunset/sunrise is displayed.

The same bug happens after cycling until the time until sunset/sunrise is displayed and waiting for max. 1 minute. Then the display shows the hour+minute of sunset/sunrise.

In summary, it seems that after cycling, the next time or temperature update of the previous widget display is shown in the current widget display, that's why you have to wait max. 1 minute until the next time update. Temperature of course can take much longer to update.

Please let us know if you can reproduce it.

BTW, still no ANRs on test83, but please let me check it for two more days to be sure that the ANRs are definitely not happening anymore.
[Android Head-Units] jeff leggett:
Trying test 83 today. Fingers are crossed. I don't have weather widget issues either. Edit. Sorry. Jumped the gun. Same issue with weather.
[Android Head-Units] tonimontoia:
always the same problem for months, I do not place the log so much does not open it, I have seen the other logs never opened by the author
[Android Head-Units] okij:
Are you using the latest test83 version?
[Android Head-Units] tonimontoia:
yes
[Android Head-Units] okij:
That's strange, because I didn't have ANR (application not responding) errors with test83 yet and currently I think that @SpeedFire- fixed this issue in test83. In test82 and before widget instances were added several times, which most likely lead to ANR errors.

So if you have ANR errors on test83 and really want to help @SpeedFire- to fix this, you have to provide more details about how often and under which circumstances the ANR errors happen. Probably you also should post some Logcat and ANR logs, even if @SpeedFire- doesn't look into all of them (which also applies to some logs that I posted, but which is OK if there are no new insights he can get from them).

The only thing that doesn't help is if you just write some unpolite posts here on this forum. At least they look unpolite at times, but maybe because of your knowledge of the English language.
[Android Head-Units] tonimontoia:
if I write unpolite things are the translations, I don't know English at all
[Android Head-Units] okij:
OK, then that's fine.

What's your native language and what translator do you use? Besides Google Translate I can recommend DeepL Translate (if it supports your native language) which in my opinion offers the best auto translation of texts. Give it a try.
[Android Head-Units] tonimontoia:
Italia
[Android Head-Units] okij:
The Italian language is supported by DeepL Translator, so give it a try.

La lingua italiana è supportata da DeepL Translator, quindi fai una prova.

(I just translated this with DeepL, since I don't know Italian at all. :-)
[Android Head-Units] tonimontoia:
OK
[Android Head-Units] tonimontoia:
@speedfire another stop of the many this morning if you want to give an eye attached to the log thanks

Log_2021-9-05_10-47-26

drive.google.com
[Android Head-Units] okij:
@SpeedFire-: Test83 still works without slowdowns or ANR errors on my PX6 MTCE head unit. I will check it for one more day, but so far it looks good! (y)

The log you posted is from 5th September 2021, so it definitely cannot be made with the latest test83 version.

Please download fcclauncher-3.442_test83.apk from post #8,086 and only do tests and posts logs when you are using the latest version.

If you still encounter ANR (= app not responding) errors, please also provide the ANR log files to @SpeedFire-, which you find in folder /data/anr/ on the internal memory, as is written in post #8,001. Those ANR logs are important to identify what went wrong and lead to the freeze of FFC Launcher.

And please use punctuation (commas, periods, etc.), because your posts are sometimes difficult to read and puncuation also helps the online translators to give a proper translation. Thanks.
[Android Head-Units] tonimontoia:
Ho sbagliato log

and this I have not changed The date on the file I forgot
[Android Head-Units] okij:
Sorry, I don't really understand what you mean. You still don't use punctuation and you don't seem to want to write in a way that others can read and understand. I'm about to give up on reading your posts an on giving you some well-meant advice. :(

The log you posted this morning is definitely from 5th September, this can also be seen inside the logfile itself.
[Android Head-Units] tonimontoia:
the log I posted and this morning, I didnt understand why he wrote another date,I checked again there are no logs of other days, tomorrow I would do another log again lets see if it is corrected,If the translators write wrong its not my fault, as if you come to an Italian Forum and translate cute you not knowing The language trusts no?
[Android Head-Units] okij:
OK, but

Please make sure that you really use the latest fcclauncher-3.442_test83.apk from post #8,086. I somehow doubt this because with test83 I didn't get ANR errors yet.

Please also provide the ANR log files from folder /data/anr/ on the internal memory to @SpeedFire-.

No, but I doubt that you use Deepl Translator, as I recommended you, because then the translation would be better.

And also the translators need proper punctuation to understand what you mean and provide a correct translation.

It is a huge difference if you write: "Come on, we eat, grandma." or: "Come on we eat grandma" (Please click on the links to get the Italian translation from Deepl Translator, so you understand what I mean.) Punctuation doesn't only make texts readable but also can save lives. ;)

It's fair enough if you are not a native English speaker and have to use a translator - there a lot of users on XDA doing this. But please don't be lazy when posting here and make sure that the dev and the other users understand you.
[Android Head-Units] SpeedFire-:
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?
[Android Head-Units] jeff leggett:
I'm not much help without logs but went on a long trip today and car sat overnight a couple times. So far no force closes with test 83 and super responsive. Will now try 84.
[Android Head-Units] okij:
After a week of using test83 (i.e. 5 days of using my car with about 4 times per day of waking the head unit from sleep) I'm happy to report that I had no ANR errors and no force closes. With previous test versions I had ANRs at least once or twice a week, so in my point of view, the ANRs have been fixed in test83. :)

As also @jeff leggett has reported, test83 is super responsive. In this aspect it's as good if not better than the stable version on Play Store. So congratulations @SpeedFire-, you did a really good job on fixing the ANRs and slow downs. :cool:(y)

After my first drive this morning I switched to test84. From my first tests, I can give you the following feedback:

Test84 feels as responsive as test83 and it's a joy to use.

The bug of the inconsistent Weather widget display (wrong text next to icon) is fixed.

The bug with layout not applied is fixed, however:

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.

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?
[Android Head-Units] tonimontoia:
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

Log_2021-11-05_17-42-40

drive.google.com
[Android Head-Units] okij:
@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.

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.
[Android Head-Units] tonimontoia:
the latest version posted last night
[Android Head-Units] daemondee:
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.
[Android Head-Units] tonimontoia:
anr_2021-11-06-11-25-21-164

drive.google.com

Anr crash
[Android Head-Units] okij:
@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?
[Android Head-Units] SpeedFire-:
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.
[Android Head-Units] tonimontoia:
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
[Android Head-Units] SpeedFire-:
fcclauncher-3.442_test85.apk

- MiniMap day/night mode should be fixed
[Android Head-Units] SpeedFire-:
Guys, please post again bugs that you see in test 85 version and which are not yet fixed.
[Android Head-Units] okij:
Thanks a lot! I just installed it, so I will see tomorrow if day mode is used automatically again.

Of course we'll do. :)

I just checked test85 quickly and it still has these two bugs that I reported on Friday:
[Android Head-Units] shdwkeeper:
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
[Android Head-Units] okij:
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?
[Android Head-Units] SpeedFire-:
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?
[Android Head-Units] SpeedFire-:
These two bugs should be fixed here: fcclauncher-3.442_test86.apk
[Android Head-Units] shdwkeeper:
Dasaita PX6
[Android Head-Units] shdwkeeper:
Yeah let me video it for you
[Android Head-Units] daemondee:
@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?
[Android Head-Units] Physen:
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.
[Android Head-Units] SpeedFire-:
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.)
[Android Head-Units] shdwkeeper:
I thought I was using it but never noticed it changing so I guess it want working for me either. I didn't even realize I had the Auto Brightness widget on my screen until I touched that area where the widget was and it showed up. It was there the whole time but hidden.
[Android Head-Units] shdwkeeper:
Here's a video

View attachment 5453867

Ok, I just had to resize it. So the Brightness widget works if I dont have the screen lock on, when the screen lock is on the widget is hidden as shown in the video. I also show that one of the App just never stays on the screen.

UPDATE: deleting the skin and installing new skin fixed the App Widget problem.
[Android Head-Units] SpeedFire-:
I can't see the link.
[Android Head-Units] shdwkeeper:
Added it above
[Android Head-Units] okij:
Then try to zip and upload it.
[Android Head-Units] shdwkeeper:
Reposted video above
[Android Head-Units] okij:
Thanks! :)

I can confirm that the text alignment is fixed, however the other bug still exists:

Please see attached video.

In this video you can also observe that the time update of the clock widget got stuck, like @Physen also reported today:

As you can see at 0:00:18 in my video, the time in the clock widget gets updated (+ 3 Minutes) when I open the App widget settings. There's really something wrong with the time update in test86, as I didn't observe this before. (Maybe this also happened in test85, which I didn't use long enough to be sure about this.)

In test86 it also happened two times that a widget changed its font size by itself and it happened once that the text alignment changed by itself, so I had to correct these settings again. I don't know when or why this happened, so I don't know how to reproduce it. I keep you updated if this happens again.
[Android Head-Units] SpeedFire-:
I can't reproduce this on any of my test devices (emulator, PX5, samsung phone) :(

Can you please send me your backup?
[Android Head-Units] okij:
Of course, please see attachment. Hope this helps. 🤞