yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
+1 :good:

---------- Post added at 06:43 PM ---------- Previous post was at 06:20 PM ----------

[MENTION=1633144]speedfire[/MENTION]

Thank you .. logo issue corrected, but there is still something not quite right.

After viewing a Frequency setting, and hitting save.. BACK takes you back to the list of Frequencies. (as expected)

But then, a 2nd back at this point does NOTHING .. it does not take you back to the menu settings menu... nothing changes.

It then requires another EXTRA Back to get you back to the main menu.

Not a problem in itself, but a symptom of something being wrong, in that it requires an EXTRA BACK to get back to the main settings menu.

Since you may be back in this code again, can I push my luck and make an addition suggestion.

Could the List of Radio Frequencies also show the stations artwork (so it is clear which ones have artwork, and which do not)

Artworks do not have to be that big, (ie fit in the same vertical layout space that the list displays at currently) - they are just there to show which frequencies have artwork, and which do not.

Also, when adding a Frequency, the initial Frequency seems to start at the lowest frequency.

For many counties, that requires a lot of scrolling to get up into the Frequency band that that country may use.

I do not know how possible it might be for FCC to get the systems Lowest Frequency value for the Country's Band, but the next best thing would be for FCC to scan the current list of FCC defined radio Frequencies, and initialize that starting Initial Frequency to 0.10 Mhz below the Lowest FM frequency already allocated frequency.

ie In the Band but not on an already allocated frequency.
[Android Head-Units] yuvalmesika:
, חחח

.

.
[Android Head-Units] TT_Vert:
Has anyone ever gotten the backup/restore to work? I'd be more apt to change things around and do more testing if this actually worked. Every time I restore not one thing works and I have to redo it again. This is across 5 devices backup/restore will not work.

Dave
[Android Head-Units] Petrovych:
Unfortunately no

Отправлено с моего SM-G950U1 через Tapatalk
[Android Head-Units] Scopesys:
I did a backup & restore a few days ago .. Did not seem to change anything. (same device)

I'll try again, but this time I'll change something after the backup, and make sure FCC gets restored to the same as before I made those changes.

Over the past few months, I have made a lot of changes to my FCC layout. I have also been updating with the latest betas.

More recently, I have noticed that when FCC loads, it partially draws the Home Page, almost to completion, except for any artwork, , and then refreshes, re-drawing the screen again (one item at a time), I am wondering if this is caused by past modifications. ?

Ideally, I should backup, uninstall FCC completely, and then reload it, and try a simple Home screen, before doing a full restore.
[Android Head-Units] TT_Vert:
Yeah I've also got that issue but I thought it was by Design. This is on a brand new install as well so it's definitely not your setup. Another thing I noticed is that sometimes Pandora will open twice when it boots it'll open go away and then reopen a second later

---------- Post added at 10:51 AM ---------- Previous post was at 10:49 AM ----------

Yeah I've also got that issue but I thought it was by Design. This is on a brand new install as well so it's definitely not your setup. Another thing I noticed is that sometimes Pandora will open twice when it boots it'll open go away and then reopen a second later. I have not mentioned these little quirks as they are very minor but they are there.
[Android Head-Units] Scopesys:
Interesting .. thanks .. so that saves me from potentially messing up my current configuration... would take some considerable time to re-do it.

Most "Little quirks" are not an issue to the user running the app, but they are probably symptoms of something that is not running correctly, and may be of great significance and helpful to the developer. (I know I would find them informative if I was developing a software app).

Pandora opening twice would seem to be one of these quirks.

Not wanting to speak out of turn, but do you have Pandora set to autoload in FCC, and is Pandora one of the apps that are selected in your Quick Player selection.

If it was in AutoLoad, and was the last Player you ran before restarting your Unit, I could imagine that could be one cause of it re-loading a second time.

I am relatively new to Android OS, but one thing I have experienced & read, is that once an app loads, it does not necessary get unloaded if you are not using it. The OS will unload non-used apps, as it does it's own memory management.

So, (I think ?) this means, that of when you turn off your car, your Android Unit "goes to sleep", the apps remain in memory, and are therefore already loaded when the unit wakes up. Hence the "Quick BOOT" from sleep.

I periodically run APPKILLER, especially when FCC seems to be having issues.

This often temporarily "fixes" current quirks. It is amazing how many apps are still installed in the head Unit's memory, even though I have not used them in days. These apps do not show up as being loaded if you look for "running apps" , but are still there, lurking in Ram, and ready to re-start again, without the long LOAD time from Rom (Drive).
[Android Head-Units] TT_Vert:
Nothing is auto loading. I also have not checked the option to close all apps during sleep. However this seems to occur either out of sleep or full power down. I am doing bench testing right now so I have the ability to power down completely or just emulate an ignition off situation (sleep). Depending on your rom there is a speed icon in top pull down menu that should kill apps also.

Dave
[Android Head-Units] michalpro:
Cannot seem to resize some widgets- i.e. PowerAmp playlist widget
[Android Head-Units] Scopesys:
Yes, I have a Speed (rocket) icon, but it does not seem to clear out as much as APPKILLER...

ie I run the speed icon, it says it has release some memory, but APPKILLER then can go and remove a lot of Apps that would appear to still be loaded.
[Android Head-Units] TT_Vert:
Maybe I'll try that. Have you looked to see if processes were actually still running that appeared to be still be running?

Dave
[Android Head-Units] Scopesys:
Not sure .. I'm new to Android OS. It's very different to Windows :)

I think the processes are not running, but the program is still in memory.

This does not seem to match the practical effect, that if they are indeed stopped, why should removing the programs from memory restore FCC's correct operation.

A lot going on I do not understand.

I am putting my faith in SpeedFire to sort it out .. it's his "baby" -- and I am confident that as he has got this far with this Launcher, he will be able to resolve any remaining bugs.

I'll do my part and report any aspects of FCC that I find that do not seem to be working as expected.

Come too far now -- I know there is not another Launcher that I would want to use, after experiencing FCC.
[Android Head-Units] SpeedFire-:
3.116 beta is uploaded:

- FM stations logos are now visible in the list itself

- Buttons added to seekbars in IconWidget and PlayerWidget settings for more precise change.

- Fixed bug with volume widget not being able to change volume when it equals 0.
[Android Head-Units] Scopesys:
ABSOLUTELY FANTASTIC :)

Radio station artwork shows great, and the new buttons for delete/save etc are a great idea. Much slicker.

Also, great job in getting the ADD new station, to initially have a frequency in the correct band :)

Gets better & better every day .. or should I say night .. looks like Speedfire was burning the midnight oil for this one :)

-----

Played a bit more with the Player Widget and discovered some potentially useful symptoms.

If the Widget is initially working correctly, one way to make it fail is to quickly select repeated next songs.

After a time, that stops working.. the right arrow may even stay in the same color, (either pressed or non-pressed color) despite being pressed,BUT the next song is still selectable by the widget .. ie the Widget's image update has locked up ?

Also, I noticed, even when it is working, the the Forwards and Backwards arrows , when pressed, change color "short time", but the Pause/Play does not change color, it just stays white and changes.

Maybe by design ?..

I would have expected the Pause/play to have changed color for a short time, and then switched to the other Icon in white. Not a big deal.

What may be more important, is that when the Widget stops updating the artwork, artist & album, the Widget's forward and backwards Buttons then also stop indicating being pressed.
[Android Head-Units] Scopesys:
Played a bit more with the Player Widget tonight :-

Turns out the Player Widget is still controlling the Player, ie it can pause it, and make play the next song, but the the Widget itself does not Update it's graphical content .. ie Artist/album or Artwork AND also the buttons do not change color when they are pressed, even through they are working .. so it looks as if, while the Widget is still running and controlling the player, it has lost it's ability to update it's own image.

If FCC is re-started, then the 1st Image may be correct, and it can do one Next Song with updated image, but after that, while it can still cause the next song to play, it has now lost it's ability to update it's own image.

Hope this helps ...
[Android Head-Units] TT_Vert:
Thanks [MENTION=4292729]SpeedFire-[/MENTION]. One suggestion for you. I know you get a ton of issues and what not to fix but if you get a second to acknowledge you are aware or looking at some of these bugs it'd be nice. I had posted a few things over the past few years and in the beginning I had an idea if you saw my post and were going to rectify it and others (The volume widget) you just fixed them but didn't acknowledge the post reporting it. It can feel like being a beta tester is pointless and our findings are pointless. I know that not to be the case but sometimes It feels that way. I did pay for the app in the beginning as I really liked where you were going with this and I still do but if I'm going to be doing beta testing I'd like to at least know I'm being heard as this if for everyone's benefit including yours.

Dave
[Android Head-Units] Scopesys:
I am really pleased with the way Speedfire responds, and the enormous amount of time & effort he must put in to keep developing FCC.

As a Beta tester, there are two things I would like to see as FCC is developed.

(1) A Change log, with some details on what has changed in each beta.

Ideally a text file, maybe on a Google Drive, where everyone can see what has been done at various versions -- especially good for anyone joining the Beta program, or has joined recently, to get up to speed with what & why things have evolved the way they have.

(2) When a Beta is released to the Play Store, in the description for that release, at the top, always remember to put the Beta Version number, so we know what version we are downloading & installing.

Thanks again to Speedfire for his excellent support of FCC. It is not many Apps that have such speedy and frequent updates.
[Android Head-Units] TT_Vert:
I'm not disputing he is VERY involved and this is clearly a passion of his. I do like how he actually resolved things but it'd be nice to know what was or wasn't going to be looked at or even possibly resolved or not. IE, FTY joying units do not work w/ this launcher AT ALL and i said I'd be willing to help develop it but got no response at all. A not at this time would have been good enough. Same w/ the volume widget I brought up. No acknowledgement, just a fix today. That's fine but even "I'll look into it" makes people know he's aware of the problem so we don't continually bug asking about something and cluttering the thread. I have a few more of these same circumstances. Don't get me wrong his effort is appreciated, just want to know where requests or bug fixes stand. Maybe something like 1. can't do 2. will look into 3. developing 4. need more info would be helpful.
[Android Head-Units] Roerbakeitje:
Yes Also a FTY Joying . And Also alot bot working with fcc launher
[Android Head-Units] twestar:
Good Day,

I would like to say that I'm in love with your launcher, but I was wondering if you can add more steering wheel buttons in the app.

There are only 4 buttons to configure ( short or long press).

I purchased a knob that looks like those luxury cars and it has 5 buttons and a scrolling wheel that your app recognize.

So is there any chance to add more buttons in your App like 7 or 8 instead of 4? Also do you think you can add a scroll function like instead of using the touch screen I can just use the scrolling wheel to navigate through the app?

Here is a pic of the knob that I bought
[Android Head-Units] SpeedFire-:
I understand your frustration. Sorry for that. This is not intentional.

Most bugs need some investigation (sometimes very time consuming) to even realize how quickly it can be fixed. Sometimes I don't have time even for that.

I could comment every bug with some standard phrase like "I will look into it", but I don't like to promise something that I can't do. I saw such developers and I don't think that such answers build trust between developer and users.

To be honest I have a very limited time for the app (mostly in the nights). Moreover in the background I have some tasks which I want to implement in the app by myself (like recent Settings restructuring). Users bug reports are really important too. But I need somehow to prioritize bug fixing.

Sometimes I fix bugs which are easy to fix, sometimes I concentrate on bugs which a reported most. Some bugs are not caused by the launcher and I need to filter them out.

My suggestion is to repeat post about most frustrating bugs. This will increase their importance in my eyes. This is not the best bug tracking approach I know, but this is how it works now :)

At least I am open with you ;)
[Android Head-Units] TT_Vert:
Be careful what you ask there. People will just continue to repeat their same posts over and over. We do appreciate all your effort and being up front.

I suppose I'll reiterate my problems/requests. None of them are urgent at all just stuff I've noticed while setting up my new stereo. That radio is not in production yet so I can do bench testing to help resolve issues if you'd like.

1. Album art issues on occasion. Same as a few others and I have provided logs in another post

2. Not exactly FCC but a bluetooth connection issue i encounter when connecting a particular device where I lose home button and volume knob control.. Logs were included.

3. Backup/restore just does not work and never has. Try it with a fresh launcher install and you'll see.

4. Pandora will open twice during boot and possibly any other app in widget but will doubt check. No auto start options enabled except "start media player if opened on power down". (I have not logged this yet or even really looked into it)

5. Joying FTY development. I never heard back from you on this so I sent back this unit as the MCU is not compatible w/ current FCC. (Nothing worked, dimming, audio controls, etc.)
[Android Head-Units] Salvo-x:
bugs

I confirm the same problems
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

Ref: Player Widget "stops updating text & Artwork" issue.

If you also turn on FCC Notifications, you should see that they also stop updating or showing any artwork, when the Player Widget stops displaying.

So there may be a connection.

I really hope you can see this issue when running in the Emulator, which will probably make it a lot easier to trace the issue.
[Android Head-Units] SpeedFire-:
This was a quick fix.

In the next beta you will have up to 7 buttons instead of 4. And also two new actions - Next screen and Previous screen. These actions will not scroll everywhere, but at least you will be able to scroll between home screens.
[Android Head-Units] sbruda:
Off-topic, that's an awesome knob, would you mind sharing from where did you purchase it? Many thanks.
[Android Head-Units] SpeedFire-:
Wheel button day today.

Beta 3.117

Wheel button remapping:

- Up to 7 buttons can be mapped (raise from 4)

- Assigned Key Codes are now visible in setting (may require a one time remapping)

- Ability to CLEAR button assignment (finally! many of you asked)

- Fixed bugs with key mapping

- New actions can be assigned: go to previous / next home screen, go to very first / last screen.
[Android Head-Units] Scopesys:
[MENTION=1633144]speedfire[/MENTION]

Is it possible for the user to make :-

(1) Custom Skins,

(2) "Custom Masks" for the artwork in the player widget
[Android Head-Units] TT_Vert:
Hey [MENTION=4292729]SpeedFire-[/MENTION] all this button mapping got me thinking. How hard would it be for your software to intercept MCU hard button keypresses like MTCDtools does to remap rather than just soft and steering wheel keys?

Dave
[Android Head-Units] twestar:
I can't post links yet since I'm a new member, but I got mine from taobao which is much cheaper than the ones on Ali express.

The knob has an IR reciver but you need to note that some knobs ( usually the knob color is black like the one I posted before ) have 5-6 wires to connect to your head unit which is more complicated since 2-3 wires of them need to be directly connected to your main car wires for them to work but mine ( the knob color is silver ) has 3 wires that only need to be connected to the canbus. You just need to ask the seller before buying the knob.
[Android Head-Units] SpeedFire-:
I decided not to use Xposed (like mtcdtool uses) in my launcher because it significantly shows down the device and boot time.
[Android Head-Units] SpeedFire-:
How exactly do you want to use it. Show me the image. Please note that the background image may be distorted when the widget scales.
[Android Head-Units] TT_Vert:
do you have the ability to intercept MCU keypresses though? MTCD tools does NOT use xposed just FYI. Or at least the part i'm using to remap hard keys.

Dave
[Android Head-Units] SpeedFire-:
Can you please give a link to the version you use? Or attach apk?
[Android Head-Units] ka724ka:
Hi Speedfire,

My head unit (Allwinner T3) uses the its own Bluetooth app instead of Bluetooth in system setting for A2DP connection. Could you please let me know what Bluetooth type should I choice in FCC setting?
[Android Head-Units] Roerbakeitje:
Glad to see more and more FYI devices with android 8. I whas Thinking that i.m the only on with type This device.
[Android Head-Units] Scopesys:
Quote:

Originally Posted by Scopesys

@speedfire

Is it possible for the user to make :-

(1) Custom Skins,

(2) "Custom Masks" for the artwork in the player widget

Wanted to make a Custom Mask that would work with the Player Widget, when using Non-Round Artwork, to darken the area of the artwork where the WHITE Player Controls are put onto the artworks, so if the artwork is very light, the controls can still be seen.

I do not currently put the Artist / album on the artwork, because it is often difficult to read, but a different mask, could deal with that text as well as the controls.

This would not be necessary if you are able to give the Text and Controls their own Back Shadow , or Black Outline -- as suggested earlier this month.

That being said, are user created custom masks a possibility -- ie a user created Graphic that can be placed somewhere for FCC to include with it's existing masks.

Same goes for Skins... I assume skins are more than just a Graphic, as when icons & widgets are placed on them, they lock to specified locations. ?

example:

NO mask -- controls lost in white artwork

(SIMULATED) With new "Custom" mask -- controls now visible on light artwork

Note: The current FCC masks do not work with the Square Artwork Player Widget... would be nice if they (and any user customs masks) did
[Android Head-Units] Salvo-x:
Bugs to Player Widget

Hello

I still have anomalies in the Player + Radio widget, radio mode does not display the name of the radio station, and the RDS text, in Mp3 Player mode, does not show the title of the song and the artist, in Dab-Z I mode you will see the name of the radio and the transmitted text but the scrolling is partial,

Do not synchronize the player with the icons, and if you press, do not highlight as chosen in the settings
[Android Head-Units] TT_Vert:
This is what I'm using. I do not have xposed framework installed on this unit currently and this works fine.
[Android Head-Units] Legolas8911:
[MENTION=4292729]SpeedFire-[/MENTION]

Firstly, awesome work, just started using it on an Xtrons HU.

Just saw your debate with issue priority and so on a couple of pages back. Why not open a github issue tracker or something similar? That way you can assign labels by priority, by status, reporters are up to date, etc.
[Android Head-Units] TT_Vert:
Yes skins are just a graphic. I actually pulled them out to use them as a template for a custom background I created. Mostly for image/text placement of my background so it was visible when I had my icons and widgets all on the screen. I was trying to find the path and names of them but I think i remove that apk from my emulator.
[Android Head-Units] SpeedFire-:
I looked at this tool and tested it on my PX5 unit. It seems that this app intercepts keyCodes of originally assigned functions just like my old method of key binding (still available in settings). It doesn't cancel the original action and just starts some additional action after it. Or I missed something? What's the benefit over the FCC's old method?
[Android Head-Units] TT_Vert:
I don't see the FCC old method? All I see is "wheel buttons" The custom wheel buttons (native remapping) doesn't detect the hardware keys. Is there somewhere else button remapping could be?

Dave
[Android Head-Units] SpeedFire-:
Under (native remapping) you should see another option like (button interception) or something similar with the white wheel icon. This is the old method.
[Android Head-Units] TT_Vert:
Yes that does not intercept any of my hardware keys. I had mentioned that i think a few weeks ago. I'll check again, would you like me to log anything?

Here is what happens when I press a key (Nothing). I''ll get a log in a bit but here is a quick video of what is happening.

[YOUTUBE]https://youtu.be/kXyPhMIE31c[/YOUTUBE]

Dave
[Android Head-Units] SpeedFire-:
Yes. You may log button assignment process.
[Android Head-Units] Scopesys:
OK.. Skins are just Graphic files.... so what defines the areas where Widgets or Icons can LOCK to. Is it the actual skin foreground graphic that acts like a boundary/grid ? If so, at what point goes something in the graphic stop being a background, and start becoming a boundary.

Also, you indicate that the skins are separate graphic files, in some path , and not embedded in the actual program. I tried looking for such graphic files, without any success. Can you or someone else tell me where they are located.

(I hope I do not have to be rooted to gain access to see them and add to them ?)

Does this also apply to the Player Widget masks -- should I be able to find these as Graphic files somewhere. ? Hope so :)
[Android Head-Units] TT_Vert:
Just looking at the apk quickly the skins are PNGs and the one I use is intro_dashboard.png and is 1024x600. Do a search of your device to locate the files. You device what widgets you want and the sizes based on the skin you use. As far as I can tell it's just an image which is designed around the stock row/column setup of FCC.

Dave