yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
The funny thing is that even on Amazon Music widget album cover is not loaded properly (at least in my case).

This can be easily reported as a bug.
[Android Head-Units] wanb1i:
Some basic issues

I recently installed FCC Launcher on my Joying PX5 Android 8 HU and have the following issues:

1. The Launcher won't "stick" as the default Launcher, even though it has been selected as the default Launcher.

2. Speed indicator is off (high) by 3-4 MPH when compared to other apps on the same device and other devices.

3. Automatic volume/speed control doesn't work at all and I'm using the paid app. For me, this is a deal breaker and it's the reason I paid $6.99 (too high priced!).?

Please help! ?
[Android Head-Units] Scopesys:
You have to be joking. to high !!! ... do you have any idea the amount of work and hours that must have gone into FCC, not to mention all the time in tech support.

$69.9 or even $699 would be a more realistic amount to pay.

You would gladly pay $6.99 for some unhealthy fast food, but when it come to an Android App, that all you have to do is press a button and download it so easily, you seem to have no comprehension as to what work when into providing this for you.

Even worse are those than say, "Hey FIX This", and then I will consider buying it as if their pityfull $6.99 is even worth the effort of the developer replying to them !!

Rant Over ....
[Android Head-Units] wanb1i:
GREAT! I hope you feel better now! I've been using Nova Launcher Prime for years now, don't remember what I paid for it, but it has NEVER listed a feature that didn't work for me. That said, it doesn't offer some of the features this app does. Unfortunately they don't work, so $6.99 is too much for something that doesn't work! That amount of money compared to other android apps is a little high (my opinion) but I paid it to support the developer, like I do with most apps that I like. I didn't pay that to be harassed by you or anyone else on this forum. I have my opinion, and here in the USA, I still have the right to express it and I will continue to express it!

BTW, thanks for the help! NOT!:p I couldn't help but notice how many "Thanks" you have on your Thanks Meter, probably because you're so helpful!

My Rant over!
[Android Head-Units] SpeedFire-:
I will try to comment:

1. It should. The only reason why it couldn't is some kind of crash which you should experience every time.

2. Impossible. The data is provided by GPS module directly without any processing (other than converting it to MPH in your case, but it is made precisely).

3. For PX5 it should work. Does volume widget works for you? If yes - autovolume should work as well. Please set some large values of volume change and see if it really works or not.

P.S. I am ready to return you the money. Please send me your order # and purchase date to a.kurapov@gmail.com
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Is there a trick to get the black screen (Screensaver) back?

First, the page got the same background as all other pages and I was not able to get the background black again.

Then I deleted the page and just now I am trying to get it back... :( ... without luck until now.
[Android Head-Units] SpeedFire-:
Go to FCC Settings -> Display -> Advanced -> Screensaver screen position
[Android Head-Units] rigattoni:
No, sorry, that does not work... :(
[Android Head-Units] SpeedFire-:
Ah. I see. Something is broken in the latest updates (after optimization). Let me fix this.

P.S. I have fixed this (will be available in the next beta). But currently I am in the process of internal migration from "old player names" to player packages to be able to basically support almost all existing media players. Therefore I can't quickly release a new version right now. Maybe tomorrow.
[Android Head-Units] rigattoni:
No problem. Take your time.

The unit is just staying beside me on the desk to do some refinement at my tasks...
[Android Head-Units] Julian75ts:
Please Speedfire, take a look at my issue . Thank. (Page 286)
[Android Head-Units] SpeedFire-:
Sorry, I don't have enough data to help with this issue. It is not reproduced on my devices (but I don't have a Sofia device).

You need to send me a LogCat log and a video.
[Android Head-Units] Julian75ts:
Ok.. Can you explain me how to make logcat log?

PS the issue Is very simple ti explain.. i use fastboot/instant boot.. minimap doesn't update After last location or display the world map! sounds like the GPS doesn't fix the location..(i have a similar problem with Google Maps that display generic error, retry later(impossible to connect to Maps)
[Android Head-Units] SpeedFire-:
This is an important addition, which makes me belive that the real issue is with the device's firmware or hardware. Anyway if external navigation apps can't get a GPS data as well the issue is not within the launcher. Try to find a solution on your device's forum. Probably you need to try a newer firmware in which this issue could be fixed.
[Android Head-Units] Julian75ts:
I think i have the latest firmware but i Can guarantee that All other GPS navigator apps work perfectly.
[Android Head-Units] SpeedFire-:
So what does this mean: "i have a similar problem with Google Maps that display generic error, retry later(impossible to connect to Maps"?

P.S. You can read about LogCat in the first post of this thread.

- make sure you updated to the latest version of FCC Launcher

- start recording video

- wake up your device

- start recording LogCat

- Restart FCC launcher with a Restart button

- stop recording when the launcher and a map are completely loaded but location is not visible.
[Android Head-Units] Julian75ts:
This means that Google Maps shows me this error message," impossible to connect to Maps, retry later "but All other GPS related Maps work with no issues.

Ok i'll follow your instructions and send you more useful info
[Android Head-Units] Scopesys:
Sounds good :)

One aspect of the player widget you might look at, that might explain some of the issues is.

Only ONE player should be select able at a time, and always ONE player should be selected. (in the widget)

ie it does not make logical sense for more than one to be selected (Name Highlighted) at the same time, or for none to be selected.

However, I often see both of these rogue conditions when switching between players which might explain a few things .. as if the widget is confused about what player is actually selected, and should be being displayed and controlled in the widget.
[Android Head-Units] Soiski71:
FM Radio vs localradio ?

Hi Speedfire,

I finally updated my headunit (previous PX3 version had the problem with widget authorizations and did not work at all) and now the FCC is working (as it should ... I guess).

Again the unit is one of these generic china units (pictures attached)... it is actually alps 8227L version and not PX5 as I originally thoiught. The radio chip is NXP6851.

https://soisalo.webnode.fi/fcc/

The issue is that the audio widget does not recognize the built in FM Radio. I purchased also the premium version just to see would that effect, unfortenately no.

The unit has these named as localradio and the standard player is called localmusic.

Is this the reason or ?
[Android Head-Units] Jgigs:
Is anyone able to make calls from their px5 head unit using this launcher? I've tried to use okay Google and changed the option to FCC per the direction and it still won't make the call. I don't see a native dialer in the widgets or apps. Any ideas?
[Android Head-Units] Scopesys:
I have a Px5 Unit, and this is what I ended up doing -- and why.

I have installed Android Auto on my PX5 head Unit.

The one on Play Store would not install on the head unit, but I did find an earlier version what does.

Google Assistant has Volume control issues, so when you talk to it, it's reply is at a very low volume.

However, the Google Assistant that is built into Android Auto does not have this issue, and the Voice is approx the same volume as any playing music, that gets muted (or reduced (Options) when the Assistant is Listening or talking.

Also, I do not have a Cellular Modem, so I use my phone, connected by USB, and linked with Bluetooth.

So, Having done the normal, set my phone to be a HotSpot, when I want to call anyone, I just start Android Auto on the Head Unit. Once started, it stays resident, and can thereafter be quickly called up, or hidden.

Then either Hello Google, or click on the Mic, to talk to Android auto, and it works great.

To get my phone contact list, I just use the Android Auto Phone , which gets my Contacts and displays them the same way as I am use to seeing them on the Phone.

It's NOT ideal, but it does get around the most annoying thing with Assistant, it's useless volume management when run as the App on the phone.

I did read some BS from Google about it being better to have the Assistant at a low volume on a Smartphone, so it does not annoy surrounding people, but in a Car you want it at a decent level, and do not want to be distracted by having to mess with the volume control.

Speedfire- did a neat "work around" where FCC can increase the Google Voice Volume, but it uses Permissions that have to be set up every time the head unit is restarted. (looks like there is a work around for that as well).

However, currently I am finding the Android Auto on the Head Unit, the best solutions.

It has added advantages, as if you are controlling say PowerAmp, the Android Auto Interface to PowerAmp is a lot simpler and less distracting, and easier to use when driving.

I also limit my Phone time when in the Car... it's nice to get away from the phone at times, and there is always Voicemail, if the caller really has something important to say !!

Lots of options.. just choose one that you feel comfortable with :)
[Android Head-Units] rabenkind:
Hi speedfire,

it is me again. I would like to request about using the offline navigation (iGO) instead of googlemaps or somtething like that for the widget on the right half of the start screen.

How can I manage this. My HU is a new px5+

thx

rabenkind
[Android Head-Units] Xtreme2k:
Some days ago I tried FCC launcher again after some months, and I'm totally impressed by the development. Thus I bought the pro version today, there's only one thing I'm missing compared to the Agama Launcher: Agama is able to catch navigation messages from Google maps and some other navigation apps if navigation is active and shows them in the launcher. I think it would be a great addition to FCC if it could show those messages in the minimap like it does with the street name.
[Android Head-Units] Jgigs:
I hear you. I have android auto as well via the dongle, but was just hoping for something better. AA is a bit laggy and buggy to me. If that's the best we can get, I wish I just bought a regular head unit. FCC is so close to perfection for me. It's so much better than AA. I bought the pro version immediately, but the darn dialer is the problem for me right now. Eventually my wife will be using this headunit full time and she won't be able to handle it without seamless dialing like android auto.
[Android Head-Units] Scopesys:
I think you might have missed the point.

You actually install Android Auto on the HEAD UNIT.

(You do not run AA on the Phone)
[Android Head-Units] musicscore:
Allwinner Support

Please can you tell me what is the status of the AllWinner T8 support.

Are these components working :

Media player (with Album Art)

FM Radio

Volume controll

Bridness controll

etc.

In the FCC launcher AllWinner is still BETA in the selection. During install via the wizard I cannot select AllWinner.
[Android Head-Units] SpeedFire-:
Does anyone want to test redone Player Widget (actually only its internal functions)?

New alpha: fcclauncher-3.180-newplayer

It will automatically migrate from "old internal player names" to the new ones, so you should continue to use your player widgets as before.

The player widget behaviour may be more buggy in this version (or maybe not). Need more tests.
[Android Head-Units] SpeedFire-:
These 4 will probably work. "etc" probably won't [emoji3]
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

I just set up the alpha version.

First of all, the "Black Screen" is back working.

About the player widgets:

If you delete a player widget and create a new one, most of the supported player are missing. You need to reboot completely to get the player list shown completely.

DAB-Z opens in foreground if you choose the app in the widget. (Can be in relation to an existing issue in DAB-Z, that the "pause" status is not switched off. This issue will be fixed in next version of DAB-Z)

Other than that I can´t see any difference. May be that we need more information what has been changed in this version to verify them.
[Android Head-Units] rigattoni:
Just now I am working with a work around for DAB-Z, which reacts if the app comes up to the foreground. With a delay of some seconds, the home screen is shown.

...but this is just a workaround, nothing what would be a proper solution.
[Android Head-Units] Scopesys:
However, FCC running on the Allwinner seems to "reset" at lot ??

Do know know if it a crash, or a re-init, or a slow refresh, but very often when using FCC, the screen reverts to the FCC logo for about 3 seconds, and then the screen populates with the Home page.

The FCC logo, instead of a Blank screen is a nice improvement.

I am wondering if that could be used to help beta test.

(1) If FCC crashes, and then restarts, could that LOGO say be RED, to show that it was restarting after a CRASH.

(2) IF FCC crashes, could that be logged to a text file, that could be viewed by User, and sent to you with Bug reports.

Maybe the above debug feature turned on/off with a FCC option setting.

---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------

Link not working :(

"The address wasn’t understood"

AHH see why now looking at it in this reply

hhttps !!!!

editing the link, and it works :)

---------- Post added at 11:28 AM ---------- Previous post was at 11:16 AM ----------

I am also testing ALLwinner.

I find that when Installing on ALLWINNER, you do not have the ALLWINNER option on install setup.

What you need to do is go ahead and install as say Px5.

Then when FCC is fully installed and running -

Go into FCC settings, and on the System select, you will see ALLWINNER (beta) as an option and select it.

Then you need to restart FCC. I do a UNIT RESET to make sure.

Not sure if you need to do this on an UPDATE.

I always Export the APK, do a setting backup to match that APK version.

Then I try a UPDATE. and evaluate.

If that works, I export APK, and do another matching settings save to Google drive.

I then Uninstall FCC, RESET UNIT, and then install the new version with a clean install, and then restore.

I know this is not 100% Necessary, but it does allow me to test both UPDATE and Clean Install, and if anything goes wrong, I have the option to go back to previous versions, and their matching settings backup.

---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------

So on an UPDATE, it FCC will automatically Migrate.

Would a Settings Restore of Pre_Migrated settings still work, or will previous settings backups now be outdated and not work because the backup player names are not the APP names (ie pre Migration) ???
[Android Head-Units] SpeedFire-:
We together with Richard (author of DAB-Z) already made some changes in FCC which will hopefully eliminate crashes of DAB-Z.

You can also check it: https://drive.google.com/open?id=1Z8XoVZhsbZYZEA7IygF8v1Cp_QtmNb7R
[Android Head-Units] SpeedFire-:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------

Previous backups will continue to work (auto-migration procedure will identify old settings and migrate them).

New backups could be partially incompatible if you will try to restore them at older builds. But nothing serious, they will restore but you will need to manually reselect quick players in player widgets.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Last night when Playing on with ALLWINNER, I did a Settings Restore that did not work (My fault), and totally screwed up FCC.

I was able to uninstall FCC, RESET, and then re-install FCC, and then RESTORE SETTING.

If I had not been able to do that, I would have been devastated, as resetting up my pages again would have taken hours and been very frustrating.

POINT IS :

THANK YOU for getting Backup & Restore working as a Priority late last year.:)

I now cannot imagine Beta Testing FCC without that assurance that I can always go back to a previously working FCC and its Settings, should anything go wrong. THANK YOU :)

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

Thanks ..

BTW: On subject of Backup.

There is still the issue with Settings backup, that when backing up to SD, the "File Error" occurs, and the backup ends up with some corruption, and will not restore. (this is the major problem )

The backup to Google Drive works fine.

Also, since we have the option now to backup to either, you might want to look at the working of the Menus & Pop-Up boxes etc, because it is confusing when backup up, and when it confirms.. ie You backup to one place, and it confirms the backup is being done and has been done to the other.

You will see this if you try to both, with this report in mind... its easier for you to see for yourself, than me type a page of detailed description ;)
[Android Head-Units] Schlusel:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

I'm testing the FCC Launcher on a Allwinner T3 Radio. Actually I use the FCC Beta Version und set it to Allwinner.

Whatever I do, the Launcher restarts after a short while. Sometimes It just closes, sometimes it starts again.

Do you have any idea?

youtube.com/watch?v=R0K02-YSUlM
[Android Head-Units] SpeedFire-:
Hi,

If you have a root and can record a LogCat log this could help to find out what really happens there. That could be anything,
[Android Head-Units] Scopesys:
Any idea how to root the Allwinner T3 Radio ?

I would like to root mine, so I can record LogCat logs

SpeedFire- Is your Allwinner unit rooted ?
[Android Head-Units] SpeedFire-:
Yes. I have rooted my T8 on 7.1 with a modified firmware found on 4pda
[Android Head-Units] Xorit:
Report 3.180

-> in FCC Settings click on Settings -> crash -> log
[Android Head-Units] SpeedFire-:
Fixed it. Thanks!

3.180b
[Android Head-Units] hapaman:
What is needed to have unsupported rockchip units supported by FCC?
[Android Head-Units] rigattoni:
Great news! :good:

I reported a lot of different crashes the last few days, but with this new version, the crashes are history. :laugh:
[Android Head-Units] SpeedFire-:
It depends. What unit do you have?

Currently I know about some Sofia devices and Tesla-style (vertical) devices which have their own implementation of rockchip interfaces and are not supported by FCC.

You can send me all apk-s from /system/priv-apps/ and /data/ folders. I will look at how difficult it is to support your device.
[Android Head-Units] wanb1i:
Thanks for the speedy response, sorry, but I didn't get the notification of your reply from XDA.

1. This could be the Joying Software (rooted Stock). I don't see FCC as a choice in the Joying settings although I do see Nova Launcher. If default isn't set here it won't take.

2. Not going to argue with you, but I drove the car for over an hour with Ulysses Speedometer on my Moto X Pure & the HU. Both were exactly the same. Your speed widget was always 2-3 mph faster. Made me wonder if you were getting the speed from the ODBII dongle (because the Prius speedo was the same as yours and IT's ALWAYS wrong), but it was connected to my phone, not the HU.

3. Not sure about this one because I don't use that widget, but I'll put it on the home page and test it later this afternoon and let you know.

Thanks for the refund offer, but let's see if we can get the autovolume to work, if not I'll PM you with the info you requested.

Thanks again for the quick response! :good:;)
[Android Head-Units] SpeedFire-:
1. Since your device is rooted please send me all apks from /system/priv-apps/ and /data/. Probably Joying just added some popular launchers to their selection list. Btw, what happens when you try to set FCC as your default home app? (FCC Settings -> System -> Autostart -> Set as default launcher)

2. So maybe Ulysses adjusts the speed? two sources (FCC and Speedo) against one. :)

FCC gets speed data from GPS chip (which can also may be different between HU and your phone). The best way to check is to start Ulysses on your head unit and compare its speed to notification (FCC displays current speed in notification). So both numbers will be visible.

3. Ok
[Android Head-Units] wanb1i:
1. Ok, I assume you want a list of all apps in those directories, not a copy of all the apps, right? Let me know & I'll go get what I can & test the widget. Joying does have 3 Launchers choices as Stock (Launcher 1, Launcher 2, & Launcher 3) Personally, I don't like any of them, so I've been using Nova Launcher Prime. But it doesn't have the automatic volume control, which I need because the road noise at speed in my Prius, makes it nearly impossible to hear the music or the Maps direction without turning up the volume. Then when I slow down it's way too loud. :eek: When I set FCC as default inside FCC, it accepts it, but when I select the "Home" key, it switches back to Nova (I have the 3 stock launchers frozen in Titanium).

2. I have Ulysses set as "overlays" so they're always visible. I noticed the difference on FCC so I placed them side by side (your speed widget and Ulysses Speed overlay). Both of them using the same GPS on the HU and an additional Ulysses on my Phone using the phones GPS, yours displays 2-3 mph over. Ulysses on both the HU & my Phone display identical.
[Android Head-Units] SpeedFire-:
1. No I need those apps. Apk files.

2. Compare Ulisses with any other GPS speedometer from Play Store then.
[Android Head-Units] Scopesys:
Just curious reading this (The Engineer/Programmer in me !!)

"always 2-3 mph faster" is somewhat vague.

Is it :

(a) Always, no matter what speed you are traveling,

or

(b) say 1 mph faster @ 30 MPH and 2 mph faster @ 60 MPH ?

One is OFFSET, the other is GAIN.

if b, maybe you can state the exact difference at say 60mph (the faster the better, driving safely !!)

Maybe original data is in KM/H and there is a equation processing issue converting to MPH ??

If everything is set to KM/H is there still a difference ??

---------- Post added at 04:01 PM ---------- Previous post was at 03:46 PM ----------

@Speedfire-

3.180 on Px5 .. Player widget works just as well as previous version, maybe even more reliably. :)

Sometimes (it seems randomly) get confused when a different Quickplayer is selected, but seems to sort itself out, either my temp switch to FM Radio, or a FCC restart.

-----

A few weeks ago you added Spotify Shortcuts.

Had a chance to test them again today.

Creating them and using them : - Works 100% :)

Only slight bug seems to be that while FCC states it has placed the Shortcut on the HOME Page, it puts them on another page (consistently) if home page is not #2.

ie If the Home page has been changed by the FCC Option, and is now, say Page 3, it still puts the Shortcut on Page 2 (the one after the 1st screen saver Page 1)

Not a Big deal .. looks like it is not picking up the current Home Page number, and may be hard coded to Page 1 ???
[Android Head-Units] SpeedFire-:
Did migration require any manual manipulation with Player Widget or everything was done automatically?
[Android Head-Units] hapaman:
I have exactly one of this so called tesla style units. I'll look how I can obtain this files, or do you think there's no chance anyway?
[Android Head-Units] SpeedFire-:
Conversion from KM/H to MPH is done using this function:

public static int convertToMiles (int km){
int res = (int) (Math.round(km * 0.621371));
return res;
}

It's pretty precise, isn't it? :)