• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

ROM ❯ PIXEL 4 XL ❯ OFFICIAL ❯ ProtonAOSP 11

Search This thread

kdrag0n

Senior Member
Feb 19, 2016
696
1,899
kdrag0n.dev
ProtonAOSP 11.5.2 has been released. Sorry for the delay this month; I've been busy with other projects, but here's the full release.

Changes:
• July security patch
• Added search to website
Added red, green, and blue color balance settings
Added alarm, ringtone, and notification sounds from Plasma Mobile
• Added HarmonyOS Sans font style
Extended font styles to affect third-party apps (reboot to apply changes)
Improved Night Light quality using chromatic adaptation (reduced color distortion)
• Improved Ambient EQ quality (with modern color science: CAT16)
• More gradual transition when turning Night Light on/off
• Pixel 5, 4a 5G, 4/XL: Added setting for increased touch sensitivity
• Pixel 5, 4a 5G, 4/XL: Added "Saturated" color profile
• Pixel 5, 4a 5G: Fixed Night Sight crashes in Google Camera
• Pixel 4/XL, 2/XL: Fixed Active Edge instability with multiple profiles
• Pixel 4/XL: Added support for HDR10+ (Diab)
• Pixel 4/XL: Added support for modem diagnostics

Website
Install from browser (recommended)
Download

As the ProtonAOSP project expands to support more devices, bandwidth and maintenance costs are increasing. You can help support the project and keep it alive with a recurring donation, or alternatively buy me a coffee. Everything helps, but a recurring donation is the best way to keep the project alive in the long term.
 

Curiousn00b

Senior Member
Dec 3, 2011
3,161
1,000
Delaware
Google Pixel 4 XL
I just installed the Google phone app from the playstore. Note I haven't fully tested it yet. Also a magisk module for dailer framework.
Are you 100% sure it's working? Are you able to change the Google Voice of call screen? That's the sign that it's working correctly.

I managed to get it working by systemizing the Google Dialer and I think I tried that module before and didn't have any luck, but I don't have RCS working no matter what I do. I'll try again later today after a clean flash though.
 

dragynbane222

Senior Member
Jul 2, 2012
185
65
Google Pixel 4 XL
Google Pixel 5
Are you 100% sure it's working? Are you able to change the Google Voice of call screen? That's the sign that it's working correctly.

I managed to get it working by systemizing the Google Dialer and I think I tried that module before and didn't have any luck, but I don't have RCS working no matter what I do. I'll try again later today after a clean flash though.
Yeah, you need to systemize the dialer as a priv-app. Dialer Framework is unneeded. As to the RCS issue, the "trying to verify" bug has hit anyone trying to set it up again. That's going to hit any rom you try as it's server side from what I can gather. Old workarounds don't seem to work anymore. Next method I have is leave it on trying to connect and it'll connect when the bug is fixed.
 

Curiousn00b

Senior Member
Dec 3, 2011
3,161
1,000
Delaware
Google Pixel 4 XL
Yeah, you need to systemize the dialer as a priv-app. Dialer Framework is unneeded. As to the RCS issue, the "trying to verify" bug has hit anyone trying to set it up again. That's going to hit any rom you try as it's server side from what I can gather. Old workarounds don't seem to work anymore. Next method I have is leave it on trying to connect and it'll connect when the bug is fixed.
Odd enough, I managed to get it working by doing nothing during a clean clash.

I had to clean flash due to messing up something with GBoard and could no longer install it through the Play Store for some weird reason. I also had a different Google Dialer settings UI than I was used to before I clean flashed, now I'm back to the UI I'm used to, but call screen is working too, so I'm all setup now.
 

i42o

Senior Member
Dec 5, 2013
715
261
Riverside
@kdrag0n i pledged for early access, did the web installer and all went well for version 11.5.0 for version 11.6.0 i had to pay $6.50 to get the link sent to me, it is not installing via web installer, and theres nothing i can do about it. seems like youre making us pay to get your rom and once we do, you make us pay again in order to get a newer version that in it of itself doesnt web install. not cool dude.
 

Curiousn00b

Senior Member
Dec 3, 2011
3,161
1,000
Delaware
Google Pixel 4 XL
@kdrag0n i pledged for early access, did the web installer and all went well for version 11.5.0 for version 11.6.0 i had to pay $6.50 to get the link sent to me, it is not installing via web installer, and theres nothing i can do about it. seems like youre making us pay to get your rom and once we do, you make us pay again in order to get a newer version that in it of itself doesnt web install. not cool dude.
It installs fine here, and you don't have to pay for it, you're paying for early access. Otherwise, you just wait for the public release.

What errors are you having?
 

kdrag0n

Senior Member
Feb 19, 2016
696
1,899
kdrag0n.dev
@kdrag0n i pledged for early access, did the web installer and all went well for version 11.5.0 for version 11.6.0 i had to pay $6.50 to get the link sent to me, it is not installing via web installer, and theres nothing i can do about it. seems like youre making us pay to get your rom and once we do, you make us pay again in order to get a newer version that in it of itself doesnt web install. not cool dude.
Sorry to hear that. I just reached out to help you via email and processed it for refund in case you are no longer interested in getting it to work. Please note that early access is completely optional and not mentioned anywhere on XDA, so please avoid posting about it in this thread. Thanks!
 
  • Like
Reactions: arsenalove

Phillis

Senior Member
Jun 9, 2009
98
8
Montreal
Sometimes upon reboot, booting into the OS takes 5-10 minutes to load and the touchscreen does not work. I have to manually reboot 3-4 times by pressing the power button 15 seconds until eventually it works.

Is this a sign of hardware failure or a bug? The phone was purchased new as a refurbished unit.
 

GROOVYJOSHCLARK

Senior Member
Sometimes upon reboot, booting into the OS takes 5-10 minutes to load and the touchscreen does not work. I have to manually reboot 3-4 times by pressing the power button 15 seconds until eventually it works.

Is this a sign of hardware failure or a bug? The phone was purchased new as a refurbished unit.
I have been only using Proton for the last 2 weeks and have found it to be extremely stable, and bundled with KRISHNA FLORAL, I get excellent battery life. That being said, I have been testing a few ROOT'd apps I am designing/working on, so I have to reboot quite a bit to test, and that's never once, ever happened to me. I have not had a touch issue, or unresponsive device in the last 2 weeks of using Proton, through maybe 100/150 boot/reboots.

Here is my Pixel 4 XL setup, Proton latest version, MAGISK ROOT (with no modules), FLORAL kernel, and I never have a touch issue on boot/reboot. I currently use FLORAL kernel, but the stock kernel was also fully tested anmd neither had any issues you describe.

Have you tried this without any modules, or anything 3rd party (fresh build), or stock firmware? If so, did you have the same touch issues running a clean build or running stock? What happens when you clean flash the firmware using stock, but absolutely nothing else modified (ROOT/MODULES/KERNEL)? I am asking because if its a device failure, then all ROMs/firmware would suffer and have it (for the most part), but if its something 3rd party that is causing it, then a clean or factory firmware would solve it so I would test this if it were me just to rule down the possibilities.
 

arsenalove

Senior Member
Oct 14, 2014
92
38
Perth
Sometimes upon reboot, booting into the OS takes 5-10 minutes to load and the touchscreen does not work. I have to manually reboot 3-4 times by pressing the power button 15 seconds until eventually it works.

Is this a sign of hardware failure or a bug? The phone was purchased new as a refurbished unit.
I had the screen issue on 11.5.2 only when I flashed a magisk module to hide the navigation bar . Otherwise never had any sorts of issue. Perfect rom. Cheers
 
  • Like
Reactions: GROOVYJOSHCLARK

GROOVYJOSHCLARK

Senior Member
I had the screen issue on 11.5.2 only when I flashed a magisk module to hide the navigation bar . Otherwise never had any sorts of issue. Perfect rom. Cheers
Thanks for the extra info, that's what I'm hoping to sift through and pinpoint to the root cause for the OP (which is probably a module or 3rd party kernel). I don't have the issue and I reboot a lot recently for development reasons. I'm hoping the OP who reported the issue does a full factory reset to test if it's device failing issue or software based issue (magisk module or kernel, or both). We will only know this by testing the factory or somehow undo anything 3rd party. Once it's factory reset but without anything else modified, they can test and if it can't be reproduced then it's just likely software but not hardware.
 

Phillis

Senior Member
Jun 9, 2009
98
8
Montreal
Thanks for the extra info, that's what I'm hoping to sift through and pinpoint to the root cause for the OP (which is probably a module or 3rd party kernel). I don't have the issue and I reboot a lot recently for development reasons. I'm hoping the OP who reported the issue does a full factory reset to test if it's device failing issue or software based issue (magisk module or kernel, or both). We will only know this by testing the factory or somehow undo anything 3rd party. Once it's factory reset but without anything else modified, they can test and if it can't be reproduced then it's just likely software but not hardware.
Thanks for the info and sorry for delay. I did not factory reset the device since it is my daily driver. I don't reboot often because of that. Today it took 2 manual reboots to get it to work.

I am on stock Proton but with Magisk. Magisk modules installed are Audio Compatibility patch, Systemless Host and Viper4Android FX.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Sometimes upon reboot, booting into the OS takes 5-10 minutes to load and the touchscreen does not work. I have to manually reboot 3-4 times by pressing the power button 15 seconds until eventually it works.

    Is this a sign of hardware failure or a bug? The phone was purchased new as a refurbished unit.
    I had the screen issue on 11.5.2 only when I flashed a magisk module to hide the navigation bar . Otherwise never had any sorts of issue. Perfect rom. Cheers
  • 13
    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
    7
    ProtonAOSP 11.5.2 has been released. Sorry for the delay this month; I've been busy with other projects, but here's the full release.

    Changes:
    • July security patch
    • Added search to website
    Added red, green, and blue color balance settings
    Added alarm, ringtone, and notification sounds from Plasma Mobile
    • Added HarmonyOS Sans font style
    Extended font styles to affect third-party apps (reboot to apply changes)
    Improved Night Light quality using chromatic adaptation (reduced color distortion)
    • Improved Ambient EQ quality (with modern color science: CAT16)
    • More gradual transition when turning Night Light on/off
    • Pixel 5, 4a 5G, 4/XL: Added setting for increased touch sensitivity
    • Pixel 5, 4a 5G, 4/XL: Added "Saturated" color profile
    • Pixel 5, 4a 5G: Fixed Night Sight crashes in Google Camera
    • Pixel 4/XL, 2/XL: Fixed Active Edge instability with multiple profiles
    • Pixel 4/XL: Added support for HDR10+ (Diab)
    • Pixel 4/XL: Added support for modem diagnostics

    Website
    Install from browser (recommended)
    Download

    As the ProtonAOSP project expands to support more devices, bandwidth and maintenance costs are increasing. You can help support the project and keep it alive with a recurring donation, or alternatively buy me a coffee. Everything helps, but a recurring donation is the best way to keep the project alive in the long term.
    5
    The vast majority of questions in this thread have been repetitive, so there is now a list of frequently asked questions to answer them.

    If you have questions or concerns, please read the FAQ before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.

    Feel free to ask your question(s) again if the FAQ doesn't currently answer them, and we will add an answer for you.
    4
    ProtonAOSP 11.5.1 has been released.

    Changes:
    • June security patch and feature drop base
    Added status bar icon and clock customization
    Added 8 font styles, including playful, serif, and AOSP fonts
    Added performance and other technical details to website
    • Improved dark UI color scheme
    • Fixed compatibility with some apps (e.g. Brevent)
    • Fixed instability in media-heavy apps (e.g. long video calls)
    • Fixed recents text selection in Pixel Launcher
    • Fixed unknown characters (tofu) in some text
    • Updated Now Playing song database
    • Updated permissions for Google apps
    • Updated website link in Settings
    • Updated system fonts

    Website
    Install from browser (recommended)
    Download

    As the ProtonAOSP project expands to support more devices, bandwidth and maintenance costs are increasing. You can help support the project and keep it alive with a recurring donation, or alternatively buy me a coffee. Everything helps, but a recurring donation is the best way to keep the project alive in the long term.
    3
    hey , how did you restrict apps that boot during device bootup ? Does it required SDMaid Pro ? and is root required ?
    yes and yes, ROOT with using SD Maid (I have Pro), so I am not 100% certain if BOOT / APP boot control is premium only or in the free version so test it and let me know. Once in SD Maid, go to app management, boot (see pic 1), and disable ALL apps you dont need. You would be VERY surprised how many apps start with boot (mainly GAMES and streaming services) so they can push you annoying game and app notifications. SCREW that, it does nothing but wastes battery, RAM, and annoys me the crap out of me so I block and disable them. Then, for things like the hidden Verizon tracking apps, I disable with IPChains so its firewall'd and dropped at the source and doesn't leave my device. Those apps (com.verizon.lkagent / com.verizon.obdm_permissions / com.verizon.mips.services AKA MY Verizon Services) start with boot and not only run in the background but collect device info and send to verizon, NO WAY that's happening! By firewalling those UUIDs, they cant reach the tracking services or verizon. Since they cant check in, they cant use RAM or battery or network (or at are using less resources than if allowed).

    I do this on ALL ROMs I test and use (even stock), but you can also freeze those apps with TiB (if you have) but freezing disables the app as if its removed, whereas turning off the BOOT, disables the auto-start BUT doesn't freeze (disable) so its still usable on demand. I use all of the apps I disable on BOOT, and I have NEVER had an issue with disabling boot so I highly recommend reviewing boot apps. Just keep an eye out and watch for apps you need to receive notifications from (like XDA or Messenger, or Amazon/eBay), stuff like that. I do not disable those auto-starts as I DO want update notifications but only a VERY few apps get to send notifications for my droids's (email/work/XDA/TXT stuff like that) or can run.

    I'm my last pic (I updated my post to show this piece), you'll see the verizon BULL SPIT services trying over and over to check-in but can't! This is WHY I firewall and DROP ALL verizon crap services so they can't track me. If you haven't seen or read what's being tracked, open the app data for my verizon and you will see literally everything about your device is sent to verizon without your permission. NOPE ain't happenin! They do not have my consent to know this type of information so to me, this is a clear sign of misconduct on their part but there's no way to stop it without firewall'ing the UUIDs (verizon services) or disable the apps and services all together. The problem with disabling them is WiFi calling is interrupted so I found it is better to simply drop the communication to their services then it is with disabling the apps.