Search results

You can keep data while switching gapps. Might have to uninstall and reinstall some google apps but that's it.

18.1 builds are pretty stable at the moment, however there are issues with volte on sim slot 2 and missed calls on slot 1 on devices upgrading from old builds and we couldn't solve that yet. Clean installs work fine, but the whole point is to support flawless upgrades.

I might release some unofficial 18.1 builds for broader testing, I haven't had time to look into remaining issues yet.

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 * before...

It's an issue that will be fixed in next build. I will open a new thread for 18.1

Builds will be available once next weekly build cycle starts. https://review.lineageos.org/c/LineageOS/hudson/+/307434

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 * before...

Please stop arguing here, as @Kielbek said, FM radio has nothing to do with battery drain. Nothing was changed related to permissions (only thing changed is how user sees the permissions in the OS), it only uses the required permissions to work, it does not run in background. It's all open...

Yes, we are just waiting for some build infrastructure issues to be fixed for lineage 18.1 nightlies.

Vibration intensity has been reduced on lineage 18.1 codebase. It's pretty stable right now, just waiting for lineage build infrastructure to be set up for android 11 nightlies.

I finally made some progress, this took a long time of debugging...

Official TWRP is out of my control and as far as I know doesn't use the same kernel as lineage, so I cannot guarantee compatibility. For now I only support the custom TWRP build from the first post.

Known issue with api2 enabled, it's a bug in camera HAL. Yes

I pushed a possible fix for this, try next build when it's out.

I made new branches today, will start working on bringup now that I have a bit of free time

Merry Christmas everyone, thanks to some user today I debugged the issue and fixed the boot problems. Lineage Recovery should also work again. Turns out the issue wasn't related to f2fs but it was specific to some hardware

f2fs just keeps causing issues, I would not recommend using it. On P2 we had big issues in the past as well since lenovo used a very old f2fs kernel driver that was incompatible with modern f2fs driver.

For people that have issues booting: if you ever used a different TWRP than the recommended one since you set up the phone, or used a different TWRP to format userdata, your userdata is incompatible and this is most likely your boot issue. You should take a backup and set up the device from...

Latest/official TWRP 3.4.0 is *not* supported because it is out of my control. Do you use ext4 or f2fs?

Has anyone tried the latest build? Do you still have the issue? Those who have issues, are you using the recommended TWRP from the first post? I can't seen to reproduce this on 2 devices I tried updating :/

This should also be fixed in latest build

Hey everyone, I haven't posted here in a while. I made big updates in preperation for android 11 and fixed some long standing bugs. You can read the full changelog in the download website, however this is a summary of what was fixed: * Fixed double tap to wake screen * Fixed VoLTE/VoWiFi not...

That's weird, my device is booting fine, I'll try to figure out what's wrong. Indeed drain is higher but I haven't figured out where the issue comes from yet. I maintain Xiaomi Mi MIX 2, Razer Phone, Xiaomi Mi A2 and soon Razer Phone 2, Google Pixel 3a and 4a. You can see why I am late...

It's been a while since I posted here, life is getting busy and now I also have to maintain 6 more LineageOS devices. However I still mostly use P2 as my daily driver, since its battery doesn't match any other phone. I'll be bringing up android 11 for P2 soon and if no unexpected issues come...

There are issues with almost half the build servers so we switched to weekly builds temporarily because there wasn't enough time to compile all devices in 24 hours. I have merged some potential fixes for the mic that should be in next build.

Google apps issue should be solved in next build, I had forgotten to pick this commit in new kernel: https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_sdm660/+/281870

I have merged that change now so people can test it. Not sure if it has any effect but I saw some recommendation for it. Still can't reproduce the issue reliably

Did anyone check the recent patches about dark video preview? Is there any improvement or breakage?

Well something must have been broken again in latest opengapps, I'll have to check what's going on :/

There are detailed instructions for installing lineage and additional zips like gapps in the first post, but I will link it again: https://wiki.lineageos.org/devices/jasmine_sprout/install

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 * before...

To be clear I haven't done anything about the media issue, I just can't reproduce it since I disabled nightlies 1+ month ago. It might still exist but I don't have a way to debug or fix it. I can't find any other device with this bug on 17.1 so I don't know what else to do right now.

There has been no progress in the audio issue, mostly because I can't reproduce it reliably. I've been running builds for 1+ week and didn't manage to get the bug. I've merged some patches that should fix fingerprint crashing on devices with broken or semi broken hardware, which should save some...

If someone donates an RP2 then yes. I don't think anyone in lineage got that device. Build servers are not up yet after the recent events but they will be up as soon as the migration to new infrastructure is complete. I've been working on various issues on the device, 120Hz was broken (panel...

There are some issues with the build boxes in the past few days, we are trying to pinpoint the source of the problem and fix it.

We know what's the issue, there is no need for more logs, the problem is that the issue is kind of impossible to happen so I have no idea why it happens. I've spent hours and hours and couldn't find the root cause yet. Rebooting usually fixes it for a bit, for those that are stuck on 17.1 right...

I have disabled builds temporarily because I can't figure out this issue. Also it looks like a similar issue is present on 16.0 https://gitlab.com/LineageOS/issues/android/-/issues/1679 which means I have to look even deeper :/

Ok I can finally reproduce the audio bug myself. Does this happen only on 17.1 or it used to happen on 16.0 as well?

https://wiki.lineageos.org/logcat.html

Not possible right now but there are some plans for that.

Not sure what is the audio problem, can you please post a few logcats when you have the issue? I've been using p2 daily for a month and I didn't reproduce this issue. I looked at https://gitlab.com/LineageOS/issues/android/-/issues/1844 but there doesn't seem to be anything relevant in logs...

17.1 thread is finally up https://forum.xda-developers.com/razer-phone/development/rom-lineageos-17-1-razer-phone-t4087619

17.1 thread is finally up https://forum.xda-developers.com/mi-mix-2/development/rom-lineageos-17-1-mi-mix-2-t4087611

17.1 thread is up https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-17-1-p2-t4087605

First build should be up tomorrow, let's hope everything goes well.

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 * before...

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 *...

Is this the full archive of the builds from basketbuild? I don't even have the builds stored locally anymore and was considering making new ones.

#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 * before...

FM is currently broken that's why there are no official 17.1 builds yet. We are working on a fix.