[ROM] [OFFICIAL] BlissRoms [bullhead] - Nexus 5X Android Development

[ROM] [OFFICIAL] BlissRoms [bullhead] - Nexus 5X Android Development

Flashed the rom today and it's awesome. Not too much lag or sluggish/stutter. Thank you dev for maintaining this great rom. Also.. can anyone port the stock gcam on stock os 8.1? It crashes on android 10 and I really need that picture quality. Thanks in advance:good:

Reserved

Reserved

**first** Awesome glad to see someone developing for older devices. Thanks a lot...

Funny, I decided last night I was going to install the new NexusROM today, and copied everything off, to discover Bliss Q this morning! However, I updated the Android platform-tools, wiped everything, and formatted Data; but after the ROM sideload TWRP says "No OS installed!" ? Fwiw, I had been on the Bliss Pie 20190920 build for a while, and had no issues. Thanks though for the work on Q!
EDIT: Ok, wiped/formatted again, used `adb push` this time for BlissQ and open_gapps-arm64-10.0-stock-20191105-BETA, then installed from TWRP...and booting up now. Is `adb sideload` on bullhead via TWRP a known issue with A10? Nice boot animation!
EDIT2: I can't get past the "Copy apps and data" part of setup, even if I try to skip it., getting this crash: "Google Play services keeps stopping" and it cycles from "Just a sec" to Checking Info" to "Checking for Updates" b/t each crash. Tried rebooting; no more Play Services crash did just cycles b/t "Just a sec" and "Checking for Updates" then eventually goes back to the "Copy apps and data" page (incl still with the "Don't Copy" option). Then it random rebooted and got stuck on the boot animation until I forced it off and back on. :-|
EDIT3: Flashed open_gapps-arm64-10.0-stock-20191006-BETA and after backing up to the setup start, the "Copy apps and data" wizard eventually says, "Couldn't sign in: There was a problem communicating with Google servers. Try again later." So I'll wait until I'm on a non-guest network.
EDIT4: After messing with it more, with more random and intentional reboots, it finally got thru setup. Still can't add a Google acct though.

Same here, system locks up after trying to restore apps/data and have to hard reboot out. Will try with the latest gapps beta in a bit as I was using the 20191006 rather than 20191105 packages.
Edit: did a full wipe and formatted data reflashed with opengapps 10 beta mini package build date 20191105. Booted up and is currently restoring from Google backup.

Got it working.
Since this is a new ROM, you'll need to format DATA in TWRP in addition to the instructions in the OP. I also used the nano package from OpenGApps.

jeremywh7 said:
Funny, I decided last night I was going to install the new NexusROM today, and copied everything off, to discover Bliss Q this morning! However, I updated the Android platform-tools, wiped everything, and formatted Data; but after the ROM sideload TWRP says "No OS installed!" ? Fwiw, I had been on the Bliss Pie 20190920 build for a while, and had no issues. Thanks though for the work on Q!
EDIT: Ok, wiped/formatted again, used `adb push` this time for BlissQ and open_gapps-arm64-10.0-stock-20191105-BETA, then installed from TWRP...and booting up now. Is `adb sideload` on bullhead via TWRP a known issue with A10? Nice boot animation!
EDIT2: I can't get past the "Copy apps and data" part of setup, even if I try to skip it., getting this crash: "Google Play services keeps stopping" and it cycles from "Just a sec" to Checking Info" to "Checking for Updates" b/t each crash. Tried rebooting; no more Play Services crash did just cycles b/t "Just a sec" and "Checking for Updates" then eventually goes back to the "Copy apps and data" page (incl still with the "Don't Copy" option). Then it random rebooted and got stuck on the boot animation until I forced it off and back on. :-|
EDIT3: Flashed open_gapps-arm64-10.0-stock-20191006-BETA and after backing up to the setup start, the "Copy apps and data" wizard eventually says, "Couldn't sign in: There was a problem communicating with Google servers. Try again later." So I'll wait until I'm on a non-guest network.
EDIT4: After messing with it more, with more random and intentional reboots, it finally got thru setup. Still can't add a Google acct though.
Click to expand...
Click to collapse
Thank you for kind words and glad you liked it!
Since this is new Rom you have to wipe Data partition during flash. Probably that is why you are facing that issue
Also Gapps OpenGapps some variants have issues so you can flash Bitgapps which works flawlessly i will link that thread here
https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500
Let me know if u face any issues
Enjoy!
#StayBlissful

Ritwyk said:
Since this is a new ROM, you'll need to format DATA in TWRP in addition to the instructions in the OP. I also used the nano package from OpenGApps.
Click to expand...
Click to collapse
jackeagle said:
Since this is new Rom you have to wipe Data partition during flash. Probably that is why you are facing that issue
Click to expand...
Click to collapse
As stated, I had "wiped everything, and formatted Data" which included wiping Data and then also formatting it.
I was able to get the Google Setup to work fine after cleaning installing with the Stock 20191006 OpenGapps, but by this time I was testing NexusROM. When I tried that version on BlissQ, I just did a dirty flash since I hadn't been able to get thru the setup at that point. I suspect a clean flash would also work fine for it. I'm sure I'll be back on Bliss soon for more testing though...

jeremywh7 said:
As stated, I had "wiped everything, and formatted Data" which included wiping Data and then also formatting it.
I was able to get the Google Setup to work fine after cleaning installing with the Stock 20191006 OpenGapps, but by this time I was testing NexusROM. When I tried that version on BlissQ, I just did a dirty flash since I hadn't been able to get thru the setup at that point. I suspect a clean flash would also work fine for it. I'm sure I'll be back on Bliss soon for more testing though...
Click to expand...
Click to collapse
Oh cool cool then ya it will work fine with clean flash
Sure! Happy flashing

It's the best android10 rom from now on.
Sometimes pattern lock setting crashes. So I have to delete locksettings.db to unlock. And chrome has blank page(It can be caused by yesterday update of chrome...).
How can I repair that kind of problems?

TRIPLEFIRST said:
It's the best android10 rom from now on.
Sometimes pattern lock setting crashes. So I have to delete locksettings.db to unlock. And chrome has blank page(It can be caused by yesterday update of chrome...).
How can I repair that kind of problems?
Click to expand...
Click to collapse
Will have a look at this one! is it always ?

jackeagle said:
Will have a look at this one! is it always ?
Click to expand...
Click to collapse
Once crash has happened, that maintains unless locksettings.db is deleted.
Chrome always has infinite loading. Default browser and opera work well.

Great work, all look good.
Only chrome is always freezing or crashing
20191006 OpenGapps
Is there a solution for Chrome?

great rom for my testing bullhead
invert layout for navbar does not seem to work

Google FI Users?
Anybody running Google FI on this ROM and having success with WiFi dialing or being able to force a change from T-Mobile to Sprint? I installed latest OpenGapps beta and latest BlissROM, wiped and loaded and LOVE what I'm seeing so far. However, I am unable place calls on WiFi dialing with a solid WiFi connection and no cell tower access. Using the new "Messaging" app I have been able to send text messages but not receive any back.
Which Gapps are showing the best results?

BlissRoms v12.1 is UP now!!
Download : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Mirror [SF] : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Changelog : Bliss-v12.1
- Issues Fixed
Chrome loading issue fixed
Pattern Lock FC's fixed
Merged with Android 10 Nov Release
Thank you guys for using BlissRoms on your device
Also Huge credits goes to @lakshay18 for continuously working on bullhead
#StayBlissful

jackeagle said:
BlissRoms v12.1 is UP now!!
Download : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Mirror [SF] : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Changelog : Bliss-v12.1
- Issues Fixed
Chrome loading issue fixed
Pattern Lock FC's fixed
Merged with Android 10 Nov Release
Thank you guys for using BlissRoms on your device
Also Huge credits goes to @lakshay18 for continuously working on bullhead
#StayBlissful
Click to expand...
Click to collapse
THX. God Bliss you!
Chrome works perfectly. But pattern lock and password lock still crash sometimes. Does my device have some problems?

Does volte work in this rom?

jackeagle said:
BlissRoms v12.1 is UP now!!
Download : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Mirror [SF] : Bliss-v12.1-bullhead-OFFICIAL-20191112.zip
Changelog : Bliss-v12.1
- Issues Fixed
Chrome loading issue fixed
Pattern Lock FC's fixed
Merged with Android 10 Nov Release
Thank you guys for using BlissRoms on your device
Also Huge credits goes to @lakshay18 for continuously working on bullhead
#StayBlissful
Click to expand...
Click to collapse
incoming call in earphone doesn't work. also voice not coming through earphone during voice call

Related

[ROM][UNOFFICIAL][UBER 4.9.4][Surnia ][7.1.2 r29] HalogenOS CAF [OMS]

Common stuff
The ROM is super stable as of now and we'll maintain a clean and proper ROM.
Known issues are going to be fixed as soon as possible. We don't have infinite time.
Highlights :
Substratum
Full media support (FFMPEG, video codecs, ...)
Great Audio quality, no distortions, no crap
Optimized many portions of the system including surfaceflinger, inputflinger, System Server, and more
Super fast boot
Superuser-capable
Great battery life
Soundmod support (not all soundmods work on Nougat, it's not our fault)
addon.d support (backups your gapps etc. when flashing new build - don't wipe system before flashing!)
init.d support
BusyBox
Disabled Access Time for all partitions (We don't need access time. When access time is enabled, it will store the exact date of the access when a file is accessed, what just wastes write cycles (in theory) and has impact in I/O performance.)
Super smooth
Signature Spoofing toggle (Support for MicroG)
Support for trusted third-party WebViews like Chrome
Long press on home for assist toggle
Security Patches in kernel
OpenGapps (Mini/Micro/Nano recommended) and Banks GApps support
Full KeyHandler & KeyDisabler support
Dexpreopt for faster (first) boot time and less space consumption on data partition
Upgrade & Boot the ROM in just 5 minutes - no more endless waiting for flashing a new build
Very high compatibility with other ROMs
How to update the ROM:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Do not wipe anything
Flash the ROM
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
You don't need to wipe Cache/Dalvik.
You don't need to flash gapps again. There is some magic going on which keeps your GApps. Just make sure that you don't wipe system before flashing.
You don't need more than 5 minutes.
How to install the ROM for the first time:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Wipe system, data and cache (If you want to try a dirty flash, dont wipe anything)
Flash the ROM
Flash gapps if you want
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema

ROM Download Links
Download halogenOS now
ROM Sources
All sources incl. ROM @ GitHub Organisation
Kernel source-https://github.com/LineageOS/android_kernel_motorola_msm8916
Device source- https://github.com/LineageOS/android_device_motorola_surnia
https://github.com/LineageOS/android_device_motorola_msm8916-common
Vendor source- https://github.com/theMuppets/proprietary_vendor_motorola

Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group

Credits
CodeAurora
CyanogenMod
And everyone else who contributed and helps us!
In case you feel left out here, please contact us!
XDA: DevDB Information
HalogenOS, ROM for the Moto E 2015 Surnia
Contributors
amarc78
Source Code: https://github.com/halogenOS
Change Log: https://github.com/halogenOS/android_vendor_xos/blob/XOS-7.0/Changelog.md
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cm 14.x firmware
Based On: CAF
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-05-24
Created 2017-05-24
Last Updated 2017-08-17

Reserved

Reserved

I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.

amarc78 said:
I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.
Click to expand...
Click to collapse
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.

ENRIQUEMM said:
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.
Click to expand...
Click to collapse
That's strange. I flashed a few builds and didn't have that problem. I'll see what I can do.

I'm running a new build now, the nav bar should be activated on first boot. If so, I'll post it shortly.

Wonderful ROM Works to perfection

RubenPCA said:
Wonderful ROM Works to perfection
Click to expand...
Click to collapse
It does run great. Very quick and smooth.
Sent from my LGLS755 using XDA Labs

Great job
My steps
All wipe
Flash ROM
Flash gapps
Flash supersu
Reboot
Init and freezing then reboot and bootloop
Reflash only ROM and gapps
Run
This ROM is fantástic
Just an observation, try to install it from the official twrp 3.1.1 and after doing the backup I was unable to access the recovery. Nor restarting in recovery mode even from the fastboot. I had to put back the squid twrp through adb ...
Sorry my bad english
Enviado desde mi XT1524 mediante Tapatalk

Thanks man rom works perfectly ! No issues on first boot!

Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.

ENRIQUEMM said:
Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.
Click to expand...
Click to collapse
I forgot to mention some Bluetooth issues, but I haven't had any trouble staying connected to anything. I thought the only problem was inbound file transfer. I'm working on it. I've been using Magisk without any issues by the way.

After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds

ENRIQUEMM said:
After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds
Click to expand...
Click to collapse
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.

amarc78 said:
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.
Click to expand...
Click to collapse
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you

ENRIQUEMM said:
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you
Click to expand...
Click to collapse
There is an updated SuperSU I see. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
I haven't tested it yet though.

New build is up. Bluetooth should be all fixed now. @ENRIQUEMM I don't have a smart watch to test with if you want to try again and let me know if your problem is fixed.

Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.

801legend said:
Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.
Click to expand...
Click to collapse
Sometimes old Gapps or a bad data connection can make the setupwizard hang. If you weren't using up to date Gapps try updating them. I'f that doesn't work. Try selecting not using any data or WiFi connection on setup. It worked fine for me with 6-17 Open Gapps before I uploaded the build.
Sent from my Motorola XT1526 using XDA Labs

[ROM][10]Android Open Source Illusion Project[Hotdogb][Official]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Download the Fastboot images zip of the variant you want
- There are two variants, "Official" does not contain Gapps while "Gapps" does.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on

XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: [url]https://www.github.com/AOSiP[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.2 or above
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-14
Last Updated 2020-05-06

Reserved
INSTALLATION PROCEDURE:
MAKE SURE YOU'RE ON THE LATEST OOS FROM HERE
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP7T!!!!!
Considering how the 7T doesn't have TWRP and has dynamic partitions, I'll try to explain everything in detail:
1. If you're coming from another ROM (including OOS) or need to perform a clean flash:
Boot into the bootloader (if you don't know how to do this, you should probably not flash)
Connect your phone to your PC and in an ADB/Fastboot shell, wipe device using
Code:
fastboot -w
Connect your phone to your PC and in an ADB/Fastboot shell, type
Code:
fastboot reboot fastboot
NOTE: If command prompt/line complains about fastboot not being a valid target you need to update fastboot from HERE
Your phone should now be in fastbootd (the UI is exactly like recovery mode so don't get confused)
Read about fastbootd HERE
Type the following to make sure your phone is in fastbootd while also making sure your phone is in the recovery-like UI
Code:
fastboot getvar is-userspace
If the above does returns the value true you can now flash the ROMs, if it doesn't try figuring out what went wrong (I don't want to hear about the failed attempts, please don't spam the thread with them)
Type this command to flash the ROM:
Code:
fastboot update <ROM.zip>
NOTE: IF COMMAND LINE IS SAYING:
Code:
archive does not contain 'xyz.sig'
This is normal, ignore it.
After the above is done, your device will automatically reboot to AOSiP, have fun!
OPTIONAL:
If you want magisk, patch the boot image from the AOSiP site which ends in the name -boot.img, in Magisk manager
Boot to bootloader
Boot into that image (DO NOT FLASH!!!)
Code:
fastboot boot magisk_patched.img
Install Magisk manager and from it select Install > Direct install
Reboot and enjoy AOSiP with Magisk!
Enjoy
OPTIONAL:
If you'd like to convert to F2FS:
Open settings>system>reset options and select Erase all data (factory reset)
This'll wipe all data and convert your device to f2fs automatically!
2. If you're updating the ROM:
a. Via the inbuilt Updater
When you get a notification of new build available, tap it
Tap Download
Wait for Download
Tap install
Wait for install
If you use Magisk, open Magisk Manager, select install, select Install to Inactive Slot (After OTA)
Tap reboot
Enjoy!!
b. Manually via bootloader
Disable all substratum overlays if you have a theme applied
Boot into fastbootd
If you're booted into the system
Code:
adb reboot fastboot
If you're booted into bootloader
Code:
fastboot reboot fastboot
Flash the ROM using
Code:
fastboot update <ROM.zip>
NOTE: YOU DO NOT NEED TO WIPE DATA WHEN UPDATING
Reboot to system and enjoy
NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).
KNOWN ISSUES:
Auto brightness is wonky in dark enviroments Fixed in 20200625

Reserved
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your OOS base versions in reports. (Eg: 10.0.1, 10.0.2, 10.0.6 etc.)
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

FREQUENTLY ASKED QUESTIONS:
Q: Fastboot isn't allowing me to flash system image, what am I doing wrong?
A: You haven't booted to fastbootd (the UI looks like recovery and fastboot devices command shows the device in fastboot mode)
Q: What GApps do I flash?
A: You cannot flash Gapps on the device, use the Gapps variant build instead if you need Gapps.
Q: When booting to the Magisk patched image, it leads to crashdump mode.
A: You didn't select the first two options in Magisk Manager before patching the boot image under Advanced settings (i.e. Preserve force encryption and Preserve AVB 2.0/dm-verity).
Q: Do I have to wipe data if coming from another ROM?
A: Yes, I will not be providing help/support to users that haven't wiped data when coming from another ROM.
Q: How often will I be getting updates?
A: The plan is for weeklies, if unavoidable circumstances come up, please don't spam the thread. I will release a build as soon as one is ready.
Q: Does VoLTE/VoWiFi work?
A: VoLTE works, I have tested on Airtel in India and a couple of my US based testers have too.
VoWiFi (WiFi Calling) works based on my testers in the US and for me on Airtel (India), let me know about other carriers.
Q: Does Android Auto work?
A: I don't have accessibility to an Android Auto vehicle nor the hardware but my testers have confirmed that it works! Let me know if it does for you too so that others have concrete proof about it.
Q: I ended up on CrashDump mode, how do I get back to my system?
A: Theres a valuable thread HERE which can help restoring your system, you WILL LOSE ALL DATA and I will not be blamed under any circumstances.
Q: Is the ROM official?
A: The ROM is Official.
Q: I use Telegram, where can I find help on that platform?
A: There is a common AOSiP Group Chat for all devices, the link is HERE
Q: Does SafteyNet pass and is the SELinux Enforcing?
A: Yes, SafteyNet does pass out-of-the-box and SELinux is Enforcing.
Q: What OOS Base firmware do I use?
A: OOS 10.0.6 is the recommended base firmware right now.
Q: I'm having high idle drain, please fix.
A: I'll need more data from you to figure it out, Install BetterBatteryStats and let me know about what it tells you after 3-4 charge cycles. Please do not report issues when having apps like Greenify, Naptime, Wakelock blocker etc.
Q: My phone is stuck on the "Bootloader is unlocked" warning page, why isn't my system booting?
A: Since there are a bunch of scripts being executed when the device is sent a power on signal, it might take some time to boot. Don't panic, your system will boot fine after some time. All builds are personally tested by me and a few testers.

Reserved

Littyyyyy???

Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.

Thank you for the perfect Rom.

This has all the customizable features like android 9

so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again

anirudhgupta109 said:
Reserved
Click to expand...
Click to collapse
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.

This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!

I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.

So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.

aer0zer0 said:
Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.
Click to expand...
Click to collapse
Thanks a lot for testing that annoying carrier ???
umair shaikh said:
so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again
Click to expand...
Click to collapse
Yes, clean flashing includes internal storage.
The only time you need to clean flash is when coming from another ROM.
When updating AOSiP you don't need to so it's basically a one time process.
david72262 said:
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.
Click to expand...
Click to collapse
yqx1110 said:
This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!
Click to expand...
Click to collapse
Thanks for the kind words the two of you, it took awhile to type it out for everyone, glad it's appreciated ??
elanandkumar said:
I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.
Click to expand...
Click to collapse
We are an open source project so including any form of closed source apps we can do away with irks me. The idea of having GApps inside the ROM itself feels wrong but it's a necessity.
Anyway, the latest Urnyx GCam works perfectly with AOSiP without any magisk modules nor setting permissive selinux. It's literally install and use so you can do so if you need to.
The OnePlus Camera also works, just that it needs to be launched from the long press menu on your launcher.
Mohammed779 said:
So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.
Click to expand...
Click to collapse
That's an interesting observation, I'll look into the red center.
No, there is nothing to refresh on AOD so it doesn't run on 90Hz.
You can also choose the type of 90Hz you want to run with in OnePlus Settings (forced or auto)

Hey the google bar seems to be permanently affixed to the home screen, I cant drag it away like a normal widget, is there anything I can do about that short of installing a launcher?

10.0.7
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks

mikefnz said:
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks
Click to expand...
Click to collapse
I'm running this ROM on 10.0.7. everything is fine.

help !!!
anirudhgupta109 said:
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Since the ROM is big in size due to gapps, try downloading from SourceForge to make sure you get the complete file and also compare md5sum.
- GApps is already pre-included in the ROM.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on

XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: https://www.github.com/AOSiP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.6
Based On: AOSP
Version Information
Status: Alpha
Created 2019-12-14
Last Updated 2019-12-14
Click to expand...
Click to collapse
writing 'system' ...
FAILED (partition not found)

hru200 said:
writing 'system' ...
FAILED (partition not found)
Click to expand...
Click to collapse
Follow the instructions maybe?
Type "fastboot reboot fastboot" then do the images flashing commands.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
Anyone having weaker WiFi signal compared to OOS? On a 5GHz WiFi that is. Same testing position, yet much weaker. Additionally, frequent disconnections.

[ROM][official] AICP 15.0 - q10.0 - castor/_windy (Sony Z2 Tablet)

{
"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, for Android Pie we based on the "Ground Zero Open Source Project" (GZOSP), and now for Android 10 we are fully based on AOSP.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Test builds: https://www.androidfilehost.com/?w=files&flid=305060
Use castor for the LTE variant and castor_windy for the wifi-only variant.
Feedback from castor users, especially concerning mobile data, appreciated since I can only test on castor_windy.
NOTE: Test builds are often those builds that I use personally. They tend to include open patches from our gerrit, and some additional changes documented here.
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
- Unlocking the device does not work directly after boot (just wait around half a minute after bootanimation finished)
- Generating QR Codes for wifi sharing is broken (AOSP bug for devices without biometric sensor)
- FM Radio is somewhat slow
- wifi connection issues for some users, possibly region-specific
- 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 discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
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, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android 10. 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 Zipfile.
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 (latest TWRP from the CarbonROM thread recommended when coming from Android < 10, on Android 10 TWRP >= 3.3.1 recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
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!
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 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.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
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.
OTA is only supported for official builds, which have not started yet.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_sony_msm8974/tree/q10.0
Device tree source:
https://github.com/AICP/device_sony_castor_windy/tree/q10.0
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:
NeoArian
rcstar6696
AdrianDC
drakonizer
Myself5
All the other contributors to sony msm8974 platform
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 15.0 (q10.0) castor/_windy (Sony Z2 Tablet), ROM for the Sony Xperia Z2 Tablet
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: Testing
Created 2020-02-08
Last Updated 2020-10-18

castor / LTE device:
Thanks a lot for your newest build! :good:
I do not seem to have any issues except the old one that i've had on your aicp 14 about the charging, which i've hoped to get rid of on the newest version:
- even if "wake on plug" is deactivated, the display always turns on when connecting (but it does not turn on when disconnecting)
- when charged between about 89 - 92% the LED begins to blink irregulary, and after a short time the display always turns on, but the LED turns off, and it stops charging, and the display never switches off and i cannot switch it off by the on/off-button, it always tuns on again, as long as the device is connected by usb.
https://forum.xda-developers.com/search/thread/3884236?query=charging

Thank you so much!
So happy you didn't forget the old Castor for Q
I don't know if I'm allowed to say that or is it important or not and I think it isn't fixable but my problem about WiFi persists in Q.
As I said in P thread I think it's a problem with country code.
Original post is here: https://forum.xda-developers.com/showthread.php?p=79126115#post79126115
Thank you for your great work In Q rom it is so smooth by the way

I liked this aicp 15 rom and realized that the battery consumes a little bit fast, not to mention that it would be nice if this rom had a split screen mode in the configuration, just like the huawei tablet, it would be different from the other aicp earlier

Maristks said:
I liked this aicp 15 rom and realized that the battery consumes a little bit fast, not to mention that it would be nice if this rom had a split screen mode in the configuration, just like the huawei tablet, it would be different from the other aicp earlier
Click to expand...
Click to collapse
There is split screen mode, just press the app icon in recents and select split screen

testing AICP 15.0 Castor Windy
Hi,
Thanks for this. I've installed this on one of my Z2 tablets to compare. I mainly use it for news, weather and video sources like Netflix. Amazon Prime, Plex etc and Maps. So far it's great, everything is rock solid. I shall use this as a daily driver from now on.
Andy

Thanks for keeping this amazing tablet alive.
I have a problem with the rom in a castor windy. I can't connect to any wifi. It seems working fine, it shows all the networks. But when I type the password and press connect it says "error saving the network" and it does nothing.
Edit: Nevermind, I reflashed the rom and the wifi is working normal now. The rom so far so good, just missing the navigation bar gestures and style change.

Hello,
Just flashed yesterday night.
Working fine for the moment, very good work !

using it since a week on my castor ( LTE ) , so far no issues with mobile data or else
using the tablet daily with music apps ( spotify, youtube, amazon ) .. for games like BrownDust and for Streaming ( Crunchyroll / Vodafone and Netflix ) no issues so far
no problems with batterie usage or standby time .. its just perfect
thanks for this rom keep up your work

Has anyone tried if this ROM works well with NanoDroid or MicroG in general?
Thanks

I downloaded the ROM yesterday and made a clean installation of it. The constant reboot issue when the screen turns off is still there unfortunately, just like in the Android 9

I use the rom for a week and everything works fine, no reboots, no force closes.

On my Xperia z2 Tablet LIT it was good, but when it turns off and leaves charging off it doesn't turn on while the charger is connected, it stays with the infinite loop and only turns on by holding the volume button up and down + the off button to be able to turn on , I hope you keep updating this rom because I like the recent grid bar:fingers-crossed:

Ryū Kenden said:
Has anyone tried if this ROM works well with NanoDroid or MicroG in general?
Thanks
Click to expand...
Click to collapse
I'm using it with microg

Thank you very much
do you have a link to gaps

Rom installed yesterday + opengapps nano.
Blutooth, wifi, 4g working regular, good battery usage. One random reboot till now.
Thank you

twicko said:
Thank you very much
do you have a link to gaps
Click to expand...
Click to collapse
One second witch Google!!
https://opengapps.org/#downloadsection

New builds are up, now sepolicy is enforcing again

SpiritCroc said:
New builds are up, now sepolicy is enforcing again
Click to expand...
Click to collapse
Hi SpiritCroc, according to you, in term of ram and battery usage, this ROM how does compare to the 14.0 one? It's on the same level or there are still fixes and tweaks to be made?
Thank you for your work nonetheless.
Best regards.

Ryū Kenden said:
Hi SpiritCroc, according to you, in term of ram and battery usage, this ROM how does compare to the 14.0 one? It's on the same level or there are still fixes and tweaks to be made?
Thank you for your work nonetheless.
Best regards.
Click to expand...
Click to collapse
I usually don't look at these numbers, so if they aren't particularly bad, I don't notice. That said, for what I'm using it I don't have any complaints right now.
Apart from that, there are some small bugs like described in the first post, and looks like timekeep (remembering the time across reboots) broke in the latest build, which I'm debugging right now.

[10][OFFICIAL] CarbonROM | cr-8.0 [z3c]

My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
Using TWRP 3.3.1-z3c-20191212-sar from here
Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
About 700MB of RAM free just after boot, with stock launcher.
Battery drain fast, but my battery is very old, no complain.
Pros:
+ reliably fast
+ everything works including GPS, BT, calls/data, hotspot and all my apps
+ no problems with audio routing and mic sensitivity
+ camera is ok but I use OpenCamera anyway
Cons/bugs:
- still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
- ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
- broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
- ringtone sound become a bit quieter after half a second from start of incoming call
- overall loudspeakers volume is not loud enough
Features I'd like to have in this ROM:
1) choose clock position in statusbar (only at left in CR8.0)
2) brightness control by sliding in statusbar without opening it
3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
6) restrict/disable power menu while phone locked
7) disable notification panel while phone locked
8) set minimal time between notifications on per app basis
9) wake by volume rocker buttons
10) increasing ringing volume
11) debugging over network (settings in devs options, absent in CR)
Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.
Thank you @Myself5 for continue work with our lovely z3c.

Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?

Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.

Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?

Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1

Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.

yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.

Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.

New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.

Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip

Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.

Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..

Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.

okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?

the "cant connect to the camera" returned unexpectedly..

Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?

Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works

Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:

okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.

[ROM][10]Android Open Source Illusion Project[perseus][Official]

INSTALLATION PROCEDURE:
CLEAN (This is also solve Mi Logo Bootloops)
1) In TWRP, Format Data
2) Reboot TWRP
3) Wipe System, Data, Cache and Dalvik
4) Flash Xiaomi EU (Stable v11.0.2.0 or Weekly v20.5.7)
5) Format Data
6) Reboot TWRP
7) Wipe System, Data, Cache and Dalvik
6) Flash AOSiP
7) (Optional) Flash Gapps & Magisk
7b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
8) Reboot into the system, and enjoy the illusion!
DIRTY (At your own risk)
1) In TWRP, flash AOSiP
2) (Optional) Flash Gapps & Magisk
2b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
3) Wipe Dalvik & Cache only
4) Reboot into the system, and enjoy the illusion!
KNOWN ISSUES:
NONE! All sensors, slider function, and AI button are all working!
If you find an issue, please let me know. Either via Telegram or here.

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your firmware versions in reports.
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

FREQUENTLY ASKED QUESTIONS:
COMMUNITY?
We have a community of over 600 helpful Mix 3 users around the world.
Join us on Telegram if you need help or want to chat: https://t.me/MiMix3Global
FIRMWARE?
AOSiP will not flash unless you are on any Android 10 based firmware.
xiaomi.eu ROM includes firmware, so this is not needed if you flashed that during a clean install (unless you want to try a different firmware version).
If you like to be on the latest firmware or try different versions, you can grab it here.
Personally, I like the latest available global variant (stable or beta).
You can flash firmware at any time, without affecting your current installation.
WHICH GCAM WORKS BEST?
Urnyx05 v1.7
WHICH TWRP SHOULD I USE?
Mauronofrio v3.3.1-17
CLEAN OR DIRTY?
If you're coming from unofficials, you'll need to clean flash since these builds are SIGNED.
Once you're in, you can just take OTAs, no more need to clean flash.

Great ROM! Congratulations on obtaining the "Official" status.

Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance

romano64 said:
Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance
Click to expand...
Click to collapse
]
Thanks for reporting, I will look into this issue.

Constrabus said:
]
Thanks for reporting, I will look into this issue.
Click to expand...
Click to collapse
Thank you

Hey guys, happy to announce AOSiP 10 Stable officials!
Please see the announcement on the Twitter post for changes and info about this release.

Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Just tested this on 1 MiMix 3 with AOISP [Unofficial] and on another MiMix 3 with ArrowOS 10.0 and it works on both devices like a charm.
Finally: ctsProfile true
Thank you for the hint including the little gem :good:

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.

ctsProfile false
Constrabus said:
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.
Click to expand...
Click to collapse
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?

chromanju said:
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?
Click to expand...
Click to collapse
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".

Great ROM, thanks so much. Everything seems solid, there is just one thing that spoils it for me - is it possible to add a toggle for the charging light? Keeps me awake at night.

Tamsy said:
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".
Click to expand...
Click to collapse
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!

chromanju said:
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!
Click to expand...
Click to collapse
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.

Tamsy said:
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.
Click to expand...
Click to collapse
That did the trick: Magisk Hide wasn't enabled.
Thanks a lot!!

Found a bug... Gboard needs camera permission to create minis (personalised stickers like mimoji) but doesn't request it and can't be given it.

Is it possible to remove the google search bar from the home screen with this rom?

Database Info

welcome