yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ab1702:
What software, rom, hardware etc are you using and any other settings that may be relevant? do you have dab-z whitelisted or anything like that?
[Android Head-Units] okij:
My hardware is a PX5 MTCE 4/64GB head unit, MCU version is MTCE_MX2_V3.37_1, ROM is Hal9k Android 9, DAB-Z is whitelisted, FCC is not whitelisted.

But maybe your issue has already been solved in FCC Launcher 3.349, the changelog says "Player autostart on boot fix". :fingers-crossed:

[MENTION=4292729]SpeedFire-[/MENTION]: Thanks for the 3.349 update, I will try it tomorrow. :) Did you by chance already have a look at the LogCat log that I posted here yesterday and did you get some insights in what makes FCC not start properly?
[Android Head-Units] Scopesys:
Switching between players is still randomly bringing up past artwork and text from previous player, or even the one before last. !!!

FCC normally corrects this to display the correct artwork & text, and thereafter, on song changes, all updates as expected.

So it's only has an issue when player is 1st selected, and apart from testing, one does not normally keep switching players multiple times a minute, so while not correct, it is (to me) acceptable, especially when there are higher priority issues to be fixed.

[MENTION=4292729]SpeedFire-[/MENTION] -- Thanks for all the hard work getting it to work this well ....
[Android Head-Units] jun81:
The file is there, will look into that function!

Definitely gonna try the third option and give you logs regarding that! Hope we can get further with this!

if option 3 does not work, will it be feasible to have a toggle between option 1 and option 2 in settings?

I got problem dragging it to delete icon because when i press and hold to drag, it actually went into the page setup instead, where we add widgets.

When i manage to select the widget, the selection box highlighting the memory widget is kinda out of alignment. however even when i manage to select the widget, the delete option does not appear and whatever i do goes to the page setup instead.

Lastly another odd occurrence, and app drawer icon appeared within the clock widget and no way to trigger it or delete it.

I have to delete the existing clock widget and insert a new one.

Thank you for the great work! really enjoy using the app!

will try to post a log for the experimental option asap!
[Android Head-Units] SpeedFire-:
Ok, I've decided to upload this beta to market.

Let me know if it is BAD :)

- [experimental] Auto-volume change + manual volume change should work together

- [experimental] Trying to prohibit Rockchip's system to autostart last app on boot.

- RAM widget fix
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

2.428

-changing manually the volume still 'jump' to that old local value.

- seems to be working will continue to test

have attached log for manual volume change
[Android Head-Units] SpeedFire-:
Thank you for the log. It helped a lot.

I hope this beta will work:

fcclauncher-beta-2.429
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

thank you for the quick updates!

2.429

fcc's last player autostart - enable

last player - FM Radio

FM Radio does not autostart

-test at low speed, does not seems to be working

-log attached
[Android Head-Units] SpeedFire-:
Thank you for your tests!

It seems that you have done some other actions as compared to the previous log?

I would suggest the following test:

1. Go above the first speed level so the volume is automatically increased (please set these values to something like 20 kph for safety reasons and +3 or higher for better tests).

2. Manually adjust volume

3. See what happens and send a log
[Android Head-Units] Roerbakeitje:
I .m like to see a manually volume button . Simple 1 widget volume +

1 widget Volume -

I can not used to it to the swipe volume
[Android Head-Units] jun81:
log attached
[Android Head-Units] SpeedFire-:
Thank you!

Please check this: fcclauncher-beta-2.430
[Android Head-Units] SpeedFire-:
Here is a new beta which will be also published to the market:

- [New] Volume widget

- FM radio start fix (hopefully)

- Auto + manual volume adjustment fix (hopefully)

- Auto-brightness fix for FlyAudio
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION] thanks good Job :good:
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

Thank you for the update!

Sorry cannot test as out of town will do it as soon as I get back
[Android Head-Units] hipkid:
[MENTION=4292729]SpeedFire-[/MENTION], Are you planning to add some fancy analog / mixed (Analog/Digital) speedometers widget? :)
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

Request: rounded borders in widget and rounded buttons media player .

Like the image . ( don't know how to tell it correctly)

Mabe a weather widget . I know there are some open source for that .
[Android Head-Units] Roerbakeitje:
Can someone confirm this little issue. When push home button from a app . I have sometimes black screen and must wait a sec of 20 before fcc is back on my screen .

Hope I.m alone at this.

And a little thing at the volume widget. I can not set the hight of the widget. Wight is ok.
[Android Head-Units] weevil_:
Two big missing features for me are the ability to swap the left and right panels (for right hand drive cars) and lack of support for the DAB+ radio app.
[Android Head-Units] jun81:
2.431

restore settings:

-after restore, widgets appeared empty, drag to settings does not work. need to be deleted and reinserted.

auto + manual volume adjustment

- still testing

-initial log attached
[Android Head-Units] SpeedFire-:
Please send me a link to this app.
[Android Head-Units] SpeedFire-:
Sure. Our current plan is:

1. Defeat all bugs for all the functions introduced in beta.

2. Release this version

3. Then we will focus on design part in the new betas.

So please report about any bugs which still exist.
[Android Head-Units] weevil_:
This is the modded version of the standard app.

https://xdaforums.com/android-auto/...b-app-realzoulous-modded-version-com-t3609608
[Android Head-Units] SpeedFire-:
I saw your video. Thanks! But I wasn't able to reproduce it on my device. I agree that it doesn't look like a big issue (at least for now).
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Agreed ... maybe at some time in the future the cause of this may become more apparent, and a fix may be more obvious.

One thing I forgot to mention, -- in recent releases (last 1 or 2), the head unit FM Radio often continues to play, after another player has been selected after the FM Radio is running ... and then TWO audios are heard playing, until one plays about with the Player selection again. Again, this does not happen EVERY time one switches from the FM radio to another player.

I believe you have a Px5 "test" head unit ? Was it that Hardware that you were not able to reproduce it on, or was it the emulator ?

I am thinking a RACE condition on the faster hardware unit, that may not be present on the slower emulator.

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

BTW: Any thoughts on the idea of "USER" files for some widget options .. ie user json file(s) for MiniMap, user Player Widget mask etc etc

see Ref: My Original POST
[Android Head-Units] okij:
I had this issue also yesterday.
[Android Head-Units] ric69:
Hello

I have this problem randomly too on px30. And if there is more than 2 skins , music or radio widget is only available on the first one. (Overs are empty)

Just suggestion now : delete "xposed not needed" page on 1st config (not needed anymore)

Restart unit fcc button is not working here.

Thank you
[Android Head-Units] Th0m4s88:
Autostarting DAB Z still isn't working for me with the newest version. It's not a problem with DAB Z because if I start it by hand right when FCC is finished it works without any problem. My headunit is PX5 mtce version from dasaita and I had the hal9k Android 8 mod running but to confirm it wasn't the Android making problems I also tried the latest Android 8 from Dasaita today and autostart still won't work.

It's really like FCC doesn't know DAB Z is a music player.
[Android Head-Units] realzoulou:
To all with problems autostarting DAB-Z that have ROOTED units:

You could use DAB-Z to create a system-wide logcat after FCC could not autostart DAB-Z and send this to yourself via email. Then attach the zip file to your post here. SpeedFire and I can find out then what is wrong.

DAB-Z is not a normal Music Player due to its USB dependency. Much more complex than a regular USB mass storage device.
[Android Head-Units] Scopesys:
Thanks -- Good to hear it is not just me :D
[Android Head-Units] ntldr:
Reboot button doesn't work anymore for me either. My unit is a Dasaita PX6. It used to work in an earlier version.

I also am having issues with the "Mode" widget. Sometimes it disappears. The widget is placed on the lower right section of the skin.

---------- Post added at 07:59 AM ---------- Previous post was at 07:41 AM ----------

I experienced the same issue the other day. The workaround was to use the "Mode" button.
[Android Head-Units] ric69:
"Mode" button has the same issue with mixed sound radio and player together. If it help...

Not sure it's possible but if FCC launcher could have task changer like Samsung good lock app, it would be awesome :fingers-crossed: just dreaming but who knows
[Android Head-Units] Super_paulie:
What does "Mode" button actually do? Cheers
[Android Head-Units] SpeedFire-:
FCC beta 3.350:

- Custom compass widget style
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION] Big Thank You -- that is fantastic :)

I opted for a more simplified background, with a pointer than ran around the outside of the circle.

For me, with the head unit located where it is, this makes it easier to read with a quick glance.

Attached is what it looks like on a page, along with the two .png Graphic files, if anyone whats them.

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

---------------------
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION] Would you please add the FM radio for nearly all CSN2 units as player?

It´s called by

com.my.radio.RadioActivity
[Android Head-Units] SpeedFire-:
FM Radio cannot be added as a separate player. The only option is to "integrate" it. Is it a separate apk or a part of some other apk? Can you attach it?

What do you expect by "adding it as a player" - be able to open it without ability to control it from widget (this is what is only possible without full integration)?
[Android Head-Units] rigattoni:
Yeah sorry... Would be nice to get the radio integrated as other FM radio apk´s too. To control it by widget.

The radio seems to be part of the CarUI.apk, see attached file.
[Android Head-Units] EJOK2:
Minimap question

Perhaps someone can help me with this one?

I use FCC Minimap with offline maps and it works just fine. The Streetname widget, however does not update/refresh.

Should this work or will the Streetname widget not work with offline maps?

Regards,

Erik

Great app. Thx for all your great work.
[Android Head-Units] SpeedFire-:
I've reviewed this apk. Integration is possible but is difficult enough. I don't think I can do it without having an actual test device. So there will be no quick solution for your platform, sorry.
[Android Head-Units] SpeedFire-:
Street name widget needs an Internet connection.
[Android Head-Units] rigattoni:
Too bad.... :crying:

If you need someone to test intermediates. I would be able to provide logs.
[Android Head-Units] tonimontoia:
hello friend, can you send me this compass configuration maybe a photo as you set it thanks
[Android Head-Units] Scopesys:
The post contains the two .png files you need to put into FCC.

Just download them, and load them into FCC when you select CUSTOM for the Compass.

see Post with Compass image files
[Android Head-Units] SpeedFire-:
This is an attempt to check if integration is possible:

FCC 3.350_csn

You need to start the "app" "FCC_RadioTest" and check if buttons work or not.
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION] ,

thanks for trying to get this done.

I am able to switch stations with my SWB.

BTW: If I start the FCC_RadioTest application, nothing happens. Is this just something doing in the background?

Locat attached.
[Android Head-Units] tonimontoia:
but this is only for mister riggatoni?
[Android Head-Units] SpeedFire-:
Try this version: FCC csn_v2

And try to put FCC_RadioTest on a home screen and launch from there.

You should see 8 buttons with test functions.

You may also try to record a log when you switch songs in built-in Standard Player and BT music (A2DP). I want to know if the artist/track data is intercepted or not.
[Android Head-Units] rigattoni:
:highfive::good::D

Okay, facts:

1. Radio is switched completely correct with all buttons.

2. A2DP works completey (with SWB and buttons in your test app)

3. Standard player is usable by SWB.

Log attached
[Android Head-Units] rigattoni:
It´s only for units with MCU which starts with CSN2_****

For all others this should not have any effects.
[Android Head-Units] SpeedFire-:
What is SWB?
[Android Head-Units] rigattoni:
Steering wheel buttons
[Android Head-Units] bossman4:
But this means that Speedfire has found a work around that may be more applicable to other audio units.

Good work!

---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

After Rigattoni validates that Speedfire's methodology with CSN units works, maybe Speedfire can expound on what needs to be done for other units (apks needed, etc.)
[Android Head-Units] SpeedFire-:
It seems that your log is not complete. Have you selected a Verbose (most detailed) level of details in LogCat app? I don't see and Debug and Verbose data in the log.

Other questions:

- Can FCC Launcher control volume and brightness? I think that the answer is "no". I also can't find those functions in your apk. You can try to record a LogCat log of changing volume and brightness in native UI.
[Android Head-Units] rigattoni:
Okay first of all:

Brightness itself does not work, but automatic brightness settings is working fine.

Volume control by FCC does not work.

See attached logs with Verbose settings. --> bright_loudn.txt

Additional added a new log for A2DP and Mediaplayer. --> A2DP_Media.txt
[Android Head-Units] SpeedFire-:
What did you do in these logs? It seems that you tried to control volume / brightness using FCC controls.

I actually need logs in which you change volume and brightness on your device using some built-in sliders or SWK.
[Android Head-Units] SpeedFire-:
Unfortunately not. Each platform requires individual approach. Some are easier to integrate, some are harder, some are impossible to integrate. Anyway, each integration requires a lot of reverse engineering and understanding of manufacturer's code. I have more experience now but still it is not as easy as I'd like it to be.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Seems that XDA has some issues with bad gateways in the moment.

The last log file Volume_Brightness.txt - [Click for QR Code] (141.0 KB, 2 views) is the right one.
[Android Head-Units] Th0m4s88:
I finished reinstalling Hal9k Android 8.0 again today so here is a logcat of what happens when my headunit boots up and FCC fails to start DAB Z. I'm not too familiar with Android and the logcat stuff but I hope I managed to do it right and you and SpeedFire are able to see what's going wrong here. :confused:
[Android Head-Units] SpeedFire-:
Please send me your SystemUI.apk
[Android Head-Units] rigattoni:
No problem...

The unit is on bench setup so always available.
[Android Head-Units] realzoulou:
Not FCC's fault and also not DAB-Z's fault. From my point of view, it's Android's fault.

What happens: During early boot, Android finds the DAB USB Adapter and queues up an USB_ATTACHED Intent for DAB-Z. This is unavoidable.

Then FCC adds its Launch Intent into the Android ActivityManager queue. So there are 2 reasons for starting DAB-Z for Android.

When DAB-Z is started it gets the USB_ATTACHED Intent and immediately exits itself, because you have configured it that way in DAB-Z. FCC's launch Intent is lost. If this is by Android design or not? I don't know.

Maybe it helps to increase the time in FCC to wait (default) 6 seconds before it restarts the previous Player.
[Android Head-Units] Th0m4s88:
So DAB Z is started by Android because it detects the USB stick and at the same time by FCC because it wants to restart the last player but accidently completely shuts down again because I unchecked the option for starting it when the USB stick is found?

If I let it start in background it starts playing all the time and more or less blocks FCC in trying to launch other players when they were the last ones playing so that's not an option. I'm going to try and add more delay in FCC and report back what's happening then. Damn that's a stupid problem...:(
[Android Head-Units] ab1702:
I’m sure he said in a previous post that he had dab-z whitelisted(i might be wrong) which would be in the Hal9k rom, so maybe it’s something to do with that.

I have today updated both dab-z and fcc to the latest versions and the autostart dab-z when it was the last player used is now working perfect for me both when starting from sleep or from cold boot. All my settings are standard so nothing is whitelisted or set to autostart or anything, just the fcc setting of autostart last player used.

I’d like to thank both [MENTION=4292729]SpeedFire-[/MENTION] and [MENTION=7838245]realzoulou[/MENTION] for spending your time to find a resolution for this as it is something that has bugged me for a long time and now appears to be working fine no matter which player I last used.
[Android Head-Units] okij:
Hm, so I think DAB-Z should double check if it should exit itself: If it has been configured not to follow the USB_ATTACHED intent, then it should check if FCC has placed its launch intent for DAB-Z. If this is the case, then DAB-Z should not exit itself.

If the launch intent that FCC has placed gets lost automatically (I don't know if this is the case) so that DAB-Z can't check it anymore, then it would be advisable that FCC places an additional hint (e.g. some other intent?) so that DAB-Z knows that it should not exit itself.

I hope that you understand what I mean. Could it be implemented this way?
[Android Head-Units] Th0m4s88:
Now it's getting interesting. I tried setting the autostart delay to 6, 10 and 15 seconds. Nothing worked (the delay works but DAB Z refuses to start). I had some time and played around a bit with the settings in DAB Z and that's when I realized something strange: If I activate startup when the USB device is found and the option start in background it refuses to start. If I don't activate start in background it starts up on every reboot.

There was a short time when everything worked when the option to start DAB Z was freshly implemented but DAB Z was started in the foreground and then sent to the background because in //i think it was\\ DAB Z version 1.6.68 background start by FCC was not allowed. (By the way is there any possibility to get an older version of DAB Z as a short term workaround for me? The one right before 'remain_background' was enabled worked for me)

I attached an other logfile of a start the DAB Z options for start when usb device is found and start in background activated when it still refused to start if you're interested.

I have absolutely no clue why that happens with my headunit but some other people don't have this problem. All I can tell you is that it's not a problem caused by the Hal9k mod because I had the same behavior with the original Dasaita software.
[Android Head-Units] SpeedFire-:
Can you try this version? FCC 3.350_csn_v3

What to do:

- Select CSN2 in FCC Settings - System - Advanced - Select device

What to check:

- FM frequency (and hopefully even RDS) will be shown on FCC's widget

- You should be able to control FM, A2DP and standard player from the widget and see track/artist data.

Video + Log will be helpful to understand how well/bad does it work.
[Android Head-Units] rigattoni:
WOW!!!! That was fast! Thanks a lot

I just installed the update and so far most of it works so far. I need to change some widgets tomorrow and will provide a video and logs after that.
[Android Head-Units] Super_paulie:
Nice work! This has been a real issue for me with my Atoto A6. If this is something that you cat get to work on the Atoto I'd be really thankful!
[Android Head-Units] SpeedFire-:
Good. I still can't find exactly the way to control brightness and audio.

Do you have some other apk?

Maybe something like "com.my.out" or "com.my.audio"?
[Android Head-Units] rigattoni:
Hi SpeedFire-,

I prepared a video and a LogCat file to see what happens.

FM-Radio and A2DP are working so far. They are now opened, but I think that you just did not implement the return part.

Standard player does not work yet.

The automatic brightness settings are not working anymore. May be because you tried to find a solution for brightness settings.

You will find the try to change the brightness at the end of the video/log file.

Edit: If I switch FCC back to Rockchip, the automatic brightness is back working.

Video: https://www.dropbox.com/s/oei755tipj0tgg4/Player_CSN.mp4?dl=0

Logfile: https://www.dropbox.com/s/985p3zdwx1o2u65/Log_Player_CSN2_2020-01-07_11-09-23.txt?dl=0

Additionally, I searched for some apps which could be responsible for brightness and volume... but didn´t find anything.

I added the complete zipped app and priv-app folder in my dropbox and send the link to you in a few minutes by PM.
[Android Head-Units] SpeedFire-:
Thank you for video. I see that each FM station change initiates running of the Radio app foreground. I can add automatic "goHome" action after each such switch but this is not ideal.

The question is: can you change FM stations or A2DP songs using your SWB in the background? If yes, could you record a Log of this?
[Android Head-Units] rigattoni:
Log for switching with SWB works for both.

Edit:

Btw: I always use Tasker to switch back to the home screen after 5 sec not using the screen for each player. So it´s no issue for me that there is no "goHome" action from your side. I just had switched off Tasker to not jump in in my video.
[Android Head-Units] SpeedFire-:
Try to switch stations on this version: FCC 3.350 csn_v4
[Android Head-Units] rigattoni:
Works prefect :highfive:
[Android Head-Units] SpeedFire-:
Please test this version FCC 3.350 csn_v5.

What to check:

- Volume control (using FCC Volume widget and auto-volume by speed).

- Brightness control (using FCC Brightness widget) - unlikely this will work.

- Call via BT (using FCC contact widget)

P.S. Standard player can't be integrated. Artist/track data is sent to a specific app and can't be intercepted.
[Android Head-Units] rigattoni:
Great success so far.

Volume control works with some glitches (attached log file Log_VolumeControl.txt)

To show these glitches I made a video which was created a little later.

Automatic brightness widget works again. No problems visible. :good:

Auto-volume works in demo mode with mocked locations (App is called Mock Locations) :good:

Call via BT (Contact widget) does not work with FCC. (attached log file Log_BT_Call.txt)
[Android Head-Units] SpeedFire-:
Volume control with 2 fingers is a little buggy itself. Can you please put a separate Volume widget (can be found in the list of FCC widgets) and record the same video/log with it?
[Android Head-Units] rigattoni:
Done...

The volume setting is not correct as you can see in the video.
[Android Head-Units] SpeedFire-:
Please test this version FCC 3.350_csn_v6:

- Test volume control

- Test phone calls

Please also send me your device data (FCC Settings - About - bottom part of the menu) to automatically detect CSN2 devices.
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

Volume Control

reacts so far

If you use the widget more than one time, the second touch closes the Android volume notification. Then a next touch works

Sound level on widget is not correct.

Phone Call by widget

Does still not work

Video in Dropbox