yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION] .

Thank you for the explanation.

I'm playing with the obd . And works.

I have coolant temperature set . And whant to ask you if it's possible to set 4 colours like bleu - orange - green red depending on temperature?

Can you post please the mini map skin empty so I can work on it ? Black background is good .

Thank you.
[Android Head-Units] SpeedFire-:
Here it is:

minimap_skin
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

My first design. Minimal distracted . Place for 12 apps under map.

Ps: it's just the mirrored copy past from a exciting design. (No credits for me)

But I like it. Maybe with some editing a new design?
[Android Head-Units] kamilwar:
Yes, it was recorded on the test version, but as far as I remember the same thing happened on the Play Store version. It happens every time. Video and log
[Android Head-Units] Joscj:
Hi,

I’ve been using FCC for the past month, and it’s been great. I just ran in to a weird problem, however. I just got back in my car after shopping, and when my player (a joying) boots up, FCC is no longer the default launcher. When I tap the “set as default launcher” option in FCC settings, it just jumps back to the standard launcher, and nothing happens. FCC no longer shows up as an option in the list of launchers in the player settings either. What is going on, and how do I fix it? This has made my HU next to unusable. Help!

Also, I’m having trouble backing up my settings to google drive, I just get an error message saying fcc is unable to save the file. Is anyone else running into this problem?
[Android Head-Units] kill_one:
system apk files where i find theme?

the specification device:

EUNAVI PX5 (1024x600) Android 10

CPU: OC Cortex-A53 1.5G

RAM :4GB

MEMORY: 64GB

Build number: rk3368-userdebug 10 QQ2A_200305.004.A1 eng.hct2.20201019.121348 test-keys

Version kernel: 4.19.111+ #2436 Wed Oct 14 19:07:04 CST 2020

Version MCU: MTCE_LM2_V3.67d_1 Nov 17 2020 16:39:08

Serial Number: 77CF0EBF811F3679

Build: k3368-userdebug 10 QQ2A_200305.004.A1 eng.hct2.20201019.121348 test-keys

Kernel: 4.19.111+ #2436

MCU: MTCE_LM2_V3.67d_1

In fcc settings device i select: ROCKCHIP new version type
[Android Head-Units] rigattoni:
I would recommend to not use the "New version type", as it is normally used for units with CSN2 MCU.

You should use the "normal" Rockchip settings.
[Android Head-Units] kill_one:
Thanks @rigattoni I try to change and see if it works
[Android Head-Units] SpeedFire-:
I agree with @rigattoni . Please try first to use other (previous) types and in case of no success we will investigate this.
[Android Head-Units] SpeedFire-:
You can try to re-setup your default home app.

Go to Fcc Settings - System - Home app - and select Fcc Launcher.
[Android Head-Units] SpeedFire-:
Thanks. I see that all FCC background threads are killed around this time for unknown reason.

It seems that Verbose level of details was not enabled in your LogCat app (please see the 1st post). The attached log includes high-level records only. Can you please enable the Verbose level of details and record a new Log+Video again?
[Android Head-Units] okij:
A short feedback after using test134 for one day: The Brightness Widget worked as intended all the time and it didn't stop responding yet like test133 did yesterday. This morning I was driving during sunrise and now can also confirm that it properly changes the icons according to the current daylight. If it should have issues in the next couple of days I'll report and take a logcat for you, but until now it looks fine. 🤞

Also it seems to me that on test134 the map animation of the MiniMap looks a bit smoother than before, i.e. the short interruption each second is less noticable. Is this just my imagination or did you change anything about it?
[Android Head-Units] SpeedFire-:
Nice! Thank you for testing and reporting.

As you advised I changed the animation time from 950 ms to 900 ms. Nothing else changed.
[Android Head-Units] guilhermeecoorrea:
Feedback test134

Feeling that the minimap is fluid, with no loading delay.

I'm using FCC combined with KWGT widgets. Good job! greetings from Brazil
[Android Head-Units] KoTiX2:
Thx for this little mod.

I'll try to add some checks in NavRadio too to avoid Hal9k modservice to send the metadatas because they are interfering in the same way in Agama launcher and probably others.

I also asked in @hal9k to add a setting to disable the metadatas for radio but will be better if more people ask it too so @hal9k will take it under consideration.

So, please guys help me make some noise in his rom thread ;)

@ SpeedFire- I used to send different infos for drop-down notifications and for metadatas. I noticed that FCC first display the notifications and later the metadatas i thought that the player widget was showing now only the infos from notification manager and not considering the metadatas or i misunderstood it?

I will use the same infos for both broadcasts in next rel but i was just curious how exactly these 2 infos are used in FCC?
[Android Head-Units] kamilwar:
That's odd because I followed your guide and set it to verbose from the beginning and didn't change anything. It was always set like this:

It was set to Verbose.

It was set to Verbose from the beginning because I followed your guide:View attachment 5525823
[Android Head-Units] okij:
I just did so and support this request, although I'm still on Hal9k v4.2.1 as I don't see a benefit of updating to v5 yet.

Thanks! :) And please remember to add an option to switch station name and RDS text (so that they can be assigned to either artist or title field), as I already asked for. Also it would be great if station number and frequency could be toggled off and on in the field with the station name.
[Android Head-Units] SpeedFire-:
There is a MediaMetadata which is part of notification. It is used in Fcc Launcher as part of notification processing.

Broadcasts and all other forms of receiving media data are completely ignored. Only notifications are used.
[Android Head-Units] SpeedFire-:
OK, thanks! So there is just not much data in the log itself. I see.

I'm very concerned with this bug, however I don't understand how to reproduce it.

Can you please try to install the release version of Fcc Launcher from Play Store and check the existence of this bug there?

How do you live with this bug? What do you do after everything is disappeared?
[Android Head-Units] kamilwar:
I tried the Play Store non-beta version and the issue also occurs there. When Fcc launcher is not responding i push the back arrow on my head unit panel several times till exit appears then Android asks me which launcher should it use and I select Fcc launcher. After that Fcc loads without problems and the error does not occur anymore. The problem is only at boot it doesn't matter whether it's a cold boot or an adb reboot.
[Android Head-Units] daemondee:
In the last few test versions, I've noticed that the FCC restarts if I open an app in the meantime.

Example:

The FCC normally starts when the HU is turned on. Then I manually launch the GPS Test app and when I press the Home key on the HU, the FCC restarts.

This only happens once after turning on the HU. After the FCC restarts, I can start the GPS Test again and the FCC continues to operate normally without restarting.

Does anybody else experienced this? @SpeedFire- could you please take a look at this?

My unit is CSN2 and I'm using test134.

Edit:

I saw, that the file was not attached, so I upload it to google drive.

Here is today's logcat.
[Android Head-Units] SpeedFire-:
OK, good. So there is no negative effect of the test version.

However, it seems that some system app of your head unit force closes other third party services on load.

Can you please make another test? Install the latest test version. Open settings of any Icon Widget and convert this widget to a normal icon (there is a button at the bottom left in this widget's settings). Then please look if this icon disappears as all the widgets or not.
[Android Head-Units] kamilwar:
Installed test version (134) and did as you instructed. The converted app stays even after the widgets disappear.View attachment 5526227
[Android Head-Units] spludgey:
Can you change the font size in the widget to something more reasonable, in the full version? If so, I'll buy it.
[Android Head-Units] GnFgr:
Yes you can. At least for the widgets that comes with this launcher.
[Android Head-Units] SpeedFire-:
Hi. What do you mean? All Fcc widgets have settings (long click on the widget) where you can change font size.
[Android Head-Units] kill_one:
nothing to do, even selecting the old version makes the same problem :( @SpeedFire- what can i do to help you solve the problem? Thanks
[Android Head-Units] spludgey:
It means I'm an idiot and posted in the wrong thread, sorry about that!!!

I love the concept of FCC, I think it's awesome! Well done!

To make it my daily driver though, there would need to be a way to disable the screensaver, as my head unit defaults to it, no matter what I try and the widgets keep wanting to go onto the next screen and it's extremely difficult to place them either in the top or bottom row.
[Android Head-Units] SpeedFire-:
1. You can watch here how to delete one of the screens:

You can also disable screensaver function (darkening of the background) and set a default screen here:

Fcc Settings - Screen - Advanced

2. You can lock the screen to protect it from modifying. Long click on an empty space - tap on a lock icon in the right bottom corner. After that you will be able to operate with widgets but not to move them.
[Android Head-Units] HatManSan:
I am right in saying the adjustments needed in NavRadio have yet to be made? I still get no radio logo or any test at all. Also in the player app with t134, instead of an album or artist title from poweramp, I see the word Apps instead, until pressing next track.
[Android Head-Units] okij:
Yesterday @KoTiX2 released a test version (0.2.23) on the beta channel on Play Store which should improve its notifications and thus its integration to FCCs Player widget.

However the NavRadio+ notification now is not working properly on my head unit, as I reported to @KoTiX2. He's currently looking into it.
[Android Head-Units] HatManSan:
@okij cheers for the headsup
[Android Head-Units] Nexmade:
Hi I was wondering.. If I could assign full apps on the homescreen carousel. This would be perfect as I would like to swipe to different pages of the homescreen. I.e first normal home launcher. But if I swipe down ( or Up.. Left/right) I would like maps or fm radio to be on the second and third page. In full screen (allready running) . Maybe a spotify remote launcher aswell. Or a custom full screen widget.

(Spotify discontinued the car appearance for the app)

And lastly

Could I assign my built-in phone app to the launcher also. Because eventhough bluetooth is enabled. Fcc isn't registering that it is. Or maybe a passthrough option.

Running a Rockchip px5 android 9

(Bluetooth option are locked away& can't choose a different dailer) ;(

Thanx in advanced
[Android Head-Units] KoTiX2:
If you have NavRadio 2.23 you have all the latest changes:

- removed temp for not MTC devices

- fixed fonts in settings screens

- on TopWay units the app now close on audiofocus lost

- unified dropdown notifications and metadatas

- added verification of installed Hal9k ModService and prevented its interference

- added FYT units with sprd9853i ed sprd9863a(UIS8581) cpu to supported list

Then you just need to be sure that you have enabled metadatas and notifications in NavRadio+ and of course set NR+ as player in the widget
[Android Head-Units] HatManSan:
@KoTiX2 Understood. Evaluating in the morning. Thank you
[Android Head-Units] SpeedFire-:
New test version fcclauncher-3.442_test135.apk

- TPMS widget fixed - text size is resizable now in 4-tire layout

- Fixed some issues when app is upgraded from Play Store release version to the test version.
[Android Head-Units] GnFgr:
Pressing twice fast back while on home screen of this launcher get you to the choosing new home screens or widgets.

If you press back again it force closes the launcher completely and removes it as a default launcher.

If you press home after a toast message asks you what the default launcher should be. If you choose this launcher to always be as default and redo the above same thing happens.
[Android Head-Units] kill_one:
Can anyone confirm if the backup restore is back working?
[Android Head-Units] SpeedFire-:
Does anyone have any significant issue with the latest test version (as compared to Play Store version). I want to gradually roll out the test version to the Beta channel if everything is OK.
[Android Head-Units] daemondee:
Maybe the issue, that I report here.

No other issues for me.
[Android Head-Units] mariodantas:
Does the plug-in starts automatically ? (if at least one tpms WIDGET is present ? or simply launched by FCC if installed ?)
[Android Head-Units] SpeedFire-:
Plug-in is started if at least one TPMS widget is placed to a home screen.
[Android Head-Units] okij:
I've been using test134 and test135 in the past three days without any issues whatsoever.

Also the Brightness widget now always updated its icon and reacted to button presses as intended, so IMHO you can remove the debug logging for it again (if you haven't already done this in test135).

As you know I use a quite common device (PX6 MTCE on Hal9k v4.2.1), so I cannot say if there might be some bugs left on other platforms, but from my point of view the current version is good to be released. :)(y)

Thanks again for all the effort you put into reworking all widgets, listening to our feedback and fixing the reported bugs! It was worth it, because the current test version is the smoothest, most bug free and functional FCC Launcher since I started to use it over two years ago. The last Play Store version was also working fine, but in the new version I e.g. enjoy very much the non-interrupted text scrolling of the reworked Player widget and the new, unified settings of all widgets.

Well done!! :cool:

One question: Did you already merge the submitted translations, like the German one from @rigattoni? I'm asking because there are still quite a lot of English texts in the FCC settings and the widget settings (like "auto", "left" etc. for the text alignment). Of course this is not a problem for most users (so it's OK to be released on Beta channel), but the translations should be as complete as possible until the official release on Play Store.
[Android Head-Units] rigattoni:
@okij

I just checked the translations.

Seems that they have not yet been supplied to get translated. Could that be @SpeedFire- ?
[Android Head-Units] SpeedFire-:
Correct, thank you for reminding this! I will update.
[Android Head-Units] Julek1981:
Hi I Just buy this erisin headunit Erisin es8106p but launcher from play store not show notifications and round widget from system radio app and system music app only working hour notifications and youtube vanced

Sorry for my english
[Android Head-Units] rigattoni:
hmmm... May be you just write your questions in your mother language, use https://www.deepl.com/translator to get it translated to English and throw the original and the translated version into this thread.

I think, that makes it a lot easier for all participants.

Edit: by the way... It´s quite normal that you don´t get any information from the internal radio application and even from this annoying internal players.
[Android Head-Units] Julek1981:
I purchased an erisin unit with android 10 then installed from the google store fcc launcher and unfortunately notifications do not work. The only working notifications are those of the application youtube vanced and time. Also does not work displaying the artist and song or radio station in the round widget displays only from youtube vanced. Maybe you can recommend applications that work in place of the system ones for radio and music. I used translator.

Translated with www.DeepL.com/Translator (free version)
[Android Head-Units] SpeedFire-:
New test verision - fcclauncher-3.442_test136.apk

- Important change - launcher will not kill itself if it thinks that another instance of the launcher is running. This should fix the issue with the launcher unexpected restart @daemondee mentioned. Based on my tests I don't see cases when 2 instances co-exist. Please test if you see any negative effects from this change.

- Fixed an issue when launcher hasn't changed widgets settings when switching from split screen to full screen (text and icons continued to be small).

- Translations updated. Thank you all for your help!
[Android Head-Units] rigattoni:
To give some recommendation, you may give some more information about your unit, like the MCU version. Just a screenshot of your "About tablet" would be sufficient if the MCU is shown there.
[Android Head-Units] rigattoni:
Nice...tested it directly on bench, as the big unit is in my workshop in the moment and i have remote access to it.

Switched a couple of times and seems to be fixed.

Will give it some more tries tomorrow and report back in case I find some issues.

Updated the missing translation so far, just one thing I was not quite sure:

"Settings peek animation"

For that I couldn´t get the exact meaning of. Can you please add some information for it, please?
[Android Head-Units] SpeedFire-:
This is the setting in the widget's setting. You can set a period of time (in seconds). When any preference is changed the widget's setting window become transparent for a set period of time so user can see (peek) the home screen.
[Android Head-Units] okij:
@rigattoni In German it could be e.g. "Vorschau für die Einstellungen".

@SpeedFire- IMHO in English "Settings peek duration" would be more fitting. (In German then "Dauer der Vorschau für die Einstellungen".)
[Android Head-Units] rigattoni:
Okay great... just the "animation" let me stumble.

Hmmm... think @okij is right, in this case I also would prefer the "Settings peek duration" instead of "animation".

I think I need more playing around with the settings and changed options. I still have my preferred homescreen now since a long time.

View attachment 5528855

@SpeedFire- , would it be possible to add another player, called "com.szchoiceway.radio"? It´s the radio app which is used in this ROM. I now use Tasker to call it and that is not really comfortable.

I would really appreciate that, to get this in.
[Android Head-Units] SpeedFire-:
"com.szchoiceway.radio" is the stock FM-Radio for some Rockchip devices. It was already integrated.

Make sure you've selected Rockchip type of head unit. You may also need to change the Bluetooth Interface Version in Fcc Settings as well as this may affect FM Radio integration as well.
[Android Head-Units] SpeedFire-:
Based on the link provided by you this is a Rockchip device. Please make sure you've selected Rockchip device type in Fcc. You may change it in Fcc Settings - System - Advanced
[Android Head-Units] Instadiegus:
Hello there!

I have TS10 UIS7862 model and FCC Launcher works perfectly except for Auto Brightness. I have the latest test version with premium and Allwinner model selected in settings. It's my fault or AB doesnt work with that kind of model?

Second question: it's possible to get a BT player widget? Because my model have the player into BT app and the widget player doesnt show it in options tab.

Thank you.
[Android Head-Units] rigattoni:
Wait...

I think I now tried all different settings for Rockchip and BT, but I am not able to get the app opened.

Any hint which settings have to be set to get this working?
[Android Head-Units] SpeedFire-:
BT player is called A2DP in the selection list. You can try it. However, since you've mentioned that Brightness doesn't work on your device, maybe your type of device is not deeply integrated (or this device has significant differences from previously integrated AllWinner devices).

What does work on your device from the following:

- Volume control from Fcc Widget

- Brightness control from Fcc Widget

- FM radio control

- FM radio data is displayed

- A2DP (BT music)

- Standard (built-in) player

?
[Android Head-Units] SpeedFire-:
It should open.

Can you show on video what do you try to do and what happens?
[Android Head-Units] rigattoni:
No, it doesn´t open, just if I use the extra Tasker button I stored beside the album art widget. No way to get it into the player widget I use to switch the player (2 widgets: DAB & Online Radio and the second is MP3 player & FM-Radio) ... and sorry, I used my remote to get this video. That´s why you don´t see touch events.

View attachment 5528887
[Android Head-Units] okij:
@SpeedFire- I just found a minor issue: The settings peek function currently isn't working (tested with test136).
[Android Head-Units] SpeedFire-:
Please test this version: fcclauncher-3.442_test138.apk

Peek animation is also fixed here.
[Android Head-Units] rigattoni:
I tested some settings for Rockchip and BT, but still not opening.... sorry. The only way to open it is by using Tasker or the app button in the app overview.
[Android Head-Units] daemondee:
I tested the version test136 and I can confirm that the issue is fixed. There is no restart now. Everything seems to work perfectly.

Thank you @SpeedFire- for your great effort and for the best launcher ever.
[Android Head-Units] rigattoni:
Please test this version: fcclauncher-3.442_test138.apk

hmmm... did you really post a #138?

I saw that this is downloaded as #137

Typo, or wrong link?
[Android Head-Units] SpeedFire-:
Sorry, this was a wrong file. Here it is - fcclauncher-3.442_test138.apk

Thanks :)
[Android Head-Units] rigattoni:
okay got now the #138, but the result is the same. :(

FM-Radio is not opened in widgets.

Do you need logs? I would be able to provide them. Don´t know if you will see anything in there.

Edit: Added log file.
[Android Head-Units] SpeedFire-:
You can try to record log on this version:

fcclauncher-3.442_test139.apk
[Android Head-Units] rigattoni:
Done... See attached logs file.
[Android Head-Units] SpeedFire-:
Based on log it is actually started but then the launcher Goes Home because you selected start FM radio in background for that action and not just to open it. Please check the assigned action
[Android Head-Units] rigattoni:
Oh no, I just press the button FM in the related widget. I don´t do anything else. It is even not possible to open the FM-Radio with the album art, as it is set to open the current used player.

View attachment 5529033

There is a task running which sends the screen back to the home screen after 5 sec. not touching the screen, if a player is in foreground. But I am even not able (if the FM would run in background) to open the FM on the album art. It does simply not respond at all.
[Android Head-Units] rigattoni:
I stopped the "Back to Home" task now, but the result is the same.

I went down into my workshop and checked if the radio is playing, but... no. As soon as I "start" the FM, the other player are paused and nothing happens. I have to open the FM manually to get something out of there.
[Android Head-Units] guilhermeecoorrea:
Desculpe sair do tópico. Onde você conseguiu esse widget de barra superior?
[Android Head-Units] guilhermeecoorrea:
Sorry to get off topic. Where did you get that top bar widget?
[Android Head-Units] rigattoni:
That is no widget, that is part of the System.ui and I would wish I could get rid of it...

It´s this unit: Klyde 12.8"
[Android Head-Units] SpeedFire-:
So you want to start FM radio playback in the background not to open the app?
[Android Head-Units] rigattoni:
I don´t care if it is in background opening or in foreground.

I´m fine with any solution which starts playing FM radio. ;)

As I already wrote: I have some script which switches back to the homescreen after 5 sec not touching the screen.
[Android Head-Units] SpeedFire-:
You can try this: fcclauncher-3.442_test140.apk

1 sec delay is added between FM radio start and going home.
[Android Head-Units] rigattoni:
(y):love:(y) Thanks a lot, @SpeedFire- that does the trick.

Thanks a lot for your amazing support!!!