yashsingh1/xdaforums huggingface dataset:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] foobar66:
Also running r52 now on OnePlus 7T pro, using latest 10.0.7 BA (Europe), working great so far - thanks Arter!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Aqyx:
Hey, can anyone tell me if SELinux is set to enforcing or permissive by default; and if it is permissive, is it possible to set it to enforcing?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] egekonuk:
it says enforcing on my phone
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Aqyx:
Thank you!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] SingularityFX:
Quick question dev, does the kernel require Magisk support to work fully/properly or once flashed I can get rid of Magisk and kernel will still work as intended? I'm on OP7T Pro McLaren and it's working great so far with Magisk on but I'd like to do a system reset and get rid of Magisk and I know the kernel will remain. Thanks in advance.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] idkwhoiam322:
arter fakes enforcing, but is always permissive.

https://github.com/arter97/android_...mmit/b05e01dc024245d8f2e59281911bc05a3403e236
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] beeshyams:
Thanks.

I don't want a default permissive kernel

Edit : OP clearly says it is permissive, so that settles it
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] PetritH:
Anyone has this working on 7T 10.0.8?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] NotATreoFan:
https://xdaforums.com/showpost.php?p=81804985&postcount=805
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
No issues here, working perfectly on 7t 10.0.0.8

Regards ysco..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] egekonuk:
Does anyone having issues with Bluetooth disconnect ?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ulxerker:
Im using BT headphones and a smartwatch and didn't have disconnects so far.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] arter97:
r53b1 is up.

A lot has changed, so I felt the need to mark this as a beta, but I don't expect any major issues.

The Wi-Fi configuration from the ROM is now ignored and the in-kernel one replaces it.

There were some clean-ups and cherry-picks from Qualcomm.

If you notice any difference regarding Wi-Fi's behavior(performance, power consumption, delayed notification, VoIP issues and etc) compared to r52, let me know.

I also enabled USB UASP.

For supported OTG devices, this will drastically improve performance.

I've been able to achieve 485 MiB/s with an external SSD connected to my OnePlus 7 Pro using OTG.

r53b1

Reworked Wi-Fi configuration

USB UASP enabled

Minor fixes to previous memory optimization commits

LV.AU.0.2.0-01800-gen3meta.0 merged

2020-02-05 security patch merged

Linux v4.14.171 merged

Latest Qualcomm's Android 4.14 kernel merged

Wi-Fi drivers updated to 5.2.03.20C

WireGuard updated to v0.0.20200215
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] bpearson325:
Arter97, thank you for the kernel, your work is great. I like to try kernels and ROMs but keep coming back. The performance, battery standby and SoT are far above the others, again thank you!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Darkmasterhk:
[MENTION=4898097]arter97[/MENTION] thanks for your kernel and updates.

I will report back on a few days, when I'm sure, but I get the feeling my battery consuming is a bit higher again, when using my home WiFi.

I had this issue on stock until 10.0.4 and/or changing to your kernel. (Did both at the same time)

Consumption of only increased in my home network, at work it's fine (+1% drain per hour screen off). No idea what is/was wrong with my home network other devices are unaffected.

Edit:

Now even my drain at work has increased.

I only used the phone for about 10min but lost 10% since my original post.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
Thanks for the update mate.

So far so good, seems that it will give me more juice with the latest kernel. Will wait for a full battery cycle and report back. Thanks for the work.

Regards ysco..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ulxerker:
I can't confirm that, battery life seems even a bit better for me (when in use and idle). So maybe something else is wrong, best is to check with BBS.

Same here, till now I experience good results.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Pipould:
Very good kernel on my side after 24h, I'll wait a bit more for final report
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Vullnet13:
http://imgur.com/a/Z0Fpj5U

So guys i don't know why but my phone after i charge to 100% the frist 10% drains the battery not normally after those first 10% than get back to normally i don't know why is that happening i am using this kernel arter97... There is a screenshot
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] vooyeq:
superb battery life in my case
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Amd4life:
Does this kernel work on Havoc, for the one plus 7 pro?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] SingularityFX:
So all good with kernel, fast, smooth, stable, wifi is top speed haven't noticed any super battery drain, except one thing I've noticed so far. After flashing 53b1 (clean oxygen, latest magisk, etc) the McLaren Theme is gone upon reboot. I have a Oneplus 7T Pro McLaren by the way...
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
Same here... But this was also the case with previous versions. Thnik it is because the McLaren version has something merged into the kernel that this kernel dont have...
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
This problem saldy isnt solved for me :(
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
First battery cycle with latest kernel ;)
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jaggillararla:
Next time show detailed usage as well. All we know is that u can have recharged it
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ahmed.ismael:
what he posted is normal ( he haven't recharged but it's lite usage )

my battery backup is almost the same as he posted on r53b1
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] gnabtib8:
delete
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] bsimpson1:
Can anyone on OOS 10 with the latest arter kernel check their logcat to verify that this is happening on other devices? I have a feeling it's causing battery drain on my device

enter:

su -c logcat *:E | grep OpSlaNetlinkHelper

in your terminal app

You will possibly see the following output every second or so:

E OpSlaNetlinkHelper: sendToKernel [OP_SLA_NOTIFY_CELL_SCORE] failed, mNlfd=null !!!

I would really appreciate your help.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] xontax:
:/ # su -c logcat *:E | grep OpSlaNetlinkHelper

03-03 23:51:45.448 1574 1857 E OpSlaNetlinkHelper: sendToKernel [OP_SLA_NOTIFY_WIFI_SCORE] failed, mNlfd=null :/ $ su

:/ # su -c logcat *:E | grep OpSlaNetlinkHelper

03-03 23:51:45.448 1574 1857 E OpSlaNetlinkHelper: sendToKernel [OP_SLA_NOTIFY_WIFI_SCORE] failed, mNlfd=null !!!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] access9:
By newest, do you mean r52, or the beta r53b1?

I see the messages with r52, but what do they mean? My cell data and wifi speeds are fast, and very consistent - I can't remember a time I had a random disconnect or problems connecting. That being said it's probably benign.

I learned a long time ago that unless you've read the docs, or are the dev that wrote the code that logged the error, those messages, without knowing the context in which the occur, are scarier sounding than they actually are.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jimmy123322:
Yap. Arter r53b drains more battery than r52. Confirm that information.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] esi2121:
battrey bakcup time is 1h lower than before in same usage on r53b1
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] esi2121:
removed
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] RicardoDimm:
Currently I have ElementalX kernel installed. What is the best way to install this kernel?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ulxerker:
Dirty re-flash you ROM or just the boot image first (including twrp and magisk). After that you can flash arter kernel.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] LucasGalasini:
Can someone please help me ...

How do I install on OP 7T if I don't have TWRP that works?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ulxerker:
Sure, use Franco kernel manager app to flash it.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Lossyx:
You need to be rooted and flash with Franco Kernel Manager.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Stephen:
Thread has been cleaned.

Thanks for reporting.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] RicardoDimm:
Amazing kernel. Phone feels so much smoother and I notice a big difference in battery life. Thanks!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] insestito:
He many SOT?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] amit_sen:
1st time using your kernel on any phone. Now I know what's the fuss is all about. Excellent job. Using it for 1day only. Buttery smooth... For battery life need to wait. Initial impressions are promising.. rb2 version
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] RicardoDimm:
Got this kernel running with RenovateICE Magisk ROM. Works like a charm!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] SingularityFX:
I thought I'd post my latest experience here since I've been using this kernel for a while on my OP7T Pro McLaren and was happy with it aside for one thing (at least I only noticed one) flashing it makes McLaren theme unavailable. The stats attached are with stock oos kernel, all CPUs on performance governor, 90hz forced at all times and qhd resolution. And I for one am baffled... Or this phone is utterly the ultimate beast.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] da4kgr3y:
Device with this kernel doesnt wake up after doze.

Installed rice and xxx.

Can you suggest snthg? One smurf and bluspark everything is ok
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] elmor0:
Fantastic battery life on the OP7T Pro (stock OOS 10.0.7 HAA). No other issues noted.

Now trying it with Renovate Ice ROM.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] 1aladdin1:
does Magisk Hide work with this kernel?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
Also this problem with newest version... Samsung browser dark mode on official arter site and sites that have nearly the same grey.. Till r50 no problems oneplus-7 7t mclaren... This kernel is fast and fluid so dont know :(
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
https://youtu.be/eIJxh9UGyak Try this
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] :
Delete
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] mani169:
Just a question, would love to try this kernel. Can anybody answer. I am flashing this kernel on my op7 pro with oos beta 10 without root. (Twrp installed) will it work on my device? Thank you.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jaythenut:
You don't need root to install so that's ok, don't know about beta
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] mani169:
Can you tell me one more thing, I want to flash a new custom kernel(arter97) over another custom kernel which is currently installed (weeb kernel). How to do it? Do i need to wipe data and format? Or just flash it over the one installed?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jaythenut:
I just flash over myself ?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] nickname_marco:
I had a fresh install of OOS to setup so I flashed kernel, format data to f2fs, optimized for f2fs then finished OOS setup. So far so good. Did I mess anything or am I missing any sort of advantage?

I am under the impression battery drain is a little high but it's too early to say. Need to give it a few days.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
havent found a solution...

---------- Post added at 10:12 PM ---------- Previous post was at 09:43 PM ----------

After weeks of looking i think i foind the problem... "dc dimming"
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] zeeshanalpha:
Any kernel that would support changing vibrate intensity ? I'm running a custom rom
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
This kernel have the option, see screenshot.

Regards ysco..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Tiz92:
Does anybody run the kernel on top of BlissRom? Does it work?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] zeeshanalpha:
Where can I get this option? Which app is this? Sorry for being noob because I can't see this option on FK

I'm on oneplus 7
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Goku1992:
Im using EX kernel Manager, under Various...
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
On fkm you have this option under kernel settings/vibration.

I'm running on default oos oneplus 7t

Regards ysco..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] zeeshanalpha:
Hi do Im currently using OnePlus 7

And I have flashed this kernel and have to tell it's really improved the battery life and experiencing smoothness.

The only issue I found is it's taking a lot time to charge than stock. Do I have to enable something in kernel manager ?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ysco:
No special settings for fast charging, just works fine and no issues.

Make sure that your cable is pushed far enough in your phone because if i isn't the phone charge slowly. I have had it also few times. You need to feel the click when pushed far enough.

Regards ysco..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] arter97:
r54 is up.

What happened to r53? Too much stuffs changed since r53b1, hence r54.

This release should fix all random lags and stalls, which was caused with previous flawed in-kernel LMK(LowMemoryKiller) implementation.

This also coincidentally fixes rare random reboots that was also caused by previous in-kernel LMK.

Huge thanks to Sultan and the internal testers.

r54

Switched to Sultan's Simple LMK to fix lags and stalls on memory-pressured scenarios

Disabled scheduler debug for better performance

Reduced memory allocations on network sockets

Reworked and optimized vnswap (renamed to vbswap)

Reworked Wi-Fi configuration

USB UASP enabled

Minor fixes to previous memory optimization commits

LV.AU.0.2.0-01800-gen3meta.0 merged

2020-03-05 security patch merged

Linux v4.14.173 merged

Latest Qualcomm's Android 4.14 kernel merged

Wi-Fi drivers updated to 5.2.03.22Q
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] dvd995:
[MENTION=4898097]arter97[/MENTION]

hello, could you consider adding this commit to your kernel that allows you to bypass a maximum battery charge block that oneplus imposes on the phone with recent system updates? This problem has been found on several devices in addition to the one plus 7. Thanks if you listen to me.https://github.com/Pzqqt/android_kernel_xiaomi_whyred/commit/1c5be9991ce6605718a8f66fcc3fc0d6cc07fd55
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] arter97:
That is extremely dangerous.

Those folks should revert it as soon as possible.

Battery capacity goes down as it lives on.

That's a mechanism for preventing battery over-charging and the patch is essentially making it possible for a battery to go over-charge, which can result in swelling and explosion.

It used to be a HW(PMIC) feature with no code exposed to the kernel.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Gordietm:
[MENTION=4898097]arter97[/MENTION] can I flash r54 over your existing kernel in PA?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] arter97:
No.

PA kernel will never be released from me.

PA releases will have the kernel updates directly.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] SingularityFX:
Flashing 54 still messes McLaren theme, possibly other things I'm missing. I realize it's not a priority but could you look into this when you get a chance please? Thanks in advance mate.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] dvd995:
The value, however, was higher with a firmware pie precede this. How do you explain this to me. Firmware owned to date. The phone is only 6 months old

---------- Post added at 09:13 PM ---------- Previous post was at 09:10 PM ----------

@arter97 We did some tests and it is a value that purposely blocks the maximum capacity that is implemented by the manufacturer who lowers it with updates, a worn battery without the block still reaches a lower capacity, which without blocking is however much higher and is still safe to use.

A phone that is never updated maintains the high limit and does not risk anything.

Furthermore, by putting an older version this limit goes back higher.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] NotATreoFan:
Are you using this on the 5G McLaren? I've been wanting to try it, but didn't want to risk a possible factory reset if it didn't work.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] arter97:
Correct, since it's just matching with the nature of Lithum-based battery cells.

lol no.

No OEMs does this.

It's an (intentional) side-effect of updating the BMS(Battery Management System)'s source code.

PMIC/BMS code is mostly from Qualcomm.

Qualcomm's BSP never had any intentional piece of code for planned obsolescence, and it'll be immediately be noticed from the community.

Yes, because it's implemented at a hw level too as an additional line of defense.

That's just your assumption.

Why do you think OEMs implements this in the first place?

What makes you think it's "safe"?

How big is your sample size?

Did you study the relevant source-code and hardware properties?

This could be one of the following:

1. OEM noticed a flaw in the code and improved it.

2. OEM noticed a new property/flaw in a shipped hardware and updated the software to solve/workaround it.

3. A newly updated code reporting in a different manner.

4. Functional code feature-wise, but with defective reporting.

All of those 4 are extremely common.

And from your assessment of "putting an older version this limit goes back higher", it's extremely likely that it's the 3rd or the 4th from the above.

Aging values are usually written to a hardware register. If an OEM planned a "planned obsolescence", they would have just written the intended values, which won't be recoverable by installing an older version of the firmware.

My OnePlus 7 Pro reports 60% of the real capacity despite almost never using the DASH/WRAP charger, meanwhile my 7T Pro reporting 115% of the real capacity, which also leads me to think it maybe the 4th from the above.

Both of the devices drains about the same when I put a load on it, which means 60% report from my OnePlus 7 Pro is very inaccurate.

Battery management is extremely complicated. 40k lines of code in the OnePlus 7’s kernel are dedicated for just that.

And if you think you can somehow “fix” it with deleting 10 lines of code with short-sighted observations, you would be very wrong.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] dvd995:
[MENTION=4898097]arter97[/MENTION] if I buy a new one plus 7 and update it, I will have this value recalibrated as if the battery was already worn compared to the beginning. If there is already a hardware block the software block is not needed, none of those who made this change had problems but only improvements and no heating or anything else. Even if you raise that value it's not that you can charge the whole battery if you don't also raise the voltage.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] amit_sen:
On a side note from all the battery talk, r54 is running smooth as expected Will update post if I find anything interesting. Flashed over rb2 from Franco kernel manager. Using OP7T.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Darkmasterhk:
I strongly support this, I don't know exactly how the bms in a smartphone works, but my experience as an engineer is never mess with lithium battery.

If people think they know their phone or distrust the bms, they should compile the kernel on their own and see how it works out.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Unknowx:
I NEED URGENTLY FOR HELP!

I have performed the procedure to change the filesystem in F2FS and now I find myself the OnePlus 7 pro in FASTBOOT mode.

I tried to fleshare the image of the latest stock ROM but it doesn't make me run it! I have no recovery nor the possibility to go further!

These are the errors he releases me if I try to run the command to fleshare the rom from fastboot

Bootloader Version...:

Baseband Version.....:

Serial Number........: 99a6e771

--------------------------------------------

extracting android-info.txt (0 MB) to RAM...

android-info.txt syntax error: ´╗┐require product=msmnile

Setting current slot to 'a' OKAY [ 0.009s]

extracting boot.img (96 MB) to disk... took 0.276s

archive does not contain 'boot.sig'

Sending 'boot_a' (98304 KB) OKAY [ 2.163s]

Writing 'boot_a' OKAY [ 0.390s]

extracting dtbo.img (16 MB) to disk... took 0.040s

archive does not contain 'dtbo.sig'

Sending 'dtbo' (16384 KB) OKAY [ 0.360s]

Writing 'dtbo' OKAY [ 0.068s]

archive does not contain 'dt.img'

archive does not contain 'recovery.img'

extracting vbmeta.img (0 MB) to disk... took 0.001s

archive does not contain 'vbmeta.sig'

Sending 'vbmeta' (8 KB) OKAY [ 0.012s]

Writing 'vbmeta' OKAY [ 0.003s]

archive does not contain 'vbmeta_system.img'

archive does not contain 'super_empty.img'

archive does not contain 'boot_other.img'

extracting odm.img (100 MB) to disk... took 0.207s

archive does not contain 'odm.sig'

Sending 'odm' (102400 KB) OKAY [ 2.231s]

Writing 'odm' OKAY [ 0.319s]

archive does not contain 'product.img'

archive does not contain 'product_services.img'

extracting system.img (3472 MB) to disk... took 12.924s

Invalid sparse file format at header magic

archive does not contain 'system.sig'

Sending sparse 'system_a' 1/5 (768317 KB) FAILED (Error reading sparse file)

fastboot: error: Command failed

Press any key to exit...

I HOPE SOMEONE CAN HELP ME! THANK YOU!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] fonix232:
**** me with a stick in the desert, I have been wondering if it was the kernel, or OB1 on my OP7TPro that was causing the reboots! Installed the new one, and all the issues seem to be gone. Thanks for the work, it's much appreciated.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] twoxa:
So any actual advantage in battery life using this kernel?..
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Unknowx:
Don't mind the post before, I solved it. Do you activate the ram boost of oxygen os with this kernel?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] sneakerspark:
No
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] knpk13:
Why don't you use fast charging? Does it reduce the lifespan of the battery? I just a got 7T Pro (upgraded from 3T) and I'm debating on whether to return it and keep the 3T because of the curved edges that distort text/images and glare. Don't they bother you?

I'm kinda upset because the phone is otherwise really great and I can't find a similar one without notches or holes.

Also how do you check the battery capacity? My 3T is almost 4 years old and I've been using the stock dash charger for it. The battery seems fine to me though and I get get good SOT. My laptop battery on the other hand can't hold a charge for more than a couple hours and the decrease in battery life is quite noticeable.

Edit: I thought I'd ask [MENTION=3873953]eng.stk[/MENTION] and [MENTION=4683552]maxwen[/MENTION] for their opinion on the curved edges as well since I noticed those devs also have the device.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] mytechtb:
hey [MENTION=4898097]arter97[/MENTION]

i just wanted to know that some people has reported boot loop on open beta 1 update..since i an using open beta too...so is it safe to install or wait for next build