yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] marcus82:
hi all, I'm newbie on this topic and I'm coming from other launcher.

I'm looking for a launcher without bis issues and with a stable integration with my head unit (tesla style SC9853); I want to try to use FCC to solve some issues on oem launcher like wrong sizing of app like alexa and maps.

First question: is it possibile to have topbar and bottom bar fixed on this launcher or I have to install other custom bars?
[Android Head-Units] Scopesys:
Thanks --- good news "_
[Android Head-Units] Scopesys:
So, having just completed a Navradio+ Logo File set for my local USA State (Maryland), I loaded up the Radio with the Logos/Artworks, and this is the "Radio Experience" I get.

I am really happy with it , the Integration, and the Experience when running NavRadio+ in the FCC Player WIdgte(s)

Here is a short Video, showing how it is working for me ...

VIDEO:

NavRadio+ running full screen, and also running in FCC Player Widget
[Android Head-Units] kramttocs:
Nice! That looks great. Thanks a lot for the video.
[Android Head-Units] marcus82:
wow, amazing skins!

a question, the 2 blue bars can be fixed ?
[Android Head-Units] Scopesys:
[MENTION=6636385]marcus82[/MENTION]

I saw you asked that in a previous post., but nobody answered you.

I waited till I had posted this video, showing what I think you were wanting, so I cold better explain how it can be done.

The BACKGROUND "skin can be fixed, and customized by you. It's just a background image file,

I think my background is an Edited version of one of the ones that came with FCC.

The Grid pattern, for where Widgets Lock into, can also be customized ( I don't know how easily, never done it), to match your customized background SKIN.

Or you can specify the Rows, columns in the grid you want.. again, never tried that.

I used an existing Grid Pattern, and just edited one of the supplied skins, to achieve what I wanted.

Getting the same Top or Bottom "WIDGETS" on multiple screens has to be done done manually for each screen that you want to have the same "TOP bar" etc

In my case, I have a number of the screens, displaying the same Player Widgets "Song . Artist" information at the TOP, on Multiple screens.

So they can be exactly the same, or slightly different on each screen.. whatever you want, so it is more configurable & powerful, than if the same Top menu was automatically able to be specified for Every screen.

IT would be nice is there was a way to COPY/Paste a whole screen, or Make a new screen that was a copy of an existing screen. (Clone a Screen) ;)

Then one could use an existing screen as a template, copy it, and then delete what you do not want, leaving what you do want ie the TOP part.

(Maybe there is, and I have not discovered it yet ??)

FCC is so highly configurable, that you can do almost anything you can imagine with it .. the variations and options are endless, so everyone up with a launcher that is very personalized, and customized to exactly what they want.

If there is anything you cannot do, and you can convince SpeedFire- it is a good idea, and he sees it that way, there is a good chance that he will add it.

This is why I cannot see myself ever switching to another Launcher, and if I ever update my head unit, the #1 critical criteria with a new unit, would be "Is it supported by FCC" ?
[Android Head-Units] marcus82:
ok, I got it! another questions: yesterday I was not ale to have maps indications in the widget but google maps was running
[Android Head-Units] Scopesys:
FCC also has its own MAP system, that is re-sizable on the launcher's screen(s)

You saw it briefly in the Video, where I selected page that was able to display this FCC Mini-Map on most of the screen but still allowed the TOP BAR, with the Artist/song display from the Player widget,

Personally, I do not use it that often... typically I use Google map full screen, but I think to get the map on any given screen page, you need to add the MAP widget to that page.

(Been a long time since I have done that)

Edit the widget to set it's properties
[Android Head-Units] marcus82:
ok, so the indications are only for minimap... too bad. I was trying to emulate the skin of carwebguru launcher.. without the issues :silly:
[Android Head-Units] Scopesys:
I tried carwebguru when I was looking for a launcher .. decided on FCC, and have never regretted the decision.

My advice .. I see so many come onto this forum, wanting FCC to do things that other Launcher do, because that is what they are use to - and if what your old Launcher does, is what you want, why are they looking to change. ?

Rather than wanting FCC to look like your old launcher, and trying to force it to be, rather, embrace the features that are different in FCC, and use them to give you a better experience than your old Launcher.
[Android Head-Units] okij:
Also from me a "thank you" for your video. :)

But don't you have any of the NavRadio+ integration issues that I've reported here on your unit?

In your video I cannot see the button presses, so I don't know if you use the FCC player widget buttons to change between different players, which leads to those reported issues on my unit.

Because of those issues (plus two DAB-Z integration issues which were caused by the changes that [MENTION=4292729]SpeedFire-[/MENTION] made for the NavRadio+ ingegration) I'm not happy with the NavRadio+ integration yet. For now I reverted to FCC 3.365 v25 in which at least DAB-Z was still working fine.

If you don't experience those issues, which kind of unit do you have? (Mine is a PX5 MTCE Android 9 unit, so a quite common one.) I'm wondering if maybe those issues don't exist on all platforms.
[Android Head-Units] marcus82:
I've only tried cwg for a coouple of days, nothing else. :o I'm still understand which one to use.

My vertical head unit has a systemUi.apk that add topbar, bottombar and statusbar with notifications; well, I'm trying to customize these bars with apktools but itìs so difficult and moreover some buttons like apps stop to work with different launchers. Cause of this, I'm thinking to remove tha bars and use only a custom launcher.
[Android Head-Units] Scopesys:
Another quick (But long !! 20 minutes -- did not seem that long when I was recording it !!) Video, showing how the Initial parameters of a newly created widget, no longer has the same parameters as the previously edited widget.

This was a nice feature, that

seemed to get broken when Split Screen was added

.

Yes [MENTION=375322]koji[/MENTION] - I do see the same issues as you with Navradio+ -- as shown in this new Video

VIDEO
[Android Head-Units] Scopesys:
Yet another Video, this one showing when FCC is running Navradio+ in a Player widgets, when one opens navRadio+ full screen (by touching the Artwork), then to return to FCC, the Home Button works fine, but the back button, while taking you back to FCC, seems to have KILLED ? Navradio+, in that it no longer plays , and does not responds to Player Widget controls, like next/previous station.

IF we try this other players, like Blackplayer MP3 player, both HOME & BACK Button take you back to FCC with the Player still running.

So currently, "work around rule" is to Remember NEVER to exit NavRadio+ with the back Button, to get back to FCC. Always use the HOME button, (Even if HOME is not where you want to return to FCC !!)

Maybe this is what others are seeing, and then thinking the issue is 100% Navradio+ ???

Note : In the Video, NavRadio +, when in Full Screen, is working fine, and PLAYING, UP TO THE POINT WHERE THE

BACK BUTTON

IS PRESSED TO RETURN TO FCC

VIDEO

: return to FCC from navradio+ by HOME vs BACK Buttons
[Android Head-Units] emerax:
for the installation on an ATOTO which setting must be set?! Tablet / Phone?

Inviato dal mio Redmi Note 8T utilizzando Tapatalk
[Android Head-Units] KoTiX2:
Back button in NavRadio close the application.

It can be set to click it once or twice but it always close it.

To go back to the launcher you have to press home.

This is exactly the same way that the original MTC radio app work too.

It has to be remembered of course but people should already knew it from the original app.

The main issue right now with the FCC/NavRadio coexistence is that NavRadio cannot be started in background and I still have to look at it.
[Android Head-Units] Scopesys:
[MENTION=678352]koti[/MENTION]

Thanks for jumping in with the explanation :)

Ohhh I did not realize that was an intentionally designed feature of NavRadio+ :svetius:

Also, I had not realized that the OEM Radio App, also closes, when the back Button is pressed ... probably because I had seldom used the Radio, until recently, when my interest in FM Radio was awoken by NavRadio+.

To me, that is "Strange Behavior", because in pressing the back Button, I was expecting to go BACK, not close the Radio.

But because that is the way the OEM radio Apps work, I can appreciate why you made Navradio+ act in the same "ODD WAY" !!

An option to make the back Button in navradio+ act as a conventional "Back Button", and not close the app, would be nice, Just because the OEM radio has this strange behavior, does not really mean that all Radio Apps should copy the OEM's Radio in this respect.

So, I will make the change in NavRadio+ from "Press Once" (The Default) to "Press Twice", so, as a reminder, if I do forget and press "Back" , I will get the POP UP to Press Again, and that should remind me to Press HOME instead. ;)

Another Problem solved :)
[Android Head-Units] KoTiX2:
I can add this option too ;)

:good:
[Android Head-Units] Scopesys:
[MENTION=678352]koti[/MENTION]2

Thanks you .. That's Great !!!

Navradio+ has many more features and functions that my OEM radio has, but one function that the OEM radio has, that t navradio+ currently does not, is to be able to select stations by Station Type (ie news, POP, Classical etc) Have you considered implementing such a functionality into navradio+

I am not sure how useful such a function really is, but my OEM radio can scan by Station Type, while keeping it's presets intact.
[Android Head-Units] SpeedFire-:
Hi guys.

I had some busy time (and still have) at my main work. So currently I don't have too much time for the launcher.

What I'm working on:

1) Adding support for PTY in NavRadio+ (working together with [MENTION=2734955]KoTiX2[/MENTION]).

2) I heard about DAB-Z issue but I currently can't reproduce it. The app send the right intent in my case (to start DAB-Z in background).

3) Added some initial support for Android 11 (API 30).

4) Probably Android 4.4 support will be dropped (discontinued) in the near future because of several reasons:

- Google dropped support for Android 4.4.

- Some libraries which are used by the FCC Launcher discontinued Android 4.4 support so I currently need to stick with the "old" versions of such libraries. This obviously not a good thing because we don't have the latest bug fixes and features.

- I plan to switch to the vector graphics entirely. This will result in lower APK size (which also good for app performance). Currently raster (.png) files are automatically generated in addition to the vector (.svg/xml) files to make it backward compatible with Android 4.4. But there is another issue here - vector Gradients are supported only starting API 24 (Android 7). So there is another difficulty here.
[Android Head-Units] okij:
Hey [MENTION=4292729]SpeedFire-[/MENTION], it's great to see you here on your FCC thread again and get some direct infos from you! :victory::cool:

We already assumed that you are busy with other things in life, so it's good to have this confirmed now. You have our full understanding for this.

I would like to ask [MENTION=7838245]realzoulou[/MENTION] to also have a further look into this and give you some feedback about what's wrong and how it can be fixed. Please help each other with this. :fingers-crossed:

Maybe the following informations can help you to fix this issue. If I got it right, [MENTION=4292729]SpeedFire-[/MENTION] started to use a different launch intent for controlling media players in FCC 3.365 v27, please see here:

So it is likely that either the boolean extra 'remain_background' isn't sent anymore by FCC or that the boolean extra 'remain_background' isn't processed yet by DAB-Z when it gets accessed by the changed MediaSession interface.

---

[MENTION=2734955]KoTiX2[/MENTION]: Maybe you should also add a boolean extra 'remain_background' like [MENTION=7838245]realzoulou[/MENTION] did in DAB-Z about half a year ago, so that [MENTION=4292729]SpeedFire-[/MENTION] can use it when launching NavRadio+:
[Android Head-Units] realzoulou:
Back button also closes DAB-Z (when in main screen of course). This is the default behavior of every app in Android.
[MENTION=4916555]okij[/MENTION] My previous tests with FCC 3.370 and DAB-Z (1.8.88) seemed to support your statement that something has broken. Just now I tested again and I found it working well several attempts in a row. So I guess it might be specific to your setup and configuration. If you supply a system-wide logcat, we could have a look and see what is the actual root cause.
[Android Head-Units] rigattoni:
I have seen this in the last few builds too, but not always. It happens from time to time and is not really reproducible.

It doesn´t bother me because I use Tasker a lot.

All player have a timeout of 5 seconds if I don´t touch the screen when the app is in foreground. As long as I am working on the screen like switching stations, playing around in the settings or what ever else, the timeout starts again and nothing happens.

Then the player is sent to background and the previous app comes up again. So if DAB-Z is opened by Tasker I don´t have to do anything to get may be the navigation or the launcher back in foreground.
[Android Head-Units] Roerbakeitje:
Ons little thing found so var in the last beta. The widgets are quite slow on a cold start. Also the music widget gives the information in about 2 3 min
[Android Head-Units] HarryBk:
[MENTION=5394055]Prometheus_au[/MENTION] it works fine on my Intel Sofia 3GR head unit; in fact it is by far the best launcher I have used so far on it.
[Android Head-Units] ftsur:
Hi There!

I have a BMW Android head unit from AVIN. Their stock launcher allows me to use my iDRIVE knob to move between icons and to launch an application. Is this something you can do with FCC? I've tried but it doesn't seem to work. If not, is there someway to integrate it? I'm happy to be a beta tester.

Thanks!
[Android Head-Units] SpeedFire-:
Hi!

If your device is rooted you can try to record a LogCat log (please see instructions in the first post of this thread) while rotating your knob. We will see if it send any broadcast to the android system which can be intercepted by the Launcher or not.
[Android Head-Units] pa.ko:
[MENTION=4292729]SpeedFire-[/MENTION]

From two last betas I experienced problem with Autobrightness. All threshold values for e.g. Sunset +/- , are set to very low values 1, 2 and 3. Even if I change them manually, after launcher restart (reboot) they are reset to 1, 2, 3.

BTW It is really pleasure to see how this great launcher is getting better and better. I had no much time to contribute here but I appreciate all work done by you and everyone who helped you in testing and debugging as well as sharing great ideas on improvement. Good work indeed.
[Android Head-Units] davidbemenderfer:
One thought is to support a USB IO board. This is what I've used previously on oDroid: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G135390529643. My thought is that you can connect them to a 30 A motor control (https://www.cytron.io/c-93-dc-motor-driver/p-md30c) for motor driven accessories. For switched accessories, you could use a relay (https://www.ebay.com/itm/3-3V-5V-30...aspberry-Pi-ESP8266-Optocoupler-/272565679171). Finally, you can interface to a Vintage Air auto HVAC system (https://www.youtube.com/watch?v=g7APiOik4IQ). Maybe it's possible to support multiple USB IO boards for futher automation.

I was thinking that I would control my door locks, windows, radio, HVAC initially. Might be fun to add other power accessories too.

Any thoughts?
[Android Head-Units] derschnelle:
Hey guys quick question as I didn't find any information by searching this thread:

The brightness widget doesn't work for me on my Sofia - unit. Is this a known problem, because Sofia units aren't officially supported?
[Android Head-Units] Roerbakeitje:
Yes lts a know problem in the last two beta,s

I hope speedfire read it.
[Android Head-Units] Petrovych:
Your reports, guys, without logs are not helpful, because there are no beta testers with Intel Sofia HU.

Отправлено с моего SM-G950U1 через Tapatalk
[Android Head-Units] derschnelle:
OK, no problem. You're right, I just wanted to make sure whether this is a known problem or just me being stupid ;).
[Android Head-Units] SpeedFire-:
Hi, guys!

I didn't have much time to work on the beta in the past couple of days. But I just uploaded a version with possible quick fixes.

Please respond if any bugs still there.

Regarding Sofia, can anyone send me all system apk-s, it will help to add support (and I also need a list of features which do not work properly on Sofia devices).
[Android Head-Units] SpeedFire-:
I don't see the last piece here - an interface (both hardware and software) between Android (your head unit) and Arduino. As far as I can tell they are completely separate now in this configuration
[Android Head-Units] Roerbakeitje:
Know you have not muts time. Maybe an idea to have a music visualization widget ? Please think about it :silly:
[Android Head-Units] derschnelle:
I would like to help you with the Sofia units.

Which system-apks do I have to get? Do I just go under system/apps and collect the apks?
[Android Head-Units] Petrovych:
You can use this live wallpaper.

---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------

And priv-app if you have such one.
[Android Head-Units] SpeedFire-:
Yes, this is the most simple way.

And also please see the /data/priv/ folder for some apk-s which can be related to the system/music/bluetooth etc.

Probably something with Sofia name or MTC or Rockchip.
[Android Head-Units] derschnelle:
OK, I'll have a look this afternoon.

One more question from my side:

I use some of the obd-widgets, which come with die launcher. When I get into my car and the unit comes out of the sleep, I have to double-click a widget to disable and re-enable it. Otherwise the widget won't reconnect or update.

Is this a normal behavior? Does anyone else experience something like this?
[Android Head-Units] davidbemenderfer:
Forgive me if I'm ignorant because I'm a .net developer trying to learn the Android ecosystem. I think that bridging between the headset and adruino adds unnecessary overhead. If the usb can be accessed from the head unit then maybe the gpio can be accessed directly with android. See the section "Example host software source code for Android" at https://wiki.odroid.com/accessory/add-on_boards/usbioboard. Do you think that this can be accomplished?
[Android Head-Units] SpeedFire-:
Now I see it. Thanks. If that test Android app works with your device there are good chances that I can integrate it into the Launcher (but this will require a lot of testing from you).
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION].

Thanks for the apps button . Auto resolution I did not test . It's dark here and by default it was dark.

Tomorrow I will make a LOG of a cold start . Than mabe you can see what happen with the player when start fcc launcher .

In short. It seems that the player don't grab the title and logo and player at start. When a new song is playing than its ok again.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I am not sure I appreciate the full implications of this.

Some time ago, you introduced the Option to select Vector (Skins)

I tried this, and found that the Vector image screens were "Quantized", which did not look good, so I went back to non-vector Skins.

If you are going to switch to VECTOR Graphics, what will be the effect on things like Player Artwork, currently probably saved as .png. Are these going to get VECTORIZED before being displayed, and if so, can we expect to see the images being degraded.

I took a Rainbow Gradient .png image, and converted it to a Vector file. It looks Horrible.

When you go to VECTOR images, is this what we are going to see in FCC, when we try to display Gradient .png files ??

IMAGE:

PNG & Vector Rainbow Gradients

Note: Even the current "Vector Skin" mode has the background Skin with "Quantized" gradients.

Is this how it is going to be going forward with 100% Vector Screens ??
[Android Head-Units] kramttocs:
I chose Allwinner and then switched to atoto in the settings after. The option isn't present in the wizard.
[Android Head-Units] okij:
For media players IMHO it's better if they don't necessarily close when the user hits the back button. For example, Google's own Play Music app keeps playing in background when the user hits the back button. So it would be great if you too could add an option to close DAB-Z after one or after two presses of the back button or if it should keep playing in background.

I can reproduce this behaviour every time, so I took the requested log cat for you (please see attachment).

My tests are made with DAB-Z 1.8.88 and FCC 3.365 v25 (for comparison) and FCC 3.370 (where the starting of DAB-Z in background fails).

These are the tests that I made, including time stamp:

16:54 still using FCC 3.365 v25 which is working fine

16:54 changed back and forth three times between DAB-Z und GoneMAD Music Player with the FCC Player widget

result: DAB-Z always starts playing correctly in background

16:55 made a short phone call to my voice box

result: after ending the call, DAB-Z resumes playback correctly in background

16:56 installed FCC 3.370 again

16:57 changed back and forth three times between DAB-Z und GoneMAD Music Player with the FCC Player widget

result: DAB-Z correctly starts playing again, but DAB-Z screen always gets into foreground

16:58 made a short phone call to my voice box

result: after ending the call, DAB-Z resumes playback, but DAB-Z screen gets into foreground
[Android Head-Units] realzoulou:
I see the difference in the log and I know why DAB-Z comes to foreground now. I will adopt in the next release.
[Android Head-Units] okij:
That's great! :highfive: I'm waiting for your next release then.

Since [MENTION=2734955]KoTiX2[/MENTION] tries to implement a way to keep NavRadio+ in background when being lauched, might I ask you to give him some infos about how you achieved this in DAB-Z?
[Android Head-Units] SpeedFire-:
Here is a new beta FCC 3.370 v5:

- NavRadio+ PTY integration is added (Radio station type)

- For Android 5.1 - Android 7.0 all skins are in raster format now (no vector skins)

- For Android 7+ you can choose if you want to use vector skins or raster skins (vector skins are enabled by default) - checkbox in "FCC Settings - Display - Advanced - Use vector skins" works now (finally). Vector skins consume less memory.

- Android 4.4 is not supported anymore.

- Android 11 (API 30) support is added.

- App size is reduced