yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
That's PE custom settings, as I wrote in OP that part of code has not been merged yet, like Dolby Atmos support (which is broken even with PE 13 changes merged, I've already tried) and FOD with screen off on my Grus. If you want to swap buttons there's a way, but you must root your phone or use adb, and it's persistent across reboots until you flash again an update.

With ADB:

1 - Extract from your phone with "adb pull" the file /vendor/usr/keylayout/synaptics_dsx.kl , or download it from my repo

2 - reverse numbers in BACK and APP_SWITCH like this:

key 139 BACK VIRTUAL
key 158 APP_SWITCH VIRTUAL

then replace the file in your device:

adb root
adb shell mount -o rw,remount /vendor
adb push /YOUR/PATH/TO/synaptics_dsx.kl vendor/usr/keylayout/

3 - reboot

If your phone is rooted then you can simply edit the same file with a file explorer that supports root and reboot

Memory and CPU are more or less in line with PE13, 4Gb devices should perform much much more better than 3Gb variants, unfortunately my Gemini pro died last year and now i have the worst possible version (3Gb - 32Gb), but I'm pretty sure that the 4Gb version is safe from the process kill-restart madness that occur on 3Gb variants, LOS with basic GAPPS require half RAM than PE (700-800 Mb vs 1300-1400 Mb), if I don't have this problem with my LOS 20 builds then you should be safe on PE :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xiguo:
Yes, it works like a charm. I have a KernelSU patch to he kernel.

BTW, 1. you can replace GCAM with OpenCamera https://f-droid.org/packages/net.sourceforge.opencamera/, which is faster.

2. you can modify the /vendor/gms/common/common-vendor.mk to reduce the ROM size and memory occupied. But I removed too many, so that the google play doesn't work.

3. Now a new second-hand 64g gemini phone is very cheap, about 100yuan($14) on https://goofish.com.

have a fun.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] StarVase:
oh dear, 100yuan is enough for a mi 5 pro on coolapk!!

Thank for your early reply.

Really bad news:(

But when will the pe14plus for Gemini publish?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xiguo:
you buy mi5 pro from coolapk, and make the deal on 2.taobao.com( https://goofish.com). Don't be kidding, he is in Italy, not in China!!!

He tried his best to support the Alpha-PE14. Come on, don't ask more.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] StarVase:
copy
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, I've uploaded a new build with a few fixes, USB tethering now is working fine, while I was at it I've also updated, cleaned and fixed USB scripts, now device doesn't show any more as a mass storage when is in charge only mode (I haven't tried but now diag mode should work too). I've added locally support for buttons light, it's really basic and values cannot be changed, but works. There are other misc fixes/improvements, see the device tree repo for details. On kernel side there are various updates for crypto/ext4/f2fs and other misc fixes, most of them from 4.9 kernel (still testing them, but I did not see any regressions or errors after 2 days)

Here's the download link:

Pixel Experience 14 ALPHA

Do you need kernelSU? As far as I know it's pretty useful if you work on a kernel in user ROMs, but since we are in userdebug mode we already have adb root shell for debugging, unless you want a root shell in a terminal app, in that case adb root won't work

1 - I don't know if OpenCamera works fine when installed as system app, I never tried. I use GCam because I prefer quality over speed, but i don't want to force user, that's why I fixed sepolicy for other camera apps when installed as user app, everyone is free to disable GCAM and set a different camera app as default

2 - You should never touch that makefile, if you want to remove some stuffs set the proper flags in device tree like this commit. BTW the same thing happened during Android 13 bringup, there are good possibilities that PE devs will debloat a bit gsm repo before official release

3 - My mobo died last year, I replaced it with a 32/3 Gb from AliBaba, if I remember well it was around 30-35 euros with shipping in Italy from China, that was the best price I found, but I just need it mostly for development, that's enough for me :)

No worries, Grus is my primary phone now, I only needed a phone for development and when I'm away for work when I'm in places where it's easy to damage it if it's in my pocket, It's perfect for me :) only real hassle is that for some things I'm forced to compile a light ROM like LOS, a clean flash everytime I switch ROM is a pain.

About PE 14 plus there's nothing published in PE staging repos for PE Plus, PE standard still misses various features, pretty sure we have to wait at least until PE 14 standard is ready for release
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] kluknawa235:
i uset this rom on my 128Gb model. Works nice for now.

What i just see. If battery is low then 20% android setup say you must charge battery. Then You can setup your phone but its too laggy.

for now i not see anything. works nice.

thanks
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xuexiang:
hello

Can you provide other download links? Restricted access to Google

You can access the following

crDroid Android - Browse /gemini/9.x at SourceForge.net

Highly customizable Android Platform

sourceforge.net
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi, sorry for the troubles with GDrive, AFH is still unusable for me and I cannot upload my work there, no matter what I try and what server i choose for the upload, it fails everytime at 0% with an unknown error, and they support team did not reply (yet) to my message. I will upload next ROM on sourceforge, hopefully everyone will be able to download it

SetupWizard it's a little bit buggy/laggy at the moment, there's something wrong with Gestures, Android tries to enable them every few seconds, this is causing lags, sometimes screen flash and you can see Pixel Launcher in the background and if you are quick enough you can escape from SetupWizard using a gesture or clicking an icon in launcher when appears. Also even if at the end of the setup you disable gestures it won't work, you are forced to open settings and manually disable them. Luckily this behaviour only affects setup wizard, once you pass device configuration everything works fine, and there's no risk that the same thing happen after you ended the setup.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xiguo:
I found the config item in

./vendor/aosp/config/common.mk:185:TARGET_INCLUDE_LIVE_WALLPAPERS

./vendor/gms/extras/config.mk:14:ifeq ($(TARGET_INCLUDE_LIVE_WALLPAPERS),true)

there are only five items:

TARGET_SUPPORTS_GOOGLE_RECORDER ?= true
TARGET_INCLUDE_STOCK_ARCORE ?= true
TARGET_INCLUDE_LIVE_WALLPAPERS ?= true
TARGET_SUPPORTS_QUICK_TAP ?= false
TARGET_SUPPORTS_CALL_RECORDING ?= true

But I delete more in vendor/gms/common/common-vendor.mk ....

thanks all the same.

Why not in -user mode? I use -user mode plus KernelSU, KernelSU w/ zgisk can use most of module from Magisk, provide full of root function to hack apps.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
That's the only flags you can disable safely for Gapps, other changes may break a ton of things, you should check packages/libs dependencies before start removing apps

Regarding user mode yes, you are right, it's booting, that's because most of our blobs comes from an Android 13 ROM, we don't need some workaround used by other legacy devices to make things work in latest Android versions, but:

1 - user mode adds some additional sepolicy rules that can break things, latest changes I made on my repo are related to sepolicy (i found most of them running in user mode, I don't remember all that denials in userdebug mode)

2 - PE and a lot of other ROMs disable several debugging features even if you compile the ROM in userdebug mode

3 - In user mode debugfs is forbidden, but I've already disabled it in both kernel and device tree, and as you can see all additional debugging packages from userdebug version has been removed

4 - You can debug user ROMs with KernelSU, that's true, but It's still a pain compared to a simple "adb root" from your PC, you are forced to open a shell and use "su" with all the related limitations (no adb push on system/vendor, cannot redirect console output in a file in your PC, etc)

5 - Recovery in user mode does not have adb, you cannot save logs or do anything if something goes wrong, so you are still forced to compile recovery in userdebug mode, at least during development

6 - "With great power comes great responsibility", I don't like the idea to ship a Kernel in a ROM with such power to people that don't use it or (worst case) don't know what root is and what can do. I will ship a kernel with KernelSU (say thanks to @Inkypen for his work, he ported the needed patches on my kernel) for people that wants to root the device, but i will not embed it as default in my ROM
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xiguo:
I have searched, the PRODUCT_PACKAGES_DEBUG and PRODUCT_PACKAGES_DEBUG_ASAN should be a list packages like this

build/make/target/product/handheld_product.mk
42:PRODUCT_PACKAGES_DEBUG += \
43- frameworks-base-overlays-debug

build/make/target/product/generic_system.mk
88:PRODUCT_PACKAGES_DEBUG += \
89- avbctl \
90- bootctl \
91- tinycap \

build/make/target/product/base_system.mk
384:PRODUCT_PACKAGES_DEBUG := \
385- adb_keys \
386- arping \
387- dmuserd \
--
build/make/core/product.mk
46:_product_list_vars += PRODUCT_PACKAGES_DEBUG
47:_product_list_vars += PRODUCT_PACKAGES_DEBUG_ASAN

I remember the official PE recovery have advanced switch to enable adb, that I can pull the pstore/last_kmsg.

ok, I have done by my self, thx all the same.

There is another question. I think why we have to format the storage when we upgrade from 13 to 14 is the filesystem of storage changed from ext4 to f2fs. My question is do you have a plan to port EROFS to gemini? or aggressivily upgrate to 4.9?

I have see one guy bump msm8953 from 4.9 to 4.19!!! https://github.com/halibw/kernel_msm8953_4.19

https://gitlab.com/msm8996-mainline/linux, this is 6.6 mainline version linux kernel, and the drivers 70% is work, 30 is partial or broken, as https://wiki.postmarketos.org/wiki/Xiaomi_Mi_5_(xiaomi-gemini).
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] geekits:
Hey, can the mainline linux kernel be used in Android ?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] StarVase:
There is a problem with my Gemini which uses pe13plus. I found the NFC is not useable in pe 13 while it works fine on my pe14 one. For some reason I still use pe13 as major system, and is there any methods to fix NFC on 13?

View attachment 6038848
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] xiguo:
I have tried PostmarketOS, it prebuilts packages include linux kernel, then downloads and then flashs w/ their python tools. I have tried it. It works but lacks some drivers, and battery drains. I don't know if it can call, send message, because I forget to test.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, PE devs released the updates to QPR1 a couple of days ago so a new release is out! Please note that ROM is still in staging stage and these rebase literally killed fingerprint on all my devices and completely break build for Gemini, I had to fix FP support, add back the mising code for udfps and add all the missing code for Dolby Atmos, everything should be fine but if someone wants to compile ROM from sources using my branches be aware that FP, Dolby and probably SELinux in enforcing mode will be completely broken

Here's a small changelog:

ROM

- Update sources to Android 14 QPR1

Device tree (msm8996-common)

- Build Lineage Health HAL

- VNDK: remove libcutils-v29.so from build

- audio: Import dolby atmos

- Link libdlbdsservice against v33 libstagefright_foundation

- partially switch to QTI IWLAN

- Add feature flag for FEATURE_IPSEC_TUNNELS

- kernel: move to Clang 18.0.0

- QCamera2: misc fixes

- Sepolicy: misc fixes

Vendor

- Import dolby atmos

- patch libdlbdsservice.so to load libstagefright_foundation-v33.so

Kernel

- Merged security patches + fixes from LOS msm8998 QCOM kernel

Download links:

Pixel Experience 14 Staging

Flashable Kernel with KernelSU

It will probably boot but will break a lot of things (also proprietary blobs from fairphone 3 are compiled against 4.9 kernel, pretty sure that 6.7 kernel will break a lot of them, like the migration from 3.18 to 4.9 kernel broke OIS)

Will be fixed next PE13 release (hopefully next weekend), PE devs removed legacy NFC support on PE13, but they reverted the change
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] teddy0209:
My device on the new build stays on black screen after booting.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
I had a report on Grus too so it's something related to PE, roll back to the previous version for now, but please provide me the logcat and the dmesg from the boot to the black screen, a lot of debugging is disabled but maybe there's something useful.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] teddy0209:
I can't take dmesg, says device unauthorized, and on logcat it says waiting for device.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] geekits:
Oh man, I build los21 for gemini with your device tree and kernel(branch los21 and fourteen), but phone bootloop at first screen🙁, what additional work is needed? I synced latest los21 code.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
You must rollback to the previous working release, enable ADB, authorise your PC and then upgrade so ADB works when you have the black screen. Did you change the lockscreen style? That may be the root cause of the crash, see here

Pretty sure you are using the wrong kernel branch (use fourteen if you want to be 100% safe, fourteen-TESTING if you want to try my latest changes) or you did not add hardware/xiaomi repo in your build environment, as there are no dependency files on my branches you must download it manually (remember to change the repo folder name to "xiaomi" or won't be used). The only thing not included in LOS is Dolby Atmos support in frameworks/av, I've attached a patch in this post, apply it and you are good to go (remember that you probably must reapply the patch everytime you do a "repo sync").

A clean build should NOT be needed in both cases, simply add the repo or switch kernel branch and run an "mka bacon"
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] teddy0209:
My PC is authorized before the upgrade. Will try reverting to default lockscreen.

Edit: I reverted to Pixel Launcher since I'm using Nova, Then tried to flash again, but still the same. I can't take logs. Or is there anything specific to do or try?

Edit 2: I removed the lockscreen security and tried again. That did the trick. Still getting occational blackscreen though.

Edit 3: The longer I use the device, the more frequent I'm getting the blackscreen. Now it's like blinking every three seconds.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] StarVase:
After changing the clock in lockscreen, the SystemUI went died, and i have no idea to undo the settings.

Ps: I've formatted my userdata and it started.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
No need to take logs, clocks packages has been updated and even if actually are still broken (lockscreen clock does not change) at least SystemUI doesn't crash

You can roll back to the previous ROM and stay there or set the default lockscreen clock and update to latest ROM, with the default lockscreen everything works fine
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, BETA build if finally out! There's only a minor bug, battery stats does not reset, apart this everything else works pretty fine, even lockscreen clocks :)

Take a look at my Github for a list of changes (sorry no changelog this time, I'm terribly busy in these days)

Here's the download links:

Pixel Experience 14

Kernel with KernelSU support
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] StarVase:
A great work! And would pixel experience 13 be updated soon?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] MI FOR 2:
Can you build a plus version in future builds and streamline the system to ensure sufficient memory? Thank you for your reply。
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] teddy0209:
is VoLTE working for you guys?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] 搞机陈:
Hello developer, this rom seems to be stuck in touch, the screen can't be touched, have you ever encountered this kind of problem
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Unfortunately my Gemini died yesterday and actually I won't be able to release anything for a while, BTW i'm considering to drop PE 13 in any case as PE devs deprecated android 13 and maintain 3 completely different devices require a lot of times

3 Gb variants have only 700/800 Mb free for apps, there's nothing that can be done, that's the memory required by PE, if you can't live with it switch to my LOS builds, with minimal GApps packages there are more or less 1300/1400 Mb free for apps

VoLTE is untested, but if you want to use it you must first load an mbn config file for you carrier from a compatible phone with working VoLTE, you need stock ROM, Qualcomm QPST/PSD and a PC with Windows

Hi, honestly no, any chance to have a log while is happening?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] MI FOR 2:
Thank you for your reply. Currently, I am using your los21, but I have found that the lsposed framework cannot be used on your los21. Can you please troubleshoot the issue?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] rh_1363:
What is the best version of Pixel Experience for Mi 5 in case of Battery Life and smoothness?

Where can I Download the previous build of Pixel Experience? (Android 9 or 10)?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] helaman.colburn:
Just came here to say BB I love you. Using your LOS21
[OnePlus 10 Pro] matti88:
Got one that's soft bricked. What I've done so far:

1. Used the OFP tool to flash OnePlus_10_Pro_5G_NE2215_EX_11_A.11_220324 - no change

2. Used Fastboot Enhance to flash NE2215_11_C.21 Stable(full) - this led to unlocked BL warning disappearing on splash screen, but device now boots to CrashDump instead of looping.

Still have access to fastboot. Active slot is B, I've thought about changing it but have read stories about others losing access to fastboot that way. Any ideas what to try next?

TIA

EDIT: Ignore. Bit the bullet and decided to switch slots and now have a totally bricked device. Super fun
[OnePlus 10 Pro] "Inkling:
Sorry...
[OnePlus 10 Pro] usama_92:
Were you able to resolve this issue, I've lost fastboot access too.
[OnePlus 10 Pro] Дудшшд:
U can use fastboot enhance to flash stock boot.img in slot_a with fastbootD, but now too late
[OnePlus 10 Pro] TJ1968:
I can find absolutely no help unbricking my One Plus 10 Pro.

I picked a bad time to invest into OnePlus, since I had a 6t.

One Plus better do something...it's not looking good for me or them.
[OnePlus 10 Pro] Prant:
Only guaranteed unbrick for 10Pro is to pay for a MSM flash. There's other methods depending how far bricked your device is, like completely and semi-manually reflashing a complete image.

But this has varying success depending how bricked your device is as there are encrypted partitions that will not be restored unless via complete MSM flash. Good luck.
[Touch Pro, Fuze ROM Development] merten3000:
M-ROM v1.3 Raphael

ROM Language: Dutch

Based on shipped rom 1.95.502.5

But ROM updated to CE OS 5.2.20931 build 20931 AKU 1.5.0 (XIP/SYS ported)

and this has been done...

Added:

- UC (make sure your sdconfig.txt links are correct: 'opslagkaart' instead of 'Storage Card' otherwise it does nothing...)

- Alternate sliding sounds (transformers, star trek, etc)

- Advanced Config v3.3

- TomTom Navigator v7.910.9185 (no maps included, but works fine!)

- Lightsaber 1.0

- Klaxon 2.0.19

- TF3D config 6.7

- MS Voice Command

- Sprite Backup

- CleanGPS data

- HTC GPS Tool

Updated:

- Google Maps NLD version 2.2.0.19

Removed:

- Cyberon Voice Dialing

Tweaks:

- Disabled SMS-threading

- Disabled Security warnings when installing non-certified applications

- Folder icons + re-arranged icons

- Many speed improving tweaks...

This ROM is 'unprotected' (includes all rgu's/dsm's) so can be cooked to your own needs....

Download: Raphael M-Rom v1.3.rar (rapidshare)

Password: XDA-Forever

Enjoy.....
[Touch Pro, Fuze ROM Development] merten3000:
After extensive testing all programs and stuff I always use myself are working great! Did not notice any bugs so far.

So after my TytnII roms I'm now releasing my first working Raphael rom.....

I use radio 1.02.25.28 at the moment which goes along fine with this rom.

If you find any bugs please let me know because I will be starting to build M-Rom 1.4 which will be based on build 20954

Enjoy and let me know how you (dis)like it!!

Greetz Merten
[Touch Pro, Fuze ROM Development] merten3000:
reserved (2)
[Touch Pro, Fuze ROM Development] merten3000:
Reserved (3)
[Touch Pro, Fuze ROM Development] pijltje:
I am downloading it now and will flash

It looks very promising.

I am very pleased with it it works like a charm keep on this good work
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jjo192:
After quite a bit of time on an old probably pointless device, I have managed to create forced resolution boot.img files for the G8141 & G8142.

G8141 Single Sim

[LineageOS20][G8141][4K]

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

G8142 Dual Sim

[LineageOS20][G8142][4K]

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Attached is an archive I put together. It includes:

- Newly built LineageOS 20 image based on Android 13r75 for G8141 or G8142.

- Gapps

- Three boot.img files, one for each resolution to be forced

- Three alternatives to the configuration file I modified to get them to work

- Build instructions if you want to build images for G8141 & G8142

4K by default.

For the build instructions I used WSL2 Ubuntu (22.04.3) with 24GB RAM allocated in .wslconfig. I have also supplied the default location of the 'dsi-panel-maple.dtsi' file that would need to be edited if you wanted to test. Only worried about ID6 not ID3.

In terms of support, it's the LineageOS 20 build, so effectively whatever that supports is what will work.

I will be looking more into this, as 1080p 120 fps seems to have a slight flicker to the screen and feels simultaneously slowish and smoothish, not quiet there yet.

4K works great in my opinion, by default it is set too 400ppi which makes things feel alittle small, but in the settings, under display then 'Display size and text' if you push the sliders to full it looks good in my opinion. Alternatively using Pixel DPi or an ADB comand for 800ppi (ish) will achieve the same.

I have been looking into DRS but it hasn't worked since 7.1.2. Anyone familiar with the forced 4K 8.1 AOSP version that is on here, when using 1080p 120 and 4K the boot animation will be screwed up until the phone starts, once the phone is on closing it and then opening it will set everything right.

Enjoy and if anyone does take this info forward I'd love to know, I'll keep working on bits my end.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] ZG_DEV:
Thanks for this wonderful work :)

Welcome to the forums❤
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jjo192:
Hi again, and thanks. Not too sure how many people still have this device or if it would be helpful. But while I'm messing around it makes sence to share it.