Development [ROM] [12.1] [OFFICIAL] Android Ice Cold Project

Search This thread

julioolares

Senior Member
May 12, 2015
146
33
Hello people anyone knows how to remove notch? Or a really big black line taking some space from my display?
 

Hymix

Senior Member
Apr 28, 2016
123
18
Xiaomi Poco X3 Pro
This ROM is working great for me. Fast, responsive, and the battery life seems good. 6h21 SOT with 45% battery remaining means I don't have to charge all the time.

More than enough customisation options for me, too. Thank you, devs!
 

borisku

Senior Member
Jan 19, 2007
582
38
Near Bonn
Samsung Galaxy Tab S
Moto G4
I love AICP since i flashed it onto my ZTE Axon 7 and i was very happy findig it for Poco X3 Pro. But i can´t find the setting where i can switch the standard memory from internal to micro sd. Can anybody put me to the right direction? thx
 

gringo80

Account currently disabled
Jun 8, 2018
743
652
I love AICP since i flashed it onto my ZTE Axon 7 and i was very happy findig it for Poco X3 Pro. But i can´t find the setting where i can switch the standard memory from internal to micro sd. Can anybody put me to the right direction? thx
You can't use your micro-sd as internal storage on the fly ... it must be formatted. A notification pop-up will appear after reboot !
 
  • Like
Reactions: borisku

borisku

Senior Member
Jan 19, 2007
582
38
Near Bonn
Samsung Galaxy Tab S
Moto G4
Thx, i did so without really knowing what i did, cause the sytem wanted the card to be formatted; i thought this was caused by an older 400gb Sandisk Micro SD which would have errors (which i could not find using the sd card on my computer), but i noticed later after reboot that the system uses the sd card for saving data. i missed in settings => Storage the item "standard path", where you could change the standard from internal to sd card under Androids earlier versions ... (maybe the name of the "stations" under settings are not exact, my system speaks german ;-))
 

Ramesh006

Senior Member
Jan 15, 2014
456
153
why this os didn't get any recognition? so far this is best os for me. customisations are great, daily data usage, inbuilt add blocker, selinux switcher and fps counter.
i did a lot of research on what is gaming rom and turns out gaming totally depends on kernel. all aosp roms are almost same software but the way they tweaking the kernel gives better benchmark scores. so i found this os has good customisation then added NGK kernel. now this os is become gaming rom for me. thank you.
 
  • Like
Reactions: borisku

sonvegeta

Senior Member
Feb 22, 2015
255
140
Jundiaí
I need to adress you the best congratulations. It's the best instructions I read for rom installing I've saw in some years! Hope the rom is like your finest writing (i'm downloading)
 

Spardorp

Senior Member
Oct 5, 2009
75
8
Amsterdam
Xiaomi Poco X3 Pro
Tried this ROM, great dark and lots of options to tweak.
But today noticed I cannot play sound from google-podcast on bluetooth. It plays 1 seconds, then the app stops. When I press play again it sounds via speaker while bluetooth still is connected.
The bluetooth settings show as if no codecs are available, it's all greyed out.

Hours later I tried again and captured logcat.
Now it ran okay for 15 seconds, now it showed it ran AAC codec.
But soon the audio stopped. Pressed play and again continued via speaker instead of connected BT.
Attached logcat:
 

Attachments

  • Screenshot_20211220-101032_Instellingen.png
    Screenshot_20211220-101032_Instellingen.png
    140.4 KB · Views: 37
  • Screenshot_20211220-203313_Instellingen.jpg
    Screenshot_20211220-203313_Instellingen.jpg
    71.1 KB · Views: 37
Last edited:
why this os didn't get any recognition? so far this is best os for me. customisations are great, daily data usage, inbuilt add blocker, selinux switcher and fps counter.
i did a lot of research on what is gaming rom and turns out gaming totally depends on kernel. all aosp roms are almost same software but the way they tweaking the kernel gives better benchmark scores. so i found this os has good customisation then added NGK kernel. now this os is become gaming rom for me. thank you.
Hi Ramesh, can I ask which NGK did you install? I only found one for F1, when trying to install via TWRP it says 'unsupported' and then abort. Thank you!
 

YoniOfWar

Member
May 5, 2018
26
4
Xiaomi Poco X3 Pro
I have problems with some banking apps and with games like mobile Apex, it detects root but does not install magisk or supersu, I tried all the available options of the rom and I was not successful. I don't want root .
Screenshot_20220527-230530_Apex_Legends.png
Screenshot_20220527-230545_BNA+.png
Screenshot_20220527-230550_WaUltra.png
 

borisku

Senior Member
Jan 19, 2007
582
38
Near Bonn
Samsung Galaxy Tab S
Moto G4
I dont think that your messages depend on root access (as you dont have), i assume that it is caused by your unlocked bootloader, which was recognized as a security problem. Often you can see on devices with unlocked bootloader a message while booting something like "Your device could not be trusted because of unlocked bootloader"...
 
  • Like
Reactions: YoniOfWar

Trgefcxg

New member
Jul 28, 2020
2
0


logo_black.png


AICP
Proyecto Android helado

AICP es conocido por todos como el "Proyecto Ice Cold" que comenzó en un Desire HD hace años (2012) y desde entonces ha evolucionado hasta convertirse en una ROM madura con la MEJOR comunidad que puedes encontrar.

Hasta Android Lollipop, la ROM siempre se ha basado en AOKP. Desafortunadamente, dado que AOKP detuvo el desarrollo (pero regresó más tarde), cambiamos nuestra base a CM.
Con el cambio de marca de CM a LineageOS (LOS), nos basamos en LineageOS con algunos ajustes de AOSP y luego cambiamos para basarnos en el "Proyecto de código abierto Ground Zero" (GZOSP) para Android Pie.
Cambiamos nuevamente para Android QR con una base de repositorios AOSP y algunas adiciones de LineageOS para repositorios específicos de dispositivos.

Si hay algún error, lo resolveremos si se trata de nuestra base de código. ¡Esta ROM no es compatible con LineageOS, por lo que no hay necesidad de informarles errores / errores!


[CÓDIGO]#incluir <std_disclaimer.h>

/*
* Su garantía ahora es nula.
*
* No somos responsables de dispositivos bloqueados, tarjetas SD muertas,
* Guerra termonuclear o te despiden porque falló la aplicación de alarma. Por favor
* investigue un poco si tiene alguna inquietud sobre las características incluidas en esta ROM
* antes de flashearlo! USTED está eligiendo hacer estas modificaciones y si
* si nos señala con el dedo por estropear su dispositivo, nos reiremos de usted. Duro y mucho.
*
*/
[/CÓDIGO]

features.png

Lista de características (resumen aproximado)


credits.png


Al principio nos gustaría agradecer:

equipo GZOSP
Equipo de LineageOS y CM (RIP)
@maxwen y el resto del equipo de OmniRom
equipo de DU
Equipo Resurrection Remix
equipo AOSiP
Comunidad

team.png


[USUARIO=1184673]@LorD ClockaN[/USUARIO]
[USUARIO=460472]@eyosen[/USUARIO]
[USUARIO=3860593]@semdoc[/USUARIO]
[USUARIO=6425591]@SpiritCroc[/USUARIO]
[USUARIO=6916498]@wartomato[/USUARIO]
[USUARIO=5040396]@Miccia[/USUARIO]
más el resto del grupo loco que llamamos "equipo"



donations.png


Estamos pagando por servidores que construyen semanales y todo lo que viene con esto, por lo que CADA DONACIÓN será realmente apreciada y se usará para cubrir esos gastos.
¡¡Gracias!!



downloads.png


Última versión estable versión 16.1

Enlace de descarga: https://dwnld.aicp-rom.com/

Tenga en cuenta que las compilaciones oficiales se eliminarán de nuestros servidores cada mes debido a los servicios de mantenimiento.
A partir de AICP 15, almacenaremos una copia de la versión más reciente aquí: https://media.aicp-rom.com/vault/ .



changelog.png


Enlace de registro de cambios completo: https://dwnld.aicp-rom.com/
(Simplemente haga clic en el botón de registro de cambios junto al enlace de descarga en la lista de compilaciones disponibles para su dispositivo)

Google Apps:
Se recomienda FlameGapps
https://flamegapps.github.io/download#descargas


issues.png


tu dices...:pags

PREGUNTAS MÁS FRECUENTES:
[OCULTAR] Antes de usar la ROM:
P. ¿Puedo tener una ETA para la próxima compilación?
R. Sí, solo mire aquí para ver en qué día se fabricó su dispositivo.

P. ¿Esta ROM admite núcleos personalizados oficialmente?
R. No. Todavía puede usarlos, pero la discusión debe ir en el hilo del kernel respectivo. ¡No ofrecemos soporte para los errores que pueda encontrar mientras los usa!

P. ¿Esta ROM incluye GApps o tengo que flashearlas por separado?
R. No, no incluimos GApps preconstruidos, debido a posibles problemas de licencia con el software de Google y porque algunos usuarios no quieren GApps preinstalados porque quieren usar servicios alternativos como MicroG o simplemente prefieren mostrar un "sabor" de GApps de su agrado.

P. ¿Esta ROM usa la aplicación de cámara o galería de stock?
R. Depende del dispositivo. En la mayoría de los casos, estas aplicaciones incluyen libs/código propietario y no se pueden incluir en los árboles de dispositivos en Github o corremos el riesgo de que la ROM sea prohibida en Github. En este caso, podemos intentar que sean instalables (separadas del zip de la ROM), o podemos proporcionar una versión de estas aplicaciones con la ROM que no incluye librerías propietarias. A veces también sucede que estas aplicaciones simplemente no están incluidas porque no sentimos la necesidad de hacerlo para el dispositivo en cuestión.

P. ¿Esta ROM tiene captura de pantalla extendida/desplazada?
R. No, la captura de pantalla extendida se implementó usando una aplicación extraída y modificada del firmware del fabricante/imágenes del sistema y también es propietaria. Condujo al cierre de muchas fuentes de ROM en GitHub.

P. ¿Esta ROM tiene FaceUnlock?
R. No, FaceUnlock también fue una aplicación extraída y modificada de algunos fabricantes. Incluso Google eliminó la función Trusted Face (FaceUnlock) por razones de seguridad en Android 9.0/10.x. Agregar la función modificada hizo lo mismo con las fuentes de ROM como se describió anteriormente.

P. ¿Puedes agregar (insertar proveedor meteorológico favorito)?
R. No, no podemos agregar más proveedores meteorológicos a medida que cambian las implementaciones y nosotros (la ROM) ahora tenemos que pagar por la mayoría de los servicios, y eso no es barato, así que decidimos usar el mejor servicio gratuito que pudimos encontrar, el único La forma de agregar la suya es que los usuarios soliciten su propia clave API para usar su servicio preferido.

P. ¿Esta ROM tiene compilaciones oficiales privadas con las bibliotecas propietarias anteriores incluidas?
R. No, creemos en el software de código abierto, de esta manera los usuarios saben lo que hay en la compilación y pueden replicarlo ellos mismos, todas las compilaciones oficiales se compilan en nuestros servidores de compilación usando las fuentes públicas de github y nadie puede (o lo haría) agregar su propias fuentes privadas para la compilación.

Flashear la rom:
P. ¿Qué necesito saber antes de flashear?
A. Verifique las instrucciones intermitentes...

P. ¿Se pueden ensuciar las compilaciones una encima de la otra?
R. Sí, este es el comportamiento habitual al actualizar una nueva compilación oficial mediante (o utilizando) el servicio de actualización integrado.

P. ¿Cómo realizo compilaciones 'dirty flash'?
A. Limpie el sistema, la memoria caché y la memoria caché de ART/Dalvik. Actualice la ROM, GApps (solo es necesario si borra el sistema), su solución raíz preferida y reinicie. O simplemente use la aplicación OTA para realizar esa tarea por usted.

P. ¿Cómo flasheo compilaciones del kernel?
A1. Si es un archivo .img, inicie TWRP y vaya a la página de instalación en TWRP, en la esquina inferior derecha, seleccione "instalar imagen", seleccione el kernel deseado, luego seleccione "iniciar" como destino, luego deslice hacia flash, luego regrese a la pantalla de instalación e instale su método raíz nuevamente, si no desea perder la raíz y reiniciar.
A2. Si es un ZIP flasheable, puedes flashearlo junto con una actualización de ROM o por separado. Vaya a la página de instalación en TWRP, elija el zip del kernel (o agréguelo a la cola flash justo después del zip de la ROM). Luego agregue su método raíz a la cola si no quiere perder la raíz. Ahora deslice para flashear y reinicie después.


Usando la ROM:

P. ¿Debo proporcionar un logcat si informo de un error?
R. Si desea que se solucione más rápido (o en absoluto), entonces sí, definitivamente debe proporcionar un logcat Y el nombre del modelo. (Nota: solo vincule el logcat desde su GDrive, Dropbox, etc. No publique el contenido aquí. Gracias).

P. ¿Cómo obtengo un logcat, qué tipo debo obtener y más preguntas que pueden responderse convenientemente con mi respuesta predeterminada?
A1. Lea esto a fondo. Además, aquí hay una buena aplicación para obtener registros: https://play.google.com/store/apps/details?id=com.tortel.syslog (se necesita raíz).
A2. Si ya está rooteado, puede usar la función integrada para hacer un logcat y proporcionarlo. Solo mire en la sección de otros en la página principal de AICP Extras.
[/OCULTAR]

instructions.png


La ROM debe contener todo lo que necesita para disfrutar de Android R. No necesita instalar ningún complemento, simplemente descargue la última ROM y GApps, luego siga las instrucciones intermitentes y listo.
Si desea que el dispositivo ejecute la ROM "rooteada", puede actualizar una solución raíz de su elección después del archivo zip de la ROM.

Se recomienda ENCARECIDAMENTE borrar por completo su dispositivo antes de flashear y evite restaurar las aplicaciones y los datos del sistema con Titanium Backup (o con cualquier aplicación de copia de seguridad/restauración) ya que esto puede causar problemas de estabilidad que son muy difíciles de depurar, restaurar las aplicaciones normales está bien aunque.
Si cree que sabe lo que está haciendo, está bien, adelante, pero no se queje si experimenta algún comportamiento extraño.

Cómo flashear por primera vez:
(Otra vez: ¡No lo hagas si no lo sabes!)

1. Descargue la ROM y GApps y transfiéralos a su dispositivo.
2. Arranque para recuperación (se recomienda TWRP).
3. Limpie el sistema, la memoria caché y los datos (¡es posible que deba formatear la partición de datos!).
4. Flashee el archivo zip de la ROM.
5. Flashee las GApps (opcional, necesario para, por ejemplo, que funcione Google Playstore)
6. Reinicie y configure su dispositivo, habilite la configuración del desarrollador y en ellos, Desbloqueo OEM/Reinicio avanzado/Conexión USB.
7. Reinicie de nuevo en la recuperación de TWRP.
8. Actualice la solución raíz de su elección (opcional).
9. Reinicie su dispositivo.
¡El procedimiento puede variar de un dispositivo a otro y es un poco diferente en las actualizaciones del sistema!


La ROM tiene persistencia de GApps entre flashes sucios, ¡así que solo tienes que flashearlos una vez! Esto puede diferir en los dispositivos AvB.



Solución raíz admitida actualmente:

Establo de magisk
Las versiones de Magisk> = 20.4 generalmente no necesitan actualizarse en cada flash sucio.
Dependiendo del dispositivo, es posible que deba actualizarlo cada vez, a menos que su mantenedor diga lo contrario, debería estar bien.

PRERREQUISITO PARA ACTUALIZACIONES OTA ("Over-The-Air"):
Se necesita la recuperación de TWRP para poder flashear usando la aplicación OTA incorporada.
¡Asegúrese de estar en la última recuperación de TWRP, tenga en cuenta que esta también podría ser una versión no oficial!
En dispositivos encriptados, deberá ingresar su PIN/contraseña en TWRP antes de que comience el proceso.

sources.png


Si desea contribuir con AICP, o si desea ver en qué se está trabajando/fusionando, no dude en visitar nuestro sistema de revisión de código Gerrit. (¡El enlace está en la parte inferior!)

Fuente del núcleo:
https://github.com/AICP/kernel_xiaomi_vayu
Fuente del árbol de dispositivos:
https://github.com/AICP/device_xiaomi_vayu
https://github.com/AICP/device_xiaomi_sm8150-common
Fuente del proveedor:

Siga esta guía si desea extraer los blobs del proveedor

ROM y enlaces adicionales:
Página de inicio de la AICP
Revisión del código AICP Gerrit
Fuentes AICP en Github
Página de descarga de AICP para compilaciones oficiales y contenido multimedia
Comunidad de discordia AICP
Canal AICP Telegram para notificaciones del servidor sobre compilaciones oficiales

Colaboradores:

[USUARIO=9769628]@SebaUbuntu[/USUARIO]

Información:
ROM OS Versión:
11.x
Núcleo: Linux 4.14
Se requiere ROM {Firmware|Vendedor}: 12.5.3
Estado: ESTABLE
Fecha de lanzamiento: 01/09/2021

Quieres ver una noche "normal" en la "oficina DEV", haz clic aquí !!
Buen trabajo gracias totales
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hello everyone! Unfortunately, I always get a TWRP error message when updating to the latest AICP 12 version (coming from: aicp_vyu_s-17.1-weekly_20220715.zip, latest TWRP-3.6.2-vayu-Nebrassy-03-07-22.img, NIKGAPPS)

    "assert failed: update_dynamic_partitions(package_extract_file("dynamic_patition_op_list"))
    Updater process ended with ERROR: 1
    Error installing zip file '/external_sd/aicp_vyu_s-17.1-weekly_20220729.zip'
    Updating partition details...
    Failes to mount '/system_root' (No suchfile or directory)"

    Any ideas?
    Flash latest MIUI via MiFlash - Tool then flash ROM again. Should work
  • 20


    logo_black.png


    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.
     *
     */

    features.png

    Feature list (rough overview)


    credits.png


    In the beginning, we would like to thank:

    GZOSP team
    LineageOS & CM (R.I.P.) team
    @maxwen and the rest of the OmniRom team
    DU team
    Resurrection Remix team
    AOSiP team
    Community

    team.png


    @LorD ClockaN
    @eyosen
    @semdoc
    @SpiritCroc
    @wartomato
    @Miccia
    plus the rest of the crazy bunch that we call "team"



    donations.png


    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!!



    downloads.png


    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/.



    changelog.png


    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:
    NikGapps Core is recommended


    issues.png


    You tell... :p

    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.


    instructions.png


    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!)

    1. Download the ROM and GApps and transfer them to your device.
    2. Boot to recovery (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
    3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
    4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
    5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
    6. Reboot and set up your device.
    7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
    The procedure may vary from device to device and is a bit different on system updates!


    The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on A/B Devices.



    Currently supported Root Solution:

    Magisk stable
    Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
    Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.

    Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
    TWRP recovery is needed to be able to flash using the built-in OTA app.
    Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
    On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
    Open the updater app, download the update, then press install, press reboot when prompted, you will be taken to TWRP, there isn't any need to flash GApps separately

    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

    sources.png


    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:
    Device tree source:
    Vendor source:

    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:

    @kubersharma001
    @nullxception
    @SebaUbuntu

    Information:
    ROM OS Version:
    12.1
    Kernel: Linux 4.14
    ROM {Firmware|Vendor} required: 13.0.2
    Status: STABLE

    You want to see a "normal" night at the "DEV office", click here!!
    5
    Wow. Thank you @Nebrassy . I am a long time lover of AICP and it is wonderful to see it for this device. Your hard work is much appreciated and I am happy to donate to the cause: Transaction ID 3HG14334YS520444K.
    4
    Official 12.1 builds have started
    3
    I switched from Pixel Plus UI to AICP and I must say that AICP is just as fast and smooth which is impressive considering how much tweaks and customization features are baked into the ROM.

    There is only one small issue. I have observed some gallery lag in this ROM that didn't exist in MIUI or other ROMS. Namely, when I open any gallery app, it takes a few seconds to actually load the images. Has anyone else noticed this or is it an isolated event?

    For consideration I am using the recommended mind the Gapps.
    To be honest I'm not facing this issue..
    I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.
    2
    FlameGapps is now the recommended package for vayu