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

[UNOFFICIAL][11] LineageOS 18.1 w/ microG patch for Pixel 4a (sunfish) (20210610)

Search This thread

roxy1712

Senior Member
May 31, 2012
50
5
Washington, DC
i think this is not lineage but default behavior now if there are to many icons they will not all show. Instead you see that little dot that i think should indicate that you have more icons that are not visible. Probably a workaround for the notches that have been introduced which reduce icon real estate.
Could be - I ended up moving the clock back to the left side and it's all good. You can change it to show more icons via GravityBox, but haven't tested it.

Here's another bug. If I make a call with mobile data disabled, it will not work if I turn it on during the call. The "x" will disappear from the signal strength icon, but there's no H+ icon next to it and no networks appear if you turn off the "Automatically select network" toggle.

Same thing will happen if I start a call with mobile data and then turn it off after the call starts. The mobile data will only work once the call is finished.
 

PeterCxy

Senior Member
Jul 15, 2013
296
859
Okay, micro sized bug report - I suspect it's LIneageOS in general as there's a few old bug reports from 16/17 that show similar problems. The status bar starts to get a little weird when you add icons or details. For example... I moved the clock to the right of the battery and started losing system icons that previously showed up when it was on the left side.
This is not a bug but a feature introduced by Google since Android 9 (I believe). Extra icons are collapsed into a single dot when there is not enough space.
 
  • Like
Reactions: roxy1712

PeterCxy

Senior Member
Jul 15, 2013
296
859
Could be - I ended up moving the clock back to the left side and it's all good. You can change it to show more icons via GravityBox, but haven't tested it.

Here's another bug. If I make a call with mobile data disabled, it will not work if I turn it on during the call. The "x" will disappear from the signal strength icon, but there's no H+ icon next to it and no networks appear if you turn off the "Automatically select network" toggle.

Same thing will happen if I start a call with mobile data and then turn it off after the call starts. The mobile data will only work once the call is finished.
Mobile data do not coexist with calls unless you have VoLTE support from your carrier.
 

roxy1712

Senior Member
May 31, 2012
50
5
Washington, DC
Mobile data do not coexist with calls unless you have VoLTE support from your carrier.
Mine should, the voice call is done over LTE and the data drops to 3G/HSPDA. It still works when I start a call with data enabled (e.g., can surf the web at 3G speed while connected to a call), but will not connect if I'm already on the call and enable mobile data whilst talking.

I could also see if I can set Tasker to auto turn on data when a call comes through in case I need to use data (suddenly reminded of that old commercial where it was a big deal for iPhones to that 😆), but yeah... not sure why it won't work.
 
Last edited:

Fung-i

Member
Aug 11, 2013
18
0
Thanks for this! Unpacked and installed first thing, seems to work so far. But how do I get the google/pixel camera app?

Edit: Oh, and what's the latest on TWRP? Is it not recommended to install TWRP with LOS?
 

claviger-pc

Member
Jan 14, 2021
12
3
  • Like
Reactions: Fung-i

Fung-i

Member
Aug 11, 2013
18
0
In previous versions of Lineage(/android?) there was an option to long press the back button to force close an app in the developer section, but I can't find it in this version. Was it removed? If so, are there any good options to bring that functionality back? Thanks.
 

claviger-pc

Member
Jan 14, 2021
12
3
In previous versions of Lineage(/android?) there was an option to long press the back button to force close an app in the developer section, but I can't find it in this version. Was it removed? If so, are there any good options to bring that functionality back? Thanks.
this is a topic a little beyond this build or even just the pixel or lineage, but tasker would be the best in my opinion. At the same time I have the impression that pressing the back button multiple times in a row will force close or bring up the unresponsive dialog
 
Anyone knows if its somehow possible to create color calibration profiles that can be switches with a widget or in some other easy way?
I find the screen needs to be darker and more red during night since the default night light is barely doing anything compared to my previous nexus 5x and at the moment im manually switching tye color calibration in the evening and in the morning and would like to simplify this process.
I'm pretty sure you van change the white balance of the live display modes in the display settings. It's been like that in past versions of lineage. But if that doesn't work for you, smartpack kernel manager has an option for it (and tons of other goodies!)
 

betacrypt

Senior Member
Jan 17, 2018
297
143
I've had some issues getting MicroG permissions fully working with this rom, specifically around allowing background location and sms permissions, also a persistent error notification with some apps that Google Play Services is not installed.

Basically you need to install MicroG from Magisk, disable it, manually install MicroG to properly allow permissions, then renable the Magisk module.

Here's what I did to resolve this in more detail:
  1. Root your phone with the latest Magisk.
  2. In Magisk, flash MicroG Revived and reboot.
  3. Open MicroG and enable as many permissions as possible. (Background location and SMS might not be allowed right now)
  4. Make a note of the MicroG version installed.
  5. In Magisk, disable the MicroG module (do not uninstall) and reboot.
  6. From your web browser, go to https://microg.org/download.html and only download the same version of Services Core that was installed from the Magisk module.
  7. After downloading, install MicroG Services Core. You should be able to allow background location and SMS permissions now.
  8. Open Magisk, and re-enable the MicroG Revived module.
  9. Reboot your system. MicroG should be installed and working correctly.
 
  • Like
Reactions: anthony.d

anthony.d

Member
Jan 7, 2021
5
0
I've had some issues getting MicroG permissions fully working with this rom, specifically around allowing background location and sms permissions, also a persistent error notification with some apps that Google Play Services is not installed.

Basically you need to install MicroG from Magisk, disable it, manually install MicroG to properly allow permissions, then renable the Magisk module.

Here's what I did to resolve this in more detail:
Thanks, that was helpful.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    Introduction

    This is my personal build of LineageOS 18.1 for Pixel 4a with the microG patches applied. If you do not want / need to use microG, it may be a better idea to use the official build available here: https://download.lineageos.org/sunfish. This build is exactly the same as the official build except for the microG patch.

    For discussion about the official build, please use the other thread instead: https://forum.xda-developers.com/t/rom-official-sunfish-lineageos-18-1.4255751/

    Installation

    Before installation, make sure your phone is updated to Android 11 firmware on both of the slots.

    Whether you are installing the ROM for the first time or updating the ROM, please make sure you reboot to recovery again after `adb sideload`-ing the ROM before installing add-ons such as Magisk and GAPPS.

    1. Download `boot-XXXX.img` (this contains the recovery needed for initial flashing)
    2. Download `lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip`
    3. Reboot your phone to fastboot mode
    4. Run `fastboot flash boot boot-XXXX.img` from your PC
    5. Reboot your phone into recovery mode (`fastboot reboot`, then press volume up immediately)
    6. Erase data
    7. Select Apply Update -> Apply Update from ADB
    8. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
    9. If you do not need to install any add-ons (e.g. Magisk or GAPPS), then just reboot into system
    10. Otherwise, if you do need to install add-ons, reboot into recovery again (this puts your phone into the recovery of the newly-installed system), then install the add-ons using sideload. If you want to use GAPPS, they must be installed here before you boot into system for the first time (this doesn't apply to microG).
    11. Enjoy

    Updating

    1. Download the newly released zip and reboot your phone into recovery
    2. Select Apply Update -> Apply Update from ADB
    3. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
    4. If you did not have any add-ons installed before update (e.g. Magisk or GAPPS), then just reboot into system
    5. Otherwise, if you did, you need to reboot into recovery again at this point before rebooting to system and re-flash every single one of the add-ons you had before. If you do not re-flash them before rebooting to the new system, the boot will fail and your phone will switch back to the old system automatically.
    6. Reboot and enjoy.

    Note: You don't need to update official firmware manually while LineageOS is installed by flashing latest official factory images. This LineageOS build now ships with latest official firmware updates which are tested to work with the ROM. Please avoid flashing the firmware manually while LineageOS is installed to avoid unnecessary issues.

    Known Issues

    - Use Magisk v21.4 or later if you want Magisk
    - Some applications require microG to be installed in system partition to function, in which case you can consider using the Magisk microG module
    - The eSIM manager only works with either GAPPS or microG installed. Without them, you can use eSIM, but you will not be able to add / remove / rename / disable your eSIM. The eSIM manager will also crash once or twice on first boot without GAPPS or microG, but after that it won't crash anymore (the system automatically disables it until you install microG or GMS)
    - Disabling / Enabling eSIM may hang even with GAPPS or microG. However, rebooting normally fixes the issue and makes your action effective.
    - I provide no guarantee for SafetyNet status or compatibility with any app that requires SafetyNet. Google has been tightening its SafetyNet verification and there is really not much we can do about it, and frankly most apps that require SafetyNet should not have done so in the first place. If you need SafetyNet, you are on your own.

    Downloads

    Note: This build has compatibility issues with MindTheGapps (just like the recent LineageOS weekly builds). It will be fixed in newer official weekly builds, but since this build is for microG users, I am not going to upload a new microG-patched build just to work around a GAPPS compatibility issue.
    20210610: June 05 security update; sorry for the delay, LineageOS had some issues while merging this month's ASB.
    This update also fixed some long-standing bugs, such as the initial crash dialog of the eSIM manager (when GAPPS or microG is not installed), and the extraneous battery percentage option in settings -> battery. Read the LineageOS changelog for the full update.
    - boot-20210610.img: https://mega.nz/file/TVolEYKL#MrJH-AVk37JDc_iKCVJ2lFGgFLG9czrE4FnJokbjnqI
    - lineage-18.1-20210610-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/uYw30SxT#CwWc0GwqMYoAT54TJqPK2U7M8Y3OzhbpPuvejkOB65o

    20210507: May 05 security patches
    - boot-20210507.img: https://mega.nz/file/rcJVHQYZ#KjFu84Wnqdx4Rq0fd6TZUlJuaD-RXFXmMCJM4V4z0Tc
    - lineage-18.1-20210507-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/jYBTESqZ#ZRc7CkUt8aUYgZRLpF6S1_LHdUXwcUOKPsCBorcYZ1w

    20210410: April 05 security patches
    - boot-20210410.img: https://mega.nz/file/eYggCKba#l7QJUMkvyEBtyptVMmWVbXochJKmY__X4VIwTla1KqE
    - lineage-18.1-20210410-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/bUpQhAQJ#uTe-2nHLKYsfFBKuJg0VAYISUCGMTbIpaC9qjEHFZ1c

    20210308: March 05 security patches and official firmware / binary updates.
    - boot-20210308.img: https://mega.nz/file/WIZxjAwA#P77ZdJ2YEed5WWmlijKcyRMLJ30KG36eL0mhQGjZWjI
    - lineage-18.1-20210308-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/eRBTkYzC#iNZUA84XR80V1so7YvjQ7TyJuZKGY9BZf-MGRtgQOH8

    20210222: Updated sources; Removed some non-functional LiveDisplay features; Switched to using Google's wifi_ext HAL; Reserved more space in system partitions for potentially larger GAPPS packages
    - boot-20210222.img: https://mega.nz/file/KVxRDY6L#7l7oejw-XEd_m1BUdp0_Z2TyHVLE2KkaGQ6g7Op7dpk
    - lineage-18.1-20210222-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/mUgzGSbC#88q95qVsI-7RJsecM8L2MHZ6EwNXrs54Xk6yi428rjU

    20210207: Updated LineageOS source; Applied 2021-02-05 security patches; Added support for glove mode; Enabled support property for Google Assistant; Optimized vibration
    - boot-20210207.img: https://mega.nz/file/aZxlDKgC#_9VR2ruCYUqmX8gLCBKX1KSMAsBYFDsLA6utk5EjB-g
    - lineage-18.1-20210207-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/yZpFQQRJ#PZlNYzI2t2fZdf1T3v6pMRi1zJe7J26f-Eu_Pohm7p4

    20200118: Updated LineageOS source; Attempted to fix GAPPS bootlooping issue
    - boot-20210118.img: https://mega.nz/file/ONYSRLKC#FhRYEhfsBndqcrJrhd1F4Tv3uu3UZNDYnQe3EcrMyC0
    - lineage-18.1-20210118-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/3VRgwZQQ#ynCPIDbW42hXvBWp8MoG-R9eEEzvnaQ649ULZM8lrAc

    20210109: Updated LineageOS sources and updated build fingerprint to January.
    - boot-20210109.img: https://mega.nz/file/qU5T2CLY#A7dkDfRS0gUaKzphT2_mm0IHW9_-3cIR76yvNV1Cs4A
    - lineage-18.1-20210109-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/GNwyxb4S#UGHclk8p60QuRWrGl3LI-Hur9X_VKF46tBNfuD0Z9-o

    20210107:
    1) Synchronized LineageOS updates and AOSP Jan 5 security patch
    2) The ROM now ships with latest official firmware, so you won't need to worry about updating firmware separately (you still need latest official firmware when installing the ROM for the first time though)
    - boot-20210107.img: https://mega.nz/file/OYRnwaII#3Ipj99mG5tpXouRRKMqWDJmimH8U2q5mZ5LKj8ZEmdo
    - lineage-18.1-20210107-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/aEBTFAwK#EM3fKYQG4Y2najLhRkZlPqDwPSwkV-yfsSlH7Za7UYM

    20201229: Synchronized LineageOS updates and fixed biometric authentication (fingerprint) in third-party applications.
    - boot-20201229.img: https://mega.nz/file/yMow3aDb#ByY4yG6LeAquqBd2vu2UnZUz2xukHYjWbIfXnlkT_XM
    - lineage-18.1-20201229-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SA5WDAZQ#fMRB9w4LLSxSAGxHOtEmN9gRBTmrnF8ozKawM34cIxU

    20201227:
    - boot-20201227.img: https://mega.nz/file/6cI3lKKK#p8Nq3jUOsOoPDeV6yPj4hQtXGIHu8-D54_g3gkzdi0w
    - lineage-18.1-20201227-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SdQnTaBa#83JjZojOS9JCRdYOng6Y0LLoUl8StAdrwsTbCSqAMhs

    Sources

    Device Tree: https://github.com/PeterCxy/android_device_google_sunfish
    Kernel: https://github.com/PeterCxy/android_kernel_google_sunfish

    Thanks: DirtyUnicorn sunfish contributors, SuperiorOS sunfish contributors, LineageOS coral contributors and the LineagOS community.
    12
    Updated to 20210222
    10
    Updated to 20210207 with fresh 2021-02-05 security patches. Also removed warnings about GAPPS because they should be working now.
    8
    Thanks for all your work! I am hesitating to switch from stock 11 for several reasons. One is whether we will be able to update from this build to an official one without wiping/reinstalling. Another is whether the build is completely stable and usable as a daily driver. Also, I am wondering about battery life and latency as compared to stock. I have found that on certain devices, Lineage was actually worse! Also, how are the opengapps working for people??

    Summary of questions:
    1. Stability?
    2. Battery?
    3. Is official coming soon and "guaranteed"?
    4. Can we seemlessly upgrade to official 18.1?
    5. Opengapps or other gapps working well?

    Thanks to everyone for any input!

    1 & 2: I've been daily driving this for quite a while and I don't think it's less stable than stock, and I don't think I've observed any more battery drain than stock. Of course this could be due to the fact that I don't install the full GAPPS and instead use microG.

    3: I am going to merge all my code into the LineageOS repository by the end of this week if no objections (I am already a maintainer of the official LineageOS repositories for Pixel 4a) and I will be submitting wiki entries & CI config for LineageOS 18.1 builds. I am not sure when LineageOS 18.1 will ship, but I expect it to ship with Pixel 4a builds, or in the worst case Pixel 4a builds will be up shortly after LineageOS 18.1 is shipped.

    4: No, you will not be able to. This ROM is signed with my own keys, and I have no access (nor should I have access) to the official LineageOS signing keys. It will not be compatible with official builds for this reason.

    5: As I don't use GAPPS myself, I'm not sure, but people in this thread have been successfully using GAPPS with this build for some time now. We at LineageOS have fixed the earlier issue causing GAPPS to break on new Pixel devices.
    6
    Updated to 20210107