yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] F_S:
Hrm, I'm getting video playback issues. No sound and very slow playback. Allegedly it's firmware related. Anyone else experienced this?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
Thanks! I'm going to try this out
[Essential Phone ROMs, Kernels, Recoveries, & Other] fastoy:
Duplicate
[Essential Phone ROMs, Kernels, Recoveries, & Other] fastoy:
I have been running Lineage 17.1 on my Essential PH-1.

I followed the procedure at https://wiki.lineageos.org/devices/mata/upgrade to upgrade.

I used lineage-18.1-20210419-nightly-mata-signed.zip and MindTheGapps-11.0.0-arm64-20210412_124247.zip

The upgrade process completed successfully but I couldn't add an account. When I tapped on "Add account" the phone just beeped and did nothing.

Then I tried a clean install following the procedure at https://wiki.lineageos.org/devices/mata/install with the same files.

The result was the same.

How can I add a Google account to my Lineage 18.1 PH-1?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
Did you do a reboot to recovery between installation of the lineageos zip and mindthegapps installation? That is required, and I missed it when I first upgraded.

(I'm assuming you're using lineageos recovery.)
[Essential Phone ROMs, Kernels, Recoveries, & Other] fastoy:
Yeah. That was in the "upgrade" instructions. I've done this a number of times and never had this problem. I usually use OpenGApps though. I don't see that they have a version for Android 11 yet.

I don't see the Google apps at all. I'm going to try another time.
[Essential Phone ROMs, Kernels, Recoveries, & Other] fastoy:
I performed the "install" instructions AGAIN. Obviously, I did something different and it worked this time. I'm up on 18.1 with GApps working fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jefffrom:
question I found a install video older but will this be the same as installing 18.1 I will have to add gapps to and install after the OS ? or just add the gapp along with the OS I'm a little rusty last phone I did linageOS on was a moto E4 plus

here is the video
[Essential Phone ROMs, Kernels, Recoveries, & Other] garfnodie:
I seem to be having a more extreme problem of every app not responding and/or crashing. I've reflashed multiple times, redownloaded all files and ran checksum on files and always fine, tried multiple cables and tried different usb plugs on pc and all with same results. I'd try that statixos thing, but those instruction are using TWRP, which I could never get to work when I initially rooted last year, so I've just using LOS's recovery. Someone on reddit said you can't flash that zip using LOS's recovery, so I'm not sure what to do.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Try crDroid, although not official but OP update regularly and the rom is stable, good enough for daily useage.

https://xdaforums.com/t/rom-10-0-unofficial-mata-microg-volte-wireguard-crdroid-v6-17.4129739/
[Essential Phone ROMs, Kernels, Recoveries, & Other] garfnodie:
I appreciate the suggestion, but that's Android 10 and I'm wanting 11. If Android 10 is my only option, I'll just go back to Lineage OS 17.1 as that was working fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Talking about StatixOS, what steps did you have problem with? For me, install StatixOS is so simple (possible device related?). If you have touch issue with TWRP, you can find the patch version of TWRP boot image in StatixOS telegram channel which gives you touch capability during flashing. Anyway here the sequence that I install it.

Make sure you're back to Jan stock before to process:

1. Copy StatixOS + TWRP installer + Gapps to phone

2. Install TWRP boot image

3. Wipe Davik/Cache/Data storage (don't wipe internal storage)

4. Flash StatixOS

5. Flash TWRP installer (I don't bother slot selection, just flash it, and it works for me all the time)

6. Reboot back to TWRP recovery (important step if you want to install Gapps)

7. Flash Gapps

8. Reboot phone for phone setup

9. Install Magisk if you want to root (I do this step last after the phone is fully function)

Hope you can get it work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] garfnodie:
I don't want StatixOS itself. There was a post further back about pulling the firmware from StatixOS, flashing that, and then flashing Lineage OS. I don't know how to pull the firmware out of one ROM and install it on it's own before I then install LOS 18.1 as usual afrer. I don't want to use TWRP though as it never worked when I initially rooted last year, and I still see lots of people talk of issues with TWRP on the PH-1.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
After the latest update my phone only reboots into bootloader. From there I can't even reboot into recovery, it keeps going back to bootloader. And, it's not detected on my computer via adb, which it was before. Any suggestions?

I usually manage to get out of trouble spots like this with my phone, this one has me stuck.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mawdogbe:
Do you mean fastboot isn't detecting it? If you can get fastboot to recognize the device, I'd just go all the way back to stock and then re-flash the last build you were on before you started having issues.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
PSA: Newest update seems to not want to boot, using fastboot to switch slots back to the old one allows devices to boot again.

If installed, the newest update fails past the initial bootloader and doesn't boot from the boot_a/boot_b partition, whichever is newer, and adb won't work as far as I can tell, fastboot will work though provided you have the right drivers etc for your computer.

Feel free to ask me for help with switching slots if anyone needs, here or in a pm.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
I can't boot into system and constantly run into fastboot mode either. Having switched to the other slot to continue use the phone properly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
You can just boot into fastboot mode, and use "fastboot --set-active=<slot>" command to switch slots, where you should replace "<slot>" with "a" or "b", which represents slot a or slot b.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
same thing happened to me. it rebooted to the bootloader. from there i was able to use the volume buttons to switch to recovery, though i didn't actually enter it. i went back to the bootloader.

i was still able to detect the phone with fastboot devices, though. in the past, some usb ports on the laptop worked better than others, and i found that switching allowed for detection, again.

i switched slots and rebooted and the phone came back up to the previous version. when i tried installing, it came back with an error. when i tried again, it started the process, which i canceled. i deleted the download and then grabbed it again and installed.

it rebooted to the bootloader, again.

i switched slots,, again, and rebooted to previous version again.

with the essential builds, sideloading the ota did not lose any information. i am assuming the same is true for sideloading the lineageos zip? or no?
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Update: after the update failed and my phone couldn't get past bootloader, I left it in the charger. When I came back 30 minutes later it had rebooted into system. It's on the previous update, so I'm guessing it rebooted into the old slot.

When it was stuck in bootloader I was trying 'adb reboot ...', not fastboot, so that was my mistake. It probably would have gotten me unstuck.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Yes, you won't lose information sideloading the lineage os zip provided you don't wipe anything yourself.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
That's interesting, it should ideally reboot into the old system after 3 failed attempts just like chrome OS does with it's boot flow, didn't fix itself for the 20 or so minutes I waited for it though
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
fastboot set_active a worked for me, are you sure you used --set-active= and not set_active

I am using the essential fastboot for what it's worth
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
on the lineageos issues page, it's reported that sideloading will not correct the issue, so i am going to skip it. thanks, though!
[Essential Phone ROMs, Kernels, Recoveries, & Other] haggertk:
OK, I've pulled the 2021-04-26 build
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
Both are valid.
[Essential Phone ROMs, Kernels, Recoveries, & Other] npjohnson:
Works in Google maps here....

weird - can't replicate in youtube, file a bug ticket as per the wiki instructions please?

uhhh - sounds like you need to wipe data - something sounds messed up.

Just follow the wiki guide and all will work fine.

you need to format /data and just follow the wiki guide, thing shouldn't crash, so long as you use lineage, and (if you want) mindthegapps

please don't discuss other ROMs here - go elsewhere for that.

please don't discuss other ROMs here - go elsewhere for that.

Their firmware fix is placebo - it's the same firmware - I'm looking into the webview issue, and strongly suspect it'll be fixed in the next build (newer webview version built in).

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Thanks mate! Appreciate you maintaining Lineage for our device
[Essential Phone ROMs, Kernels, Recoveries, & Other] buckiller:
Is it possible to fix (make lower) the lowest brightness setting for mata in 18.1?

I don't know how it was in 17.1, but the stock images had Android P introducing a higher lowest brightness, and then a later update from Essential (July 2019?) lowered the lowest possible brightness. It seems like 18.1 has the lowest brightness possible as too bright: it's very bright in a dark room.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
@npjohnson since you seem to be involved with the development of LOS, do you have any idea what's going on, on phone calls, with the loud speakerphone that doesn't respond to the volume keys? i can't remember, anymore, which versions of essential's builds had the same problem and i never read anything about what they did to fix it. i do remember that it wasn't an immediate fix.

the fact that it did exist in essential's builds, oi LOS17.1, and now in LOS18.1, makes me think that it's something deeper than a ROM typically goes. but that is just my not-understanding-the-nuts-and-bolts-of-things thought. :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] npjohnson:
There's a bug ticket open for it, unsure what the cause is, but we know about it and are trying.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
cool. it's not a huge deal. i just turn the call volume up and hold it away from my head. it's speakerphone'ish. thanks for the work you all do :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
PSA: Today's lineage OS build boots fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] F_S:
Quick update after the latest OTA. Can no longer replicate the video slow down bug. All is running smoothly! Thanks again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jefffrom:
I want to flash but very nervous anyone want to make a video how to for noobs?
[Essential Phone ROMs, Kernels, Recoveries, & Other] malerocks:
If you read the instructions on the lineage website for the device, it's pretty clear
[Essential Phone ROMs, Kernels, Recoveries, & Other] andypiznti:
im still on the old old official essential os (QQ1A.200105.007) with twrp installed. will i have any problems installing this, using the wiki? i believe my bootloader is already unlocked. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Use LOS recovery to intall. TWRP doesn't work well with LOS, besides it's too old.
[Essential Phone ROMs, Kernels, Recoveries, & Other] andypiznti:
so i got it up and running but no one can hear me when i use the speaker on the phone. i have sprint. i tried turning VoLTE on and off. neither worked. i could hear them fine but they couldnt hear me. yesterday, on stock, it was fine. i couldnt find an area to update my prl or anything like that. i tried changing the networks too, but nothing worked. only when using speaker, using it regularly, they can hear me. thanks for any help!
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
I remember this issue is on and off in mata and not only happens in LOS but also in other roms as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Hasn't ever happened to me, I'm on the 5th February vendor, what vendor are you guys on?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
Lineage builds include all 15 files needed to run Android on the PH_1 (abl.img, bluetooth.img, boot.img, cmnlib.img, cmnlib64.img, dsp.img, hyp.img, keymaster.img, modem.img, nvdef.img, rpm.img, system.img, tz.img, vendor.img, xbl.img).

It doesn't matter what earlier PH_1 build was installed, Lineage installation overwrites every .img file.
[Essential Phone ROMs, Kernels, Recoveries, & Other] andypiznti:
i had read it didnt matter, but i was on QQ1A.200105.007 which i think was the Jan vendor. i still cant get the speaker to work. i tried messing with the audiofx app too but it didnt seem to help. duo with the speaker works fine, but speaker with the phone doesnt work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Not sure then, a backup and a fresh install is probably your best option, if that fails then providing a logcat would probably help
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
February vendor update here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jobayer:
Can anyone help me how to pass SafetyNet? I can't use banking apps and google chrome freeze continuously. Except this two, everything working fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
i don't know if this is related to an existing bug ticket. yours is different, in that no one can hear you.

Microphone issues (noisy, low volume) on speaker mode (#2209) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Microphone audio should be clear when on speaker mode. Current Behavior

gitlab.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
i saw that others had experienced this and got it to pass using the canary build. that's what i did, and it worked for me, too.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Regarding the Chrome freezing issue: When I (dirty) upgraded from 17 to 18, I didn't have this problem. For other reasons I decided to do a factory reset of my phone, and clean flashed 18. Then I had the problem with Chrome (and all browsers) freezing after a minute. I tried everything that's been suggested to fix it, no luck. I flashed original stock firmware, Jan/Feb 2000 modems, etc.

What finally fixed it for me was factory reset/flash last version of 17.1/flash first version of 18.1. I'd be curious to hear if those who had the browser freezing problem did a clean flash of 18.1, and those who didn't have the problem did a dirty upgrade from 17.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tnthd2:
It's the same problem as described in issue #2209. Just found out it's because it switches to the top/ambient mic instead of the bottom one when speaker is on in a phone call. Speak to the top mic and the recipient can hear quite clearly.

There seems to be a workaround using Open Camera:

https://www.reddit.com/r/essential/comments/hr5icc
.

Hope it's fixed soon in LOS.
[Essential Phone ROMs, Kernels, Recoveries, & Other] fr0styx:
Hello All,

I'm having the same audio crackling/speed-up issue, basically when the person in the other end speaks my essential ph-1 just reproduce it at a crackling-speed-up noise.. but they do can hear me fine when i speak. Also, switching to speaker will then effectively make both channels IN/OUT to go in some sort of mute (i cannot hear them and they cannot hear me).

This doesn't happen in stock (I have tested both PH1-OTA-PQ1A.190105.090 and PH1-OTA-QQ1A.200105.032 and don't have any call issue at all). So what I'm doing is clean flashing stock, then I would follow lineage wiki installation page to get both the 18.1 lineage rom and recovery installed as per the step by step..

Any ideas? Should I flash vendor images over the already installed 18.1 to fix the call audio issues?

Appreciate your help

EDIT: So it turns out that if I disable VoLTE within my mobile settings the call start working just fine and i don't experience any of the above issues mentioned.... hope this helps anyone having these issues.

Now the question is, has someone with T-Mobile have a way of getting VoLTE working fine? As id love to have it for WIFI calling.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jbloggs2008:
Noob question - I couldn't find the canary build. Can you let me know where you got it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
You can switch to the magisk canary channel in the magisk app settings iirc
[Essential Phone ROMs, Kernels, Recoveries, & Other] life02:
Anyone else have issues with the Google Voice app? It works fine on first install (or after clearing storage) once. Each time I open it after that, all the tabs are blank.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
heh. that's good to know, as i went through the process of uninstalling it, downloading the apk, and following the instructions to install it via recovery.

the instructions for doing so are here, though if i ever have to do it again i will use the settings method.

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
At some point the recovery method of rooting with Magisk stopped working for me. What did work was installing the apk directly on my phone like any other apk, very easy. After this morning's update, surprise, the phone retained Magisk/root and I didn't have to reinstall it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mario3DS:
Hi, I've owned an essential phone since 3 years ago and I've just decided to finally install a custom ROM in it. Just want to thank every mantainer because the ROM is excellent, the only 3 bugs (I could completely fix one of them thanks to an user in this thread) I've encountered are actually not game breaking, and Magisk passes SafetyNet just fine with the Canary build.

Hope you guys can fix the "activating speakerphone during a call switches from the bottom mic to the top mic" and the "Chrome crashing after a minute" bugs. If you need any logcat regarding those bugs I'll be pleased to give it to you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Barracuda79:
when I quit an app by swiping up to get to the homescreen, it sometimes takes quite long for the homescreen and the widgets to appear. The problem does not exist with the trebuchet launcher, but with all the other launchers that I have tried.

the alexa app doesn't work either.
[Essential Phone ROMs, Kernels, Recoveries, & Other] npjohnson:
We include everything! Just flash lineage recovery (mata TWRP is outdated as hell), and then follow the wiki guide!

If you flashed lineage, you're on our vendor, not Essentials. Much different.

Good man, yeah, we try to have a simple UX that makes getting on LineageOS as easy as possible.

Fresh install should always be first debugging step for this type of issue.

If you flashed lineage, you're on our vendor, not Essentials. Much different.

Yeah we're aware, it's hard to solve - the mics on this device suck lol.

speakerphone - trying, but it's hard to fix.

chrome - no clue why only some people hit this... Try Googles webview from the playstore maybe?

wiki has details for providing bug reports, would love to see them.

No clue, Pixel Launcher is fine here - and idk why Alexa wouldn't work - maybe safetynet?
[Essential Phone ROMs, Kernels, Recoveries, & Other] malerocks:
No issue with launcher. I am using Nova. Am on the beta based on launcher3 though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
hey there, thanks for you and everyone's work on LOS.

i don't know if this helps, but the phone had this problem while running the official releases from essential. It went on for a while, then one release (no idea which, but i will try to find) it was fixed. I don't recall if what they did was disclosed, but whatever it was the speakerphone worked great, after that.

trying to find when and what they did is going to be a pain, i am guessing, but i will give it a try and report back if i find anything.

edit: thinking about it, i can't recall if the problem was an absolute loud volume that didn't respond to the controls, or if the minimum volume was still too loud. this occurred to me as i am doing searches and i see the complaints that the minimum was still way too loud.
[Essential Phone ROMs, Kernels, Recoveries, & Other] fastoy:
I did a clean flash of 18.1 and do have the Chrome freezing issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
You might want to do what I did - clean flash the last 17.1, then flash the first 18.1. It may have been a coincidence that this fixed it for me (most likely), or it may have been the reason. I'd be curious to find out if it works for someone else.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mario3DS:
wow, I thought it was just a matter of changing a 0 to 1 or something like that

I actually tried to use a different WebView than the stock one but it crashed anyways, I also tried Chrome Canary and it still crashed, guess I'll try with other WebViews to see if one of them works

@malerocks have you tried setting up Alexa here? android Settings > Apps > Default apps > Asisstant
[Essential Phone ROMs, Kernels, Recoveries, & Other] malerocks:
I don't use Alexa. Am on google assistant. Sorry.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] npjohnson:
Google Pixel 3a XL

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

bonito

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!

Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Yaznas:
Going to try it now.

Thank you!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] ssurell:
syntax error Are we talking about the Kernel being bundled?