yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] mclellan83:
Sorry to bother you guys but figured I have tried two of the resident experts on this type of stuff with no luck, and I apologize that I am not very knowledgeable on this stuff. I totally redid my 84 Monte Carlo SS both outside and now finishing up the inside of it. While doing so I came up with the idea of having a dedicated head unit run a backup camera, air ride controls, and other accessory type of stuff. While having a second unit run the stereo and front facing DVR, I thought I was all set because it had Bluetooth and I avoided the issue of having my phone run bluetooth stereo on one while the other would be able to bluetooth for the air ride. The one I have setup for running accessories I installed the FCC on and from what I have been using it on I really like. But truthfully still trying to finish up the car and then actually use this setup and how it'll best work for me.

What I currently have is these two units, JY-UOS02N4PX5S and UK-JY-UOS01P4V. The UK-JY-UOS01P4V is the unit I was hoping to run the Ridetech air ride app on to control the air ride. But I can change how I have the two setup if it would make a difference, but think they are pretty much the same specs except that the UK-JY-UOS01P4V has fast boot which is part of the reason for choosing to run it on the accessory stuff. Thanks for your time and sorry for invading another thread but have searched through and not found anything related to my specific units. And I think it is related because while it may not work on my units integration of the air ride app would be a really nice feature. Here is a pic of the basic setup of them to mimic modern cars to a point, this was when I first got them connected to make sure I could wire them both up and partially work.

View attachment 5014509
[Android Head-Units] SpeedFire-:
1. I decided not to use LAST_FM_ALBUMART file because it used to use read/write to/from sd card operations which are "expensive" in terms of data processing time. Now everything is done in RAM only. However I have found some last bits of code which still used this and deleted them in this version of the app (see below).

2. Despite the app developer's claims that he uses MEDIA_BUTTON receivers he does not (maybe he uses dynamic receivers but he better use the static receiver as well). Please ask him to add something like this to the app's Manifest:

<receiver android:name="com.kodarkooperativet.bpcommon.util.aosp.NewMediaButtonReceiver">
<intent-filter android:priority="999">
<action android:name="android.intent.action.MEDIA_BUTTON" android:priority="999"/>
</intent-filter>
</receiver>

Then FCC Launcher will identify this app as a media player.

New version: FCC Launcher 3.365 v3
[Android Head-Units] SpeedFire-:
I installed your backup and was unable to reproduce the crash. However I tried to fix it based on your Log. Please try to install the new version posted in the previous post.

Overall it looks like you had too many experiments with the Launcher in the past and accumulated some errors. Maybe it would be a good option to make a clean install with a restore from the backup.
[Android Head-Units] okij:
Thanks for your detailled reply, much appreciated! :highfive: I'll pass this info to [MENTION=2734955]KoTiX2[/MENTION].

So when NavPlayer+ will then be recognized as media player and can be set as one of the players in FCC player widget, will the widget display the station name / logo / RDS info of NavPlayer+'s broadcast intents?
[Android Head-Units] KoTiX2:
Nope,I never said that. I said that i haven't implemented media buttons yet but the mediasession and the metadatas are working properly.

Agama Launcher and Ubiquity widget can read the metadata from NavRadio without problems and without needing to use mediabuttons at all.

I tried adding other media intents to make Navradio being recognized as player but they didn't seem to work.

I'll add the mediabuttons receiver as you said and see what happen. Tnx ;)
[Android Head-Units] Drunkenninja:
I just purchased the full version, as the test version on the recommendation of [MENTION=5022255]whitewolf8111[/MENTION] has fixed a lot of problems in my BMW but I am a bit lost [MENTION=4292729]SpeedFire-[/MENTION] as the initial setup is great but feel I am missing out on a lot of functions that I can't find a guide for. I would appreciate some help.

1. Is there an icon/widget pack for FCC, if there is where can I find it, download and apply?

2. I managed to add basic widget info to the center widget, is there a way to turn this into a nice analog clock?

I am an avid reader and if there is a guide video or written showing the full capabilities of the loader I am up for a read.

Thank you, initial impressions are that this is so much more than just a loader!
[Android Head-Units] SpeedFire-:
Sorry. Probably I misunderstood someone's words.

Please give me a link to this test version once it is ready.

Being recognized by the Launcher will not solve the issue (cause the Launcher tries to get the same data directly) but it will allow me to make a workaround.
[Android Head-Units] okij:
I just tested FCC Launcher 3.365 v3 but unfortunately it doesn't solve the problem that I experience when using the stock (respectively Hal9k Mod 4.0.2) FM radio app: The problem is that when switching from FM radio to a different media player and then back to FM radio, the station logo isn't displayed anymore. So if you don't write LAST_FM_ALBUMART to sd card, it might be that you have to keep it "safer" in RAM and use it again after switching back to FM radio. Please have a further look into this. :)

---

Thank you both guys for working on this now! :highfive:

It will be very cool when NavRadio+ is fully working with FCC's player widget!

If you need someone for testing, please let me know.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION] Some thought on SPLIT SCREEN functionality in FCC ...

( If anyone else had idea or suggestion, now might be the time to submit them, before the Split Screen functionality design is completed)

Great news that is technically possible for FCC can now work in a Split Screen mode, but to best make the best use of this feature, here are a few thought & suggestions.

When a currently designed FCC page is put into a split screen, there is obviously a change in its aspect ratio, which is going to alter/distort it's original design layout.

A screen layout designed for full screen, is not necessarily going to display in a such a optimal way when in split screen mode.

So rather than trying to force a FULL SCREEN designed page into a split, it might be better to design addition FCC pages to be optimized in the Split screen format.

Why would one even want Split screen ? The most obvious answer is to display a Nav App, along side FCC with its widgets.

But, when you don't need Nav, do you really want FCC to only be displaying on a small part of the screen , with the other part of the screen wasted, or when operating in Full Screen mode, displaying a page that was really optimized for a small, different aspect ration to work with a Split Screen ?

A better design solution, might be to design some new "Split Screen" Screen to be optimized for when you want another APP displaying in a split screen along with this Split Screen designed FCC layout.

This way, you get the best design for both a Full Screen FCC display, or a SPlit screen FCC display.

I would imagine having my currently designed screen (optimized for full screen), along with other Screens designed for SPlit screen mode, and be able to quickly go to one of these screens with a "select page" button, or a swipe etc etc.

This would require that ALL screens have the Parameter, full, 75%,50%, 25% for when they are selected, and automatically appear in that mode, with a parameter defined APP running along side FCC.

To achieve this, my request is to add the option of these two parameters to every screen definition (Default being full screen, no app)

So this would have no effect on existing FCC Page designs, but would allow Pages to be defined to be specific SPlit Screen pages, with appropriate design and layout.

This is NOT to disregard the current option to manually put an exiting FCC screen into Slit mode, but rather to add the ability to have a optimized design layout when choosing to use specifically designed "split screen" Screens.

==============

BTW: Page selection Button Widget -- could this please have the Button Style parameter added (as most other Button WIdgets have)
[Android Head-Units] Yak54:
minimap

I also have a problem with the minimap since the last beta. I have to switch it off and on after each start of the headunit to make it visible again.

Is it possible to create a widget or button to show the minimap? Switching off with a long keystroke is quite good.
[Android Head-Units] ric69:
Please how to add exception for rear view camera in full screen?
[Android Head-Units] rigattoni:
Okay, after clean install with my last Google-Backup, it works fine. :highfive:

Idea for split screen:

On one side of the screen you have FCC running and on the second part navigation. In background some music is playing and source, file or station can be switched on the FCC window.

What now happens is, that the navigation is set to background and the player comes up... not wrong so far, because some player want to get to foreground.

But after the change of nusic has been done, the player does not go to background again and the navigation window is gone.

You now need to tap on the last apps button, choose the navigation to get it back in the 2nd window.... hhhmmmm... not that comfortable.

So I tried to get this fixed with Tasker.

Idea:

If a player comes up, the task is waiting for 5 seconds if the screen has been touched. If yes, it waits again 5 seconds. If not, Tasker switches back to the last visible application... in my case back to navigation.

As this is really tricky to implement for common user, I would like to ask if something like that would be possible to implement in FCC.
[Android Head-Units] Scopesys:
Yes, just create a APP button to start the MiniMap. ( The long press on the map can set set to close it , as you already know)
[Android Head-Units] Yak54:
I have tried it, but it does not work reliably.

First I made a link to the app on my second screen, but unfortunately the icon remains very small, even if I set icon size to 300. Then I assigned a button of the headunit to the app. In both versions the display jumps to the home screen and at the bottom there is a banner with a note that the map is displayed. It is then sometimes really shown after the 4th or 5th try, sometimes also on the home screen where I don't want it. But in the options it is always marked as displayed. If I switch off the minimap in the options and then switch it on again, it works until the next start of the headunit.

I use Mapbox, in case the problem is related.

In the previous beta versions it was better, I had to do a few tries until the minimap was on the right screen, but then it was still active after a reboot.
[Android Head-Units] SpeedFire-:
I can't reproduce the issue with the Minimap not being showed. Can you describe all steps or send a video?
[Android Head-Units] Yak54:
I'll see if I can do it tomorrow. Thanks
[Android Head-Units] hapaman:
You can find a video here https://1drv.ms/v/s!AqBx6DjK0ovThy8PXEb1T9Svwoyq
[Android Head-Units] Drunkenninja:
[MENTION=4292729]SpeedFire-[/MENTION] I know your busy, but could you reply to the above, I did pay for the launcher. .

Your launcher is so deep, it really needs a guide and the 600+ pages are impossible to navigate even with a search.
[Android Head-Units] SpeedFire-:
FCC 3.365 v4:

- Most widgets auto-scale in split screen mode (please report about those that do not).

- AlbumArt mask with a chrome circle is added (this is a vector type of a mask that previously was a part of a skin in the most popular skin with MiniMap).
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I appreciate you adding an additional extra Album Art Masks, but PLEASE can you add at least one User Defined mask, that is associated with each particular instance of of the Player Widget.

Here is why.

(1) Currently, with a square Artwork, the progress bar along the bottom (say red) can be lost if the artwork is red at the bottom.

So in this case, I would want to make a Mask that just darkened the very bottom of the artwork, so the Bright Red Progress bar shows up better on the mask darkened lower part of the artwork.

(2) For a Spit screen display, which is still going to show the artwork, to save space on the FCC side, one would probably want to put text (Song, Artist name etc on top of the Artwork)

(With FCC Full Screen, there is more room to put them OFF the artwork, so they show up very clearly -- which is what I currently do)

But when text is placed on top of the artwork, it would be good to be able to darken the specific parts of the artwork where the text is placed, leaving the rest of the artwork to be bright and clear.

Depending on what one ends up placing as text on the artwork, one would want to be able to customize this mask.

So before the addition of Split screen, the user defined mask was requested primarily for adding definition to the progress bar, but now with the split screen options, there is even more desire to be able to customize a mask, to add definition to any text placed on the artwork.

BTW: for need 2, an even better solution would be top be able to put a custom color, "drop/shadow background" around any text displayed on the artwork.

This would be IDEAL, and would seem to be technically possible,(Text write options) but might require a little more coding, that just adding the option of custom masks.
[Android Head-Units] SpeedFire-:
To be honest this will require some very boring work to do. I am not ready to do this right now.

What I suggest is that you draw approximate images of these masks and I will redraw them in vector and include into the app.
[Android Head-Units] bajoseph04:
I use the "Car Widget" app with "Monoic SQ" icon pack to make my home screen look like this. I know it's pretty simple but looks neat. The "lines icon" pack goes well too.
[Android Head-Units] Yak54:
minimap

I tested it again today and made a video of it.

After switching on the headunit there was no minimap to see, as expected. To switch between the screens I mostly use buttons of the headunit.

First I clicked the app icon on the second screen, FCC jumps to the home screen and shows 'map is visible', but there is no minimap visible on any screen. Then I did the same on the third screen. FCC jumps to the home screen and shows 'map is visible'. But there is no minimap shown. Then I opened the FCC menu and it says that the minimap is enabled. I used the 'Turn off' option in the menu and FCC goes back to the home screen and shows the minimap on the home screen, the second and third screen. I then disabled the minimap on the homescreen and everything worked until the next reboot.

In previous versions of FCC I had to try several times until the minimap was displayed as desired, but it was still visible after a restart.

https://youtu.be/1s-JkOcZN7A
[Android Head-Units] SpeedFire-:
It seems that I reproduced this issue. Please test: FCC 3.365 v5
[Android Head-Units] Scopesys:
Thanks for reply... getting the mask right 1st time without trying them in FCC is difficult (as demonstrated by a mask I submitted about a year ago), so maybe it is better to hold off till such time that you might be ready to address user masks.. I appreciate that the current " Split Screen" work is far more exciting to do :)

Hopefully, if at a later time that you feel like looking at it, the option to have a drop/shadow text option for Player Artwork text, might not be too boring to code.

There are other areas where drop/shadow text might also be of visually of benefit, like the Speed information displayed on the Mini-map :)
[Android Head-Units] Drunkenninja:
Thank you, this is really helpful.

It is a shame that [MENTION=4292729]SpeedFire-[/MENTION] didn't reply. Not even a thanks for your purchase. disappointed to be honest. He has cleary read two very polite messages and decided to ignore them. favoring replies to others. Thanks to this great community I did get some help.

I understand the push for development and it is great the launcher continues to evolve, but surely new purchases play a part in encouraging such development.

Anyway a big thank you for your time and help [MENTION=9483956]bajoseph04[/MENTION]
[Android Head-Units] Scopesys:
Tried this version this evening ( 1st version with split screen I have tried)

(1) Home button on head unit no longer works ( Page select widget and Home on steering wheel work)

(2) In split screen mode, widgets text size cannot be changed. Siders move, but text is not resized.

I go back to what I said (predicted) a few days ago, before I tried Split Screen.

Splitting screen with a FCC screen "optimally designed" for Full screen does not lead to a very satisfactory result.

If a FCC screen is to be run in Split Screen mode, it is best designed with that format & size in mind, and will typically have less content that a full screen , because there is less room.

To this end, I would suggest it is better to be able to set a given screen to always display in split mode, and then design that screen for that format.

Fcc would then consist of multiple Screens, some Full & some Split, with the % split being part of the screen's settings, along with the app that is to occupy the other part of the split screen.

This would also eliminate the need to have intelligent/dumb resizing.

A given screen would either be FULL Screen, or split (75%, 50%, 25%), and in each case, would be designed with that size & aspect ration in mind.

(Btw .. I could only achieve a 50% split with this FCC version) ????

Splitting existing screens, really does not work, and just leads to unusable FCC split screens

Also, manually Splitting screens when driving is a non-starter unless you have a death wish.

==================

Attached are two screenshots to show the above.

(1) My Home screen, Full size, and optimally designed to be Full Screen

(2) The same Home screen in 50% split mode, along with Google map

The 50% FCC screen is now terrible, but could be a lot better if it was simpler, and designed to be only used as a 50% FCC screen

(I tried to modify EDIT it but FCC would not allow me to change the Text sizes, when it was split !! )

With the Home button not working, I reinstalled a earlier ( "Pre-split screen version), and all is back to normal, working well state.

The Spit screen with Google map, I would use, if it was a new Specifically designed split screen, and I could create and edit it in the split mode, to be designed to something that worked and was both readable & functional.
[Android Head-Units] bajoseph04:
The purpose of the community is that you'll get help from someone. Your questions can mostly be answered by users than the developer. There's a big learning curve for FCC. I mostly test launcher on my mobile which we use more and then implement it on my head unit. A tutorial should be good but then it needs lots of time to prepare it. May be any experienced users here can make a youtube video showing the features of the launcher and how to start using it with some demos will be good for beginners and for the launcher to gain more popularity.
[Android Head-Units] Yak54:
I tried it this morning and it worked immediately. Thanks!
[Android Head-Units] SpeedFire-:
Thank you for supporting the app, man! Really appreciated.

Unfortunately I can't answer all the questions as I am more focused on app development (when I have time). Other community members can help with some of them and thanks to them for that.
[Android Head-Units] SpeedFire-:
I saw the first issue as well. This is because of some changes I had to do to make the Launcher split screen compatible.

Please try this version: FCC 3.365 v6
[Android Head-Units] mclellan83:
I think this would be very helpful to me, like I had mentioned previously I installed it probably a year ago to see if I liked it enough to purchase the full version. I haven't used the car yet to be able to try it out, I think I am also a bit nervous it run it on both head units just because I am unsure how to properly use it. I really like the look of the way I have it setup but not sure how functional it will be to me. If anyone wouldn't mind showing a rookie some of the ropes hope to have the car finished in the next couple of days. I am still very interested in finding a way to run the Ridetech app through my unit but still have not found a way to do so.
[Android Head-Units] rigattoni:
You won´t find a way, because the implemented BT-Stack is only for phone calls and some OBD. You can´t connect to to the Ridetech unit.
[Android Head-Units] Smess1210:
This version puts my Hal9k 3.365v6 px5 into a heart stopping boot loop after sleep. It has cured the home button issue that appeared on the previous version but not the minimap issue.
[Android Head-Units] SpeedFire-:
That's not good. How have you went out of boot loop (probably it was a continuous launcher restart)?

What is your issue with minimap (better show this on video)? What minimap provider is selected?
[Android Head-Units] Smess1210:
The unit goes to the Hal9k start screen immediately out of sleep, then hangs with my startup logo for a while, then restarts with the android boot page saying system not found try again after that it will boot normally albeit rather slowly....

The minimap issue I've been experiencing for some time now thru beta releases is the launcher shows the message minimap visible but it isn't until a few restarts of fcc, when it eventually does show the map it shows the same size map over each screen rather than the different sizes it used to.

Im using Google with an api & quite often when I click any of my direction widgets to launch minimap fcc crashes, I presume this is due to the Google bug mentioned above.....

I'll try to film the unit tomorrow.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

You mentioned in an earlier post, that Split screen support for FCC will be in fixed 25%, 50% and 75% split.

How does one get to the 25% or 75% split ?

If there anything in FCC that evokes the split (ie a Widget), or does one have to manually get Android to split ?

Will one be able to edit a FCC split screen (ie change text & icon size when it is displaying in it's split state)

What is the possibility that :-

(1) Screens can have the Split amount as one of their parameters, as well as the default app ?

(2) The Screen select widget can specify the app to runs, if it is a Split Screen.

This would seem to open up some great possibilities for Split & non-Split screen selection, with specified apps to run along side FCC , and make for a far simpler use Interface to take advantage of the split screen feature, a simple press of a Screen select Widget Button.

At the moment (unless convinced otherwise), I am a firm believer that Screens should be created and then designed as either a Full Screen or as a Split screen, in favor of having the same Full Screen being able to display in either Full or Split mode.

This would also greatly simplify and remove the need for FCC to "attempt" to re-scale a Full Screen to a "Split screen", with all its associated problems of scaling and changing aspect ratio
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Additional:

Can we get a possibility to be able to keep FCC in window mode? something like a switch available from Tasker?

Some OEM application are forced into full screen mode and after switching back to home screen, FCC is set to full screen too.

Other than that, I figured out that FCC restarts on Home button usage if I have activated any OEM application as FM-Radio, so the FCC Autostart option jumps in always.

...this could be related to my new unit (Klyde PX6, RK3399 with rotatable screen), which is not fully supported by FCC.
[Android Head-Units] SpeedFire-:
This doesn't look like a Launcher related issue since it wasn't loaded yet on that stage.