yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
Please also try this version. FCC 3.353v2
[Android Head-Units] liamstears:
Thank you, I can test tomorrow, do you think this has fixed my problems?

As for APK's I have uploaded every APK from the latest January 2020 CSN2 firmware and uploaded them for you here: https://www.androidfilehost.com/?fid=4349826312261709622

Hope this helps
[Android Head-Units] nokian95ita:
I was waiting the mtk support tomorrow i Will test It in special modo the volume control and the steering whell function

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] rigattoni:
Is it possible that you activated "Restore volume on autostart" ?

[MENTION=4292729]SpeedFire-[/MENTION]

With activation of this setting, exactly this behavior is seen also on my device. FCC switches the volume 2-3 times, even if you change it in between.

On my device the volume is set always to 1, even if I set it in FCC to any other number. (Just now 20)

For this to show, I just grabbed a logfile and attached it.
[Android Head-Units] SpeedFire-:
Unfortunately APKs taken directly from a firmware image cannot be used.

You need to take them from a rooted device with this firmware installed (better to use RootExplorer app to copy them)
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

He has the same firmware as I do. The only difference is the MCU.

Give me some minutes and I will provide a link by PM.

---------- Post added at 03:27 PM ---------- Previous post was at 02:53 PM ----------

[/COLOR [MENTION=4292729]SpeedFire-[/MENTION] You got PM.

---------- Post added at 03:28 PM ---------- Previous post was at 03:27 PM ----------

[/COLOR [MENTION=4292729]SpeedFire-[/MENTION] You got PM.
[Android Head-Units] SpeedFire-:
Thanks for the log. I tried to fix this. Please check: FCC 3.353v3
[Android Head-Units] rigattoni:
No, this does not fix the issue.

I set it to volume 8 in the settings, but FCC switches it still to 1.
[Android Head-Units] SpeedFire-:
Please try another one: FCC 3.393v3
[Android Head-Units] rigattoni:
Same behavior as before...
[Android Head-Units] SpeedFire-:
Please try to change volume manually to let's say 10 and then restart. Please also record a log of manual volume changing.
[Android Head-Units] rigattoni:
Okay, I set volume to 10 and sent the unit into deep sleep.

After wake up, I waited until the first volume bar with "1" popped up and I changed the volume manually. The second volume bar came up and reset the volume to 1 automatically.
[Android Head-Units] SpeedFire-:
The issue is because FCC Launcher doesn't receive updates of volume value (probably this can be checked by putting Volume widget on home screen - it will not change its value when you adjust volume manually).

So I need to find how to get this data for your device. Thanks for apks.
[Android Head-Units] rigattoni:
Yes, you´re right.

The widget does not get updated if I change the volume manually. It always shows "1", nothing else.
[Android Head-Units] SpeedFire-:
I'm not sure this will help. But let's try: FCC v3.353v5
[Android Head-Units] liamstears:
Thanks for the continued updates, I will also try to check these updates as and when I can but unfortunately I am quite busy

As for apks can I ask why you say apks from an image are no good for you? I don't understand this as I have done lots of work on apks previously including ROM building and the apks in an image and on a device will be exactly the same? They are simply copied.... Sorry maybe I missed something?

Also I have a request if it's possible, on my device I have a vehicle info app which shows speed in kmph, would it be possible to pull this info into FCC for a more accurate speed measurement? Although for my use in the UK this would need to be converted to mph....

Thanks so much again, btw have I missed a donate option? I would like to contribute to your time and effort as it's much appreciated as this is by far the best Android launcher for car
[Android Head-Units] Waveler:
Hi, just wanna seek assistance with the steering wheel control when using FCC. The SWC works for the stock radio app but does not work on Spotify, poweramp etc. I tried to remap the SWC on FCC but it does not do anything when I press any key.
[Android Head-Units] SpeedFire-:
Yes. I downloaded your archive and apks seems good. Previously I had many cases when apks taken by someone from firmwares were corrupted and unable to be used. These look good.

Please send me this speed app. However, where do you want to show this info?
[Android Head-Units] liamstears:
Oh I see, yes I like to extract firmware properly so I can actually do some work on the files ?

As for the app I cannot look at the moment but may be able to later on today but it will be in the zip I sent, from the top of my head I know the icon for the app is very similar to the icon used for the canbus settings app so it may be the same app and the APK for that is called "mycarservice. APK", on the device it calls itself "Vehicle Info" and having a quick look in the zip I sent it actually looks like it may be the canboxsetting.apk

As for where it would be nice to have a seperate widget for this speed...
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

this version does set the volume as expected.

Great work!!!

Thanks a lot for your support.:highfive:

The app [MENTION=682191]liamstears[/MENTION] is talking about is correct. It´s the CanBoxsettings.apk.

We are both on the same firmware as I wrote, The only difference is the MCU, because he has a CSN2_D unit. This is the only difference.
[Android Head-Units] SpeedFire-:
Great! I am glad it works now. Does the volume actually changes by the FCC Volume Widget?

What is not yet integrated for CSN2 based on your observations? Except for Standard player (which is impossible to integrate) and wheel buttons (which are hard to integrate)..

Regarding CanBus. I'm not yet ready to integrate it on any platform. They are even more specific not only to device but to the car model as well. Really hard to test and support.

What I can try to integrate are the indicators which are accessible in status bars (like acc voltage or outdoor temp on some devices). Btw, please try to put Voltage widget it may show Outdoor temp for your devices (yeah, I know, but I haven't created a separate widget yet).
[Android Head-Units] ric69:
Hello since yesterday I'm using custom Malay rom on my px30 but there's a conflict when ignition off. Unit doesn't restart. I had to uninstall FCC. Too bad

Edit : I reflashed rom with wipes. Every thing perfect now. Apologize. Was my mistake sorry
[Android Head-Units] rigattoni:
The volume widget just shows the preset volume (set in FCC settings). It does not change on manual changing the volume.

The voltage widget seems not to work, even if the voltage is shown in the status bar. As the unit is not mounted in my car I cannot say if it would show the outdoor temp.

May be I find the time to change the units in my car, I would update my comment.

View attachment 4935659
[Android Head-Units] jhony benitez:
I'm trying to configure odb2 for using fcc widgets.

Although odb device is paired and working with other software, when I try to configure in fcc it says "paired" but doesn't work. Besides, if you try to identify in fcc your odb device it says there is any

Could someone help me to configure it, or let me know where can I check instructions or manual?I would like to show range in widget. Thanks friends, any help is welcome

Enviado desde mi SM-G975F mediante Tapatalk
[Android Head-Units] rigattoni:
If you are on Malaysk ROM you are rooted. So why don´t just store a logcat file so that [MENTION=4292729]SpeedFire-[/MENTION] is able to see what´s wrong and if the launcher is the reason? :confused:
[Android Head-Units] SpeedFire-:
Can you record a log of manually changing the volume and then changing the volume from the widget?
[Android Head-Units] rigattoni:
Okay, did it.

What I observed is, that the volume set in the widget overrides the startup volume.

I set the startup volume to 8 and changed the volume in the widget to 3. On next startup, the unit started with 3 instead of 8.

So you will get 2 log files.

The first file View attachment 4935709 shows the manually changing of volume in running system. First a couple of times manually with soft buttons and afterwards a couple of times on the widget.

The second one View attachment 4935713 shows the behavior with different settings on the widget and in the FCC audio settings.

Widget is set to 3 and autostart volume is set to 8. The unit starts up with volume 3 instead of 8.

Edit:

Even if I remove the widget, changes in the autostart volume don´t have any effect. The volume on startup is still set to 3 even if the settings show 9 now.... strange... seems to be persisted anywhere.

Even a complete reboot did not "repair" this issue as visible in the attached 3rd log file.
[Android Head-Units] liamstears:
Thank you SpeedFire- making amazing progress

My opinion on CSN2 integration is that it is almost complete, mainly it is little bugs rather than anything missing. For me to say 100% complete CSN2 integration in an ideal wold I would like: (But of course I don't expect it, you do what you can and I am grateful)

1. Volume control fixed with widget (I know you are currently working on this)

2. Wifi/Bluetooth widget to correctly display bluetooth status - At the moment you can click bluetooth icon and it opens bluetooth but icon makes it look like there is always a bluetooth connection, if there is a way to show if its connected or not that would be great, I know there is option to have notification in status bar for connection, maybe this could be used to fix this?

3. Wheel Buttons - Or should I say button? - This I expect is more per car specific but for me all wheel buttons work fine I just have 1 button in the middle which on standard head unit is for voice, I would love to be able to map this to google voice search but so far cannot but this is more limit of headunit than FCC right? I wish I knew more about smali as I would try to reverse engineer what that particular button does and remap it to voice search as at the moment it does some sort of toggle between inputs which is so unhelpful (switches to inputs not used etc)

4. Canbus speed - I know you say you are not ready to integrate canbus functions and I understand but I would kindly request if you have time that just the speed option is looked into (this is something universally will be used and appreciated by many). On PX5 using the apk I told you about I can only assume there must be a general value that is used to display this in the app, if there is some way you can intercept that I would assume it would work quite generically across multiple vehicles and devices if the same apk is used. I am assuming a bit here and just hope you can take the time to look

Thanks SpeedFire- :D
[Android Head-Units] SpeedFire-:
Looks like an important issue? Can you describe/show it in more details? What exactly happens and why it doesn't allow to use the launcher?

Thanks!
[Android Head-Units] SpeedFire-:
This was by design.

The volume was set to the lowest of two: last volume and preferred volume.

In this new version I've added a checkbox to disable this behavior (please note that Volume on boot is now a separate preference): FCC 3.353v6

Regarding the volume it is not clear from the log what is wrong. Looks like you change the volume using the FCC controls and it changes. If it is not actually changing can you please record a short Video+Log?
[Android Head-Units] ric69:
Absolutely not ... I'm really sorry, I reflashed rom with wipes (manually in recovery this time) it seems to be working perfectly now :silly: I apologize sincerely
[Android Head-Units] SpeedFire-:
Great. Thanks for the update [emoji106]
[Android Head-Units] rigattoni:
May be I explained wrong... my fault... :eek:

The problem was, that FCC ignored the boot volume set in audio settings after I changed the volume in the widget.

Widget volume set to 3

I manually changed the volume manually with soft buttons to 5,

audio startup setting in FCC was set to 8

Observed behavior:

Volume on startup =3

Additional workflow:

Removed widget

changed volume with soft buttons to 5

switched unit to sleep mode

waked up unit

Observed behavior:

Unit still waked up and volume changed to 3 even the widget was not acitve.

Even complete reboot (completely removed power from the unit) did not heal that.

Expected behavior:

Inactive widget should have no influence on volume.

Regarding volume widget:

The widget does not get updated if you change the volume by steering wheel button or by soft button or volume knob.

The widget is first updated if you use the widget to change the volume.

Final statement:

Now with the new setting the situation is completely okay.

Lowest volume is used on startup, regardless which setting is higher.

So all fine now. :good::highfive:

Edit:

[MENTION=4292729]SpeedFire-[/MENTION]

I need to withdraw my final statement:

The widget has still influence on the volume even if it is not on the screen.

I just now have manual volume set to 12 and start volume to 8.

The unit starts up with 4 as it was before I removed the widget.
[Android Head-Units] nokian95ita:
Dear Developer

i installed the latest version of fcc with mkt 8227l support. Generally the use is much improved, however it is still not possible to intercept the steering wheel controls and configure a new operation for the same. while the mini map of yandex now works much better than the google one since this navigator leaves in the cache the map that has already been traveled
[Android Head-Units] SpeedFire-:
Regarding cache on Yandex. You can download Yandex Maps (not Yandex Navi) and download offline maps. Some users say that FCC will use these offline maps ;)
[Android Head-Units] nokian95ita:
a little while ago I went around and I add that it doesn't even regulate the volume with the speed control and no regulation of screen brightness

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] dagosjt:
Hello,

I had some time this weekend and this is what I discovered:

1) The MiniMap works well, what I saw was a temporary glitch dued to hotspot connection. So no problem.

2) Radio FM works inside the Player widget if I start from scratch. Instead if I use the backup from tablet there is no way to make it works, even if I delete the original widget and I create a new one. It seems like something saying the RadioFM doesn't exist (true on tablet) is saved somewhere. Is there any hope to correctly restore a backup made on a tablet to a HeadUnit with RadioFM working? Some options I didn't see maybe? For me it would fantastic to plan new layouts on the tablet, it's much easier than directly on the HU.

3) As I said Radio FM works inside the Player widget, but a little different from the others player. While clicking on Poweramp/Google Play Music the correct music start immediately when clicking on switches, to let Radio works I need to click before on switch, then on "cover", this brings in foreground the Radio app, and finally I can return to FCC and see the updated info in widget. Is designed to be in this way?

In other words, wonderful job, simply asking if there can be room for further improvements about what I experienced.
[Android Head-Units] SpeedFire-:
Probably you forgot to change a device type (which is required to enable proper "deep integration" with your head unit). Please go to FCC Settings - System - Advanced - Device type
[Android Head-Units] SpeedFire-:
Some further MTK 8227L integration: FCC 3.353v8
[Android Head-Units] nokian95ita:
dear speedfire the latest beta adds an important element to the integration with the 8227l models. Now the brightness control works very well as does the volume control with the speed and for this reason I decided to buy the premium version. Globally, stability has also increased although with Amazon music and Sygic the launcher continues to restart instead of remaining in the background. Nothing to do instead in the interception of the steering wheel controls that are still not correctly identified. Thanks for the work you do and I'm happy to have supported you.

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] Ericang:
Hi how do we change away the blue the color of the "selected widget" hightlight?

i uses a wiresless keyboard to "tap" it around

i had upgraded to premium but i cant find the option to change the blue highlight to other colour

The weather widget

Able to enable resizing of the weather icon as well ?
[Android Head-Units] chrissooo:
Hi,

Good News: i have buy the Premium Version :)

Now i Test the Beta in Play Store and see you add MediaTek support. I will report some things that dont work:

- Radio shortcup in Player dont start radio and dont show radio info

- Phone shortcut dont work

i will test more.

thanks
[Android Head-Units] dagosjt:
Thanks a lot, that was the problem! I'm sure I checked but probably I imported once again the backup doing my tests and the Device Type was reverted back to "Android Tablet". Switching to "Allwinner" the radio worked as described before (click on widget switch -> click on cover -> Radio FM is launched in foreground -> click on home -> FCC Launcher back in foreground and widget updated). While with other players simply clicking on the widget switch start the relative music... Just to be sure if this how it's expected to work and there is no way to switch to Radio FM directly from widget.

Now that I can play more on tablet hopefully don't losing time, I'll check better all the options because there are a lot of them even in free version, already thinking about some suggestions...
[Android Head-Units] bossman4:
I installed this latest Alpha version on to my Pumpkin unit with the MTK chipset. I did not test a lot of things at this time, but I did notice something peculiar.

When I installed the original 8227L alpha from Speedfire, it installed a lot of apps that showed up on the file explorer. Those "apps" did not show up in the APK installer, but they were there in the file explorer..

Radio

So there are three "apps" in my file explorer now.

Car Radio

Radio (Orange Icon)

Radio (Blue Icon)

There are no icons in the file explorer that are titled "FM Radio"

Two of the app choices will pull up the FM radio (full screen) on the file explorer screen if I pick them, one does not. Obviously, I need to get rid of the duplicates, eventually.

The FCC Quick menu setup allows you to install different media players. It has a short list of available media options in the setup screen that it sees in my system. One of the options is "FM Radio", but there no other .....radio.... apps to pick in the FCC Quick menu. I would think that FCC would pull up one of the ......radio..... apps that I have, for a choice in the Quick menu. If I pick the "FM Radio" for use in the quick menu, it does nothing when I pick that media choice. The following apps are not shown as options in the quick menu setup screen.

Car Radio

Radio (Orange Icon)

Radio (Blue Icon)

rather than app titled "FM Radio". Perhaps that is why FCC quick menu does not play the car radio on my particular unit.

I will look further at other 8227L integrations, but so far I did see that issue......
[Android Head-Units] chrissooo:
Hi,

Good News: i have buy the Premium Version :)

Now i Test the Beta in Play Store and see you add MediaTek support. I will report some things that dont work:

- Radio shortcup in Mini Player dont start radio and dont show radio info. I have set in Quick Playerlist "FM Radio". That was only one FM Radio.

- Phone shortcut dont work

Then i try your tpms Sensor Plugin, but cant Pair my sensors. I have a original App from my sensosrs that show a ID from witch sensor. is it possible to use it? Look Screenshots

i will test more.

thanks
[Android Head-Units] nokian95ita:
after other tests I point out that on mtk the Launcher does not always remain active in the background but often restarts

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] KitF:
[MENTION=4292729]SpeedFire-[/MENTION] Is this possible on stock? I know Malaysk has the option but no idea if a launcher can get the info by itself.
[Android Head-Units] nokian95ita:
good evening therefore the version published yesterday on the PlayStore is different from the v8 in that the latter controls the brightness while that of the PlayStore does not. furthermore, I have concerned the programming of the controls on the steering wheel and a toast appears where he looks for a rockchip and not a mediateck. unfortunately the problem of rebooting has not yet been resolved and also the music widget with both Amazon and PowerAmp shows the title of the random song and not always as well as the notification with the song thanks always for the great work you do

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] mclaudio:
hi there

is it foreseen to integrate intel airmont integration?
[Android Head-Units] Ericang:
[MENTION=4292729]SpeedFire-[/MENTION] The song title strolling in the music player is not smooth if the song title is too long. Able to fix that to continuous strolling ?

---------- Post added at 10:07 PM ---------- Previous post was at 10:07 PM ----------

[/COLOR [MENTION=4292729]SpeedFire-[/MENTION] The song title strolling in the music player is not smooth if the song title is too long. Able to fix that to continuous strolling ?
[Android Head-Units] VladimiroCampus:
Troubles on Erisin ES7909FS on Focus2008

Dear Developer, ty for your great work.

Hi have FCC CL premium version on PX5 Erisin ES7909FS 4gb/32 With Hal9k 4.01 Android 9 MCU Mtce 3.37.

I've experienced these issues:

I can't use vocal command to say Ok google, call someone.

I tried with mtcdealer, tried with FCC as deafault dialer app, nothing changed.

Often rear camera stops working. I have to disconnect HU for 4 min.....

SWC often don't work....i must reset and then works for a day or two.

I dont have canbus, and with native car laucher of Hal9k in didnt experience these issues....

Do i have to lesect someting in advanced FCC CL configuration?

TY for the attention, regards.....
[Android Head-Units] Scopesys:
I also experience this, Long titles not scrolling smoothly, but this only seems to happen for a few minutes after FCC starts, After that, there is a significant improvement in the smoothness of the scrolling, and it becomes quite acceptable.

In fact, I see this more as a FEATURE, than a bug .. when it is not scrolling smoothly, it indicates that FCC is busy "initializing" itself, and then when it starts to run smoothly, it would indicate that FCC has finished that startup process, and is now running smoothly (ie has the time now to update the scrolling in a smooth manner)

So, the sooner it settles down and starts scrolling smoothly, the better FCC is getting at starting up quickly, and this has been getting quicker and quicker over the past year of updates. :)
[Android Head-Units] Scopesys:
You still have to look at the screen long enough to READ/recognize the text characters N,NW,W,SW,S,SE,E & NE.

The solution I took was to make a very small version of the Compass widget - one that took up only one small Square on the Home Page.

Then a very simple Compass background png, and a suitable Arrow png.

The advantage is that all you have to do is a quick glace at the small square compass widget out of the corner of your eye, to get a mental picture of where the arrow is pointing, before returning concentration to the road. Then with that mental picture of the arrows direction, you can relate that to the approximate direction.
[Android Head-Units] sbruda:
That's what Torque does too (a bit prettier maybe but the idea is the same) and does not work very well for me. I can recognize letters and digits (preferably plain white with no decorations) with less effort than the direction of that arrow. To each his own I guess (the only difference being that your preferred rendering is possible in FCC and mine is not ;)).