yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
New alpha 3.302

No visible changes, but that problem with "corrupted database" worried me a lot. Because I had the same "corrupted database" issue with the latest backup from [MENTION=9325785]Scopesys[/MENTION] as with the previous one.

Since backup/restore function is very important I investigated this issue and fixed it.

The problem was with SQLite databases which normally produce additional "journal" files containing some unfinished transactions. When existing journal files didn't match with a restored core database file SQLite thought that the database is corrupted and deleted it. Now launcher clears all the existing journal files before restore. This fixed the issue for me.

FCC alpha 3.302
[Android Head-Units] Scopesys:
Good news.. I'll update to 3.302 and then do a new backup for you, which I will post in about 10 minutes.

Note: Whenever I restored from my previous backups, they all "seemed" to restore reasonably well, but in hindsight, sometimes some of the widgets setting seemed to get messed up, in a random way, and I had to re-edit them.

Maybe this latest fix will correct that.
[Android Head-Units] SpeedFire-:
No need for a new backup. Your previous backup files work pretty well on 3.302.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

10 minutes turned into 1 hour.

Updated to 3.302, all looked ok.

Re-Boot - all still OK

Backup setting. Restored settings

Almost all FCC Widgets had lost their background color and Text colors were all set to a default Blue :(

Did a 2nd restore, and all the background colors came back.

Video showing issues with 1st restore, corrected by 2nd restore

https://drive.google.com/file/d/18FPeDIgxdQAtsAQqBtfMNGfycbt9PhkG/view

Unexpected (at least by me)

Attached is that FCC settings backup. Hopefully the database is not corrupted since it was saved with 3.203
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Got significant improvement with FCC 3.302 by completely uninstalling FCC (even though I was updated to 3.302), cleaning out all references to FCC I would find on my unit with file browser app, re-booting Unit, and then doing a Fresh Install of 3.302.

Then restoring by previously save FCC setting, saved when I was updated to 3.302 earlier.

The restore went 100% successfully -- no corrupted Widgets, and need to do a 2nd Restore like earlier (Video)

Text starts to scroll smoothly a lot sooner now ... so looking good.

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

Still believe there is an issue with the Bluetooth WIdget.

If I have a Bluetooth connection and then re-boot, when FCC starts up, I see that the Bluetooth Icon is indicating the CONNECTED Icon, but there is no text.

If I then disconnect Bluetooth, the Icon changes to the Non- Connected , and it display "No Connection" (as expected)

But when I then re-connect Bluetooth, the Icon Changes to the "Connected icon", but the Text Continues to say Not-Connected.

Text should have changed: - to "Connected", (To be in sync with the ICON), and then maybe, if it has managed to get a name, display the name instead of the word "Connected".

(BTW: Also tried removing Widget, and then put a new copy of the widget in it's place.. no difference)

That being said, (for me) 3.302 seems to be more stable than any recent Beta, so might be a consideration for Play Store distribution.
[Android Head-Units] SoberXDA:
In latest beta, the launcher restarts itself quite often... Say I want to navigate in the minimap and the whole launcher usually gets restarted. Finally I get it to navigate after 3-4 tries...

PS: what do the 3 dashes (---) that show when navigating mean? Shouldn't it show your ETA?

The player widget is (as always) showing the music art quite randomly... sometimes it even shows some road signs instead of the music art (?)...

To be honest I don't see much improvement in the new versions... Or maybe I should do a fresh install of the launcher as some people above do?
[Android Head-Units] jukk:
Is there any way to increase the font size of the speed reading in the status bar? It is incredibly small.
[Android Head-Units] SpeedFire-:
What Android OS version do you have? And what device?
[Android Head-Units] SoberXDA:
Its an Erisin unit (4GB RAM, 8 core version) running Android 8.0 HAL9K ROM.

I can try to record some logs if this helps.
[Android Head-Units] SpeedFire-:
Yes, please record.

I agree that we still have issues with reboots, but normally not constant reboots.
[Android Head-Units] AdekP:
ETA should be like that there, but there is a problem displaying it from Google Maps. When you switch the minimap to Yandex, ETA appears. I reported this problem to the creator, but so far he has not referred to it;)
[Android Head-Units] SpeedFire-:
ETA is not available for Google Maps. I just need to hide this panel completely (it was added for Yandex).
[Android Head-Units] TheSalko:
Idea. Sometimes I forget my phone at home. Could the FCC alert me?

I tried to do this via TASKER, unfortunately on my radio (Xtrons PB88UNVP) I can't find out if the bluetooth device is connected. My phone is still reporting paired and disconnected (in TASKER).

For example, 15 seconds after start / wake up, the FCC would detect if the selected phone is connected and if not, it will throw a notification.
[Android Head-Units] SoberXDA:
Hello! See attached. Hipe I did it correctly ;)
[Android Head-Units] Super_paulie:
Are you familiar with KWGT? you can create your own widget to do that function and then then add it to FCC. Might be the only way to get it how you want it.
[Android Head-Units] SpeedFire-:
Beta 3.303 is uploaded to Play Store beta channel:

- 4th player in player widget does not auto-hides

- Added a separate active/inactive icon colors for BT/WiFi widget

FCC beta 3.303
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Many thanks... I did not expect that before you released the next version to Play Store. :)

Both changes work 100% ....

I still have a problem with the Connected Icon having text Not-Connected. but the Icon is right, so I have for the time being just removed the text (same color as Background), and now it "appears" to look correct.

ie Both Bluetooth_On and Bluetooth_Off Icons work correctly, but the text is always not Connected, and the Icon color is always the NOT-Connected color, and the NOT-Connected text.

Maybe later, this could be looked at again, but it would seem to be a low Priority, as the Bluetooth Widget Icon works correctly as far as Image shape is concerned, so is now quite usable.

ie from the Shape, one can tell if Bluetooth has a "connection"

The two major issues I experience with FCC still are

(a) Numerous restarts

(b) After a boot, a long time for FCC to settle down and respond consistently to UI. (what is it doing for so long ?????)

However, once it has settled down, and the 3 (or 4 Players) are established & working, it is quite stable, with few if any restarts.

For reference, the numerous restarts seems to start occurring about the time you added the alternative MiniMap, but a lot of other changes were also being done around that time, so it was probably not the Minimap.

---------- Post added at 01:49 ---------- Previous post was at 01:27 ----------

Thanks :- I Played about with KWFT about 6 months ago, but most of the functions I wanted to implement required that my Head Unit was rooted, so I decided the easiest thing was to STOP wanting those extra functions !!

Would like to find a Non Play-Store app, that one could run at restart (or on demand) that gave specified Accessibility Permissions to specified apps.
[Android Head-Units] AdekP:
I started using the Yandex minimap (with API key) and it works very well (navigate the minimap). It looks much better than the Google minimap.

Thank you :)

The only thing I miss is the display of traffic without a route ...
[Android Head-Units] SoberXDA:
Can you direct me on how to obtain the correct API key? Is it the "MapKit Mobile SDK" free version?
[Android Head-Units] SpeedFire-:
Yes. MapKit SDK key is required for Yandex. Can be requested here for free: Link
[Android Head-Units] SoberXDA:
Ok, so that's the one I've tried yesterday. Didn't get it to work, maybe will try some more later...
[Android Head-Units] SpeedFire-:
It needs some time to be activated.
[Android Head-Units] AdekP:
Strange. I downloaded Yandex from google play, obtained the key API and it works
[Android Head-Units] SoberXDA:
Is the Yandex app mandatory for the minimap navigation?
[Android Head-Units] SpeedFire-:
Not required. Just select "MiniMap (Yandex)" in the list of navigation apps.
[Android Head-Units] rigattoni:
If your unit is rooted, I would have one. ;)

Needs to be rooted, and Tasker incl Secure Settings needs to be installed.

Secure Settings needs to be activated.
[Android Head-Units] riccardone1:
my mini map doesn't auto center and disappears from the map when I'm moving. I always have to click on the north compass to center the arrow. Does it happen to you too?
[Android Head-Units] Scopesys:
Thanks ... I tried going that route some time ago, but was not able to, as my HU is not rooted. So never mind, on the few occasions that I have to enable it, I have to do it manually.
[Android Head-Units] rigattoni:
It was driving me crazy that Android does not store the accessibility settings since Android 9.
[Android Head-Units] Super_paulie:
Was there a resolution to this? Asking for a friend, looking for the radio names or frequency to be displayed.

---------- Post added at 08:32 PM ---------- Previous post was at 08:26 PM ----------

I use tasker to do this exact thing. Got it attached to a button that I click, or you can set it to autofire on an event. If you have tasker I can help you out?
[Android Head-Units] Scopesys:
I believe I need ROOT access to be able to do this with Tasker ?

( Oreo Android 8.0)
[Android Head-Units] Super_paulie:
I'm on an Atoto, Android 6 and you dont need root. See attached for how I start the accessibility service for AutoInput app.
[Android Head-Units] Scopesys:
Looks ideal -- thanks -- (did not know about this one :) ) ... lots of thing I may now be able to automate, making it a lot easier, especially when driving :good:
[Android Head-Units] riccardone1:
what a disaster this car launcher! I lost many hours configuring it and when I thought I had finished after two reboots many icons disappeared. The mini map does not keep the position centered at startup. I did a restore of a rescue and it was a disaster. I lost all my work. We still have to work on it a lot
[Android Head-Units] surfer63:
On Android 7.x and up that doesn't work anymore. You need to be root to activate that. Once activated you can remove root again.
[Android Head-Units] SpeedFire-:
Sorry to hear that. What app version did you use?

I try to catch that bug, but this is really hard to reproduce it.
[Android Head-Units] riccardone1:
I'm sorry too, the application has a lot of potential. I use the latest official version of the Play Store
[Android Head-Units] SpeedFire-:
If you still wish you can try the latest betas and check if this issue is fixed or not. I haven't had such complaints about the recent betas yet
[Android Head-Units] SoberXDA:
Speedfire, did you have a chance to check the restarts issue? I've posted some log files on Monday. I've noticed the issue gets worse when an other application works in overlay more. Maybe that is a clue...
[Android Head-Units] Scopesys:
I must have done at least 50 FCC settings backups and restores over the past year, and NOT ONCE did the restore not work. Sometimes, if FCC had been updated since the last settings backup, the restore had to be done TWICE, as the 1st time, some widgets failed to fully restore, but the 2nd restore ALWAYS corrected this.

Bottom line, you should not be loosing all your settings and having to re-create all your screens again.

But yes, if I lost all my settings after many many many hours of creating screens, I would be very frustrated as well.

The good news is that is is unlikely you have really lost all your hard work, if you have that settings backup.

I would suggest you might like to post that Backup on the forum.

Maybe Speeedfire- would find it of use, and I would be more than happy to test that backup on my system, as I am confident that after that, I can always get back to my settings with my backup.

At least if you get confirmation that your Backup is good, then it's just a question of getting FCC sorted on you HU, and you will have all your hard work of creating screens back.
[Android Head-Units] SpeedFire-:
Fighting restarts is the top priority now.

Please try this alpha:

FCC alpha 3.304

In emulator I had no restarts. If anyone (@ScopeSys?) will still have restarts on 3.304 and could reproduce this in emulator - this would be nice (I need steps to reproduce).
[Android Head-Units] v1ck:
Hi. I recently tried your fcc launcher and it looks great so far. Is it possible to configure hibernate options? I have navi app which shows traffic, accidents and police etc. It has a floating widget when running in background. Is it possible to prevent it from closing while hibernate or force to go to the background on autostart?
[Android Head-Units] SpeedFire-:
You can set this app to autolaunch in FCC Settings and then set Go Home action. This will put this app in background.
[Android Head-Units] whitewolf8111:
Once in a while, with 3.304, I still get restarts on wake while it's loading everything (I do have tasker do a few things on wake). I don't have an emulator setup but I think I was able to capture it with the attached logs. It definitely did it on the larger log, just not sure if it captured anything that you can use.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION] So do I, but it's a lot better than previous versions.

Very few... much improved.

I had Android Studio running, but something got messed up ( I probably changed a setting, and cannot determine what I need to set back), so I intend to completely re-install it.

Before I do, can you tell what Device Model you typically use, and if it is one with Play store already in the image, or if not, if you added Play Store.

Unfortunately, I cannot find a Device Model that is 1024 x 600, with Play Store, to closely match my Eonon Px5 Head Unit.

[MENTION=4292729]SpeedFire-[/MENTION]

FYI

I appreciate the FCC re-start issues are top priority at the moment, but in recent version, the FCC RE-BOOT widget has started not to work as expected.

ie Sometimes it does NOT do a re-boot, and has to be called a 2nd time.

Another time, I was in MiniMap, on the editing (deleting routes screen) and when I tried the RE-Boot, it would never re-boot, but just brought me back to a BLACK screen, with my Route Icons displayed. I had to get out of that screen, before the FCC RE-Boot widget would work.
[Android Head-Units] riccardone1:
is there a solution regarding the arrow of the mini map that does not remain in the center of the screen when the launcher starts? All the time I have to click on the north compass to reposition the arrow correctly
[Android Head-Units] SpeedFire-:
Mainly I use Tablet 1024x600 without Play Store integration on Android Pie.
[Android Head-Units] SpeedFire-:
Which map do you use and what app version?
[Android Head-Units] Scopesys:
Got FCC 3.304 running in Android Studio, almost acting as it does on my head unit.

Made a Video of the Android Studio showing the Logcat & The Emulator running together, with a clock on the FCC screen, showing time down to seconds... so you can clearly see what is happening on the FCC Screen and read the LogCat at the same time, pausing the video for more detailed examination.

(Best viewed in 1080P)

https://drive.google.com/open?id=1yh3Q3xPlbPDt6-1JSKXanHNm0AADnW6o
[Android Head-Units] riccardone1:
does it with google map and mini map. I use the 3.220 version
[Android Head-Units] SoberXDA:
For me this version is definitely more stable. I've seen a few restarts here and there but not so often. I've done a fresh install of FCC and it seems even more stable. Will test some more.
[Android Head-Units] SpeedFire-:
Here is a further optimized version 3.305:

FCC Alpha 3.305

Please test
[Android Head-Units] SpeedFire-:
Can you try the latest alphas/betas?
[Android Head-Units] riccardone1:
yes, sure
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION], are there any plans on getting it working with FCC?

By the way...

Would it be possible to change the size of widget icons as BT and WiFi?

Just now you only can change the size by widen the widget. Unfortunately the smalls are too small and one size bigger they are too big.

View attachment 4861741View attachment 4861743
[Android Head-Units] SpeedFire-:
Alpha 3.306:

Another MASSIVE optimization of initial widget drawing, resource management and multi threading.

FCC Alpha 3.306
[Android Head-Units] bossman4:
I have a new Pumpkin single Din running Android 9. Both the radio and the Bluetooth do not work either and there does not appear to be a Radio APK to add back. Here is a picture of the system setup
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Alpha 3.306 is a good improvement as far as switching between QUickplayers, and is very reliable once each Quickplayer 1-4 have been selected at least once.

However, after a FCC restart, or a Re-Boot, FCC does not seem to be able to come back to the same stable operation of the quickplayers.

It seems to have trouble remember which quickplayer was running before the restart, and often will not show any quickplayers as being selected, even if a player is playing.

Also, after just a restart, FCC often looses the 4th player selection.

To reproduce.

Run FCC and set a 4th player.

Make sure you can switch between all 4 players, in any order, and both player, text & artwork correctly update.

(At this point all is working Very well)

THEN do a FCC restart.

4th player randomly gets lost, and often none of the quick players are selected, and one has to select each in turn, and get everything "synced" up again.

Expectations are that after a FCC restart, and also ideally after a re-boot, that FCC has remembered its Quickplayer setting, and restores everything to the same state it was in before the Re-Start or Re-Boot.

I assume that each player will need to get & refresh its Text & Artwork, as soon as the player starts running, as during the rest/reboot time, the current one might have changed, especially if the source is from a live stream.

Currently, it does not seem to do this, until the NEXT song is selected, or the player is changed.

Note My FCC setting are set to

Do not kill apps on re-start

Do not force load a player.

Do not load last running app
[Android Head-Units] bossman4:
My Eonon

My good experience with the new version is speed and more consistency. I have a separate menu page for the Quickplayer on my unit.

Choices 1) Radio 2) Blackplayer 3) FM Tuner (Podcast player).

Both media players seemed to work fine and changed the artwork (little stutter every once in long...while), but when I picked the radio, it went popped back to the main screen. The artwork changed correctly to whatever the radio shows in the middle circle. When I clicked back to the Quickplayer menu screen, the art was ok.

I have moved Amazon Music to just be an app choice. When I do bounce back to the FCC menu screens after starting and using Amazon Music, the Amazon artwork is present on the FCC main menu screen and the Quickplayer screen. Of course, it goes away when one of the Quickplayers are chosen. So Amazon is storing artwork in the right place and FCC is displaying it correctly. When all this other work gets straightened out, I might try it as a Quickplayer choice.

Pumpkin Android 9.0 single DIN Unit

I reinstalled the Pumpkin system Software that was sent out as an update. This caused me to rebuild the whole radio over again. (WIFI, APPS, Logins) Had a bit of a time trying to bounce out of FCC setup to do a quick restore. Did not seem to be an easy off ramp from the previous incomplete FCC setup to restore the menus from an earlier backup on an SD, but when I finally got to the right place, it went smooth on the restore. It appears that you need to redo the Quickplayer list after you reinstall the player software (even though the setup menu looks like it has the correct choices. The new Pumpkin system software is faster and the same FCC behavior was noted as the EONON, except there is still not a FM Radio APK to point to on the Quickmenu. (see other post).
[Android Head-Units] SoberXDA:
I don't think that those issues are specific to the latest alpha, right? The player widget was never been flawless in any version. Especially when it comes to how it reacts to unit restarts or switching between players.
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] I'm still getting the occasional restart on wake with 3.306. I have even had a few crashes that I haven't had with the last few versions until the 3.306 version (didn't try 3.305), and was able to (hopefully) capture a crash and a restart or 2 with the log labeled FCC 3.306 Log. There are also a some restarts in the other 2 Logs that I made while running 3.304
[Android Head-Units] SpeedFire-:
The crash is not in the launcher (according to logs) but in some app com.e39.ak.e39ibus.app.

This app should be updated. It should include a command "startForeground()" when launched on a newer version of android.

The crash:

11-01 00:14:22.771 1584 1584 E AndroidRuntime: FATAL EXCEPTION: main

11-01 00:14:22.771 1584 1584 E AndroidRuntime: Process: com.e39.ak.e39ibus.app, PID: 1584

11-01 00:14:22.771 1584 1584 E AndroidRuntime: android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground()

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1775)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:105)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:164)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6541)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)

11-01 00:14:22.771 1584 1584 E AndroidRuntime:	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:108)

11-01 00:14:22.772 1584 1584 E ACRA : ACRA caught a RemoteServiceException for com.e39.ak.e39ibus.app

11-01 00:14:22.772 1584 1584 E ACRA : android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground()
[Android Head-Units] surfer63:
I am switching from CWG to FCC, or at least investigating that thoroughly, and I know that many users ask "can you add this..?", but I'm still adding another one. ;)

The minimap allows for some navigation apps like Google Maps and Yandex.

I use (open source) OsmAnd-plus (the -plus is the donation version). Osmand comes with an API that can be used from other apps. It has a small demo app on github. That can be used with both the free version (net.osmand) as well as the donation version (net.osmand.plus)

I assume it cannot be integrated in the minimap? Or can it?

But could it be used to use Google voice to start navigation using the NAVIGATE and NAVIGATE_SEARCH commands? (readme.md from github)

In that case you do have support for an OSM based offline navi app as well.

(Using a decompiler I could find 3 string occurrences of net.osmand.* but it wasn't clear to me what they do)
[Android Head-Units] whitewolf8111:
Okay, cool thank you. I will let them know.

Did those logs help at all with any restarts?
[Android Head-Units] Super_paulie:
Can anyone tell me if this Google minimap behaviour is normal? Even when i drag and move it still pulses in and out. Also the ETA will be removed soon, i know that has been mentioned previously.

Also are the Google minimap and the actual app Google maps not linked?

Cheers

https://vimeo.com/370294553