[OFFICIAL] LineageOS 18.1 for the Essential Phone

Search This thread

npjohnson

Recognized Developer
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!
you're fine, we flash everything needed.
 

IronRoo

Senior Member
Aug 4, 2014
1,361
438
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.
It's working now, strangely.

I added "mms" settings for MMS as well (defaults from SIM/network are blank), there was no change.
Then I selected IPV6/IPV4 (SIM/netwrok default setting is just IPV4), still no change.
Gave up as everthing semed to be working (bar assistant.)
Then later i noticed the little cross bottom right of signal strength bars was gone!!! Can't explain it, maybe my changes triggered some setting at my network provider and it took a little while to roll out?
 

TDP95

Member
Mar 9, 2020
16
8
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.
My PH-1 also experiences the chipmunk audio when trying to make a call using VoLTE. I've tried installing LOS 18.1 with either the stock February 2020 or January 2020 OS's originally installed on the device, but the issue persists. I haven't found a solution except to disable VoLTE. My MVNO carrier is Ting and I'm using the T-Mobile network. It looks like others are having this issue too since LOS 17.1, https://forum.xda-developers.com/t/chipmunk-audio-on-los-17-1-essential-ph-1-t-mobile.4193983/ https://www.reddit.com/r/LineageOS/comments/l1r8ez https://www.reddit.com/r/LineageOS/comments/kwatpy
I noticed however this doesn't occur on the January 2020 stock OS when I tested it. The audio with VoLTE enabled works fine.

Has anyone found a solution to this issue? T-Mobile is going to require devices to support VoLTE very soon as they're killing off their 3G network.
 
  • Like
Reactions: Pendragonx315

malerocks

Senior Member
Mar 6, 2018
484
105
I reinstalled the ROM from scratch and now if I go into my Google account settings to check what it's syncing, Contacts doesn't even show up as an option (see screenshot). Any clues how do I fix this?

Will I have to remove the Google account and set it up again? Or worse, have to reset the phone?
 

Attachments

  • Screenshot_20220117-114501_Settings.png
    Screenshot_20220117-114501_Settings.png
    150.2 KB · Views: 18

malerocks

Senior Member
Mar 6, 2018
484
105
I reinstalled the ROM from scratch and now if I go into my Google account settings to check what it's syncing, Contacts doesn't even show up as an option (see screenshot). Any clues how do I fix this?

Will I have to remove the Google account and set it up again? Or worse, have to reset the phone?
In fact, contacts from my exchange account aren't syncing as well.
 

malerocks

Senior Member
Mar 6, 2018
484
105
My device is always uncertified with LOS from beginning (even in 17.1)
This is the first time I have installed the rom on the Essential phone. Previously I had it on a different device. That was always registered as certified from 17.1 onwards. I was even able to use Google pay. Can't seem to do on this one.
 

malerocks

Senior Member
Mar 6, 2018
484
105
Does anyone know if there is a way to keep phone vibration off when the alarm goes off? I am one of those that will snooze the alarm 5-6 times before I wake up and all that vibration ends up draining the battery unnecessarily. Phone vibrating when the alarm goes off is unnecessary IMO.
 

ziddey

Senior Member
Aug 26, 2007
1,829
1,573
Anyone have Widevine L1 support? From what I remember, it doesn't require the bootloader be locked on the PH1. Only seeing L3 here.
 

Pedro2NR

Senior Member
Sep 14, 2007
347
71
Los Angeles
Just installed nightly 18.1-20220124 with mind the gaps. I noticed my phone reboots randomly and boots into recovery stating: "Can't load Android System".
I select "try again" and it boots up but randomly happens.
Any suggestions?
 

chanh2018

Senior Member
Jan 19, 2018
510
130
Just installed nightly 18.1-20220124 with mind the gaps. I noticed my phone reboots randomly and boots into recovery stating: "Can't load Android System".
I select "try again" and it boots up but randomly happens.
Any suggestions?
Try fresh install from Jan stock rom and don't root. Let see if it happens again. Mine is ok no problem at all.
 

malerocks

Senior Member
Mar 6, 2018
484
105
Just installed nightly 18.1-20220124 with mind the gaps. I noticed my phone reboots randomly and boots into recovery stating: "Can't load Android System".
I select "try again" and it boots up but randomly happens.
Any suggestions?
I have the random reboots too. For me, it typically happens when I am in a location where the network keeps jumping between 3G/4G. Not sure why are facing the loading error though.
 

IronRoo

Senior Member
Aug 4, 2014
1,361
438
Does anyone know if there is a way to keep phone vibration off when the alarm goes off? I am one of those that will snooze the alarm 5-6 times before I wake up and all that vibration ends up draining the battery unnecessarily. Phone vibrating when the alarm goes off is unnecessary IMO.
can be set for each alarm when setting alarm up
 
  • Like
Reactions: malerocks

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hey, I'm having a problem installing the recovery file onto my phone. When I try to fastboot flash boot either to slot a or b, with the .img file, I get hit with

    Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 67108864).
    Sending 'boot_a' (65536 KB)

    and it either stops there indefinitely, or it eventually shows

    FAILED (Status read failed (Too many links))

    I've tried many different solutions. Different usb ports, different PCs, different .img files (like TWRP), and I've been having no luck, and I haven't seen anyone else who has the same problem as I. Any help would be tremendously appreciated.
    Try to go back to Jan stock rom and when flashing LOS recovery image, don't put slot (fastboot flash boot recovery.img)
    I followed LOS installation instruction closely, and it've never failed me.
    Hope it works for you. Good luck.
    1
    @npjohnson can I ask a question about the v19 of the LineageOS ROM for Mata (whenever that is, no rush)?
    Like you kept the essential camera in the ROM in v18.1, will you do the same for v19 as well? Thanks.
    Yes, it's already there.
  • 15
    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:
    • 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.