The ROM itself has to add an option for this, otherwise it is not possible, even if I add a file to toggle it, the kernel manager app would also need to add support for it.
[KERNEL][Oreo/Pie/10] Fz Kernel
- Thread starter Feinzer
- Start date
The ROM itself has to add an option for this, otherwise it is not possible, even if I add a file to toggle it, the kernel manager app would also need to add support for it.
I am using official lineage os 16 and there is an option to turn off the gesture vibration under Settings -- System -- Gestures -- Touchscreen gestures
And to turn off the haptic feedback. I always keep it turned off and after I flashed the fz kernel I noticed that the feature is broken( I mean I am not able to turn off vibration). I hope this is what you have mentioned in the above post. I am asking if this toggle can be fixed?
Attachments
Last edited:
The haptic feedback for the gestures is being disabled correctly, as I said, it is a forced vibration that only happens on double tap to wake the phone. These are two different things
Do not do this, LOS trees saves the init files for the kernel on system, instead of ramdisk. Meaning they won't get deleted when you replace the boot.img and hence could cause inestabilities.
To uninstall dirty flash the ROM.
No you don't need to, the camera on POSP and ROM's using those trees sometimes crash on reboots, it is not kernel related.
For the kernel app, I personally use smartpack kernel manager.
Thanks for the info. Mine the camera almost constantly crash on reboot and i need to reboot again until the camera is ok.
And thumbs up for this kernel. Smooth as fish
I am not having that issue myself, did you try doing that with the stock kernel of the rom you're using? Also if you are using ANY mods or magisk modules that could be related uninstall them and test.
In any case please state the ROM you're using, the kernel version, if magisk and magisk modules / mods, and send a log while trying to send a video and getting the error.
I'm pretty sure it's kernel related issue. I'm currently using Official Nightly LineageOS 16. When I switched to the Tomoms' kernel, the issue changed, to the one that I stated on his thread. I've also faced this issue using your kernel on the Tomoms' LineageOS 16 build, and the problem was identical, so there's no relation in the build.
I'm not using any Magisk, module, modification or nothing. Just vanilla LineageOS and the kernel.
I have the same problem, here is the log when the error occurs:
2019-06-19 12:15:24.641 428-428/? E/QCOM*PowerHAL: Failed to acquire lock.
2019-06-19 12:15:24.753 428-428/? E/QCOM*PowerHAL: Failed to acquire lock.
2019-06-19 12:15:24.971 466-26178/? E/OMXNodeInstance: getConfig(0xb17fa004:qcom.encoder.avc, ConfigLatency(0x6f800005)) ERROR: UnsupportedIndex(0x8000101a)
2019-06-19 12:15:24.972 466-580/? E/OMXNodeInstance: getConfig(0xb17fa004:qcom.encoder.avc, ConfigAndroidIntraRefresh(0x6f60000a)) ERROR: UnsupportedIndex(0x8000101a)
2019-06-19 12:15:25.079 466-578/? E/OMXNodeInstance: getParameter(0xadca1004:qcom.decoder.avc, ??(0x7f000044)) ERROR: UnsupportedSetting(0x80001019)
2019-06-19 12:15:27.270 466-466/? E/OMXNodeInstance: getParameter(0xadca1004:qcom.decoder.avc, ??(0x7f000044)) ERROR: UnsupportedSetting(0x80001019)
2019-06-19 12:15:27.374 466-580/? E/OMXNodeInstance: getParameter(0xadca1004:qcom.decoder.avc, ??(0x7f000044)) ERROR: UnsupportedSetting(0x80001019)
2019-06-19 12:15:27.419 8990-8596/? E/ACodec: [OMX.qcom.video.encoder.avc] ERROR(0x80001009)
2019-06-19 12:15:27.419 8990-8596/? E/ACodec: signalError(omxError 0x80001009, internalError -2147483648)
2019-06-19 12:15:27.419 8990-8595/? E/MediaCodec: Codec reported err 0x80001009, actionCode 0, while in state 6
2019-06-19 12:15:27.560 428-428/? E/QCOM*PowerHAL: Failed to acquire lock.
Ok thanks for the log, it didn't say much but I was lucky enough that I suspected it was related to I/O, although my issue wasn't the exact same, whatsapp would get stuck after trying to send a recently recorded video, and when trying to watch the video on whatsapp, it would be distorted. Turns out it is in fact related to I/O, seems like it happens when using deadline, maple and row I/O schedulers.
So I'll be disabling those in the next version while I see if I can fix them, for the time being you can change the I/O scheduler to bfq, zen or any other and it should start working again. Thanks for the report.
Thanks for the answer, but I'm sorry to inform you that I was on bfq scheduler (or at least that's what SmartPack was saying) when I took that log, so I tried switching to zen and the problem still occurs. If I can help in any other way feel free to ask.
Ok so I tested a lot of my old and newer versions and they all suffer the same issue, in fact, I went to official POSP without any mod, no magisk and no custom kernel, just stock, and it still happens.
I am not sure if it's kernel or device tree related, however seems to be a universal issue as of now.
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
27Code:
#include <std_disclaimer.h> /* * Your warranty is... still valid? * * I am not responsible for bricked devices, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this Kernel * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */ NOTE »
Fz Kernel
Only for 8.1, 9.0 & 10.0 ROMs.
ABOUTThis kernel was made using the current LineageOS kernel source as base and merged all the necessary changes to work on Android 10 (Ten). On top of it I then added some features for it to be customized by each user if they do want to.
Feature list
- Replaced Qualcomm cpu-boost with Sultanxda cpu_input_boost driver.
- Replaced Qualcomm MPDecision with NVIDIA CPUQuiet driver from Tegra CPUs.
- Charging current customization Interface.
- Voltage control for undervolting.
- KCAL Color Control support.
- Simplified Thermal driver.
- Franco's Wakelock blocker.
- Franco's Sound Control.
- Franco's Backport of POWER_EFFICIENT workqueues.
- Enabled Multicore power saving.
- A LOT of under-the-hood optimization changes from Sultan, Franco, Boeffla, arter97 and many others.
- Fixes USB MTP without enabling USB Debugging.
- Fixes Data Saver.
- Smooth default kernel behavior using ZaneZam's zzmoove governor with ZZ Battery Plus profile.
- Custom Governors:
- Alucard
- Impulse
- Intelliactive
- Intellimm
- Lionheart
- Smartmax
- zzmoove
- Custom Hotplugs:
- MSM Hotplug
- AutoSMP Hotplug
- CPUQuiet
- Custom I/O Schedulers:
- FIOPS Scheduler
- SIO Scheduler
- TripNdroid Scheduler
- zen Scheduler
DOWNLOAD HERE
OTA Updates
Going forward, kernel OTA updates will now be handled via Franco's Kernel Manager app. Users may import the following URL in FKM Flasher to receive updates:
https://raw.githubusercontent.com/Feinzer/fz_kernel_data/master/ota/release.json
Thanks to
CyanogenMod / LineageOS
Ak
Nikhil18
DeadlyIndian
ArtxDev
Sultanxda
franciscofranco
ZaneZam
Lord Boeffla
flar2
Adithya R.
Tomoms
Idprophecy
All of this is possible ONLY because of the work of these people and teams. Thank you.
XDA:DevDB Information
Fz Kernel, Kernel for the OnePlus One
Contributors
Feinzer, LineageOS, AK, Nikhil18, DeadlyIndian, ArtxDev, Sultanxda, franciscofranco, Lord Boeffla, ZaneZam, flar2, Adithya R., ab123321, Tomoms, Idprophecy
Source Code: https://github.com/Feinzer/fz_kernel_oneplus_msm8974
Kernel Special Features:
Version Information
Status: Stable
Created 2019-05-23
Last Updated 2020-01-1514Well guys, I finally updated the thread. New build is up in Google Drive and everything seems to be working and all features are now present after the rebase to LineageOS source code. The default profile at boot is the same as before.
As for you, I'll be PM'ing you so you can test those features before I release it, hope that's okay for you8
The CPU is not forced to 1.9Ghz, so you can just select it right back to 2.4Ghz using a kernel manager. For the hotplug, if you want to use a hotplug or disable the hotplugging behaviour (The one that turns the cores on and off) please go to the CPU section and where it says CPUQuiet Governor, select "userspace". Doing this will disable the CPUQuiet hotplug and you can use other hotplugs if you so want to.
There is no temp control file? You just control at which temperature the CPU will start throttling, is 65 by default but you can make it higher if you need to (But I do not recommend it because the phone will get hot.)
Is a new version of the kernel in the works? I would be really glad to see some updates
Yes, but I won't be adding any exciting features, It's mostly just a cleaner code rebase and removing conflicting features. I recently rebased the kernel to LineageOS' sources because Thunder/Lightning's history is quite messy. I am currently testing some default profiles before making a release build.
Regarding CPUQuiet I think I'll be removing it in the next release, or at least disable it by default, mostly because it's not really making any difference.
I have to be careful on what I'm adding to it because it can mess up the performance a lot even if it seems unrelated, for example interactiveX governor was causing issues so I will not be including it again.7Reserved
Changelog:
- Fz v4.3:
- Removed CPUQuiet Hotplug driver.
- Added Intelli Hotplug driver.
- Updated installer zip to anykernel3.
- Added FKM OTA Support
- Fz v4.2:
- Added ZRAM (Disabled by default)
- Removed Maple I/O Scheduler due to reboots caused by it.
- Back to good ol' zzmoove default setup.
