[ROM][UNOFFICIAL][7.1.2] OmniROM - Shield Tablet Android Development

[ROM][UNOFFICIAL][7.1.2] OmniROM - Shield Tablet Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OmniROM is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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. Hard. A lot.
*/
OmniROM 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. Linked below is a package that has come from another Android project that restore the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
Homepage:
=================
http://omnirom.org/
Wiki:
=================
http://docs.omnirom.org/Main_Page
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
Use this thread to report bugs as this is UNOFFICIAL
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
Root access is not included by default. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.
Screenshots:
=================
http://abload.de/img/screenshot_20170814-2qlsi5.png
http://abload.de/img/screenshot_20170814-2mssai.png
Installation Instructions:
=================
First time installing OmniROM to your Shield Tablet or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working Team Win Recovery Project (TWRP) - https://twrp.me/devices/nvidiahshieldtablet.html
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM zip to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Downloads:
=================
UNOFFICIAL builds
omni-7.1.2-20171110-shieldtablet-HOMEMADE.zip md5:196df454441117da0962015063573a95
omni-7.1.2-20170901-shieldtablet-HOMEMADE.zip md5:02b22807016a3e39d0b0e46986fb24d9
omni-7.1.2-20170818-shieldtablet-HOMEMADE.zip md5:1ebc771fa3626a2a2bd7e68d72df9f7b
omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip md5:4710c3ec9347e1c9ca7dc4013fde0bbf
MIRROR: omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip
Gapps: Open Gapps
http://opengapps.org/
SuperSU:
http://www.supersu.com/download
Device Source Code:
=================
Device trees:
https://github.com/Lolzen/android_device_nvidia_shieldtablet
https://github.com/Lolzen/android_device_nvidia_shield-common
Kernel:
https://github.com/Lolzen/android_kernel_nvidia_shield
Nvidia hardware:
https://github.com/Lolzen/android_hardware_nvidia_power
https://github.com/Lolzen/android_hardware_nvidia_thermal
https://github.com/Lolzen/android_hardware_nvidia_libstagefrighthw
Vendor blobs:
https://github.com/Lolzen/proprietary_vendor_nvidia
Credits:
=================
Steel01 for providing device trees and blob sources and doing an excellent job maintaining them
BitOBSessiOn and OmniROM folks for pointing me in the right direction getting past the Black Screen
OmniROM Project for code base and being #swag in General

Thanks ! The only problem is that the video is not working

marcostesvk said:
Thanks ! The only problem is that the video is not working
Click to expand...
Click to collapse
Thanks for reporting! Could you specify which app? I do have mixed results on this, on one hand YT / MX Player are working on the other one Clover can't play webM's.
I'll certainly look into it.

The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?

marcostesvk said:
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
Click to expand...
Click to collapse
I'd advice against that, personally.
However, i have a workaround for the videos. There's some problem with the hardware decoding, i still have to figure out why.
For now i simply disabled hardware decoders, the software decoding seems to work fine, but this isn't a fix by any means.
I'll add the link to the download once the upload finished.
added to OP
Another bug i've encountered is that the Shield Camera's pictures are distorted, however when you activate HDR everything is fine. Again, just a workaround for now. The alternative is to use AOSP Camera.

Charging issue fix available?
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.

fmcgregor said:
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
Click to expand...
Click to collapse
Seems weird.
Does anybody else have this issue?

klo_lol said:
Seems weird.
Does anybody else have this issue?
Click to expand...
Click to collapse
Thanks for trying. And thanks to anyone for replying. In terms of self help, I downloaded some battery apps to see if they can re-align the battery so it can charge up to 100%. Still only charging up to 89%. Tried cleaning the input ports and the chargers. I have wiped cache partitions. I have the latest TWRP. I'm scared to try to re-flash because it was so difficult - "setup wizard keeps stopping."

you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!

fmcgregor said:
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
Click to expand...
Click to collapse
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?

klo_lol said:
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
Click to expand...
Click to collapse
Yes TWRP 3.1.1-1. Thx very much for the OTA link. Just fyi, the battery zip link was dead. But I'll find a working link now that I know the general name..

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
Hi, just an update. I re-flashed and used bean gapps this time. No problems this time, but the battery still won't charge above 89%. Just as a by the way, the clock and date start up at factory until I get it on the wifi and it syncs. Every time. If there's no wifi, it's set to Dec. 31, 2012. Anyone else with this?

uploaded a new build. Link in OP.
No major changes, just up2date with omni source as of today

new build in OP.
*updated with latest omni 7.1 changes
*updated with some device changes from Aaron Kling
*updated kernel with latest nvidia kernel sources
i'm still bumping my head against a wall why hwencoders seem to have some sort of problems. You can play media, it's just not working with the configs it's supposed to.

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

M7+M7vzw+M7spr AICP-13.1-O 8.1 UNOFFICIAL BUILDS

{
"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 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 (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link m7: https://www.androidfilehost.com/?w=files&flid=239910
Download link m7vzw: https://www.androidfilehost.com/?w=files&flid=238220
Download link m7spr: https://www.androidfilehost.com/?w=files&flid=239908
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
(link the best one for your device, there are several variants out there right now, pico/nano gapps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), 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", 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 then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the deivce, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/icxj1/android_kernel_htc_msm8960/tree/o8.1
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@icxj1
@alial04
@tathanhlam66
ROM OS Version: 8.1.x Oreo
Kernel: Linux 3.4.113
Version Information: Development
Status: UNOFFICIAL
Release Date: 02-28-2018
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
HTC ONE M7ul,wlv,wls, ROM for the HTC One (m7)
Contributors
icxj1, alial04
Source Code: https://github.com/AICP/platform_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: All of the above
Version Information
Status: Testing
Created 2018-02-28
Last Updated 2018-02-27

[/ATTACH][/ATTACH]

This ROM is testing & development. I know it must be hard for some to comprehend, the source is not complete yet. And the more they advance the less compatible m7 becomes.
Please report bugs with logs! No need to report what works on N ROM that does not work on O. M7 is not compatible for Oreo & i have many modifications to make it work. If you cannot live with a few bugs for awhile then GTFO! I do not get paid to maintain or develop so I don't want to here your pissing & moaning about an piece of **** obsolete device.
Bugs= "system process isn't responding" anr warning on boot. Select wait & carry on. This is caused by system partition not being mounted early enough in the boot process. 8.0+ expects an early mounted system partition. This is handled in the kernel by use of a separated dts, our kernel does not support dts for m7.
Lock screen with pin or password causing problems for some user's. not sure the entire issue, but reports of waiting up to 5 minutes to unlock. ??? send logs on this please.
Rooted devices must enable d2tw & pocket mode in kernel aduitor to fix proximity wake not working on outgoing phone call, (when screen is black dt2w it). Not an issue on non-rooted devices.
It is pointless to post here, most don't read it & will report the same bugs over & over in thread.

Should have ffcamera in this one & mobile settings partialy fixed, no data usage info & quick settings tile will crash. please do not report these bugs, i already have logs for them. enjoy!
m7 += https://www.androidfilehost.com/?fid=673956719939822539
m7vzw += https://www.androidfilehost.com/?fid=890129502657586018
m7spr += https://www.androidfilehost.com/?fid=746010030569956907

Can you guys make a kernel with wake gestures included?

lucyr03 said:
Can you guys make a kernel with wake gestures included?
Click to expand...
Click to collapse
They are already working on it but it makes some problems with oreo. If it is working they will release it.

Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil

samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Gapps are beta, search their unofficial thread & see if you can find anything. And m7 will probably have to start using the magisk universal cts module. Search magisk modules for zip.
https://forum.xda-developers.com/an...cial-opengapps-builds-android-t3743495/page28

samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235

first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.

olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card when os booted.
Click to expand...
Click to collapse
This device, the m7 allways had wifi problems even with stock rom it drops sometimes and doesnt connect when a known network is around sometimes. That must be related to the hardware because it was in all android versions from 4.1.2 up to 8.1 in stock and all custom roms the same no matter which firmware is used stock sense or gpe.

olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.
Click to expand...
Click to collapse
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
Aha, good idea. It seems this sim card issue is only happening on m7 if build m7vzw first. Next builds I will make clean & run m7 first then will see if problem still exist.

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.
Click to expand...
Click to collapse
Is that video related?

icxj1 said:
Is that video related?
Click to expand...
Click to collapse
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.

lucyr03 said:
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.
Click to expand...
Click to collapse
Aha, oK. I will look into it. Thanks

lucyr03 said:
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235
Click to expand...
Click to collapse
Thanks, THAT'S IT. Great.
---------- Post added at 08:13 PM ---------- Previous post was at 08:00 PM ----------
I see, it's working very well.
- Video recording in Camera app is not working (as told before by some other member).
- GPS is marked as "Supported" but Enabled "No", and not possible to enable (but working GPS is important to me, so we have to wait for the devs and their great work).
- IR is marked as "Not supported" - even it is in the device -, sigh (it's not really very important to me, but it's "nice to have").
- Mobile data work correctly, but it's impossible yet to switch it off.
- WiFi works to me, even reconnects.
Thanks again,
samhhmobil

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
tried this, but not working, still had to reinsert it, at least on my device (international version)

olivrd said:
tried this, but not working, still had to reinsert it, at least on my device (international version)
Click to expand...
Click to collapse
I have international version too but with GPE firmware.
Sent from my OnePlus 2 using XDA Labs

lucyr03 said:
I have international version too but with GPE firmware.
Click to expand...
Click to collapse
same here

[ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus]

Copy Partition- Initial Setup
Flash the attachement via TWRP

Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok

Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?

Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.

I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense

david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far

Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.

Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.

If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA

The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.

Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?

Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo

Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?

smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.

Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk

Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?

Anyone running xposed? Any issues?

Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

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

Database Info

welcome