Fcc Car Launcher [official thread]

[kill_one]

@SpeedFire- widget "go to page" still does not display the correct number of pages to jump...please can you check it? Thanks

 

[SpeedFire-]

@SpeedFire- widget "go to page" still does not display the correct number of pages to jump...please can you check it? Thanks

Sure, thanks!

 

[SpeedFire-]

@SpeedFire- widget "go to page" still does not display the correct number of pages to jump...please can you check it? Thanks

Please try this - fcclauncher-3.442_test129.apk

 

[okij]

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)

I can confirm that the secondary text is fixed in test128, thanks a lot!

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:

1. 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.
   
   
2. 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!

 

[SpeedFire-]

I can confirm that the secondary text is fixed in test128, thanks a lot!

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:

1. 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.
   
   
2. 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!

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.

 

[okij]

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.

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?

 

[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!

 

[SpeedFire-]

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?

I've probably reproduced it and hopefully fixed. This version is also back to 950 ms.
fcclauncher-3.442_test131.apk

 

[ric69]

Onesky fr language updated thanks for your work. Better & better as always

 

[okij]

I've probably reproduced it and hopefully fixed. This version is also back to 950 ms.
fcclauncher-3.442_test131.apk

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.

 

[mariodantas]

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.

Same behaviour here test131
uis7861 6Gb/128Gb

 

[HatManSan]

Just installed t130b. This is getting ridiculous now.

 

[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).

 

[okij]

Just installed t130b. This is getting ridiculous now.

View attachment 5522663

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.

 

[rigattoni]

Okay, German translation in OneSky updated too.

 

[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.

 

[SpeedFire-]

@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).

I've made some changes to the brightness widget - fcclauncher-3.442_test132.apk

 

[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!

 

[_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?

 

[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