yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] AvdonR:
Makes sense. I used the old R19 package with a clean install of the 18.1 build and everything is working very nicely. Haven’t run into any issues yet to be honest. It’s looking like Android 11 is going to be a solid release overall.
[ONE Android Development] ImmortAlex:
And then again me, with f*cking encryption :D

I do wipe and format everything except media, install 18.1 w/o gapps or anything else, and have no luck. It loads (or just hung on bootlogo) for about 5 minutes and then reboots to recovery with "RescueParty" message.
[ONE Android Development] minimoncho:
Morning!

First off, thank you for giving my phone back 48h of battery on standby. This ROM feels so snappy and smooth.

Now to the point. Since the last update the gravity sensor isn't working and thus the screen rotation. I did the update through the inbuilt updater. Might that be the cause? Am I suposed to download the full ROM and install overwriting from the recovery? Or should I do a full clean install?

I'm open to admit it might be my phone, since the proximity sensor has been failing with other ROMs aswell (general sensor problems?), but it was working just fine before the update.
[ONE Android Development] Tomoms:
In the last build I've applied some updates and tweaks to the GPS implementation, because the official nightlies' implementation was working very bad for me... I'll keep searching for a universal better solution that works fine for everybody.

This time it cannot be my fault :)

Can you grab last_kmsg after it reboots to recovery, please?

Thank you for the words of appreciation. The rotation sensor is working fine for me. I guess your sensors are failing... Updating with a dirty flash is totally fine, and whether you do it via the Updater or by manually downloading & flashing the zip, is up to you. There's no difference :)
[ONE Android Development] Tomoms:
I've built an unofficial OpenGapps pico package for Android 11 on arm platforms. I haven't tested it yet. If someone wants to try it out, let me know if it works fine:

https://www.androidfilehost.com/?w=files&flid=321109 or here: https://mega.nz/file/VotQmBCQ#clTE9svcmju_rCR_pXv5cAlntqXT3MXpCGdvhr7e7Ys

EDIT: Warning: not working. Will look into the issue as soon as possible.
[ONE Android Development] Pap0ose:
Hello,

We lost TWRP Recovery ?
[ONE Android Development] Tomoms:
Please be more specific. Did you flash 18.1? Maybe 18.1 overwrites TWRP with its recovery. 17.1 for sure doesn't do this.
[ONE Android Development] Pap0ose:
Yes I flashed 18.1 yesterday and it was OK ...

This morning I wanted to flash "your" OpenGapps pico (on which there is a slight problem) and that's when I saw that TWRP had been replaced by a basic recovery ... I wanted to reflash the old gapps and there planted ! I had to erase all my datas ...

Sorry for my english, I'm french .. ;)
[ONE Android Development] MidnightRaver:
On first boot, there's a tickbox to 'restore Lineage recovery on every reboot'. You probably left that on.

ROM says SELinux is not on, can't install certain essential government app because of this. Intentional?

...and MagiskManager install got me into bootloop now.
[ONE Android Development] Pap0ose:
Hello,

Yes I certainly forgot to check this box ...

Anyway I had to delete all my data and more TWRP in recovery ...

Which Gapps do you use ? and which Magisk Manager do you use ? Thank you and good evening ...
[ONE Android Development] Tomoms:
SELinux is not enforcing because sepolicies are not ready yet. This is a consequence of the fact that 18.1 (and, specifically, 18.1 for bacon) is not considered stable yet, thus it's not intended for daily usage.
[ONE Android Development] SethGeckoXDA:
Is this commit and the ones mentioned in the relation chain relevant for our OPO?
[ONE Android Development] Tomoms:
New 18.1 build available! Link in the first post. There are also Gapps I packaged that go with it. It's all written in the first post. My 18.1 now supports MicroG and UnifiedNLP :)

The next 17.1 build will instead bring a couple of SELinux policy fixes (that I have already tested & submitted to the official LineageOS repo) and possibly some new kernel stuff.

Yes, we'll probably end up using that new set of values in the future (I could implement it in my builds even tomorrow). We'll see if it brings real improvements or not.
[ONE Android Development] Pap0ose:
Thank you.

I made a total reset factory but now I only have access to the LineaOS recovery which is empty so no way to flash the Rom and when I want to start I only see fastboot ...I'm completely stuck...
[ONE Android Development] Tomoms:
Can't you simply enter fastboot mode and flash TWRP?
[ONE Android Development] Pap0ose:
Maybe, but I've forgotten how to do it in the meantime ...

On the other hand I have the impression that by carrying out a complete wipe with the datas it removed everything and it also formatted the Rom and the system ... I think the root is gone too...

And even if I managed to flash TWRP, what do I do next? What system do I reboot on?

I'm a little lost here ...

Thanks
[ONE Android Development] Tomoms:
You're getting way too confused over a very simple thing.

I suggest that you start by completely cleaning your OPO by flashing the original CyanogenOS 13 ROM. There's plenty of info on how to do that on XDA, it's very simple. Then you flash TWRP. Again, very simple and very well documented (even on the official website), as the procedure is the same for 99% of all the existing Android phones. Then you use TWRP to flash your favorite ROM (+ Gapps).
[ONE Android Development] Pap0ose:
Thank you, I understand the procedure .

I have already flashed at least 50 times this OPO without any problem and now I think it has formatted everything and I only have the recovery which is not even original and the fast boot ...

Even asks me if the bootloader is still unlocked ...

I will try to recover like 6 years ago ... LOL

This OPO only serves me as a smartphone for testing different alternative Roms ...

Thanks again to you ...

Translated with www.DeepL.com/Translator (free version)
[ONE Android Development] GasLoop:
Thanks a ton for the Android 11 ROM! I have done a clean install with Magisk 21.1 and MinMicroG but I cannot get MicroG to work. Under self check, the permission for signature spoofing is given but the system level signature spoofing does not work. Also, it seems that the camera is not being recognised, correct?

I have proceeded as such: wiped everything but internal storage, flashed ROM and Magisk, rebooted into ROM, rebooted into TWRP, flashed MinMicroG, fired up an ADB su shell, granted permissions to gms and vending and went to check the self check page. The permission is granted but the system doesn't report signature spoofing. Hence, I cannot launch the Play Store. Any ideas?
[ONE Android Development] sumitinhome:
I am facing a bug in android 11 build. If i put screen lock either pattern or pin and reboot then it goes into bootloop.. happenend to me twice.
[ONE Android Development] Pap0ose:
@Tomoms =>Hello

I did as you advised me, I started from scratch trying to flash CyanogenOS 13 ROM by following all the tutorials of the time on XDA but I encounter a problem indeed it tells me that my USB is not debugged and I fear that all settings and options have jumped when the clean flash is complete ...

Do you have a solution ?

Thank you very much for your patience and availability ...
[ONE Android Development] Tomoms:
You are doing something wrong because flashing CyanogenOS only requires entering fastboot mode. No USB debugging is needed. Make sure you have fastboot & its drivers properly installed. I can't help you with that because I've never dealt with fastboot on Windows (I assume you are using Windows). Anyway, we're going off-topic here, please seek for help in a more appropriate thread. Thanks.
[ONE Android Development] Pap0ose:
Sorry ..
[ONE Android Development] Tomoms:
Camera should work, I don't know why it doesn't for you.

Under Trust preferences, in Settings (Settings > Privacy > Trust, at least on 17.1), there should be a switch that must be enabled in order for signature spoofing to work. If you don't see it, I might have made some mistake while implementing it. Please do let me know.

I'm already investigating this issue.
[ONE Android Development] APBNDRUM:
Disappeared camera icon, but visible in apps management list.

Thanks in advance (y)
[ONE Android Development] murti52:
Is it happening with you as well? Have you checked it? Coz idprophecy wasn't facing it.. so if not, I am flashing the new build tomorrow, so without xoosed or any mods, if it happens I'll give the logs. :)
[ONE Android Development] Tomoms:
I've faced it long time ago, and I've never tried calling with speakerphone again. I'll try later or tomorrow. No logs are needed, thank you.
[ONE Android Development] secretkloud:
Funny, I've never had speakerphone problems. You might want to check the modem you're using. Maybe flash a different one to check. The only annoyance I have is that Google contacts sync keeps crashing. Anyone have a solution for that?
[ONE Android Development] Tomoms:
I've tried 3 firmwares and the issue persists. What firmware are you using? Basically, when using the speakerphone, the other person can't hear me if I talk into the main microphone (the one close to the microUSB port); however, they can hear me if I talk into the small microphones that are close to the camera and the 3,5 mm jack.

I'm pretty sure I know how to fix the Contacts Sync fc, give me some time and I'll test (& release) a new build :)
[ONE Android Development] vivmar:
Hi,

can you please check this new kmsg , sadly i have reboots again. I'm on latest build, no magisk.

thanks
[ONE Android Development] Tomoms:
There are some errors/corruptions either in the /data or in the /cache partition. The kernel performed an emergency remount of those partitions in R/O (read-only) mode to prevent writing more data to a damaged filesystem, but obviously /data and/or /cache can't be read-only because they're the two main partitions in which the OS and the apps store their files, thus the system reboots. You can try to wipe /cache from recovery. You could also change its filesystem to f2fs, just to see if it solves your problem. However, if the errors are in the /data partition, you're pretty much forced to perform a full wipe.
[ONE Android Development] secretkloud:
I sorted the Contacts sync fc by removing and readding my google account. I lost all contacts from the last couple of weeks but it appears to be ok now. I'll report back after a day or so...

I'm using this firmware

bacon_firmware_update_2016-08-26_0.1.c1.11-00006.zip

I don't remember where I got it from. Also, I haven't tested the main mike only problem. I'll check and report back.

Thanks for your builds again!
[ONE Android Development] Tomoms:
What a shame, I've just built a ROM that fixes the fc...

Hello, I don't know if you're still using my ROM, but maybe I've found a way to prevent data corruption and fix your reboots. The fix will be included in my next build, that will probably be available tomorrow.
[ONE Android Development] vivmar:
Yes, i'm with your rom. Thanks, i'll try for sure!
[ONE Android Development] secretkloud:
Please upload the build, just in case it happens again.

Thanks!
[ONE Android Development] Tomoms:
Unfortunately I won't be able to upload it until tomorrow.
[ONE Android Development] Tomoms:
The new build is up! [MENTION=2051524]vivmar[/MENTION] [MENTION=5476357]secretkloud[/MENTION]

This build fixes the Google Contacts Sync crashes, hopefully fixes the random reboots caused by ext4 filesystem errors, and also brings some optimizations for ART and libcore. The latest Neon kernel (v16) is included too.
[ONE Android Development] vivmar:
Thanks,

do you suggest me to full wipe or i can dirty flash?
[ONE Android Development] Tomoms:
You can dirty flash (wipe /cache and dalvik cache)
[ONE Android Development] secretkloud:
Thanks!
[ONE Android Development] vivmar:
[MENTION=5727088]Tomoms[/MENTION]

Hi,

i have noticed that my phone will never go to deep sleep. So i have tryed with full wipe, but still no deep sleep.

Any idea?

UPDATE: Change governor from Interactive to OndemandPlus, and now seem solved.
[ONE Android Development] murti52:
Is anyone using cast here...? The performance is really sloggy over here.. it lags allot.., can others check it out if it's true or it's just for me. Thanks
[ONE Android Development] vivmar:
[MENTION=5727088]Tomoms[/MENTION]

Sadly, now i have again the issue with OndemandPlus...:confused:
[ONE Android Development] kbhasi:
After dirty flashing from one of the November builds of this ROM to the latest build, I found that I can't record video, regardless of which camera app I use. However, I can still take photos just fine.
[ONE Android Development] Tomoms:
No log = no bug.

I have tried recording a video, everything worked perfectly. Try to reflash the ROM, and if the issue persists, provide a logcat.
[ONE Android Development] GasLoop:
Iriun Webcam could not recognise cameras for some reason. I found the switch for signature spoofing, but microG still doesn't report that the system supports signature spoofing. I tried granting the permissions via ADB again, didn't change anything. What can I do? How would a clean flasher have to proceed to get microG up and running on Android 11?

I managed to get the camera running with the default app. However, it didn't save the image I took, instead I received an app not responding error. Now, I cannot access the camera anymore, the camera app says there is an issue connecting to the camera.

Thank you for your efforts and merry christmas to you!
[ONE Android Development] Tomoms:
Hello! Don't worry, signature spoofing isn't working and it's my fault. I might have forgotten something while implementing it, I'll check that in the afternoon. In fact, I already have an idea about what to try, and I'm pretty confident we'll solve this problem quickly :)

A merry Christmas to you as well and keep an eye on this thread, for a new build is coming very soon :)
[ONE Android Development] sbhajband:
I know that the Linageos 18.1 is unstable for for our OPO. But when I installed it I have on OPO only one problem experienced is Gapps not stable. Please developer Find or develop android 11 gapps for ARM.
[ONE Android Development] GasLoop:
Thanks a ton for your efforts!
[ONE Android Development] Tomoms:
Please try the new build, it should fix signature spoofing.
[ONE Android Development] Crazy073:
Is this new build lineage os 18.1 fixed the lock screen issue.
[ONE Android Development] alprtewwqfr:
Hi,I try it yesterday because I want to replace the lineageos 17.1. But when I set the pass lock but it always crash setting?
[ONE Android Development] GasLoop:
Hi Tomoms, thank you very much, microG now reports that the system supports signature spoofing. But the Play Store's signature spoofing has no tick although I have applied your ADB commands and rebooted. I have used the MinMicroG-Standard-2.9-20201128144725 package for installation. Also, the camera app is not visible but Iriun Webcam recognises the camera.
[ONE Android Development] Crazy073:
Ok thanks 👍
[ONE Android Development] Tomoms:
I know... Please be patient, I'll try to sort this issue out as soon as possible.

Hmm, I don't know what could be the problem... I'll try to come up with a possible debugging idea.
[ONE Android Development] Gold Ribbed:
I am running 18.1 and for me it is pretty stable. However the rom overwrites Twrp. I have flash twrp via fastboot bot on reboot it goes back to lineage recovery. How can I prevent this please?
[ONE Android Development] Pap0ose:
@Gold Ribbed =>

As I posted it a little above to me also the 18.1 removed the twrp and also re-blocked the bootloader ... I managed to recover by putting it back under cyanogen in 4.4 ... LOL ... It is necessary to start all over again from the beginning like in 2014 !

I'll switch back to Android 10 for the moment ...
[ONE Android Development] Gold Ribbed:
Oops I should take more notice. I managed to get sorted using fast boot. I had to boot twrp in fast boot, once open flashed lineage 17.1 and gapps. I am now up and running and twrp is preserved.
[ONE Android Development] Tomoms:
I honestly have no idea why TWRP gets overwritten, because other users aren't reporting this problem (perhaps you have enabled the related switch in Developer Settings?), but one thing is for sure. This ROM has not re-locked your bootloader. Otherwise you wouldn't be able to boot the LineageOS 18.1 ROM itself.

Did you reboot after typing the commands? You must have made some mistake if it still doesn't work, because an user told me it's working fine for him.
[ONE Android Development] Pap0ose:
@Tomoms =>

To be completely honest I don't think it's the Roma that's in question, I rather think it's the pico Gapps of December 20th. Previously I had installed this Rom with Gapps given by a member on the thread and it was working well ... It is at the time of the change of gapps that it happened ...

Good evening to you ...
[ONE Android Development] Tomoms:
Hey guys, just wanted to tell you that lots of exciting things are happening behind the scenes, and new builds of 17.1 and 18.1 will come soon, to deliver the awesomeness to your devices :)

The new 17.1 build will feature: an updated kernel with interesting backports (already done), the screenshot quick tile (shouldn't be difficult to add - it was requested by an user several months ago, but I've kept forgetting to implement it), updates for Eleven, the default music player (thanks to the LineageOS team).

The 18.1 build will fix the lockscreen issues & it'll have enforcing SELinux. Maybe something more but I don't know yet. It'll stay pretty close to what would be an official LineageOS build for now, as I'm still mostly focusing on 17.1.

Stay tuned!

Gapps can't relock the bootloader in any way either.
[ONE Android Development] Pap0ose:
So I don't know what could have happened but the 18.1 was working well until I wanted to change Gapps and then no more twrp and nothing ... I had to start again from cyanogen 13 ... but I don't understand this OPO either, I've flashed it at least 50 times and never encountered this problem ... Now we're going to move on and move on ...

Thanks
[ONE Android Development] rew2:
Hello!

Happy new year 🎉!

Any chance for an update link refresh?

The phone updater is not downloading.

Thank you very much!
[ONE Android Development] Tomoms:
Done! Reboot and check for updates again, then it should work.
[ONE Android Development] Pap0ose:
Hi, I'm going to try this rom again but which Gapps do you recommend ? Thank you and happy holidays .
[ONE Android Development] Tomoms:
If you're going to install 17.1, use OpenGapps Pico, the official package available on their website. If you're going to install 18.1, I've linked the recommended Gapps in the first post of the thread.
[ONE Android Development] rew2:
Done and updating as I type (is my wife phone. Bought it with an Oneplus invite, long time ago)

She still likes it a lot. Thank you for your support and work!!!
[ONE Android Development] Pap0ose:
@Tomoms Many thanks ... ;)

Everything OK except TWRP is gone ..LOL ..

TWRP is replaced by this recovery !which is not even the original recovery but a recovery that looks more like LineageOS ...

And this recovery does not want to install Magisk .

Moreover I can't install TWRP from the fastboot because the adb drivers are not found anymore and so the device is not recognized anymore ! .
[ONE Android Development] Gold Ribbed:
This happened to me Too. Fast boot seems to work . I flashed Twrp. I then used flashboot to boot twrp img. Twrp launched. I was then able to flash 17.1 and gaps. Rebbot system and all was back to normal for me.
[ONE Android Development] Pap0ose:
Thank you but I can't flash TWRP from the fastboot because the adb drivers are not found anymore and so the device is not recognized ! .
[ONE Android Development] Gold Ribbed:
My device is not recognised by ADB but it is by fastboot.
[ONE Android Development] Pap0ose:
From fastboot I flash TWRP and it's OK but when I reboot in recovery I find the recovery LineageOS and not TWRP... This rom is weird !

Thanks to you
[ONE Android Development] Gold Ribbed:
Do not reboot. Fastboot boot recovery and it should launch twrp. Good luck this happy new year.
[ONE Android Development] Pap0ose:
OK, I understand ... Many thanks !!!;)

Happy new year ..
[ONE Android Development] Tomoms:
Very strange, guys, I don't know what to tell you. There are users who have been testing my 18.1 builds since day one and their TWRP was never overwritten by Lineage recovery...

EDIT: I'll ask this again: during the first setup of 18.1, when you were asked if you wanted automatic recovery updates, did you enable the checkbox? If you did so, that's the reason why your TWRP was overwritten.
[ONE Android Development] Pap0ose:
I don't remember that, but it's possible, yes ...

It would indeed be an explanation !
[ONE Android Development] sumitinhome:
it is exactly the reason for it.
[ONE Android Development] Gold Ribbed:
I do not recall seeing anything about automatic recovery updates on setup. Where would this be?
[ONE Android Development] Pap0ose:
Yes, it can be interesting where it is located
[ONE Android Development] Tomoms:
During the initial setup, after selecting your preferred language, the timezone, the WiFi network, etc., towards the end of the process there is a screen which only asks that single question. It's impossible to miss it :)
[ONE Android Development] Pap0ose:
OK, many thanks.. ;)
[ONE Android Development] sbhajband:
I have tested 2 realeses of 18.1 four time but no problem of twrp. Because not selected the option "update linageos recovery" in setup wizard. Its simple but need attention in setup wizard, step by step.
[ONE Android Development] Pap0ose:
OK, I will try to reinstall the 18.1... LOL
[ONE Android Development] Pap0ose:
Hello,

Indeed I have just reinstalled the rom 18.1 and I saw this famous box which is checked by default and that I thus unchecked and there it is OK for the TWRP ...

On the other hand the root with Magisk does not work (flash failure)

In the developer options there is no advanced restart ?

Thanks a lot
[ONE Android Development] nullington:
I am on 17.1 and am experiencing issues with mobile data. Sometimes it just stops working, toggling airplane mode or mobile data does not fix it. Only a restart helps.
[ONE Android Development] Tomoms:
Can you be more specific and share a picture about Magisk's failure?

Don't know about advanced restart, sorry, I'm still using 17.1.

I'm not facing any issue. Try to check if the APN parameters match the ones suggested by your carrier, and eventually change those which don't.
[ONE Android Development] Pap0ose:
@Tomoms => Here is the error during the flash :

Ok for advanced reboot

If it's not indiscreet, why do you stay on 17.1 and not on 18.1?

Thanks
[ONE Android Development] Tomoms:
Why in the world are you using Magisk 20.3???? The latest version is Magisk 21.2, use that one. Previous ones are probably incompatible with Android 11. I'm using 17.1 because I still have got some development to do on Android 10 and I need a reliable phone right now. The new 18.1 build will be quite an improvement over the last one, but I think I'll stay on 17.1 for one more month.
[ONE Android Development] Pap0ose:
Ok many thanks ...
[ONE Android Development] Tomoms:
The Advanced Reboot option has been moved in Settings > System > Gestures > Startup Menu (something similar).
[ONE Android Development] Pap0ose:
Ok, nice .. Many thanks ... ;)
[ONE Android Development] tpuserhp:
The latest LineageOs 18.1 rom and the unofficial opengapps are very stable and smooth. Thanks for the great work!