yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
See the same with my Eonon head unit here in the USA .. The Eonon FM radio apps shows some information on some stations, but it is not consistent, and FCC does not see that info.

I just accepted that I had to make Artwork and names for my local radio stations .. but since the local FM radio station's CONTENT is not worth listening to, I typically listen to my own Mp3s, or other Internet Radio stations worldwide .
[Android Head-Units] rigattoni:
This is something you need to claim at Eonon, this has nothing to do with FCC.

...and yes, in most countries you get RDS data via FM and it´s a known issue that some umlauts or special character are not available.

All FM apps do not provide any information as the frequencies to other apps, even the own widget does not get these information.

That means that your possibility to get station names of FM, to store the names yourself in FCC. There is no other way for now.

But once again, the problem is on south side, not on FCC.
[Android Head-Units] parisisal:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

The total park time widget does not work.

Grows up every day without resetting the value every day.

Can you fix?
[Android Head-Units] tonimontoia:
Yes total park not work
[Android Head-Units] rigattoni:
I think there are more important things to fix. Just push the reset button of the widget in the morning.... and voila, the issue is gone.

In Germany we would say that this is "Schmuck am Nachthemd", means "Jewelry on a nightgown", not more not less.

You don´t need to report this minor issue every few weeks. I´m pretty sure that this is on his to-do list to be fixed later, if this is really a bug. I personally don´t see this as a bug.
[Android Head-Units] SpeedFire-:
This will be fixed.

However I started to slowly roll out the version 3.333 to the release channel (20% of current user base will receive the update). Then I need to wait patiently for possible bugs.

So, in short, this will probably be fixed in the next beta but not earlier than next week.
[Android Head-Units] sabanook:
I use TuneIn Radio Pro and the radio station logo is present in the player widget. Also artist / title info is displayed. Forward / backward have no function for my TuneIn.
[Android Head-Units] parisisal:
Thank you,

I really appreciate your feedback.

Thank you for your work.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION] Did you overthink this feature of the parking time, before you have to work double on it?

To count parking time while the unit is running makes no sense at all. Parking is when leaving the car. In this case the unit should be off. To count the time while waiting at some red lights in the city and the system is running is useless to count these times as parking time, because this is no parking time.

If you would take the difference between shut down and wake up, this would count the parking time.

May be you think once again about this feature. What should this feature tell us?
[Android Head-Units] Scopesys:
I think that maybe the issue is the word PARK (maybe something lost in translation between languages) ?

I just assumed that the PARK time was in fact a "Stopped - not moving with engine running time" -- ie when the Engine (Head Unit) was running but the speed was zero.

Ie The time during a trip when you were stuck in stationary traffic, or waiting at a Traffic light.

BTW: What is the TRIP average speed... the average speed over the time you are moving, or the average speed over the total trip time. ?
[Android Head-Units] riccardone1:
Excuse me, but what is the purpose of measuring parking time? Why do you measure it?
[Android Head-Units] Scopesys:
That is exactly what is being discussed already (above) , with the aim to define what it is, and how useful it really is.
[Android Head-Units] rigattoni:
No, the park time counter has a parking sign on it´s icon. ;)

Nevertheless, let´s wait for some explanation.

Good one too!
[Android Head-Units] SpeedFire-:
Another issue with Trip widget was identified so I updated to the beta to 3.334

FCC Launcher 3.334:

- Trip widget fixed

- Total park time should reset every day
[Android Head-Units] SpeedFire-:
You're right. It's more like an "idle time" or "traffic jam time". I don't know how to call it better (and what icon to choose). Can someone suggest?

This one: "the average speed over the time you are moving" (this parking/idle time is not accounted for, so this average speed is not exactly correct for some hard traffic jams situations).
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

Could you help check this issue regarding the widget's primary text size.

Eg. Memory widget primary text size set to 13. Widget will display correct text size.

But at next redraw of widget the text size returns to default. Eg. When u try to hide an icon in app drawer. Widget text size returns to default

Thank you
[Android Head-Units] SpeedFire-:
Should be fixed in the uploaded beta.

Other fixes:

- Top-right corner settings are now disabled by default

- Bluetooth bug fix
[Android Head-Units] jun81:
Thank you! Looking forward to that!
[Android Head-Units] TT_Vert:
What was the bluetooth bug fix?

Dave
[Android Head-Units] SpeedFire-:
App sometimes asked for permission to enable Bluetooth. Now it should not.
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

2.420 runs ok

2.421 frequent crashes

eg.

- crashes after selecting backup settings

- selecting fm radio from player widget after fm radio is already selected.
[Android Head-Units] SpeedFire-:
Thank you for report. Should be fixed now. New beta:

- FCC's icons can now be changed as well

- Bug fixes
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

2.423

Crashes at

-restore settings
[Android Head-Units] hgreen70:
Hello guys,

New here! I have purchased a 10.4 Android head unit for my 2013 Cadillac. Its based on Rockchip I believe its a PX3. I would like to to run FCC on it. i feel it would give me great service. is there any reason i cant? is there a launcher you recommend better for me? Although my unit says it Android 6.0 i have my doubts! the settings screen looks like KitKat, so is that hindrance, can i pay someone to port it? I AM WILLING TO PAY FOR MY SERVICES. just let me know.
[Android Head-Units] Roerbakeitje:
I recommend that you first look at the free version of fcc. A launcher can not break your unit. Also there are tons of launchers on play store . For mtcb this is the most suitable.
[Android Head-Units] TT_Vert:
FYI it seems that pandora track/artist is showing in the music widget in 4.4.4 usually now. It was hung a few times today and I force closed FCC and reopened and it worked.

Dave
[Android Head-Units] vincent_hall:
Thank you! :good:
[Android Head-Units] Mike6208:
Can't change speedometer to mph. By default it's at kmh. But when I try to edit the settings on the widget. The option to change is just not there. Any fix on this?
[Android Head-Units] SpeedFire-:
I've just checked. The option is in Speedometer's settings and it works for me:

Please check
[Android Head-Units] Mike6208:
maybe my problem is a version issue, anyone have the link to the latest beta? cant find it on this thread
[Android Head-Units] SpeedFire-:
The latest beta:

beta 2.426
[Android Head-Units] TT_Vert:
I think this is also a paid option only right?

Dave
[Android Head-Units] SpeedFire-:
Switching to miles? Of course not :)
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION]

Jus installed 2.426

-Backup and restore works great!

may I check if the backup saves and restores hidden apps?

-speed volume adjustment

Can we make it an option to have volume sync with manual volume adjustment? Something we had before?

Bugs found:

1. Memory widget

-unable to access settings via click top right corner

-not able to delete widget
[Android Head-Units] SpeedFire-:
It should save(as well as custom icons). You can check it by going to FCCLauncherBackup foldet at your Google Drive. If you'll find 'fcc_hiddenapps_db.db' file - then they are saved

This is a bit harder issue.

As you probably know this issue is caused by a bug in Rockchip's firmware where the volume data is kept in some local variable which is not updated if the volume is changed by third party apps.

We can update this variable from FCC Launcher but the volume bar will pop up. So we have two options:

1) Do not update that variable (current option)

pros: volume bar will not pop up when the volume is automatically changed each time depending on speed.

cons: manual adjustment is broken. In this case if you change it manually the volume will 'jump' to that old local value.

2) Update that variable.

pros: manual adjustment will work, but

cons: too many volume pop ups

Here is the experimental third option. I don't know if it will work. We will try to update that local variable if we recognize that the volume is changed manually. There may be some bugs. Here is the beta (it will not be uploaded to the market).

Please check (log is also appreciated): fcclauncer-beta-2.427

- Yes there is something weird when you hold your finger on it. I will check. But still you can drag it to 'delete icon (cross)'.

- I will check settings issue
[Android Head-Units] ZeroZorro:
What about a snail?

[emoji222]

Verstuurd vanaf mijn Z2_PRO met Tapatalk
[Android Head-Units] Scopesys:
How about "STOPPED" with the STOP icon
[Android Head-Units] riccardone1:
these?
[Android Head-Units] rigattoni:
Please take care about copyrights... All of your icons are registered and copyright protected.
[Android Head-Units] Scopesys:
I do not think that the standard RED STOP sign is copyright. ?

In any case, the a TEXT "STOP" on a red background could be easily designed, and FCC could hold it's copyright !!!

One thing to consider with an Icon for this, is that it should be Simple, and be clear when it its very small. Complex icons may not be so readable at small size.

FYI: I do not find a need to display this sort of Information on my head unit, but I can understand why others might choose to :)
[Android Head-Units] rigattoni:
No, I assume that the STOP icon should not have a copyright....and yes, it should be clear in this size. I would not color it in red, so it would not touch any obscure rights. :)
[Android Head-Units] parisisal:
I suggest to add also trip widget time that sums : car moving time + traffic jam time (this sum is the real trip time).

When I go at work, my car is stop for the 40% of the time (heavy traffic jam).

Currently we have :

- Trip time : time when car is moving

- Park time : time when car is stopped

You could add

- Total trip time : time when car is moving + time when car is stopped

Regards,

Salvo
[Android Head-Units] magikweis:
I recently came across FCC Launcher and installed it on an Android Box that I have connected to my cars head unit and I´m pretty with FCC launcher from what I´ve seen so far - takes some time to identify and understand all the option. great work!

Once question though:

In the maps view/widget the location arrow is pretty far centered in the map view which bugs me cause it shows so many crossing and streets that are already behind me.

On the opening post there are two pictures which actually show what I mean pretty well.

I noticed that you can set the zoom level based on speed (love that !!) but I couldnt find an option to alter the field of view or the viewing angle in 3D view: I would love to have the 3D view "closer" to the location allow.

Any ideas?

/edit: A while back on a jailbroken iPhone I used to have GMEnhancer installed which had exactly the features I´m looking for now. You´ll find the description here: hxxps://www.idownloadblog.com/2018/10/08/gmenhancer/

There was an option to change the zoom level, viewing angle and a "look ahead" feature.
[Android Head-Units] okij:
Location not working after standby in recent beta versions

[MENTION=4292729]SpeedFire-[/MENTION]: Since last weekend (so it must be since FCC Launcher Beta 3.332 or 3.333) the MiniMap and the speed widget aren't working after the head unit is started from standby.

It seems that they don't get the current location, even though it is enabled in the app settings and other apps (like GPS Status) get the current location without problems, so GPS is working.

I have FCC in the white list of apps which should stay in memory during standby and this was working fine with previous FCC versions.

This issue can temporarily be fixed by restarting FCC (or of course rebooting the head unit), but only until the head unit goes into standby the next time.

Therefore I would like to ask you to look which optimisation or code change in version 3.332 or 3.333 might have introduced this bug.
[Android Head-Units] magikweis:
Alright, I did a little bit of research an apparently the camera position, tilt and zoom needs to be changed for the Maps API as described here:

https://developers.google.com/maps/documentation/android-sdk/views#changing_camera_position

Is this something you could implement? Please?
[Android Head-Units] mclaudio:
hi there...cant the RDS information on FM be displayer as album information text on FCC?

thanks

---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------

how can i install mappbox offline maps?

thanks
[Android Head-Units] ab1702:
Take it out of the whitelist. There is an option in fcc settings to start fcc on boot and then it starts automatically every time so no need to have it in your whitelist.
[Android Head-Units] okij:
I know that this is possible, but

the head unit is faster up and running if FCC isn't closed in standby and

it was perfectly working until last week.

That's why I asked [MENTION=4292729]SpeedFire-[/MENTION] to look after this issue.
[Android Head-Units] magikweis:
Location indicator too far ahead in mini map

I tried to visualize the issue and hope someone could review it? Please see attached picture

In case it matters: I have FCC launcher installed on an Android box running 7.1.2 including root access. The box is hooked to my Volvo cars screen (which is portrait more, could be part of the problem) and can completely used there with touch support and everything
[Android Head-Units] hostelhostel:
The launcher is really great. I have a problem. I use the minimap and after the Launcher Starts , the symbols like Zoom In and Zoom Out are visible, but the screen behind remains black. I have to click on the black screen once, then the map works immediately. I use the Google Map with the style "Black" without automatic zoom.
[Android Head-Units] Th0m4s88:
I just upgraded my px5 headunit from dasaita from Android 8 to 9 and played around a bit with the FCC launcher. Everything but one widget seems to work correctly.

The widget not working 100% is the navigation arrow. The arrow itself is showing the correct direction but the distance till you have to take a turn isn' t showing at all anymore. With Android 8 it was working perfectly.

The Agama launcher has a similar function and it is showing the same problems so I guess the problem lies in Android 9 blocking part of the old way of the navigation messages.

The problem is also not related to the navigation software. I tried Google maps, sygic and Yandex and all of them are showing the same problems.
[Android Head-Units] Scopesys:
Out of interest, have you found any advantage of upgrading from 8 to 9 ?
[Android Head-Units] Th0m4s88:
No. Unfortunately nothing at all:rolleyes:
[Android Head-Units] pr0l4m3:
[MENTION=4292729]SpeedFire-[/MENTION] I have bug in last alpha with song widget. I think is still the same as previous. Link for video.

https://www.youtube.com/watch?v=iy51MQV4gJA
[Android Head-Units] SpeedFire-:
FCC Launcher 3.338:

- A separate Navigation widget is fixed for Google Map (shows more info)

- New feature: Go to Overview mode on Back button long press or double press

- Small bug fixes
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Overview mode on back Button.

Not sure what you mean by OVERVIEW MODE, but on my unit, now, a double press of the back button put FCC into the screen modification mode, (where widgets can be added to screen etc), but it allows these modifications, even if the Screen is locked ( ie Red padlock)

I would suggest that the SCREEN LOCK should be the priority, so if the Screen is locked , it is LOCKED, and cannot be changed, even via a double press of the return button.

ie If the screen is LOCKED, then a double press of the back Button, should not do anything, except maybe temporarily display the Lock Screen padlock (and maybe not even the Lock screen pop-up) -- Reason: when car is moving, and you press the back button, it is easy to do an unintentional double press say if you hit a bump in the road), and you really do not want

any sort of edit mode coming up, (including even the lock popup) if you have the Screen Locked. (The red padlock warning should be sufficient)
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION],

I found out how to enable the Auto brightness in FCC.

The trick is to set in Settings/App info (FCC) --> Advanced --> Modify system settings to allowed.

Just now the automatic brightness setting is working as expected.

Seems that you should ask for these settings on set up. ;)
[Android Head-Units] Scopesys:
Ive seen FCC ask for permission to set this -- "Sometimes" ..

Some times I do a complete re-install of FCC, other times just an update, but FCC still seems to be random when asking for permissions for "Modify system setting" and for other permissions.

I had always assumed that some of these got remembered between updates, or even re-installs, in which case, FCC did not ask again.
[Android Head-Units] surfer63:
I have installed quite a number of alpha builds (I'm thinking of switching to FCC) and mostly fresh. FCC does request the permissions (it is even an unavoidable step on 8.x), but FCC sometimes takes focus back immediately, and thereby the permission popup disappears in the background. I have to minimize FCC, give permission, maximize FCC again, and tap the "next".

On updates Android only requires this step for additional permissions.
[Android Head-Units] rigattoni:
I did not had any issues in the past on each other unit, except on my CSN2 unit.

So may be I did not recognize the pop up to accept the rights.

I reinstalled the unit a dozen times now, completely from the scratch and never got the pop up for it.

This was one of my most important issues I have with my CSN2.

Another question is regarding the FCC Servicemode.

Even if this is activated, the user is able to use the status bar to access anything else. Do I miss here something?

I would expect that all active apps are closed before. Only with all apps closed, the servicemode makes sense.
[Android Head-Units] SpeedFire-:
Launcher cannot do this - it has no enough rights. Yes, the lock doesn't really locks the system completely and can be disabled via status bar. But it's something at least..
[Android Head-Units] Xorit:
Hi there,

long time no write for me on this, as I was just busy with things.

Wonder how the player widget does in regards to passing commands from steering to the player?

I recently noticed a lot of unresponsiveness and am curious if it's caused by FCC.

I use Neutron Music Player and am facing none responsiveness from the steering, pressing buttons which then don't translate into Neutron doing the commands I intent to execute, like play/pause/forw/rev.

Also I experience the speedo to still sometimes drop out and I need to re-enable GPS twice or more to get it back.

Using the latest playmarket beta.

Any logs I may attach to find what's going on?
[Android Head-Units] whitewolf8111:
For quite a while now, the only permissions I would see come up would be the notification access and sometimes the widget permission.

Normally when I install a new version of FCC, right after it's done installing, and not gone through with the wizard or anything yet, I will press the system settings button and manually allow all the permissions I can find for FCC:

Go to app info and select FCC, then select Permissions and enable all the Permissions listed. I will also go ahead and allow the Notification access and set FCC as the default launcher. Then go back and complete the FCC wizard, then restore my backup.

[MENTION=4292729]SpeedFire-[/MENTION] I do still have some issues with the restore process, same as mentioned before, but after a reboot and a couple try's to restore my backup, it did crash once while trying to restore, but after the crash, FCC restarted itself and went through with the restore. And the process of loading the widgets went very fast and smooth. So definitely getting better there but still needs some work with the first part of the restore. I can post my backup if you think it would help.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

I mentioned it a few months ago, but is there any chance you would consider adding the "option" of a Compass on the Speed Widget, and also as an "option" on the Speed Limit widget.

Currently there is nobody offering a GPS Compass Widget on the Play store, and even if they were, it would take up valuable space on a page.

Making it an option on the Speed Widget (and Overspeed widget), gets a compass without taking up any additional space (if one of those is already displaying)

(in addition, if one just wanted a Compass, one could then use the Speed Widget, with the speed colors set to the background color)

Attached is a Photoshop page, with an edited Speed widget image, which also displays a Compass
[Android Head-Units] SpeedFire-:
This is a really clever idea and a good suggestion. After the release I will try to implement this.
[Android Head-Units] Scopesys:
Thanks so much :)
[Android Head-Units] SoberXDA:
Hello!

Is this the way the song info is expected to be scrolled? Looks jerky... I would rather prefer it would not scroll at all

https://youtu.be/10sq56WGRUo
[Android Head-Units] Scopesys:
No, that is not how it should scroll. ... It should start the text again after a gap at the end of the currently displaying text.

In your example, it is RESETTING, instantly displaying the start of the text, as much as will fit, and then it starts to scroll.

I find that that most of the time, the scroll is as expected, but sometimes, it does scroll like your example, but I have not figured out why it does it mostly correctly, but sometimes with resets.

One thing to notice, is that when it is scrolling, if you have a mechanical volume control, and operate it, the scrolling will reset each time you start turning the volume knob...

Not desirable, but not too bad to live with.
[Android Head-Units] bossman4:
I think that the next phase of development of FCC Launcher should be tighter integration with some of the suppliers of the Chinese radios. This is a very competitive business in supplying radios and it appears that "features" are what sells. What would be a better feature for a Chinese supplier than a smooth integration of a sophisticated launcher platform like FCC.

I am not sure of the business structures and relationships in this Chinese radio business, but surely some company could see an opportunity in getting integrated with Speedfire. There are companies that seem to put out firmware updates quite often and others that just let you hang.

To keep FCC alive, it will have to change with the technology and somehow, a more formal link needs to happen. I have one radio running 8.1 Android on a PX5 (Eonon) and FCC works great. The other unit is a 9.0 Android with an 8227L processor. The "supplier" does not have or won't supply the FM radio and Bluetooth APK. I can't use FCC on that unit.

The radio suppliers need to realize that they can increase their market share, if they have a thoughtful and clever launcher. They should be working with Speedfire to achieve that results!