yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
Thank for the update -- I see some improvement, but there are still quite a few issues....

The Good news is that the correct selected player is restored after a re-set or re-boot.

The bad news is that there are are still significant issues when selecting players, which are there, even if 4th player is not enabled.

So, eliminating the 4th player, by turning it OFF, and there are still Player selection issues, especially if the same player is selected multiple times in succession.

(1) Selecting FM radio, multiple time, toggles MUTE on/off, but this is not reflected i ten Player CONTROL, and only happens for the FM Radio.

Using the CONTROL, to pause the Radio, the Quickplayer display for that FM Radio selector goes dim when muted (as expected), and CONTROL shows PAUSE/PLAY as expected.

Pressing the FM Radio multiple time. just mutes & un-mutes the sound, with no other visual indications.

(2) Pressing the 2nd or 3rd player multiple times, and then selection the 1st player, switches to the 1st player, but then a few seconds it incorrectly switches back to the player that had been selected multiple time.

Sometimes, it get into a re-start loop, trying to display the correct player, but then jumping back to the incorrect player.

Both the above are clears shown in the linked video, which is 3.317 after a fresh install, and with a minimal configuration (to keep it simple)

That being said, 3.317 is an improvement, and is workable, provide it is "babied" and one does not do anything to upset it, and cause it to go unstable.

The major improvement is that it seems to consistently come back to the player that was playing when the unit was last put to sleep.

One thing to note, (not on Video audio), is that when it is re-stared, it does not come back to the same position in a track, that it was when it was told to restart.

It come back to an earlier position, but not all the way to the start.

Show towards the end of the video, when the unit was restarted multiple time playing Spotify, with downloaded music..

Note the PROGRESS circle, and the audio then it is re-starting ..

3.317 VIDEO

https://drive.google.com/open?id=1CZFh3_uxawmhkCtEx1IHrp65uebTJrbO
[Android Head-Units] bossman4:
I watched Scopesys's video. Those videos are very useful in articulating the issues that are still out there with the quickplayer.

I installed 3.17 this morning on the Eonon (PX5) and played with the QuickPlayer. Here are my observations beyond what Scopesys did in the video. I was just using three players (Blackplayer, FM Player [podcast player], and Amazon [Offline] music at this time.

To me it is apparent that you want your most stable and quickest booting player as the first choice of QuickPlayer if Speedfire is working down the list when he is looking for artwork. In my case, the FM player (Podcast). It starts quick and seems to only have one "album cover". The second player in my sequence is Black Player. It starts a little slower and does not seem to be as stable as the first app. I recommend that the Amazon player (and other potential streamer that checks for internet access) as the third choice.

Some of these players have different graphics within their own application (album covers, lyrics, list of songs in album). I am not sure how FCC knows where the "album cover" is located for the particular application and the lag time in being sure that the album art is current for the particular application. In the case of Amazon Music, there is a side benefit of the recent 400x400 graphic change. The previous obscured graphic that was showing for Amazon album art is actually the "TPMS graphic" for the tire pressure app that FCC has built in. I am not using TPMS at this time. So clearly the FCC pointer for the album art in Amazon Music case is incorrect.

I think some of the FCC problems with the switching is time delays in the apps, so slowing things down may help (switching, button pushing) the situation. As Scopesys says "babying". Slowing things down may help, but it may induce the user to strike the button again.
[Android Head-Units] giffordj:
Routing Failed

Same issue on the latest, I hit the home key, brings up google maps, they gives me a routing failed. Then it opens up google maps with the destination as my current location.
[Android Head-Units] rigattoni:
As Scopesys mentioned, you need a transceiver to do that, which is really expensive.

We do have one in the office and it costs about 2.000 Euro/year... but with some extras as FM, DAB+, Traffic, SDARS transmitter...over the air.

I think this should not work via USB sharing, because you need the connected receiver and get the signal over the air.

[MENTION=4292729]SpeedFire-[/MENTION] If you are interested, I would be able to provide a TeamViewer session with Cam on the unit and shared desktop.

On the other side... may be you need to get in contact with realzoulou, may be he has an idea to share
[Android Head-Units] 007matman:
[MENTION=4292729]SpeedFire-[/MENTION]

First off, I have been doing application testing/development for the better part of 15 years. I represent the business side (not the IT team) for a Fortune 10 company here in the US.. I say all of this to hopefully help you understand that I'm just not some unhinged moron out there on the web complaining about every issue I see.

That said, I have an Eonon Android 9.0 unit that is having a lot of issues with the past couple of versions to the point now where I feel I might need to uninstall.

I have not added any plugins or installed any extensions. I'm running the boat basic form of your software.

The music players don't work a lot if the time. Sometimes simply rebooting the application (using the application widget) will force the app to work. In other instances I need to reset the device.

Most frequent, I use Bluetooth streaming from my phone and while the phone will connect and indicate that music is suing no sound will come out of the speakers. Sometimes switching to the radio will trigger the audio and in other cases it won't work.

I'm really hoping to get your software working again as the OE UI really stinks. I do like the product and would like to see it improved.
[Android Head-Units] Scopesys:
The USB over internet idea should work, if the Internet speed is fast enough.

The person with the USB DAB receiver, connects his USB DAB receiver to a PC, and runs the USB Internet sharing server software.

SpeedFire- then runs the USB sharing client software, and it should be as if he has the USB DAB Receiver local to him on his PC/Emulator, but really, the receiver is in a country with DAB.

It should be as if he plugged the DAB receiver into his PC, assuming that Android Studio can support the DAB USB device.

Cool that you have DAB simulator !!!

We don't have DAB here in the USA.

Looks like be are getting some new FCC approved Digital system here in the USA, owned now by the DTS people. A 10 year plan !!!
[Android Head-Units] rigattoni:
No it will not work, because it needs the real receiver plugged in and the complete decoding works on the DAB+ box.... and the box just gets the signal over the air.

Another idea would be to ask realzoulou for a dev drop using FM instead of DAB+. The receiver software should be able to decode it.
[Android Head-Units] Scopesys:
Sorry, I must be not understanding ... I cannot see why it should not work.

I am thinking of a USB DAB receiver, the complete receiver + antenna etc, that has a USB interface to connect to an Android head unit. These are the receivers sold to work with many of the China manufactured Android HEAD UNITS. (someone posted a link to one being sold on Amazon or Ebay - there are many different models )

ie

https://www.ebay.com/itm/DAB-Car-Radio-Tuner-Receiver-USB-Stick-DAB-Box-for-Android-Car-DVD-US/193171520819

This is what Speedfire could use and plug into his system, to receive DAB signals, if only he had a local DAB station ,--which there is not in his country.

So, move that USB DAB receiver to a location (Country) with DAB service, and then effectively run a VERY LONG USB cable, all the way to SpeedFire-'s PC/Head Unit.

Obviously, the 5000+ mile USB cable is not realistic, but USB over the Internet might be a workable substitute.
[Android Head-Units] SpeedFire-:
I ordered a receiver from China. I think it should work for the purposes of app start debugging.

Although I will not hear any music from DAB+ I still should be able to check the DAB-Z app start.
[Android Head-Units] okij:
That's great! :) :fingers-crossed:

Since you ordered the receiver just for development purposes, I would like to make a donation to support you with at least a part of this investment. I couldn't find a donation info for you, do you have PayPal?
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] just updated to the latest beta and some of my station logos from dab-z have stopped working with the player widget. Is this because of the resolution change that you’ve made?

I also would be willing to donate to you seeing as though you have spent your own money to buy a dab receiver, that’s if you have PayPal?

---------- Post added at 03:18 PM ---------- Previous post was at 03:18 PM ----------

[/COLOR [MENTION=4292729]SpeedFire-[/MENTION] just updated to the latest beta and some of my station logos from dab-z have stopped working with the player widget. Is this because of the resolution change that you’ve made?

I also would be willing to donate to you seeing as though you have spent your own money to buy a dab receiver, that’s if you have PayPal?
[Android Head-Units] 007matman:
Can someone take a look at my post from earlier? Anyone else seeing this issue? Glad you guys are eager to enable new functionality

However, in my book you have a major defect here.
[Android Head-Units] Scopesys:
Sure -- I took a look-- I see Player Selection issues as well... Bluetooth works 100% OK for me though

---------- Post added at 08:41 ---------- Previous post was at 08:34 ----------

@SpeedFire-

I posted quite a long video & Player Widget Bug report yesterday

Ref: https://xdaforums.com/showpost.php?p=80871185&postcount=4611

In hindsight, the Video was a little long and covered multiple issues .. maybe making it a little confusing.

So I have edited it down just to ONE primary BUG (good excuse to play about with some Video editing software !!)

Hopefully, this one can be addressed, as it's fixing might lead to correcting other related selection issues.

(Short) VIDEO

https://drive.google.com/file/d/1K12GktwJvXUk1hxscIn02rKcbFYBf7GN/view?usp=sharing
[Android Head-Units] riceboyler:
[MENTION=9992725]007matman[/MENTION], have you considered that the defect may be with the head unit itself? My Eonon unit does all kinds of weird dropouts no matter what launcher or player I have.
[Android Head-Units] AdekP:
You gentlemen here talking about the operation of four players, DAB + radio and for me FCC can not handle the basic application, which is the built-in FM radio. I often have that after starting the main unit, the fm radio does not start automatically, and forcing them with the physical keys causes the application to be displayed, but unfortunately without sound. Currently, I changed to AGMA launchers, there the radio works without any problems. However, I would prefer to use FFC due to the minimap, radio station logos etc. However, when I get in the car and start the journey, I don't have time to force the main unit to work properly. I have to focus on driving. The main unit is not a smartphone and the car is not a bus.

I've been using FCC for over a year and it's getting worse. There used to be no problems with basic functionality.
[Android Head-Units] 007matman:
It was working well until the last two updates (I'm subscribed to the Beta Channel updates).
[Android Head-Units] Scopesys:
Which Eonon model do you have. Mine is the the GA2170B.

One reason for picking this model was because it has 3 rear USB ports + one more on the front. !!

Apart from its very poor display contrast, it is quite stable with the oem Rom, provided it does not get too hot, CPU runs very hot, (180F + ) even in an Air Conditioned car..

If it is very hot outside, and the A/C fails, then it gets overheated, and will go crazy.

(Before next summer, I intend to fit a fan to my unit).
[Android Head-Units] 007matman:
It's a GA2178 Universal Double Din Android 9.0, 10.1" display. There are 3 USB ports.. one on the back and two that are wired to the unit. The CPU has never been an issue (Rockchip PX30). I have a MicroSD slot on the front (which I have a 64GB card in).

It's been ok.. the initial software was flaky bit they gave me a new version that was a lot better.
[Android Head-Units] Scopesys:
sounds similar -- mine has a micro-usb ? Port on the front, next to the SD slot...

You might have that 4th USB port as well
[Android Head-Units] 007matman:
Yeah.. mine doesn't have the front port. Just the microSD slot labelled "GPS" LOL.
[Android Head-Units] SpeedFire-:
Nice video editing skills, especially soundFX ;) :D

I reproduced the bug and hopefully fixed it

FCC Alpha 3.318:

- Fixed switching between player and FM Radio

- FM Radio is started in background now on Rockchip devices after first full-screen start (which is still necessary, unfortunately)
[Android Head-Units] SpeedFire-:
Thank you, guys, for your offer!

This dongle was quite cheap, so this is not needed at all. Thanks!
[Android Head-Units] Scopesys:
Sounds good -- will try it tomorrow morning .. Its below freezing tonight.

Beatles fan ??
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] This is probably one of the worst ones I've used for trying to restore my backup... or even to get it to load a default setup was a huge pain. It would just keep kicking up a message at the bottom, "That didn't go right, lets retry setup again" or something like that and it would just keep going through that cycle and just wouldn't load. Once I completely cut power to the head unit, and still many tries after, I was finally able to get my backup to load.

And after that, I had problems where it keeps trying to tell me that Titanium backup froze my widgets (or something like that) and I would click the option to try and restore them... But I don't have titanium backup installed. I've seen this problem for quite a few versions now.

I can probably try to reinstall again but with logcat running or whatever you need.
[Android Head-Units] SpeedFire-:
Yeah, I know about the restore function mostly broken. Will be my next priority.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

100% Agree -- fixing broken RESTORE function should be #1 priority. Without reliable Backup & Restore, testing becomes an enormously time consuming task.

As others have reported, unfortunately 3.318 has not really fixed too much, in fact, it seems to have made things worse and more unstable.

There are still Major Issues when trying to select Quickplayers, and seeming random behavior with FCC switching to other Quickplayers by itself (with no user selection)

But, once a given Player has been successfully selected, and FCC has stopped doing "its own thing", most players run well in the widget. :)

FCC still seems to be doing a lot in the background, after a re-boot, something that seems to last for Minutes, even after the screens have loaded, and have become usable.

( Ref: jerky scrolling Text, being a symptom of a lot of other things going on)

So here are 2 Videos .. Hope they help --- I greatly appreciate all the time you put into Developing FCC - amazing dedication .. THANK YOU

Maybe it's time to stop trying to do a quick Fix of the Player Widget, and when you have sufficient time and motivation to get into it in detail. fully evaluate exactly the Logic of the player selection, and maybe consider a fresh logic re-design, if that is what it will take.

As it stands it is "USABLE" .. but a PITA !!

So I have made 2 videos. showing my experience running 3.318, and the multiple issues I experience -- once again, watching a video is probably a lot more informative than a text description of what I "Think" is wrong ... in a Video you can see what is wrong yourself, and form your own opinions and diagnosis.

https://drive.google.com/file/d/1D30q-aqcJz4n8BZrmjX_6w5guojkq2B8/view?usp=sharing

https://drive.google.com/file/d/1D7Rvr7KylWZD90xAI_kXFfusQrhCoAO8/view?usp=sharing

[
[Android Head-Units] okij:
Then again, thanks a lot for buying it just for development purposes! :)

But I think there is at least one thing that we can help you with: Since you don't have DAB radio stations in Moscow, we can give you our DAB-Z configuration (e.g. by posting a Titanium Backup file of our DAB-Z installation), so that you have DAB radio stations in the list and can switch between them - even if you don't get sound of course.

I will post my TB backup file later this day or on the weekend.

I saw that the current official version 3.220 on Play Store is much smaller (20 MB) than the recent alpha versions 3.31x (47 MB), so I'm wondering what the additional code is being used for? Maybe it contributes to the jerkiness after a reboot and could be slimmed down or optimized?
[Android Head-Units] SpeedFire-:
Additional code is almost entirely represented by native C++ libraries of MapBox and Yandex minimap providers (in 3.220 we had Google only).
[Android Head-Units] okij:
OK, good to know! My guess is that those libraries don't lead to the jerkiness that [MENTION=9325785]Scopesys[/MENTION] observed (well, they could if MapBox or Yandex is used.)

BTW, I didn't observe jerkiness after updating to FCC Alpha 3.318 on my PX5 4/64. I just updated the APK, maybe after a full reboot the system takes longer to settle. I'm using Google as minimap.

I now attached a TB backup of my DAB-Z 1.5.61 installation. It contains the DAB+ stations that I can receive in the western part of Germany.

This morning I used FCC Alpha 3.318 together with DAB-Z 1.5.61 and again had echo effects because of two instances von DAB-Z running.

For now I restored DAB-Z 1.5.60 which I used before and will keep an eye / ear on it.

For the last couple of days I used the older version FCC 3.205 together with DAB-Z 1.5.60 and had no echo effects, so this bug must have been introduced by one of the newer FCC or DAB-Z versions.
[Android Head-Units] Scopesys:
The Jerkiness I am referring to is in the SCROLLING of Artist & Song text in the Player widget (If those text entries are longer than their display box).

(To me, a good indication of how much processing FCC is doing, and if high, the scrolling smoothness suffers) .. It gets significantly better after a few minutes after a re-start or re-boot when FCC seems to settle down.

BTW I use Google Map as well, but this is not even on a map page.. just a simple Player Widget page.

---------- Post added at 16:01 ---------- Previous post was at 15:53 ----------

You should be in a position then to determine if the BUG is cause by the later FCC version, OR the later DAB-Z version.( 1.5.61 ?)
[Android Head-Units] rigattoni:
Would you please post the link to it?

I hope you did not buy any stick with a RTL chipset, did you?
[Android Head-Units] realzoulou:
I looked into your configuration of DAB-Z 1.5.61 and see that you enabled OMRI.

I just found a bug in DAB-Z (versions affected are 1.5.60 and 1.5.61) that results in "echo audio", but only with OMRI enabled.

I'll test FCC with DAB-Z and try to find out whether there is a problem in DAB-Z causing the "no restart" issue
[Android Head-Units] SpeedFire-:
I ordered this one

https://s.click.aliexpress.com/e/n6EvJ9C
[Android Head-Units] ab1702:
That makes sense, I’ve seen the problem before but not recently. I disabled omri a few weeks ago and it’s been fine ever since
[Android Head-Units] realzoulou:
Will work with my app.

But with no DAB reception you cannot run a station scan and with no station list, DAB-Z will behave differently than with a station list. E.g. it will not do anything when being controlled via MediaController. No PlaybackState, no MetaData...
[Android Head-Units] SpeedFire-:
Will it work if I restore some other user's settings via Titanium Backup? Or maybe you can add some dummy station?
[Android Head-Units] Scopesys:
[MENTION=7838245]realzoulou[/MENTION]

How possible would it be for you to create a Custom/Developer's version of your App, that included TWO DUMMY Pre-defined stations, that had preset Meta Data, and maybe even played customized test Mp3 music files (That had the meta data in them)

ie That DUMMY/TEST station would always be available, even in a location without DAB reception, and could would always display these Two test stations, and their data, with the ability to switch between the two station, and get their updated meta data etc.

(or even make this an added feature present in future version, so they can also be tested by developers with their launchers)
[Android Head-Units] realzoulou:
I just tested with the TB.zip from [MENTION=4916555]okij[/MENTION] and following these steps it should work for you *IF* the DAB USB adapter is connected. No DAB reception is needed.

1) Install DAB-Z from PlayStore

2) Start it and run through the installation steps (permissions, blabla)

3) Kill DAB-Z

4) Upload complete folders "files" and "shared_prefs" from TB.zip to the device and thus replace the existing files in those 2 folders

5) Make sure that the file permissions are correct!! They all may now be only accessible by "root" . So use chown/chgrp to recursively change all file permissions to match with the user/group that Android gave to DAB-Z during installation.

Example: When DAB-Z app is uid "u0_a165":

px5:/data/data/com.zoulou.dab # chown -R u0_a165 *
px5:/data/data/com.zoulou.dab # chgrp -R u0_a165 *

6) Start DAB-Z and you should see 6 stations, 5 of them have a logo, "WDR 2 Rhein-Ruhr" has only the default logo
[Android Head-Units] okij:
Thanks for reading along the FCC thread and looking into my configuration!

Should I disable OMRI for now (and of course do a new scan) or should I use DAB-Z 1.5.55 with OMRI enabled until this bug is fixed? (I found version 1.5.55 on APKPure, unfortunately they don't host 1.5.59, the direct predecessor to 1.5.60.)

That's great, thanks a lot! :)

Thanks for checking and confirmation that it works! This way [MENTION=4292729]SpeedFire-[/MENTION] can do his own tests with DAB-Z when his DAB adapter arrived.

IMO it should also be possible to extract the contents of TB.zip to the TitaniumBackup folder and then restore DAB-Z 1.5.61 with my configuration via TitaniumBackup. This way it shouldn't be necessary to manually change the file permissions.

---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------

That of course would be perfect for developers who don't have DAB in their country. [MENTION=7838245]realzoulou[/MENTION]: Could you implement this with reasonable efforts?
[Android Head-Units] SpeedFire-:
[MENTION=9325785]Scopesys[/MENTION] can you please check this version in terms of Backup/Restore? If it doesn't work please send me your backup files again please.

FCC Alpha 3.319
[Android Head-Units] Tbizzness:
[MENTION=4292729]SpeedFire-[/MENTION] I too have a problem with backup/restore where it can't sign in to my account.

Any suggestions would be gratefully received.
[Android Head-Units] realzoulou:
I propose to keep current version of DAB-Z and only disable OMRI until the next release of DAB-Z.

I will have a look but I cannot promise. It's for sure some significant effort.