yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] solar666:
Hi, I have done more extensive testing and can conclude that the issue is directly link to your last kernel.

Previous ROM dated in November is doing fine with Magisk. Dirty flashing to the current one removes already present modules and new ones cannot be installed.

Using latest Sultans with your kernel v14 shows the same problem without using your kernel v14 Sultans is working flawlessly.

I can try to make again a clean flash of your latest ROM which includes v14 of your kernel and later on provide a logcat installing a magisk module if it will help you to solve this issue.

Please let me know.
[ONE Android Development] Tomoms:
Download Neon kernel v14 and flash it on top of the latest build of the ROM. Does Magisk work?
[ONE Android Development] solar666:
Done this with Sultan's ROM.

Without kernel v14 magisk is working as expected. With kernel v14 no modules can be installed.
[ONE Android Development] Tomoms:
I really don't know what's going on... I'm using Magisk modules without any issue...
[ONE Android Development] LTMendarynas7:
Can confirm that magisk modules doesn't install (with v14 and v14.5)

Magisk log shows that it installed without any problems, but after reboot there is no modules (I only tried V4A and greenify4magisk)

P.S Clean flash
[ONE Android Development] Tomoms:
Aaaaaaahhhhh you were using Xposed... I'm afraid that's the issue. Don't get me wrong, I'm not an Xposed hater (I was one of its regular users in the Jelly Bean/KitKat days), but after trying it on several post-Lollipop Android iterations, I would advise everybody to stay away from it.

Also, do root your next install. No root = no possibility of getting logs, or checking system stuff to debug problems...

So basically, clean flash again, with root but without Xposed, and install only the essential stuff, then check the performance of the ROM again.
[ONE Android Development] OnniXx:
I cleaned flash this new version yesterday and it's smoother than the previous version for me but still not as smooth as 2 or 3 versions ago. Chrome especially is so laggy and takes so long to open that I had to look for another browser, other apps take a bit longer to open but after opening they are very smooth. Screen has a bit of delay to turn on like a second or so.

I'm using magisk and a couple of modules (that I can post if it's useful for you) but no Xposed.

Once I get home I'll try to do the kernel auditior thing when I get home.

Another thing I can't install viper4android? Everytime I open it tells me to install drivers, I tried practically every fix I found online but nothing worked. Do you use it or could know what's causing this?

In previous versions it worked flawless
[ONE Android Development] Tomoms:
I really don't know what's wrong. I've downloaded Chrome on my phone just to check its opening speed, and it's blazing fast and super responsive. I'm using this Viper: https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651

and I'm having no problems at all.
[ONE Android Development] OnniXx:
That's the version I was using and I'm trying to install but nothing. Yesterday it started to work randomly but then I rebooted the phone and it's not working anymore and the drivers aren't installing again.

I also checked the kernel adiutor and it seems the 4th core is most of the time offline and the frequencies 1958 mhz and 268 mhz are practically the only ones used and most of the others either aren't used or have a really low percentage. But 268 mhz is by far the most used Wich could explain the slowish experience?

Does this last zip contains the kernel included or should I flash it separately?

Using pico open gapps ( don't know how useful this info is but I'm trying to be the most complete possible with the feedback)

Edit: Managed to make Viper work but then rebooted and it's asking me to install drivers again. I don't even know how it started working in the first place, i tried alot of ways multiple times. It seems random when it installs

Edit2: Also related to Viper, managed to install the drivers again somehow. Rebooted to see if this time it would work but nope. It's asking me again to install them. It's the 3rd time the drivers are gone after reboot

Edit3: my final for tonight, I believe I managed to install the drivers for good. At least so far it survived 4 or 5 reboots.

I don't know what was causing the problem but if someone is having the same problem I can post the steps I did tomorrow
[ONE Android Development] Zayphod:
I too feel like the latest release is sluggish compared to the previous versions. Everything happens with a significant delay, even typing or turning the screen on, as mentioned.
[ONE Android Development] __infin1ty:
I can confirm sluggish behaviour and serious delays that lead to unresponsiveness and sometimes I have to force shut down device so I can use it again.
[ONE Android Development] Tomoms:
The ROM is perfect for me. Please download Kernel Adiutor and post here a full description of you setup.

--

A question for all the users: are you experiencing problems with battery charging? Ever since I switched to stock LineageOS from Sultanxda's CAF-based Cyanogenmod 14.1, I've experienced charging hiccups: when I plug in the charger, the phone charges intermittently for a period of time that can be a bunch of seconds or even one full minute, as though the charger was being continuously plugged and unplugged. This happens with both my stock charger and third party ones, although it happens less often using the stock one. So I decided to try to port Sultan's custom battery charging drivers into my Lineage-based kernel source (no hiccups ever happened on Sultan's ROM). I did some work in the past days, and the kernel boots, however the reported battery level is always 0%, so there's still some work to do :(

I'd like to hear whether there are other people with the same issue.
[ONE Android Development] Tomoms:
Guys, I've released a new update. Minor improvements in the kernel and March security patches are included. If you're still facing major performance issues, you must provide some useful information (details about the kernel configuration, for example, to see if there's some problem I haven't noticed with the default kernel configuration), otherwise, I can do nothing about it.

Thanks :)
[ONE Android Development] sgtfoo:
Will the latest magisk work on this?
[ONE Android Development] awtacular:
Yes Magisk 20.3 works fine with this rom.
[ONE Android Development] gil80:
Yes I'm experiencing that exact charging issues. I have two 1+1s and both present that charge issue you described ever since 7.1.2 Sultans ROM.

I replaced so many cables thinking it was a cable issue, but it works fine if you completely shut down your phone. So it means there's a problem with the ROM.

---------- Post added at 12:28 AM ---------- Previous post was at 12:23 AM ----------

Does anyone experience this?

Yesterday the system displayed a warning [emoji615] sign that all my google accounts needs sign in again.

I had to remove them in order to sign back in.

I was only able to sign in to one of my Google accounts.

All other Google accounts cannot be added.

There are no error messages. I go to accounts, add a google account, enter the details and accept T&C and after a few seconds of the spinner animation, the screen will change to my home screen and the account is not added.

I've tried all my google accounts to no avail.
[ONE Android Development] Tomoms:
Hey! Sorry for the late reply, anyway I don't know what to say about your Google account issue. Have you tried updating Gapps, if you're using OpenGapps? It's a good practice to reflash them every now and then, to keep away all kind of bugs and problems.

Anyway, a new release with a bunch of small improvements is almost ready :)
[ONE Android Development] Tomoms:
A quick update for you guys.

One of the improvements I was looking forward to implement in my new build is causing a bootloop. I am currently doing some debugging to narrow down the list of possible culprits, and I'm adding back the safe changes gradually, building time after time to test them out. It'll take me a few days to complete this process, and tomorrow April's security patches are going to be release, so I'll wait for them to be available in LineageOS and then release a new build with improvements + latest security fixes.
[ONE Android Development] Tomoms:
The new build's available. Enjoy :)

EDIT: the OTA updater has been broken for a few days, I guess, due to an expired link. It should be fixed now.
[ONE Android Development] capt.ron:
Very nice ROM!

I have been using this ROM for several days now and it has been flawless for me. I have noticed no problems with the battery charging issue mentioned in the posts above. I haven't tried my GPS tracking app yet (endomondo) but I am hopeful it will work. Thanks for the reliable ROM!

P. S. Clean flashed, open_gaaps_nano, magisk 20.4
[ONE Android Development] citydweller1985:
Hi,

I did an clean install. But after installing WakeLock, I get the following error.

As I can remember there is no root required for WakeLock?

Is there anything I did wrong?

Kind Regards
[ONE Android Development] Tomoms:
The fact that WakeBlock's core mod is integrated in this ROM doesn't imply that the app can run without root. You indeed have to be rooted to use WakeBlock.

I'm glad the ROM works fine for you :)

Just out of curiosity, are you only using the original Oneplus charger that came with the phone?
[ONE Android Development] citydweller1985:
Hi,

thanks for your quick reply. I thought it's possible without root, look here:

https://xdaforums.com/showpost.php?p=70262930&postcount=4

No, I'm not using the original OnePlus One Charger, sorry.

Kind Regards and many thanks for your good work!
[ONE Android Development] Tomoms:
The question about the charger wasn't for you, but for the other guy I quoted ;)

Anyway, that post is not updated. It still refers to the v0 implementation of the core mod. Now, since October 2019, we're using the v1 core mod. Maybe using WakeBlock without root was possible with v0 but it's not possible anymore now. Try asking in the thread, the devs might be able to give you the true answer to this doubt.
[ONE Android Development] capt.ron:
I'm glad the ROM works fine for you :)

Just out of curiosity, are you only using the original Oneplus charger that came with the phone?[/QUOTE]

I am using the original One plus One charger and cable.
[ONE Android Development] Tomoms:
Most (but not all) original chargers don't give that kind of issues.
[ONE Android Development] capt.ron:
Good to know, thanks.
[ONE Android Development] indhimaga:
One of the greatest rom till now for bacon!
[ONE Android Development] Brzi99:
Moved to this rom yesterday from sultans latest los 14.1. Everything works like a charm so far except for the constant charger being plugged-unplugged thing. Using an original charger with new usb cable. :confused:
[ONE Android Development] Tomoms:
Unfortunately that's a problem I don't know how to fix. I've tried porting Sultan's charging drivers into my kernel source but they don't work properly. I'm sure they can be fixed but I haven't got time to do it now. I might try again in the future, though. Fortunately this bug doesn't damage your phone and your battery, and charging should become stable after 1 or 2 minutes.
[ONE Android Development] mituga:
Good Morning, you can't support kcal?

or have any similar application.

thank you
[ONE Android Development] Tomoms:
Settings > Display > LiveDisplay :)

Anyway, I'll add Kcal as well.
[ONE Android Development] mituga:
Ok, kcal is better thank you
[ONE Android Development] Tomoms:
Here's a kernel with some new features: https://androidfilehost.com/?fid=4349826312261786604

It can be flashed on top of the latest build. It features general kernel improvements and fixes, f2fs driver backported from Linux 4.12, sound control interface (for adjusting headphone and microphone gain) and Kcal support!

EDIT: I'm also working on another fix for the charging problem. I'll let my battery discharge a bit more than the usual for a few days, to be able to test it properly.
[ONE Android Development] Tomoms:
First attempt at solving the charging problem

[MENTION=5494784]Brzi99[/MENTION]

This kernel could possibly fix the charging hiccups! I've charged my phone twice, using third-party chargers and cables, with no hiccups at all.

https://androidfilehost.com/?fid=4349826312261789254

Everybody should flash it, as it also features some security patches and general bug fixes (plus all the features present in the kernel I posted yesterday).
[ONE Android Development] mituga:
thanks for the update
[ONE Android Development] :
Oh my gosh, I am sorry for being gone so long. Just got over covid19 and been having major vehicle problems again ??*♂️ so glad to see you're still working on the ROM! I want to donate
[ONE Android Development] Tomoms:
I've prepared another kernel! https://androidfilehost.com/?fid=4349826312261790451

There's only one major change in this one: CPU hotplugging is totally different now. It is known that turning off and on the cores is quite expensive in terms of power and also adds some latency. Some devs, such as franciscofranco, decided to leave all cores online in their kernels, as they say the performance boost is good and comes at no real cost in battery life. I've decided to try a hybrid approach to this problem: in this kernel, all CPUs will be always online when the screen is on (when we use the device, they tend to be onlined quite often), but when the screen goes off, AutoSMP starts working again, so that when the phone is left in idle for a long time (e.g. overnight), we don't waste power by keeping 4 CPUs online in a useless way. We should all test this new setup in everyday life scenarios to confirm battery life is not affected. Also, I also expect a small performance boost.

Hello, it's nice to see you here again :) I hope you're doing well now!
[ONE Android Development] Saison2018:
Can we (and do you want me to test) to flash your kernel on official LOS firmware?
[ONE Android Development] Tomoms:
No, it wouldn't work as intended.
[ONE Android Development] Saison2018:
Got it

Thanks
[ONE Android Development] Brzi99:
Charging seems to be working great so far :laugh: I did have two random reboots, could be because of uninstalling magisk before flashing the new kernel, idk really

Also will now flash and test the latest kernel, thanks a lot!
[ONE Android Development] :
Awwh, thank you it's nice to be back ? I am doing well now, i completely quit smoking due to covid, and haven't gone back. Lungs feel healthy and I can go for night runs without breaking a sweat ?? huge difference from a month ago. Got winded going up stairs. Wasn't fun. Didn't have to go to the hospital though, which I am very thankful for ??

I should be up and running with the latest rom within the next few days. I've got a lot of energy and coffee on board ???
[ONE Android Development] Tomoms:
If you have a charger that didn't give any problem previously (in my case, for example, the original charger and cable never showed this issue), please try that as well - we need to confirm that each and every charger/cable works fine.
[ONE Android Development] Brzi99:
Before flashing the new kernel I had only tried the original charger, but with two different cables. Both cables stuttered pretty much every time.

So today (with the latest kernel) I tried 6 chargers (OPO original 2.1A, NOKIA 2.1A, 2x Samsung 1A, Apple 2.1A, Huawei 1A) and 3 cables (1m, 1.2m and 1.5m).

No problems at all. Phone mostly takes 900-1100mA while charging, except on the longest cable which sits around 50-350mA, only sometimes going full speed @~1000mA.

Will test a bit more during the next few days.
[ONE Android Development] Tomoms:
Thanks, this is the kind of details I need :)

Were the charging current values you have reported measured while the screen was on, or off?
[ONE Android Development] Brzi99:
The screen was on at around 75% brightness, I measured the charging current with Ampere
[ONE Android Development] Tomoms:
Ok, so the actual charging current was considerably higher, due to energy being drawn for the battery to power the display.
[ONE Android Development] mituga:
good night, i have wifi problems 2.4 ghz very slow connections at 5 ghz are good ...
[ONE Android Development] Tomoms:
Let me cast a spell on your phone, so that it starts working correctly.

Seriously mate, what kind of help are you expecting? Your message is so vague and lacks a whole heap of details that could help us understand what's going on. And since my ROM does not break 2,4 GHz WiFi on purpose, it's highly probable that the issue is specific to your access point, and/or some kind of interference (maybe a saturated channel?), or a similar issue.
[ONE Android Development] mituga:
I've been testing some different firmware but the result is similar 8mb, when testing the WiFi network 2.4 ghz from my house with Samsung A80 I have 50mb.
[ONE Android Development] psidco:
Is this kernel support lineage os17 sir?
[ONE Android Development] Tomoms:
It should, but I don't advise installing it on other ROMs.
[ONE Android Development] psidco:
Try to instal and the updater say uncompatible android version.
[ONE Android Development] Tomoms:
Why did you flash it if I advised against doing it? I could change the installation script to add Q compatibility, but I've already told you that you shall not install this kernel on other ROMs! The fact is that my ROM provides some custom commands that are run at startup, to set up some kernel parameters properly. Other ROMs obviously don't have these commands, thus the kernel wouldn't work as intended.
[ONE Android Development] psidco:
Thanks for the explanation and sorry for my stupid question.im just asking,since your kernel is great for battery saving.imho
[ONE Android Development] Tomoms:
Don't worry. In the future I might release the kernel separately, with a proper zip file to allow installation on Q ROMs. And, additionally, some ROMs will feature my kernel out of the box. So just wait for a little while, you'll be able to use my kernel sooner or later!
[ONE Android Development] psidco:
Thanks .keep up the good work :good:
[ONE Android Development] Tomoms:
A new build with May's security patches is coming in the weekend.
[ONE Android Development] Tomoms:
The new build is up :)

It features May's security patches and all the kernel work I've released as separate kernels in the past days, except for the hotplugging change, which I want to improve some more. So for now, I've sticked with the classic AutoSMP hotplug that plugs and unplugs the cores when needed.

I've also changed the file storage solution I use, so please tell me if the OTA updater works properly. Enjoy!
[ONE Android Development] capt.ron:
Greetings [MENTION=5727088]Tomoms[/MENTION] and thanks for the awesome rom and update. I did use the OTA updater and everything seemed to go as expected. I have not noticed any issues so far. I noticed that the kernel version was dated 9May so I guess I'm up to date with that. Thanks again!
[ONE Android Development] Kentuckykiid:
Thanks [MENTION=5727088]Tomoms[/MENTION] for this awesome ROM. I am currently on Jan 18 Build. since then i am facing issues with OTA updates while downloading. I am getting following message while downloading OTA updates - "The download failed. Please check you Internet Connection and try again later".

Should i dirty flash 9th May build until this issue gets fixed?
[ONE Android Development] Tomoms:
Unfortunately, both AFH and Microsoft OneDrive provide direct links that change during time, so the OTA updater often breaks after a few days, as the link expires. I'm looking for a more reliable solution. I've just fixed the OTA link again, so it should work now. Reboot and manually search for updates in the OTA updater, the new build should download correctly.
[ONE Android Development] Kentuckykiid:
Thanks [MENTION=5727088]Tomoms[/MENTION] I was able to update it. :)
[ONE Android Development] Tomoms:
I need your feedback

A few days ago I started experiencing the same problems with Viper4Android. The drivers install properly and survive reboots, but the app is never processing any audio and in Viper's status screen I see "Status: Abnormal".

I've tried to remove the app, the Magisk module, reinstall it, but nothing. Also, it seems like LineageOS's AudioFX is terribly broken: if I enable it for the headphones and I play a song, instead of the music I hear a terrible loud and broken noise. Disabling AudioFX and restarting the music app solves the problem.

So please, guys, can you try at least AudioFX with your headphones, and tell me whether it's broken for you as well or not? Please try it with both mp3 and flac files. Maybe my setup has been messed up by remnants of Viper4Android, but I cannot be sure unless you try it as well.

Thanks.
[ONE Android Development] OnniXx:
Hey, I’m actually back on this rom because the one I changed to had some annoying bugs.

I’ve only been using it for 3 days but so far it seems great and no bugs

Yesterday I tried to install viper and was having the same problems but I got it work, what I did was used titanium backup to uninstall audiofx, installed the audio modification library module from the magisk repo and only then I installed viper and so far is working normally with mp3,flac and m4a with headphones and phone speakers, haven’t tried Bluetooth yet
[ONE Android Development] OnniXx:
I'm having an issue, I can't play online videos. Reddit doesn't load vids' neither does Twitter or YouTube.

Can only play local files, any suggestions?
[ONE Android Development] Tomoms:
Hmm... I can play videos finely in Reddit, YouTube (through Firefox) and YouTube through NewPipe... You could try to get a logcat.
[ONE Android Development] OnniXx:
It's working again, I updated my adway hosts and rebooted. Now I don't know if it was some hosting messing up or it was just the reboot that made it work but anyway I think it's normal now.

Did you manage to make viper work?
[ONE Android Development] Tomoms:
No. It's driving me mad. But I still have a few ideas to try. Anyway I'd love to know why it's not as straightforward as it was. Until a few months ago, there was no need to install the Audio Library Modifications module, nor to remove AudioFX.
[ONE Android Development] OnniXx:
Aaaand my videos aren't loading again, I'll try to get logs later

Have you tried to completely uninstall viper, than install the older 2.5 version and install those drivers, and if it works normally go to the installation folder (can't remember where it's located) and replace the APK with the newer 2.7, don't forget to rename it the same and reboot

I had to do something similar once to get it to work
[ONE Android Development] Tomoms:
I can't even manage to uninstall AudioFX. I remove it with Titanium Backup but it doesn't really disappear, it just stays there! I've read that setting SELinux to permissive is needed to uninstall system apps, but in my case it doesn't help. How did you manage to remove it?
[ONE Android Development] OnniXx:
Used titanium, clicked uninstall and rebooted phone. Didn't need to do nothing else and I haven't touched selinux so it was whatever its default
[ONE Android Development] N34S:
Hello. Is there a bug tracking system for this rom? because i'd like to report two annoying bugs that i've found. Thanks
[ONE Android Development] Tomoms:
If you are facing bugs, you can report them in this thread. It's better not to report bugs to LineageOS's official bug tracker, because they could be caused by my customizations, and in this case the official version would be unaffected.

EDIT: I'm preparing a new build, with the goal of solving the annoying in-call speakerphone problem, a bug that has been present for a very long time on several ROMs: basically, whenever we make a phone call and use the speakerphone, our voice becomes inaudible to the other person. I've made some progress so I think I'll be able to eliminate this problem soon.