[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance] - Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance] - Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Reserved

Will it work on the dual SIM version XQ-AU52?

ig2205 said:
Will it work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
Of course.

i wish we can have it for our xperia 5ii lol

Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?

dreDREb13 said:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
Click to expand...
Click to collapse
Flash directly, if you don't meet any issue, there is no need to wipe the data.
flyl0 said:
i wish we can have it for our xperia 5ii lol
Click to expand...
Click to collapse
Coming.

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Coming.
Click to expand...
Click to collapse
It would be even better Resurrection Remix
But I'm glad LOS 18.1 is coming, can't wait to try it!

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Click to expand...
Click to collapse
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?

erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?

dreDREb13 said:
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
Click to expand...
Click to collapse
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.
ig2205 said:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?
Click to expand...
Click to collapse
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Will this rom be rebased on the Android 11 stock ROM sources once we have them?

You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?

KriiXOne said:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
Click to expand...
Click to collapse
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
ig2205 said:
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?
Click to expand...
Click to collapse
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.

Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.

Sjll said:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.
Click to expand...
Click to collapse
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.

ig2205 said:
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Post the result here plz.

Sjll said:
Run
Code:
fastboot getvar all
Post the result here plz.
Click to expand...
Click to collapse
Is that the point?

So I installed and everything booted up fine, but I hit a couple snags.
One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.
Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.
Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.
EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...
All looks good otherwise and this is turning out great!

Related

[ROM][OFFICIAL][pioneer][9] LineageOS 16.0

How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

Jozinek said:
Reccomended Gapps for this build?
Click to expand...
Click to collapse
dunno, just try any gapps you want.
btw I recommend downloading new build, I fixed wvm and camera no longer takes an eternity to launch.

Does it use 4.9 kernel or 4.4?

Casserole said:
Does it use 4.9 kernel or 4.4?
Click to expand...
Click to collapse
4.4

Unable to boot?
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.

techboy11 said:
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.
Click to expand...
Click to collapse
Stop flashing twrp lol.

LuK1337 said:
Stop flashing twrp lol.
Click to expand...
Click to collapse
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.

techboy11 said:
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.
Click to expand...
Click to collapse
Try fastboot -w reboot.

LuK1337 said:
Try fastboot -w reboot.
Click to expand...
Click to collapse
That worked. Now boots. Thanks for your help!

Thanks dude

Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!

Schritti said:
Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!
Click to expand...
Click to collapse
Yeah it's a temporary camera app until Snap is back so I won't bother figuring out what's wrong with it.

Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs

Schritti said:
Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs
Click to expand...
Click to collapse
No, I don't.

please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks

zsolt64555 said:
please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks
Click to expand...
Click to collapse
yeah i need to figure out a way to test it without leaving my room first.

LuK1337 said:
yeah i need to figure out a way to test it without leaving my room first.
Click to expand...
Click to collapse
THX your hard work!
Keep it Up.

Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.

zsolt64555 said:
Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.
Click to expand...
Click to collapse
i cant reproduce that, on youtube and twitch with 1080p 60fps everything is smooth, no lags and no glitches

[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [instantnoodlep]

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
LineageOS & CM (R.I.P.) team
Evolution X Team & @AnierinB
GZOSP team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Whole Android Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: Download from HERE
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
16.08.2022 Weeklies were the last builds based on OOS11 base.Starting with 23.08.2022 Builds, we are switching to OOS12 Base.BE ADVISED !!!!DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA. Please follow the instructions in the 2nd post for FW update first, then you can flash New Weeklies.
If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
If you are flashing using OTA, no need to flash GAPPS, .
Currently supported Root Solution:
Magisk versions >= feel free to report. Didn't tested myself.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
Using on board recovery will be enough mostly for your operations.
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_oneplus_instantnoodlep
Contribute to AICP/device_oneplus_instantnoodlep development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:
ROM OS Version: 12.1
Kernel: Linux 4.19.11-perf
ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
Status: STABLE
Release Date: 23-08-2022
You want to see a "normal" night at the "DEV office", click here!!

For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.

If you are on OOS11 based Stock or Custom ROM:
Best approach is to flash stock OOS11 and update to the latest for your device OOS12 OTA.
While it's done, you can follow the flashing instructions over stock OOS12 given below.
Click to expand...
Click to collapse
The current firmware upgrade path is available here as found on the Op8 series Telegram support group:
Spoiler
1. Boot up AICP recovery
2. Go to "Advanced" -> "Enable ADB"
3. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
or in case getprop returns an empty value, use:
adb shell cat /proc/devinfo/ddr_type
4. Download firmware (C33 recommended, minimum C20/21 required) from here:
FirmWares - Google Drive
drive.google.com
5. Go to "Advanced" -> "Enter fastbootd"
6. Execute following commands after opening a command line in the fw directory:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
7. Flash correct XBL files
* For DDR type 0 (DDR4):
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
* For DDR type 1 (DDR5):
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
8. Boot your recovery from here and then install the new update:
Android12L - Google Drive
drive.google.com
9. Now, you can update via OTA safely.
IF YOU ARE ON STOCK OOS12
These instructions are for you:
Spoiler
Thanks to @Anierin_Bliss
First Time Install / Clean Flash
1. Have an unlocked bootloader & OOS 12 (C20 - C33) flashed to both slots.
2. Download vbmeta, recovery, ROM and GAPPS (optional) for your device from here: https://drive.google.com/drive/folders/1A2SeD6YFKJ2S-iiAKmyfgnrEeJz8zjNm
3. Reboot to bootloader
4.
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip
7. Format data, reboot to system & Enjoy !

Thanks to bring the A12 flavour to Op8 pro !

Excellent rom!
A couple of things I noticed.
1. Power button only invokes assistant, even with advanced restart checked.
2. Even though the one touch from AOD is selected, it is not responding at all.
Thanks for this update. I installed it from AICP 16.1 without formatting and it booted with everything still there and working.

HolyHog said:
Excellent rom!
A couple of things I noticed.
1. Power button only invokes assistant, even with advanced restart checked.
2. Even though the one touch from AOD is selected, it is not responding at all.
Thanks for this update. I installed it from AICP 16.1 without formatting and it booted with everything still there and working.
Click to expand...
Click to collapse
1. Disable hold for assitant from Settings -> System -> Gestures -> Press and hold power button.
Then you shall be fine
2. Enabling Pocket mode may cause this. Can you try after disabling Pocket mode in Settings -> Display ?

semdoc said:
1. Disable hold for assitant from Settings -> System -> Gestures -> Press and hold power button.
Then you shall be fine
2. Enabling Pocket mode may cause this. Can you try after disabling Pocket mode in Settings -> Display ?
Click to expand...
Click to collapse
Both items worked. Thanks so much and I wanted to mention thanks for the 48M camera mode which I have not been able to use since I went to custom roms on this phone.

Hi! Great rom ! can we change the icons size on the aicp launcher?
the only flaw I found on this rom is the animation when you minimize an application or switch from one application to another with the navigation gestures, it's slightly buggy, jerky as if it's was at 60hertz, something I had never felt with other roms, it's a shame it was almost flawless in terms of functionality and battery life.

dede3413 said:
Hi! Great rom ! can we change the icons size on the aicp launcher?
the only flaw I found on this rom is the animation when you minimize an application or switch from one application to another with the navigation gestures, it's slightly buggy, jerky as if it's was at 60hertz, something I had never felt with other roms, it's a shame it was almost flawless in terms of functionality and battery life.
Click to expand...
Click to collapse
What if you siwtch to 120 Hz ? I have also great battery life with 120 Hz too... Be sure you switched to 120 from Settings -> Advanced device settings ... (choose min & max values as 120)

Just to validate, you don't need to be on OOS stock prior to falhing the ROM. I'm on AICP 16 now. Also, any GAPPs recoomended over another?

nijohnson said:
Just to validate, you don't need to be on OOS stock prior to falhing the ROM. I'm on AICP 16 now. Also, any GAPPs recoomended over another?
Click to expand...
Click to collapse
Yes you can install from AICP 16 as long as you flash the AICP 17 recovery first.
Any 12.1 GAPPS will work.

Coming from LOS19 / A12 base (lol) (LOS recovery already flashed), i format data then flash AICP, reboot recovery then sideload OpenGapps Pico
Issue #1
Settings app force close when i try to access Fingerprint in Security
Imma try a format data and see if it persists
Issue #2 --> FIXED (available soon ?)
Centered clock isn't centered (because the margin set does start at the front cam punch hole i guess)
Issue #3
No 5G ? Sticks to 4G+ (like LOS)
Issue #4
A System UI Tuner change make 3 statusbar clocks to appear (left center and right)
Issue #5
Battery icon toggle doesnt work (should sélect 'Hidden' in the battery icon style list below)
Issue #6
Smart notification sounds broken

Hey, could you add a small advice to the guide to not update the vendor firmware a12 based on op8 devices? This causes a lot of hardbricks at the moment, due to the fact that oneplus ships the LPDDR4-XBL-Config firmware in the ota packages for the op8p (https://forum.xda-developers.com/t/...pro-8t-9r-with-oxygenos-12-coloros-12.4426167).

And thanks for the work! Would have loved to test the new rom version, but unfortunately i could not even get to installing it thanks to oneplus

Neil_Armstrong_ said:
Coming from LOS19 (LOS recovery already flashed), i format data then flash AICP, reboot recovery then sideload OpenGapps Pico
Issue #1
Settings app force close when i try to access Fingerprint in Security
Imma try a format data and see if it persists
Issue #2
Centered clock isn't centered (because the margin set does start at the front cam punch hole i guess)
Issue #3
No 5G ? Sticks to 4G+ (like LOS)
Issue #4
A System UI Tuner change make 3 statusbar clocks to appear (left center and right)
Issue #5
Battery icon toggle doesnt work (should sélect 'Hidden' in the battery icon style list below)
Issue #6
Smart notification sounds broken
Click to expand...
Click to collapse
How much does the 5g effect you? (I'm sure this is a YMMV kinda thing.)

Anybody know why media keeps pausing during playback? It affects all video and audio and just stops for a a couple of seconds then restarts.
What's really weird on a fresh install if I just install Rocket Music Player and Youtube they are fine and play normal until some point of installing other apps and setting up it quits working proper.
Everything works fine on AICP 16.1 and has for years.
Any suggestion's?
Update: I have tried everything I know what to do and media still stops and starts.

nijohnson said:
How much does the 5g effect you? (I'm sure this is a YMMV kinda thing.)
Click to expand...
Click to collapse
4G+ is totally fine to me
I just point out things that doesn't work

Does the ROM show any issues with Verizon?

nijohnson said:
Does the ROM show any issues with Verizon?
Click to expand...
Click to collapse
No, Verizon works fine on this rom.

Very nice !!! AICP 12.1 came to instantnoodlep .

Is there possibility to use whatapp messenger with google account backup. Latest i've Android 12 installation and it dont work with mind gaaps.
Ok, i have flash ROM and gaaps works ok with Whatsapp.

[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [kebab]

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
LineageOS & CM (R.I.P.) team
Evolution X Team & @AnierinB
GZOSP team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: Download from HERE
Due to new light sensor autobrightness is a mess for now. But will be fixed soon I hope.
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)16.08.2022 Weeklies were the last builds based on OOS11 base.Starting with 23.08.2022 Builds, we are switching to OOS12 Base.BE ADVISED !!!!DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA. Please follow the instructions in the 2nd post for FW update first, then you can flash New Weeklies.
If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
If you are flashing using OTA, no need to flash GAPPS, .
Currently supported Root Solution:
Magisk versions >= feel free to report. Didn't tested myself.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
Using on board recovery will be enough mostly for your operations.
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_oneplus_kebab
Contribute to AICP/device_oneplus_kebab development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:
ROM OS Version: 12.1
Kernel: Linux 4.19.11-perf
ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
Status: STABLE
Release Date: 23-08-2022
You want to see a "normal" night at the "DEV office", click here!!

For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.

bessss

Installed in the early afternoon,
Everything works perfectly for the moment
Pleased to see aicp on A12.
Good work guys !

great work

Flashed and works super smooth

NICE, love these ROMS.'
my 1+8t updated to 12 about 2wks ago, i know i let that slip thru...will have to backflash to 11 prior to flashing this ROM?
OR could i perform a factory reset and follow prompts to install?
Thanks much,
Richard K

racenrich said:
NICE, love these ROMS.'
my 1+8t updated to 12 about 2wks ago, i know i let that slip thru...will have to backflash to 11 prior to flashing this ROM?
OR could i perform a factory reset and follow prompts to install?
Thanks much,
Richard K
Click to expand...
Click to collapse
You gotta be on the oos11 firmware as a base before you can flash any custom a12 roms on the 8t at the moment.

Thanks for the confirmation, looks like im going backwards before forwards!

racenrich said:
Thanks for the confirmation, looks like im going backwards before forwards!
Click to expand...
Click to collapse
Haha yeah. A bit of a pain.

Hi,
AICP on Oneplus 7T pro for a while and now on Oneplus 8T.
What happiness with this ROM on these 2 phones. No bug discovered yet.
There is only the July patches to receive and everything will be perfect (I am aware that the ROM on 8T is recent and that the developers are doing their best -a big thank you to you-).

Hi! Installed AICP 17.1 (latest)today with MindTheGapps 12.1.0 arm64 and any Google service is not working ie. Contacts, Downloading from store (Stucks at pending...). I came from latest OOS as instructed. I noticed that in Play Store's and Play Serveices' Mobile data & Wifi settings there were Setting "Allow network access" toggled off, but didn't help to turn them on
Tried fresh install without Gapps and other Points of Interest (thse are working in fresh install without gapps):
- Developer options not working
- Opening settings/AICP Extras -> "Not rooted ..." Message
- Android notification bar not expanding
- Mobile data not working
Have I missed something?

vezkari said:
Hi! Installed AICP 17.1 (latest)today with MindTheGapps 12.1.0 arm64 and any Google service is not working ie. Contacts, Downloading from store (Stucks at pending...). I came from latest OOS as instructed. I noticed that in Play Store's and Play Serveices' Mobile data & Wifi settings there were Setting "Allow network access" toggled off, but didn't help to turn them on
Tried fresh install without Gapps and other Points of Interest (thse are working in fresh install without gapps):
- Developer options not working
- Opening settings/AICP Extras -> "Not rooted ..." Message
- Android notification bar not expanding
- Mobile data not working
Have I missed something?
Click to expand...
Click to collapse
I have the same problem. And there is no first setup like adding google account and so on. Phone just boot to system and all is messed up...

Zeezala said:
I have the same problem. And there is no first setup like adding google account and so on. Phone just boot to system and all is messed up...
Click to expand...
Click to collapse
I managed to recover from this with these steps:
1) Flash ROM again without Gapps to get access to Developer options and ADB
2) Download MSM Tool for your device from HERE. I used latest European version.
3) Follow precisely THESE instructions to get stock ROM
+) I installed PixelExperience 12 Recovery and ROM and now working device

vezkari said:
I managed to recover from this with these steps:
1) Flash ROM again without Gapps to get access to Developer options and ADB
2) Download MSM Tool for your device from HERE. I used latest European version.
3) Follow precisely THESE instructions to get stock ROM
+) I installed PixelExperience 12 Recovery and ROM and now working device
Click to expand...
Click to collapse
Ahhhh, ok, thanks. Good job.
I use MSM tool everytime I install new rom. So I think there isn't problem in my case. But another recovery is good point. I will try this in the future. Thanks.

Hi, does this ROM has SafetyNet built-in?
Thanks

Great rom thanks for your great work!
Just a small knit pick...
The font for 5G seems really small compared to LTE. Just wondering if that can be tweaked to match the LTE font size.

The night light feature seems a bit too strong even when set at minimum. Can that be tweaked?

i use signal for sms, etc.
when receiving a txt, i dont get the notification banner pop-ups. upon review of settings, everything is proper, but still no pop-ups.
the issue seems to be described per this link:
Android 12 Beta 4: Most notification banner pop-ups are not appearing due to bug
Google is "moving into the final phase" of Android 12. However, a bug in Android 12 Beta 4 sees most notification banners not pop up...
9to5google.com

Newbie question. I have not flashed a rom in a very long time! I just paid off my T-Mobile OnePlus 8t and want to flash this custom rom. I am just on the stock android 11 software from T-Mobile. I understand how to unlock my bootloader and I should be able to follow the provided instructions in the first post. My question is is there anything else I should know before hand. I only ask cause I jumped the gun on my 7T McLaren and the finger print scanner never worked again! Is that the same with the 8t. Or can I simply follow the above instructions and enjoy the rom? Thanks

[OFFICIAL][zippo] LineageOS 20 (Android 13) for the Lenovo Z6 Pro

KNOWN BUGS
Currently only works with bootloader unlocked
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Fingerprint icon is too low compared to actual location of the scanner
Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and maybe assist with TWRP later. I also own a Motorola Edge 30 (dubai) which I maintain LineageOS for, Asus Zenfone 5z (Z01R), and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked

Heyyo, LineageOS 20 official is out and the first build for zippo is up!

@ThE_MarD ,
Will you be including this commit the hardware fix/support for the camera (camera: Expose aux cameras in third party apps) from Chemas Evo build in your Lineage build? I'd rather not have google services installed to use GCAM in order to access the other lens' and the ZUI camera does not install correctly anymore for 13 (it did for 12, partially). There are other apps that don't rely on g-services that are able to access the hardware (HIDL?) switch to select which lens is used for image processing.

Heyyo @project_2501 , after checking with other devs about that commit and also how aux cameras are set up? I think for that we can just modify our props in the device tree tbh. The problem we currently have is we are limiting it to only a few app names. We could transition to an aux camera blacklist since there's probably only a handful of apps that would screw up (I can't remember if it was here or my Asus Zenfone 5z, but the Adobe Scan app would screw up and fail to initialize any camera) so we could just tackle a blacklist as crappy apps show up lol
As you can see here, we mainly expose aux cameras to a few apps and others have to essentially find out themselves like gcam mods
android_device_lenovo_sm8150-common/system.prop at lineage-20 · LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com

@ThE_MarD ,
Will the blacklist instead of a whitelist be applied on the next scheduled build? Thank you for addressing it.

@project_2501 sorry not yet as I need to test it first and I haven't had time yet

Heyyo, lineage-20.0-20230122-UNOFFICIAL-zippo test build is going up! ! It has a new rebased kernel by MikeNG. Please test all functions. It also has a change to swap the aux camera allowed list to an aux camera exclude list to keep things easier and only exclude apps that don't play well with aux cameras so please test a lot of camera apps
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo - OSDN
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo #osdn
osdn.net
@project_2501 if you could please test this build. You can swap between unofficial and official builds at any time

Switching between the camera lens' works (still don't see 48mp for the main lens' resolution); install almost hanged on patching vendor which I found odd. Camera app believes there are six cameras for some odd reason and will crash if selecting the sixth camera, I'm guessing it's also referencing the video profile because it doesn't crash in video mode when selecting the sixth camera (dual lens for video or mixed up with front lens' maybe)? Can you provide a link to the source for the kernel?

@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there

ThE_MarD said:
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
Click to expand...
Click to collapse
Open Camera.
I'm unfamiliar with MikeNG and kernel modifications he may have committed when looking at the source code for the kernel, just wondering since you stated it was using a different kernel (than official LOS?).

@project_2501 oh, Open Camera does things a lot differently than other camera apps so tbh I don't think there's a way to configure it... So I'd recommend just sticking with Aperture or use a gcam mod... But from what you said Open Camera is now seeing more camera apps so the change in aux camera lists commit is working then?

@ThE_MarD , yes I can switch between all the lens'. System stability has not been jeopordized, the app will just crash if trying to process from the sixth camera ID. Do you remember what modes the ZUI camera app had? Was there a dual (both front and back camera) mode? Maybe the sixth profile is for the front camera and the app doesn't switch to it when cycling through the lens' (front camera can still be accessed with a different on screen UI switch anyways). The problem in itself is app related; regardless, the commit works and should be included in the next build for others like myself who enjoy a clean minimalist build with full access to the hardware.

Hi, i'm on firmware 11.0.405 ST.
Now i'm still waiting my SN from Lenovo to unlock bootloader.
Newbie question:
After installing TWRP --> Wipe > tap "Format Data" button > type "yes" > keyboard checkbox > Flash firmware CN 12.5.332 > reboot to recovery or reboot to system ?
Thanks a lot for the rom!

Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.

ThE_MarD said:
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
Click to expand...
Click to collapse
@ThE_MarD , thanks for the reply. Appreciated
I'm still waiting file from Lenovo to unlock bootloader.

Finally got the file to unlock bootloader.
I flashed twrp > shut down the phone > hold Volume Up + Power > but it cannot boot to recovery, only show fastboot/bootloader.
Then I tried I flashed twrp > shut down the phone > Volume Down + Power > fastboot mode > then i select recovery mode > phone restarted > only returned to fastboot mode again.
Any help to solve this problem? failed to flash twrp recovery.
Thanks in advance.

@danz852 just to check, you're flashing it to the recovery partition?
The TWRP website has the full instructions too
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Code:
fastboot flash recovery twrp.img
Otherwise you can try first via Lineage Recovery and follow the LineageOS wiki instructions
Install LineageOS on zippo | LineageOS Wiki
wiki.lineageos.org

Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.html to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.

danz852 said:
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.htmll to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
Click to expand...
Click to collapse
UPDATE:
Finally it worked out:
I'm still using TWRP 3.4.0. Copy firmware L78051_CN_11_5_229_Q_Stable_recovery to internal storage then flash it. Reboot to System. It said my phone partition is corrupted .
Then i reboot the phone to Fastboot mode. I checked bootloader is Locked > proceed with fastboot flash unlock sn.img > fastboot oem unlock-go > reboot to system. After enable USB debugging in Developer Option > reboot to recovery > Wipe Dalvik, system, cache and format data > flash CN 12.5.332 and LineageOS. > reboot to system > Finally it booted to Lineage.
I'm happy. Thanks again @ThE_MarD for the rom!!!

[ROM][13.0][Oneplus8T][UNOFFICIAL] Pixel Extended ROM V5.6 [23/05/2023]

{
"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"
}
PixelExtended ROM for Oneplus8T [kebab]
What is this?
PixelExtended ROM (or PEX for short), We are Combining Pixel Goodies with some essential features you were missing in Pixel Experience, delivering a ROM that promise you stabilty and being feature-rich at the same time . TBH this ROM will keep it's Pixel' idea intact and won't be bloat with unwanted features .
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13 (T)
FeaturesEverything You've Always Wished For With Pixel Experience> OOS (Oxygen OS) Styled Traffic Indicators
> VoLTE Icon Customization
> Smart Charging
> Adaptive Media Playback
> Notification Counter/Logs
> G-Visual Mod
> FOD (Fingerprint On Display) Customizations
> Status Bar Customizations
> Volume Panel Customizations
> LS (Lock Screen) Clock
> Switch Styles
> Tinted QS (Quick Settings) Tiles
> App Lock with Face Unlock
> QS Customizations
> Gesture Customizations
> New Accents/Fonts/Primary Colors
Whats working?
All
First Time Install / Clean Flash
1. Be on the OOS13 (F13 or F15, F62)
2. Download copy_partitions, vbmeta, dtbo, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to recovery
Update
1. Reboot to bootloader
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from Mega
Android OS version: 13.0_r43
Security patch level: May 2023
Build author/Device Maintainer: bojantanasic
Source code: https://github.com/PixelExtended
Prebuilt kernel:
GitHub - bojantanasic/android_kernel_oneplus_sm8250: Android 13 kernel for oneplus 8T
Android 13 kernel for oneplus 8T. Contribute to bojantanasic/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
PixelExtended Developer: Aryan Gupta
Changes 23.05.2023.
-brightnes fix
-fix for theme and fonts
-switch to erofs (now system is fluid like butter)
-add App lock (Settings/Security/More security/App lock)
Kernel
- update kernel to v4.19.283

Includes OOS Cam?

kuto232 said:
Includes OOS Cam?
Click to expand...
Click to collapse
OOS cam not include in rom, you can use LMC8.4 for better result then OOS cam.
Hasli: LMC8.4_R13
Download LMC8.4_R13 by Hasli.
www.celsoazevedo.com
and use config for better result.

Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.

netusername said:
Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.
Click to expand...
Click to collapse
Brightness working just fine,as you can see in screenshot.I don't have second sim card to test, but I think that is fine too.

Can't download the vbmeta and copy partition files from the link you provided.

silverhazesupreme said:
Can't download the vbmeta and copy partition files from the link you provided.
Click to expand...
Click to collapse
Sourceforge delete files from server, very strange. I will upload on mega today.
For install temporary use this files
recovery:
https://mirrorbits.lineageos.org/recovery/kebab/20230119/lineage-20.0-20230119-recovery-kebab.img
vbmeta:
https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20230119/vbmeta.img
copy_partitions:
https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
Thanks LineageOs team for files
Sourceforge has problem with files today!

Good as a daily driver? No stuttering, just fluid?

Goat24K said:
Good as a daily driver? No stuttering, just fluid?
Click to expand...
Click to collapse
Here is small video how fluid is rom, no stuttering. Kernel is great in turns of battery and performance.
Kernel is Illusionx with small performance upgrade by me.Thanks Blaster4385 for kernel.
Video
Streamable Video
Watch this video on Streamable.
streamable.com

Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.

bookofjoshua said:
Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.
Click to expand...
Click to collapse
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.

bojantanasic said:
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.
Click to expand...
Click to collapse
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.

bookofjoshua said:
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.
Click to expand...
Click to collapse
This rom is for F13 or F15 firmware, if you are on Android 12 then this rom is not for you, because touch wil not work.

I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae

ivirtex said:
I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae
Click to expand...
Click to collapse
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?

bojantanasic said:
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?
Click to expand...
Click to collapse
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab

ivirtex said:
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab
Click to expand...
Click to collapse
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img

bojantanasic said:
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img

Click to expand...
Click to collapse
Thanks, flashing dtbo.img allowed me to install the ROM and everything seems to work fine, please update your instructions, so others won't have this problem.

New build are up
Happy flashing

Decent but the sound externally is awful. Very low and static-like. I usually have to turn it down, but i had to turn this ll the way up and i barely heard the song. *sigh* any suggestions? It's the same with the ring tones, they're VERY low.. what is going on here?

Database Develop

welcome