yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
With regard to your 1920x1200 resolution and the PeaceOS SystemUI.

Inside the SystemUI you will find under res the following folders

values-1800x720

values-1920x1200

values-1920x720

values-2000x1100

Inside those folders you will find the dimens.xml

In that file you have to play around to get the correct values for icons, spacing and font sizes. You might want to look at the 2000x1100 as it must be almost the same as your 1920 (you could try for the sizes to start calculating with 1920/2000* <size>).

There are also layout folders like

layout

layout-2000x1100

layout-land

layout-watch

As with many of the launchers, there is no 1920x1200 layout. You might want to try to add it, but it might not be picked up by tghe SystemUI. This 1920x1200 layout is a badly supported resolution.

What did work with some of the launchers is to put all 1920x1200 elements inside the 1280x70 layouts and values, but that would make it ONLY sutable for a 1920x1200 layout.

Anyway: Once you have completed that and all is working fine, please share the dimens.xml here so that @LLIyT_HuK can apply it to the SystemUI.
[FYT Android Head Units] surfer63:
Why?

Your application layer is from 20 April this year and your kernel from 10 May this year. It is brand new.

Only reason to upgrade is, if you have issues.

And if you really want to upgrade to a new version, because it is possible, then first read the forum. So much information here. You are past the "feed the baby" stage, so do spend some time on it. Start with "General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware"
[FYT Android Head Units] mohan2891:
Yes sir you are right.. I recently updated my unit but after update some apps are missing. 360 camera app, default system app store. So I need to install some other update, that suitable for my head unit. Please help me.
[FYT Android Head Units] surfer63:
Take the latest "7862-A12-wbt-9-10.rar" from Mekede. Again read "General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware".

It tells you where to find it and what to do in case of different manufacturer ids and the like.
[FYT Android Head Units] mohan2891:
Thank you sir , I installed 7862-A12-wbt-9-10.rar. successfully rebooted. But it's showing this error (UI and MCU dose not match!(YIN) )
[FYT Android Head Units] Clandaries:
Read Post 295 again. He said already what to do
[FYT Android Head Units] mohan2891:
I don't know what to do now. Please help me
[FYT Android Head Units] surfer63:
What did I tell you? Twice even!

You need to READ the forum.

Everything is in the thread I twice mentioned.
[FYT Android Head Units] mohan2891:
I read that forum ,but I'm confused, I can't understand, because I'm poor in English, please I'm requesting you sir , please tell me , what to do now in a short way. Please
[FYT Android Head Units] surfer63:
This post , bullet 2.

Use the lsec6315update from the firmware you downloaded. The one with the script is now too old. I will update it.
[FYT Android Head Units] mohan2891:
Ok
[FYT Android Head Units] mrduagang:
Thank you sir for guiding me in so much detail. I have just received support from Mekede to upgrade to M6 3D system. After I have finished experiencing it, I will post a review!
[FYT Android Head Units] mohan2891:
Finally error (ui and MCU dose not match) was gone. Thank you sir...

But navigation buttons are looking different than previous, and when I'm using default launcher ( Android launcher ui 22,17, 06) screen is blinking continuously.

And last one doubt sir, this 7862-A12-wbt-9-10 update is genuine Android 12 or fake.
[FYT Android Head Units] j0hn83:
It is not possible to upgrade these units from Android 10. Currently they are stuck on Android 10.

Any upgrade to 11 or 12 is fake.

I can make it say Android 99, only the number changes.
[FYT Android Head Units] Kaelub:
I was able to download everything for this except the system folder for my unit (1280x720). What would happen if I installed what I did download, and the SystemUI.apk? That's what I really want. That status bar is what im after! Is there a simple way to backup the original systemui.apk? So i can try and then switch back. :)

edit: Also, does flashing the SystemUi.apk or PeaceOS wipe the unit? I didn't see a "twipe_all" or whatever the command is for that.
[FYT Android Head Units] Clandaries:
Would like to see it working on Teyes CC3 devices.

Mario made his firmware/kernel now also work with Teyes.

So maybe it would be possible?

I like your bar
[FYT Android Head Units] LLIyT_HuK:
Mario has a system part that is virtually identical on all devices. And the OEM part is where all the differences are. I do not have Teyes devices and do not plan to purchase them, so I have nothing to test modifications on.
[FYT Android Head Units] LLIyT_HuK:
You can simply copy your SystemUI from the system using a third-party file manager.

When installing PeaceOS, wipe is required; when installing SystemUI, it is not necessary.
[FYT Android Head Units] surfer63:
Well,

You could create a USB-stick with an lsec script with a big removal+copy set. Unpack the AllaAppUpdate into an /oem folder on your usb-stick.

First remove everything from /oem on your unit. Then copy the contents of /oem from your usb-stick to your Teyes.

rm -rf /oem/*
cp -rf /storage/sdcard1/oem/* /oem/
chmod -R 0755 /oem/*
chmod -R 0644 /oem/*.apk

And maybe you need to change /oem with /elable.

Of course: Everything on your own responsibility and you might need to backup first some Teyes specific apks and maybe also copy them to the /oem folder on your USB-stick.

But if it doesn't work you can simply reflash with a Teyes firmware.
[FYT Android Head Units] LLIyT_HuK:
There is one point, Teyes has a different number ro.build.fytmanufacturer=95 )) the visual will be drawn based on it. In theory, changing through the config or FYT.prop will help, but it’s unlikely that anyone has already played with this.

As you rightly noted, “Everything is on your own responsibility.”
[FYT Android Head Units] DrumVlado:
Looks very nice! Do you plan to make a 1920 x 720 version?
[FYT Android Head Units] bassrockers:
Works smooth but miss screen off mode in wheel button study. Have Eonon Q51Pro and in this unit have this option. Very useful in night. Latest update from mekede have app for auto turn on fan. Please add in next update.
[FYT Android Head Units] LLIyT_HuK:
Only if or when I get a device with this resolution. Making complex mods without a device is virtually impossible, and there are simply no emulators for this platform.
[FYT Android Head Units] LLIyT_HuK:
Give me a link to this update, I'll see if I can transfer it.
[FYT Android Head Units] bassrockers:
When back from work upload because download from Mekede site is painful and need to register.
[FYT Android Head Units] Kaelub:
I wanted to ask you... Does your System UI still allow to have Network transfer data show in the status bar, like the factory SystemUI? Hopefully yes, and hopefully you made it look better than the standard one where the text is too big and misaligned. :p
[FYT Android Head Units] bassrockers:
here You go

File on MEGA

mega.nz
[FYT Android Head Units] LLIyT_HuK:
The size is slightly smaller than the standard one, but it displays the same information as the standard one. I don’t see the point in this thing, so I turn it off when I use it))

Spoiler content hidden.
[FYT Android Head Units] Kaelub:
Oh ok, I see. Yeah that looks better than standard one. I use it to know when or if my unit is downloading auto updates. Thank you
[FYT Android Head Units] Kaelub:
So I flashed your SystemUI, and my unit booted ok. My problem is now I have no more status bar. It looks like its in immersive mode. Couldn't figure out how to get it to show, so I re-flashed the original SystemUI back. With no problems after. Just wondering what could be the problem. My unit is 1280x720.
[FYT Android Head Units] corey_s:
Hi all,

My use of PeaceOS's SystemUI broke, I'l explain below, apologies for the essay. I thought it best to provide as much detail as possible. I'm a developer and I hate sparse Jira tickets.

My system was:

EKIY T7 in a 2016 Jeep Grand Cherokee Overland RHS Diesel.

Store link(Thought now is slightly different): https://www.aliexpress.com/item/100...der_detail.order_detail_item.9.5d18f19ctKwwbg

Resolution 1280x720 9"

CPU: 7862 2.0GHz, 8G, 128G

Stock firmware, Apps installed from Play store but the only things I had done(at least that I remember) from the forum was:

Backup as per Surfer's instructions in his 'main' thread.

Installed SystemUI only thread from earlier in this thread.

Surfers modded launcher. The one with buttons down side and bottom.

All was working fine.

Then I started getting symptoms similar to some of the early posts in this thread where the status bar at the top kept flashing. Actually, I never actually saw the status bar, just everything else resized to allow space for it, then resized again to not allow space (full-fullscreen) this happened at about 2Hz, 1s full, 1s space-for-status bar. This made the system very difficult to use. Navigating menus were horrible plus I could never see any status info. Many apps however, just seemed to stay always in full-fullscreen (Like waze) so at least Nav worked fine.

As for what changed, I don't really know. I did install Nova but hadn't started using it and certainly didn't make it the default. Also, accidentally, when trying to install Nova, I installed some stupid made-simple-android thing thanks to Google's annoying sponsored links popping up at the top. I uninstalled it straight away once I realised, perhaps it was the cause?

I did some early steps in trying to fix:

I tried switching launchers. I tried Nova also a couple of the fyt ones. Didn't help

I tried to install Mario Danta's latest MD edition. I thought this unlikely to solve the problem but I was thinking to do it anyway. It didn't help.

Next step was to try and get the old SystemUI on. I somehow missed Surfers post where is added a line to backup the old SystemUI. Fortunately however thanks to his excellent instructions in his main thread, I was quickly able to unpack my AllAppUpdate from my backup and install that. This fixed my issue but of course now I am stuck with the stock SystemUI.

I have 2 SD cards, one installs the stock, one installs the PeaceOS SystemUI. I tried going backwards and forwards a few times but no luck. The PeaceUI one is always broken(in a crash loop perhaps?)

Any ideas? Does this SystemUI store settings/state somewhere that I can nuke in case they got corrupted?

I'd rather not have to Nuke my whole system and install everything again from scratch, especially calibrating my 360 cameras, especially if it is likely that this will just break again in the same way in a bit but I understand if that is the only viable option.
[FYT Android Head Units] Kaelub:
Same problem I had, I made a backup of my systemui.apk right before flashing. So I reflashed my old systemui to return to normal
[FYT Android Head Units] surfer63:
# Deleted #.

Wanted to say the exact same thing like @Kaelub
[FYT Android Head Units] Kaelub:
Btw... Flash back to my normal system ui fixed my split screen issue. Now it works. No clue why or how. 🤷‍♂️
[FYT Android Head Units] khangozzy:
Hi @LLIyT_HuK

I want to try this launcher with my stock firmware (HW info attached) that already have the launcher 34, can I just unzip your file to the root of USB and let it flash?
[FYT Android Head Units] surfer63:
You have a FYT uis8581a with a 1280x720 screen. As such you can simply flash the the launcher.

However, the script is made for a 7862. So you have to add the lsec6316update binary from your own firmware to the usb-stick and copy or rename the 7862lsec.sh script to 8581lsec.sh.
[FYT Android Head Units] khangozzy:
Tried to flash as your instruction but no luck, it rebooted and I saw that it is successfully flashed in the screen output. But, after rebooted the launcher is still the same old launcher 34 as below.

Then I tried to manually install 2 apks (190001034_com.android.launcher34.apk & com.musicwidget.apk) and surprisingly it was successful.

@LLIyT_HuK I noticed that there are 2 music widget as screenshot, the one above radio widget seems doesn't work and the below one works with my stock music player.
[FYT Android Head Units] surfer63:
That sometimes happens that it doesn't change. In that case you had to remove the cache/storage from the Settings->Apps settings for the launcher.

After that first installation you can indeed install the other apks manually (the widget always, by the way).

And if you do a real, normal Android install, the system takes care of removing the old dalvik-cache.
[FYT Android Head Units] LLIyT_HuK:
Try setting your clock to 24-hour format before installing SystemUI. This is probably the reason. Perhaps I can fix this by returning the watch to its previous appearance
[FYT Android Head Units] corey_s:
Thank-you. This did solve the problem. I can change it back to 12-hour and it works then but is broken again after at least a full reboot. I have left it on 24 hour time for now.
[FYT Android Head Units] louforgiveno:
It'll "work" until you try to interact with the pulldown menu or click any of the icons.

I spent a few days trying to find the right location to change back to 12hr time, but eventually just gave up....got "close" a few times but just wouldn't take.
[FYT Android Head Units] LLIyT_HuK:
Essentially, you can just take the time output from the SystemUI source file. I took this from the navigation bar from another Russian mod CEUI, but I didn’t check all the possible options for working in the status bar, which is why the problems appeared)
[FYT Android Head Units] khangozzy:
Hi @LLIyT_HuK @surfer63

The Music widget does not work with my stock firmware, although notification access permission has been enabled.

Now I want to uninstall it, please advise if this 8581lsec.sh script (modified from launcher uninstaller script) can remove it?

#!/system/bin/sh

rm -rf /data/dalvik-cache/profiles/com.musicwidget.apk

rm -rf /data/data/com.musicwidget.apk

rm -rf /data/dalvik-cache/arm64/*com.musicwidget.apk*

rm -rf oem/app/com.musicwidget/com.musicwidget.apk
[FYT Android Head Units] surfer63:
If you have the Google app installed, try to disable it and try again.

The Google starts first and the discover option behaves like a music player.

Another option is to disable the Discover option via the settings (of the Google app).

Another option is to disable the recent apps and then start you music player.

For me it doesn't work correctly with my favorite music player. The first time it works, a next time not anymore.
[FYT Android Head Units] khangozzy:
Thanks for your suggestion but I just want to remove it as the widget below radio widget works fine for me.

Please advise if the below script can uninstall it?

#!/system/bin/sh

rm -rf /data/dalvik-cache/profiles/com.musicwidget.apk

rm -rf /data/data/com.musicwidget.apk

rm -rf /data/dalvik-cache/arm64/*com.musicwidget.apk*

rm -rf oem/app/com.musicwidget/com.musicwidget.apk
[FYT Android Head Units] LLIyT_HuK:
In the script it is enough to rm -rf oem/app/com.musicwidget/com.musicwidget.apk

If you want to clean up all the tails, then look at the original package name.

This widget is for controlling third-party players, the bottom one is for controlling native ones.
[FYT Android Head Units] khangozzy:
Thank you for your reply, I don't need this Ubiquity widget as I only use native music player.

Beside the rm -rf oem/app/com.musicwidget/com.musicwidget.apk cmd

please suggest other cmd to put in the script to remove all data of com.musicwidget.apk
[FYT Android Head Units] surfer63:
If you use PeaceOS and the PeaceOS launcher, you will get errors if your remove the widget. The launcher will not load completely and start flashing as it wants to position the ubiquit widget inside the reserved place in the launcher. The "hole" in the launcher will not automatically disappear because you remove the widget.

So either you modify the launcher yourself and remove the ubuqity widget from the layout xmls, or you need to select another launcher. Only in these two cased you can remove the ubiquity widget.

If you only remove the widget, you will have a non-functioning unit as you can't use the launcher anymore.
[FYT Android Head Units] khangozzy:
I like this launcher and unable to mod the launcher so I will leave the widget alone :)
[FYT Android Head Units] surfer63:
It is actually very simple.

= Use apktool d launcher apk to decompile it

= Go inside the decompiled folder and go to res/layout-1280x720 (assuming this is the resolution of your unit)

= Open the custom_layout_one.xml in a proper ascii editor (NOT notepad)

= Remove the

<RelativeLayout android:background="@drawable/music_bg" android:layout_width="400.0px" android:layout_height="145.0px" android:layout_toRightOf="@id/iv_map1" android:layout_alignBottom="@id/iv_map1">
<com.syu.custom.MFPMusicWidget android:layout_width="392.0px" android:layout_height="137.0px" android:layout_marginLeft="4.0px" android:layout_marginTop="4.0px" widget_package="com.jackthakar.musicwidget" widget_class="com.jackthakar.musicwidget.TallWidget" />
<ImageView android:background="@drawable/music_bg" android:layout_width="400.0px" android:layout_height="145.0px" />
</RelativeLayout>

= Recompile with apktool b -c "decompiled folder"

Sizes, x-y-coordinates might differ. Simply remove that releativelayout.Install it on your unit.

Then you can deinstall the music widget.
[FYT Android Head Units] khangozzy:
Thank you for your guide, but it looks too complicated for me :)
[FYT Android Head Units] khangozzy:
Hi @surfer63

Follow your guide, I removed the code and re-complied the apk, but when I tried to install it the package installer reported that the app is not install. :( please help to check the re-complied apk
[FYT Android Head Units] surfer63:
Did you already have a modded launcher34 installed? The one from PeaceOS for example?

And how did you install it? Using an lsec script or as a normal APK?

When recompiling did you use apktool b -c <folder>? or only apktool b <folder>?
[FYT Android Head Units] khangozzy:
1. I already have modded PeaceOS launcher34 installed.

2. I tried to ínstall both as normal apk and using lsec script.

3. I used apktool b -c <folder> exactly as your guide.
[FYT Android Head Units] Moldeb:
Two questions on this version (the latest, right?):

I use the PiP mainly to switch between GMaps, Here and Osmand navigation softwares via Frontapp. Works well in general but quite often the window is empty initially when waking up from standby. I then have to press Frontapp and select e.g. Here and it then fills the PiP. This "blackout" didn't seem to happen with your original Launcher34 (before the redesign) - not sure why. I see this behaviour on both units. Seems to work ok when I use the (still installed) earlier version of your launcher (the one where you have to press the centered line+circle for the all apps drawer)

Likely unrelated to the Launcher but maybe someone has an idea: GMaps used to show all information when using navigation in PiP. Not any longer, it now shows a simplified screen that e.g. lacks lane info etc. and once you arrive at the destination the PiP goes green and I have to open GMaps properly to get rid of that. I guess it came through a GMaps update - and am just wondering whether someone has a solution.

Thanks much! And sorry if this has been discussed earlier, haven't spotted it then...
[FYT Android Head Units] surfer63:
Your apk seems OK and the xml centrainly is, but that is all I can check.

I took the launcher34 from post #294 and removed the RelativeLayout from the custom widget com.syu.custom.MusicWidget. => removed version

Then I took the original and added the android:visibility="gone" statement to the relativelayout. => gone version.

You can try both.
[FYT Android Head Units] khangozzy:
What is the different between the "gone" and "removed" apk?

Are they all based on launcher34 form post#294?

In the "removed" apk, are you remove the stock com.syu.custom.MusicWidget instead of Ubiquity com.jackthakar.musicwidget ?
[FYT Android Head Units] surfer63:
some elements are really necessary for a launcher to be able to work, you can't remove them. Then you have two options:

android:visibility="hide" and android:visibility="gone". The first option hides the element, but it still takes the x and Y pixels space on the screen. The second hides it and takes it "out" of the layout so that other elements can take that x-y space.

No. In the removed version, I removed the com.syu.custom.MusicWidget with the com.jackthakar.musicwidget.

The right part is a scroll view with Ubiquity widget, radio, standard music widget. I removed the top Ubiquity widget.
[FYT Android Head Units] khangozzy:
I tried to install both version by both normal apk and lsec script installation but no success.

After retrying several times I decided to install original launcher34 apk to see if it can replace the launcher34 in #294, it could and I have stock launcher34 back. Uninstall the Ubiquity widget using lsec went fine.
[FYT Android Head Units] surfer63:
And why is it not successful?

If you refer to the /dev/block//dm-2 message and the recovery message: This has been mentioned many times. They are not relevant.
[FYT Android Head Units] khangozzy:
I don't know why it wasn't success. The modded launcher34 PeaceOS with both music widgets still there after flashing lssec (tried with my own mod and your 2 removed & gone apk) or normal apk install. But it was replaced when I manually installed the original launcher34 apk.
[FYT Android Head Units] surfer63:
what was the content of your lsec? Did you remove the dalvik cache? If not, you will still se the "old" one.

If you install an apk normally, the android system takes care of removing the dalvik cache.
[FYT Android Head Units] khangozzy:
Do you mean the 8581lsec script? I had tried with 2 script below and no success

PeaceOS script

#!/system/bin/sh

# Mod launcher 34 PeaceOS

#rm -rf /oem/app/190001034_com.android.launcher34

cp -r /storage/sdcard1/lsec_updatesh/app/* /oem/app/

chown -R 0.0 /oem/app/190001034_com.android.launcher34

chmod 755 /oem/app/190001034_com.android.launcher34

chmod 644 /oem/app/190001034_com.android.launcher34/190001034_com.android.launcher34.apk

Launcher install script from http://fytfactory.mariodantas.com

#!/system/bin/sh

rm -rf /data/dalvik-cache/profiles/190001034_com.android.launcher34

rm -rf /data/data/190001034_com.android.launcher34

rm -rf /data/dalvik-cache/arm64/*190001034_com.android.launcher34*

cp -r /storage/sdcard1/launcher/* /oem/app

chown -R 0.0 /oem/app/190001034_com.android.launcher34

chmod 755 /oem/app/190001034_com.android.launcher34

chmod 644 /oem/app/190001034_com.android.launcher34/190001034_com.android.launcher34.apk
[FYT Android Head Units] surfer63:
This one is OK.
[FYT Android Head Units] khangozzy:
Already tried this one but didn't work :(
[FYT Android Head Units] khangozzy:
Flashed back the launcher at #294 , installed GoneMAD music player for Ubiquity widget and I am satisfy with this laucher.
[FYT Android Head Units] Gymnae:
Just installed this on a fresh MD Firmware and lost the Status bar completely. I had set it to 24hrs before. Tried to reinstall my stock SystemUI.apk from my vanilla backup, but it doesn't return.

I'm running a 2k screen on an FYT UIS7862s platform
[FYT Android Head Units] wooldogsinc:
Has anyone had success on flashing peace os on teyes spro or CC2 ?

Little worried about doing it.

Great project. Amazing.