yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
We don't have DAB yet but we have RDS on a standard FM Radio. I haven't seen that the stations change or even transmit logos.

As we have a cheap Internet with a good 4G+ coverage almost everywhere I prefer to use streaming services like Google Music or Spotify.
[Android Head-Units] Scopesys:
I also have not seen the FM stations transmit any logos, just text.

Some HD radio stations transmit artwork, as well as text.

And of course, Internet streaming radio stations seem to send whatever they feel like sending... at least it seems that way when selecting them.. not aware of any Standards.
[Android Head-Units] rigattoni:
Yes it´s for US HD radio stations the exact same behavior and of course for SIRIUS radio too...surely known that this is satellite radio and afaik only available for OEM.

[MENTION=4292729]SpeedFire-[/MENTION]

If you need some traces to analyze the behavior... I would be able to provide video and traces....

I think there are a lot of user in about 35 countries incl. China, Australia, nearly complete Europe....

Edit: May be you can get in contact with the dev of DAB-z... He is a nice guy presenting his app at XDA too.
[Android Head-Units] Scopesys:
FYI: You can also get Sirius-XM via Streaming, (Paid service) but the Sirius-XM Android App is terrible for a HU .. it is Locked in Portrait, and the channel Graphics do not display correctly (at least not on my HU). The Iphone version is a little better.

Sirius came free for 3 months with a recent car purchase, after which it is quite costly. Even if it Free, I would not listen to it .. much prefer my 128GB SD card with music I like on it.
[Android Head-Units] TT_Vert:
[MENTION=4292729]SpeedFire-[/MENTION] have you had any chance to look at this? If not no big deal but for others w/ buttons it will be eventually.

Dave
[Android Head-Units] SpeedFire-:
I need a log for this.
[Android Head-Units] TT_Vert:
I already attached them. post 2246
[Android Head-Units] SpeedFire-:
Can you record another one on the latest FCC versions since I have made some changes to the wheel button interception.
[Android Head-Units] TT_Vert:
Yep will do now. Later than .117?
[Android Head-Units] jun81:
Encountering service permission every restart of device here. Anyone manage to overcome this?

Thank you in advance!
[Android Head-Units] TT_Vert:
I'm going to have to get you more info in the morning but it is sort of working. I am getting "please enable accessibility services to enable the back button" but I am not even mapping the back button, I'm mapping the navi button. But it is seeing key presses w/ the newest version so that is progress. Any idea what that accessibility warning is for?

Dave
[Android Head-Units] rigattoni:
You can use Tasker with the the plugin "Secure Settings" to activate the permission on each reboot.
[Android Head-Units] jun81:
Thank you for the inputs!
[Android Head-Units] EnumC:
Attempt to invoke interface method NullPointerException

UPDATE:

After some digging, I encountered this thread: https://groups.google.com/forum/#!topic/android-building/6Aqo2JpSRio.

By creating a new file with the following content:

<permissions>
<feature name="android.software.app_widgets" />
</permissions>

to

/system/etc/permissions/android.software.app_widgets.xml

, I was able to fix the NullPointerException!!!

Leaving this here for anyone else who encounters this issue.

Attempt to invoke interface method 'void com.android.internal.appwidget.IAppWidgetService.deleteHost(java.lang.String, int)' on a null object reference

[MENTION=4292729]SpeedFire-[/MENTION]

Thank you so much for making this app for the rest of us! Unfortunately for me, the app immediately crashes upon load. Upon checking logcat, it seems that the issue is due to a NullPointerException (See line #7051 and below + 7167).

If you can take a look at this and see if this bug could be squashed; that would be fantastic. I suspect a couple other users who previously posted also have the same issue, but was unable to provide the logcat due to the lack of root method. I was able to acquire root via boot.img and therefore was able to capture the log.

The device is running Android 5.1 with no gsf or gms installed.

* Some part of the log was trimmed in order to fit it into the 512kb file size limit.
[Android Head-Units] SpeedFire-:
Just to clarify. Did FCC Launcher work previously on your device or is this a first time install?
[Android Head-Units] EnumC:
First time install. I was never able to start it without crashing until creating that XML file. Now the app opens, but the widgets are still a bit wonky. Maps doesn't show up, and some of the widgets also seem to be displaying incorrectly.
[Android Head-Units] Scopesys:
Thanks :)

Exactly what I have been wanting to do, both for FCC as well as a few other programs I have on my HU, that need Accessibility permissions.
[Android Head-Units] SpeedFire-:
Your Log says that you have a pretty limited firmware with no Google Services included (which are required for MiniMap and some other parts) as well as no Google Play.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Talking about MiniMap and associated FCC GPS type Widgets

Am I correct in assuming that some of their functionality require an Internet Connection to function correctly ?

ie: Speed Limit and Street Name

Can you please briefly explain how those two function operate, in terms of update rate.

(1) I find that the Speed Limit sometimes goes Blank or to an incorrect speed, when traveling down a major road (with side streets) that has a constant speed limit.

(2) The Street name also changes when travelling down a major road with side streets, randomly displaying the side street name when passing, and then taking some time (15-30 seconds) before it changes back to the correct road again.

This also happens when the Cell Reception is strong, so I do not think I am getting temporarily disconnected form the Internet.

The display of Side streets is actually a nice feature, if it were more consistent.

Ideally the display would display the Main Road one is on, and then in a 2nd line of text, the next

nearest

road, if within say 100 meters.

It would also be nice if the Main Street name kept displaying as the main Street, until such time that it was sure that the car was actually traveling down a different road.

Not knowing exactly how FCC is doing the Road or Speed limit, I assume it must be polling Google with current GPS position data, to get both the road & speed limit.

If it cannot get the required data, it might be appropriate for FCC to display that the data is "old", by a color change.

This would be especially useful if Sound was ever re-added to the Over Speed limit conditions, with an option to turn sound off if data is not validated (ie OLD).

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

Current "Driving" screen

What screen might look like with additional "side street" display, and indication that Google data was not updating.

-----------

FYI: Why is screen data so BIG ?

Reason:

My HU is fitted in an older car that use ti have a Radio mounted low in the center console.

It is not easy to look down at it for any length of time while driving, so my screen design is to make things BIG and Clear, with minimum Touch screen use .. making most needed function controlled from one of the 10 steering wheel controls.

That, and with Google Voice, I very seldom have to reach down and use the touch screen.

The Wheel Control features included with FCC have been a great help in achieving this -- so thanks again...
[Android Head-Units] TT_Vert:
[MENTION=4292729]SpeedFire-[/MENTION] A little update on button presses

It seems to mostly work. Few issues which I see someone mentioning tasker has to resolve? If true, can that be resolved w/o tasker?

1. I have a button mapped for muting however it rarely works when pressed. The double click function of that same button works every time (see mute.log)

2. Using the Navi button (NOT BACK BUTTON) I get "please enable accessibility service for FCC launcher to emulate back button" (See log navipress.log)

3. Adjusting volume stops song title widget scrolling and then it restarts at beginning of song name when done adjusting volume

4. Is there a way to define items to assign to the remapping of keys? I'd like to set up double press on volume knob to open recent apps.

Thanks

Dave
[Android Head-Units] Scopesys:
I have found that with Volume UP / Down (with or without FCC), that those functions only respond to a single press, because as soon as you press the button in, it starts to auto-repeat on the volume control movement.

So a double press just is a manual auto repeat !!!

IF there was a way to add dual functionality to the Volume Buttons, that would be GREAT .. ( can never have too many Buttons Functions !!! -- provided you can remember what they all do )

Maybe I am missing something, as my Buttons seem to work in a world of Short Press and Long Press, not single click & double click. So maybe there are effectively 3 options ?

(1) Single Click

(2) LONG Click

(3) Double Click

That would open up another 10 functions for me !!!!
[Android Head-Units] SpeedFire-:
Beta 3.122 is uploaded:

- Back button asking for Accessibility fix (if it is not selected to cancel default intercepted action)

- Volume fix - manual volume adjustment will start from the last FCC Launcher's value

- Players are in ascending order now
[Android Head-Units] TT_Vert:
This is for volume button press not rotate to set volume up or down. It's a physical rotary button/knob
[Android Head-Units] TT_Vert:
A little update for you on 3.122

Accessibility issue still persists w/ 3.122

#1 I stand corrected on #1. It does work, it just does not say MUTE on screen like the original mute button does. Is there a way to retain that toast of "mute" when it is pressed?

#2 Accessibility issue still persists w/ 3.122 but I am using the old way to map buttons. Does not matter if the "cancel built-in button's action" is checked or not.

#3 still persists but it's really not a big deal at all to be honest, just wanted you to know it was happening.

#4 would be helpful for other resources as I'd like to assign a long press to rebooting. I can define long press to any key in factory settings and then I can come into FCC and remap independent of single and double press.
[Android Head-Units] Yak54:
Thanks for the quick adjustment of the Player Widget. Messages from DAB+Z are now displayed correctly on my head unit.
[Android Head-Units] rigattoni:
Yes same for me. The size is fine now, but still the issue with not updating the provided slide show from the radio station, as long as there is no change in artist name/song name.
[Android Head-Units] rigattoni:
Just another question:

Why are the widgets for speed and altitude different in UI?

I set the same size in both widgets for primary and secondary text but it shows completely different on the screen. At altitude the secondary text is cut off on the bottom.

I won´t use the combined widget, because I don´t need any icons in it, I just want to show the unit.
[Android Head-Units] rigattoni:
Up-Down buttons implemented... :good:

...but I found an issue in using the arrow buttons:

If you change the icon size by those new arrow keys and press OK, the icon is in a wrong size. Edit the app again and you see, that the size shows "0". The only chance to get it in the needed size you still have to use the slider instead of the arrows.
[Android Head-Units] kokillo:
Stock Radio App

Hello. Probably my question has already been answered and I tried using the search in this thread without results. i'm probably gonna get my head bash for asking this but.... all the launcher that i have tried cant access the factory radio app(no icon, no app). the only one that does it is the one that came with my HU. my device does not show MCU version and it looks like a stripped down android system. so i can't get much information about it, can't get root either :( basically can't do a lot. its a Ezonetronics RM-CT0009 with Android 6.0. can there be a way to make radio app function on this launcher or in any other? I can use any other apps but without FM radio it just wont cut it. can't listen to spotify all the time :)
[Android Head-Units] SpeedFire-:
Bug confirmed and seems to be fixed now.

Beta 3.123:

- Since Google cancelled free routing feature, routing on MiniMap is not available now. However, if you have your own developers key you can now use it (go to NaviLink settings to enter it).
[Android Head-Units] TT_Vert:
Accessibility bug fixed w/ latest, nice job!!!

Any way I can define a process for an intercepted key? If not I'll make an apk to call adb shell input keyevent KEYCODE_APP_SWITCH and then have the button run that apk but i was hoping for an easier way to be able to define commands to run when a button is pressed. I've got this thing about perfect, now get that damned backup/restore functionality to work so I don't lose it all LOL

Dave
[Android Head-Units] Scopesys:
This seems to have successfully fixed the issue when rapid song changes can cause the Widget to stop working. Thank you :)

I am still getting the notifications stop working, especially after coming out of sleep, and most times, a re-boot does to correct it.

It often requires a series of re-boots, Killing all running apps, and re-starting FCC, to restore reliable Notification (& corresponding widget updates).

Often, after such rest attempts, the 1st song that plays will display OK, and so will the next one , but after that, the updates stop (ie stuck on 2nd song info).

Note: When Widget starts failing to update, so does FCC pop up Notification of song change.

Seems to be directly linked.. every time..

Hit & Miss as to if re-boot / restarting FCC / killing apps with start reliable operation of the widget.

The net result is, EVERY time I start the car, and the HU comes out of sleep, I spend 5-10 minutes, messing with FCC, re-booting, re-starting etc, if I want the Player Widget to update correctly during my trip.

[MENTION=4292729]SpeedFire-[/MENTION]

Found this reference to "Notification listening service stopping"

The only "solution" I've found was to have the notification listener running in a separate process. Then if the rest of the app crashes it doesn't stop the listener. So it's only then specifically notification listener service crashes that require the reboot

It's Getting very old and frustrating, so I hope you can figure out what is going on and fix it soon.

I see there is a FCC Starter APP, on Playstore, that is connected with starting FCC when coming out of sleep. Is this still something that could benefit current version of FCC ???
[Android Head-Units] timduru:
Good to see a nice and very configurable car launcher,

keep up the excellent work [MENTION=4292729]SpeedFire-[/MENTION]

Looks like it's gonna be my daily launcher for now. :)

I've noticed a few minor bugs (tested on stable and beta version V3.123):

I can't delete a workspace as the delete icon is not displayed

I have vertical PX3 Android 4.4 and 7.1 units.

From what I see , I think it might be because the delete_workspace_container layout is missing in launcher.xml for the layout-port & layout-port-v17 res

I have a similar issue to delete a widget. The widget delete and settings icons don't show up when I long press on a widget.

It might not be only related to portrait orientation for that one though,

as I have the issue also on a PixelC in landscape mode.

what is weird is that I've seen the widget delete and settings icon displayed at the top of the screen when long pressing on a widget once,

but I don't see them anymore now.

screen info:

WINDOW MANAGER DISPLAY CONTENTS (dumpsys window displays)

Display: mDisplayId=0

init=768x1024 160dpi cur=768x1024 app=768x890 rng=768x614-1024x736

deferred=false layoutNeeded=true

Also The unit is a PX3 RK3188 unit, so I've selected the Rockchip MTCD /MTCE /PX3 /PX5 model during the setup.

but things like brightness / volume and such don't seem to work.

If you need I can provide any info for that model like if you need a list of /sysfs nodes or apk extractions and such,

don't hesitate to let me know.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Ref: Player Widget -- Locking up and not updating artwork / text

Looks like my issues may have been caused by using BlackPlayer / BlackPlayer Ex.

About 4 weeks ago, I was having issues with Poweramp (Player Widget update ?), and I switched to BlackPlayer.

Then recently you did some fixes to the Player Widget, which improved things.

In hindsight, the FM Radio app then worked well, but BlackPlayer would still hang in the Player Widget.

I just switched back to PoweAmp, and now find that the Player Widget is reliably updating now in both the FM radio AND "Poweramp" (as well as Pandora, Google and Amazon).

So it looks like the issues were being cause by BlackPlayer - which might also explain why the issues could only be corrected by removing BlackPlayer from memory with APPKiller.

Also, another symptom was that if I have BOTH PowerAmp & Blackplayer set as Quickplayers, and the Player Widget is displaying BlackPlayer, and starts to stop updating, then switching to PowerAmp restores Player Widget updates, and then even switch back to BlackPlayer, the Player WIdget starts to run correctly for BlackPlayer again.

Bottom line, now looks to me as a "BlackPlayer Compatibility with FCC" issue, and having switched back to PowerAmp, the Player Widget (and FCC Popup Notifications), now seem to run a lot more reliably (so far !!)
[Android Head-Units] Ben.suffolk:
Today I updated to the latest Beta in play store, and the latest DAB-Z version. The combination of the 2 new versions fixes the issue where the DAB information (Station name and whats playing) kept going blank.

I'm not sure if that was due to the FCC update or the DAB-Z one, but I'm very pleased to say its now working.

Ben
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Please could we have some Masks for the Rectangular Player Widget so that items like the CONTROLS show up on light artwork.

Note: None of the circular mask affect the Rectangular Player Widget .. which makes sense.

However, any Rectangular Masks "should" also be made to work with the Circular Widgets, for when the Artwork is not set to be circular.

Example (Not a great example of a white background Artwork, but shows the intended effect)

Current Rectangular Player widget with Light Artwork

Current Rectangular Player widget with Light Artwork and a Rectangular Mask so that controls always are visible
[Android Head-Units] Salvo-x:
encountered problems with the player widget,

the icons do not synchronize with the player running

Rds text and radio station name are not displayed

MP3 text artist and album are not displayed
[Android Head-Units] hapaman:
Great launcher, so I went strait premium. I like the minimap, but offline maps are not working. Can this be added?
[Android Head-Units] rigattoni:
Google does not allow to use offline maps in their API.
[Android Head-Units] SpeedFire-:
Please upload your masks in 400x400px PNG format.
[Android Head-Units] Scopesys:
I can do that, once I figure out how to make a correct Png file with the correct Apha Channel. !!

(I tried a few days ago, did not get too far, so the examples I did above where hacked with Photoshop).

Please confirm you want 400 x 400. ? The current circular ones in the APK (res\drawable-nodpi-v4) are all 398 x 398.

Can I assume you plan to add any new Rectangular new mask files to the APK, rather than allow users to put their own make files in a given FCC data directory ?
[Android Head-Units] SpeedFire-:
1) Yes, 400x400 will be good. They will be scaled anyway.

2) Yes, I think this way is better.
[Android Head-Units] Scopesys:
OK, I'm make one for you to try, and if that works, I'll make a set to cater for the various Control/Text options for Rectangular Artworks.

Here is a mask for just the Controls, and a Photoshop edited image of what it should look like when applied to the artwork.
[Android Head-Units] Thormb:
Hi, i would Love to Test this Launcher, but unfortunatly it always crashes when i try to Start it on my Huawei P20 Pro. As i Like my head unit as Clean as i can (pumpkin Android 8.0 octa core) i always Test launchers in my Phone before installing it on my head unit.

Configurating it was no problem, (checked "Android Phone or tablet") but after that it Just crashes everytime i trY to start ist. First the Screen is all Grey and then i get kicked to my normal homescreen.

I Hope You can Help as i would Love to Test this.
[Android Head-Units] SpeedFire-:
Do you have a root? Can you record a LogCat log (see the first post in this thread)?

Please also try to select a skin without MiniMap just for a test.
[Android Head-Units] SpeedFire-:
OK, added:

3.124 beta:

- Square masks for PlayerWidget's album arts

- PlayerWidget buttons animation is done differently to eliminate widget's freezings
[Android Head-Units] Scopesys:
That was FAST !!! Thanks ... late night or more precisely, early morning for you.

Thanks for that... I will check it out as soon as it becomes available in Play Store.

(so maybe late night for me as well :)
[Android Head-Units] Thormb:
Sadly no root here. As Huawei stopped giving Keys.

So no possibility for a log.

But i thought You get the crash Info over Google. I guess there wont be much P20 Pro s with crashes.

Tried every theme while configurating.

By the way, P20 Pro could appear as CLT-29
[Android Head-Units] Asterion:
Hello there,

I'm using FCC Car launcher for a couple of day and must say that i'm supprised how good the launcher works.

Altough I have some little problems.

i'm using the widget to control my music and switching between different players.

It works really great but the radio app opens when I switch the player..

Switching between the standard player en spotify works great, only switching to radio opens up the app.

Is there a work around for this problem?
[Android Head-Units] crazycarl123:
Steering Wheel Controls

[MENTION=1633144]speedfire[/MENTION]

I first wanted to thank you for making this launcher. I haven't been using it for very long but I really like the customization. The previous issue that I was having with the speed dependent volume is now fixed in the latest release. I don't know if that was something you were already working on or not but I appreciate the quick fix.

I am now having a new issue that I am hoping you can help with. My steering wheel controls are resistor based and their value can change by several ohms with changes in temperature, especially when it is very cold outside and I run the heat in the car. When I try to use the native remapping of the steering wheel controls it works a few times but then stops working. I have noticed that the value on the buttons can change by +/- 1 ohm without any temperature changes at all.

I was wondering if you could add a range of values for the keycode of each button to fix this issue. I checked the resistance of all my buttons and the closest ones are about 50 ohms apart so a +/- 10 ohm range form the assigned keycode should work well for me. This could be an option with a check box so that others who are not having this issue don't have to use it. Please let me know your thoughts on this.

One extra button assignment would be nice as well since I have 8 physical steering wheel buttons but this is not nearly as important.
[Android Head-Units] Hazard15301:
Requesting that the SiriusXM app be added to the list of officially supported players. Thanks!