yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] HatManSan:
Greetings.

Yesterday, I had to drive some 65miles to a unknown location. Using just installed 3503, the latest build of Sygic and Hal 5.1.0 off we went. Whilst Sygic was active the HU restarted eleven times! By restarted I mean it literally went black instantly and then booted as usual. This happened without any intervention nor during any Sygic spoken directions. In the end I had to resort to my iPhone. Whilst I was waiting for my folks, I removed 3503 and installed 3501 t4. Restored and tried again. On the way back the HU restarted twice. Twice only because I knew the way back and closed Sygic. Sygic has not been updated in the last week but FCC has. Am I right in saying that Logcat is a waste of time as the blunt shutdown and restart would have simply closed LC every time so any records would have been lost? I also noted that with 3501 t4 and NavRadio 227 I have no player widget data anymore. I did with 3503. On a good note, no text changed position or size. Is there any info I can post that will help?

Cheers
[Android Head-Units] SpeedFire-:
Hi,

Yes, LogCat will not be recorded in case of hard restart. I would suggest you to put RAM widget to the home screen and track how much free memory your HU has.

Then I would suggest to delete Fcc completely and see if there are hard resets.

This issue could be caused by Fcc if it consumes too many resources but also can be caused by some hardware issues with your HU (maybe it is slowly dying).
[Android Head-Units] okij:
I noticed that with the new renderer the outlines of the streets weren't visible anymore when using the Icy Blue 2 Day and Icy Blue 2 Night themes that I provided two years ago.

Today I fixed them and attached the new json files to this post, so you can use them in the next FCC build.

Also I noticed that in the new renderer - which I generally like a bit better than the legacy renderer - the 3d buildings aren't somewhat transparent anymore, at least when using the Icy Blue 2 Night theme. Unfortunately I didn't find a way to fix this in the Google Maps Styling wizard, i.e. when changing the fill colours in Landscape -> Human made, the 3d buildings get fully opaque. This doesn't apply to the Icy Blue 2 Day theme, because here the fill colours aren't touched and instead a a hue for everything is set in All -> Hue.

Can you maybe set the 3d buildings somewhat transparent via the API of the new renderer?
[Android Head-Units] SpeedFire-:
I've added your themes.

Regarding opacity. This is not documented but I've tried and it works. You can set opacity in the colour itself.

Normal colour is set in the format "#RRGGBB" but you can add additional values in the beginning: "#OORRGGBB" (opacity for first two positions from 00 - fully transparent to ff - opaque).

So I changed your colour "#001c48" to "#cc001c48" and it became semi-transparent.

fcclauncher-3.501_test5
[Android Head-Units] okij:
Thanks, that's great! :) I will check the new test build tomorrow.

Did you already use the changed mapstyle_icy_blue_2_night.json (with #cc001c48 as landscape geometry fill colour) in test5?

Also I'm curious if you could reproduce this last remaining issue of the NavRadio+ support:

Today I tried it again and could reproduce this issue myself. Do you think that it can be fixed in FCC or does @KoTiX2 have to look after it?
[Android Head-Units] SpeedFire-:
Yes. New styles are already applied.

I won't be able to test NavRadio this week as I don't have a test device at this location. Remind me later please.
[Android Head-Units] VBA_Dev:
Hi @SpeedFire- Can you check the media player layouts for album cover on its own and song name/title. I have been trying to create a page with a large album cover for 2/3’s of the screen, but for some reason the second widget showing just song name/artist cannot sit underneath anymore.
[Android Head-Units] Shadow128:
Hi there

It is possible to do a manual trip reset with Tasker?

I'd to configure FCC with Tasker that is is not stopped after switch off of the head unit. But so the driven kilometers are stored and I want to reset them with every start
[Android Head-Units] SpeedFire-:
Starting from the next version you can send broadcast "ru.speedfire.flycontrolcenter.RESET_TRIP_DATA_FORCED"

Currently you can send broadcast "ru.speedfire.flycontrolcenter.RESET_TRIP_DATA" but it will show you a dialog with confirmation.
[Android Head-Units] SpeedFire-:
Can you please show a screenshot and mark what is wrong?
[Android Head-Units] Shadow128:
Great, thanks for that information 😊

Then I'll wait for the next version and try it
[Android Head-Units] okij:
I tried the new themes in real use today and the semi-transparency works very nicely. Thanks for finding and adding the opacity value! :)
[Android Head-Units] Julek1981:
I try to install fcc on t10 6/128gb tesla style vertical android and launcher working strange
[Android Head-Units] rigattoni:
What do you expect with such a different screen size and orientation?

There is nothing strange...

You need to create your own "homepage". That is quite easy. Just go for it.
[Android Head-Units] rigattoni:
@SpeedFire- May be a good point to create also at least one template for portrait mode units, as all existing ones just look terrible on the Tesla style units?

As of now, Tesla-Style user have to build their own main page. If you need someone for testing, feel free to contact me.

As I am writing... I can use my unit in portrait and landscape mode. I tried to find a way to switch between both modes. I am able to get the info in Tasker in which orientation the unit is, but I had no luck to switch the page yet. Seems no longer be available. There is a possibility in Tasker to switch pages, but this is no longer working in Fcc. Can you please have a look into this feature?
[Android Head-Units] Julek1981:
@SpeedFire- I found errors in translation of some commands into Polish... I could fix it but I don't know where to find the translation file...
[Android Head-Units] SpeedFire-:
Hi!

You can fix it via this site - https://osd2jt2.oneskyapp.com/admin/project/dashboard/project/317150

Thank you for your help!
[Android Head-Units] mariodantas:
Works as expected :!
[Android Head-Units] Julek1981:
Applications widget/button is moving down every touch musi restart launcher to fix

Default radio and music player not working On round widget at all

View attachment 5543995View attachment 5543999
[Android Head-Units] Julek1981:
I have corrected and completed the translation into Polish
[Android Head-Units] rigattoni:
3 things to comment on your posting...

1. Which Fcc version are you using?

2. Did you try to lock your screen yet? Long press on a free space and you get a small lock on the bottom right to click on. Then the apps should not move any longer.

3. I don´t think that you won´t get the FM radio fully implemented and for sure there is no album art showing up. As music player you should use any other player than the default one as they are only internal and don´t give any information to any other app.
[Android Head-Units] Julek1981:
@rigattoni

1. My FCC version is 3.501_test5

2. Yes workspace is locked

3. So i buy Navradio+ and PowerAmp
[Android Head-Units] PhantomDj:
Regarding translations:

I have updated (and fixed some errors too) on Greek translation a few days back.

It was definately before test version 5 that I'm running.

But I don't see the translation fixes on 3.501_test5

Do we need to let you know when we do updates so that you manually include them, or is it an automated process when building the APK to fetch latest translation files ?
[Android Head-Units] rigattoni:
If the workplace is locked, the widgets/buttons should not move...

NavRadio+: Did you check with the free version first? I expect that this should not work on your unit.

PowerAmp may work now with Fcc, but works. BlackPlayer would be an alternative.
[Android Head-Units] Julek1981:
AD 1

But whenever I press the Applications button/widget it moves down a few pixels. Only restarting the launcher fixes the button placement correctly.
[Android Head-Units] rigattoni:
There is an animation in the button, but may be check the size of the button/widget. May be you just need to resize them a bit.

Other than that... You can export your Fcc settings and add it here. I also be able to test it on my 12.8" unit in portrait mode to see what is ongoing there.
[Android Head-Units] Julek1981:
My backup files
[Android Head-Units] rigattoni:
Will have a look late afternoon.
[Android Head-Units] rigattoni:
Okay, imported your backup on my unit and tested the setup.

I was not able to reproduce your issue with moving buttons. Just the animation is visible as expected. Unfortunately my unit is a bit different from yours... and I have another background as yours.

The green icons are in there, because I have different apps installed as you have and different System-Apps.
[Android Head-Units] Julek1981:
My application button has a different layout than yours I have the icon at the top and the text at the bottom when you click on the application then a big arrow to the left to exit and again the application and again the arrow to exit and after a few clicks on the application you will see that the button goes down...

I try to make video...
[Android Head-Units] rigattoni:
As I just imported your setup, there should be no difference. I didn´t change anything.

...and I tried a couple of times before I started the video, so I don´t see that at least on my setup.

Which MCU, Android-version is on your unit?
[Android Head-Units] Julek1981:
View attachment 5545727
[Android Head-Units] Julek1981:
This is My android version

View attachment 5545741View attachment 5545745
[Android Head-Units] mariodantas:
The import config (from SD or GDrive) stuff still doing strange things, it must be imported at least twice to recover the config
[Android Head-Units] okij:
I now tested the night theme with the semi-transparent colour a bit more and found out that - while it was a great idea to use the transparency channel of the colour setting - in practice unfortunately it doesn't work well.

First I didn't notice this when driving through town - with the 3d buildings being shown and also being transparent so that roads are not fully obstructed by the buildings - but when then driving on a motorway I noticed that the ground colour of the landscape was always altering, like a slow flicker between a transparent and non-transparent colour.

Because of this I decided to have a further look at the map styles:

The Icy Blue 2 Day Theme (which is working without problems and has semi-transparent 3d buildings) mainly uses the global hue value to change the standard Google Maps colours to the bluish hue.

In opposite to this I based my old Ice Blue 2 Night Theme on some existing night theme that I found in an online repository and changed all colours that didn't match the Icy Blue Day theme. Unfortulately, once changing colours, they aren't transparent anymore, so the 3d buildings always obstruct the roads.

Therefore I now fully rewrote the Ice Blue Night Theme to also use the global hue value and I globally inverted the lightness of all colours to get the nightiesh look. I then just adjusted some other elements by only changing their lightness and not touching their colour value. This IMHO is a much better and universal approach than changing individual colours. Then I also did some fine-tuning on my Ice Blue Day Theme.

Since now only a few parameters (mainly the global hue plus some fine tuning of other parameters) have to be changed, I also made a red version of my day and night theme. Maybe e.g. @rigattoni with his red FCC Launcher design can make use of them. ;)

I named these new themes Icy 3 Blue Day Theme, Icy 3 Blue Night Theme, Icy 3 Red Day Theme and Icy 3 Red Night Theme and attached them to this post, including a preview of how they look like.

Plase add them to the next test version. :)

Theoretically it would be possible to make an "Icy 3 Universal Day Theme" and an "Icy 3 Universal Night Theme" where only the global hue value (which e.g. is #0c6ee6 in my Icy 3 Blue Day Theme) needs to be changed. If the user would select this theme, FCC would have to ask for the hue value and dynamically put it into the json file before applying it. But when making the Icy 3 Red day and night themes, I realised that I had to fine tune the lightness settings of some elements to make it look well. When e.g. making a green or yellow version by changing the hue value, the day theme looks too bright and has a lack of contrast, so at least the global lightness value has to be lowered. So - if you like - you could try to add universal day and night themes where the global hue value can be set by the user, but then you also at least have to make the global lightness value adjustable by the user.
[Android Head-Units] rigattoni:
Thanks for sharing the themes.

Unfortunately I don´t use GMaps. I just use TomTom in here and this expects an own window, or just split screen which I use.

I ordered yesterday a really new unit from Klyde... 12.2" screen with PX6 and CSN2. This would normally completely working with Fcc. Let´s cross the fingers.

Hope it takes a short and fast way from China to me.

I think I have to sell now the one or other unit... :ROFLMAO:
[Android Head-Units] okij:
Hi @SpeedFire-, first of all, I hope that you are well. :)

I want to come back to an issue that I reported here:

for which you replied here:

I don't know if currently it's appropriate to remind you about this issue, but I think that at least it would be a good idea to stay in contact here on your thread.

There's also one issue that I already noticed twice when using the new Google Maps renderer and the auto-switch between day and night being activated: After parking the car in the evening with the night theme being active and then waking the head unit again at day, the day theme isn't automatically applied and only becomes active when entering the MiniMap settings.

We had this issue before and you already fixed it, so I assume that it just needs to be fixed in the implementation of the new Google Maps renderer.

Take care.
[Android Head-Units] Excessed:
@SpeedFire- I've been told to contact you.

First of all, I absolutely love FCC Launcher.

But, I have only one wish.

I love the FrontApp for Teyes app, but I really dislike the lack of customizing options, that FCC gives, in the stock launchers. And FCC allows a mapbox for Maps, mapbox, yandex. But I would want to use a Dutch nav with radar detection and stuff in there. With FrontApp I can place said app in the stock map box and it works perfectly, but cant figure out if there is a way to integrate that in FCC for example.

I would think it would be some kind of widget in which you can place a windowed app. But I'm not sure.

So I was hoping that you have an idea how to implement that in FCC or maybe know of a way already.

Cheers!
[Android Head-Units] Tronuk:
Hi all.

There is a question. Is there a version of the program for Teyes.

I have Teyes SPRO+. The program from Google Play gives errors when working.

Maybe there is another version?
[Android Head-Units] SpeedFire-:
I know about Teyes devices. They are pretty cool by using some firmware "hack" which allows to actually run any third party app in a free form window. However to work with this unique feature I need an actual device.

This means probably that I need to purchase one. What would you suggest? SS2, SPro, SS3 (probably not SS3 as it is excessively expensive)?
[Android Head-Units] SpeedFire-:
What type of error?
[Android Head-Units] Excessed:
Thanks for the answer! But i'd have no idea which one you would need. I'm using the app with a Navifly uis7862, and that app works on my head unit.

Maybe @surfer63 can answer this question for you.
[Android Head-Units] SpeedFire-:
So you mean that you can use this app on a non-Teyes device?

Приложения в Google Play – FrontApp для Teyes

Изменяйте приложение на главном экране Teyes с легкостью

play.google.com

Wow.
[Android Head-Units] Excessed:
That's the one idd! And (so far) it works flawlessly with the app I want to use as a frontapp :)

The WidgetUpdater app also (kind of) works, I can tap it to open the music player but then artwork won't show.
[Android Head-Units] SpeedFire-:
This is super interesting. Thanks!

I will try to run it on my MTK device!
[Android Head-Units] SpeedFire-:
Have you installed any custom firmware or Teyes launcher on your device?

Can you please give more details?
[Android Head-Units] Excessed:
I have installed the Mekede firmware on my headunit. Thats it, havent changed anything besides the microphone settings in the config file.

I am using the stock launcher that came with the Mekede firmware right now.

But I havent installed any custom firmware whatsoever.

Ask if you need anything else!
[Android Head-Units] SpeedFire-:
Thanks!

Here is a test version with all your styles applied - fcclauncher-3.501_test6.apk

It also has some unfinished new parts:

- New Fcc Settings (the icon is called Settings New) which uses the new recommended settings libraries (which were also used in all the new widget's settings). This is not finished yet. I have issues with a Back button implementation and non-working action bar (top bar) in this Settings New.

- Some icons were added to run system apps on some MTK device. I will hide them automatically for other devices in the next test version.
[Android Head-Units] SpeedFire-:
Thanks. Can you please also record a short video how your stock launcher looks like and how the app FrontApp for Teyes work?
[Android Head-Units] Excessed:
Here you go:

And I've added a picture with what happens when you don't select an app.

View attachment 5549807Hope it helps!
[Android Head-Units] ric69:
Since new 3.501, FCC launcher is restarting after 15 / 20 minutes randomly. I cannot find what's the problem
[Android Head-Units] HatManSan:
@ric69, @SpeedFire-

That is exactly what has been happening to me. I have been away recently and not had a chance to be in my car. @SpeedFire- you asked me to install the RAM widget. I did and RAM never exceeds 65% in use with Poweramp, Sygic and FCC running on top of core. Temps also don't go above 80c.

This morning, I had Poweramp running and FCC t5. I changed track and had giant text again. See image below. I immediately saved the Log. I rebooted and decided to try NavRadio 2.29. I get the Radio Station meta immediately in FCC widget but the other data only appears when (I guess) HAL's ROM flashes up the notification. Then FCC widget displays as it should. when turning on the headlights I no longer get "Apps" appearing instead of the second line of text in the player widget, I get the letter "M" instead. This is happening with t5, not t4.

On a side note. There must be hundreds of us sitting in our cars tweaking and configuring the HU to get the interfaces as we all want. How about a fund for someone to make a PC app that will allow us to compile an FCC backup using a mouse and keyboard etc and send that to the HU. Changes and tweaks would be so easy.

Thank you.

LogCAT file attached
[Android Head-Units] HatManSan:
Cannot attach to the thread above.
[Android Head-Units] HatManSan:
LogCAT
[Android Head-Units] okij:
Thanks a lot for your reply and for the new test version with my new styles applied. :)

I can confirm that it's working well here. Furthermore it also fixes the auto-switching between day and night style for the Minimap when using the new map renderer after waking the head unit. (y) If you didn't fix anything related, then most likely it's working fine with the built-in styles (which I'm using now again) but is not working when using the custom styles (gmaps_day.json and gmaps_night.json files). In this case you should have a look.

Also I'd like to ask if you now could have a look at this issue too:

Please tell me if you cannot check it right now. In this case we could ask @KoTiX2 to have a look first.
[Android Head-Units] gusmano_br:
Hi Guys,

Recently i buy this central: https://pt.aliexpress.com/item/1005...=glo2bra&spm=a2g0o.9042311.0.0.2420b90a1UXlni

With this spec: View attachment 5551215

Is not clear for me what is the difference about "TS10" / "PX5" / "MTCD" and "MTCE" and i don´t like the the actual launcher, i can use the FCC launcher?

thanks!
[Android Head-Units] mariodantas:
Yes you can
[Android Head-Units] GnFgr:
I have a small problem the last two weeks.

Px6 with hal9k 5.1 rom

Fcc launcher

Fcc tpms application.

Fcc was on autostart applications list in 4om settings and also on restart after sleep. That was working absolutely fine till two weeks ago.

Havent change anything or installed any new applications. It just stopped working when unit wake up from sleep.

Did try after that to reset fcc tpms, to downgrade from 1.14 to 1.13 version.

Only solution is to kill the application and reopen it every time unit wakes from sleep.

Is there any version i could try? Or any settings?
[Android Head-Units] aiui:
hi guys, i don't know what my MCU is, can you help me?

can i use the FCC launcher?View attachment 5552249
[Android Head-Units] Excessed:
You should be able to use FCC yes. Maybe not all functions, but the most of them for sure! Install FCC and it's plugins and set it as default launcher in Android settings.
[Android Head-Units] HatManSan:
@ric69 Hi. When your HU reboots, does it simply shut off, instantly going black, then starts up from cold?
[Android Head-Units] aiui:
in the launcher settings it asks what my model is, and I don't know what to answer, can you tell me what it is?
[Android Head-Units] SpeedFire-:
Wow! Really great idea! Thank you
[Android Head-Units] saverius93:
Love it!!!!!
[Android Head-Units] sarruma:
[MENTION=1633144]speedfire[/MENTION]

Hi,

your launcher rocks and you are a very supportive developer!

Now, a little question...Could you please think of any reason why the volume of the sound (of any source) raises when I enter the headunit settings app or in general any other app than my home screen? When I set the volume to the desired level and try to use any other app, there's a sudden pumping up which returns to normal after I go to the home screen. That keeps happening no matter what. So far, I haven't figured why, but it's very annoying and distracting... Could it be a setting?

Please help, that issue is driving me mad!

Thank you in advance.
[Android Head-Units] SpeedFire-:
This is an interesting bug. I don't remember anything in my code related to volume change while opening / closing the Launcher.

If you have a rooted device it would be great to get a LogCat log from you (ideally with video). Btw, what device / device type do you have?

Please also check that you have disabled all Xposed modules related to volume control (if you have any).
[Android Head-Units] SpeedFire-:
Well, many bugs were fixed in the past few days. Most importantly - FCC Launcher is now usable on Android 7+ devices (I'm not sure about 8.1 because Google introduced some hard to fix changes there, but anyway better than before).

New beta:

- Major bugs are fixed for Android 7+ (disappearing widgets and other)

- Much faster initial screen setup when the app is installed first time

- Some customization was added during initial setup (currently you can choose default accent color, later some other options will be added).

- Various bug fixes
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

Are you working on the theme I give you ?
[Android Head-Units] mrnorx:
I'll try the new beta today, if the music widget now works with DAB display, I'll buy premium. It's the only thing stopping me at the moment.
[Android Head-Units] mrnorx:
Well everything seems to work great on the new beta, I just wish I could get a widget to work with the dab+ modded APK. The only app that seems to work with it is carwebguru launcher but I like this launcher better.
[Android Head-Units] SpeedFire-:
Give me a link to dab app please
[Android Head-Units] L-ight:
So I have a Pumpkin Headunit 7.1 Android. Do I need to root this device before installing this launcher? Very new to this so any help would be appreciated. Thanks!
[Android Head-Units] Petrovych:
No, you don't. You'll need your device to be rooted only when you'll need to send a full log to the developer.