yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
If one is constantly editing widgets, sooner or later you will drag your widget to the DELETE instead of the EDIT .. and its all gone !!! (no Undo !)

Maybe for the DELETE, there should be a CONFIRM Popup ?

( and maybe configurable on/off for a Confirm Delete Popup) ?

Speedfire: I know you are working hard to get things stable, and I don't want to overload you with masses of suggestions for changes. I am spending a considerable (enormous) amount of time , configuring this Launcher (which is 100% a KEEPER), so most of my post are observation of issue I have experienced as a new user of the App - hopefully they help :)
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

What are the biggest issues at the moment ?

Is there something i can test?

Little confused what works what not
[Android Head-Units] Julian75ts:
For me the only issue is that i have to restart my

Joying Radio in order to make minimap working and updated!

Your Interface is very Powerful and i like It!

If you fix this problem i'll update to Pro?

​

QUOTE=Roerbakeitje;77381856][MENTION=1633144]speedfire[/MENTION]

What are the biggest issues at the moment ?

Is there something i can test?

Little confused what works what not[/QUOTE]
[Android Head-Units] sbruda:
Thank you for getting back to me. This morning I updated to 3.072 and went grocery shopping. The mini-map, etc. worked beautifully on my way to the store. I then turned the engine off, got back from the store, and turned the engine back on. From then on the same jerky updates started to happen again.

Here is the video; sorry for the crappy quality, I did not have any stand with me and the light did not help either (how do you capture the screen directly by the way?). The logcat will follow as soon as I find the time (might take awhile).

The video was shot while driving an almost complete square Saint-Louis to McManamy to LaRocque to Union to Saint-Louis again. In fact it starts just after the turn on McManamy (and ends a short time after turning back to Saint-Louis). The best example of the jerky update is on LaRocque from about 0:22 to 0:45 or so. During this time you can observe about 4 position updates on the map instead of a smooth position updating process.

As I said a logcat will follow as soon as I find the time. Thank you very much for looking into this.
[Android Head-Units] rigattoni:
I use https://play.google.com/store/apps/details?id=com.kimcy929.screenrecorder for recording screen videos and the original screenshot functionality in Android.
[Android Head-Units] Scopesys:
Ref: Ver 3.072

Updated from 3.071 to 3.072. Seemed to be stability issues, had to reboot numerous times.

Finally, I messed up and deleted a widget instead of editing it, so tried a restore.

Total Failure ( It was a restore from a 3.071 backup).

In any case, there were items on the Page that could not be edited, or moved, or selected, so I was forced to Uninstall. Clear cash. Re-boot, and then install 3.072 again, and proceed to set everything back up again.

The point is, will a "Clean Install", everything worked a lot better - no unexplained freezing, or things not working.. Mini-Map was nice and smooth as well (Smartphone as Hotspot).

Remaining issues I see.

(1) Right side panel 3 Items, do not pick up their App Icons, unless the default is set.

(2) Text Scrolling in Player widget is Hit/miss, mostly it jerks back to a refresh, but for a short while, it was scrolling nicely.

(3) Really wish there was a Pop-up CONFIRM delete when editing a page, and a widget/app is dragged to Trash instead of edit by a slipped finger !

Wish List:

(4) Please can you add "Amazon Music" to list of players when player lists are presented. ( Amazon is quite BIG here in USA, as well as elsewhere - Amazon Prime music is one of the best music subscriptions deals out there as well).

(5) MiniMap is great, but the restricted color selections are poor (IMHO)

Some selections allow the background to show through on certain colors ?)

Either custom selection of colors for Background, Road, text etc, or if that is too much, at least some better colored, better contrasting, colorful preset color schemes.

Personally, I would like to be able to fully configure the colors :)

(6) As others have mentioned, having a reliable Backup/restore of settings and configuration, would go a long way to making Beta testing less time consuming, and potentially more reflective of the currently installed version.

(There always seems to be issue with a non "Clean Install" of a later version)

MOST DEFIANTLY the most desirable function to be working correctly

All that being said, I LOVE "FCC".. best thing I have found for my Head Unit - almost all works as intended, and is getting better & better literally Every Day.

Tnks :)

---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------

Ref: Mini_Map

I assume, by default, we are running under the developer's Google map API key ?

Could this we a potential source of issues ?

Can we install our own "personal" developer key (Free for the small amount a typical user would call the API),

If so, what API's need to be included in the key to support all the required functions in the FCC's Mini_map and where do we need to put the key in FCC so that FCC uses it ?
[Android Head-Units] sbruda:
OK, sorry for the earlier, clumsy attempt. I have updated the video (shorter and more to the point; the new video shows a brief and straight trip along a single street) and the logcat is also available (is this what you need?). Note that my drive during the video was smooth; I started from a complete stop and then kept driving at a relatively constant speed.

Here are my observations:

1. The mini-map definitely works well from cold boot (a bit laggy but nothing to write home about), but not so much after a suspend and resume. The video illustrates the problem quite well. Note that the street name and current speed widgets have the same issue (as described earlier), but they are hidden beneath the map in my video; I am assuming that a deeper underlying issue causes all of these problems.

2. I discovered yet another issue with the latest version: long presses on the background used to bring the main menu on the left hand, just like pressing the menu soft key. Not anymore. The latest version apparently tries to do that, a small icon appears in the lower-right corner, but the main screen does not shrink and of course the menu items do not appear as they should. I only tried this after a suspend and resume, so things could work well after a cold boot.

My overall impression is that FCC does not shut down properly on suspend and some bits and pieces ramin active and mess things up after resuming. I am obviously not sure about this, but the symptoms do match with this scenario.

Thank you again for looking into this. Advice is much appreciated.
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

Ref: Animated Notifications

GREAT FEATURE -- now they are there I could not live without them !!

But -- Animated Notifications kill Touch-Screen UI while running.

When they are running, they Kill the Touch Screen UI of the HU, and occasionally when they are running and one attempts to do anything on the Touch-Screen, the unit crashes and re-boots.

Are you are running Notifications and their animation in the Main (UI) thread. ?

Maybe put it in its own thread, so it does not mess with and freeze the UI when it is running ?? (or whatever it takes to stop its animation from Killing the Touch-Screen UI)

Note: when a Notification is running, doing something like a Steering Wheel action, say Next song, works., and one can do multiple Next Song request, they are accepted while the previous notification is running, and it would seem that the Notifications are buffered nicely, and run one after another .. but all the time they are running, the Touch Screen UI is dead.

So, for example, if the Touch-Screen is used to select next song, or one is doing something on the Touch-Screen when a song ends, a new one starts, and there is a Notification, then the Touch-Screen effective then goes dead, till the Notification has run, and one has to patiently wait for it to finish, before anything else can be done via the Touch-Screen.

---

The only other Bug I get today, was when editing a Widget -- the edit process ended prematurely, and all the Text for Apps on the left side of the menu screen had changed their Font Size to about 4x their original value.

(Each one then needed to be edited to restore their correct text size).
[Android Head-Units] SpeedFire-:
Oh.. this looks really bad :(

Yes, I think you're right that the main issue with the device's sleeping period. Actually I have found that during power off the system tries to kill FCC Launcher and then starts it again (for unknown reason - maybe because this is the default launcher and it needs to start something). In 3.072 I tried to limit the processes it starts in the backgroud during sleep but it seems not to work well (if you are on 3.072).

Need to think what to do with this...
[Android Head-Units] tjaller:
Hi All,

I wondering what your preferred way of running FCC Car Launcher is.

Currently i run in on Malaysk 2.0 which is rooted, but i believe that i have seen somewhere that a root is not needed for FCC Car Launcher to function.

Will i loose some features if i go back to my stock rom and install FCC Car Launcher?

How do you run yours?

Thanks for sharing

/Tjaller
[Android Head-Units] SpeedFire-:
Hi!

No, you will not loose anything. None of FCC's features requires root. So you can go back to stock safely.
[Android Head-Units] Roerbakeitje:
I dont get It i did the same as on my device as on the video. No problem found all is good in minimap also after cold start . I Will make a video of It.

My device JY px5 3 gig ram running stock not rooted

I.m not a expert on this . But do you have a memory problem? Is It still the same at minimal system use.

I see on the video that tour system seems to be bussy . Look the widget that counts the sec

About loading a other launcher i dont Think so. Look at the system settings and look of It realy sets. Fcc as default launcher.
[Android Head-Units] sbruda:
I am on 3.072 and regret that. ;) Do you happen to have historical versions available, and if so where? I would like to downgrade to a version that works, though I don't remember which version worked for me so I would like to keep downgrading until I hit the spot.

That would be much appreciated. Thank you.
[Android Head-Units] SpeedFire-:
You can find some versions here in thi Google Drive folder: FCC betas

But probably you won't be able to downgrade without clean install (that's how android works).
[Android Head-Units] sbruda:
Good for you. :) That's one datum point though, I am sure it works for many other people (and who knows, maybe it fails for several more).

I am on a Klyde MTCD PX5 with 4 GB of RAM running Malaysk's latest Marshmallow. So my datum point is different from yours. ;)

The memory use was low at the time. The system load was also low. More significantly, the load was identical before and after suspending. I believe that one can safely rule out any kind of excessive load.

The system was not busy actually. I will try without the trip time widget, but I seriously doubt that this is going to make any difference: one interrupt/redraw per second is not high and again the widget was counting seconds before as well as after suspending. Under the hood I do run some other processes that might be questioned including but not necessarily limited to Xprivacy, mtce-utils, and other Xposed modules. However, (a) in my experience they to not impose an undue load on any reasonably modern system including this one, and (b) they were running before as well as after suspending. Also worth noting is that location (mini-map, street name, speedometer) is the only thing that is choppy on the whole system; all other apps and widgets (including Torque which also displays the current GPS speed between other things) are running smoothly.

This is all however pointless. In the absence of undue load (which is indeed the case here) FCC's location services should run smoothly no matter what other things happen on the head unit.

It is not that FCC is set as default, but also all the other launchers are actually frozen.

Thank you for your input. :) Unfortunately though I did try and ruled out any load-related issues.

---------- Post added at 12:29 PM ---------- Previous post was at 12:20 PM ----------

Great, thank you very much.

Understood. I was actually thinking of clearing the FCC data anyway and redo everything in the hope that a fresh setup will work better. I was also thinking of whitelisting FCC but I seem to recall that you said earlier that this is not a useful setup.

Since I am at it, here is a feature suggestion: can you provide an option to hide the search bar in the app drawer? I am not using it and it wastes valuable screen real estate in my application. Many thanks in advance!
[Android Head-Units] SpeedFire-:
Great suggestion!

Update: option is added (will be available starting from the next version)
[Android Head-Units] Julian75ts:
Hey Speedfire.. at what about my issues?

Thanks
[Android Head-Units] checksum123:
Great launcher, I love it.

Better than carwebguru, which I found to be good, but not very well tailored.

One question:

How do I add additional screen?

I have the paid version
[Android Head-Units] Roerbakeitje:
[MENTION=1633144]speedfire[/MENTION]

Splitscreen is not working

Also autostart player dont work.

Please look at it
[Android Head-Units] SpeedFire-:
Drag any item to the side of the screen - a new screen will appear
[Android Head-Units] SpeedFire-:
I think your issue is connected with the other major issues discussed here recently. I need some time to find the cause of them and fix them (this is not an easy task unfortunately).
[Android Head-Units] sbruda:
Oh, sorry for the noise, I discovered that the reason for this behaviour is that I locked the desktop (the small icon in the lower-right corner, I must have pressed it accidentally). The mini-map/location issue obviously still applies.

By the way, I will argue that parts of the menu (such as the app drawer button) still have meaning even with a locked screen (and they can be brought forth using the menu key, just not on a long press) so I will argue that even if the desktop is locked it would still be useful to bring the menu up on long press; for me this is a very handy feature while driving (no need to look away from the road, just long press somewhere in the screen).
[Android Head-Units] SpeedFire-:
Another very good point. Thank you! Will try to do it.
[Android Head-Units] alek_05:
Hello,

would be possible to implement the opportunity to add more widgets on the same spot/place and switching between them clicking on it (or its title)? And the current address as widget?

I have these widgets in my current launcher in Car Launcher Pro (on play store). I'm starting to try this launcher now, mostly because of its integration with the system (brightness, radio info, etc.).

Thank you.
[Android Head-Units] Scopesys:
Surely the That Screen Lock is an EDIT LOCK, not a function lock ??

The Function Lock is the "Password Lock" app that comes with FCC, to stop others "Service People / Valet Parking" from accessing and messing with your Head Unit.
[Android Head-Units] Scopesys:
After a few weeks of being a FCC beta tester, and on the "FCC beta Tester Roller Coaster Ride" I would make the following observations.

(1) FCC is one, if not, the best HU Launcher and has many unique features.

(2) Since there are no apparent log to Beta testers of what is changed in each beta release, each time a new beta version is loaded, its a crap shoot as to what we will find.

(3) I would ask that the developer gets existing issues documented and resolved with some visibility to Beta testers, before adding to the complications and adding additional features.

(4) The Mini_Map is cool, but it is only a minor Launcher, and there are many ready developed alternatives available. The Mini_Map obviously needs significant work just to get it's current features working, as well as needing some additional changes to it's appearance & functionality.

PLEASE, instead of dedicating so much time to this one "extra" feature, please will you address the issues with the main Launcher Functionality, and its existing "Launcher feature" , before adding more stuff (no matter how GOOD AN IDEA they are), and get the Basic Launcher Stable and working correctly.

I appreciate the dedication and the effort being put in by the Developer, but as an Aerospace Software developer myself, I would suggest that better Version Documentation and sharing that information with those spending considerable time helping Beta Test this App, would result in a far quicker resolution to bugs and issues in the APP and far less frustration to Beta Testers.
[Android Head-Units] oscyp:
Totally agree with you.

After a few days of testing I went back to AGAMA Launcher + MyMTCService xposed module as FCC Launcher was just irritating me in so many places.... Of course it has a great potential but functional and appearance issues were driving me mad. Agama on the other hand maybe doesn't have so much functions and is not being developed so hard, but... it is very nice looking, working stable and is nice to operate and nice to an eye. Maybe some day I'll try FCC again... but not now.
[Android Head-Units] rigattoni:
I went back from Beta testing to the stable version... you know why I think. :D

As a Problem Resolution Manager in automotive development I would like some sort of ticket handling process or anything which sets priorities in bug fixing and development and some sort of release notes...
[Android Head-Units] Scopesys:
Well, between you and me (Developer - close your eyes !!)

I took a peek at the code in the FCC, and there is a LOT, and it is very complex.. as would be expected, in such a powerful App.

Compared with something like a Player (ie PowerAmp), such other apps are trivial compared with FCC.

So, without very strict version control and documentation (at least at the Dev end), they is an increasing possibility of when fixing one thing, breaking many other things and getting hopeless lost as to what is working and what is not.

( I am not aware of any Automated Test Programs, to test Android apps, especially any as user interface intensive as FCC .. so the task is left to the Human frailties of the Dev & beta Testers)

Add to that, the need to sometimes completely re-design major parts of the internal coding of the app, to fix an issue, or allow an additional function to be added , and the "fix one - break many" is to be expected.

Multi threaded apps are inherently more complex that apps that run everything in the main UI thread,

On top of all that, I seem to recall the Dev saying this was more of a Hobby Project - not his main "JOB", and I therefore find it amazing that he has managed to develop something so complex, and is willing to put so much additional time and effort into it, in excess of all the time already spent.

( I speak from a similar development experience)

So "well done" -- we are so fortunate that developer has created FCC, and I for one, am more than happy to have spent so much time testing and reporting on the App.. (20+ hours so far in about 3 weeks, which is bordering on OBSESSION)

That's fine, I want to help the APP be all it can be, and have no intention of abandoning it for any of the alternative Launchers, none of which are as configurable, well designed, AND SO WELL SUPPORTED.

I am not criticizing anything.. just trying to make constructive suggestions for the good of everyone that are supporting FCC

---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------

+1 :good:
[Android Head-Units] SpeedFire-:
Thank you :)

You're right this is entirely my hobby. I would add that I am not actually a programmer (at least I was not). This app wad my first ever program in Java and the first large app in my life (my programming experience was limited by writing macros in VBA for Excel and Word for my core financial work). So you guys are very unlucky to have such an unexperienced developer. I definitely make more mistakes than some experienced developer would do.

This app was kind of an attempt to make the best launcher for me (as I was unable to find one ready on the market at that time) and to implement all (most) features useful for you (your suggestions are always very clever and sometimes totally unexpected therefore very useful).

Currently we are in the stage of refactoring the app. Fighting memory leaks. Working with multithreading. Trying to find inefficiencies. I personally don't like this stage. It is boring and stressful because of new bus. I hope it will end some time soon :)
[Android Head-Units] Julian75ts:
Great Job Speedfire!

You are on the right way

I personally think that minimap is a great feature

No other Launchers has this type of integration of a useful map like Fcc launcher
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

You got PM...
[Android Head-Units] SpeedFire-:
New version (3.075) is uploaded in Release channel (I had to upload it to release channel because Google once again deleted the app becuase of one of unnecessary permission which was still mentioned in Manifest - already fixed). Other changes:

- Improvements in Street names and Speedlimits updates -> better updates with less data requests.

Some more details on this:

Restored a work of internal geocoder (which should provide offline street names). Street names data should always be actual now (I hope).

Now when the speedlimit data is received the app also records a rectangular related to this speedlimit. While the car is within the bounds of this zone no further requests are made (this will save mobile data as well).

More speedlimits should be recognized now, because we understand responses from OSM not only with exact speed (like "60 kph") but also a popular "keywords" like "RU:urban" which means 60 as well in Russia (https://wiki.openstreetmap.org/wiki/Key:source:maxspeed). Such keywords are widely used in OSM, therefore I expect more speed limits data to be recognized.

- Ability to hide search bar in All Apps

- Deleted unnecessary permissions requirements

Download: 3.075
[Android Head-Units] Scopesys:
(1) While you are still working on the Map :-

Will FCC support a private user API Key for the Google Map API(s)

If so, what API's are needed to support the functions used in FFC ?

(ie which APIs do we have to include in our private key)

Where does one put our Google issued Key in FCC ?

(2) Please do not forget to look at the issue with your animated Notifications locking out the UI while they are running :)

Thks
[Android Head-Units] SpeedFire-:
1) there is no need for a private key. Everything I use in my minimap has unlimited number of requests. So don't worry. My developer's key will cover everything.

2) ok I'll try. You said earlier about crash. Can you record a LogCat log of this crash?
[Android Head-Units] SpeedFire-:
For me it blocks only a small area around notification itself. Other parts of screen work fine.

Btw, notifications are dismissable. You just need to swipe it to the side to cancel / hide.
[Android Head-Units] SpeedFire-:
This needs a consequence of steps to reproduce the issue.

All, please report how 3.075 works for you. It is optimized further so maybe it will work better.
[Android Head-Units] SpeedFire-:
I also forgot to mention. It turns out that starting from the newer PX5 devices manufacturers changed a service protocol (used by native apps and FCC Launcher for deep integration). This results, for example, in non-properly working next / previous button in player widget while controlling A2DP or not being able to call via BT.

This new protocol is supported now in the latest release. You can switch to it in Settings -> Call via BT -> Rockchip service protocol -> choose v5.