yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Snapdragon)] VlitalityX:
Probs need to get a new battery.
[Galaxy Note 4 Android Development (Snapdragon)] gangpe:
Hey kevintm78,

Should the beta v4 version work with stock note 4 roms? I just tried with an older t-mo rom, but it never made it past the note 4 logo screen. Just curious...

NM - Turns out it was a bad flash. Reflashed it recently, and v4 works great. Thanks again for all your hard work!
[Galaxy Note 4 Android Development (Snapdragon)] xda-graphite:
the same here on n910f
[Galaxy Note 4 Android Development (Snapdragon)] li0nh3art3d:
Yall should really look into magisk. Supersu is being discontinued
[Galaxy Note 4 Android Development (Snapdragon)] RadeonHD4250:
This kernel is almost perfect performance wise aside from the random reboots that happen literally out of the blue. I've been living with it since it happens just once every few days. I see a few others have the same issue.
[Galaxy Note 4 Android Development (Snapdragon)] Halcyon:
Thanks for your reply dear, Yes Hani. K is a nice guy I'm in contact with him too he don't develop his kernel anymore though.

Same kernel with more recent source is also awesome! My Device has a new stock rom on it but this kernel is soo old causes some random hangs sometimes. But overall works brilliant.

I think if going up to 3.10.108 would improve the quality so why not, but if it's hard and there's no difference then I'm ok with the one in the H. VITAMIN but its 3.10.40 as I've checked in the settings.

I'm using a N910G variant (with N910F stock Rom Actually), your help will let me use my old device for another year.

Thank you for helping Note 4 Community! :good: :highfive:
[Galaxy Note 4 Android Development (Snapdragon)] glhelinski:
I have maybe a strange question/request. I have the verizon note 4. I've tried a couple different roms now and am puzzled by something....maybe a different kernel (or modification of) can take care of.

I typically have my phone powered off a lot. Powered all the way off...for days at a time. If I shut down the phone (for storage) in the "normal" way, within a week the battery will be dead.

BUT, if I reboot to TWRP and use TWRP's power off, then within a week there is no drain whatsoever. This makes me think that "normal" shutdown is just hibernating the phone...thus the drain.

Is this something that a change of kernels could fix? The TWRP shutdown works but I find it annoying

Thanks
[Galaxy Note 4 Android Development (Snapdragon)] ghostwheel:
A hardware solution would be to rotate the battery in place.
[Galaxy Note 4 Android Development (Snapdragon)] glhelinski:
thanks but that would be more trouble than using the TWRP shutdown method
[Galaxy Note 4 Android Development (Snapdragon)] sxg75:
Would support for "USB Gadget Mode" be possible?

Like used for USB Mass Storage Mode (UMS)? See USB Mass Storage Mode Enabler
[Galaxy Note 4 Android Development (Snapdragon)] Zaileion:
Does not work on sprint 910p. Wish it did!!!!! Large donation for anyone who makes it work on sprint!
[Galaxy Note 4 Android Development (Snapdragon)] Netharion:
What doesn't work? Boot loot?
[Galaxy Note 4 Android Development (Snapdragon)] annoniem:
Are there leftovers to manually delete when flash other kernel?
[Galaxy Note 4 Android Development (Snapdragon)] u81:
Are there any N910F users here V3.1 successfully with Alexander's Dev Base 4.6 without any battery/fast charging/ other problems?

If so, please share your baseband/bootloader info.

I'm running N910F, DQL2 baseband and DQL1 bootloader and a new genuine Samsung battery with the stock Dev Base Kernel and having a lot of battery charging/ fast charging issues and the phone booting into download mode automatically so wondering if this kernel is likely to help.
[Galaxy Note 4 Android Development (Snapdragon)] CRuSH MS:
Xposed installer

Is there any xposed installer for 910t build? This might make my work easier... thankyou in advance :o
[Galaxy Note 4 Android Development (Snapdragon)] MEMOREX2:
When the beta kernel changed to stable with new optimized code?:victory:
[Galaxy Note 4 Android Development (Snapdragon)] chimmot307:
I'm planning to buy Wubatec 10000 mAh battery. Does Flashpoint v4 beta will compatible with the battery ? Or still acknowledge its 3220 mAh in system.

Currently running Apocalypse X MM rom.

Thanks in advance.
[Galaxy Note 4 Android Development (Snapdragon)] Raven_999:
Have you at least read the OP? THERE are links to default kernels and ZL version ones(extended battery patch applied). And yes it'll work with your extended battery. I have a TQTHL 11800 mAh and it gauged the battery meter pretty well after a few cycles, but FP is kinda draining it. Try it, if not there's other choices as well
[Galaxy Note 4 Android Development (Snapdragon)] Jdgame:
Please up kernel overclock for note edge n915f android 6.0.1.

Thank very much !!!!!!!!
[Galaxy Note 4 Android Development (Snapdragon)] chimmot307:
My bad.

Is it really THTQL 11800 mAh ? No shipment to my country (Indonesia) for your kind battery.

My OEM battery (3220 mAh) only last 3-4 hrs SOT. Does anyone have the same SOT ?

SM-N910P running ApocalypseX_MM 8.1.0 Final, Magisk rooted, delete all Samsung bloated apps, Xposed, Amplify, Greenify, Force Doze, PowerNaps, Doze for Magisk Module, AppsXposed still only last 3-4 hrs SOT. Any suggestion to increase SOT while waiting for my Wubatec 10.000 mAh to arrive ?
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
I'm not sure if I can do a whole lot about battery life. I've tried looking at other kernels, seeking advice from real developers, and looking at how AOSP roms get such good battery life. Personally, I've never gotten anything more than 3-4, maybe 5 SOT with any stock based rom/kernel. Others claim that it's possible and I suppose I believe them but that hasn't been my experience with either of my note 4s.

Admittedly, I don't use any battery saving methods. Sync, WiFi, and location are all on. I don't use xposed/greenify or anything like that so maybe that's why but I honestly think this is just about as good as it gets in terms of battery life. I'm going to keep trying for improvements in that area which will probably include ditching all of the overclock features (they seem to be a bit frivolous anyway) and I'm definitely open to suggestions if anyone has any but it sort of feels like a wild goose chase.
[Galaxy Note 4 Android Development (Snapdragon)] YG007:
Hello kevintm78!

I just got a note 4 (moved from note 3 [gotta have that removable battery!]) and I use your kernel. Firstly, thanks for all your hard work for making the note 4 a better phone to use!

I'm currently using your note 4 beta unified kernel v4 and was wondering if you can reimplement these options for the interactive governor?:

sampling_down_factor

screen_off_maxfreq

sync_freq

Also, when comparing to your previous 3.1 release I think there were other options like: up_threshold_any_cpu_freq, up_threshold_any_cpu_load, single and multi _enter_load, _enter_time, _exit_load, _exit_time... Is there a reason that these options are removed?

-- For the overclock features, maybe have one version for OC and one for regular 2649MHz max? I don't OC because of battery life, so I undervolt each MHz setting and I set my max CPU to stock 2649MHz max using kernel auditor, but it still can use the higher frequencies during boot. Other people might still want the OC capability, but those are my thoughts...

One more thing, is it just me, or is there no option to change the voltage for 2457MHz? On apps like CPU Spy, it says that 2457MHz gets used, but when you go to Kernel Auditor the list shows only ...2342, 2419, 2496....

Thanks again for an awesome kernel!
[Galaxy Note 4 Android Development (Snapdragon)] StarBusters97:
Did you find any solution yet ?

I am using 3.1 Flashpoint kernel on SM-N910V with racerom v13 and having same problem random reboots.
[Galaxy Note 4 Android Development (Snapdragon)] m0usju1c3:
I've tried MANY kernels including Flashpoint 3.1 and 4, they all have made my phone randomly reboot at some stage. My work around is to disable 4G/LTE mode in data settings.
[Galaxy Note 4 Android Development (Snapdragon)] andy8858:
I am using race rom v14 with flash kernel 3.1 and my fhone work nice with it
[Galaxy Note 4 Android Development (Snapdragon)] StarBusters97:
Thanks for quick replay but i am using 4G data regularly so i will move back to stock kernel Flashpoint V1 which i was using before with help of data fix. compare to 3.1 kernel it has less reboots while using 4G data.
[Galaxy Note 4 Android Development (Snapdragon)] YG007:
So I observed two things over the weekend:

1. No matter what you do or set in the CPU settings/hotplug, two cores are always active, even if you tell the hotplug to use minimum one core.

2. In the two cores that are always active, one of the two cores is always at the maximum CPU frequency. Also, the maxed out CPU core alternates between the two active cores.

The ROM I'm using is Apocalypse 8.1.0 with the beta v4 kernel (the 3.1 kernel wont allow the Apocalypse 8.1.0 rom to boot). Even if I try to debloat the ROM further, the CPU usage is the same and two cores are always active. Going into a process monitor app shows that the CPU usage is very low and shouldn't be using that much CPU (about 15% usage or lower). No matter what you change the CPU max frequency to, one of the two active cores when the CPU is idle will almost always be maxed to that max frequency. I think this could be one of the reasons that the battery is draining quickly when the screen in on. While the screen is off, the phone battery life is great.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
Keeping 2 cores on has been a little controversial and I promise that will be removed in the next update. It was done on purpose with this commit and the reason behind it can be found here. Funny enough, that commit is also present in nearly all the note 4 kernels but I don't believe I've seen this brought up in any of the other kernel threads. It's supposed to help save battery according to the tests ran by senthil360, but since core control can be done with KA I suppose it's not really necessary to be hard coded in the source.

The problem with 3.1 not booting for you is going to be a little trickier to figure out I think. What seems to be the problem is two xbin files that are included in the zip, but when I removed them for the v4 beta it will not allow F2FS to work properly (or at all). I'm curious, do you have an F or G model?

I've been agonizing a bit over how to proceed with this kernel which is what keeps setting the update back. Honestly I believe a lot of the added features should be removed and I'm definitely going to go back to the original Interactive Governor that's in 3.1. In v4 the Interactive Governor was replaced with an upstreamed version, but I've never been thrilled about how it works. The beta version has quite a few "experiments" in it and if it wasn't for the fact that some people can't boot 3.1 I would have removed the download option for the beta.
[Galaxy Note 4 Android Development (Snapdragon)] jonnie77:
Is going to have an update that awesome kernel?thanks in advance!!!i am waiting for kali nethunter support!!!
[Galaxy Note 4 Android Development (Snapdragon)] YG007:
I see.. I would like to see the original interactive governor from 3.1 as well. When I was using the stock ROM from Rogers and just rooted and Xposed installed for the first few days that I owned the device, I liked how the interactive governor worked. I undervolted my CPU and it actually lasted noticeably longer than it does with the v4 kernel. If you're going to take out the hard coded 2 cores always on, and go back to the original interactive governor, then I don't care about getting 3.1 to work and look forward to the final V4!! :D

I'm using the N910W8 model for Canada, I'm on Rogers, which kinda sucks cause I did the VoLTE hack and after all my efforts, I found out that Rogers has a whitelist of IMEIs for VoLTE access, so if the device was originally intended to have VoLTE, it would work. Since the note 4 doesn't natively support VoLTE from Rogers when they released it, I'm SOL.

FYI: I'm using the v4 kernel with Apocalypse ROM and further debloated/modded it so it runs more lean on my N910W8. /system, /data., and /cache are all F2FS. Baseband is: N910W8VLS1DPK1. Also did a couple mods to further disable Knox from that rom, since the state it was in caused 30-60% (sometimes 80%) constant CPU usage with this kernel. (Now I get 8-25%, with very rare spikes)
[Galaxy Note 4 Android Development (Snapdragon)] hightech316:
Do I need to be on the DQI6 baseband ?

I'm using sm-n910t on EPG2 baseband .

Thanks for sharing !

Edit

Version 4 had flashed and running great . Awesome battery and running more cooler than before .

What have you guys been setting thermal to within kernel auditor ? I have left it at 70 degrees
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
H-Vitamin

Last month [MENTION=1816176]Halcyon[/MENTION] brought up the idea of updating Hani K.'s H-Vitamin kernel and I heard back from him a couple days with permission to do just that. Right now I'm just going to post it in this thread and if need be I'll create a new thread for it.

Change log between this version and the original:

Built with DQL2 source from the SM-N910F

Updated Linux version to 3.10.108

Added F2FS support

Added a commit to allow WiFi to work on (hopefully) all variants

Patched Ramdisk so it will work on port roms

No root method or busybox added to the zip

You'll need to flash Magisk or SuperSu in order to have root

after

you flash the kernel zip. You'll also want to flash Busybox as well.

For those unfamiliar with H-Vitamin kernel you can find the original thread here.

Other features of note are:

Permissive

Extended Battery Patch

Original H-Vitamin Source Code

Source Code for this H-Vitamin kernel

H-Vitamin Download- It should work on ports and stock based roms. I tested both and all seems to be working well.

Credits to [MENTION=6518928]Hani K.[/MENTION] for the original H-Vitamin kernel and for being gracious enough to allow me to continue his work.
[Galaxy Note 4 Android Development (Snapdragon)] mbr007:
Boot loop on 910T.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
Which rom are you using?

Edit- if using an AOSP rom then you have to use a kernel that is compatible with AOSP.
[Galaxy Note 4 Android Development (Snapdragon)] YG007:
With this kernel, all 4 cores stay on at all times. Also, no way to change CPU voltages, no screen colour adjustment, and LED control. Since 4 cores stay on all the time, my battery drains so fast that I went back to Flashpoint v4 beta.
[Galaxy Note 4 Android Development (Snapdragon)] megaequs:
Flashpoint v4-beta seems to be the coolest kernel for me. Even on full loads the temperature is around 60 degree (didn't try 3D-Gaming). By doing (nearly) nothing around I get around 35-40 degree. And I get nearly 3h of SOT with 50 percentage of battery left.
[Galaxy Note 4 Android Development (Snapdragon)] MEMOREX2:
No problem here:good: all' core active respect v4beta
[Galaxy Note 4 Android Development (Snapdragon)] nopnopnop:
On some roms (notably ManuProN5), there's a misconfiguration in how entropy-gathering is set up. Symptom: one CPU sits at 20% while idle.

If you are using flashpoint kernel v4 beta, try using Kernel Adiutor to set Entropy:Write to 256.

When this happens, at any setting above 448, one CPU will spin forever at idle priority.

That setting's the same as:

echo '256' > /proc/sys/kernel/random/write_wakeup_threshold
[Galaxy Note 4 Android Development (Snapdragon)] Halcyon:
Dear [MENTION=5285430]kevintm78[/MENTION]

Thank you so much for this cool surprise,

I've installed it and it works excellent, I had some problems with hot plug now it works good.

Aweasome work, confirm works on G variant perfectly.
[Galaxy Note 4 Android Development (Snapdragon)] JOSHSKORN:
[MENTION=5285430]kevintm78[/MENTION]

I'm sorry to say, but for now, I've moved on from your MoDestROM to LineageOS 15.1, and well, I think I've seen you in that thread so you're probably vaguely aware of it.

The ONE thing I do wholeheartedly miss about your ROM, is THIS kernel, considering I have an extended battery, and I'm not getting the vibe that my battery percentage is correct on LineageOS 15.1. Other than that, I'm hooked on LineageOS 15.1, which I've had better luck than Lineage 14.1, actually. Some stability issues still exist, but I can handle them.

To your knowledge, are we able to somehow edit the kernel on LineageOS 15.1 to suit extended batteries, better?

I haven't run my phone battery totally down since upgrading to LineageOS 15.1, but I can tell it has been draining faster since the switch, therefore I'll more than likely have the 1% problem for several hours.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
Awesome, I'm glad it's working out for you. I think there's still an adjustment or 2 that I need to make (battery seems to top out at 95%) but it's been working well on my 910V too.

There's a bit of a bug with how mpdecision and Kernel Adiutor react together that prevents cores from off lining. It's affected every kernel that I've ever run and the only way I know to fix it is to either delete the app data of KA or uninstall it altogether and reboot. It only seems to be a problem if mpdecision is turned off and then turned back on. I wanted to try to keep H-Vitamin original but for other Flashpoint builds I'm going to remove that hotplug altogether unless I can finally figure that cause of that issue.

Hey buddy. I saw that you moved on :crying:. Lol, I don't blame you that rom is pretty great and there's no competing with the battery life compared to stock roms. I was running it for awhile too, but I always tend to come back to stock for one reason or another. Actually, at the moment I'm running star53's norma rom v26 which you might like if you if you decide to move on from LineageOS.

I'm not sure there's anything thing that can be done about the extended battery without hard coding that change into the kernel source. Maybe someone else can correct me if I'm wrong. I have seen others in the Lineage thread say that will eventually correct itself after a few battery cycles but that may be a placebo effect. I could try to make a lineage compatible kernel but the source code seems to be scattered about so I'm not real sure where to begin. I'll try to pm whoever maintains that kernel and see if I can get some help on it when I get some time to work on it. I think it's _mone that's in charge of most of it if I'm not mistaken.
[Galaxy Note 4 Android Development (Snapdragon)] JOSHSKORN:
Yea sorry man. Lol. But the deciding factor was that ModestRom was running very slow and freezing my phone after awhile. I'm thinking like all ROMS, they start out great but eventually get sluggish. I actually tried a clean wipe and reinstall but I couldn't activate it for some reason. I'll give the other ROM a looksie when I get home.
[Galaxy Note 4 Android Development (Snapdragon)] Halcyon:
Dear [MENTION=5285430]kevintm78[/MENTION]

For the charging stuff, you sure it's only charges to 95%? Because once I've checked the phone and it was 100%, maybe it's an effect of battery patch you've done?

For hot plug, I just unistalled the Kernel Auditor and checked with another app, Lspeed from Play Store, Hot plug now working randomly when I use Lspeed's Qualcomm MP decision button.

To my experience I've got more SOT than the H-Vitamin itself, my phones stability is improved noticeably, so I'm thankful for all of it, if you could just fix the battery % problem (if persists, I didn't face yet) and most importantly the hot plug issue I believe it's the best kernel I've tried to the moment on my N910G.

Please improve this kernel too! I love how pure/simple and efficient it is, performance and SOT are my main goals by installing this kernel

:highfive:
[Galaxy Note 4 Android Development (Snapdragon)] Halcyon:
[MENTION=5285430]kevintm78[/MENTION]

Hello there!

I confirm the kernel doesn't allow to charge battery more than 95% sometimes 94%

Can you buid the kernel without extended battery patch?

Any solution?
[Galaxy Note 4 Android Development (Snapdragon)] JOSHSKORN:
Just installed it today and I've never seen an installer like this, before. Interesting. One thing did interest me in particular, which brings me back to you.

Upon installation, I was able to choose a kernel, Flashpoint of all kernels. I had no idea that such would be available. It looks like 3.1 and it looks like it might just be the main kernel that's available, not the one for extended batteries.

Can I flash the Unified Kernel on this ROM or not? Mind you, when I set it up, I had Magisk (I think v15.3) installed.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
I should be able to get to that tonight or tomorrow. I'll go back over the code and see what went wrong. As of now I'm not able to figure out a fix without recompiling.

Yeah, you should be able to use any of the port compatible kernels with that rom. Just remember to reflash Magisk afterwards because if I'm not mistaken that Magisk zip that's included has a older release.

Did you notice if your battery percentage was starting to even out with Lineage. Just curious if the extended batteries will eventually even out on their own.
[Galaxy Note 4 Android Development (Snapdragon)] JOSHSKORN:
Magisk - I think I saw it was v15.3. What happens with Magisk when I install a kernel? Please explain. You kinda lost me on that whole thing.

Battery - Honestly, I'm too dependent on my phone, particularly when I'm out and about all the time. That said, I didn't really notice the same amount of drainage, but at the same time, I never did run my phone down to a dead battery. My battery just seemed like it was draining faster than normal, which could either be a kernel issue, or maybe my battery is getting old, it's hard to say. I've had my current battery for a year, now. I'm thinking closer to the 2 year mark is when the battery starts dying off. I was gonna flash the Unified Kernel up until I saw you mentioning something about Magisk, so I'll wait on it for a bit, then see what happens with my battery, again.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
When you flash an unrooted kernel it essentially removes Magisk/SuperSU because the ramdisk, which is part of the boot.img, is being replaced. There can be some left over parts that will be overwritten but if you are switching from SuperSU to Magisk or vice versa I recommend running unSU.zip before flashing the new kernel. Osm0sis's unSU.zip will now uninstall Magisk as well.

This next part you don't really need to read but if you want a more detailed answer......

Whenever you flash Magisk/SuperSU it unpacks the boot.img and places patches inside of the ramdisk during the install and before Magisk was popular most kernel devs would go ahead and put the SuperSU patches in the ramdisk so there would be no need to reflash SuperSU and root would survive the kernel flash. Now if you pre-patch the kernel and someone wanted to use an alternative rooting method the install will fail.

That's why on some of the Note 4 kernel that haven't been updated in awhile Magisk can't be easily installed. You would have to unpack the boot.img and remove the existing SuperSU patches then repack and flash Magisk.

I hope my ramblings make sense. Just to clarify a little more the boot.img is comprised of many different files. It's often referred to as the kernel but it actually contains quite a bit more than that. The main parts being the ramdisk, zImage, and dtb.img. Anything that is modified in the ramdisk will be removed when flashing another boot.img.

Tl;dr Flashing an unrooted kernel will remove Magisk completely (well, most of it anyway).