new YAAP build Version: 11.0 20210414 for 7T have patch for proximity sensor.. ) please add it also into the kernel)
This was fixing an unrelated issue, happened when the device booted too quickly, would cause all sensors to disappearIt's always good to add the matching commit(s) to help the dev quickly see where and how it was fixed. It does make it easier to add it if the dev doesn't have to search for it
A quick look lead me to the device source code that apparently fixes it: https://github.com/yaap/device_oneplus_sm8150-common/commit/c2bb1ab44a16d81e066509bd5f44eefaaaa041bc
I couldn't find any matching commits in the kernel repo of YAAP unfortunately.
same commit in last derpfest R ROMThis was fixing an unrelated issue, happened when the device booted too quickly, would cause all sensors to disappear
My money is on https://github.com/yaap/device_oneplus_sm8150-common/commit/351f2335b207c62eb7f33554f24272614e094e62
As for how it's fine on stock kernel + OOS but not on custom kernel for OOS, "for all intents and purposes, stock kernel is patching something but we don't really know"
again the wrong one, this is for when there's a race condition during boot which leads to entire sensors stack being dead not just proxsame commit in last derpfest R ROM
* fixes broken sensors due to race condition Signed-off-by: Omkar Chandorkar <[email protected]>github.com
yeah both of the fixes are rom side, maybe someone could try replicating it on oos and checking prox with custom kerneland that is for the rom and not for the kernel itself or am I lying there ??
No you didn't do something wrong. Custom roms change the backend for the gestures in the kernel.I just installed the newest Kernel on my 7 pro running official LineageOS18.1 and being on the newest OOS11 Firmware files. Everything seems fine but the double-tap to wake feature stopped working. It is surely not a dealbreaker but I wanted to mention it regardless. Maybe I did something wrong tho I don't know.
Yeah a telegram group would be awesome
No everything one needs can be found in this thread.Does this kernel has a telegram group?
Hi freak. Post installing the kernel, charging slows down compared to stock kernel. In FKM it shows only 7.7 W with Current 1818 ma and voltage 4.17 volts. Though in stock it's 12 to 13 volts. In case possible please have a look into it.
Befor in A10 this was never the case. Thanks
This means 30 W (5*6). Usually One Plus 7 stock charges between 12 to 13 W and was same with Freak Kernal till A10 but now it charges approx 7.7 W. So I just wanted to inform him in case he would like to check it.the stock oneplus (7t warp 30) charger can only handle max 5 volts with a maximum of 6000mah
I wondered always if it's possible to use as kernel 5.10/11/12 (mainline or newer lts)
Let's say, you guys port always the minor revision updates of 4.14.xxx to the current sources that you have.
But it should be possible to port device specific modules to upstream instead?
I mean, yes i know that it will be a very hard task, because some things are incompatible and needs changes etc, and you will need to track oneplus changes and port them upwards... instead of backwards porting of 4.14 updates.
But since the Qualcomm drivers at least are in the upstream kernel anyway, it shouldn't be thaaat impossible
So why no one ever tryed or did this? Just because it is that hard? Or is the 4.14 kernel any special, like a specifically android tree?
I mean almost every newer android phone is based on 4.14, i seen that myself, but an 5.12 kernel on an android device, would actually be impressing
Don't take this as anything, i just want to understand it, not asking to port anything or whatever.
there have been some people who tried to run the kernel 4.4 and 4.10 (stock is 3.x.x) on an axon 7, but because you couldn't find everything for porting and it was not stable, you let it go again. So it is impossible but not very expensive where the 5.4 kernel is divided into two parts: boot.img and vendor_boot.img because the 5.4, if I understood correctly, is a gki (generic kernel image) and devices have specific data (drivers and co) are provided from the vendor_boot.img because they are not contained in the boot.img themselves.
aner from 4.14.x to 4.19.x should be easier to do than the jump from 4.14.x to 5.4.x (but I have no plan myself)..
but if someone who knew about it would want to try it (if @Freak07 would want to test something like that) I would agree to test it with my 7t
I don't think it's really worth it, really important things gets mostly backported to lts kernels, new features doesn't get added, but new features inside a kernel needs to be used by userspace too (programs/code that uses the kernel). So basically there is almost no benefit.
my question was only meant to understand the reason. didn't wanted to start a discussion about it.
Things where we would actually benefit needs to cherry picked and ported... like a more efficient lz4 algorithm or any other more efficient better code, that is compatible and used by userspace.
Sure, probably there are many things that the kernel handle itself, that gives us benefits, without any "android" code that "controls" it and sure probably there are some things or more things of that if we would actually switch to 5.12 for example, but the risks and work is high to detect and fix the broken functions that probably negates the benefits.
However, all what i mean is, it's a lot of work and a project, where the time could simply be better invested. If @Freak07 wants to try it, it's his time and choice.
but for me personally, i would rather benefit from a kernel that is working/optimized for custom roms like derfest/crdroid etc, instead of oos. With cherry picked things that makes my device actually faster/more powersave etc...
But as you see, in the conclusion everyone wants something, or wants something new, or likes to experiment etc, that's why we are here and customize our phones at all
But im not going to request anything, just wanted to know why i never seen an new kernel for our devices.
Can Oneplus 7 pro sprint 5g use this kernel?
I have no idea what you´re talking about. I think people moved on, have less time, their life changed or have simply no motivation to update their project to Android 11. After all everyone of us does this for free and as a hobby.@Freak07 ,thanks for you time and great work ,
i have question about kernel on A11 for 7 pro , i saw other developer like arter97 stop develop kernel on A11 for our devcie because of precaution damage to device , what can be happen with custom kernel to device on A11 and why its that?? thanks