yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Hminhh:
Yes, it also belongs to fyt, it's quite interesting, you can put the car behind the pip, I decided to work a lot with it, but it still causes the error as I mentioned above. Have you ever encountered this situation?
[FYT Android Head Units] surfer63:
Again: which launcher is this? It is not the 34. It is hard to say anything if it isn't clear which launcher it is. Every launcher behaves differently.
[FYT Android Head Units] Hminhh:
yes it's not launcher 34, it's launcher 21, can I post it here
[FYT Android Head Units] Sztifel:
I use Google translator.

I'm looking for this launcher that is marked in the box. After flashing, the one above it starts.

View attachment 6112142
[FYT Android Head Units] apikanto:
7862/8581 FYT Factory by Mario Dantas
[FYT Android Head Units] Sztifel:
You did not understand me;)

After flashing this launcher in the frame from the MarioDantas website, the one above it launches.
[FYT Android Head Units] apikanto:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

you need to go to factory settings and select them

*********************************
[FYT Android Head Units] Oswald Boelcke:
Hello and good afternoon, @apikanto

As a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Polish posts.

Spoiler content hidden.

And I grant you 3 days to translate all your other "Polish-only" posts. Unless done within this time frame, I'll delete them.

Regards

Oswald Boelcke

Senior Moderator
[FYT Android Head Units] Sztifel:
I do this, but after selecting this launcher in the factory settings, the one above it launches anyway and I don't know why. Additionally, the map widget is poorly sized and covers some of the icons at the bottom and some of the other widgets.
[FYT Android Head Units] apikanto:
and do you have a screen resolution of 2000x1200
[FYT Android Head Units] Sztifel:
View attachment 6113334
[FYT Android Head Units] apikanto:
Reset the radio and try to select it in factory settings
[FYT Android Head Units] Sztifel:
I managed it and here is a link to the firmware package located on my Google Drive, which I received today from an Aliexpress seller for my radio.

View attachment 6116947

https://drive.google.com/file/d/11kzeQ5WfqMyTO4oEA8iR0kxv5J3Otg4K/view?usp=drive_link

Additionally, there is a link to the launcher36, which I extracted from this firmware for resolution:

1024.x600

1280x720

1920x1100

2000x1200

Just unpack and put it on a pendrive. This is the launcher from the video in this post with a small difference, namely the car widget is smaller and there is also room for a navigation widget.

Sorry for my English, but google translator helps.

https://drive.google.com/file/d/11ofwM9u0dxoC39Vuzc6ThEm-bGEZTZjF/view?usp=drive_link

These are not my screenshots, just borrowed from the Internet.

View attachment 6116957View attachment 6116958
[FYT Android Head Units] surfer63:
Really? your version is of 15 September 2023. The latest firmwares are of 9 April 2024.

This is an old firmware.

And why post it here (and again). This is a laucher thread, not a firmware thread.
[FYT Android Head Units] Sztifel:
Sorry. I searched everywhere for the latest software for my MCU ANC_53, including on 4pda, but I couldn't find it anywhere and I thought that since I managed to get it from the seller, since I am already posting a link to the launcher, I might as well post a link to the software too.

Could you point me to the latest firmware?
[FYT Android Head Units] djbooya:
For the launchers that have a car widget that shows the speed in K/ph -- how do you change that to M/ph? I tried searching the xml looking for strings such as kph, mph, speed, but it wasn't obvious to me where I should be looking to make this modification.

Thanks
[FYT Android Head Units] louforgiveno:
I'm not sure it's been done, but an interesting post i read recently about something unrelated gave an idea worth looking in to.

Use an ai program and ask it,

Can probably get you close
[FYT Android Head Units] surfer63:
It is mentioned in one of the M6 threads. I believe you have to tap and hold the km/h or mph a few seconds and then it automatically switches to the other unit (but this is from the top of my head), but it is only for the M6 models.
[FYT Android Head Units] j0hn83:
Unfortunately it is not for the M6 models but it only works on specific launchers. I think only 1 launcher on my M6 did this and it wasn't a launcher I liked.

FYT have their properties all wrong.

I can see my temperature in 2 units and I can see my tyre pressure in 3 different units but I can only see my speed in a unit not used in my country.

Fortunately I now use a device with active developers who don't rely on FYT fixing everything.
[FYT Android Head Units] djbooya:
I think it's not in the cards for me then..I did try that method thinking it would to it too..oh well, not a huge deal.

Also, in regards to launcher modding is it only possible to have 1 PIP/custom block? I'd really prefer to specify an app. Other than your notes at the beginning of this thread are there any other docs online about launcher development?
[FYT Android Head Units] surfer63:
I did not remove this.

This is the battery status of the connected phone. In some images I simply did not have my phone connected.

So that is how you can "remove" it ;)
[FYT Android Head Units] old.splatterhand:
Oh, i didn't know this.

Thanks for making this clear to me!
[FYT Android Head Units] xavermcos:
Hello, im using the one with Only Bottom App Bar and have an issue with alignment. Im not complete sure if this is an problem with my unit only. The rectangle behind the app symbols, the bar isn't there at all. Is it my device?

Device is with 2000x1200.

Thanks for your efforts!
[FYT Android Head Units] surfer63:
No, I don't think it is your device.

- The app bar needs to be shifted to the right.

- I don't know where the background bar went. :)

- The PIP window and semi-transparent background are not correctly aligned.

I will have a look.
[FYT Android Head Units] xavermcos:
Thank you very much,

I think this version with the large window is the clearest version. Especially in combination with the FrontApp
[FYT Android Head Units] surfer63:
I did send you a PM with an new experimental one.
[FYT Android Head Units] j0hn83:
Working perfect here. Thank you 👍🏻
[FYT Android Head Units] Fredday:
You got the 2000x1200 res as well?
[FYT Android Head Units] surfer63:
Currently working with @xavermcos to get the 2000x1200 correct. Seven posts up you can see the mis-alignment and my comments.
[FYT Android Head Units] Fredday:
Ok nice! Saves me the trouble then haha. Goodluck!
[FYT Android Head Units] surfer63:
The 2000x1200 layout for the version "OnlyBottomAppBar_190001034_com.android.launcher34.apk" has been corrected.

Thanks to @xavermcos for testing two intermediates.

See post #1 version 1.0.2
[FYT Android Head Units] Fredday:
I just installed the launcher, this went perfectly so no troubles there, however I did notice the layout is still not right. I took a screenshot as you said to showcase what I mean. At the bottom the app bar isn't near the margin like it should, it's a tad bit higher which in turn also affects the pip to be smaller than it should be as it could be stretched more downwards. In regards to the app bar I want to ask if it's possible to shrink this a little bit? As the icons are quite big still and preferrably we'd have more screen than apps in our face, not? Besides that everything does seem to work and looks great! :cool:
[FYT Android Head Units] surfer63:
I know that, but what if you have an M6 Pro with a bottom menu? Then it's a tight fit without any margin at all. I got this image from another user.

What I can do is make the margin between the icons and the PIP-window smaller.

And with regard to smaller icons: There are some design standards with regard to icon sizes. Of course I can deviate, but with smaller icons and bumpy roads, it might be less easy.

In first instance the icons on the app bar were too much to the left, they now should move a little back to the left.

View attachment 5982603
[FYT Android Head Units] Fredday:
I understand your reasoning and I do have the m6 pro with the bottom menu however since we're using @LLIyT_HuK peace_os this becomes obsolete as we can just use the notification bar to give commands. To further specify while I was using launchers from @mariodantas the bottom menu already overlapped the app bar.
[FYT Android Head Units] corey_s:
Hi Surfer63,

Just a quick thank-you. I tried yesterday and had the same problem that others had on my brand new EKIY T7, it's not even in the car yet because they sent me the wrong cable, new one arriving soon. Latest version works great. Still trying to figure out which version I like best. Probably the bottom only but right now I'm using the default.

Also many thanks to LLIyT_HuK for the status bar and your other work.

Right now, I'm being restrained in what I install before I get it into the car to test the actual integration works.

Corey
[FYT Android Head Units] surfer63:
But what do you use in @LLIyT_HuK's PEACEOS? Do you mean the systemui? And what functionality are you talking about?

I also use the notification bar, but as far as I know there is no app launcher in it.

If so, please share your knowledge ;)
[FYT Android Head Units] Fredday:
Yes the systemui, where you can use the same commands as the bottom menu coming stock from the m6 pro. A back button, open your other open apps and a home button.

Because the other commands possible with the stock bottom menu would be turning off the screen (never used) and volume up or volume down (which I control through my steering wheel).
[FYT Android Head Units] ducthang83:
great job thank you

can you make version for 13in 1920x1200 screen
[FYT Android Head Units] surfer63:
The Launcher is made for resolution widths of 1024, 1280 and 2000 wide, where 1280x800 has a big margin on the bottom and 2000x1100 has no bottom margin at all.

It would require adding smali code to the Launcher, which is not my expertise.
[FYT Android Head Units] surfer63:
That has nothing to do with LLIyT_HuK's systemUI. Every SystemUI has those buttons. In LLIyT_HuK's version they are top-left, in the standard FYT version they are top-right.

But the "open other apps" is only "recent apps". It does not give you an option to normally stat Apps. So after a reboot (or firmware flash) that recent apps option will be empty. This means that you have no option at all to start Apps.

Please correct me if I'm wrong, preferably with screenshot, as I use the same SystemUI and simply can't find an option to start apps. I can search on apps, but for me that is too awkward, especially when driving.
[FYT Android Head Units] Fredday:
Yes that's exactly what I ment. Open recent apps but this is the same as the bottom menu bar does on the m6pro that you highlighted in this screenshot.

You can however scroll through the apps you chose to launch on default when the unit turns on if you changed this through settings so in theory you can scroll through 'recent' apps. I for example have dab-z, tpms and obd app 'launching' when I turn on my device.
[FYT Android Head Units] iamrance.asa:
Thank you for this! I've been working on trying to modify some launchers for my vertical unit but have been running into some issues with the signature. I'm sure with this I will be successful :)
[FYT Android Head Units] surfer63:
Do you mean the apps you can chose to start on system start? (Settings.apk: Application Setting ( which applications you want to auto-start when you start your car and unit )).

Or which other setting?
[FYT Android Head Units] Fredday:
Yes exactly what I mean indeed.
[FYT Android Head Units] KoTiX2:
As I know all system apps on FYT units are signed using standard Google keystore (user,password and alias are simply "android").

I attached the platform.jks needed to sign the app with keytool (extract it from the zip)

This mean that you can create any app with same package name of a system app and replace it simply with an update/increase of version number in the manifest.
[FYT Android Head Units] iamrance.asa:
Wow! Thanks for this. Wish I would had known this earlier. Would have saved me so much time
[FYT Android Head Units] surfer63:
@Clandaries: I did send you a PM.

I tried to make the launcher "OnlyBottomAppBar_190001034_com.android.launcher34.apk" also suitable for 1920x1200. I modified the smali code for that, and of course added the necessary layout.

Please try.

Off course you first need to install the not optimized version before you can install the apk.
[FYT Android Head Units] surfer63:
@ducthang83 : I did send you a PM.

I tried to make the launcher "OnlyBottomAppBar_190001034_com.android.launcher34.apk" also suitable for 1920x1200. I modified the smali code for that, and of course added the necessary layout.

Please try.

Off course you first need to install the not optimized version before you can install the apk.
[FYT Android Head Units] Dietama:
already try, working good on m6 pro plus 1200x2000 nice fit size, why can't add aple music on front ?

thanksss
[FYT Android Head Units] surfer63:
That is Apple Music. It doesn't want to play in a PIP-window. What else do you expect from Apple?
[FYT Android Head Units] Dietama:
ok then 😂😂😂,

mmm why i didn't get status bar cpu temp etc at upper bar, did i missed something?

thanks 🙏🏼🙏🏼🙏🏼🙏🏼
[FYT Android Head Units] Gscipione:
Nice I try on my medeke m6pro with md kernel and all works fine. I used with waze in pin and work fine
[FYT Android Head Units] old.splatterhand:
You should read the last part of first post again ;)
[FYT Android Head Units] Dietama:
okay thankss 🙏🏼🙏🏼🙏🏼🙏🏼
[FYT Android Head Units] surfer63:
You have the standard SystemUI.

I have @LLIyT_HuK's SystemUI intalled. See his PeaceOS thread, or the last line in post #1

Edit: @old.splatterhand shoots faster than his shadow ;)
[FYT Android Head Units] haixuling:
well done.

Can you make the map as large as possible, and the icon area on the left can be made narrow。
[FYT Android Head Units] surfer63:
I already had many requests. This weekend I will look into a few.

- Reduce margins around elements, but note that some facias (the plastic around the screen) can vary thereby reducing the screen a little.

- maybe reduce icons

- Try to make the 2000x1200 in two variants as some 1200 units have margins at the bottom.

If your wishes, or other persons wishes are not granted, you can easily make your own changes. I did write the high-level howto. Everyone has to practrice and learn.
[FYT Android Head Units] haixuling:
thank a lot.

I had use android kill open your file。

My screen is 1280*720.

The results I calculated are very different from yours。I don't quite understand。

I calculated it the sys.lsec.pip_rect is ( 115 60 1160 665).

Your plan is "115 80 1013 584"

The difference between length and width is too large

View attachment 5984279
[FYT Android Head Units] Fredday:
Victim of your own success 🤣

Just proofs how much we like your content.
[FYT Android Head Units] surfer63:
You are in the wrong section. The part as of .line 609 is for 1280. That is what I mentioned in the section below the smali code. 0x500 hex = 1280 dec.

sections as of .line 610 is for the 1024x600 screen. 0x400 hex is 1024 dec

And I extended the smali with a 1920 section 0x780 hex = 1920 dec.

Edit: so for 1280 on a "OnlyBottomApplicationBar", I calculated "130 80 1252 705". It also depends whether you want only the bottom application bar (the example), Only the left recent apps bar, or both bars. Everythime you get a different size pip window.

If I want to get rid of the the frames I would have mentioned "110 60 1276 725", whete the 1276 gives me 4 pixel margins on the right side to "compensate" for less fitting facias that reduce screen size sometimes by 1-2 millimeters.
[FYT Android Head Units] haixuling:
Thanks!

But I find that the parameters of this may also be very very important。

The (android:id="@iD/iv_map1") in layout_one.

It determines the coordinates (x y) of the starting point of the pip window。 OR pip windows depends on it.

in line 609 (130 80 1252 705 )

The Length(1252) and height(705) of pip window can only be greater than (android:id="@iD/iv_map1") and cannot be less (android:id="@iD/iv_map1")
[FYT Android Head Units] Gscipione:
hi @surfer63 it is possible to install your SystemUI bar without installing the whole PeaceOS firmware? but only the bar?
[FYT Android Head Units] surfer63:
It is not my SystemUI. @LLIyT_HuK made that SystemUI.

And yes, it is perfectly possible to only install it. I don't have the PeaceOS and use it also.

Look at the last line of post #1 or check the PeaceOS thread. There is a zip that creates a flashable install.
[FYT Android Head Units] surfer63:
To start with: always tell me which launcher you are talking about: the "launcher34 apk with left "hot seat" (recent apps) bar and bottom application bar", the "launcher34 apk with only left "hot seat" (recent apps) bar" or the "launcher34 apk with only bottom favorites application bar". I don't like guessing and I don't like at all that I first have to spend time to find out which launcher you are working on.

Of course there is a direct relation.

The smali PIP window gives programmatically the size of the PIP-window.

The layout in custom_layout_one.xml shows where it will be placed with which size.

The accompanying layouts for the several resolutions need to have the exact same size as the PIP window definition. And it is up to you to decide where you want to place that window.

If you increase the PIP window size, you also need the increase the layout size. And vice-versa.

I now show the read-only java code, as the smali code is much, much longer and hardly to read.

If you open my modded "OnlyBottomBar" launcher in jadx-gui, you will see the following read-only java code:

private void setWindowLoc() {
SystemProperties.set("persist.syu.launcher.haspip", "true");
SystemProperties.set("persist.lsec.radius", "14");
Intent intent = new Intent();
intent.setAction("android.intent.action.MAIN");
intent.addCategory("android.intent.category.HOME");
if (getPackageManager().resolveActivity(intent, 65536).activityInfo.packageName.equals(getPackageName())) {
Log.d("LZP", "----->>> UI20");
if (getResources().getDisplayMetrics().widthPixels == 1280) {
SystemProperties.set("sys.lsec.pip_rect", "20 80 1260 585");
} else if (getResources().getDisplayMetrics().widthPixels == 1024) {
SystemProperties.set("sys.lsec.pip_rect", "20 80 984 484");
} else {
SystemProperties.set("sys.lsec.pip_rect", "20 125 1930 913");
}
}
}

And the latest for testing 1920x2000 (not publicly released yet), you will find:

private void setWindowLoc() {
SystemProperties.set("persist.syu.launcher.haspip", "true");
SystemProperties.set("persist.lsec.radius", "14");
Intent intent = new Intent();
intent.setAction("android.intent.action.MAIN");
intent.addCategory("android.intent.category.HOME");
if (getPackageManager().resolveActivity(intent, 65536).activityInfo.packageName.equals(getPackageName())) {
Log.d("LZP", "----->>> UI20");
if (getResources().getDisplayMetrics().widthPixels == 1280) {
SystemProperties.set("sys.lsec.pip_rect", "20 80 1260 585");
SystemProperties.set("persist.lsec.radius", "12");
} else if (getResources().getDisplayMetrics().widthPixels == 1024) {
SystemProperties.set("sys.lsec.pip_rect", "20 80 984 484");
SystemProperties.set("persist.lsec.radius", "11");
} else if (getResources().getDisplayMetrics().widthPixels == 1920) {
SystemProperties.set("sys.lsec.pip_rect", "25 125 1870 913");
} else {
SystemProperties.set("sys.lsec.pip_rect", "35 125 1965 913");
}
}
}
[FYT Android Head Units] Gscipione:
thanks for the information. Perfect 😄
[FYT Android Head Units] surfer63:
I released a new "OnlyBottomAppBar_190001034_com.android.launcher34.apk" version 1.03

Changelog:

1.0.3 beta - 25 August

- Added 1920x1200 smali check and layout

- Added 1280x800 smali and layout

Two users asked for a 1920x1200, so I asked these two users to test the 1920x1200. One is on holiday, the other said he would test, but I heard nothing so far.

@ducthang83 : Please let me know whether the 1920x1200 works?

@Mr Magictree : Can you test this version for 1280x800?

I will see what and if I can do something about the frame margins.
[FYT Android Head Units] Mr Magictree:
@surfer63 i would like to say: “goed bezig”. I installed the launcher just by installing the package not via lsec. This is what I got on my screen. If you tell me which file you changes I do not mind also fiddling around with it.
[FYT Android Head Units] surfer63:
Sorry. I already see what I did wrong. I increased the size of the PIP-window, but forgot to "push" the app bar further down. I will release another tomorrow morning.
[FYT Android Head Units] ducthang83:
I just got it today for testing I think ui34 matches my fyt116 is fyt108 so the launcher flickers

Version 1920x1200 available ui34 install error not for overwrite
[FYT Android Head Units] surfer63:
@Mr Magictree : Please find attached a new 1280x800 version.
[FYT Android Head Units] surfer63:
Can you please make a screenshot of it?

Please do this by drawing down the top notification bar twice and select the "scissors" or "camera" screenshot option, NOT a mobile phone photo of the unit.

Edit: Or do you see nothing at all? Only a flickering screen?
[FYT Android Head Units] haixuling:
Sorry! My fault。

I just talked about onlyleft version.

I know nothing about java code.

Just wanted to modify some layout。

I modified several versions, I'll test them later。

Thank you for the guidance。

Very thank you.
[FYT Android Head Units] I[E:
I can't for the life of me get this installed.

Freshly formatted USB (exFAT).

Extracted the zip to the USB

Plugging it in triggers the FW update but then it shows "no command"

Looks like the USB DVR was initializing first. Unplugging it works.
[FYT Android Head Units] surfer63:
exFAT is Not supported. Can be read, but not used as flashing disk format. Are you sure you used the same formatted usb stick for the MD flash?

If so: do a chkdsk to see if your stick is not corrupted.

Otherwise: Format as FAT32.

Please show us your listing on the USB-stick as well.
[FYT Android Head Units] surfer63:
I know that a lof of users want the margins as small as possible, but I already mentioned that the facia's that come with every unit might "cut off" some pixels.

I created for my self a version with 5 pixels top/left/right/bottom for the PIP window, and going to 665 pixel deep (on a 720 pixel) unit for the app bar.

Left is the "real" screenshot from the screen as the unit makes it.

Right is the version as I saw it. The 5 pixel on the right is completely "eaten up" by the bezel of the facia and even takes some from the Maps window. I marked that with the red bar.

You can also see that the bottom bar "touches" the bottom of the screen and even misses some pixels.

View attachment 5987101	View attachment 5987103

5 pixels is not enough on my 1280 width screen, at least not on the right side, so I will go for 10 pixels on each side.

That means that I will "calculate" (2000/1280x10=) ~15 pixels on a 2000 pixel width screen.

I can decrease margins and increase the PIP window, but not as much as I wanted or other users want.

To be continued ....
[FYT Android Head Units] Mr Magictree:
@surfer63 almost there…… I had some issue with my headunit due to playing around and mixing with firmwares :-) I know have a set of installers that brings it back to stock. So it took a bit longer for feedback. But have a look at the screenshot.
[FYT Android Head Units] Fredday:
Thanks, I appreciate the hard work. Let me know if you want me to test something for you. 🖐🏾
[FYT Android Head Units] surfer63:
@Fredday : The attached version for the 2000x1200 layout has narrower margins, a bottom applicationbar pushed 80 pixels "down" and increased PIP window size.

@Mr Magictree: The attached version for the 1280x800 layout has corrected app bar. And also reduced margins and a bigger pip window.

I hope I did the calculations right.

Edit: If I did correct, it will become the new version.