[NOVUS][ROM][JFLTESPR|6.0.1|UNOFFICIAL|CyanogenMod 13]

[NOVUS][ROM][JFLTESPR|6.0.1|UNOFFICIAL|CyanogenMod 13] - Sprint Samsung Galaxy S 4 General

CyanogenMod is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system.
Code:
/* Your warranty is now void.
/* I am not responsible for bricked devices, dead SD cards,
/* or you getting fired because the alarm app failed.
/* If you have any concerns about features
/* included in this ROM, ask before flashing it!
Information
I present you with Android 6.0.1/CM13 for the Sprint Galaxy S4. This is a WIP, I try to work on it when ever I get a bit of free time.
I will try to post a new weekly build once a week or sooner.
The newest build will be at the top of the downloads list.
Prior to Installation
1) I recommend using and/or upgrading to TWRP 3.0.0 (Install version via 2.8.4 zip, then flash 3.0.0 img to upgrade)
2) Make a complete full backup! I cannot stress this enough! Boot, System, Data, Cache, everything. If for some reason this build doesn't work out for you, no biggie go restore.
3) Full wipe of the system is required (Dalvik/ART Cache, System, Data, Internal Storage, Cache). CM13 is based off android 6.0.1 and is a completely new version requiring a complete new install.
4) Download and have ready in the device's sim card Gapps Version "Arm, 6.0, Pico". (Other variants may work, I have not tested them all)
5) Download and have ready in the device's sim card the new jfltespr CM13 Rom (download below).
Installation
After wipe is fully properly completed...
Reboot in to recovery and go to "Install".
Search for the new Rom.zip where you stored it in the sim and select, DO NOT "Swipe to confirm Flash" at this time, we have to install Gapps first.
BEFORE you swipe, select "Add more Zips" and search for your GappsVersion "Arm, 6.0, Pico" and select.
If you flash the Gapps after the CM install, you will have an error loop so flash during initial install is a necessity.
Now proceed to "Swipe to confirm Flash" and Reboot.
First boot takes some time, but shouldn't take more then 10-15 mins total and progress shouldn't be stalled at any point past 5 mins.
Downloads
cm-13.0-20160321-UNOFFICIAL-jfltespr.zip
cm-13.0-20160321-UNOFFICIAL-jfltespr.zip.md5sum
cm-13.0-20160311-UNOFFICIAL-jfltespr.zip
cm-13.0-20160311-UNOFFICIAL-jfltespr.zip.md5sum
Version Information
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.4.x
Status: Beta
ROM Firmware Test Phone: OK3
Android Security Patch Level : March 1, 2016
XDA:DevDB Information
CM13 jfltespr, ROM for the Sprint Samsung Galaxy S4
Contributors
Novus (aka ThomasJoseph315)
Source Code: https://github.com/CyanogenMod
Build Notes
I've noticed that the APN settings are hard to modify. This may change at a later date, but for now it is what it is. If you use an MVNO like do, you will need to flash the APN settings during the rom flash process just like Gapps. I personally have boost mobile and Moped_Ryder has made a very well Boost Mobile zip, though I had to modify slightly with the settings to get LTE working consistently. If you need a zip for your carrier, download the Boost Mobile Zip Ver-2.2 and use notepad++ to edit it to suit your needs.
If you have LTE, but are still having sms issues, install Chomp SMS, it worked right out of the box for me, but you can also set apns manually within the app itself if needed.
Possible bug with Gapps. On my first boot, I installed Gapps Mini and was getting download errors from the play market. I re-flashed with Pico, seems to be working.

Looks dope! Going to have to test it out! Also, I would recommend you add screenshots!

Thanks, I'm expecting my Sprint S4 soon to use on Ringplus. Is there a zip made for R+ or do I not need one?

New Rom Freshly built. Also don't forget to read the build notes about the connection optimizer

GSM Doesnt Work
GSM doesnt work anyone CM 13. What can I do?

Emergency Calls Fail
Emergency Calls cause the device to Lockup and require a reboot, Unable to make emergency calls at all. Other than that GIANT problem, I love the build!

Related

[ROM] Official CyanogenMod 14.1 for Falcon (NIGHTLY)

{
"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.

[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][OFFICIAL][enchilada][11.0]crDroid Android[v7.30]

NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery, ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0

Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13+).
- No changes to device-specific files.
Known issues:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)

Looking forward on this one, thank you for the effort!

Hopefully android auto and face unlock are working. Thanks in advance.

gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
Can't say anything about Android Auto, but Face Unlock works just fine!

MaWalla99 said:
Can't say anything about Android Auto, but Face Unlock works just fine!
Click to expand...
Click to collapse
Great, will test and report about the android auto and overall Rom. Thanks again.

DC dimming seems to be missing

Welcome back team with a11...even with initial build rom is so stable , like this rom simplicity with so many customisations thankyou

Screenshot ???

vindipi said:
Screenshot ???
Click to expand...
Click to collapse
This Rom has latest Android security patch of January and for screenshots open and scroll down this website
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net

what gapps

DRAKOITYU said:
what gapps
Click to expand...
Click to collapse
I personally used nikgapps...may be all are compatible

gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
After running the Rom for 5 days now I can confirm that it's very stable and has tons of customization. Unfortunately though android auto is not working. face unlocking, camera, etc works fine. Would appreciate it if you could fix the android auto issue in the future build.

Anyone else having issues with GPay? I'm using Magisk, hidden, and GPay still won't work.

Is it possible to update crDroid from 6.13 to 7.2 without data formatting (keeping application and data)?

MaWalla99 said:
Download ROM
TWRP (use 3.5.0 or higher)
Magisk (use 21.2 or higher)
Click to expand...
Click to collapse
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA

mahroze said:
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
Click to expand...
Click to collapse
Twrp 3.3 should work fine with the rom. You can keep using it if you want to. However, there is no extra step to use 3.5 vs 3.3. You have to flash twrp after flashing the rom so you can upgrade to 3.5 by just flashing it instead of 3.3.

Quick questions, this rom have smart charging feature?

Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.

not_the_droid_ur_lookin4 said:
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
Click to expand...
Click to collapse
You have been positing this in more than one thread. This has nothing to do with any rom, and is related to what you are doing with your phone or the phone itself. Telephony is flowless on every Android 11 custom rom for Oneplus 6. And so is GPS, which literally connects in seconds.
First thing you should do is: disable wifi calling, because if your provider doesn't have the feature (or you are not provisioned for it), that could cause your problems. Next, uninstall any mode you might have. Try calling without Gapps.
Also, if you ever used Syberia Rom, you got custom /vendor, which would not work with other custom roms that use stock /vendor. So, you need to re-flash full stock rom onto both slots, which is a pre-requisite for flashing most custom roms. Then follow directions for installing a custom rom.

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