yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
Actually, the last time I checked LED & sensors on Enforcing was quite some time ago. I'm pretty sure that LED works on Enforcing now. If on official LineageOS 16 sensors are working correctly on Enforcing, then they should work the same way on my builds. I just haven't checked.

By the way, the next build will feature: increased smoothness (thanks to a priority boost for some process that are critical for user experience), libjpeg updates (properly implemented, no WhatsApp/Telegram crashes anymore!), auto face unlock, and probably some other tweaks/useful features.
[ONE Android Development] gil80:
Unfortunately, sensors are still not working on enforcing.
[ONE Android Development] ralpyka:
Please make the auto face unlock configurable through the settings. I'm using the trusted devices feature from smart lock, and the auto face unlock can interfere with this too (I'm turning on the screen, the phone detects the bluetooth device because it was just woken up, and it skips the lockscreen, which is not something that I want because it makes the phone unpredictable (because sometimes it skips the lockscreen and sometimes does not)). Thanks
[ONE Android Development] Tomoms:
Don't worry, it'll be on by default, but there will be a toggle in Settings!

I'll check this issue when I have time. This won't be very soon, unfortunately.

--

Manual mobile network search will be fixed as well :)
[ONE Android Development] WilderSu:
What about hotspot turning? Is it a know issue? sometimes I have to try it 4-5 times to turn it on.

That being said I'm getting insane idle times with this ROM [LOS 16] like 1% per 15h insane, I'm not using any gservices or microg though, it's just a phone ;] Was something changed with deep sleep recently?
[ONE Android Development] Tomoms:
Hello!

I've uploaded the new build :) It's dated May 2nd and not May 3rd because I built it yesterday.

This new update is a big one! It's based on the latest LineageOS code base and it features: the fix for manual mobile network search, updated libjpeg-turbo (WhatsApp & Telegram crashes are now permanently fixed!), some user experience optimizations, and some fixes in the kernel.

Additionally, there are also three useful new features: support for signature spoofing (allows users to install microG), auto face unlock and manual reset of battery usage statistics.

Let me know your opinion on this update!

Bye :)
[ONE Android Development] ze7zez:
Are you sure you uploaded correctly on AFH?

I have a message:

OOPS!

no mirrors found.
[ONE Android Development] Tomoms:
AFH is often broken, use Mega instead.
[ONE Android Development] gurashish1singh:
Great rom! Pretty fluid, experienced no lag so far. One question I had was that how do I go on about changing the root access in the trust settings ?
[ONE Android Development] Tomoms:
A new release is available

I've uploaded my latest build from yesterday.

It includes May's security patches, all the latest changes by LineageOS, and many improvements in the kernel (f2fs backports and some bug fixes).

Only available on Mega at the moment: click here!
[ONE Android Development] :
Has anyone tried encryption with f2fs after the recent backports in Argon kernel?
[ONE Android Development] :
I think it's the lack of arm neon support. When I install viper4android on nougat and above, the line that says "neon enabled" is gone. I wonder if this instruction set is needed to access the snapdragon 801 dac?

Edit: I also wonder, if the solution for now is to use a Bluetooth adapter for your analog audio system. Correct me if I'm wrong but that would not require a dac to be used, making high res audio possible
[ONE Android Development] Tomoms:
The NEON instruction set is supported in all kernels for the OPO, you can check it by installing any app like CPU-Z or Aida64 on any ROM. So I think this shouldn't be the problem.

By the way, I'm using Viper4Android installed through the Magisk module, and I still can see "NEON enabled: Yes" in the "Driver status" section.

EDIT: I'll release a new build very soon, with new updates for jemalloc and sqlite.
[ONE Android Development] pranavrocksharma:
Error 70 gapps is coming, this is first time i encountered such error , tried to resize but still not solving my problem
[ONE Android Development] Tomoms:
The new build is up! I won't use AFH anymore, it's way too problematic. This build is only available through Mega, thus, and the same will apply to the next builds.

This new release contains updates for jemalloc and sqlite, all the latest LineageOS changes, and a small improvement in the kernel that could give us additional ~8 MB of free RAM.

Download it from here.

Enjoy :)
[ONE Android Development] Syaani:
Hello all! What are the exact sensor issues with enforcing selinux policy? Do you know if official Lineage OS 16 builds are affected too? I really wouldn't want to run my system as permissive but I'm interested to finally update from Oreo to Pie some time this summer. Currently running your 15.1 build from October, I really appreciate your work! [MENTION=5727088]Tomoms[/MENTION]
[ONE Android Development] Tomoms:
A quick recap for you:

sensors aren't working with Enforcing on my ROM...

...but an user said they are working with Enforcing on official LineageOS.

I haven't tried the official builds, but I trust this user, even because Lineage's guidelines state that in order to have official builds, a device should have Enforcing SELinux and all sensors should work properly.

-> Thus, I'll have to give a look at this issue as soon as possible.

In the next week I'm going to wipe my phone and reflash everything cleanly, because I usually do so once or twice a year, so I'll take advantage of this occasion to try the official builds, grab some logs, and see what I can do to fix this issue.

And thanks for the kind words :)
[ONE Android Development] diegomsg:
Great ROM, thanks. I was using arrow before and it was great, full of addins and customization, until it compromises battery and performance.

Using Tomons ROM as daily system showed good enhancements without loosing performance and battery life

Congrats and if you keep upgrading we will keep flashing it

The only issue is the sensors bug, known, resolved with permissive SElinux. I personally don't see as a big, cause other ROMs don't let you choose between enforcing or permissive, they just throw you permissive and 100% functionality

Tomons let you choose between enforcing without all sensors or permissive with complete system working. Great job
[ONE Android Development] gil80:
Thank you for deciding to try to fix the sensors/led with selinux enforcing :)

On a different matter: Did you ever encounter random reboots?
[ONE Android Development] Tomoms:
Very very rarely. Like once every month or two!
[ONE Android Development] Saison2018:
I use this ROM on my OnePlus One as a second phone. Mainly usage is game, XDA app and some other stuff (weather,...).

My phone reboots on average one a week or more.

My last reboot was yesterday evening: was playing "Star Wars: Galaxy of Heroes" https://play.google.com/store/apps/details?id=com.ea.game.starwarscapital_row&hl=en

Phone froze and rebooted. It is stable until now.

Tell me if I can help to find the culprit.

[MENTION=5727088]Tomoms[/MENTION]: Question: Does rotation is supposed to be fixed? My screen never rotate.

Thanks
[ONE Android Development] Tomoms:
After the reboot, grab /proc/last_kmsg and upload it here. Rotation doesn't really work for me as well; I remember I had merged some fixes for it but they might have gone away while rebasing my code on top of Lineage's. I'll look into it in the weekend.
[ONE Android Development] Saison2018:
My phone rebooted tonight.

I went into TWRP and check many times, I do not have "/proc/last_kmsg", only "/proc/kmsg".

I know this sound silly but I can assure you I have double and triple checked before writing.
[ONE Android Development] Tomoms:
It's not silly at all xD

That file is deleted during the first reboot after a random reboot. If you hadn't manually rebooted to TWRP after the random reboot that occurred in the night, it would have been there.
[ONE Android Development] Saison2018:
Could you please tell me the best way to get the file after a reboot?

I would like to help and it seems I am not doing the right thing.

Thanks in advance
[ONE Android Development] Tomoms:
It's simple :)

The reboot occurs -> you wait for the phone to finish booting up -> you grab the file! This is not possible, however, if you haven't got root.
[ONE Android Development] Saison2018:
Thanks, I feel less idiot! :)

About root: Does installing LineageOS Addon (https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm-signed.zip) in TWRP is supposed to give root right?

I did it in previous LOS version, but it not seems to work in your rom. Maybe I did something wrong.
[ONE Android Development] Tomoms:
Never tried it, I've always used Magisk. It's possible that Lineage's devs coded something that prevents their addonsu from working on unofficial builds.
[ONE Android Development] Saison2018:
Thanks, I will root with Magisk and grab file after next unwanted reboot.
[ONE Android Development] Saison2018:
Back to home, rooted with Magisk, Installed Syslog application, opened game, less than 1 minute and phone rebooted.

Here are the logs, hope this will be helpful.
[ONE Android Development] Saison2018:
[MENTION=5727088]Tomoms[/MENTION]

Another reboot this morning. Unfortunately there is no "/proc/last_kmsg" (I do not why because I have let android reboot and did nothing else).

My game was minimize for some minutes and when I went back, phone rebooted not long after starting to play again.

Maybe it is a clue: Everything was stable until this morning when I decided to reactivate my ad blocker (DNS66). I will do more test (with and without DNS66) and also with another product like this one to verify if it could be a cause. Hope this help.
[ONE Android Development] Tomoms:
Yes, another user had already reported this but I haven't looked into it yet. Do you have any clue whether it works on Sultan's builds?
[ONE Android Development] Angrydr0id:
Nope. I didn't install the sultan ROM. :/
[ONE Android Development] :
Are you guys talking about the feature that unlocks the phone as soon as you enter the right PIN without requiring further submission?

If so, the CM team removed it a while ago because of security reasons (brute-force would easily break it) and as you know Sultan always syncs to the latest upstream, so..

You can find a screenshot of the PIN settings on his latest build attached to this reply.

As you see I'm not using this ROM but it will be on my One as soon as I have time to flash and play a bit. Meanwhile, may I ask if Wakelock Detector works on this build? I'm asking because I have problems with magisk and latest Sultan's build.

Thanks in advance!
[ONE Android Development] Tomoms:
I'm also synced with main LineageOS however I have the switch for Quick Unlock. It's not in the section of Settings you posted the screenshot of, it's in the generic Security section, between the type of Lock Screen selector and Smart Lock.

About Wakelock Detector: I have never tried it so I can't tell if it is working or not.
[ONE Android Development] :
Seems that I can't find it anywhere :confused:
[ONE Android Development] Tomoms:
That's Sultan's build right? If so, I'll remove the option from my ROM, as it must have snuck in accidentally for some reason. Thanks for your screenshots.
[ONE Android Development] murti52:
Here's the screen shot of that setting.

Secondly that setting doesn't work as others have reported, but since i am using xposed, there is a similar option in gravity box. That option works once i enable it in the module.
[ONE Android Development] MaestroCharan:
That's a nice theme you have there!

Could you pls tell what theme is it?

[MENTION=5727088]Tomoms[/MENTION],

It's really great to have you present us with your work.

You really filled the gap!

I, like many, for long l, was looking forward to work like this one.

Thank you for your understanding of other's desires! :angel:

I Thank you for your support.
[ONE Android Development] murti52:
Cosmos substratum :good:
[ONE Android Development] Tomoms:
Hello!

There's a new build on AndroidFileHost - it's dated 20171111 because I actually built it yesterday. I hadn't even made it thinking of releasing it publicly, because I wanted to remove the broken Quick Unlock feature before releasing a new update, but then I saw the new ROM was working well so... Why not publish it? And here it is :)

As usual, together with the ROM comes a new Neon kernel release (v13), and as usual, this new kernel is already included in the ROM.

Enjoy the new build!
[ONE Android Development] secretkloud:
Awesome. Thanks a lot!...
[ONE Android Development] Tomoms:
Small announcement: I just realised that the kernel provided in the latest build of this ROM is

not

Neon v13: it's 99% similar to v13 but it's missing one single patch that could improve a little bit the general performance of the phone. So I suggest you to flash Neon v13 on top of the latest build to be as up-to-date as possible :)
[ONE Android Development] :
Just installed latest build: it seems to perform pretty well!

Since it's declared to fully support OMS, I've tried to apply some layers for the first time but I'm wrong at something (I guess)..
[ONE Android Development] Tomoms:
What is bothering you? The fact that the app says this ROM is not supported? That is not a problem at all. Use OMS-compatible themes and you're good. They work as they should.
[ONE Android Development] :
Yeah, forgot to mention that I tried applying "Pixel UI" by xdnax apps and I couldn't manage to theme the navigation bar. The developer claims that this happens when the ROM doesn't fully support OMS and that's why I asked

Could you have a deeper look into it if it's not a problem?

Thanks in advance!
[ONE Android Development] Tomoms:
Oh, the navbar... It's the only part of the UI I have never tried theming because I keep it hidden all the time, due to the fact that we have hardware buttons. I'll look into this problem!
[ONE Android Development] secretkloud:
[MENTION=5727088]Tomoms[/MENTION]

Just to let you know that your ROM is still doing very well. Thanks again for the build and hope you'll still provide updates...
[ONE Android Development] Tomoms:
I'm glad it's working well. A new build is in the works, but I'll be quite busy in the next days; anyway I think I'll manage to release it in a week.
[ONE Android Development] JT1510365:
Nice to see you here developing for our one plus one:) I love flashing ROMs on my one plus one and I would love to try this one in multirom so could you tell me if you fixed the developer options force closing when this ROM is secondary in multirom. I think its a commit you need to add but anyways I am going to test this ROM in primary slot first
[ONE Android Development] anzi2001:
You could always try uefi boot manager since it doesnt need kexec patch :D
[ONE Android Development] Saison2018:
[MENTION=5727088]Tomoms[/MENTION]

Another reboot and another logs files. Hope this will help.

I am now almost convince that DNS filtering (DNS66 or AdGuard with DNS filtering) is the reason why the phone reboots.

I am using AdAway and phone still reboots but less frequently.

I am not sure why (your rom or latest Android OS version difference with previous one) but behavior seems prouve that fact.
[ONE Android Development] :
My apologies, you are 100% correct lol
[ONE Android Development] xymonx:
Hi [MENTION=5727088]Tomoms[/MENTION]. I've been using your LOS16 builds for months now and I am very grateful for them. They mostly are perfect. There is one issue I have though, when I turn up volume on headphones too high, whole UI restarts. It seems to be connected with too high volume warning ("listening on high volume for prolonged period of time can be harmful blabla") - the warning never gets shown. I have a workaround that involves modifying the output loudness in viper4android but if you could look into this it would be great, as it is annoying. I use your rom with gapps, magisk, viper4android, and substratum (no themes installed nor used though). Thanks so much!

And one more question, I saw that LOS recently brought back WIFI/BT selection from quick settings dropdown menu, will it be included in your rom? Like this https://i.imgur.com/7qSpvzV.png
[ONE Android Development] pranavrocksharma:
My phone is not detecting under Android auto in this rom, please kindly look into this issue, selinux - permissive
[ONE Android Development] Tomoms:
The "harmful volume" message pops up every now and then on my phone as well, and it works as expected, it doesn't crash SystemUI nor it has any other unwanted side effects. I'm using ROM+ Gapps + Magisk + Viper + Substratum (with theme applied). Today or tomorrow I have to wipe my phone and perform a fresh, clean install of everything, I'll check if what you described happens, for some reason, when no theme is installed. Anyway, you could grab a logcat and send it to me, it would be of help.

About WiFi/BT selection, I'm glad it has been brought back, and if standard LineageOS has merged it into its sources, then it'll be included in my next build (you can expect it to be available within a couple of days!).

Logs please! I barely know what Android Auto is...
[ONE Android Development] :
????☀ Rejoice!!! ☀????

Full storage encryption with /data and /cache as F2FS works flawlessly for our device now!

I've even managed to set an extra-long (longer than 20 characters) encryption password!

For anyone who wasn't already encrypted (most likely you won't be if you're trying F2FS encryption anyways) - pie removed the ability to run cryptfs within terminal emulator for "security and usability reasons". This is sad because they don't allow you to use a password longer than 20 character. To take advantage of the latest F2FS commits, I flashed Tomom's latest pie on a completely fresh F2FS install. Booted up, began full data encryption. Downloaded Tomom's latest Oreo, rebooted to recovery, performed a nandroid backup of Tomom's pie. Booted to Tomom's Oreo ROM, downloaded terminal emulator and executed:

su

Then:

vdc cryptfs changepw password [currentpassword] [newpassword]

Then restored to my backed up Tomoms pie rom with my extra long boot password, with /data and /cache as F2FS ?

Only thing I noticed is that I had to use edexposed with microg's signature spoofing module to fully get the system to spoof microg's signature, even though I allowed signature spoofing through the system prompt. I don't necessarily consider this a problem since I already use xposed for blocking ads on Instagram.

I have noticed a few times the phone will lock the screen as if I pressed the power button when my finger wasn't even near it. I'll collect a log for you next time is happens [MENTION=5727088]Tomoms[/MENTION].

I can also play viper4android on max volume through my headphone jack and phone speakers without any audio warning popup. Altogether I'm using systemless micro g, magisk, and systemless bromite system webview along with edexposed. In fact I haven't experienced a single crash and I'm using a heavily customized kernel audiutor-mod profile.

Tomoms you're a godsend. You have created the ROM of my dreams. I love you ♥ also +1 for using maple I/O in argon kernel. I've been advocating/bug testing for maple since MM.
[ONE Android Development] gil80:
Hi.

I don't know if this is only on my phone or it's an issue with version 16 of this ROM.

When I increase the ringtone volume, the whole notification and other sounds are increased as well. There is no way of separating them.

Could this be something to do with mixerpath.xml file?
[ONE Android Development] Tomoms:
1. Yet another weird issue I've never faced nor heard of. Maybe you are involuntarily double-tapping on the status bar? Don't know, just asking :D

2. The high volume popup is very very rare on my phone, but sometimes I see it, I don't really know why.

3. Thank you for the kind words, you make me blush :)

I'm glad you're enjoying my version of LineageOS!

This doesn't happen here on my side. Could you describe your problem with more details? Do you open Settings > Audio to change the ringtone volume? I'm asking for confirmation just because Pie handles volumes differently than previous Android releases (i. e. the volume rockers change media/playback volume by default), so I need to know what should I do to reproduce your problem.
[ONE Android Development] :
You may be right, I'm coming from MM so I'm not used to all these new gestures ? didn't realize the screen locks when I double tab the top bar. I use my notifications quite often, I'll see if I can't turn off the top bar gesture
[ONE Android Development] Saison2018:
[MENTION=5727088]Tomoms[/MENTION]

Did you had the chance to look at the logs for reboot issues?
[ONE Android Development] Tomoms:
Yes, the reboots don't seem to be caused by the kernel. I can't really help you, then.
[ONE Android Development] :
Please delete
[ONE Android Development] :
Ok, I spoke to soon. I enabled Android logging in kernel audiutor after having it disabled for the past few days. Walked in to the house, enabled airplane mode and turned on wifi. Waited for openvpn to reconnect and started playing a YouTube video. Unlocked screen to select another but android was showing wifi had no internet access. Then crash.

https://drive.google.com/open?id=1j85TBlE1BLFGmEVRLTfreqKuHaAnpxt-

I disabled Android logging again in kernel audiutor-mod and so far no crashing.

I've also noticed, that with display brightness set to auto, when swiping between pages on home, using the stock launcher, the screen for whatever reason gets brighter between the pages and goes back to a the dim light it should be at once the page is set. Turning auto brightness off, and manually setting it to my preferred brightness fixes it. This is something I've noticed actually since MM running lightning kernel v50. Has anyone else noticed this?
[ONE Android Development] Tomoms:
I'll check this later and I'll keep you informed.

In the meanwhile, I'd like to announce that the new update will come out today, with (among other improvements) June's security patches!

EDIT: today's build doesn't work, I'll have to figure out what's wrong (I already have an idea). So a new one is in the works :)
[ONE Android Development] Saison2018:
[MENTION=5727088]Tomoms[/MENTION]

FYI, I have made a factory reset and installed Official LineageOS (lineage-16.0-20190608-nightly-bacon-signed.zip) with GApps. Also, restored exactly same applications and Rooted with same Magisk version.

It is 2 days on a row now and still no reboot.

Rotation is working correctly and I feel that touchscreen responsiveness and accuracy is a bit higher in official LOS.

I do not make criticism of your work, I think your rom is fantastic, but I think these informations can give you an hint to try to integrate it in your rom.

hope this will help.
[ONE Android Development] Tomoms:
I accept criticism and I admit that my ROM, for some mysterious reason, has some bugs that the official builds haven't got, despite sharing device trees and 98-99% of the code base. I'm still working to get a functional new build. I'll post a detailed thread tomorrow. In the mean time, let me advise you to flash the SELinux permissive patcher zip I've linked in the first post: all sensors will work properly, thus rotation should work as well.
[ONE Android Development] TheAlmightyOgreLord:
No touch responsiveness issues or sensor issues here, running selinux permissive patcher like you recommend. Glad to see you putting so much effort in to a much needed project for our device. Selinux is annoying but it can be corrected. Your rom provides too many benefits for me to consider the ladder!