yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Contra01:
I don't have that option

View attachment 4613595
[Android Head-Units] Contra01:
Oh I found it I had to change a couple of settings let me try

---------- Post added at 05:44 PM ---------- Previous post was at 05:24 PM ----------

well I tried every combination and in each I tried calling out with the FCC launcher and the default phone app and neither one will work

---------- Post added at 06:00 PM ---------- Previous post was at 05:44 PM ----------

what I am trying to accomplish is to make a widget where I can simply just push the picture of the person I want to speak to and speed dial calls them directly as opposed to trying to put in their number or look them up in the contact list each time I want to call them. I created a widget successfully due to adding Google contacts but it does nothing when I push it
[Android Head-Units] TT_Vert:
I don't believe anything but you tube works for me. I'll try a few of those and see if they work, at least that'll show me where the problem lies. You had mentioned that Flyaudio devices were for the most part the majority, I wonder if the fact it's a Joying MTCB has something to do w/ this? I wouldn't think so as it's communicating w/ the MCU just fine but who knows.

Dave
[Android Head-Units] TT_Vert:
Ok this appears to be a problem w/ both jet audio and pandora. Works fine w/ google music. So in summary, song title/artist display rine, just no album art in Jet audio/Pandora.

Is there any chance you'd be willing to work w/ me to resolve these? Both Pandora and Jet audio are very large media players and would really be a plus if this worked properly. I am also a BETA tester and have provided tons of logging data early in your development days so I'm willing to work with you on this.

**UPDATE**

I changed versions of pandora and that resolved pandora. Let me see if I can find a different jet audio version, not sure why this would be occuring based on versions but maybe these are very old versions I had.

Dave
[Android Head-Units] TT_Vert:
Just ran into another few bugs it appears w/ the volume widget.

If I get volume to 0 I cannot use the volume up on widget to increase volume to 1. I must use knob then volume up will work again until I go to volume 0. Included a log of using the widget to go to 0 then attempting to press volume up on widget. Then manually went to volume up w/ knob and then back to widget to show what is going on.

When backing up I notice two files are 0 kb and when I do a restore to another device it doesn't change anything. Related? I see files in FCCLauncherBackup are created and have data in them but still doesn't change the fact I'm unable to restore. I'll have to log other device as well but I figured those two JSON files in root of google drive should not be empty. I notice backing up from my newer device to google cloud does create those files and puts then in the FCCLauncherBackup folder and they have data. Both devices are running newest BETA 3.111. One is an MTCB device (Not backing up properly) and one is an Essentials PH1 android phone running android 8.1.

Dave
[Android Head-Units] Scopesys:
Ref: Street name & Speed Limit.

Is there anything that can be done to improve both these items.

(1) Street names,

Driving down a major road, the street names keeps changing for a few seconds (Randomly) when passing side streets.

Not every side street, but randomly about 50% of them.

Ideally, it should be Display All, or display none (ie Some form of Sensitivity or filtering)

Might even consider 2 lines .. Top with the Current Road Name, and the lower to indicated passing street names ( say withing a few 100ft of car) ? Even two colors for the passing, one for within a few 100ft, and another when within 100 feet.

(2) Speed Limit.

Speed limit is still very unreliable. It typically goes to Blank for extended periods on a road with a steady speed limit for many miles.

I recall there was some talk to adding an Over speed Audio warning, but this was held off until the speed limit detection was fixed to work more reliably.
[Android Head-Units] Scopesys:
A neat work around for the low volume of Google Assistant:-

Mainly for use with an Android head unit in a Car.

Problem:

Google Assistant has a low audio level, so when listening to music at a good listening level, when Google Assistant is called, even if set to complete mute the Music, it is a very low level audio. While there are some good attempts to get around this, until Google Assistant adds its own in App volume control, using Assistant is an issue.

SOLUTION:

ANDROID AUTO !!

Although AA is typically run on your SmartPhone, and used to connect to an Android Auto enabled Head Unit, AA Can be run directly on your Head Unit as an APP.

This has several neat advantages.:-

(1) A simple interface, ideal for when driving, giving the basics, Music, Phone and Navigation.

(2) And this is the GREAT ADVANTAGE -- the Google Assistant's built into Android Auto has a significantly louder volume than the stand alone Assistant APP, and has good control over muting other audio sources when required.

In practice, if you put an AA icon/widget on your FCC menu, you just press it to start AA.

If you currently playing Music with an app (say BlackPlayer) that is one that is compatible with AA, it keeps playing and can be controlled now from the AA Music playing screen.

Now when you press the Mic Button that is always present on AA, you get to talk to Google, and Google replied in a good loud volume that matches your current Music volume. (without cutting off the end of short Google replies !!) and no need to mess with volume control to hear Google.

At any time you can press the HOME button on you HU (or steering wheel), and return to your FCC menu -- but AA is still running in the background, (Unless you specifically close it when in AA).

So next time you press the AA icon on your FCC menu, AA runs instantly, where you left it

There are numerous other advantages of being in the AA screen, but at any time you came leave it and go back to your FCC menu.

Not only does Blackplayer's setting become a lot more simple to use in AA while driving, but also Assistant works better, and even the Google Map seems to work slightly differently and seems to be more Car-Driving friendly.

Defiantly worth trying out, to see how you like it, and is yet another option when operating under FCC.

Note: Not yet tried making Phone call using AA on the HU. (may not work if it needs to use Phone to make the call ... may work somehow.. ? Should work if your HU has it's own USB Cellular Modem... but I suspect most do not have that, and rely on their phones.)

If nothing else, the GOOGLE VOICE (Google Assistant) within AA replies at a decent volume.
[Android Head-Units] Xorit:
[MENTION=4292729]SpeedFire-[/MENTION]

Remember the button mapping not functioning for some ppl?

-> mtce-utils xposed can map 98% of my buttons (google 4pda :) )

-> from the logs it listens to com.microntek.canbus

-> my back and menu buttons are mapped via keyboard layout from android directly though - had to use ButtonMapper Back button is android input code 4 and menu sits at 82.

[terminal - input keyevent #]

Managed to remap everything I need to.

Maybe you wanna look into that, if it's possible for you to use similar method.
[Android Head-Units] jun81:
[MENTION=4292729]SpeedFire-[/MENTION],

Latest beta KLD PX5 Oreo

there are still some issues with the player widget

1. on boot poweramp start playing randomly, when that happens player widget unable to control player to stop/play.

2. fm radio still randomly switches back to poweramp.

3. minimap street name only update once when fcc starts.

Have attached the cat log. hope it helps!

to the rest please help SpeedFire- by getting logs of your specific issues, that will help him to pinpoint where it may go wrong.

Thank you
[Android Head-Units] jun81:
sorry double post
[Android Head-Units] sbruda:
Almost there... :) The manual reset works fine, but when the widgets reset by themselves they do so partially. In this circumstance the distance resets but the rest of the data is kind of messed up. Am I doing anything wrong, or is this a bug?
[Android Head-Units] Scopesys:
Latest beta Eonon GA2170B PX5 Oreo

I also get the Poweramp issues as above, when re-booting, or coming out of Sleep mode, when the car is started, and the HU resumes without a full re-start.

Also get the Radio issue all the time when selecting radio at any time.

However MiniMap street names seems to be working fine (provided I have my Phone set as a Hot Spot). Otherwise, the HU will pick up the WiFi from the house and update the Road, but as soon as I drive away from the house, and get out of range, it stops updating. Maybe this is what is happening to jun81 ?

Actually, I have the OPPOSITE problem with the MiniMap Street Names.

It updates to often, each time I go past a side street, while on a main road, it will randomly some of the time, show the side street for from 1 - 10 seconds.

Especially happens when driving over or under road bridges ...

Maybe the Street name functionality needs some AI, or filtering, so it does not update, unless it is sure it is on a new road.

(Same goes for the Speed Limit)

Speed limit will randomly go to "Blank" while still in a speed limit region, and may take up to 1/2 mile driving before it goes back to displaying the original speed limit.

In fact, I got so frustrated with PowerAmp wanting to start by itself on startup or randomly when another quick player was selected - even if PoweAmp was not the selected "quick player",_ that even though I had the Pro version, I uninstalled it and went to BlackPlayer (which does not suffer from this issue)
[Android Head-Units] aalmans:
Hi,

I am having an issue with the speed dependent volume. I have configured the volume to be 10 at boot and to increase by 1 at 40,60,80 kmh. This is working just fine. The volume increases and decreases with the speed as designed.

However, let's say i am driving at 90 kmh with the volume then being at 13. Whenever i then hit the volume up button on my steering wheel it goes to 11. So it looks like it does not take into account the volume increase it had in the meantime because of the speed increase. It should have gone up from 13 to 14.

Or am i missing something?
[Android Head-Units] Ben.suffolk:
I have noticed both these things happening more recently, I also have a main road I drive down and there is a cycle track running parallel, sometimes I thinks I’m driving on that, so maybe it should also filter to assume your on a road.
[Android Head-Units] Scopesys:
I think you need to look at it as there being a BASE volume that YOU set, and then FCC adds to that volume with speed, but without changing that base volume that you set.

In your case that was 10.

You drive at speed and FCC adds say 3 to that effective volume, so your volume level is now 13, but FCC knows that you really set it to 10.

You touch the volume control and FCC shows the level you set it to (the zero speed Volume), and you then turn that 10 up to 11.

But if you are moving at the same speed, FCC really sets the volume to now be 11 + 3.

So YOU adjust the BASE volume, and FCC adds to it (if you like, in the background).

This is how I am assuming it works, which would make sense. ???
[Android Head-Units] aalmans:
If this is by design then it works but to me it does not make sense.

If my base was at 10 and with speed it has increased to 13, touching the volume up button then turns it back to 11. So when i was expecting 13+1 it is now set at 10+1. This does not make sense.

It would be better if FCC would increase or decrease based on the current volume level. That would make more sense to me!
[Android Head-Units] Scopesys:
OK .. I have NO IDEA for sure EXACTLY how it works, but it does work, and it works really well.

So who cares what the # is ?

If it's too soft, then turn it up

If it's too Loud, then turn it down

There is probably more variations in volume between say Radio, Poweramp or Pandora, so chances are you need to alter the volume when you change player.

Even more difference in volume between different mp3 recordings .. so what does it really matter what the absolute Number is . . . . it's going to be all over the place, according to what player you are using, what the music is, and how much you want to talk to your passenger !!

Personally, I never even look at the number that the volume display is showing when I change the volume - far safer to be watching the road than a volume Number !!! -- I just press my Wheel Button to adjust the volume to what I want .. not to a given number.
[Android Head-Units] Scopesys:
Gone quiet in here...

For some inspiration, here is a short video, showing the ability to scroll both "Album Name" & "Artist" on the same Page.

Zip of a .mp4 video file
[Android Head-Units] bsavoir22:
I have been having problems lately.

1. Music player plays and pauses about 3 or 4 times on its own.

Album art doesn't refresh for poweramp or stock music player (not sure if it was able to before as I always used poweramp).
[Android Head-Units] Scopesys:
I still get intermittent times when the Artwork stops updating.

Only cure I have found that works is to close all apps, clear cache & then restart FCC.

95% of time that fixes it, if not need to do it again till it does.

Typically, if it is running, provided I do not change players, it keeps running ok, even after being awoken from sleep.

Note: Artwork within the player itself updates correctly 100% of the time .. just not in the FCC Player widget.
[Android Head-Units] bsavoir22:
FCC launcher supports Rockchip units and fly Audio. I ask a while back if he had plans to, he said he would look into it. But i had issues with the Allwinner unit that i didn't like (sound and OBDII Bluetooth reader) to work and not much support for the unit either, so i sent it back to amazon and got a Rockchip PX5 unit and glad i did.

---------- Post added at 08:52 PM ---------- Previous post was at 08:27 PM ----------

here is a a video of my issue, i think it explains it better. I reset the system 2 times already and have narrowed it down to FCC launcher. I will deal witht the issue because there is no better launcher than this, it a minor annoyance that is all. https://www.youtube.com/watch?v=nz_OTWKfbn8
[Android Head-Units] rigattoni:
Good choice... :)

But... you should choose any other player than Poweramp and you are happy.
[Android Head-Units] Scopesys:
I dropped Poweramp and switched to BlackPlayer ........ so far, so good

https://play.google.com/store/apps/details?id=com.kodarkooperativet.blackplayerfree&hl=en_US
[Android Head-Units] TT_Vert:
[MENTION=4292729]SpeedFire-[/MENTION] I'm starting to wonder if there is some integration issue w/ FCC and the new PX5 MCUs. Joying has two (FYT and QD). I just purchased a new android 8.0 unit for some testing and with the QD firmware not only does the auto dimming not work nor do any other things that interface w/ the MCU (Sounds, brightness, etc.) Brightness widget also does nothing.

I also find that I have the issue w/ calls saying Bluetooth is not connected, try to change BT interface version. And like [MENTION=6986648]Contra01[/MENTION], I have tried all versions. I'd assume I'd use v5 as it's a newer PX5 device but alas none work. The stock BT dialer app works. Device type is Rockchip and device series is MTCD/MTCE/PX3/PX5 . I am not able to do much logging right now as I do not have any adb access to this device and typing everything out by hand to move logs to and from is a bit difficult.

[MENTION=4292729]SpeedFire-[/MENTION] I've also discovered on these new PX5 devices the volume widget also does not work. It always says 0 regardless of volume and does not change volume by pressing + or -. Perhaps this is an MCU you've not played with? I am a BETA tester and enabled logging since I can't really be doing logcat logging right now, where is that log? I don't see it in /sdcard but I do not have an external sd card right now, just the NAND memory but there is a valid /sdcard path.

[MENTION=6986648]Contra01[/MENTION], did you figure out your BT issue?

So in summary w/ these QD MCU's from joying the following is occurring (I may test more later to see but I think this does not communicate w/ MCU at all)

1. BT not seen (Will not dial out)

2. Auto screen brightness does not work (Nor does widget)

3. Volume widget does not change volume (Always says 0)

4. reboot option does not work but that's the least of my worries and could be because this is not rooted

Dave
[Android Head-Units] Scopesys:
All 4 work on my p5x Eonon GA2170B (Not rooted, oem Rom)
[Android Head-Units] TT_Vert:
[MENTION=9325785]Scopesys[/MENTION] can you tell me what your MCU version is?

Yeah I'm 99% sure this is just not communicating w/ the MCU as it's not an MTCD/MTCE. MCU is TP9735.44, unit is a joying 4/64GB unit w/ Android 8.0 and a PX5 CPU. I'll wait to hear what Speedfire has to say. I know it works perfectly find in my slow ass MTCB unit but It's time to finally move away from 4.4.4 but i'm having a bear of a time finding my exact unit that has physical buttons w/ an MCU that's moddable and also works w/ FCC launcher.

Dave
[Android Head-Units] Scopesys:
Eonon GA2170B (Px5 Oreo)

MCU: MTCE_HT_V2.84_1

May 2 2018 08:55:17
[Android Head-Units] nicusopterean:
hi guys, is it possible to build a route in the Minimap by searching an adress ? , and using it as navigator? or the Minimap is usefull only to view your possition , speed and traffic ?
[Android Head-Units] rigattoni:
You are able to have ADB access if you try this...

You need to be connected to the same WiFi network.

Check the IP address in WiFi settings and write it down.

Install a Terminal emluator app from playstore, open it and put in these commands:

setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot

If the unit is back on, you can connect to your headunit by using ADB on your laptop.

ADB connect 192.***.***.***

If you have Tasker installed, you can import the XML file, added to this posting. Then you are able to start it as task, instead of typing it manually into the Terminal Emulator.... ;)
[Android Head-Units] TT_Vert:
Thanks I already had enabled Wireless ADB. the other day. I have an issue that when the token authentication pop-up comes up it disappears right away. No idea what causes that but I started happening the first day I tried to get wireless ADB working I also have a male to male USB cables hoping to use ADB USB but that didn't work either.

See what it's doing. Disregard the PX3 header, this app works on both intel and rockchip PX3/PX5s. Clearly something w/ this device. Even tried to fully reinstall the stock ROM and same deal. No matter how fast I press ok I can never auth. I did try CLI enabling TCP ADB and it does the same thing.

https://www.youtube.com/watch?v=3HpvqwAt5Rg <---- Video link as embedded seems to be uncooperative.

[YOUTUBE]https://www.youtube.com/watch?v=3HpvqwAt5Rg[/YOUTUBE]

---------- Post added at 11:08 AM ---------- Previous post was at 11:02 AM ----------

[/COLOR]

Thanks for the MCU info. If only I could find your unit w/ the 4th button like I have now that'd be in my garage right now. Have you be able to remap your buttons? I need this one:

[IMG="4 Button head unit"]https://images-na.ssl-images-amazon.com/images/I/71FFJoRNImL._SL1500_.jpg[/IMG]

Dave
[Android Head-Units] Scopesys:
I used the Steering wheel Button define APP that came with the unit to define most of the keys.

For the Google Voice functionality, I used FCC ro define that Steering wheel button.

Then the Buttons on the unit were set up (actually already set, but I messed with them), using the built in setup under Factory Configuration.

I see you have an extra Hardware Button on your unit, What does it do.

The one Con of the Eonon GA2170B is that the screen is not that bright.. Cheap LCD .. not nearly as bright and high contract as say the latest Honda EOM HU.

I suspect most of the China HUs are about the same.

I don't think that a brighter Back light would help... the current one is already breaking through the Blacks.. unit just does not a high Contrast ratio ??
[Android Head-Units] TT_Vert:
Thanks, I'm going to have to reconfigure double/triple press on a few buttons as well. I'm hoping speedfire- sees the post about the MCU compatibility issue and is interested in working on this w/ me as there are quite a few people who are going to be using these units sooner than later. If for nothing else because they want buttons and/or they want the 64GB of ROM.

Dave
[Android Head-Units] Scopesys:
I used the Steering wheel Button define APP that came with the unit to define most of the keys.

For the Google Voice functionality, I used FCC ro define that Steering wheel button.

Then the Buttons on the unit were set up (actually already set, but I messed with them), using the built in setup under Factory Configuration.

I see you have an extra Hardware Button on your unit, "SRC" What does it do.

Also looks like you have 2 CF slots on the front ? The Eonon has one and a micro usb. ( with 3 more USBs on the rear .. giving total of 4 USB + the GPS CF slot)

The Eonon GA2170B has no Car BUS interface, but since the car I have it in is a 1987 Maxima, thats not an issue.

The one Con of the Eonon GA2170B is that the screen is not that bright.. Cheap LCD .. not nearly as bright and high contract as say the latest Honda EOM HU.

I suspect most of the China HUs are about the same.

Good excuse for Tinting the windows !!

I don't think that a brighter Back light would help... the current one is already breaking through the Blacks.. unit just does not a high Contrast ratio ??

I have managed to get most function I need to work from the ADDON Steering wheel Buttons., and make use of Google Voice/assistant, so there is little need to look at or touch the unit when driving.

Have a DRIVING screen, with Clock, Speed, Speed Limit, Street name and the Music Playing.. that is good for 90% of the time.. and if needed I "ask" Google to navigate me.

I'm happy with the setup, ESPECIALLY with FCC .. cannot imagine my HU without FCC ( Thanks [MENTION=1633144]speedfire[/MENTION] )
[Android Head-Units] TT_Vert:
By default it just switches source to source (Radio, video, mp3 player, etc). I have mine mapped to open pandora on a double press and go to next sond on a single press. I configured the navi button to open waze on single press and my radar detector app on double press. I had the volume know single press would mute and double press would open task list. Back could not be programmed so it is just a back button. I used MTC-keys for all of this but it doesn't work on these units I don't think. So you used FCC launcher to define the physical buttons also?

I have two micro SD slots in front. Both can be used.
[Android Head-Units] Scopesys:
OK. Just Googled what the SRC buttons does .. seem pretty redundant if you have Steering wheel buttons, and/or use FCC.

I use 2 instances of the FCC Quickplayer Player Widget to show the selection of 6 Players -(some would say the 3-4 are sufficient :p ) then I can select what I want immediately, without having to cycle though a list of apps, and have them all load and bog the unit down.

One issue I have with the Android system, is that it is so easy to load/start another app, but then it is always running in the background, and after a time they accumulate, and one has to go and un-load them later. I use APPKILLER every so often to clean things up, and then all runs a lot smoother.
[Android Head-Units] TT_Vert:
Yes redundant but I do not have SWC so I need it. I'm not familiar w/ the quickplayer or that name for it. You could also use the speed icon in the top pulldown menu. It'll kill active apps.

Dave
[Android Head-Units] SpeedFire-:
Hi, guys.

There was some time since last beta.

I was working on some internal things which allowed to get rid of launcher restarts in some cases.

Beta 3.112:

No more waiting for a long launcher restart when you:

- Add a new pre-setup screen (Hold finger -> Skins -> Add as a new screen).

- Delete existing screen