yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
This is what I see as well, and have asked Speedfire- in the forum about it.

He says he does not see this happening with his installation .. (or could be not exactly understanding what the users are reporting)

To me, it is now very clear in your Video, as it is in the one I posted a few posts earlier, with exactly the same concert.

I don't see that it is really that detrimental, but the settings suggest that one should be able to set FCC, so when it displays an APP, there is control as to if the Status Bar should display or not.

When you make a sharable link, you also need to set that shared link to be Readable by All.

Default is PRIVATE

, and users then have to request permission to see the Video.

I made this error as well, when I started to post Google Drive links in the forum, and got flooded with emails telling me that they cannot see my video !!
[Android Head-Units] rigattoni:
I don´t use any skin... so useless for me personally.

But interesting that the switch and the restart of FCC fixed it. I restarted FCC and the unit a couple of times today, while working on some special tasks for split screen usage. So I am more or less not able to find the real route cause for this behavior.
[Android Head-Units] ric69:
Hehehe yes I hope it is ok now... and sorry for this horrible sound...
[Android Head-Units] rigattoni:
Okay retested on my CSN2 unit which is at the moment the I am working on...

What I could see is, that it takes a second to move the main screen up.

VIDEO
[Android Head-Units] Scopesys:
[MENTION=2534110]rigattoni[/MENTION]

Maybe you can clarify the condition with the Status bar displaying at the top of Apps.

It is my understanding, from looking at the FCC "Display" settings, that it implies that one can disable the Status bar from displaying on APP screens.

I am beginning to think that I must be interpreting these settings incorrectly, as in your recent videos, and all other FCC user videos I have seen, APPs are always showing the Status bar,

So, should one be able to set the FCC display settings so that the Status bar does not appear on APP screens ? (or not) ??

Not that it is is really important to me if you can or can't - does not really make any difference to me, as long as the Status bar can be turned of when on a FCC Screen (which is currently can)
[Android Head-Units] rigattoni:
Yes, if you activate Full-Screen-Mode (Hidden status bar), deactivate the status bar in AllApps and then deactivate the Full-Screen-Mode it shows no status bar in All Apps, but in all other views as the home screen.

You need to go this way, because otherwise the All Apps setting is deactivated. ;)

Edit:

If you are working with split screen view, and you want to have the home screen visible too, you should not deactivate the status bar, because there is no way to deactivate it in split screen...
[Android Head-Units] ric69:
That's exactly right. If I have 1 app in background then FCC will not display well. If I close all apps it's ok

https://drive.google.com/file/d/1gagt-_fpW1MMkekkVFSP5Pd2cAYaip-D/view?usp=drivesdk

Btw I have Hal9k rom and there's an option to enable immersive mode but if I enable this I have no statusbar anywhere
[Android Head-Units] parisisal:
Bluetooth delay

Hi [MENTION=4292729]SpeedFire-[/MENTION], Hi All,

i have an issue with the Bluetooth on Headunit startup.

See this scenario:

1) I'm on the phone outside the car (BT phone is on but not connected)

2) Then I enter in the car and I turn on the headunit (I'm still on the phone in a call - BT phone is still not connected)

3) The Headunit boot up (I'm still on the phone - BT phone is still not connected)

4) Now FCC starts (i see the triangle picture)

5) Now the Phone connects the BT to the Headunit BT (I'm still on the phone in a call)

6) Now the phone use the BT to send and receive the call sounds : I can't hear nothing.

7) For 40/60 seconds even if the phone is in call i can't hear nothing

8) After that period (i think FCC finish to load all components) I can talk through the headunit BT

Can I delay the Headunit BT turning on ?

I'd like that the Headunit turns on the BT only when it finished to load all components.

Can FCC do this ?

Can FCC turn off the BT when the Headunit is going off ?

And Can FCC turn on the BT at the end of FCC loading process ?

I think that I can do this with tasker. But Tasker won't start automatically.

Thank you,

Salvo
[Android Head-Units] Scopesys:
:)@Speedfire-

What is FCC so busy doing during startup. ?

(1) there is quite a long delay, before the Screen becomes responsive, while widgets appear to be loading, displaying, and then often updating their display, as FCC comes out of sleep ?

During this time, the head unit is basically Unresponsive to user control.

Fair enough. (it has to load)

If It is FCC "loading/Initilizing", it would be nice if there was POP UP to indicate this, that got cleared, when FCC had finished loading, to let the user know that they can start interacting with the head Unit.

(2) Then, once the Head Unit is responsive again, there is about a 3-5 minute period, where it seems that the head Unit is very busy doing tasks (I assume FCC tasks ?), and this is apparent because any Scrolling text (Song/artist in the Player widget) is very jerky. Then after a time, it settle down to run a lot more smoothly (but never a completely smooth scroll)

Other processes, seem top be causing the Text Scroll to be jerky, and , for example, if the Volume control is moved, the Text scroll Resets to its starting position (which is not ideal)

While the Jerkyness of scrolling text, does serve as an indicator of how stable and settled down the head unit is, it would obviously look better is the scroll was smooth.

Note: Historically, it was always during this 2nd period, that FCC would seem to have a mind of it's own, and randomly switch between Players etc. (not doing that anymore ") _
[Android Head-Units] rigattoni:
[MENTION=9325785]Scopesys[/MENTION]

How many pages in FCC do you have?

I just have 3 pages and there is no delay and no delay even with my tasks working in the background.

May be this is one reason?

---------- Post added at 09:19 PM ---------- Previous post was at 09:01 PM ----------

Did not get into this situation yet, but...

BT is independent from Android and therefore not able to delay the activation, or wait until all stuff is prepared and ready to rumble.

The point with Tasker can be done with just installing an additional app from realzoulou --> https://xdaforums.com/android-auto/android-head-units/solution-start-tasker-head-unit-sleep-t4102439

If this a regular issue for you, I would use Tasker on your phone to delay the BT activation for ~ 60 sec. to get this done.
[Android Head-Units] parisisal:
Hi,

thank you for reply.

how would you use tasker on the phone? on which event would you insert the delay ?

Can you share with me your idea ?
[Android Head-Units] Scopesys:
I have about 8 pages, 5 of which are highly populated.

I'll try a fresh install with just one page, and see how that loads.

While I can understand that the 8 pages may take some time to load, after they load and the system is responsive, why does it take another 3-5 minutes before text starts to scroll significantly more smoothly than it did when the system first became responsive. ?
[Android Head-Units] rigattoni:
No problem... ;)

Will do it out of memory... so may be it needs some refinements afterwards.

New profile:

needs to have 2 trigger.

State --> Call --> any

State --> Net --> BT Connected --> activate Invert (You also can choose the car BT in Name to be able to just trigger for this unit)

That means that the profile only gets activated if you are on a call AND you are not connected to your unit. This is needed to not get cut off.

Enter Task:

Wait 1 sec or longer

Bluetooth to off

You need a second profile to get the information that Profile 1 is active.

Second Profile:

State --> Tasker --> Profile active --> Profile 1 --> Invert --> Active

Entry task:

Wait 60 sec

Bluetooth set to ON

... just as a first test version to find the right timing and may be some other things to do in there...
[Android Head-Units] rigattoni:
...this is also not remarkable visible on my side, whether in my PX5, nor the CSN2 or the new PX6.

May be a good idea to connect via ADB to the unit and call shell and then top to get the high load apps listed.

I just did it directly after wake up from sleep:

View attachment 5058147

What you can see in this screenshot is, that some other apps are more involved in using CPU and memory as FCC.

I took this shot ~17 sec. after wake up and FCC is consuming about 15% CPU usage... nothing more, beside DAB-Z takes 42% and my unit is complete reactive.
[Android Head-Units] parisisal:
Thank you.

I'm trying to create a profile with 2 conditions but i'm having problems because seems that only one condition is supported (1 condition -> multiple task)
[Android Head-Units] rigattoni:
Long click on the profile call --> add
[Android Head-Units] Scopesys:
I'm willing to try almost anything !!! never used ADB before -- could be a long weekend !!! .. Do I have to be Rooted to do this, ?? (I am not rooted)
[Android Head-Units] rigattoni:
No there is no need for root.

Unit and laptop/PC needs to be in the same WiFi network for it.

ADB needs to be installed on your laptop/PC.

ADB is available here: https://adbdriver.com/

Open CMD on your machine.

Commands:

adb connect 192.***.***.*** (needs the IP-Address of your radio)
adb shell
top

To stop top from refreshing, just press the "q" on your keyboard.

With input of exit you close the connection and the CMD closes.

If you don´t get connected to your radio right away, just use the app I added.

It just activates ADB on your radio and reboot the device afterwards.

View attachment 5058189
[Android Head-Units] jrobbom5:
Does anyone know which Google Maps API is used by the mini-maps service. There are about 15 of them. I have a google developer account and can generate the API key, I just need to know which API is used.
[Android Head-Units] rigattoni:
I use the "Distance Matrix API" which works for me.
[Android Head-Units] SpeedFire-:
Good news!I have won the appeal .. by just asking how I breached them (and providing some details how I came up to the FCC name) :)

However, I decided to change the name to a non-capitalized version: "Fcc Car Launcher" to avoid negative association with FCC and such potential problems with Play Store.
[Android Head-Units] okij:
Congratulations, that's great! :cool:

On a different note, two weeks ago I posted here that the assignment of user defined MODE actions currently are not working, but unfortunately I didn't get a response from you yet. It seems that the mode actions are not stored properly in ru.speedfire.flycontrolcenter_preferences.xml after they have been selected, as I wrote in that post. Could you please look after this and fix it or give me some feedback about this issue? :fingers-crossed:
[Android Head-Units] SpeedFire-:
Please remind me about this a little bit later. Now I need to check that the app will be correctly restored in the app store and solve some other issues.
[Android Head-Units] rigattoni:
Great news... congrats! :highfive:
[Android Head-Units] Scopesys:
How about your "FCC Starter" and "FCC Plugin" ? were they brought up, and will they also being changed to "Fcc" ?
[Android Head-Units] SpeedFire-:
No. They were not mentioned at all. I assume that someone (competitors?) reported the main app and forgot about those little apps.

However, I will change their names as well.
[Android Head-Units] reneskoda:
Hello, my SWC works well with the radio Apps, but on FCC forward and backward doesn't work. Is there a workaround?
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I see today that the "little" Apps are appearing on the Play Store as "Fcc" (lower case cc), but Google seem to be taking it's time restoring the main Fcc Launcher to the Play Store.

Frustrating for everyone...

Maybe if you have the time, you can comment on where you see "Fcc Launcher" is at the moment, and what any near future developments might be. ?

From what I can see, looking at the latest Version, Split Screen and Navradio+ integration are working well, and the Player widget is the most stable it has ever been. :)

(Not really sure about Split Screen, as I do not use it because as it is not something that is easily set on my head Unit ,(Oreo 8.0) and is not that visible on it's small display size)

Do you have plans for any new changes or advances. ?

To date, the biggest "cosmetic" issue I see, is that when a different player is selected, very often, the Artist/song Text & Artwork are not being set to defaults, so if the new player takes some time to Load, (connect to Internet etc), FCC Player widget is still displaying stale information from the previous player.

Still hoping you will be able to get around to

(a) Adding "user Defined" Artwork masks. (usable for both Circular & Non-circular Artwork)

(b) Control over density and size of the Background Shadow of Text & Controls placed on the Player Widget Artwork.

(c) Improvements to reliability of the WiFi & BlueTooth widget (often does not update or reflect the true state of these connections)
[Android Head-Units] kramttocs:
My vote is on halting any new feature development and focusing on reported issues to improve stability/eliminate errors. I still get crashes every few minutes on my Atoto S8 and my single screen is a very simple setup.
[Android Head-Units] Scopesys:
I would agree with you -- especially if it was crashing every few minutes on everybody's head Unit.

Every few minutes on YOUR head unit seems to be more the exception, so you will probably have to offer more than "it crashes every few minutes" to stand any chance of a resolution.

Are you running the latest version 3.400 v3 ?? Did any earlier version NOT crash every few minutes ?

How/when does it crash. A video would probably be most informative.

A Logcat would defiantly help anyone trying to figure out what is uniquely happening on your unit.

I feel your frustration... but with so many types of head Unit out there, some of the China ones being of questionable quality, it is not surprising that there may be issues with some specific Head Unit models. On the bright side, Fcc seems to be working very well now with most recognized as "Supported" Units.

Are there any others in the "Atoto S8 General Discussion" forum using Fcc, and having a similar crashing issues to you.

Could the crashing be caused by any ROM upgrades you may have done.

Are you able to produce a Logcat of when it crashes. ?

Is it CRASHING the head unit, or just re-starting FCC ??

Reseaching your head unit indicates a few potential Red Flags.

I purchased by Eonon Unit before discovering FCC. I was Lucky. Fcc runs very well on my 2 year old Unit.

I dread the day if I ever need to update my head unit, and find the newer unit is not yet so well supported by FCC.
[Android Head-Units] kramttocs:
Hey Scopesys,

I mentioned it here. Unfortunately I am unable to provide a logcat - I explored all of the options I am aware of.

With an app that is as customizable as this, yes it's not surprising that one persons setup will exhibit issues that others will not see. My whole point is that there are a number of things reported in this thread where behavior isn't working as expected. Be that errors or sporadic behavior.

You asked what 'new changes' might be coming and I am just saying that to me, getting the current offering more robust would be beneficial. Things like the auto-dimming granularity and the auto-volume (speed) are absolutely great ideas but they don't appear to work on my headunit. Stuff like that is also what I am referring to. If it can be made to work that would be great but if not maybe hide it from the menu. I am just looking at this from the viewpoint of someone not technical and what might cause them frustration.

You are spot on that there are a lot of different units out there and they can vary a lot in regards to hardware. Both a blessing and a curse when trying to make software like Fcc.

It's been a couple days since I've been in the vehicle so before I go further into my specific issue and do the video route (good idea) I'll ensure I have the latest.

Without the ability to root or connect via adb I am afraid the video is probably the best option if sending the generic android crash reports doesn't provide anything useful.
[Android Head-Units] Scopesys:
I am also trying to figure out how to ADB into my unit, in the hope I can help by providing Logcat reports. (when things don't seem to go as expected)

So while I currently provide Logcats, I am getting plenty of practice making "Screen capture Videos" to show my perceived issues.

With help from [MENTION=2534110]rigattoni[/MENTION], I am now able to run ADB on my laptop, and connect to my Phone. (step 1 .. adb is working on the laptop)

Next step is to ADB into my car's Eonon head Unit, which is currently proving a PITA, namely because it is so HOT these days sitting in the car, without the engine & A/C running, and my head unit is not being recognized via USB, with "ADB Devices" :(

Also, I am still not sure how much of a useful Logcat I can get (specifically for FCC) via ADB, without actually being rooted. ?

Getting this is work is more a project than a necessity, as currently, my head unit seems to be working pretty well, even with navradio+ (and my OEM radio still enabled)
[Android Head-Units] kramttocs:
No kidding!

Sounds like we are in the same boat. The usb ports on the Atoto don't allow being read FROM so the computer isn't able to detect it. Wifi ADB is an option but you have to connect to the computer at least once so that's a no go. I've emailed Atoto about this but so far they have said they don't plan to allow it.

If this is something common with headunits I wonder if it's going to fall more on the app developer to implement their own logging?
[Android Head-Units] bajoseph04:
[MENTION=1633144]speedfire[/MENTION] if at all you plan to fix some bugs, please have this in your list. Thanks
[Android Head-Units] rigattoni:
This is quite easy... ;)

If you are connected to your phone and you put in:

ADB logcat -d

In this case the CMD stores the complete buffer of logcat in your window.

Each run of logcat -d starts from the beginning of the buffer.

If you use the command:

adb logcat -d >log.txt

the log is completely stored in a file named log.txt in the ADB folder.

Give it a try, it works on unrooted devices. ;)
[Android Head-Units] SpeedFire-:
Finally, the app is restored in the Play Store - LINK

If someone wants to rate it to support its return it would be nice!
[Android Head-Units] Scopesys:
Looking good .. well done..

---------- Post added at 15:35 ---------- Previous post was at 15:31 ----------

OK, got that so far, and it produces a LOG file on the SD Card. I then have to copy it back to the PC.

But this is a log of EVERYTHING running on the Unit - can just FCC be specified, or does one need to edit the logcat afterwards, to remove all but FCC information ?
[Android Head-Units] rigattoni:
It mostly make sense to have the complete dump to see what happens before something got wrong.

So editing or reducing to one single app is not really helpful... but you can if you really want. Here is a complete list of possible things to do with Logcat.

---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------

Done! Did it long ago, but edited my comment.
[Android Head-Units] Scopesys:
Thanks... will try again tomorrow morning when it is cooler, and I do not have a Flat battery !!!

Note to self: If you are going to sit in the car, playing with Fcc for any length of time, connect the battery charger, or risk the car not being able to start when you need it !!
[Android Head-Units] rigattoni:
That´s the reason I never do something like that in the car. I grab the unit out of my car and do stuff like that on my desk.... ;) If at winter time or summer, it´s always more comfortable....and yes, I am totally :silly:
[Android Head-Units] Scopesys:
I am even more :silly: ---- This evening I came up with this as a "solution"
[Android Head-Units] jrobbom5:
I just did a search on the play store, and I can't see the launcher. I can see Fcc Starter and Fcc Plugin, but not the launcher.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

FCC Version 3.410 (latest )

Updated to latest version this morning, and then found the "FCC Restart APP" was not working.

All it did was to return to the Home Screen.

Re-Booted -- No difference.

So I created a new button for the FCC Restart app, and that worked. The Old button continued not to work.

So , I deleted the old button, but this does raise a question that has always concerned me, especially with FCC widgets.

If I have a Screen with Apps and Widgets on it, and an update of FCC has modified one of those widgets (or Apps, as may be the case with FCC Restart), does that existing Screen widget update as well, or is it still the old widget/App, and in order to get the latest version, one has to delete and place the current version of the widget/app on the screen.

The experience with the FCC Restart App would tend to support this theory.

In which case, how does one know if a existing Screen Widget.app has been updated, and one should re-create it, so one has the latest version.

My concern is tat having created most of my pages over the past 2 years, are some of my Widgets the old version when I put them on the page, or do they get updated automatically, with a new FCC version.

or, was this a Unique case, that just applied to the FCC Restart App ??
[Android Head-Units] SpeedFire-:
This is probably because of the renaming of all "FCC" into "Fcc". Some of them were in the Java class names.
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

Thanks... so how does one find out which ones are not working, without testing every one on every screen, and editing them. (Thank you Google !!)

FYI: The FCC Re-Boot app continues to work,
[Android Head-Units] davemazo:
Is it possible with this Launcher to have a screen/page (other than the main home screen) where I can place icons of my most commonly called contacts. My Joying unit does not allow me to make calls using Google voice so it would be simpler to have a screen just for contacts that I can touch to make an instant call.
[Android Head-Units] Scopesys:
YES .. ( why not ? ) That is also what I have done for a few of my frequently used contacts. (You can also make the "Contact Call Button" a Photo of the contact if you want.)
[Android Head-Units] davemazo:
Contacts

Excellent thanks. I only ask because my current launcher (and various others) didn't seem to allow more than the one page (home screen)
[Android Head-Units] tonimontoia:
before I had the widget restart the launcher, and restart the device, now restart the launcher is no longer as widget disappeared
[Android Head-Units] segu45:
I have android 10 installed, for testing purposes and at the moment with fcc (Google's 3410) you cannot make backups or restore them. I think it's because of the new partitions, because now I can't see the main partition with root Explorer either. when you have time if you can, look at this problem.

Enviado desde mi ONEPLUS A5010 mediante Tapatalk
[Android Head-Units] davemazo:
I have just upgraded to premium and despite spending 30 minutes or more I just can't find any way to add another blank page to add favourite contact icons as per my question above. Also I can't see any difference between the premium and free versions
[Android Head-Units] tonimontoia:
Android 10 ROM hal9k?
[Android Head-Units] segu45:
No, android 10 HTC original from (24/06/2020). Halk9 I think he still working in it. We matter must wait a little bit for him ROM.

Enviado desde mi ONEPLUS A5010 mediante Tapatalk