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

[OFFICIAL] LineageOS 18.1 for the Essential Phone

Search This thread

malerocks

Senior Member
Mar 6, 2018
451
103
LineageOS only allows devices to ship one version at a time.

Mata is on the newest shipping version (18.1 as of this post). If you want a newer 17.1 image with newer security patch, just go build it, follow the wiki build guide and swap 17.1 for 18.1 where applicable.

Not sure why you would though. 18.1 is far better on Mata.
Sorry, yes that's what I meant. I was trying to point out to the person that raised the query that updating 17.1 would be an unofficial build and maintainer may not have time for that.
 

qvd

Member
Nov 9, 2014
43
4
Sorry I don't follow this thread closely so I don't know how good the 18.1 vs 17.1 for mata. I have been using 17.1 since the day Essential decided to end software update. I'll give 18.1 a try. Thanks.
 

qvd

Member
Nov 9, 2014
43
4
Beside the WI-FI Display issue and MindTheGapps being the only supported GApps package listed in first post, is there any other issue I need to be aware of?
 

qvd

Member
Nov 9, 2014
43
4
Chromium-based browsers will crash (at least they have for a lot of us .. myself included) frequently to the point of not being usable ... Firefox / FOSS browser work fine though
Thanks. I use DuckDuckGo most of the time so that's not a deal breaker for me. But I'll report back if it crashes.
 

MuddyDog

Member
Sep 3, 2019
45
24
Hi npjohnson, the ongoing weekly releases of 18.1 have been great (particularly keeping the kernel up to date). The one issue that (for me) blocks 18.1 from being useful as a daily driver is that VoLTE doesn't work correctly. It is enabled and *#4636#* shows that it is Provisioned, Registered, and Available, however in-call audio either fails completely or "chipmunks".
Anay Wadhera says that this may be an issue when using t-mobile... (an audio encoding issue)?
My workaround has been to use Andy Yan's 18.1 GSI, which is built using phhusson's treble base. In Andy's builds (and all of the phhusson variants) VoLTE works correctly; hd audio is clear and very stable.
Can this be fixed in the Lineage builds? I could generate log files from GSI and Lineage 18.1 if helpful.
 
Last edited:

Pendragonx315

Member
Jun 11, 2018
10
0
Essential Phone
Hi npjohnson, the ongoing weekly releases of 18.1 have been great (particularly keeping the kernel up to date). The one issue that (for me) blocks 18.1 from being useful as a daily driver is that VoLTE doesn't work correctly. It is enabled and *#4636#* shows that it is Provisioned, Registered, and Available, however in-call audio either fails completely or "chipmunks".
Anay Wadhera says that this may be an issue when using t-mobile... (an audio encoding issue)?
My workaround has been to use Andy Yan's 18.1 GSI, which is built using phhusson's treble base. In Andy's builds (and all of the phhusson variants) VoLTE works correctly; hd audio is clear and very stable.
Can this be fixed in the Lineage builds? I could generate log files from GSI and Lineage 18.1 if helpful.

I'm on T-mobile as well, and my VoLTE does seem to be working ... I do occasionally get the 'chipmunk' audio ... The workaround I've found is to switch audio devices (i.e. switch to bluetooth headest, switch to speakerphone, etc) somehow that seems to "fix" the problem and the audio goes back to normal... Not sure if that will help you?
 

Pendragonx315

Member
Jun 11, 2018
10
0
Essential Phone
I still can't recreate this.
I just did some looking and fascinatingly a lot of the browsers that use Gecko\WebView engines seem to work just fine

Firefox
IceRaven
Bromite
DuckDuckGo Browser
Privacy Browser (uses a new 'GeckoView' engine?)
FOSS Browser

these all seem to work
yet anything that uses the Blink engine seems to crash for me

Chromium
Vivaldi / Vivaldi Snapshot
Brave

I wonder if I can enable debugging and get a log of the crashes ...hmmm
 

malerocks

Senior Member
Mar 6, 2018
451
103
I just did some looking and fascinatingly a lot of the browsers that use Gecko\WebView engines seem to work just fine

Firefox
IceRaven
Bromite
DuckDuckGo Browser
Privacy Browser (uses a new 'GeckoView' engine?)
FOSS Browser

these all seem to work
yet anything that uses the Blink engine seems to crash for me

Chromium
Vivaldi / Vivaldi Snapshot
Brave

I wonder if I can enable debugging and get a log of the crashes ...hmmm
What about apps that use webview to load their content?
 

Spey

Senior Member
Nov 9, 2007
51
7
Two questions:

1) Does a PH-1 running Android-10 with Feb 2020 Security Patch (10 QQ1A.200105.032) need to be downgraded (previous to Feb 2020) to install LOS 18.1 ?

(I remember some time back, downgrade was required but see no mention of this in LOS Wiki Install Guide.)

2) Also have PH-1's that were not updated past Android-8 (have NOT yet taken Build PQ1A.19105.112), and wondering if anything other than LOS Wiki Install Guide instructions need to be done to load LOS 18.1 ?
 

npjohnson

Recognized Developer
Two questions:

1) Does a PH-1 running Android-10 with Feb 2020 Security Patch (10 QQ1A.200105.032) need to be downgraded (previous to Feb 2020) to install LOS 18.1 ?

(I remember some time back, downgrade was required but see no mention of this in LOS Wiki Install Guide.)

2) Also have PH-1's that were not updated past Android-8 (have NOT yet taken Build PQ1A.19105.112), and wondering if anything other than LOS Wiki Install Guide instructions need to be done to load LOS 18.1 ?
To all of the above, we include firmware - just boot recovery and flash the ROM.
 

Der-Knuffi

Senior Member
Jul 23, 2012
958
212
OnePlus 3
Samsung Galaxy A71
I have updated from official 17.1 to 18.1. A clean install was needed.

The chrome freeze means I can only use the LOS browser for now. This freeze also occurs with Vivaldi browser.

Magisk installed without issue via LOS recovery update (I renamed the .apk to .zip).

If the browser freezes can be addressed, it looks like this will be a solid ROM.
I have the same freeze problem. Did you find a solution? I'm on a oneplus 3.
 

IronRoo

Senior Member
Aug 4, 2014
1,354
435
@npjohnson A big thanks for maintaining this ROM, much appreciated.

I do have 2 bugs though on my install

1) Network status shows as "no internet" as the signal strength indicator has a little cross on BOTTOM RIGHT of bars, but internet still works except for Google Assistant (which I only ever use with Android Auto). I've checked my providers APN settings, tried their alternative APN, that automatically update when inserting SIM. All correct., everthing blank except
Name
VF WEB​
APN
live.vodafone.com​
MCC
505​
MNC
3​
APN Type
default​

2) Phone defaulted to "GLOBAL" for network type, calls & internet worked. However it only ever showed LTE never LTE+ (I live in an area where it used to regularly switch between the two) (Now that i type that I have a feeling Lineage/newer OS dropped the +?) So I switched it to LTE only (having read in the OSOM article that the weak signal reported with our phones was due to having Japanese network specs & transmitter, so wondered if switching off Global might give stronger signal as stopped Japanese bandwidths) but this resulted in being unable to place/recieve calls, data still worked. So went back to Global which works fine.

Anyone else with either of these issues?

PS. To anyone else thinking of installing I suggest you do, it was my first time using ADB/fastboot, having only ever flashed Samsung phones in the past & I was worried about the A/B partitions but no need to have worried. (only thing I did a little differently from Lineage instructions was that I just dragged files to be flashed into ADB/Fastboot window so the full path was used)

Thanks again for this great ROM, especially like the Essential camera being included as it gives most natural colours, I think, though have installed GCam port for when light is low.
 

npjohnson

Recognized Developer
@npjohnson A big thanks for maintaining this ROM, much appreciated.

I do have 2 bugs though on my install

1) Network status shows as "no internet" as the signal strength indicator has a little cross on BOTTOM RIGHT of bars, but internet still works except for Google Assistant (which I only ever use with Android Auto). I've checked my providers APN settings, tried their alternative APN, that automatically update when inserting SIM. All correct., everthing blank except
Name
VF WEB​
APN
live.vodafone.com​
MCC
505​
MNC
3​
APN Type
default​

2) Phone defaulted to "GLOBAL" for network type, calls & internet worked. However it only ever showed LTE never LTE+ (I live in an area where it used to regularly switch between the two) (Now that i type that I have a feeling Lineage/newer OS dropped the +?) So I switched it to LTE only (having read in the OSOM article that the weak signal reported with our phones was due to having Japanese network specs & transmitter, so wondered if switching off Global might give stronger signal as stopped Japanese bandwidths) but this resulted in being unable to place/recieve calls, data still worked. So went back to Global which works fine.

Anyone else with either of these issues?

PS. To anyone else thinking of installing I suggest you do, it was my first time using ADB/fastboot, having only ever flashed Samsung phones in the past & I was worried about the A/B partitions but no need to have worried. (only thing I did a little differently from Lineage instructions was that I just dragged files to be flashed into ADB/Fastboot window so the full path was used)

Thanks again for this great ROM, especially like the Essential camera being included as it gives most natural colours, I think, though have installed GCam port for when light is low.

So, your APN is correct? That's odd.

Also, LTE+, yeah that's mostly marketing fluff from carriers, you're still connecting to that band wherever you used to. Just doesn't differentiate the icon.
 

brochacholibre

New member
Jan 5, 2022
1
0
I have encountered a really strange issue and I'm hoping one of you guys may be able to shed some light on it. I recently picked up an open box unused unit which came bone-stock with an older stock build, Android 8. It seems to be as from-scratch as one can possibly get here. I intended to use Lineage 18.1 on it, so I followed the following steps:

- Dev options > OEM Unlock > Reboot fastboot > fastboot flashing unlock
- Once unlocked and wiped I booted right back into the bootloader and flashed QQ1A.200105.032 (Feb 2020) with the flashall.sh script
- Once flashed I booted right back into bootloader and flashed lineage recovery
- Rebooted recovery
- ADB'd Lineage img
- Rebooted system
- System boots but refuses to detect SIM card. When a SIM is inserted, the phone soft reboots immediately and sends me to a recovery prompt. Paraphrasing, "Android couldn't start. Factory reset?"

I managed to (I think) solve the issue and I now have my SIM (Verizon) working by doing the following after the above:

- Reboot recovery
- Flash QQ1A.200105.007 (Jan 2020)
- Rebooted straight into bootloader
- Flashed recovery, rebooted recovery, flashed Lineage img, rebooted system

My question after all of the above is this: The device functions perfectly now, and I think I solved the issue. Is there a compatibility issue with the Feb build even though the Lineage img flashes all relevant partitions anyway? Do I need to fastboot flashing unlock_critical and redo the January flash? Does a Lineage OTA flash all the partitions like initial installation through fastboot or just boot/system etc?

I'm glad my phone is working, but I'm worried there's a firmware mismatch somewhere along the line and I don't want to encounter the issue again after an OTA.

Unrelated, but after reading the whole post chain: I have used and loved this ROM on my old PH-1 for quite some time and I love it. A big thanks to the devs and the maintainer(s) for their hard work!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    lineage-os-logo.png

    Essential Phone

    Code:
    - 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 Essential Phone.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Wi-Fi Display - won't be fixed most likely - there are no 11.0 msm8998/sdm660 proprietary binaries to use.
    • 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_essential_msm8998
    8
    Anyone else's gps unable to "go to/find my location"?
    Works in Google maps here....
    Hrm, I'm getting video playback issues. No sound and very slow playback. Allegedly it's firmware related. Anyone else experienced this?
    weird - can't replicate in youtube, file a bug ticket as per the wiki instructions please?
    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?
    uhhh - sounds like you need to wipe data - something sounds messed up.
    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
    Just follow the wiki guide and all will work fine.
    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.
    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
    Try crDroid, although not official but OP update regularly and the rom is stable, good enough for daily useage.
    please don't discuss other ROMs here - go elsewhere for that.
    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.
    please don't discuss other ROMs here - go elsewhere for that.
    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.
    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).
    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.
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
    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.
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
    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.
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
    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.
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

    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?
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
    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.
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
    5
    Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!

    Thanks mate! Appreciate you maintaining Lineage for our device
    4
    There's a bug ticket open for it, unsure what the cause is, but we know about it and are trying.
    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 :)
    4
    @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. :)
    There's a bug ticket open for it, unsure what the cause is, but we know about it and are trying.