yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
It may have depended on what you backed up & restored.

I had some issues until I made sure I was running the latest Beta, and backed up from it, and restored to it.

Basically, I updated to the latest Beta .. did a backup. Then uninstalled FCC and then re-installed it again .. (ie a fresh install).

Then I did a restore, and it worked perfectly.

Before I did the uninstall & re-install, I was also getting a corrupted restore, with random background colors etc... which seem to be similar to what you are getting.

BTW: When I sent my Backup to SpeedFire- , when it was not restoring correctly to my Updated FCC, when he restored, it was 100% OK.

Then when I tried to restore again to a FRESH INSTALL of FCC, it worked 100% for me as well.

This is what worked for me .. :)

---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------

FYI: Works for me.

I use 500x500 jpg for both Radio Station Logo, and for embedded artwork in Mp3s.

Many of the FCC widgets have an option to display different STYLES, some of which do not include artwork.

Then when you have selected a STYLE for your widget that does have Artwork, there is typically an option in the widget to turn that display of Artwork ON or OFF (and in some case, to Circular).

SO, make sure you are selecting a Widget "STYLE" that includes artwork, and that in the Artwork settings for that widget, you have it selected to display the artwork.
[Android Head-Units] dgcruzing:
Loving it so far as well..

Paid for all the work the developer has put I to it..

Thanks for the effort..

Still playing and setting it up.

Getting Radio app crashing sometimes but haven't had time to debug. Seems to come right when I start it a few times..it's like it can't find a station then loses the plot.

Will keep an eye on updates and report anything a miss..

As said..thanks for effort..
[Android Head-Units] Scopesys:
FYI: I have never had a problem with the Radio, when using FCC ( last 4 months)... with it not being able to tune to the presets 100% of the time.

You might want to temporarily go back to your Unit's OEM Launcher, and see if the Radio is still acting up.

It may well not be FCC causing the issues.
[Android Head-Units] TT_Vert:
Tried that and it was even worse. Completely uninstalled and reinstalled/restored and it was even worse. In fact it looks as if it did nothing.

Dave
[Android Head-Units] Salvo-x:
Problems of stability of the whole system:

Audio problems and volume adjustment

frequent crashes

I uninstalled FCC launcher, to verify that the problem was not my device, but with the standard launcher, I have not encountered problems, my conclusions are that create these malfunctions is FCC launcher.
[Android Head-Units] SpeedFire-:
Please send me your .fccbackup file.
[Android Head-Units] tebukan:
Yes I have the same problems. my device px3 mtcd version mcu v2.95, Android version 7.1.2
[Android Head-Units] Scopesys:
Suggestion to all.

Since we all may have differing Head Units ( make/model etc), it would make things a lot clearer, when reporting bugs, if it was know what unit you have.

Could I suggest that everyone might add a description of their Head Unit to their signature, so when reading someone's post, the writer's issues were put in context with the Head Unit they have.

ie I have in my Signature

Eonon GA2170B. (p5x Oreo 8.0)

--------
[Android Head-Units] TT_Vert:
See attached. Had to compress them as .fcc files are not accepted here.

Dave
[Android Head-Units] TT_Vert:
Disregard, misread.

Dave
[Android Head-Units] whitewolf8111:
Firstly, It was merely a jab right back at you, as you did the same exact thing to my post. But I guess you didn't quite catch that. I did nothing but throw out an OPTIONAL feature as well, and you come along and crap on it without even reading that is was OPTIONAL too.

And by "endorsements" I simply meant my posts that I've wrote in other BMW forums of recommendations for this great launcher and that people need to go try it, to help give more support and attention to this launcher. That doesn't mean I must put it in my signature to have "endorsed" this launcher. Perhaps you don't know what the term "endorsement" means: "an act of giving one's public approval or support to someone or something."

I've only been playing with the app for the last few weeks at most, and trying to make sure it works as I want it to, and when funds are freed up for me, I will buy premium. My finances are none of your concern. Nor is the cost my car. And yes, originally, the car was expensive. But if you'd look it up, those cars are selling for only $5k or less as the car is 18 years old. I'm also fortunate enough to be a mechanic and can work on about anything, so I can do all work on the car myself and that saves me a ton. But it's been quite the project car as it sat for the last 8 years and needed a lot of work done.

So anyway, let's just call a truce and keep things peaceful :highfive: So now that we're friends again :), what car is yours? Kinda looks like a first gen Toyota 4Runner or Pickup?? I've got a 2nd gen (95) 4Runner that has been my reliable, awesome, pride and joy for the last 14 years. I love that thing and I'll never get rid of it. Someday It will get an Android head unit too, and the head unit sits in a very similar looking dash and position as yours. And, at least with my Appradio that's in it now, no direction was really "comfortable" for swiping for me because it does sit rather low and the driver sits rather high.
[Android Head-Units] SpeedFire-:
For me it restored like this:

Looks similar to your pic (besides different screen resolution which resulted in larger text).

Have you waited until the very end? You don't need to tap Cancel button. The app will restart and setup itself.
[Android Head-Units] whitewolf8111:
Certainly not really required but it would help in further customizing homepages and allow you to kind of combine multiple widgets into one ultimate widget and the user can fine tune the look and feel of everything a little better. But yeah, don't worry about if it's not just a simple thing to add. I know you have enough going on with everything else ;)

Unfortunately, my steering wheel buttons can't be picked up and reassigned as they are controlled through the i-bus of the car. Makes things a little more difficult for me there.

But I can understand your reasoning for vertical. No worries. I didn't realize how integrated the coding is for that feature.

No, there is no option for it. Just the "Active state" color.

I agree that normally white is the best for most things like that, but I don't use the controls over the album art and they are on top of a constantly dark colored background, and I have an amber color scheme going on with everything else that matches my dash lights. Everything else has a color option to it, and it would be nice to be able change the color of these buttons too.
[Android Head-Units] EwaldB:
Hello together,

I just bought this awesome FCC Car Launcher yesterday because it convinced me with most of it's features and because it seems to be a living project.

I didn't found the option to change the color of these buttons but would appreciate to change them, too. I'm using an amber color scheme too, so my request is the same :)

BTW: Is it possible to apply icon packs to FCC laucher and if, how do I do that? If not, is it planned to be added?

Thanks for your reply and first of all thanks for your great work.
[Android Head-Units] TT_Vert:
That would be good enough for me to fine tune. I did wait and clicked restart when it popped up.. I should be clicking restart right? No luck after trying again. I would think even if it was as issue w/ an app not being installed that it'd show the app shortcut icons for the ones that are installed.

Dave
[Android Head-Units] sbruda:
With all due respect that is not terribly useful. Given that vendors do not publish all the specs (most notably the MCU type is almost never disclosed) the brand and model number say nothing interesting except perhaps to people who have exactly the same model. The useful information would appear to be the chipset (such as PX5, etc.) and the MCU type (MTCD, etc.). Just out of curiosity, is anybody looking at signatures? I certainly never do that... For me it would be more useful to include head unit information in the body of the message.

In unrelated matter since the last two-three beta versions the launchers works flawlessly for all my use cases. Thank you very much [MENTION=4292729]SpeedFire-[/MENTION] !
[Android Head-Units] Scopesys:
Thanks for the feedback & advice. Based on that, I have updated the Info in my signature to include MCU type.

However, I see no point in typing this information every time in the body of the message, when it is better severed up in a signature.

This way it does not clutter up the Body, and only those that chose to read the signature, get to read what may be of little interest to some.
[Android Head-Units] TT_Vert:
FYI speedfire, I restored to the exact same unit and all was well so I'm not sure why to other units the config doesn't carry over but it's not a deal breaker. I'll just have separate backups for each and when I get a new unit I'll hope that issue is resolved.

Dave
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I also had this issue when 1 first did a backup & restore.

I sent you my backup, and it restored correctly for you.

I tried again, and then it restored correctly for me.

I think I have found a pattern, in the incorrect restore.

If I backup, the 1st time I restore, it is corrupted... especially background colors etc

Then, if I do a 2nd Restore, it restores correctly.

Tried this 3 times :

Backup - Restore (Corrupt) - 2nd Restore (Correct)

Knowing this, I can certainly live with Restoring twice... I am just so pleased to be able to backup and restore now .. :)
[Android Head-Units] TT_Vert:
[MENTION=4292729]SpeedFire-[/MENTION] noticed an anomaly w/ jet audio and album art. It will update the track name but album art NEVER shows. It just shows the last art from whatever was playing prior. Included a log for you. **UPDATE** Out of nowhere it just started working. Perhaps it was just doing some updates in background slowing things down? It took a good 2-3 minutes but it's working fine now.

Also, I think you deserve a little cash for all you've done and all the pestering I've given you. Got a paypal account I can gift you some cash?

Dave
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I am seeing a similar issue.

If I switch between PowerAmp and Blackplayer, the artwork stops updating.

(song & artist update fine)

If I have been using both Poweramp & Blackplayer, then there are two Notification entries when I pull down and look at notifications.

If I close the Notification for the player I am not using, then the artwork starts to update correctly for the player that is current.

The problem only exist when going in one direction ie switching to Poweramp, after running Blackplayer, where Poweramp artwork does not update.

Going back to Blackplayer, and the artwork for Blackplayer updates fine.

Switch to Poweramp and close BlackPlayer notification, and then Poweramp artwork now starts to updates ok.

It's NOT a big deal, once it is ealized what is going on. It's not like one is constantly switching players.

(easy enough to go in and close the notification when one realizes that Poweramp artwork is not updating .. unlike if FCC has had an internal crash, like was typical a month or so ago)

The recent improvement to the Player Widget have made its use so stable, and I thank you for all the work you have put into it to get it to the consistent working state it is now.
[Android Head-Units] TT_Vert:
another thing, more of a request. Is there a way for autostart apps tot start minimized? I have a sound mod that uses a modified amplifier.apk file and for it to be implemented I need to open it once but I never need to or want to see it, just have it run in background.

Thanks much

Dave
[Android Head-Units] sbruda:
[MENTION=4292729]SpeedFire-[/MENTION]

I spoke too soon, or rather I have a feature request: I am not sure whether this is intended but I would be happier with the old way of displaying the current street name. To summarize my experience, I have noticed throughout the various versions two classes of behaviour:

Hyperactive: the street name changes upon entering the intersection irrespective of whether the driver intends to switch to the new street.

Conservative: the street name change is slow, so that one has to be well on the new street for the name to change. In addition, whenever the system does not know the name of the current street, the name of the last known street continues to be displayed.

The current mode appears to be conservative, but I will argue that the hyperactive mode is more useful: For once, it offers advance notice of the intersecting street (presumably the driver is aware of the intersection coming up so she is not taken by surprise). Secondly, it provides very up to date information about the current street. By contrast, the conservative mode leaves the driver in limbo right after a street change, which is arguably the most useful moment to have street information displayed on the screen.

This all being said, please take this as a suggestion more than a request or bug report: however useful, street name is more of a gimmick: whenever I am in need of serious navigation I fire up my navigation app anyway since it is very accurate with this kind of things.
[Android Head-Units] Scopesys:
I have found, for the last 3 months of beta's, that the Street names have consistently been Hyperactive (when they are working). (same applies to Speed Limit)

What confuses me, is under what conditions, they should work.

I had assumed that when I did not have a WiFi or cell connection, that they would not update, as I thought they came from a google API.

Then, at times when I was driving around in the same location as the previous day, with no WiFi or Cell connection, they seemed to update ?? Is there some Cache effect going on. (I thought I read on this Forum that caching Google map API data was not really allowed :confused: )

If the Hyperactive was consistent .. ie displayed EVERY intersection, or side road, it would be a nice feature, but when the display is hit-and-miss, and cannot be relied upon, it is more misleading than useful.

In an ideal situation, there would be the option for 2 lines of information.

(1) The Current Road, with a very conservative update.

(2) Hyperactive Intersection/side road info, (that would never be same as Current Road in line 1)

And would side-road be for the car's side of the road only, or both sides ??

Starts to get complicated, and although I very much like the feature, and it would be great if it was Reliable, as it stands now, I see it more of a novelty -- if one really wants to know what side-streets are coming up, then some form of map is currently far more reliable.

The Current Road text displays probably need some form of AI, that is looking at the Car's position, speed and direction to be a reliable indication of what Road the Car is actually traveling down.

Maybe a little bit much to be asking of a Launcher ?
[Android Head-Units] SpeedFire-:
It seems that we're finishing work on backup / restore.

Beta 3.141

- Weather widget fix

- Backup / restore to / from Google Drive added.
[Android Head-Units] TT_Vert:
So out of nowhere the dang album track notification box that showed album art is now just showing a blue box. I'm NOT on 3.141 yet I'm on 3.139. No idea how these things work and they just stop. Very confusing.

Dave
[Android Head-Units] Salvo-x:
Hello,

even with this new version, on my device, there are stability problems, frequent crashes of active players, and unstable volume adjustment with the knob
[Android Head-Units] SpeedFire-:
Player crashes may be caused by FCC Launcher only if the launcher occupies too much memory. Can you put a memory widget and confirm this?

The best way would be to record a LogCat log but you don't have root..
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Was looking into why I was having a restore issue, and needed to double restore

Ref: widget_pref.xml

<boolean name="iconwidget_is_custom_layout336" value="true" />

is only "name="iconwidget_is_custom_layout" that does not have a _ before it's widget #

Should it be ?

<boolean name="iconwidget_is_custom_layout_336" value="true" />

----------------

Also some similar cases in ru.speedfire.flycontrolcenter_preferences.xml

ie

<string name="widget_track_saved517">Separate Tables</string>

instead of

<string name="widget_track_saved_517">Separate Tables</string>

If it is being saved incorrectly, then on restore, FCC may have some issues parsing these ones ???
[Android Head-Units] Scopesys:
Same here .. on 3.139 & 3.141

On selecting the player, there is a notification, and the data populates.

But on next song, no update, and there is also no FCC pop-up notification that song or artwork has changed.
[Android Head-Units] TT_Vert:
I don't get any album art on popup ever. I don't even think I had changed from 3.139 and it stopped working. It may have updated in background but it was working the last time I used radio. I don't drive this car in winter so that maybe have been 3 or 4 days ago.

Dave
[Android Head-Units] tebukan:
The microphone photo widget on the skins is not stable.
[Android Head-Units] SpeedFire-:
I've finally found a bug in backup restore function. Now it should be applied correctly after first restore.

Uploaded beta 3.142
[Android Head-Units] Scopesys:
Thanks SpeedFire- That's great news. :)

However, to get the restore to work 1st time, every time, I had to

(1) update to 3.142

(2) Backup

(3) Delete FCC

(4) Re-Install 3.142

(5) Restore --- worked

(5) Restore --- worked the same

Before that, I still needed to do a 2nd restore

(1) Update to 3.142 from 3.141

(2) Backup

(3) Restore -- INCORRECT --- many of the widgets had incorrectly parameters

(4) RESTORE -- Now all OK

(5) Restore -- INCORRECT --- many of the widgets had incorrectly parameters

(6) RESTORE -- Now all OK

It was not until I did a complete Uninstall & re-install of 3.142 that consecutive RESTORES were always correct.

-----

But so far, after a re-install of 3.143, the backup-restore seems to be working correctly now. :)

Unfortunatly, like other are finding, the Player Widget seems to have take a few backwards steps during the past few beat updates.. :(

Now it is virtually unusable.. both Artist, title & artwork stop updating (as well as FCC popup notifications) :(

The lack of Player Widget updates directly matches the loss of FCC popup Notifications.

----------

Now Backup-restore is working, and one can always get back to one's desired created screens, one can now easily re-install FCC and do tests with minimal FCC pages.

So.. I did this.

Backed up

Then completely uninstalled FCC.

Re-Boot

Re-Installed FCC with 3 players RADIO, BlackPlayer & Poweramp

Default screen with circular Player widget in center..

DID NOT EDIT or ADD any additional Widgets.

Blackplayer & Poweramp both have the same Player Widget update issues.

With 1st track change, update is correct

Any additional updates, and the Artwork, song & artist do not update.

Re-Starting FCC, and they work again, but as before, only for the 1st Track change.

So, Please could you make fixing the Player Widget a high priority...
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

3 Hours later .... EURIKA !!!

I've found out why (in my case at least), artwork, notifications, etc stop working.

If two players have been loaded, and they both have Pull Down notifications, then they confuse FCC.

To Reproduce: ( Now that we can easily Backup our Configuration, and try test ones!!! :) )

(1) Fresh Install of 3.142 -- default Page with Circular Player Widget

(2) Set up FCC with 3 QUickPlayers

RADIO

BlackPLayer (free version)

Poweramp (free version)

Set FCC Popup Player Notifications, incl Artwork

(3) Select Radio.

(4) Close any PullDown Notifications for BlackPlayer and/or Poweramp

(5) Select Blackplayer

Cycle through tracks... all Update correctly & Pop-up Notifications also run

(6) Select Poweramp

Cycle through tracks -- after 1st update, no further updates.

(7) Remove Pull Down Notification for BlackPlayer

NOW POWER AMP updates, and so do FCC Popup Notifications.

What is strange is that BlackPlayer can update when Poweramp has Pull-down Notifications

but

PowerAmp cannot update when there is a BlackPlayer Notification.

So it would seem that FCC is getting confused when there are multiple Pull Down Notifications ??

or .. whatever is causing it, the problem can be reproduced very easily with a simple test configuration from a Fresh Install.

For me, a temporary solution is to remove Poweramp from the Quick Players, and only have RADIO and BlackPlayer. While I am missing out on other players, at least I have a major Mp3 player that runs and updates correctly in 3.142
[Android Head-Units] SpeedFire-:
Can you please upload your fresh backup so I can reproduce your settings exactly?

My current plan is to:

1) fix recent bugs in player widget to make it more or less usable

2) release this version

3) fully rewrite player widget internals using more reliable methods of getting data from media sessions (improvements will be applicable to Android 5+ devices)
[Android Head-Units] Scopesys:
Looks like a very good plan :)

Attached is a ZIP file containing two Rev 3.142 Backups

Note: Looks like the backup filenames within this zip got messed up copying from google drive -- the .zip needs to be removed from after the .fccbackup (obviously)

(1) "Player_Widget" is a Minimal Test Player Widget

This clearly demonstartes the loss of Notifications and updates when players are switched.

(2) "1_Player_OK" is my current FCC configuration, but with only Two Quickplayers .. The radio & BlackPlayer.

Note: Switching between just the radio & Blackplayer is OK. It's just when another player is involved as well that problem start.

I include this backup really just for your interest, so you can see what I have done with FCC.

If you can get Player_Widget to run correctly, then hopefully the update issue might be corrected for all other players.
[Android Head-Units] audi tts:
Premium version

hello, congratulations for the app. what differences are there in the paid version?

---------- Post added at 10:53 AM ---------- Previous post was at 10:48 AM ----------

I really like the fcc app but I would like to know if it's possible to have a scrolling icon bar like the "car launcher" app I used before.
[Android Head-Units] Scopesys:
Read the full APP description on Google Play Store. (click on READ MORE)

== Free features ==

and

== Paid PREMIUM features ==

https://play.google.com/store/apps/details?id=ru.speedfire.flycontrolcenter&hl=en

NO BRAINER -- get the Premium Version ... a lot of Bang for your Buck -- you want the Premium Version to get the full benefit of this fantastic #1 Launcher ..
[Android Head-Units] audi tts:
Thank you.

it's possible to have a scrolling icon bar like the "car launcher" app I used before?
[Android Head-Units] Scopesys:
You will have to ask the Program Developer - SpeedFire-

It does have scrolling Pages, and you can put whatever Icons you want, arranged however you like, on those pages .. so it might well be more powerful & flexible than "Car Launcher".

I've tied a few other Launchers, and FCC is BY FAR the most configurable and feature packed.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Are you winning that battle with the Player Widget ? - does it look as if there is a workable temporary solution ?