yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
I've also noticed that resistance of the same button can change and I use +/- 10 range while teaching the buttons in native remapping method (for example I detect that the same button was already assigned and rewrite its value).

However after the teaching is completed MCU takes full control over detecting if the current resistance equals to the recorded one or not (that is why it's called native). So MCU has its own threshold.

The only workaround here would be to record several resistance values. But this method have consequences. MCU has only 24 slots (buttons) to be assigned. If we record 2 resistance values we can record only 12 buttons in total instead of 24. If 3 - only 8.

The good question here is how to choose the alternative resistance values. Should they be higher or lower than the current one, how far?
[Android Head-Units] Ben.suffolk:
I have noticed that the sizing of widgets is not always consistent. In this case I'm thinking of the circle used for the Player and for the Speed Limit.

The Speed Limit one has a larger border around it. See attached screen shots. I would like to use the speed limit on a page as a large display, fitting in where the player goes on other pages. But it's not possible for it to take up the same space in the template.

[IMG="Speed Limit Widget"]https://dl.dropboxusercontent.com/s/irfary6xkeqnfgx/IMG_1345.jpeg[/IMG]

[IMG="Player Widget"]https://dl.dropboxusercontent.com/s/u6pf4d4yi1jmlh1/IMG_1346.jpeg[/IMG]
[Android Head-Units] Scopesys:
+1

Must just be when the Speed Limit is put in the Circular Center.

If it is placed elsewhere, the outer circle seems to fill the allocated space, with very little gap between the outside the circle and the sides.

BTW: How does FCC get its Speed Limit data ??

If I forget to put my Smartphone into Hot Spot mode, I still get some speed limit updates on my HU, but they are not reliable.

Is any data being cached from a previous trip when I did have Hotspot on ?

With no HotSpot, I would have assumed I would get no Street name or Speed Limit data.

Note: When I start from home, the HU gets a wifi connection form the House, but will loose that as I drive away from the house, and thereafter has no Internet connection (unless I turn on Hot Spot). ( No USB cell modem on HU )
[Android Head-Units] crazycarl123:
I see, I really didn't have any idea of how it worked. I have most of my buttons assigned through the included wheelkeystudy app because it works pretty well but if the temperature changes enough I have to assign the buttons again in that app. I was ending up with 2-3 assignments for the same button sometimes.

The main thing I was using your native button remapping for was the mode button (to have custom apps) and another button that I have that I want to launch google assistant as I can't do either in the included app.

I can't really think of a good solution for this although if there was an option to assign 3 values to each button and use up all 24 that would work for me (unless the hardware buttons are included in that because I have 4 of those on the unit as well although I never have any issues with those). So if we could do assigned value, assigned value +10, and assigned value -10 for the 3 values that would work for me as I only have 8 physical buttons.

Another option would be to remove your restriction of +/- 10 for the assignments so I could assign the same button to the same task even if it is only 5 from the previous one I assigned. I don't like this solution as much as the first one because it ends up being the same as the first solution except I have to do the assigning manually.

Possibly the best solution would be to change the range of values the MCU will accept for each button. Is there any way to change this, possibly with an xposed module? (I have Malaysk rom, root, and xposed installer) Or is this something that is done in hardware with no way to change it in software?
[Android Head-Units] SpeedFire-:
Beta 3.127:

- Various bug fixes mostly related to Player Widget
[Android Head-Units] Scopesys:
Learned a lot following this thread :)

The thing that stuck me when I 1st started reading was "WHY is the resistance changing so much -- maybe only in your case" ?

May be a defective Switch Unit, defective resistors in that unit, or bad connections/connectors.

Also, do you have a heated Steering wheel.

A quick Google search of this issue did not show up anything of significance, so maybe it's not a general issue, but instead, just something faulty in your setup ?

My Wheel Unit is a Universal Addon, that is wireless from the switch units, to a small unit by the HU, that plugs into the two R1 R2 inputs on the head unit.

I can imagine if the switches on the wheel are hard wired from the wheel, to the HU, then there must be either some multi-turn twisting of wires, or some sort of slip ring, that could be the cause of changing resistances.

Then again, it could be bad switch contacts.

Do these units have any form of Thermistor Thermal correction for changes in resistance with temperature. ?

Is the CODE that we see when a button is pressed, the measured RESISTANCE value, (or some representative form) . Not find much dealt about all this on the internet.

I can understand that in a good working unit, the resistance may change a little with temperature, but it should not be that high a percentage, that it should cause a problem, unless your unit is defective.

Maybe there could be an auto-recalibration system, that looks at the keys being pressed, and if their values are are drifting too much, does an auto-recalibration in the background... but all this could be unnecessary, if the problem is being caused by a non-typical defective unit.

FYI: I don't think that my unit has had such issues, but there was a time when an extra 11th entry was created for my 10 switch unit, which really messed things up, requiring a reset, and then a re-creation & assignment of the buttons entries. This was during the period that SpeedFire- was working on the Button system, and I assumed it was something that happened with a beta update, or a change in the way a later beta did things.

24 available Entry Slots !!! That potentiality means I could have another 14 buttons added to my existing 10, if they created resistance values that were appropriate !!!

24 short presses, 24 Long presses - that's 48 functions to remember !!!

[MENTION=9525716]crazycarl123[/MENTION] Care to share what car and what wheel button system you have ?
[Android Head-Units] Ben.suffolk:
I think it's just a matter of scale, the bigger you make it, the bigger the margins get.
[Android Head-Units] crazycarl123:
I have a 2014 Hyundai Accent and it does not have a heated steering wheel. It had the base radio in it when I got it with no steering wheel buttons at all. When I bought the android head unit I bought the buttons brand new from a Hyundai parts dealer and I also had to buy a new harness for inside the steering wheel to be able to hook everything up.

I will admit that I didn't exactly know how to hook them up to the android head unit and I couldn't really find clear documentation on it included with the head unit. The head unit has 3 wires for steering wheel controls: a "key 1" wire, "key 2" wire, and "key ground" wire. I could only find 2 wires coming from the steering wheel though and they were "remcon" and "remcon ground". I tried hooking the "remcon" wire coming from the steering wheel up to the "key 1" wire on the head unit and it worked. It also works when I hook the "remcon" wire up to the "key 2" wire but the readings are different. In both cases "remcon ground" from the steering wheel was connected to "key ground" on the head unit. So I basically ended up using "key 1" and leaving "key 2" disconnected because I didn't know what else to do with it.

Is there some other way that the steering wheel keys are supposed to be hooked up to the android head unit that utilizes all 3 wires? This is my first one so I don't really know what I'm doing even though I did do quite a bit of research before and after I purchased it I am very much a newcomer.
[Android Head-Units] An92:
[MENTION=4292729]SpeedFire-[/MENTION]

My problem with microg and minimap
[Android Head-Units] Scopesys:
One of the clearest Pic I found on the Internet

Bottom (Common) Line is GROUND

Middle line in Key 2

Top Line (Connected to resistor chain) is Key 1

Key I is the main one with the buttons giving different resistance values between Key 1 and Ground.

Key 2 has just one switch to ground.

Think of it like a SHIFT key. giving you and extra 10 effective button function.

The wiring of Key1 and Ground between the Steering Wheel Unit and the HU must have good connections, or it will introduce additional resistance.

The lower the resistance switched is by the buttons, the more effect a small additional contact resistance will have on that lower value.

Looks like you have it right.

Do not connect Key 2.

Remcon to to HU Key 1

Remcon Ground to HU Ground

---------- Post added at 07:07 PM ---------- Previous post was at 06:54 PM ----------

Beta 3.127 is giving me major issues. :(

Did notice the Foward & Reverse Player Widget buttons now have a Pressed color again ... :) but

Even after re-booting HU, clearing cache etc, when FCC loads (or is reset by its widget button),

(a) it now takes at least 10 times longer to re-load.

(b) Often it puts up messages about FCC has stopped responding.

(c) Touch screen is dead until well after FCC has finished loading, and finished drawing the Home Screen.

(d) Very often, the Player Widget Controls do not get drawn.

(e) Often, even after re-drawing, the UI is dead.

(f) Occasionally, it does load (slowly) and then runs OK.

@SpeedFire- Please can you post a link for 3.126 because at the moment 3.127 is unusable (for me)

3.126 --> 3.127 One of the few times I did not make copy of previous version before update :crying:
[Android Head-Units] SpeedFire-:
Please try the latest beta 3.129. I hope it will help
[Android Head-Units] Ben.suffolk:
Thanks for fixing the size of margin on the speed limit widget so quickly. I wonder if you could thicken up the red circle border a little when it in a larger size. I think it would make it look a little better if its more in proportion to a speed limit sign. Maybe twice as thick would be about right at that size.

[IMG="Speed Limit Widget"]https://dl.dropboxusercontent.com/s/n4oi2ns2ijwgulp/IMG_1347.jpeg[/IMG]
[Android Head-Units] HgtDave:
Direct Dial issue

Cannot get the direct dial widget to work on my head unit.

I have a car Head Unit, a Dasaita PX5 MTCE running Oreo.

Results of trial

Tried setting the phone call method as FCC or Phone, there is no difference in the results. BT interface is currently V5, tried others but can’t select contact with V4 or lower. The base BT app works perfectly and I have imported all the contacts into "android contacts" store. They are available to all Phone and Contact apps that I have tried on the head unit. The Head unit doesn’t have

•	FCC Contact Icon, click on ‘pick a contact’ select contact from list, fails to attach contact

•	FCC Contact Widget, click on ‘pick a contact’, select contact from list, select phone number and apply, click icon on Home Screen does nothing but flash FCC Launcher or Phone on the notification bar as it’s trying to work

•	Google Contact widget (no Dial widget on HU) , select from list places widget on home page, click on widget opens contact item. I can press the phone button to call the number but this requires two button presses

FCC is set with all permissions, have I missed something on setting up FCC, is there a simply answer or is this a bug. I had similar results on a Samsung S7 mobi, FCC didn’t dial with earlier release but now works.

Is this feature just not working on the PX5 or is it fixable, using a HU with minimum interaction is a must for safety reasons.

Look forward to your reply
[Android Head-Units] Scopesys:
Thanks -- that's fixed it .. Best Beta so far !!!

The Player widget is working a lot better now, particularly when Switching between players.

Currently, I have one Player Widget on bottom left, just showing the current active player... it is a quickplayer widget, just showing the 4th player.

The Players are selected by their own Player Icons along the bottom.

Works great .. with both Known Listed Payers, as well as unknown players.

Whatever player is selected, its name appears as the 4th player in the botton left.

EXCEPT the RADIO.

The Radio acts differently.

(1) It requires to be selected twice.

(2) Then it displays the Radio Artwork, and the Song Title Info, and plays the Radio, but FCC has not updated the 4th Quickplayer to Radio .. it stays on the previous selected player. (see attached Screenshot)

Apart from that, it's working GREAT .... best so far .. Thanks

Its now 100% usable, with just the Radio selection appearing to be a little Buggy, and not displaying as expected.

Note: I switched from having 2 quickplayer widgets, displaying 3 players, and 3 players + 4th because there might have been some strange interaction or non-interaction between the 2 widgets when in a control mode, and in any case, the way I have it now with separate "buttons" for each player, is a lot more flexible & expandable
[Android Head-Units] Joecool92:
Are there any plans to implement dab-z (dab radio app) better? Currently the player widget only show the dab-z cover/station logo. The media buttons and song text stays at infos from player before.
[Android Head-Units] SpeedFire-:
As I don't have dab-z in my Head Unit (and in my country) I really need someone who can record video + LogCat log to show me those bugs.
[Android Head-Units] rigattoni:
I expect still an issue in DAB-Z, because the support of some stations with often changing pictures are not working. The dev is informed and I think he will fix that soon.

Other than that displaying of album art works as expected in FCC.

Displaying song name and artist in first line and station name in second line are working as expected, if you reduce the visibility of these data to only DAB-Z.

If you choose in 'Additional Settings' the 'Limit this widget to only......' to all supported media and radio player.

If you just choose DAB-Z, song name, artist and station name are shown as expected.

If you need logs and video, I could do that (probably) tomorrow.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Spoke too soon ... still the Player Widgets seem to have a random mind of their own .. which is frustrating, as (for me) the major function of the HU is to play Music or Radio.

Unfortunately, I cannot root my unit to provide a log, but I suspect that you will see the same problems as I do, if you set up a Page to select between different players.

Maybe you could set up a simple page like the example above, and see for yourself what happens when players are selected, and how the FCC Widgets respond or don't. Does not matter what players, as long as you have a few, and the HU's FM Radio player as well.

What I expect to happen is for the Widgets to update and display the information of whatever Player is selected and in Play mode, and to show that player's Notification info.. ie Artwork, artist, song etc.

What I experience is that the Widgets Randomly do or do not update various parts of their information, (artwork, album, song and even Player name).

In the above screenshot, the Artwork, song & artist (Radios station / description) have updated, but the Widget is still saying that the player is BlackPlayer Ex.

What happens when Players change can differ each time, so it is difficult to describe what seems to be random updates or lack of updates.

Should be a lot clearer if you can experience it yourself, and see what is happening in the code.

=========================================================

---------- Post added at 08:55 PM ---------- Previous post was at 08:08 PM ----------

[MENTION=4292729]SpeedFire-[/MENTION]

After another hours sitting in the car, I think I have found the pattern !!

(1) After selecting a new player from the FCC menu screen, and entering the player's APP, one has to BACK out back to the FCC Menu screen for things to update.

I had been hitting the HOME button to get back.. and when one returns to the FCC Home page that way, it seems that things are not getting updated correctly.

Would be really nice if it did.

(2)

The RADIO app is still the odd one out.

If one selects radio, and then uses BACK to get back to the menu screen, then all updates correctly like any other player App, except, FCC does not display RADIO as the Player -- instead it just makes the last Player used appear, in the de-selected color.

Agreed, the last player is no longer selected, BUT -- the new RADIO player is, and it should there be shown as the current Selected Player.

ie FCC does not treat RADIO as a selectable Player (when displaying the Player name in the Widget)

Conclusion:

(a) If one BACKS out of a selected player App , back to the main Page, things update ok.

Would be nice if it updated when HOME is pressed

(b) Would be nice if the RADIO was treated correctly as just another Player, and could therefore be the "Selected Player" in the Player Widget.

So, its actually working quite well, if Driven in a specific way .. ie using BACK after selecting a new Player App, rather than HOME.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Rev 3.130

Looks like a winner !!! Thank you so much for all the hard work .. I realize that the player Widget has been a frustration to many .. but it looks like it is now working very well.

My issues were partly MY fault .. I was trying to use Multiple Instances of the QuickPlayer Widget, which in Hindsight, was not the best thing to try, especially as it was probably not designed to support this.

Now have just One Instance of the Quickplayer Widget, supporting 3 main Players, and then a 4th, evoked by a set of Player App buttons ( I know .. probably as you designed it to work in the 1st place).

Anyway, its all working fine now that I am using it correctly .. so BIG THANKS
[Android Head-Units] SpeedFire-:
Thank YOU (as well as other guys) for all your tests and very good bug reports!
[Android Head-Units] SpeedFire-:
What's the problem? Can you describe it? I don't see any issue in this pic.
[Android Head-Units] An92:
The minimap is present on the wallpaper and can not be deactivated (it is not the real minimap but the background of the map), this problem occurs with the last two versions of microg .. If I put one before the last two the problem does not appear
[Android Head-Units] Salvo-x:
I always encounter problems with the Qiuck Player Widget, it does not update based on the Player that is actually started.
[Android Head-Units] Joecool92:
My Fault. I setup the widget for Spotify only. Now i changed to both players and it works. Now there are the logos, station infos. But everytime i switch from spotify to Dab-Z via quick player it opens Dab-Z. Other players doesnt open and work in background. i will make a video and log for this after work.
[Android Head-Units] chandlerp:
I've got the same issue. First time install yesterday on a factory reset head unit

It's as though a quarter of the wallpaper is a map. nothing I do can resolve it.
[Android Head-Units] An92:
Install a Microg version (agosto 18)
[Android Head-Units] chandlerp:
I installed from the Play Store, where do I get a MicroG version from?

Thanks
[Android Head-Units] WarSpaz:
I've got a problem with fcc "crashing" or something every now and then. It usually happens around 5 minutes after wake up/ full boot up. It does'nt always happen but like a third of the times i use the car. Did'nt happen a couple of months ago though. The screen turns solid Grey for about 20 seconds and then the launcher comes on again. Radio keeps playing and i can use my hardware buttons to go to settings etc..

Also did full reinstall of the launcher but didnt fix it.

Got px5 device with paid version of the launcher

Skickat från min ONEPLUS A6003 via Tapatalk
[Android Head-Units] An92:
Microg on PlayStore? I don't know

Microg download from site or f-droid app
[Android Head-Units] TT_Vert:
[MENTION=4292729]SpeedFire-[/MENTION] Bringing this back up to see if I can do this or not.

Dave
[Android Head-Units] aalmans:
Awesome! This works,thanks!
[Android Head-Units] ab1702:
Just installed this launcher today and got the paid version.

I have no idea how to customise a lot of it so I’m going to have to spend quite some time learning it but I do have a question and have noticed a couple of bugs.

1. I have a px5 unit and it has a home button in the top left corner which I use quite often. Since installing this launcher I can press that home button but it doesn’t do anything. Can I get this working again?

2. The bugs - As my music players I selected, dab, a2dp and fm radio. When I swap from dab to say a2dp it will show what I am playing on a2dp but it will also still show the dab radio station logo. Also after I have done this I lose all sound from the dab app if I go back to it so I have to shut everything down and use something else first and then go back to dab before I can get the sound back on again.

I see this launcher has a lot of features probably more than what I will use but one of the reasons I wanted it for were so I could use everything from one home screen which is mainly dab and a2dp.
[Android Head-Units] SpeedFire-:
THANK YOU!

This bug (which is still probably on MicroG side) helped to find a very important issue in the FCC Launcher.

Previously when you scrolled to the home screen without MiniMap, MiniMap view became invisible. I thought that everything related to MiniMap (updates, data consumption) should stop automatically. But it turns out that this didn't happen and MiniMap continued to consume resources.

Now I entirely deactivate the MiniMap and all of its activities when it is not visible.

For example CPU consumption on emulator now looks like this:

Before this fix, everything looked like the left part of this chart.

Beta 3.131 is uploaded:

- MiniMap is fully deactivated when not visible (this will increase CPU performance and save mobile data)
[Android Head-Units] Scopesys:
Interesting -- well found & Fixed !!!

Raises the question -- does a Widget placed on another screen (ie not the current one being viewed) consume resources and interact with it's app.

For Example, consider a widget that sequentially read a directory of image file every 5 seconds, and displayed them

If That Widget was put on two different screens, ie page 1 and page 2, and you are viewing page 1 .. would the widget on page 2 run and consume resources reading the files.

Also, I am wondering what happens if multiple screens have the same or similar Player Widget... do they interact. ?

I have found, that even on the same page, having multiple Player Widgets can cause issues if configured in different ways..

ie

(a) Center Player Widget displaying Artwork and Control.

(b) Lower Text Player Widget, showing Quick Player names.

(c) Upper-Left Text Player Widget, displaying Artist

(d) Upper-Right Text Player Widget, displaying Song.

I find if I set the same Quick Players in all Widgets, but choose to only display the player names on the Lower Quick Player Name Widget, it is a lot more stable, and if I define the other Player Widgets to have "Blank" Quick Players (or something else), even though they are set to only display in the lower "Quickplayer text listing widget"

With my Home screen set up as above, this is the 1st time when switching between players, that I have got the correct artwork & text updates to work reliably. Also likely to be dues to all the recent Bug Fixes in the Player Widget... thanks again SpeedFire-