[ROM][10][OFFICIAL] lineage-17.1 for Pixels (marlin/sailfish)

Search This thread

gverma1

Senior Member
Feb 7, 2012
902
287
New Delhi
I have tried the latest update available on the Play Store and the sensors continue to fail, at least after a few minutes. Something is still broken in the Google App.
But hadn't you said on 27 October that your sensors problem had got solved on its own! So are you saying that your problem is back!
Also, I guess latest version of Google app on Playstore is dated November 1. I guess you must have checked after installing that one.
 

ninorastaman

Member
Jan 10, 2015
15
16
But hadn't you said on 27 October that your sensors problem had got solved on its own! So are you saying that your problem is back!
Also, I guess latest version of Google app on Playstore is dated November 1. I guess you must have checked after installing that one.
Yes and that's how it was when I wrote it; the sensors worked fine for a while without me doing anything. But the problem came back and so I read on the forum that the Google App was the problem.
Yes, I tried the November 1 update you mention and it kept crashing. For now I uninstalled the updates and disabled the automatic Google App update and everything works fine. I think we have to wait for some solution yet, maybe server side.
 

blckbear

Senior Member
Feb 15, 2015
223
128
23
Montevideo
Moto G 2015
Huawei P8lite/P8 Lite
Hi guys! Here another affected by the sensors, none of them work (microphone and speaker yes).

In my case, I noticed that the sensors were failing a few days ago, but I did not care because it was not a constant failure. I was at LOS 17.1 in a September version, because until yesterday I hadn't updated to the latest version for a month. I also have Magisk. An app test confirmed the failure of the sensors.

So yesterday I updated to the latest version and for a few moments everything worked fine (with test app confirmed it), until I changed a setting of the status bar and suddenly everything stopped working. Weird or a fluke.

First, I tried clearing Dalvik cache from TWRP, but it didn't work. So, I went into Safe Mode and all the sensors are working smoothly. So I don't know where the problem is, I just know that it is software problem. After a few reboots, the sensors work for a few seconds and then fail again, checked. Will any background service be blocked?

I would not like to have to install LOS 17.1 again, it is boring, but especially since I have seen that in Safe Mode everything works fine. I do not know what to do. I have not found any problematic app either.

Thanks in advance!
Exact same thing happened to me but on my ArrowOS 10.0 build, I only got sensors working after a factory reset :(
Do you have GApps installed?

Edit: saw that disabling Google app made it work again, makes sense, I was thinking Google messed something but I couldn't trace it to the Google app
 

Dragon Kumera

Senior Member
Mar 14, 2019
335
116
Hi

I have the same problem.

After the latest update, I lost all sensors. Some notes:
- uninstalling magisk did not solve the problem;
- the sensors do work for for some time after a reboot.

Does anyone have a working older lineageos image that can upload? Thanks!
Mine been working fine for the build I was on before trying pixelexperience 11plus out.

If you still got the problem, I can let you know the build I got that worked.
 

Dragon Kumera

Senior Member
Mar 14, 2019
335
116
Sensors have been working for quite some time now. I am on 22Dec build with latest opengapps nano. Be sure to update latest Gapps while flashing LOS. All works.
Just reinstalled fresh lineage os latest build a week ago from scratch after flashing google stock everything.

Hoping all goes well. (not had phone on lately but it flashed and did boot)
 

houscpp2

Member
Jan 29, 2022
19
1
Hi razorloves
I am a new LineageOS fan from Hong Kong and this is my first time to flash rom
When I follow step 6 at Official website to install nano opengapps, the device shows that nano opengapps is too big and cannot install.

I also notice that you say ''Good News! I finally fixed the bug in the Updater that caused the missing nav bar. https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/285458 It affected all a/b devices that have small system partitions. So, it's safe to use nano opengapps again now.'' at Post #963

Is this my problem in doing some steps wrong? If not my problem, will this be fixed in the future, or the only way is to install pico opengapps?

My last question is that will I still be able to have unlimited google photo stroage upload from Pixel XL device?

I hope you can understand what I am talking about, sorry for not good at using English.

Many thanks.
 

gverma1

Senior Member
Feb 7, 2012
902
287
New Delhi
Hi razorloves
I am a new LineageOS fan from Hong Kong and this is my first time to flash rom
When I follow step 6 at Official website to install nano opengapps, the device shows that nano opengapps is too big and cannot install.

I also notice that you say ''Good News! I finally fixed the bug in the Updater that caused the missing nav bar. https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/285458 It affected all a/b devices that have small system partitions. So, it's safe to use nano opengapps again now.'' at Post #963

Is this my problem in doing some steps wrong? If not my problem, will this be fixed in the future, or the only way is to install pico opengapps?

My last question is that will I still be able to have unlimited google photo stroage upload from Pixel XL device?

I hope you can understand what I am talking about, sorry for not good at using English.

Many thanks.
Opengapps nano dated 26 Jan 2022 is large and doesn't fit. You could flash Pico or flash an older version of nano. I flashed 17 Dec 2021 nano as I had it readily available on phone, and it works fine with latest LOS17.1.
Yes, you will have unlimited photo/video storage using Google Photos app on your Pixel/XL.
 
  • Like
Reactions: razorloves

rauhut

Member
Apr 22, 2013
26
10
Bad Endbach
Hi all, I think I did something really stupid last night by updating Magisk from 23 to 24.1 (24100) when new version was offered. Unfortunately this broke NFC payment on Google pay somehow that was possible with MagiskHide so far. Despite having "Universal SafetyNet Fix", "MagiskHide Props Config" (tried both fingerprints of lstest versions 8 and 10 for Pixel XL), Zygisk enabled and gPay on denial list activation of NFC payment is blocked on Marlin (app opens but cannot activate contactless payment). Does anyone have Google Pay successfully running with NFC running on latest 17.1 build and new Magisk?
Update1: SafetyNet check is now passed according to YASNAC app but still no change on gPay NFC.

Update2: It appears that there was some hiccup in the first install, finally got it working after starting from scratch with
  • fresh installation of Magisk 24.1 (24100) on existing 17.1 build and Zygisk (Beta) enabled.
  • Magisk moduls "Universal SafetyNet Fix" (V2.2.1) installed and enabled (MagiskHide Props Config is installed as well but not active so I guess it's not needed).
  • DenyList enabled and forced, in DenyList activation for
    Google Pay (com.google.android.apps.walletnfcrel (but not *.premis_lifeboat)
    Google Play Services (only com.google.android.gms and com.google.android.gms.unstable but it was disabled again automatically?)
  • deleted cache and data for Google Pay app (manually granting permissions afterwards again) and Google Play Services in app settings.
  • reboot after almost every step mentioned (and I rebooted a lot).
I don't know if all is really required but it finally did the trick on my device, just returned from super market with three successful NFC payments. The deletion of app cache and data seems to be important, before doing or doing only for cache Google Pay denied any activation as first mentioned above while data deletion the previously used cards were remembered (via the Google account?) but had to go again through the verification process to be enabled. After it worked again as before.
(just wanted to share in case anyone else runs into this or to be prepared if I need to do clean install some day again :))
 
Last edited:

gverma1

Senior Member
Feb 7, 2012
902
287
New Delhi
Hi @razorloves - i know work on official LineageOS 17.1 has stopped. However, a lot of stuff was baked for Marlin on 16th Feb including Feb security update. This is visible in the changelog.
If one last build can be made including all these changes, it would be really great.
Long live Marlin (& Sailfish)!!!
 

razorloves

Senior Member
Sep 19, 2007
3,156
15,281
Miami
Google Nexus 5
Nexus 9
right, all official lineage 17.1 builds for all devices has come to an end.
see here.
we only ever support 2 versions at a time. and lineage 19 is about to start for some devices, so 17.1 had to be dropped.

lineage 18.1 on marlin/sailfish still has 2 major bugs. that's why it hasn't gone official.
ims doesn't work. (ims is volte, video calling, hd voice... stuff like that).
and "ok/hey google" doesn't work.
no one has figured out how to fix it.
so i will continue support with 17.1 and provide unofficial builds here. (y)
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
3,271
1,802
Google Pixel XL
right, all official lineage 17.1 builds for all devices has come to an end.
see here.
we only ever support 2 versions at a time. and lineage 19 is about to start, so 17.1 had to be dropped.

lineage 18.1 on marlin/sailfish still has 2 major bugs. that's why it hasn't gone official.
ims doesn't work. (ims is volte, video calling, hd voice... stuff like that).
and "ok/hey google" doesn't work.
no one has figured out how to fix it.
so i will continue support with 17.1 and provide unofficial builds here. (y)
Thanks for continuing to support the Pixel XL.
 
Last edited:
  • Like
Reactions: razorloves

wavedashdoc

Senior Member
Mar 9, 2011
1,018
1,757
right, all official lineage 17.1 builds for all devices has come to an end.
see here.
we only ever support 2 versions at a time. and lineage 19 is about to start for some devices, so 17.1 had to be dropped.

lineage 18.1 on marlin/sailfish still has 2 major bugs. that's why it hasn't gone official.
ims doesn't work. (ims is volte, video calling, hd voice... stuff like that).
and "ok/hey google" doesn't work.
no one has figured out how to fix it.
so i will continue support with 17.1 and provide unofficial builds here. (y)

As I've stated before, getting the IMS to work is the most time consuming trial and error process. However, has anyone tried to replace the marlin IMS with one from the Pixel 2, 3 or 4. That might work, but beyond that, I wouldn't waste the time or energy.
 

razorloves

Senior Member
Sep 19, 2007
3,156
15,281
Miami
Google Nexus 5
Nexus 9
here you go. with february security patches. :)

marlin rom zip: https://sourceforge.net/projects/razorloves-lineage/files/marlin/

sailfish rom zip: https://sourceforge.net/projects/razorloves-lineage/files/sailfish/


I added a kernel patch so that safetynet passes. No need for any other safetynet hacks or magisk or anything else. (y)

I suggest you have adb logcat setup and working with your device and pc, just in case something goes wrong during the update. And have adb root enabled in developer option.

Note: The following steps are written assuming you're using lineage recovery. The same can be done with twrp, but the wording might be a little different.

*Instructions*
To update from official 17.1 to my unofficial 17.1:
1. Go into recovery and install/sideload the rom zip.
-Note: when you do this you will see a prompt on the screen about the signature not matching. This is expected since my rom is not signed with same key as official. Select yes to continue.​
2. After a couple minutes the install/sideload will finish. If you don't have gapps or magisk installed, you're done so tap "Reboot system now". Otherwise, continue to next step.​
3. Tap "Advanced" then tap "Reboot to recovery".​
4. Install/sideload the gapps zip and/or magisk zip. Then you're done so tap "Reboot system now".​
 
Last edited:

vildevilde

Senior Member
Aug 6, 2014
223
59
here you go. with february security patches. :)

marlin rom zip: https://sourceforge.net/projects/razorloves-lineage/files/marlin/

sailfish rom zip: https://sourceforge.net/projects/razorloves-lineage/files/sailfish/


I added a kernel patch so that safetynet passes. No need for any other safetynet hacks or magisk or anything else. (y)

I suggest you have adb logcat setup and working with your device and pc, just in case something goes wrong during the update. And have adb root enabled in developer option.

Note: The following steps are written assuming you're using lineage recovery. The same can be done with twrp, but the wording might be a little different.

*Instructions*
To update from official 17.1 to my unofficial 17.1:
1. Go into recovery and install/sideload the rom zip.​
-Note: when you do this you will see a prompt on the screen about the signature not matching. This is expected since my rom is not signed with same key as official. Select yes to continue.​

2. After a couple minutes the install/sideload will finish. If you don't have gapps or magisk installed, you're done so tap "Reboot system now". Otherwise, continue to next step.​
3. Tap "Advanced" then tap "Reboot to recovery".​
4. Install/sideload the gapps zip and/or magisk zip. Then you're done so tap "Reboot system now".​
Excuse me for my little knowledge but will this wipe my phone or will it work as a "normal" update?
 

razorloves

Senior Member
Sep 19, 2007
3,156
15,281
Miami
Google Nexus 5
Nexus 9
has anyone tried to replace the marlin IMS with one from the Pixel 2, 3 or 4.
yeah, no luck

I created my own sailfish build a few weeks ago following the official Lineage instructions. Will any future changes you make to the Sailfish build or kernel be applied to my build process?
probably not

Excuse me for my little knowledge but will this wipe my phone or will it work as a "normal" update?
normal update
 
Last edited:
  • Like
Reactions: vildevilde

lentm

Senior Member
Dec 3, 2008
470
106
  • Like
Reactions: trisolaris

Top Liked Posts