Retrial
Recognized Contributor & Translator
Announcement from dev in Telegram.
[Kernel][Overclocked] No Gravity [2023-08-28] [ProtonClang]
- Thread starter Pierre2324
- Start date
-
- Tags
- gaming kernel ngk overclock performance
OOS Builds intentionnally prevents custom kernels from booting so no it won't work unless you subscribe to their Patreon OOS builds. Just use Q Blobs. At first android Q came with Pie blobs and then afterwards got updated with Q blobs. For the camera to work, kernel needs proper implementation hence why the two kernel variant, now it doesnt matter every single Q ROM has Q blobs.
Okay so good news and not so good news.
So I've lost my Pocopone F1 tried everything and couldnt find it back so I'll have to change phone. More details on that on the telegram group. But posting here for people who aren't on telegram. BTW sorry for the late replies lately, I totally forgot about XDA as most of the things happen on telegram.
What will happen?
I'm still working on the next update and it will be coming soon. This will be the final update for F1 / Mi8. Afterwards there may still be upstream/CAF tag updates and if lucky app updates if new features can be ported easily to F1 from the new phone I'm going to get.
Which phone next?
I'll be getting the Xiaomi POCO X3 Pro. NGK + App development for it is starting so if any of you are switching phone or have it already, you'll find me there. I really don't want to force anyone, but if you plan to have/have the phone or just like my work and want to support me you can do so here: https://gofund.me/743fd7b8
Thanks everyone, NGK and its app really took another big step with the Pocophone F1 / Mi 8 devices.
So I've lost my Pocopone F1 tried everything and couldnt find it back so I'll have to change phone. More details on that on the telegram group. But posting here for people who aren't on telegram. BTW sorry for the late replies lately, I totally forgot about XDA as most of the things happen on telegram.
What will happen?
I'm still working on the next update and it will be coming soon. This will be the final update for F1 / Mi8. Afterwards there may still be upstream/CAF tag updates and if lucky app updates if new features can be ported easily to F1 from the new phone I'm going to get.
Which phone next?
I'll be getting the Xiaomi POCO X3 Pro. NGK + App development for it is starting so if any of you are switching phone or have it already, you'll find me there. I really don't want to force anyone, but if you plan to have/have the phone or just like my work and want to support me you can do so here: https://gofund.me/743fd7b8
Thanks everyone, NGK and its app really took another big step with the Pocophone F1 / Mi 8 devices.
I'm planning to install the other version of NGK with different touch firmware. I'm running on MIUI 12.0.2. I'm starting to have touch issues when playing.
Do I need to clear data and such? Or is it okay to just flash the ngk right away?
Do I need to clear data and such? Or is it okay to just flash the ngk right away?
D
Deleted member 8833290
Guest
@Pierre2324 As you have decided to focus on newer devices, could you provide us your tweaked touch drivers only. So that we can use them on any other kernel. I am asking becausethese touch drivers are amazing. These show very rare touch issues.
Well my kernel always been open source, anyone can take the drivers if they want to. Btw NGK will still receive upstreams and caf tags.
Last edited:
I'm on latest oos 11 patreon build which i think supports custom kernels.... So will this kernel work on it??? Its port from op7 android 11
Weird, I dont know. Those ports are modified a lot and closed source.
Kernel update
Good news!
NoGravity Kernel has been updated to 2.3! Can update directly from NGK app or manually from sourceforge. Make sure you read changelog and notes. Thread updated...
As mentionned this is my finale build for Poco F1 & Mi8, futur updates will be upstreams & CAF tags only. NGK App may still receive updates since I'll be working on it on my next phone (POCO X3 PRO).
Reason for device change is that I lost the F1.
Been a pleasure to work for this big community, hope to see some of yall on a futur device!
#keepDefyingGravity
Good news!
NoGravity Kernel has been updated to 2.3! Can update directly from NGK app or manually from sourceforge. Make sure you read changelog and notes. Thread updated...As mentionned this is my finale build for Poco F1 & Mi8, futur updates will be upstreams & CAF tags only. NGK App may still receive updates since I'll be working on it on my next phone (POCO X3 PRO).
Reason for device change is that I lost the F1.
Been a pleasure to work for this big community, hope to see some of yall on a futur device!
#keepDefyingGravity
Attachments
thanks, pal but does this kernel perform better than the latest etude on PE plus? gonna be switching to this if so
Yeah, facing no performance issues and temperatures are also quite low compared to etude.
D
Deleted member 8833290
Guest
If you do play heavy games with multitouch, NGK outperforms etude, silvercore and optimus drunk kernel. IYou can also decrrease the charging speed from the NGK app to play heavy games while charging without burning your phone.
If you don't play heavy games, stick to the default kernel as custom ROMs do not support third party kernels (it means you may encounter bugs and they won't accept your bug reports).
I flashed this over the June 2021 build of PE+, and everything works great, app works flawlessly. But I noticed that battery charging gets stuck at a specific percentage—82% for me—and does not charge beyond that.
I opened the battery menu in the app, and I had the Charging thermals to “off” (check the attachments).
EDIT: Seems like the negative charging was due to throttling. When I left the device alone to charge without using it, charging came back.
I opened the battery menu in the app, and I had the Charging thermals to “off” (check the attachments).
EDIT: Seems like the negative charging was due to throttling. When I left the device alone to charge without using it, charging came back.
Attachments
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
144NoGravityKernel
No Gravity Kernel 1.0.0 + 4.3 App Trailer
Hey, NoGravity Kernel dev coming from the good old OnePlus 2 here! I'm a graduating student in computer science and I actually work as a programmer. I made a pretty solid kernel for that old Oneplus device and even added Energy Aware Scheduling (EAS) support to it backporting new features like Dynamic Schedtune Boosting to this old 3.10 kernel. With it being pretty much at its apogee, I need a new challenge on a newer kernel (4.9+) while keeping NGK's mindset of Performance/smoothness while getting decent battery life due to added battery oriented features.
For those who want a to know more about my work here is the link to NoGravity Kernel for OnePlus 2.
The Kernel will boot using stock (Pocophone F1) CPU & GPU frequencies that correspond to the Balance Profile when Magisk is present. Overclocked frequencies can be selected in any kernel manager app. Other profiles for battery, performance and gaming can be switched to in my app.
To tweak the kernel easily, here's my No Gravity app! featuring custom profiles (Battery, Balanced, Performance and Gaming). My app offers some features that cant be found in other kernel tweaking apps. You can find them lower in the thread.)
-No Gravity app! support
-Android T (13) ready
-Rebased to full CAF
-Enforcing SELinux
-KernelSU support
-OxygenOS Ports support Please read compatibility section
-9.1.24 & 10.3.7 Novatech Touchscreen Firmware
-Updated, Cleaned up & Optimized NVT/FTS Touchscreen drivers for latency and responsiveness and reduced touch issues
-The two CPUs (Silver and Gold) can be configured completely separate in terms of min/max frequencies and governors
-Unlocked PUBG HDR+Extreme options (Disabled by default, enable it in app)
-CPU Next frequency selection tunable (linear/expnential)
-GPU Overclocked to 835 MHz (GPU overclock/underclock is possible)
-GPU Underclocked to 160 MHz on idle
-Adrenoboost
-Updated energy model
-Pixel Thermals support
-Using Evaluation Thermals
-Own Thermal Suspend API
-Own Thermal Locking Mecanism (Mostly for using NGK thermals on MIUI)
-NAP power saving state for Adreno 630 GPU
-Dynamic Stune Boost
-Devfreq boost and Cpu Boosting drivers
-Disabled ZRAM by default
-FSync Control (ON/OFF)
-Faster Applications Opening speed
-Slimbus Overclock
-Added Fingerprint boost
-Added WakeBoost module
-Added and Using ZEN I/O Scheduler as default for app opening speed && overall Smoothness
-Added Maple, SIO, FIOPS, BFQ, ANXIETY I/O Scheduler
-Westwood(Default) & BBR TCP Algorithms
-DTS Headphone X Software Drivers
-Sound Control support
-Vibration Control
-Charging throttling removed
-Maximum charge rate over USB 3.0
-WireGuard support
-USB Ethernet support
-Controller support
-DriveDroid support
-HDR Video Playback support
-KCAL support
-K-Lapse 5.0 support
-Network Guru app support
-Blocked and tweaked wakelocks (Boeffla & more)
-Fingerprint improvements
-Caches optimisations
-Compilation optimisations
-Debloated
-F2FS Support with GC
-Compile with Proton Clang + Polly + Thin LTO
-Latest CAF Tags merged in
-Always upstreamed to latest! (4.9.337)
-And many more under the hood changes...
-More features...
-Let me know what you want and those may be added!
This kernel should work on any ROM/Ports! Since I love OnePlus and I'm myself a OnePlus 2 user, I will do my best to fully support OOS ports.
Reported to work on: OnePlus 6 Holi Edition, OnePlus 7 OB8 & OB8 Quince, Quarantine Edition. OxygenOS devs do not support custom kernels so if you face any issues with NGK don't post in their groups, post here instead. Latest OOS may have calling issues as reported by some users.
-I recommend before coming to conclusion, give it at least 2 complete charge cycles and then raise any issue.
-I recommend to use my app, franco app or EX Kernel Manager if you need to tweak the kernel further
-CPUs since Snapdragon 845 can't be overclocked from kernel this is why it is removed
-Flash No_Gravity_Kernel-vX.X.zip file in TWRP (Latest TWRP Recovery Recommanded)
-(Optional) - Clear cache and Dalvik => if you do so, Use App Optimization button in NGK App.
Download No gravity Kernel / Download No Gravity App
Donate me! / Telegram Group /
No Gravity App Changelog / No Gravity Kernel Changelog
-The android community and to all my testers for using my kernel and your precious feedbacks and ideas!.
-thanasxda for his experience/knowledge on the Pocophone
- @[COLOR=#00b5d3]_undead[/COLOR] & @[COLOR=#00b5d3]Wmbruckner[/COLOR] for the crowdfunding
-Followings for their donations!
@[COLOR=#00b5d3]Wmbruckner[/COLOR]
-@SquireInk
-@samyak032
-@2WildFirE
-@lucyr03
-@bamz1117
-@jackiass
-@Johnjamess
-@Cocolion
-@patrick
Contributors
Pierre2324
Source: https://github.com/Pierre2324/NGK_android_kernel_xiaomi_sdm845
Version Information
Status: Stable
Current Version: 4.5.0
Created: 2019-11-16
Last Updated: 2023-05-287641Kernel Update!
Good news!
NoGravity Kernel v1.1 for Android [9] Pie released! Please read changelog and notes.
Releases from now on will be separated in 2 builds: Android [9] and Android [10].
Differences between builds:
[POCO][9]NoGravityKernel_x.x.x.zip builds:
-Based on v1.0
-Works any Pie ROMs/MIUI/Ports
-Also works on Q but [10] is recommended for best performance and compatibility
-Will do my best so it gets same features as [10] builds
[POCO][10]NoGravityKernel_x.x.x.zip builds:
-Rebased to full Q CAF since v1.1 (Best performance due to this)
-Better support for Android [10]
Happy holidays everyone here! Here's my gift to the community Hope you'll love it!
See yall later40Useful stuffs
Clean flashing a kernel:
1. Boot into recovery
2. Wipe dalvik/art cache, cache, system and vendor(if recovery have this option)
3. Reboot into recovery (only needed on some recoveries)
4. Flash latest ROM zip
(Optional) Flash other zips like GApps, DFE, etc depending on ROM and your preference
5. Flash latest Magisk zip
6. Reboot into system (yes boot with stock kernel first)
7. Reboot into recovery
8. Flash latest NGK Kernel zip
9. Reboot and enjoy
Not to be confused with a ROM clean flash!
Do not wipe data or internal storage!
Encryption fix
For the ones who uses an encrypted device, those steps needs to be done to worl properly with NGK:
To those who are facing screen flicker/bootloop upon flashing NGK on an encrypted device.
1. Dirty flash your current ROM and boot into system.
2. change your password to whatever you want then click on "No" when it shows "Secure Start-up".
3. Boot into recovery then flash NGK. You will notice that it will not ask for a password even though you are encrypted.
Taking logs
Screen Freezes:
-Connect phone to PC
-Run following commands in terminal:
[*]adb shell
[*]dmesg
Random Reboots:
-When the random reboot occurs press the TWRP button combo to got straight into TWRP
-Send the pstore folder as a .zip file located in /sys/fs/
Any runtime kernel/app related crashes that doesnt make the device reboot or freeze:
-Use Matlog app on play store
-Start recording before the issue
-Stop recording after the issue
-Send the .zip file created
Charging:
Okay lets break it down for yall.
Every kernel on every device has WARM_TEMP and HOT_TEMP values which are usually always 45 and 50 respectively.
When device reaches 40-42C charging rate will decrease more and more until it reaches about 45C where device will stop charging even if its plugged in for safety reasons. Battery must not charge when they are this hot.
Battery thermal removal: this will prevent throttling before battery reaches about WARM_TEMP. Once battery reaches about 45C there is nothing in the world you can do. So yea battery thermal removal is still safe, just a matter of preference because if charging throttles before reaching 45C it will heat less then continue charging but if charging doesnt throttle yea it will charge charge faster under 45C but may heat more so you may hit 45C faster. So as in every other tweaks it depends on user.
As per my tests I would get about those but that may vary for you:
Battery temp (°C) - Charging rate (mA) tuples
46-1800
45-1800
44-2000
43-2600
42-2800
What else? oh yea here are some tips for you to lower temps (cause yes some of you charge while playing pubg..)
Tips for lowering temps:
-Turn off NGK thermals from NGK APP
Right you all need to understand thermals first.. A lot of users are just asking best thermals, best this, best that.. there is no universal bests..
Thermals will throttle performance depending on heat generated.. so yes there is a gain in performance when using NGK thermals because performance will throttle at higher temperatures. Why do I say it depends? Well someone living in a hot place and is getting high temps and throttling will use NGK thermals so he gets more performance for the same temperature point but there is always throttling else a phone would heat too much in the end and be really unsecure and all. That being said, if your device throttle with stock thermals then you go ngk thermals it will throttle at higher temps but in the end may still throttle and if you hit too high temps it will throttle even harder to keep temps low. For those people using normal thermals would be best since yea performance will throttle but it will prevent the phone from getting higher temps which could lead to more intense throttling. (Can also read about charging above you may want more aggressive thermals that will throttling performance to reduce heat so you can charge phone)
So next tip:
-Reduce Big cluster max frequency as this cluster is a hest generator
-Use another profile than Gaming! (Performance for me is best because its less aggressive, some people prefer balance for gaming)
All in all, try stuffs by yourself I think I did my part guiding you through all this, the best things you can do is the best things for yourself not necessarily the best for others.
Touchscreen Tests (NGK v1.5.5):
Spent a whole week with testers to just sit down and find the firmware to choose and then rebuild the drivers from the groud up.. but first here's an intro
Intro:
Small intro for everyone cause many people confuse many things..
-Panels: We have 3 main panels:
FTS, NVT REV1 & NVT REV2
-Touch firmware: comes in kernel and also in ROMs but kernel will flash its inbuilt firmware if the kernel firmware checksum is different to the one already present in ROM
-Touch Drivers: comes in kernel and those dont have numbers/versions its up to the kernel dev to make changes it those so stop asking for driver version no one can answer that precisely compared to firmware
Tests:
Alright now enough talking, the tests and results.
-Panels:
For FTS panels, using stock xiaomi drivers was fine no touch issues seem to happen since those went out.
For NVT panels, some had touch issues on rev1 and rev2 depending on firmware used while keeping xiaomi stock drivers so below tests were focusing on NVT mostly
-Firmware:
We tried 3 firmware and the ones who remained are 9.1.24 and 10.3.7 since other one gave issues
So I did incremental test builds modifying drivers for both firmware
-Drivers:
For drivers, as said before I reverted all changes to xiaomi stock drivers from their source. Some issues were present for some on both firmware version and different issues on both panel revisions (rev1 and rev2)
-Latency:
some issues was only related to latency and I knew latency was going to be better by optimizing the drivers later on
-Touch issues:
So based on that, I only took account of the issues present between firmware for each driver changes
Part 1:
Part 1 was updating novatech drivers from a CAF source that can be seen in my kernel source. So did that, compiled 2 versions again fixed some small issues here and there like firmware flashing wasnt working, touch didn't work at first and some bootup issues, anyway main thing is that novatech driver were updated a bit with less variable locking and such coding changes making the driver faster. Results after that were good it fixed some people's issues but latency wasnt perfect.
-Part2:
Now was time to optimize the drivers and did for both NVT and FTS (most of those optimizations were seen in previous ngk versions) but needed to add them again and add some more and see how they impact (cause not every optimizations means better results, some optimizations introduced issues)
Conclusion:
So in the end if TLDR
The conclusion was that issues were fixed after some driver changes as some optimizations made them worst, 9.1.24 firmware gave better touch (mostly under load or heat a.k.a for gamers) and didnt impact day to day users hence why NGK uses now 9.1.24 drivers.
BUT that is based on the fact that I reviewed the drivers from official xiaomi source, then updating them, then doing specific optimizations, other kernels may have different results or different ways of doing tests, thats just how I did it.
So yea for people who wont like touch, I will send this cause I did work on it to give better touch to most users and limiting the touch issues. I still dont think its possible to have perfect latency and perfect touch due to our phone but here's what has been done..33
Exactly, it takes time cause Im re-doing the app from scratch. There will be more features too. Sorry for the wait but it will be worth it. Im working on something for thermals too on kernel side so a lot of testing is done for that too. You are right and ngk 1.6 will come in 2 variants for people having touch issues on one of the firmware.
To answer the other guy, cant blame kernel directly for battery drain issues. Why? Because most users dont face those. Unless it was a general issue where everyone would see worst drain then yea we could blame kernel for it but on my side I never really see my idle go above 0.9%/h on any profile even performance and I listen to music a lot screen off.
Conclusion, dont worry yall Im still actively working on ngk + app, just that 1.6 is quite big and cant push an half baked update also quarantine is still present here but im no longer at home with a lot of time to spare on development Im back to work since a month so I work on android stuffs at night and on weekends + testing during the day.
Thanks for your understanding. Stay safe guys and defy gravity?
