yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] rigattoni:
FM-Radio is no real app!

The radio itself is on the mainboard and the FM-Radio app in Android is more or less the mute/unmute part of it. FM-Radio plays always and long before android is ready with startup. If you close FM with the back button, it is more or less muted, nothing else. If you don´t close FM-Radio completely before shut down (Sleep), FM will always be the app which starts first and stays there unless you close it, or press the Home button.

I assume that this is quite difficult to overrule, but may be [MENTION=4292729]SpeedFire-[/MENTION] has an idea, to send FM at least to background that FCC can start up.
[Android Head-Units] Scopesys:
I would also welcome such a widget. especially if it showed both that there was a connection, as well as showing that there was Internet Connectivity (maybe by an occasional PING)

The current FCC WiFi widget work very well, but there are still some issues with its Bluetooth part, which could be improved, despite the issues of a widget not being always able to get the Paired device NAME. At least the widget "could" show the connection states ( Not paired, pairing, paired, or paired with media data on).

(Will post a beta testing report on this later, when the current Player/startup issues have been resolved.)
[Android Head-Units] SpeedFire-:
This may resolve issues with launched FM Radio on boot as well as with some other boot actions.

Please check.

FCC beta 3.352
[Android Head-Units] maipaozi@gmail.com:
Thanks alot. Would try it out!
[Android Head-Units] okij:
I found out that with Tasker it's possible to perform an action when the screen is turned on (= head unit is being waked from standby). This works very reliably.

Can FCC start playback of the last used player on receiving an intent (which I would then send via Tasker)?

If not, could you implement such intent?

The current beta 3.352 still behaves very inconsistent when FCC gets started after standby. Therefore I want to whitelist FCC and resume playback by the above mentioned approach via Tasker. If this works well, we could try to find a way to do this without Tasker.

I'll write some more infos later today when I have more time.
[Android Head-Units] SpeedFire-:
Yes, I could. What intent do you receive by the Tasker? SCREEN_ON? I tried to use it.

Can you send me the logs of your inconsistent start with some short description as before?
[Android Head-Units] maipaozi@gmail.com:
Speedfire fixed this with a new beta. The default fm player doesn't start anymore :)
[Android Head-Units] okij:
I looked for some universal way to do some actions (like resuming media play) after standby. First I found this post here which describes to use the com.microntek.startApp intent for this purpose, but I tested this intent with Tasker and it doesn't react to this intent, so obviously it isn't used anymore by recent Microntek ROMs. Besides this, it wouldn't work for non-MTCD/MTCE ROMs.

Then I tested the built-in Tasker function to execute a task upon ScreenOn. For testing purposes I set up tasker to display a toast notification when the screen is turned on (i.e. the head unit is woken from standby) and this works absolutely reliably. Every time after starting the device from standby, I instantly get this toast notification.

So I thought of using the ScreenOn event in Tasker to send an intent to FCC to resume playback after standby. That's why I asked you about this.

I don't know how Tasker reacts to a ScreenOn event. It might well be that it uses the android.intent.action.SCREEN_ON intent as is described here.

Are you already using android.intent.action.SCREEN_ON in FCC? If this is the case, then this method should work very reliably. But if this is the case, then the code that's being executed to resume playback isn't working reliably yet and has to be fixed. Of course this only applies to FCC being whitelisted.

Today I did some similar tests with 3.352 like I did yesterday with tested 3.151 v2. Since DAB-Z worked again after I fixed the antenna cable, I used it for those tests now:

17:42 cold boot, FCC and DAB-Z started as intended

17:43 start from standby with FCC whitelisted, DAB-Z started to play as intended

17:44 start from standby with FCC whitelisted, DAB-Z didn' start

17:46 start from standby without FCC whitelisted, DAB-Z started to play

17:47 start from standby with FCC whitelisted, DAB-Z didn' start

17:49 start from standby without FCC whitelisted, Tasker was not killed and stayed in foreground, DAB-Z only started after pressing the Home button to launch FCC

Like yesterday, when FCC was whitelisted, the resuming of the last player only worked one time (at 17:43) but not again after this. Again this was during the first start from standby after the cold boot, after this it gets buggy. So obviously this needs to be fixed.

This afternoon I did just one test for you with Tasker running (at 17:49), but this morning I did some more tests and Tasker sometimes gets killed during the start process of FCC, sometimes it doesn't get killed. This is quite inconsistent too. Actually I don't want any task to be killed by FCC, since I want to leave it up to my personal decision what apps survive standby, according to the whitelist in the ROMs settings. That's why I absolutely prefer FCC to be whitelisted, so it doesn't kill (and doesn't have to kill) other apps before or after standby. The only problem currently with FCC being whitelisted is that the resume of audio playback isn't working most of the time.
[Android Head-Units] hycraig:
[MENTION=4292729]SpeedFire-[/MENTION] is there Mediatek integration yet if so what option can i pick to use it?

this is the unit i have its a MT3561 chip https://www.aliexpress.com/item/32542027294.html?spm=a2g0s.9042311.0.0.b3134c4dQpB78f
[Android Head-Units] rigattoni:
You should post screenshots from "About the tablet" or similar.

There we need the MCU, CPU and Model of the unit.
[Android Head-Units] maxbboard:
Please [MENTION=4292729]SpeedFire-[/MENTION], can you tell us if is possible to improve someone thats itens bellow? Specialy the firts.

Please, is very important to my project. You laucher is the better that i find. Tanks a Lot.
[Android Head-Units] chrissooo:
Hi, i have buy a Device with following specs:

Manufacturer: alps

Model: FF-5000

Android version: 10

CPU: 4 cores; ARMv7 Processor rev 3 (v7l); Max: 1118.0 MHz; Min: 598.0 MHz

Display: 1024 x 600; DPI: 240

GPU: Mali-450 MP; ARM; OpenGL ES-CM 1.1; OpenGL ES 2.0 58bf738

RAM: 2 GB

Flash: 16 GB

Board / Device: ac8227l?? MediaTek? (I have found this information in Internet)

When i start FCC Launcher the first time, i must choose the Board, but nothing work. In the Info at botom are the Board marked as unknow. My Problem ist that the FM Radio App (and some other Apps) are not visible in the App list, but when i set up my favourit Media Apps in the FCC Launcher Setup, i can choose the FM Radio App. How can i fix my FM Radio problem. Becourse at the moment i can´t launch FM Radio from the Launcher. The Other Apps is not the Problem.

Thanks for help.
[Android Head-Units] ric69:
Hello, you need to install radio apk's to resolve problem with ac8227l, then Shortcuts will appear afaik :good:

Check this : https://xdaforums.com/showpost.php?p=79053917&postcount=4
[Android Head-Units] rigattoni:
deleted
[Android Head-Units] bossman4:
Yes, these are the APKs that I now use in my Pumpkin unit which has the 8227. Unzipping them in a directory and clicking on the individual apks will install them individually. You can make these items a menu choice on the FCC menus. (FM Radio, Bluetooth, Standard Player)

The only things that I do not have working in FCC

1) The phone dialing within FCC system through the custom dialer option, rather than using this Bluetooth apk

2) I believe on the FCC Quick player choices, I can't get the FM tuner to start for some reason if I make it one of the players.
[Android Head-Units] ric69:
About 1) : It's not FCC related, if you install Google.Contact.apk on Playstore, you will not be able to see your contacts - Impossible to synchronize google account (according to my tests)- The only program working is contact+ but it's expensive and will never work to phone directly (as there is no direct dialer.apk like a phone)

In fact, car radio is a tablet not a phone as far as I know
[Android Head-Units] chrissooo:
Thank you very much. Now i can run the FM Radio.

- Is there a plan to make a deep integration of this device type?

- And do you have also so bad performance? I think this device ist really slow. Google Maps start very slow, Voice recognation ist very slow...
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

I startet yesterday eve a message, but to be sure I deleted my posting.

Now I am sure that the Autostart option for other apps is not working anymore.

I tested a couple of different apps last night and none of them are started after sleep sleep.

During startup it´s not really possible to grab log files. If you are not able to reproduce it, I would try to get logs over shell.
[Android Head-Units] SpeedFire-:
MTK (8227) integration is what I want to do next. I have a test Mekede device but I wasn't able to get a root on it. Do you have a root on yours? If yes can you send me the apks from system folders (priv and priv-apps)?
[Android Head-Units] mclaudio:
hi there

i have premium and Intel processor

on previous versions the widget was able to open Radio, but now it does not open. some times (depending on type of device i select), it trys to open google play and says not found, on other type of devices (from settings), it simply does nothing when i hit radio. also SWC do not work with AIMP. in both cases it does not get focus for album art or radio frequency.

Spotify is working great for album art, SWC, etc

what can i do?

good news is that with the new SMN2 type of chip, brightness widget does work.
[Android Head-Units] ric69:
That's strange, it's working great on px30 (cold start or after stand-by) I'm using camsam, each time it's starting automatic with FCC

Only issue to me (but it has probably already been said before) tag's name are always wrong, it's always the previous song name from list. (standard player) I have to click on home button to refresh
[Android Head-Units] rigattoni:
Camsam is the same as the German Blitzer.de and this app starts automatically on BT connection.

I know that this was working last week on my unit, because I always have to enable some settings on start up to get notification listener and some other system-settings back working for some specific apps.

For this to make happen, I built an app which activates these settings, triggered by autostart for application. Since the last 2 updates this is not working anymore.

Unfortunately none has found a solution to whitelist some apps to keep them running in sleep mode.

I tried several apps in autostart, but none of them starts after FCC is starting.
[Android Head-Units] ric69:
Ok you're right with camsam autostart but I tried with Spotify, its starting too (ok it has BT autostart) so I tried YouTube vanced... it's starting too here :good:
[Android Head-Units] rigattoni:
May be related to the FCC settings to CSN2.
[Android Head-Units] bossman4:
There is a very large contingent in a Russian Forum that has been working on the Mediatek (8227) The link to the missing APKs (previously posted) leads you back to that forum. I have skills, but Russian is not one of them. Based on the numbers of posts on that particular forum, you would think somebody has rooted a unit with an 8227L.

---------- Post added at 12:05 PM ---------- Previous post was at 11:30 AM ----------
[Android Head-Units] fresnoautobody:
About that Car Launcher

Great! It would be nice and enjoying having your car with this launcher. It's not just fanciness but also the benefits and services that it would give to you. If I'm correct this launcher has it's GPS and other features right? I wonder when will be the best time to install this in our car.
[Android Head-Units] chrissooo:
Hi again, sliwly my Radio works nice. Performance is not the best ... however. One of the left Problem ist that there is Not possible to Start the DSP App witch i need to Set Sound / equlislzer, and positions in Car, Bass ...

Ist there a solution die my ac8227l?
[Android Head-Units] Shadow128:
OK, today another test and trial of FCC.

After disabling all automatics for the media player and configuring Tasker to do this it seems to run.

But two points for design improvement (in my mind):

1) It is possible to make the position of the Album/Artist configurable?

I'd like to put it to the middle/bottom of the displayer cover of the current playing album.

2) It is possible to make a configurable background color for the displayed text?

Would be great :)
[Android Head-Units] aprt:
Same here
[Android Head-Units] Scopesys:
I am now totally LOST when reading many of the posts on this forum !!

This year there seems to be many posting about Players starting or not starting etc etc, some say things are working ok, other say they don't.

There is also a stream of FCC alphas & betas updates, that seem to be trying to address these issues.

The two problems I am having, making any sense of all this is.

(a) Are these FCC updates to address issues with specific Head Unit models (and if so, which one), or are they meant to have an impact on ALL models.

(b) When user post about having issues, it would be most helpful if they had their head Unit make/model in their Signature.

They know what unit they have, and may have mentioned it in some distant past post, but trying to keep up with who has what is becoming increasing difficult -- and I don't know how SpeedFire could keep up with it (which is the most important thing)

Personally, I have Px5 unit, and live in the USA (so no DABs to worry about), and it see that for the past few months at least, I have not experienced any issues with any of the Mp3 or streaming players starting. -- the only issue I experience is slowness in starting, mp3 players because the Android OS insists on doing a long winded Media check when the unit boots, and streaming players waiting for an Internet connection to be established,

BTW I am NOT using tasker, or any other method to force anything.. FCC seems to be doing just fine without any extra help.
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION], since you asked for it: My head unit is a PX5, 4GB RAM, 64GB flash, MCU: MTCE_MX_V3.41, ROM: Android 9 Hal9k v4.0.1. As you know this head unit is a very common model (PX5 MTCE). Yes, I am using DAB-Z for digital radio reception, but the issues that I experience happen with other players too. And since you mentioned it: Normally I don't have Tasker activated, since I don't need it for anything yet (although I have some plans for it), so my tests are done without Tasker running if not otherwise mentioned in my posts.

From my experiences the stability and consistency of FCC when starting from standby is far from perfect and needs to be fixed. In the past two weeks I posted some detailled bug reports including log files for [MENTION=4292729]SpeedFire-[/MENTION]. Especially these five posts I consider worth mentioning:

#4966

#5103

#5105

#5111

#5114

What IMHO really needs to be fixed is the resuming of audio playback after standby when FCC is whitelisted and so survives standby. It doesn't make sense at all that FCC is killed when the head unit goes to standby (plus FCC then even killing other running tasks) if the ROM supports this via whitelist. To be honest: Do you know any Android phone or tablet where the launcher is killed during standby (= screen off) and then started from scratch each time? The users would go mad if this was the case.

As I pointed out in post #5105 and post #5114, the resuming of audio playback after standby when FCC is whitelisted already works, but only for one time after a cold boot. That means it resumes playback after a cold boot and also resumes playback after the first start from standby, but not on subsequent starts from standby. Therefore I am quite sure that this issue can be fixed.

[MENTION=4292729]SpeedFire-[/MENTION]: I guess that you didn't have much time in the last couple of days, since you didn't give any feedback on my latest post or released a new test version. But I would like to know if you could make use of my log files and if you need some more tests and log files. I have some time this weekend and am happy to help. :)
[Android Head-Units] SpeedFire-:
OK, I understand that we have some issues with autostart and players, but I decided to postpone fixes for a short period.

I really want to integrate MTK first because it seems to become the most popular platform now.

I've finally rooted my Mekede 8227 unit and now I can start to integrate it. First result is that integrated apps are now visible in the launcher without any action required from user.

View attachment 4928935
[Android Head-Units] Scopesys:
Thanks .. not really just for me, but for everyone, Why not put it in your Signature, so it is always visible when you post ?
[Android Head-Units] bossman4:
Great!

We just need to figure out all the different "brands" of all units sold that are really the same hardware (8227L) and software.
[Android Head-Units] hycraig:
[/COLOR]

thats great news if you need a tester let me know i would like to help if i can.

also which method worked for you to root? as i am trying and not getting anywhere so any info to help would be good. :good:

thanks for your hard work
[Android Head-Units] jukk:
As I have understood it, one important bit of information in these Android units is the actual manufacturer name, which is indicated by two letters along with the developer "generational" name, e.g. in my case MTCE_HT, where HT is the actual manufacturer of the MCU unit. You can read more here https://xdaforums.com/wiki/Hui_Fei_Type#Manufacturers

The two manufacturer letters are important, because different MCU units are not compatible with each other and you can't for instance flash the MCU firmware from one manufacturer to another (some of them could be compatible). Thus, they could have some difference in functionality, too.

This information is visible in the system information on the unit, so if you look at it once, please write down the letters.

I've included a picture of my own unit where these letters are marked with two red boxes. You can also see the MCU firmware version after these letters.
[Android Head-Units] okij:
I understand your decision, now that you managed to root your Mekede 8227 unit, so I wish you good luck with the integration of the MTK platform! :) But I take your word about further looking after the autostart and players issues in a short period. You should know that - after having posted several bug reports and log files - I'm a bit disappointed that I didn't at least get some feedback if you found something useful in my logs.

Actually it's not only that I don't use my own signature, but also that I have "Show Signatures" disabled in my XDA options. I decided for myself that it's too much "bling bling" (= a bad signal-to-noise-ratio) to see the user signatures at the bottom of each post when reading the XDA forums. Quite often I read them on my 4.6'' phone screen and some signatures are a little long to scroll through or too attention seeking. :)

Nevertheless you are absolutely right that posting the hard- and software configuration is useful when making a bug report.
[Android Head-Units] nimslo:
[MENTION=4292729]SpeedFire-[/MENTION]

On my T3-P3 Quad-Core with Android 6.0.1 the "Route" widget, which shows the navigation instructions on the launcher screen while the navigation app is working in background, does not work correctly with Google Maps.

While the widget works perfectly when using Sygic and shows both the direction arrow and the text instructions (see Pic 1), only the text instruction is shown correctly when using Google Maps, but not the direction arrow. Instead of this, a navigation icon (Pic 2) appears unchanged throughout the journey. This icon only changes when Google Maps is downloading offline maps (Pic 3). Installed FCC Launcher software is Version 3.350, but the same malfunction has also occurred with the various previous alpha and beta versions of the past few months. The hardware seems to be a modified Allwinner (Pic 4), but think of it as a pure tablet, without radio receiver and so on, just a so called Android box to complement the stock car radio, no "deep integration" by FCC Launcher needed. It does not matter if I choose "Allwinner" or "Tablet" in the FCC settings, the malfunction occurs in both cases. Should I do something wrong and just have to make some special settings on Google Maps, I would be grateful for tips. However, I am afraid that, maybe just under Android 6.0.1, the widget asks for the wrong values of the Google Maps app, for which in my opinion the fact speaks, that the navigation icon is not frozen, but can change to a download icon. It would be great if this matter could be resolved!
[Android Head-Units] SpeedFire-:
I looked at your logs earlier and found out that SCREEN_ON intent is actually sent to the system after wake up, but it was blocked by Android. Starting Android 9 probably apps (including FCC Launcher) cannot receive broadcasts while they are "in the background". So I don't know how to fix this.

If Tasker was able to receive this intent you can try to start a special IntentService in the FCC Launcher (this can be started even if the app is in the background). Here is the code (you need to adapt it for Tasker):

Intent intent = new Intent("ru.speedfire.flycontrolcenter.ACTION_ACC_ON");
intent.setClassName("ru.speedfire.flycontrolcenter", "ru.speedfire.flycontrolcenter.receivers.AccOnOffServiceReceiver");
mContext.startService(intent);

Please pay attention that this is startService not a sendBroadcast.

All of the above is a workaround (which I don't like, generally, because they require some actions from the users) but you can try it for now.

P.S. MTK integration is really hard. I've spent several hours without any good results so far.
[Android Head-Units] nimslo:
Shortly after I sent my post # 5144, I noticed that picture # 1 contradicts itself. The direction arrow points to the left, the text below it says "turn right". Nevertheless, the widget works perfectly with Sygic. This contradictory photo is due to a special situation in the parking lot where it was taken. It would be better to upload an other picture, but I did not realize this issue. Once again: The widget works perfectly with Sygic, a problem occurs only when using Google Maps.
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: Thanks a lot for your feedback, much appreciated! :)

So in Tasker this should translate to a Send Intent action with

Action: ru.speedfire.flycontrolcenter.ACTION_ACC_ON

Package: ru.speedfire.flycontrolcenter

Class: ru.speedfire.flycontrolcenter.receivers.AccOnOffServiceReceiver

Target: Service

Can you tell me if this correct?

I will try it tomorrow on my head unit and report the results here. If it works, maybe this can give a clue how to fix the SCREEN_ON issue in FCC.

From what I tested so far, Tasker triggers a task reliably on my head unit by its built-in Display On event. Tomorrow I will also try if a task gets triggered reliably by the android.intent.action.SCREEN_ON intent in Tasker. (Actually I think that Tasker's Display On event internally uses android.intent.action.SCREEN_ON anyway.)

I keep my fingers crossed that you make some progress. :fingers-crossed:
[Android Head-Units] surfer63:
As far as I know this only works for system apps. If you are rooted you might try to copy/install the apk into something like /system/priv-app/fcc-launcher and reboot (and think of correct folder and apk rights being 0755 and 0644). And see if it works. If it really requires "system signing" you can forget it as FCC has its own signing different from the system.

This is also a work-around as it will break the automatic upgrade from the play store (I think).