[OFFICIAL] LineageOS 18.1 for the Essential Phone

Search This thread

npjohnson

Recognized Developer
  • 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!
     

    buckiller

    New member
    Feb 22, 2018
    1
    0
    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.
     

    moichman

    Member
    Sep 12, 2018
    25
    9
    @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. :)
     

    npjohnson

    Recognized Developer
  • @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.
     

    andypiznti

    Senior Member
    May 8, 2011
    81
    8
    If you read the instructions on the lineage website for the device, it's pretty clear
    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!
     
    Last edited:

    andypiznti

    Senior Member
    May 8, 2011
    81
    8
    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!
     
    Last edited:

    chanh2018

    Senior Member
    Jan 19, 2018
    483
    120
    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!
    I remember this issue is on and off in mata and not only happens in LOS but also in other roms as well.
     

    MuddyDog

    Member
    Sep 3, 2019
    22
    14
    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.
     

    andypiznti

    Senior Member
    May 8, 2011
    81
    8
    Hasn't ever happened to me, I'm on the 5th February vendor, what vendor are you guys on?
    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.
     

    gavinfernandes2012

    Senior Member
  • Nov 25, 2015
    392
    110
    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.
    Not sure then, a backup and a fresh install is probably your best option, if that fails then providing a logcat would probably help
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 1
      does anyone know what does and does not work on a sprint OEM Essential phone? will I enounter any issues using this as a daily driver?
      If you still have it carrier-locked, you might want to remove that lock before flashing anything else. you will need to replace the "modem files" iirc.. i did that years ago, so I can´t give you any more details. apart from that, a sprint ph1 is like any other ph1, I have a "sprint" unlocked and one "openam", both act the same
      1
      also, can I re-lock the bootloader after flashing lineage?
      From what I have read, it is not advisable to relock.
      1
      does anyone know what does and does not work on a sprint OEM Essential phone? will I enounter any issues using this as a daily driver?
      Mine is an old Sprint model! It it is carrier locked, you may want to undo that by following the thread about it elsewhere on XDA, but if it's already unlocked, it's good to go!
      also, can I re-lock the bootloader after flashing lineage?
      You can but not if you use gapps or modify system - I really would NOT advise it.
    • 12
      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.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone