Develop Bugs

Android P on Redmi 5 Plus

For those who want to try Android P here are the how-to.
I just sharing the experience, I´m not involved in the project.
The sources will free-up for the ends of the month so maybe some dev could put his hands on it.
For now it´s unlikely unstable and with some bugs but usable for a basics and sharing some issues could be solved.
A good introducing for a better comprehension :
https://www.xda-developers.com/android-p-beta-port-snapdragon-project-treble-devices/
This is the general thread:
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
These are the steps for our device:
https://forum.xda-developers.com/showpost.php?p=77101817&postcount=308
Maybe someone can wipe too system adding to the steps of wiping from recovery and only will stay vendor partition needed to boot.
Other links:
Treble rom base: https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
Recovery used for this: https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
I tried before with the latest recovery provided for miui 10 (vince_treble_twrp-jay-port-v3), I formatted data to can boot as indicated for some users in the thread but never boot and never recovered the ability to see files and flash nothing more directly (but adb sideload) from this twrp version, any of the three no-verity/lazyflasher/antibootloop worked for this so I started again with Orange Fox recovery. (although any treble recovery could work following right steps indicated)
No need to flash callfix.zip.
Some 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"
}

would appreciate if you provide the list of bugs and what about major things like volte and camera2api?

ridersam said:
would appreciate if you provide the list of bugs and what about major things like volte and camera2api?
Click to expand...
Click to collapse
I didn´t try many, for me it´s in beta level yet but as far as I know VoLTE is a global bug in all devices yet and camera2api it´s not working for me but maybe with other mods can work so in some devices it works, but we can expect that as many users and devs take part of this then we get more advance. I hope that users can share the experiences and so help others.

I use android p. And for me this gsi is much better than los 15.1 ... except for fingerprint. 2api camera works great! only first you need to flash .zip 2api, only after that install the camera application! The battery holds well, and is pleasant and smooth to use.)) I love the new from Google)

I am currently on DP 3 so should i flash clean or dirty flash over DP 3

I did the exact steps and still it goes directly to fastboot and does not boot the os

ibbi.ir7 said:
I am currently on DP 3 so should i flash clean or dirty flash over DP 3
Click to expand...
Click to collapse
DP3 is the GSI, what do you want to flash over DP3?

seekahaa said:
I did the exact steps and still it goes directly to fastboot and does not boot the os
Click to expand...
Click to collapse
Did you made wipes before to flash Cardinal treble?

SubwayChamp said:
Did you made wipes before to flash Cardinal treble?
Click to expand...
Click to collapse
Yes I wiped everything as I supposed to, still nothing.
I will try the same steps again now.

SubwayChamp said:
Did you made wipes before to flash Cardinal treble?
Click to expand...
Click to collapse
I started from start to flash DP 4 and it is more fluid than DP 3.

Anyone tried with a treble enabled custom kernel?

why cardinal treble rom ? cant we use other treble based roms ?

---account closed

---account closed

langster- said:
I got DP4 installed on the Redmi 5 Plus 3GB version. It does work and you can use it but there are some major problems and the rom is totally unusable.
- the launcher crashes constantly (pixel launcher isn't responding) so you lose your navigation and phone is unusable
- even when the launcher isn't crashed everything is so slow (20 seconds to open any app) and the pill switcher is 10 seconds to open
- no double tap to wake phone is a joke
- no fingerprint sensor at all
- no volte
- no camera
- google treble is full of bloatware that you are forced to download for the phone to work
- dark theme doesn't work on settings
All in all a total fail by google just like their new gmail interface, but well done to the developer who tried to port it.
Guys don't waste your time with this just install a normal custom rom.
If you must try it take a nandroid backup first and after restoring your nandroid backup there is a stupid bug in TWRP you have to use file manager to delete /data/system/locksettings.db to get back into your phone!
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-oksFOzjR1o this guy was able to run it flawlessly. You must have done something wrong i guess.

---account closed

langster- said:
see how he doesn't open playstore, that is because the playstore patch is not installed installed yet.
once he installs the playstore patch it will turn into what i described.
i was very excited because of videos like that also, but no, i will reinstall just in case I did something wrong, but i highly doubt it.
Click to expand...
Click to collapse
maybe you are right but atleast i get a hope that our device will soon be running Android P.
another thing do u know why every developer has stopped working on Treble ROMS?

---account closed

I got it to work, and it is cery smooth for a port. My main issue is the wifi keep disconnecting and random freezes on the os. Other than that everything works as smooth as it should even the fingerprint.

---account closed

[ROM] [UNOFFICIAL] Lineage OS 16.0 -- 7/10/19

{
"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"
}
What This Is
This is a personal project to get Lineage OS running on my Pixel 3a. As such it is provided as is, though I will endeavor to provide regular builds and offer limited support as I am able.
What's Been Tested
This is my daily driver, so I've flashed ElementalX kernel and openGapps Pico over stock.
T-Mobile (at least), camera, wifi, bluetooth, gps are used regularly without issue.
What Was Not Tested
Root
Squeeze sensor
Gapps beyond Pico
Known Issues
eSIM doesn't work and has been removed
If flashing Gapps, an app downloaded at first-time setup Data Transfer Tools will crash constantly and needs to be uninstalled. This may mean you can't transfer data from an old phone to this one via setup.
Downloads
Lineage OS 16.0 Unofficial
Installation
I have not had success with an installable zip for TWRP yet, so the rom images must be flashed via fastboot. You should be familiar with fastboot before attempting to install this rom. It is recommended that you back up your current OS before installing a new one.
Installing this or any rom will void your warranty.
After unlocking OEM and your bootloader, boot into bootloader either with fastboot reboot bootloader or by holding VOLUME DOWN + POWER from power off, plug your phone into the computer.
If running on a linux machine with fastboot installed you can execute the flash-all.sh script included in the download. Alternatively or otherwise:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w (to wipe cache and data)
After installing, Gapps (ARM64, 9.0, see note in Known Issues), kernels, Magisk (UNTESTED) and other zips can be installed as normal via TWRP.
I Wanna Go Back
Up-to-date stock images are provided by Google and can be reflashed from bootloader.
Just follow the instructions at the top of the page.
Sources
LineageOS
Vendor proprietary packages (thanks to Dirty Unicorns and ZVNexus)

Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...

Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!

gee one said:
Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
Click to expand...
Click to collapse
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how) wifi calling works fine on T-Mobile, and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
koichirose said:
Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!
Click to expand...
Click to collapse
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working works with Google Photos installed. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.

pipyui said:
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how), and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.
Click to expand...
Click to collapse
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.

Nevermind @koichirose, camera Motion works fine once I installed Google Photos. :good:
gee one said:
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
Click to expand...
Click to collapse
It's odd that it only shows up when I connect to logcat via adb. Local terminal logcat doesn't show me these squeeze errors.
Also, wifi calling working on T-Mobile :good:

Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!

Chronzy said:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
Click to expand...
Click to collapse
I ran into this same issue - had to remove Data Transfer Tools (don't need root for this, since it was downloaded by gapps) and do a cache wipe to be able to download apps again. I think it blocks you from using the play store until you complete google's first-time setup, and this app blocks that (not to mention it crashes frequently).
I'll test out Magisk when I'm able. You may need to enable root access to apps in dev settings, but I'm unsure.

OMG thank u so much! Was waiting for this forever, hope you can make twrp zip

Getting "Sim not Found" on both rooted and unrooted

Tiebe said:
Getting "Sim not Found" on both rooted and unrooted
Click to expand...
Click to collapse
Have you checked OP? eSIM doesn't work. Need physical SIM

Uzephi said:
Have you checked OP? eSIM doesn't work. Need physical SIM
Click to expand...
Click to collapse
I have a physical sim. I solved the problem tho. I just had to reflash the stock radio image

Thanks for putting a build together! Provides even more incentive for me to make the switch over to a 3a Keep up the good work.

Is the device showing as certified without root?

Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.

any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.

Unstroofy said:
Is the device showing as certified without root?
Click to expand...
Click to collapse
It is not certified.
Dreamsocks66 said:
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
Click to expand...
Click to collapse
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
Geo411m said:
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
Click to expand...
Click to collapse
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.

pipyui said:
It is not certified.
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
Click to expand...
Click to collapse
I'll test for you

Neat, I'll get a build together for ya tonight then.

Any chance of a flashable zip for the official twrp?

Question Viper4Android drivers install in loop

Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please?
{
"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"
}

please help me !!

Install ainur narsil in magisk

V0ltan said:
Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please? View attachment 5633897
Click to expand...
Click to collapse
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12

zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
Thank you very much, I will try this now

zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?

this is how i put the files

V0ltan said:
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?
Click to expand...
Click to collapse
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc

zgfg said:
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc
Click to expand...
Click to collapse
Why I is not audio_effect.xml?

V0ltan said:
Why I is not audio_effect.xml?
Click to expand...
Click to collapse
Look also here - good luck:
[Bounty] Viper4android fix
So I'm not sure if I'm doing this the right way, but I think in an effort to get experienced devs to take a look into our viper4android driver loop issue a bounty is in order. I have tried every method I could find to get viper4android to work...
forum.xda-developers.com

I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com

guardian_uk said:
I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com
Click to expand...
Click to collapse
Btw, did your phone come or you upgraded to MIUI 13/A12?
Also, you used Xiaomi.eu ROM (Weekly or Stable) with A12?
I'm asking bcs I'm curious, you are quoting to my post for (stock) MIUI 12.5.8/A12 for Lisa, I'd like to know does it work for A12 as well (potentially different folders for audio drivers)

@zgfg
Phone came with MIUI 12.5 based on Android 11, I upgraded it to MIUI 13 / Android 12. Battery life was pathetic on stock for me, so unlocked and flashed the stable xiaomi.eu ROM.
Moved to an AOSP ROM (PixelOS) a week back because I prefer stock Android any day. Battery life is far better than even xiaomi.eu.
But I was able to successfully install Viper4Android on both xiaomi.eu and now PixelOS using these instructions. Although there is one additional step I did which is not mentioned here. I manually copied the audio_effects.xml file to all the locations mentioned in the instructions. You need to copy over the xml file which has v4a_fx mentioned inside the file after the copyright section. It is also the larger size file (7.93 KB for me). Unfortunately I don't remember where this file is originally stored for you to copy it. But you can search for it using a file manager that supports root. You need to copy this file to the locations mentioned after installing Viper plus the driver and rebooting for the first time.
Also make sure that all other audio mods like AudioFX, Dolby Atmos, etc are not installed before installing Viper. I am aware of Audio Modification Library which integrates multiple audio mods, however I have never used it. I suppose it will be even more difficult to install Viper with AML. I could be wrong though. Anyway, for me Viper is enough.

Apparently the problem is with the atom kernel, I say this because I installed the same OS on my two devices (Alioth and Lisa), on Alioth SuperiorOS uses n0kernel, on Lisa it uses atom kernel, and in Alioth a simple installation of the module audio modification library + V4A already worked, a pity that the same does not happen in Lisa, the same already happened in Evox.
Does anyone know which pixelOS kernel it uses?
I'm seriously thinking about going back to Memeui with Lisa, my last attempt will be AOSPA which apparently doesn't use atom kernel.

dude.. i need help
i use Samsung Galaxy A50 and CRDroid Custom ROM Android 11,
i have installed Viper4Android. when i use loud speaker. it worked very well, but when i play with my earphone plugged in.. driver status said processing : no
can you guys help me please?? thanks.. pardon my english

@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.

guardian_uk said:
@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.
Click to expand...
Click to collapse
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future

Then paer
unsavorypinkie said:
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future
Click to expand...
Click to collapse
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!

guardian_uk said:
Then paer
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!
Click to expand...
Click to collapse
that folder you mentioned is empty, and i've tried to search with my root explorer. unfortunately i don't have audio_effects.xml file on my phone.. how can i solve this sir?? can i download it from the internet??
EDIT : i have found it sir.. i have copied that file from data/adb/modules/VIPER4AndroidFX/system/vendor/edc to vendor/etc but i don't have folder named audio inside but i have folder called dolby

Sorry, I have no idea then. What I do know is Viper will not work with existing audio mods so you'll have to remove/disable those. There is a Magisk module for multiple audio mods, but I have never used it.
That yupik folder is specific to a 11 Lite NE. I have two other phones, they don't have a yupik folder in them. But they are also running Android 11, which is easier to get Viper working on compared to Android 12.
You'll have to research how to get it working specifically for your phone.

Development [ROM][Android 13][OFFICIAL] LineageOS 20 for Xiaomi 11 Lite 5G NE / Mi 11 LE [lisa]

{
"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 is a free, community built, aftermarket firmware distribution of Android 13 (T), 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads
Here
Flashing instructions
Here
Upgrade instructions
Here
Sources:
- LineageOS
- Kernel Tree
Happy modding!

Reserved

Okay but does it run Crysis?

I've been running it and everything seems to work ok

Links provided by you are loopy and I don't seem to find any link to the "firmware.zip" you have mentioned in your website. Please write some more details. I'm very excited to flash it
Edit: Found everything.

Hey @Its_Vixano,
Thank you for this release in the first place, I'm really happy with it. Seems to be stable so far after the few days I've been running it.
I have only noticed some minor UX bugs with the recents(/gestures) while using Trebuchet (I haven't experienced it yet after switching to Lawnchair), but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Other than that, do you know if the camera quality is better with the stock MIUI camera app? If yes, maybe it would also be worth to include it in this ROM as well, since others are starting to include it, I figured it wouldn't be too much of a hassle.
I only meant these as suggestions/observations, if you need more information on the bug, please let me know.
Thanks in advance.

ardrift said:
but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Click to expand...
Click to collapse
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues

Its_Vixano said:
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Click to expand...
Click to collapse
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.

ardrift said:
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
Click to expand...
Click to collapse
Can you try reflashing the fw i mentioned ??

Its_Vixano said:
Can you try reflashing the fw i mentioned ??
Click to expand...
Click to collapse
I flashed it now and it fixed the problem, thanks for confirming that it was working for you.

Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?

Just pushed august ota
enjoy

by_BenjamiN said:
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Click to expand...
Click to collapse
The least i can do for banking apps is to include ih8sn on my builds (which i already do it)

You're doing a remarkable work. What about submit for official build?

Its_Vixano said:
Just pushed august ota
enjoy
Click to expand...
Click to collapse
Thanks a lot for your great work!

AudioSculpt said:
You're doing a remarkable work. What about submit for official build?
Click to expand...
Click to collapse
who knows ?

Not sure where to ask this, I apologize if I'm asking in the wrong place. But how is the lack of the proximity sensor is handled in this ROM?
Do you face any issues when accepting calls or listening to WhatsApp audio messages?
Thanks for sharing your work.

Has anybody managed to get Google wallet working?

Flashed today, so far everything looks very good
Is it possible to get the stock Xiaomi Cam on this rom?
I need makro and ultrawide cam
Thanks a lot for this great Rom

I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.
Ran into a bit of a problem following the flashing guide.
Downloaded the following files:
boot.img
192 MB17 days ago
dtbo.img
24 MB6 days ago
lineage-19.1-20220824-UNOFFICIAL-lisa.zip
1.1 GB17 days ago
vendor_boot.img
96 MB17 days ago
From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.
I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.
Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).
Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.

Development [ROM] LineageOS 19.1 [UNOFFICIAL] [12.1.0] [raven]

{
"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 for Google Pixel 6 Pro[raven]
What is this?
We all know what LIneageOS is, The backbone to most custom android development with a tremendous list of supported devices
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to system
DO NOT USE THE PIXEL LAUNCHER, USE TREBUCHET
Donate
Not needed but always welcomed
Keep in touch
Twitter
Reddit
Android OS version: 12.1
Kernel Source

alvin14 said:
LineageOS for Google Pixel 6 Pro[raven]
Click to expand...
Click to collapse
Any screenshots of settings etc.
Stock kernel or in-built custom?

Texan1 said:
Any screenshots of settings etc.
Stock kernel or in-built custom?
Click to expand...
Click to collapse
Prebuilt

When I attempt to flash your vendor_boot and then boot to recovery, I get stuck at a Google logo and then my phone reboots. Why?
EDIT: I had to extract the vendor_boot.img and boot.img from the Lineage ZIP to get a working recovery.

neelchauhan said:
EDIT: I had to extract the vendor_boot.img and boot.img from the Lineage ZIP to get a working recovery.
Click to expand...
Click to collapse
Would you mind outlining the exact steps you took to flash the rom as I'm a bit confused by the OP, thanks.

I've been using this ROM since yesterday and noticed one somewhat serious bug: touch and hold doesn't work near the screen edges (~1cm) after subsequent screen unlocks. It only works on the first unlock after booting.
Touch and hold worked on the edges before I flashed this ROM. I am using Magisk so should I try without it?
EDIT: Incoming calls also doesn't work on T-Mobile US, when it does on both ProtonAOSP and GrapheneOS. Outgoing calls works fine.
I get an error that says "Carrier settings has crashed". As much as I love LineageOS, I probably will have to flash another ROM for the time being.

Texan1 said:
Would you mind outlining the exact steps you took to flash the rom as I'm a bit confused by the OP, thanks.
Click to expand...
Click to collapse
You need to extract the payload from the OTA. Use a payload extractor, and then use the boot.img and vendor_boot.img from that.

when attempting to flash adb sideload gets hung up at 2% and one time 16%.
EDIT: upon restarting windows and trying brand new usb cord and different slot, i got the 47% and its just stuck there however the underline is still blinking.
EXTRA EDIT: nvm it finally decided to flash xD excuse me and my nonsense.

So looks like this isn't stable enough yet as a daily driver?

so far no issues except the holding on the edges. i have had that when trying to delete a message but a simple restart fixes that
Texan1 said:
So looks like this isn't stable enough yet as a daily driver?
Click to expand...
Click to collapse

Texan1 said:
So looks like this isn't stable enough yet as a daily driver?
Click to expand...
Click to collapse
I've actually been using it today as a daily driver and have came across a few issues such as the phone hanging for a few seconds when making an outgoing call or when receiving calls it'll send them to voicemail The Edge just seems to be an issue sometimes battery life is good with stock kernel.

Another weird quirk I was having. I was in my discord and we were all talking about pizza so I went to go order Domino's and remembered I didn't have the Domino's app and whatever reason could not find the Domino's app on the Google Play store nor could I find DoorDash but going back to derp fest I was able to go ahead and download those apps so I'm not sure if the Google Play store is from a different country? I'm not sure if that is even possible but yeah that was an issue I had last night.

Twiggy000b said:
Another weird quirk I was having. I was in my discord and we were all talking about pizza so I went to go order Domino's and remembered I didn't have the Domino's app and whatever reason could not find the Domino's app on the Google Play store nor could I find DoorDash but going back to derp fest I was able to go ahead and download those apps so I'm not sure if the Google Play store is from a different country? I'm not sure if that is even possible but yeah that was an issue I had last night.
Click to expand...
Click to collapse
Same I just tried to download the same apps and they're not available maybe this ROM is built the first specific country, charging is extremely slow for me...

That's what I was saying

I don't want to needlessly promote my post, but I have another LineageOS 19 build which is more stable: Link here.
My build also supports the regular Pixel 6, but I don't have access to one.
It does not include GApps, but GApps can be installed, and has far fewer issues. The only issue being that screen edges may not work with long press (which this ROM also suffers from).

No need for shameful posting, you're doing great work!