yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Jokert129:
should i even try to flash it ? i havent rebooted my phone since last flash and its getting slower and slower by the day, the thought of permanent soft brick scares me
[ONE Android Development] watchoutbehindyou:
Is there any way to turn on face unlock? I don't have this option in smart unlock settings at all. On 7.1.2 it 's working great. I'm using NANO gapps package.
[ONE Android Development] Tomoms:
Sorry, I don't know. I'm using MindTheGapps and I can't see the option either.
[ONE Android Development] ConnerJSP:
I have encountered this issue myself and it has been discussed on the Gapps xda forum: https://xdaforums.com/showpost.php?p=77894229&postcount=5662 . There are other android articles explaining it as something they were trying to "fix" or debug. Apparently, using the beta version of Play Services brings it back, but after flashing recently and reinstalling beta, face unlock hasn't come back; waiting for the next beta version to try out.

There are other issues I have with google apps like photos not showing photos in my internal storage and messages not having dark mode. These were also discussed and seem to have been addressed (messages works now, but photos is still broken for me): https://xdaforums.com/showpost.php?p=77925165&postcount=5676 .

Somehow these minor issues are most interruptive to the use of my phone. What would be the proper way to get support for these issues? Thinking of ways to be helpful: send logs to GApps developers, send feedback in the apps?
[ONE Android Development] salmanfarisy:
Why is CPU underclocked to 1,9 GHz by default?
[ONE Android Development] Tomoms:
Because Sultanxda has always done it and his motivation made sense to me: https://xdaforums.com/showpost.php?p=72784090&postcount=3
[ONE Android Development] Milan34119:
Hey [MENTION=5727088]Tomoms[/MENTION]

Have you found out something yet?
[ONE Android Development] watchoutbehindyou:
And you can always add more power in kernel aduitor or ex kernel manager. For mid-range user (and battery) 2400 Mhz it's kinda overkill ;)
[ONE Android Development] Tomoms:
I haven't even opened the logs yet. I'm way too busy with my exams. You'll have to wait one more week :)
[ONE Android Development] Milan34119:
I am sorry good luck with your exams:good:
[ONE Android Development] nipun03:
I have Official Build - 01/15/19 (15.1) and was facing the same issue with opengapps nano (01/15/2019). The issue was resolved by uninstalling Xposed Module - Instant Face Unlock and flashing opengapps nano - 01/19/2019. I hope it helps.
[ONE Android Development] Tomoms:
Hello guys,

I'd like to inform you that I plan to switch to LineageOS 16 soon. I'll start by using TugaPower, to get used to the new OS and to finish setting up my building environment (I have to pull some files from LineageOS 16 before I can start building my own releases). Then I'll start sharing my own builds. Since it'll take me a while to implement in LineageOS 16 all the features and the optimizations that I've added to my 15.1 builds, the first LineageOS 16 builds will be very close to the standard LineageOS ones, but I'll gradually get to the point I've reached with Oreo.

I might build and upload one last 15.1 build in the next days.

I'll keep you informed :)
[ONE Android Development] Tomoms:
Hello :)

I'm currently building LineageOS 16! I'll test the new build tomorrow in the afternoon, and if it boots & works properly (and I see no reason why it shouldn't) I will share it here with you.
[ONE Android Development] Tomoms:
Hello! My first LineageOS 16 build works fine and even Argon kernel is working fine :)

However, the ROM is not ready for you to use it, especially because I have to improve the kernel's implementation (currently it's very buggy and a normal user would go crazy to make it work properly). So I will

not

release this build, however I think that within a few days I'll get this stuff sorted and a new build will be ready!
[ONE Android Development] Tomoms:
It's time to have some Pie!

Here I am, ready to share my first LineageOS 16 build.

There are a few things I have to write, in order to let you know how to get the best out of this build and what to expect from it.

Optimizations: there are very few optimizations in this build (compared to my 15.1 builds). The ones that I've implemented mainly consist in some hwui improvements and some debugging options that have been disabled (debugging stuff can cause overhead). I plan to compile the next build with the latest Clang & GCC, then I'll add -O3 optimizations and in the end I'll switch to Qualcomm's sdclang.

Argon kernel implementation: Argon v11 is included in the build, however Spectrum is not supported (WIP). Qualcomm's hotplug has been completely removed from the ROM, bricked hotplug is the only hotplugging driver you'll find. I forgot to tweak a few parameters in the boot scripts of the ROM, thus I suggest you to download Kernel Adiutor, open the "I/O scheduler" tab and modify the scheduler's tunables to match these values:

async_read_expire = 100
async_write_expire = 250
sync_read_expire = 50
sync_write_expire = 200

Then, in the "Virtual memory" tab, set

dirty_ratio = 20
dirty_background_ratio = 10

These tweaks will be implemented in the next build. Actually, they're not essential (the ROM will work perfectly even without applying them), but anyway - I recommend you to apply them.

Root access: Magisk v18 works perfectly, but after installing it, Magisk Manager for some reason was not present in my phone. I had to download it separately and install it manually. SuperSU should work as well (not tested).

GPS: I made a quick test and it worked. Locking did take a few seconds (I was inside a car, moving in an area with poor mobile network signal), but in the end it worked.

Substratum/OMS: I haven't implemented it natively. Anyway, it's possible to install & use overlays, but be careful: reboot your phone after installing and removing them (otherwise, the substratum app won't show them as installed or will show them as installed even after removing them).
[ONE Android Development] JT1510365:
Thank you for sharing your rom with us:)

Just a couple questions though is cell hotspot working on this ROM and which firmware do you recommend with this ROM?
[ONE Android Development] gil80:
Hi. Which camera libs are used in this ROM? I'm hoping the Sultan camera can be used with this.
[ONE Android Development] Tomoms:
https://xdaforums.com/showpost.php?p=77461145&postcount=6

Yes, of course, both USB tethering & WiFi tethering are working fine. I'm using this firmware.
[ONE Android Development] JT1510365:
Cool then I will test the ROM today on my one plus one and report to you how well it goes for me:) Thank you again for supporting this device me and the rest of the xda community definitely appreciate you:)
[ONE Android Development] gil80:
Hi.

I'm just about to install this ROM, but there are two things I'm not sure about:

1. Is this ROM rooted? If not, what's the best way to root it?

2. I saw the post about the firmware question. Does the firmware affect wifi speed/mobile data speed, reception etc.?
[ONE Android Development] Tomoms:
1. The answer to this question is written in one of my previous posts (the one in which I describe the features of this build).

2. Firmware surely affects mobile network reception. I'm pretty sure it has nothing to do with WiFi (but here I might be wrong).
[ONE Android Development] gil80:
How would I know which firmware to install? And is it done prior to flashing the ROM or whenever I want?
[ONE Android Development] Tomoms:
Flash it whenever you want. Here you can find more info on all the available firmwares: https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-t3462214
[ONE Android Development] gil80:
Thank you.

I'm getting Android Setup keeps stopping, right after I enter my wifi password when it searched for updates.

I did wipe twice.

I flashed the latest ROM and nano Gapps.
[ONE Android Development] Tomoms:
I faced the same issue. Just tap on "Close app", the setup process will continue anyway.
[ONE Android Development] AliasOfiuco:
Can I update the new Lineage 16 ROM just released as a normal update like I already did till now?

Or should I do an installation starting from zero?

I hope it makes sense what I said.
[ONE Android Development] Tomoms:
If I have correctly understood your question, you're wondering whether you can upgrade from my 15.1 builds to the Pie build without wiping. It might be possible (by simply flashing ROM + Gapps), however I strongly recommend that you perform a clean installation.
[ONE Android Development] AliasOfiuco:
Will your LineageOS 15.1 be discontinued by now, given that you are working on LineageOS 16 ?
[ONE Android Development] Tomoms:
Yes, I don't plan to update it anymore.

BTW, I've released a new build. It brings tons of updates, tweaks and optimizations :)
[ONE Android Development] gil80:
does anyone get force close on the Sounds app when trying to change ringtones/notification tones?
[ONE Android Development] Tomoms:
Yes, it happens on all devices. Just downgrade to Sounds v1.x and never update the app anymore.
[ONE Android Development] gil80:
I can't find an older version. How do you downgrade and detach from market?

Thank you for the help!
[ONE Android Development] Tomoms:
Settings > Apps > All apps > 3 dots in the top-right corner > Show system apps > Sounds > 3 dots in the top-right corner > Uninstall updates

Then open the Play Store and check for updates. An update for Sounds will immediately be shown, at this point you need to tap on Sounds to enter its Play Store page, tap on the 3 dots in the top-right corner and untick the Automatic updates option!
[ONE Android Development] JT1510365:
Im experiencing massive battery draim with the february 3rd build of lineage 16. Does anyone have any suggestions of what i can do to fix it? I am using the kernel that came with the rom and i have done a full wipe and clean flash
[ONE Android Development] gil80:
Use CPU Spy app. When you open the app, reset the counters and then close the screen and leave the phone untouched for at least 15 minutes.

If you have a battery drain, it means that CPU doesn't get into deep sleep. If it does, then it won't make sense :)

If you see it doesn't get into deep sleep, I suggest installing Better Battery Stats (BBS)and set a custom reference point and leave the phone untouched for about 30 minutes.

Then open the app and try to figure out which app is running all the time.

p.s. - BBS can also do what CPU Spy does.
[ONE Android Development] ralpyka:
Is selinux enforcing on the LOS 16 build?
[ONE Android Development] Tomoms:
By default it is. But you must set it to permissive if you want the notification LED to work. Check my post here.
[ONE Android Development] timbuctoo:
Bluetooth Apt-X, Apt-X LL and Apt-X HD won't work on the OnePlus One

Apologies for responding on an older post, but it's the only one relevant on Apt-X and Apt-X HD that I found.

As far as I know, these codecs are only effective on devices supporting these protocols in hardware. Else, they revert to the common denominator - typically, SBC, especially, as our OnePlus One does not support Apt-X by virtue of the Snapdragon 801's lack of it.

I'd be happy for a confirmation from any Bluetooth experts for a correction.
[ONE Android Development] antfior93:
I've two bugs. When I send photos or videos on WhatsApp , the app crashes. Another bug is the proximity sensor when I call doesn't work, the screen isn't black.
[ONE Android Development] Tomoms:
I've seen many devices on which the Apt-X codecs were ported by XDA devs. I don't know if these ports are functional or not, but they should work, according to what I've read in some XDA threads. Unfortunately, I can't confirm it because I don't use bluetooth headphones.

Anyway, I'll soon implement these changes, more info can be found here.

I don't face any of these issues.
[ONE Android Development] JJohnson1988:
Can the new Pie-based builds be dirty flashed on top of the Oreo builds?
[ONE Android Development] ConnerJSP:
See Tomom's post regarding dirty flashing:
[ONE Android Development] JJohnson1988:
No idea why I didn't see that.

Danke.
[ONE Android Development] timbuctoo:
The link you shared confirms devices natively need Apt-X (as it requires licensing fees)/LDAC. Quoting an excerpt:

"...buy devices and headphones with aptX or LDAC codecs supported. These codecs require licensing fees, so devices with them are more expensive."

Confirmed with the OP here also - https://xdaforums.com/apps/magisk/module-magisk-aptx-hd-enabler-hi-res-t3579793.

So hardware as well as software support is required for a working Apt-X configuration. Unfortunately, the OnePlus One does not support this natively in hardware (licensing or otherwise); so it's a no-go for this phone. However, as mentioned in the link you shared, the alternative is high bitrate SBC, and it's fantastic that you're going to include these changes! Hope to see this soon. :good:

P.S: I had already tested a Magisk module for Apt-X libraries and confirmed that it does not work on OPO.
[ONE Android Development] ConnerJSP:
Man, I've been having real trouble lately with multiple issues.

They (likely) don't stem from your ROM, of course. GApps has been a mess for awhile now, especially because I rely on the stock version and most of the apps; messages and photos breaking. Now, on Pie, the pixel launcher continuously crashes. It seems to be an overlay problem that happens on most (all) ROM's.

So, I suppose I'm stuck with going the stock route or waiting for these issues to be resolved.

But again, thank you, Tomoms, for the continued support of this device and the effort to deliver a truly optimized ROM.
[ONE Android Development] CedArctic:
You should definitely check out microG if gapps are causing you issues.
[ONE Android Development] gil80:
So recently I've got battery issues which I don't think has anything to do with this ROM, but while trying to reset the battery I found that this ROM doesn't allow to charge the battery while the phone is completely shut down.

The moment I plug in the charger, the phone will go into this boot loop, where it will show the battery icon and then boot to the one plus one logo, then again to the battery logo and vice versa.

Is there a way around this?
[ONE Android Development] dabanhfreak:
Would it be possible to release at least one more update, at least until your Pie build has been tested for stability for a few weeks? These days I'm somewhat conservative with my ROMs since I prefer reliability from my daily driver.

Will Upgrade as soon as I read fewer bug reports.
[ONE Android Development] Tomoms:
I hope and I'm pretty sure that this bug exists across all the different unofficial builds for bacon. It is quite serious and I'm not sure I can fix it, so, assuming it's a LineageOS bug, we have to wait until our devs fix it. Anyway, I'd like to at least look into it, but this won't happen before the end of the next week.

Yes, sure. I'll release it next week.
[ONE Android Development] gil80:
Thank for looking into it.

Before upgrading to this ROM I had linageOS 7.1.2 which was done by SultanXDA, this linage based ROM didn't have this issue. So I'm assuming it's from Android 8/9 if it's truly a widespread issue.
[ONE Android Development] antfior93:
I try to upgrade WhatsApp app but I 've the same problem. I'm on Los 16.1
[ONE Android Development] gil80:
I think this qualifies under the BUGS section in the first post, isn't it?
[ONE Android Development] fabiomcz:
Congratulations on your work, I tested your version of Pie, and it's on the right track to be one of the best.

I noticed two issues besides the bugs of the sensors, already known. FaceUnlock does not unlock atomically and not the function to activate this functionality. another must activate the MTP mode, you need to manually activate in the developer options, without this the PC does not recognize the device.

The good points are for the lower battery consumption when idle, in addition to overall battery performance.
[ONE Android Development] AliasOfiuco:
Hi Tomoms, a last question about your optimized LineageOS 15.1...

If I download and flash the upstream official LineageOS 15.1 , the one you were used to sinch with, and then I flash your Argon Kernel, I would get something stable and close enough to your optimized LineageOS 15.1 or I would do a mess?

I'm saying that because I really liked the stability and the performance of your discontinued rom and I would like to have it still updated with the upstream official Lineage.
[ONE Android Development] Tomoms:
I've just tested offline charging and it works perfectly. It might be another bug related to SELinux. My SELinux is Permissive because I want the notification LED to work (although, starting from the next build, the LED will work with Enforcing SELinux, thanks to the help of an user who found a patch that fixes it). If you can, try flashing the SELinux Permissive patcher and test offline charging again.

What's the "bug of the sensors"? Sensors are working fine for me. MTP mode must be set as the default USB mode only once, then the new preference should stick forever. But other users reported the same issue with my 15.1 build. Do tell me if the setting does not stick across reboots.

I can't help you with FaceUnlock, sorry: I don't use it and I barely know what it is.

Flashing official LineageOS 15.1 on top of my builds should work but I can't guarantee it. Official 15.1 + Argon kernel isn't a bad combo, but honestly it'd be quite far from my ROM. It's not an effort for me to keep building 15.1 every now and then, if you need it, I'll consider doing it; after all, I just need to type a couple of commands in the terminal, the computer does the rest on its own :)
[ONE Android Development] gil80:
Where can I find the patch to have selinux enforcing again?

Also, can someone please assist me with USB OTG?

It used to work for me with 7.1.2, but not anymore. I use it to save nandroid backups since I cannot have the space for nandroid backups on local device. I've tried several USB sticks, formatted to NTFS.
[ONE Android Development] Tomoms:
I've linked it in the first post.
[ONE Android Development] gil80:
I can find the mod for permissive but not the revert mod for enforcing.

I want to confirm it's the selinux issue, but then I'd like to revert back to enforcing.
[ONE Android Development] Tomoms:
There's no mod for reverting to Enforcing. You can reflash the ROM and you'll be on Enforcing again.
[ONE Android Development] AliasOfiuco:
Great! :victory:

Thank you Tomoms! :)
[ONE Android Development] gil80:
Oh. Then I'll skip this test :)

I cannot afford spending time setting up the phone again with all the sounds, mods etc.
[ONE Android Development] Tomoms:
You don't need a clean flash! A dirty flash with no wipes would be enough :)
[ONE Android Development] gil80:
I can confirm the following. After switching to permissive, the battery is stuck at 100%. This makes the test almost impossible, since I'm not able to verify if the phone won't get stuck in boot loop when the battery is low and the system tries to reboot itslef once battery levels are enough for system operation.

So while the battery is stuck at 100%, I was able to confirm that I'm now able to charge the phone when it's off.

Do you think this can be fixed if it's a SELinux enforcing issue? I know that one other Pie ROM with enforcing, doesn't have this issue (POSP)

p.s. - I know it cannot be at 100% because I did a nandroid backup with compression so it should have drain the battery.
[ONE Android Development] sayash5:
Is the LOS15 going to get monthly security updates? or is it discontinued for good?
[ONE Android Development] Tomoms:
I can assure you that the status of SELinux has nothing to do with the accuracy of the battery readings. I've been using permissive SELinux for days and, of course, the readings are correct. It can happen that the battery gauge driver reads a wrong value, but that can happen independently of the status of SELinux. Pie ROMs based on AOSP and not on Lineage haven't got this bug because the device trees & offline charging systems are different. The bug will be fixed on LineageOS as well, some day.

I've literally discussed this with another user yesterday. Please check the last posts of the thread before posting a question, because it's useless to ask what has already been answered.
[ONE Android Development] theekilla:
Can anybody tell me if in the system profiles when you try to set the "Preferred Network type", does is still crashes?
[ONE Android Development] Tomoms:
I had prepared a new build earlier today but for some reason it crashes right after booting. I have no idea why this happens, I hope and think there is some problem on Lineage's side, because in this build there were very few changes of mine, thus I don't think it's my fault. I'll resync and build again in the next days, and I'll let you know what I find out.
[ONE Android Development] rolarocka:
Very smooth and fast Pie ROM, good work ?
[ONE Android Development] Saison2018:
[MENTION=496090]Tomos[/MENTION]

Sorry if the question was asked or seems stupid but i did not find a truly clear answer: What Gapps version (ARM or ARM64) do we need to flash with your LOS 16 rom?

I have done a clean installation of your LOS 16 rom and MindTheGapps (https://androidfilehost.com/?fid=1322778262903983907) but could not use phone because a lot of errors with "Pixel .... keep crashing". i could not connect to google account or do anything.

Just want to be sure if this is related with this Gapps package or something else.

Thanks a lot
[ONE Android Development] Tomoms:
ARM64 is the architecture of the 64-bit ARM CPUs, thus ARM64 Gapps cannot be used on bacon, because the Snapdragon 801 is a 32-bit CPU. I'm surprised the phone even managed to boot. You must use OpenGapps for the ARM platform.
[ONE Android Development] Saison2018:
Thanks a lot, I will do a new clean installation with ARM OpenGapps.
[ONE Android Development] rockmadhavan:
Been using Lineage os 16 with argon kernel for 2 weeks. Pretty stable with no random crash. Overclocked CPU to 2.88ghz and it seems good so far. The only bug I noticed is faulty setup process after fresh install of ROM. Had to keep retrying the setup until it works. And I can't charge the phone if I off the phone(heard its from lineage 16 related problem). Other than the 2 bugs mentioned, don't have any other issues. Edit-led not working
[ONE Android Development] Tomoms:
Thanks! I hope to release a new update soon, but I'm having some trouble. The two bugs you mentioned are already mentioned in the first post, together with a workaround you can use to fix them.
[ONE Android Development] gil80:
You can "fix" the charge when phone is off by flashing SELinux permissive mod, but I recommend against it.

It's enough your phone is rooted, you don't want to have SELinux in permissive as well.
[ONE Android Development] Tomoms:
In my very humble opinion, people's reaction to SELinux being set to permissive is exaggerated. I agree that SELinux should be Enforcing on a stable, public build of the OS, but if during the development of the ROM there are a few bugs that are SELinux-dependant, I don't think anyone should really be worried and give away two useful features (such as the LED and offline charging) only because SELinux must be set to Permissive in order for them to work.

Also, you talk about our phones being rooted as though this exposed us to hundreds of dangers. Well, having the possibility to run commands as root is a normal feature of every single Linux distro for computers: it is up to each user to use it wisely. I strongly believe that as long as one is not a complete idiot, 99% of the time there's no reason for them to be worried about SELinux, and having a rooted phone should be something normal.

EDIT: LineageOS has merged a new commit in our device tree that should fix offline charging. So the next build will hopefully have both the LED and offline charging working with Enforcing SELinux.
[ONE Android Development] AliasOfiuco:
Hi Tomoms, can you post the link where the upstream Official LineageOS realeas the builds?
[ONE Android Development] @pranit:
Please do something for HEVC playback