[COMMUNITY] Ubuntu Touch for S10, S10e, S10+ (beyond1lte, beyond0lte, beyond2lte) - Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve

[COMMUNITY] Ubuntu Touch for S10, S10e, S10+ (beyond1lte, beyond0lte, beyond2lte) - Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve

Thank you for this. Love Ubuntu/Linux. Will give it a try sometime but without GPS it wouldn't be my daily driver. Your work is appreciated though

Is sound and cameras working now?

Where is the vendor for beyond1lte and the rom?

Bugz1 said:
Is sound and cameras working now?
Click to expand...
Click to collapse
Yes.
Bugz1 said:
Where is the vendor for beyond1lte and the rom?
Click to expand...
Click to collapse
Git LFS' bandwith got full for some reason, will increase bandwidth.
[email protected] said:
Thank you for this. Love Ubuntu/Linux. Will give it a try sometime but without GPS it wouldn't be my daily driver. Your work is appreciated though
Click to expand...
Click to collapse
Thank you.

kreato3303 said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this OS
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Ubuntu Touch?Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
Ubuntu Touch is developed and maintained by UBports: a community of developers.
What doesn't work?
NFC
MTP
GPS
VoLTE since it depends on Samsung's proprietary framework
RequirementsYou need to use Official LineageOS' recovery with this ROM! TWRP is NOT supported and you may face problems.
DownloadCI Builds
Vendor image
Installation
Download the latest CI build and the vendor image for your device
Flash boot.img to boot, vendor to vendor, and system.img to system
UBports installer support is planned.
CreditsTheKit on UBports Telegram for helping me a lot
Linux4 for helping me fix the fingerprint sensor and the camera
What a wurst team for the kernel and for the a10 rom that i tested Ubuntu Touch with.
Source codeKernel and CI stuff
Patched vendor
SupportTelegram - @utbeyondxlte
Gitlab issues
Note: I made this new thread mainly because a lot of progress was made, including S10+ and S10e support.
Click to expand...
Click to collapse
Hi, Anyone know i have s10 plus + dex2 can i use this combo with broken screen and this Ubuntu touch rom? Thank you the answer.

first of all, thank you very much for your work!!!
My question is, do someone know how to boot a custom rootfs?
I would like to put arch linux on it. Do you think its possible to download the rootfs from archlinux arm flash it to system?
I unfortunately dont understand how the initramfs is build and how everything works with this weird android stuff mounted into the filesystem.
I mean they are like 30 partitions.
If someone knows how and where i could learn this, please let me know.

Bugz1 said:
Where is the vendor for beyond1lte and the rom?
Click to expand...
Click to collapse
It is now available thru here, i re-uploaded em. Sorry for the delay.

[email protected] said:
Thank you for this. Love Ubuntu/Linux. Will give it a try sometime but without GPS it wouldn't be my daily driver. Your work is appreciated though
Click to expand...
Click to collapse
Yeah, GPS is one of the features that needs to be worked on. Thank you and enjoy!
HyperFrame said:
first of all, thank you very much for your work!!!
My question is, do someone know how to boot a custom rootfs?
I would like to put arch linux on it. Do you think its possible to download the rootfs from archlinux arm flash it to system?
I unfortunately dont understand how the initramfs is build and how everything works with this weird android stuff mounted into the filesystem.
I mean they are like 30 partitions.
If someone knows how and where i could learn this, please let me know.
Click to expand...
Click to collapse
You can boot rootfs that supports halium (theoretically), but since theres no initramfs for now you need to use halium jumpercable. I tried Droidian and it didnt boot, but dont know bout anything else.
pgkhun said:
Hi, Anyone know i have s10 plus + dex2 can i use this combo with broken screen and this Ubuntu touch rom? Thank you the answer.
Click to expand...
Click to collapse
You should be able to use any dex adapter with this rom. I only tried a usb-c to hdmi + usb adapter though, so you are on your own on that one. If you can boot onto recovery and flash it, you should be able to use it with a external display.

would love to see some screenshots
I had Ubuntu touch on an old smart phone and loved it. Wished had more functionality but Im excited to see on S10

erych said:
would love to see some screenshots
I had Ubuntu touch on an old smart phone and loved it. Wished had more functionality but Im excited to see on S10
Click to expand...
Click to collapse
Note: These are not my screenshots, but they are from my port.

kreato3303 said:
Note: These are not my screenshots, but they are from my port.
View attachment 5461075
View attachment 5461077
View attachment 5461079
Click to expand...
Click to collapse
They look great! I can't believe my eyes

Update: GPS does look like it is working. This is essentially what works/doesn't right now. A recovery image is in the making and this device (hopefully) soon will have OTA updates aswell.
(I will make a merge request to devices.ubuntu-touch.io to update the what works/doesn't page once the recovery image is released)

can you please tell more information how to flash it?
i have s10 with lienageos recovery and i choose fastboot and try flash boot system and vendor from that site but i have boot loop 10s and restart phone
i need to run that github script on my own linux pc or i need to download artifacts only?
i should choose build deploy or manual?
on build i have artifacts with tar file and two folder inside that tar file i dont know how to flash it
on deploy i got artifacts witf ubuntu.img and boot.img and vendor.img from other site when flash it its not working boot loop
thank you

when i build myself from that github script and flash it over fastboot i dont have that error on fastboot when flash system.img about header magic looks like fixed but phone still no boot, its still in loop. my device is beyond1lte
can someone explain me how to do thins i dont like android
why i got thsi error?
Code:
cp: cannot stat 'partitions/*': No such file or directory
my lineageos recovery info
Code:
FASTBOOTD
Product name - beyond1lte
Bootloader version - G973FXXSEFUJ2
Baseband version -
Serial number - RF8M2....
Secure boot - yes
HW version - 26

its working!
1. install twrp recovery via odin
2. download ci deploy artifacts and vendor
3. on twrp clean all partition format
4. flash image via twrp image
only flash via twrp working, odin over download mode or lineageos recovery dont work block on boot loop

kreato3303 said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this OS
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Ubuntu Touch?Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
Ubuntu Touch is developed and maintained by UBports: a community of developers.
What doesn't work?
NFC
MTP
GPS
VoLTE since it depends on Samsung's proprietary framework
RequirementsYou need to use Official LineageOS' recovery with this ROM! TWRP is NOT supported and you may face problems.
DownloadCI Builds
Vendor image
Installation
Download the latest CI build and the vendor image for your device
Flash boot.img to boot, vendor to vendor, and system.img to system
UBports installer support is planned.
CreditsTheKit on UBports Telegram for helping me a lot
Linux4 for helping me fix the fingerprint sensor and the camera
What a wurst team for the kernel and for the a10 rom that i tested Ubuntu Touch with.
Source codeKernel and CI stuff
Patched vendor
SupportTelegram - @utbeyondxlte
Gitlab issues
Note: I made this new thread mainly because a lot of progress was made, including S10+ and S10e support.
Click to expand...
Click to collapse
Few days ago ive flashed this rom on my phone
But why i cant made phone call and cant used internet?
I think ive followed the istruction completely
Can someone give me suggestion?
Thank you

Absolutely fantastic that you're working on Ubuntu Touch for this device. My main reason for using custom roms is being able to throw out a large part of the google stuff and having full control over the hardware I own. From that perspective this seems great.
However, these days I don't have a lot of time, which means I need something that is close to the Android experience in daily driving. Simply put, I want things to simply work. So my question is: how close is this rom to the user experience of a well supported custom Android, like LineageOS?

doeternietoe said:
Absolutely fantastic that you're working on Ubuntu Touch for this device. My main reason for using custom roms is being able to throw out a large part of the google stuff and having full control over the hardware I own. From that perspective this seems great.
However, these days I don't have a lot of time, which means I need something that is close to the Android experience in daily driving. Simply put, I want things to simply work. So my question is: how close is this rom to the user experience of a well supported custom Android, like LineageOS?
Click to expand...
Click to collapse
Its full Linux Ubuntu, you can run inside this a Waydroid and emulate LinageOS and play games and run aps on emulated android in android phone thats crazy i was testing this and its works very good emulation android aps is snappy and can even watch youtube movies in 1440p in emulated android.
But the best is you can connect to hdmi and can run wayland gui desktop aplication and simple x11 over Libertine.
The idea is crazy but need lot of work to be done

Awesome. I just ordered S10+
Interested to see how it behaves with my dell thunderbolt dock.
Will hdmi out and the usb mouse / keyboard all work?

Related

[EXPERIMENTAL][AOSP][O] Homemade Oreo for OnePlus 5

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh atyou.
*/
Hi everyone, here is my port of Oreo on OnePlus 5. Source is based on AOSP android-8.0.0_r3 (r9 since 20170916, r15 for 20171008), as it's for Pixel. Device repo, kernel and vendor etc are available at the end of the post.
And the same note as before: this ROM is highly experimental, and only meant for the brave ones. I may not update this work regularly.
Hardware features:
Things went more smoothly than before.Majority of hardware features are working, including mobile network, WiFi, Bluetooth (file transfer, network, audio etc), GPS, camera / camcorder, fingerprint, sensors, HW-based encryption etc.
There are some minor issues regarding HW:
1. Virtual keys and hardware keys are enabled altogether. You can disable hardware keys at /proc/touchpanel/key_disable and /sys/module/fpc1020_tee/parameters/ignor_home_for_ESD . If you do want the virtual keys to hide, read first several pages of replies and there are some solutions.
2. Slider is not working, but it produces key event. There are lots of tools that can be used to customize actions for key events, and examples can be found in the first several pages of replies as well.
3. No offscreen gestures.
4. No option for color profile switching (default, sRGB, DCI-P3). You can switch that manually at /sys/class/graphics/fb0/color_profile
Known bugs:
1. Permissive SELinux, and init allows services without a SELinux domain to start
2. Behavior of camera is not consistent - it works on my phone, but it may crash yours. If your phone reboots into EDL/9008 mode after flashing this ROM, use recovery or fastboot to flash back to other ROMs IMMEDIATELY!
3. Sometimes the system does not show charging status (no flash sign in battery icon, but LED lights up as usual), while the battery is being charged just fine.
4. No UI shown when alarm clock goes off. This is an AOSP bug (missing NotificationChannel parameters). Use Google Clock from Play Store instead.
5. VoLTE is broken. Maybe we need to wait for an official release for updated blobs.
And as you may have already known, AOSP does not include a fully functional browser nor a file manager. An `adb install` may be needed after flashing.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Make backups! Make backups! Make backups!
20171008: https://drive.google.com/open?id=0BwkmhbR5VHpARHYwUE1BSGkxbTQ
20170924: https://drive.google.com/open?id=0BwkmhbR5VHpAU2lUVEVQcDRuaDQ
20170916: https://drive.google.com/open?id=0BwkmhbR5VHpAbkpMWFU1R1VLNDA
20170910: https://drive.google.com/open?id=0BwkmhbR5VHpAcGsyZ3hYWkZZcFU
20170907: https://drive.google.com/open?id=0BwkmhbR5VHpAMEVQX3h0UG1pUHM
You will lose Magisk and GAPPS after upgrading since boot and system partitions are overwritte. Better flash GAPPS right after the firmware, otherwise apps depend on GAPPS will FC even if GAPPS are re-installed.
This is NOT a flashable zip. Use fastboot to flash:
Code:
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
And wipe data before usage.
NOTE: This ROM requires encrypted data partition. If your data partition is not encrypted, format it. Moreover, OxygenOS 4.5.10 4.5.12 firmwares are required.
Changelog:
20171008
Since proper development on Oreo has started, this ROM has served its purpose as an experimental (or first-taste-only) ROM, and thus will not receive any updates anymore.
Updated blobs to OxygenOS 4.5.12 (baseband version was not changed, but better use the new firmware bundled with 4.5.12)
Updated to android-8.0.0_r15
Switched to new kernel source used by MoKee (may solve some WiFi issue, and possibly some others)
Some minor cosmetic changes
No new patches applied, the 0924 archive would be fine.
20170924
Fixed voice translation in Google Translate (maybe other apps as well)
Add a power HAL and double tap to wake is available in settings now (wondering if it actually works)
Use RenderScript driver from OnePlus 3 Oreo beta. Stock one is too old for Oreo, thus it was not loading at all.
Included navigation bar fix from this post
(Also tried new kernel used in MoKee and Lineage OS, but it still causes stalls when remounting so I switched back to the old kernel)
20170916
Bluetooth address should be correct
Fixed broken compress_offload feature (some music player (or ringtones) rely on this)
Make DASH chargers recognized as standard AC charger with fast charging support
Update to android-8.0.0_r9
20170910
Fixed Bluetooth audio. Now LDAC, AAC and SBC all work. If you want aptX / HD, find libaptX{,HD}_encoder.so elsewhere and push them to the phone.
Fixed AOSP keyboard crash when switching to symbol / numbers panel: https://android-review.googlesource.com/#/c/platform/packages/inputmethods/LatinIME/+/469478/
20170910
Initial build
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8998 (aosp-o-new branch)
Device: https://github.com/updateing/android_device_oneplus_cheeseburger (aosp-o branch)
Vendor: https://github.com/updateing/android_vendor_oneplus_cheeseburger (aosp-o branch)
In order to build kernel with AOSP, you need build/core/tasks/{kernel,dt}.mk from other ROMs build system. And external/{libnfnetlink,libnetfilter_conntrack} needs to be forwarded to AOSP master.
Source patches are attached to this post.
Credits:
MoKee/@XiNGRZ for this awesome kernel
Qualcomm for the great SoC
And Google for the OS
Thank you all!

Nice, will give it a go later, I presume there shouldn't be a problem with TWRP and going back to our present rom?
You also didn't post any gapps link, would these work ok?
http://www.cyanogenmods.org/forums/topic/gapps-lineageos-15-android-oreo-roms/

You're a brave man @djsubterrain

Does this work as a secondary ROM on multirom?

ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
No..As it says its not a flashable zip

ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
Judging by the way you need to flash this it's categorically NO

ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
It's labelled "EXPERIMENTAL" so it's highly unlikely, you really think that would be a priority to get it working with multiboot when the rom isn't even fully working?

niceeeeee

Nice to see some OREO love for our device. Thanks Developer for your hard work.

djsubterrain said:
Nice, will give it a go later, I presume there shouldn't be a problem with TWRP and going back to our present rom?
You also didn't post any gapps link, would these work ok?
http://www.cyanogenmods.org/forums/topic/gapps-lineageos-15-android-oreo-roms/
Click to expand...
Click to collapse
TWRP should work fine. Personally I'm using TWRP 3.1.1, official build, and haven't noticed any issue.
There should not be any issue when going back to 7.x ROMs (though I have not tried myself), but as wiping data is always involved when changing ROMs, do make a backup of everything including internal storage!
I have not tried any unoffical build of Gapps, and the only official build available now is DeltaGapps. It doesn't work OOB however, I need to extract some libs from APKs to get it to work.

1st to release N for bacon, O for cheeseburger.
Good job bro.

Good!!
Guo Lai Yang Wang Dalao!

Good job bro~
Sent from China fanboy~

missing on u in bacon family.. like u provided Nougat rom for oneplus 1..

*crais for posting OT* @updateing ,by any chance,are you working on oreo for bacon as well? Your work for Nougat on bacon is highly appreciated.

Mr.Ak said:
*crais for posting OT* @updateing ,by any chance,are you working on oreo for bacon as well? Your work for Nougat on bacon is highly appreciated.
Click to expand...
Click to collapse
Bacon already has an Oreo port.

djsubterrain said:
Bacon already has an Oreo port.
Click to expand...
Click to collapse
Ikr,but hopefully he'll be able to get camera working on oreo for bacon.

First O rom. Wow ?

Snapdragon815 said:
1st to release N for bacon, O for cheeseburger.
Good job bro.
Click to expand...
Click to collapse
Mmmm.... I love some bacon on my cheeseburger... Typed on the 1+1 while my 1+5 is charging... Keep up the good work!

Thanks Dev. Oreo love

[ROM] [8.1.x] LineageOS 15.1 Official (All variants) [NO VoLTE]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 15.1 is a free, community built, aftermarket firmware distribution of Android 8.1. (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Requirements
* You must read this post completely
* You must have flashed a stock MM update to update the firmware to a version that is compatible with these builds. Search XDA for the best way to do so for your device (if you already did that prior to installing any Nougat ROM, you are fine!).
* You must use the search first and make sure your question has not been answered yet!
* Do NOT ask for the availability of features or if any specific app works - we implement / announce new features when we want to
* Use the latest TWRP available, otherwise expect issues
* If you have a problem, do not ask if someone else has it. Post with logs or don't post at all!
Code:
[COLOR=RED][B]Important note:[/B][/COLOR]
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
Known Issues / NOT working / "Bugs"
* Search the thread!
* Anything running VoLTE firmware
* You tell me! (See "Other Issues")
Everything else WORKS, do NOT ask if anything (feature, function, ...) specific is working or not (Search the thread if you want to make sure and if you don't find it: test it yourself)
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates us more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem: boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
LOGS LOGS LOGS!!!!
Press BOTH volume keys + power key - it will vibrate very short. Wait until a notification appears that the bugreport is ready, send it to your mail and post it.
Alternatively go to dev options (press "build number" in "About phone" 7 times to activate it), activate the switch "Shortcut for bugreport", then go to Settings->Keys->Power key and activate it there as well. Long press power-key and then use the new menu item.
Only if rooted:
Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the LineageOS boot logo), use adb or any other file explorer tool to pull a copy of "console-ramoops" after the reboot and provide that.
Code:
adb pull /sys/fs/pstore/console-ramoops
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)
Changelog
* Gerrit (All)
* Device tree
* Kernel
Download Links
ROM: https://download.lineageos.org/kiwi
Again: if you need Google-Apps, install them after flashing the ROM and BEFORE the first reboot!
Google apps addon:
(Note: Not required to run the ROM)
We are using Open GApps (Link) Arm64 version, others might also be working (make sure to use ARM 64bit when using other providers!)
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
Note: If you install a package which replaces the default dialer (mostly "Stock Gapps") you have to go to Settings->Apps->Gear-Icon and set the new dialer as a default telephony app to prevent force closing of apps
Root addon:
Official download site - our device is ARM64
Don't use SuperSU or other tools, otherwise expect bootloops!
Important note
This is a development thread. This means it is NOT your personal support thread.
Questions about anything not related to LineageOS on kiwi (Honor 5X) will not be accepted nor be answered.
This includes topics like going back to stock, problems with third-party apps (e.g. Snapchat), ...
Also do not encourage people with such questions by answering them but report them to keep the thread clean!
Supported variants
Honor 5X
USA: KIW-L24
Russia: KIW-L23
India: KIW-L22
Europe: KIW-L21
China: KIW-AL10, KIW-AL20, KIW-CL00, KIW-UL00, KIW-TL00 (might have some firmware problems), KIW-TL00H
Honor GR5
Canada: KII-L05
Japan: KII-L22, KII-L21
Your's missing? Contact us!
XDA:DevDB Information
LineageOS 15.1, ROM for the Honor 5X
Contributors
BadDaemon, Dobroslaw Kijowski
Source Code: https://review.lineageos.org/#/q/(project:LineageOS/android_device_huawei_kiwi+OR+project:LineageOS/android_kernel_huawei_kiwi)+AND+(statuspen+OR+status:merged)+AND+branch:lineage-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.1.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-09-22
Last Updated 2019-06-26

Reserved
FAQ
Q: Why the **** did it take so long?
A: Besides the fact that I don't really need to answer about my working speed:
I have actively been working on bringing up 8.x for this device since February. Some might have seen some development going on with the kernel on 14.1, but effectively this was all in preparation for 15.1: The kernel being used in this version of the ROM is completely redone:
We threw away what we had and started fresh with a plain qcom kernel. Then we re-added what we needed, effectively ending in around 700k lines less of custom additions by the OEM.
Q: Why didn't you share it before, so others could work on it as well?
A: Because last time we did that, someone else came along, compiled our work and shared it himself. (Not to start about all the other copy&paste-ROMs who could have done the work as well but usually just wait for us to do it)
Q: Anything else to add?
A: Yes: read the first post before replying or testing the ROM!

Reserved
Install instructions:
* Follow the instructions on https://wiki.lineageos.org/devices/kiwi/install

Reserved

Reserved 2

this was suprising will test it and see if it works

it fails flashing with error 7
E3004 : this package is for device KIWI; this device is .

omid_shirzad said:
it fails flashing with error 7
E3004 : this package is for device KIWI; this device is .
Click to expand...
Click to collapse
Please tell me you have updated your twrp before trying?

BadDaemon said:
Please tell me you have updated your twrp before trying?
Click to expand...
Click to collapse
nope
its 3.1.1.0

So far, no issues to report on KIW-24. Awesome job!

omid_shirzad said:
nope
its 3.1.1.0
Click to expand...
Click to collapse
Bro ... update it and try .... please read Frist post

Bharath kumar 007 said:
Bro ... update it and try .... please read Frist post
Click to expand...
Click to collapse
THANKSSSSSS
updated it and i'm flashing rom again<i think it workd:good::good::good:

finnaly oreo is coming for honor 5, cant wait to test it, thanks dev

So glad people follow the instructions:
"Read the first post!"
"* Use the latest TWRP available, otherwise expect issues"
...

BadDaemon said:
Install instructions:
* Follow the instructions on https://wiki.lineageos.org/devices/kiwi/install, just use the ZIP linked in the first post instead of one from the official page
Click to expand...
Click to collapse
Thanks. Buddy. I always knew you are working and you will post it. Community thankful to you.

omid_shirzad said:
it fails flashing with error 7
E3004 : this package is for device KIWI; this device is .
Click to expand...
Click to collapse
you can try this method

Guys, this problem is already solved. dont post such stuff please, especially when its a user error...

Thanks to devs to make it possible.... I am coming from LoS 14.1 did a full wipe but rom does not boot (showed LoS logo but reboot to recovery) after that I flashe Rom + Gapps + BaPatch.zip but phone stucks on Huawei logo. I don´t know how to downgrade Emui because I have the chinese variant UL-00

Bootloop
Hello first of all thanks to the devs who made it possible for our device i really appreciate their hard work so im coming from los 14.1 using it as my daily driver for almost 4 months had no issues with it so far with it but today when i flashed this rom [clean installed] it show the lineage boot logo but after a min device reboots back to recovery i have tried again a several but no luck so far hopefully the devs can understand whats the issue thank you? btw I'm on latest twrp also and my device name kiw-l21 and also I'm not on volte firmware

blackscreen
hope i take the logs right
lockscreen goes black after restart
View attachment 2018-09-23_09.54-lockscreen.zip

[ROM][10.0][UNOFFICIAL] LineageOS 17.1 for Mix 3 5G [andromeda]

Additional installation instructions if coming from stock MIUI:
In order to install a custom ROM you must have an unlocked bootloader. You can apply for this at Xiaomi's official site: https://en.miui.com/unlock/
You then need to install a custom recovery. Official TWRP builds are available, and the official maintainer has a thread with installation instructions here: https://forum.xda-developers.com/mi...covery-unofficial-twrp-xiaomi-mi-mix-t3941867
Once you have TWRP installed, boot into recovery mode. Wipe cache,dalvik,system,vendor partitions.
You are strongly advised to flash the latest modem firmware. You can grab that here: https://sourceforge.net/projects/xiaomi-andromeda/files/firmware.zip/download
WARNING: You will lose all saved files on your internal storage in the next step, make a backup of important files before proceeding
Data partition must be formatted (not wiped) to remove forced encryption. Use the bottom right "Format Data" button in the Wipe menu. You will be asked to type "yes" to confirm your choice.
At this point your internal storage will be empty. Copy the ROM from your PC to the phone, click install in TWRP and select the ROM. If you wish to install gapps/nanodroid, copy it to the phone and install after the ROM. Once you have flashed the ROM and any add ons, you must format internal storage again. Internal storage must be completely empty for the very first custom ROM boot, once a custom ROM has been installed and you want to swap to a different one, further formatting is not necessary.
Reboot back to system and enjoy custom ROM goodness

Reserved

Thanks, been waiting for this. Will test it out

Just switched to this one because Xiaomi probably won't ever release Q for andromeda. Working great so far!

Can you flash modem via twrp or do I need to use Odin?

Arcticsoldier said:
Can you flash modem via twrp or do I need to use Odin?
Click to expand...
Click to collapse
twrp

pm4rcin said:
1. After some trouble with installing (first time so...) system works fine but when I plug my usbc-jack adapter and headphones it doesn't see them. How can I fix that?
2. Another thing is no 4k option in camera app for recording.
PS. Thanks for your work delivering that ROM.
Click to expand...
Click to collapse
I got no problem with headphones here.
Stock LineageOS Snap camera can't do 60fps or 4k recording. There are plenty of camera apps on the play store that have these options.
If you want to use GCam then this port is the most compatible with andromeda, it can do 1080p/60fps and 4k/30fps video recording. https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.9.apk
This GCam port does not work with selfie camera at all, you must use the built in Snap cam for that. My suggestion would be to set the slider to open the default camera app and to have have GCam on your home screen.

Phone is not rooted, but many apps do not work because they think its rooted. I.E. Revolut, banking apps, Outlook, Teams. Is there an workaround for this?

flori.one said:
Phone is not rooted, but many apps do not work because they think its rooted. I.E. Revolut, banking apps, Outlook, Teams. Is there an workaround for this?
Click to expand...
Click to collapse
This problem with false positives happens on stock ROMs as well. When I owned a Zuk Z1, loads of apps thought the stock ZUI was a rooted custom ROM. Not a lot can be done about it because each app uses it's own detection method and the companies that make these apps obviously aren't going to broadcast the detection methods they use.
You may have success running these apps by actually rooting your phone and using Magisk Hide on the apps that don't work.

It's the first time I install a non-official Lineage ROM and I've found that both SELinux and device encryption are disabled. I also got a notification saying this was due to the ROM being built with public keys?
I don't know if this is normal and if there's something I can do to enable SELinux and searching for solutions hasn't returned any
Also, what's the keys thing about?
Thanks for your efforts!

Groctel said:
It's the first time I install a non-official Lineage ROM and I've found that both SELinux and device encryption are disabled. I also got a notification saying this was due to the ROM being built with public keys?
I don't know if this is normal and if there's something I can do to enable SELinux and searching for solutions hasn't returned any
Also, what's the keys thing about?
Thanks for your efforts!
Click to expand...
Click to collapse
I'm not on the LineageOS team so I don't have access to their build system or their private keys, hence the warning about public keys. If you really want encryption it is possible but would involve formatting your data partition again and losing all your files. Writing SELinux policy is a bigger task than porting the ROM and I'm only one guy working alone in his free time. If you try to force SELinux to enforcing mode it's quite likely the ROM won't even boot.
If you're worried about a security risk, considering you have unlocked your boot loader and installed an unknown firmware from a random person on the internet, I would say you have already made a decision concerning your phone's security. All my source code is linked in the first post, so feel free to look it over to make sure I'm not doing anything shady

Inkypen said:
I'm not on the LineageOS team so I don't have access to their build system or their private keys, hence the warning about public keys. If you really want encryption it is possible but would involve formatting your data partition again and losing all your files. Writing SELinux policy is a bigger task than porting the ROM and I'm only one guy working alone in his free time. If you try to force SELinux to enforcing mode it's quite likely the ROM won't even boot.
If you're worried about a security risk, considering you have unlocked your boot loader and installed an unknown firmware from a random person on the internet, I would say you have already made a decision concerning your phone's security. All my source code is linked in the first post, so feel free to look it over to make sure I'm not doing anything shady
Click to expand...
Click to collapse
Well, I've never read a better argument for security! I'll try to learn about writing a SELinux policy and will PR you if I can get it to work in my own device. Once again, thank you very much for your contribution!

Hello
Great Job. Hope you could be merged soon in Official build, they announce a relaxed form in order to submit devices BTW.
Also, i'm trying to get encryption working and i'm stuck.
Like my old phone, after a fresh install a go to encrypt my phone.
I have a little droid during few seconds and a reboot (without progressing bar, a classic boot).
After checks phones still unencrypted.
Just for my reminder here are the steps:
- Flash MIUI EEA
- Boot MIUI
- Fastboot > flash TWRP
- Reboot Recovery
- Wipe Cache, System, Vendor, Data
- Install firmware
- Format Data
- Install lineage
Is it correct ?

kikadisa said:
Hello
Great Job. Hope you could be merged soon in Official build, they announce a relaxed form in order to submit devices BTW.
Also, i'm trying to get encryption working and i'm stuck.
Like my old phone, after a fresh install a go to encrypt my phone.
I have a little droid during few seconds and a reboot (without progressing bar, a classic boot).
After checks phones still unencrypted.
Just for my reminder here are the steps:
- Flash MIUI EEA
- Boot MIUI
- Fastboot > flash TWRP
- Reboot Recovery
- Wipe Cache, System, Vendor, Data
- Install firmware
- Format Data
- Install lineage
Is it correct ?
Click to expand...
Click to collapse
I have testing builds with encryption enabled. The good news is the next update will have encryption enabled, bad news is you'll have to format data partition again to get it working.

The LineageOS team have added in Qualcomm's Bluetooth stack so I've uploaded a new build. You probably won't notice any changes because these are "under the hood" improvements, but if you have some high end headphones you may hear a difference!
Also this build and all future builds have encryption enabled. Unfortunately this means you will need to format your data partition in order to install this build, but this is a one time only thing. I can also confirm that F2FS is working perfectly with encryption if you wish to change filesystems. I can also confirm you can switch to a different ROM without formatting (just the usual wipes) so long as the new ROM you are installing is also encrypted. This change might mean that you can come straight from MIUI without formatting but this is completely untested by me.
Here's the link, and remember you MUST format internal storage if you are on an unencrypted build:
https://sourceforge.net/projects/xi....1-20200630-UNOFFICIAL-andromeda.zip/download

I have tried to flash after format data partition, but I had a bootloop. I was forced to do a clean install after that. I don't know why, but it's working now.
Thanks for your work

Hello, does 5G work on this custom rom?

karolwojak said:
Hello, does 5G work on this custom rom?
Click to expand...
Click to collapse
yes it does

I really need to record conversations or have. I would love to try it out if it had this function

Development [ROM][OFFICIAL][13][lemonadep] tequilaOS tobacco

Can this ROM be considered a "daily driver"?
Kudos to the Devs!

best rom in the universe

Rayan said:
Can this ROM be considered a "daily driver"?
Kudos to the Devs!
Click to expand...
Click to collapse
I daily drive it for over two weeks now, so i suppose it can be considered as a daily driver.

Anyone have a carrier unlocked T-Mobile phone using this? I have Verizon and all the other a13 Roms don't detect my sim. Want to make sure before I flash. Thanks.

OOS camera on this?

TheSayaMan said:
Anyone have a carrier unlocked T-Mobile phone using this? I have Verizon and all the other a13 Roms don't detect my sim. Want to make sure before I flash. Thanks.
Click to expand...
Click to collapse
Yes, it's working vith Verizon

ejbtrd said:
Yes, it's working vith Verizon
Click to expand...
Click to collapse
Awesome, thanks!!!

this.guy.lol said:
OOS camera on this?
Click to expand...
Click to collapse
Nope, there is no OOS camera included (at least not yet)

ejbtrd said:
Nope, there is no OOS camera included (at least not yet)
Click to expand...
Click to collapse
alright thanks. will try out when/if it happens. thanks!

Can we get screenshot of this ROM?

@ejbtrd
Is there burn-in protection included in the rom for AOD?

ejbtrd said:
Yes, it's working vith Verizon
Click to expand...
Click to collapse
Wrong, it does not because I tried it. Won't detect my sim. My original question was, will the carrier unlocked T-mobile version work with Verizon. It's obvious you have the Global version. Complete waste of my time. Thank you!!!

TheSayaMan said:
Wrong, it does not because I tried it. Won't detect my sim. My original question was, will the carrier unlocked T-mobile version work with Verizon. It's obvious you have the Global version. Complete waste of my time. Thank you!!!
Click to expand...
Click to collapse
Works fine if you just stay on your stock firmware and flash custom rom over it.

I am unabled to start accessibility services
(it's my fault, or shared)?

EDIT MODERATION
I can see that some members sometimes tend to forget certain things that I will remind them of.
Firstly that we are here to share knowledge, but also to help in our comments.
But I would also like to remind you that it is good to research and read before posting a question (xda forum rule #1), as you may not be the first to ask that question.
Sometimes some people should reread the forum rules, especially the one concerning courtesy in answers or questions:
Rule #2.3 => ... When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Click to expand...
Click to collapse
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Click to expand...
Click to collapse
Thanks for your comprehension and have a nice day
Regards
Sib64
Moderator

break.cold said:
@ejbtrd
Is there burn-in protection included in the rom for AOD?
Click to expand...
Click to collapse
Yes, there is.
TheSayaMan said:
Wrong, it does not because I tried it. Won't detect my sim. My original question was, will the carrier unlocked T-mobile version work with Verizon. It's obvious you have the Global version. Complete waste of my time. Thank you!!!
Click to expand...
Click to collapse
You are right, official release doesn't include a fix for it. Next build will.
Psk.It said:
I am unabled to start accessibility services
(it's my fault, or shared)?
View attachment 5735169
Click to expand...
Click to collapse
Accessibility services seem to work fine for me, i can allow/deny any app without issues.

ejbtrd said:
Accessibility services seem to work fine for me, i can allow/deny any app without issues.
Click to expand...
Click to collapse
You will know that you have a button at the bottom right called ' Edit', which allows you to edit your post and therefore add comments.
The '+Quote' button allows you to add comments from other members to your post.
This is why I have taken the liberty of editing your posts and combining them into one.
Thank you for your understanding

SaintZ93 said:
Works fine if you just stay on your stock firmware and flash custom rom over it.
Click to expand...
Click to collapse
I am on stock firmware and it doesn't work. No sim detected.

ejbtrd said:
tequilaOS for the OnePlus 9 Pro [lemonadep]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
About
tequilaOS is just an another aftermarket OS based on Android Open Source Project. Even though we focus on stability and performace, we still allow user to customize system to his own needs.
Flashing instructions
Clean Flash
1. Download the proper flashable ZIP for your device, as well as all additional images
2. Flash provided boot, vendor_boot and dtbo via Fastboot
3. Reboot to Recovery
4. Sideload the ROM
5. Sideload firmware (if necessary)
6. Format data
7. Reboot to System
Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Sideload the ROM
4. Reboot to System
Download
Download latest build from our website:
https://tequilaOS.pl/download?device=lemonadep
Contact
Reach us on our Telegram Group or Discord!
Android OS version: 13
Security patch level: October 2022
Build Author: ejbtrd
Source Code: https://github.com/tequilaOS
Kernel Source Code: https://github.com/tequilaOS/platform_kernel_oneplus_sm8350
ROM Developer: ejbtrd
Click to expand...
Click to collapse

CherishOS V4.8 [13] [Gapps/Vanilla] [NB1] [Unofficial]

Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,

Kasi1906 said:
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Click to expand...
Click to collapse
hey, thank you i am glad you are happy with it, always nice to see things like this, appreciated.

4.2 build is up, happy flashing, changelog in git page

marceldossantos91 said:
4.2 build is up, happy flashing, changelog in git page
Click to expand...
Click to collapse
Thank you for the timely security update! My gratitude is still very high. The ROM works perfectly. So far I have not had any problems.

I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear

satanvade said:
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
Click to expand...
Click to collapse
Hi, you can follow the guide in the Q & A section linked above or in our telegram support group, but the basic idea is:
Unlock bootloader + critical
Flash Tvirus 2.0, which includes twrp 3.6 already (there is however a 3.7 update available, which supports decryption in A12/13, but 3.6 can flash fine)
Flash the rom
Wipe data
Reboot to system
If you need further support, we are more responsive in our support group

It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock

guorium said:
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
Click to expand...
Click to collapse
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added

marceldossantos91 said:
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
Click to expand...
Click to collapse
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!

guorium said:
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
Click to expand...
Click to collapse
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me

marceldossantos91 said:
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
Click to expand...
Click to collapse
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.

guorium said:
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
Click to expand...
Click to collapse
thanks

marceldossantos91 said:
thanks
Click to expand...
Click to collapse
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.

guorium said:
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
Click to expand...
Click to collapse
thank you for the log i will look into it and see if i can resolve it in updated builds

marceldossantos91 said:
thank you for the log i will look into it and see if i can resolve it in updated builds
Click to expand...
Click to collapse
No problema. PE A12 has the same problema. Must be easy to miss.

4.4 build is up, happy flashing

marceldossantos91 said:
4.4 build is up, happy flashing
Click to expand...
Click to collapse
Thank you!
Enjoy

Kasi1906 said:
Thank you!
Enjoy
Click to expand...
Click to collapse
tysm appreciate it

4.6 build is up, happy flashing!

Develop Bugs

welcome