yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
Running 3.370 v5 with latest beta navradio+

Good news.. The navradio BEEP no longer closes navradio +

Where in 3.370 v5 is the support for NavRadio+'s PTY ??

The Bad news:

navradio+ now forgets mode selection, so nothing shows up ie No Presets & Freq is ----.----

( so one has to keep re-selecing the Mode.. ie FM, but then a little later it resets to nothing selected - typically after FCC is restarted or a system re-boot.)

Even with navRadio closed, now the FM radio does not show Station Logos, as set into FCC

[MENTION=4292729]SpeedFire-[/MENTION]

Reason may be because now the radio Frequency, as displayed in the Player WIdget, no longer has a decimal point - so now, maybe it cannot match to the radio Logo database.

see Screenshot - No Decimal Point in Frequency

VIDEO: No DP in Frequency

This "MAY" be a reason why the Logos are not displaying anymore

In order to get a stable launcher, I have gone back to FCC 3.365 v29, and uninstalled Navradio+

The combination of FCC 3.370 v5 and the latest Navradio+ is just too unstable to be usable
[Android Head-Units] SpeedFire-:
Thank. Please try this version: FCC 3.370 v6
[Android Head-Units] rigattoni:
After cold boot FCC runs with this version into a crash loop.
[Android Head-Units] Scopesys:
Thanks for the warning. I saw the update post, and was just about to download it and install it.

I still will, if only to verify your finding,

I have updated, uninstalled & reinstalled FCC & NavRadio+ so many times , that I can do now with my eyes closed !!!

FCC is real easy, thanks to the Settings backup.

Navradio+ not so painless -- while the Stations can be saved in their" json" file,(GREAT !!) the SETTINGS have to be set again, every Install, as there is no Settings Backup & Restore (Hint Hint)

If one does a lot of customization of the Theme, then it can be quite time consuming to get it all back again after a re-install
[Android Head-Units] okij:
Current state of NavRadio+ integration

Thanks, I tried it with latest NavRadio+ 1.70 and it doesn't get killed by the button beeps. :good:

Those NavRadio+ integration issues are still existent with FCC 3.370 v6 and NavRadio+ 1.69:

The player widget still randomly stops updating station name, logo and RDS info, so even when changing stations, the widget display is stuck until changing back and forth between different players and/or fully closing NavRadio+ before starting it again.

Quite often I have to press the player widget button that I have assigned NavRadio+ to 2-3 times to switch to NavRadio+. This should work with only one press, like it's correctly working with the other players (DAB-Z and GoneMAD Music Player in my case).

When switching from a different player to NavRadio+, it takes about 6 seconds before even the NavRadio+ screen is shown and shortly after this the playback starts. IMHO there is something wrong, this delay cannot be caused by the time that NavRadio+ needs to load (it's an app of just 2-3 MBytes in size). [MENTION=2734955]KoTiX2[/MENTION]: Please also have a look at this, i.e. do some test with FCC v29, to see what might be wrong and how it can be improved. Edit: I now did some tests with NavRadio+'s own widget and (when pressing on it), NavRadio+ starts instantly. So this 6 second long delay is something that needs to be fixed on FCC's side or in the way that NavRadio+ is controlled respectively activated.

The NavRadio+ screen is shown for about a second when switching from a different player to NavRadio+. It would be great if this could happen in background, similar to the way that FCC starts DAB-Z in background. (Side note: This currently doesn't work reliably in DAB-Z too, please see #4 above, and might be caused by the way that FCC accesses the player apps.)

NavRadio+ sometimes keeps playing in background when switching to a different media player.

Also [MENTION=2734955]KoTiX2[/MENTION] for information, since I don't know which of these issues need to be fixed in FCC Launcher and which in NavRadio+.

Please let me know if you need any logs for debugging.
[Android Head-Units] SpeedFire-:
Thank you for logs!

There was an issue with a weather forecast (external library).

This should work: FCC 3.370 v8
[Android Head-Units] Scopesys:
Good news:

(1) The FM radio logos are now being displayed, and the Frequency now has it's Decimal Point back.

(2) No Boot loop for me -- maybe I'm not using the weather library in my setup.

The Bad new:

New BUG.

Steering wheel Next/Previous Station buttons, when in FM radio,

causes FCC to switch to previous Player.

This was not happening in prior version.

Widget control of next/previous radio stations works fine, it's just the Steering wheel control. has this issue (see Video)

Still the defect, that when a new Player is selected, the Artwork & SONG/ARTIST are not be initially "CLEARED", so can still show the old Player's information, until thee newly selected player updates this information. Not always, but still happens in many circumstances (see Video)

VIDEO
[Android Head-Units] SpeedFire-:
Can you record a log of steering wheel issue? (with video)
[Android Head-Units] Scopesys:
[MENTION=2534110]rigattoni[/MENTION]

I am not rooted, so cannot produce log information.

If you can reproduce the issue I am seeing, where the Steering Wheel next/previous station in FM radio, cause FCC to jump to the previous player, maybe you could LOG it, and send it to Speedfire, which may help him see what is going wrong.

Also, LOG when a new layer is selected: - if that player is of a type that takes time to get it's information as it loads and connects to the Internet, why during this time, FCC is refreshing the artwork and Song/Artist with the information from the previous player.
[Android Head-Units] tonimontoia:
this latest version always crashed fcc cannot be used
[Android Head-Units] Scopesys:
No, I have just asked rigattoni if he can do that for me , and send it to you.

---------- Post added at 11:03 ---------- Previous post was at 11:00 ----------

Which "latest version" ? the latest changes hourly !!

v6 is known to crash (Weather Library issue ? )

v8 should have that crashing fixed
[Android Head-Units] tonimontoia:
the v8 crashed continuously, while the v6 I had no problems
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

A expected, going from V6 to V8 did not change the FM Radio the Next Station by Steering Wheel, switch to previous player issue.

So if rigattoni is updated to latest v8 and can reproduce the issue, he may be willing to send you a LOG.
[Android Head-Units] SpeedFire-:
Yes, it looks like in v8 the issue is not resolved. Please try v9

FCC 3.370 v9
[Android Head-Units] tonimontoia:
always the same crash continuously
[Android Head-Units] rigattoni:
I may be found the issue of my reset I reported with the last ones. I´m just now back to 3.336 v29 which is stable.

Even with the 3.370 the same reset happened with active WiFi.

It happens only if the unit has WiFi.

If I switch it off, FCC keeps stable until I activate WiFi.

Just now, I´m connected to the unit via WiFi and not directly sitting beside the unit, it will take ~ 1 hour to be back from my balkony. ;)

Then I will update to V9 and report back with a log file.
[Android Head-Units] Scopesys:
Amazing amount of activity in the Forum today, after almost 10 days of virtual silence.

Lost count of the Version Updates today .. but very impressed by the rapid support from the developer :)

2 Hours ago I decided to STRESS TEST V8, which at the time was the latest update.

Some had reported that it kept crashing,

At first, it did not seem that it was crashing for me.

So I started recording, and do as much as I could to try to evoke a crash.

I have a reasonably complex setup, with multiple of pages, and multiple instances of widgets on multiple pages, so it seemed to be a good test.

If nothing else, and I could not get FCC to crash, it might end up be an interesting Video, especially to new FCC users, to show what can be done with FCC, if you push its features.

All seemed fine for about the 1st 30 minutes, and then maybe a co--incidence, or whatever, FCC started to Boot-Loop.(Just after a FORCED re-loading Widgets)

I tried all sorts of things to stop it from Boot looping, including complete Systems Re-Boots.

Finally, I found a way to stop the boot-looping --- restore a previous FCC settings backup. (that was made during running a previous version)

This stopped the BOOT-LOOPING

AND

It also stopped the Steering Wheel control from FCC resetting back to FM radio, when trying to advance through on the Mp3 Player !!!

TWILIGHT ZONE !!

Anyway, now with V8, and a restore of FCC settings, all appears to be running well without FCC restating repeatedly in a loop.

Since I was recording the whole STRESS TEST, including the start of the FCC Restarting loop, and it's final recovery by reloading a Settings backup, I may as well link to that video in this post.

(Try not to fall asleep watching it !!! )

VIDEO: V8 getting into a Restart loop, and its fix

(LARGE Warning: 252MB)

Now Lets see what V9 does :)

BTW: FYI Throughout the above V8 testing, NavRadio+ has been completely UNINSTALLED from my head Unit

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

I messed up, when I re-booted the UNIT, I did not restart the recorder,

so I do not have Video of the way I got out of the BOOT-LOOP

After the re-boot, FCC was still in a restart-loop.

The way I fixed it was to RESTORE a previous settings backup.

Then all was working again, AND -- the next station button on the steering wheel was no longer forcing FCC to FM Radio

GO FIGURE ..

So, at the Moment, I have a Working FCC - YAY !!
[Android Head-Units] tonimontoia:
then you mean that the problems are with navradio
[Android Head-Units] rigattoni:
Video without audio... sorry.

I just updated to v9 and the initial thing is that the reset is still in there.... but first after wakeup from sleep.

Just now I will do a cold boot to reduce the trace

0:00 -0:45 current reset visible.

0:45 --> switch off WiFi After that FCC keeps stable.

1:18 --> switch station with stearing buttons and player manually

Switched between DAB-Z, Online Radio and MP3, but FCC

Station changing switches player in the widget when using stearing buttons.
[Android Head-Units] okij:
Then you did not read his post carefully enough or did not watch his video.
[Android Head-Units] rigattoni:
Sorry folks I had to edit my posting to add the right video.

Just now it is the correct one.
[Android Head-Units] SpeedFire-:
It seems that I reproduced the issue (this is probably because of switching to the Alpha version of Android Studio).

In this version I don't see crashes but weather does not work.

FCC 3.370 v10
[Android Head-Units] rigattoni:
Argh... I tested the Alpha too with bad results. Went back to the stable version.

I will try the v10.

Weather is not that important. I am able to have a look outside. :D
[Android Head-Units] Scopesys:
NO, quite the OPPOSITE.

I had Navradio+ UNINSTALLED, and still got into a FCC Restarting loop
[Android Head-Units] tonimontoia:
how can I see the video that gives me error ??
[Android Head-Units] Scopesys:
OHH... Is it just you that cannot see these videos, or is it everyone ? (and I am wasting my time posting them)

I am 99.9999% sure I now remember to set their Google Drive Permissions to "anyone can view" -- a mistake where I was failing to do that a month ago.

This was a BIG one (250+ megs) . maybe that is the issue, if you are on a slow connection ?
[Android Head-Units] rigattoni:
Reset is gone! :highfive:

Weather broken as you wrote.

Still some strange behavior in switching player...

https://www.dropbox.com/s/d4d5taubd0y02wm/20200621_212232.mp4?dl=0
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION]: I can see your videos since you changed permissions.
[Android Head-Units] Scopesys:
Thanks

Here is my V10 Video .. Radio is still messing up with Steering Wheel Buttons.

VIDEO: Version 10 -- Radio issue with steering wheel NEXT/Previous Station Buttons,

(OK with FCC widget control button

)
[Android Head-Units] rigattoni:
I just had this 2-player playing too. Unfortunately I am not able to get the mic activated, so no audio...

May be visible in the traces.
[Android Head-Units] Scopesys:
NO Mic ? -- so does that mean No Google Voice, NO Phone or it it an issue with the On Screen Recorder ? ( I use DU Recorder)

I think it was a few $'s to get the AD Free version, but it has proved to be well worth it.

Works, Takes Screen shots, and is easy to use, and transfer Videos back to Google drive.
[Android Head-Units] SpeedFire-:
So here it looks like the weather is back to normal.

Some other issues related to deep integration of head units may be resolved as well (in previous betas class names were obfuscated excessively).

FCC 3.370 v11
[Android Head-Units] rigattoni:
hmmm... Weather seems to work... Just now I only get the forecast.

BUT.... Player widget is completely messed up now. :(

I will prepare a new trace and video.

Just now rebooting the device to minimize the traceload.

Hang on...

Edit:

I need to withdraw my first impression mostly...

Switching between the player works mostly. Sometimes it takes DAB+ even if I chosed MP3 player. May be related to the existing issue in DAB-Z....

But the issue with getting the audio focus seems not really reliable. Sometimes the MP3 player is not muted if I switch to Online radio and vice versa.

Did a new video and traces.

Video
[Android Head-Units] rigattoni:
This is, because the unit has it´s own speech recognition for the most common commands, like "Start navigation, start player, start phone.... "

May be I will deactivate this functionality, because it only works for internal apps. But before, I need the new MCU and firmware which might be ready within the next 2 weeks as I got informed by Klyde.

I use AZ Screen Recorder which has the same functionality DU Recorder crashed from time to time, so I got rid of it.

Google Voice, Phone and all other things are working fine.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

V11 .. interesting change in operation

Complete uninstall, re-boot, then Install V11, then re-boot. Then restore my FCC settings.

Note: Even Before restoring my FCC settings, with very basic setup, it was still not working correctly -- as below

Still has issue with steering wheel buttons, but only in FM radio.

Select FM radio, runs, FCC widget changes stations. - all OK

Screws up with Steering Wheel Buttons:

1st Steering wheel Press. Radio stops playing

2nd Steering wheel press, and Blackplayer (2nd player) starts playing --

but now, no Screen update

Still showing FM radio selected

, and

still showing FM radio Artist/song/artwork

Further Steering wheel presses ,and Blackplayer changes song, but no screen updates .. still displays FM radio info

At least in Previous version, after incorrectly switching to Blackplayer, it showed it was on Blackplayer, and the Song/Artist Artwork updates with steering wheel button Next song

LOL I guess you gave me what I wanted -- FCC not changing from FM radio selection display when it should not, but now the end result is worse. ;)

ie Displaying FM radio, displaying last FM radio Song/Artist/Artwork, but happily playing Blackplayer, and Blackplayer responding to controls.

I feel your frustration, from all the way over here :(
[Android Head-Units] rigattoni:
[MENTION=9325785]Scopesys[/MENTION]

I can´t really use the FM-Radio, as it just get´s activated in background, but since the implementation of the new FM-Radio is missing, there is no change in FCC visible. Unfortunately FCC takes a random other player as album art and song information in without refresh.

So tests with this player makes no sense. I have Poweramp as MP3 player, not the Black Player. May be some issues are related to Poweramp too, but it seems not really to be so.
[Android Head-Units] Scopesys:
A lot of changes and advances in FCC over the past 2 months. (April 10 to June 21 2020)

Introduction of Split Screen

Navradio+ Integration

Easy to get lost with all these changes & Updates.

So I have put together a list of all the updates over those period, with whatever descriptions were available for the Update changes.

This makes it a lot easier (for me) to see what previous version to go back to, to achieve a more stable launcher, which, (for me), was just before the Introduction of Split Screen, and just after the fixes were made for the Google Library updates (To correct a bug in those Libraries)

So, for me, that last Previously STABLE version was

4/24/2020	FCC 3.364v2
[Android Head-Units] okij:
Just want to report that for me v11 is working as good as v5/v6, i.e I don't have problems with steering wheel buttons and the problems with the player widget are the same as I've described in post #6392, but not worse.
[Android Head-Units] tonimontoia:
version 11, time does not work, more often than not it loads logos of any kind, navradio, Spotify, poweramp
[Android Head-Units] rigattoni:
Why are you always posting issues without showing anything?

No screenshots, no video, no logs.

That makes definitively no sense.

No issue seen with time on any of my units. The other issue with the player widget is visible on all of them.

No issue with logos, no resets, nothing else.

I updated yesterday evening my MTCE, the CSN2 and my new unit where the videos are coming from.

So if you have problems, reboot your device and show details instead of posting a oneliner...
[Android Head-Units] tonimontoia:
you don't deserve an answer, do you think I write a lot to write? what should I post that the weather does not indicate the temperature, that the logos sometimes go sometimes no, the log file I don't even know where it is taken, then I don't have these problems like you to me if it doesn't work patiently I wait for another version, I just said my problems
[Android Head-Units] rigattoni:
Sorry, once again...

If you have problems, just show them.

You really should be able to create screenshots if an issue occurs, right?

You even don´t post your setup yet.

No one knows with which settings in FCC and on which unit you are testing. Not any information given from your side.

What do you think, any developer should be able to analyze without any detailed information?

Right... nothing if this is not visible on his test devices.

So please... If you have visible issues, show them in an adequate form. Take screenshots, show screen videos as we all do and please provide details of your unit.

Which unit with which MCU, Android version and what you have set in FCC as unit. That is the minimum of needed information to get bugs fixed.

You can find the settings in FCC in the settings menu/system/extended settings. Post a screenshot of this page.
[Android Head-Units] Scopesys:
Better still, put this basic Information in your SIGNATURE, so that at any time, anyone reading your posts, can see your signature, and know what equipment you have, and are having issues on.

Posting a Screenshot is all well and good, but when reading Forum Member's Post,

who can remember what equipment every Forum Member has

??

If it's in the signature of each post, it makes so much more sense... in so many ways.
[Android Head-Units] parisisal:
version 11, the custom skin (external png) are not working anymore.
[Android Head-Units] kramttocs:
Great to see all these updates!

I'd mentioned this earlier but Chrome isn't playing well with FCC. Is there a way to exclude it as a 'Player'? I think that's the root issue. I have it as a shortcut on the homescreen and pressing it doesn't launch it but it does appear to change the player to it (which I don't want). Anyone else experience this? A way around it while still having a homescreen shortcut?

Using v11
[Android Head-Units] Scopesys:
[MENTION=4916555]okij[/MENTION] I saw you discussing navradio+'s PTY RDS information on the navradio+ forum.

But how does the PTY information display in FFC.

I can see ARTIST and SONG in the Player Widget, (or more specifically Line 1 & Line 2) and a way to swap them over, but where is the 3rd item of text, the new PTY information. ?

I was expecting to see it as an option to be added to one of the 2 current items ( Song or Artist), or ideally, the selectable choice to add it to whichever of the two one wanted.

(Or add it Onto the Artwork)
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION]: On my unit the PTY is shortly shown in one of the two lines (can't remember right now if it's in the artist or song line) when tuning to a new station, until the first update of the media information.

For me this is sufficient, I prefer this behaviour over a 3rd line or over the text being written onto the artwork, since PTY isn't that important. If SpeedFire- should implement in one of the other ways, IMHO it should be optional.

Unfortunately the display of NavRadio+'s station name, logo and RDS info in FCCs player widget doesn't work stable yet (it gets stuck quite often), as I already mentioned a couple of times. Still hoping for a fix.
[Android Head-Units] Scopesys:
I have found that once NavRadio+ is running under FCC, and is not conflicting with the oem's FM radio App, then the Artwork, Station name and RDS text work without fault, every time I change station. (And I have manually edit Station Name, which I choose to make a long string of text, so much, that it scrolls in FCC's widget,) and all is well.

TMI ?? :D

Initially, personal preference would be an option to add PTY to the end of the "Station name Text" or the "Other RDS dynamic data text", but I can see that may be an issue, as Station name may available immediately, and getting the PTY is delayed a little. So this may be something easier for FCC to do, as it collects the Information over time from navradio+, and assembles it to be displayed in the FCC widget.

ie FCC may display just the Station name information initially in the Station name window, but then later, when it gets the PTY Information, FCC updates it's Station name to add the PTY to the end.

However, in the end, what I will probably do, is to do this myself manually, when I manually edit the Station Name -- I'll just add the RDS PTY information into the edited Station Name (in Navradio+), and then if the station is not sending RDS information, so no PTY information, I then have the option to decide what I want the PTY to be, and the option to add it in if I want.

Actually I really like that as" my solution" - gives me total control :)

Typically I manually edited the NavRadio+ Station name to be something like:

WRCK 97.90 "98 Rock" Baltimore MD

so to manually include the PTY information, is easy, and I could make it

WRCK 97.90 "98 Rock" [Rock] Baltimore MD

In practice, I have found that if I do a DX scan for stations, and set those up with Logos and manually edited Station names (No choice here in the USA.. One has to manually edit what the USA radio Stations send out as "station name", as it is often the field they choose to send ALL their Station Information on, including what they are playing etc and ADs !!), (and save that configuration)], then I am good for FM radio for about 100 miles from Home, so there is little need to Scan again and setup again - and I am "Good to go"

If In travel outside the range of these radio Stations, I can always do a temporary "add stations scan" and not bother to fully set those newly found stations up, and then restore my Good HOME scan configuration later.​

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

Another thought : If FCC is now displaying Navradio+'s PTY information sent as the field "ALBUM", will FCC be able to display the ALBUM metatdata from a Mp3 player ?
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

just a short remark:

I think it would make sense to change the names in the list of BT interfaces.

Would you be able to sort them by BT-chip with it´s name like BT-6, BT-5... or whatever else, instead of "New PX5" and so on.

What do you think? A new user doesn´t know what to set in there.

My new device has a Sundinq Qualcomm 3008 BT chip which is not yet supportet, but just now I don´t need to have it, as I am able to voice calls.