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

Trying to install GCam, where can I get the latest patched boot image?

I'm following this guide: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414
And it takes you to a thread with old boot images, and I was wondering if there were any ones that were more recent (i.e. January 2020 security patch). Or does it not matter if I'm using this method only to enable camera2api?
Thanks

Grab the latest stock Rom from here and download it (10.0.18.0 is Jan 2020) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then follow this guide until step 9 to get your own patched boot.img : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
It matters which version of the boot.img you're using, if you happen to use an older version, your device won't boot and you won't be able to do what you want.

marstonpear said:
Grab the latest stock Rom from here and download it (10.0.18.0 is Jan 2020) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then follow this guide until step 9 to get your own patched boot.img : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
It matters which version of the boot.img you're using, if you happen to use an older version, your device won't boot and you won't be able to do what you want.
Click to expand...
Click to collapse
Thanks for the help. But after reading that thread, it looks like a lot of people lost their data doing it, so maybe it's not worth it

tomd-87 said:
Thanks for the help. But after reading that thread, it looks like a lot of people lost their data doing it, so maybe it's not worth it
Click to expand...
Click to collapse
Search for my comment in the same thread, I described the way you should follow to avoid data loss. With my method you won't lose your data. But also if this is your first time unlocking the bootloader, you will lose data. If you've unlocked the bootloader before then you won't have any issues. Cheers.

marstonpear said:
Search for my comment in the same thread, I described the way you should follow to avoid data loss. With my method you won't lose your data. But also if this is your first time unlocking the bootloader, you will lose data. If you've unlocked the bootloader before then you won't have any issues. Cheers.
Click to expand...
Click to collapse
I'm at the step where I have to actually run adb shell to set camera2api, but it doesn't detect my device
{
"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"
}

tomd-87 said:
I'm at the step where I have to actually run adb shell to set camera2api, but it doesn't detect my device
Click to expand...
Click to collapse
Go to developer settings in the Settings > System. If you can't see it there, you need to enable it first. To do that go over to About Phone in settings and tap on the Build Number several times, until you get a toast notification saying Developer settings are enabled.
Once you're in the developer settings, find the USB Debugging option and enable it. After you connect your phone and execute "adb shell" command, a pop-up will appear on your phone saying if you want to trust this computer, tap yes then you'll be good to go.
EDIT: I believe you tried to use 7zip for extraction, 7zip can only extract 1 archive at a time and the file you downloaded is compressed twice (tar, gz). WinRAR can decompress the file in one go. Final files have no difference so use whichever suits you best. Don't forget to use my method while locking the bootloader again. Cheers.

Hey! Don't want to open a new forum so I'm just curious which version of gcam you guys are using? Can someone suggest me a gcam? The ones I tried all have some bugs (for example: random freezing, slow motion video lagging etc.). Or there's not a single gcam that has all it's features working on mi a2 lite?
Currently I'm using GCam_v7.0.009-v4.4.front.hdr.working.

andraslate said:
Hey! Don't want to open a new forum so I'm just curious which version of gcam you guys are using? Can someone suggest me a gcam? The ones I tried all have some bugs (for example: random freezing, slow motion video lagging etc.). Or there's not a single gcam that has all it's features working on mi a2 lite?
Currently I'm using GCam_v7.0.009-v4.4.front.hdr.working.
Click to expand...
Click to collapse
There is not a single gcam that has everything working currently, there are 2 reasons for this and lags :
1 - Our CPU is old, so it can't handle gcams' processing that well.
2 - There has never been a single gcam optimized for our device, except for hass31's gcam port. But that gcam's version is 5.1 and although it worked wonders in Oreo, it has focus issues on Pie.
The gcam you're using produces the best results on this phone right now, at least the front and back cameras work. You can try Urnyx05's gcam ports version 6, those will have back camera working, but the front cam HDR+/HDR+ Advanced won't work. If you downgrade to Oreo, you can use hass31's port. Or you can flash a custom kernel on stock Pie ROM, which fixes the focus issues. If you only have Cam2API enabled with a locked Bootloader, I'd suggest sticking to the gcam you're using right now, because it's the one that works properly. But feel free to test other gcam ports here : https://www.celsoazevedo.com/files/android/google-camera/

marstonpear said:
There is not a single gcam that has everything working currently, there are 2 reasons for this and lags :
1 - Our CPU is old, so it can't handle gcams' processing that well.
2 - There has never been a single gcam optimized for our device, except for hass31's gcam port. But that gcam's version is 5.1 and although it worked wonders in Oreo, it has focus issues on Pie.
The gcam you're using produces the best results on this phone right now, at least the front and back cameras work. You can try Urnyx05's gcam ports version 6, those will have back camera working, but the front cam HDR+/HDR+ Advanced won't work. If you downgrade to Oreo, you can use hass31's port. Or you can flash a custom kernel on stock Pie ROM, which fixes the focus issues. If you only have Cam2API enabled with a locked Bootloader, I'd suggest sticking to the gcam you're using right now, because it's the one that works properly. But feel free to test other gcam ports here : https://www.celsoazevedo.com/files/android/google-camera/
Click to expand...
Click to collapse
Thank you for your detailed answer! Guess I stay with the one I use for now. I'm a bit disappointed as the stock camera records slow motion but gcam don't ,but having an app that makes better quality pictures is more important. Shame xiaomi doesn't update their camera app so we could use theirs with Cam2API.

andraslate said:
Thank you for your detailed answer! Guess I stay with the one I use for now. I'm a bit disappointed as the stock camera records slow motion but gcam don't ,but having an app that makes better quality pictures is more important. Shame xiaomi doesn't update their camera app so we could use theirs with Cam2API.
Click to expand...
Click to collapse
Yep, Xiaomi doesn't care about their AndroidOne devices, we learnt that the hard way. Meanwhile as I've mentioned the most stable gcam version out there is hass31's Mi A2 Lite optimised port. I'd suggest giving it a try, if you're willing to flash a custom Kernel on Stock. Because it checks all the boxes you've mentioned (including slo-mo), but it lacks Night Sight.

Not sure if anybody has tried this, sorry I don't have gcam enabled on my device so cannot test, but on my redmi note 4 that is almost the same hardware this one works really well
https://www.celsoazevedo.com/files/android/google-camera/dev-UltraM8/
Ultra m8

[ROM][12 CBT 01][OFFICIAL][BETA]Color OS 12[Oneplus 8 PRO]

Moderator Information
Always be caution when you flash files. Be sure to understand how to backup and rescure yoru device in case of flash failure or something happened. It is the general rule for every flash lover.
Click to expand...
Click to collapse
Color OS 12 CBT 1
Android 12
Only for OnePlus 8 PRO
Spoiler: MSM tools for all 1+ version, please use only for your version IN...
Unbrick/Msm tools for Oneplus Smartphones – Complete Collection
Unbrick/Msm tools can restore any Oneplus smartphone to factory image/Stock OS. In the post, we will be adding all the Unbrick/Msm tools for all the Oneplus smartphones and the list will keep updating whenever Oneplus launches a new Smartphone. Join Techibee Telegram Channel Join Now WhatsApp...
techibee.in
Spoiler: Fingerprint Fix
Just installing ColorOSMagisk-v1.2 module and reboot device.
微博
随时随地发现新鲜事！微博带你欣赏世界上每一个精彩瞬间，了解每一个幕后故事。分享你想表达的，让全世界都能听到你的心声！
m.weibo.cn
Spoiler: Color OS 12
1. Backuped your persist before flashing!
OnePlus 8P how to quickly falsh into ColorOS 12
First you download the MSM Tool of Hydrogen OS
Link: https://yun.daxiaamu.c…8C%85%E6%B0%A211.0.4.4
After the flashing is complete, download Hydrogen OS 11.0.13.13
Select local upgrade, select the downloaded package, and perform OTA upgrade
Link: https://yun.daxiaamu.c…ro/%E6%B0%A211.0.13.13
Then download ColorOS 12 CBT 1
Select local upgrade, select the downloaded package, and perform OTA upgrade
OnePlus 8Pro ColorOS 12 CBT 1
link： https://otaafsc-cost.h…555_e253ead2c7ae5e.zip
Restart the phone after installing 100%
Spoiler: Root
- Unlock Bootloader
- Download and extract ColorOS-12_ROOT_8Pro.zip
- Reboot to bootloader
- Run coloroot.bat
- Done
Spoiler: Sim FIX
If You just booted into ColorOS 12 on 8 Pro and have no signal or other sim issues..
Extract the zip and run simfix.bat from fastboot
SimFix_OnePlus8Pro_ColorOS12
https://mega.nz/file/I…Lzi3cliDjvf0U1BxvlE_og
Spoiler: Screenshot
{
"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"
}

Downloading right now. Any screenshots?

xtcislove said:
Downloading right now. Any screenshots?
Click to expand...
Click to collapse
Added a screenshot to the first topic.
I have not installed it yet, describe pls your experience later.

zloynavseh said:
Added a screenshot to the first topic.
I have not installed it yet, describe pls your experience later.
Click to expand...
Click to collapse
First things first: Thanks for your work.
Everything is working fine but its too much beta to test it as a daily driver.
What i have to say is, i like the new ui overall BUT the OOS11 UI is so much cleaner an i prefer it over any other ui.
-On first boot the numbers to enter my sim code where to big and i couldnt reach the enter key, a reboot fixed it.
No playstore preinstalled.
-Root is working fine
-USB debugging, pc connection has some problems
-Overall it feels good
-It looks and feels clean but i prefer oos look and feel
-Fingerprint animation is awesome
Going back to OOS11 in 10 minutes, you might have some questions first?

More screenshots

xtcislove said:
More screenshots
Click to expand...
Click to collapse
Thx, can you delete part of screenshots with you phone number, ore just smear over it.
Did you check safetynet and GPAY? Is fingerprint works fine?

Oh nice!!! @zloynavseh
I just saw the sim fix. (Last time I test got no-sim error too.)

zloynavseh said:
Thx, can you delete part of screenshots with you phone number, ore just smear over it.
Did you check safetynet and GPAY? Is fingerprint works fine?
Click to expand...
Click to collapse
Yeah thanks didnt saw the number there.
Didnt checked safetynet but gpay was working fine. Fingerprint was working as good as in oos11.

xtcislove said:
First things first: Thanks for your work.
Everything is working fine but its too much beta to test it as a daily driver.
What i have to say is, i like the new ui overall BUT the OOS11 UI is so much cleaner an i prefer it over any other ui.
-On first boot the numbers to enter my sim code where to big and i couldnt reach the enter key, a reboot fixed it.
No playstore preinstalled.
-Root is working fine
-USB debugging, pc connection has some problems
-Overall it feels good
-It looks and feels clean but i prefer oos look and feel
-Fingerprint animation is awesome
Going back to OOS11 in 10 minutes, you might have some questions first?
Click to expand...
Click to collapse
i wasn't able to get root working, could you give a quick instruction?

conquistadore.11 said:
i wasn't able to get root working, could you give a quick instruction?
Click to expand...
Click to collapse
-Unlock Bootloader
-Download and extract ColorOS-12_ROOT_8Pro.zip from first post.
-Reboot to bootloader
-Run coloroot.bat
Done.

What are the chances of this build getting an OTA update since it is a closed beta one?

gsser said:
What are the chances of this build getting an OTA update since it is a closed beta one?
Click to expand...
Click to collapse
Chance more than colorOS 11. Open beta will staring Q1'22.

I'm currently on OOS 11.0.9.9 and directly flashed the CBT through local upgrade. Everything is working fine except fingerprint. All my apps are retained no issues like data loss, no chinese bloatware.

manojkumarn said:
I'm currently on OOS 11.0.9.9 and directly flashed the CBT through local upgrade. Everything is working fine except fingerprint. All my apps are retained no issues like data loss, no chinese bloatware.
Click to expand...
Click to collapse
Did you backuped your persist before flashing? If you didn't do it, I have bad news for you, you will have great difficulty in restoring it! Try to load backup.

zloynavseh said:
Did you backuped your persist before flashing? If you didn't do it, I have bad news for you, you will have great difficulty in restoring it! Try to load backup.
Click to expand...
Click to collapse
Same problem here. I have the persist.img backed up from OOS but replacing data and engineermode folders didn't seem to help

The region are Chinese,, ( on settings, or Europe ?).

conquistadore.11 said:
Same problem here. I have the persist.img backed up from OOS but replacing data and engineermode folders didn't seem to help
Click to expand...
Click to collapse
Did you unblock your Bootloader? Sometimes it's happening when you unblock it.

zloynavseh said:
Did you unblock your Bootloader? Sometimes it's happening when you unblock it.
Click to expand...
Click to collapse
yeah it's unlocked atm. should i re-lock and try again?

xtcislove said:
More screenshots
Click to expand...
Click to collapse
大侠阿木云盘 | 一加手机官方ROM下载
OLAINDEX,Another OneDrive Directory Index
yun.daxiaamu.com

conquistadore.11 said:
yeah it's unlocked atm. should i re-lock and try again?
Click to expand...
Click to collapse
1. Change to Hydrogen OS via MSM, check fingerprint, if it broken resolve via backup persist. Then update Hydrogen.
2. Flashing via MSM Color OS 12 again

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

Development Android 14 Beta Program DP 1

We don't recommend installing this on your main device, and especially if you're not familiar with development or alpha/beta testing. There are quite a few known issues right off the bat:
{
"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"
}
Developer Preview 1
WLAN malfunctions in certain scenarios
Connection fails when casting to a TV display
Red screen is seen when switching from Guest mode to Owner mode in certain scenarios
Manual connection fails after the phone is disconnected from the tablet
WeChat calls may not ring with Bluetooth headsets
Red screen flashes when creating a new calendar
Screen freezes when taking picture with the front camera in WhatsApp
Which devices support the preview?​
OnePlus 11 (all variants except carrier-branded e.g. TMO/VZW)
Where can I get the preview?​Before installing, be aware that installing a developer preview carries a risk of bricking your phone. Make sure you know what you're doing, and backup your files/media before proceeding. Also ensure your battery level is at least 30% and you have at least 5GB space left on your device.
Refer to the forum threads for more information:
OnePlus 11:
Developer Preview 1
Can I revert to the stable version of OxygenOS?​Yes, please read the forum thread of your device as linked above for detailed instructions. Rolling back will completely wipe all your data, so please take a backup before proceeding.
Below is the rollback/downgrade packages for the OnePlus 11. Make sure you choose the correct rollback package for your device and region. We are providing these links purely for your convenience, as rolling back isn't natively supported by our app. After downloading the correct rollback package, move the file from the "Downloads" directory to the topmost directory of internal storage (the same directory that the "Downloads" folder is in). You may also have to rename ".jar" to ".zip".
Then, open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode" (you might have to enter your phone's PIN/password too). Once this is done, "Local upgrade" will once again be visible in Settings -> About device -> Software update -> top-right button. It it doesn't show up, download & install OPLocalUpdate_For_Android13.apk, and use that to install updates locally.
Rollback packages​The following packages will rollback your device to Android 13, and will wipe all your data. Note that these rollback ZIPs will take you back to A.09 even though the latest OOS13 stable version at the time of writing is A.10. These are not the packages you should download if you're looking to update to Android 14/U.
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Thumbnail and image credits: Google/AOSP/OnePlus
Source: Oxygen updater/OnePlus firum

Rollback packages can be very helpful to convert CN Modele to IN, EU or GLO and also to be flashed to solve softbrick devices.

Init_boot_CPH2449_Android 14_DP1

Steve0007 said:
Init_boot_CPH2449_Android 14_DP1
Click to expand...
Click to collapse
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?

kevp75 said:
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
Click to expand...
Click to collapse
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates

Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
exactly what I was thinking lololol

In the meantime... here's CPH2451 A14 Stock and Magisk Patched init_boots

@Steve0007
Could you please rename the topic to something more understandable and manageable?
E.g. "Android 14 beta 1 (DP) for OnePlus 11"
I don't understand why you called it "Google 14" - it just makes no sense.
Thanks.

Hey finally I can convert my phone back to the US firmware.

My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?

lassetth said:
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
Click to expand...
Click to collapse
Try switching fastboot slot. This fixed for me, although it will take you back to a13

JPower123 said:
Try switching fastboot slot. This fixed for me, although it will take you back to a13
Click to expand...
Click to collapse
Thanks, fixed!

cabagekiller said:
Hey finally I can convert my phone back to the US firmware.
Click to expand...
Click to collapse
what are/were you on for firmware?

Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now

kevp75 said:
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
Click to expand...
Click to collapse
Steve0007​Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10

kevp75 said:
Steve0007​Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
Click to expand...
Click to collapse
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)

kevp75 said:
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
Click to expand...
Click to collapse
Yep, as we thought

Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D

t0ng00 said:
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
Click to expand...
Click to collapse
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.

Steve0007 said:
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Click to expand...
Click to collapse
Sorry for not making myself clear, I mean, downloading the apk from the forum and take it to a CN color os device and forcefully "downgrade" it to the 13 ROM - could it be even possible?
Or forcefully for to DP1 NA first and then, down?