Fcc Car Launcher [official thread]

[okij]

fcclauncher-3.442_test126.apk
- Experimental version for Google Map fix. Camera animation time is decreased from 800 ms to 500 ms / every second. To left more time for map drawing. Does it help?

Thanks, I just tried it, but unfortunately the bug still happens on test126.

 

[SpeedFire-]

Thanks, I just tried it, but unfortunately the bug still happens on test126.

Hm... can you try to install some old test version and check?

 

[electrico.clax]

I have in my both cars OEM-TPMS in the tires, so I am not able to use the widget, because I see the messages in the cluster if there is anything wrong.

If the widget is already working like that, I would exactly have it like that nothing else.


As SpeedFire- already explained, use the widget as it is supposed to be used and it should be right.
Continuous data visibility is not the way it is you want to have and I don´t get the point that you want to have it constantly on the screen. Keep your eyes on the street and not on the TPMS and let the app do it´s work.

Fcc is not able to become one of the best launcher... Fcc is already the best you are able to get hands on.

Ok, i catch your poin, thanks for the sharing your opinion.

 

[electrico.clax]

fcclauncher-3.442_test126.apk
- Experimental version for Google Map fix. Camera animation time is decreased from 800 ms to 500 ms / every second. To left more time for map drawing. Does it help?
- TPMS widget. Previously it was set that if no new data is received for the last 15 seconds (normally it is updated every 10 secs) then "--" are shown. Now the period is increased to 45 secs.

Thanks @speedfire to your fast respons, very amazing.

 

[okij]

Hm... can you try to install some old test version and check?

Yes, I could do this as long as it basically works with my current FCC configuration.

Which older test version would you recommend to try?

 

[SpeedFire-]

Yes, I could do this as long as it basically works with my current FCC configuration.

Which older test version would you recommend to try?

I don't know to be honest. You better remember / try when this bug first appeared.

 

[okij]

I don't know to be honest. You better remember / try when this bug first appeared.

@uktim32 wrote in post #8,482:

I haven't updated FCC Launcher for probably 6 or 8 weeks. I'd say starting about a week ago I noticed as the map loads the oncoming top part of the display is blurred the eventually catches up with itself but this just repeats as you move with the map showing the new area you're moving into again blurred etc etc.

@SpeedFire- Also for me this bug started "out of the blue" maybe 2 or 3 weeks ago and not with a certain test build.

So I'm not sure if trying an older test build really helps, but I'll check one.

 

[SpeedFire-]

@uktim32 wrote in post #8,482:


@SpeedFire- Also for me this bug started "out of the blue" maybe 2 or 3 weeks ago and not with a certain test build.

So I'm not sure if trying an older test build really helps, but I'll check one.

That's why it is important to understand the possible reason.
Maybe this is caused by some issues with Google servers for example and is not caused by the changes in the app.

 

[okij]

That's why it is important to understand the possible reason.

Yes, of course. I just tried test90 from November (the build that fixed the ANR and FC bugs) and it has the same issue with Google Map display in the MiniMap. However, this was working fine some weeks ago.

Maybe this is caused by some issues with Google servers for example and is not caused by the changes in the app.

I also think that there must have been some change on Google's side, but nevertheless this issue must be fixed in FCC.

I'm sure that it can be fixed because the map display is correctly updated when swiping the map and only doesn't update when it's just following the GPS position.

Internet access for my head unit hasn't changed BTW, I'm using a Huawei E8372 4G-Wifi-Hotspot USB stick which has the same good speed like months ago, so this cannot be an issue.

I really hope that you find a solution, because the MiniMap is one of the features that makes FCC so unique.

Edit: P.S. Did you do some tests for yourself, e.g. with Mock Location app, as @rigattoni suggested here?

 

[monstereye1898]

I would think my minimap problems started when I updated hal9k to the latest version 5.0.2. I rebuilt everything a few days ago and with version 5.0.0 the minimap worked, however I did not test it extensively an now i'm back on 5.0.2 and it's not working. It may also be that it was a coincidence. It can't be because of the internet connection, it is very good. Yandex also works fine, but I prefer Google Maps.

By the way, I already had the problem with the version which is in the Appstore, so I only started with the test versions now.

 

[okij]

I would think my minimap problems started when I updated hal9k to the latest version 5.0.2. I rebuilt everything a few days ago and with version 5.0.0 the minimap worked, however I did not test it extensively an now i'm back on 5.0.2 and it's not working. It may also be that it was a coincidence.

This must be a coincidence, because I'm using Hal9k v4.2.1 and didn't update the rom in the last ten months.

By the way, I already had the problem with the version which is in the Appstore, ...

This is interesting for @SpeedFire- to know, so thanks for your confirmation of the issue and infos.

 

[uktim32]

That's why it is important to understand the possible reason.
Maybe this is caused by some issues with Google servers for example and is not caused by the changes in the app.

I was running a test version which I downloaded in November (I can't remember which one), I hadn't updated since until trying the map update. So I don't think it's something in an update that has caused the error either.

 

[SpeedFire-]

It seems that I "fixed" the wrong value in the previous version. Please try this:
fcclauncher-3.442_test127.apk
- Possible Mini Map fix (map loading)

 

[okij]

It seems that I "fixed" the wrong value in the previous version. Please try this:
fcclauncher-3.442_test127.apk
- Possible Mini Map fix (map loading)

Thanks a lot! I just tested it for 20 minutes and so far the map loading bug didn't occur anymore, so from my side I would say that it's fixed in test127. Well done!

May I ask what was the reason for this issue and how you now fixed it?

Also I have a small feature request for the MiniMap:

I'm using the MiniMap 99% of the time in 3D mode and then prefer to have it always at the maximum tilt angle. Unfortunately this doesn't always stick when e.g. swiping the map and also seems to be separately or differently stored for each zoom level, so I often have to swipe upwards with two fingers to restore the maximum tilt angle.

Could you therefore please implement a switch to have the MiniMap at maximum tilt level when 3D mode is activated?

 

[SpeedFire-]

Thanks a lot! I just tested it for 20 minutes and so far the map loading bug didn't occur anymore, so from my side I would say that it's fixed in test127. Well done!

May I ask what was the reason for this issue and how you now fixed it?

Also I have a small feature request for the MiniMap:

I'm using the MiniMap 99% of the time in 3D mode and then prefer to have it always at the maximum tilt angle. Unfortunately this doesn't always stick when e.g. swiping the map and also seems to be separately or differently stored for each zoom level, so I often have to swipe upwards with two fingers to restore the maximum tilt angle.

Could you therefore please implement a switch to have the MiniMap at maximum tilt level when 3D mode is activated?

It turned out that camera animation period was set to 1500 ms (1,5s) and GPS updates normally occur every second. So new animation overrided old animation and car marker was always moving (this was done for smooth marker animation). Now it is changed to 800 ms (0,8s), therefore each second camera moves for 0,8s and then stays (and loads map) for 0,2s.

The new approach should theoretically look like less smooth, but should solve the map loading issue.

Regarding the camera tilt - I will look how it is implemented now and what can I do. Thanks!

 

[monstereye1898]

Back from shopping and tested the version 126. Sometimes it works,

It seems that I "fixed" the wrong value in the previous version. Please try this:
fcclauncher-3.442_test127.apk
- Possible Mini Map fix (map loading)

I can confirm that it works, great job, THANKS!

that it is less smooth i could not determine, but i had to drive and could not always look at the navi

 

[okij]

It turned out that camera animation period was set to 1500 ms (1,5s) and GPS updates normally occur every second. So new animation overrided old animation and car marker was always moving (this was done for smooth marker animation). Now it is changed to 800 ms (0,8s), therefore each second camera moves for 0,8s and then stays (and loads map) for 0,2s.

Thanks for your explanation! I wouldn't have come up with that, but now - knowing this explanation - it really makes sense.

The new approach should theoretically look like less smooth, but should solve the map loading issue.

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

Regarding the camera tilt - I will look how it is implemented now and what can I do. Thanks!

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.

 

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

 

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

 

[SpeedFire-]

I'm using the MiniMap 99% of the time in 3D mode and then prefer to have it always at the maximum tilt angle. Unfortunately this doesn't always stick when e.g. swiping the map and also seems to be separately or differently stored for each zoom level, so I often have to swipe upwards with two fingers to restore the maximum tilt angle.

Could you therefore please implement a switch to have the MiniMap at maximum tilt level when 3D mode is activated?

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.