yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] marjanoos:
I downloaded the archive v0.2 from Yandex but Windows Defender screamed about virus called Trojan:Win32/Spursint.F!cl when I tried to open the archive.

Anyone have experienced that?
[FYT Android Head Units] LLIyT_HuK:
Check with any third-party antivirus)

Home kaspersky and desktop malwarebytes do not see viruses there. I didn't put anything into it myself.
[FYT Android Head Units] surfer63:
Just to confirm. I just flashed your systemUI.

Both temperatures work fine. Left the outside temperature, on the right the CPU temperature.

I added one line to your script after the "#!/system/bin/sh" just to be sure.

#!/system/bin/sh
cp /oem/priv-app/SystemUI/SystemUI.apk /oem/priv-app/SystemUI/SystemUI.apk.org

In that case it is always easy to restore the original one.

Thanks!(y)
[FYT Android Head Units] Moldeb:
Mine is 1280x800 - is that a relevant blocker? Would think it's pretty much the same...
[FYT Android Head Units] taufikthexfader:
Hi All,

I just found an interesting fact about my 7862 headunit when I tried to update/merge my own AllAppUpdate.bin with the latest AllAppUpdate.bin from Joying (I just realized this was useless because PeaceOS has its own AllAppUpdate.bin)

My Headunit's original (and backed up) fyt.prop > fyt manufacturer id =31 and uuid =2.

Working Steps

1. When I Installed PeaceOS 0.2's AllAppUpdate.bin which contains its own fyt.prop (fyt manufacturer id =1)

2. No need to copy my original fyt.prop, only config.txt which sets ro.sf.swrotation=90

3. copy lsec6315update and updatecfg.txt (set test and twipe_all)

The installation was flawless..

How can this be? was the difference of fyt.prop id ignored?

Doesn't Working Steps

1. I tried to copy my original fyt.prop and config.txt alongside with PeaceOS 0.2's AllAppUpdate.bin which contains its own fyt.prop (fyt manufacturer id =1)

2. copy my own config.txt which sets ro.sf.swrotation=90

3. copy lsec6315update and updatecfg.txt (set test and twipe_all)

The installation was successful but failed to copy config.txt and ended bootloop...

So I do these instead

1. Flash to the latest @mariodantas 's MD Kernel with my original AllAppUpdate.bin

2. Flash Peace OS 0.2 AllAppUUpdate.bin (via working steps)

3. Flash the latest Peace OS System UI patch

4. Flash the latest Carlink APK

and still try to figure out why i failed to update/flash with my own fyt.prop..

Maybe I will try to update/merge the latest Joying AllAppUpdate.bin with PeaceOS AllAppUpdate.bin and see how that goes..
[FYT Android Head Units] desibawaji:
Amazing work by @LLIyT_HuK looks amazing much much better then other UI and launchers. The installation was a breeze and went fine but I am facing with still one issue I am not able to see google maps in the main widget. I went through all the options in the setting as well as the FrontApp but with no luck. I have attached an image for reference. Just and FYI I was also facing this with my previous launchers and want google maps on the main screen in one of the widgets. The first 2 images are after installation of PeaceOS and the other two are before the installation.

What should I be doing to get Maps on the main screen widgets.

Thank you
[FYT Android Head Units] Clandaries:
Try Teyes frontapp from playstore. Working on many FYT head units
[FYT Android Head Units] desibawaji:
Thank you, I updated the frontapp from playstore but with no luck. Same output
[FYT Android Head Units] Moldeb:
In Frontapp settings, click on fix PiP
[FYT Android Head Units] desibawaji:
Hi, I did that but it is not helping as a matter of fact it breaks the launcher as in when I press the home button a popup keeps appearing asking which application to use (once or always) as it the file type association is lost.
[FYT Android Head Units] LLIyT_HuK:
What for?

File usage priority goes to build.prop < fyt.prop < config.txt

everything you write in config.txt takes precedence over the other two files
[FYT Android Head Units] LLIyT_HuK:
What kernel are you using? Native? Try to take from Mario Dantas, in the latest builds this is often the main reason on m6 devices, they came up with some kind of workaround for working in Russian.

Also, you have already been offered the option to open FrontApp (F icon on the desktop), select the cards there and click restore.
[FYT Android Head Units] taufikthexfader:
So, theoretically can I just flash any AllAppUpdate.bin without my own fyt.prop as long as the config.txt is valid for my headunit?
[FYT Android Head Units] LLIyT_HuK:
Yes that's right.

If you wanted to specify the manufacturer's number in fyt.prop, then this can be done in the same way in config.txt
[FYT Android Head Units] taufikthexfader:
By only copy and paste what's inside fyt.prop into config.txt? now i see why the parameters are so familiar between them..

So..

Spoiler content hidden.

and..

Spoiler content hidden.

then if i want to flash any AllAppUpdate.bin, the safest way will be combining those two inside config.txt...

Spoiler content hidden.

All good?
[FYT Android Head Units] LLIyT_HuK:
usually no one bothers with this, the maximum adds only "ro.build.fytmanufacturer=" if an error appears in the statusbar
[FYT Android Head Units] surfer63:
Do NOT use frontapp on the newer firmwares/launchers. It does not work anymore and you need to use the Settings app.

Go into the Settings app: General-> Launcher app Setting.

Set it to Maps.
[FYT Android Head Units] desibawaji:
Tried it also no luck.
[FYT Android Head Units] LLIyT_HuK:
It does not work only on Mekede firmware for m6, they made some other principle of issuing a window. For the same reason, the system part "kernel" from them does not show a window on the old allappupdate.
[FYT Android Head Units] Moldeb:
@LLIyT_HuK as there was no answer I've tried. Using Launcher 6_3 and the newer SysUI, the only thing that goes wrong is placing the PiP like so

I'm not sure why as my extra 80 lines are filled between the PiP and the lowest button row. PiP comes up functionally but placed in the wrong place. I've hit Fix PiP in Frontapp and rebooted, no change - any idea before I give up?

I use this together with MD-Edition and @seb21 syu.ms.apk - had been using these before and guess they don't make a difference.

Thought about reinstalling without modded syu.ms.apk but if you tell me the issue is due to the resolution, I'll spare the time...

Edit: To exclude other causes, I've done a clean install - i.e. latest factory firmware (Joying), then your FW, no restore of any data, stayed with your original launcher

As expected it makes no difference so I suspect a resolution issue. Would love to use your FW on this 1280x800 unit (already have it on my other unit which is 1280x720).
[FYT Android Head Units] LLIyT_HuK:
Try again to apply the launcher in the system settings, window alignment often helps, but if the resolution is correct.

If it doesn't help, then choose the one you like and I will try to fix the window in it for you.
[FYT Android Head Units] Moldeb:
Thanks for your help! Just chosen the launcher again in system settings, no change.

Window alignment? How do I do it? Cannot drag the PiP and don't see anything relevant in Developer Settings.

My preferred launcher is the one with the big PiP and no car. Launcher 3_6 In think, the one in the first two screenshots above...
[FYT Android Head Units] LLIyT_HuK:
Install and select again in the settings. Should help.
[FYT Android Head Units] Moldeb:
You're a star! Unit has no network yet hence empty - but a perfect fit! Interesting to see this is hardcoded...
[FYT Android Head Units] LLIyT_HuK:
Initially, this launcher was for 1024x600 and 1280x720 resolutions, the window coordinates in the code were set for these two resolutions. If the launcher is used with a different resolution, then it uses window coordinates from 1024x600. And I did not change them, they remained from the base launcher. And now I changed it to similar 1280x720
[FYT Android Head Units] Moldeb:
Ok understand, yes 1280x800 is probably nothing Teyes has on offer...
[FYT Android Head Units] Moldeb:
One more question on the Launchers, Launcher3_6 in my case but probably relevant for the other Teyes launchers also: Is there any way to reorganize the apps on the main app overview? If I drag one, it wants to place it on the main screen but there's no space obviously. I cannot add a second screen (long press only offers background etc). I cannot change the order on the all apps view either...

Alternatively, is there a way to hide apps?
[FYT Android Head Units] LLIyT_HuK:
Nothing in the bottom bar can be changed or removed without interfering with the launcher code. On the right, 4 icons are customizable.

Probably soon there will be another launcher with more assignable icons and other goodies.
[FYT Android Head Units] Moldeb:
Ok so it's not about me being stupid here... there is no way to add further launcher screens either, correct? Then I'll simply wait. The main app drawer right now shows an app in the top row that the police should not see ;)
[FYT Android Head Units] LLIyT_HuK:
It is possible, but so far it does not work out so that it works normally)

If you find a working stock launcher with such capabilities and a PIP window, then send it and I will do it without problems.

While I come across either a window or a free addition, but not all at once.
[FYT Android Head Units] Moldeb:
I guess I won't find more, I'm just starting to use FYT launchers, used other launchers before (Agama, Vivid) and they were not tailored well enough to FYT so caused other issues. Your launcher is already much more usable!
[FYT Android Head Units] desibawaji:
Hi, Just installed the Bundle #1 and Bundle #2 by merging it into one package. The installation went fine. Bu the following is observed.

1) File Manage Disappeared.

2) EQ icon not showing up (Just a Black box)

3) When you pull down with two fingers on the top the Data Icon is showing up as just a white box.

Also with PEACEOS installed I am never able to get PiP working on the home screen. My launchers never display google maps. But if I use Vivid Launcher the same show up perfectly fine.

Thank you for all the hard work and contribution to the android HU community.
[FYT Android Head Units] LLIyT_HuK:
Friend, I don't understand what you've done

What is Bundle #1 and Bundle #2?

“Also with PEACEOS installed I am never able to get PiP working on the home screen. My launchers never display google maps. But if I use Vivid Launcher the same show up perfectly fine."

- Is the system part of the MD edition installed?

- Vivid does not display maps in the window, as such, but displays a picture from Google.
[FYT Android Head Units] desibawaji:
Apologies if I have caused any confusing. What I was referring to is Upgrade Bundle #1 and Upgrade Bundle #2 from @mariodantas site. Just a background on what I have done

1) Updated the MD Edition Firmware dated 2023-06-16

2) Updated the unit with PeaceOS. (FYI - I was ONLY able to boot only with Peaceos, no other AllAppUpdate.bin would work it gets stuck while booting).

3) Later on I updated the unit with the other 2 bundles as mentioned above.

Those observations reported after the above steps. The reason for me doing all this was that in the factory launcher home screen I was not able to get Google Maps in widget.

Also after downloading Vivid Launcher I am able to get Google Maps displayed.

Hope that helps in explaining the issue.

Thanks you
[FYT Android Head Units] LLIyT_HuK:
allappupdate.bin should be flashed by anyone, the problem is either with your flash drive, or with the file itself, or with the flash driver.

Start over. What device do you have? I need screenshots from the settings, where you can see the MCU version, resolution and processor. Also attach your config.txt from backup
[FYT Android Head Units] desibawaji:
Thank you for the reply, Here are the details and screen shots as requested.

Please note the file attached is a merged file as the name suggest. I have renamed it to config.txt during deployment of the firmware.

Just as an fyi my AllappUpdate.bin which was a backup taken using post#4 had a corrupted launcher which I have reconstructed again after removal of the corrupted file but did not help in restoring the original backup. Now I dont have a working copy of my factory backup.

As of now the unit is performing fine but I just wanted to use maps with other launchers on the main screen. Which currently is working only with Vivid.

Also the issue of the EQ icon being corrupted or shown as white box has been resolved. Not the EQ icon is being shown. Don't know how but I presume a couple of restarts should have solved the issue. But the Data icon in the images is still shown as a white box.

Thank you
[FYT Android Head Units] LLIyT_HuK:
0. I asked to give me information about MCU version, resolution and processor. But instead I received only internal, but 2 times)) with difficulty, but I was able to see the necessary information in the background.

1. Change the USB flash drive! Problems with installing and removing backups are precisely because of her!

2. Before installation, do not forget to format to FAT32 and unpack all files for flashing under Windows!

3. Use a normal native config, not the mess that you have now.

4. Be sure to use the updatecfg.txt file with the contents of twipe_all when flashing

5. If the window does not start after the above, change the 6316_1.zip file to an older one. Now the new system parts from Mekede display the window differently and don't work on older builds of allappupdate. I don't have an 8581A device so I'm not sure if that's the problem.
[FYT Android Head Units] surfer63:
Displayed is the correct word. You can't navigate in a Vivid launcher window.

If you use Google Maps in navigation mode in Vivid or one of the other "non-FYT" launchers (Agama/CarWebGuru/Etcetera) you only get the navigation intents like a big arrow (continue/go right/ go left / roundabout icon with which exit to take) and the instruction "After 500 meters ...".

In the modern FYT launchers and also in @LLIyT_HuK launchers you get the Google Maps displayed AND you get the actual navigation screen from Maps in "windowed mode". That is the big difference and huge advantage of the modern FYT launchers.
[FYT Android Head Units] LLIyT_HuK:
Gradually I spread different variants of templates for discussion. From that very 34th launcher, there were 7 options))
[FYT Android Head Units] surfer63:
Sorry. "Launchers".

I corrected my previous post.
[FYT Android Head Units] desibawaji:
Hi,

Thank you @surfer63 and @LLIyT_HuK for the response. I did a small test and changed config.txt and told it to use ro.build.fytmanufacturer=116 and bingo the Google Maps or Any Application defined like calculator pops up in all launchers which has the widget.

But if I change it to ro.build.fytmanufacturer=1 or 8 or 0 which is what @LLIyT_HuK default is or my default of 8 the maps don't show up but the yellow warning of mismatch disappears.

The ro.build.fytmanufacturer controls a lot of thing, when I set it to 112 the same software behaves completely different and even the unit name changes to ATOTO something... and the pull down bar from the top also changes icons and size.

I want to use MD Edition and PeaceOS but my main need is I want Google maps to be displayed. My MCU is NOR

I am attaching additional images for better understanding.

Thanks
[FYT Android Head Units] LielBachar:
Hello:)

First of all, I'm super grateful for your work, the interface, integration, and launcher are exactly what I would describe as the perfect setup for a HU.

I got an issue that was previously mentioned but I don't seem to understand how to fix it:/

The FrontApp doesn't seem to work for me.

My HU information is attached below.
[FYT Android Head Units] desibawaji:
Hi,

I am also facing a similar issue. Can you see the post just above you. I would like you to try just a small test and add the line ro.build.fytmanufacturer=116 to your cofig.txt as see if it works and provide an update. I am sure this will help @LLIyT_HuK to understand the issue.

Thanks
[FYT Android Head Units] louforgiveno:
Is there any way (with the fyt launchers) to assign the music widget to control a specific (3rd party) music player? I'd like it to control poweramp (so i won't need to use an icon launcher space for it)

Thanks
[FYT Android Head Units] surfer63:
No, not the FYT widget itself. You really need something like the Ubiquity "universal media" widget. And that is part of the Launcher(s) of PeaceOS.
[FYT Android Head Units] LielBachar:
Yes sir, will share an updated in no time

Update: I used the manufacturer update script to change from 1 to 116.

Checked the fyt.prop file and the "ro.build.fytmanufacturer=" disappeared

What the hell
[FYT Android Head Units] desibawaji:
I have updated some additional details for the previous post...
[FYT Android Head Units] LielBachar:
I think it wasn't that clear i guess, my HU root/oem/app/fyt.prop the line "ro.build.fytmanufacturer=" is totally gone.

Anyone with an explanation or a fix:(?
[FYT Android Head Units] surfer63:
That is has disappeared from your fyt.prop doesn't mean everything. It can still be active.

Please open a teminal (install one if necessary) and do a

getprop | grep manufacturer

and see what is displayed.

If that is too difficult, download my HWGetInfo.apk and run it it. It will immediately show the fyt* properties.

And otherwise use an lsec script and copy a correct fyt.prop back to your /oem/app
[FYT Android Head Units] LielBachar:
Ran a script but still can't tell :/ (SPRD??)
[FYT Android Head Units] surfer63:
The property has indeed disappeared.

But what did you put inside the 7862lsec.sh script?

How did you change the line sed -i "25i ro\.build\.fytmanufacturer=999" /oem/app/fyt.prop ?

Did you really change the 999 to 116?

And which editor did you use?
[FYT Android Head Units] desibawaji:
@LielBachar no need for a script or anything just use Notepad++ and add a line ro.build.fytmanufacturer=116 to your existing config.txt.

Copy the config.txt on the USB along with the file lsec6316update and just plug it in. The USB should contain only two files 1) config.txt and 2) lsec6316update.

No need to update fyt.prop what I have seen is config.txt take precedence over fyt.prop and as a matter of fact my current config.txt contains what config.txt properties as well as as fyt.prop setting/properties and it is working fine.

If I want to try any property all I do is add/change it in config.txt and plug the USB in with lsec6316update and it works fine.

@surfer63 @LLIyT_HuK as per you expertise please can you kindly provide a workaround as to why ro.build.fytmanufacturer=116 displays google map but

ro.build.fytmanufacturer=8 or 0 or 1 does not work.

@LielBachar please post your output result after setting it to 116.

Thank you
[Motorola Edge 20] empy16:
I'm having a weird issue with a phone that I'm otherwise completely happy.

The screen feels too sensitive to the touch, which in turn makes pretty difficult to type quickly or results in many accidental presses.

Running the latest Lineage OS 20.0.

To reproduce:

Open keyboard, and hover your thumb over a key. SLOWLY move it closer to the screen where it's touching lightly. You should get ridiculous key spam, like a full row in 1 second.

Possible issue:

It appears that the 'finger' area required for a touch to be registered is too small

What I've tried:

Disabling haptics, different keyboard, changing "Cursor speed", a Magisk module that was supposed to add touchscreen sensitivity control.

Any pointers are very welcome, thank you!
[Motorola Edge 20] Username: Required:
I can recreate this as well. I don't really see how it could be a problem. I don't get accidental touches, in fact I find that the screen isn't sensitive enough and sometimes it doesn't register touches. The phone had a touch problem in Android 11 where it wouldn't register touches and I guess the devs tried everything they could to fix a display that was just too garbage to be saved anyway, so now we're stuck with how it is. I guess you could try a GSI with open source drivers that you could edit yourself since the drivers we have are closed source and the custom ROM devs (which should know better than anyone else) told me they couldn't fix it since they didn't have access to the drivers.
[OnePlus 9] AutruiP:
Hi,

I've tried to flash a new magisk-boot img, following this guide, after downloading the signed flashable zip LE2113_11_F.75.

I've patched the boot.img with my magisk app, and after flashing it,my OnePlus 9 doesn't boot anymore.

I've got this error : QUALCOMM CrashDump Mode. dm-verity device corrupted. verity-ctr

I can't boot to TWRP, I tried a fastboot boot and a fastboot flash recovery, but I always get a Qualcomm dump error.

Can someone help me to fix this issue ?

Thanks !
[OnePlus 9] Creepergames360:
this refrence might help-

https://xdaforums.com/t/help-needed...-magisk-upon-upgrade-to-android-[__].4347295/

"The update to [Insert Version Here] does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to [Insert Version Here] is finished though, so you can still have root.

In your case manually upgrading to [Insert Version Here], letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc"
[OnePlus 9] AutruiP:
Hi, thanks for your answer.

I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.

I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.

I've managed to boot on TWRP using this one for the encryption support.

I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.

I've tried to flash the signed flashable zip in TWRP, and got this :
[OnePlus 9] TheNewHEROBRINE:
It's not a problem if one slot is broken, it will probably fix itself on the next update.
[OnePlus 9] AutruiP:
Hi, thanks for your answer.

The fact that you talked about the next update made me try to locally install the update with the signed flashable zip, using the system updater. It worked and fixed everything !

Thanks :)
[OnePlus 9] Levi4cyber:
Thanks.
[OnePlus 5T  Questions & Answers] maitree4:
I recently landed in USA from India. My Airtel SIM was working fine and registered to T-Mobile network.

I purchased mint mobile line and both Airtel and Mint were working fine.

Somehow I was not able to connect to Hotspot so I called up Mint mobile customer and they asked to reset network settings.

After that My phone stopped detecting Airtel T-Mobile network (Mint works fine).

I formatted my one plus 5T still its not registering to any network (even manually I tried).

Is there anyway to get India Airtel APN or other network settings back ?

Note :

My SIM works fine in other mobile which still has india settings. Something wrong happened with my mobile after Mint customer cares advice.

There is recharge in SIM and is active.
[OnePlus 5T  Questions & Answers] mjk7774:
I am facing same issues too
[General Questions and Answers] ju76:
Hi

is it posible to modify a windows auto/windows automotive device?

the firmware can be downloaded at this location for example:

http://www.pioneer.eu/eur/content/support/support/upgrade/AVIC_F900BT_F700BT.html

kind regards

ju
[Realme GT Neo 2] alexwhitney845:
Guys, wanna try pixel experience in my gt neo 2, but I couldn't find it anywhere. Can anyone make it easy to me and share the download link pls? i'd be grateful
[Realme GT Neo 2] traman124:
There is no GT Neo 2 build of Pixel Experience right now.....

You might be able to use this GSI guide to install Pixel Experience GSIs (not official, but they are on GitHub) to get PixelExperience on your phone.