yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
The two sides, being darker, look more like the Unit has a basic backlight issue, and the lighting is not evenly distributed over the whole screen.

FYI: I decided on a 100% Black Background, so I used a custom Background, generated in Photoshop, with color &H000000 = 100% Black. (1024 x 600 Jpeg)

The Dark Grey one that comes with FCC is however, far better to see any problems in Backlight Lighting, as the Dark Gray would seem to get Darker towards the sides on your unit.

Attached are two Background files. A 100% Black one and a Dark Grey one.

If your unit uses actual CCFL tubes, and not Led, then such end darkening is possible, as over time, both ends of the tube can blacken, causing exactly what you appear to be seeing. This is yet another reason why LED backlighting is so much better.
[Android Head-Units] Scopesys:
Currently at a loss as to why I can do a Clean install of 3.155 and all is OK, but a clean install of 3.158 or 3.159 fails to install correctly or run, just keeps saying FCC has stopped running, each time I try to run FCC, Never goes through the setup on install.

3.155 Installs 100% OK from a Clean Install.

My definition of Clean Install: (Brute force, overkill !! )

(1) Uninstall FCC

(2) Clean cache.

(4) Run Kill Aps

(5) Full Re-Boot

(6) Clan Cache

(7) Run Kill Aps (again)

(8) Full Re-Boot

(9) Install current 3.159 from Play Store

or 3.158 from my Google Drive

or 3.155 from my Google Drive (works)

Seems very strange and unlikely -- so will make a video to prove and show what happens when I try a clean install of 3.159

BTW: The 3.159 on PlayStore and the one you put as a link to your Google drive, have EXACTLY the same number of Bytes, so are most likely the same .

Will try again in the morning (Saturday East Coast USA Time)

---------- Post added at 04:44 AM ---------- Previous post was at 04:34 AM ----------

Not sure why the White Paper. The only post I can recall I made about white paper in front of the Screen was on the Honda CivicX site, taking about reflections on a non OEM Head Unit in a Honda, and how the way Honda mounts the unit, pointing up at an angle towards the dark internal roof of the car, minimized screen reflections, that could be significant if the screen pointed to a light surface, especially if that white surface was strongly illuminated by sunlight.

You appear to be looking at the screen Through white paper ?

No matter .. maybe try the dark-gray background file I posted earlier.

It could be that the darkening effect is less apparent on your Default Launchers background blue color, than the FCC dark gray background ??

Attached is a 1024 x 600 Dark Blue Background, about the same color as your default Launcher's background (as photographed in your uploaded image)
[Android Head-Units] jostor4713:
I honestly do not remember where I read it, but I am sure that you were the author. Thank you very much for the advice.
[Android Head-Units] Xorit:
Did a clean install on BlueStacks emulator, just to see if things are working.

- Went through the initial installation of FCC, enabled every permission asked for.

- Installed Amazon Music.

- Album Art is displayed in the notification bar, but not in the widget, like in the car. (btw: PX5 device, Malaysk Android 6)
[Android Head-Units] Scopesys:
No problem -- hope the 3 background Images help you track down where the problem might be coming from. :confused:
[Android Head-Units] SpeedFire-:
3.160 is available via Play Store. Please try it.
[Android Head-Units] sbruda:
Last update screws the pooch big time for me, as in force closing immediately upon launch. This is not acceptable even for a beta version, so could you please look into this. Many thanks.
[Android Head-Units] SpeedFire-:
Are you sure you are talking about 3.160? It was just uploaded and I don't see any crash reports so far. Can you record a LogCat log?
[Android Head-Units] Scopesys:
3.160 crashes for me as well as soon as it start to run after loading from Playstore.

100% sure it is 3.160

3.160, 3.159, 3.158 all do the same

3.143 installs fine & runs.

3.155 runs, but widgets do not bind. (warns you with a popup on install, but never ask to to select a widget, and enable binding, like 3.143 does.

So, currently 3.143 is the latest version I have saved, that will run on my Px5 HU.

I have Videos of this, but it is Basic what is happening.

Clean install of 3.157, 3.159, or 3.160 ALL do not run after loading, and attempting to setup. (do not have a copy of 3.158 but assume it is the same)

These issue seem to be since you started Allwinner support.
[Android Head-Units] SpeedFire-:
3.162 is sent to Play Market. However it needs some time to be approved
[Android Head-Units] sbruda:
It is the latest (updated some hour ago) so it must be 3.160 methinks. I can look into recording a logcat as soon as I manage to sideload a working launcher, but hopefully that will not be needed with the new version (thank you by the way for the quick response!).

For the record, this is the first version that does this; I have had no problem with any of the previous versions.

Almost forgot to mention: this is all on a Klyde PX5 MTCD running Malaysk's Marshmallow ROM.
[Android Head-Units] SpeedFire-:
Some crash reports were received. It looks like the issue is inside the Google's Firebase plugin which I updated to the latest version. In 3.162 I returned the version of this plugin to the previous one. I hope it will help.

Btw, I had no issues on emulator and PX5.
[Android Head-Units] rigattoni:
Same on my unit.

FCC is not able to start with 3.161 which arrived a few minutes ago....

So no launcher now. I need to switch back to an older version... :crying:
[Android Head-Units] SpeedFire-:
Just wait for 3.162 first please. It is in the process of approval
[Android Head-Units] SpeedFire-:
While Google is (slowly) approving 3.162 please check it manuall: 3.162
[Android Head-Units] nt7561:
Hi everyone! My name is Nick and I have installed the latest version of the launcher. Excellent launcher but I have some small issues. I cannot find the default radio app, music app etc. Also when I try to go to system settings through the launcher it keeps crashing. Any ideas. Find attached my unit's specs.
[Android Head-Units] SpeedFire-:
Hi, Nick. What is your device type? Rockchip? FlyAudio?

Issue with settings will be fixed when a correct version will be uploaded to Play Store.
[Android Head-Units] SpeedFire-:
3.162 is approved in Play Store please check how it works and tell here.
[Android Head-Units] Scopesys:
Relieved to know it's not just me, being a PITA.

On a positive note - having to revert back to the Default Launcher for a short time, just makes one appreciate FCC all the more. I'd forgotten how primitive the default launcher is by comparison.
[Android Head-Units] SpeedFire-:
Can you please check 3.162?
[Android Head-Units] Scopesys:
Sorry to say, same issue with 3.162 (fresh install)

After it installs, the 1st time it runs to go through it's setup, the first thing to display is the "FCC has stopped running" popup.
[Android Head-Units] EwaldB:
Dear SpeedFire,

I really appreciate your great work and I see a lot of potential in this launcher. But for now I have to go back to stock or to an other browser.

Being on the payed and/or beta version actual available I will no longer use it for my dayly drivings.

I also have the issues reported by others: delays and interruptions on using DAB-Z, the speed widget sometimes works, sometimes not, same for "showing street" widget. Issues which I do not have with stock launcher or HAL9K's ROM Launcher or Nova Launcher. I unfortunately do not have the knowledge and time to handle logfiles or replacing system files, which I know it may help to fix the issues.

Nevertheless I do not regret that I've paid for FCC because I'm sure it's on the right way to get an excellent launcher. And once in a while I will give it again a try to see how it evolved. And of course I will follow this thread.

Wish you success and a healthy happy new year!
[Android Head-Units] SpeedFire-:
This is awful. The error definitely says something about the Google Firebase plugin and I can't reproduce it on my device and don't know how to fix quickly..

Will try to find some solution

Fatal Exception: java.lang.NullPointerException
Attempt to invoke virtual method 'void com.google.firebase.perf.internal.zzv.a(boolean)' on a null object reference
com.google.firebase.perf.internal.zzd.zzc (Unknown Source:91)
com.google.firebase.perf.internal.zzi.run (Unknown Source:1)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
java.lang.Thread.run (Thread.java:764)
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

am out of town now will check out the new beta when I am back.

may i check which provider are you using for the street name widgets?

I do not get updates for the speed limit widget over here. it is always a empty red circle.

Thank you!
[Android Head-Units] SpeedFire-:
Source for Street names: 1) Internal geocoder 2) If not available or nothing found then OpenStreetMap

Source for speed limits: 1) OpenStreetMap
[Android Head-Units] Roerbakeitje:
Steering wheel controls has never be so good as now. Thanks.

Question. On Google Voice. I say *navigate to... *

It opens maps. Can it be Waze to?

And when opening FM radio in player widget I have almost no volume. When opening. Pcradio in widget it's ok. Than switch back to FM radio no sound. Only in background

Danny
[Android Head-Units] Petrovych:
Yes, but with some restrictions. You need to install Autovoice app which will intercept voice commands. Then you need to assign your favorite geopoints and

which app will be used to build a route to these points using a navigation link widget. Then you can command "navigate to home" or "navigate to my office" and the route will be build in the assigned navi app.
[Android Head-Units] bmccrary:
Just wanted to say THANKS for this great launcher! I have been wanting to redo my MTCB unit for awhile and saw this when I was looking for a better launcher. It is so nice to have all of the music players on one screen. Pandora support would be nice but I'm not complaining. I've never had much luck getting Pandora to cooperate with anything else period. I purchased the premium version and everything works really well. For anyone else using a KGL unit, I had to use mtc-keys xposed module and add this to mtc-keys.ini:

[click.1]
#disable mode button
action_2 = null
#disable bluetooth button
action_69 = null

so that the MODE and BT buttons would work without calling their native functions. I never could get the play/pause button to work (keycode 3) to work in the launcher itself but it never has really worked correctly anyway. I'm very pleased with the launcher and I'm sure a lot of hard work has gone into this!

---------- Post added at 01:52 PM ---------- Previous post was at 01:50 PM ----------

I wanted to add I tried the beta that was on the google drive, but no matter what media player I had open the next/prev buttons kept making the radio launch. The beta in the play store works fine though.
[Android Head-Units] B3rt:
How to install this on a MTCD PX5 unit? (android 6.0.1)

When i go to the play store my device is NOT listed, my other devices (android 4 and 7) are listed, but not my MTCD unit....
[Android Head-Units] SpeedFire-:
Thank you for your support! :)
[Android Head-Units] TT_Vert:
Hey you may have missed this buy was wondering if you saw something I didn't

Also, any idea if we can have safe volume actually be the new volume upon restart rather than have the volume go back up to what it was prior to shutting off car when you move the volume up one turn? IE, while car on it was at 15, turn car off and restart, now at safe volume level I set (3). Then if i want to go to 4 I turn knob right one and it goes to 15! (LOUD) rather than from safe volume (3) to next increment (4)

Dave
[Android Head-Units] pa.ko:
[MENTION=4292729]SpeedFire-[/MENTION]

Do we need mtc-keys to make SWC remapping in FCC Launcher working? (mtcb kgl 3188)

[MENTION=6016411]bmccrary[/MENTION] reported he got it working only by disabling these keys in mtc-keys. I don't like to have need for it.

Also, how to have remapping preserves default behaviour on single click (while having new function on double click)?

Is there a way to have arbitrary keycode remapping instead of fixed list? In list there are just a few keys, which most of them I don't have on the wheel (e.g. tuneup/down, stop... I have track next/prev, volume and BT Pickup Phone).

---------- Post added at 05:50 AM ---------- Previous post was at 05:40 AM ----------

[/COLOR [MENTION=4292729]SpeedFire-[/MENTION]

Song info works in widget for stock Music player in last beta. Any plans for cover image, please?
[Android Head-Units] TT_Vert:
You could just use MTC keys for all of key remapping also. That is what i've done.

Dave
[Android Head-Units] SpeedFire-:
No I haven't seen anything special. I just agree with your observations re Waze.

Actually I don't know why is that. I change the volume the way it should be done. I've read on 4pda that Chineese programmers made a mistake in the MTC code by preserving volume level in some local variable and not changing it when any other app changes the volume. I didn't find workarond yet. Any suggestions would be appreciated.
[Android Head-Units] SpeedFire-:
Ok. Let me clarify FCC's Key interception function in more details.

Some facts:

1) It actually does not 'intercept' the native function. It listens to the button press event (irKeyDown) and when find it - send FCC's custom event. BUT it does not cancels the native behaviour, it sends FCC's action AFTER the native behaviour. (However for Mode function it goes home which almost always kind of cancels the native behaviour).

2) That's why I selected a list of functions which do not do anything most of the time (for call accept and call hang out actions I save their native behaviour during call and cancel custom actions by listenting the BT state). However if you still need to cancel the native action entirely you will need xposed module. No other way.

3) These actions (selected by me to intercept) can be assigned to the wheel's buttons by your native MTC remapping tool.

Therefore you need to do the following:

1) Select some button on the wheel which will probably be entirely used for custom functions (single and double click)

2) Select some actions from a selected list of actions in FCC settings, which do nothing most of the time.

3) Assign these actions to a selected button by your native MTC remapping tool.

4) Select custom actions in FCC for single and / or double click.
[Android Head-Units] pa.ko:
Yes I know. But it has no UI for config and I hope to resolve everything with FCC which provides good UI.

---------- Post added at 09:35 AM ---------- Previous post was at 09:17 AM ----------

Thanks for details. Looks like mtc-keys is still required for most truly useful mapping. But I hate it's non-GUI config...

I hope we will discuss this issues more, as I believe we all together may realize better ways to have support for SWC mapping and overall usability.
[Android Head-Units] Petrovych:
I don't use mtc-keys at all. Furthermore I don't use any xposed module in my MTCB HU KLD A4.4.4 Nissan vehicle. So steering wheel buttons interception now works fine for me. I mean that when I press BT call ending button twice it leads to Google Voice app execution (nothing else is executed), on the other hand when someone is calling me I can use the same button to end the call.
[Android Head-Units] pa.ko:
Well, I tried BT answer button to map. But as soon as I single click it, I get into BT app. Second clock is then redialing the last number. So it is unusable. Did you tried with BT answer as well? What happens on single click of BT call end? Does it go into BT app (as answer does) or it just do nothing and thus you can map double click of it?

[MENTION=4292729]SpeedFire-[/MENTION]

Could you add action for 'Back' (e.g. Android back action, to get back from activity, cancel etc.) So it can be mapped to keys. I'm using Mode button to be attached to Back action in HU SWC config app. But would rather map that key into something else you support (e.g. tune up or whatever) and then map singleclick to Back and double click to Voice or whatever... That would be great, as I found that Back is one of the most used things in Android and very useful and for safety reasons 'a must've to have on steering wheel.
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

What's happening here? Latest Beta.

I setup my system again all the widgets and all.

I restarted my system and all settings are gone.

I tryd now 4 times. And always same result.

This what I get after restarting the device.

I had make a restore but that restore d for 10%

Edit: I reinstalled the app and installed again now it seems. That it works.
[Android Head-Units] bmccrary:
You bring up a good point. I guess I forgot to mention in my case the remapping tool doesn't do anything at all since I switched to a Malaysk ROM a long time ago., but that's for a different thread. Therefore using mtc-keys was the only way around it. With that said, the problem I ran into using mtc-keys for everything was that there was no easy way to switch media players using the mode button and make it work like it does with FCC launcher where you can just press the button and never leave the home screen.
[Android Head-Units] SpeedFire-:
This is the second such report. And this is not good. Because we don't know the exact reason,

Let's try the next beta (just uploded) and if the issue still exists we will try to find it.
[Android Head-Units] SpeedFire-:
New beta uploaded:

- You can apply the same style (color, transparency etc) to all widgets.

- Pandora(and maybe other unsupported players) integration on Android 5+.
[Android Head-Units] Roerbakeitje:
No problems so far with the update.
[Android Head-Units] rigattoni:
Still crashing...

...even after reset.

Edit:

Logcat attached.
[Android Head-Units] SpeedFire-:
Can you check this version?

fcclauncher-3.163a (3.158 renamed)

I just need to upload something working (temporarily) to Play Store until I find out the issue
[Android Head-Units] SpeedFire-:
Can't download it.
[Android Head-Units] rigattoni:
This one works so far.

Hopefully you will find the issue soon.
[Android Head-Units] SpeedFire-:
Good. Thank you! At least we have something which I can upload to Play Store!

I have 2 more files to test:

1) fcclauncher-3.163b (real 3.163 with old gradle)

2) fcclauncher-3.163c (real 3.163 with old crashlitics and gradle)

Will some of this work?
[Android Head-Units] rigattoni:
Uploaded the file once again...

But... I am not able to set FCC as standard launcher?!?
[Android Head-Units] musicscore:
To many problems to use.

installed 3.162 and launcher stops / crashes while trying to start. Had to return to the launcher of the unit because I do not have previous versions of Fcc car launcher. The previous version I installed was 3.159 and that did not crash but was very unstable. Because the launcher is getting more attention as is save while I'm driving due to thinks not working as they should be, I will Stay with the default unit launcher for a while. I Will check on a requal time if the Fcc launcher works ok but until then I can not us the fcc car launcher. I wish you succes with the fcc car launcher and hope you Will make it a great car head-unit launcher in 2019.
[Android Head-Units] Scopesys:
3.163a Not working for me... it always comes up with the message about Widget added permission not being granted... does not do the thing where you try to install your 1st widget, and you get a popup, asking if you want to enable that permission.

And the recent version like 3.159 3.160 , FCC just crashes ebfore it even runs it's setup.

3.145 is the latest version I have that works.

Then I have 3.155 that has the widget permission issue
[Android Head-Units] SpeedFire-:
We are currently investigating what causes the most critical issue - crash during start up. Let's focus on this first.

Can you also show a video of your issue with the widget?
[Android Head-Units] nt7561:
Hi speed fire.

I'm not sure what type it is. How can I check it?
[Android Head-Units] Xorit:
On my emu the 3.159 works. (Bluestack runs Android 7 btw.)

logcat attached -> found some lines reg. the album art.
[Android Head-Units] rigattoni:
Both version are not able to get installed.

The 3.163a is not really good. It´s just not crashing. I had to deinstall the latest version and I am just trying to get it back as I need it.
[Android Head-Units] Xorit:
fcclauncher-3.163b (real 3.163 with old gradle) - works on emu

fcclauncher-3.163c (real 3.163 with old crashlitics and gradle) - works aswell

Seems like my emu isn't that sensible :D
[Android Head-Units] Xorit:
btw Logcat Extreme has a floating log window.. alot easier..

2nd screen is with Amazon Music widget and version info
[Android Head-Units] Scopesys:
Sure - I can do whatever you want, that I am able to do to help.

Unfortunately, I am not rooted.

The point I was trying to make with the widgets was, that this would seem to be just one of 3 symptoms, that have developed since about 3.145

1st thing that started to happen was the inability to restore an earlier version backup.

Then the inability to clean install, and still be able to add widgets (widget permissions). Updating did allow widgets, because it did not do the full setup again, giving "adding widget permissions" .. apps shortcuts could be added OK.

Those just updating would not have been aware of any of this up to this point.

Now with the latest version, inability to even run FCC - with FCC Crashing, either with Clean Install, or an update.

If you can get the Clean Install to work with a latest version, and do not see a widget permission issue (and I do), I'll make a video to show it.

As you say, investigating what causes the most critical issue - crash during start up is the highest priority, and I'll promptly test anything you publish.
[Android Head-Units] jostor4713:
Hello again. I see that now [MENTION=1633144]speedfire[/MENTION] has other issues to solve. But when I can review my video, and if it only happens to me, then I'll have to resign myself.I have uninstalled FCC and reinstalled again and continue the dark sides. I have observed that after boot I get dark sides and if I go to the app drawer, when returning there are no dark sides. If I start an app, any, and return home, I get dark sides.

Attached video.

https://drive.google.com/file/d/1rQeEuJrDZE5i9FNMVmJIXCij5TCXP3ib/view?usp=drivesdk
[Android Head-Units] SpeedFire-:
Please try this beta with the fixed restore function (I hope):

fcclauncher-3.165a

App may not ask for manual widget binding if permission was already given (even after clean install) or is not required. You can check it by manually putting widget afterwads and seeing if it asks to give permission or not. If you still have issues please send me a video.
[Android Head-Units] Scopesys:
Thanks ....

Just to make it clear... what was happening before in later versions before they would not run was:

On install, popup would appear, saying that permissions were not granted to add widgets, but then, on attempt to add widget, it was NOT asking if I want to grant permission.. the dialogue box was never poping up with the add now, and checkbox to add in future.

This resulted in FCC running but never being able to add widgets (just APP shortcuts).

Anyway, will get back to you later about 3.165a :)