yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
This old user also doesn't have a clue what to set his BT Interface to, without trying each one, so see if any work
[Android Head-Units] rigattoni:
...but it´s easy to find out if the old user just opens the factory settings. There the BT-Chip is mentioned and set. ;)
[Android Head-Units] Scopesys:
But the problem is, when the old user was a new user, and did not have a clue, he went into factory setting and changed what the BT Interface was, and now he is old, he cannot remember what it was originally :p
[Android Head-Units] rigattoni:
In this case your BT would be out of any functionality... :D
[Android Head-Units] parisisal:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

I'm testing the v11. with NavRadio+, here the issue :

- On Headunit startup -> FCC Starts -> Click on NavRadio -> Music Starts -> then FCC close NavRadio -> i've to click again on NavRadio icon in order to start again the music (then the music continues)

- After a phone call the music doesn't starts automatically -> i have to click on NavRadio icon

- If the radio is playing and i click on the widget -> the music is stopped (ok) -> if I click again it opens NavRadio interface (it would be better if the music starts without open the NavRadio main interface)

On V11, I can't use the custom skin. Even if i choose a file FCC don't care about it. I don't know why,

Regards,

Salvo
[Android Head-Units] KoTiX2:
I just sent a PM to [MENTION=4292729]SpeedFire-[/MENTION] regarding the same BT problem.

NavRadio can handle the MTC bluetooth by itself but because FCC handle NavRadio as a music player and it send pause/play commands and some MTC broadcasting messages that cause the audiofocus to go mad.

You can test with original launcher or with agama that this is not happening and everything work correctly.

EDIT: SpeedFire is now in "UltraFast mode" and already sent me a patch. I 'll keep you informed ;)

EDIT2: ....and it's already fixed :)
[Android Head-Units] kramttocs:
I know the discussion right now is heavily favored towards NavRadio+ integration but how can we prevent crash reports and core functionality issues from being lost? Not trying to be selfish about it (although I can't use NR+ unfortunately) but looking at it from a new user acceptance factor, I feel those should be given some priority.

For example I don't know if it was the new TPMS I added or not but I can't go 5 minutes without a force close now. I am seeing what I can do for logs (unable to root) but I know if I didn't realize just how amazing FCC is, I would likely try a different launcher.

[Take this post as truly wanting to see FCC become the top auto launcher]
[Android Head-Units] rigattoni:
Yes you are right, crashes need a high prio to get fixed.

Would you please add some information about:

The used head unit

Android version

MCU version

The FCC version you are using

Did you try to unconnect the TPMS and test again?

This would help to get this sorted, even if you are not able to provide logs.
[Android Head-Units] kramttocs:
I have updated my signature. Let me know if more is needed.

This evening I will do some testing and see if I can get some logs sent out.
[Android Head-Units] okij:
Cool, so you got a patched FCC version which is working better with NavRadio+? :cool:

Today I did some tests with Ubiquity Music Widget installed in parallel to the FCC player widget. Interestingly, when the bug occurs that the FCC player widget doesn't update the media information (station name, logo and RDS text) anymore, also the Ubiquity Music Widget isn't updated anymore.

Therefore I'm wondering if something gets stuck in NavRadio+ when this bug occurs (probably triggered by the still buggy way that NavRadio+ is controlled by FCC v11?)

At the same time, NavRadio+'s own widget still gets updated correctly, so I guess that doesn't it depend on the media information broadcast but gets these infos from NavRadio+ directly?
[Android Head-Units] Scopesys:
Going to be a little "DIRECT" here :-

Personally, I think the 1st thing that should get fixed in FCC, is the random behavior of the Player Widget, that is still, after over a year,is still having the issue where it can switch to a different Player, without any input from the user.

Until such time that it reliably remains on the user's selected player, and the Player Widgets ONLY displays information and updates from that selected player, and only tried to Control that selected player, I think all bets are off ever getting any player reliably integrated into FCC.

I think these attempts to integrate Navradio+ have just highlighted this issue once again, and it seems like "quick fixes" are being thrown at the problem to get NavRadio+ to work with an inherently unstable FCC widget, rather than first fixing what is the major issue .. FCC cannot remember that Player it is meant to be interfacing to.
[Android Head-Units] VladimiroCampus:
Navradioi+

really similar issues happening to me.....

Actually i have FccCar Launcer 3.370 V11 and NavRadio+ 1.69, an hard marriage....

Simply i'd like to start automatically Navradio+ after Waze and then go to home with the minimap. I think is enought easy....

I tried to set this sequence in Fcc system automatic start: Waze, Navradio, none, home. 10 seconds delay from start , 3 second between apps.

Every apps starts perfecly,but when system go to home, Navradio+ stops at all. It seems that homescreen killed the process....

So i disable FCC automatic App start and tried Tasker Pro.

I tried with Tasker creating a task starting after 3 second about display on.

3 second delay, start Waze, wait 15 secs, go to home, start Navradio+ waith 60 secs, go to home.

Task starts regular, but when going in homescreen, Navradio+ stops....totally dead.

I have to press icon on screen.....

Really frustrating.

With Default launcher of Android 9 no problem...

Please Help....
[Android Head-Units] okij:
Hm, I don't have this issue.

Besides this, of course it must be possible and allowed that the active player is changed from outside the player widget, e.g. when the user manually starts a player which is assigned to the player widge (by tapping the app icon, by pressing the media key on the steering wheel, ...) or e.g. when a player app is started automatically on boot.

I'm not saying that there are no bugs in this matter, but maybe something else on your head unit is provoking the changes of the active player.
[Android Head-Units] Scopesys:
I don't know what in my head Unit can be causing it. I am not running any sort of tasker type program.

If you don't see it, maybe it's an Android Version thing - I am running the Oem's original Android 8 install.

Its been an issue ever since the Player widget was first Introduced.

It was very bad, it got better, but now, probably with the Changes to accommodate navradio+, the issue has re-surfaced.

It cannot be a false touch of the screen.. It happens very consistently, even when using the Steering wheel buttons.

My GUT feeling, is that it is caused by Caching, or buffering, and then FCC starts to respond to those buffered/cached items that were for another player, although now an different player has been selected.

This might also explain, why, when a Setting Backup from days ago, is restored, some of the player widget windows, seem to update with the old data, that might have been kept in the backup.

Also, since I though it was agreed, that when a player changed, any Artwork or other Player Widget test, would be cleared, until data from the new Player was available, but the widget often displays data from a previous player, that would tend to support the idea that FCC is incorrectly using cached/buffered information, when it should not.
[Android Head-Units] KoTiX2:
Please take logs when you do these tests, it's the only way for us to understand what is going on.

Install any logcat app from playstore and save the logs.

I don't have tasker and I (but I guess SpeedFire too) really don't even have time to try all the combinations of setup that all the users have on their units.

What I can say about the NavRadio crashes on startup now depend on that I have to make NavRadio service start in background.

Once I do that many of the problems related to switching to my app or play/pause behaviour should be gone.

I didn't had much time on these days, the real life is keeping me very busy, but we are on it . Don't worry ;)
[Android Head-Units] marcus82:
sorry for the question but I didn't understand how to display the album cover from DAB or other audio apps. it's displayed the title and radio name but wchi is the widget used to display in the center the cover?
[Android Head-Units] SpeedFire-:
I tried to reproduce your issue but I can't.

For me switching between FM Radio and AIMP player works very well.

Please send me your current backup.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Thanks, will make a backup this evening, and a new video to show it happening.

I will also make sure its V11 :)

Do you have Poweramp, or Blackplayer, if not, what Mp3 player do you use that I can test with ?

Do you have Spotify or pandora, if not, what streaming APP do you use that I can test with. ?

Hopefully, I ca reproduce these issue with a Minimal configuration, just one screen, with 4 quickplayers players.
[Android Head-Units] parisisal:
Hi,

could you do a test for me?

If you are using FCC v11, could you try to apply this skin (is a simply png file) ?

PNG Custom Skin

In my FCC the custom skins are not working anymore :

1) I try to apply the skin

2) FCC wants to reboot

3) FCC restars

4) the skin was not applied

Currently i have a two pages layout :

1) First page with a FCC skin

2) Second page with a custom skin and minimap widget.

Thank you
[Android Head-Units] SpeedFire-:
Yes, there was an issue.

Please check this version: FCC 3.370 v13
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

Thanks ,, now I have more time to spend on my backup / video ;)

On the subject of PMG skins, does FCC mind if the PNG is Interlaced or non-Interlaced ???

I typically make Interlaced pngs, but notice his skin is Non-interlaced

What would you recommend for FCC ??
[Android Head-Units] SpeedFire-:
Well.. I don't know...

I think it doesn't matter
[Android Head-Units] okij:
Thanks for v13, I will install it tomorrow. :)

Does it also contain the patch that [MENTION=2734955]KoTiX2[/MENTION] wrote of yesterday?
[Android Head-Units] SpeedFire-:
Yes!
[Android Head-Units] SpeedFire-:
The latest version under the name 3.380 is uploaded to the Beta channel.

FCC 3.380

It seems that the Release version (3.362) has some issues with Android 10 devices or something else. So I need to relatively quickly issue this Beta (with or without some further fixes) to the Release channel. What do you think? Is it ready? Do you have any major issues?
[Android Head-Units] kramttocs:
Just to confirm - this replaces v13?

To answer your question though, whether it's my setup or not I don't know yet but I am having enough issues with v11 that I would have to err on the side of it not being ready. It is possible that I would have the same issues in the latest official release so pushing .38 as official might not have any more of a negative impact than not pushing it.

Has it been confirmed that the issues with Android 10 (or something else) are resolved in .38? If so, and they are more significant issues than the stuff that has been reported over the past few pages then it is likely in the best interest to release it.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

OK here it is.

Video and FCC Config (and my test tones set of Mp3 files as featured in the Video -- for anyone that would like them)

ERROR in Video Audio comments:

Title : 1000 Hz Test

Artist: Artist Test

Album: Album Test

So Blackplayer is displaying TITLE & Artist ( which is correct ) :eek:​

Also, when just selected FM radio, t

he 1st Steering Wheel NEXT Station does NOT update the station, it Flashes, but its still on the same radio station

( I missed that)

The 2nd press, and it's off to Std Player.

Anyway, the Jumping to another player is VERY Reproducible.

It only happens when

(1) in FM Radio,

(2) Steering wheel button is used for Next Radio Station.

(3)BAD: If After switching to FM radio, the Steering wheel button is used for the 1st Radio Station Change

then the radio station

DOES NOT CHANGE

, but on the 2nd Steering wheel button press, FCC switches to 4th Player (in my case), the Standard Mp3 Player.

(4)GOOD: If After switching to FM radio, the widget or swipe is used for the 1st Radio Station Change:

then all is OK, and the Steering wheel button can then be used for 2nd, 3rd etc Change, and all is well.

There may be other related things going on, where the Player changes when it should not, but this one is 100% Reproducible.

Video:

Showing Jumping from FM radio when steering wheel button is used for next station

FCCBackup file

Can anyone else reproduce this, with their steering wheel buttons ?.

(More than one User reporting this would be very useful information for Speedfire- )​

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

The Test_tones.zip (as featured in the Video) is not part of the issue, but is here if anyone wants it.

( I get a 1 seconds Buzz, 1 second after Players start playing new mp3s, or even when streaming video goes to next song !! Go Figure)

(

I do not get this Buzz with Standard Player

, but i do with all other Mp3 layers I have tried . Blackplayer, Poweramp, etc)
[Android Head-Units] ab1702:
I too see this issue. I’ll be driving along listening to something then all of a sudden it just randomly changes to the other player without any buttons being pressed.
[Android Head-Units] okij:
The APK size of FCC 3.380 (49 MB) is bigger than v13 (46 MB), so I also would like to ask this question.

Is FCC 3.380 still compiled with the stable Android Studio, while v13 is compiled with the alpha version, or are there other differences?
[Android Head-Units] parisisal:
The main issues that i have are :

- even if the music info are coming from NavRadio+, clicking on the widget the default (stock) Radio Player is opened. I don't know why. Sometimes I found both players in background even if I removed all links/icon from the FCC interface (i can open the stock radio player only from the app list). FCC calls the default radio player.

- on first attempt NavRadio+ is stopped (i have to lunch it again)

- the widget on startup shows infos (text and picture) about youtube videos that i watched from my phone (same Google account of headunit)

Thank you,

Salvo
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION],

I found a bug in the v11:

The all apps menu is not set "fitsSystemWindow" as far as I could see.

That means that my top bar is partly overlaying the first buttons.

See example and fix on this page: https://medium.com/androiddevelopers/why-would-i-want-to-fitssystemwindows-4e26d9ce1eec
[Android Head-Units] kramttocs:
I am seeing this also (reported on the 16th).
[Android Head-Units] rigattoni:
Yes, you´re right and I searched for the solution. May be this helps him to get this fixed.
[Android Head-Units] okij:
I tried v13 today and it seems to have fixed the bug that NavRadio+ sometimes kept playing in background when switching to a different media player. :good:

The other bugs that I summarized in post #6392 are still there. I hope that they get fixed when [MENTION=2734955]KoTiX2[/MENTION] made NavRadio service start in background, as he wrote in post #6452. :fingers-crossed:

[MENTION=4292729]SpeedFire-[/MENTION]: There seems to be a bug with the three apps that can be assigned to cycle through with the mode button in FCC settings. I used to have to set them to DAB-Z, FM Radio and GoneMAD Music Player (which I also had assigned in the FCC player widget) and was able to cycle through them with the FCC Mode widget. Now I have replaced the stock FM Radio with NavRadio+ both in the mode button settings and in the FCC player widget, but still FM Radio is invoked instead of NavRadio+ when I use the FCC Mode widget. Also replacing other apps in the mode button settings (like DAB-Z with something else) doesn't have an effect, it's like the changed settings are ignored by FCC. Am I doing something wrong or is this a bug?
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]=

Ref: https://xdaforums.com/showpost.php?p=82914379&postcount=6464

The issue where switching to FM radio, and then the Steering wheel control makes it change player.

FIXED !!!

Either I missed it, or you added (could have been some time ago) :- a setting in Player Widget, to always make the FM radio start in Full Screen, to fix Steering Wheel control issues !!!

I was making a new very simple FCC install, to have just a very simplified (single) Player Widget to demonstrate the issue, and when setting up the widget, I noticed the setting !!

I created all the Player Widgets over a year ago -- maybe that setting was not there a year ago.

Anyway, all is working well now, and with NavRadio+ as well -- so I am very happy :)
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

NavRadio+ -- PTY display in Player Widget

I see PTY (when sent from navRadio+) display in FCC Widget, but as soon as there is more RDS information, it disappears,

Sometimes, that "more RDS" information comes very quickly, and therefore the PTY information only displays for a Fraction of a second.

Would it be possible to either have a fixed (or user variable slider control for) Min Time PTY displays before being removed

or maybe option for FCC to always to ADD it to start of the RDS information display. and any update RDS information, maybe in format [PTY] space space RDS_INFO

FYI: here in the USA, we strictly have RBDS, the USA version of RDS, and USA FM radio station that make it a free for all whet they send as the Station name, and the RDS Text of what they are currently playing, or choose to advertise.

Some times, that Long stream of RDS text takes some time before it sends, or resends, so the PTY info can stay up from a "

Fraction of a second

" to "

5-10 seconds

", or sometimes, if no other RDS message, it

stays there for ever

. (not a problem to me if it stays there for ever)

The some station do not sends RDS info at all !!! (about 20% in my case, living near a major city in the USA)
[Android Head-Units] ab1702:
Are you using Hal9k rom?

If so it may be that in the Hal9k rom settings you have set different apps to be controlled by the mode button compared to what apps you have set in fcc mode function?
[Android Head-Units] dodis827:
i have a dasaita px6 car radio i can't make voice calls work i have tried all versions from the bt settings the problem is known?
[Android Head-Units] okij:
Yes, indeed I'm using Hal9k Mod 4.0.2, but in its rom settings I've only assigned FCC Mode Action. a small app that I made to cycle through the players which have been selected in the FCC settings.

As I wrote, for me it's the selection of the three players in FCC settings which doesn't work anymore.

Could I ask you to try if it works for you with the current FCC version?
[Android Head-Units] Scopesys:
UPDATE: FIXED !! .. 3 hours of messing about , changed masses of settings & defaults, and suddenly NO MORE BUZZ. No idea what really fixed it, but it's fixed -- :good:

HELP Please -- from some of the many Techies here in the Forum

FCC - working great

NavRadio+ - working well

BUT: Any MP3 player except Standard Player : NOT working great :(

At the start of every new Track, about 1 second into the track, there is a loud BUZZ for about 1 second.

You HEAR it, and SEE it on the Spectrum Analyzer video

No Buzz if same track repeats.

No Buzz when Standard Player is used .. Buzz with Poweramp, Blackplayer etc.

Not FCC.. buzz still there when using Oem Launcher.

CPU Load with CPU Load App, makes no difference . same amount of Buzz, for same length of time.

Mp3s on GPS CF card, or USB 2 or USB 3 stick - makes no difference.

Once you hear it, you hear it in every track change,

Makes no difference if Force New track, or wait for current track to end.

Anyone any ideas ??

VIDEO:

Buzz at each new Mp3 track

Note: Each tone is a separate 3-4 second Mp3 file playing

Test Tone Mp3 collection attached if anyone else wants to try this ...
[Android Head-Units] tonimontoia:
fcc possessed by the devil
[Android Head-Units] Scopesys:
In all fairness to FCC ( and NavRadio+) this BUZZ on the Mp3 players was NOT caused by either of them, because it was still there when both App were 100% Uninstalled.

I struggled for 3 hours to find the cause, and then with no success, went on to try to change my Android Notification sounds.

They seem to be stuck, and could not be changed, because Android thinks they are on a specific USB stick, that is no longer plugged into the unit.

Had no success there either, but when I went back to listing to any of the Mp3 players, the Buzz was 100% gone.

The whole track of audio use to sound a lot better on the Standard Player, than any of the other Mp3 players that has the Buzz.

Now the Buzz is gone at the start of each track, the other Mp3 Players are back to sounding as good as the Standard Player..

No idea what was causing it, but its working fine now. Before it was so bad, that I was starting to look at options for a new head unit.

If I ever need to get a new head unit, that is going to be tricky, as it will HAVE to be both FCC & NavRadio compatible .. no going backwards on those two Apps.
[Android Head-Units] tonimontoia:
navradio I don't think it centers, but I don't understand or understand much I can't help
[Android Head-Units] matrixx1:
Hi I don't use navradio but the normal stock FM radio. I fortunately since latest update Yesterday music widget became unstable. Sometimes it switches from Poweramp or Spotify or Deezer by itself to FM. Sometime even if nothing is running no music app, it just switches to FM. :(
[Android Head-Units] Scopesys:
Check ...

Fixed a similar issue for me. ( I added the TICK to select this function)
[Android Head-Units] tonimontoia:
friend, I did not understand the check you have to remove it? I always had it removed but nothing changed for the radio
[Android Head-Units] Scopesys:
NO, you have to ADD it .. ie It has to be Ticked to select this action.
[Android Head-Units] tonimontoia:
Ok thanks freund
[Android Head-Units] Scopesys:
No problem Kumpel .. but did it help ???
[Android Head-Units] tonimontoia:
friend removing the tick fcc seemed crazy, the km marked 240 all busted
[Android Head-Units] matrixx1:
Hi thanks but it has always been enabled for me
[Android Head-Units] SpeedFire-:
FCC 3.390 (release):

- AllWinner support is restored
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

did you see my comment? --> https://xdaforums.com/showpost.php?p=82919973&postcount=6468