yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Dolphine_80:
Hello,

today I have installed ROM, tomorrow will show how it behaves. :)

There is a mistake I do not understand. The favorites on the contact and the favorites in the dialer are completely different! :( My favorites in the dialer are not what I have not been calling for months so these are not favorites but old numbers. How can I fix this?
[ONE Android Development] Tomoms:
I don't know how to help you, I see the most frequently called contacts in the main screen of the Dialer app...

--

I've uploaded a new build. It brings some changes that might make the UI smoother. Let me know if you can feel the difference or not!

Download link: https://www.androidfilehost.com/?fid=11410932744536995306
[ONE Android Development] Kengat:
Using the latest version now. So far didn't really notice much difference but I'll let you know.
[ONE Android Development] Dolphine_80:
Unfortunately, there is also a bigger problem. :(

1. The phone is automatic switched off at night.

2. The morning when I turned on the battery was 75%, although it was fully charged in the evening.

Which Gapps do you use? I put MindTheGapps, but maybe that was the problem.

Today should I start it again! :(

Should I delete my internal storage before installation?
[ONE Android Development] philash_flash:
How's the battery life?
[ONE Android Development] sayash5:
Just update by dirty flashing, I'll report in a week, cheers!
[ONE Android Development] Syaani:
For me, it is good. I have bought cameran sino battery and usually get full day battery life with single charge. But this question is a bit complicated since we all have different use cases and our batteries have aged differently. So.. I suggest you to give it a try!
[ONE Android Development] ConnerJSP:
In-built Kernel

Flashed just the ROM and checked the Kernel, said GCC was version 7.x. Is that because the ROM is built with that version or is it the wrong kernel? I flashed Kernel v.8 over the ROM and now the kernel information is updated with the 8.2.1 version.
[ONE Android Development] Tomoms:
You're right, I should have stated this somewhere. Argon kernel v8 is built with GCC 8.2 but the kernel that is built and shipped with the ROM is still built with GCC 7.x because I forgot to update the toolchain. So technically Argon v8 is not exactly the same kernel you can find in my latest build, but feature-wise, the two kernels are identical.
[ONE Android Development] ConnerJSP:
Ah, makes sense. Just wanted to make sure I wasn't messing anything up. No matter.

However, I flashed the ROM and have been messing with it. Something I noticed: I don't think my PC recognizes my device correctly because it installs the wrong drivers, then I can't transfer files to the phone. Never had this problem on other ROMs or on my computer.

Any idea what it could be or solutions to the drivers?

*Edit: I can do small batches of files, but if i try to copy 900+ songs it starts freaking out and not copying. Only happens with .m4a music files, didn't happen with photos.
[ONE Android Development] abadasstanker69:
Anyone have any issues with slow charging? I feel like I may have screwed something up with kernel auditor but I have no idea what I messed up. I have a gold plated USB charging cable so it's definitely not that. Any help would be greatly appreciated
[ONE Android Development] patp:
Just flashed up from Sultan 14.1. Looks great so far, thank you for saving our Bacon.

One issue I've noticed - the starred callers in the dialler is messed up. It contains a bunch of people I haven't called for years, while my actual starred contacts don't appear there at all. Tried clearing data in the app settings, but no change. I wiped system, cache, dalvik before flashing (but I left data intact).
[ONE Android Development] ConnerJSP:
I've observed this same behavior, but am none the wiser as to why it happens, likely something Google messed up. All I can offer is how to get rid of the randomly added contacts: tap and hold each contact and you can drag to remove at the top of the screen. However, a contact doesn't seem to show up there even if you favorite it, instead the most frequently called people will start showing up (close enough to favorites).

No slow charging issues here, plugged in at 16% and it stayed there for a sec, one video later and it was at 42%... But in the case that you messed something up in KA, you can either wipe the app data or reinstall the app; I wouldn't change any voltages for charging or battery.

P.S. Gold plated doesn't really do much, the quality and gauge of the cable matter more.
[ONE Android Development] donk165:
Hi there, just wanted to say this ROM is great. I came from tugapower, I was on sultans rom for a long time and fancied upgrading to 8.1, on tuga, I was getting occasional random reboots and the kcal color app seemed to be broken for me. After switching to this rom, my phone feels nice and stable again!

Thank you for your work, it is appreciated!
[ONE Android Development] Alpha Psi:
This rom has been quite stable after updating the firmware to the one linked in the non-optimized version.

How difficult is it to add screenshot to the power button functions?
[ONE Android Development] abadasstanker69:
Same
[ONE Android Development] Syaani:
There is already screenshot on power menu. You just have to enable it from the settings.
[ONE Android Development] JimJ2Mz:
Wanted to drop by to say thanks for developing this ROM. Came from Sultan's LOS 14 and this is good all around.

My idle battery drain is pretty bad though. We're looking at 10% per hour just leaving the phone on the table. Checking Kernel Adiutor, my phone is in deep sleep for most of the time, so there's nothing that should be keeping it awake.

The other culprit I had in mind was Youtube Vanced, since the last time I used it on another ROM, it kept my device awake until I uninstalled it. But this time, there was no indication of that with Adiutor. I just uninstalled it again and am seeing if the drain is still bad. At this point I feel like it's the battery that's dying out. If it is, then that's a shame.

Anyways, thanks again. I appreciate the work.
[ONE Android Development] Tomoms:
I have no idea why you are facing this problem. I don't use Windows so I need no drivers to get my phone to communicate with my computer; I often transfer files via USB and never had a single problem, although I've never transferred that many files.

I'm facing the same issue, don't know why it happens though...
[ONE Android Development] patp:
Annoying isn't it! Favourites was my default way to dial family.

Anyone recommend another dialler?
[ONE Android Development] Dolphine_80:
Unfortunately ROM problem. I installed another dialer, same problem! :(

Now I'm on Tugapower ROM and the dialers are fine. Favorites are favorites!
[ONE Android Development] patp:
Pie or Oreo? I'm afraid of Pie, my battery is not great these days.
[ONE Android Development] Dolphine_80:
Pie, with Greenify Agressive Doze and Shallow Hibernation.

The battery drain is average. At night, in stand by mode 6-7% (No Wifi, BT, or LTE), in daytime 1% / hour (No Wifi, BT, or LTE). That was last night, but I'm still testing.
[ONE Android Development] Kengat:
I've always experienced this on this phone. Not sure if it's rom related but seems it isn't. I can charge just fine and really quickly a S7 using the same charger and cable but when it comes to our bacon damn does it take long. :eek: Is there even a safe way to speed the charging?
[ONE Android Development] Ruvy:
This ROM along with Argon Kernel is a beast in terms of performance and battery. As stable as it could be. Played PUBG with balanced Graphics and medium fps (max available settings on OnePlus One) and it was a smooth ride. Phone became a little warmer but that was expected. Astounding SOT of 2.5 hours, all gaming
[ONE Android Development] AliasOfiuco:
Same 2 problems here:

1) Favorites in the dialer are not "right". :(

2) During the night the phone seems to swicht off, but it goes in a kind of "black crash" and I have to hold the on/off button for several seconds to bring it back to life. When my phone is working again I can realize that 25% of the battery is lost. :(

Except these 2 problems the ROM is great! :)
[ONE Android Development] Alpha Psi:
Ah yes, you're correct. It's under "buttons" and not developer options. I don't know why I keep looking for it under there. And search doesn't work on certain menus.

---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------

Good to know I'm not the only one with the strange total crash. The notification led still works but nothing happens with the press of power or home buttons. I've missed a couple of alarms, so that's bad...
[ONE Android Development] Tomoms:
Does any of you know if the problem exists in official LineageOS 15.1 or other Lineage-based Oreo ROMs?

You can set your preferred charging rate by writing the value in /sys/kernel/charge_levels/charge_level_ac. You must express the charging speed in mAh, the maximum allowed is 2000, if I recall correctly. This might fix your issue. It's a safe method, provided that you don't abuse it, for example by setting a high value when the battery's very hot, because I'm pretty sure that the battery chip's safety mechanisms are bypassed when you enforce a charging rate; so I advise you to do this only if you're sure that your charger & cable are high-quality (you could test them with another device and check if the charging speed is normal).

Thanks! It's nice to know that my ROM and kernel are appreciated :)

I might be able to fix the issue with your help, because it could be a CPU voltage/clock problem that shows up only on certain (low-quality) chips. Please post the content of these two files: /sys/module/clock_krait_8974/parameters/pvs_config_ver and /sys/module/clock_krait_8974/parameters/table_name.

Also provide as many details as possible: is the notification LED the only thing that keeps working during this sleep of death? What happens if, for example, you try to charge your phone?

Thanks.
[ONE Android Development] Kengat:
Hey thanks for the help! I've tried changing using the MiX file explorer from xda and it does save the value I put "2000" without quotes but when I reboot the changes it goes back to 0. Could it be a permissions issue?
[ONE Android Development] Syaani:
I have encountered this sleep of death/black crash like two times so can't tell much about the possible reason. Only common thing is that I was connected to wifi only and I think there were no apps open in the backround.

My values are:

/sys/module/clock_krait_8974/parameters/pvs_config_ver = 1

/sys/module/clock_krait_8974/parameters/table_name = qcom,speed3-pvs6-bin-v1
[ONE Android Development] Dolphine_80:
No. Before, I tried this ROM, I used [MENTION=4511190]idprophecy[/MENTION] ROM. It was no problem at the dialer!
[ONE Android Development] AliasOfiuco:
My value are:

/sys/module/clock_krait_8974/parameters/pvs_config_ver = 1

/sys/module/clock_krait_8974/parameters/table_name = qcom,speed3-pvs6-bin-v1

My phone was online with bt on, wifi on, sim on, nfc on, but I turned off all audio, completely silent.

This happened 2 times in 2 different nights. I didn't notice any led blinking, maybe there wasn't any on.

What do you mean with "problem that shows up only on certain (low-quality) chips" ?

All the chips of all OnePlusOne are the same and they could be low-quality?

Or some OnePlusOne are different with low-quality chips?
[ONE Android Development] Tomoms:
No, it's totally normal. After a reboot, the changes are lost. A user in Argon kernel's thread shared some code that you can import into Kernel Adiutor to modify that value more easily, and you can also make the app apply the change on boot. If you're using Kernel Adiutor, this could be a convenient thing to do, but if you have no idea how to do it, I plan to add a note in Argon's thread to explain all the required steps - I'll let you know when it's done.

Thanks.

Ok, thanks. Now that I know that my changes have caused the bug, I'll try to fix it in the next build.

All SoCs of all phones exist in versions that differ in production quality. These different versions are identified with a number called PVS. Each CPU has got its own range of PVS values that goes from 0 to some positive number. 0 means extremely low quality chip, while the highest number means extremely good chip. If I recall correctly, the PVS range for OPO's Snapdragon 801 goes from 0 to 15, but - for example - my older phone, a Sony Xperia SP, had a much smaller range: from 0 to 6. As you can see, your OPO has got a PVS 6 CPU, which means it is a middle/low quality CPU, while for example mine has got a PVS 8 CPU, which is slightly better. Now, you might be wondering what's the actual difference between CPUs of different quality. The answer is: low quality CPUs require higher voltages to operate at each frequency, compared to the high quality ones. Thus, a lower quality CPU is prone to heat up more and consume more battery.

There's another quality indicator in the OPO: that "speed3" label written before the PVS number in the table_name file. I have no idea what it means, but I surely know that in our OPOs, it can either be speed3 or speed1, and speed3 is better than speed1.

Keep in mind that this is a thorny topic and to discuss it properly, we'd need much deeper knowledge in the field of electronics and embedded systems, I think. So I just wrote what I learnt from other discussions that took place here on XDA in the past and from looking at the Linux kernel source code.

I noticed that you and [MENTION=6474041]Syaani[/MENTION] have got the exact same CPU variant in your OPOs. I'll try to come up with a solution for you guys; in the meanwhile, can I ask you to flash Argon kernel v6.1 on top of the latest build and test it for a few days? I'd like to know if the issue exists on older versions of Argon kernel as well. Also, since this issue is (most likely) related to the kernel, can we discuss it in Argon's thread, please?

Thanks!

EDIT: it looks like "speed3" identifies the MSM8974AC (the Snapdragon 801, that is able to reach a frequency of 2,5 GHz, used in all OPOs), while "speed1" identifies the Snapdragon 800, which can only reach 2,2 GHz if I'm not mistaken, and is present in the Nexus 5, for example.
[ONE Android Development] Dolphine_80:
Anytime. Thank you so much! :good:
[ONE Android Development] AliasOfiuco:
Thanks for the detailed explanation.

I will flash Argon kernel v6.1

I have to say that I tested your precedent rom for a week before installing this latest build, so I think you could be right in assuming that it's a kernel problem. I will test it with the older kernel and I'll let you know.

Thanks for everything
[ONE Android Development] Tomoms:
Does anyone remember whether the favorite contacts bug existed since the first build of my LineageOS 15.1, or if it has appeared at a later stage?

EDIT: [MENTION=9485423]Kengat[/MENTION] this is for you. https://xdaforums.com/showpost.php?p=78125203&postcount=2
[ONE Android Development] andyqp:
I'm on (latest?) idprophecy's rom. It looks like the built in dialer shows "frequents" on favorites tab.

On exDialer contacts favorites work as expected.

So maybe it's not your fault :)

Andris
[ONE Android Development] Tomoms:
[MENTION=9247643]Dolphine_80[/MENTION] [MENTION=354058]patp[/MENTION] [MENTION=4293978]AliasOfiuco[/MENTION] [MENTION=7541467]ConnerJSP[/MENTION] [MENTION=1661916]abadasstanker69[/MENTION]

[MENTION=2900692]andyqp[/MENTION], you were right. It must have been an upstream bug that was fixed a few days ago by the LineageOS devs, because today I've synced my sources and made a new build, and the bug is fixed! So here's the new build, that alongside this fix, brings also some optimizations for bionic and a minor update of sqlite: https://www.androidfilehost.com/?fid=11410963190603844734
[ONE Android Development] AliasOfiuco:
Latest build installed, now favourites works perfectly. :victory:

About Argon Kernel, I would like to reproduce the exact condicions that created the "Black Screen of Death". The problem unfortunatly is randomic and not deterministic, so I would like to make the problem show up again, before testing the Argon kernel 6.1 for at least a week, to be sure that the problem was really the latest Kernel.

Thanks again.
[ONE Android Development] abadasstanker69:
You nailed it. Works perfectly now. Thanks! Charging seems to be working better too. Now I just have the issue of low mic volume. Thanks again!
[ONE Android Development] Kengat:
Thanks so much for :) just did that but I have a question should I tick the on boot for both controls? Also should I mess with the maximum USB charging speed as well? I put the AC at 2000 not sure what would be a safe one for the other. Thanks :good:
[ONE Android Development] Tomoms:
Well, if you want your changes to be applied on boot, tick the option, otherwise don't! It's completely up to you, there's no right or wrong thing to do :)

If you don't plan on charging your phone by connecting it to a computer, you don't need to change the USB charging speed.
[ONE Android Development] Kengat:
Gotcha! Thank you so much seriously :)
[ONE Android Development] patp:
Thanks for the update, dialer started contacts now working.

However, search in settings not working since 11 Nov update!
[ONE Android Development] AliasOfiuco:
In which case "search in settings" is not working?

In my OPO is working since 11 Nov update, but my OPO is in Italian.
[ONE Android Development] miltonsaha9200:
How to increase charging speed? On Accubattery i'm getting around 700-900mA
[ONE Android Development] Tomoms:
My OPO's language is Italian as well but I don't think it matters much. Search in Settings has always been flawed for me: sometimes it works, sometimes it doesn't. Did it work perfectly for you on the Nov. 4th build?

Please, try to look if the question you want to ask has been already answered, before posting. I've talked about how to increase charging speed in the 2nd post of Argon's kernel thread, and I've even linked it here, in one of the last pages of this thread.
[ONE Android Development] AliasOfiuco:
On the Nov. 4th build, it didn't work out for me, but now with Nov. 11th build it works well.

About the above "Black Screen of Death" it didn't appear again from the Nov. 11th build. So I'm going to wait for it to show up again before trying to flash the precedent Kernel.

For now the rom works great!

P.S.

Did anyone else have the "Black Screen of Death" problem again with the actual kernel?
[ONE Android Development] Jokert129:
You mean one where its just a black screen and the system technically works, you can go to recent app switcher and whatnot but it doesnt load the launcher ? I have it aswell very rarely but i thought thats the launcher problem.

Will flash the 11th build soon, wanna fix the contacts bug too, maybe the launcher thing will fix itself aswell
[ONE Android Development] Tomoms:
No, "black screen of death", often called SoD (= sleep of death) means that the phone refuses to turn on the screen when you try to unlock it, and nothing else works either (e.g. if someone calls you, the phone doesn't ring and acts as though you switched it off). Someone said that in their case, the only thing that kept working was the notification LED.
[ONE Android Development] AliasOfiuco:
I noticed other 2 bugs:

1) "Android Auto" dosen't start at all, it says that Google Play Service dosen't start. But I have to say that is an upstream bug, given that I come from ufficial Lineage 15.1 and until a certain poit "Android Auto" worked out but from an update on (I don't remeber the date) it didn't work out anymore.

2)Messenger of Facebook most of the times crashes, I don't know if this is an upstream bug or a bug of this build, I don't use Facebook and Messenger Facebook very often.

---------- Post added at 07:09 PM ---------- Previous post was at 06:35 PM ----------

And in this very moment I had my third "Sleep of Death", but now it wasn't during the night, while I left unused my OPO, it was while I was using it, trying to make the torch working. I tried to put in charge my phone but nothing, I tried to use recent app switcher but anything happened neither. There weren't any led on before, so I don't know about the persistence of led notification.

I'm going to flash the Argon Kernel 6.1 right away!
[ONE Android Development] abadasstanker69:
I was listening to Pandora today and got a random reboot with the screen off. I've had this happen a few times but this was the first time I got a bug report I could open.

https://drive.google.com/file/d/1b4WIXtKLFonxDAqCncem46qQn_m_oCyY/view?usp=drivesdk
[ONE Android Development] mohit310:
when clicking power button quickly twice the phone hangs
[ONE Android Development] miltonsaha9200:
I'm on the latest build. Clean flashed. Didn't do any kernel modifications, but getting heating issue :( please help me to solve it. I'm loving this rom. I want to stay in this :(

Also getting battery draining issue :(
[ONE Android Development] Tomoms:
Hello, unfortunately a bug report in this case is useless. The only thing to do after a random reboot is to grab a copy of last_kmsg, please refer to this post: https://xdaforums.com/showpost.php?p=77593458&postcount=29
[ONE Android Development] abadasstanker69:
I actually traced it back to Substratum. The black theme was killing Google play services and a few other Google apps after some recent updates. I disabled the offending overlays and I'm good now. Just never got around to updating my progress. Thanks tho!
[ONE Android Development] FreekX:
I am using this ROM for more than 2 weeks. Awesome performance and endurance in terms of Oreo ROMs. Is this ROM is still alive. Any work in progress?
[ONE Android Development] Tomoms:
Of course it's still alive. In fact, I've launched a new build before leaving home this morning, it contained some new stuff so I hope it hasn't failed...
[ONE Android Development] FreekX:
Thanks mate. Really appreciate it. :)
[ONE Android Development] Tomoms:
Flash news: the build has failed :(

I'll try to fix the errors and release a new update within the weekend.
[ONE Android Development] Tomoms:
Here's the new build: https://www.androidfilehost.com/?fid=11410963190603856785

Notable changes include Argon kernel v8.1 and some optimizations for bionic and dalvik (I'd always thought dalvik was replaced by ART back in Lollipop, but apparently I'm wrong - it still has got a role in the latest Android releases).

Happy flashing :)
[ONE Android Development] maseegal:
Do your magisk modules work? Mine install but the app never shows up. I've also tried installing xposed (through magisk) but I get an error saying it does support the SDK version 27 or the version architecture.
[ONE Android Development] Ruvy:
Found a little bug. Was present in the previous build as well. Hotspot doesn't works first time. Devices gets connected but cannot access internet. Have to restart the hotspot to get it work.
[ONE Android Development] Tomoms:
I use several modules without facing any problems.

--

Out of curiosity: did anyone notice improvements in terms of GPS locking speed on my ROM, compared to the other Oreo ROMs that are available? I'm asking this because in the latest builds I've merged some improvements for GPS, and I'd like to know if they're useful or not.
[ONE Android Development] patp:
I've had a couple of lock-ups - where the phone won't turn on and I have to hold the power button until it reboots. Can anyone tell me how to get a log that might help understand this? I am not rooted.
[ONE Android Development] dabanhfreak:
This is going to sound super nitpicky but there's a activity indicator next to the wifi and mobile data icons in the status bar.

They are like little blinking lights. Super distracting, so much so that I've been going back to the 1015 build via TWRP.

is there a way to get rid of them?
[ONE Android Development] Tomoms:
Unfortunately, if you're not rooted there's no way you can provide me the information I need.

Those indicators slipped into my ROM when I merged a bunch of features/tweaks one month ago. I don't mind seeing them but they're quite useless, so I'll remove them in the next build.