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?

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.

Question Keeping Stock Camera App, Throwing out Google Analytics (boot.img, Magisk, Debloater?)

Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!

lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!

Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM

GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!

lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"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"
}
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also

GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play

[UNOFFICIAL] LineageOS 20 for the Pixel 3a

{
"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"
}
Google Pixel 3a
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 3a .
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
sargo - Official builds - Potentially coming soon!​
sargo - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.​
Find any? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9

Works very well Android 13 it's weird but it's very snappy and fast! Although I found that flashing the new recovery broke the WiFi so I went back to 19,1 recovery and now everything works.

The download links are dead at the moment, for me anyway. I was just about to attempt to upgrade.
EDIT: working again now

I have installed it but every time it starts up I get a notification:
Trust - System security
SELinux is not enforcing, your security has been weakened

Glenn2 said:
I have installed it but every time it starts up I get a notification:
Trust - System security
SELinux is not enforcing, your security has been weakened
Click to expand...
Click to collapse
You can disable that notification in the setting
But seriously: I also had this after upgrading from 19.1 with 19.1 recovery. Then it was gone after clean flashing with 20 recovery.
Awesome ROM! Thanks a lot OP!

gibbsnich said:
You can disable that notification in the setting
But seriously: I also had this after upgrading from 19.1 with 19.1 recovery. Then it was gone after clean flashing with 20 recovery.
Awesome ROM! Thanks a lot OP!
Click to expand...
Click to collapse
When you say clean flash you mean wipe the data and start over?!
Or did you mean, load the new recovery and flash from that?
I just did what the instructions on the website say and sideloaded it using the existing recovery.
I don't want to wipe data unless I really, really have to, it is otherwise working fine (so far anyway).
EDIT: I dirty-flashed it again with adb sideload from the 20 recovery and SELinux is still disabled.

I upgraded to 20.0-20221101-UNOFFICIAL from 19.1-20220909-UNOFFICIAL without wiping data. Then SELinux began to show notification. After updating to 20.0-20221105 the notification disappeared.

I updated and flashed the new 11/05/22 recovery and the WiFi issues were fixed so everything is functional, although I'm still seeing SElinux disabled, of which I have no idea. But I'm really liking this new rom regardless, it's a bit frustrating that some apps downloaded 3rd party are just flat out broken, they don't even attempt to run in some cases

jmat2240 said:
I updated and flashed the new 11/05/22 recovery and the WiFi issues were fixed so everything is functional, although I'm still seeing SElinux disabled, of which I have no idea. But I'm really liking this new rom regardless, it's a bit frustrating that some apps downloaded 3rd party are just flat out broken, they don't even attempt to run in some cases
Click to expand...
Click to collapse
What apps are broken?
Selinux permissive is a temporary thing

npjohnson said:
What apps are broken?
Selinux permissive is a temporary thing
Click to expand...
Click to collapse
The apps I'm talking about are modded , none of the play store official apps, but like SL Bridge, Ram Cleaner, even when I give them all permissions to include accessibility, but yes this is very minor, it's few and far between and my guess is because they are modified packages is all.

Hi - can you guys check if your wifi is running at full speed?
When I do a Speedtest (via Ookla app) my download speed starts off high then quickly drops to half, every time (50M then drops to about 25M). Upload speed is half too.
From other devices (including a Samsung tablet on LOS18.1) this does not happen.
It didn't happen previously with my 3a either. It seems to have coincided with the change to LOS20 but it could of course just be a coincidence that's why I want to check with other users of the ROM.
EDIT: I have discovered that it's the location stuff that cripples the speed. If I turn off the location permission for the Speedtest app or just switch off the 'precise location' switch, the speed is back to normal. Must be an Android 13 'feature'. (The green dot in the corner is always on during the speedtest.)

npjohnson said:
What apps are broken?
Selinux permissive is a temporary thing
Click to expand...
Click to collapse
For me, Bitwarden does not work at all. It instantly closes as soon as you try to login.
EDIT:
The Fdroid version works fine

Can anyone check if selinux enforcing on lasted build?

Clearall2 said:
Can anyone check if selinux enforcing on lasted build?
Click to expand...
Click to collapse
It is not

Now "adb shell getenforce" returns "Enforcing" after updating to 20.0-20221119-UNOFFICIAL. Thanks a lot.

I would like to know if the Google One backup (that include calls history, SMS and all the OS system & apps setting) works with this custom ROM.

kerpert said:
I would like to know if the Google One backup (that include calls history, SMS and all the OS system & apps setting) works with this custom ROM.
Click to expand...
Click to collapse
yup.

Hello!
Wow I really like this build.
I reccomend everyone to run this command in bootloader mode
Code:
fastboot -w
in order to wipe your userdata for a fresh install.
Anyway, I would love a degoogled version, just like lineageos 19.1 ones. I don't like to use google services, and I may not be the only one.
That would be great.
Keep up your work. Cheers!

SkippyDream said:
Hello!
Wow I really like this build.
I reccomend everyone to run this command in bootloader mode
Code:
fastboot -w
in order to wipe your userdata for a fresh install.
Anyway, I would love a degoogled version, just like lineageos 19.1 ones. I don't like to use google services, and I may not be the only one.
That would be great.
Keep up your work. Cheers!
Click to expand...
Click to collapse
Officials won't have google apps.

'Select' button in recent apps view does not work.