yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Roerbakeitje:
Don't know if it's possible to make a new widget with the streetname where you drive at the moment?
[Android Head-Units] SpeedFire-:
Wow. That is interesting. I will try to do this.
[Android Head-Units] SpeedFire-:
OK. After some development work here is a new beta:

- Added vertical multi-finger gestures! (2 and 3 finger up and down swipes)

- By default: volume control with 2-finger up and down swipes with indication.

- Aaand ... one little surprise! Let me know how you like it :)
[Android Head-Units] Roerbakeitje:
I like suprise . Now going to download

I tested the beta . And the two fingers swipe and I whas swiping from top to bottom and now

My ? is hurting. Lol it's working . The 3 finger . mute is working to. The suprise not found jet. But I whas oly testing for 2 minutes
[Android Head-Units] SpeedFire-:
Check this little icon in the bottom right corner ;)
[Android Head-Units] Roerbakeitje:
Nice!!!! Suprise!!!

I test the volume swipe. Better now I have a MTCB rk3066 and seems that it have a issue. Two fingers swipe up or down give me mute sound. 3 finger give me nothing. My idea is better have a floating side button that disappear after 5 sec with a + - mute button. With a simple floating on off in settings.

The suprise :good: maby moveble and resizeble?

Google work !!!!
[Android Head-Units] Roerbakeitje:
Check... Works on the last beta. Did also a quick random on my mtcb . Also no problems so far.

150 beta.s that's alot lol .
[Android Head-Units] VMPhil:
ive read through about 30 pages and the Play store page and (going through 72 pages of posts is a lot even with searching specific terms) I dont see a mention of the issue I am having. I loaded this Launcher on my Android head unit (Panlelo) and in the widgets screen, I am not seeing the FCC Launcher widgets as an option to choose. Just the basic Android ones. Any thoughts?

Thanks!
[Android Head-Units] Roerbakeitje:
Can you make a screenshot from your about device? Maybe that it helps.

---------- Post added at 07:58 PM ---------- Previous post was at 07:15 PM ----------

Also [MENTION=1633144]speedfire[/MENTION] the bug fix on android 7.1.2 almost fixed. Only also I can't set widgets on home. Sorry.

Maybe this is related to the problem above.

Issue description: when pickup a widget and placed in home screen screen goes back to widget screen. (No widget placed) it only appears to be infect the FCC widgets . Stock widgets works.

Hope to be helpful.
[Android Head-Units] VMPhil:
[IMG="Screen in car"]http://tinypic.com/r/332z39c/9[/IMG]

http://tinypic.com/r/332z39c/9

---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------

in the widgets screen, it's not even an option. I am running android 6.0
[Android Head-Units] SpeedFire-:
FCC's widgets should be in the top (first) row. Please check.
[Android Head-Units] VMPhil:
It's not there, however, I installed it on my phone and the widget row is there and i noticed before I got there i got a notification to allow FCC launcher to create widgets. I don't remember that on my stereo. I will uninstall and re-install see if the popup shows up.
[Android Head-Units] VMPhil:
Scratch that. it did not work. seems to be a function of my custom Android implementation. being that it is different even from the joying or Pumpkin interactions of android. The Launcher works it is just the widget portion that is not showing. I wonder why. It is a shame, this is exactly what I was looking for in a Launcher. Only thing I can think of is if there was perhaps a separate add-on or extension for the widgets like you did with the car controls or auto resume on sleep extensions.
[Android Head-Units] SpeedFire-:
Can you please write a LogCat log of launcher restart (push FCC Restart icon) and then opening the widgets menu? Would be better with video.
[Android Head-Units] VMPhil:
ill try. trying to transfer a log file from my radio is pain but not impossible. I can email you a video. which email address would you prefer?

*edit* i need root for the verbose log cat. my device is not rooted.
[Android Head-Units] pa.ko:
[MENTION=4292729]SpeedFire-[/MENTION]

Noticed that player widget is not showing FM Radio is playing on boot. Radio plays but widget is showing nothing (no station name, no radio icon, no play/pause button is greyed).. After any interaction like pressing next/previous station on Steering Wheel, widget gets synchronized. Looks like initial synch of widget with auto start app on boot is not working properly.

Is not a big issue, but plz look at it.

Thanks for great work! I really enjoy seeing it gets its well deserved popularity.
[Android Head-Units] Petrovych:
Did you enable option force update widgets on boot?
[Android Head-Units] HarryBk:
Every time I read that thread I am amazed. Great work [MENTION=4292729]SpeedFire-[/MENTION], as mentioned again by far the best money I have ever spent in an app.
[Android Head-Units] SpeedFire-:
OK, guys, here is a one more beta:

- Auto-disable of screen by timeout or by custom action (backlight is completely off until you touch the screen).

- 2 new skins

- Ability to apply custom colors to custom skins

- Integrated 1 new player: RadioNet https://play.google.com/store/apps/details?id=com.slaler.radionet

- Various fixes (OBD2, track progress bar etc.).

New skins:

1) Slightly updated initial skin with gradient circle:

2) New skin:
[Android Head-Units] smithkt:
I like the new skins. What resolution are they designed for? I notice on my head unit that the circles are not round, I probably have a different aspect ratio.
[Android Head-Units] Petrovych:
1024*600

Отправлено с моего SM-G950U1 через Tapatalk
[Android Head-Units] smithkt:
I see what's happening. My head unit has both a notification bar and soft buttons along the bottom which means my screen is not 600 high. I'll have to figure out what the actual height is and make a custom skin.
[Android Head-Units] SpeedFire-:
Yes. These skins are designed for a case with all panels hidden
[Android Head-Units] Roerbakeitje:
I personally think it's time for a release of FCC. And start building on version 3. We are so so far from the version in the playstore that that version looks a bit odd now. And it will be atract new people.

Very nice work Speedfire and thank you for the effort and fun you put into it.
[Android Head-Units] VMPhil:
The more and more I think about this, the issue may be inherent to my device as incompatible with this launcher. Sucks but oh well. I did take a video but its like 100MB and most email clients will reject that. I took a chance and rooted my device to no avail. The next step may be trying to grab the log.....

no matter how this turns out though I will say, I have not seen a more responsive Dev around these parts. Excellent work on dealing with all the feed back. :good:
[Android Head-Units] SpeedFire-:
1. You can upload your video to youtube with private access and send me a link via DM.

2. If you have rooted your device please write a log (see the first post in this topic, it is important to select the most deep level of details - Verbose).

3. Please also try to install some other third party launcher with widgets support, such as Nova or Apex and try to find FCC widgets there.

4. Please try to install some other app from the Play Market with widget (such as weather app etc). We need to understand if the problem is with all third party apps' widgets or with FCC's only.
[Android Head-Units] whitewolf8111:
@SpeedFire- I can confirm this too. It's kind of random when it happens, but mostly when changing between players. Also sometimes the alternative image for album art will sometimes still be the 2 circles instead of the BMW logo I selected. Or sometimes it should be the album art, but shows my BMW logo, or the 2 circles. Very random.

@kill_one Are you talking about replacing the default image when album art isn't displayed? This was just added in the last test version.
[Android Head-Units] kill_one:
yes, I did not know it was just added, however I would like if it was obviously possible to view an animated gif like a disc that runs for example, it would be very cool: D
[Android Head-Units] shzlmnzl:
Hi there. at the moment my JOYING JY-UQS05N4G-H-EU has a little problem with FCC and/or the default JOYING launcher3.

I've set the FCC as the standard launcher and sometimes it switchs to the joying standard launcher3.

Curious, after the joying unit wake up, FCC is starting and working few seconds, and the switching to the joying standard launcher3...

Several settings tried on joying and FCC.

FCC version at the moment 3.442

joying firmware the newest.

the problem existed already before firmware update to last one.

is this an know bug from FCC ?
[Android Head-Units] okij:
@SpeedFire- I want to report that this morning FCC became unresponsive again after waking the head unit, so I had to force close and restart it. :(

Since I reported this three times already, including Logcats and further details (please see posts #7,938, #7,969 and #7,975), I don't see a point in posting further Logcats. But please tell me if you need further logs.

However, this issue is occuring about two times per week and is really annoying, so I hope that you can soon fix it.

Honestly I'm quite disappointed that you didn't reply yet to my last two reports (#7,969 and #7,975) where I tried as good as I can to give you details and point to some parts of the Logcat.
[Android Head-Units] SpeedFire-:
Hi!

I saw these posts. Thank you!

However I currently don't have much time to work on the Launcher. Moreover, I want to finally rewrite Weather widget first (which is difficult because it changes its data on click).

Then I will get back to these reports.

Thanks again
[Android Head-Units] okij:
@SpeedFire- Thanks for your prompt reply! :)

I understand that you currently don't have much time for FCC and that you want to rewrite the Weather widget, but please tell me if you already saw something in my reports and logs that helps you to fix the FCC freezing issue, or if I should continue to post logs about it.
[Android Head-Units] HatManSan:
@SpeedFire- does you FCC app support 1280x480 natively? When starting your app from scratch some of the text is off the screen. t69 for me is working normally. Thank you
[Android Head-Units] SpeedFire-:
I saw ANR errors in your reports. I also saw similar errors in my tests. However, LogCat reports seems to show only consequences of the real issue (that some service wasn't loaded properly) and do not help much to identify it. Currently there is no need for additional LogCat reports. More important is to identify some similarities among situations with ANR (what is the same in all these cases).
[Android Head-Units] okij:
The only similarity which I noticed and already reported is that the freezes always occur after FCC has been woken from standby.

Couldn't you implement some extra debugging output that is captured in the logs to identify the cause of the ANR errors, e.g. which service isn't loaded properly?
[Android Head-Units] Kewz4:
Hey, i really like the idea of this launcher, however may i ask if the call feature works on MTK Devices? If so, do I need to pay for the app to get this feature?

So far I've done everything in the guide but when setting fcc launcher as the dialer app it just sends me back to the launcher home screen and doesnt make the call.

Thanks in advance, looking forward to buying the premium version 👀.
[Android Head-Units] okij:
Maybe the Minimap is causing or contributing to the ANR errors:

On my first drive today, the minimap didn't update, although it reacted to touching and swiping it. Of course I checked if GPS reception is OK, which was the case (e.g. Google Maps worked without problems when started separately). After the drive, I took the first attached Logcat.

On my second drive today, FCC reacted extremely sluggish after waking the head unit (although surprisingly the minimap worked again) and after a while totally froze, so I had to force close it. After this I took the 2nd attached Logcat.

I hope that you can get some more insights by this to fix the FCC freezing bug. 🤞

BTW, after I had this bug three days ago, I chose the split-screen version when being prompted, in hope that this might prevent this bug. However, the bug occurs regardless of the split-screen preference.
[Android Head-Units] mariodantas:
I can add a behaviour (bug I guess) that I observed yesterday

minimap, usings Google Maps, when I click the "Nord always UP" the setting does not remain, I mean when I restart FCC the "Nord" is no more pointed to UP
[Android Head-Units] mclellan83:
I also have had issues with it, my main issue is on a slightly customized version of this it won't let me use any of the buttons while playing Spotify on the standard bluetooth player? I have tried it with each of the 3 screens I have on that setup and none of them control it, honestly while I have had the app for a long time I haven't been running constantly for very long. So may totally be a noob issue that I am not understanding

View attachment 5422979
[Android Head-Units] SpeedFire-:
Here is a rewritten Weather widget (finally) as a separate widget: fcclauncher-3.442_test70.apk
[Android Head-Units] HatManSan:
@SpeedFire- Having just decided to make my on transport buttons for the player widget, I have noticed that when a song is pause, I need to press Play twice before the icon changes. First press restarts the song but another press is required to change the icon.
[Android Head-Units] wifi7501:
Hello @SpeedFire- this problem it is solved?
[Android Head-Units] mclellan83:
Dunno if anyone else has run into this but having trouble with a few things all at once, for some reason the navi was showing beside the road even though I was on it within the skin. But if I opened up Maps then it showed just fine like in one of the lower pictures. At other times it wasn't showing the map at all, even though I have downloaded an offline version so that it can show while I am driving around without wifi or phone. Anyone else have this? Also, still having trouble with the audio players on the home screen skin changing anything

View attachment 5425445

View attachment 5425447View attachment 5425449

View attachment 5425451
[Android Head-Units] kill_one:
@SpeedFire- since I updated to test 69 and even 70 I can no longer add a new player widget, once inserted it is invisible, it also does it with other widgets but when fcc is restarted then they become visible, instead the player widget any style I choose but in particular only round poster is always invisible if I press the resize box comes out and if I hold down the widget settings but it is impossible to show it.
[Android Head-Units] kill_one:
another problem encountered is with the bluetooth widget, in practice it initially works well indicates connected and what it is connected to, then at each resumption of standby by turning the machine back on, it is either gray (disabled) or blue with written enabled or the connection icon without text, bluetooth is connected
[Android Head-Units] okij:
Just to let you know, I tried test67 version for some days to check if the freezing (ANR) bug maybe does not occur there, but this morning I had this bug with test67 too. I will not try even older versions, since they have some drawbacks in everyday use for me.

Thanks a lot! I just installed it and set up the new Weather widget, which has some more configuration options. (y)

Now that you finished the new Weather widget, I hope that you can soon fix the ANR bug, which is quite a show stopper at the moment. Please let me know if I can help you with testing.
[Android Head-Units] SpeedFire-:
Weather widget is finalised and old widget is replaced with the new one: fcclauncher-3.442_test71.apk

Let's try. As I said, ANR is a hard thing to identify.

Can you please check your folder /data/anr/ and upload all reports from this folder?
[Android Head-Units] okij:
Thanks a lot, I really like the new customization options. :)

OK, here we go.

There were two ANR reports in the folder, both of the most recent FCC Launcher freezes from two days ago. I zipped and attached the reports for you.

I hope that they help you to find and fix the cause of the ANRs.🤞

Please keep us updated about how it's going on.
[Android Head-Units] SpeedFire-:
Thanks for the report. Now I think that LogCat reports would be more useful. Please try to record a couple LogCat logs with ANR error on this version: fcclauncher-3.442_test72.apk
[Android Head-Units] okij:
Thanks, I will do so. I'm not sure if I can catch an ANR error in the next couple of days because I'm on holidays for the next week and so I'll have to drive less in my car. But I'll try to start the head unit for some extra times even when I don't have to drive, maybe I'm lucky.

Does test72 contain some extra logging? I'm asking because I already posted LogCats several times when the ANR happened.
[Android Head-Units] tonimontoia:
@speedfire with the latest update the player button no longer works to pause and crash the same
[Android Head-Units] okij:
I can't confirm this, the Player widget buttons work fine here on latest build.

Please record a video and a LogCat for @SpeedFire- to have a look at.

Btw, you wrongly tagged him, @speedfire is a different xda user.
[Android Head-Units] tonimontoia:
Log_2021-10-10_11-08-09

drive.google.com
[Android Head-Units] kill_one:
I would also like to contribute to solve the bugs affecting my unit, to create the log the stereo necessarily needs the root? my px5 Android 10 has this specs:

Build: k3368-userdebug 10 QQ2A_200305.004.A1 eng.hct2.20201019.121348 test-keys

Kernel: 4.19.111+ # 2436

MCU: MTCE_LM2_V3.67d_1

Can I root it? If so, which working guide can I follow?

Thanks
[Android Head-Units] okij:
Now using test 72 I just caught ANR errors again, sooner than expected. :)

I attached the according LogCat for you, as well as the three files from /data/anr/. It's three of them because only on the third prompt "application not responding" I restartet FCC Launcher.

I hope that this now helps you to fix this issue.

Also I would like to ask you again if test72 contains some extra logging?

Please tell me if you need further assistance.
[Android Head-Units] SpeedFire-:
No, it doesn't contain any extra logging because I still have no good guess about the cause of ANR.

This could be unfinished launch of internal services (like the one that gathers players data NotificationsListener or the one that shows pop-up notification AchievementService).

I saw in your previous logs some log inputs from Tasker. Looked like Tasker tried to cancel some Fcc Notifications. But I'm not sure. Therefore I asked for more logs.

You can try to disable Tasker for a couple days to check this.
[Android Head-Units] okij:
I only use one Tasker project on my head unit, please see attachment. It automatically switches the BT connection to my private and my work phone depending on the week day and time, so I don't have to worry about having my private phone connected when I'm driving for my job.

It does not cancel FCC notifications or any other notifications, please have a look at my Tasker project.

The only direct connection it has to FCC Launcher is that it listens to ru.speedfire.flycontrolcenter.BT_ACTION to manually switch the BT connection between my two phones when I press the FCC BT widget.

You are correct that in some - but not all! - of my logs there are some inputs from Tasker too. But IMHO the culprit is FCC and not Tasker, because the FCC ANR issues started with one of the test versions of the reworked FCC Launcher and I had no problems before with those two apps working side by side.

I wrote an email to João Dias, the developer of Tasker, because sometimes Tasker crashes when FCC freezes, and he answered me: "Hmmm, judging by that logcat it seems that tasker was killed when another app attempted to send it a broadcast... Can that be it?"

So this might be related to the broadcast intent ru.speedfire.flycontrolcenter.BT_ACTION. Did you maybe change anything about the code when rewriting your BT widget, so this better should be reverted?

AFAIK João does not have a user account at XDA, but if you want to contact him to talk from dev to dev, you can do so via email to support (at) joaoapps.com. It usually takes some days before he answers. Anyway, I will mail him the link to my post here so he can take notice about our conversation in your thread.

Good luck and please tell me if I can be of further assistance. :)
[Android Head-Units] SpeedFire-:
I agree. Tasker is probably has nothing with this issue.

Here is a new version - fcclauncher-3.442_test74.apk

- Removed some parts related to old Bluetooth and WiFi widgets (could have possibly caused ANR).

- Wi-Fi enable/disable action is now a panel on Android Q+

- Icon widget text is automatically truncated if not fits (for left aligned text)

- PlayerInfo widget - quick player button is hidden if quick player is not set.
[Android Head-Units] okij:
Thanks a lot, this sounds promising!

Unfortunately it seems that you have removed some part of the code which is still needed, because the BT state (connected to device xy / not connected) isn't updated anymore.

This also doesn't seem to work anymore for the Wifi state, although I'm usually not using the Wifi part of the BT/Wifi widget.

Please have a look after this. Thanks.
[Android Head-Units] SpeedFire-:
Combined BT/WiFi widget will not work and will be probably removed.

You need to put separate BT and WiFi widgets (both are rewritten).
[Android Head-Units] okij:
I would like to do so, but I just tried the separate new BT widget and noticed the following issues:

An option to send ru.speedfire.flycontrolcenter.BT_ACTION when the BT widget is pressed is missing so far. I need this option to switch my phones via my Tasker profile.

Also opening the Bluetooth app (when this option is selected in the widget settings) doesn't work (at least on MTCE device).

Resizing of the BT icon doesn't work, it always stays at the same (big) size. Btw, this also applies to the new Wifi widget.
[Android Head-Units] tonimontoia:
always crashing, I have decoupled the separate Bluetooth and Wi-Fi widgets but nothing changes, useless to post the log file so much it does not read it and so on

View attachment 5432825
[Android Head-Units] SpeedFire-:
Hi,

Please check this version. All of the issues mentioned by you should be fixed: fcclauncher-3.442_test75.apk
[Android Head-Units] bhudcser:
Hi, I'm new guy in the FCC Launcher world, so I have some general questions:

* Is that possible to control brightness with this launcher? My radio is ff-5000 8227L and this function doesn't work.

* Is there any way to control FM Radio with the mini music player widget? I'm able to select some kind of "FM Radio" but it's doesn't work at all.
[Android Head-Units] okij:
Thanks a lot! :)

I just checked it and found only one small remaining issue: When having selected "Open Bluetooth app" as action in the BT widget, it actually sends ru.speedfire.flycontrolcenter.BT_ACTION instead. In the old widget I had to select "-" to have ru.speedfire.flycontrolcenter.BT_ACTION sent.

Could you please add a separate list entry in the BT widget to send ru.speedfire.flycontrolcenter.BT_ACTION (e.g. "Send BT_ACTION intent")?

Also IMHO there does not have to be a separate list entry "Open Bluetooth app", because for this we can just select "Bluetooth" in the apps section of the list, or wouldn't this be the same?
[Android Head-Units] SpeedFire-:
I don't really want to add a separate option. Please tell me in which case do you need this BT_ACTION intent?
[Android Head-Units] SpeedFire-:
Have you selected MTK integration? If yes and it still doesn't work then your device is not supported.