Vibration is working fine here. Doesn't sound like a kernel issue. If it was the phone wouldn't vibrate at all and it would be completely broken most likely.Anyone having trouble with haptic feedback? I've always felt it was a little bit light on this phone but now I'm having problems where it doesn't vibrate at all to the touch or any other action that would trigger it. Phone calls vibrate.
Been through the system settings and app settings to make sure nothing got messed up when updated to October.
Since DerpFest isn't stock Pixel firmware, it wouldn't surprise me if this kernel just won't work with it correctly.i would like to install this on derpfest 13, but i also lose root if i do so and cannot flash magisk in recovery.
maybe the problem is the preinstalled radioactive in derp.
i flashed it with exkm, with this i lost root and did get stock recovery (instead derp) where i could not sideload magisk
someone knows how to do it? =)
Can you share a log of the flash?
Will try to next time because 7.0 was pushed yesterday and as of right now, I can't even flash Magisk on stock boot.img nor of course install 4.2.0
No derpfest 13, but should be the same. I use magisk 25.2, you can sideload the apk and don't have to rename. Guess we should stop now with OT.
The only way to keep root is to flash the stock rom's patched boot.img (yes it works)I have did your tutorial seriously :
- I take boot.img of ROM
-I unpack using Android boot image editor ( cfig github ).
-I replace zimage from kirisakura zip
-I repack to boot.img.signed
-in fastboot I flash all img from kernel kirisakura + boot.img.signed
Reboot , its boot normally in kirisakura kernel without root
In magisk v25.2 I patch boot.img.signed
I flash magisk img generated
Its boot but magisk still no working
For me now :
I prefer use kirisakura kernel without root as its work great to stock a13 kernel used in lineage actually. ( since I no use app root despite no module kirisakura then ).
There are sources for QPR Beta available, that´s not the problem.
No there´s no telegram group. Everything you need is here on XDA. All information is in the first few posts. If you use the search function you´ll find even more I guess.
No, that´s not related to the kernel. The framework decides how the framerate is handled. The kernel just provides the endpoints the frameworks decides when to switch from and has nothing to say about this.
Neither do I have a problem running my kernel with now playing enabled