[AOSP 11.0] [2020-11-27] LeOS - ungoogled GSI - Treble-Enabled Device Development A/AB ROMS

Hi all,
I have created a GSI based on latest PHH AOSP Android 11
What is LeOS:
1. It's full ungoogled
2. It includes full Working MicroG
3. It includes Seedvauld
4. It includes SimpleGallery, SimpleContacs, Silence, Telegram, F-Droid, Jquarks, K9, DAVx5, OpenCamera, ASK, TotalLauncher
5. available as arm64avS, arm64avN, arm64bvS, arm64bvN
6. no google Apps will work !!!!
You can download latest release at https://leos-gsi.de/downloads
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=com.kevintresuelo.treble . Don't use other Treble Check apps, they'll give wrong informations.
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Join us a telegram group for support: https://t.me/LeOS_Support
Short overview: http://leos-gsi.de
November 3rd 2021:
from November builds on LeOS-R base will swap to Linage18.1.
November: 30ten 2021:
from December on LeOS-R will include AuroraServices

RESERVED

Download takes you to a login page with no option to register.

Vulnerability said:
Download takes you to a login page with no option to register.
Click to expand...
Click to collapse
For Username and Password try LeOS
I found the login info via Telegram.

Are you planning a real ungoogled version without microg?

Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation

forart.eu said:
Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation
Click to expand...
Click to collapse
I think a gsi would be a better option to let users try this os before asking for a full porting to \e\ foundation.

works on Huawei P10lite

forart.eu said:
Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation
Click to expand...
Click to collapse
The bad thing on eOS is, that it'S not uptodate. That's why I have created LeOS

ushilives said:
For Username and Password try LeOS
I found the login info via Telegram.
Click to expand...
Click to collapse
This is changed. No special login needed anymore

harvey186 said:
The bad thing on eOS is, that it'S not uptodate. That's why I have created LeOS
Click to expand...
Click to collapse
Are you planning to build a LOS degoogled by default? I really like your work but I want avoid every connection with Google and microG still has some connections with it.

eltanque9 said:
LOS degoogled by default?
Click to expand...
Click to collapse
I'm building from time to time an ungoogled LeOS-Q version, which is based on LOS17.1.
But my main work is building an ungoogled LeOS-R which is based on AOSP

Thanks for your precious share @harvey186
i tried to install Leos on my OnePlus Nord AC2003 (avicii), by following this guide
https://community.e.foundation/t/gs...note-9pro-with-super-partition-and-root/22648
but got the Qualcomm crashdump mode after finishing install and reboot.
Official LOS17.1 is working however, and now i'm trying to build an unofficial eOS build, but would love to have your LeOS working.

getthiswork2 said:
Thanks for your precious share @harvey186
i tried to install Leos on my OnePlus Nord AC2003 (avicii), by following this guide
https://community.e.foundation/t/gs...note-9pro-with-super-partition-and-root/22648
but got the Qualcomm crashdump mode after finishing install and reboot.
Official LOS17.1 is working however, and now i'm trying to build an unofficial eOS build, but would love to have your LeOS working.
Click to expand...
Click to collapse
Have you tried LeOS Q or LeOS -R ?? Which Android version (Pie or Q) was installed on your device ? Are you using OEM vendor or from a custom rom. Most issues are from not using OEM vendor sources.
We have one user which have installed LeOS on a AndroidGo device successfull
for better support, visit the LeOS community here
LeOS — NO GAPPS WILL WORK
Deutsch/englische LeOS support Gruppe. ACHTUNG: KEIN OffTopic erlaubt. Wer dagegen verstößt wird entlassen ————————————German/English LeOS support group. ATTENTION: NO OffTopic allowed. Whoever violates this will be fired
t.me

I tried LeOS R 20210106-RW-bvS.img.xz 2021-01-09 11:13 686M
My OnePlus Nord is delivered with Q (Oneplus 10.5.10 for the moment), and i think i'm using OEM vendor, since i haven't modified anything else.
From my understanding, it's an ARM64 A/B device, is the RW-bvs the correct ROM to use ?
Can you please tell us what's the meaning of RO RW avs avn bvs bvn ?
Thanks

OK, first a stupid question: You have decompressed the xz file ?
Why have you used such an old version ? Please try the latest. Yesterday I have uploaded a new set of GSI.
RW means system partition is write able. It's for people which want modify anything on /system.
RO means that system partition ins not write able. But all about versions you can find https://leos-gsi.de
Normally this way should work unlocked Q devices:
>adb reboot bootloader
>fastboot devices
>fastboot reboot fastboot
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
>fastboot reboot fastboot
>fastboot erase system
>fastboot reboot fastboot
>fastboot flash system LeOS.img
>fastboot -w
>fastboot reboot bootloader
>fastboot erase userdata
>fastboot reboot
if stuck in bootloop
>reboot in TWRP
>flash permissiver.zip
>reboot system

Great idea creating the ungoogled ROM! But it seems to be on the alpha stage yet, as I'm experiencing many issues after installing it to my Redmi 7A 3/32:
1) Screen is blinking sometimes, also brightness slider works very weirdly..
2) On initial load when opening location settings it crashes
3) When in battery saver mode the notifications indicator light constantly blinking and there's no setting to turn it off
4) Many apps have issues accessing SD card or even internal memory, so it makes them impossible to use (like apk downloaders, music players)
5) Contacts and calculator apps are missing, had to install additionally
The rest seem to be fine, the great thing is that all Magisk modules I use (Xposed, ViperFX, Dolby Digital) are working flawlessly!
To sum up - great work so far, but still requires a lot of polishing. Good luck!

Always make sure your system partition is big enough when installing. Apps missing or settings tabs not working correctly are symptoms that gsi did not install correctly.

thx, but I think it's more than a beta status.
to your issues:
1. it's a know issue of your device. On other devices it works as it should.
2. Seems you using an older version. It's fixed since January versions
3. Do you using OEM vendor? And which Android OEM version are the vendor sources ? A9 or A10?
4. Are you using FOSS apps ? Or Apps from Play Store ? Normally all apps have access to externalSD. You have to allow it. That's a A11 feature
5. You will never find a ROM or GSI wich has all apps you need. Most peopel are using the mini version because they don't want any default app.
I think you should try the latest LeOS from yesterday with the latest OEM vendor sources.

Sorry, i think you're confusing me with the user above me. Was just trying to help... I don't have this gsi installed

IamTheBRAVE said:
Sorry, i think you're confusing me with the user above me. Was just trying to help... I don't have this gsi installed
Click to expand...
Click to collapse
No, it was a helpful hint. That's why I have liked it

Related

How to Treble without lost your mind

Hello I write this post to try to asnwer all your questions so I will updating when i get more free time here you go!.
First, we have now fully treble rom (sources can be released soon don't worry).
after this I write some know questions and answers I hope it help us to kill all the doubts
Q&A
Can I flash MIUI oreo in treble build?
No, MIUI doesn't have GSI rom
[*]I can't flash Gapps in GSI how can I fix that?
Well do this, Go to TWRP, Wipe option and go in advance wipe option then select system and tap in repair o change file system
see the screenshots
https://imgur.com/a/NuuuR in the url.
Or flash GSI with Gapps incluided
Which version of PHH's treble rom is compatible with our device?
You can use A Only ARM64
[*] My camera take time to open in GSI roms what is the problem?
Well since we need some libshims they aren't incuided in GSI so the camera takes time open due to the camera daemon take time to be initialized correctly and released from the system calls.
How can I install a treble rom, im in (miui, aex , los, pixel experience, or any other not treble build)
Well some guy writed a tutorial so I link you here: How to install Treble xperience
[*] How can I install treble PHH's rom?
You can use one of this 2 forms:
You can download the system.img then Open CMD (in windows) or Terminal (in Linux) (First of all you must have minimal adb (in windows) or have installed the android tools in linux) If you have it, continue reading, if not, read below that I leave as install
1.- (thermianl or CMD) in the directory where you have the system,img and write For example
Code:
fastboot flash system system-arm64-aonly-vanilla-nosu.img
then reboot to your recovery and wipe data factory reset.
2.- Go to Your TWRP wipe data factory reset
Copy system-arm64-aonly-vanilla-nosu.img inside your internal memory then go to install option and select image and search the image and selec system in the menu and swipe
Reboot and enjoy!.
You are here if you haven't installed the adb and fastboot​Windows:
1.- Download minimal adb from here: https://forum.xda-developers.com/showthread.php?t=2317790
2.- Execute the exe and is all.
Linux:
1.- Open a Linux terminal (this is for debian based and debian hahaha (like ubuntu, kubuntu, Linux mint etc)
2.- Write in the termianl:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
and is all XD easy no?...
I will write more soon.
Good flashing.
reserved idk
Cool tuto
How to flash to miui from treble
HoganSam123 said:
How to flash to miui from treble
Click to expand...
Click to collapse
Via fastboot I think ?
I read about treble support and able to understand it just on paper but on actual usage i'm still blank. I wanna ask how is it helping in our device (land) case and could we get android p beta running as flagships having treble support can run latest android p beta images.
kamalpreetsingh said:
I read about treble support and able to understand it just on paper but on actual usage i'm still blank. I wanna ask how is it helping in our device (land) case and could we get android p beta running as flagships having treble support can run latest android p beta images.
Click to expand...
Click to collapse
yup ,i wanna know it too.
Can i flash normal roms over treblized rom?
The_CelldWeller said:
Can i flash normal roms over treblized rom?
Click to expand...
Click to collapse
Yes but you need to do a clean flash... including system+data+vendor+dalvik+cache.
NaYaB786 said:
Yes but you need to do a clean flash... including system+data+vendor+dalvik+cache.
Click to expand...
Click to collapse
Thanks. It worked.

[SM-T825][UNOFFICIAL] 20180911 Treble Project

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate partition, with enough space (about 450mb) to place the whole vendor there.
As a result, I created a solution and tried to make it as much easy as possible for daily use.
I created 2 files - system.img/vendor.img as ext4 images and put it in to the system partition. And then on early init I mounting real system partition as /system_src and then mount system.img as /system and vendor.img as /vendor.
Also I created twrp treble's version for easy use /system and /vendor. It's can wipe new system\vendor partitions, you can restore images to system/vendor in the same way, as we use for boot/recovery.
How to
Prepare - need only once
1. in the current twrp make full wipe (at least we need clean /system, because later we fill all /system by 2 files: system.img/vendor.img)
2. you need flash my twrp with treble support (sm-t825-twrp_3.2.3-0_treble.img): https://drive.google.com/file/d/1GJMrHI4wkePXh8JmF_jgxBSly38B5tu1/view?usp=sharing
3. flash zip with new system.img/vendor.img as ext4 images: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Installation
1. download treble zip from Links and flash it as usual zip. It will flash boot.img and /vendor partition (this is part, specific for our tablet only)
2. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development, if it not a .img file - extract it, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
3. some images require vendor's modification, in oreo some firmware has a 90 rotate, some 270, in my treble zip 90, if you see - image rotated on 180 - flash zip from Additional Links
4. if you wanna back to original lineage\rr without treble - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Known Issues
sound 2 skeakers only for now
fingerprint
keys light dnw on some firmwares
Links
2. 20180911: fix rotate, back to stock sound (fix bt, quad speakers): https://drive.google.com/file/d/1e_mzosWYL7bv29n613OKZpvSZPXMh26k/view?usp=sharing
1. 20180802: initial treble: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Few notes about item 2: your tablet has wrong image orientation, panel horizontal, sensor - vertical, as result troubles with show right image in right orientation. In 7.0-8.1 this problem was fixed by adding ro.sf.hwrotation=270 in build.prop. For pie this way dnw. Google remove this option and update configstore with new ISurfaceFlingerConfigs. It was added new method: primaryDisplayOrientation. Problem was in adding new configstore sources in the 15.1 sources. Finally I had successfully builded configstore 1.0/1.1 from 16.0 in 15.1.
Additional Links - need only for some oreo images, if image rotated on 180
2. 20180911: https://drive.google.com/file/d/1S4mvXFcX-d2xoZEp9b9dG3ywUhybT6U2/view?usp=sharing
1. 20180802: initial fix rotate: https://drive.google.com/file/d/1JKGu7vudrU0bJPEdkGwBVFkyCJpsHLLs/view?usp=sharing
Magisk
For some reason original Magisk dnw with our treble. It's somehow connect to sepolicy and I'm almost sure about it connected to our treble way with loop0/loop1 mount.
Finally I made small update of the original latest Magisk and it's working. Only one thing was done by me: inside zip in the binary magiskinit file I remove seclabel (seclabel u:r:magisk:s0) for magisk services.
Fixed 17.1 Magisk beta: https://drive.google.com/file/d/1lMhM8ceaJoy5pHRHjCsxxG2C9e5sB5Ot/view?usp=sharing
17.1 Magisk beta manager (this apk also inside Magisk, but cann't be installed automatically during Magisk install), install it as normal apk after install Magisk: https://drive.google.com/file/d/1qCoVPUxvvxopCGfIpoHdAnKueNIxMXal/view?usp=sharing
GApps
https://opengapps.org
Almost all firmware say about wrong vendor version. This is normal, just press OK.
Checked firmwares
AospExtended (need rotate 270 patch): https://forum.xda-developers.com/pr...evelopment/rom-aospextended-rom-v5-5-t3797509
Cosmic-OS: https://forum.xda-developers.com/pr...ment/cosmic-ospulsar8-1-0201805243-2-t3794806
DroidOnTime: https://forum.xda-developers.com/pr...pment/official-droidontime-dotos-2-x-t3794338
Havoc-OS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Lineage: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
OmniROM Treskmod (need rotate 270 patch): https://forum.xda-developers.com/pr...development/rom-8-1-omnirom-treskmod-t3818188
Pixel Experience (it's requere register custom firmware): https://forum.xda-developers.com/pr...e-development/8-1-0-pixel-experience-t3796011
Resurrection Remix: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
let's experiment together!
Wow! Man, you rock! My Favourite dev! Thanks for Your hard work!
Thanks for this. One question, do we use A/B or A images?
Peeps1513 said:
Thanks for this. One question, do we use A/B or A images?
Click to expand...
Click to collapse
Forgot: system a only
Valera1978 said:
Forgot: system a only
Click to expand...
Click to collapse
And what did You think about the bugs You have mentioned? (Fingerprint, deepsleep, speakers) Fixable or not?
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Valera1978 said:
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Click to expand...
Click to collapse
Really appreciate your work :highfive:
Nice project. Good stuff.
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Peeps1513 said:
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Click to expand...
Click to collapse
Yep. I've tested treble but no sucess atm for me. Better stay with non-treble lineage, as most of the things work just fine. Maybe in future if Valera fix some things on treble bulid (if ever). Hope Dev focus on oreo lineage than treble project (which is good stuff, but not good enough as daily driver)
I want to leave a feedback after almost a month with treble roms
I have to change my mind: treble is fantastic! Such a great thing, very helpfull for all of us. I was running Valera's lineage 15.1 as daily driver for about 2 months.
In regular non-treble bulid almost everything work. Bad thing were performance (slow animations) and not working deepsleep.
I was happy but not at al. That wasnt this what i was looking for. Then i found again this thread and again give a try (longer) :fingers-crossed:
I am running now treble omnirom for few weeks. Worst things i find is: magisk did not work (very sad, tried multiple versions with no luck, other users report magisk is working for them) and my bluetooth headphones arent working (probably our side bug too)
In plus: no random reboots, performance is very good, no slow downs, deepsleep problem almost gone (drain 6% overnight connected to wifi)
Didnt find any other bugs
I am really happy now. It would be exelent with magisk and bluetooth audio working
Great job, i stick with treble for now :laugh:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
imder said:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
Click to expand...
Click to collapse
Work only with T825
Any updates Master?
@Valera1978
Could you PLEASE make this for us left out t820 owners???
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
You better wait for Pie relase. Valera is working on it.
suzook said:
@Valera1978
Could you PLEASE make this for us left out t820 owners???
Click to expand...
Click to collapse
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
I'll update non-treble build soon. And treble too. During working on treble I had fixed some stuff, like hexedit finger libs to remove shim lib. But I need fix audio in calls again first.
About pie - I dont see any reason to start work on it right now, it's too early, it still has a lot of problems. Better spend this time to make something cool - may be even make samsung port from note 9 or tab s4 with dex and some stuff.
But if you don't want use treble (I agree, it's may be too complicate with special twrp and additional partitions), I think I can prepare integrated pie system images with simple flash without any additional manipulations, like you flash lineage.
Valera1978 said:
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
Click to expand...
Click to collapse
Man, if you would be somehow able to build a unified or a separate treble rom for 820, you would be the greatest man on xda! Cause we have no support for 820 anymore...

[Project Treble][SM-T580][SM-T585] 20190401

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link below
2. flash treble zip
3. download any system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development and flash it as system image
Known Issues
1. need fix gps on SM-T580
2. in aosp 9.0 phh image build-in camera app crashed, all other working fine
Notes
- This is treble build, based on latest lineage 16.0, latest 3.18.137 OC kernel (thanks @followmsi) (with mac fix and 4.0.10.205 wlan driver from codeaurora project) and latest device\configs.
- for /vendor partition I use /cache (it's about 209mb, it' enough for our vendor)
- for /cache partition I use /hidden (it's about 50-60mb, it' enough for cache)
Links
Treble images
SM-T585:
1. 20190401: https://drive.google.com/file/d/1BsmyMb7hI-xYZhIj1XqLNpkfNI9kjDxa/view?usp=sharing
SM-T580:
1. 20190401: https://drive.google.com/file/d/1nQciZhBq_2BnyxbHcP4JuDDA22wUfbzW/view?usp=sharing
Root
Use Magisk if need
Recovery
SM-t585:
1. my repack with add /vendor: https://drive.google.com/file/d/1kEQ-Wwee9MYrF5i69EII8p8R_lOwwf-O/view?usp=sharing
SM-T580:
1. my repack with add /vendor: https://drive.google.com/file/d/1wB665QMq6yesKaMteHQGrmdBAKvkHo0Y/view?usp=sharing
System images
A only and 64Bits
Checked firmwares: almost all pie roms from treble's thread should work. Checked aosp, pixelexperience, arrow, havoc.
Sources
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870/tree/lineage-16.0_treble
Device tree SM-T585: https://github.com/Valera1978/android_device_samsung_gtaxllte/tree/lineage-16.0_treble
Device tree SM-T580: https://github.com/Valera1978/android_device_samsung_gtaxlwifi/tree/lineage-16.0_treble
Vendor SM-T585: https://github.com/Valera1978/android_vendor_samsung_gtaxllte/tree/lineage-16.0_treble
Vendor SM-T580: https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi/tree/lineage-16.0_treble
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
twfs said:
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
Click to expand...
Click to collapse
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
BT audio does not work in all treble firmware
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
thenubknownasepic said:
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
Click to expand...
Click to collapse
I'm guessing that it will happen when your custom ROM is on a different build number from the underlying official build.
Whatever it is, I think you can just ignore it - as long as both are up-to-date, you should encounter no actual errors.
The mismatch is probaly between the build fingerprint mentioned in the build.prop file in the system partition and the build.prop file in the vendor image, specifically the ro.vendor.build.fingerprint key.
RichyE said:
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
Click to expand...
Click to collapse
I dont know about the headphones, but i have the same problem with audio always at full volume rr gsi
hi how r u
is there any problem with havoc 2.9 please?
any bugs?
Thanks @Valera1978 for this Treble implementation. I am a huge fan of Treble, as it opens a wide range of ROMs to this tablet. Do you continue development on it? It seems come to a stop?
There is another Treble implementation for this Exynos, this is for Galaxy A3 2017 (A320FL). Maybe that can help.
Please could you make a version that supports AB system images?
@Valera1978
Does it support Android 10
this project supports android 10 can someone tell me please
@Chris_0147 the project is dead, you'd better to sell the device. i'll do that also. it's too old and no developer wants to develop anymore something for it. i tried any a10/a11 gsi rom, all are not supported.
I've been looking at previous comments ,OK , I understand it doesn't support 10 and 11 but has anyone tried installing Pie and then upgrading to 10 or 11.
Nope
You can try and tell us
Chris_0147 said:
You can try and tell us
Click to expand...
Click to collapse
Very helpful, I was hoping for something more constructive

[ROM][12.1][UNOFFICIAL][wt88047x] LineageOS 19.1

Important information:
This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
SELinux Permissive
Encryption
Connecting to some Bluetooth Classic devices
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool. It is highly recommended to flash it using ADB sideload.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to tipzrickycheung
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@tipzrickycheung, @althafvly, @nicknitewolf, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Reserved
New update!
20220218
- Fixed Bluetooth
- Baseband and IMEI now detected
Download
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
Yup, I am on Coolapk
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
About the expansion zip, you need to have the stock partition layouts to start with.
New update!
20220219
- Fixed LiveDisplay
- Added SEPolicy Changes
- Added Binder and lmk kernel backports
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
I'm just popping in to say this looks very promising! Thanks for caring about this device. Please don't give up with this build
New update!
20220227
- Fixed Hotspot (Can be fixed for 18.1 too)
- Software navkeys now works properly
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
BangJhon.id said:
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
Click to expand...
Click to collapse
Use the partition expand package first
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
I think I might have fixed bug 3, will push an update when appropriate.
one by one step i try, no fixed this message, from recovery all path, partisi, i not working instal lineage os based 19.0
New update!
20220228
- Fixed TimeKeep (?)
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
RandomNewbie said:
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
Click to expand...
Click to collapse
No, and we don't support using that tool.
tipzrickycheung said:
Use the partition expand package first
Click to expand...
Click to collapse
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
SaneComputing said:
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
Click to expand...
Click to collapse
Update your TWRP.
New update!
20220323
Android 12L!
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Still using latest twrp but error show up everytime

[CLOSED][ROM][12L] LineageOS Special Edition SE F1 [11/05/2022]

Moderator Announcement!!​
Just wanted to finally put an end to all the drama of the past week concerning accusations regarding RD side and RC and Translator Retrial. Whether these accusations stemmed
from outside platforms such as TG, or from within XDA itself, calling these Recognized members such things as: "racists, kangers, or scammers" are completely
unfounded, unsubstantiated, and unwelcome on XDA plain and simple!! As a result of all this drama, this thread shall remain closed!
If you have a disagreement with these members in good standing with XDA, or with any other member for that matter, please report these matters to the Moderator Staff,
or at least contact the member via PM to state your grievances. Posting unsubstantiated personal attacks on the public forums in any section will be removed with immediate effect
as per XDA Rule 2.4:
Spoiler: XDA Rule 2.4
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
I thank you all for your cooperation, and wish everyone a pleasant day.
-Regards: Badger50
Senior Moderator
LineageOS+
brought to you by the SyntaxError
DISCLAIMER
I am not responsible for any damage you made to your device.
You have been warned!​
FEATURES
Based on Official LineageOS 19.1 - Android 12L
Encrypted by default
SafetyNet pass by default
microG support
4G instead of LTE
crDroid Keyboard by default
Unlimited Google Photos
One Handed Mode
Few Status Bar and Battery icon customizations (to be added soon...)
Latest Firmware included in ROM (to be added soon...)
DOWNLOADS
ROM:
GApps: NikGApps / FlameGApps / MindTheGApps (Your choice)
Recovery: Official TWRP Recovery / LineageOS Recovery
DFE: Disable Force Encryption
Root: Magisk
FLASHING INSTRACTIONS
Note: ROM is encrypted by default!
First Time - Clean Installation:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, ROM, LineageOS Recovery, GApps of your choice, DFE (optional), Magisk (optional).
Create one Folder in your PC and move all the files you downloaded there.
Reboot to Fastboot Mode.
Connect your device to PC and Boot into to TWRP via ADB:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Once you booted in TWRP and while you are there, transfer the TWRP.img you downloaded.
Now press Install Image, find and select the TWRP recovery and flash it to Recovery section.
Go back and Reboot to Recovery.
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash ROM > Gapps > DFE [Optional]
[Optional] Go back and press Install Image, find and select the LineageOS Recovery and flash it to Recovery section.
[Optional] Flash Magisk.
Done! Reboot to system.
Update via TWRP:
Reboot to TWRP
Flash ROM updated.zip > DFE [Optional] > Magisk [Optional] > Wipe cache
Reboot
Update via LineageOS Recovery:
Reboot to Recovery
Navigate to Apply update and choose from adb (if you have Lineageos.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload Lineageos zip
Code:
adb sideload Lineageos.zip
POCO F1 ULTIMATE COLLECTION AND GUIDES
You can find everything you need in POCO F1 Ultimate Collection & Guides by Retrial.
SOURCE CODE
Device tree source code
Kernel source code
CREDITS
bgcngm - Official Sources
SyntaxError - Main Developer
Retrial - For his amazing ideas, making the thread and support
Silent_eyes For being always there to help and making this project possible
TioCareca- For his support and help
LineageOS Team
Crdroid Team
JDCTeam​
Changelog:
11/05/2022
Updated to May security patches (android-12.1.0_r5)
Replaced crdroid launcher to lineageos launcher
AutoBrightness: Add support for one shot auto-brightness
Settings: Add preference for one shot auto-brightness
Fix divider color for dark theme
Fix auto brightness not working for some users
fingerprint: Setup dimming & fp press notifications
EmergencyInfo: Allow adding contacts
Add support for toggling taskbar
SystemUI: Add back charging ripple
Reserved.
thanks!!!!!!!!!!!!
carry on
silent_eyes said:
carry on
Click to expand...
Click to collapse
Thanks building another version with safety net pass by default and few other changes.
Oh yeah...!!!!
Can anybody say about daily use....?
Any important problems....?
Thx...a lot for testers words....
pimmelbingo said:
oh yeah for me not working BOOOOOTLOOOOOOOOOOOOOOP
Click to expand...
Click to collapse
i think you must format all ....
flash latest xiaomi firmware....
and twrp, dfse....and so on....
pimmelbingo said:
yes bootloop!
Click to expand...
Click to collapse
THX for information, and maybe wasting time...
Garfield3333 said:
Oh yeah...!!!!
Can anybody say about daily use....?
Any important problems....?
Thx...a lot for testers words....
Click to expand...
Click to collapse
All good for me, very stable for now
pimmelbingo said:
oh yeah for me not working BOOOOOTLOOOOOOOOOOOOOOP
Click to expand...
Click to collapse
You must have done something wrong follow flash instruction, no boot loop here BTW you can see from the screenshots proof enough?
How can I root this pocophone?
I've tried everything, this one keeps popping up
I don't know Chinese how to get through it? I realized that the device is locked. I bought my phone on banggood, legally.
I have never done this before
uduro said:
How can I root this pocophone?
I've tried everything, this one keeps popping up
View attachment 5552369
I don't know Chinese how to get through it? I realized that the device is locked. I bought my phone on banggood, legally.
I have never done this before
Click to expand...
Click to collapse
Check the Unlock Bootloader Guide at my POCO F1 Ultimate Collection & Guides thread.
So ive finished my Poco to Los 19....
Magisk 24.1 works, Banking app with safety net on Magisk works,
TWRP with twrp-3.6.0_9-0-beryllium.img works......
i can say all works great, very stable and for daily use.....
THX for support.... SyntaxError....
SyntaxError said:
View attachment 5551417
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 , which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
VoLTE and WiFi Calling)
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
GPS
Encryption (FBE)
WiFi Display
Broken:
you tell me(?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.
Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v11.0.3.0 global stable package.
Flashing Instructions
• Download ROM from the link above
• Download Gapps from the link bellow (Tested With NikGApps core)
• Reboot to recovery
• Format data (if encrypted)
• Wipe system, vendor, cache, dalvik, data
• Flash latest firmware
• Flash ROM zip•
• Flash GAppa
• Reboot
• To get root access, reboot to recovery after ROM setup and flash magisk
• Encrypted by default flash dfe zip from bellow after flashing rom if you want decryption
Downloads:
TWRP Recovery Download from here()
NikGapps core (Download from here)
Rom Download Link ( Download Rom From Here)
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Official wiki link
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Android OS version: 12
Security patch level: Feb 2022
Build author/Device Maintainer:SyntaxError
Click to expand...
Click to collapse
Hello.
How can I get LineageOS recovery on poco f1.
I installed your software but I wanted to upload some other software. I did a wipe, now I can not upload the file to the phone by encryption on adnroid 12. Now how to upload anything
uduro said:
Hello.
How can I get LineageOS recovery on poco f1.
I installed your software but I wanted to upload some other software. I did a wipe, now I can not upload the file to the phone by encryption on adnroid 12. Now how to upload anythiShould have flashed dfe zip file attached to this post
Click to expand...
Click to collapse
I am building another version witch will be decrypted by default flash the ROM again and then flash dfe zip for decryption.
I will upload lineage recovery later on if you want to use that.
SyntaxError said:
I am building another version witch will be decrypted by default flash the ROM again and then flash dfe zip for decryption.
I will upload lineage recovery later on if you want to use that.
Click to expand...
Click to collapse
but will it help me?
I now have a phone without a system.
I can't upload anything via twrp, would you give some recovery to bypass encryption now?
Thanks
@uduro decryption does not work for any Android 12 system currently. So you gotta have to live with it, until we get decryption support.
instead use adb sideload .zip

Categories

Resources