yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
Hello! A new build is up on Mega. I've merged all the changes implemented by LineageOS, and there's a lot of them: most notably, you can now see WiFi networks and BT devices directly from the quick settings tile (as in Nougat & Oreo), and the Do not disturb function has been re-implemented, I think, and now it's like Oreo's DND (which is a huge improvement IMO: Pie's DND is poorly implemented & really confusing).

June's security patches are included as well.

I've also implemented a few small tweaks and optimizations, which may improve app opening speed.

Yesterday I clean-flashed my ROM, and unfortunately I started noticing that the volume warning popup crashes SystemUI, as reported by [MENTION=6021430]xymonx[/MENTION]. This might be related to Substratum; anyway, in this build, the volume warning popup has been completely disabled. This is not an ideal solution because, if I recall correctly, the law - in some countries - requires this popup to be displayed for the safety & health of the users. Let's hope I don't get arrested before I find a way to fix this bug :D
[ONE Android Development] pranavrocksharma:
Is selinux with enforcing working with all sensors like lineage os
[ONE Android Development] Tomoms:
No, but this bug is my main concern at the moment. Be patient and I'll sort it out :)
[ONE Android Development] pranavrocksharma:
Ok , thanks for working so hard for this rom
[ONE Android Development] :
[MENTION=5727088]Tomoms[/MENTION] just make sure you're using a VPN ?
[ONE Android Development] Togheter:
This is a very good ROM, been using it since Oreo releases. But my main concern was that there's a problem when a I send Videos or Gifs in WhatsApp. At the beggining, the video starts processing, but the whole app hangs, making me to force close it. When I do it, and reopen it, the video starts processing again, but normally, and sends itselfs correctly. Been happening since Oreo builds. What's causing it? How to track the issue origin? Regards!
[ONE Android Development] JT1510365:
Do you have a direct download link to just this build that you just made. I tried clicking the download link in the OP but that takes me to a mega link that is 5 gbs in size and that's too much to download for just one build I think and I have a WiFi limit data cap at my place so that's too much thanks in advance
[ONE Android Development] Tomoms:
I'll give a look at this ASAP & let you know what I find out.

The link in the 1st post points to my Mega folder that is so big because it contains all the builds of this ROM. You just have to download the one you want ;)

Anyway, here's the direct link: https://mega.nz/#F!FoNHkCaA!m7eXUf7HbBiJbM9l3cPOtg?c18k1Y5D
[ONE Android Development] gil80:
Hi [MENTION=225757]TomTom[/MENTION]

I don't know if it's been identified or not, but I stumbled upon a major issue for my use case.

To get the sensors working, I need SELinux permissive patcher.

The SELinux permissive patcher breaks Magisk SafetyNet check and Magisk Hide. Magisk manager is: 7.3.1 (222) and Magisk version: 19.3 (19300)

The test I've done was to install the latest Magisk and check Magisk Hide and SaftyNet check, then check sensors using Phone Check app. The app displays that no sensors exist.

Then flashing SELinux permissive patcher, sensors are now working but anything Magisk related (exept Su permission) is broken.

I'm using your ROM with build 20190428. I didn't want to update yet because I was hoping to update once there's a fix for the sensors issue.
[ONE Android Development] Tomoms:
An announcement that might interest you:

https://xdaforums.com/oneplus-one/development/kernel-argon-kernel-t3833348/post79752530
[ONE Android Development] Tomoms:
Hello! A new build is available here.

This one includes all upstream (LineageOS) changes + a small improvement for f2fs filesystems, which may slightly benefit power consumption. Also, I've implemented updated versions of some external libraries.

The fix will come when I have got time to actually do some testing & try to solve the problem. This means, not before the end of the next week. In the meanwhile, I strongly suggest you to update to my latest build. The number of changes, improvements and upstream updates included is totally worth it.
[ONE Android Development] :
I was able to get all of my previously mentioned magisk modules to work with selinux permissive patcher on the the 20190611 release of the rom. (Haven't tested 20190622 yet)

I first installed magisk and all the modules I wanted and rebooted to make sure they were all fully initialized. Then flashed permissive patcher over it. So far from my testing the only way to properly uninstall magisk with permissive patcher is to do a clean install of the ROM. In my case that's each security patch or whenever I have the time.
[ONE Android Development] gil80:
I had to flash a different ROM, also Linage based but with SElinux enforcing and sensors working and Magisk working.
[ONE Android Development] :
Edit: off topic
[ONE Android Development] dabanhfreak:
Just installed 2206 and had problems. Play Store closing, Lastpass closing (it's in my quick settings) and my phone app mysteriously disappeared (I installed the Google version)

Now running TWRP restore.
[ONE Android Development] Tomoms:
Hello!

I just wanted to let you know that a new build will come out as soon as Lineage merges July's security patches (which will happen very soon, I guess). It'll be a very small update because - as usual - there are lots of things I'd like to try/test/fix (such as sensors with Enforcing SELinux!) but I've barely got time to sync and rebuild, during these weeks (I'm doing some important kernel work as well).

I'll keep you informed :)
[ONE Android Development] Tomoms:
Hey there, the new build is up!

The changelog is in the first post, this is a minor update, synced with LineageOS and with a couple of minor tweaks here and there :)
[ONE Android Development] Dr.SAM88:
LOS16 Clean install with no additional flashes, not even gapps (wiped everyting, i'm on twrp 3.3), it doesn't even go past the 1+ logo, it bootlops endlessly.
[ONE Android Development] Tomoms:
Very unusual issue + no logs = I'm disregarding your post, sorry.

I don't want to sound rude, but how many times do we devs have to repeat that you users have to provide the frigging logs whenever you report an issue?
[ONE Android Development] Tomoms:
Sensors fixed!

Good morning/afternoon/evening/night people!

I've got some wonderful news :)

After months, I've finally managed to fix the sensors problems: now all sensors are working when SELinux is Enforcing! However, I'm not ready to release a new build now because I've got to check a couple of things first, and given that I'm going on holiday tomorrow (for one week), you'll have to wait until the very last days of July before you can get the new build.

Thank you for your patience :)

[MENTION=3184773]gil80[/MENTION] I think this will interest you!
[ONE Android Development] gil80:
That's great news!

Thanks for your efforts.

I'd love to try this ROM again.

p.s. I'm currently on TugaPower ROM. One killer feature is the built-in call recorder. Do you believe it's possible to implement it in this ROM?
[ONE Android Development] Syaani:
Wow, you made it! Maybe I'll try your Pie soon :) Have you looked the Whatsapp video etc. problems some users reported? I'm also wondering, how is the GPS lock in Pie builds? These are the issues that always bothers me when thinking the version update. But anyway, nice achievement!
[ONE Android Development] Tomoms:
There is an inbuilt call recorder in my ROM & in official LineageOS too. In fact, I used it not long ago. It might be disabled/hidden, however, if you live in a country where call recording is prohibited.

The WhatsApp/Telegram media issues have been solved a long time ago. GPS lock sometimes is very fast, other times is quite problematic, anyway I haven't tested it in a while. Next week I'll be outdoors most of the time so I'll test it again and let you know :)
[ONE Android Development] Bittornado:
Indeed great news if the sensors issue can find a solution!

This bug has been killing me?

I'll look forward to test your upcoming build update ?
[ONE Android Development] :
Is there support in the kernel for OTG-Y cables? I've been looking to use my OnePlus One as a solar-powered mobile file/web server with my unlimited data plan
[ONE Android Development] pranavrocksharma:
Thanks a ton
[ONE Android Development] Tomoms:
Hello! I'm back home after my holiday, I still haven't released the new build because, for some reason, there's a problem in the kernel that causes the CPU frequencies to be set at very bad values by default. Obviously, this need to be fixed before I can publish a new build! Fortunately, I'm pretty sure I know what's causing this, so within a couple of days I should be able to get this issue fixed and then release a new update (and Argon kernel v16). Trust me, it'll be worth the wait!

Thank you again for all the kind words and your patience :)
[ONE Android Development] Tomoms:
The new build is up!

In addition to the sensor fix, it brings Android Q's animations and WiFi icons, plus some other small bug fixes & improvements. The kernel is Argon v16, which I'll release separately later today or tomorrow.
[ONE Android Development] ralpyka:
Thanks for the new build!

It would have been nice to replace also the other icons to Android Q style, the WiFi icon like this just doesn't fit in :)
[ONE Android Development] Tomoms:
While I agree with you that I could replace all icons with the Android Q icons, I have to say that I couldn't find the commits that implemented the other icons, and what's more, I don't think the new WiFi icon doesn't fit in with the others. Anyway, should I come across a way to implement more Q icons, I'll add them for sure.

EDIT: [MENTION=6474041]Syaani[/MENTION] I've used GPS with Google Maps twice in the past 2 days and it has worked perfectly. The fix was accurate and quick.
[ONE Android Development] dabanhfreak:
Deleted
[ONE Android Development] oviung:
Hello. I'm having a problem with the display option "Prevent accidental wake-up". It doesn't seem to work...

I installed the latest rom release with a clean flash.

Does anyone else have this issue? Attached a log, if it helps.

EDIT:

The issue can be temporarely fixed by checking the proximity sensor with a sensor testing app. But after some time it will stop working again. It can be reproduced like this:

1. Test the sensor

2. Put your palm close to it and tap the screen repeatedly (sensor will work, screen won't turn on)

3. Keep tapping while removing the palm

4. Keep tapping while putting your palm in the range of the sensor (<5 cm) (screen will wake up, although it shouldn't)
[ONE Android Development] daniga74:
Hi, on Pie does it works native screen casting and manual network scan?
[ONE Android Development] Tomoms:
I can confirm the issue but I have no idea how to fix it. Do you by any chance know if the issue exists on official LineageOS as well?

Screen casting doesn't work on Pie, manual network scan does!
[ONE Android Development] Zayphod:
Hello, I clean flashed the ROM and now my wi-fi connection is slow as hell and i'm experiencing connection drop-offs or "Connected, no Internet".

Is there any other firmware/modem compatible with LOS 16 that I could try?

P.S. Flashed bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip and so far so good - no drops, wifi connects instantly and the speed is back to normal.
[ONE Android Development] m_a_k_s:
Hi,

After clean install I cannot connect to my wifi if SSID is hidden. Even if I manually add network setting (SSID and password) there is no auto connection. I've changed modem to bacon_firmware_update_2016_1-25_.4.0.1.c7-00011 but that is not the problem. I can connect to any network in my work (stable, no drop-offs) but SSID there is visible.
[ONE Android Development] :
[MENTION=5727088]Tomoms[/MENTION] I don't know if you use viper4android, but your latest rom release broke it. Specifically the viper4androidfx reborn magisk module. It's reproducible every time, status says "Abnormal" neon enabled says "no". Tried compatibility mode, and ticking "attach audio effects". Tried with and without audiofx system app installed and same results.

I would have loved to provide you a kmesg, but I can't for the life of me find where it's stored in root now. I've been searching all over the internet and can't find anything that mentions a valid location for kmesg. I'm at a loss here lol

Edit: reverted back to your 20190710 release and all is working fine, with selinux disabled of course.
[ONE Android Development] Tomoms:
This Viper4Android works: https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651

I'm using it, it's perfect!

BTW, the path is /proc/kmsg :) And you can print it in a terminal by running

su -c 'dmesg'
[ONE Android Development] JJohnson1988:
Yes, the version on XDA Labs seems to be the most recent as well as the most seamless and reliable.

I didn't even know it existed for a while since I was just using the dated (legacy) Magisk module.
[ONE Android Development] Tomoms:
I've uploaded a new build!

It's got August's security fixes + more UI stuff ported from Android Q (animations & icons).

Also you can now open Settings directly from the notification drop-down menu. No need to expand the Quick Settings menu.
[ONE Android Development] :
That's the one I'm using, the same version and everything. Just the magisk installer. I tried the link you sent me and I'm still getting abnormal status. Am I doing something wrong?

Thank you for the kmesg info, I have the kmesg now but I can't upload it here to XDA. Tried zip and just plain kmesg, it spins on uploading forever.... Ugh

Edit: I must say though... The f2fs speeds have quadrupled. Especially when waiting for partition details in recovery. Amazing work!!

Edit2: I'm going to try cloning my storage, doing a full storage wipe and starting over with f2fs. It's likely some weird corruption problem that appeared over rom upgrades and newer f2fs versions. Since I need an extra long boot password, I'll do what I did before and start on your Oreo rom where I can change the password manually in terminal. Then I'll clean flash your latest August release over this fresh f2fs installation
[ONE Android Development] :
I had to go through Google drive, and for some reason I can't PM you or any Dev so I'll just link it here again

https://drive.google.com/file/d/1n4sDwQp2ATl0r9P-JNZdkc74CIrRFmG2/view?usp=sharing
[ONE Android Development] Tomoms:
You sent me /proc/last_kmsg, which is the kernel log that was saved the last time you shut down your phone. Thus it does not contain any information about anything that happened since the last time you powered it on. You tried zipping /proc/kmsg but the process seemed endless? It's normal :) /proc/kmsg is the current kernel log, thus there's always something that's being written to it, it's a file that never gets closed, thus you can't zip it! The correct way to read it is opening a terminal and running

su -c 'dmesg > /sdcard/kernel.log'

This way, you'll save a copy of /proc/kmsg into /sdcard/kernel.log.

Anyway, a kernel log won't help me understand what's wrong with your Viper setup. Since that version of Viper must work on my ROM because I'm using it, try this:

open AudioFX, disable it through its toggle

completely remove Viper's Magisk module

reboot your phone

if Viper is still there (e.g. because you installed the one I suggested on top of the Magisk module) uninstall it

reboot again

install Viper from this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

open it up, grant root access, install drivers & reboot
[ONE Android Development] :
Thank you so much for clarifying, I had no idea.

Good news actually! I figured out the problem and solved it, didn't need to do a full storage wipe!

My ROM got corrupted because I didn't run a fsck on /data /cache and /system before flashing the magisk zip in recovery. Viper4androidfx reborn v2.7 magisk module is working perfectly now. A good thing to note for f2fs users looking to future updates!

Edit: fsck.f2fs must clear the filesystem cache, which makes sense when updating it with changes. Running a fsck on /system repairs any damage that was done.
[ONE Android Development] :
I spoke too soon, my rom got corrupted again while restarting. 20190710 release of the rom doesn't corrupt itself with f2fs /data and /cache. Something must have changed with one of the f2fs backports maybe?
[ONE Android Development] Tomoms:
It's possible that those f2fs backports I've implemented a few weeks ago are giving problems. I'll remove them & build a new kernel, then I'll send it to you. If you can try everything again and let me know, it'd be great.
[ONE Android Development] xda_xxx:
Hi, Tomoms. Is there any new information about connecting to hidden wi-fi? Latest build of LOS15.1 still has this problem.
[ONE Android Development] :
Ok will do. Thank you for your time ??
[ONE Android Development] oviung:
Tested and yes, it's also present in official LOS. I'll file a bug report.

BTW you forgot to update the latest release link in your OP
[ONE Android Development] Tomoms:
Fixed, thank you!

By the way, a new update is already coming, with a couple of small improvements and support for OTA updates!
[ONE Android Development] ze7zez:
5000 thanks ;)
[ONE Android Development] Tomoms:
Hello! The new build with the OTA updater and a brand new version of my kernel is up! More details about this new Argon kernel release will follow in its thread.

The OTA updater allows us to install the upcoming builds directly from the Settings app, no need to download the build separately anymore :)

EDIT: there's a bug that prevents the CPU's max freq. from being capped down at 1,9 GHz on boot, thus the max frequency is 2,8 GHz. I know it's not a nice thing, because it causes overheating during the first boot, but I forgot to fix it. Anyway, there's a workaround! Just replace this file

/system/vendor/etc/init/hw/init.qcom.power.rc

with the one I've uploaded here. Sorry for the inconvenience.

;)
[ONE Android Development] skymera:
chmod 0644 necessary for that file?
[ONE Android Development] Tomoms:
The permissions should be already set, anyway, double-check it upon replacing.
[ONE Android Development] :
[MENTION=5727088]Tomoms[/MENTION] did you get my PM about f2fs still causing corruption on the latest rom releases past 20190710? I tried the kernel you PM'd me reverting some of the f2fs backports but it still ends up corrupting upon first reboot.

I wonder if I could flash the old argon kernel over the latest rom release to keep f2fs working for now?

---------- Post added at 10:28 PM ---------- Previous post was at 10:11 PM ----------

There's actually a magisk module to bring back screen casting support, it's supposed to be universal. Might be worth a try ??*♂️

Edit: merged your fixed qcom power file in to my 20190710 rom install, works great ??
[ONE Android Development] diegomsg:
Great update, working fine.

Dirty flashed it couple weeks ago. A minor issue was solved with this update (or prior that I didn't applied): with earphones plugged changing volume caused system crash

Now it's all fine and stable
[ONE Android Development] WilderSu:
Battery usage is way worse with the newest version, I don't have any services installed, be it gapps or microg, it's pretty much clean rom, so it's very easily noticeable as it turns weeks into day or two. I'm rolling back for now
[ONE Android Development] Tomoms:
I haven't noticed this. I would have needed a log to understand what's going on on your side.

Yes I got your PM but I'm away from home and I'll be back next week, so there's not much I can do. I'll try the Magisk module and report back.
[ONE Android Development] trynex:
Seems like there is some hope for screencasting...
[ONE Android Development] luka18697:
I noticed that when I'm connected to a 2,4GHz WiFi or I'm tethering using the 2,4GHz band and have localization on the network speed drops to around 3-4Mbps (and the ping skyrockets to 130-200ms). When using the 5GHz band or disabling localization the speed get back to normal (55Mbps, 15ms ping). I read on various forums that it's a common issue on Pie, but for most people it happens when bluetooth is turned on. For me bluetooth isn't making any difference.

P.S: The battery life isn't great (I've been using LOS 14.1 by sultan for the past months). The screen-off consumption is better, but the screen-on consumption is way worse (like 25% usage in an hour, on sultan's ROM it was like 16-20%). Also I think that the CPU speed is not limited to 1,9GHz (I tried applying the fix that was posted a couple of replies back).
[ONE Android Development] hithold:
I also replaced init.qcom.power.rc with fixed version, it doesn't help, max frequency is stil 2.88GHz
[ONE Android Development] :
Yeah I noticed my phone still gets pretty hot when booting up. I'm on 20190710 though so I wasn't expecting much since it's not latest release
[ONE Android Development] Tomoms:
Strange. We'll see if the permanent fix I'll include in the next build fixes this for good. What's weird is that replacing the file solved it for me.

You can replace the same file on that build as well.
[ONE Android Development] :
I've noticed even on the 20190710 release, running f2fs on /data and /cache using the latest cm13 firmware, every week or so the phone will just disable the Sim card as if there isn't one in there. I've tried pulling the sim card out, putting it back in. Rebooting. The only thing that fixes it is going in to recovery, running a fsck on /system /data and /cache, then wiping dalvik and cache partition. Rebooting afterwards fixes it for another week or so.
[ONE Android Development] Tomoms:
Hey guys, this time I'm the one facing an issue and I'd like to ask you if you're noticing this as well. Starting from when I clean flashed one of the July builds, the phone becomes very very slow and laggy during the installation of apps through the Play Store (not while downloading, only while installing them). It didn't happen before. This is something that I would expect to happen on an old, low-end device (in fact it happened on my older phone), not on the OPO; what's more, it really bugs me that it started happening all of a sudden. Are you guys facing the same problem on the latest 3 or 4 builds?
[ONE Android Development] luka18697:
I clean flashed the latest Pie build (18/8) and I'm having the same issue.
[ONE Android Development] Tomoms:
Only if you have some spare time (since I won't be home for a few days), could you try to flash some older build to find out which is the first one on which this problem appears? Otherwise I'll do it next week.
[ONE Android Development] :
Honestly apps install pretty quick for me with /data and /cache formatted as f2fs. The only issues I have is apps installing in the background would just quit if the screen turned off. Going in to power optimization settings and whitelisting my app stores seems to have fixed it.