yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

I just created some user stories for a feature request regarding Day/Night mode:

Global

As a user I would like to have the possibility to choose different schemes for Day/Night mode, including:

Free configurable backgrounds for Day/Night mode.

Free configurable button colors for Day/Night mode.

Free configurable font colors for Day/Night mode.

As a user I would expect to be able to decide at each time if I want to setup, delete or change schemes.

Settings-Menu

As a user I would expect a possibility in the settings-menu to choose:

Day Mode

Night Mode

Automatic, dependent to the daylight settings (needs to be defined when the switch happens)

Automatic as in system settings (car light)

As a user I would expect to have a sub-menu to set up global color schemes for Day/Night mode.

User Interface

As a user I would expect to have a widget to toggle the mode.

As a user I would expect to be able to enable/disable the schemes for Day/Night mode in each widget.

I would like to invite all user to add needed user stories if I forgot something.

Please keep in mind that we are only talking about color schemes for Day/Night mode. Please don´t capture this for any other features...
[Android Head-Units] VBA_Dev:
Should the music widget show Bluetooth song info? Mine does not, but would be nice if it did.
[Android Head-Units] SpeedFire-:
This is really depends on the head unit / platform.

Does it show artist?
[Android Head-Units] VBA_Dev:
No, it’s just shows the previously played player. My head unit is a Sofia 3GR and FCC is set to android device.
[Android Head-Units] SpeedFire-:
Try to set it to Rockchip
[Android Head-Units] VBA_Dev:
Ok thanks, I was told that was wrong previously and it has caused a few crashes/reboots when I’ve experimented with it in the past.
[Android Head-Units] lcha:
I aprove Scopesys idea. Adding an optional battery status and it would be great.

On the actual TPMS widget, spare tyre is missing and also battery satus.

The only remaining problem on my device (Dasaita Android 9) is the request for access to USB device after each boot (Cold or not). Sometime the USB acces request seams to be hiden behind fcc so I can't clic on OK and widget can't be refresh.

With the Option to automaticaly grant USB request set, FCC crash (as it is said).

On this App w ww.realmediashop.de//FIRMWARE/10TPMS.apk the request for acces to USB device have a check box to remind the choice.
[Android Head-Units] Scopesys:
My thought are that any Low Sensor batter should trigger a WARNING mode on the Widget, but there should be an option to turn off any low battery alarm, if the system is otherwise reporting that all sensors are working correctly.

I like the idea of the optional battery low alarm warning, but one should be able to disable it, as it can take some time to get batteries changed, during which time the unit should operate fine (provided the batteries do not get TOO low), and the drives need not be distracted with a battery Low Warning.

Low tire pressure or high temperature, and yes, all ALARM HELL should break loose !!
[Android Head-Units] SpeedFire-:
My understanding is that this is because such TPMS apps target maximum SDK number => 19 (KitKat). There are less strict rules for such low SDKs.

My app should target the latest SDK => 28 (Q) if I want it to be uploaded to the Play Store.
[Android Head-Units] SpeedFire-:
Can someone with ATOTO MTK device send me all system and priv-apps apks?
[Android Head-Units] ElMery:
I got an eonon MTK device, might i help you?

Inviato dal mio SM-G973F utilizzando Tapatalk
[Android Head-Units] mat317:
The navigation widget only ever displays the arrow not the upcoming Street or distance is blank with Google maps is that normal?
[Android Head-Units] ElMery:
[MENTION=4292729]SpeedFire-[/MENTION]

Bad news.

I've installed the new beta:

Random launcher reboots still occurs

I tried to save my settings to Google drive but when choose "update to Google drive" the window "FCC launcher has speed working" comes up.

When I reopen it, the main page look like is mixed up with TPMS pageView attachment 4794343

Inviato dal mio SM-G973F utilizzando Tapatalk
[Android Head-Units] SpeedFire-:
Yes, please. I need this also.
[Android Head-Units] ElMery:
Ok tell me what to do and how to do it and I will do it

Inviato dal mio SM-G973F utilizzando Tapatalk
[Android Head-Units] onmail:
And what about cheap Allwinner T3 with Android 4.4 (fake Android 7, 8 or even 9) - would sending of these help you to make the FM Radio app work with your widget on these devices? If it would help please let me know ;)
[Android Head-Units] SpeedFire-:
AllWinner T3 should work. Have you selected AllWinner device type in settings?
[Android Head-Units] onmail:
Yep, but FM Radio app is not working with the widget... AFAIK I am not the only one, there we some people here with the same issue... I am testing nearly all your alphas and have even tried FM radio app from different roms for my radio (I think 8 versions). The FM app is working, the widget is doing nothing. I have been digging through the 4pda.ru (ГУ на Андроид 4.4.х и 6.0.х, платформа Allwinner T3 Quad Core 1.2GHz (модель K2001)) trying to find some help but had no luck. I can tell you my reading russian about 25 years after passing my exams is not so good but these forums helped me a lot :)
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] A bit of feedback here on your latest alpha.

1. When I now switch to dab-z from another player, dab-z now stays in the background which it never did before. So that is fixed, thankyou.

2. I have it set in fcc settings to restart the last player that was used. However it cannot still restart dab-z if that was the last player used. Dab-z has a setting where if selected it will automatically start as soon as it detects the usb adaptor, this is the only way that dab-z will automatically restart. I also use Apple Music though, so if I have been using Apple Music last what happens is dab-z automatically starts playing and then after about 15 seconds fcc will switch it to Apple Music because that is the last player i was using.

What I would like it to do is for me not to have to select automatic start upon usb detection in the dab-z app and then for FCC to restart dab-z for me if it was the last player I was using like it successfully does with Apple Music.

3. On this new alpha FCC has crashed and had to be restarted twice already. It said FCC has stopped, I then also had to select it as my home button again.
[Android Head-Units] tonimontoia:
Crash latest alpha
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

Hope I found the correct BT apk...

View attachment 4795034

View attachment 4795035
[Android Head-Units] tonimontoia:
what is this Bluetooth apk for?
[Android Head-Units] rigattoni:
Nothing you can do with.

It´s just for Speedfire-
[Android Head-Units] hillbicks:
I was wondering if anybody had problems with using FCC on a joying headunit. I know that [MENTION=1633144]speedfire[/MENTION] already mentioned that it might not work with these new intel chipset, but I gave it a shot anyway. First install was great (chose android tablet as headunit), unit went into sleep mode and woke up just fine.

Yesterday the unit was completely off though and while starting it reset itself back to factory, I could only see a short message about corrupted filesystem (was driving). I'm not sure whether that is at all related to FCC, but maybe somebody here had the same problem.
[Android Head-Units] jmcnown:
hello i have an Atoto a6 i got FCC PRO is there anyway i can get FCC to control the sound on the system

what settings would i use for the mcu

thank you
[Android Head-Units] rigattoni:
You should choose Rockchip PX5+

The only thing missing is, that FCC is not able to see the BT device... but [MENTION=4292729]SpeedFire-[/MENTION] is working on it.

By the way... If you mention someone, take care of the name. You mentioned a user named speedfire, but this is not the one you want to talk to. His name is SpeedFire- ;)
[Android Head-Units] SpeedFire-:
New alpha 3.234:

1) Optimized initialization (initial loading is 20%-50% faster - less "black screen")

2) Optimized animations

3) When application is deleted - IconWidgets related to this application will be automatically deleted as well

4) Bugfixes

FCC Launcher 3.234
[Android Head-Units] SoberXDA:
I've tried the latest beta, but to be honest I don't see much improvement:

- application hangs from time to time

- now doesn't show the 4th player (youtube vanced in my case)

- in general the links for 3 players are initially not very reliable. Sometimes I click on the first one and it starts to play the 3th (?). Once all is loaded and started it seems ok, but after each wake up it's not very predictible.

- still sometimes there is an issue with autozoom in minimap. It does not allow to zoom in, immediately zooms out each time I try to zoom in. Workaround is to disable the feature and reenable it again.
[Android Head-Units] SpeedFire-:
If you have a root - LogCat log (see the first post) + Video will help.
[Android Head-Units] hillbicks:
perfect, thanks for the answer. I just reinstalled the unit with FCC and so far so good, but I'll change the head unit type.

One thing I noticed while quickly playing with it. Connecting spotify to it and using the widget, I was unable to play songs. When I press the play/pause button, playback resumes for a second and stops again.

And one last question: I read about TPMS compatibility of FCC but couldn't find it. Do I need an additional plugin for that?

Thanks
[Android Head-Units] ElMery:
Hi,

I noticed the same problem about Spotify but I think it's a Spotify problem.

I guess there is a conflict between phone and head unit.

Try killing spotify from the phone, I resolved in this way

Inviato dal mio SM-G973F utilizzando Tapatalk
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] Latest Alpha seems to work pretty well for the most part... But I've been having an issue for quite a while now with everything not auto resuming after sleep but if I restart FCC (with the icon in the apps), everything pops right up and works as it should. I've tried whitelisting and auto launch and nothing seems to work other than restarting FCC.
[Android Head-Units] SpeedFire-:
Try to remove it from white list. White listing can be bad sometimes.
[Android Head-Units] whitewolf8111:
It hasn't been whitelisted for a while now as it never seemed to make any difference.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

latest Alpha is working well for me .. nothing appears to have been broken, and the players start significantly quicker after a boot or reset.

I have a large number of screens, many with multiple complex widgets etc.

All work well, but I do notice, that while loading, and the HOME screen is displaying, it seems to load up widgets in the order they were last edited.... so if I have recently edited a widget on the Home Screen, then screen loads, and later edited widgets update (I assume) after loading widgets on other hidden pages)

Is there any sort of database sorting, or removing duplicate entries that change a previously loaded setting. ?

If not, is it practice to add a Database sort/optimize tool, that the user can run manually, when their database has been heavily modified , to speed up loading.
[Android Head-Units] SpeedFire-:
Thank you for testing!

Actually, widgets should appear in the order they are located on the home screen.

BUT, we have a new approach in the latest alpha. Previously, all widgets were updated while "black screen" was visible. It did cost 1-3 seconds of loading time.

In a new approach I show the home screen and "not yet updated" widgets and then start widget updates. This should appear like a faster loading with less "black screen" time. Some widgets have a "blank default layout" when they are added - something is become visible only when they are updated. This may look like those widgets are added later than the others. I will try to deal with this in further updates (switch from "black layout" to some "default layout" - btw, this was already done for BT widget and TripCombined widget in the latest alpha). My undestanding is that most such issues relate to the Player Widget.

Since no serious issues are detected so far, Alpha 3.234 is sent to a Beta channel in the Play Store
[Android Head-Units] parisisal:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

i've three pages/screen :

1) A clock page

2) Main page (this is the default screen)

3) Another page,

In the settings i uncheked the "return always to the main screen".

In the page 3 i've a radio background widget (to start and stop the radio).

If the radio is playing and i click on the widget the radio stop and the page remains to 3.

If the radio is stop and i click to start the playing -> the radio starts but the launcher goes to page 2 (the main).

It is annoyng.

It's happen also after go in back camera, or hang a call and so on.

Can you fix ?

I have pro edtion of playstore. (no beta)

The standalone widget (trip time) has display problem :

- sometimes loss the icon (watch)

- when became mm:ss the last digit was cutted.

Regards
[Android Head-Units] segu45:
I installed the last alpha and these are my impressions:

1.- When it restarts after the sleep starts up well, I have three players spotify, pcradio and tunein. When I'm on spotify it works as it should, change to pcradio starts well but sometimes the logo of the radio that I'm listening to does not appear. Change to tunein starts well but the logo appears for a few seconds and then disappears, at this time are the three in the backroom working and when switching between them there is no problem, they start fast.

2.- The biggest problem is in the mimi-map, I have the yandex offline installed off my area. I start in the minimap in google and when I put some color it does not change, besides the zoom goes crazy and starts to move away that I can almost see the globe. Change to yandex online without problem, change to yandex offline and without any problem. When I change from yandex offline and online to google the launcher restarts giving a problem, besides if I press the home key the system asks me again if I want it to be the main launcher. If I do a fcc restart they work as they should.

These are the most serious problems I see for now. Thank you for your great effort and we will continue testing.
[Android Head-Units] King Mustard:
How do I remove this annoying map?

I accidently opened it by opening the Maps app (was curious).
[Android Head-Units] whitewolf8111:
Pressing the same Maps icon in the apps should toggle the map on and off.
[Android Head-Units] King Mustard:
How odd!

Thanks :)
[Android Head-Units] michLQ:
Is it possible to use sygic as map on the widget?
[Android Head-Units] hillbicks:
I just spend an hour reinstalling everything and couldn't figure out why newly installed apps weren't visible for the autostart settings, so I rebooted and what do you know, it crashed again and was reset to factory settings. So now I'm pretty sure that FCC is the culprit and I'll try again by only installing FCC, rebooting and see what happens. :)
[Android Head-Units] Scopesys:
Thanks for the detailed explanation .. so when the "LOADING" icon vanishes from the screen, all Widgets on all pages have finished loading .. COOL ..
[Android Head-Units] djoxdev:
Purchase

Hi,

Is there any other way to make purchase of premium option, since there is not avaible to make purchase with google wallet in my country (serbia)?
[Android Head-Units] hillbicks:
I was able to reproduce the error, in my case it is enabling the wifi hot spot on boot.

On a freshly reset headunit I only installed keepass and FCC. Rebooted the unit, everything is fine. Enabling bluetooth on boot is fine, only if I enable wifi hotspot the crash occurs. Once the tablet has completely booted, FCC launches and then the headunit reboots. This cycle repeats itself 2 or 3 times and then the headunit is reset to factory setting.

Headunit is this one:

https://www.joyingauto.eu/joying-wide-screen-single-din-head-unit-android-8-0-car-stereo.html

As per the recommendation, I chose rockchip PX5+ as the device type, but even with Android tablet as the device type I had the same problem. [MENTION=4292729]SpeedFire-[/MENTION] If you need additional information, just let me know. For the time being, I'll start the hot spot with tasker/automagic.
[Android Head-Units] SpeedFire-:
Unfortunately not. Google Play only.
[Android Head-Units] SpeedFire-:
Do you mean you have selected Start WiFi Hotspot on boot option in FCC after which it crashed? Right?
[Android Head-Units] hillbicks:
Yes, using the start wifi hot spot on start in the FCC settings seems to be the culprit here.
[Android Head-Units] djoxdev:
Too bad...
[Android Head-Units] AbuNwaaf:
A problem in fcc car launcher RTL

After purchasing the application

I encountered a problem in the application from left to right working properly

From right to left, menus disappear and maps remain

The system uses Android 8.0

Arabic

Screen Type 9 inch Capacitive 1024 * 600 IPS Screen with 1080P Support

Is there any solution

Thanks
[Android Head-Units] tonimontoia:
hi, but it is possible to start Viber without opening the screen and then press the back button to return to the home thanks
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

With version 3.234 I found an issue.

Precondition:

PX5 unit completely new setup with OEM 8.0

Installed FCC from Playstore

Backup FCC from Google Drive

All buttons from previous version are shown, even if the app is not yet installed.

Set up all widget related application from Playstore

Workflow:

Uninstalled navigation software (Button on main screen disappeared as expected)

Installed the correct version of the navigation software

Placed the button on the free space on the main screen and adjusted the settings of the button.

Set unit to sleep and waked it up after it reached the sleep mode

Observed behavior:

New created button for Navigation not visible.

Additional new button cannot be placed on the free space on the screen.

Seems that

Expected behavior:

A new created button could be placed on a free space.

Workaround:

Move buttons around, place the new button at another place and move all buttons around until the set up is as expected.

Attachment:

Screenshot (The small icon needs to get placed on the free space.)

View attachment 4796352
[Android Head-Units] Obi8:
Hello can i use this launcher with mtce radio android 9?
[Android Head-Units] VBA_Dev:
Hey [MENTION=4292729]SpeedFire-[/MENTION] I have changed my setting on my Sofia head unit to use rockchip as you advised, but the media widget still does not show Bluetooth song info.

Also, as the Sofia is not MTCB or MTCD (as far as I know) what should I be choosing for my head unit?
[Android Head-Units] rigattoni:
Additional Notes from my tests today on the bench:

Because I switched off the power supply last night, the unit made a complete cold boot.

The yesterday added additional buttons are not there anymore. Seems to be an additional issue with persisting.

So I tried to add the buttons again:

As I wrote yesterday, there seems to be a button which prevents from position another button.

Unfortunately this button can not be deleted, because you can´t move it.

If you long press on the hidden button, the settings menu opens and on first try you can see the hidden button as empty rectangle. There you can resize the button in all dimensions, but you can not drag it.

If you try it again, the hidden button is not marked with the resize rectangle.

Next steps:

Saved the settings from FCC to SD card --> done [MENTION=4292729]SpeedFire-[/MENTION] if you want to get the file, please give me a hint.

Uninstall FCC and give it a new try.

Attachments:

Original desktop (background has not been changed after new set up)

View attachment 4796797

Shown rectangle on desktop.

View attachment 4796795

View attachment 4796796
[Android Head-Units] Scopesys:
I'm not impressed easily, but I have to congratulate you on that Bug Report.

The best I have seen anywhere --in many years.

You have raised the standard of what a Bug report should be ... and with that detail, it must greatly help the developer, both find and fix the reported issue.
[Android Head-Units] SpeedFire-:
Yes, that would be great. Thank you for such a detailed bug report.
[Android Head-Units] rigattoni:
Just have a look into your postbox. :)
[Android Head-Units] SoberXDA:
Hi!

I'm not able to zoom in anymore in the minimap. Even with auto zoom off! Using the beta version. But also occured in official one as far as I remember.

https://youtu.be/IUacASPsxRA
[Android Head-Units] Smess1210:
I have also witnessed this behaviour recently....

Sent from my ZX81
[Android Head-Units] djoxdev:
After purchase of premium ODB widgets not working. After few seconds they freeze. Only after complete reinstall of FCC they work again for few seconds and freeze again...

This device: https://www.aliexpress.com/item/32869811500.html
[Android Head-Units] SpeedFire-:
I have spent more time than I planned on this.

Alpha 3.236:

- TPMS app is extracted into a separate FCC TPMS Plugin because this was the only way to get rid of those annoying requests for access to the USB port. FCC Launcher's TPMS widgets will continue to work as before but you will need to install FCC TPMS Plugin for them to work (TPMS Plugin can be installed only directly as an apk). The most difficult part here was a fast and simple communication between two separate apps (which was finally done).

- As [MENTION=9325785]Scopesys[/MENTION] asked TPMS widget has one of the styles when only "OK" or particular issues (like "Air leak!") will be displayed on the TPMS widget (this compact widget style shows an aggregated status for all TPMS sensors / tires).

Downloads:

FCC Launcher 3.236 Alpha

FCC TPMS Plugin
[Android Head-Units] SpeedFire-:
Please try FCC TPMS Plugin 1.09:

Download
[Android Head-Units] lcha:
Great, no more crash.

But there is some other things :

At every start I have to validate usb permission (I always check the remember box)

Cold start : fcc tpms ask for usb permission.

Hot start : sometime ask, sometime not. If not, widget show no values - - - -. I open FCC TPMS, had to validate usb and it's working.

After some time (approx 1 min) widget display (pressure + temp) is lost (display is - - - -). I clic on widget, fcc tpms app open with good pressure values, get back and all TPMS widget display ok... Then lost less then 1min later.

Spare Tire is no more display in FCC TPMS (even if checked).
[Android Head-Units] lcha:
Ok Google call [name]

I try Phone calls via connected phone using 'Ok Google call [name]' and it's not working.

May be it because of android 9.

I try MTC Dialer modified by scorillo (https : / / github.com/scorillo/MtcDialer/releases/tag/1.2.3) for android 9.

It's working but only without FCC Launcher. FCCLauncher seams to select itsef for dialer when using "Ok Google call [name]"

Another thing :

Google assistant propose 3 apps for dialing : Bluetooth phone, FCC launcher and MTC dialer.

I choose MTC dialer for default app for dialing.

When FCC launcher is on top : "Ok Google call [name]" use FCC launcher => Not working on Android 9

When another app is on top (for example poweramp) : "Ok Google call [name]" use MTC Dialer => Working as expected.
[Android Head-Units] lamparts:
I extracted the APKs from my ATOTO. I PM'ed you some information about the AOTOTO and a download link for the APKs.