yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] PhilEsk:
Lineage 18.1 installed fine on my two OnePlusOnes. But on first boot the message about updating Lineage recovery came up and I did not OK it. One phone has Lineage Recovery from 17.1 and the other had TeamWin recovery.

Is this going to be a problem if I have to do a factory reset after a couple of monthly security updates?
[ONE Original Android Development] gerald_raaf:
i have problems with MindTheGapps and paid apps from play store tried 3 times. so i have installed offical test opengapps from sourceforge https://sourceforge.net/projects/opengapps/files/arm/test/
[ONE Original Android Development] mrhamed:
I have 'boot-loop' issues after install/active LSPosed or EdXposed as Magisk's module. do you test it? (I'm using microG build)
[ONE Original Android Development] stefan.pilsu:
No.
[ONE Original Android Development] npjohnson:
As the OP says, I can't support things like that - it's a mess to support - if it doesn't work, sorry, but I can't do much.

As for microG, can't really provide support for those easily either. Not sure what they're changing or if my fixes are applied.
[ONE Original Android Development] mt.:
At the beginning I also started the journey with a sideload update from 17.1 but finally ended up with a clean install of 18.1 with the newest TWRP (3.5.1_9-0). The flashing worked but I had to workaround two bugs that were prevented the OS to start:

1: unlock-protection-bug

This can be solved with the hint from @stefan.pilsu, thanks!

2: IColorEnhancement (Livedisplay)

This causes a boot loop on "Phone is starting" and several errors in the logcat:

Deleting the IColorEnhancement-tag from manifest.xml (/system/vendor/etc/vintf/manifest.xml) will finally boot the OS. Livedisplay seems to work anyway. At the initial Livedisplay commit (from 16.0), IColorEnhancement wasn't added in the manifest since not all panels support it:

https://review.lineageos.org/c/LineageOS/android_device_oppo_msm8974-common/+/241419

ColorEnhancement wasn't implemented before 18.1, is there a reason to add it now?

Can this issue be confirmed and how can this be better workarounded or even fixed?

High priority, thanks for any suggestions.

3: UI-crash on settings from nav-bar

It's a smaller bug and this happens directly after a fresh start of the OS: when you try to open the settings through the right bottom icon in the nav-bar (or any settings of WiFi/BT/Profile) the UI crashs and restarts:

E WindowManager: java.lang.IllegalArgumentException: Requested window null does not exist
E WindowManager: at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:5451)
E WindowManager: at com.android.server.wm.Session.actionOnWallpaper(Session.java:356)
E WindowManager: at com.android.server.wm.Session.setWallpaperZoomOut(Session.java:382)
E WindowManager: at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:1154)
E WindowManager: at com.android.server.wm.Session.onTransact(Session.java:139)
E WindowManager: at android.os.Binder.execTransactInternal(Binder.java:1159)
E WindowManager: at android.os.Binder.execTransact(Binder.java:1123)

BUT when you open a notification window at first (Trust or USB mode message) and open settings in the nav-bar after it, the UI does not crash, strange.
[ONE Original Android Development] TheElbenreich:
Can partially confirm #2: I am also having a bootloop with "Phone is starting". After a minute or so, it reboots itself.

That only after the phone was working perfectly yesterday. It then died and I recharged it. Since then, I can't get it up and running any more.

Update:

I managed to logcat and am getting the exact same message as @mt.

However, I can't find /vendor/etc/... Are you sure it's in that directory?

Update 2:

Can also confirm #3 (ui crash).
[ONE Original Android Development] Fekkik:
Am im blind or there is no more "hold back button to kill app" in dev options?
[ONE Original Android Development] ilmich:
Hi all,

thanks for the hard work.

Rom is near perfect, the only thing that doesn't work well on my opo is the nfc (not vital because it's not my primary phone anymore).

I have tried several nfc cards and it rarely works.

But I also saw that the following commit

https://review.lineageos.org/c/LineageOS/android_packages_apps_Nfc/+/260063

has not yet been rebased on 18.1 branch.

I don't know if it's still necessary.

Thanks

Michele
[ONE Original Android Development] Sodomos:
After update i cant pay with google pay. NFC reader read card, but in shop when i touch terminal nothing happened :(
[ONE Original Android Development] mt.:
Thanks for the confirming.

If you switch into the TWRP recovery you should also mount the "system" folder to be visible in the file manager and you should see /system/vendor/etc/vintf/manifest.xml

You can edit this file directly but the nano editor in twrp is a little getting used to. Just search and delete following lines (around line 480), hope that helps.

<interface>
<name>IColorEnhancement</name>
<instance>default</instance>
</interface>

and

<fqname>@2.0::IColorEnhancement/default</fqname>
[ONE Original Android Development] TheElbenreich:
@mt. I did mount system partition but still could not find the folder.

It got worse with whatever I tried... First the screen was just black after reboot, then it would not boot at all.

I'm now back on 17.1 as it's still my primary phone! (adoring that little piece of hardware ;) it's getting old with me)
[ONE Original Android Development] mt.:
@TheElbenreich I remember there being more "vendor" folders in the file system, which is a bit confusing indeed. The right "vendor" folder is inside the "system" folder when you came from the root. I changed the link im my previous posts here.

This can indeed be annoying, and I use this device the most too, but I'll give 18.1 one more try as the OS is now finally booting. Sure, it should getting old with us together!
[ONE Original Android Development] npjohnson:
2 and 3 are fixed, will be fine in the next build.

Turns out bacon has 3 different display panel vendors! And one of them doesn't support colorenhancement! So had to split things out to use different hardware skis to determine what supports what feature. Hence why it worked for me but not a select few of you all.

Bootloop, and the UI crash should be fixed in the next build.

Turns out bacon has 3 different display panel vendors! And one of them doesn't support colorenhancement! So had to split things out to use different hardware skis to determine what supports what feature. Hence why it worked for me but not a select few of you all.

Removed it for a variety of development based reasons.

Will look into it, maybe needs to be forward ported.
[ONE Original Android Development] Purple-_-Tears:
@npjohnson when's the build dropping? It's supposed to be today but didn't see it yet...

Edit: Nvm, it just dropped now, thank you very much. Will flash and let you know :) I was having problems with bug no. 2

Edit 2: Seems like the build isn't uploaded yet. I'm seeing the 20210408 build on https://download.lineageos.org/bacon, but clicking on it is taking me to https://mirrorbits.lineageos.org/full/bacon/20210408/lineage-18.1-20210408-nightly-bacon-signed.zip and I'm getting a "Not Found" error.

Edit 3: build is gone from downloads page

Also, @mt. :

The file path is actually system/system/vendor/etc/vintf/manifest.xml; with two systems.
[ONE Original Android Development] ImmortAlex:
Actually, most of them are JDI panels, some are Sharp, and I have never seen someone with Truly. Even Steve Kondik at the good old time of CM11-13 had problems with support them all just because owners of Sharp and Truly panels were hard to reach until they got bootloops :)

AFAIR Sharp's panels have better colors and higher energy consumption and mostly used on bacon's "brother" Oppo Find7a.
[ONE Original Android Development] ertrink3n:
Please help, I can only take one picture with the camera, after one picture the camera is locked in-use & I have to fully restart the handset. Also any pictures I take cannot be shared/viewed by others. I tried looking for 'pending photos' per another comment on this thread but I didn't see any. I'm running LOS 18.1 4/9 build with microG pre-built. I have tried deleting dalvik/cache & reinstalling but nogo. The issue started with the 4/1 build. Thank you!
[ONE Original Android Development] npjohnson:
it's fixed now :) - forever hopefully.
[ONE Original Android Development] npjohnson:
had to cancel due to panel issues - it's queued up for next week.
[ONE Original Android Development] Purple-_-Tears:
@npjohnson when's the build dropping?
[ONE Original Android Development] npjohnson:
Like I said, next week. 7 days from yesterday.
[ONE Original Android Development] Purple-_-Tears:
@npjohnson

Oh ok, I'm not familiar with the XDA app so I asked the same thing twice 😁
[ONE Original Android Development] BrainlessGamer:
Thank you for the good work in maintaining such an old phone.

if only my phone was in a useable condition 😢
[ONE Original Android Development] mrhamed:
if you stuck on boot-loop after install LSposed/Edxposed update magisk by attached file.

special thanks @yujincheng08
[ONE Original Android Development] peter53:
Does this version support live caption? Thanks!
[ONE Original Android Development] zzjea:
Notification sound does not work for me. Anyone else?
[ONE Original Android Development] MacGyverSolidSnake:
Good morning, anyone test the new build of 15/04?
[ONE Original Android Development] pas7771:
Installed the new 15/4 build with the pico beta gapp

then I restored a TWRP data partition BU from 17.1

then I deleted the file /data/system/locksettings.db by using TWRPs explorer functionality

as indicated on post #23

All is working fine now.

I reverted to 17.1 because I need my phone working with a bank app otherwise I need to reactivate my phone...
[ONE Original Android Development] zzjea:
Updated today Via TWRP and all the daily driver functions are working well. Haven't tried everything yet but all is good. Thanks for the work on this ROM. We have 2 identical OPO 64Gb model that are used all day, every day.
[ONE Original Android Development] lom4x:
Hi, this https://review.lineageos.org/c/LineageOS/android_packages_apps_Nfc/+/260063 patchset should be ported to fix NFC payment issues on bacon.
[ONE Original Android Development] netbuzz:
Here's my dirty flash process (everything works afterward):

On Lineage 17.1:

set creen lock to None

upgrade TWRP to version 3.5.2

backup everything

Boot to TWRP and then:

delete /data/system/locksettings.db

wipe /system, /dalvik, /cache (don't wipe /data)

install latest Lineage 18.1

install OpenGapps pico ARM test package

install Magisk 22.1

After first boot:

set screen lock back

With that process, I did not need to recover any apps and everything works great after the upgrade.
[ONE Original Android Development] npjohnson:
up for review now.
[ONE Original Android Development] lom4x:
Did you have encryption enabled on you phone before the upgrade?
[ONE Original Android Development] lom4x:
@npjohnson, can you please clarify your comment on this PR https://review.lineageos.org/c/LineageOS/android_system_vold/+/304821.

What were fixed on bacon regarding HW FDE if you stated here and on LG G3 review that HW encryption is broken and should be replaced by dm_crypt as i understand?
[ONE Original Android Development] netbuzz:
No.
[ONE Original Android Development] mrhamed:
@[SIZE=13px]npjohnson[/SIZE] Can you build with microG please?! (because last build is 20210409)

bacon
[ONE Original Android Development] peter53:
The selfie camera is often overexposed. Anyone has this problem?
[ONE Original Android Development] Purple-_-Tears:
Opened the camera app to check it, but the flip camera icon itself is absent. I instal5other camera apps and even tried with whatsapp video call, the front camera is not being detected for me.
[ONE Original Android Development] peter53:
I got the same problem now after a reboot... No front camera is detected.
[ONE Original Android Development] Purple-_-Tears:
Guess it'll be fixed in next build @npjohnson
[ONE Original Android Development] npjohnson:
HW backed encryption works fine on bacon with that, the issue is the OS side framework removal of legacy credential support, which breaks PIN/Pattern.

I could have left he crypto enabled, but PIN would never work. Better to fall back to dm_crypt and software encryption them have half working.
[ONE Original Android Development] mt.:
@npjohnson thanks for the fixes, the 15.4 build is now working without changes to the file system.

One question according the AOSP dictionaries:

Currently the AOSP keyboard spellchecker has the default languages included (de, en, es, fr, it, pt_br, ru)

Is it possible to include also the additional .dict files to the build? The most of them are already included in (java/res/xml/spellchecker.xml) but the .dict files are missing. although they are committed to the LOS code.

The unneeded ones can be later uninstalled from the menu and that was working fine the previous versions, thanks.

Additional .dict files:

https://github.com/LineageOS/androi...s/packages/inputmethods/LatinIME/java/res/raw
[ONE Original Android Development] Seb512:
Hello all,

I've been reading this forum for a couple of years but only recently got an account. Anyways, I recently clean installed the latest official build of LOS 18.1 and an unofficial openGAPPS build on my OnePlus One, and it runs well except the camera and torch is broken. When I open the stock camera app, even after a reboot it crashes instantly, and I cannot use any third party apps, as they say "camera in use". When trying the torch, it also says camera in use and is greyed out. Any ideas? Thanks
[ONE Original Android Development] peter53:
I think it is a bug in this build now. I have rebooted my phone several times and about 1 out of 4 or 5 times I can get both front and rear cameras working. Sometimes only the rear camera is working, sometimes both camera are not working.
[ONE Original Android Development] npjohnson:
unsure - if you have a way to include them, push a patchset to gerrit!
[ONE Original Android Development] Vege02:
Yeah, I'm having the same issue. Guess we have to wait for an update.
[ONE Original Android Development] lom4x:
I've successfully dirty flashed to the 18.1 from 17.1. Here is my story.

I've had lineageOS 17.1 with encrypted /data with some 2FA apps like Google Auth and banking apps which i don't want to reinstall. First thing I've tried is to disable encryption on 17.1 as it were mentioned that full wipe required because incompatibility in encryption support between 17.1 and 18.1.

* I backup my /sdcard data with adb, than /data /system with TWRP.

* pulled backup data to the PC

* formatted /data from TWRP confirming that i want to remove encryption.

* rebooted to TWRP

* pushed backup back to the TWRP

* restored /data from backup

but next time I've booted to los 17.1 to temporarily remove lockscreen pattern as were suggested in this thread, OS welcomed me with encryption in progress with ETA to complete.

So i

* repeat formatting /data from TWRP second time

* rebooted to TWRP

* pushed backup to TWRP

* restored /data from backup

* removed /data/system/locksettings.db

* WITHOUT reboot i've installed official los 18.1 from 22.04 and Opengapps from Tomoms thread.

After the boot to LOS18.1 I were again welcomed with ENCRYPTION in progress screen now from los18.1

Than I've set a lockscreen key from 18.1 setting and that's it.
[ONE Original Android Development] peter53:
Just curious, what is the difference between this and Mindthegapps? Can you get Live Captions from the Opengapps? Thanks!
[ONE Original Android Development] lom4x:
I don't have it in Settings. After a quick search it looks like it is Pixel's feature based on some AI engine in recent Pixel phones.
[ONE Original Android Development] trancinguy:
Is anyone else having the UI app crashing as soon as settings is accessed from the quick settings?
[ONE Original Android Development] npjohnson:
Please file a bug ticket with logcat as the wiki details. I'll take a look.

Happy that worked, but I wouldn't recommend, for others, not sure that will cover all cases.

OpenGApps 11 builds are all betas. MTG is thoroughly tested at this point.

For now it's a pixel exclusive, might not be someday. Some people have gotten it working.
[ONE Original Android Development] lom4x:
I wouldn't either :)

The only reason I chosen OpenGapps is concerns that installing MTG over OpenGapps data while transitioning from los17.1 to los 18.1 was tested well or at all.
[ONE Original Android Development] trancinguy:
I figured it out, it is a small bug, if you encrypt without a lock screen, then that bug occurs.
[ONE Original Android Development] npjohnson:
pls file a bugreport like the wiki details, would love to look into that one.
[ONE Original Android Development] onlyme111:
Hi, A complete Noob here - I flashed to lineage OS 17 in Jan 2021. I am not sure if I should update to 18.1, as it says it would be even slower due to software encryption instead of device . can anyone give comment on the performance of Oneplus one with lineage 18.1 - was it slower or not much different?
[ONE Original Android Development] npjohnson:
It's about the same!
[ONE Original Android Development] Lex_Michdeandroid:
With the latest update the camera is still not responding. Anyone found something to fix that already or am I missing something?
[ONE Original Android Development] trancinguy:
Bug fixed with latest update and Export Update is fixed as well, thanks a lot.
[ONE Original Android Development] drezz2:
Does anyone know what the solution to this can be? In lineage 17 it was already happening to me, I tried 18 and it still happens to me, so I returned to 17 because it is my main phone and with version 18 there were things that were not going well for me. The fact is that lately almost every day I have to restart the mobile because it loses coverage completely, it is "without service" and I have to restart it so that it can find coverage again. Anyone knows how to solve this? change the version of the radio? (I have also verified that the coverage is very low, but I have put the sim on another mobile and I do not have these problems)

It is quite annoying, since sometimes the phone has been "without service" for hours and I have not noticed
[ONE Original Android Development] gerald_raaf:
After the last update i had also a problem with camera app, it doesn't open. I solved it with following, boot into recovery mode and delete cache and dalvik/art cache in twrp, then reboot to system. After that camera is working again. Maybe this helps you.
[ONE Original Android Development] wvy:
You're talking about the problem where the OPO eventually loses mobile signal and has to be restarted, right? Your comment has prompted me to finally write about how I've managed to resolve this issue on my device. Bear in mind that I'm using an unofficial build of LineageOS 17.1 at the moment, but I think it's quite likely that the work-around could work for the official build (including LineageOS 18.1) as well. I've posted about the work-around here. The TLDR of the post is to disable System -> Developer options -> Mobile data always active and reboot the device. I'd still recommend anyone to read my linked post though because it includes additional details about the issue.

Edit: if anybody ends up trying this work-around, please report back if it worked for you or not.
[ONE Original Android Development] drezz2:
Yes, that is the problem, again I am in version 17, I have the lineage office, but the option you indicate I have disabled (I have never had it active) This happens to me both if I have the data active, as if I have them deactivated .. they can spend hours without looking at the phone, and when I look at it .. it is "without service" and I do not know how many hours it can take like this Lately it is happening to me very frequently and even sometimes several times a day I thought it could be related to being in an area where the mobile catches a low signal, although it has also happened to me in areas where it gave me a good signal, but it is true that the signal levels vary a lot, that is why I thought that the same Changing the radio could be solved, but with the official twrp I don't know how the radio is installed and if I have any danger of getting stuck with a brick. thanks for your answer

(To rule out that it was a sim problem, I tried a moment on a nexus 5 and it seems that the signal level it catches on that mobile is higher)
[ONE Original Android Development] jpandino:
Thank you for the tip. It really helped with the camera working again.
[ONE Original Android Development] mrhamed:
Does it possible to add WIFI-ADB quick-toggle ?

Thank you!
[ONE Original Android Development] Fekkik:
I've got a problem with Google Discover on latest build. It crashes every time when i pick article to read.
[ONE Original Android Development] APBNDRUM:
Thanks for the effort dev npjohnson

Works well.

Can I get a advanced power menu

Advanced reboot option, my volume rockers are broken

Thanks in advance
[ONE Original Android Development] Likort:
When switching from 17.1 to 18.1, I got bootloops, either loading, reboot, loading over and over again, or just back to recovery after a while of dancing dots.

The combination of apps causing it was

Magisk 22.1 (22100)

Riru 25.3.4 r399

EdXPosed 0.5.2.2 4683

The easiest way to revert to a state that booted successfully was installing uninstall.zip (renamed Magisk zip), which also clears all Magisk modules, then, without the need for rebooting, Magisk zip again, from TWRP.

After that, and after installing Riru, installing either EdXPosed or LSPosed triggered the bootloop again.

What finally helped was

Magisk nightly 22.1 (22105) (6099f3b0157a5aeff1935199215be26f1ad8ccbc) from the "Actions" tab on GitHub (https://github.com/topjohnwu/Magisk/actions/runs/827291454)

The framework(zip install) of this version worked, but the app(apk install) didn't (black screen) so I used this 22105 framework with the official 22100 app

Riru 25.4.4 r426

EdXPosed nightly 0.5.2.2 5183 (8f2308) from the "Actions" tab on GitHub (https://github.com/ElderDrivers/EdXposed/actions/runs/644256064)

I think it was mainly Magisk that did the trick, as the EdXPosed nightly is from March 11, while the Magisk nightly was from May 10. LSPosed nightlies also didn't help on their own when trying various stuff.

Today Magisk 23.0 was released, and after installing, the system also booted successfully. I'll keep the EdXPosed nightly until an official update is released.
[ONE Original Android Development] npjohnson:
Already there - Settings -> System -> Gestures -> Power Menu -> Advanced Reboot.
[ONE Original Android Development] APBNDRUM:
Thanks for the quick replay
[ONE Original Android Development] validat0r:
MAC randomization on Wifi doesnt seem to work. Is it just me?
[ONE Original Android Development] hystrix65:
Does Gps work fine? Have you tried using it with google Maps and moving? It's very important for me, I use it quite often driving
[ONE Original Android Development] npjohnson:
Yeah this won't work on this old of a device.
[ONE Original Android Development] npjohnson:
Yes, it works fine for me.
[ONE Original Android Development] hybiepoo:
Which version exactly, do you know? I'm trying to install even the PICO edition of the latest OpenGapps and it's saying I don't have enough room even after wipe and fresh install.

Edit: Nevermind.. another complete wipe and queued GApps with the ROM install and it seems to have worked fine. Weird.
[ONE Original Android Development] hybiepoo:
Anyone have any issues with not being able to install any apps? "Not enough storage space".

Looking in the storage settings, it seems to be OK, so not sure what is going on. Perhaps permission issues?
[ONE Original Android Development] SethGeckoXDA:
Let's see. What do you mean by "complete wipe"? Which recovery did you use?