yashsingh1/xdaforums huggingface dataset:
[Huawei P10 Lite Questions & Answers] davidhozic:
So I've made 4 videos in total, 2 of those are for huawei.

I am now going to make videos based on what people want to see.

Just reply with with you want to see.
[Huawei P10 Lite Questions & Answers] XperiaThemeLover:
How to unlock bootloader with DC unlocker perhaps
[Huawei P20 Lite Questions & Answers] davidhozic:
So I've made 4 videos in total, 2 of those are for huawei.

I am now going to make videos based on what people want to see.

Just reply with with you want to see.
[ONE Android Development] Tomoms:
Reserved

How to set up the charging speed interface in Kernel Adiutor?

First thing, download the attached zip and decompress it. You'll find two .json files in it, place them in your internal storage and open KA. Go in the "Custom controls" tab, tap on the "+" button, choose "Import" and select the first of the files you downloaded, then import the second one too. Done! You can now delete the two files.

Keep in mind that the "0" value means that the standard charging logic will be used, and that the AC charging speed cannot be set to a value lower than 200 mAh, even though the slider allows you to set any value. If you set any value between 1 and 199, the driver will fallback to 200.
[ONE Android Development] pradie:
working fine with AEX 5.7.
[ONE Android Development] antfior93:
is it compatible with oxygen os blobs or sultan blobs?
[ONE Android Development] Ruggerxpunk:
Running well for me on AEX 5.7.
[ONE Android Development] Tomoms:
Starting from Oreo, all ROMs implement Sultan's camera, thus this kernel only supports Sultan's camera HAL.
[ONE Android Development] Tomoms:
New version is available :)

It's an important updates that brings lots of improvements (mainly "under the hood"), for more info I suggest you to check my Github repo!
[ONE Android Development] rolarocka:
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build? ?
[ONE Android Development] Tomoms:
Most probably, this kernel already works on Pie :)

You just need to flash it, then flash the Kernel Permissive Patcher (link - needed to set SELinux to Permissive before booting the OS) and you should be good to go. If you try, let me know the result!
[ONE Android Development] twowheeler:
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
[ONE Android Development] Tomoms:
The stock settings are kind of good. Not the best you could get, but close (I'll tweak the default configuration a little more in the future). If you're using idprophecy's ROM you will end up having maple as the default I/O scheduler, while if you're using other ROMs, I'm pretty sure you won't. Anyway, if you flash this kernel, I'm sure you'll benefit from the general improvements I implemented, which do not need any tweak to be enabled.
[ONE Android Development] pat99:
Works well on following ROMs;

-AOSiP 20180825( Argon v1 )

-TugaPower O25 ( Argon v2 )
[ONE Android Development] tamboli007:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
[ONE Android Development] MrYuraB:
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
[ONE Android Development] Tomoms:
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
[ONE Android Development] Mr.Ak:
Good to see you're still contributing for Bacon. :)
[ONE Android Development] MrYuraB:
Yesterday I tried to send you message, but it is why it is not sent... I agree :)
[ONE Android Development] Tomoms:
I've uploaded a new kernel!

Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual :)
[ONE Android Development] Ruggerxpunk:
I've been loving the Kernel on AEX 5.7, but I've needed to reboot a few times because the screen won't turn on, or the screen has frozen.

Do you think that could be from the default underclock?
[ONE Android Development] jmax91:
[MENTION=2727695]Ruggerxpunk[/MENTION] Same issue on my side since V2 version, but I don't have any logs cause I'm not using it at this moment.
[ONE Android Development] PrinceOfDarkness:
I have Installed Argon kernel on my Opo and its working fine I check fuctions and I have issue.

very nice to have this Kernel working fine :fingers-crossed::good::victory:
[ONE Android Development] chill4279:
Argon v10 works perfectly on CandyRom 8.1 - Just thought I would let you know so you can list that as a compatible ROM in the OP. thanks for the great work on this ROM!
[ONE Android Development] effry:
hi [MENTION=5727088]Tomoms[/MENTION], i just flashed your kernel on top of official LOS and i have to say that you really did an amazing work, my opo more than doubled it's battery life without sacrificing any performance. really, thank you!

i'm only getting 1 problem: push notificiations (Email, whatsapp...) stops working after few minutes and i receive messages only if i open the application manually. I guess this is one of the reasons of the great battery life. Is there any tweak i can make to improve this situation? already tried to un-doze whatsapp and Outlook, but this sorted no-effects.
[ONE Android Development] Tomoms:
I'm using my own ROM and Kernel Adiutor is able to change the max frequency on boot as expected. I don't really know how to help you, try uninstalling and re-installing KA.

Another case in which I cannot be of help...

All the other users and I have never faced issues with push notifications. If the kernel suffered from this severe issue (that affects a crucial functionality of a smartphone), I wouldn't release it publicly.
[ONE Android Development] PrinceOfDarkness:
Hey Effry, I have only one issue on official LineageOS after calling on whatchapp, that my sound for notificiations is stop working it's an issue in the LOS rom this is already happends for few months for me with stock kernel, I use now Argon kernel and for me everything is working execpt the the sound issue for notification in the rom it own.

But I only have one issue with this kernel on Official LOS 15.1 when my phone does restart on hes own he keep repeat rerstart on de ''Oneplus logo powerd by android'' on boot over and over. To fix this I have to hold volume down to go in recovery and boot system by my own or with luckl hold and press the power button to power off and start the phone again
[ONE Android Development] Tomoms:
Hello!

I've released a minor update, Argon v10.1. You can find it here or here!

It includes some updates & fixes, mainly for the ext4 filesystem.
[ONE Android Development] 1plus:
Thanks Tomoms for your hard work. I'm using your kernel with Tugapower LOS15.1

Have you tried your custom kernel for LOS16? Any plans to port it in the future perhaps?
[ONE Android Development] Tomoms:
Many people reported that the kernel is already working on certain Pie ROMs (only Lineage-based ones), so my guess is that the kernel is compatible with LineageOS 16 :)
[ONE Android Development] OPOt585:
hei, thank you very much for the kernel. I am using it on official LOS 15.1.

I was wondering if update 10.1 has something different about charging because it seems like it charges as fast as 10 but my OPO is much much cooler while charging!

With the previous version it became hot pretty fast.

Nice work!
[ONE Android Development] Tomoms:
Well, that's nice, but I didn't change anything xD
[ONE Android Development] portfolio:
yes, works very well with L-based roms, I myself enjoy Argon on my TP rom
[ONE Android Development] Fatsodonkey:
IMHO Intellithermal was superior to Sultans thermal. It went from snappy to laggy. I can always downgrade to 8.1 though. :)
[ONE Android Development] Tomoms:
Interesting. If you want, we can discuss this further when I've got more free time.

In the meanwhile: I've released v10.2. It's just a small update with some security fixes :)
[ONE Android Development] 1plus:
Yes, it kinda works. Cannot extensively test it though, as I use it only for a backup phone, but features I use seem to work.

Only one thing -- it seems like both on LOS15.1 and LOS16 the impulse governor is broken. It works but the UI becomes very sluggish, can be noticed when opening a new window or during scrolling.
[ONE Android Development] Tomoms:
I'm using impulse with bricked hotplug on 15.1 and the phone is super smooth. Can you check your governor parameters? Maybe the default ones are bad and I've never noticed it.
[ONE Android Development] portfolio:
:confused: Argon does not work anymore on latest TP8 Pie rom, has been excellent until TP7
[ONE Android Development] grinimark:
No problem here.

TP8 and Argon 10.2 works really fine.
[ONE Android Development] 1plus:
I don't have any bricked hotplug though (using KA here) Only MPDecision and MSM MPDecision. Which one should I use then?
[ONE Android Development] Tomoms:
MSM MPDecision is another name used to indicate bricked hotplug :)
[ONE Android Development] ralpyka:
Does anybody has this problem that the CPU is going to 2.8ghz sometimes? I had this issue on pie ROMs, and now I installed Tomoms 15.1 build, but the CPU is still going to 2.8ghz. Even if I change the max frequency in KA, it ignores the setting after a while.
[ONE Android Development] Setting.Out:
Max frequencies aren't respected..
[ONE Android Development] Tomoms:
I'm pretty sure the behavior you're reporting is completely normal. The 1,9 GHz frequency is set as the max frequency by a command that is placed in the ramdisk. Ramdisk commands are executed (more or less) when the Oneplus kernel splashscreen disappears and the ROM's bootanimation is displayed. Before this happens, the CPUs run at the kernel's maximum frequency of 2,8 GHz. There's nothing to be worried about, as the 2,8 GHz frequency is only used for a few seconds immediately after you turn on the phone.

Sorry, I didn't look at the screenshot carefully.

Can you please tell me what governor you're using and which frequency have you set as the max frequency? Are you by any chance using Qualcomm's default hotplug (mpdecision) instead of bricked hotplug? It is known to interfere with frequency restricitons.

Also, what kernel tweaking app is that?

I'm using impulse and I've set the max freq. to 2,2 GHz in Kernel Adiutor, and my settings are never violated.
[ONE Android Development] Setting.Out:
I'm set stock, just using a CPU monitor to verify the frequencies.. I was planning on tweaking the settings, but wanted to test against your presets.. I ran geekbench to spike the load artificially.. :)
[ONE Android Development] fabiomcz:
I also had problems with using KA, bricked hotplug leaves only a core running, with mpdesion the 4 cores worked normally, but the frequency of the clock did not fix, besides some crashes when long in stand by. with the smartpack app(https://xdaforums.com/android/apps-games/app-smartpack-kernel-manager-t3854717) not have as many crashes.

ROM: Tuga power P8
[ONE Android Development] PrinceOfDarkness:
Yup I have this too
[ONE Android Development] Tomoms:
I use bricked hotplug and it's working perfectly. Are you sure you're not using 2 hotplugs at the same time?

BTW, it's normal that mpdecision doesn't allow you to change the frequency limits.

What settings are you using? What governor? What hotplug?

I need more info, because it's difficult for me to debug an issue that I've never faced.

Anyway, I've uploaded v11, it includes quite a few important updates and fixes, and it's been built with the very latest gcc toolchain. One notable fix affects the DDR bandwidth boost: basically, due to my lack of attention, when I had initially implemented it (in the very early days of Argon kernel), I coded a wrong value, thus the feature has never worked! Anyway, it's fixed now: better late than never!
[ONE Android Development] PrinceOfDarkness:
Well have this issue on officieel LineageOs 8.1 on governor zzmoove, interactive and Performance on this I have tested I this and all with same issue, on zzmove I used number_profile: 2.

I havent change the hotplug I still use the msn mpdecision Hotplug thats active if you want I can take screenshots if you want.

And this is on v10.2 I will install now v11
[ONE Android Development] 1plus:
[MENTION=5727088]Tomoms[/MENTION]

I understand that currently your kernel is not officially supported for LOS16. Still, worth mentioning -- v11 did not work with TP8 rom. Obviously due to lack of encryption support only way to upgrade is adb sideload from twrp. With v11 causes instant bootloops, never reaches even encryption pin entry on boot. Downgraded back to v10.2
[ONE Android Development] Tomoms:
I've just clean-flashed TP8. Argon v11 booted successfuly (I don't use encryption, though). Sorry, I don't know why you're facing problems...
[ONE Android Development] fabiomcz:
with kernel manager smartpack, only MPDecision is shown as an option, all cores always active. I was able to set the frequency to 1.9 even with MPDecison. I created logcat inside the smatpack itself, I hope it helps.

ROM: Tuga Power P8 - PIE

tested with argon v11
[ONE Android Development] jmax91:
[MENTION=5727088]Tomoms[/MENTION] thanks for the update and for keeping alive our Bacon. Your kernel is rock solid, but I have issues when I set 2457 MHz as max. frequency in KA: as others said, it doesn't stuck and goes to 2880 MHz. For that reason, I would like to ask if you could remove overclocking. At least until this issue is solved. Thank you.
[ONE Android Development] Tomoms:
A quick heads up for you: one of the last commits merged into our LineageOS 16 device tree moved the init scripts to a different location, thus Arfon kernel's installer is not able to patch them anymore, leading the device to boot with only one CPU online, a broken hotplug and severe lagging. Thus it is very important that Pie users stop using the kernel right now. I'll fix this ASAP, it's not my top priority right now, and additionally I can't dedicate much time to Android nodding in these weeks. Thank you for your understanding.
[ONE Android Development] Maurosebas:
This kernel is working really good, can't wait to see how much better it will become in the near future!

My Oneplus ONE is having a second life :) Thanks to the dev for making it happen and optimizing it time by time.
[ONE Android Development] Tomoms:
Thanks for the appreciation :)

I've been a bit busy these days and now I'm having some trouble with the development of my ROM. As soon as these things get sorted, the development of the kernel will be resumed, and I'll add proper Pie support.
[ONE Android Development] ralpyka:
Hello Tomoms, I don't want to annoy you, just would be nice to know when that new version of the kernel (with proper pie support) will come out?
[ONE Android Development] Tomoms:
Very very soon! The kernel is ready, I just have to finish the work on the installer. So I'd say it'll be ready within the weekend :)
[ONE Android Development] Tomoms:
Hello! I've released Argon v12: starting from this version, Oreo is not supported anymore. Only ROMs based on LineageOS 16 are supported :)

This new kernel mainly brings a few miscellaneous tweaks (especially for the impulse governor) and some backports affecting the memory management stack.

Due to the fact that I'm using my unofficial LineageOS 16 builds, which have got all the necessary ramdisk patches pre-applied into the ROM's sources, I couldn't test whether the installer of Argon v12 works flawlessly or not (it should apply those patches on all the other ROMs). So please keep in mind that I might have made some small mistake, thus it is important that after flashing this new kernel you make sure that:

Qualcomm's MPDecision hotplug doesn't exist, and bricked hotplug is enabled by default;

impulse is the default CPU governor;

maple is the default I/O scheduler;

the CPU's max frequency is set to 1,9 GHz.

As you can see, as of now I'm not sure Argon v12 is not a flash-and-forget kernel. I need confirmation from someone who uses either official LineageOS 16, or Tugapower, or other ROMs, except for mine.

Thanks for your attention and I hope to receive some feedback soon!
[ONE Android Development] ralpyka:
Installed on Tugapower P12. Observations:

- impulse is the default CPU governor and maple the default I/O scheduler

- the CPU frequency is a little bit weird (on first boot it seemed like the max frequency was 2.8ghz, on second boot it didn't went above 1.7ghz)

- attached a screenshot from kernel adiutor about the hotplug settings. Is it correct, or should I use another app to see the configuration?
[ONE Android Development] Tomoms:
Thanks. The CPU hotplug is configured well. You're not the only one facing issues with maximum CPU frequency, other users reported problems on Oreo even when using other kernels (if I recall correctly, someone reported similar issues with Thunder kernel as well). I've never faced any issue, though. Can you try changing the max frequency to something else using Kernel Adiutor? Does the change stick or not?
[ONE Android Development] ralpyka:
Changed it to 1.9ghz, it does stick for a while, but after some time it switches to 2.8ghz (uses all of the frequency steps up until 2.8ghz)
[ONE Android Development] jmax91:
The same for me. I'm on stock LOS 16.
[ONE Android Development] Tomoms:
Please run this command as root in a terminal emulator:

ls -l /sys/devices/system/cpu/cpu0/cpufreq

Then post the output here.
[ONE Android Development] ConnerJSP:
A0001:/ $ su
A0001:/ # ls -l /sys/devices/system/cpu/cpu0/cpufreq
total 0
-rw-r--r-- 1 root root 4096 2019-03-11 18:14 UV_mV_table
-r--r--r-- 1 root root 4096 2019-03-11 18:14 affected_cpus
-r--r--r-- 1 root root 4096 2019-03-11 18:14 cpu_utilization
-r-------- 1 root root 4096 2019-03-11 18:14 cpuinfo_cur_freq
-r--r--r-- 1 root root 4096 1970-06-02 02:08 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 2019-03-11 18:14 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 2019-03-11 18:14 cpuinfo_transition_latency
-r--r--r-- 1 root root 4096 2019-03-11 18:14 policy_max_freq
-r--r--r-- 1 root root 4096 2019-03-11 18:14 policy_min_freq
-r--r--r-- 1 root root 4096 2019-03-11 18:14 related_cpus
-r--r--r-- 1 root root 4096 1970-06-02 02:08 scaling_available_frequencies
-r--r--r-- 1 root root 4096 2019-03-11 18:14 scaling_available_governors
-r--r--r-- 1 root root 4096 2019-03-11 18:14 scaling_cur_freq
-r--r--r-- 1 root root 4096 2019-03-11 18:14 scaling_driver
-r--r--r-- 1 root root 4096 2019-03-11 18:14 scaling_governor
-rw-rw-rw- 1 system system 4096 2019-03-11 18:14 scaling_max_freq
-rw-rw-rw- 1 system system 4096 2019-03-11 18:14 scaling_min_freq
-rw-r--r-- 1 root root 4096 2019-03-11 18:14 scaling_setspeed
drwxr-xr-x 2 root root 0 1970-06-02 02:08 stats
[ONE Android Development] jmax91:
:/ $ ls -l /sys/devices/system/cpu/cpu0/cpufreq
total 0
-rw-r--r-- 1 root root 4096 2019-03-12 00:03 UV_mV_table-r--r--r-- 1 root root 4096 2019-03-12 00:03 affected_cpus
-r--r--r-- 1 root root 4096 2019-03-12 00:03 cpu_utilization
-r-------- 1 root root 4096 2019-03-12 00:03 cpuinfo_cur_freq
-r--r--r-- 1 root root 4096 2019-03-11 23:51 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 2019-03-11 23:51 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 2019-03-12 00:03 cpuinfo_transition_latency
-r--r--r-- 1 root root 4096 2019-03-12 00:03 policy_max_freq
-r--r--r-- 1 root root 4096 2019-03-12 00:03 policy_min_freq
-r--r--r-- 1 root root 4096 2019-03-12 00:03 related_cpus
-r--r--r-- 1 root root 4096 2019-03-12 00:03 scaling_available_frequencies
-r--r--r-- 1 root root 4096 2019-03-12 00:02 scaling_available_governors
-r--r--r-- 1 root root 4096 2019-03-11 23:49 scaling_cur_freq
-r--r--r-- 1 root root 4096 2019-03-12 00:03 scaling_driver
-rw-r--r-- 1 root root 4096 1970-04-28 10:15 scaling_governor
-r--r--r-- 1 system system 4096 2019-03-10 22:46 scaling_max_freq
-rw-rw-r-- 1 system system 4096 2019-03-10 22:45 scaling_min_freq
-rw-r--r-- 1 root root 4096 2019-03-12 00:03 scaling_setspeed
drwxr-xr-x 2 root root 0 2019-03-11 18:11 stats
:/ $

When phone gets stressed maximum frequency changes to 2880 MHz automatically, like on LOS 15.1. I have tested it a lot of times with Antutu.
[ONE Android Development] MMelite:
I'll try to flash latest version on Pixys 2.4 unofficial but failed it and device didn't work. Is it no compatible?

Is it only for LOS?

I solved it by writing rom again.

Is there another alternative for my rom? Thanks.
[ONE Android Development] Tomoms:
Pixys is based on AOSP, thus my kernel can't work well with it. My kernel will only work on Lineage and Lineage-based ROM's.
[ONE Android Development] MMelite:
Ho visto ora che sei di Trieste. Complimenti per il Kernel! Me ne suggeriresti uno per Pixys? O quello che ha integrato va già bene?
[ONE Android Development] JT1510365:
English please no one can understand you
[ONE Android Development] MMelite:
Is there a good alternative kernel for PixysOS 2.4?
[ONE Android Development] Tomoms:
Thunder is made for AOSP but I don't remember whether it has been updated for Pie.
[ONE Android Development] MMelite:
I don't think so...
[ONE Android Development] zzyyi66:
any plan to support aosp 9.0?
[ONE Android Development] Tomoms:
It'll never happen.
[ONE Android Development] iPusak Gaoq™:
It has been updated to Pie long time ago in fact i'm using it on Bootleggers Pie right now...
[ONE Android Development] PrinceOfDarkness:
I hope this kernel will be supported and updated for very long time. I like this kernel for my Oneplus One
[ONE Android Development] portugt30:
I loved the kernel but it only needs to be able to tune the temperature at which the CPU can reach "thermal throttling" Arrow rom has almost perfect kernel, I say almost perfect because of in standby consumes a lot of battery, I do not know the reason I tried a clean installation and nothing was useful to the problem, I installed everything to try to solve and nothing, i will thank you very much ? could fit this function on your kernel. Thank you and a great work. ??
[ONE Android Development] Tomoms:
Hello! I've released Argon v13 :D

This release brings a new TCP congestion control algorithm (based on Westwood and Reno, mainly), overclocking for the memory bandwidth (faster access to RAM), and lots of small tweaks (especially for the impulse CPU frequency governor and for some memory management libraries for the ARM architecture).

The thermal driver's parameters are tunable. Not in the most straightforward of ways, but you can do it. Open this directory: /sys/kernel/msm_thermal. There you'll find some files where you can set the temperature threshold above which the CPU frequency must be capped at a given frequency (because it's heating up too much), and the threshold below which the CPU is allowed to run at a higher frequency (because it's starting to cool down). The syntax of those files is:

[frequency] [throttling temperature] [un-throttling temperature]
[ONE Android Development] dudas89:
Tomoms, thank you so much for your work. I've been using your kernel for a very long time.

However, I'm facing an issue since this last version. I want to set the maximum CPU frequency to 1958 Mhz and everytime I open Kernel Adiutor-Mod Reborn, it insists to stick at 2880 Mhz. Every other settings are kept after I change them.
[ONE Android Development] jmax91:
Sadly the issues I have with maximum frequency keeps me away from using the kernel at this moment. I really dislike overclocking and I'm not able to manage it.