yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
While benchmarks don't tell the whole story, I ran Geekbench 5 on the latest Havoc and PA Beta.

- Havoc scored: 366 / 1506 (single core / multi core)

- PA Beta scored: 373 / 1542

The PH-1 has only a few officially supported roms: Statix, PA, Carbon, Lineage. And, since I'd like to keep using my phone, I try to keep up with their development, hope that they continue to support the PH-1, and hope that they work correctly. PA's development looks like a science project, but the beta works. An unofficial rom like Havoc (which is almost all working) is very dependent on the time/commitment of liamtw22, who is still at university.

The alternative roms for the PH-1 are the GSI roms, And, particularly the roms based on phhusson's very mature work.

His builds are always kept up to date and outperform all of the official builds.

So, I also ran Geekbench on the latest crDROM 11 (one of eremitein's builds based on phhusson and using crDroid 7.6 sources).

- crDROM 11 scored: 375 / 1615

The official roms are easier setup (restore from Google backup, pass Safetynet right away, etc.), while the GSIs need more hands on configuration (to enable VoLTE, pass Safetynet, manage backups). So lately, I have been test driving all of the official builds as they have been getting updated to Android 11. And, it has been easier and quicker to switch back to a rom like PA, which works better for me than the others.

If none of the official roms catches up to the phhusson GSI variants, then I'll go back to one of them (probably crDROM 11, CAOS 11, or Pixel Experince Plus). Or an Android 12 GSI.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
Geekbench scores don't mean much if the rom still feels sluggish and there are notification LED and speakerphone bugs.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pkt1986Q:
Unfortunately not released in India yet.. Plus still not at par - no ceramic titanium.
[Essential Phone ROMs, Kernels, Recoveries, & Other] pakpenyo:
Havoc:

Smooth

Extreme Battery saving (sometimes can't see notification from some apps)

Led Notification working fine

Problem with mic (WhatsApp call, etc)

Volume step (lot of customized)

PA Beta:

Smooth

Good Battery saving

No Led Notification

No issue with mic

No volume step/minimal customized

I always remove some default apps like Chrome, Photos, MusicFX, CameraGo, etc (not using Chrome), but ungoogled Chromium version works fine at PA and Havoc.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Sceccu:
With Havoc the only issues I have are I don't always get calls even with full service, and I have VoLTE issues.

With this ROM I don't have those issues but I have noticed I can't send texts to anybody that is not on Tmobile as far as I can tell. Which is a big frustration.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mawdogbe:
Having the same issue on T-Mobile. Are you running the build from the link or the newer one?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Sceccu:
6/29 build, that link for the 5/15 auto redirects to the 6/29
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
Hey there, I've installed the Ruby beta listed above (06/29), and whilst everything seemed fine, I can't seem to get mobile data functioning (network connectivity is only attained via WiFi). Is anyone else having this issue, otherwise I assume it's specific to my carrier (and this beta)?

I just dumped StatixOS as I wanted GPay to function (CTS/safetynet), without root (as Magisk borks O365 apps).
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
I'm using t-mobile and texting to recipients that are not on t-mobile has been working without any problems.

t-mobile is known to set messaging blocks ... could be worth checking.

Or, if the Messaging app is treating everything as MMS, then it could be an APN settings problem... but current PA beta doesn't enable access to Mobile Network settings. On my phone the automatic settings have everything enabled correctly.

I'm not having any problems with mobile data.

Disappointing to hear that guys are having these issues. Hope the PA devs are monitoring XDA.

The most active PA discussion is on Telegram. I'll post these problem reports over there.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Sceccu:
For what it's worth, I'm having the same issue on the 7/18 build of SatixOS4.2 which is Aosp based.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
Thanks guys - appreciate the feedback. Let's hope development continues and these issues are ironed out (getting access to the APN settings might help to some degree). It's a pretty solid ROM IMO, it's likely not top of mind on Mata as it might be on other devices. Anyway, looking forward to more releases.
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
Thanks for sharing, mate! The ROM does indeed work well, the only issue for me is mobile data is not working :(

I did a clean flash (except internal) from PA5. I also tried flashing PA5 again (data works on that, changed network mode to global since I'm in NL), and dirty flashed Ruby on top, the flashing worked, and there weren't any issues, but data was still not working. Any idea, how I can make this work? I prefer Ruby to PA5

Otherwise, could you please recommend any other Android 11 based ROM, that doesn't have in call mic issues (while on loudspeaker or otherwise)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
I had the same issue until I made a change to the APN (without root). Since the settings are grayed out adb isn't an option, though I had success with addapn;

ht*ps://play.google.com/store/apps/details?id=com.nyblnet.addapn
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
Thanks, will try it out if I go back to this ROM, I just flashed Statix 4.2 (03-10) build for now, and it seems quite stable.
[Essential Phone ROMs, Kernels, Recoveries, & Other] psychic_quark:
Anyone have the copy/archive/mirror link for the last/latest build? Especially since this and stock seem to be pretty much the only roms without the dreaded Mic bug.
[Essential Phone ROMs, Kernels, Recoveries, & Other] luis saucedo:
Hi friends, have the latest Quartz 5 build, the official page link is broken.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
Same. The website keeps "loading" all the time without showing up any devices or roms.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DeathGrind:
Im pretty sure it's a bug. It happens on Statix Rom also. Had to flash back to stock, too bad, i liked the rom.

Seems any android 10 based rom has the no data issue with verizon in my experince.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Everything is running great so far. One thing I've noticed is that when using the bottom search bar from the home screen, the app drawer pops up for a little, and then the search inputs comes after. Anyone else seeing this? I should note that this only happens with the Paranoid Launcher.
[Essential Phone ROMs, Kernels, Recoveries, & Other] KwesiJnr:
The in-call volume of this ROM is pretty low. It's about half the volume you get on the stock ROM. I can confirm this since I just reverted to stock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nijohnson:
Thats interesting. In every other Q rom I've tried, the call volume has been way loud.
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
Some minor issues -

a) when using the speaker for calls, the other side hears a lot of noise to the point of unusability.

b) videos in whatsapp - do not play. is it only me?

c) NFC toggle doesn't work.

These are all things I can live with but perhaps can be improved later on! :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] mpena:
I can confirm the three issues, the issue a is only in speaker mode for me. I hope that the three issues can be fixed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mhamzas:
I do face (a) issue on Statix Rom as well
[Essential Phone ROMs, Kernels, Recoveries, & Other] mpena:
Edit: I now can record, I have a setting in the Google camera that I think was causing trouble with the app and the others apps. But still can't record directly on WhatsApp.

Another thing that I'm facing an I did know just recently is that I can't record video and some times the photos don't save.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nijohnson:
Does the ROM have customizable volume steps?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
I don't think that they are customizable, but, they did add more steps. In my opinion, much better than stock.

---------- Post added at 10:14 PM ---------- Previous post was at 10:09 PM ----------

Issues I'm having:

i) Lock screen wallpaper doesn't set

ii) Mic seems a little quiet when talking to someone on the phone (earpiece speaker is fine)

iii) Boot animation freezes before it reaches the lock screen (minor issue, ROM still works)

iv) Charging animation when phone is shut down is off center (very minor issue)

v) Video playback errors

That's all the issues I could find so far, will update if I have more. Great work on the ROM, much appreciated.

Edit: Fixed the camera, just need to delete the current DCIM folder and Clear the data for Media Storage (in the settings)

Edit #2: Camera fix only worked temporarily.
[Essential Phone ROMs, Kernels, Recoveries, & Other] oken735:
I similarly to DeathGrind get no data on Verizon, but I do get texts and calls. I also tested a Mint mobile sim and I get LTE+ just fine and everything works.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
360 Cam Shutdown

One issue i have noticed is with the 360 camera. When connecting it and switching to video mode, the phone shuts down. It's happened to me three times in a row. I attempted to catch a logcat. Hopefully there is enough in there to help. Note that when I plugged in the phone, it did not shutdown and I was able to record a 360 video.

Another issue I encountered the other day was with bluetooth. When using bluetooth headphones on a phone call and tapping the mute/unmute call, eventually the phone shutdown and when I rebooted, all my theme settings were lost. It had reverted to the default color and font. Also, I was getting tons of Bluetooth force close. Unfortunately, I did not have the chance to get a log for these errors so hopefully someone else out there has experienced the issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Also, whenever I'm using the Hotspot, the phone does not show any devices connected.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
No rush here, but is there any plan for when to expect the next beta build?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
Latest build isn't booting for me.

Edit: Was being dumb. I was following the instructions before they updated the page. Love the boot animation though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CharFalco:
Supposedly this is official now, no longer in Beta. Does that mean OTA works now, and if so how do I enable that and what recovery do I need?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
Looks like OTA works. It's pre-enabled. Go to Settings -> System -> Advanced -> Paranoid Android Updates.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CharFalco:
So I should flash the vendor image to both slots, boot TWRP, flash TWRP installer, reboot to TWRP, wipe everything, flash this, flash the installer, and reboot? Do I need to reflash the TWRP installer after each update? What if I want Magisk?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
If you haven't already, yes. After every OTA, you DO need to reflash TWRP installer. Then reboot to recovery, and install Magisk. However, on some ROMs (not sure if this has it) integrate Magisk in the OTA so you don't need to reflash Magisk.

---------- Post added at 10:37 PM ---------- Previous post was at 10:37 PM ----------

Safety net is broken on stable release.

Edit: Fixed Safety net. Follow these instructions: https://xdaforums.com/apps/magisk/safetynet-fix-google-update-march-2020-t4063679
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
It's awesome that you guys were able to go stable so quickly! Any chance that a non-Gapps build is released? I installed AOSPA because I didn't want Google Apps and needed to flash a custom ROM. I went with what I had known back in the day and wasn't disappointed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Is the mic issue present in this update? The mic issue where it doesn't work with WhatsApp /uses the rear microphone instead of the bottom one?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Snowbird04:
On the first page of this post, it says the QQ1A.200105.088 Vendor image is required for this ROM, but a later reply says that it is not. I thought QQ1A.200105.088 was for Android 11 support? I'm currently only running the February QQ1A.200105.032 build.

Could you please clarify and confirm which build is required?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ggpew2:
qq1a.200105.088
[Essential Phone ROMs, Kernels, Recoveries, & Other] hogehoge61:
Stock camera app doesn't work

I flashed pa-quartz-1-mata-20200415.zip on my Essential Phone PH-1 (mata) and it worked fine, but the Stock camera app (com.essential.klik) crashed and didn't work.

After some trial and error, I found out that this is what happens when a Japanese carrier's SIM card is inserted.

If that SIM card is not inserted, everything will be fine with the Stock camera app.

I think the reason for this bug is that Japan is one of the few regions that fall under the specification of "Shutter sound is forcibly enabled when the SIM card of the region is inserted".

When using the Stock camera app with Stock ROM, the shutter mute function will be hidden if a SIM card is inserted in some areas, including Japan.

I know that this is a very minor problem, but I'm in Japan and I use the 360 degree camera module in the Stock camera application, so I'm very troubled.

Also, this bug seems to occur in other custom ROMs (such as LineageOS 17.1) as well, but where is the appropriate place to report such information?

EDIT: I flashed Quartz 2 ( pa-quartz-2-mata-20200425.zip ), but this issue is still not fixed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mimariposa:
If you are on February QQ1A.200105.032 build, I am afraid you won't be able to get into TWRP in the first place and flash any ROM for that matter. Your best bet would be to flash JAN QQ1A.200105.007 build, then install TWRP and try flashing this ROM. I did exactly that, but am still not able to install this ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Snowbird04:
So I managed to get it to work by following the january release / aosp vendor flash from the StatiXOS thread (you'll see it first page). I then followed the instructions on flashing the twrp.img and zip. I then installed the ROM through TWRP. That seemed to make it work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mimariposa:
Thanks for the headsup!! I will try doing that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] cocadanko:
HOLA
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Anyone has a full proof method to get touch in TWRP without fail? I had a way that worked before but for some reason, it does not seem to work anymore even though I'm following all the same steps as before? This is just annoying to have to go through all this trouble just to get touch to work in TWRP. I'm in the January image on both slots. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
This is how I did, and it works all the time:

1. Transfer ROM, TWRP installer.zip to phone (for example: /sdcard/download )

2. Reboot to bootloader

3. Use fastboot to flash TWRP img file

4. Goto Recovery mode (TWRP recovery ... now no touch for sure)

5. Need OTG USB dongle to connect external mouse from this step

6. Use mouse to flash ROM (first) and then TWRP installer zip file (after flash ROM)

7. Reboot to TWRP recovery to check touch if working (for sure it's working now)

8. DONE
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I did not realized I could use the mouse on that phone. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
So even after your approach, I'm still not getting touch in TWRP. But I don't care that much anymore now that I know I can use the mouse.

---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------

Is it just me or the device is shown as Not Certified in Google Play? That's kind of a bummer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Something is not right. I suggest you re-flash Jan stock ROM to make sure everything is ok .
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I'm wondering if it isn't the QQ1A.200105.088 vendor that causes the device not to be certified. Cause I did start with a fresh January flash_all, but flashed the new vendor afterwards as recommended on the OP. I'll retry without flashing that vendor. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Here' how I did:

1. Back to Jan stock ROM

2. Use fastboot to flash QQ1A.200205.088 vendor image (to both slot a and b)

3. Transfer PA ROM, TWRP installer to phone

4. Flash TWRP image (again no touch at this point, need to use external mouse)

5. Boot to TWRP Recovery and flash PA ROM (first), TWRP installer zip (second)

6. Reboot to system

Note:

1. For me, it took very long at first boot (I almost force quit because I thought it's got hang at PA logo rolling)

2. This ROM is very close to stock ROM and smooth

3. I'm back to stock ROM because: Google Play system security update doesn't show what version it is, the only information this ROM said is "up to date", I'd like to know exactly how "up to date" not so general info.

If anyone can live with it, then everything else is ok.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Yeah that's exactly what I did the first time and it booted, albeit with "Device not Certified" showing in Google Play and the unknown Google Play system update. So my guess is with this vendor image, the device is not GP certified and that's a problem for me. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
If you try again with Feb stock vendor image, could you please let me know how it works? I'd like to see the Google Play system security patch level.

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Where does it show device not certified in Google Play exactly? I'm trying to compare mine.

I'm using the aosp vendor as recommended in the OP and rooted with Magisk. I have Magisk Hide enabled too. The safety net check in Magisk shows CTS profile false, however. I looked into it and it appears Google changed something with safety net in the March security update. Everyone with a custom rom, unlocked bootloader, Magisk, etc. Seems affected. There may be some exceptions.

I did find a solution. I installed the safety patcher module for Magisk, then edited the script to remove line 11 from the script. Details are in the xda thread for safety patcher. You might have to go back a few pages though.

After a reboot, CTS profile is no longer false. I just wanted to see if I'm getting what you are and see how "fixed" this is.

BTW, my Google Play security update also shows unknown.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
So I tried fresh January with February vendor and I don't get past the Essential logo. It just sits there and never boots. So that seems to be a no go but I'm a bit surprised given that I believe someone else on this thread said he did this and it worked. Just not for me though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Open Google Play->Settings and scroll all the way to the bottom (see screenshot). I'm with you on this though, it seems like something changed. I was on evolution x before with the device certified. And now when I go back to eX, it also says the device is not certified. I'm puzzled. And now suddenly I don't get to install Netflix which I could before even on the beta of this rom.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Ok, yes. I see that. Mine says not certified also.

I side loaded Netflix from apkmirror (had to use their new app to install it though). I didn't try opening it before hiding it in Magisk Hide and applying the safety patcher fix though. But Netflix is now showing up in the Play Store for me now, even though I side loaded it. I was able to sign into the app, but haven't tried playing anything yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I might try this if it comes down to it. But I was trying to avoid the Magisk route given all the issues people are having with it. I was hoping I could stay with the rom alone and have everything working fine. But it appears we're not there yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Well... An unlocked bootloader in itself trips safety net and Netflix won't install for anyone that trips safety net. Magisk hide will hide an unlocked bootloader. There are also or were also tricks for the kernel to hide an unlocked bootloader I think... Seemed like Franco kernel did this when I had the Nexus 6.

And what issues with Magisk? I've been using it almost since the beginning. Only issues are if you use a module that's not compatible and that's been getting better and better as developers add scripts to detect compatibility.

---------- Post added at 05:05 PM ---------- Previous post was at 04:44 PM ----------

So... Voice calls aren't working for me... No audio on either side

Edit: James DSP broke call audio
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
For me, I've never been able to get it to stick. I flash rom + twrp, reboot to recovery and flash Magisk. Then when I reboot the rom, Magisk still says it's not installed. So I gave up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Milan P.:
Is anyone else experiencing screen timeout issues? Mine doesn't seem to turn off the screen.
[Essential Phone ROMs, Kernels, Recoveries, & Other] shri_chanakya:
Don't pay same thing on multiple threads. These are rom specific threads, post it on rom you are running.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Just a FYI, viper4android and james DSP both break call audio. Once installed, there is no audio on my end not the other end of the call. Uninstalling them fix this
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I gave it another try and this time around I finally managed to have Magisk installing successfully. Is the module you were referring to called MagiskHide Props Config?

---------- Post added 19th April 2020 at 12:08 AM ---------- Previous post was 18th April 2020 at 11:35 PM ----------

Can you point me to this safety patcher fix? I found one but I want to make sure it's the right one. Thanks!