yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] bossman4:
Based on U.S. discussions that I have seen and my serious looking for options for universal radios...Here is my list of higher volume "new 2019 unit" sales within the US.. Trying to get a radio with an OEM look and fit really limits your options and I won't address it.

1) Joying comes across as a larger vendor because of their flexibility. Recently, they has seemed to focus on the Airmont (Intel) chips in their units. All the Airmont chips are Octacore

2) Pumpkin seems to be focusing their lower cost with high performance options on the MTK chipset. These have DSP, a high end feature. A keyword for a unit with a MTK chipset is Quadcore

3) Eonon seems to be drifting away from the PX-5 chips and are using the MTK chipset in their high performance value units. The key is that you get DSP in these units as compared to the old PX5 unitswhich cost a lot more. Again, Quadcore indicates MTK chipset.

4) Xtrons newer units seem to be focusing on Quadcore units in the lower ranges. This could be a PX30 or maybe MTK. Not sure The really expensive units seem to have a 64Bit Qualcomm Processor (4GB + 64GB). Not sure chip that is, but the units are about twice the cost as the new mainstream units

5) Dasaita seems to have stuck with the Rockchip Series of chips and are moving up to PX6

Comments

Not sure about the subset of CSN2 operating system (PX Chips?) that Rigatoni is dealing with.

It appears that the value pricing in the Quadcore region and smaller memory is the MTK chipset. It has a lot of the features that folks think they need with the latest Android systems and it has a lot of resellers switching.

Rockchip (PX3,PX5,PX6) appears to be the tried and true heavy weight, but they are being challenged by the MTK chipsets that can get close perfomance for cheaper money. A normal customer has a hard time differentiating for the price differential

Finally, Car Joying had a unique product (movable screen) and continued off with the Airmont chip. They seem to command a high price relative to the MTK chip based units, because of the flexibility of their design

Not sure what the Qualcomm chip is that Xtrons is trying to push on the high end

My bet..... If you have a newer unit from a vendor that is a Quadcore processor with 2 GB Ram 16 GB Rom, 720 resolution, Android 9.0 and DSP ......then it is a MTK chipset and probably the same basic software and interface.

Thoughts?
[Android Head-Units] rigattoni:
...and now nearly all 8-Core units from Pumpkin are sold as CSN2 or CSN2_D with DSP.

All these units are built by Klyde
[Android Head-Units] SpeedFire-:
Great summary! Thank you!

So it seems that some MTK devices cannot be integrated (like mine MEKEDE device), but some other may have a potential.

I would ask MTK (8227) users to send me apks from "/system/app/" and "/system/priv-app/" (root is required) with the name of their device manufacturer.

Then I can deside which device has good potential and will purchase it for integration (or will integrate it "remotely" as it was done with CSN2 but a good tester is required.)

Update: It seems that I have some older modification of MTK unit U708. Newer modifications like YT9217 look much better, maybe I need to buy one.

Overall it is really hard to decide which MTK units are the most popular... really confused with all those different models
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION] Did you see my crash logs some posts above?
[Android Head-Units] SpeedFire-:
This is not a crash. Crash is a "Fatal Error". This looks like a process of closing of different apps (including FCC Launcher) by your head unit while going to sleep.
[Android Head-Units] rigattoni:
OKay, crash is the wrong wording...

But if you have a look at the attached logs, this is the startup trace.

In line 1121 FCC is firstly mentioned in the trace, before the time master was able to set the correct time:

01-18 09:50:28.944 493 493 D AccessibilityManagerService: Ignoring non-encryption-aware service ComponentInfo{ru.speedfire.flycontrolcenter/ru.speedfire.flycontrolcenter.assistant_volume.FCCAccessibilityService}

In line 2197 FCC is started the first time:

01-20 22:30:00.555 493 568 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher (has extras)} from uid 1000
[Android Head-Units] okij:
Haha, stupid me. :laugh: Before testing the latest v2 to v5 for you, I forgot to turn this option on again. (I had turned it off before because I was using the autoplay option of DAB-Z app.)

With autostart player on boot enabled in FCC, now all of my players resume playback as intended, no matter if I only turned off the screen or if I also turned off ACC power. So the resuming of audio playback is fixed and now also works if FCC is whitelisted in the ROM's settings. :victory:

The only issue for me now is that the MiniMap isn't working anymore after FCC is woken from standby. As I already wrote yesterday, this issue was introduced with a code change from FCC 3.352 to FCC 3.352 v2, so should be easy to revert.
[Android Head-Units] SpeedFire-:
First time for a long period I looked at the top list of active devices and.. was amazed that the 1st place takes 8227L. Wow.

It seems that I need to concentrate on supporting this platform.
[Android Head-Units] SpeedFire-:
But in terms of active sessions PX5 is ahead (especially if we combine PX5 and px5 under different name). 8227L is on the 2nd place.

So I should say that MTK platform quickly becomes the most popular (maybe because it is cheaper).
[Android Head-Units] bossman4:
To add some confusion, here are two snapshots of the operating system on my Pumpkin Single DIN. Notice on one screen, it lists "FF-5000" . On the other screen, it lists "8227L-demo".

So in the survey you were referencing, it appears that some folks were calling it 8827L and some were calling it FF-5000. So if you assumed that those were separate answers, it appears that there are a lot of the 8227L/FF-5000 units active. Yes, they are cheaper, but they seem to have the same features as the PX series.

I would like to help you on the apk, but I have never rooted a unit
[Android Head-Units] Scopesys:
I think what it says on those screens is more than a little confusing.. Apparently, it thinks it has no RAM !!
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: Do you need some more informations about this or do you already know what I mean because of the changes you did between FCC 3.352 and FCC 3.352 v2?

What happens is that after waking FCC from standby, the MiniMap display area first isn't shown at all, instead I see just the wallpaper. After swiping to the second FCC screen and then back to the main screen, the MiniMap display area is shown, but I see just its background color and no map on it. Only restarting FCC fixes the MiniMap display until the next standby / wakeup cycle. I have Google Maps set as maps provider.

If you need a logcat for this issue, you can have a look into the two logs that i posted yesterday, where this MiniMap issue also occured.

If you need any more infos or assistance, please let me know.
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] I’ve come across a minor bug. I’m using the latest version from play store. Sometimes if I’ve been using dab-z and then the unit wakes from sleep, then the dab-z will autostart and play audio but the player widget will be blank. There will be no station logo/art, no station info and no track/artist info. It hasn’t happened with Apple Music yet just with dab-z. Sometimes I can get it working by changing player and then changing back or sometimes I have to restart the unit.

Edit. I’ve attached a picture to show the blank player. At this point dab-z was playing audio.
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] I’ve come across a minor bug. I’m using the latest version from play store. Sometimes if I’ve been using dab-z and then the unit wakes from sleep, then the dab-z will autostart and play audio but the player widget will be blank. There will be no station logo/art, no station info and no track/artist info. It hasn’t happened with Apple Music yet just with dab-z. Sometimes I can get it working by changing player and then changing back or sometimes I have to restart the unit.
[Android Head-Units] SpeedFire-:
I think I know the reason. Please check: FCC 3.352 v6
[Android Head-Units] jukk:
Hi,

I have a Rockchip PX30 device (RK3326) and in the latest version at least, FCC doesn't start after sleep. Instead radio app always starts after sleep. When I press my Home button, it takes a while for FCC to start. I have the latest released (paid) version of FCC from Playstore.

Is there a way to configure FCC to start after sleep? I have selected Rockchip device and PX5+ in settings. Is there some other settings I need to check?
[Android Head-Units] SpeedFire-:
If you have a root you can select an option to "erase the latest app" or something like this in FCC Autostart settings. You will also need to give FCC permission to modify system settings.

Radio is launched by your Head unit automatically as a last native app. It is quite difficult to override this behaviour programmed by Chineese manufacturers. But the above may help.
[Android Head-Units] Bugscze:
Hello [MENTION=4292729]SpeedFire-[/MENTION],

can you please add widget for ambient temperature? Hal9k ROM can show it in status bar and in screensaver without OBDII adaper, so it could be possible.

Intent

com.canbus.temperature

can be read by Tasker.
[Android Head-Units] SpeedFire-:
Can you show full Intent / parameters?
[Android Head-Units] Bugscze:
In Tasker, Action is set to com.canbus.temperature and both Cat are set to Default without any additional parameters. Received message is in format "#°C" where # is actually temperature.
[Android Head-Units] jukk:
Thanks, I don't have root in the default OS (don't know how to root it. Does anyone know? If I install custom OS I will get root). But good to know.
[Android Head-Units] SpeedFire-:
There should be some value name which is got from intent. Can you show your Tasker receiver settings?
[Android Head-Units] okij:
Thanks for the new test release. :)

I tested v6 this morning and the issues that I described in post #5196 are not fully solved yet.

What still is not working in v6 (but was working in FCC 3.352, as I double checked this morning) is that the map only gets shown after a "screen refresh". This refresh can either be made manually by swiping from FCC's main screen to the second screen and back to the main screen, or e.g. by the resuming of the FM Radio playback, which brings the radio app to the foreground and immediately toogles back to the FCC main screen.

Before this refresh I still only see the wallpaper instead of the MiniMap display area after FCC resumes from standby. It seems to me that when sending the unit to standby, the MiniMap display area already gets deleted from the screen before the screen goes off (so I assume the task for the map display gets killed?) which didn't happen in FCC 3.352.

What has been fixed in v6 is that when the map is displayed again, it is shown correctly and not just its background color.

I attached a log file for you. For example at 8:29 I woke the device from standby and waited for about half a minute before I swiped the FCC screen to manually start the map display.

As I said, the resuming of the map display was working fine in FCC 3.352 and those issues started in FCC 3.352 v2, so IMHO there must have been another code change which needs to be reverted.
[Android Head-Units] margartom:
The value name is %temperature.

I made a Kustom widget with this info, but it would be great if you could integrate it as an FCC widget.
[Android Head-Units] SpeedFire-:
This should work: FCC 3.352 v8

Please also try the version above. I temporarily put this data into AccVoltage widget. If it works I will make a separate Temperature widget. Please confirm.
[Android Head-Units] tonimontoia:
and for all this version?
[Android Head-Units] SpeedFire-:
Every version is for all :)
[Android Head-Units] tonimontoia:
Ok thanks
[Android Head-Units] okij:
It's PERFECT now, thanks a lot! :highfive:

From my point of view you can now disable the test toast messages again and release FCC 3.353. :)

Now that the audio resume also works well with FCC being whitelisted in the ROM's settings (which prevents several issues that I had when FCC started from scratch each time after standby) and DAB-Z is very well integrated (also thanks to the DAB USB stick which you extra bought for implenting this), I would be happy to make an extra donation to honor your work. Please add a donation info to your profile or write me a pm about this, if you like.
[Android Head-Units] ric69:
Hello I'm not sure I understood well but if you think at this widget, it's not supported by px30 here
[Android Head-Units] dagosjt:
New user

Hi,

after looking to several headunit launcher I narrowed the choice between two of them before to buy. I would already bought FCC if I didn't encounter some little problem, but let me make little introduction:

- I have a tablet at home (Samsung tab S5e) and an Xtrons PR78FSF-S head unit, Android 8.1 original ROM not rooted, Allwinner T8, 2Gb RAM and 16Gb ROM, 7" 1024x600: https://xtrons.co.uk/pr78fsf-s

- I started to customize my headunit with Nova + KLWP, and I basically was able to have an interface I liked a lot. I built it mainly on tablet, then with some adjustment (dued to different screen resolution) I was able to restore on HU.

- I'm using the free PlayStore version (3.352)

However I liked a lot two features that only FCC seems to have, MiniMap and RadioFM widget integration. The other choice I'm evaluating misses RadioFM integration but give a wonderful graphical aspect, something I noticed FCC is still missing.

Now, let me say what's not working in my setup:

1) On tablet S5e I'm not able to add widgets that need to be configured before to be added. For example, Chronus or weawow. I guessed it could be because FCC is NOT the default launcher on my Tab, am I right? Is it possible to solve this? I can find some time inside house much more easily than on car to play with FCC widget configuration, but it's not so convenient to continuously change default launcher.

2) On HeadUnit the MiniMap works fine a part the street name that rarely update. Reading through this thread it seems it was an old problem the developer was able to solve, however it wasn't so for me. I'm speaking about the road shown directly inside MiniMap, and I'm using the google one, the only possible for free users.

3) The most annoying problem is about RadioFM. Simply it doesn't work inside Player widget. If I'm listening another player and I click on "RadioFM" everything mute and there is nothing to do but press another player or directly start the Radio (I use the hardware button). All the other players I tested works just fine.

I would like to know if the problems 2) and 3) are expected (for example because I have an Allwinner T8) or not. And if a reason could be that I built the screen configuration on Tablet and I restored on HU. It appeared everything fine but maybe this brings something strange with it. As test, I already removed and recreated the Player widget, unsuccessfully.

Thanks in advance for the help :)
[Android Head-Units] margartom:
I confirm that your widget behaves properly on my PX5 unit. :good:

As you can see in the attached image, I placed the 2 widgets side by side and noticed that they work the same way.

Suggestion for implementation: The font size for the °C part is 60% smaller than the numeric part of the temperature . Additionally, it would be nice if somenone can change the font family of the widget. The latter is a more generic suggestion: the ability font family to be changed at the widget basis and not globally.

By the way, in my headunit the font family setting affects only the items of the configuration screens of FCC and not the foreground items. Has anybody else noticed the same thing?
[Android Head-Units] SpeedFire-:
First steps of MTK (8227) integration. FCC Launcher 3.353

Please check is anything work on your device or not:

1) FM Radio from FCC widget

2) Volume control

Don't forget to go to FCC Settings - System - Advanced and switch to MTK device
[Android Head-Units] liamstears:
Thank you for your continued support and releases they are much appreciated!

However I do have an issue with the new CSN2 integration, I have 2 faults, 1 is that randomly when turning the headunit back on and resuming from sleep the volume jumps to 30, sometimes multiple times I put it back down then it jumps back up, this is very bad for me as I have spent a lot of money on my audio equipment and this is risking blowing something up

Also the volume widget works to turn volume up or down but is always stuck on the volume you leave it set at. For example set volume to 10 using widget but then turn volume up to 14 using steering wheel controls and widget still says 10

Hope you can help, in the meantime I will try and see if I can get a logcat but I have moved back to PX5 setting in FCC as I don't want to cause damage to speakers using CSN setting...

EDIT: If you need any APK sending to help let me know I have full rooted latest ROM and can send any file you need, also I think it's important to point out your beta tester was using standard CSN2 unit and I have DSP CSN2_D so this may be the difference in how audio is handled?
[Android Head-Units] SpeedFire-:
Yes this is an important bug. Thank you for reporting it! Yes I need apks. If you could get a log this would be great as well.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

It looks like you will be involved in CSN2 integration for some time.

Is there any chance you can sneak in support for User defined Minimap json files (one for day, one for night). (like you did for custom images for the Compass Widget)

I am assuming that this is a relatively simple and quick thing to add.
[Android Head-Units] bossman4:
I installed 3.353 on my Pumpkin (8227L). Initially, it looks like it installed multiple APk's onto my system. Some of the names were repeats. Some were named slightly different. I am assuming that they were APK's from your donor unit. I already had an APK titled "Radio" from a previous source. If I picked that APK it would activate the radio. 3.353 installed an APK titled "Car Radio".

I went into FCC settings and switched on MTK.

I changed the quickplayer choice to installed "FM Player". I then tried the different choices in Quickplayer (BlackPlayer, Amazon HD, Radio). All worked except for the radio. Is that because you picked the "Car Radio" APK rather than "Radio" APK in your coding?

I was not sure on how to check the volume widget and will need to go down again and see if I can find a volume widget in FCC.

I will go back to your "screen shot" of the MTK unit that you are working on to see if I can isolate the extra APKs that came along with the install that may be duplicates (Bluetooth, or not applicable).

Thanks for the work on this unit.

---------- Post added at 10:50 AM ---------- Previous post was at 10:36 AM ----------

Here is the link that I used to find my Radio.apk. I attached the zip with some APK's and a separate APK.

https://xdaforums.com/showpost.php?p=80655725&postcount=143
[Android Head-Units] SpeedFire-:
There are too many different versions of 8227L MTK units. My older U708 version cannot be integrated at all. I tried to integrate newer YT2916, YT2917, YT2918 units with aps like "xy.com.*.apk"

Pumpkin is probably a completely separate story.
[Android Head-Units] bossman4:
Hopefully, that Thread and the attached files that I sent may help with my situation.......

Hope somebody else can test your fix.......with their units ( YT2916, YT2917, YT2918)

Where are you locating the YT designations on the radio. The nomenclature that the ALPS (MTK) units uses to describe their units is quite a bit different than the PX5 units and I get confused trying to figure out what kind of basic unit that I have.

Thanks again
[Android Head-Units] SpeedFire-:
This is a Build ID which can be found using AIDA64. Here is the newest YT2960 build ID:

View attachment 4934481

All of these units are Quad-core fake "Android 8.1Go" units (they are actually Android 6.0).
[Android Head-Units] KitF:
How would I go about poking around to see if it'd be possible to get speed from canbus? The default launcher has speed (but only in kp/h), but seems everything else fakes it with GPS.
[Android Head-Units] bossman4:
My unit seems to fairly close to these EONON units with a true 8.1 (even though it is supposed to be 9.0) based on the signatures.

https://xdaforums.com/android-auto/...on-ga2168k-head-unit-eonon-v0057-dsp-t3914574
[Android Head-Units] maxbboard:
Hi [MENTION=4292729]SpeedFire-[/MENTION], I helped finalize the Portuguese translation of the FCC. You can see this on your collaboration platform. Hope this helps.
[Android Head-Units] bossman4:
Here is my report from AIDA64 for the Pumpkin .

https://www.autopumpkin.com/product...gle-din-car-stereo-radio-7-inch-with-gps-navi

Obviously, Build 27 is 8.1, even though it says 9 (Pie)

<<< Android >>>

Android Version: 9 (Pie)

API Level: 27

Android Security Patch Level: 2018-05-05

Rooted Device: Yes

Android ID: da143ef5146db2be

Build ID: full_8227L_demo-userdebug 8.1.0 O11019 1550113051 test-keys

Codename: REL

Fingerprint: alps/full_8227L_demo/8227L_demo:8.1.0/O11019/1550113051:userdebug/test-keys

ID: O11019

Incremental: 1550113051

Java Runtime Version: Android Runtime 0.9

Java VM Version: ART 2.1.0

Java VM Heap Size: 192 MB

Kernel Architecture: armv7l

Kernel Version: 3.18.79 (root@ubuntu) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) ) #72 SMP PREEMPT Tue May 28 14:01:55 CST 2019

Tags: test-keys

Type: userdebug

Google Play Services Version: 19.8.31 (040304-284611645)

Huawei Mobile Services Version: < Not Present >

OpenSSL Version: OpenSSL 1.0.2 (compatible; BoringSSL)

ZLib Version: 1.2.8

ICU CLDR Version: 30.0.3

ICU Library Version: 58.2

ICU Unicode Version: 9.0

Android Language: English

Configured Time Zone: Eastern Standard Time (UTC-05:00)

UpTime: 00:06:12

<<< System >>>

Manufacturer: alps

Model: FF-5000

Brand: FFKJ

Device: FF-5000

Hardware: ac8227l

Platform: ac8227l

Product: FF-5000

Serial: YL9TDM4LTWP7KZZH

Installed RAM: 2 GB

Total Memory: 1957 MB

Available Memory: 915 MB

Internal Storage Total Space: 11.90 GB

Internal Storage Free Space: 8384 MB
[Android Head-Units] bossman4:
Here is my report from AIDA64 for the Pumpkin .

https://www.autopumpkin.com/product...gle-din-car-stereo-radio-7-inch-with-gps-navi

Obviously, Build 27 is 8.1, even though it says 9 (Pie) .

Did a snapshot of "About" screen also

<<< Android >>>

Android Version: 9 (Pie)

API Level: 27

Android Security Patch Level: 2018-05-05

Rooted Device: Yes

Android ID: da143ef5146db2be

Build ID: full_8227L_demo-userdebug 8.1.0 O11019 1550113051 test-keys

Codename: REL

Fingerprint: alps/full_8227L_demo/8227L_demo:8.1.0/O11019/1550113051:userdebug/test-keys

ID: O11019

Incremental: 1550113051

Java Runtime Version: Android Runtime 0.9

Java VM Version: ART 2.1.0

Java VM Heap Size: 192 MB

Kernel Architecture: armv7l

Kernel Version: 3.18.79 (root@ubuntu) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) ) #72 SMP PREEMPT Tue May 28 14:01:55 CST 2019

Tags: test-keys

Type: userdebug

Google Play Services Version: 19.8.31 (040304-284611645)

Huawei Mobile Services Version: < Not Present >

OpenSSL Version: OpenSSL 1.0.2 (compatible; BoringSSL)

ZLib Version: 1.2.8

ICU CLDR Version: 30.0.3

ICU Library Version: 58.2

ICU Unicode Version: 9.0

Android Language: English

Configured Time Zone: Eastern Standard Time (UTC-05:00)

UpTime: 00:06:12

<<< System >>>

Manufacturer: alps

Model: FF-5000

Brand: FFKJ

Device: FF-5000

Hardware: ac8227l

Platform: ac8227l

Product: FF-5000

Serial: YL9TDM4LTWP7KZZH

Installed RAM: 2 GB

Total Memory: 1957 MB

Available Memory: 915 MB

Internal Storage Total Space: 11.90 GB

Internal Storage Free Space: 8384 MB
[Android Head-Units] SpeedFire-:
Great! Thank you for your help!