yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
Thanks for your explanation! I wouldn't have come up with that, but now - knowing this explanation - it really makes sense.

For me it looks as smooth as before, so no problem at all.

Thanks! :)

In terms of bugs there's currently only one small issue left on my FCC home screen: Since you rewrote the Combined Trip widget, the secondary texts (like "km" and "km/h") are not displayed anymore. I tried to fix it by changing the widget configuration, but I did not succeed, so I think that it's a minor bug. Please have a look after this if you find some time.

Edit: I forgot about one more minor bug that I've already reported: The Brightness widget doesn't reliably show the current screen brightness, e.g. this evening when starting the car it again showed full brightness (plus "A" for activated auto brightness), although it should have showed lowest brightness, as the screen was actually set. So the screen brightness is properly controlled by auto brightness and it's only a display issue of the widget, but still it should be fixed.
[Android Head-Units] segu45:
I also confirm that the minimap now works fine, it runs even smoother than before. Thanks for the work you do with this very good launcher.
[Android Head-Units] SpeedFire-:
fcclauncher-3.442_test128.apk

- Secondary text for TripCombined widget fixed (don't forget to check that Secondary text is enabled in the widget's text settings)
[Android Head-Units] SpeedFire-:
I checked camera tilt settings. The app tries to apply maximum tilt value available to the camera. You're right that you can change it slightly more with your fingers, but this is not available to do programmatically.
[Android Head-Units] kill_one:
@SpeedFire- widget "go to page" still does not display the correct number of pages to jump...please can you check it? Thanks :)
[Android Head-Units] SpeedFire-:
Sure, thanks!
[Android Head-Units] SpeedFire-:
Please try this - fcclauncher-3.442_test129.apk
[Android Head-Units] okij:
I can confirm that the secondary text is fixed in test128, thanks a lot! (y)

Since you are currently ironing out the final bugs before the reworked FCC Launcher can be released on Play Store, I'd like to give you some feedback about the remaining issues that I noticed:

As I added to my post #8,537 yesterday and reported before, the Brightness widget doesn't reliably show the current screen brightness. Today I had a closer look on this issue and as it seems, the widget is updating properly while the head unit is in use, but doesn't show the correct brightness symbol after I wake my head unit (MTCE on Hal9k v4.2.1) from standby.

So in my point of view, you must add some code that updates the widget symbol according to the current daytime (respectively screen brightness) after the device is resumed from standby.

Today I also had a closer look on the updated animation times of the Mini Map which you explained here. While the map looks smooth when driving straight on, it unfortunately looks quite bumpy when driving a curve. I then can cleary see the animation stopping for 0,2 s each second.

I've been thinking about what you could do against this (without getting the map-not-loading bug back) and I would suggest that you set the camera animation period to 950 ms or so (maybe also 990 ms could work). I'm suggesting this because it's quite likely that the map properly loads as long as it gets triggered to do so, for which 50 ms (or maybe even 10 ms) should be sufficient. I cannot imagine that the process which loads the map gets interrupted while the map is animated (and of course I hope that I'm right with this assumption).

Could you therefore please make a test version with a camera animation period of 950 ms, so I can try it and report back? If it works and if it then should still look not smooth enough, we could then try 990 ms or something like that. IMHO this should help to get the animation as smooth as it was before the bug fix, with the map still loading properly.

Thanks for your attention and once again for your great work on FCC! :)
[Android Head-Units] SpeedFire-:
1. I tried to reproduce brightness widget bug but couldn't.

2. Here they are:

fcclauncher-3.442_test130a.apk (950 ms)

fcclauncher-3.442_test130b.apk (990 ms)

Actually I can set separate times for straight movements and turns (angle more than x). So theoretically this could be solved this way.
[Android Head-Units] okij:
Thanks for providing the test versions so quickly! :)

I just tried them in my underground parking, so I didn't have good mobile data connection for the head unit and had to use Mock Locations app.

The good thing is that even the 990 ms version loads the map tiles, so generally it's working. However, it seems to me that at least the 990 ms version needs a bit more time to load the map tiles, but this could also be caused by slowish the data connection. The 950 ms version seemed better in this aspect.

But both versions also didn't supply smooth animation, both also were interrupted much more than 50 respectively 10 ms each second. It might be that this is caused by the GPS signal updated only every second, but for testing I was using Mock Locations app and I don't know if it maybe only updates once per second.

When driving normally, I have set Hal9k rom to update GPS with 5 Hz, so every 200 ms. Maybe I'll have to check test130a (950 ms) when I'll be driving next time (probably this weekend but definitely on Monday) in real GPS use. I have kept test130a installed for now.

BTW, I also shortly tried test125 again (the one before you fixed the Mini Map) and it also didn't supply smooth animation but stopped animation for a short time each second. Having said this, it could be that the map display isn't less fluent now than before the Mini Map fix but that I only thought so because now I especially looked after it. ;)

About the Brightness widget: After starting the head unit for trying test130a and b, I again observed that the widget erratically showed full brightness (+ "A" for auto) and only went back to correct display after tapping on it 4 or 5 times to get to "A" again.

So for me this seems to be reliably reproducible each morning and evening, I don't know why you cannot reproduce it. Do you need any more infos or logs? And most importantly: Does FCC already have some code that sets the Brightness widget to the correct icon after the head unit is woken from standby?
[Android Head-Units] Andason74:
I have used FCC launcher for many head units and CarPlay air devices. Works very well.

I wish there was more support, encouragement etc of themes for this launcher.

Good job!
[Android Head-Units] SpeedFire-:
I've probably reproduced it and hopefully fixed. This version is also back to 950 ms.

fcclauncher-3.442_test131.apk
[Android Head-Units] ric69:
Onesky fr language updated :) thanks for your work. Better & better as always
[Android Head-Units] okij:
Thanks, I've just installed it.

As a first feedback: Directly after installation the symbol showed lowest brightness and "A", whereas correctly it should have shown highest brightness and "A", because it was 3:30 pm here and about 1,5 hours till sunset.

Also cycling through the Brightness widget to "A" again didn't change this, it still showed lowest brightness and actually the screen was at its lowest brightness.

Because of this I entered FCC settings and looked into the auto brightness settings (which were correct) and toogled auto brightness off and on again. After this, the screen correctly was at its highest brightness and also the Brightness widget properly showed the sun icon for highest brightness and "A". Cycling through the Brightness widget to "A" again then also worked as expected, i.e. highest brightness plus "A" was correctly used and shown.

So maybe there is a small bug in your latest change which needs the auto brightness in FCC settings to be checked and toggled off and on as a workaround. For me this doesn't matter if it's something that has to be done just once.

I will further observe if the auto brightness and the Brightness widget display now behave correctly and will report back.
[Android Head-Units] mariodantas:
Same behaviour here test131

uis7861 6Gb/128Gb
[Android Head-Units] HatManSan:
Just installed t130b. This is getting ridiculous now.

View attachment 5522663
[Android Head-Units] okij:
@SpeedFire- I checked now again after sunset: The screen brightness was at its lowest setting (so OK), but the Brightness widget showed the highest brighness symbol (sun) plus "A".

Only after cycling through the Brightness widget until "A" is displayed again then showed the correct lowest brightness symbol (circle) plus "A".

I will check once more tomorrow, but I think that unfortunately test131 didn't fix the Brightness widget issue yet (MTCE device here).
[Android Head-Units] okij:
Aha, so the dev should now start to guess what's wrong based on your screenshot? Seriously?

Please give more details like:

Which version did you use before?

How did your layout look before?

Did you try if restarting FCC fixes the issue?

Did you try if restoring a backup of your working FCC config fixes it?

Did you try if restoring your previous version (plus maybe a backup of your config too) fixes it?

Did you think about providing @SpeedFire- a backup of your working config for checking what might be wrong?

...

After all these are test versions and meant for testing and reporting bugs. Just saying "this is getting ridiculous" is only offensive, but not helpful at all.
[Android Head-Units] rigattoni:
Okay, German translation in OneSky updated too.
[Android Head-Units] HatManSan:
@okij valid but I have posted so many screenshots that I didn't think it was necessary. Last version was t129. I posted that too. The dev has my last backup and nothing has changed.

In the meantime. I formatted the HU. reloaded HAL9k ROM. started from scratch. Restored backup etc. Exactly the same screenshot was generated. However for completeness, I have included my backup, which hasn't changed in months now. FCC BU

Don't think IU am ungrateful. I have posted many times the high regard I have for the @SpeedFire- but it only seems to be me, who's HU goes tits up so wrong.

View attachment 5522807
[Android Head-Units] SpeedFire-:
I've made some changes to the brightness widget - fcclauncher-3.442_test132.apk
[Android Head-Units] spludgey:
Is there a way to disable the screensaver screen?

Is it also possible to disable all other windows? My widgets keep running away when I try to place them, very annoying!

Are there any skins for higher row and column settings?

Thanks!
[Android Head-Units] _Trolk_:
Is it possible to set an autostart so that after starting the FCC launcher automatically switches to the split screen mode with google maps?
[Android Head-Units] csr1:
Hey there, i just got a china tablet yesterday got it all working just not enable notifications its somehow deactivated in tablet to safe ressources? Is there a Workaround maybe, ive googled the whole night lol

Android 10 (go?)

Api 29
[Android Head-Units] peleakan:
I manage to do so by using an application call Split Screen Launcher which generates a short cut for 2 app in split mode. But to use it with FCC, I have to play with Tasker to sequence the start up. It is a bit of a mess to find the correct timing and the result is sometimes random.

It would be a great feature if you could configure the existing FCC start scheduler to allow start in split screen with FCC homepage beside another app (Maps, Waze...)

Here is part of my Tasker script:

View attachment 5523363

And the result (when everything starts correctly...)

View attachment 5523367
[Android Head-Units] SpeedFire-:
Have you just updated to the new version or made a clean install and restored from bacup.

I restored from your backup and first time it looked like on your pictures. Then I restored a couple more times and it restored well.

This is clearly a bug with database restoration. I will look to make it restore from the first time. Thanks for reporting!
[Android Head-Units] okij:
Thanks again! :)

As a first feedback: After installation this afternoon the Brightness widget properly showed highest brightness + "A". Now after sunset I checked it again after waking the head unit and it properly showed lowest brightness + "A", so it seems that test132 fixed the Brightness widget issue! (y) Tomorrow I will keep an eye on it if it works well in everydays use and give you another feedback.
[Android Head-Units] IAmNotMe01:
wooow , nice skin man, can you please share it? :)
[Android Head-Units] SpeedFire-:
fcclauncher-3.442_test133.apk

- Possible fix of restore from backup process

- Pics on buttons in widget's settings are finally visible
[Android Head-Units] kill_one:
Thanks! Number page now is ok

but the widget alignment is different from the old ones

@SpeedFire-

is this an error or is this last alignment correct?
[Android Head-Units] HatManSan:
t133 has repaired the restore function. Thank you.
[Android Head-Units] okij:
After using test132+133 for today too, I can give you the following feedback about the Brightness widget:

Yesterday evening the Brightness widget was correctly showing lowest brightness + "A", as already reported.

This morning the Brightness widget was correctly showing highest brightness + "A".

I didn't drive during sunrise or sunset, so I cannot confirm if the icon of the Brightness widget adapts properly while the head unit is in use, but I guess (and hope) that this should work too.

This evening the Brightness widget was correctly showing lowest brightness + "A".

Unfortunately the Brightness widget didn't react to button presses this evening, although it is properly set up, as you can see in the attached video. This issue could only be solved by manually restarting FCC.

I would like to report that the Brightness widget bug is fixed, if it weren't for the fifth point. For some reason the Brightness widget didn't response to button presses, which shouldn't happen.

Please tell me if you need a logcat too to fix the remaining issue, I could then go to my car and save it.
[Android Head-Units] SpeedFire-:
Thanks for testing!

Yes, Log may help. Please use this version. Here Debug is on for Brightness Widget: fcclauncher-3.442_test134.apk

I've also made some small change that could theoretically fix this bug. However I couldn't confirm / test it as it is not reproduced on my device.
[Android Head-Units] okij:
OK, thanks, I will try test134 tomorrow and report if this bug happens again. Please keep the debug logging for the brightness widget enabled in the next test versions too, as we don't know yet if this bug maybe happens only every couple of days. I will report back if it happens again, including log.

Does this mean that you don't need a log from when the bug happened this evening (since it doesn't contain debug infos)? If you need a log from this evening anyway, please tell me.

I also wanted to give you some feedback about the MiniMap in everydays use with the 950 ms animation period: It looked the same as the tests I did with Mock Locations app last weekend, i.e. it is noticable that the map animation gets interrupted once per second and the interruption feels longer than 50 ms. I didn't check again with the 800 ms build, but I would say that the lack of smoothness is similar. As I already wrote, this might have been the same in all older versions, just that I never paid attention to it. Map loading was OK with the 950 ms build, but to be on the safe side (and as long as you don't get feedback from other users) I would suggest that you set the animation period now to 900 ms, so it could be a bit easier for slower devices and/or with slower internet speed to load the map on time (I use a PX6 and a 4G Wifi dongle).
[Android Head-Units] segu45:
Updated the language to Spanish.

I have tried the last update of the mini map and yes, sometimes it has a little delay, but it only happens when you have activated the zoom depending on the speed. When you accelerate on the highway and the speed increases rapidly, the equipment needs a time between zooming and reloading all the data to see the traffic in real time. This is significantly slower depending of the device . I will test with the automatic brightness widgets, so far it has worked well for me.
[Android Head-Units] rigattoni:
Let's do a little advertising... ;)

You folks, reading in silence or contributing in here with testing, finding issues or just reading and contributing from others...

There are still a lot of languages not fully translated to your mother-languages. May be a good chance to support @SpeedFire- and translate the missing phrases. What do you think?

You just need to create an account at https://www.oneskyapp.com/ and you can contribute to this great launcher at https://osd2jt2.oneskyapp.com/collaboration/project?id=317150

Just make a move and help him to get the app for all languages.

Unfortunately I just can put in German translations and that is what I did.
[Android Head-Units] kamilwar:
Hello SpeedFire-,

My device is a Junsun V1 Pro 6/128.

Model: 825X_Pro (full_825X_Pro)

Board: 825X_Pro

Chipset: AC8257V/WAB

I have a weird problem with FCC at startup of my device. It loads normally but after about two minutes all widgets disappear and FCC is unresponsive.

Any idea what might be the issue?

Logcat and bootup video
[Android Head-Units] SpeedFire-:
Interesting. Thanks for reporting! What version of the app do you use?
[Android Head-Units] kamilwar:
I tried the Play Store version and the test versions. Currently, I'm using fcclauncher-3.442_test133.
[Android Head-Units] riccardone1:
Hello,

for a few weeks the minimap has not worked properly. He struggles to load maps, shows them in low resolution and then loads them in high resolution. Sometimes the map is completely blank. This problem had never occurred before. Does it happen to you too?
[Android Head-Units] SpeedFire-:
Please try the latest test versions. This is already fixed
[Android Head-Units] SpeedFire-:
This video and log was recorded on a test version, right? Does it happen every time? Can you please record another one with video (and please add seconds to the Time widget so it is easier to identify the exact moment).
[Android Head-Units] kill_one:
even with the T133 fcc it continues to close when trying to assign the steering wheel control buttons.

does it just me this problem?
[Android Head-Units] SpeedFire-:
Based on your previous Log your device doesn't have a CarManager (a part of deep integration) and that's why it crashes.

It looks like if you've selected incorrect device type (Rockchip instead of AllWinner for example) or your device is completely different from the previously integrated.

Can you send me all your system apk files and show your device type?
[Android Head-Units] VMPhil:
Ill keep it in mind :good:
[Android Head-Units] steef84:
Exact same unit, exact same problem when trying to install via Google Play. What could this be? Are you distrubuting fcc on other channels than Play Store?

Wanna try this launcher very much [emoji41][emoji41]
[Android Head-Units] SpeedFire-:
Do you have all of this on your device?

- bluetooth

- touch screen

- location.gps

- microphone

- wifi

Anyway try to install this beta as apk: beta
[Android Head-Units] steef84:
Yes, got this Carjoying. Its capabel (I assume [emoji41]) of bluetooth l, touchscreen, gps, microphone and wifi.

See specs here: https://www.carjoying.de/octa-core-android-head-unit-car-stereo-jy-um135p2.html

Will try the apk though asap! Can I provide more info to possible fix?
[Android Head-Units] SpeedFire-:
I will upload a new beta to the Play Market soon (where I have disabled requirements for microphone, bluetooth and wi-fi). Please first try to install it from Play Market again (don't forget to sign-up as a beta-tester) and only if unavailable install from apk.

New beta (2.517) is uploaded, will be available soon. I have included a half-baked new feature, it will be improved later:

- [Temporary] When you drag an icon to your home screen it automatically adds as a widget. In next beta you will have a choise how you want to add it: as an icon or as a widget.
[Android Head-Units] sarruma:
Hi, thank you so much for your efforts, your launcher is amazing!

Could you please include, in your next beta, full support for BlackPlayer Ex https://play.google.com/store/apps/details?id=com.kodarkooperativet.blackplayerfree&hl=el or the Pulsar Music Player https://play.google.com/store/apps/details?id=com.rhmsoft.pulsar ?

They are both quite popular among music lovers so I believe that others will appreciate this feature too!

Thank you in advance and keep it up!
[Android Head-Units] vassandrei:
How can I make my fcc launcher look like this?? Is there a preset like this already included in the app?

---------- Post added at 01:27 ---------- Previous post was at 01:26 ----------

How can I make my fcc launcher look like this? It’s really very slick! Is there a preset included somewhere I just haven’t found?
[Android Head-Units] steef84:
Oke, on my px5 unit the beta app still doesn't install via Play Store. Installed it via apk. Here is a prinstcreen of my message.
[Android Head-Units] VMPhil:
Hopefully that will work around my issue!
[Android Head-Units] Roerbakeitje:
Yes when you follow the beta program. It's under skins .
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

Little request from a friend of my. To add xiialive pro. (Radio broadcaster)

He said it works with unknown player but not start automatically.

https://play.google.com/store/apps/details?id=com.android.DroidLivePlayer
[Android Head-Units] SpeedFire-:
New beta is out:

- Icon drop on home screen looks better (no blinking screen, this may look like a simple thing but it was really hard to do).

- IconWidget -> Shortcut switch. You can now get back to a normal Shortcut after dragging an app to your home screen (by default it will be added as a widget but you can choose to switch back to a shortcut - see notification to the bottom of the screen)

- BlackPlayer support is added

- Yandex Radio support is added
[Android Head-Units] SpeedFire-:
Another beta:

- XiiaLive Pro player is integrated

- Fixed color change for custom skins: sub-colors are also applied now

- Right panel can be hidden in Free version of the launcher
[Android Head-Units] Roerbakeitje:
Thank you Speedfire for the really fast fixes.
[Android Head-Units] pa.ko:
Thank you for fast fixing!

Could you also take a look into why on initial load media widget is not rendered properly (buttons are positioned to the right instead of center - gets good after few seconds but looks ugly at first load). I believe it has something to do with layout missing initial synch with players so it may be "easy-fix" (yeah I know - there are easy-fixes as there are free-dinners :p) to change layout in order to position media control buttons correctly without need to get info from players. It would be even Ok to render all buttons as "disabled" until synch with players is done (but to have them positioned where they should be according to widget layout selection).
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION].

When I want to make a custom skin what must I do?

First make framework 6 by 9 ?

Must it be full transparent ?

What is t uhhhhhe best frame setting for 1026x600 ?

Do we have by custom a template for different resolutions ?

Sorry alot of questions:D

Edit: can someone give me the skin for minimap?

I whant to edit it. Thank you .
[Android Head-Units] SpeedFire-:
- Currently most skins are for 6 x 7 grid, but you can choose your own grid for your skin

- Resolution should be the same as a screen of your device ( 1024 x 600 on most head units with all panels hidden). If you want to keep statusbar or left/right panel you need to reduce skin's resolution by the size of these panels.

- Yes, "skin" as a middle layer should mostly be transparent. But you can also make it non transparent if you don't want to see a wallpaper layer behind it and / or add some texture like here (this is a custom skin from a designer of most of our skins):