yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] N34S:
thanks for the work you're doing with this rom. i admire your work.

in theory i'd have two bugs with this rom, but one of these i discovered to be depended from something else while i tried to reproduce these bugs with a clean installation. so I found that the rom actually has only one of the bugs i found, which is as follows:

in practice, when you disconnect from a VPN, the system freezes and restarts immediately. tried with multiple apps for VPN and the result is always the same.

to reproduce the bug, you need to have an app for VPN connection, grant and connect to one of the servers made available by said app, disconnect from VPN and draw your own conclusions.

[OT] this reminds me so much of the time when i tried to connect to a VNC server using a newer app than the one that continued to work without problems. every attempt was always ending with a self reboot of device. [/OT]
[ONE Android Development] Tomoms:
This bug is easy to fix, as it is caused by a kernel patch that doesn't behave properly. The strange thing is that I thought I had already fixed it in a previous release, some months ago. Maybe I have accidentally reintroduced the faulty patch again. I'll check and let you know, because this should really be a simple bug to fix

EDIT: Exactly as I suspected. A few days ago I introduced the faulty patch in my kernel by mistake. I'll post a new kernel with the fix in a few hours.
[ONE Android Development] Tomoms:
New kernel

Hello, this is a new kernel: https://androidfilehost.com/?fid=4349826312261818966

It brings many source updates and fixes for the kernel's memory subsystem, a new packet queuing algorithm for the network subsystem, and of course, the VPN fix.
[ONE Android Development] N34S:
i'm sorry to have to bring such a disappointment, but even with this kernel i'm experiencing the exact same anomalous behavior immediately after disconnecting from the VPN. also tried with a clean rom installation (+ this kernel) and with two different VPN apps but no luck. i'm afraid that the VPN issue will require a bit more work.
[ONE Android Development] Tomoms:
Instead of reverting the faulty patch, I've applied a correction patch on top of it, assuming it would do the job. It seems this is not the case. I'll revert them both and then VPN will most likely work flawlessly. No need to clean flash BTW. If a kernel fix doesn't work, it simply doesn't, regardless of the state of the ROM. So I'll push a new kernel later today, stay tuned and thank you for your patience :)
[ONE Android Development] Tomoms:
Ok so here's today's new kernel: https://androidfilehost.com/?fid=4349826312261819600

[MENTION=4280079]N34S[/MENTION] it fixes VPN for good, I've tested it myself using ProtonVPN. Also features a few fixes here and there and memory bandwidth boost on screen unlock (boosts performance immediately after unlocking the screen).
[ONE Android Development] N34S:
I use ProtonVPN too, and i can confirm that now VPN connection is working flawlessly. I also noticed how screen unlock has now become faster and more responsive, in effect it was quite slow before. Great job thanks!
[ONE Android Development] Tomoms:
Ok guys so I've finally found a fix for the annoying speakerphone bug. I'm testing it and it seems to be working alright, during phone calls my voice can be heard clearly in all situations (normal call, call using speakerphone, call using headphones). If no issues arise in the next days I'll implement it in my next build, which will come after June's security patches are merged into LineageOS 16. The new build will also feature a few tweaks that allegedly reduce the quality of the system's animations, in order to increase their smoothness. I'm already testing them in a private build and honestly, I can't notice any difference in terms of quality but I do notice a small improvement in terms of smoothness.
[ONE Android Development] JJohnson1988:
I'm also having issues with V4A not working (the classic abnormal status), and the solution is of course to change SELinux to permissive.

But I thought this was a well-known issue and that it was now solved.

Anyway, just wondering if anyone got it to work on this ROM with SELinux enforcing. I've already tried the tricks mentioned in this thread, including the Audio Modification Library and uninstalling AudioFX.
[ONE Android Development] Tomoms:
Hmm... The new Viper4Android available through XDA Labs & Magisk should work even with Enforcing SELinux, and in fact it has worked for me for a very long time, until a few weeks ago. If that's the version you're using as well, it means that for some reason now the SELinux issues are present again (maybe some change in LineageOS?). I remember there was some code I had to inject in the ROM's sources to allow Viper to work with Enforcing SELinux back in the Nougat/Oreo days, I'll try to put it into my sources again, it might actually fix the issue :)

I'm going to try tomorrow.
[ONE Android Development] timbuctoo:
Great battery life!

I switched over from the MSMXtended ROM.

Amazing battery life! Kudos [MENTION=5727088]Tomoms[/MENTION].

Just two nitpicks

the network activity bar is on the center of the status bar; would it be great to align it with the icons on the right side, as is usual

if the LTE icon can be merged with the signal icon, it will save space for another icon on the status bar

These are fixed in other ROMs like MSMXtended. Would it be possible for you to pull in the changes?

Thanks for a very stable ROM.
[ONE Android Development] Tomoms:
If the two things you mentioned are "fixed" in MSM Xtended Pie (not Q), I can try to pull in the changes. Will have a look at them.
[ONE Android Development] Tomoms:
Unfortunately the old trick that used to work in Oreo doesn't work anymore on Pie. I'll try to see which permission is denied to V4A by SELinux, but I don't know if I can fix the issue, SELinux stuff is usually hard to fix for those who (just like me) don't know much about it...
[ONE Android Development] JJohnson1988:
Ah well. Thanks for trying. :)
[ONE Android Development] JJohnson1988:
Kernel panic 100% of the time I try connecting to my IPsec-based VPN. Latest ROM and kernel version. Persists on fresh install. Confirmed not an issue on official LOS.

https://pastebin.com/25wzK1N6
[ONE Android Development] Tomoms:
Please try this kernel: https://mega.nz/file/QllUTACa#tADil61y-iRppPJ0_0LMFMg483hb1tmvYpOUnEVBpds

EDIT: if it still crashes, post another last_kmsg.
[ONE Android Development] JJohnson1988:
No luck unfortunately :(

https://pastebin.com/GUFZmEWx
[ONE Android Development] Tomoms:
This is going to be hard to fix.
[ONE Android Development] JJohnson1988:
If it helps, there was no issue connecting before one of the latest hotfixes regarding the panic on VPN /dis/connect.

Which specific hotfix though, I'm not sure yet. I'll try flashing the 20200509 ROM again and using the kernel included with that one.

---------- Post added at 12:44 PM ---------- Previous post was at 12:14 PM ----------

Confirmed no kernel panic on connect with 20200509 kernel. The /dis/connect panic is still there though of course.
[ONE Android Development] Tomoms:
Very, very helpful information. The issue is still hard to fix but at least I know where exactly it originates from. I'll provide you with some new test kernels in the coming days. I'm sorry that you can't use VPN without issues either at connection or at disconnection :(
[ONE Android Development] JJohnson1988:
No worries, I'm just happy you're still taking your time to support bacon. I think everyone in here appreciates it. :)
[ONE Android Development] Tomoms:
Try this one please: https://mega.nz/file/lt9HwLTB#5UCzWZBbmtnGCQWJSG9Awv9L4lrvZloTO3oBQEEbKL0

Today and in the future, keep providing a copy of last_kmsg whenever you try my one of my kernels and the crash still happens.

EDIT: the new build with June's patches is coming today or tomorrow :)

EDIT #2: it appears that the LineageOS team has already merged in May the fixes that later were labelled by Google as "June's security patches", so the new build won't bring anything relevant with regard to security fixes.
[ONE Android Development] JJohnson1988:
https://pastebin.com/cRELPrxg
[ONE Android Development] Tomoms:
When you provide a log, please also specify whether the crash happened on disconnection or on connection, please. This one should have happened on connection, am I right?
[ONE Android Development] Tomoms:
Please try this kernel: https://mega.nz/file/RodE2KYD#A13yms-yb3QWB0Oopn11EcWTed2ZfjT9VopFZuw_kIQ

BTW, the new build is delayed since I think I'm close to fixing this VPN bug for good. I might wait until I have fixed, so I can provide the fix in the new build.
[ONE Android Development] JJohnson1988:
On connect.

https://pastebin.com/uDACJeC0
[ONE Android Development] Tomoms:
Try this please: https://mega.nz/file/F5l1CBLY#HZrZnCV4wxGoczlLyuLj6DxkRr-bZq3Jew-27J3u414
[ONE Android Development] JJohnson1988:
On connect.

https://pastebin.com/3zq8r9J2
[ONE Android Development] Tomoms:
Sorry for the "insolent" question: are you 100% sure that there was no panic on connection using the default kernel provided in the build from May 9th?

I mean, this is very, very strange. The second-to-last kernel I gave you should have been built from identical sources (same as 20200509), and before building the last one I had reverted even more changes... I'm very surprised. If there was no crash on the 20200509 default kernel, something must have escaped my attention.
[ONE Android Development] JJohnson1988:
I will double and triple check again later today once I've had some sleep.

I do think it's strange that I'm the only one that seems to be having issues on connect. Maybe the type of VPN is the difference. Just speculating.
[ONE Android Development] Tomoms:
Thanks. The type of VPN is the difference indeed. Just dirty-flash the 20200509 build (no wipes needed) and check. It'll be enough.
[ONE Android Development] JJohnson1988:
Re-confirming no kernel panic on the 20200509 build when connecting to the IPSec Xauth PSK type VPN.
[ONE Android Development] Tomoms:
Hmm... I guess we'll have to keep on trying until we manage to get rid of this problem! I suggest that we switch to private messages not to fill the thread with the back and forth of our posts. I'll send you a new kernel to test later today.
[ONE Android Development] Tomoms:
I wanted to release the new build to day but my home Internet connection is not collaborating and the sources sync process keeps failing. I hope I'll be luckier tomorrow.
[ONE Android Development] JJohnson1988:
Some good news is I seemed to have got V4A working with SELinux on Enforcing.

It seems to have been a problem with Magisk. Updating to the canary branch and V4A functions as it's supposed to without any patches or tweaks.
[ONE Android Development] Tomoms:
How strange!
[ONE Android Development] Tomoms:
My new build is up! It should be available through the OTA updater as well; if the download fails, then it means the link has expired. Post here in case of problems.

The new build features lots of user experience tweaks that (at least in my case) seem to give a small, yet noticeable, bump to general smoothness and performance. This is because - among other things - I've disabled the "complex" parts of the animations, so they are faster and smoother, but the animation itself looks the same (or at lease I couldn't find any difference with the previous animations).

This is most likely the second-to-last build of this ROM. I'll probably publish the last one in July and then I'll start working on Lineage 17.1 :)
[ONE Android Development] OnniXx:
Aannd there goes my functioning Viper with the update :(
[ONE Android Development] JJohnson1988:
I don't think it's the update. I think it's just the module or Magisk being wonky.

Half the time when I reboot V4A works properly. Half the time it's back to abnormal status. I'm not sure what that's all about.
[ONE Android Development] OnniXx:
Yeah it's not the update, it was pain to get it to work on previous version too but I got it to work normally and was hoping the update wouldn't mess with it. I was wrong
[ONE Android Development] Tomoms:
There's a new, minor, unexpected update. I've bundled in it all the recent kernel work: now the kernel is built using the very latest GCC 10, I've applied several bug fixes and improvements, and all the VPN-related kernel crashes are officially gone (thanks to [MENTION=5599724]JJohnson1988[/MENTION] for having tested lots of kernels).

There are also some very small tweaks in the device tree.

The update should be already available via OTA.
[ONE Android Development] Anyoe:
unable to clean flash lineage-16.0-20200627-UNOFFICIAL-Tom-bacon-signed.zip after update to twrp 3.4, shows a mkdir error, can you fix that? thank you.
[ONE Android Development] Tomoms:
As you might have noticed, we'll soon get official LineageOS 17.1.

Yeah! Bacon did it once again :)

Despite the fact that I'm probably going to get a newer phone in winter, this has awakened my enthusiasm for bacon. So I'm confirming that I will release my unofficial, optimized LineageOS 17.1, although I don't think it'll come before mid-August.

Don't know how to help you, sorry. I haven't updated my TWRP yet. Does it happen with other ROMs as well?
[ONE Android Development] Anyoe:
i've tested clean flash( wipe Dalvik/System/Data/Cache ) MSM-Xtended/TugaPower and didn't shows the same error.

the error is

mkdir "/cache/recovery/5a79362318d00cf4c316e86435b3ed388dd35082d" failed: No such file or directory
[ONE Android Development] Tomoms:
Don't know what to tell you. Try official LineageOS 16 if you can. If it fails, then the newest TWRP doesn't play well with Pie ROMs. Anyway it's a recovery problem, as the zip is installing perfectly with the older TWRP 3.3.x
[ONE Android Development] dabanhfreak:
With this update I'm getting terrible battery life, around 12-14 hours. I was getting at least 20 previously.

It's a relatively new battery that I replaced about 18 months ago.
[ONE Android Development] N34S:
+1

Battery is draining quickly on the latest build (20200627). My battery was replaced 12 months ago.
[ONE Android Development] Tomoms:
Ok, I'll post here a new build and/or some kernels to test soon.
[ONE Android Development] Tomoms:
Hey guys,

the new build is coming tomorrow :) I'm pretty sure it'll address the anomalous battery drain.
[ONE Android Development] Tomoms:
[MENTION=5139620]dabanhfreak[/MENTION] [MENTION=4280079]N34S[/MENTION]

The new build is up. It'll soon be available through the OTA updater as well.

Please let me know if the battery drain is back to normal again.

Only if it's not, flash this kernel, then test and report back again.

I won't be able to do any work for a week, as I won't be at home, but I'll keep an eye on XDA, of course :)

EDIT: I suggest that you dirty flash this build and wipe cache & dalvik cache. Reboot, let the phone settle for an hour or so, reboot it again, and then start checking your battery life.
[ONE Android Development] indhimaga:
Anyone have a problem with wifi connection after deepsleep... Whatever the battery backup is best than the other roms for now.. Thanks
[ONE Android Development] indhimaga:
Is this the higher fast Charging rate From this rom??
[ONE Android Development] dimzidp:
hi, thanks for this amazing rom and keeping my bacon alive till today. I love this rom. :good::good:

But, there is a problem. I got bootloop after flashing this rom. First time, when I tried to dirty flash 20200509 build from 20200410. Then, I clean flashed 20200509 and everything's okay. Second time, when I tried to dirty flash 20200711 build from 20200509. I used TWRP version 3.3.1.0.

Could you help me with this? Was there some steps i missed before flashing?:confused:
[ONE Android Development] Tomoms:
July's update is available

Hello! I've prepared a new build with July's security patches. This should really be the last Pie build, in fact I'm about to build my first Q ROM (LineageOS 17.1). For this reason, I'd like to know if there is anyone interested in helping me test some initial builds. Most of the things should be already working, but having a few people using the phone and trying features would be great. Things might break every now and then so if you need your OPO to work reliably, this is not for you.

Send me a private message if you're interested.

Of course it's not. If the charger & cable you're using is working better on other ROMs, this means that your charger doesn't play well with the different charging drivers I'm using in my kernel. But these charging drivers work better for many more combinations of charger and cables, so I'm not planning to switch to the other ones. I'm afraid you're just unlucky with my ROM.

Check the md5sums of the files you download (if you update through the OTA, the check is performed automatically, I guess). Other than this, I don't know how to help you. I've been dirty-flashing my builds nonstop since September of the last year, and I've never faced any kind of bootloop, except for the one that occurred some time ago (and in fact, I didn't release the build).
[ONE Android Development] Tomoms:
Work in progress

Hey guys, just wanted to share with you what I have done in the last week or so.

I have successfully built two LineageOS 17.1 builds using the official sources, i.e. the ones that will be used by the LineageOS servers to build our first official nightly. Everything is working fine except for the notification/charging LED, which is broken, probably due to SELinux issues (this is my guess, I haven't actually checked yet).

I've included my kernel and a small tweak that should improve app launching times. My builds also support signature spoofing, in fact I'm already using them with MicroG :)

I've also managed to get Viper4Android working on them without issues, and with Enforcing SELinux!

My builds aren't available yet because I want to implement the OTA updater first, so you can get over-the-air updates right from the start. Now I'm going on a little holiday, when I am back I'll finish up the last things and I'll release the first public build here, together with all the information you need to get them up and running fine :)

Have a nice weekend!
[ONE Android Development] Tomoms:
LineageOS 17.1!

Ok so here we are with my first LineageOS 17.1 build.

This one is very similar to the first official nightly, except for the presence of August's security patches, even though the Lineage team hasn't merged them yet :)

I've only added support for signature spoofing, WakeBlock and a few minor tweaks.

The kernel is LineageOS's default one. I'm thinking of restarting the development of my kernel from scratch, because its performance in Q ROMs is not always good (I've experienced UI/scrolling lags), and if I manage to get in touch with our LineageOS maintainer, I could maybe help with merging security fixes into the official LineageOS kernel for bacon, thus helping also the users of other ROMs.

Anyway, the ROM is super smooth, although there are some bugs which are present in the official nightly as well. Nothing critical though, I might try to fix a couple of them soon.

IMPORTANT

Refer to the thread's 2nd post for some useful information to set up stuff like Gapps, MicroG, or Viper4Android.

A clean flash is required. Upgrading from my LineageOS 16 with a dirty flash is not possible, unfortunately.

Happy flashing!
[ONE Android Development] ze7zez:
.

What do you mean by "my first LineageOS 17.1 build"? :confused:

.

Until today I was sure you made lineage-17.1-20200723-UNOFFICIAL-Tom-bacon-signed.zip

and lineage-17.1-20200728-UNOFFICIAL-Tom-bacon-signed.zip.

.
[ONE Android Development] Tomoms:
It means that you weren't supposed to use those builds, as I had not talked about them in here :)

Those were some initial test builds I had made for myself.
[ONE Android Development] Tomoms:
Hello,

I'm happy - and also a little bit proud :victory: - to inform you that I started making some small contributions to official LineageOS for bacon: I've submitted (and I'll keep submitting) some kernel bug/security fixes that got merged into our official LineageOS kernel. This way, both users of my builds and users of the official nightlies can benefit from them!

Also, our LineageOS maintainer has fixed the LED issue, thus it'll work in the next nightly, and of course in the next build of mines too :)

Talking about my next build, it'll come in a couple of days!
[ONE Android Development] Tomoms:
Hey there, my new build's available!

It bring fixes for some major bugs (LED fix by our LineageOS maintainer, low in-call microphone fix, MTP kernel panic fix), and a few nice tweaks as well :)

The ROM now boots up super fast thanks to the lower resolution boot animation, the kernel supports CPU underclocking and has been improved with ~500 bug fixes, and there is support for OTA updates (starting from the next build, obviously).

You can now install my ROM with OpenGapps nano, because I managed to free up more space in /system, at the cost of removing some fonts. For this reason, some languages could be broken (i.e. special characters may not be displayed properly). If you face such issues, let me know, and I'll add back the fonts in the next build.

When I booted this update for the first time, I found out that most apps' permission had been reset. I'm pretty sure this is an issue with my setup, and not with LineageOS itself or with my builds. Please confirm that your permissions are kept after flashing this update on top of my previous one.

As I suspected, the permission issue is related to my setup. The new build is 100% safe to flash :)

Thanks!
[ONE Android Development] ze7zez:
font packages provided by google

In the absence of a specific font and/or language version in a badly written application that cannot use another similar font,

anyone can download the missing font extracted from the font packages provided by google.

.

I didn't check it, but maybe in the /system/fonts directory after creating a symlink to the missing font placed on the data partition, the application will be "satisfied".

.
[ONE Android Development] david72262:
Nice to see this whole phone is still alive. This was still my favorite phone out of all of them. Best flash friendly phone ever made.
[ONE Android Development] aevan:
Hello [MENTION=5727088]Tomoms[/MENTION],

First of all, I would like to thank you for your hard work to bring us that fantastic ROM :). It’s great to see that today there are still guys like you who are keeping our old device alive!

Since the last release (lineage-17.1-20200811-UNOFFICIAL-Tom-bacon-signed) and the removal of some useless fonts I experience some issues with emojis, I think it is directly related to that (I put a screenshot in order to better explain the problem). In fact, they do no longer work at all .

I also experience an other issue since your first official release (lineage-17.1-20200805-UNOFFICIAL-Tom-bacon-signed) which is, I think, related to Google services. Indeed, I’ve got an notification which pop regularly to inform me that « OK google model update download failed » (I think it is the right english translation, but you can see my screenshots in french to see what I mean). Note I flashed OpenGapps nano as you suggested in earlier post. I tried to clean Google and Google assistant apps with no luck. Have you got that problem too on your setup?

Thank you very much for you answer and see you soon !

Screenshots (sorry for the big size, I didn't find how to upload images directly on the topic) :
[ONE Android Development] nathsagar96:
You could have removed the preinstalled apps like calendar, music player, email etc. Because people anyway use the the google alternative.