yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] KnightTim:
Unfortunately, I don't live with my parents so I can't easily test. I might end up getting him a Pixel as an upgrade, if that is the case I'll probably trade him for the Essential PH1 and will have it for a bit, though that won't be til next month.

And my dad isn't savvy enough to easily dump a log.

(I don't know if it's related at all, but the Play Store is having issues detecting / connecting to the internet. All-in-all the PH1 has not been a great experience for flashing ROMs so far for me. I don't blame you, it's an older device that doesn't have as large a community as other devices.)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Since there's another user who reported the same speakerphone issue (which I obviously cannot reproduce...), I will try to fix it with his help, so it is possible it'll be fixed by an upgrade sometime next month.

The Play Store issue sounds totally new to me, I've never heard anyone complain about anything similar.
[Essential Phone ROMs, Kernels, Recoveries, & Other] brikki:
Hello Tomoms!

As I told you, In log1 I replicated the speakerphone activation during a call.

I noticed another problem, I would send you another log for black screen during a call.

Thank you again!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I'm doing a lot of work behind the scenes to prepare my first LineageOS 20 build. It'll come in a couple of weeks at most. I will not release any 19.1 build in February in the meanwhile.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
This post is about Klik (the Essential Camera App):

Tomoms' unofficial LineageOS 19.1 (and soon 20.0) includes patches to Klik that enable Portrait and HDR, but there remain problems with lags and freezes.

There is a setting in Developer Options that eliminates the lags/freezes. It is a workaround, and Tomom is looking at getting to a permanent fix.

So,

- Enable Developer Options (Settings/About Phone then tap Build Number 7 times)

- Goto Developer Options and scroll down to the 'Hardware accelerated rendering' section

- Tap/Enable 'Disable HW overlays'

Klik then works nicely.

Disable HW overlays lets the GPU handle the full screen display of the camera.

However it also makes the PH-1 use the GPU all the time, which consumes more battery than leaving the HW overlay enabled.

I haven't seen this add up to any noticeable additional battery drain, but I still have an original 2017 battery and my setup is very conservative. I set App Battery Usage to 'Restricted' for most apps, always have the Battery Saver enabled, and turn on WiFi/Mobile Data/Bluetooth/NFC just when I actually need to. So, your experience may vary.

If battery life is an issue, you could Disable HW overlays just when using Klik (not great for spontaneity).

NOTE:

The Portrait and HDR patches are not in [OFFICIAL] LineageOS 19.1 or Nolen's [UNOFFICIAL] LineageOS 20.

Tomom (and perhaps Nolen) will be posting about the future for Klik in LineageOS 20.

For now, Tomoms builds are the only ones with Portrait and HDR; and the 'Disable HW overlays' workaround is only for these builds.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
2023-04-12 EDIT: the only remaining issue with Klik is:

the app sometimes shows a wrong layout when the phone is rotated in landscape mode and the user is viewing a previously taken picture

2023-02-26 EDIT: issue #1, #2 and #3 are completely fixed, Klik is not affected by them in my unofficial LineageOS 20 builds.

Hi, so here is a complete overview of what is going on with Klik at the moment.

As we all know, since the release of LineageOS 18.1 for the PH-1, Klik has started working progressively worse: first HDR broke, then Portrait, performance issues arose, etc.

At the moment, as far as official LineageOS 19.1 for the PH-1 is concerned, these are Klik's issues:

HDR & Portrait mode crash;

the app quits when deleting a picture (the picture is however effectively deleted);

the app does not remember its settings, they go back to their defaults once you close it;

the app lags and freezes the whole phone, especially when using it in low lighting scenarios (daytime outdoor usage is mostly ok, at least in my experience).

Given the high severity of these issues, our LineageOS maintainers (in particular Nolen, with whom I talk about my development efforts pretty often) have decided that official LineageOS 20 for the PH-1 should be delayed until either I fix Klik properly, or I give in and we decide to switch to Aperture (which is a suboptimal replacement, as it does not fully exploit the two sensors, and does not support the external 360° camera).

After a couple of weeks of work, I have managed to fix issue #1 in a way that is suitable for official LineageOS (an inelegant fix has already been present in my 19.1 builds for a few months), but all the others are still present. I have a high-level idea of what is needed to fix #3, while #2 and #4 seem more challenging to fix in a proper way, although not impossible. As a consequence, in order not to excessively delay the release of official LineageOS 20, we will drop Klik and switch to Aperture. In the next few months, however, I will continue to work on Klik's problems, so that hopefully they are fixed before the next cycle begins (LineageOS 21), and Klik can be brought back!

My unofficial 20 builds (which I will start publishing here within the weekend, I think) will contain both Klik and Aperture. This way, those of you who want or need to use Klik will be able to use it while I fix it, with the option to mitigate issue #4 via the workaround found by @MuddyDog (see here: https://xdaforums.com/t/rom-s-mata-...eageos-20-february-26th.4344275/post-88145983 )
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
So, here we are! My unofficial LineageOS 20 builds are finally available!

Some interesting features are already available, while most of the optimizations will come gradually in the next weeks.

The biggest change this year is that my ROM now supports not only MicroG, but also Sandboxed Google Play! This very interesting feature, developed by the GrapheneOS team, allows to install Google Play Services, Play Store and Services Frameworks as normal user apps, instead of privileged system apps, greatly reducing the set of permissions they have, while maintaining almost all their functionality. Instructions on how to set up Sandboxed Google Play are available in the second post.

Keep in mind that using Sandboxed Google Play prevents you from fully passing SafetyNet (the Basic integrity test will pass, the CTS Profile match test will fail): Google Wallet payments won't work, and it is possible that some banking apps (not all of them: mine works, for example) will complain.
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
Flawless Build! Thanks you very much.

Regarding Gcam - i highly recommend the latest Parrot043 version v1.8. https://t.me/googlecamera_mod
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi there! A new build is available. It does not include March's security patches, because it looks like Google hasn't made them public yet, but worry not: this update is a big one!

Lots of optimizations applied at compile time, lots of updates to critical system components and the kernel, fixes for NFC issues and improved GPS performance are the benefits of today's build. Enjoy!
[Essential Phone ROMs, Kernels, Recoveries, & Other] morphius88:
@Tomoms

For some reason after flashing the 3/11 build, there is an update available for the same build. Same size too. Updating doesnt change anything. It goes through the whole process but the build stays the same and the same update is available again. The updater is showing 2/17 as the current build. Weird.

Screenshots attached.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Has anyone tried the dual speaker mod on lineage 20? Need to know before going forward with it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Oh ! I forgot to mention how Great this rom is. Only keeping my essential for this rom. Totally killing it even in 2023 😘
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.

I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.

Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Thank you, I am very much interested. Can't try coz I am using my essential as my main phone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] morphius88:
I dont really care either as long am I am on the latest build. I will try the dual speaker mod shortly as I am interested in that as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi,

a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.

Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] morphius88:
Sounds good. I will be on the lookout for that. I think I will also hold off on the new build for now or maybe I can try to fix the background issue by messing around with something like Project Themer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Thank you for your continued work on this device, and for the heads-up on potential issues. I'll also hold off till this is resolved. 🙂👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Well, you guys need not wait any longer. I've released another build which addresses that issue :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] morphius88:
Sweet! The option of using Themer did not work anyway. Neither did AOSP Mods.
[Essential Phone ROMs, Kernels, Recoveries, & Other] danz852:
Hi, thanks for the rom. I have problem when using WhatsApp video call. I can hear the voice of ppl on the opposite but they can't hear my voice. I need to end the video call and restart the call to make it work.

And one more thing related to WhatsApp. When using WhatsApp's Fingerprint Lock, sometimes it work the other times it's not working.

Does anyone have the same problems with voice on WhatsApp video call and WhatsApp's Fingerprint Lock?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.

It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] danz852:
Thanks for the reply.

At the moment, I think WA video call audio issue gone after I restart the phone several times. I hope it stay that way.

WA's fingerprint lock still randomly working. Not a big deal as I can still use Lineage Hidden & Protected app.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
@Tomoms , to go from your lineage 19 to this latest one, do you think a dirty upgrade will work (without wiping data)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
@MuddyDog tried this with one of my very first LineageOS 20 builds, and it worked.

@danz852 if the audio issue comes back, do grab a log though. It'll be useful for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
hi, as @Tomoms said, a dirty upgrade from his 19.1 to his very early 20 build worked smoothly.

but... i'm not reckless enough to have done that without a complete backup on hand. i don't recall whether i used Google Backup or Swift Backup.

also, @Tomoms current build has merged QPR2 and the Updater installs this build correctly. But, both @Tomoms and i found that going back to a previous build to do some checks (pre-QPR2 to QPR2) resulted in a lot of breakage. i think @Tomoms rolled back, while i just switched slots and rebooted.

so, @Tomoms newest build is really great, the Updater works fine, and i can't think of a reason to downgrade back to 19.1.

but be advised that going back to an earlier build will require a clean reinstall... and keep a healthy backup handy.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Thanks for the feedback. Yes, backups without question. Just want to save time by not having to reconfigure everything again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Yes, I have faced strange problems when rolling back after the QPR2 merge.

Sometimes I also faced visual glitches after normal 20->20 updates, but this only happened on some private testing builds I keep for myself. Builds released on xda are always free from these issues.

So in the end, I'd say you have a 95% probability of success. This is not official LineageOS, I don't want nor can give absolute guarantees of any kind, this is why I'm saying 95% and not 100%.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Well, the dirty upgrade went smoothly - all seems to work... EXCEPT: no DNS resolution! As a result, no network at all! This is with the latest stable (March 21), though I also tried latest beta (March 26) with same results...

Mobile works, and Wifi connects and shows strong signal. I can ping my router by IP, but can't ping any hostname. I've tried different options under Private DNS (including Off and Automatic, of course). I've restarted numerous times. I've cleare the cache. I've uninstalled and reinstalled Adguard (which updates the filters correctly - must be by direct IP).

Any thoughts/suggestions?
[Essential Phone ROMs, Kernels, Recoveries, & Other] izombiev:
I would say that every single custom rom for this phone has suffered from this. I used your version right after facing such bugs on another LOS maintainer, but your visual bugs drove me nuts (no offense).

Yeah, such bug seems to disappear right after a reboot but it's just a matter of time before you're again at it.

Regarding this, I've been using LOS 19.1 for as long as a week and I can guarantee that this does not exist here.

Restarting the phone every time this happens is not a big deal, but it does happen like 10 min. after the phone boots up xD
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Side note: don't flash the beta builds unless you're told so. They can be potentially dangerous. Though you've been lucky: it is not the case of the 03-26 one.

We can surely fix your problem.

Can you ping by IP a server outside your local network?

Please reboot the phone and grab a logcat after it has booted up.

What visual bugs are you talking about?

I'm waiting for the log :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] izombiev:
I will install your rom once again, Sir, in order to get logs and get this bug (audio one) fixed once and for all. I was talking about the transparent notification panel and the one that made me wanna cry was lock screen messages, which, despite being fully charged/disconnected from the charger, the phone kept showing "unlock to use all functions"; "charged" messages.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Oh well, the first one has been quickly fixed, the second one seems strange and I've never faced it, nor heard anyone complain about it. I don't think any of my modifications could cause such behaviour.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
@Tomoms here's the log [REMOVED]. Thanks in advance!

By the way, yes I can ping 1.1.1.1 successfully.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It looks like you are using Gapps, did you flash Android 13-compatible MindTheGapps immediately after my LineageOS 20 build, like you would do if it were a 19.1 -> 20 upgrade between official LineageOS builds?

EDIT: sorry, a second look at your log suggests you're using MicroG, is this correct?

EDIT #2: in my LineageOS 20 build, I've introduced patches from GrapheneOS that massively change how the Internet access permission is managed. It is possible that after the update, it has been automatically revoked, rather than granted, to all apps. Since I see that you have AppManager installed, use it to check if the android.permission.INTERNET permission is granted or revoked to most of your apps. If it is revoked, grant it and see if it makes any difference.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Yes, microG here. And, yes, I think we're on the right track with that permission. I found it was disabled for Adaway, enabled it and voila!

Will report back 😉👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
So, it was indeed a question of the INTERNET permissions being revoked and not requested. Thank you for pointing me in the right direction. I re-enabled it for the apps that should have it and all is well.

Other than that (which was a bit stressful because of not knowing), this was by far the smoothest in-place/dirty UPGRADE (Android 12 -> 13) that I have ever experienced. Everything is working and configured like before. Congrats to the developers and @Tomoms for maintaining this super-solid and snappy ROM!
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
I should add that it appears that INTERNET permission setting is more of a nuisance than security. If an app can still connect via a direct IP (without name resolution), then any well-designed "malicious" app will do that and bypass the lack of such permissions, no?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I don't think all apps would have been able to connect to an IP. I think the system components involved in the network operations that worked for you (pinging, IP-based filtering in AdGuard) were, indeed, system apps/libraries, and it might be that these system components were automatically given the INTERNET permission after the upgrade, and only the user apps were denied the permission. I don't really know. Anyway, the possibility of toggling the INTERNET permission is not really that useful on Lineage, since Lineage has got an in-built firewall that can provide the same functionality (although implemented very differently). The reason why my ROM offers the possibility to toggle the INTERNET (and SENSORS) permission(s) is because it is a feature tightly coupled with the Sandboxed Google Play code I picked from GrapheneOS. In practice, the latter can't exist without the former's code.

If you want to grab another logcat after ~1 h of normal operation of the phone, I can analyze it, just to make sure there are no other problems occurring in the background. Glad that we fixed your issue rather quickly!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I've released a new build, with lots of small improvements and updates, some fixes for Klik (which is not yet 100% perfect, but I'm getting there :D ), and April's security patches.

This build also introduces support for the three-finger swipe to screenshot gesture (you can enable it in Settings > Display).
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
I just dirty flashed the newest build with MindtheGaaps. Everything is working smoothly. I had the same Internet Permission Problem as Temporarium. And fixed it the same way.

I wanted to report that NFC now works with extended length transmission. Thank your very much Tomoms.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
hi, and thank u for sharing the build with everyone.

i'm on pixel experiance for a year or so, happy with my google photo backup.

i read somewhere on here something about pixel features. i was wondering if it means i'll get the google photos functions on this rom as well. if so i'd verymuch like to try this android 13 with some nice kernel features.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Yes, my ROM features an implementation of PixelPropUtils which is taken from PixelExperience 13, so any Pixel feature that is unlocked on that ROM, should also be unlocked on mine. I can't confirm, though, as I don't use Gapps.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
i hopefully find the time to flash and use it for some time and update here, thank u
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
I have installed it today on January update because any other update BTS fails on my phone followed by nikgapps. The OS seems smooth and everything seem work except there a notification saying 'app updates are ready, connect to wifi to continue' when wifi is on. So no apps. Ok wondering if anyone here has a solution for this
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Very old build + unsupported Gapps package = you're on your own.

I assume that "BTS" is a typo and you were referring to the "CTS Profile match" test that is part of SafetyNet. My latest build with the recommended Gapps package (MindTheGapps, https://androidfilehost.com/?fid=4279422670115734716 ) passes SafetyNet without any problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Any impact to Google account if I use these features? specially Google photo backup?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
I was off wifi for a while and after getting back on wifi the apps started downloading without me doing anything except the notification saying connect to wifi remained

I don't think so, I've been using pixelextended rom with this google photo backup for more than a year
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
by bts i meant back stock roms for some reason the latest bts alway put my phone to bootloop also any roms installed on that BTS reboots back to fastboot mode so i alway do jan update then install new rom. ur rom is super smoothe with all the apps installed and the unsupported gapps, unlike any other lineage os i tried. thanks for the link, i'll try and update my stock to latest and install the mindthegapps and see if the update the connect to wifi notification goes away. untill then thanks again for sharing the rom with us. I'll update here if i reflash it.