*edit2*
You need to "compile & active" your favorite theme 5-10 times. It's like gambling ??
https://plus.google.com/+MertSativa/posts/1C3c954TGHL
____________________________________________________________
*edit*
Confirmed: March update breaks Substratum on rooted stock Rom's and custom ROM's with OMS
____________________________________________________________
Hi guys,
I updated yesterday my Pixel (March Security Update & Pixel 2016) and after setting up I want to use the Swift Dark Theme (Center Clock for O don't work too). So Substratum compile everything without problem and after a reboot still everything white. Someone else have problems with Substratum?
Confirmed. It did break Substratum on a stock non-rooted phone. Not sure if the rooted ones still work. Hopefully the Substratum team will fix it soon.
harihacker said:
Confirmed. It did break Substratum on a stock non-rooted phone. Not sure if the rooted ones still work. Hopefully the Substratum team will fix it soon.
Click to expand...
Click to collapse
If I know this before I wouldn't update haha
Me too!!
Sh0X31 said:
If I know this before I wouldn't update haha
Click to expand...
Click to collapse
Me too!!
No problems here on rooted (Magisk v16) stock. I did have to apply the themes about 6-8 at a time, or I had issues like those described in the OP.
funkybrunk said:
No problems here on rooted (Magisk v16) stock. I did have to apply the themes about 6-8 at a time, or I had issues like those described in the OP.
Click to expand...
Click to collapse
Thanks man
Build and enable overlays..reboot..go back in to subs and select enable and Bam!! Took me a while of playing with it the last two days but this "seems" to work
Apply the theme.
Reboot.
Go back to Substratum (bind with andromeda if not rooted).
Apply the same theme again.
Mostly works!!
Reboot.
Enable again in Substratum.
All works!!
Note: Am on stock unrooted.
Sh0X31 said:
*edit2*
You need to "compile & active" your favorite theme 5-10 times. It's like gambling ??
https://plus.google.com/+MertSativa/posts/1C3c954TGHL
Click to expand...
Click to collapse
It actually is just a bug with Package installer in the March update.
Many people approached us and thinks this is a big problem.
Instead of constantly Building and Applying...
1. Install all overlays you plan to use (Build and Update)
2. Reboot
3. All overlays installed before the reboot can be enabled/disabled. If you build and compile again, a reboot will update it.
NOTE: Building overlays and installing them IS NOT the fix. Please do not spread that fix.
Sent from my iPhone X using Tapatalk
What was wrong with cm theme engine that we gave up on it
attention exertion said:
What was wrong with cm theme engine that we gave up on it
Click to expand...
Click to collapse
Nobody gave up on it, it died when cm died and Lineage haven't resurrected it...
@nicholaschum - apart from reverting the two commits (in six files) and building from source so that rebooting isn't necessary again, has a simpler alternative been found?
There were mentions of a couple of fixes in the designers chat but there were no references.
Spannaa said:
Nobody gave up on it, it died when cm died and Lineage haven't resurrected it...
@nicholaschum - apart from reverting the two commits (in six files) and building from source so that rebooting isn't necessary again, has a simpler alternative been found?
There were mentions of a couple of fixes in the designers chat but there were no references.
Click to expand...
Click to collapse
Just need to revert one file and one line only. You don't have to revert the security patch.
Seems like a lot of developers believe tampering with what a security patch committed is such a big deal. If they actually read the code, a one liner is easily doable.
nicholaschum said:
Just need to revert one file and one line only. You don't have to revert the security patch.
Seems like a lot of developers believe tampering with what a security patch committed is such a big deal. If they actually read the code, a one liner is easily doable.
Click to expand...
Click to collapse
The file and line to revert would be useful - as a themer building from source is new to me!
Spannaa said:
The file and line to revert would be useful - as a themer building from source is new to me!
Click to expand...
Click to collapse
Try this: https://github.com/VelvetProject/frameworks_base/commit/636d0fc93f497bab26f9198a69fb813c7c1931ca
nicholaschum said:
Try this: https://github.com/VelvetProject/frameworks_base/commit/636d0fc93f497bab26f9198a69fb813c7c1931ca
Click to expand...
Click to collapse
Thanks @nicholaschum, that's sorted it - no reboot necessary now :good:
I am facing so many issues.
Microphone not working, phone getting restarted frequently and hangs.
This is happening only after March update and the pixel team does not have a fix yet. Can't call this a flagship service. Customer service is very much cool and calm after thousands of pixels are almost dead for a few days till now.
No response from Google yet.
Using substratum through andromeda on stock beta oxygen os with april security patch. i am using only (swift black)
follow steps below to use theme again
* Follow these steps with your own risk , I am not responsible if any damage caused
1 You have to uninstall all overlays from substratum
2 update all apps , theme ,substratum from play store.
3 open substratum through andromeda desktop client. (only for non rooted)
4 Select theme and click on overlays which you want to install
5 Click on build & install (let the processing to be done)
6 After that all overlays appearing in pink color
7 Restart your device (if nothing happens follow further steps)
8 open substrarum again (use desktop client if non rooted)
9 Click on manager icon
10 enable select to toggle all overlays and click on change overlays states (placed in blue floating overlay button)
11 Reboot device again
BOOM all overlays are installed and apps themed perfectly.
Related
Hello fellow OP3 owners;
I recently rooted my OP3 and am a noob when it comes to Layers. I've only ever used CM theme engine. I'd like to stay on Oxygen until the binaries for dash charging are released.
My question is, does Oxygen support Layers? Now that I am rooted is there anything special I might need to do to get it working?
Anybody with expertise to discuss is appreciated. Hope everyone is enjoying their new device as I am
Cheers!
Just installed layers manager and layers showcase from the play store and it worked. Sweet. It also doesn't trigger the safetynet check so if you are using systemless root, Android pay should still work. The downside though is that many layers on the play store don't list compatibility with the OP3 so many of them are harder to get from the showcase app.
Edit: Should mention I'm on OOS 3.1.2 with systemless SuperSU.
Sent from my ONEPLUS A3000 using Tapatalk
Every theme *should* work but I've noticed most ones that theme the "Framework" have issues such as not booting or rebooting when you get power menu style popups.
thebcooper said:
Every theme *should* work but I've noticed most ones that theme the "Framework" have issues such as not booting or rebooting when you get power menu style popups.
Click to expand...
Click to collapse
Have the same exact prob.
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
Wow, was just looking for a fix today and bam!!
Freak07 said:
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
Click to expand...
Click to collapse
Delete
Do you plan to share your DU build? Would be highly appreciated as there aren't much roms for walleye.
Sent from my SM-G965F using Tapatalk
I get an error when trying to install this via Magisk Manager, do i need to flash this via TWRP ?
Flashing
- Copying zip to temp directory
- Installing Multi_Touch_Fix_8.1_P.zip
****************************************
Please install Magisk v15.0+ !
****************************************
Failed !
! Installation failed
Magisk v16.0 is properly installed and i'm rooted.
Edit: nvm, seems to be an issue with Magisk in general since i can't install any modules.
usernametaken53 said:
I get an error when trying to install this via Magisk Manager, do i need to flash this via TWRP ?
Flashing
- Copying zip to temp directory
- Installing Multi_Touch_Fix_8.1_P.zip
****************************************
Please install Magisk v15.0+ !
****************************************
Failed !
! Installation failed
Magisk v16.0 is properly installed and i'm rooted.
Edit: nvm, seems to be an issue with Magisk in general since i can't install any modules.
Click to expand...
Click to collapse
Update Magisk to version 16.3 and then try again yo install any modules
ApoelEllhnwn said:
Update Magisk to version 16.3 and then try again yo install any modules
Click to expand...
Click to collapse
Worked, thanks !
Seems to be working well! Legit, thanks! ? Stock April rom
@Freak07 thanks a lot! Works like a charm on mi5s plus running rr6
hi how to remove this module? Android P caused bootlop.
Edit: solved using module uninstaller
gillboyzz said:
Do you plan to share your DU build? Would be highly appreciated as there aren't much roms for walleye.
Click to expand...
Click to collapse
I would also be interested in this, it's a shame that such a feature packed flagship phone is lagging so far behind in terms of ROM development and support, it would be nice to see a new rom thread on this forum!
Beans
bbeanss said:
I would also be interested in this, it's a shame that such a feature packed flagship phone is lagging so far behind in terms of ROM development and support, it would be nice to see a new rom thread on this forum!
Beans
Click to expand...
Click to collapse
My build is for pixel 2 xl... Sorry.
But there are builds for the walleye out there just not on xda.
Freak07 said:
My build is for pixel 2 xl... Sorry.
But there are builds for the walleye out there just not on xda.
Click to expand...
Click to collapse
Do you know what roms are available and where? I just had a dig around LOS website, DU's G+ and Carbon's Website but can't find anything mentioning the pixel 2
Thanks
Beans
bbeanss said:
Do you know what roms are available and where? I just had a dig around LOS website, DU's G+ and Carbon's Website but can't find anything mentioning the pixel 2
Thanks
Beans
Click to expand...
Click to collapse
Try this
http://dwnld.aicp-rom.com/?device=walleye
jascolli said:
Try this
http://dwnld.aicp-rom.com/?device=walleye
Click to expand...
Click to collapse
You sir, are a gentleman. Thank you very much!
Beans
bbeanss said:
Do you know what roms are available and where? I just had a dig around LOS website, DU's G+ and Carbon's Website but can't find anything mentioning the pixel 2
Thanks
Beans
Click to expand...
Click to collapse
Edit:
https://plus.google.com/+JacobStermer/posts/9n128vF5RfL
bbeanss said:
Do you know what roms are available and where? I just had a dig around LOS website, DU's G+ and Carbon's Website but can't find anything mentioning the pixel 2
Thanks
Beans
Click to expand...
Click to collapse
https://plus.google.com/+FrankieTR3Ds/posts/9kYN5d5L4Ho
This is the ROM I'm using currently. You should consider AICP and AquariOS as well, as they are being updated officially
TCUofficial said:
https://plus.google.com/+FrankieTR3Ds/posts/9kYN5d5L4Ho
This is the ROM I'm using currently. You should consider AICP and AquariOS as well, as they are being updated officially
Click to expand...
Click to collapse
does the DU you linked needs gapps or are they built in?
munchy_cool said:
does the DU you linked needs gapps or are they built in?
Click to expand...
Click to collapse
By the looks of the size of the zip they should be included.
bbeanss said:
You sir, are a gentleman. Thank you very much!
Beans
Click to expand...
Click to collapse
Aicp is awesome used it on my N5x for a looooong time
They will incorporate your feedback also
I've recently noticed this trying to apply substratum themes since i updated to Android Pie. None of the overlays compiles or applies. No overlays in manager either. Most times compiling does not even give any errors. I've tried most themes that claim Android 9.0 support.
Any ideas on how to troubleshoot this issue?
Ad.Shk2 said:
I've recently noticed this trying to apply substratum themes since i updated to Android Pie. None of the overlays compiles or applies. No overlays in manager either. Most times compiling does not even give any errors. I've tried most themes that claim Android 9.0 support.
Any ideas on how to troubleshoot this issue?
Click to expand...
Click to collapse
What version of substratum are you using? And, what themes have you tried?
Badger50 said:
What version of substratum are you using? And, what themes have you tried?
Click to expand...
Click to collapse
Substratum 1001.
Tried pitch black, mono/art, flux, Swift dark.
When i complete the there it creates a .Substratum folder on my storage. But when i reboot, it's gone.
Ad.Shk2 said:
Substratum 1001.
Tried pitch black, mono/art, flux, Swift dark.
When i complete the there it creates a .Substratum folder on my storage. But when i reboot, it's gone.
Click to expand...
Click to collapse
Ah. Yeah version 1001 doesn't work on the P2XL. Uninstall the one you have, reboot, then use the one in the link. Also, when you build your overlays, select "build and update" then reboot, then enable them in substratum manager. Pitch Black works great. Be careful with the others especially when themeing system and system UI, they can shut your UI down. Pitch Black works on everything though :good:
https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
Badger50 said:
Ah. Yeah version 1001 doesn't work on the P2XL. Uninstall the one you have, reboot, then use the one in the link. Also, when you build your overlays, select "build and update" then reboot, then enable them in substratum manager. Pitch Black works great. Be careful with the others especially when themeing system and system UI, they can shut your UI down. Pitch Black works on everything though :good:
https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
Click to expand...
Click to collapse
This version keeps crashing constantly. Restart/rescue me don't help either.
Ad.Shk2 said:
This version keeps crashing constantly. Restart/rescue me don't help either.
Click to expand...
Click to collapse
Are you rooted? If not, then I'm afraid your outa luck
Badger50 said:
Are you rooted? If not, then I'm afraid your outa luck
Click to expand...
Click to collapse
Rooted of course ... But it's luck still apparently.
Same here as well.
Android 9 rooted
Flash kernel.
Substratum v1001
Multiple themes don't work. They appear to apply but the apps are not themed.
Working for me, Pie, Magisk v17.1, Flash Kernel, using Substratum v998. Are you doing Build and Enable, then rebooting, then toggling the overlay state? I'm using Ethereal for System (Pie support) and Swift Dark for some apps.
Officechris said:
Working for me, Pie, Magisk v17.1, Flash Kernel, using Substratum v998. Are you doing Build and Enable, then rebooting, then toggling the overlay state? I'm using Ethereal for System (Pie support) and Swift Dark for some apps.
Click to expand...
Click to collapse
I've tried v998 but it keeps crashing
Ad.Shk2 said:
I've tried v998 but it keeps crashing
Click to expand...
Click to collapse
Have you tried clearing app cache/data a couple times? As well as uninstall/reinstall?
Use 998 and dont patch the substratum app when you install the themes
xDakos said:
Use 998 and dont patch the substratum app when you install the themes
Click to expand...
Click to collapse
1001 working correctly here, on top of it being themed. 998 worked correctly here even when themed, so substratum itself likely isn't the issue. What theme are you using?
yeah im using 1001 fine aswell but 998 worked with a restart and 1001 doesnt even need a restart anymore. Try PitchBlack
Just updated from 998 to 1001, so far everything working as expected.. lets hope it stays that way!
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
SOLVED: New substratum update available on play store.
sidhg said:
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
Click to expand...
Click to collapse
No such issue on my P2XL. Have you tried clearing substratum app cache and data? And/or uninstall/install substratum again?
Badger50 said:
No such issue on my P2XL. Have you tried clearing substratum app cache and data? And/or uninstall/install substratum again?
Click to expand...
Click to collapse
Yes I've reinstalled both the app and the theme.
Still nothing shows in the Overlay Manager.
sidhg said:
Yes I've reinstalled both the app and the theme.
Still nothing shows in the Overlay Manager.
Click to expand...
Click to collapse
Does substratum have root privileges?
sidhg said:
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
Click to expand...
Click to collapse
Substratum is not compatible with the new Magisk 18. As far as I know, a new version is worked on right now. You either have to wait or use Magisk 17.3.
Badger50 said:
Does substratum have root privileges?
Click to expand...
Click to collapse
Yes it has the access to the root.
May be the new magisk update is the problem.
kost7 said:
Substratum is not compatible with the new Magisk 18. As far as I know, a new version is worked on right now. You either have to wait or use Magisk 17.3.
Click to expand...
Click to collapse
I'll wait for the substratum update. Thanks.
sidhg said:
I'll wait for the substratum update. Thanks.
Click to expand...
Click to collapse
I just can't stand the white pages everywhere; it drives me both blind and crazy, so I'll stick to 17.3 for the time being.
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
CamoGeko said:
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
Click to expand...
Click to collapse
This explains the difficulties I was having getting some overlays to work. Thank you
Try flashing Magisk 18 in the Magisk manager app itself instead of in twrp, I was having problems gaining root until I did that. I'm currently on ver 18 with Substratum working.
There is a new update available for substratum on the Google play. I hope this resolves the issue.
Edit: It's working fine now.
JoeNeckbone said:
Try flashing Magisk 18 in the Magisk manager app itself instead of in twrp, I was having problems gaining root until I did that. I'm currently on ver 18 with Substratum working.
Click to expand...
Click to collapse
Thats how I installed mine and Substratum still broke.
Anyways that's a moot point now, new Substratum release on Play Store fixes the problem.
Sent from my Essential Products PH-1 using XDA Labs
CamoGeko said:
Thats how I installed mine and Substratum still broke.
Anyways that's a moot point now, new Substratum release on Play Store fixes the problem.
Click to expand...
Click to collapse
Even with Substratum taken out of the equation, I was having problems getting root with Magisk 18 until I flashed within Magisk app and chose recommended install option.
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
davidisflash said:
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
Click to expand...
Click to collapse
Latest substratum works only with Magisk 18 afaik.
davidisflash said:
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
Click to expand...
Click to collapse
kost7 said:
Latest substratum works only with Magisk 18 afaik.
Click to expand...
Click to collapse
Kost7 is correct. You must be on magisk 18.0 if you want to use substratum :good:
Badger50 said:
Kost7 is correct. You must be on magisk 18.0 if you want to use substratum :good:
Click to expand...
Click to collapse
You guys are awesome ?
I've bootlooped before when installing the 17.3 zip in twrp. What's the safest way to upgrade to 18
davidisflash said:
You guys are awesome ?
I've bootlooped before when installing the 17.3 zip in twrp. What's the safest way to upgrade to 18
Click to expand...
Click to collapse
Just let magisk upgrade itself from within the magisk manager app. Worked without issue for me :good:
Did it with twrp and worked. Thanks again!!!
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
componentchunk said:
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
Click to expand...
Click to collapse
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
fastboot flash boot boot.img (stock October). That booted it for me until he can update a fix. This ROM btw is phenomenal on battery life
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
kdrag0n said:
ProtonAOSP • Pixel 2 XL
Click to expand...
Click to collapse
Hello. Proton is incredible. Very fast, smooth and tenacious. Tested it from the first version. Thank you very much. I want to clarify something else for myself: Do I need to flash in both slots if a stock is installed?
palimatix said:
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Click to expand...
Click to collapse
No, you only need to wipe data if switching from another ROM.
73sydney said:
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
Click to expand...
Click to collapse
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
73sydney said:
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Click to expand...
Click to collapse
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
componentchunk said:
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
Click to expand...
Click to collapse
Sorry for the inconvenience, the problem lies in a botched SafetyNet fix that was missed in testing due to not flashing all partitions. You can make it boot temporarily by flashing the stock boot image. A hotfix that boots out-of-the-box will be up shortly.
pablo9023 said:
Hello. Proton is incredible. Very fast, smooth and tenacious. Thank you very much. I want to clarify something else for myself: I tested it from the first version. Do I need to flash in both slots if a stock is installed?
Click to expand...
Click to collapse
No, ideally the latest stock ROM would be installed in both slots beforehand but that's only because this build is missing firmware. A hotfix will be up shortly with the latest firmware included.
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
componentchunk said:
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
Click to expand...
Click to collapse
Xposed will never be supported, you are on your own if it's broken. I wouldn't recommend using it because it can cause all sorts of weird bugs.
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
kdrag0n said:
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
Click to expand...
Click to collapse
Great work, and thank you for the fast updates. Really looking forward to using the ROM when I clean format next time. Waiting for Google to release the last Security patch in December before making the jump, don't want to clean install every month. I usually stick with a ROM for a few months at a time.
Just to clarify if anyone is confused: this is an Android 11 ROM, not Android 10. XDA DevDB has no option for 11 so I had to put 10. I've just edited the DevDB info out of the post now and added 11 to the header so there should be no more confusion.
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
GROOVYJOSHCLARK said:
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
Click to expand...
Click to collapse
thank you very much for your assessment! I also find this rom to be very stable, snappy and the slight changes to the stock rom are very well thought out - next to perfect! big thanks to the dev krag0n!
I'm coming from an Android 9 Custom ROM and I wanted to switch to this, the instructions states that it should just be a simple flash. Should I still start from a clean reinstall of stock Android 11 or does flashing this come with that already?
kdrag0n said:
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
Click to expand...
Click to collapse
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
kdrag0n said:
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
Click to expand...
Click to collapse
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
73sydney said:
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
Click to expand...
Click to collapse
My Pixel 2 XL has been getting hardware attestation in all of my tests recently if the model name is set to "Pixel 2 XL". It's possible that I'm being A/B tested and most users don't have this problem, but either way, I haven't been able to pass SafetyNet without changing the model name because of it.
Either way, I've added hacks into the system in my ROM to avoid spoofing the model name while still defying hardware attestation and passing SafetyNet despite being on a mismatching security patch level. I agree, I don't want to change the model name just to pass SafetyNet, so I've been coming up with other solutions to avoid doing that.