yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
Unfortunately, its the LONG term operation that seem to be the major issue at the moment.

I'll try 3.310 and test the corrections for that release.

I don't believe anything has been done yet to address the long term stability issues, but I really endorse the "small steps at a time" approach, not trying to change too much all in one go. :good:

ie fix the easier ones 1st, and then see what is left that may be more difficult.

---------- Post added at 14:41 ---------- Previous post was at 14:31 ----------

The online streaming Players add extra complexity in their own right, so I am taking the approach only to test with Players with local sources, ie Mp2 players and Radio.

Amazon & Google are both potentially problem prone.

Spotify is OK, if it is set to just play Local "downloaded" music.

So I am using

FM Radio (am.fm radio)

BlackPlayer (mp3 player)

Spotify ( downloaded music only)

and 4th player "Standard Player" Mp3 and other MP3 players (except Poweramp) -- have always had issues with Poweramp & FCC :(

My thought are that it may be easier to get many of the FCC Quickplayer bugs that are common to all players, sorted out with the simpler players, before adding in the complexity of streaming services.
[Android Head-Units] bossman4:
I was testing Amazon Music in the local storage mode, just like Spotify. The behavior that I documented on the Eonon that I mentioned, was in that offloaded mode. Should be no different than Spotify when it is running local I was just complaining that the replacement of the external memory (USB stick) to accommodate the continuing list of newer versions of FCC was causing Amazon to reload the downloaded music on external memory for testing. The options on Amazon Music for offloaded songs indicate that it is stored on a SD card (which I have). But when I pull a USB stick, it tends to corrupt the local Amazon Music Database. It then requires the Amazon music to be downloaded again. Makes me want to be sure the local Amazon music database is small during the constant FCC testing.
[Android Head-Units] SpeedFire-:
Alpha 3.311:

- Attempt to fight memory leak. I don't know for sure but I guess this long term degradation is caused by some memory leak. In this version I've made some changes to SharedPreferences (a tool to store values on hard drive) throughout the whole app. This may help or may not. We need to find out.

FCC Alpha 3.311
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

3.309 After 10 hours of operation, (overnight), it was completely locked up in a FCC re-start loop, and only solution was to switch to OEM launcher, uninstall FCC, and the re-install. Now running 3.310

Restored my FCC setting, and had to do quite a lot of switching between Players, before it settled down and operated correctly.

Now running correctly .. but I feel sure that if left for 10 hours, will be in a loop again.

Maybe you can let 3.310 run for an extended period in your Emulator,(Overnight, with a player playing Mp3s ) and see if you get this re-start loop, and can see what is causing it.

I'll try doing the same tonight, although I do not have a lot of confidence in my Android Studio emulator and setup yet.

BTW: What level of Logcat should I use to be the most useful, if I get this looping, and want to send you the log ?? Verbose, Warning ??

---------- Post added at 16:42 ---------- Previous post was at 16:38 ----------

[MENTION=4292729]SpeedFire-[/MENTION]

Cool, missed that when I made last post ..

Will install 3.311 and run overnight .. FINGERS CROSSED !!!

While installing 3.311 I had a thought, as I was running through the players, getting thing to run in a stable manner.

A Diagnostic Watchpoint Widget.

One that could display maybe up to 10 variables, each one selected from a list of available ( informational variables), and that updated those watched variables say every 1/4 second.

If that widget was displaying when say switching Players, then any video made of an issue, with relevant Variables displayed, might greatly help.

I assume this is what can be done in Android studio, but few have that, and running in an emulator is not nearly as realistic as on an actual head unit.
[Android Head-Units] rigattoni:
Running on my bench unit over night too...

Let´s cross our fingers. :highfive:
[Android Head-Units] SpeedFire-:
Alpha 3.312:

- BT widget optimized (for some reason it consumed a lot of resources).

- Other internal optimizations.

Better install this version for test.

FCC Alpha 3.312

Verbose!
[Android Head-Units] 007matman:
[MENTION=4292729]SpeedFire-[/MENTION]

I noticed something with the most recent version posted to the Beta Channel.

The countdown clock to sunset as well as the auto-brightneas feature seems to have the incorrect time. This just started occurring on Sunday (when Daylight Savings time ended). Tonight the countdown to sunset was an hour behind.

I did a quick search in this thread and didn't see similar mention of this issue. The time on my clock is correct.

Thoughts?
[Android Head-Units] Scopesys:
For SUNRISE:

East Coast USA at 21:30 ( FCC 3.312) FCC clock says 21:30 so Correct

Widget says Sunrise is 6:37 (Internet says 6:37) so Correct

So , calculating from above , sun rise is in 9:07 hours

Widget says 9:07 hours - so is correct.

For SUNSET:

Will have to wait till daytime tomorrow to get values.

I have never paid it that much attention, being more interested in current Temperature, so it stays set at that 99% of the time.
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]_

FCC 3.312 Full re-install, and then restored FCC settings.

Video showing:

POINT #1

After FCC re-start by Re-start widget, FCC returns with original Player Playing, dislay that player's Artwork & Text, but does not have that player selected as the current Quickplayer.

FCC, then gets into a Re_Start loop, but seems to never be able to determine which player is playing.

Way to stop the Loop, is to select another Player, and then the original player, and maybe then another player, and finally the original player, and then FCC shows that player selected, and stops re-starting.

POINT #2

Removing the option to have a 4th player, does not change this above re-start issue

POINT #3

Having removed the 4th player, if it is then turned back on again in the Widget, it has remembered the last 4th player, and put that back into the Widget display as the 4th player. CLEVER, maybe TOO CLEVER ... ? If 4th player is turned off, maybe it should get rid of all 4th player historical info, so that there is no confusion if a 4th player is then turned on again in the future, and one is selected (or not).

Since FCC seems to be doing quite a bit of Un-expected re-starting, maybe a high priority should be given to fixing this issue after a re-start, that might also lead to an overall reduction in re-starts.

I would really like to see an Overlay down in the corner (like the Padlock), that showed when FCC was LOADING, or still in the process of Re-Setting, and warns you that it is UNADVISABLE to touch the screen until it has finished.

Very often it looks like FCC has finished doing its re-start, and then, anything up to 1-2 minutes later, it suddenly does something like switch the Player !!!

Not as bad as about 10 version ago, when I would start the car, music would play, and then some 3-4 minutes later, a few miles down the road, FCC would suddenly switch players !!!! Its getting better :)

VIDEO: FCC 3.312 in restart loops

https://drive.google.com/open?id=1B_xoV869Lg-XfDFkhmm_VAzM4NwjjB5V
[Android Head-Units] tonimontoia:
after last update km / h does not work anymore, done clean installation and restored backup, also returned back of application but nothing to do
[Android Head-Units] LinkseD:
I got massive minimap problems since updating to version 3.312.

No matter if I choose Google, MapBox or Yandex it stays at the non working google map. The current speed (km/h) and location are not updated, the map stays on the last location it has worked when updating to 3.3.12. Sometimes when switching map providers, the minimap stays completely black until the next restart of the HU.
[Android Head-Units] ab1702:
Im using version 3.310 and I’ve lost the use of the speed widget it just stays blank or shows - .

I’m guessing there’s some sort of gps bug after experiencing this and reading a few of the posts above.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

3.312

After 10 hours running playing Mp3 player (Blackplayer),

the Volume widget was no longer displaying, and the volume had dropped from 8 down to 4. Very strange !!!

Selecting different quickplayer was still working corrected :) Maybe that issue of them locking up after time was fixed by fixing memory leaks .

Re-starting FCC with the FCC re-start widget, restored the volume control widget.

I have noticed many time, that when running, or from re-start, widgets will sometime not display, or get corrupted (parameters change). In the past, only easy solution (apart from re-editing them to correct them), was to restore FCC settings.

This time, when the Volume control was lost from the Home page sometime during the 10 hour overnight run, a re-start of FCC brought it back.

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

As far as what is the Active layer after a re-boot (ie non selected), I realized that recently I had turned off starting a specified app on re-start (I use to have the Blackplayer selected).

Will try turning that back on again, and see if I get a selection of a player after a re-boot.

But all in all, 3.312 seems to be an improvement over previous recent version -- (probably mainly due to the memory leak fixes ?)

Of concern still are the loss or corruption of widgets over time.

As a user, I imagine that a possible reason may be corruption of the FCC database, which is corrected by restoring settings.

When I had FCC running in emulator, I did see some database warning/error messages, so maybe that would explain widget changing of disappearing ??

Wonder how possible it is to get a 10 hour Logcat in verbose mode ? It will be BIG.

But if it could be captured, them maybe searched for Database relater error ?

Anyway, starting the car this morning with FCC still working after 10 hours running overnight, with 3.312 was something I have not seen happen before with earlier versions-- so good progress.

---------- Post added at 13:01 ---------- Previous post was at 12:19 ----------

SUNSET is working correctly as well.

[MENTION=4292729]SpeedFire-[/MENTION]

Since the widget knows if it is Sunrise or Sunset that is being displayed, and displays the correct Icon, please could the Notification also say either Sunrise or Sunset accordingly, and not "Sunrise / Sunset" for both case.
[Android Head-Units] liamstears:
[MENTION=4292729]SpeedFire-[/MENTION]

Feature request, well more of a tweak

I use internal TPMS sensors and they are great to let you know when you have a leak or an issue and to give a general idea of pressure in the tyres but they are not 100% accurate

Would it be possible to add a correction option per tyre? for example If I set both front tyres to 35 PSI using professional gauges 1 tyre might say 33.9 and the other 35.8 so it would be nice to add a manual correction of +1.1 PSI and -0.8PSI respectively to give a more accurate overall reading?

Hope you can help, good work lately massive improvements in the last beta's :good::good:
[Android Head-Units] SpeedFire-:
Alpha 3.313:

- Access to databases is done in more reliable way (but not completely, need to test if this is enough).

FCC Alpha 3.313
[Android Head-Units] LinkseD:
Unfortunately Minimap isnt functioning in this Version, too.

GPS seems to be broken since .10

My radar warner app and sygic navigation are working fine.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Version: 3.313 Big Improvement in Quickplayer Stability

Seems to have stopped the FCC Restart Loop when one has run FCC Restart widget. :good:

That, and the recent memory leak fixes, and Database access changes, seem to have made FCC a lot more stable. :)

Since the introduction of remembering the 4th player (if another Quickplayer is selected, or after a re-boot), there was, and still is an issue when re-booting or re-starting FCC, -- The currently playing Player is not shown as being selected in the QuickPlayer list, and at least initially the 4th player is missing.

(see recent Videos of this )

FCC seem to recognize this, and "finally" added back the 4th player, but until the user has messed about selecting all the Quickplayers in turn manually, the operation and display of Quickplayers is faulty.

Once a few selections have been made, all settles down.

Maybe, during the time of memory leaks, and database issues, a lot of extra code was added to try to fix this, that may be redundant, and just causing extra confusion now.

If FCC always knows the current Quickplayer, and also know if 4th player widget option is selected or not, present or not, what that 4th player is, and that is stored successfully in database, then after a reset, it should be straightforward to make sure that that state is restored, without a lot of having to cycles of re-starts etc.

In earlier version, when the 4th layer was removed if another player was selected, the above was not an issue, and FCC always re-started, or system re-booted showing the correct formerly running Quicklplayer.

Having the recently added feature of remembering the 4th player is good, but the bug introduced when this was added, (while there was memory leaks & Database issues), hopefully, could now be fixed.

The priority to fix this is not so high (at least to me), especially if there are more pressing issue, like GPS and MiniMap function that may have recently stopped working.

Temporary fix, is to go through and make a few Quickplayer selection after FCC starts, to get it running smoothly.
[Android Head-Units] tonimontoia:
km don't even work on this version, players do their own thing, change by themselves
[Android Head-Units] SpeedFire-:
Alpha 3.314:

- GPS functionality restored (sorry for that bug)

FCC Alpha 3.314
[Android Head-Units] jun81:
error during restore

[MENTION=4292729]SpeedFire-[/MENTION]

Alpha 3.312

encounter "something went wrong, re-setup." during restore.

log and backup attached.

hope it help to get the bug

thank you for the great work
[Android Head-Units] 007matman:
Glad it is working for you.. just because I'm not getting the same result doesn't mean that my issues is invalid. It's still an hour off.

I just stopped using the widget and changed to the temp widget instead.

However, I think there is still an issue here with the software that you should take a deeper look at.
[Android Head-Units] whitewolf8111:
I had this problem on 3.313 too (still need to test 3.3.14). I had to do a full restart and then it was able to restore.
[Android Head-Units] Scopesys:
MiniMap no longer switches between 2D & 3D .

Stuck in 3D mode

Been like this for quite a few updates... not sure when it got broken.

(North UP / Direction Up works fine )
[Android Head-Units] bossman4:
On my Eonon Unit

3.314 Works much better, including Amazon Music when the using downloaded music.....

But still

When I have FM Radio as the first choice on Quick menu, it still goes back to the FCC main menu, instead of staying on the Quick Menu screen and displaying the radio information text in the circle. When it switches to the main menu after I pick the radio choice button, I am getting a quick transient warning about an overlay permission not working on the main menu (sorry about the poor photograph). Afterwards, I can then roll back to the Quick menu page and the text is correct.

I am wondering if the inability to do the overlay is causing the Quick menu to pop back to the main menu when I pick the first choice FM Radio.

Now that I think about it, when I substituted Amazon Music for the first QuickMenu choice (and it is already running in the background) instead to the FM Radio, it does not bonce back to the Main Menu, so It seems like the FM Radio is the problem.

In doing all this testing, I have lost track of all the Bluetooth settings. Scopesys, I should have the same setup as you. What are your FCC Bluetooth settings?
[Android Head-Units] SpeedFire-:
Btw, how is the latest version in terms of unexpected launcher restarts?
[Android Head-Units] Scopesys:
3.314 s a lot better, but a few months ago, FCC never seemed to do all these restarts.

Is it know WHY FCC is doing re-starts ?

ie

Are they Intentional because FCC has to do them for a good reason

or

Are they because FCC gets an Error, and thinks it has to re-start to clear the error.

It seems to me, looking at FCC as a user, that FCC is doing most of these re-starts when it is coming out of sleep, or a re-boot, and determines that something has been initialized incorrectly, and is attempting to correct it.

ie Incorrectly initializing the QuickPlayer state -- wrong or no player selected, when there is a player playing.

The Good news is that Long term stability seem to have been restored... I have had FCC running all day, playing BLackPlayer, and no widget corruption, and all control work, including Player changes.

@ SpeedFire- Thank you for all your updates and time spent on fixing this re-start issue.

The remaining issue is still the chaos after a re-start or re-boot, that requires extensive Player switching by the driver to get sorted out.

---------- Post added at 16:51 ---------- Previous post was at 16:42 ----------

WEATHER WIDGET.

(a) Https:// is all that is view-able in the Get an API key section of settings

(b) Please add option to switch to 12 hour time, with AM / PM

This will make it a lot clearer is it Sunset time or Sunrise time, and if it is time till these events, no AM or PM (as it is not a time, but rather a number of Hours:minutes)

(c) Minutes should have leading zero. Hours too, but not so important.

ie 4:5 >>> 4:05 Am or 4:05 Pm
[Android Head-Units] bossman4:
What restarts? I was doing the testing over about a 45 minute time period. None that I detected. Just the warning about overlay, that I mentioned earlier. I was just playing with quickplayer.
[Android Head-Units] rigattoni:
Great job [MENTION=4292729]SpeedFire-[/MENTION]

I don´t have any resets, the app runs stable even after reboot and after some hours of playing in background. No GPS issues (I had no before too) and switching between players is working smooth and the widgets are working fine....at least on my bench unit.

By the way.... did you do something on the widget icon size?
[Android Head-Units] Scopesys:
Currently, (for some) re-starts occur after a re-boot, or after FCC is restarted using the "FCC Restart Widget"

If FCC is up and running, and the current Quickplayer are all running, and can be switched between, the re-starts now are very rare (if at all), even if FCC is run for hours.
[Android Head-Units] Scotttyz:
Amazing work!!

First off, great Launcher! I purchased this after just a little playing around with other launchers. I love having the google maps mini on all the time. I read probably the first 80 pages of this thread and you all convinced me to spend the money as soon as I downloaded it, kudos to the whole community on this thread.

I have a Dasaita 10.2 universal PX6

MTCE ver 3.37

MAX 6 3399 9.0 ota

Not rooted

My one issue so far: I have tried a few full boots and I still get "setup google assistant" every 30 to 45 seconds, if I do a full setup on assistant I get constant assistant interruptions while talking, while doing nothing. Any thoughts?

Thanks all!

Scotttyz
[Android Head-Units] TYourdog:
ATOTO

I set FCC latest alpha 3.314 settings to control my ATOTO A6Y with the ATOTO device type and noticed the volume is increasing/decreasing with the auto volume, but the numbers at the bottom right are not changing. When the device type is set to Android Phone or tablet it all works properly.

I also noticed with the auto volume, when on the interstate the volume increases normally but when slowing down to stop the number actually drops lower than what it was originally set to. I realize the decrease speed setting (Delta) would affect that but is there a way to prevent it from lowering the volume less than what I originally set the volume to?

When using the mini map, I have it set to Mapbox Offline with API key, with downloaded mbtiles, and the navigation app set to Google maps MiniMap. When I try setting a route I get 2 messages: first says "Building route" and the second says "Exception: Cannot parse routing response." Any ideas?

Lastly when using MiniMap is there a way to prevent screen going to Screensaver screen? I have it set for 60 seconds sleep when it's during night hours but I'd like to have some extra control to prevent it from causing the screen to go to sleep when a route is made. Is there an option that I am overlooking?

Thank you!
[Android Head-Units] SoberXDA:
If I may suggest this, I would prefer that the 4th player is not restarted. I think the idea behind the 4th player is that it is a player that is used ocassionally (like chrome or youtube) and not on regular basis.

The issue I see is that FCC tries to restart youtube, but as youtube starts with the home screen instead of playback screen, FCC is not able to start the playback and falls into a loop.

It would be ok for me if FCC starts (after a restart or a wake up) with the 4th player not shown at all.
[Android Head-Units] piercedpanda:
My iPhone 8 Plus on IOS13 seems to have difficulties connecting to my Pumpkin unit running FCC Launcher.

It takes longer to connect and somehow it doesn't connect the first time around.

Toggling wifi on and off on the headunit and Personal Hotspot on and off sometimes does the trick.

Sometimes it doesn't work at all.

Anyone else experiencing these problems?
[Android Head-Units] LinkseD:
No problems here on my 11 Pro Max with iOS 13.3 Dev beta.
[Android Head-Units] bossman4:
Speedfire

I took a better picture of the exception that has popped up since the latest alpha. I got the exception to be more consistent in popping up under certain keystroke sequences in the quickplayer choices.

The wording of the exception is 'canDrawOverlays' permission is not granted

I ended up picking the FCC 6th alternative communication protocol for the Bluetooth/Phone on my PX5 Eonon. This in combination with the installation of the missing Google communications APK (bad move by Eonon) now permits me to use the synchronized Google Contact list for by phone needs rather than the device phone list..
[Android Head-Units] SpeedFire-:
Ok. I need some additional details:

- What does not autostart after wake up? Player? Third party apps? Something else?

- What device do you have (PX5 or earlier versions)?
[Android Head-Units] TT_Vert:
I have an MTCB you had fixed it before for me. It's an app in autostart (The only app) called YaV1.

Dave

---------- Post added at 02:34 PM ---------- Previous post was at 02:27 PM ----------

To refresh your memory maybe. Here is where you fixed it.

Dave
[Android Head-Units] Roerbakeitje:
I have the app Next Song . It gives me notifications of the song titel of spotyfy , mp3 pcrsdio enz in a simple notification with controle next play pauze enz.

Maby somthing for fcclauncher.

Now i can also control the music outside fcc
[Android Head-Units] SpeedFire-:
Here is a new beta with some (old) fixes:

- Attempts to fix OBD2 widget

- Backup is now created in a separate Google Drive folder FCCLauncherBackup

- Rotated album art (doesn't work very well)
[Android Head-Units] pa.ko:
Just small issue noticed: switching from Music player (stock) to Radio, in widget the album art image from Music is shown instead default radio icon (microphone).
[Android Head-Units] SpeedFire-:
Thanks. Tried to fix this in the latest beta.
[Android Head-Units] TT_Vert:
Let me know if there is a fix I should test for the auto start apps not starting on sleep again.