yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] DavisD2:
Thank you for doing that, I appreciate it. I just tested mine and am able to record a voice msg as well, but with phone and video calls, there is no microphone.

Since microphone works for a voice msg and not a call, I'm inclined to think it is a software issue, but everything was working before, all things being the same except this ROM.

Could I trouble you to test a voice or video call and see how that works for you?

Thanks again.

---------- Post added at 03:49 PM ---------- Previous post was at 03:13 PM ----------

Some notes - the PH1 apparently has two microphones. The bottom mic is generally used for calls, and the top mic for recordings.

Through testing speaking softly into the top and bottom microphones, I have verified:

The regular built-in Phone app (not Signal) works fine, using the bottom microphone.

The Signal voice recording feature works fine, using the top microphone.

With that, I am confident that it is not a hardware problem.

For me - Signal (on this ROM) is having a problem accessing the bottom microphone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Tested, no microphone on calls, weird bug... Voice msg works fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
---------- Post added at 06:16 AM ---------- Previous post was at 06:04 AM ----------

You need to install a terminal after installing the magiskhide props config and BusyBox. Then su - root type props select 1 to edit fingerprint. Next type f. Then you will get a list of device venders Essential is on there but I went with google 6. Next it will show you all the devices made by that company I chose 22 Google pixel 4 . After that let it do it's thing . Reboot and your cts should pass! Your welcome!
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
Tried that, doesn't work afaik
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Worked for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Why Google pixel 4? Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
That's the one that worked for me. You can try any of them and see what happens.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Props select 1 throw me this

:/ $ su - root

:/ # props select 1

Loading... Please wait.

MagiskHide Props Config v5.2.4

by Didgeridoohan @ XDA Developers

=====================================

Collect logs

=====================================

This will package the Magisk log and the

module specific log files, together

with the device default build.prop

file and all the current prop values

to a file and save it on your device.

Upload the file to the support thread

@ XDA, with a detailed description if

you're having issues.

Do you want to contine?

Enter y(es) or n(o): y

MagiskHide Props Config v5.2.4

by Didgeridoohan @ XDA Developers

=====================================

Collect logs

=====================================

Logs and information collected.

The packaged file has been saved to the

root of your device's internal storage.

If it did not, please see the documentation

for details on how to collect the logs

manually.

Attach the file(s) to a post in the support

thread @ XDA, with a detailed description

of your issue.

Press enter to continue...

MagiskHide Props Config v5.2.4

by Didgeridoohan @ XDA Developers

=====================================

Bye bye.

=====================================
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
i attached step by step of pictures below.\/ also when it says something about reboot not working, just reboot manually.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
I. Was writing props select 1 haha..

1 su

2 props

Then select different options of menu.

Select Google pixel 4, then restart, but don't work for me :'v don't know why.. Is activated and all

Pd: works deactivating riru exposed module.

Pd2: Netflix freeze and restart the phone :o someone else experience this?

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
I can't print as pdf on chrome as I do before. Don't know how to fix it
[Essential Phone ROMs, Kernels, Recoveries, & Other] d0u8l3m:
Flashing that put my phone in a bootloop....wont get out of fastboot now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
You're going to have to provide more info than that, what ROM, what else you flashed etc etc
[Essential Phone ROMs, Kernels, Recoveries, & Other] d0u8l3m:
Ive been running the latest build provided on here. Didn't flash anything other than what you linked to try to fix the mic issue.

I fixed it by reflashing the system with the same build.

Probably gonna go back to stock. LOS aint what it used to be. Its more stable on my old galaxy s4 -_-
[Essential Phone ROMs, Kernels, Recoveries, & Other] foueddyf:
LOS17 has not been officially released for mata...

The LOS in this thread is a beta at best thus not bug free.

It's not really fair to compare an official build to an unofficial one.

Imo, if you want stable Android 10, stock is your best bet.

Once LOS17 becomes official for mata, it will become more stable and the other roms will follow suit.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Official want either. At least on my phone. I have a weird audio bug with audio message. Only latest stock was stable... Hope we got official soon and it's upgradable from this version because I don't want to configure again haha
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Yup, agree....after trying so many unofficial ROMs, I went back to stock Q and it's still the best. Without getting latest security update, but I can live with it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] d0u8l3m:
I'm running unofficial 17 on my s4...the official one only recently came out and I haven't had time to bother updating it. So yeah I still stand by my statement. Things seemed much more organized and active during the cyanogenmod days. I don't get why either since architecturally these newer versions of android should be easier to create custom ROMs out of.

Hopefully with everything essential released these ROMS should be able to be just as stable as stock, but I'm a hardware engineer so idk really, hopefully the software guys can figure it out.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Don't know what happen, but I lost ssfenet again.. ? XD Fingerprint is already set on pixel 4.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lllGurulll:
Why does lineage install their own recovery program? I'd like to try other roms without having to go back to my PC to do it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Proof you don't read...

Recovery is in the kernel... It will always disappear when you flash a rom
[Essential Phone ROMs, Kernels, Recoveries, & Other] lllGurulll:
asked and answered. Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Welcome to A/B...

Now... Go read all of the information you haven't about how this works... Because if you're uninformed... You're gonna brick...

And I'm tired of "firehos wen"
[Essential Phone ROMs, Kernels, Recoveries, & Other] lllGurulll:
Dude, you are the reason that new people don't like coming to these forums. I've been doing this for years but it's been a year and a half since I've felt the need to flash. This was a new experience. It was an unexpected occurrance. Again, stop being an ass.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Whatever ... I'm not here to be your friend..

I am here ... To encourage you... Thru brow beating... To read before you go modding your phone ... So maybe you don't wind up like the hordes of people who didn't that have a ceramic and titanium paperweight

Edit: or 2
[Essential Phone ROMs, Kernels, Recoveries, & Other] lllGurulll:
Mine is already modded successfully thank you very much. Take your bullcrap elsewhere.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
I'll try not to be an ass but he's right. This phone has no recovery partition. The recovery system is integrated into the boot image, where the kernel lives. This isn't the only phone, either - I think Pixel 2 on are this way too and other newer devices. You'll know if there's a TWRP installer zip you need to flash along with TWRP - the installer integrates TWRP with the existing boot image.

Basically, you flash TWRP, your ROM, then the TWRP installer to keep TWRP. But if you flash anything that touches the boot image (such a a kernel or ROM that includes a kernel - aka any ROM), you'll lose TWRP. When you flash TWRP by itself, you replace the entire boot image with TWRP - you have no kernel. So flashing the ROM or at least a kernel afterwards is required.

I'm not sure how delta updates affect this yet. It shouldn't, especially if it doesn't update the kernel. But if there's a kernel change for some reason, I'm not familiar with what happens during delta updates.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lllGurulll:
Now that's a informative answer. Thank you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
LOS 17.1 official just released, but I can't find what vendor image is required... Anyone know? Or maybe it doesn't matter?
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Can I still use TWRP or I have to use LOS Recovery?

---------- Post added at 06:52 AM ---------- Previous post was at 06:44 AM ----------

So when new LOS update comes out, the best way to do is flash it over and then re-flash TWRP. Because if we use OTA then TWRP will be wiped....Am I correct?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
That's something I'm not certain about right now. An OTA should be a delta update, meaning it only updates what changed. In that case, it shouldn't affect the boot partition, where TWRP lives.

If the update includes a kernel change, it's entirely possible that you lose TWRP but I'm not certain or how likely that would be.

The other thing is LOS has their own recovery and they might push that every update - again, not sure.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
I've just tried to install it, but failed with using TWRP. After reboot, the phone boots back to bootloader.

I tried to use LOS recovery, but sideload didn't work for me.

(btw, I started with Jan stock rom)

Any tips are highly appreciated.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I was about to try it but I'm not sure anymore now. Just to be sure, did you follow the official site instructions?

1. Factory Reset,

2. Format data / factory reset,

3. Wipe System.

4. Return to the main menu and sideload.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
I failed at step 4

I couldn't do sideload.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Snowbird04:
I'm having issues installing the official as well. I was running Paranoid but went back to the January stock build (using the fastboot method from the Essential website).

I then sideload the Lineage recovery onto slot_a, and boot to the recovery. I can Format data/factory reset, but when I try to format system partition, I get the error:

E:/system/bin/mke2fs failed with status 1

E:format_volume: Failed to make ext4 on /dev/block/platform/soc/1da40000.ufshc/by-name/system_a: No such file or directory

System wipe failed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
What is the error you are getting?
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Sorry that I didn't record it, but something about not getting through.

I'm gonna wait for fews more week to try again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] anonxlg:
Is lineage 17.1's notch setting the same as the previous lineage 16?

I moved back to official android 10 because lineage's 'disabled' notch settings didn't work quite right. Not sure how else to explain it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Anyone has had some success doing a fresh install of the 4/29 official 17.1 build?
[Essential Phone ROMs, Kernels, Recoveries, & Other] slayerdiabolus:
Looking for instructions on going from UNOFFICIAL 17.1 -> OFFICIAL

Assuming it will be:

Reboot -> TWRP

Delete DATA

Run OFFICIAL installer

Run TWRP installer

Reboot to TWRP

Install Magisk

Anyone have any insight?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Snowbird04:
I was able to get Official 17.1 installed but through TWRP (using the January stock Essential ROM). After that, it gets screwy. Unable to install Gapps (constant errors / cant get back into recovery it just keeps going to bootloader).

This is a very glitchy experience.
[Essential Phone ROMs, Kernels, Recoveries, & Other] droidian5:
Weird it won't install with twrp. I would wipe everything with fastboot -w and then re-install twrp and go on from there. Forget about persistent twrp as LOS has its own recovery. Here's the official method from Lineage for mata..

https://wiki.lineageos.org/devices/mata/upgrade
[Essential Phone ROMs, Kernels, Recoveries, & Other] Snowbird04:
Ya this method just doesn't work. The Lineage recovery isn't great.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
So I was able to install the official build following most of the steps from the website. The only thing I had to do different was using TWRP to flash Gapps.

I did get a message when sideloading the ROM but it wasn't actually an error. When I looked at the very bottom, it said "no error". So I proceeded to flash Gapps with LOS recovery and that does not seem to work. However, switching to TWRP gets Gapps through and the ROM boots fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Thanks for sharing....I hope someones write up the full procedure of how to install this ROM, it's so confusing.

(btw, I'm back to PA and it's good now)
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
What order did you do this in? Flash rom via adb, then flash twrp via adb, then reboot into recovery and flash gapps? Which twrp? Did it have touch?

And, were you coming from Jan or Feb stock?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Every time I tried TWRP, it wouldn't boot to TWRP... Just kept going to the bootloader. Which TWRP and what steps got you to boot TWRP?
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I came off PA Quartz release. But I don't think it matters that much. I think as long as you have a ROM that plays well with TWRP, i.e. not the stock Feb release on both slots to begin with, you can follow these steps to get it to work.

1. Follow the steps on Lineage website up until after you flash the ROM. You will get an error when wiping system. You can ignore and move on. You will get a message when sideloading ROM, but if at the end it says "no error", you're good to go, so move on.

2. For flashing Gapps, do the following:

a) reboot to bootloader.

b) check the slot you are in and switch to the other slot.

c) flash TWRP image and boot to TWRP. That should be the slot opposite of where los was flashed.

d) use Adb push to send your Gapps zip, etc to your phone

e) from TWRP, switch the slot you were in step b and flash Gapps and anything else you want. You won't have touch. Use a otg cable to connect a mouse and use the mouse (nice trick I learned from someone on xda).

f) reboot system.

Let me know how that works for you.

---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------

The battery drain was killing me so I thought I'd try something else. But I've heard that a clean install fixed it up so I might go back.
[Essential Phone ROMs, Kernels, Recoveries, & Other] zombiepower:
I flashed TWRP with no error but couldn't get in TWRP. It keeps taking me to bootloader.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
I did clean flash (really clean by wipe EVERYTHING), and I see no more battery drop. I charged 90% at 9:00pm and by 6:00am it's 85%)

Some ppl in Telegram shared their tips of flashing PA, they said "flash Jan stock twice before PA rom", but I didn't try because I'm ok with it for now.

---------- Post added at 08:50 AM ---------- Previous post was at 08:43 AM ----------

I just want to share my experience about flashing LOS 16 with TWRP, I didn't try with LOS 17.1 yet, but maybe it'll work.

Here's what I've seen (and don't understand why)

To make TWRP works with LOS after flashing it, the initial ROM in phone must be custom rom, if I start with stock ROM, it never works for me

So, before flashing LOS:

- Flash any custom ROM

- Transfer LOS rom + TWRP installer + Gapps to phone

- Boot to bootloader and flash TWRP image (no touch now, I got to use OTG dongle + mouse to operate at this point)

- Boot to TWRP recovery and wipe everything except internal storage

- Flash LOS rom (LOS 16)

- Flash TWRP installer

- Boot back to TWRP recovery

- Flash Gapps

- Reboot

- Done

Again this is what I got success with LOS 16
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
I doubt that will work. I tried that method, minus starting from a custom ROM, and it just didn't work. I started from Jan stock Essential. Everything is fine until you flash LOS17.1 - Once you do that, TWRP will not boot after you flash it, no matter what.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Try switching to the other slot after you flash the TWRP image. I'm trying to go off memory of what I did but no doubt I remember having to switch slot to get TWRP to boot. Just not sure if it was before or after flashing the image.

At this point, if try to boot, it would, albeit without Gapps. That's the last thing you need to figure out and you need TWRP for that. No matter which package I tried in Los recovery, it would error out.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I just tried again and I can confirm that these steps work:

1. Start with TWRP on both slots.

2. Boot TWRP.

3. Switch to the other slot and wipe dalvik, system and cache.

4. Switch back to the original slot and flash LOS. It will install in the slot you wiped in step 3.

5. Reboot to recovery. It will boot LOS recovery given that this is now the active slot. Go in the advanced option and reboot to the bootloader

6. Switch slot and reboot to recovery. This will be TWRP recovery.

7. Switch slot in TWRP and flash Gapps, Magisk, etc.

8. Reboot to system.

9. Done
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
So at the end, we'll have two slots with different recovery?
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Yep.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
When weekly update arrives, will our TWRP slot still remain or be overwritten?
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Android Auto and File transfer still appears to be broken on this build. Not many options for fonts and safety net fails. Magisk 20.4 did not stick for me even though it flashed successfully in TWRP. I did not spend too much time trying to get to the bottom of that given that the lack of Android Auto makes it a no-go for me at the moment. Otherwise, it's pretty smooth and definitely looking forward to these kinks being resolved.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Thank you for your update.

Of course, no root is no go for me as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
I patched the boot image for LOS 17.1 with Magisk and shared in the thread on Reddit. Just flash that from the bootloader with fastboot and you'll be rooted.

Also, just got word they're fixing lineage recovery in the next build so at least open gapps will flash without error. Hopefully Magisk too so it's easier for others
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Sweet! I might give that a try. Any words on File transfer?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Still no MTP file transfer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
I'll probably wait a little while longer to see if this gets fixed. Can you share the link where you posted the patched boot? I went on Reddit but can't seem to locate it. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Here https://www.reddit.com/r/essential/comments/gabboj/official_lineageos_171_has_arrived_for_the_ph1

But next release of LOS is supposed to have recovery fixed to flash zips properly. Shouldn't need the patched boot anymore
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
How do you like the battery life on this new LOS compare to stock Q ? Is it better or the same?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Hard to tell. Maybe same
[Essential Phone ROMs, Kernels, Recoveries, & Other] zombiepower:
Success with L16 recovery. We may need updated TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Absolutely we need an updated TWRP. It hasn't been updated in 2 years and Essential has made significant changes since then, especially with their last update. Hell, TWRP can't even decrypt our phone.

Problem is, majority of users respond "it works as it is" when no, it really doesn't or they link to a blog talking about how difficult it will be to build for Android 10, which may be true but it's a dated blog post and that challenge may have been overcome - all of that may not even apply to this phone.

But most importantly, we have no active maintainer. Whoever is listed as maintainer has done nothing in 2 years - ya know, way before Android 10 release that's so challenging. So someone has to step up and take it over
[Essential Phone ROMs, Kernels, Recoveries, & Other] Randal84:
Yep.. welcome to the new way of flashing Android devices. A/B partitioning is the new way Google is doing things.

Basically anytime you flash a new rom/ update the current rom, it is placed into the opposite partition. Because of this, you are REQUIRED to reflash TWRP

EVERY. SINGLE. TIME.

There are instructions posted as to how to do this but yes, like it or not this is what Google has been doing since.. I'd say the Pixel 2, and onward and this phone is included as, I'm sure nearly every other Android device on the market.

Take the time to figure it out, not too hard...more of an inconvenience if anything as it's another step when installing a custom rom/ side loading an update. If you forget your screwed...better get the computer out and get ADB up and running again. Again once you figure out how to do it it's super easy...just more of an inconvenience/ an extra step, than anything.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Waancho:
We should put a bounty on it. That'll get people going.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Is this real ????

https://www.zdnet.com/article/hackers-breach-lineageos-servers-via-unpatched-vulnerability/
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Yes, but they claim it was detected before any damage could be done and they put their servers offline to prevent any continued"damage." Also they verified nothing regarding their ROMs have been manipulated.

So far, nothing to worry about, but they claim they're thoroughly investigating.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
Thanks! This saved me a lot of work to re-setup my phone after a dirty flash of LineageOS 17.1 over LineageOS 16.0 w/o wiping my data.

Thumbs up! :good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] R2D2_SW:
Glad I could help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Someone did try los17. 1 official? I did a dirty flash over this unofficial... Not sure it goes well, was difficult to have gapps installed... Still don't have luck with twrp and magisk on both. Same USB transfer file bug... Everything else looks fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Yes, there are issues with Lineage recovery installing gapps. Some have flashed lineage recovery from LOS 16 and was able to flash zips just fine.