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

[cyber180]

Hi, I'm another user affected by the sensors problem(no screen rotate, auto brightness or triple tap to wake are the major annoyances). Safe mode also works similarly to other previous comments. Sensors do not work on a fresh boot. I think the problem started with an update in mid-September.

However, I have found that if you switch to the guest user and back(sometimes twice is necessary), sensors start working again. But, it seems to only be temporary, requiring another guest switch to get the sensors working again. I'm thinking it might be related to deep sleep...

 

[wavedashdoc]

My gf is now experiencing the same rotation sensor loss on the first October 13th update. Tried rebooting and also switching to the guest account. GPS, Camera, Bluetooth, etc seem to be unaffected.

 

[astrod]

My gf is now experiencing the same rotation sensor loss on the first October 13th update. Tried rebooting and also switching to the guest account. GPS, Camera, Bluetooth, etc seem to be unaffected.

Huh, I can confirm that auto rotate no longer works for me too. I was the one who earlier said all sensors are working, so I guess I have to walk that back a bit. Using the Oct 16 update.

The devcheck app shows all sensors functional so this must be a bug in auto screen rotate itself...?

EDIT: apologies, I forgot I turned off screen rotate in my home screen. I just now confirmed that it is indeed working. So all sensors are functional.

 

[gverma1]

Huh, I can confirm that auto rotate no longer works for me too. I was the one who earlier said all sensors are working, so I guess I have to walk that back a bit. Using the Oct 16 update.

The devcheck app shows all sensors functional so this must be a bug in auto screen rotate itself...?

There's an app called Sensor Test which I use to test all the sensors like proximity, light, accelerometer, gyro, etc. You could use that to check. If screen rotation is gone for you then chances are there would be other failures too.

@razorloves - is there something that can be done for this sensors issue that came some time in September?

Also, no pressure, but will you be exploring A12 for Marlin?

 

[razorloves]

@razorloves - is there something that can be done for this sensors issue that came some time in September?

no sensor issues here, and i've been updating to every new build each week.
what's the last working build, or which build did the problem start on?
i need to see logs showing the problem.
really the only changes that were added in september were the monthly security patches from google (linked below). they were added on the 16th.

https://review.lineageos.org/q/topic:Q_asb_2021-09

 

[Noeljunior]

My gf is still using a build from 23/04/2020 (don't judge) and lost the rotation and light sensor. Proximity still works.
When I lost mine, I also experience something like that: not all sensors got lost at the same time.

I know more people with the same phone and I'll check with them later.

 

[ninorastaman]

Hi guys! I come to say that the sensors on my Pixel XL are working normally again and I did nothing to fix it. I'm still on LOS 17.1 (20211020 build). I hope it keeps working. Anyone else like me?

Edit: Just comment that a few days ago the mobile data disconnected by itself, without me touching anything (I don't even have the toggle set in the quick settings). I thought my Pixel was dying haha But I activated it and it didn't happen again.

 

[Talyrius]

I've searched through this thread rather extensively to see if there's been any discussion on how to resize the system partition and get those changes to persist through OTA updates. However, I haven't had much luck.

I know everyone recommends against doing so, but I want to install a larger selection of Open GApps. Even after pairing things down significantly with an exclude list (gapps-config.txt), there's just not enough free space available—or not enough to feel comfortable with, that is.

When I resize system_a and system_b, everything works just fine right up until the point I go to reboot after installing an OTA update. I tried using this 00-resizesystem.sh addon.d script, but it hasn't helped. Perhaps one of you may have some insight as to why?

 

[cyber180]

Hi, I'm another user affected by the sensors problem(no screen rotate, auto brightness or triple tap to wake are the major annoyances). Safe mode also works similarly to other previous comments. Sensors do not work on a fresh boot. I think the problem started with an update in mid-September.

However, I have found that if you switch to the guest user and back(sometimes twice is necessary), sensors start working again. But, it seems to only be temporary, requiring another guest switch to get the sensors working again. I'm thinking it might be related to deep sleep...

So I still haven't found a pattern that triggers the sensors to fail once I get them working again by switching users. Sometimes it'll break within a minute, sometimes it works overnight.

I've never heard of the pretty common sensors issue with Android 10 before, but I wonder if this is my problem, https://www.thecustomdroid.com/android-10-sensors-bug-fix-guide/.

I've had a quick look, and there was a cache directory (from twrp) inside my /persist partition - which I deleted, but that hasn't helped.

There are files in /persist, so it doesn't look corrupted to me, but I do note that the size of the files in the partition is less than 1MB. I found an image of persist partition from a pixel3 and it is much larger and has a sensors directory that my persist partition doesn't. Unfortunately I've never backed up my persist partition, so have no way to tell if mine is missing files or not.

Can anyone without the sensors problem tell me how much space is used by the files in their /persist partition? Even better, can anyone dump their persist partition so I can try to use it to see if it fixes the sensors problem?

 

[psaez84]

Hi, as i also have problems with the sensors, searching I reached this thread about sensors problems in Pixel XL (I dont use lineage but the sensors problem can be the same even not using lineage) and I registered only for posting here something I think can help you guys with your sensors problem. The problem is that a moderator has deleted my post just because in his opinion "your post is off-topic and didn't add any value to thread. Please don't spam the forum. Regards Oswald Boelcke, Moderator". I dont share the moderators opinion, not using lineage ok, but sensors problem present here too, and if I think this can help you, I must try it.

Please, if you wanna try a different solution that can help you with your sensors problem, check this:

https://xdaforums.com/t/pixel-xl-sensors-stopped-working-i-think-i-know-why.4354691/

Maybe the issue is not with lineage or with recover partition but simply with a recent google app update, which is probably present also in lineage.

And tell me if it helped you.

Grettings.

 

[cyber180]

Maybe the issue is not with lineage or with recover partition but simply with a recent google app update, which is probably present also in lineage.

As posted in your thread, I have disabled the google app and sensors work on boot. They break if I enable the google app. I don't use the google app, so will see how stable things are with it disabled.

Thanks for your post!

 

[wavedashdoc]

As posted in your thread, I have disabled the google app and sensors work on boot. They break if I enable the google app. I don't use the google app, so will see how stable things are with it disabled.

Thanks for your post!

Good find! This worked! I also found that the phones proximity and light sensors were also not working prior to disabling the Google app. @razorlove I will try and provide a log later today from boot.

 

[ninorastaman]

I can confirm that disabling the Google app solves the sensors error and is not related to LOS 17.1. I'll also post it in the thread created for this purpose. All the best!

 

[gverma1]

I can confirm that disabling the Google app solves the sensors error and is not related to LOS 17.1. I'll also post it in the thread created for this purpose. All the best!

I have latest Google app from Playstore on Los 18.1 and all sensors are working fine.
Maybe Google rectified the problem from back-end. Can you check on Los 17.1 with latest Google app enabled?

 

[nacimpalirmou]

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.

All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.


IMPORTANT NOTES:
1. If you use twrp it will ask if you want to install the twrp app. Make sure you tap "DO NOT INSTALL".
2. If you care about your stuff, make a backup in TWRP first, just in case. Transfer it to a pc, along with all your stuff in internal storage.
3. The newest vendor, radio, & bootloader img's are included in the rom zip, so no need to worry about flashing those manually.
4. Lineage comes with adb root that you can enable in developer options, but if you want root for apps, flash magisk in recovery (after renaming magisk.apk to magisk.zip). Just don't flash it during initial lineage install, as it's known to cause bootloop if you do.


Downloads:
marlin rom: https://download.lineageos.org/marlin

sailfish rom: https://download.lineageos.org/sailfish

gapps: (gapps are optional) link WARNING: Only use nano or pico because the system partition is too small on our device.
google fi gapps addon: if your carrier is Google Fi, flash this zip right after flashing the gapps zip. https://androidfilehost.com/?fid=8889791610682871038

Instructions:
FOR INITIAL INSTALL
marlin: https://wiki.lineageos.org/devices/marlin/install
sailfish: https://wiki.lineageos.org/devices/sailfish/install

FOR UPDATING
For normal updating from official 17.1 to a newer official 17.1, follow these steps:
marlin: https://wiki.lineageos.org/devices/marlin/update
sailfish: https://wiki.lineageos.org/devices/sailfish/update
Protip: Enable "Prioritize update process" in the Updater preferences to make it go faster
NOTE: If you're updating from my unofficial build to the official nightlies, follow steps here.

Alternative manual updating instructions:
1. boot into lineage recovery.
2. install rom zip.
3. if you use gapps or magisk, select the "reboot into recovery" option, then install those zips.

FOR UPGRADING (From official 16.0 to official 17.1, for example)
marlin: https://wiki.lineageos.org/devices/marlin/upgrade
sailfish: https://wiki.lineageos.org/devices/sailfish/upgrade



Changelog
marlin
sailfish


Bug reporting
https://wiki.lineageos.org/bugreport-howto.html


Source Code:
Marlin Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-17.1
Sailfish Device tree: https://github.com/LineageOS/android_device_google_sailfish/tree/lineage-17.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-17.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.1


Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:


Android version: 10
Kernel version: 3.18.137

Status: Nightly

does google photo unlimited storage go away when i flash this?

 

[gverma1]

does google photo unlimited storage go away when i flash this?

No. Unlimited storage stays. You just have to delete the file pixel_2018_exclusive.xml from /system/etc/sysconfig folder. This file gets created every time you flash gapps.

 

[nacimpalirmou]

No. Unlimited storage stays. You just have to delete the file pixel_2018_exclusive.xml from /system/etc/sysconfig folder. This file gets created every time you flash gapps.

thank you i'll see try it

 

[razorloves]

You just have to delete the file pixel_2018_exclusive.xml from /system/etc/sysconfig folder. This file gets created every time you flash gapps.

you don't have to do that anymore with new gapps.
i just fixed that recently: https://github.com/opengapps/opengapps/commit/d1db9bd
@nacimpalirmou

 

[Talyrius]

I've searched through this thread rather extensively to see if there's been any discussion on how to resize the system partition and get those changes to persist through OTA updates. However, I haven't had much luck.

I know everyone recommends against doing so, but I want to install a larger selection of Open GApps. Even after pairing things down significantly with an exclude list (gapps-config.txt), there's just not enough free space available—or not enough to feel comfortable with, that is.

When I resize system_a and system_b, everything works just fine right up until the point I go to reboot after installing an OTA update. I tried using this 00-resizesystem.sh addon.d script, but it hasn't helped. Perhaps one of you may have some insight as to why?

Is there anyway we can get the OTA updates to run e2fsck -yf <new system partition> and resize2fs <new system partition> after it's done flashing, but before it copies the GApps and any modifications over?

 

[ninorastaman]

I have latest Google app from Playstore on Los 18.1 and all sensors are working fine.
Maybe Google rectified the problem from back-end. Can you check on Los 17.1 with latest Google app enabled?

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.