yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
@SpeedFire-

Recently I noticed an issue of the Minimap display, with Google Maps as maps provider:

When driving, the display very often isn't fully updated, i.e. only the layer with the colour areas of the streets, fields, woods etc. gets updated, but the contour lines of the streets etc., as well as the street names and other texts and also the 3d buildings and traffic informations (colour tint of the streets) are missing in the display.

Since often I see one Google Map tile (the one I'm currently driving in) with correct display and another (the next one in the direction that I'm driving to) with the missing contour lines etc. as described, I first thought that mobile data access is missing, so FCC cannot load the new tiles it needs.

But as I tested yesterday and today, this is not the case, because I checked if mobile data access was available, which was the case.

Most interestingly, the missing map elements are instantly displayed when I swipe the map with the finger, without missing map data being loaded (which would take some seconds, as I know from regular MiniMap usage). So the map data (map tiles) are already cached in memory, but only displayed when manually swiping the map, but not displayed when the MiniMap just does it's auto-update based on GPS position.

Unfortunately I cannot provide you a video, because I cannot and will not take a video when driving. But I hope that the descriptions that I gave are detailled enough. If you need more infos, please ask.

I don't know exactly when this issue started to happen, e.g. if it started with one of the latest beta versions.

Did you change anything MiniMap or Google Maps API related? Also, could this bug have been introduced by Google, so you have to update some code related to the Google Maps API?
[Android Head-Units] KoTiX2:
Hi huys, i want to show some progresses and discuss about them a bit...

This is the notification now for the dropdown menu on android 9 device:

View attachment 5512945

This is what FCC show:

View attachment 5512953

I cannot test interference with hal9k rom yet sorry, but is this what you guys needed from NavRadio?

I beleive that the datas RDS etc are taken from metadata and not from notifcation title, text and large icon...

Am i still missing something??
[Android Head-Units] okij:
From my understanding this notification is exactly what FCC needs to fetch the data for its Player widget display. But let's better wait for @SpeedFire-'s feedback. :)
[Android Head-Units] rigattoni:
Hi okij,

since long time I use the app Mock Location Path to test navigation software in a nearly life scenario.

Mock location path sends fake GPS routes instead of getting real GPS in the lab.

Nice thingy to check if the navigation does the turns, notification... you name it.

May be this is something you can use for a video instead.
[Android Head-Units] uktim32:
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.

Not sure if this is the issue you mean? If so it might be something Google related as I haven't updated FCC Launcher in a while.
[Android Head-Units] okij:
Yes, this describes it very well. Good to know that I'm not alone with this issue.

@SpeedFire- Is the MiniMap display dependent on e.g. the Google Maps version on the device, so it can get disturbed by an update by Google?
[Android Head-Units] SpeedFire-:
New version fcclauncher-3.442_test120.apk

Finally, ALL the remaining widgets are rewritten to the new format:

- TripCombined widget rewritten

- OBD widget rewritten

- Contact widget rewritten

This means that this long way of switching from remote updates to more responsive local updates is over.

Now we can concentrate on bug fixing and then upload this version to the official Beta channel.

Please test.
[Android Head-Units] SpeedFire-:
Looks great! Thank you!

Is this version already available for test?
[Android Head-Units] KoTiX2:
No, I'll upload it tonight on PlayStore.

Btw there are still some things not clear to me and surely i haven't finished to work on these notifications.

Right now in FCC i can see the logo and Infos correctly in the FCC widget but the FCC popup notification always show the NavRadio icon but not the logo.

It seem to me that the widget show the metadata from media session while the popup show the title and text from Notification.compat but not the Large icon that contain the logo.

I haven't tested this with hal9k rom yet but I'm pretty sure that everything will be even worst because of Halmod notifications interferences.

Anyway when in PlayStore is available version NavRadio 2.21 please give it a try ;)
[Android Head-Units] SpeedFire-:
This is probably because Google Maps have some interesting bug/feature. It doesn't download new tiles while camera is moving. I leave some time (several milliseconds each second) when camera is not moving during which Google can download data. If mobile speed is not enough it may fail to download everything during this period. When you drag the map camera is not animated and it downloads the data.

I saw that Google released a completely new Beta of their built-in maps SDK with new rendering capabilities. Now it is deprecated and will be part of a normal library update:

Using Maps SDK for Android v3.1.0 BETA | Google for Developers

developers.google.com

So maybe I already switched to this new map SDK when updated Google Libraries.
[Android Head-Units] SpeedFire-:
This is probably an issue on my side. Thanks. I will check when new version of NavRadio is released.
[Android Head-Units] SpeedFire-:
fcclauncher-3.442_test121.apk

The only change in this version compared to test120 is that I updated all the libraries to the latest versions and targeted the latest Google SDK 32 (Android 13?) instead of 31 (Android 12) previously.

So we can identify bugs (if any) related to this switch.
[Android Head-Units] okij:
Thanks! :) Does this also affect the Maps SDK, so the Minimap bug that I reported might be fixed again?
[Android Head-Units] okij:
Thanks a lot for your update with the support of media notifications! :)

I can confirm that it's basically working, i.e. the station infos from the NavRadio+ main screen are on the media notification, as you can see on the 1st and 2nd attached screenshot.

However, I get three different results in the player widget display, as you can see in the other three attached screenshots. None of these is the expected result, i.e. the RDS text is always missing.

I assume that this is caused by the fact that FCC Launcher currently still reacts to some radio intents that are broadcast by the Hal9k v4.2.1 rom that I'm using, so it has to be fixed in FCC.

@SpeedFire-: Please have a look after this, i.e. please let the Player widget now only react to updates of the NavRadio+ notification when NavRadio+ is in use, so it doesn't interfere with Hal9k rom (or the MTC Radio interface, if this could also interfere). Thanks. :)
[Android Head-Units] KoTiX2:
RDS text is not received within station name but a certain time after station is tuned.

So you will never see it right after changing station but only in a second time.

I'm running hal9k 5.02 now on my unit and i don't see all this interferences if i disable original radio app and Hal notifications for radio.
[Android Head-Units] okij:
Yes, that's what I expected, but I never see the RDS text even after waiting for a text update, that's the problem.

By "Hal notifications" do you mean toast messages or notifications in the pull down menu? I don't have activated Hal toast messages and don't remember that there are Hal notifications in the pull down menu or a setting for (de-)activating them, or am I wrong?
[Android Head-Units] okij:
Thanks a lot for the two new updates and congratulations that you finished rewriting all widgets now! :cool:(y)

I updated from test115 to test121 today and can give you the following feedback:

The Bluetooth widget had adifferent layout after the update (bigger space between logo and text), but I could manually change it to its previous look again.

Also the GPS Satelites widget had a different layout after the update (bigger space between logo and text), but I can manually change this as well again.

The TripCombined widget doesn't show the 2nd texts and I didn't manage to get them shown by adjusting the settings. Please compare the attached screenshots from before and after the update. According to the widget settings (which are the same as before the update) the 2nd texts should be shown, but they aren't, so this seems to be a bug.

The Brightness widget doesn't show the "A" anymore when automatic brightness is activated and I couldn't get the "A" to be shown by changing the widget settings, so this seems to be a bug.

Besides this (not test121 related, but checked with test115 on my MTCE head unit) the Brightness widget still doesn't seem to update to the correct icon according to the time of the day, please see attached video. I took the video in the evening, so the icon of the Brightness widget should have been at low brightness already, but it still showed full brightness. Only after cycling through the brightness settings by tapping on the widget, the correct icon is shown, as you can see in the video. The auto brightness function of FCC itself seems to work well, only the icon display is wrong.

I don't use the OBD widget (which doesn't work on my system) and the Contact widget, so I cannot give you feedback about them.

Please let me know when you need any more infos or testing. I'm looking forward for the remaining bugs to be fixed, so you can release the new version on Play Store. :)
[Android Head-Units] KoTiX2:
You can check for RDS text in the drop-down notification without leaving FCC so you know when it should be visible in FCC.

Yes i mean the toast message but just to be sure we have the same settings. Is the original app turned off in factory settings?

Are metadata and notifications enabled in NavRadio?
[Android Head-Units] okij:
Today I also checked if the Minimap display bug is still existent in test121 and unfortunately it still is.

Thanks to @rigattoni's tip I used Mock Location app to record a short video of how this bug looks like, please see attachment.

As you can see in the video, the map tile ahead isn't fully shown, but just the underlying colored areas. Only when swiping the map (at 0:00:10 in the video), the missing information/layers are immediately shown.

I actually don't think that this is mobile data (or the speed of it) related, because it also happens with map tiles that should be already in cache.
[Android Head-Units] SpeedFire-:
New test version fcclauncher-3.442_test122.apk

- I noticed that TPMS widget didn't work well. Now it is fixed.

- Hal9k updates are ignored when NavRadio+ is installed
[Android Head-Units] okij:
Yes, I know. :)

Yes, of course. Also double-checked with Titanium Backup, which shows that original Radio app is frozen.

Both are enabled. But since FCC doesn't use metadata but only notifications according to @SpeedFire-, I disabled metadata for the testings I just did (please see below.)

Thanks for the quick update. :) It fixes most, but unfortunately not all of the issues I had with the display of NavRadio+ data in the FCC Player widget.

The remaining bug is that randomly I see the text "Not provided" instead of the station name, even though the NavRadio+ notification correctly provides the data, please see attached video.

Another small issue that I would like to ask you or @KoTiX2 to fix is that the RDS data currently is displayed as "Artist" and the station freq and name is displayed as "Track" in the Player widget. I would like to have it vice versa (or an option to assign it one or the other way), because then it would be the same as DAB-Z data is displayed in the Player widget. I have "Artist" set in a bigger font size than "Track" and usually station freq and name are shorter than the RDS texts, so this assignment would make sense.
[Android Head-Units] SpeedFire-:
I didn't have such issues and cannot find the source of this "Not provided" title however I explicitly banned it in this new version: fcclauncher-3.442_test123.apk

This is better to be done on @KoTiX2 side
[Android Head-Units] okij:
Thanks. I just tested it for five minutes and didn't see "Not provided", so it seems to work. Edit: I was wrong, it's not working yet, as I'll explain in my next post.

Nevertheless I took a logcat for you to look for the source of this "Not provided" title, please see attachment.

I just found one occurence of "Not provided" here:

01-22 21:38:55.278 463 477 I ActivityManager: Waited long enough for: ServiceRecord{b8a7bc3 u0 com.android.providers.media/.MediaScannerService}
01-22 21:38:55.410 26898 26898 E goc : *****************song info*************************
01-22 21:38:55.410 26898 26898 E goc : name : Not Provided
01-22 21:38:55.410 26898 26898 E goc : artist :
01-22 21:38:55.410 26898 26898 E goc : album :
01-22 21:38:55.410 26898 26898 E goc : number of media : 1
01-22 21:38:55.410 26898 26898 E goc : total of media : 1
01-22 21:38:55.410 26898 26898 E goc : playing times : 0 ms
01-22 21:38:55.410 26898 26898 D goc : GOCSDK_AVRCP_INFO
01-22 21:38:55.410 26898 26898 D goc : send_ind: [MINot Provided���0�1�1]
01-22 21:38:55.410 26898 26898 E goc : *****************song info over********************

Then this would be great. :)
[Android Head-Units] SpeedFire-:
@okij So the real reason is that A2DP is not integrated for your head unit. What head unit do you have? Can you upload your native a2dp apk and native launcher apk?
[Android Head-Units] okij:
I have a common MTCE MX head unit with Hal9k 4.2.1 rom running on it. Do you need the APKs of those two apps or do you have them?
[Android Head-Units] SpeedFire-:
Yes I need them.
[Android Head-Units] okij:
OK, here they are:
[Android Head-Units] SpeedFire-:
Some previous bugs fixed here fcclauncher-3.442_test125.apk

- TimeDigital widget auto-fit fixed

- Text alignment labels added to buttons

- Brightness widget "A" label is back
[Android Head-Units] HatManSan:
I ran t123 this morning and updated all that was available from the appstore including NavRadio.

I still have no radio information on the player widget. Works fine for Poweramp. My clock has moved right about 20 pixels, such that the text is now masked by the widget border. I still have the letter M in the player widget on occasion. I have cleared system cache but wonder if there are other cache locations i can try. Also and this is more problematic than no data. I have to press Radio at least four times if Poweramp was running. If I only press once i hear radio for a split second then back to Poweramp.
[Android Head-Units] monstereye1898:
First of all, I would like to say that I find the FCC Launcher and its possibilities super.

I have the problem with the mini map that GoogleMaps does not load the map while driving. If I change the screen or tap the map, it just loads again. It's like it just won't update the map itself. Do you guys know about this problem?

View attachment 5517371
[Android Head-Units] electrico.clax:
@speedfire, TPMS widget still gone after about 10-20 Second, it longer than before. If i touch/click the icon of TPMS widget it will open tpms plugin then i click home/back button then tpms widget show again the pressure but after several Second its gone again n again. Please you can solve that, its great with TPMS widget in home screen in my opinion. My device allwinner T5.
[Android Head-Units] okij:
Yes, here I reported this problem last Wednesday to @SpeedFire-, so thank you for confirmation.

Unfortunately it's not fixed yet, so we have to be patient.
[Android Head-Units] kill_one:
@SpeedFire- widget "go to page" always mark page 1 as text if I click, however, it goes to the right page.
[Android Head-Units] mariodantas:
I think that it should work like....

if(TMPSWidgetPresent > 0 && isTMPSAppInstalled()){

startforeground(TPMSApp)

}
[Android Head-Units] SpeedFire-:
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.
[Android Head-Units] rigattoni:
Well... I don´t know why anyone should have the need to have the TPMS always visible. The app itself alarms you and shows deviating data immediately. There is no need to have a full time visibility.

To have it at startup... okay, makes sense to see if there is anything weird and get alarmed if there is a deviation while driving. That is what the app is supposed to be used for.

But just my 2 cent.

But... what would be a good idea: to have the possibility to have 2 visibilities for it. Just a message that all is fine if there is nothing wrong since the last update and if there is a deviation to show the current data?
[Android Head-Units] Quinlann:
Can this luncher be used on 8227l CPU?
[Android Head-Units] electrico.clax:
You are right that is what the app supposed to be used for. But, I Just focus on the TPMS Widget, if there is a widget so that widget must show data continuosly. I Just want the fcc launcher become the one of the best head unit launcher that i have. :D
[Android Head-Units] SpeedFire-:
There is already such a layout of this widget. It shows "OK" when everything is good and warning message if something is wrong. You can select it. I use it most of the time.
[Android Head-Units] rigattoni:
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.
[Android Head-Units] okij:
Thanks, I just tried it, but unfortunately the bug still happens on test126.
[Android Head-Units] SpeedFire-:
Hm... can you try to install some old test version and check?
[Android Head-Units] electrico.clax:
Ok, i catch your poin, thanks for the sharing your opinion. :)
[Android Head-Units] electrico.clax:
Thanks @speedfire to your fast respons, very amazing.
[Android Head-Units] okij:
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?
[Android Head-Units] SpeedFire-:
I don't know to be honest. You better remember / try when this bug first appeared.
[Android Head-Units] okij:
@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.
[Android Head-Units] SpeedFire-:
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.
[Android Head-Units] okij:
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.

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?
[Android Head-Units] 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.
[Android Head-Units] okij:
This must be a coincidence, because I'm using Hal9k v4.2.1 and didn't update the rom in the last ten months.

This is interesting for @SpeedFire- to know, so thanks for your confirmation of the issue and infos.
[Android Head-Units] uktim32:
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.
[Android Head-Units] 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)
[Android Head-Units] okij:
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! 😀(y)

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?
[Android Head-Units] SpeedFire-:
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!
[Android Head-Units] monstereye1898:
Back from shopping and tested the version 126. Sometimes it works,

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