[ROM] Official CyanogenMod 14.1 for Falcon (NIGHTLY) - Moto G Original Android Development

[ROM] Official CyanogenMod 14.1 for Falcon (NIGHTLY) - Moto G Original 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"
}
Code:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* I am 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 me for messing up your device, I will laugh at you.
*/
The "N" is for Nougat
some words of wisdom:
1- This is an Android 7.1 Nougat-based release - update your third party addons to ensure compatibility
2- The CM backupscript.sh in recovery will ignore and remove incompatible applications from your system partition (these are usually non-CM apps that users have opted to install). You must install a compatible app (or app pack) to regain that functionality
3- You can flash CM14.1 nightlies directly from CM13 snapshot or CM 13 nightlies (no need to wipe, BUT for optimum results, better follow Clean Update procedure explain below.), provided you read and followed items 1 and 2
ALLERT:
4- Once one CM14 nightlies, you cannot downgrade back to CM13 – if you are thinking of just exploring the release, then take a backup of your existing installation if you want to go back to it.
5- You’ll need an N compatible recovery, i.e. TWRP 3.0.2-1
Happy Flashing,
Latest features :
XDA:DevDB Information
Cyanogenmod 14.1 for Falcon, ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, CyanogenMod Team, Motorola
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: CyanogenMod13
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-09
Last Updated 2016-11-19

Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: Since 20161118, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
-Not confirmed for CM14 as of 20161109- Pro-TIP : To avoid GPS locking issue, refer to #Q7 of the CM12 dedicated FAQ
HOW TO DIRTY UPDATE
Download the rom zip using CM Updater or third party apps like CM downloader, CyanDelta...
Press update.
Wait 2-3 min
HOW TO CLEAN UPDATE : this kind of update helps to avoid any update related issues, you can follow this when coming from CM13 and want to keep you personal data.
ProTip : Read the Changelog and disable features that have been updated between your build and the latest build (this is important when Theme features are updated and it could break things)
Download the rom zip on the CM Website or using CM Updater or third party apps like CM downloader, CyanDelta... make sure you have gapps zip on your device
Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA!
Select the Zips
Swipe to install
Reboot and wait 2-3 min

Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Where are themes/tiles/whatever gone?[/SIZE]CM14.1 I still at early stage of public development, you should expect to face bugs, missing features, regressions, and other things closely related to WIP. Do not complain about it (even less if someone already discussed it in the thread)
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: Why does swipe to write feature doesn't work although it is enabled? [/SIZE]There is a fix for that "known" issue: see here.
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]

reserved

i will try it and will post the results.

Just downloaded the ROM and Pico GApps.
I'm running CM14.1 unofficial before. I'll do the Clean Install anyway.

Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.

Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:

legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
Does the home button long press show recents instead of assistant like with the unofficial 14.1?

cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Click to expand...
Click to collapse
working fine on my xt1033 both sims are working, sms are also working didnt try the call yet

legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.

cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Click to expand...
Click to collapse
same,sim card not getting detected
edit:reflashed it and both sims are getting detected

Can we disable second sim if we want in this latest nightly of 14.1.
Because I need sim disable feature.

drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
yes

drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
Yes, this was fixed a while ago and it is working in this build, head to Settings > Buttons > Configure your home button action(s).
This is build is very stable and the multitasking is unbelievable. Totally worth it!

Hiraethic said:
yes
Click to expand...
Click to collapse
You can change that in buttons option

matmutant said:
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
Click to expand...
Click to collapse
We really appreciate the work you do (in your free time) for our beloved Moto G. I know you guys worked really hard for this to happen, I've been checking the CyanogenMod Gerrit for a while now.
P.S.: I was in no way trying to dissuade anyone from using the dirty update or clean update methods. In my experience, a clean flash is always the most stable in the long run.

battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.

Hiraethic said:
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Click to expand...
Click to collapse
SuperSU over CyanogenMOD should have caused a bootlop, you were lucky.

running 20161109.
* Dual SIM works fine
*Music app is not opening. Showing me that the app is stopped (Is it just me?)
Long press Home button brings Google Assistant after configuring with Buttons settings. (I tweaked build.prop for bringing up Google Assistant)
Battery percentage is showing only on Icon Portrait. None of other icons are working.
It's been 7 hours since I flashed it. The SoT is not that bad.
May be I'll flash abyss kernel later to check if the battery life will be improved and the swipe is definitely working very well on abyss kernel.

Related

[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s

LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
NOTE: This build is unofficial, don't report bugs to the official LineageOS bug tracker.
HOW TO FLASH
Download the ROM from here
Download GAPPS from here
Install TWRP recovery from this thread
Boot to recovery
Wipe Data/Factory reset
Flash LineageOS
Flash GAPPS
Wipe Cache/Dalvik
Boot to system
What works
Audio
Camera
RIL (calls, sms, etc)
GPS
Bluetooth
WiFi
Everything else not listed below
What doesn't work
HDR
WiFi Hotspot
Wireless display
Before asking any question read the FAQ below
Big thanks to @voidzero for letting me use his server to build and for the initial device tree
XDA:DevDB Information
[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s, ROM for the HTC One (M8)
Contributors
root-expert, voidzero
Source Code: https://github.com/M8s-dev/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M firmware base
Version Information
Status: Stable
Beta Release Date: 2018-06-18
Created 2018-06-18
Last Updated 2018-10-27

Changelog
Code:
[B][U]26 October 2018[/U][/B]
* Instagram videos fixed
Code:
[B][U]18 October 2018[/U][/B]
* August/September/October ASB merged
* Use sdFAT instead of exFAT
* Reduce GPS fix time
* Increased speaker volume
* Increased microphone volume
* Increased upper earpiece volume when in-call
* Enabled HDR
* Fixed wakelock
Code:
[B][U]26 July 2018[/U][/B]
* July Android Security updates
* Kernel updated from tag 3.10.49 to tag 3.10.108
* Bluetooth now recognises the correct bt address
* Use low-latency as primary output for notifications and ringtone
* Switched SELinux to enforcing
* When usb composition is on "charge only" adb works
* Enabled audio offloading
* Added the option to disable Double Tap to wake gesture
* Added option to unlock phone with a gesture (you can find it under gestures tab)
* Used newer WiFi configuration files (hope that fixes WiFi problems)
* The name "HTC One M8s" is shown to your pc when connected instead of "Android Phone"
Code:
[B][U]20 June 2018[/U][/B]
[LIST]
[*]Fixed headphones microphone
[/LIST]
Code:
[B][U]18 June 2018[/U][/B]
[LIST]
[*]Initial commit
[/LIST]

Frequently Asked Questions (FAQ)
Q: I flashed the ROM and I'm getting random reboots and crashes
A: Ensure that before flashing this ROM your last stock rom was Android version 6.0. If not follow the instructions on the post below
Q: I found a bug, what should I do?
A: Describe in this thread the issue as best as you can and include steps to reproduce.
Also include a logcat taken the time that the bug happens.
If you had a random reboot don't bother taking a logcat instead pull /sys/fs/pstore/console-ramoops file and atach it to your post.
Q: I want to root this ROM. Should I flash something?
A: Either download su addon from https://download.lineageos.org/extras or flash Magisk.

If you are coming from CM12.1 (Just like I did) then follow these steps
NOTE: If you do not follow these steps, your final Oreo ROM (LOS 15) will crash, you'll suffer randoms reboots and instability problems due to incompatible radio / HTC firmware. This whole update process to Stock 6.0 can take up to 4 hours! So make sure you have the time to do everything correctly, don't cut corners.
I suffered
1. Create a full backup of your ROM using TWRP (v2.8 or v3.0.2.0), Copy your INTERNAL STORAGE and SD Card contents to PC .
During the upgrade from "CM12.1 > 5.0.1 Stock > 6 Stock > LOS 15" you WILL lose your internal data! (because of bootloader relock & unlock again)
2. Relock your bootloader; (Make sure you are using the htc_fastboot.exe)
Turn off phone
Go into bootloader (Hold down VOL DOWN+Power button
Connect USB and enter Fastboot (Should show as FASTBOOT USB)
Open commandprompt;
Code:
htc_fastboot oem lock
The phone should restart and show up as ***RELOCKED***
3. Get your matching RUU from https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If you dont know which RUU to get, follow this thread; https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238 (M8sQL_UL > Firmware (Expert)>Firmware Crypted (Original HTC))
If you get the "Device halted due to Large Image update fail" error during installation, just try another RUU - but make sure it matches your CID.
I got it working using a "signed" version. The "combined-signed" version did not work for me. Your mileage may very.
Click to expand...
Click to collapse
4. In Android Stock (5.0.1), continue the setup and after that go to: Settings > Software updates (At the bottom) > Check for updates
At first I only got 2 APP updates: "HTC Sense" and some other app (cant remember). Update both apps and reboot.
After a reboot check again for updates. Now you get a ~400Mb update. Download and install.
After the first update check again for updates. Now you get a ~1.23Gb update (Update to Marshmallow, Part 1 of 2). Download and install.
After that check again, and now you'll get a ~700Mb update (Update to Marshmallow, Part 2 of 2.)
That's it for going back to the most recent stock version. You now have Android 6.0 Stock running.
To install TWRP (if you want to flash LOS 15)
1. Unlock your bootloader again.
Go to https://www.htcdev.com/bootloader/ and follow the instructions.
2. Flash TWRP.
Code:
htc_fastboot flash recovery twrp-recovery-image-name-and-version.img
After that:
Wipe Cache/Dalvik, Data and System
Install LOS15
Wipe Dalvik again
Flash Gapps
Wipe Dalvik
Boot
Say thank you to @root-expert for keeping this phone alive with the development and @voidzero for providing the build-environment / mirrors
- Jeroen

Nice job! Great work on the rom and keeping the one m8s alive!

New build up!
Headphones microphone is now fixed.
Grab it as usual from here
-Chris

For the users who want to remove the"root icon" ( the status bar), there is no setting to disable it.
{
"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"
}
To remove it:
Connect your M8s to PC with USB
Open CMD
Code:
adb shell settings get secure icon_blacklist
The output is:
Code:
[COLOR="Red"]rotate,headset[/COLOR]
Now enter the output + su
Code:
adb shell settings put secure icon_blacklist rotate,headset,[COLOR="red"]su[/COLOR]
And after that:
Code:
adb reboot
Now the "#" icon is gone from the status bar.
- Jeroen

My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !

brunkonjaa said:
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
Click to expand...
Click to collapse
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris

root-expert said:
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
Click to expand...
Click to collapse
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different

brunkonjaa said:
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
Click to expand...
Click to collapse
I don't believe you have to do that. The only requirement is that your last stock android version was Android 6.0
Post battery statistics here

After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...

GeoEgbA said:
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
Click to expand...
Click to collapse
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris

Problem with google play services
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance

root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min

root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
Click to expand...
Click to collapse
View attachment recovery.log
Try by twrp-3.0.2-0-m8ql.img
View attachment twrp-3.0.2-0-m8ql.zip

GeoEgbA said:
View attachment 4533829
Try by twrp-3.0.2-0-m8ql.img
View attachment 4533830
Click to expand...
Click to collapse
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris

monkyMatys said:
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
Click to expand...
Click to collapse
Hello,
Ensure that you flashed GAPPS straight after flashing the ROM WITHOUT rebooting to system. If you reboot to system and then flash GAPPS you'll have problem and crashes like you do. Also ensure that your previous stock andorid version was android 6.0. If not follow the instructions on this thread to revert back to stock and then try to flash the ROM
-Chris

root-expert said:
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
Click to expand...
Click to collapse
Yes yes that why i wrote that need 3.2.1..0 becouse on 3.0.2.0 get error 7. I flash 3.2.1.0 anf LOS and work great for 15h now sorry for confusion

How long should the first boot take? i followed the instructions, twrp 3.2.1 gave a /persist error but everything else seemed fine. its been 20m and im at the lineage os boot screen.

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

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][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus

Yener, you're amazing. Thanks to you we are on the current Android version. Installation ran without problems. I was so free to attach some screenshots.
What I noticed so far:
- I can confirm the list of things that are working and things that are broken.
- Significantly newer kernel (3.18.138) than LineageOS 15.1 (3.18.115) and of course Nougat (3.18.31).
- Magisk 18.1 works fine (had problems with it under LOS 15.1)
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Will you offer a new TWRP 3.3.0?

LumenReaper said:
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Click to expand...
Click to collapse
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
LumenReaper said:
- The release is an engineering build. @yener90 isn't it common to release userdebug?
Click to expand...
Click to collapse
Everything is normal, I don't know, why it is like that
LumenReaper said:
Will you offer a new TWRP 3.3.0?
Click to expand...
Click to collapse
I'm not planning to change something on TWRP currently.

yener90 said:
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
Click to expand...
Click to collapse
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
yener90 said:
Everything is normal, I don't know, why it is like that
Click to expand...
Click to collapse
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.

LumenReaper said:
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
Click to expand...
Click to collapse
Same bug, will be also fixed.
LumenReaper said:
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.
Click to expand...
Click to collapse
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build

yener90 said:
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build
Click to expand...
Click to collapse
Forget it, my mistake. I should read more carefully.

Update
2019-04-22
• fixed fingerprint removement after reboot/user switch
• fixed partially camera (same like in 15.1)
• fixed reboot to recovery and bootloader for advanced reboot menu
• fixed long time to wake up screen
• fixed deep sleep
ROM

I'm impressed!

Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.

thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice

Sparkrite said:
Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.
Click to expand...
Click to collapse
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.

yener90 said:
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.
Click to expand...
Click to collapse
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
It's doing my head in, it was running well, had rebooted a few times, intentionally, and all was well.
Make a backup and then the problem appears and I don't have time to do much before it re-boots, unfortunately.

Sparkrite said:
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
Click to expand...
Click to collapse
For me it looks like TWRP made some rubbish, which lead to failure on partition.
Normally you would end up in a bootloop. The system wouldn't start.
Use my TWRP then use in TWRP internal file manager.
Go to the location sys/fs/pstore and upload the files here.

Preyer11 said:
thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice
Click to expand...
Click to collapse
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.

yener90 said:
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.
Click to expand...
Click to collapse
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot

Preyer11 said:
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot
Click to expand...
Click to collapse
Its not broken. There is something wrong.
I need to compare both kernels X704F & X704L and check that issue out.

Hey, just wanted to report i also dirty flashed and it worked without problems, i own the F model. Works great so far, awesome! However i have one little bug (i guess it is one): long pressing an app icon to move it does sometimes not work, nothing happens then. but i have this since the 15.1 version. does anyone also have this?
kind regards

I dirty flashed it over lineage 15, after wiping system and caches. I flashed the gapps after the rom and everything works perfectly so far. No bugs yet or problems with apps and files. Thanks Yener, I had lost all hope of ever seeing this device updated.

hi @Yerner90 installed ROM using the format data method (ie wiped everything), so far everything is working good so thanks again for ROM

@yener90 great job, works a treat and you've fixed the led colours and added screenshot back on. I'm keeping an eye on the battery as it's draining much quicker I think.

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

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.

Database Develop

welcome