yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
I think what you are seeing has nothing to do with FCC.

Your head unit in your car has TWO 12v supplies.

(1) Battery, (Battery Backup) connected all the time, that draws minimal power, and keeps the head unit's alive (sleeping), when you turn off the Ignition (Vacc)

(2) Vacc - Ignition, that is turned on when you turn on the Ignition, and is the main power source for the head Unit, waking it up, and supply all the power to make it run, display, and give audio output.

When you turn off the Ignition, the Head unit goes into standby, drawing its power from the battery backup connection, and is ready to start up again quickly when the Ignition is turned on.

After a time of being in Standby, (user setting), the unit turns off, and when the ignition is turned back on again, the unit effective starts with a full BOOT.

So yes, "the next morning" when you start the car, and the head unit has timed out and shut down, it start with a full boot, and everything has to re-load, so hence the Gray screens, with no Icons etc, until the system has fully re-booted, and FCC is back up running again (as it is your default Launcher)

So, bottom line, BOTH your head unit & FCC would appear to be operating as expected.
[Android Head-Units] Bueb:
I know what you mean, but I got this Problem only with FCC Launcher.

I installed Car Launcher AGAMA and all is working fine, also on the next day.

But I like FCC more, because I can customize more.

Maybe I chance my battery connection to 'all time on' later. Hope the standby(sleep) doesn't need too much energy that my car doesn't start if I not drive 3-4 days
[Android Head-Units] nokian95ita:
no folder fom me in my internal memory, i created manually? is true?
[Android Head-Units] mclaudio:
hello

my backup to google drive does not work. any hint?
[Android Head-Units] SpeedFire-:
Alpha 3.296:

- I've made some changes to the Player Widget. Please check if it works better or not.

FCC Launcher 3.296
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

This new 3.296 is NOT as good as 3.295.

At least (for me) with 3.295, after switching between players a few times, and possibly a re-start, the artwork & text then switched when players are changed correctly, and also as next & previous songs are selected.

With this version, I was NEVER able to get the artwork & text to switch to the correct data from the newly selected player "consistently".

Also, I notice now, that the RE-Boot Widget, does not work the 1st time it is pressed. It does a re-start FCC the 1st time it is pressed, but then then the 2nd time it does the expected re-boot. Was like this in previous 3.294, but worked ok in version prior to that.

What is strange, is that you (Speedfire-) said you do not seem to see this incorrect Player operation when you run FCC on your emulator (or on actual Hardware) ?? (or do you ?).

When you test, what 3 QuickPlayers do you use ?

If things are working for you, Can you post your FCC setting backup, so I can try running more closely what you are testing with, to see if running with those setting work for me. ( I have a very complex and extended set of screens etc.. maybe that is a factor here, so let me try running the same FCC restored setting that you are using, and see what happens.)

---------- Post added at 10:10 PM ---------- Previous post was at 10:05 PM ----------

Always works 100% ok for me. Is your Google Drive app up to date ?

(They seem to quite often update it .. my phone is often saying there is a new version to install !!)

Try using the Google Drive app, to copy something off your Head Unit, and see if it then appears correctly on your Google drive.

Maybe you saved login info on your Head Unit is not correct ??
[Android Head-Units] michLQ:
This does not work for me. Have it downloaded and copied as you described it. Street name widget shows only "none". In widget settings I have selected "Internal + Openstreetmap" maybe that works only with the beta version?
[Android Head-Units] nokian95ita:
Good morning I am happy to use this launche r and I have same question for correct use

1 I downloaded the open map but I don't understand how I can use it. I created the folder because in my internal memory there not was but today it continue to use on line map: suggest me the correct set up

2 when I open an app the fcc reboot and close Bluetooth why?

3 i don't use fm radio but a streaming app that is called radio italiana and the widget don't work properly with this app: suggest me an good app for Italian use excluded tuneln

Thanks

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] emerax:
Try fm-world ;)

Inviato dal mio Redmi Note 5 utilizzando Tapatalk
[Android Head-Units] AdekP:
[MENTION=1633144]speedfire[/MENTION]

Could you deal with this problem? Or write how to get the previous beta version that worked for me correctly?

I will add that yesterday I did a clean installation and there are still continuous restarts in the loop :(
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I had major Player Widget issues with 3.296, so went back to 3.295, which (for me) works (so much better).

BTW: FCC widgets back at top again with FCC icon. Altitude widget switching correctly between Feet & Meters.

(Might have corrected due to complete Uninstall, manually deleting all signs of FCC data etc, and then after cold boot, a clean install of 3.295)
[Android Head-Units] mclaudio:
hi to all

i am trying to connect obd...until now i was not able to do it, altough i disabled again the option on factory setting of the unit,on the autorun on boot on FCC and removed the OBD widget, altough i keep always receiveing a small pop-up notification on the botton of the screen saying that the odb widget cannot find the odb device.

how can i solve this?

thanks a lot for the best launcher ever
[Android Head-Units] emerax:
on Atoto A6 is there a possibility to force the fullscreen?

Inviato dal mio Redmi Note 5 utilizzando Tapatalk
[Android Head-Units] segu45:
In the latest updates there is a problem with the minimap. When you restart the system or restart the launcher, no matter what color you have chosen, the one that is default appears, you have to enter the map options, give ok without doing anything and then that is when the color you have chosen previously is . The same must also be done so that it switches to night mode, when it is already dark and the car lights are on. You can have a look?.
[Android Head-Units] Bauru-SP:
Hi [MENTION=4292729]SpeedFire-[/MENTION], you did an excellent job with your app!

Could you make it so it is possible to adjust margins/borders on ALL widgets? It would greatly improve positiong and placement. It is currently possible on some of them, but not all.

Right now I can adjust borders/margins on apps, but not on the time widget, weather widget, player widget, bluetooth/wifi widget, speed widget.

Thank you.
[Android Head-Units] dooGemaG:
Silly question. How do you unhide the mini map once you hide it?
[Android Head-Units] TYourdog:
Well I figured out most of my confusion with the minimap.. after typing in address in 'home' and 'work' you have to click the search icon to the right of the address, THEN click ok.. I was so confused haha but that part is working now.

Click on 'Apps' then click Map (earth icon)
[Android Head-Units] TYourdog:
Is there a way to change the font size and color of the streets within the mini map? When I zoom in to the map the street names stay the same tiny size making it hard to see which street I'm on.. in settings I notice there's an option for changing street size but it only changes the size of the street I'm currently on at the top of the map box.
[Android Head-Units] Scopesys:
I have chosen not to use Mini map, mainly because, here in the USA, it appears that Google map is a better option (unless I am missing something ?)

However, when I did look at Mini maps, I seem to recall there should be an option to make your own Configuration file, to control colors, etc, bur there was not much information on how to do that in FCC, so I never perused it.

As far a controlling Mini Map, I chose to set the map so if I did a long press on it, it closed it, and put a FCC Apps Icon on the screen where the map can appear, to open the map, if I wanted it active.

Worked for me, but I ended up never using it.

Really, I have never really understood the reason for developing MiniMap within FCC, apart from the feature it has, that it can display a Map in a sized window, so you can see other things on the screen at the same time.

Very cool that this can be done, - but maybe I am missing the BIG PICTURE as to what Mini-Map is really all about ???
[Android Head-Units] mclaudio:
widget problem

hello to all

i have the following message always appearing

how can i remove it ?

i dont have any widget active thans
[Android Head-Units] TYourdog:
I'm in the USA too, Google maps is better for more in depth stuff but if I want quick access to my apps and still have a view of where I'm going, then the mini map is an awesome idea IMO. Just 1 less step if I want to change music or something while on the road.

Anyone have any information on making a config file for the mini map?
[Android Head-Units] taffanaro:
I like the Launcher, but .... :)

I tried to use MiniMap, but everytime it says something like "routing failed.... you don't have an API Key" or so.

But according to an older post of speedfire, there is no need to enter am API Key.

How can I get it to work?

Best regards

Taff
[Android Head-Units] bossman4:
I finally got home and tried 3.296. I did not detect any changes compared to the last version. Still has problems on artwork. (that is what I am focusing on for the EONON player). Not sure why my results are different than Scopesys…...
[Android Head-Units] Scopesys:
Both still have problems, but I found that 3.295 did work reasonably well, once it had settled down with the Mp3 player BlackPlayer. Helped manually closing any other Player apps.

In contrast, I could never get 3.296 to reliably update Player artwork when songs changed, no matter what I did.

Hopefully, there can be one last, successful push to get the Player Widget to run reliably for everyone.
[Android Head-Units] SpeedFire-:
[MENTION=9325785]Scopesys[/MENTION] please test this Alpha 3.297. I further changed the "bad" 3.296 version, because I still think that we should move in this direction in terms of Player Widget.

Please compare 3.297 to 3.295.

FCC Launcher 3.297
[Android Head-Units] ab1702:
I use a px5 unit and I don’t really see too many issues with the player widget, I get the odd glitch every now and then but nothing major so could it be more to do with the actual players people use or maybe how many screens/widgets people use in fcc?

I only use Apple Music and dab-z, I have a2dp as a 3rd player but never use it and then also I only have one screen set up on fcc so what I use is quite minimal but perfect for what I need and I don’t really ever have any major problems.

I’ve noticed a couple of little things on beta 3.295 where if I’m listening to dab-z then after about 5 minutes it will randomly start playing Apple Music and switch player to that one. Also if listening to dab-z the progress bar is permanently on and full to the end.

I also noticed something last week which I found interesting. I changed the antenna for DAB radio on my car and the new antenna basically gave me more or less no signal. Whilst trying things to fix this,with the dab-z app on fcc kept restarting with the arrow on the screen, dab-z would freeze and then fcc would restart, it was a reoccurring pattern. As soon as I put the original antenna back on which gave me full signal, dab-z worked properly again and fcc never restarted again and worked as normal.

What I’m trying to say is that for all the hard work speedfire puts in to this launcher this to me just shows that programmes and applications out of his control will affect it but users may just think it’s an fcc fault.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Thanks ... I just tried 3.297 for about an hour in the garage.

Unfortunately, there are still issues where it does not work as expected, but when it does not work correctly, I see no obvious pattern to what makes it start working again correctly, and then suddenly stop.

One easily identified symptom, that might be a good clue, is that sometimes when a Quickplayer is selected, that player shows selected for a brief second, and then it returns to displaying the original player.

This is a very basic, and clear bug, and it may be this that is leading to FCC getting confused as to what Player FCC "thinks" is selected, so what Player it gets Notifications from.

At the back of mind is the thought that this "May" be being cause by having copies of very similarly setup Player Widgets on multiple screens. If I do, they are always set with the same 3 Quickplayers (in same order), but maybe there is some sort of interaction / race condition between them. ?

It's going to be a lot easier for you to find out what may be going on at your end in the emulator, or with Android Studio, so maybe you might want to try running with my FCC settings, and see if you see issues with it at your end.

Everyone has different setting, and maybe these issues are a function of those different settings.

Attached is my current FCC setting backup.

(settings and associated .png, zipped up in one file for the forum)

Obviously, anyone is welcome to download my setting file, and "look see" , but for your own good, make sure you can backup & restore your own setting, before you load my backup !!

Also, bear in mind that some Icons will not do anything, if you do not have the correspond APP installed !!!

ie Just because I have an Icon to select "Spotify" it will only work on your system, if you actually have Spotify installed. ;)

Would be Interested in any Feedback if you try it :confused:
[Android Head-Units] SpeedFire-:
Thanks for testing. No, this is not caused by your screen setup - this is caused by the audio players and when/how they post notifications to the Android system. The second part is how FCC processes this data.

I also continue to see issues in my emulator but sometimes everything works fine. I will make another attempt to get rid of these bugs.

With 3.297 I just wanted to know is it better than 3.296 and is it still worse than 3.295?
[Android Head-Units] liamstears:
I haven't tried 3.296 or 3.297 but I did find when using Poweramp I had many issues with the widgets not displaying correctly but I've now changed to Stellio (which I must add I think it is inferior to Poweramp) to try and I've had almost 0 issues with the player widgets

Only consistent issue I've noticed is at the bottom of my screen I have the play/pause and skip track buttons which work fine but if I play/pause using factory button on my dash the play/pause button doesn't update and shows pause regardless or if music is playing or paused
[Android Head-Units] bossman4:
Tried it on both units. The EONON unit like Scopeys and a Pumpkin Single Din, running Android 9.0 but apparently a much slower machine. I am autostarting the three music players during startup with 3 seconds between each startup. My there apps are 1) Amazon Music, 2) PowerAmp and 3) FM Tuner (podcast player). I started testing after a brief time to get the unit to settle in

EONON

3.297 was better than 5 or 6 and for awhile I thought it was working, It was picking up the artwork on the three apps. Then after some consistent button pushing, it started to get confused. It was trying hard. When it did the behavior of picking the wrong art going from 3 to 2, it would toggle the art several times until it settled on the right art. Then the Amazon Music started to be inconsistent. On this particular radio, I had it playing downloaded songs on Amazon. Still not right, but closer.

Pumpkin

Clearly this is a slower CPU and everything acted in slower motion. I set up the sequence the same and put a delay in the auto startup of each player. Switching players works great, but the art does not follow and Amazon does not show at all. On this test I was using streaming rather than offline songs for Amazon. It appears to me that the same button sequences on the slow unit are not working correctly. I tried to slow down the button switching and hitting play and pause to give it time, but to no avail on Amazon. Was working partially between Poweramp and FM Tuner, but not near as well on the EONON unit

3.297 is definitely better, but not quite there.
[Android Head-Units] Scopesys:
yes, better than 3.296, but not as good 3.295.

In 3.295 I did not see the wrong player (ie not the playing player) ending up showing as the selected player.
[Android Head-Units] bossman4:
Did some more testing on the Pumpkin unit. Found a missing checkbox for art work (lots of switches for all the options). After I set this and did some downloaded songs on Amazon, I was getting the same type of behavior as the EONON, but more in slow motion. It is really curious, but the most stable application out there in the switching department is the FM Tuner (podcast player). It has notification boxes like the other apps, so it does not appear that notifications may be a culprit, but they may take CPU time.
[Android Head-Units] pr0l4m3:
3.297 - android 8.0 px5 - album covers are ok, but title are eta -1 (ex. song 1 - title 1, song 2 - title 1, song 3 - title 2)

[MENTION=4292729]SpeedFire-[/MENTION] maybe its possible to add layers to home screen for widgets? Or its possible to add widgets above the map widget? Cheers.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Make a couple of Videos this morning with latest 3.297, that clearly show whats some of the symptoms are when FCC has issues with the Player Widget.

What I see is

(a) FCC not always knowing what is the currently playing player, because when it got selected, FCC after displaying that newly selected player for a second, then went back to displaying the previous players info.

(b) Even when they are on the same page, multiple instances of the Player WIdget can get out of sync with each other... ie Two Player widgets displaying the QuickPlayer selection, can display different Current Quickplayer.

Attached, two Mp4 videos

On the 2nd Video, I turned on TOUCH Press Display, so it is easier in this 2nd Video to see what is being selected on the screen.
[Android Head-Units] SpeedFire-:
Here is a 3.298 with further improvement of Player Widget.

I still see some issues with PowerAmp and album arts. But overall it performs better.

FCC Launcher 3.298
[Android Head-Units] oddvarr:
[MENTION=1633144]speedfire[/MENTION]

I have been using the latest 15-20 alphas. But not 3.296. Installed 3.297 today.

Finally what is playing now is beeing updated. But it seem itonly did when I changed song in Poweramp or switched channel on DAB-Z.

It seemed to me it did not update when current song was finished and next started.

Then I see you have released 3.298 Will try it later.

Seem better and better this. :D
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Looking better :)

The multiple instances of the Player Widget no longer seem to be getting "out of sync" (as they were in previous posted video for 3.297)

However, the issue where FCC is told to switch players, does do, but then goes back to show the previous player selected, along with the previous player's info, is still an issue in 3.298.

In 3.298 this behavior is now a lot more repeatable, and might be the last remaining bug to be fixed, before the Player Widget is running as expect.

Attached is Video of the new 3.298, clearly showing the issue of FCC jumping back to displaying the information from the previous player, because it has jumped back to the previous player, after briefly switching to the newly requested player.

Almost there ;)

Video attached
[Android Head-Units] Scopesys:
3.298 is defiantly the best to date. :0

Drove for a bit today, and this is the 1st time in for ever that I felt I had a reliable and consistently working Entertainment Center in the car.

Changing players still has some alight issues, but once the new player is established and working, song updates and artwork updates seem to be flawless.

[MENTION=4292729]SpeedFire-[/MENTION]

While you are in the Player Widget code, is there any reason why the 4th player, once evoked, should need to be removed if one of the other 3 players are selected ?

Could the selected 4th player stay there as a 4th player, until such time that a new 4th player is selected.

Ideally, stay there through FCC restarts, and system Resets/cold boots.
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] I don't really see much difference between 3.295, 3.296 and 3.297 and worked okay. But with 3.298 it is actually worse for me, it rarely updates the album art at all no matter what player I have selected. And if I switch between the players enough, sometimes it will bring the album art up... and sometimes when I try to switch to another player it gets weird and will bounce back to the other player I was just using, and not the one I want, all while usually stuck on the last album art that happened to work.

With all the latest ones, sometimes if a player hasn't been started since wake, the album art wont update until the next song or you skip to the next song.

And not a big deal really but I've noticed for a quite a few versions now that the track progress indicator bar is not very accurate as when the bar gets to end, it's still not the end of song.

***All the above are minor issues to me. I don't switch between players too frequently so they are of little concern. My biggest issue is the constant crashing while coming out sleep. I've tried to tell you about this in the past but it keeps getting ignored. I have to go all the way back to 3.222 Alpha5 for the crashing issue not to be there so it must be something that was changed in between. I know it also has something to do with USB devices, and I MUST run a special USB adapter to interface with my car and this app called I-BUS app that I have to use in order to turn on the factory amp, that gets loaded when the USB mounts after sleep (which is almost instant) and it seems to freak out FCC that it loads right away and causes it to crash. I also think the root cause has something to do with USB devices because I can ALWAYS make FCC crash by just plugging in OR unplugging a USB keyboard or remote. USB thumb drives don't seem to be affected.***
[Android Head-Units] bossman4:
I tried the 3.298 on both radios today in the garage. It is better than the other 3. Seems to be more consistent on Poweramp and FM Tuner which are set to play off of the USB or SD card. It does work on Amazon music, but it is more sporadic. I tried to use the Amazon offline music mode where the music is stored on the USB or SD card and it seems to work better, but it still gets confused.

This is still a work in progress and seems to be very sensitive to whether the players are started and running.

Definitely making progress.
[Android Head-Units] SpeedFire-:
How does this crash looks like exactly?

I see one crash reported on 3.298 version. It relates to some internal bug in built-in Google Maps (the cause of crash is inside the google's part of code which makes it difficult for me to fix). Can you try to disable google maps MiniMap and restart? Do you still have this crash?

Ideally you need to record a LogCat log and send it to me (try to search words "FATAL ERROR" in the log by yourself). Sometimes LogCat Extreme app can record a log even during wake up.