yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] HatManSan:
I have installed Logcat and run it as per the video. I hope this is correct.

---- Jul 9, 2021 11:21:39 ----

--------- beginning of main

07-09 11:20:40.741 7855 7855 E scd.lcex: Not starting debugger since process cannot load the jdwp agent.

07-09 11:20:40.991 7855 7855 D OpenGLRenderer: Skia GL Pipeline

07-09 11:20:41.049 7855 7875 I mali_so : [File] : hardware/arm/maliT760/driver/product/base/src/mali_base_kbase.c; [Line] : 876; [Func] : base_context_deal_with_version_affairs_rk_ext;

07-09 11:20:41.049 7855 7875 I mali_so : arm_release_ver of this mali_so is 'r18p0-01rel0', rk_so_ver is '9@0'.

07-09 11:20:41.049 7855 7875 D mali_so : [File] : hardware/arm/maliT760/driver/product/base/src/mali_base_kbase.c; [Line] : 881; [Func] : base_context_deal_with_version_affairs_rk_ext;

07-09 11:20:41.049 7855 7875 D mali_so : current process is NOT sf, to bail out.

07-09 11:20:41.058 7855 7875 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0

07-09 11:20:41.059 7855 7875 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0

07-09 11:20:41.059 7855 7875 I OpenGLRenderer: Initialized EGL, version 1.4

07-09 11:20:41.059 7855 7875 D OpenGLRenderer: Swap behavior 2

07-09 11:20:41.081 7855 7875 D mali_winsys: EGLint new_window_surface(egl_winsys_display *, void *, EGLSurface, EGLConfig, egl_winsys_surface **, egl_color_buffer_format *, EGLBoolean) returns 0x3000

07-09 11:20:41.131 7855 7875 D GRALLOC-ROCKCHIP: RK_GRAPHICS_VER=commit-id:0472af1

07-09 11:21:11.441 7855 7855 I Choreographer: Skipped 1780 frames! The application may be doing too much work on its main thread.

07-09 11:21:11.543 7855 7875 I OpenGLRenderer: Davey! duration=30283ms; Flags=1, IntendedVsync=2751698444376, Vsync=2781867934936, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=2781880569859, AnimationStart=2781880655318, PerformTraversalsStart=2781894823611, DrawStart=2781942180657, SyncQueued=2781947259158, SyncStart=2781947309033, IssueDrawCommandsStart=2781948982616, SwapBuffers=2781978918702, FrameCompleted=2781981764494, DequeueBufferDuration=210000, QueueBufferDuration=1361000,

07-09 11:21:19.835 7855 7875 D mali_winsys: EGLint new_window_surface(egl_winsys_display *, void *, EGLSurface, EGLConfig, egl_winsys_surface **, egl_color_buffer_format *, EGLBoolean) returns 0x3000

07-09 11:21:23.187 7855 7875 W libEGL : EGLNativeWindowType 0x77639a9010 disconnect failed

07-09 11:21:23.187 7855 7875 D OpenGLRenderer: endAllActiveAnimators on 0x775b700800 (AlertController$RecycleListView) with handle 0x77639b1b00

07-09 11:21:36.770 7855 7875 D mali_winsys: EGLint new_window_surface(egl_winsys_display *, void *, EGLSurface, EGLConfig, egl_winsys_surface **, egl_color_buffer_format *, EGLBoolean) returns 0x3000

---- Jul 9, 2021 11:21:39 ----

A link to a poorly made video :( will follow when it upload to YT

Thank you

P.S I made the Logcat file after trying to install t27
[Android Head-Units] SpeedFire-:
Please make sure that you've selected Verbose level of details in LogCat app (see the first post for instructions).

Your LogCat log should be several megabytes in size (lots of records).
[Android Head-Units] SpeedFire-:
Please also try this version. I've fixed some known issues based on online crash reports: fcclauncher-3.442_test29.apk
[Android Head-Units] HatManSan:
t29 failed in the same way. Now pulled the HU from the car and fully formatted it and reinstalled everything stock except Hal9k 4.2.1 MCU is GS3.62. So radio is as new. t29 loaded ran then crashed. Logcat now making a much bigger file.

Log_2021-07-09_16-09-08.txt

Text Document

1drv.ms
[Android Head-Units] SpeedFire-:
Based on the Log - you selected a MapBox map.

It will not work in test versions.

MapBox changed their API and the new version unfortunately crashes. Yesterday I tried to fix this, but with no results so far.

So do not select MapBox map until this is resolved.
[Android Head-Units] bettuccio:
test version 29 does not fit on my PX5. When I try to change the compass widget, it disappears and you have to restart. When restarting the whole OS shows a black screen and you have to restart again from the hole / reset button until the right FCC screen appears. Added something new but still needs to be fixed. Maybe it was better the test version 25
[Android Head-Units] HatManSan:
Speedfire, hi. I never get as far as selecting anything. However i shall try to change that right now.
[Android Head-Units] HatManSan:
It lives!!!!
[Android Head-Units] HatManSan:
I tried to install my settings backup and it died again. So I am simply redoing the homepage etc without the Mapbox for now. Thank you for working this out.
[Android Head-Units] SpeedFire-:
Here is a quick fix of MapBox issue: fcclauncher-3.442_test30.apk

I'm not sure if it still supports offline maps, but at least it does not crash and shows the online map.
[Android Head-Units] HatManSan:
Superb. New homepage etc now. New backup etc. Very pleased to be back and running. Thank you
[Android Head-Units] SpeedFire-:
Guys, I have a question.

Can someone with Android 9 or lower test backup / restore on the latest test version?

I see the following issue. Google introduced additional restrictions in Android 11 related to the access to the external storage. I switched to the new method which seems to be working fine on Android 10+.

BUT, I test this on the Android 7 emulator and backup/restore (using this new method) doesn't work. The old method is deprecated and I can't use it. So it seems to me that file save / restore is broken for Android 9 and older (Google didn't test its own new methods on older devices?).
[Android Head-Units] rigattoni:
No problem with Android 9 on my side.

Edit: #30 shows version #29 in "about".
[Android Head-Units] HatManSan:
FCCL not working again for me. i was trying to make a backup I think, cant remember exactly but i was still configuring the Street Name widget i think when it crashed. Never had it back since.

https://drive.google.com/file/d/10PS0qeW5V2-Q6894z3kToxlutw1P9flF/view?usp=sharing
[Android Head-Units] bettuccio:
if you mean it got stuck on the black screen, it also happened to me while setting up the compass widget. I had to reboot the system more than once to reset everything. I am now back to test version 24 on my PX5
[Android Head-Units] HatManSan:
Everything was running normally until I was using the Wi-Fi Widget. Not the Wi-Fi BT widget buy the last one in the list. It kept changing to the BT symbol when placed. So I deleted it. I was setting up a button for TPMS with secondary text. I couldn't get the secondary text to show up. I may have tried to do a backup then it simply crashed and went to the familiar Close App or App Info screen. Never had FCC running again so far.
[Android Head-Units] HatManSan:
I would if i could find it. :(
[Android Head-Units] SpeedFire-:
You've deleted the log before I was able to download it :)
[Android Head-Units] HatManSan:
Sorry. :(

Latest Log with t30

Running t29 with no issues presently but not trying Mapbox until you say it is ok to do so.

Anyone have an accurate data usage for using Google Maps just as a "where I am now" map. Using Sygic to go places. Thank you
[Android Head-Units] okij:
To give accurate data is a bit difficult, because it depends on your usage pattern (how often you use it, how many new areas you visit). Some of the map data is buffered, but you don't have an influence on it, it's handled by the Google Maps API.

IIRC for me it was about 50 MB of data usage per month before Covid (still doing partly home office now), anyway much less then the montly data usage of app updates via Play Store.

Btw, I'm also using Sygic for navigation.
[Android Head-Units] HatManSan:
okij, thank you. Ah so not much then. I have a 4G modem in the car with a 24Gb SIM in it that lasts 2 years. I figured I might use Google Hybrid view in the future. I always wanted to but as Mapbox was data free I thought that was the best way to go. Sygic Premium+ with Speed Cameras etc is fantastic. My only complaint is the overlapping speed and speedometer on the main page. I wish I could separate and move them :)
[Android Head-Units] HatManSan:
Does anyone here on the FCCL thread have a copy of the Xtrons TPMS apk or know where it is please.?
[Android Head-Units] SpeedFire-:
New test version with bug fixes: fcclauncher-3.442_test32.apk
[Android Head-Units] HatManSan:
Excellent. I shall try that today and post back. Thank you for your continuous input.
[Android Head-Units] ric69:
My px30 is definitely too slow and not powerful enough for FCC launcher, too much freeze, 1 or 2 minutes to open and app. I will stay with stock for now
[Android Head-Units] SpeedFire-:
What fcc version did you try? PX30 should be fine for the launcher.
[Android Head-Units] okij:
Thanks a lot! This seems to have fixed some fcs and "app not reacting" that I had with test29. :)
[Android Head-Units] okij:
@SpeedFire-: Even though it got better with test32, I still have issues after waking my head unit from standby. :( FCC hangs when resuming after standby ("app not reacting") and it takes a while until it works well again. I'm not quite sure if it settles again or if it force closes and restarts.

I also observed that the compass rose of the compass widget sometimes isn't displayed, instead only the km/h display which I selected as text for the compass widget is shown. So it might be that something with the hardware accelleration isn't working correctly (as I didn't have this problem before you implemented hardware acceleration). Maybe it isn't properly resuming after standby. I have whitelisted FCC Launcher in Hal9k Mod v4.2.1, but this has been working very well before.

Please have a look at the attached Logcat log, e.g. starting from 07-15 07:53:48 when my head unit woke from standby this morning. I hope that you can get from useful information from it. 🤞 Specs of my head unit are PX6 MTCE MX, running on on Android 9 Hal9k Mod v4.2.1. Please tell me if you need some further help or infos.
[Android Head-Units] HatManSan:
No issues for me. Not tried Mapbox as I am liking Google. Thank you.
[Android Head-Units] tonimontoia:
with the test 32 from yesterday started at each power on application stopped bo
[Android Head-Units] okij:
So I'm not the only one who has issues with the recent test versions.

What do you mean with "bo"?

Please also take a Logcat log for @SpeedFire-.
[Android Head-Units] tonimontoia:
bo = I don't know
[Android Head-Units] SpeedFire-:
This required a lot of efforts but I've found some solution for backups and mapbox:

1) Backups/restores should now work on all versions of Android even after the Google's introduced new restrictions in Android 11. Now you can even save backups to any subfolder of the Downloads folder.

2) MapBox map is updated to the latest API and offline map works again but with some changes. Offline map should be saved to the App-specific folder on sdcard (/sdcard/Android/data/ru.speedfire.flycontrolcenter/files/Download/tiles/). This is done almost automatically:

- If you download the map from the Launcher for the first time - it will be saved to the correct folder automatically.

- You will also have an option to select the .mbtiles file manually and it will be copied to the app-specific folder.

The only downside is that the app-specific folder is deleted when the launcher is uninstalled.

The new test version: fcclauncher-3.442_test33.apk
[Android Head-Units] okij:
Thanks a lot, I'll install it tomorrow.

Did ypu have a look at the Logcat log that I posted here two days ago? Any clues or fix for those FCC freezes yet?

Edit: BTW, the link in your post is not working.
[Android Head-Units] SpeedFire-:
One "activity not responding" bug is fixed.

Link is also fixed. Thanks!
[Android Head-Units] mrmole2021:
Brilliant launcher! Kudos to the dev for continuing the development and support of this product, I feel it has the potential to become one of the best launchers. It has given me most of the customisation and control abilities without using a custom ROM.

I would like to report a small issue (like some others previously in this thread), and that is that the brightness controls don’t respond on my unit. Volume controls work great though.

The other minor issue I have spotted is that the mini player widget doesn’t seem to be able to control the built in a2dp (Bluetooth music streaming) app - although this is probably not the launchers fault! The built-in software for the head unit is not great. The player widget does show the artist/track name, just the controls don't respond.

I am running FCC Launcher (Premium) 3.442 off the Play Store. My system is a 1-week old Dasaita PX6 running stock Android 10, MCU is MTCE_HA_V3.78 (dated May 31st).

I'm no Android guru and I don't have root on this unit so my troubleshooting and info gathering ability is probably limited... but if there is anything I can do to help, let me know!
[Android Head-Units] tonimontoia:
always crashing on every boot shame
[Android Head-Units] SpeedFire-:
Yes, I see the freeze issue on my test devices as well. I'll try to fix it (the exact reason is not clear yet).
[Android Head-Units] SpeedFire-:
Here is a new test version where I tried to fix some of these issues: fcclauncher-3.442_test34.apk

Let's test it together and see if it works better or not.
[Android Head-Units] SpeedFire-:
Based on my tests the last version 34 still has these issues.

The issue is that the system process (Widget Host) is dead for unknown reason. This process holds the widget views in its own system process and updates them. This process is working outside the launcher. Launcher only sends updates to this process. I call this type of update a remote type.

Someone suggest that widget host may become dead because of hardware acceleration - link

I cannot drop hardware acceleration because of a need in more complex and smooth animations.

So here we come to the new approach. This approach was prepared by me during rewriting of the widgets. This approach is - switching to the local type of updates. What does it mean:

- All the (rewritten) widgets will be updated and drawn directly inside the app, without using system processes like Widget Host.

- This should be a much quicker and cost effective process for CPU.

- Widget work should be more reliable

- However this means that Fcc Widgets cannot be used outside the Fcc Launcher (in other launchers) like now, because they are not a "normal remote widgets" anymore, they are local views inside the Fcc Launcher.

- The other temporary downside is that not all the widgets are rewritten at the moment, but I will do this in the future.

So here is a preview of the local approach implemented. All the rewritten widgets in this version are forced to a local type of update (previously only Analog Clock and Compass widgets were in this mode). The widgets which are not yet rewritten continue to work in the remote mode but may stop working if the Widget Host becomes dead (so this will require a launcher restart).

Initially I wanted to wait until all the widgets are rewritten, but now it seems reasonable to show a current preview.

This is a preview version: fcclauncher-3.442_test35_local.apk

Please test and describe how this new approach works for you.
[Android Head-Units] okij:
I would say that this is not a problem for most (if not all) users, because we wouldn't have the other benefits that FCC Launcher offers when using its widgets with a different launcher. Until now I didn't even know that this was possible. ;)

Thanks for the new preview version. I just installed it and shortly tested it (not long enough to tell if the dead widget host issue still exists.)

However, in both test34 and test35 versions there are big issues when switching players:

When using the Player widget to switch players, it doesn't react at all and always stays at the currently active player.

When using the Mode widget, the players are switched but do not start playing. I have to manually enter the players and turn on playback.

It would be great if you could fix those issues quickly, since they break some essential functions of FCC Launcher.

For now, I'll keep test35 installed and see for the next two days if the dead widget host issue appears again.

Thanks again for your great work!
[Android Head-Units] rigattoni:
I also think there is no problem that widgets don´t work outside Fcc. I have seen some guys using your widgets in other launcher, but tbh... not your problem at all.

If someone uses another launcher, he should live with the available widgets, that´s it.

Didn´t try yet 34 and 35, but will give 35 a try tonight.
[Android Head-Units] okij:
Looks good so far. Today I woke the head unit three times from standby and FCC didn't freeze.

I will report back if it stays like this also tomorrow, then it should be safe to say that this issue is fixed (usually I had the freezing at least once per day).

Hopefully you can also fix the player switching issues soon again. :)
[Android Head-Units] rigattoni:
I can confirm the player issue.

I am not able to switch to any player. I need to open the player and change the station (DAB-Z or Online radio) and then the new player starts playing. First after doing this, the widget on Fcc is updated.

@SpeedFire- if you need additional logs, please ping me.

Freezes are not visible on my PX6 unit.
[Android Head-Units] squarefw:
does radio problem fixed? The quick player radio doesn't work on my TS9-SP9853 head unit
[Android Head-Units] squarefw:
How did you replace default radio app, I also want to replace it with NavRadio
[Android Head-Units] tonimontoia:
after 2 days of everything ok again the sudden crashes,
[Android Head-Units] wifi7501:
I have the same problem, spotify is not running, I went back to an old version.
[Android Head-Units] dape16:
No more force closing for me after updating to test35.
[Android Head-Units] okij:
@SpeedFire-: Also on the 2nd day of using test35 I didn't have any freezes or force closing, so this issue seems to be fixed for good. (y)

Did you have a look into the Player and Mode widgets issue (switching players not working) yet?

This issue was introduced just two test releases ago, so it should be easy to fix by reverting the according commits, as it was perfectly working before.
[Android Head-Units] SpeedFire-:
Can you please show on video what exactly doesn't work.

In my tests quick player selection works fine.

Btw, I started to rewrite the player widget. It is one of the most complex widgets so this will take some time.

If someone wants to suggest some new player widget layouts please send me the images (this could be layouts from Car Play, other launchers, players or apps).
[Android Head-Units] okij:
Here you go. :)

I attached both a video (zipped, so I can attach it on XDA) and another Logcat log, saved shortly after taking the video.

What you can see is:

Tapping on the player buttons of the Player widget shortly shows the information of the selected player but then jumps back to the previous active player again, which keeps playing all the time.

Tapping on the Mode widget changes the players, but playback stops and the new player doesn't start playing.

Manually starting players after opening them works of course.

When tapping on the player buttons on the Player widget and then *quickly* tapping on the image area in the Player widget (before it jumps back to the previous player) opens the selected player as expected, which then starts playing (either automacially or after pressing the playback button in the player itself).

Please don't be confused that both DAB-Z and UKW (=FM) Radio play the same song, because I have set the same radio station. ;)

I have the strong assumption that the players actually change correctly by both using the Player or the Mode widget, but that in both cases FCC doesn't send the needed "play" command / intent anymore. This leads to a) the Player widget jumping back to the previous active player and b) the Mode widget changing players without starting them.

As I already said, which was always working properly until about two test releases ago (IIRC until test33).

Please have a look into this. If you need some more infos, please let me know. Thanks. :)
[Android Head-Units] SpeedFire-:
Thank you for your video and log and especially for pointing to the exact test version.

I went through the latest changes and probably found the issue.

Please check: fcclauncher-3.442_test36.apk
[Android Head-Units] okij:
Thanks for your fast response! :)

I will check it this evening, in about an hour.

One question: Does it still contain the local approach which you implemented in test35? (I hope so.)
[Android Head-Units] SpeedFire-:
Sure. All new test versions will have a forced local type of widgets rendering enabled (if it works fine).
[Android Head-Units] okij:
The issue is fixed in test36, thanks a lot!! :)
[Android Head-Units] shdwkeeper:
So using the mini-map without a developer key, I can use the navigation app Waze for the routing and than switch back to mini-map and it will have the routing on there? Is that how this is supposed to work?
[Android Head-Units] SpeedFire-:
No. Please read a FAQ in the first post.
[Android Head-Units] shdwkeeper:
Yeah, I figured it out. Thanks.
[Android Head-Units] HatManSan:
Installed t36 today. Zero issues issues thus far. GS MCU3.62/HAL 4.2.1
[Android Head-Units] Сергей87:
На ГУ Teyes не восстанавливает и не сохраняет настройки и не перехватывает кнопки руля
[Android Head-Units] SpeedFire-:
Please write in English here.

Backup / restore is working again in test versions (you can find link in some of my latest posts).

Wheel buttons mapping is not available for all head units. Teyes is not integrated in this part.
[Android Head-Units] wifi7501:
I have installed 36, but there are always problems with media images, sometimes just go right and then forward and the image appears.
[Android Head-Units] SpeedFire-:
Just wait for the next test version. I am currently rewriting the Player Widget.
[Android Head-Units] wifi7501:
Nice !
[Android Head-Units] mariodantas:
Oh, this is the moment I'm waiting for.......

Just think about TPMS plug-in, autostart if at least one tpms widget is present
[Android Head-Units] wanze2001:
How can I sort the apps? Currently they are sorted by alphabet, I would like to have the order for the important kit, so arrange it myself
[Android Head-Units] rigattoni:
You can put all important apps on a second page of the Launcher. Free sorting of apps is not available in the apps overview page. It´s sorted alphabetical since a long time, almost ever.
[Android Head-Units] SpeedFire-:
Now I understand why Player Widget is the most complex widget in the Fcc Launcher. So many days were spent rewriting it :)

Here are the first results of rewriting it. Not all the features are available but most should be.

In this test version new Player Widget is a separate widget (not yet replacing the old Player Widget) so you need to add it manually for tests (this widget will be the first in the list with a Lab icon).

Do not replace your old widgets with the new one because in some of the next test versions this will be done automatically. Old Player Widget will become a New Player Widget. All the currently added New player widgets will disappear. So put them only for tests.

New version: fcclauncher-3.442_test40.apk
[Android Head-Units] mariodantas:
Thanks for that SpeedFire
[Android Head-Units] SpeedFire-:
Please send your feedback on the new player widget.
[Android Head-Units] mariodantas:
Ok did the test, the widget is fine, fully customizable, love it

But still facing the album-art issue where the album-art shown is the one of the previous listened music
[Android Head-Units] SpeedFire-:
I don't have such issue in my tests.

What player do you use?