yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] guilhermeecoorrea:
The minimap flashes after making some modifications. Basically the combination of FCC with KWGT widgets. Can you help me?

The main skin of the FCC reminds me a lot of the look of winamp, nothing against it, but maybe doing something different as an option can help. A suggestion, create a minimalist skin using apple car play and android auto as references. In this way, I believe we will reach a larger audience of users
[Android Head-Units] kill_one:
@SpeedFire- if it is possible could you fix the alignment of the go to page widget?

Thanks :)
[Android Head-Units] kill_one:
@SpeedFire- to restore the voice call function which version of the google app should be installed?

do you believe that by installing the google app apk manually and disabling the updates from playstore it might work again or will it be useless?

Thanksss
[Android Head-Units] SpeedFire-:
Can you please remind me what was the exact issue?
[Android Head-Units] kill_one:
Page 2 - 3 creating with old widget page 3 - 4 with actual widget
[Android Head-Units] SpeedFire-:
Fixed for new widgets put - fcclauncher-3.442_test141.apk
[Android Head-Units] Instadiegus:
You are right, nothing that you said works on my HU, I’m using NavRadio widget for radio and volume controls from steering wheels.

There is a way to solve that?
[Android Head-Units] SpeedFire-:
Please try first to check all other existing types of devices in Fcc (try TEYES first)
[Android Head-Units] Instadiegus:
Tried all with no luck
[Android Head-Units] SpeedFire-:
If you have root you can send me all system apks from your head unit.

Normally they are located here:

\system\app\

\system\priv-app\

\data\app\

Sometimes in the other folders

I can't guarantee that your device can be deeply integrated because this is a difficult process and normally requires me to purchase the device or to have a very active beta tester. So this makes sence to do for popular types of devices. However, if your device can be easily integrated I will try to do this.
[Android Head-Units] Instadiegus:
My device it’s not rooted and don’t know how to do thath but there is an old firmware from Onwice uncompressed and uploaded to Drive. Please take a look and tell me.

TS10 Ownice K7 1280x720 - Google Drive

EDIT: my HU it’s not Onwice but is the same unit with different providers. I will try to root or ask in TS10 forum and upload it again. Meanwhile there is the firmware I have

TS10.1.2_20210902.153432_THEME1.zip

drive.google.com
[Android Head-Units] SpeedFire-:
I checked the APKs. Yes there is a different implementation of these functions on this head unit as compared to the previous AllWinner devices.

I don't think this is possible to quickly integrate this device unfortunately.
[Android Head-Units] Instadiegus:
We are a lot of people that uses TS10 HU (look at TS10 thread, there is a lot of people commenting all time) so if we can help to fully integrate FCC launcher it will be very appreciated.

Tell me how can i help you. Meanwhile i will search the latest apks.

Thank you again.
[Android Head-Units] Julek1981:
View attachment 5531609View attachment 5531611View attachment 5531613View attachment 5531615View attachment 5531617View attachment 5531619View attachment 5531623

This is my radio Erisin

The radio/music widget does not work for me, it does not show the artist name and song title, nor the album cover from the standard music app, nor any information from the radio fm app.

Can I change something in settings ?
[Android Head-Units] SpeedFire-:
You can try to change btInterface to a different version as well.
[Android Head-Units] SpeedFire-:
Here is the version I want to upload to the beta channel - fcclauncher-3.442_test143.apk

- All libraries (including Google libraries) are updated to the latest versions

- Translations are updated.

Please check this version. If no significant bugs are discovered I will upload it (with a new major version number) to the beta channel.
[Android Head-Units] Julek1981:
I am referring to this widget and notifications. It doesn't show any information.
[Android Head-Units] okij:
Thanks! :D

I noticed a small issue with the layout in the German translation: In the text alignment of widget settings, the icon for "centered" gets squeezed up because the German text "Zentriert" wraps into a second line, please see attached picture.

For fixing this I would suggest that @rigattoni abbrevates the translated text to "Zentr."
[Android Head-Units] rigattoni:
Done ;)
[Android Head-Units] okij:
That was fast! :cool: Thanks!
[Android Head-Units] rigattoni:
tbh... that was just open the translation, search for the string, change and submit. As I already was online that was something for some seconds to change. No rocket science. ;)
[Android Head-Units] Trayal:
Re: Cell data signal status/strength -

Would it be possible to revisit this concept, now that some head units are shipping with SIM card support for cellular data directly on the unit? CC3, etc.

It would be nice to tell at a glance where data is coming in from without having to toggle the status bar.
[Android Head-Units] kamilwar:
Hi again, I checked a couple of features of Fcc Launcher on Junsun V1 Pro 6/128 (MTK AC8259). Brightness control widget does nothing whether native android brightness control is switched on or off. Bluetooth widget also does nothing and there's no native radio app integration.
[Android Head-Units] kill_one:
@SpeedFire- with this version linking to recent applications no longer works in widgets please check and fix if possible thanksss
[Android Head-Units] SpeedFire-:
What do you mean? Sorry, can't understand.
[Android Head-Units] kill_one:
Sorry!!!

Today it works ... I don't understand why it didn't go last night, maybe I just had to restart the device... 😅 Thanks
[Android Head-Units] SpeedFire-:
New test version - fcclauncher-3.499_test1.apk

- Custom fonts for widgets are back!

View attachment 5533037

View attachment 5533039

Btw previous beta "3.499" version is still under review by Play Store (more than 24 hours already). I wonder how long will it take to publish?...
[Android Head-Units] SpeedFire-:
OK. The version 3.500 (basically the same as 3.499_test1) is released to 10% of beta testers in Play Store (I've set a 10% ratio for now then I will increase it to a higher value if no critical issues are identified)
[Android Head-Units] sandpita:
Hi all, don't know if it's been mentioned but is it possible to incorporate the USB version of the ELM327 OBDII Canbus?

​
[Android Head-Units] kill_one:
@SpeedFire- if it's not too complicated could you implement animated gif support as the default cover album?
[Android Head-Units] okij:
Just one small issue: I guess that you didn't sync the German translation yet after @rigattoni changed the text "Zetriert" to "Zentr." for the text alignment.

I see that you already changed the central text alignment button so it doesn't get squeezed to a smaller height, but now the text under the central text alignment button is just "t" (i.e. the last character of "Zentriert" which wrapped into a 2nd line, while the 1st line is not visible) and not "Zentr.".

So please sync the translations again for the next test release. Thanks. :)
[Android Head-Units] rigattoni:
Checked again and the "Zentr." is available in OneSky:

View attachment 5533625
[Android Head-Units] jmckeejr:
Been a while since I've tried any updates since brightness controls only work for me on 3.220, I have tried this latest and still have same problem. Please implement same brightness controls as version 3.220 or make an option to use those controls so I can update to latest and help with development. Have tried most versions posted here later than 3.220 but none allow FCC to control brightness (so also no auto brightness). If there's something I can do to fix please let me know
[Android Head-Units] SpeedFire-:
There is no such thing as "the same brightness control as 3.220" unfortunately. Too many things have changed since that time. You need to specify your device and what device type you selected in Fcc.

You can also try to select the following option:

Fcc Settings - System - Advanced - Force use android brightness control.
[Android Head-Units] jmckeejr:
Sure, it's an Xtrons unit rockchip PX5 (MTCD) and I select new PX5+ in settings (tried other options as well). Works on older version of launcher. The specific model and link is below. I've been happy with the older version of launcher, but every once in a while I try to update in case things are working again. Most other apps that change screen brightness do not work either (mx player, tasker/automatic, etc), just seems the setup of 3.220 somehow works and I like the auto brightness so I always revert back almost immediately (although it means uninstalling after an update in order to revert). I will try again with the settings you mention to see if it's helpful.

"Android 10 Octa Core 4GB RAM + 64GB ROM 8'' Head Unit for Chevrolet | Xtrons" https://xtrons.com/chevrolet-buick-...droid-10-octa-core-4gb-ram-64gb-rom-pbx80jccl
[Android Head-Units] kill_one:
In T143 default Radio FM app in background not show as fourth player in widget player list @SpeedFire- can you check it if it's a bug or my problem? thanks
[Android Head-Units] SpeedFire-:
The problem is that animated gifs are not natively supported by Android. So it's not that easy.
[Android Head-Units] HatManSan:
Using t1 - Love the new fonts. That has made some small writing much easier to see on the ultra crap resolution screen Xtrons use. So that's great! Thank you.

The player widget, for me at least is still very much hit and miss. I get the player name text either disappearing - when going into settings for the widget, text size is "0", or the text gets larger and wraps.

NavRadio metadata was working with t143 after the NavRadio update, but no longer in t1. Poweramp is shown as expected but no logo or text in NavRadio. That is not all however. If Poweramp is running and playing, the player widget shows Apps more often than the title. I have never selected the word Apps, so no idea where that is coming from. If the title of the song is visible and working normally, if I turn the headlights on manually or they come on automatically the song title changes to the word Apps all on its own. The title can be shown again only by selecting the next track and going back. It is instantly demonstrable, and included in my video below.

This is likely a ROM settings issue but I only need press Poweramp once to start it playing but sometimes five times to get NavRadio to stay running. What happens is the Radio plays then Poweramp is back, then I press Radio again and it plays for a split second then Poweramp is back etc.

This issue is not new to me, but I have never really been too worried about it. However I now have the map setup exactly as I like it and it works great, except the Scale by speed never works. And has never worked for me. I have the default at 15, the -2 at 20, -2 at 40 then -3 and 100. But nothing ever changes. Am I missing a setting somewhere. Minor issue, but the feature is there and I would like to utilise it.

Once again it is very nice to see this app progressing and being supported so well. Thank you

Apps Anomaly
[Android Head-Units] SpeedFire-:
New beta for Play Store with some crashes identified fixed - fcclauncher-3.501.apk
[Android Head-Units] kill_one:
same problem also with 3.499_test1 :

the fourth widget is not displayed when starting the default fm radio app in the background
[Android Head-Units] SpeedFire-:
For me it works. Please check that 4th player is enabled.
[Android Head-Units] SpeedFire-:
Here is a new beta with some fixes - fcclauncher-3.503

Currently I can't upload it to the Beta channel because the previous version was rejected by the Google for unspecified lack of description of use of Accessibility Service API (it is used to assign Back action to the wheel button for example). The funny thing is that I've provided all the details and descriptions including a video explanation (as required by them) and one of the betas was approved! But the next one was rejected again. Now I submitted an appeal with request for more details. This will require a couple working days for them to answer.

I already forgot how difficult it is to be published at Play Store.. :)
[Android Head-Units] shdwkeeper:
@SpeedFire- I was on test 106 and upgraded to the new version from playstore. Using the main skin the album art in the center seems a lot dimmer than test 106, any way to make that brighter?
[Android Head-Units] SpeedFire-:
Maybe Album art filter was applied. Please check Album art section of the Player widget.
[Android Head-Units] HatManSan:
I report NO issues at all presently, with 3501 and HAL 5.1.
[Android Head-Units] HatManSan:
Sadly, my drive out today was not error free. HU booted fine. I went through a tunnel, my lights came on automatically and bingo - text the worse I have ever seen. Massive it was! Difference this time was the widget did not say Apps, it just pushed the map off to the right and the text was huge and also pushed well over to the right. See the first image. I rebooted and all was fine for about 50mins, then me changing from PA to Navradio caused the HU to swap between radio and PA and me having to continuously press radio. I rebooted and the HU came back as the second image. I rebooted again and everything normal. Poweramp and NavRadio are talking to FCC without issue it seems which is great. I did make a Log, but clearly messed it up as I cannot find it in the LogCat log folder. :( Notice how the Satellites widget was also broken by the giant text and was the Map Street Name widget. All returned to normal after the first reboot except DAB Radio was wrapped. The second reboot all was normal. Cheers

View attachment 5538603

View attachment 5538605
[Android Head-Units] shdwkeeper:
The Mask was on, thanks.
[Android Head-Units] Bcraig23:
I've just installed this on a elinz headunit with Android 10. It keeps telling me I need to give it permission to display over other apps, but when I open the menu it's not available. It says "feature has been turned off as it slows down your phone". Also everytime I swipe right the notification access settings menu pops up but there are no options to allow notifications, it says "the feature is not available on this device". Can anybody help me out?
[Android Head-Units] PhantomDj:
@SpeedFire-

1) I also have a Junsun V1 Pro unit and deep integration doesn't work. It would be very nice if you could take a look at it at some point as it seems that there are enough people with that unit (and the stock launcher is mediocre).

There are a few threads about that unit here on XDA btw that maybe could provide you some insight.

Volume integration is partially working with it if I use "Android" method to control it but Brightness integration is not working at all.

However the bigger problem for me is Radio integration.

NavRadio+ does not support this unit. And most other popular radio apps (that usually work over internet) don't support it either. This means that I'm stuck with the default radio app that there's no way to integrate to Fcc.

The lack of deep integration also means that a lot cool features of Fcc (like adjust volume according to speed) also don't work. Nor programmable steering wheel buttons e.t.c.

I can understand that both your time is limited and that our HU is not one of the most popular out there, but if you can take a look and it's an "easy" task to integrate, then it would be cool.

2) I still have random issues with Players widget. 8 times out 10 when the HU will start, players widget works properly and shows info from Poweramp that's the only media player I use now. However, 2 out 10 times the widget will not show any information at all. It WILL control poweramp though. I can use the widget to initiate play/pause or nexr/previous track and even call the playlist on screen (show media list if supported option IIRC)

When that happens I tried several things as switching audio apps, restarting Fcc (by the icon or by hitting back repeatedly 3 times) and nothing works. The only thing that DOES work is to shut off the HU, wait a few minutes and then start it again. The HU is NOT set to sleep mode.

One or two times in total the widget started working again on it's own after I received a phonecall. I do have my phone paired to my HU, but I have now changed my phone settings so that bluetooth is used only for phonecalls and not for media streaming. In previous versions/builds the AD2P would cause the widget to go crazy, so I disabled that.

PS: Before Poweramp I was using AIMP. With AIMP the issue was even worse. Fcc would show info at about 2 out of 10 times the HU would start. I'm sure the issue has something to do with the new way you fetch the info from notifications. I'm not saying "bo back to previous method" (that for the end user worked better) but there's still a bug somewhere that makes Fcc stop reading notifications and fetching info on players widget.
[Android Head-Units] SpeedFire-:
New test version fcclauncher-3.501_test2.apk (switched back from unapproved 3.503 to the approved 3.501 so users can purchase Premium):

- New google maps renderer applied (you can switched between the legacy renderer and the latest renderer in the MiniMap settings).

You can read about the new renderer here: https://developers.google.com/maps/documentation/android-sdk/renderer
[Android Head-Units] okij:
Thanks a lot! :) I just tried the new maps renderer in my parked car by using Mock Locations app and I like the new map rendering (e.g. it seems to have a better 3D effect). Tomorrow or on Monday I will check how it behaves in real use.

I've encountered a new minor issue in 3.501_test2: When switching from NavRadio+ to a different player, there's a new toast message saying "FM radio is ignored. You can enable it in the Player widget's settings." Of course I have FM radio disabled in the widget settings as I'm using NavRadio+, but I don't need this toast message. ;)

Please have a look after this and of course also after the issues that I've reported here yesterday when using NavRadio+ with the Player widget. Thanks!
[Android Head-Units] SpeedFire-:
Yes, I reproduced the issue. Unfortunately it hardly can be fixed.

The possible cause of it that two notifications are posted almost simultaneously:

- One from NavRadio+ with the new track data

- Another from Hal9k rom ("com.navimods.radio").

My notification service tries to identify which app posted the notification and sometimes identify the package incorrectly when the notifications are simultaneous. So the correct new track name was identified as received from "com.navimods.radio" and not from NavRadio.

However, this error is quite rare and appears only when you quickly switch between players.

I, however, noticed a more important issue. It looks like NavRadio+ adds extra margin to the radio station logos so Fcc cuts the image to a circle incorrectly (with black bars). Margins can be clearly seen when compared NavRadio's notification to AIMP's notification. @KoTiX2 can you please delete extra margins from the logos sent via notification updates?
[Android Head-Units] SpeedFire-:
Here is the fix - fcclauncher-3.501_test3.apk
[Android Head-Units] okij:
I was already thinking that two notfifications respectively metadatas interfere, but "com.navimods.radio" actually is Navradio+, as you can also see in its package name in the Play Store link: https://play.google.com/store/apps/details?id=com.navimods.radio

That's why I wrote:

So IMHO you must clarify to @KoTiX2 how exactly his notification has to look like respectively (from a dev's point of view) what elements it must contain and if any metadata needs (or is even allowed) to be sent in addition to the notification. I assume that the latter is currently the case, i.e. that NavRadio+ is sending additional metadata, but that this is causing the issues.

Thanks. Is this a fix just for the "FM radio is ignored. You can enable it in the Player widget's settings" toast message or did you manage to fix something about the interfering NavRadio+ notifications and metadata? I'm asking because I'll probably not be able to check it this weekend, since in my underground parking place I have no good FM reception and cannot check anything RDS text related.
[Android Head-Units] SpeedFire-:
My bad! You're right. I mixed it with "com.microntek.modservice" but this was actually a NavRadio app so the notification service identified it correctly!

I checked the following path and identified the other possible issue where I tried to avoid interference between previous versions of NavRadio and Hal9k Rom. It is removed now and everything seems to work correctly now. Please test - fcclauncher-3.501_test4.apk

Yes, both latest test versions fix that toast.
[Android Head-Units] KoTiX2:
In NavRadio settings/notifications there is an option to add black background to the logos. You can disable it and logos will be sent as they are (just resized to 255*255pixels max).

About Hal9k notifications interferferences, i added also in my app a check that is FCC is home launcher i don't update anymore the widget broadcast that he use to send notifications. So it shouldn't be a problem anymore but never say never.

I also have been contacted by Hal9k about this problem and i sent him my app but i got no reply after that.

Let me know if you need more things to check/change from my side ;)
[Android Head-Units] SpeedFire-:
I excluded the black background but the issue with the image size still exists.

Please also take a look how your logos look in notifications. Something is wrong with the size.
[Android Head-Units] KoTiX2:
I can't look at it until Monday but all i can say is that logos are resized to 255*255 pixels keeping the apectratio.

RadioLogos can have their own margins or not, logo i never edited the images to make them fill the available space.

i don't know if "NRJ" have margins but We should try with a logo that we are sure it doesn't have any margin.
[Android Head-Units] okij:
I tested 3.501_test4 and can confirm that the NavRadio+ integration for the FCC Player widget is now working correctly! :love:

Switching between NavRadio+, DAB-Z and GMMP (which I assigned to the Player widget) as well as switching forth and back between FM stations in NavRadio+ now is 100% working and giving the correct display in the Player widget. Also the RDS texts now are displayed in the Player widget as soon as they are received by NavRadio+.

Thanks a lot @SpeedFire- and @KoTiX2 for making it work, you guys rock! :cool:(y)

I noticed only one small last issue after waking the head unit and NavRadio+ being the last active player (with FCC being configured to resume playback of the last active player): It first started to play correctly, but then stopped playing again, with the NavRadio+ notification looking like in the first attached picture and the Player widget like in the 2nd picture. I also attached the Logcat for you to have a look into this.

I hope that you can reproduce this issue and fix it too.🤞 AFAIR @KoTiX2 wrote to me that he already noticed that the playback of NavRadio+ is not working reliably after waking the head unit (but I'm not sure if he tested this with FCC or with Hal9k being configured to auto-start playback after standby.)