Search results

I'm aware of the bug but never investigated. the commit you mentioned was merged in lineage a month earlier than PA https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/271420

because of system-as-root, it's indeed a corner case bug.

I'm not sure but the possible workaround might be: wipe system leave system empty and reboot twrp restore your pie backup

I'm pretty unsure but the margin between 16 and the test build is probably because the test build doesn't ship any network location provider. I guess the new gnss stack is not fully compatible with our qmi stack, but they're both proprietary software so god knows if this could be the root cause.

twrp 3.4 names both sar and non-sar system backups as system.* so you can backup/restore both types, system_root.* was produced by my unofficial sar twrp and is no longer supported, you have to rename manually to be able to restore on twrp 3.4

Did you wipe data when downgrading?

can you evaluate if this build has comparable performance with 16.0, I rolled back to the old gps stack https://androidfilehost.com/?fid=8889791610682878968 my result with this build is as follows, using "gps test" app. 1. get 3d fix right after launch the app 2. clear agps with "clear only"...

gps_debug.conf is used by android framework while gps.conf is for the gnss hal. https://github.com/LineageOS/android_frameworks_base/blob/lineage-17.1/services/core/java/com/android/server/location/gps_debug.conf is basically all valid items of gps_debug.conf along with the default values...

Yes, I've updated the state in OP. The major advantages are: fbe warning is gone bootloop after automated ota upgrade when encrypted and magisk installed should be fixed auto detect sar and non-sar (need restart after change, non-sar by default, i.e. empty system partition)

nvertigo67 BillGoss https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/279070 adds back xtra servers, they're relocated since https://github.com/LineageOS/android_frameworks_base/commit/19b214dd7339d75ad889d30bbb25f548d01bef22 , please test if it helps, lemme know if you...

So...is SatStat the only thing made the difference on 17 in your experiments? I think the conclusion is incorrect because it couldn't be possible

will be fixed with the next release (probably official nightly), as a temp workaround you can encrypt on other working roms and switch over

Works fine for me, can you provide logs? -------- UPD: it crashes when reading some cards, I'll investigate later, thanks for your report!

LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. #include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked...

Nice to know that nfc pay is working now. Apps are out of my scope, you may consider open an issue on gitlab. For TWRP, the SAR backup/restore fix was merged earlier, along with a fix for OTA bootloop when encrypted. I may consider updating the official build when I'm able to fully test it.

it doesn't hurt, the .mk one is just a placeholder and expected to be overridden by the .cpp one ------------------------- all 17.1 builds were removed because /system can't be mounted rw on some devices after flash due to signing, not sure if op3 is affected but still got removed.

TWRP is still recommended, lineage recovery does NOT support FDE thus you might encounter problems when installing magisk and opengapps

yes

gapps continuously crash, you probably forgot to wipe data after installation or whatever

#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM...

it's expected

file corrupted during upload, should be fine this time.

Indeed, I just fixed it and the download link is updated.

Unable to locate '/system' partition for backup calculations. I guess you should replace /system with /system_root from your scripts. Old backups are not compatible with system-as-root recovery as well.

This is caused by selinux, I just built a new TWRP with system-as-root to address the issue, check op for download link.

ofc, upload and I'll merge

this won't work, must disable on boot. repack boot.img or use some magic magisk modules (if any?) ----------- EDIT: instead of disabling selinux, add this line to /vendor/etc/init/hw/init.qcom.rc and it should work after reboot.

Confirmed, and I already have a fix locally. Just temp disable selinux before getting the next update.

Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure. NFC works fine for me, it wound be nice if you could grab related logs.

Can you provide more info such as logs, my aptx headset works fine here.

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device. #include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked...

Well, right now we don't have better solution, so...push it and I'll merge. btw we don't really need VENDOR_SECURITY_PATCH so drop it while you're at it

apparently they don't wanna keep taking care of an old device, the "fix" they promised is a ghost

I got leaked BSP source

NEVER

Latest official TWRP works with locked bl. Also I'm curious about why you were unable to boot to the system.

Notification on firmware migration It's been several months since OP released official Pie. Despite the infamous data corruption issue with unlocked BL, there's no evidence they'll gaf. Now that OOS "stable" is released, there's no reason to keep waiting for them to fix their firmware, and most...

Will be included in the upcoming TWRP 3.3.1

#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM...

No logs, no idea:\

Yes, and -0 has the fix as well.

No, it's according to fstab, so footer is always reserved on userdata.

Good news (maybe), after communicating with oneplus stuff they promised fw upgrading with unlocked bl will be fixed in future builds.

backup "system image" as a workaround, it works. I'm still not clear what goes crazy after restoring a system backup as I'm unable to capture useful logs so far. ---EDIT: The root cause of the issue is /system isn't assigned with a valid selinux context after mke2fs, I'll investigate later...

Exactly, busybox is dropped from omni9.0 based TWRP

Clear password before locking

New official TWRP is out with several bug fixes merged so it became recommended again, for details check https://forum.xda-developers.com/showpost.php?p=79351842&postcount=565 You can relock bootloader after flashing the new TWRP 3.3-1 as it's signed now, any ROMs(including latest lineage) with...

What I care about most is, TWRP 3.3 (both -0 and -1) has my crypto footer fix merged, i.e., you're able to encrypt data after format with official TWRP 3.3 thus my custom build is no longer needed and suggested. The new -1 version is build against 9.0 tree, added the new reboot edl button (you...

Magisk modifies boot and resigns it with testkey which is different from verity key so there'll be a 5s warning on boot when bootloader locked, it still boots. TWRP needs to be signed as well.

A warning on leaked Pie builds As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I...