[ROM][9.0.0][m8/m8d] Android Ice Cold Project 14.0 [Official weeklies] - One (M8) Android Development

{
"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 we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP 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:
GZOSP team
LineageOS & CM (R.I.P.) team
 @maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
[B @LorD ClockaN[/B]
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 14.0
Download link: http://dwnld.aicp-rom.com
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
Google Apps:
(link the best one for your device, there are several variants out there right now, pico/nano GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. 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 preform 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 loose 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 loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
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. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and 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 in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
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 it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure might 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!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently supported Root Solution:
Magisk stable
Magisk versions higher than 17.2 doesn't usually require to be flashed on every dirty flash. Depending on the device, you may need to flash it every time. Unless your maintainer says otherwise it should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
To be able to flash using the built-in OTA app, TWRP recovery is needed.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/LineageOS/android_kernel_htc_msm8974
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
 @Claymore1297
 @LorD ClockaN
ROM OS Version: 9.0 Pie
Kernel: Linux 3.4.103
Version Information:
Status: WEEKLY
Release Date: 13-01-2019
You want to see a "normal" night at the "DEV office", click here!!​
XDA:DevDB Information
AICP 14.0, ROM for the HTC One (M8)
Contributors
Claymore1297
ROM OS Version: 9.x Pie
Based On: GZOSP
Version Information
Status: Nightly
Created 2019-01-13
Last Updated 2019-07-11

*Reserved*

*Reserved2*

Ahhh time to bring my HTC M8 back to life!
will install this tonight and leave feeadback

Installed the rom fine but when I try to install gapps it says insufficient space and quits, do I need to resize the partition? Rom loads up and runs great besides that

JaffaTB said:
Installed the rom fine but when I try to install gapps it says insufficient space and quits, do I need to resize the partition? Rom loads up and runs great besides that
Click to expand...
Click to collapse
you could try repartition, or use the magisk module for gapps called "MagicGApps"

Thanks for bringing this up and letting me test.
The Rom runs blazing fast on my m8, can't wait for the newest build!

JaffaTB said:
Installed the rom fine but when I try to install gapps it says insufficient space and quits, do I need to resize the partition? Rom loads up and runs great besides that
Click to expand...
Click to collapse
sounds valid...

Yes, you need to resize system partition in recovery to flash gapps.

New build is up!!
the build is containing mainly the following:
- januar ASB's
- decreased density to 420 (just look better, Icons fitting better on screen)
- builtin JamesDSP
- SELinux to enforce
- camcorder fixed
- latest AICP-stuff
Enjoy!

Using the magisk module worked fine thanks

Rom is fast and works great! Thank you so much for building this rom. Screen Rotation does not work for me. Did anyone else had this issue?

Thanks for the rom, it works great! still gotta test casting.
but i got 1 issue. i can not power off the device or do a advanced reboot to recovery.
1. when i do power off, phone turns off but after a few second it boots up by itself. i have to go into twrp recover and power off there to keep it off.
2. when advanced reboot is turned on trough AICP settings, hitting "reboot to recovery" is just a normal reboot. it wont enter recovery for me.
not sure if its just my device. can anyone else confirn or bust this?

BADA 187 said:
Thanks for the rom, it works great! still gotta test casting.
but i got 1 issue. i can not power off the device or do a advanced reboot to recovery.
1. when i do power off, phone turns off but after a few second it boots up by itself. i have to go into twrp recover and power off there to keep it off.
2. when advanced reboot is turned on trough AICP settings, hitting "reboot to recovery" is just a normal reboot. it wont enter recovery for me.
not sure if its just my device. can anyone else confirn or bust this?
Click to expand...
Click to collapse
Yes it does confirmed plus doesn't on some installs. It needs work before daily use.

Hey I'm having a problem after installing, my phone just wont boot into recovery. I've tried all the possible ways, it just restarts and boots up the phone even after trying to enter recovery through adb

Thats a already known bug.
Hold Vol- Button while your phone is shutting down. It will bring you to the bootloader from where you can boot to recovery.

New build is up!!
the build is containing mainly the following:
- reboot/bootmenu issue solved
- ambient display
- hardware keys overlay (Long press power for torch, Volume buttons)
- FlipFlap (DotView)
Enjoy!

Thanks you for your rom but need tout resize partition ok but what size ?

Boot to recovery - wipe - advanced wipe - tick system partition - repair filesystem - change size - swipe to resize - reboot to recovery and check if the size has changed.
I hope i habe not forgot a step...

Hey thanks for the update, just wanted to say that I could not get away with a dirty flash over the 13th build.
The flash was successful but once phone booted up all kinds of weird things happened.
1. When opening play store I was greeted with a "sign in" button. When pressed nothing happened.
2. Magisk v18 was tripping. The "SafetyNet Check" button had dissapeared. Yes I was connected to a network.
3. Wi-Fi turned itself off 3x.
When those issues appeared so quickly I decided to do a clean flash. And all seems fine now
No idea what the cause was here.

Related

[ROM][UNOFFICIAL][11] LineageOS 18.1 [T710][T715][T715Y][T810][T815][T815Y]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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, I will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.5. Simply flash the linked below version 3.5 or higher, reboot back into recovery, and flash the rom zip again.
Q: Will any of the variants ever receive official builds from LineageOS?
A: In short, no. The reason is that, in order to get a modern version of Android working properly on an ageing device some legacy commits needed to have been re-introduced into the current source branch. These include a fix for something as fundamental as Wi-Fi.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
ROMs
- SM-T710: gts28wifi
- SM-T715/Y: gts28ltexx
- SM-T810: gts210wifi
- SM-T815/Y: gts210ltexx
Open GApps
Magisk
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 18.1 variant, which corresponds to the model of your tablet!
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your tablet and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the tablet.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- The microphone is able to record sound, but the sound is very faint. This is due to Samsung's proprietary drivers, as determined by Skulldron.
- T710 & T715/Y: Camera viewfinder is misaligned with the dimentions of the display, such that the shutter button is almost off the screen
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- bonuzzz, McFy, Skulldron, RaymanFX, CTXz, T_I, and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the gts28ltexx, gts28wifi, gts210ltexx, and gts210wifi.
Sources
- LineageOS
- universal5433
XDA:DevDB Information
LineageOS 18.1, ROM for the Samsung Galaxy Tab S2
Contributors
ripee, ananjaser1211
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 11
Stable Release Date: 2021-09-17
Created 2018-12-15
Last Updated 2020-12-29
Join us on Telegram!
LineageOS is part of the Tab S2 ROM Universe, courtesy of Skulldron.
Reserved
Thanks for the hard work, Ripee.
The ROM works great on my T815; good battery life and performance.
mixer paths
low mic gain and speaker volume seem to be related to the mixer , 2 other roms that are based on stock dont seem to have these issues, will try to port over a fix for the audio. so far everything else works . t710
715 working without problems
Hi, nice to have a dedicated new thread (after the slow dying of bonuzz's thread).
I installed the latest version on my SM-T715 and using it without any problems until now.
Using Magisk v18.
All my apps work after restoring them from Titanium Backup.
No problems with fingerprint (using left hand finger and right hand thumb).
Thanks for your support.
710 new build 1216
Camera works, window still not sized correctly
Mic gain not good
Checking audio
Anybody else also experiencing slower charging of the T810 than before? Mine needs several hours (3+) to be fully charged, before maybe 90 Minutes.
Or maybe its the battery, too old.
dombo1970 said:
Anybody else also experiencing slower charging of the T810 than before? Mine needs several hours (3+) to be fully charged, before maybe 90 Minutes.
Or maybe its the battery, too old.
Click to expand...
Click to collapse
Yes, I actually felt the same, although I didn't measure the time and I have only charged once with this ROM.
Not a big deal though and everything else works great. Battery life seems improved too.
Changelog
Build 1217 for all variants
* Speaker and mic gain fixed, courtesy of Skulldron
* Synced with LineageOS sources
Thanks for your great work! Nice to see that the t815 will receive updates after LOS has dropped it.
Is it possible to provide check-sums for the download files? THX!
ripee said:
Changelog
Build 1217 for all variants
* Speaker and mic gain fixed, courtesy of Skulldron
* Synced with LineageOS sources
Click to expand...
Click to collapse
Great job.
Had to switch back to Nougat.
Telephone didn't work - I could call but nobody could here me. People called me today but I didn't reveive it (nothing, no ring, no message).
And my usual VPN-Connection to my Fritz-Box didn't work.
ThaiDai said:
Had to switch back to Nougat.
Telephone didn't work - I could call but nobody could here me. People called me today but I didn't reveive it (nothing, no ring, no message).
And my usual VPN-Connection to my Fritz-Box didn't work.
Click to expand...
Click to collapse
Did you try Google's own dialer app? AOSP apps can be buggy with uncommonly used functions, such as calling on a tablet.
ripee said:
Did you try Google's own dialer app? AOSP apps can be buggy with uncommonly used functions, such as calling on a tablet.
Click to expand...
Click to collapse
No, I didn't. Simply need a working phone - no time for trying different solutions (I missed a call from school informing me that my daughter is sick).
May try again in the christmas holidays.
Nope no sound on 710
Somehow, in messenger lite, during videochat even if I see myself and the other party, the other party can't see me, just connecting video appears on the screen forever. T810 12.11 build.
Anybody with T815... How is idle drain? ROM works like an absolute champ but noticing strange idle drains while on airplane mode and everything off. Will check BBS overnight tonight to see if it sleeps at all.
Meakii said:
Anybody with T815... How is idle drain? ROM works like an absolute champ but noticing strange idle drains while on airplane mode and everything off. Will check BBS overnight tonight to see if it sleeps at all.
Click to expand...
Click to collapse
No deep sleep for me also, couldn't find any solution so far!
tripLr said:
Nope no sound on 710[/Q
Sound works fine (WiFi not LTE)
Click to expand...
Click to collapse

[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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, I will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: The room is bootlooping the first time I attempt to boot into it after clean flashing. What should I do?[/COLOR]
A: Force reboot using the Power and Volume Down buttons. The rom will boot properly the second time around. This is a known bug and it affects clean flashes only.
Q: Whenever I try flashing any lineage-17.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.4. Simply flash the linked below version 3.4 or higher, reboot back into recovery, and flash the rom zip again.
Q: Will any of the variants ever receive official builds from LineageOS?
A: No.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
ROMs
pitrus-
- SM-T713: gts28vewifi
- SM-T719: gts28velte
- SM-T813: gts210vewifi
- SM-T819: gts210velte
Open GApps
Magisk
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 17.1 variant, which corresponds to the model of your tablet!
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your tablet and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the tablet.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- The rom bootloops only after clean flashing. Force rebooting allows it to boot properly the second time and every time afterwards. See the FAQ's above.
- The cameras work, but with a delayed response, so they are impractical to use.
- T719 & T819: RIL does not work at all.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developer in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Luk1337 and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the gts28velte, gts28vewifi, gts210velte, and gts210vewifi.
Sources
- LineageOS
- team-infusion-developers
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy Tab S2
Contributors
pitrus-
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-03-25
Created 2020-03-21
Last Updated 2021-11-10
Reserved
Join us on Telegram!
LineageOS is part of the Tab S2 ROM Universe, courtesy of Skulldron.
Reserved
TWRP 3.5.2_9-2
The official TWRP for all four variants is built by TeamWin's servers from the outdated android-6.0 branch. A major bug in this branch is that mtp is broken, so I ran my own builds from the android-7.1 branch. I fixed hw encryption, which is why I bumped the version number up to "-2":
twrp-3.5.2_9-2-gts210velte
twrp-3.5.2_9-2-gts210vewifi
twrp-3.5.2_9-2-gts28velte
twrp-3.5.2_9-2-gts28vewifi
it says lineageOS 17.1 but when you click on the google drive link it links to a file that says 16
[email protected] said:
it says lineageOS 17.1 but when you click on the google drive link it links to a file that says 16
Click to expand...
Click to collapse
It is building right now, and I am going to sleep. It will finish building and uploading before I wake up.
ripee said:
It is building right now, and I am going to sleep. It will finish building and uploading before I wake up.
Click to expand...
Click to collapse
Awesome. Glad to see this tablet still getting attention.
@ripee Your link above to the T813 goes to your GTS210wifi (exynos) folder, and not the GTS210VEWifi (snapdragon) folder. I'm going to assume these are different Roms?
I think the GTS210wifi was the T810? Going off this page? (LOS Github link)
you are just linking us to the wrong folder I found the build and the camera isn't working for me not sure if it's me or you right now...
[email protected] said:
you are just linking us to the wrong folder I found the build and the camera isn't working for me not sure if it's me or you right now...
Click to expand...
Click to collapse
It is already mentioned in bug section.
The OpenGapps link points to ARM instead of ARM64.
---------- Post added at 10:28 AM ---------- Previous post was at 10:21 AM ----------
[email protected] said:
you are just linking us to the wrong folder I found the build and the camera isn't working for me not sure if it's me or you right now...
Click to expand...
Click to collapse
Which variant? T719 (gts28velte) does not boot at all.
fmc000 said:
The OpenGapps link points to ARM instead of ARM64.
---------- Post added at 10:28 AM ---------- Previous post was at 10:21 AM ----------
Which variant? T719 (gts28velte) does not boot at all.
Click to expand...
Click to collapse
SM-T713 - gts28vewifi
I had to try a few different gapps to get it working bitgapps seems to do the trick for me
Error 7 whit TWRP 3.3.1-0 with lineage-16.0-20200311-UNOFFICIAL-gts28ltexx
ROMs
ripee
- SM-T713: gts28vewifi
- SM-T719: gts28velte <---------- lineage-16.0-20200311-UNOFFICIAL-gts28ltexx
- SM-T813: gts210vewifi
- SM-T819: gts210velte
SM-T719
---error 7.....
E3004: this package is for device gts28lte, gts28ltexx; yhis device is gts28velte.
????????
To be more clear: gts28velte does not boot, it remains stuck at the bootanimation stage for at least 15 minutes. No gapps, no magisk, only the ROM.
---------- Post added at 10:51 AM ---------- Previous post was at 10:46 AM ----------
fmc000 said:
To be more clear: gts28velte does not boot, it remains stuck at the bootanimation stage for at least 15 minutes. No gapps, no magisk, only the ROM.
Click to expand...
Click to collapse
Full wipe of course.
Inviato dal mio SM-T719 utilizzando Tapatalk
Sometimes they won't boot without gapps
[email protected] said:
Sometimes they won't boot without gapps
Click to expand...
Click to collapse
Will try again with BitGapps and report back.
Edit: not a gapps problem, doesn't boot with BitGapps either.
Inviato dal mio SM-T719 utilizzando Tapatalk
fmc000 said:
Will try again with BitGapps and report back.
Edit: not a gapps problem, doesn't boot with BitGapps either.
Inviato dal mio SM-T719 utilizzando Tapatalk
Click to expand...
Click to collapse
Please send logs.
ripee said:
Please send logs.
Click to expand...
Click to collapse
Would love to but I don't know how to send logs from a non booting device. Anyways, @gkwok had similar problems when he started publishing his own version of the Pie ROM for the gts28velte, maybe he can help.
Inviato dal mio SM-T719 utilizzando Tapatalk
fmc000 said:
Would love to but I don't know how to send logs from a non booting device. Anyways, @gkwok had similar problems when he started publishing his own version of the Pie ROM for the gts28velte, maybe he can help.
Inviato dal mio SM-T719 utilizzando Tapatalk
Click to expand...
Click to collapse
As far as I know, pie on gts28velte should boot when using the official sources.
Let the boot animation run for around 1 minute, then reboot by pressing power + volume down. When the animation disappears, immediately switch to pressing the buttons to go into TWRP. In the advanced menu, tap on File Manager. Navigate to this folder:
Code:
/sys/fs/pstore/
In it there should be two files, ramoops and another one, probably named pstore or something like that. Post both here.
ripee said:
As far as I know, pie on gts28velte should boot when using the official sources.
Click to expand...
Click to collapse
Please have a look at this thread, posts 211-217
https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-16-0-t3838618
ripee said:
Let the boot animation run for around 1 minute, then reboot by pressing power + volume down. When the animation disappears, immediately switch to pressing the buttons to go into TWRP. In the advanced menu, tap on File Manager. Navigate to this folder:
Code:
/sys/fs/pstore/
In it there should be two files, ramoops and another one, probably named pstore or something like that. Post both here.
Click to expand...
Click to collapse
Will try that, thank you.
Error 7 whit TWRP 3.3.1-0 with lineage-16.0-20200311-UNOFFICIAL-gts28ltexx
....
Now there is the correct file.
Regard.
@ripee Logs extracted from a non-booting gts28velte.

Development [SUPERCEEDED][ROM][OFFICIAL][barbet][11] - AICP 16.1 for Pixel 5a

{
"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-R 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:
GZOSP team
LineageOS & CM (R.I.P.) 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 16.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: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
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 R. 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
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:
https://github.com/AICP/kernel_google_redbull
Device tree source:
https://github.com/AICP/device_google_barbet
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:
@Siluxsept
Information:
ROM OS Version: 11.x
Kernel: Linux 4.19.160
ROM {Firmware|Vendor} required: 11
Status: SUPERCEEDED
Release Date: 03-03-2022
You want to see a "normal" night at the "DEV office", click here!!​
AICP Android 12.1 release candidate for Google Pixel 5a
ROM - https://www.androidfilehost.com/?fid=14655340768118475742
BOOT.IMG - https://www.androidfilehost.com/?fid=14655340768118475907
Screenshots here
Reserved
Nice nice for when I get me a pixel 5a. God bless fam.
Thank you for making a ROM for the 5a. Waiting for mine to arrive so I can start testing
Dumb question: does this support substratum?
grandpajiver said:
Dumb question: does this support substratum?
Click to expand...
Click to collapse
Not sure tbh. I never tried Substratum on AICP. We have advanced theming options in AICP Extras replacing it pretty well.
Nice
Why are there weekly updates?
Can I make the back button on the right?
ALWA7SH6 said:
Nice
Why are there weekly updates?
Can I make the back button on the right?
Click to expand...
Click to collapse
Updating hosts for integrated adblock and security patches on 11.
Yes, check AICP Extras -> Onscreen navigation options -> Invert layout
hmm the phone seems to think it's got airplane mode on when it isnt. trying the latest weekly with a t-mobile esim and it wont use the mobile network. im using mindthegapps linked in the post
nvm ignore that. seems ubreakifix broke something inside. it isnt working on stock either.
Hey Sil, quick question. Does your rom include the option to add the cursor arrows to the navigation bar?
Locklear308 said:
Hey Sil, quick question. Does your rom include the option to add the cursor arrows to the navigation bar?
Click to expand...
Click to collapse
Okay never mind. My P5a came in today and somehow I was able to load the ROM without any issues ON MY FIRST TRY. Wow talk about luck on my part... haha.
Anyway, I found the cursor arrows for the navigation drawer...but I found a problem. Or, at least I think it is a bug? When you invert the back and resents button it inverts the arrows as well. Is this intentional? If so... by chance do you think the option to not invert the cursor arrows is possible?
Other than that I love the ROM so far. Tomorrow will be the first test run of the phone and the ROM!
Locklear308 said:
Okay never mind. My P5a came in today and somehow I was able to load the ROM without any issues ON MY FIRST TRY. Wow talk about luck on my part... haha.
Anyway, I found the cursor arrows for the navigation drawer...but I found a problem. Or, at least I think it is a bug? When you invert the back and resents button it inverts the arrows as well. Is this intentional? If so... by chance do you think the option to not invert the cursor arrows is possible?
Other than that I love the ROM so far. Tomorrow will be the first test run of the phone and the ROM!
Click to expand...
Click to collapse
Hmm working okay for me with AOSP keyboard. Are you using GBoard or any other keyboard app?
Siluxsept said:
Hmm working okay for me with AOSP keyboard. Are you using GBoard or any other keyboard app?
Click to expand...
Click to collapse
It's the AOSP keyboard. I can grab some screenshots if that helps. Basically if you leave the navigation bar where the back buttons on the left, the cursor arrows look normal, but if you hit that invert switch to move the back button to the right it also swaps the cursor arrows. It's not just visual though, they work swapped as well.
finally got my phone back from google. flashed the rom per the instructions in the op. i let it restore my apps during setup as it says that should be fine. i cant download anything. the storage permissions seem to be messed up. i grabbed a logcat using the extras app. i tried the reset app pref and it didnt help. the only app i was able to fix was solid explorer, i removed it's access and then regranted it. i tried that with a few more apps but it didnt work.
pbanj said:
finally got my phone back from google. flashed the rom per the instructions in the op. i let it restore my apps during setup as it says that should be fine. i cant download anything. the storage permissions seem to be messed up. i grabbed a logcat using the extras app. i tried the reset app pref and it didnt help. the only app i was able to fix was solid explorer, i removed it's access and then regranted it. i tried that with a few more apps but it didnt work.
Click to expand...
Click to collapse
Sounds like it did not setup data partition correctly. Try this:
- Format data and reboot into recovery
- Flash / sideload ROM and fully reboot into system. Setup PIN or password in security settings. This should initialize and encrypt data.
- Reboot to recovery. Back in TWRP go to Mount -> Decrypt Data to make storage available. Sideload or flash Gapps package, Magisk, etc without wiping
- Boot system and start restoring your apps (3rd party apps like Titanium might cause trouble, refer to respective app devs then)
Hope that helps.
Siluxsept said:
Sounds like it did not setup data partition correctly. Try this:
- Format data and reboot into recovery
- Flash / sideload ROM and fully reboot into system. Setup PIN or password in security settings. This should initialize and encrypt data.
- Reboot to recovery. Back in TWRP go to Mount -> Decrypt Data to make storage available. Sideload or flash Gapps package, Magisk, etc without wiping
- Boot system and start restoring your apps (3rd party apps like Titanium might cause trouble, refer to respective app devs then)
Hope that helps.
Click to expand...
Click to collapse
alright, ill give that a try. i stopped using backup apps a while ago and just use the google backup stuff. ill let you know how it goes. other than this issue the rom is really nice.
got it working, what i did was
- formatted data and reboot to recovery
- flash rom and reboot to recovery
- installed gapps and magisk
- booted and went through setup without setting a pin or anything
- set pin
im not sure if not setting the lockscreen up in setup mattered at all as it defaults to swipe and encrypted. what you said to do also worked but wouldn't let me restore from google
the camera that comes with the rom seems to crash once at every reboot. https://haste.aicp-rom.com/omagewutig other than that, everything is perfect.
side note. i love all the log grabbing stuff built into the rom
Hello, do you plan to update ROM up to Android 12?
pbanj said:
got it working, what i did was
- formatted data and reboot to recovery
- flash rom and reboot to recovery
- installed gapps and magisk
- booted and went through setup without setting a pin or anything
- set pin
im not sure if not setting the lockscreen up in setup mattered at all as it defaults to swipe and encrypted. what you said to do also worked but wouldn't let me restore from google
the camera that comes with the rom seems to crash once at every reboot. https://haste.aicp-rom.com/omagewutig other than that, everything is perfect.
side note. i love all the log grabbing stuff built into the rom
Click to expand...
Click to collapse
Thanks for your report. For camera - need to double-check perms. Probably not to be fixed on R releases anymore. Android 12 around the corner.

[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.0][Bonito/Sargo] Android Ice Cold Project 17.1 [Official]

{
"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:
GZOSP team
LineageOS & CM (R.I.P.) 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: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
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!)
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
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:
https://github.com/AICP/kernel_google_msm-4.9
Device tree source:
https://github.com/AICP/device_google_bonito
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:
@Siluxsept
Information:
ROM OS Version: 12.1
Kernel: Linux 4.9
ROM {Firmware|Vendor} required: 11
Status: STABLE
Release Date: 07-06-2022
You want to see a "normal" night at the "DEV office", click here!!​
Reserved
Reserved
Here we goooo
I can't seem to get Visible service to work, APN's can't be edited either. I would assume there is another way to get service working, just need to be pointed to the correct location.
Thanks!
-edit-
enabling DSDS in phone menu got me up and running. weird.
hi. thanks for all your work! quick question, i have a pixel 3a xl. that is an a/b device, right? was reading your instructions and dont wanna mess up. also, if its an a/b device, will this be a clean install if we can't wipe device?
MikeW14 said:
hi. thanks for all your work! quick question, i have a pixel 3a xl. that is an a/b device, right? was reading your instructions and dont wanna mess up. also, if its an a/b device, will this be a clean install if we can't wipe device?
Click to expand...
Click to collapse
Correct, its A/B. Normal data + cache wipe is okay, just don't wipe system partition.
got it. thanks. one more thing....when rooting, would we still do the same process as before, where we patch the boot image and then flash the patched boot image, etc?
MikeW14 said:
got it. thanks. one more thing....when rooting, would we still do the same process as before, where we patch the boot image and then flash the patched boot image, etc?
Click to expand...
Click to collapse
You can simply use Magisk v23 flashable zip - install or sideload from TWRP / LOS recovery.
Siluxsept said:
You can simply use Magisk v23 flashable zip - install or sideload from TWRP / LOS recovery.
Click to expand...
Click to collapse
Tried to sideload that file and got verification failure something about the footer.
While a little more cumbersome I have always found the following to be the most reliable method to root...
download the latest kernel/recovery file
download the latest magisk.apk from github and load on phone
In the magisk app click on install next to the magisk entry
patch the file you just downloaded
move the file to a pc for fastbooting
reboot the phone into bootloader mode
fastboot flash boot the file you just patched
profit
im open to all suggestions. you guys are the experts. im just appreciative for all the work done and time put into making the rom great.
So which firmware do I need? Do I keep A11 or flash A12 first?
JasonB96 said:
So which firmware do I need? Do I keep A11 or flash A12 first?
Click to expand...
Click to collapse
If you never upgraded to 12 stock firmware do it first.
how is battery in this update?
so wait, im currently on aicp 11. can i just DL aicp 12 onto my phone and update, or do i need to install android 12 stock rom stock rom and then install aicp 12 after?
Hey guys, please scratch 12 firmware requirement. Update from 11 to 12 working fine without flashing 12 stock first. Just clean flash latest weekly.
had trouble getting this rooted. it just got stuck in a bootloop (tried it twice).
MikeW14 said:
had trouble getting this rooted. it just got stuck in a bootloop (tried it twice).
Click to expand...
Click to collapse
Hmm initial root works fine for me with Magisk 23 zip file and LOS/AICP recovery. Can you provide more details? Did you sideload from LOS recovery?
Try attached boot image. I just patched it old fashioned for bonito. Should work.
Patching the boot img for root always worked for me. Something about being able to just boot the img to see if it works first before flashing is appealing to me.
esjames said:
Patching the boot img for root always worked for me. Something about being able to just boot the img to see if it works first before flashing is appealing to me.
Click to expand...
Click to collapse
fastboot boot <image name>?

Categories

Resources