yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
That experimental build has been made by the LineageOS team for internal testing purposes only. Thus I won't provide any link.
[ONE Android Development] Paulroberts:
Thanks, the MinTheGapps package still just runs the lineageos set up, is there a way to get the lineage setup to not run and run the google setup. I'd like to restore the google backups from LOS17.1

[edit] the opengapps linked in the OP decided there was enough room and the google setup is running.
[ONE Android Development] remedya:
No, I'm not involved in this experimental build and I don't access to the download.
[ONE Android Development] minimoncho:
Hey Tomoms, not long ago I contacted you about this problem. I've been testing other ROMs with custom Kernels, and well, gravity and proximity sensor didn't work on most of them, but weirdly enough they work flawlessly on SultanXDA LOS 14.1 with his 3.4 kernel. I'm loving Android 10 and I'd rather not have to give it up.

Could I use Sultan's Kernel with this ROM? Would this be asking for a bricked device? Also, would this kill the battery life I gained with your ROM?

Is this something that could be taken a look at?

Thanks in advance.
[ONE Android Development] Tomoms:
Glad you got it to work somehow. I don't use Gapps so I'm not able to help you guys on that side :)
[ONE Android Development] Tomoms:
You cannot use Sultan's kernel on this ROM. It wouldn't even boot. But sure, it is very strange that the sensors are not working on other ROMs. Can you install DevCheck, when using my ROM, open it in the "Sensors" tab, and provide some screenshot to show me the full content that is shown by the app?

Just a quick note to let you know that I haven't forgotten about this. I've been overwhelmed with my study duties + more important development stuff so this hasn't been on my radar for a while, but I'll definitely take a look at it soon.
[ONE Android Development] minimoncho:
The gravity sensor stays blank no matter what. The proximity sensor begins as blank, goes to 0 when I block the sensor and stays 0 until I go back to the sensors menu and get back in, then it's blank again and I can repeat the process.
[ONE Android Development] EotT:
No problem. Personal life should always come first. And it's not a major problem, so don't worry.
[ONE Android Development] Tomoms:
I'm happy and proud to announce that I am now an official LineageOS maintainer for our Oneplus One!
[ONE Android Development] kekerosberg:
This is great news. I hope you will continue to update your own optimized ROM for those of use that find stock LineageOS too conservative.

I finally took the plunge today and updated from stock 17.1 to your 18.1. So far so good!
[ONE Android Development] Tomoms:
Sure thing. My unofficial builds won't cease to exist: as I've done until now, I'll use them as a "playground" to test device-specific changes that could be implemented in official builds as well before submitting them. The "craziest" and most extreme changes/optimizations, those that would never be accepted in LineageOS, will continue to live inside my builds.

EDIT: I'll stop updating my 17.1 builds after releasing the last one, which will come when April's patches are available.
[ONE Android Development] ImmortAlex:
Really great news!

And now back to bugs ;)

Do anyone use NFC payments with 18.1 ?

My setup is: Tomoms' LineageOS 18.1, OpenGapps, Magisk canary, MagiskHidePropConfig.

Google Pay app works, NFC itself works (tested with "NFC tools"), but when I try to pay nothing happens. Tested more than one time with different payment terminals.
[ONE Android Development] kekerosberg:
Just an observation. The phone did not fully charge during the night. It was at 35 % in the morning. On stock 17.1 the phone would be fully charged during the night every time.

I use an old 700mA Samsung charger to conserve the battery. I just now rooted and installed Smartpack and will keep an eye on this.
[ONE Android Development] Tomoms:
The charging drivers my ROM uses are screwed up. Official Lineage's are even worse for me, that's why I use these older ones. Sometime they just don't accept current from slow chargers and/or old cables (I've been experiencing the same with my Sony 850 mA charger). For now, just set the charging input current to any value higher than 700 mA in Smartpack and it'll work. One day I'll have the time to look into this issue as well... The plan is to implement Sultanxda's custom charging & battery drivers, I recall they worked perfectly on his Nougat ROM.
[ONE Android Development] ImmortAlex:
In official post about 18.1 npjohnson mentioned that encryption in 18.1 is not compatible with previous versions.

How it can be, if I successfully installed your version above 17.1 without formatting encrypted /data, just wiping it?
[ONE Android Development] Paulroberts:
I do, I can read an oyster card (London transit contactless card) in NFC tools but paying at a till or even on the photocopier at work, no card is detected nothing happens it's like the phone is not there.

Also having trouble with security (magisk?) with some cards as they wont register in Pay.
[ONE Android Development] ImmortAlex:
No problem with four of Russian banks, all cards are registered. Magisk Hide + Manager renaming works very well.

Looks like something broken in between NFC module and Google Pay...
[ONE Android Development] Paulroberts:
I think it's the bank not responding, it says to check the card details which are correct.

There is no response to the phone from the copier, it has a Kyocera nfc reader which does nothing, it should beep and go green or red if it detects a NFC tag, any other card I try it beeps etc.
[ONE Android Development] Tomoms:
Well, you wiped it, which deleted the /data/system file that are associated with lockscreen codes and encryption setup. That's why it worked.
[ONE Android Development] madmax85812:
So I was on RR Q 8.5.9. Am having proximity sensor issues so wanted to try other Roms. I installed your 18.1 build.

- Updated TWRP to latest 3.5.1_9.0

- Rebooted to TWRP

- Wiped Cache/Dalvik/System

- Flashed 18.1 Rom/OpenGApps (from OP)/Magisk v22.0

- After reboot got to lockscreen and faced the same issue (Input pin > back to lockscreen).

- Checked for the files to delete that you mentioned through TWRP

- As mentioned later, no such files found

- Looked for other files & found "locksettings.db"

- Deleted that file & rebooted

- Voila-It works! Successful flash (dirty) from 17.1.

Thanks again for the beautiful ROM.

Unfortunately, my proximity sensor issue persists. When the phone display sleeps, it refuses to wake up most of the times. Phone is functioning, I get calls and notifications and everything, even the key lights come on, but the display doesn't turn back on/wake up. It generally happens when once the proximity sensor is blocked (like in pocket). The only option is to hard reboot the phone. If anybody can help me solve this it would be awesome. Thanks in advance.
[ONE Android Development] Tomoms:
Glad to hear that you managed to dirty-flash. Did you disable the "Check proximity sensor before unlocking" option in Settings?
[ONE Android Development] madmax85812:
Yes. Have kept it disabled for a long time now. No game. Have got a third party ambient display app installed to keep the screen awake at all times, even when locked, just to avoid this issue 7 times instead of 10 times a day. Have to keep the phone out of the pocket and the proximity sensor uncovered at all times. It has become a real pain. Any way to disable the sensor completely? Have tried searching for a solution for months now but have not found any effective one.
[ONE Android Development] Tomoms:
On my previous phone, a user had a similar issue and the dev provided a flashable zip that disabled the sensor. I'll inspect it and see how it can be adapted to the Oneplus One.
[ONE Android Development] madmax85812:
That would just be great. Thank you so much Tom. :)
[ONE Android Development] Tomoms:
A new, juicy update is available! Not only April's security patches are included, but also lots of unnecessary debugging instructions have been stripped out of several components of the OS, to avoid wasting resources on unnecessary computation. I've implemented some updates & optimizations for libpng, sqlite, jemalloc (Android's memory allocator) and bionic (Android's C standard library & math library). I've taken all of these patches from ProtonAOSP's repos, so a huge thank you goes to kdrag0n.

This build also features an important fix that will be included in the next official nightly as well: https://review.lineageos.org/c/LineageOS/android_device_oneplus_bacon/+/307402

The update is already visible on SourceForge, but it will be available for download & via OTA in a few minutes.

EDIT: available now.

@EotT I gave a look at your brightness problem but didn't manage to solve it yet.

@madmax85812 disabling the proximity sensor seems a bit harder than expected. I'll look at it again soon.
[ONE Android Development] EotT:
Thanks for taking the time to look at it, Tomoms!
[ONE Android Development] kekerosberg:
Still no OTA? Am I just being impatient or is there something wrong?

By the way, battery life is great compared to stock 17.1!
[ONE Android Development] remedya:
It's available now.
[ONE Android Development] Tomoms:
I've made it available in this exact moment.
[ONE Android Development] Paulroberts:
any fixes for NFC?
[ONE Android Development] capt.ron:
Some Good News @Tomoms, I did a clean install of your latest 18.1 ROM including your mindthegaaps and I can report that Android Auto now connects properly to my car headunit. So glad to have this working again:)
[ONE Android Development] Tomoms:
What's wrong with NFC?

Nice to know!
[ONE Android Development] Paulroberts:
it does not work, you can read a card with nfc tools but there is no reaction from a reader or a payment terminal.
[ONE Android Development] Tomoms:
I've heard similar reports before, but don't really know what to do. You could try to grab a logcat after the problem appears, maybe it'll be helpful. I've tried reading a few ID cards with NFC here and it's working for me.
[ONE Android Development] Paulroberts:
I think it's not presenting as a card, if I put it on a reader nothing happens.

Will try with the new build tomorrow.
[ONE Android Development] SamVVaeck:
Is it possible when clean flashing latest 18.1 build with mindthegapps package that there is no google setup part that prompts you to restore all previously installed apps, reinstalls themes, etc. ?
[ONE Android Development] Paulroberts:
There is no google set up in the mindthegapps package you need the opengapps package if you want the google setup
[ONE Android Development] SamVVaeck:
Yes, I used the other pico package and now everything is set up automatically
[ONE Android Development] ashutoshmn:
First things first, @Tomoms Thank You! kind Sir for your support on this device.

One thing I'd like to ask to you guys is about the camera libraries. Last time I heard there were Coloros ones, Sultanxda ones but those must be obsolete now? Stock camera app on this one takes pretty average pics and doesn't have a lot manual controls as well. So, I tried the bacon camera but that was doing weird things with the white balance in the viewfinder.

Which libraries are used in this build and any tips on to how to get decent quality pictures?
[ONE Android Development] kekerosberg:
I noticed that the camera picture was VERY bright when using my banking app's camera for scanning bar codes.

Stock camera white balance is off until I toggle HDR on and off again. It seems to be a bit random. At least I have not found any pattern to it.
[ONE Android Development] hystrix65:
Finally I upgraded it to your 18.1, everything seems to work fine but the APP Revolut, home banking. I have to take a selfie to get recognized, I take the photo but the app stop working there.
[ONE Android Development] Saison2018:
@Tomoms : Sorry if you said it before, I still need some time to be used with new forum version.

About your 17.1 build, do you still maintaining it or you only working on 18.1 build (and so, I should think to upgrade my beloved OnePlus One to 18.1).
[ONE Android Development] Tomoms:
I'll prepare one last 17.1 build in a few days. Then, unless there's someone who has a valid reason to ask for another 17.1 build, I'll stop building it, but I'll keep the sources for a while. I, as of now, can't see any reason to choose 17.1 over 18.1. Do you care to explain why you're hesitant to upgrade? :)

The HAL used by LineageOS is Sultan's. I can see all of Sultan's patches applied on top of the CAF msm8974 camera HAL. Maybe just a few of them are missing, I'll try to apply them manually. Added to my to-do list :)

Known issue. It didn't happen on 17.1, if I recall correctly. In the latest 17.1 builds I have disabled Zero Shutter Lag by default, maybe that's the reason (the patch then made its way into 18.1 since the very beginning). I'll revert the change in the next build.

One of MindTheGapps' dev explained to me that SetupWizard is deleted during installation because there's not enough space in the system partition. Maybe I can delete something else from the Gapps package. I'll check.
[ONE Android Development] Paulroberts:
Getting force closed on the latest update with bacon camera and camera apps.

also NFC is the same nothing happens when put on a reader. what logs can be of use?
[ONE Android Development] Tomoms:
@Saison2018 the new 17.1 build is up! It'll be available via OTA later tonight or tomorrow (it depends on how fast it'll propagate to enough download mirrors). It includes April's security patches and some of the recent improvements I've implemented in my 18.1 build.
[ONE Android Development] Saison2018:
Thanks a lot.

About your question on 17.1: I will upgrade to 18.1, I was just too lazy to do it, my phone is running so well actually, I was not in a mood for change, but i will do it.

Thanks a lot for your work and taking time to reply to (almost) every posts. Your deserve it.
[ONE Android Development] Sodomos:
Same. I cant pay with google pay. NFC reader read card, but in shop when i touch terminal nothing happened :(
[ONE Android Development] minimoncho:
To be honest, I like some things of the 17.1 more, like the restart/turn off menu on the side instead of on top. Can't toogle the flashlight with a long press on the power button while locked. Lost the option to force stop an app with a long press on the back button from the developer options menu.

On the topic of the weird sensor behaviour, have you had time to take a look at it? I'm thinking of trying to fiddle with it myself, but I'm no even sure on where to start, do you have a github repository to take a look at the kernel?

Tyvm for keeping our OPOs up to date!
[ONE Android Development] SamVVaeck:
Flashlight toggle is still there on 18.1, rest I can understand.
[ONE Android Development] Paulroberts:
Yep, it's an option in settings > system > buttons
[ONE Android Development] Tomoms:
I hate the restart/turn off menu on top. Not only because it is on top, but because it looks ugly. That flashlight thing is still present in 18.1. Killing an app using the back button was a cool feature but it was dropped by LineageOS due to trouble in implementing it in Android R.

All my sources are available here, in particular the kernel is here. Haven't had the chance to look at it yet, I hope to do it soon.
[ONE Android Development] daniga74:
try this: SultanSnapCam_MOD_by_SuperDroid-BOND.zip
[ONE Android Development] Tomoms:
This is not a link. The file can be easily found with a search engine, though. Did you actually flash it on my 18.1 build? I'm not sure it'd work, because this zip is very old. Anyway, I think that disabling ZSL by default in the camera HAL is the proper way to fix this issue. I've prepared a personal test build and the issue seems to have disappeared.
[ONE Android Development] daniga74:
I test on official lineage 17.1 and it works very well.
[ONE Android Development] Tomoms:
@Paulroberts I think Nolen (the first official LineageOS bacon maintainer) has found a fix for your NFC issue! Stay tuned and please try the next build (I will release it soon).

That's good then :) Will try it myself on 18.1 sooner or later.
[ONE Android Development] Tomoms:
A new 18.1 build is available, with GPS & NFC fixes and some general improvements.

OTA will be available within the afternoon (CET).

EDIT: the zip is quite larger because the system image is less compressed. It'll fit in your /system partition anyway, no worries :)

EDIT #2: available via OTA right now :)
[ONE Android Development] Paulroberts:
NFC now unlocks my copier. :cool:

Will try gpay later on
[ONE Android Development] hystrix65:
I have a problem with this rom: i can't take photos from other apps, i mean, for example, if I want to send a photo with whatsapp, first i have to take the photo using Camera, then i have to attach the photo to whatsapp. I don't know if it depends on Camera APP, but i can't uninstall and even if i install other Camera apps, when i use whatsapp other other apps i can make photos only if default Camera APP. How can i solve it? thanks
[ONE Android Development] Paulroberts:
@Tomoms paid twice with google pay and nfc. :cool::cool::cool:
[ONE Android Development] capt.ron:
Here too.
[ONE Android Development] Pap0ose:
The thread is sleeping ? ;)
[ONE Android Development] Tomoms:
Let's revive it, then! I've just released a new build. It comes with several updates for some libraries (libyuv and libvpx), -O3 optimizations for art, bionic and SurfaceFlinger, and reduced priority for the ugly and intrusive USB persistent notifications.

OTA will be available in a few hours.
[ONE Android Development] Pap0ose:
Ok, many thanks ..

!!! ;)
[ONE Android Development] kekerosberg:
I'm guessing that the quiet is because everyone is just very happy with their devices. I know I am.
[ONE Android Development] Tomoms:
The new build is available via OTA starting from now!

Also, this is currently the state of Gapps, according to the experiences of a couple of users here:

Unofficial OpenGapps: not updated in a long time. They seem to cause lags and bad performance.

Official MindTheGapps: up-to-date, but ther don't work very well and often crash.

Unofficial MindTheGapps by me: seem to be fine.

So the currently suggested Gapps package is this one.
[ONE Android Development] hystrix65:
Do you suggest to do an update via OTA and then to update Gapps too?
[ONE Android Development] vHAPpY:
hi need some help anyone knows how to fix the screen problem in my 1+ after replacing it with a generic one from lazada?

[IMG="OEM SCREEN LAZADA"]https://im4.ezgif.com/tmp/ezgif-4-639a683e97.gif[/IMG]
[ONE Android Development] geokilla:
It seems that the Music.apk is not working as well. None of my music are playing and the app keeps on crashing. Was fine yesterday prior to flashing the latest build.

Not sure if it's a WhatsApp glitch or what but I noticed this on Resurrection Remix as well. WhatsApp notifications are disabled when "Less Frequent Notification Sounds" are enabled. It used to be fine a couple months ago. Going to put it back at default behaviour and see how that works.

Can confirm. Enabling the "Less Frequent Notification Sounds" screws up the WhatsApp notifications.
[ONE Android Development] Tomoms:
Music seems to play mp3/m4a files fine, however there are again problems with flac and I have no idea why, since I have never touched/modified anything related to codecs/media playback etc. As I've previously said, using an external player that provides its own codecs, like VLC, is a possible workaround.

There's not much I can do about WhatsApp notifications, unfortunately.

BTW, I advise everybody to flash Neon kernel v17.1!
[ONE Android Development] geokilla:
I'm just playing MP3 files. Guess it's a possible bad flash then if it works for you. I'll Wipe /system and flash again when I get home. That way it's a semi-clean flash.

As for WhatsApp notifications, any ideas on if there's a workaround where it doesn't enable "Less Frequent Notification Sounds" for WhatsApp then? I've never seen it before but hey, maybe there's a code out there lol.
[ONE Android Development] Tomoms:
No need to wipe /system. It is wiped automatically every time you flash a new build, but there are some scripts that are ran to save Gapps and other mods. If you wipe it by hand, the only different result is that you lose Gapps, so doing it is 100% useless. Just wipe /cache and dalvik-cache.
[ONE Android Development] F3AR:
But in my case it persists. Do you manually tweak something in KE or just the stock settings...? I guess i will have to give it a go again and see if it goes away, fingers crossed
[ONE Android Development] JJohnson1988:
Start with changing the CPU max frequency to 2457 MHz and see if that helps.

The result is nowhere near as smooth as idprophecy's ROM and kernel, but maybe there's a specific reason Tom isn't doing the same thing.
[ONE Android Development] Tomoms:
Nope, the ROM should be as smooth as idprophecy's. It's clear that there's something wrong in the kernel, however, the fact that the performance is bad only for the two of you makes me think that there's some hardware difference in your OPOs the kernel doesn't cope correctly with. As soon as I have some time, I'll try to think about what could be causing this issue and if you agree, I'll send you a kernel to test.
[ONE Android Development] anzi2001:
Have the same lag problem, noticed that sometimes 1 core is just at 100% for like 5 minutes even after every app turned off
[ONE Android Development] JJohnson1988:
I've experienced the lag/choppiness for as long as I can remember with this ROM and kernel, but just figured it was due to an attempt at some fairly liberal power-saving or heat reduction.

And the fact that no one has really brought it up until now made me not really question it much.
[ONE Android Development] JJohnson1988:
This may have something to do with it. Mpdecision is spamming the logcat with errors.

Can anyone having the same lag issue confirm this as well?

Edit: may only happen when turning Mpdecision off and on again in KA. Definitely need a confirmation on this from someone else.
[ONE Android Development] geokilla:
Flashed it again and wiped /cache /dalvik-cache as usual. Still got issues playing MP3 songs. Weird... Maybe I should just retire my OnePlus One and get a OnePlus 5T...
[ONE Android Development] Tomoms:
Weird, indeed. I've just tried playing music again: no issues with mp3, m4a and even flac works fine again (I guess a reboot just fixed the issues I had with flac). Did you try wiping the Music app's cache & data from Android's settings?
[ONE Android Development] geokilla:
Yep I have.
[ONE Android Development] Tomoms:
I'll check this as soon as possible. I'll try to re-enable mpdecision after having disabled it, and I'll try to get it to spam the logcat the same way.
[ONE Android Development] geokilla:
It seems that some of my music streaming apps are not working as well. So my issue is not just limited to trying to play MP3 files. Going to flash back an old ROM and report over the next couple days.
[ONE Android Development] JJohnson1988:
I mean, the choppiness was still there when using AutoSMP, so I assume the issue isn't as simple as fixing that MPDecision issue.

Still, if it'll scratch another problem off the overall list of bugs, I'm all for it.

I appreciate that you're looking into it, in any case. :)
[ONE Android Development] Tomoms:
Hello, I've uploaded a new build. It mainly brings some additional optimizations, and, as usual, it's synced with the official LineageOS project. The in-built kernel is Neon v18, that will be available separately tomorrow. Did anybody try out the OTA updater? Does it work? I still haven't tried it (I always end up flashing the new builds before uploading them).
[ONE Android Development] JJohnson1988:
Yes, the updater seems to be working.

And whatever you changed in the newest build made everything much smoother. I didn't even need to change anything in KA this time.

There's still a fair bit of lag /right/ after boot. But after 20 seconds or so it feels just about right.

Wonder what the other people with the lag issues have to say.