yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] whitewolf8111:
I think this is the correct bluetooth apk. I found it under: / -> system -> app -> Bluetooth

I also found a "Bluetooth MidiService" too, not sure if that would be of any help?

Here's a link to the bluetooth apk

https://drive.google.com/file/d/13nheUvFZVlSXH4piAf3OrmP_43jw67qt/view?usp=sharing
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

here is my BT app.

I tried all available profiles, no other profile worked for getting connected to the phone.
[Android Head-Units] Scopesys:
Player Widget improved (?) but it still has a Mind of it's own, sometimes it updates, sometimes it does not, sometimes it goes crazy, and jump about between the players, or the other players Artwork and Information.

The impression I get is that an any particular time, FCC does not really now which Player has been selected, or it it does, it is getting the wrong stored information that has been saved for another player.

Often it will get the WRONG Player's information, and then a second later, update to the right player's info at other times, it will not update at all.

The only Player that always works 100% of the time is the FM Radio, and often switching to the FM Radio 1st, before selecting a different Player, will cause that newly selected player to display correctly.

So, while there is a WORK AROUND (that works with recent Version), of always selecting FM Radio before selecting a different Player, it still really needs to be "Fixed" to work correctly going forward.
[Android Head-Units] sambhasanbiswas:
Am having a strange issue with the street name on mini map. I see that on my android phone street names are quite sensible (probably pulled from google) but on my car headunit it is quite crapy though settings on both the device are identical. Even in the car autosizing of street name doesn’t work at all.

SpeedFire can you please explain the reason behind this? And moreover I would love to get street/location names from google maps. Is this possible?
[Android Head-Units] SpeedFire-:
Hi!

What players do you use? I will try to reproduce these issues.
[Android Head-Units] sambhasanbiswas:
Can we create a shared document like google sheet to keep track of the music players and keep a track of the issues? I think that might be helpful for all to track!

I use a regional player ‘gaana’. With this player i can pause the music but not resume it again. I use steering wheel controls to resume the same.
[Android Head-Units] Scopesys:
Thanks - MUCH APPRECIATED :-

I am currently using as Quickplayers

(1) FM Radio (Eonon's Radio tuner)

(2) BlackPlayer Pro

(3) Spotify (in mode both Online & Offline)

But basically, its the same for any players I select as #2 & #3

AS I said, selecting the FM Rafio between selecting other players, seems to help significantly in having the newly selected player getting the correct Artwork & Song/Artist text.

It uses to do the same with PowerAmp, but since you identified an issue with Poweramp, I stopped using it and switched to BlackPlayer (even though you had a work around in FCC for the Poweramp issues)
[Android Head-Units] SpeedFire-:
I use the same set of apps with no issues. Can you please record Video + LogCat?

Please also check that you are on 3.217 version and reboot your device.
[Android Head-Units] SpeedFire-:
This apk is corrupted. You need to copy it using RootExplorer and only from your head unit (not from an unpacked firmware).
[Android Head-Units] SpeedFire-:
The same issue is with this apk.
[Android Head-Units] Scopesys:
Unfortunately, my Eonon is not rooted.

The issue I am seeing may be because I have Multiple copies of the Player Widget on the same page, displaying different things, in different parts of the Screen.

I have attached my FCC Backup. Maybe you can try that and see if you see the issue with my Home screen.

Hopefully, if you can see it happening, you can debug it on the emulator easily. and maybe if it cause by multiple copies of the widget, there is a way to fix that so it can work with multiple instances of the widget on the same page.

(it is a Zipped copy of the fccbackup file, (not the file Renamed with a zip extension added, so it will upload to the forum)
[Android Head-Units] rigattoni:
:confused:
[Android Head-Units] whitewolf8111:
Here is another one copied with RootExplorer. You might not be able to install it as it is a system app. This (and the other one) was pulled from the directory of my head unit.

I'm running the latest Malaysk ROM (in my signature). Are you able to install that ROM on an emulator or something (I would love to know what emulator to use for that too)?
[Android Head-Units] whitewolf8111:
He's saying your APK is corrupted too.
[Android Head-Units] rigattoni:
Yes I know what he means, but that is nearly impossible, because I copied the folder (not only the APK) directly from my unit... with FX and root rights.
[Android Head-Units] whitewolf8111:
I can't even reinstall the apk from the same directory as its stored in. I was thinking maybe it had something to do with the author locking it somehow.

What ROM are you running? I'm running Malaysk ROM
[Android Head-Units] rigattoni:
I´m using stock ROM.

Got an update yesterday which will be installed tonight (need to root afterwards again, but this is routine in the meanwhile.) I will test the apk myself, if I am able to decompile it.
[Android Head-Units] crazycarl123:
Speed Dependent Volume Control

[MENTION=1633144]speedfire[/MENTION]

I am on version 3.217 of FCC Launcher and the speed dependent volume control doesn't work properly for me.

If the volume has been adjusted by FCC Launcher and I change the volume manually more than once with my steering wheel controls (it doesn't matter if I go up, down, or a combination) the volume gets reset to the base volume that the head unit was set at before FCC Launcher started adjusting the volume based on speed.

If I don't try to adjust the volume manually after the volume has been adjusted by FCC Launcher then everything works fine. Also, if I use the volume widget to change the volume manually then everything works properly.

So the problem only happens when the android volume toast notification comes on screen showing that the volume has changed. When using the widget to change the volume this doesn't happen and there are no issues.

I would like to be able to change the volume with my steering wheel controls manually after FCC Launcher has changed the volume based on speed without the volume getting reset to the base volume if possible.

Is this something that you are aware of and working on or something that you could look into?
[Android Head-Units] rigattoni:
... new try...

I was able to decompile the APK, so it should be okay.
[Android Head-Units] whitewolf8111:
How did you end up getting yours?
[Android Head-Units] rigattoni:
Nothing different. I just used a fresh formatted SD card... just to be sure that the SD would not be the reason...
[Android Head-Units] SpeedFire-:
I can't decompile it :(
[Android Head-Units] rigattoni:
:confused::confused:

Okay, attached the decompiled app. May be you are able to find the reason in it.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Ref: Issue I was having with Player widget, not displaying correct Artwork, artist, song etc.

I think I have found the cause and have corrected it.

Sorry -- It was because I was using Multiple Instances of the Player Widget on the same page, each instance displaying something different.

One instance was the Player WIdget just displaying the Quickplayer selection at bottom of page.

This obviously needs to be configured to select the desired quickplayers players.

However, initially I had all the other instances, also defining the same set of quickplayer.

This was causing the issues.

If I deselect QUickplayers (ie Bank) in all the other insatnces of the Player Widget on that page, so ONLY the QUicjplyer select instance has the quickplayers defined, all works smoothly.

In hindsight, that would be the logical thing to do, but requires one to edit & de-select the quickplayers,, if you add additional instances of the Widget to the same screen, as by default, new instances inherit the quickplayer definitions previously defined.

I am reasonably sure this has fixed the issues, after editing the widgets, it seems to work correctly 100% of the time now ... time will tell.

---------------

I don't know how many other users of FCC place multiple Instances of the Player WIdget on the same Page .. it is certainly possible to do, and can provide a very nice interface -- but be warned, it looks like only the Instance that selects the quickplayers, should have quickplayers defined, other instance need to have the quickplayers defined as "None"

[MENTION=4292729]SpeedFire-[/MENTION]

One way to help users with this might be to not have additionally added Player widgets INHERIT the Quickplayers name -- ie have new instances start off with the quickplayers undefined.

Obviously -- your call :)
[Android Head-Units] SpeedFire-:
Actually, I don't think this was the reason of the issue. At least I can't think how multiple instances can affect the widget behavior. They shouldn't. But I will try to reproduce.

Update: I restored from your backup and while everything was fine 99% of time I was able to reproduce an issue by quickly changing between quick players. It was caused by incorrect assignment of player package name to the track / artist data because of too fast changing. This issue will be fixed in the next version as well (hopefully).
[Android Head-Units] Scopesys:
Many thank for investigating the issue, and hopefully fixing a potentially remaining bug. It will be wonderful if this instability is finally eliminated ...
[Android Head-Units] SpeedFire-:
Unfortunately, this is not exactly what I need. These are only resources decompiled. But I need more (the source code).

Please try to copy apk with this app: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
[Android Head-Units] rigattoni:
3rd try...

Downloaded with the expected App, but the Bluetooth.apk are byte identical.
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] was my second one able to work for you? I copied it using Rootexplorer.

https://xdaforums.com/showpost.php?p=79118826&postcount=3467
[Android Head-Units] tonimontoia:
but what is this Bluetooth application for?
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

I think we ran into the wrong direction...

Please see the attached file. Seems that this apk should be the correct one...
[Android Head-Units] tonimontoia:
[MENTION=1633144]speedfire[/MENTION]

what does it mean to say this error? always worse this launcher
[Android Head-Units] iRcKenny:
Simply you need an your own Maps API Key, follow this link
[Android Head-Units] SpeedFire-:
Yes. This is the working version. Thank you.
[Android Head-Units] whitewolf8111:
What directory did you find yours in?
[Android Head-Units] Scopesys:
Really looking forward to this update :)
[Android Head-Units] SpeedFire-:
Beta 3.219:

- Rockchip devices: new BT interface v6 added - for some devices on which BT calls previously didn't work

- Player widget fixes

[MENTION=2534110]rigattoni[/MENTION] your BT interface was unique. Please try v6 added in this latest beta.

Direct link: Beta 3.219
[Android Head-Units] rigattoni:
I will update my unit this afternoon and give feedback on it.

Thanks a lot for your great support.
[Android Head-Units] Hammerhand.17:
[MENTION=4292729]SpeedFire-[/MENTION] is there any chance that you implement tesla units support?
[Android Head-Units] SpeedFire-:
If you mean deep integration then - I doubt so (without purchasing the unit). They are too different from a normal Rockchip. Actually they are a whole new platform.
[Android Head-Units] Hammerhand.17:
Yes, that I thought. I wish I would be able to help, but my knowledge is not enought to go that further. The truth is that for now I am happy, because they refunded most of the money I paid for it (due to their fake advertisement of the units being 7.1, when they really are 4.4), but your launcher is fantastic and it would be awesome to be able to control the units to a deeper level.
[Android Head-Units] SpeedFire-:
I need to order the same unit and refund my money LOL ;)
[Android Head-Units] rigattoni:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

the new v6 works as expected.... really good job!

I think most of the newer Klyde units should come around with this BT version. So it´s probably not a unique solution.

Thanks a lot for your great work. I appreciate your fast and unique support. Never seen that so far. :highfive:
[Android Head-Units] SpeedFire-:
Great! Can you please post your device info, so I can automatically apply this profile to similar units?

Go to FCC Settings - About - Scroll to the very bottom
[Android Head-Units] Hammerhand.17:
It could sound like a dishonest thing to do, but they really advertise their units with specs that are false, even when they know they are. If you want a link, just contact me :laugh::laugh:
[Android Head-Units] Scopesys:
THANK YOU .. Player widget is "FIXED" .. never worked this well before.

It's so amazing to be able to change Players, and they work 1st time, and update correctly.

YOU ARE AMAZING ... Thanks
[Android Head-Units] Julian75ts:
Hi.. Sofia user.. which setting May i use.. android generic tablet or Rockchip?

Many thanks
[Android Head-Units] Scopesys:
Has anyone tried FCC on a Honda Hacked Honda Head Unit ???
[Android Head-Units] VBA_Dev:
[MENTION=4292729]SpeedFire-[/MENTION] Please add artwork support for Audify Music Player

https://play.google.com/store/apps/details?id=com.musicplayer.playermusic

Many thanks
[Android Head-Units] Smess1210:
The v6 BT interface seems to have sorted my Pumpkin px5 issue... Very good work [MENTION=1633144]speedfire[/MENTION], if nothing else has been changed with this beta, fcc is working perfect and stable on my Pumpkin branded px5 unit.

Is it possible to have the speed displaying mph and the altitude displaying m or is this a limitation of the metric-imperial conversion?
[Android Head-Units] millab:
My BT interface wasn't working on my Eonon GA2171S MTCE PX5 and I think this might solve mine too - I don't have my car back from the workshop for a few more days but can't wait to test it!
[Android Head-Units] SpeedFire-:
Beta 3.220:

- USB keyboard movements should now be visible on all devices.

- Altitude ft/m units can be selected independently from speed's mph/kmph
[Android Head-Units] Scopesys:
Player WIdget now Fixed. BT fixed for many more users .. Amazing Progress with FCC :)

[MENTION=4292729]SpeedFire-[/MENTION] maybe when the pressure is off, and you get some time, you can review the GPS Street Name widget, that currently randomly pick up the side streets, and Cross Roads.

It's a nice feature that it can, but is is intermittent and not consistent.

Maybe the Street Name could have a Two Line Display. One for Current street name that you are driving on (filtered so it does not change unless the street name has changed for some distance.. and a second street name line, that only shows side streets ( ie Blank, or side-street, but never the same as the main Top street name).

Maybe the side-street name could be retained for a minimum distance, unless an new side street is detected.

Once you get into it, and a little AI added, it should, become clear what is a good design and good compromise.

The Speed Limit Widget may also in need of a little improving.

Sometimes it does not change when it should, and sometimes it displays blank for short periods, while you are driving on a road with a speed limit. (Picking up side streets maybe without designated speed limits),

If the plan is to restore the Over Speed warning sounds, the detection of the actual speed unit should be improved to be more reliable first.

I personally would very much like to see the option for Over-speed audio.
[Android Head-Units] bossman4:
I just tried the new version on a 15 minute drive. I am splitting my time between the Eonon FM radio, Powerplay and Spotify from a previous menu setup. I did not delete the widgets and reinstall them. In general, things are smooth now.

FM radio switching is immediate.

Switching to Poweramp immediately starts the music from the radio,

The Spotify switches, but it complains about not being hooked up to the internet (I am running without a phone hooked up) and I push play (far lower right on Spotify screen) to start playing the downloaded Spotify songs. I consider this a Spotify problem.

The Poweramp switches correctly from Spotify and plays immediately, but the artwork does not change until the song selection in Poweramp moves to the next song.
[Android Head-Units] calimero-no1:
Hello, I have the same question. Thanks for answering.

Gesendet von meinem SM-G930F mit Tapatalk
[Android Head-Units] Scopesys:
I conform that this is also happening on my setup.

I am very happy with the current version ...

The only remaining issue I have with the Player, is that when starting with a boot or soft boot, any player using USB goes into a pause mode, because the player has loaded and is ready to play, but the USB drive is still starting up and doing its media check, so one has to wait, and then go into the player, and tell it to run. Touching the FCC run control does not do it, as it is already in the run state, but the player is not.

It's not a really BIG DEAL, but if there was some way around this, so the player automatically started to play correctly, it would be good.

Note: FCC is in PLAY mode, but the player is paused. so they are out of sync.

Maybe a solution would be for FCC to regularly check it's sync, and if FCC's Player control is in Play mode, but the p;layer is not playing, have FCC try to start the player, Eventually, when the USB is ready, this should then work,

or any other solution, so that the Player plays at start up, and is in Sync with FCC.

FCC and the player should not be allowed to get out of sync, but it can happen, so maybe FCC needs to check the sync on a regular basis ??
[Android Head-Units] millab:
Have you tried setting a long delay for resuming playback after restart?
[Android Head-Units] Scopesys:
Yes... I will check again, and make sure it is at max.

If this is going to work, the delay will need to be long enough.

I seem to remember when I set it, I did set it to max but with Larger USB drives, that delay might not be enough.

Currently I am using 64GB Usb drive. If I try a smaller one that will init faster, and that works, then maybe all that is needed will be to have the option for a longer delay for that FCC setting.

Will check it out today, and post findings later today.
[Android Head-Units] millab:
Ok cool.

Another suggestion is to place an empty file named '.nomedia' in the root of your USB drive. It instructs the media scanner to skip this storage from its scan. You need to be sure your chosen player access the files outside the library. I had it work very well on an old Android 6 tablet using media player 'Mortplayer' with a 4TB HDD full of MP3s, tv shows and movies
[Android Head-Units] Smess1210:
Sorry if this is a dumb question, how do I apply my own Google maps api to use minimap for navigation?
[Android Head-Units] Smess1210:
Found it, configured via navi link widget for anyone else looking.....

Sent from my ZX81
[Android Head-Units] Scopesys:
Many thanks .. I will try that, but I do not think that that is the problem.

[MENTION=4292729]SpeedFire-[/MENTION]

It's not the Players scanning the USB drive for media -- rather it's the Android Operating system INSISTING on doing a "CHECK DISK " of the USB drive when it gets mounted on Boot. Even a 16GB USB drive or SDCard takes some time to check, and while the drive is not yet available, the Players starts, and cannot find the drive, because it is not yet ready. (even with the Player being told to start with the Max FCC delay)

You can see the USB check-disk is being run, in the pull down notifications.

In an ideal world, FCC would either delay starting a Player, or check that no drives were in the state of being mounted & checked, before it started a player --- or whatever mechanism would prevent the player from stalling.

Also when this happens, FCC Player CONTROL Widget happily display PAUSE, implying that the player state is PLAY, while in fact the Player is NOT in play mode. ie Out of Sync.

Pressing the control does NOTHING -- one has to go into the Player and tell it to start, before FCC can control it.

It would be really nice if the Play/PAUSE icon in the CONTROL did not even display, or displayed a count, until such time that the Player was ready AND the USB/SD was also ready, and FCC has established correct play/pause sync with the Player.
[Android Head-Units] SKORPiO1975:
Any plans to support CSN2 head units?
[Android Head-Units] bossman4:
Quick question on the difference in volume between media players. The loudness of the music is comparable between the FM radio and Poweramp during switching but Spotify is softer and needs to adjusted manually. Is there a setting to adjust the volume on the different players?
[Android Head-Units] millab:
There isn't that I am aware of, but Spotify has a setting called Normalisation. You can select soft, normal or loud volume levels so this might solve your problem.
[Android Head-Units] stevie_po:
So I was trying to install the latest beta version, but I couldn't get it to install. Thought maybe I needed to uninstall the old version which I did and then tried again. Still wouldn't install. I've tried clearing out the data and the cache of the Google Play store app and rebooting the device but I still can't seem to install FCC launcher from scratch anymore, it just tells me "can't install FCC Car Launcher". Does anyone have any idea why or how to fix?
[Android Head-Units] Xorit:
[MENTION=4292729]SpeedFire-[/MENTION]

https://repo.xposed.info/module/com.thomashofmann.xposed.mediascanneroptimizer

There are apps around to control the android media scanner - maybe possible to use some tweaks from there?
[Android Head-Units] Scopesys:
MANY MANY Thanks !!! That looks like Exactly what I have been looking for.

Going to try it out right now !!!
[Android Head-Units] Xorit:
Dude, you're not rooted!

It's an exposed module there.. not gonna work out of the box :)
[Android Head-Units] sambhasanbiswas:
Speedfire, have you looked into the csn2 headunit radio apk? FCC car launcher cannot recognise the radio app so its like driving without . Even the speed sensitive volume control fails to work.

The good part is auto brightness works like a charm!!

If you need any input, I can help you :)
[Android Head-Units] Scopesys:
OH !!! so "Exposed Modules" can only run on a rooted system.. (did not know that .. so thanks - learn something new every day)

As it turns out, a few changes to FCC's setup and to Blackplayer's setup, and now it is starting up without any manual intervention :)

Takes a bit of a delay, but that's ok .. by the time I get the car started, and get to the bottom of the driveway, it is running before I get out into the traffic on the road.
[Android Head-Units] VBA_Dev:
Hi, there was a question a few days ago asking which setting to choose for a Sofia unit - I asked the same a while ago thinking it was rockchip as rockchip is mentioned in quite a few places in the head units settings, but was told it was not, but I’ve since noticed that selected rockchip allows control of the FM radio and I’m guessing now that having android tablet selected is why the volume speed control is not working?

I’ve tested using the rockchip setting a few times, but it is not stable, and usually goes slow or crashes.

Any further advise please as it’s not obvious which setting a Sofia unit should be set to. Why does it not auto select the appropriate settings automatically?
[Android Head-Units] mihaimilea2005:
Hi,

You can try this app: https://play.google.com/store/apps/details?id=com.spycorp.appvolumecontrol

I have successfully used it with a former unit and I was happy with the results.

It basically allows you to set the volume for each app individually, exactly the way you like.

Hope this helps :)