yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] SpeedFire-:
Actually I don't remember that I changed anything related to this. Probably it is better to reinstall the app and check if this bug still exists. If yes I will need something to investigate it (log, description of some specific conditions in which it appears etc.).

And one more important question: does anyone here have the same problem?
[Android Head-Units] Roerbakeitje:
No problem with the autostart when it comes out of sleep. 1 have only 1 program in autostart that's waze
[Android Head-Units] TT_Vert:
Yeah it seems it just is crashing if i come out of sleep too soon, nothing to do w/ FCC.

Dave
[Android Head-Units] SpeedFire-:
You can increase a pause before apps launch (in FCC autostart settings).
[Android Head-Units] TT_Vert:
Thanks, I'm not sure the issue was that the app was starting up too quick. I think it is just android freaking out. The exchange service crashes sometimes also. If I let it sleep for a minute or so all is well it appears. Now i need to find out why waze just locks out of nowhere some times. I have force kill it sometimes twice to get it to not lock. Multiple versions do it. I'm going to ensure it isn't this launcher causing this.

Dave
[Android Head-Units] Roerbakeitje:
Dave I think it's waze . I have that problem also that waze freeze out of nothing. I.m going to download 2 versions back . I hope that that solves the freeze problem in waze.
[Android Head-Units] TT_Vert:
is it freezing right when you open it?

Dave
[Android Head-Units] Roerbakeitje:
No sometime like 30 sec . When it's search for GPS. Showtime out of nothing. I.m gone try a old waze version to test.
[Android Head-Units] TT_Vert:
Yeah mine freezes fairly quickly. It shows the map but usually doesn't finish populating it. Im a waze beta tester so I may try an old non beta again.

Dave
[Android Head-Units] pa.ko:
Even non-beta freezes for me, too. It started some time ago. And I doubt they have any ambition to address that issue. For instance, Here WeGo just crashes on start everytime on 4.4 (not only HUs but on phones also) and they don't address that for months and several new version releases.

It looks like many are dropping support for old Android versions, like 4.4. And they don't care.
[Android Head-Units] TT_Vert:
ok If you find a version that works let me know

Dave
[Android Head-Units] TT_Vert:
BTW, are the versions. I'm going to try a few. The problem doesn't always occur for me so I won't know right away. I'm going to start w/ 4.16..0.1 if you find out before me what is reliable please report back.

Dave
[Android Head-Units] SpeedFire-:
Just uploaded a new beta:

- Experimental: you can change apps' icons and labels

Let me know if it works.

Update: just posted a quick fix (the app crashed when widgets settings were launched)
[Android Head-Units] SpeedFire-:
This means that permission for notification messages (animated overlay notifications) is not granted. To enable it manually:

- Open Settings > Apps

- Tap the Gear icon on the top right of the Settings page

- Scroll down and tap “Special Access”

- Tap “Draw over other apps” and toggle launcher in the list
[Android Head-Units] bossman4:
Thanks, will try

---------- Post added at 10:18 AM ---------- Previous post was at 09:19 AM ----------

Ok, got that straightened out. With all the alpha testing of the different versions, things got scattered. Now I am concentrating on getting the album art consistent on BlackPlayer and Amazon Music downloaded files, so FCC can actually display it. I am noticing that there appears to be some missing artwork after moving all the USB drives around. Downloading all the sticks again. Out of curiosity, does FCC have a limit (or a recommendation) on the artwork resolution? On the FLAC/MP3 files, there is a choice. On Amazon Music, you get what they provide.

After that, it will be time for a leisurely drive with some trying of the various applications (Quick Player, Maps, Contacts)
[Android Head-Units] SpeedFire-:
Previously I set a limit of 256x256. Every album art with a higher resolution was downscaled to 256 pixels.

In the latest alphas maximum resolution was increased to 320x320.
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

This was something I was going to bring up again, once the priority was not on fixing current bugs in FCC, but since you are in this area of the code :-

On the popular 1024 x 600 Head Unit screens, the FFC normal Player Widget, the typical Artwork size displays as 400 x 400. (assuming that the top screen menus is turned off). ( with top menu, it's more like 400 x 350)

I have made all my Radio Station images 400 x 400 in the hope that this would be the best size for original, pre-scaled Image, that should then not need re-scaling if displayed in FCC.

It seems that FCC was then taking that 400 x 400 image, and converting it to the limited 256 x 256, ( now 320 x 320) and the re-scaling up to 400 x 400 to display. :(

If you have gone from 256 x 256 to 320 x 320, that 320 x 320 still has to be scaled to display. Might it not make more sense to set the FCC limit to 400 x 400 ( the typical native FCC artwork image display size)

Not that the difference between a native 400 x 400 image vs a 320 x 320 upscaled to 400 x 400 may be that noticeably better on a Car head Unit

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

IGNORE the "on the same subject" part of post below.

When I went to take some screen shots to show this, I realized that you had already done what I was suggesting below (some time ago). I had not noticed that update, as was still incorrectly assuming that this issue was still pending to be fixed. ( I left it in this post, so others will appreciate that it was done some time ago)

Speedfire- MANY THANKS for fixing that when you did back in an earlier FCC update.

On the same subject.. If the original Artwork is Square, then without top menu, it is re-scaled to fit correctly in a 400 x 400 area on the screen,

If the top menu is on, then it is still scaled to 400 x 400, and then when displayed in the 400 x 350 screen area, the TOP part of the image is CROPPED, which in many case hides content of that original image,

Could FCC detect if the Top menu is present, and rescale to 400 x 350 to display on the screen.

While this results in a slight aspect ratio distortion of the image, it is typically not that noticeable (unless directly compared next to the original), but will result in the better alternative of having ALL the original image content being displayed. (ie No lower image cropping)

​

Attached is an Historic Screen shot, from 2018, showing the top part of the artwork being CROPPED, when displaying on a screen with the top menu.

Not a real problem for this image, but is for some other images with important information at top of artwork.

FIXED sometime between Sept 2018 and Nov 2019 :)
[Android Head-Units] Salvo-x:
Hi speedfire

after the last beta update, I found problems with the left panel, the configuration is not maintained and the apps inserted in this panel are eliminated every radio restart
[Android Head-Units] mclaudio:
hello

in the non beta version, brightness control does not work on my unit, altough in carwebguru brithness control works.

what can i do?

thanks
[Android Head-Units] bossman4:
Speedfire

If and when you have time to expand the capability of FCC to additional radio units, I have gathered up some additional notes on the 9.1? Mediatek units

Here is a post under

https://xdaforums.com/android-auto/...ndroid-9-1-t3941261/post80799901#post80799901

I used Nova launcher to find the system apk for the Bluetooth. My head unit has Bluetooth music, phone calls, and contacts all in one. I will have to see what it was called. Once I found it in Nova launcher, I was able to locate it in carwebguru in order to add it to the home screen.

Edit: the name of the app was: com.ts.MainU
[Android Head-Units] AdekP:
[MENTION=1633144]speedfire[/MENTION]

In recent alpha versions, the automatic start of the radio application does not work when the main unit starts
[Android Head-Units] jun81:
Thanks.

Was not able to restore even after restart or clean install of the app.

Thats why posted for speedfire to see if there problem with the backup.
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] Running on the latest 3.314 alpha, I do still get the occasional restart. But it seems to be improved a little.

It's usually around wake when everything is sorting itself. I have a few things automated through tasker on wake and after some of the tasks, I have it set to go to home, and this is where I usually see the restarts. I sometimes have it happen when manually pressing home too. So I wonder if it has something to do with some of the home button optimizations you made some time ago, to have the home button respond faster... Which sometimes I do have quite the delay of the home button responding on wake still but sorts itself out after some time.

I think I was able to capture 2 -3 restarts in a row, on wake, in this single log.
[Android Head-Units] Scopesys:
I have no experience in reading these CatLogs, but you seem to get a lot less Errors and Warning than I do when I run in the Android Emulator.

( My head unit is not Rooted, so cannot get a log directly from my Head unit)

The one WARNING in your log that did jump out and get my attention were the multiple IllegalAccessExceptions

ie

11-09 12:30:40.738 16613 16613 W System.err: java.lang.IllegalAccessException: Cannot set public final static field java.lang.String com.joaomgcd.autotools.util.MediaState.MEDIASTATESTORED of class java.lang.Class<com.joaomgcd.autotools.util.MediaState>

Mainly because of the MEDIASTATESTORED

Ref: http://java-performance.info/updating-final-and-static-final-fields/
[Android Head-Units] rigattoni:
This seems to be an issue in Autotools from Tasker. AutoTools is not needed on the unit, you should delete it.

By the way...

11-09 12:34:03.242 398 9122 I hash_map_utils: key: 'av_channel' value: ' '
11-09 12:34:03.244 18988 18988 W Bundle : Key value expected String but value was a [I. The default value <null> was returned.
11-09 12:34:03.244 18988 18988 W Bundle : Attempt to cast generated internal exception:
11-09 12:34:03.244 18988 18988 W Bundle : java.lang.ClassCastException: int[] cannot be cast to java.lang.String
11-09 12:34:03.244 18988 18988 W Bundle :	at android.os.BaseBundle.getString(BaseBundle.java:1089)
11-09 12:34:03.244 18988 18988 W Bundle :	at android.content.Intent.getStringExtra(Intent.java:7081)
11-09 12:34:03.244 18988 18988 W Bundle :	at ru.speedfire.flycontrolcenter.FCC_Service$h0.onReceive(FCC_Service.java:30)
.
.
.

There are 40 null pointer exceptions in your log file....

398 9122 I hash_map_utils: key: 'av_channel' value: ' ' seems to throw an integer instead of a string.

This throws exceptions in Android and then in FCC.

I´m not sure where this comes from, but seems to be the route cause.

I never seen this issue on my units, running on OEM Android. May be there is a relation to the custom ROM from Malaysk???

Nevertheless, there are tons of other issues:

IMGSRV : clear.c:2632: alpha is NOT supported, to set it to 1, original value : 1.000000

This needs to get analyzed too.

Seems to be a streaming app, which streams video/pictures from internet.

First I would try to get rid of Malaysk...
[Android Head-Units] Scopesys:
[MENTION=2534110]rigattoni[/MENTION]

I am new to Android Studio, and tried running FCC in the studio emulator, Android 8.

It seems to acts in a similar was as my Eonon Head unit, which is not rooted, but still runs better on the Head Unit than the Emulator.. certainly not quite so many issues after a re-start of FCC,

The Emulator's Logcat is full of "E" & "W" many of which may be emulator related, and not necessarily FCC ?

So my question is, should I be able to use Android Studio to produce a CatLog from my unrooted Head unit, if I connect the Head Unit to the PC running Android Studio via USB (Or even better WiFi, as head Unit is permanently installed in the Car on my Home Wifi Network.

I am thinking if this is possible, I will get a better picture of what is actually happening wrt FCC and my Head unit, rather than running in the Studio Emulator.

or - Does my Head Unit still have to be rooted to do this ?

Also, is the Exception error I quotes something of concern ?
[Android Head-Units] rigattoni:
I don´t think you are able to run it on your head unit.

But if you have ADB installed, you could try to connect via WiFi to the unit and run the command ADB_TRACE on your PC after connection is established.

USB debugging needs to be activated on your device.

The mentioned exception of the AutoTools of Tasker should be a warning that there is something wrong. I suspect that most of the issues are related to Magisk... I could be wrong, but I found tons of similar issues on my PX5 units in the past with this ROM.

That was the reason I don´t use it anymore.
[Android Head-Units] Scopesys:
Thanks for the tip .. I'll continue to perceive with the emulator.

The Exception I quoted

Came off Android Studio, running Android 8. ( Not a unit with Magisk)

The main issue I experience with latest FCC, is the restoration of the Player Widget, and FCC knowing what was the currently selected Player that was running before the re-start or re-boot.

So an error associate with something called MEDIASTATESTORED appears to be possibly significant.

A few version ago, I believe it was discovered that some variables were attempting to be stored in a location that could not be written to .. that was fixed in multiple places, along with some memory leaks, and some SQL Database issues. ???

I was wondering if this MEDIASTATESTORED is another similar issue.

All I see are errors and warning, but I have no idea what the code is that is generating them - not my place to know -- I am just reporting what I see when I run FCC, and anything in the Emulator log that might be significant with what I see when running FCC .
[Android Head-Units] SpeedFire-:
Alpha 3.316:

- Camera zoom in/out re-done on all maps (some technical issues)

- Mapbox may work better. I hope no more crashes.

FCC Alpha 3.316
[Android Head-Units] huseyin102:
thx

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

Map can now switch correctly between 2D & 3D .. Thanks :)

I don't use Map much, but in recent versions, I have noticed Horizontal & Vertical lines on the map .. What are they ??

(They may have appeared after I got an API key ??? )

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

Still having problems with Player Widget after a re-start or Re-Boot.

Fresh install of 3.316 -- very simple almost default setup -- should be easy to reproduce.

Problems follow a repeatable pattern...

Linked Video shows exactly what is happening in good detail (Far easier to watch & listen to Video, than to read 2 pages of Bug description !!)

Hopefully this can be finally sorted out, and permanently fixed. :)

VIDEO

https://drive.google.com/file/d/1Bu3sMme6CWq5sD_as7wH94jW2Cf7TkR-/view?usp=sharing

CAN ANYONE ELSE SEE THIS / REPRODUCE THIS ?? YES / No ??

BTW: as mentioned in end of Video: Map 2D/3D, when I later went to test this, it seems to have been fixed in 3.316, and now switches correct, no longer STUCK in 3D :)
[Android Head-Units] whitewolf8111:
Thank you guys very much for checking out my log! (Lol that sounds funny!).

I did have Auto tools installed along with Tasker but Autotools is one of the Tasker plugins I'm not using so I deleted it and a few other plugins I don't use. I only use AutoInput and AutoNotification for Tasker plugins now. I do still get restarts on wake but everything does seem to run a little smoother now :good:

I'm not sure about the IMGSRV : clear.c:2632: alpha is NOT supported, to set it to 1, original value : 1.000000

I can't think of an app I have installed that is a streaming app that streams video/pictures from the internet... YouTube is the only app I have like that? I have Pandora, Spotify, Deezer, Amazon Music and Poweramp for my players installed and none of them stream video/pictures that I know of?

I kind of need to run Malaysk mainly for the built in MTC tools and remapping/customization of the steering wheel and head unit buttons. I was not able to accomplish such customization with the stand alone MTC tools. Plus it has a few other features that I really like. The ROM by itself runs super fast and smooth with the latest version.

I've been trying to automate my music playing with tasker... When I have normal 4G (or 3G) service, it will play whatever the last playing music was, but if it looses internet, like playing around in the mountains where no cell service is, it will continue playing the remaining buffered music and once the music stops playing, it will then automatically switch to my offline player (Poweramp in my case) and will continue playing from where it left off last time. Then once 4G (or 3G) service is restored again, it will automatically switch back over to whatever my last online player was and continue playing. I've tried to research on how to use Tasker quite a bit but it's a very complex program for the novice and I've got it working most of the time but I would be forever grateful if someone with some Tasker skills would be willing to help me clean up my profile and make it work a little better.

I would love to not use Tasker at all but it fills in some holes that FCC does not do... yet... hopefully ( [MENTION=4292729]SpeedFire-[/MENTION] ).

Along with autoplay music I described above, I use it for my screen dimming overlay app (CF.lumen) to kill it when going to sleep and start it when waking otherwise it doesn't work most of the time. I would love to see a screen dimming overlay to be added to FCC's auto brightness, and I could stop using that app and that Tasker profile.

I also use Tasker to remap my USB remote buttons. This one too, I would love to see integrated into FCC, then I could stop using Tasker.

My tasker profile:
[Android Head-Units] Tbizzness:
Hi

I'm using Xtrons TE103AP

Version 3.0 MCU

Android 8.0

Memory 4gb + 32gb

Loving the latest app from playstore.

Everything so far appears to be working fine that I've tried thus far.

Love being able to use voice to make a phone call.

Just need to find a way to get something to read text messages.

But when I try to backup or restore it won't log into my Google account.

Is this a known issue or is it just me.

Wanna upgrade to 9.0 and see if this is causing the issue. Just have to find upgrade software from 8.0 to 9.0 1st.
[Android Head-Units] SpeedFire-:
Thank you for the video. I reproduced the bug and it seems to be fixed now.

FCC Launcher Alpha 3.317:

- Fixed a bug with incorrect 4th player selection

- allowed Album Art maximum quality in Player Widget is increased from 320 to 400 pixels.
[Android Head-Units] okij:
Is there a chance that it also fixed the two known issues with DAB-Z?

DAB-Z running two or multiple times, leading to echo effects, respectively having DAB-Z still playing in the background when a different player is in focus

DAB-Z not resuming to play after restart from sleep or reboot

[MENTION=8476598]ab1702[/MENTION] and other users reported repeatedly about these issues, which don't occur in stock launchers and therefore must be a bug of DAB-Z.

I'm new to FCC Car Launcher since a couple of days and very much like it fearure-wise (already bought the full version), but I really would like to see these bugs fixed, since I live in Germany and mainly listen to DAB+ radio.

Currently I use an older version of FCC which doesn't have issue #1 and I configured DAB-Z to start playing when the DAB USB device is detected as a workaround for issue #2, but a real fix would be much better.

Also tagging [MENTION=7838245]realzoulou[/MENTION] for information. On your DAB-Z thread I read that you already know about these issues. Would it be possible that you and [MENTION=4292729]SpeedFire-[/MENTION] work more closely together to track down the reason for these bugs? :fingers-crossed:

IMHO FCC Car Launcher and DAB-Z are the best pieces of software for their purposes, so it's a pity that they don't perfectly work together yet. :)
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] is there anything we can do to help you fix bug #2 above? I haven’t seen bug number #1 recently.

Bug #2 is my biggest annoyance to be fair as fcc can never restart the dab-z app after sleep or a restart whereas I know it can for other players.

I have dab-z set to start automatically on usb detection but this isnt ideal as it means dab-z starts up and takes over every time even if I was using a different player before I turned the unit/car off.
[Android Head-Units] SpeedFire-:
I would be happy to fix those DAB-Z related bugs, but I don't have a DAB in my region.

I can purchase DAB receiving equipment, no problem, but will it help me to identify those bugs? Is there any option to broadcast DAB signal locally?
[Android Head-Units] Scopesys:
Equipment to Generate a DAB signals locally are extremely expensive.

http://www.redwoodcomm.com/product/01.php?cate_1=36

Maybe a user in an area with DAB, with a USB DAB Receiver, can use "USB-over-internet" to give SpeedFire- USB access to their USB DAB receiver.

http://www.usb-over-network.com/usb-over-network.html

Purchase price $150 to own, but has a

15 day free trail, and a 3 month License is available for just $32

I would gladly do this, but we do not have DAB here in the USA.

Maybe someone else can step up, if this is a workable solution.

---------- Post added at 04:43 ---------- Previous post was at 04:40 ----------

[MENTION=4292729]SpeedFire-[/MENTION] THANK YOU so much. 4:40 AM here, but I am going out to try this right now, even if it is a cold 36F out in the car !!!

---------- Post added at 04:44 ---------- Previous post was at 04:43 ----------

[MENTION=4292729]SpeedFire-[/MENTION] THANK YOU so much. 4:40 AM here, but I am going out to try this right now, even if it is a cold 36F out in the car !!!
[Android Head-Units] ab1702:
Do you really need to purchase the dab equipment to resolve the problem? personally I don’t know if you do or not as I don’t know anything about developing a launcher etc but if so I wouldn’t expect you to do that especially if you can’t even use dab in your area.

The problem is literally just that fcc doesn’t start the dab app after sleep or reboot if it was the last player used, there’s no problem that I see with fcc actually playing and opening dab at any other time and the artwork etc all works fine for me at all times.

Through fcc I have reassigned my Mode button on my steering wheel to switch between the players which in my case is dab-z and Apple Music and if I shut everything down on the unit and then use my mode button to open dab-z then fcc opens and plays dab-z in the background no problem.

It is literally just when coming out of sleep or a reboot that it doesn’t open the app in the background or foreground if it was the last player used, nothing happens.

I’m pretty sure though if you were to get a usb dab receiver and zoulou’s dab-z app from the play store then you would be able to recreate this problem even though you can’t use dab in your area. The app will open as long as the usb dab receiver is connected to the headunit. obviously though if it has no signal coming to it then it will just not play or receive any stations but the app will still be open and you can go through all the settings etc.

This is the receiver I have https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/133219446786