yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] zeu55:
i tried forest v4 , bauners stock beta 4 and raw9 kernel on beta 4 rom. on raw r9 kernel i am getting more vibrant display colour compared to other two. may be for the refresh rate ...secondly my battery is working great with this kernel . trim is working. overall smooth experience on beta 4 .

sent from N7000 powered by bauner's CM12 beta 4
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
That's because of the s3cfb update that hasn't been merged to CyanogenMod kernels.
[Galaxy Note GT-N7000 Android Development] I_android:
[MENTION=5145944]GeeckoDev[/MENTION]

CM12 beta4 kernel has OC oled as well?

And any specific reason to overclock to 59hz and not 60hz?
[Galaxy Note GT-N7000 Android Development] User_99:
For speed up your file system - like a defragmentation. Newer kernel do this automatically so no need to do that manually. For our note only few kernel have trim feature included...
[Galaxy Note GT-N7000 Android Development] dev_freak:
And can I use it on as example forest kernel if I want to?
[Galaxy Note GT-N7000 Android Development] dev_freak:
Thanks. I think xda is the best forum for help and modding etc.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Because 60hz makes the screen flicker at boot and breaks S-Pen. On Touchwiz only the second issue appears.
[Galaxy Note GT-N7000 Android Development] KalZakath:
[MENTION=5145944]GeeckoDev[/MENTION]

are you still workin' at kernel with i9300 sorcess?

Any progress?
[Galaxy Note GT-N7000 Android Development] I_android:
thanks for explanation :)

Does CM12 beta4 kernel has OC oled as well?
[Galaxy Note GT-N7000 Android Development] I_android:
[MENTION=799465]bauner[/MENTION] [MENTION=5145944]GeeckoDev[/MENTION] [MENTION=4576973]forest1971[/MENTION] [MENTION=4141005]Lanchon[/MENTION]

Here I am attaching screenshots from AndroBench app benchmark results with bauner, GeeckoDev and forest1971 kernels.

But before that I'd summarize my findings:

1. With bauner's stock kernel the scores are good before Trimming (and after Trimming on forest1971 and GeeckoDev Trim enabled kernels), I did not notice any huge difference in the scores before and after trimming.

2. Scores seems to be poor with forest1971 and GeeckoDev kernels before and after trim.

3. Not only scores, I also noticed that on forest1971 kernel apps took long time to install as compared to bauner's stock kernel.

4. Well I know all respected devs may say that I am the one who won't gain from trimming and may be trimming is not for me. But my question is that why trim enabled kernels (forest1971 and GeeckoDev) are giving so low scores? They should at least give equally good scores as bauner's kernel.

Is there anything that forest1971 and GeeckoDev need to look into their kernels.

Could [MENTION=4576973]forest1971[/MENTION], [MENTION=5145944]GeeckoDev[/MENTION] and all the amazing people checking this thread please verify these results on your device and report to devs so that we can have enough stats to conclude.

Thanks a lot for all the amazing work done by [MENTION=799465]bauner[/MENTION] [MENTION=4576973]forest1971[/MENTION] [MENTION=5145944]GeeckoDev[/MENTION] and [MENTION=4141005]Lanchon[/MENTION].

Screenshot from [MENTION=4576973]forest1971[/MENTION] kernel after trimming on beta3:

Screenshot from [MENTION=799465]bauner[/MENTION] stock kernel after returning from forest1971 kernel on beta3 (there were almost similar results on bauner stock kernel before installing forest1971 kernel and trimming):

Screenshot from [MENTION=5145944]GeeckoDev[/MENTION] kernel after trimming on beta4:
[Galaxy Note GT-N7000 Android Development] Lanchon:
firstly, andobench results are hardly repeatable.

also, trim capable kernels are absolutely NOT in any way different than noncapable ones, except when you actually execute a trim command (ie: it works).

if you want to compare apples to apples, compare one of my trim kernels against my corresponding fpbug-only non-trim version.

some ramdisks might be mounting partitions with the DISCARD mount option. this transparently trims on a trim kernel and not on others, introducing differences. DISCARD should not be used in android 4.3+, as it decreases performance and android 4.3+ has an "offline" trim feature. my kernels do not mount with DISCARD.

but again, the highest factor is probably androbench's randomness.
[Galaxy Note GT-N7000 Android Development] I_android:
Thanks for replying.

Well I 100% agree with your view point, to different kernel's results can't be compared that way. Only thing I wanted to point out is forest1971 and GeeckoDev is doing something differently and bauner is doing differently apart from Trim support, that's why there is such a huge difference in the results.

And I would really love to try out your kernel, however unfortunately your kernel is not available for Lollipop CM12. Do you have any plans to release one for CM12?

Thanks.
[Galaxy Note GT-N7000 Android Development] Lanchon:
no. my kernel is trivially modded from CM's. there's no official CM12 kernel for exynos 4 (so i can't do mine), and fpbug fix has been merged (so there is no reason for me to do it anyway). if official cm12 releases, ill do a trim version of it.

i insist that it all *could* be an artifact of androbench. if you run the bench 3 times on each kernel and results match, only then IMHO it'd be worth it for the involved individuals to investigate.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
bauner's kernel outperforms the other two because of dynamic fsync. There's no way the eMMC could pull a real 200+mb/s for writing. It's cached.
[Galaxy Note GT-N7000 Android Development] I_android:
Well I did run test multiple times on each kernel (before trim, after trim, just after restart, after using phone for couple of hours etc), all the tests gave me nearly same results for that particular kernel. I just uploaded only one screenshot from each kernel just to show the results to all the Devs. If you want to see those multiple results I can upload all of them. But trust me they all are nearly same.

---------- Post added at 05:47 PM ---------- Previous post was at 05:41 PM ----------

Well I do agree that 200+ mb/s is very high as far as writing is concerned. But I don't know how cache be involved while writing data to disk or to DB. While reading yes cached data can be used however. That's my knowledge with development I do in Java (not Android related though)
[MENTION=799465]bauner[/MENTION]

please share your view point on the subject.
[Galaxy Note GT-N7000 Android Development] Lanchon:
lol! i never even opened the screenshots to look!

disabling fsync is extremely dangerous for your data and partitions. i wouldnt use any kernel from someone who disables fsync, i just couldnt trust their judgement at all. IMHO disabling fsync is something al-qaeda would do lol!

btw, is there any way to replace fsync's implememtation with write barriers so that writes are performed asynchronously but data consistency is preserved?

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

google write-back cache
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Here's a better explanation.

'man fsync' says:

In other words, it forces the operating system to flush buffers and write all the data to the disk. dynamic fsync just makes this function non-blocking when the screen is ON, effectively reducing lag in some applications. However, this can be dangerous because data integrity is not assured anymore.

Furthermore, it has a drastic effect on synthetic benchmarks. These applications HAVE to use fsync to ensure all data is written to the disk and calculate its speed. But if fsync returns immediately, the benchmark will think the device is much faster than it is really, hence the 200+mb/s write speed.

I agree. TIL [MENTION=799465]bauner[/MENTION] belongs to Al-Qaeda. :laugh:

Nah really, I think it would be better if NightOwl shipped with a untouched kernel, except FPBug and TRIM fixes merged. No -Ofast, dyn fsync or other aggressive optimizations.
[Galaxy Note GT-N7000 Android Development] I_android:
Thanks a lot... write-back cache, I know that...I didn't think of it when I read GeeckoDev comment.

But this is like writing data to cache and not to disk or to DB. Which is very risky.

---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------

understood it very well thanks for explanation...it was a good learning :)

---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------

[MENTION=799465]bauner[/MENTION]

We are eagerly waiting for you to comment on above discussions. Is fsync disabled in beta4 stock kernel?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Announcing Raw Kernel r5 for Touchwiz

Changes over r4/TW :

* Latest FPBug patchset merged

* TRIM-enabled

* -fno-pic build to fix recovery

* -50mV GPU downvolt for group B+

Only compatible with Touchwiz roms. r3p1 blobs + libc.so included.

Download :

* raw_kernel_r5_tw.zip

* raw_kernel_r5_tw_59hz.zip (59hz build for S-Pen users, and no screen flash when offline charging)

This is likely the last TW release because I'm switching over to Lollipop as my daily driver. It's been a great time! :)
[Galaxy Note GT-N7000 Android Development] bauner:
The kernel is build with -Os in the NightOwl Roms.

I know that disabling fsync is very dangerous for data integrity.

But for me dyn fsync was an acceptable way for speedup with an bit lower risk for data corruption.

But I agree that such potentially dangerous optimizations should not shipped in the default kernel for all day use.

In the next beta5 I will remove dyn fsync and will provide an alternate kernel for such crazy users like me.

For now if you don't want to use dyn fsync you can disable it with "echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active"
[Galaxy Note GT-N7000 Android Development] Macrint:
Just flashed r5 tw and testing it now. Thanks again!
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Great! Way to go bauner! :good:

-Os build is interesting for embedded devices that have a very small cache, but I doubt it's useful for a dual Cortex A9 chip.
[Galaxy Note GT-N7000 Android Development] ThaiDai:
I installed the latest TW version and get the same error as with v4 in Avast Firewall.

When I try to activate this firewall I get this message (original in german):

Error when applying the firewall rules (Code 1). dmesg: klogctl:

Function not implemented

With the original kernel no problem. [MENTION=5145944]GeeckoDev[/MENTION]: Is something missing in the kernel or in the firewall implementation?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
It seems Avast depends on dmesg, which is disabled because this kernel is based on c.o.h's HelloWorld sources.
[Galaxy Note GT-N7000 Android Development] ThaiDai:
Thanks. So I have to look for a different firewall. If I do not find a suitable one then I have to switch back (but I do not want to do this).
[Galaxy Note GT-N7000 Android Development] cheaterdawaq:
Hello [MENTION=5145944]GeeckoDev[/MENTION] Thanks for the new release. This will be the first time that I'm going to use TRIM, so I'll still ask, can I use your flashable zip (run_fstrim.zip) on r5 TW?
[Galaxy Note GT-N7000 Android Development] phoenX80:
I believe this zip is only initiating terminal commands - so its not a classical "flash" in its sense. So it should work an any trim kernel in my opinion.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
You can use it on any kernel, but it will do nothing if the kernel doesn't support TRIM.

Yep it doesn't flash anything, see the script:

ui_print("Mounting partitions ...");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/preload");
show_progress(0.200000, 0);
ui_print("Trimming /system ...");
run_program("/system/xbin/fstrim", "-v", "/system");
show_progress(0.400000, 0);
ui_print("Trimming /cache ...");
run_program("/system/xbin/fstrim", "-v", "/cache");
show_progress(0.600000, 0);
ui_print("Trimming /data ...");
run_program("/system/xbin/fstrim", "-v", "/data");
show_progress(0.800000, 0);
ui_print("Trimming /preload ...");
run_program("/system/xbin/fstrim", "-v", "/preload");
show_progress(1.000000, 0);
unmount("/system");
# /cache stays usually mounted in the recovery
unmount("/data");
unmount("/preload");
ui_print("Done.");
[Galaxy Note GT-N7000 Android Development] BarelyPosting:
Yes yes you can. I already did it. It works perfectly.

[MENTION=5145944]GeeckoDev[/MENTION] Thanks for the last release of TW Kernel. I think I'm going to stick with TW as my daily driver. Since it will be the last, can I have a last request too for R5/TW? Can you release a last separate version of r5/TW with all the features included but with OC GPU (just the GPU 160-267-400mhz)? It seems that no one released an overclocked GPU after updating the mali driver (blobs - 4.2) since it's not needed anymore. Though I really want to try it for gaming purposes, just for the sake of gaming. lol I also noticed that every time I try using your kernel, it seems that it is more vivid and vibrant in color compared to most kernels, or is it just my imagination? :confused: Well anyway, thank you in advance. Good luck to your kernel development for KK and LP ROMs! :D
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Thank you. 400MHz will do close to nothing in itself because of thermal throttling, you can try it with Tegrak Overclock. I never touched these settings and I'm afraid to do it. You'll have to wait at least one week for that because I'm taking a break.

As for the color difference, I can explain it for the AOSP variant, it's because a newer s3cfb driver from i9300 is merged in Omni and my kernel is based on that.
[Galaxy Note GT-N7000 Android Development] BarelyPosting:
So that's why it was vibrant. :p Sure sure, I can patiently wait for that 400 mhz release. I'll still try it. Hoho. Thanks again and have a good break. :)
[Galaxy Note GT-N7000 Android Development] zeu55:
i am preety happy with r9 beta 4 kernel. my wife has a korean note shv e160l with rom providing bivid colour on stock rom. bauner and forest kernel was not providing that ammount of vividness . now after this s3cfb driver update its fantastic.

sent from N7000 powered by bauner's CM12 beta 4
[Galaxy Note GT-N7000 Android Development] Galaxtus:
You can use it on Stunner. Use the CM10.1 r2 kernel.
[Galaxy Note GT-N7000 Android Development] yokonunz:
My phone continues to freeze. Last time happend when i was typing on WhatsApp.

I attach the last_kmesg.

View attachment error.txt

Maybe gpu voltage too low?
[Galaxy Note GT-N7000 Android Development] M3TALLICA:
Voltage Control and SetCPU do not show voltage menu.

This is super fast kernel.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Thanks for the report. Which rom are you using? And which group?

In the meantime you can stick to Raw Kernel r1 and see if it's more stable. ;)
[Galaxy Note GT-N7000 Android Development] yokonunz:
I'm with latest jelly beer as you can see in my signature.

0x2 group B

I'll try to flash v1

Inviato dal mio GT-N7000
[Galaxy Note GT-N7000 Android Development] Hank87:
Same here, i have now increased gpu voltages with tegrak oc, testing and report.

I am group b.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Ok, if you don't have instabilities, I will increase gpu voltages. It may currently be a little to aggressive as step 2 is both at higher frequency (200MHz instead of 167MHz) and at lower voltage (-50mV).

If you confirm it is more stable, I will cook for both of you a test build so you can report.
[Galaxy Note GT-N7000 Android Development] yokonunz:
Maybe +50mv can solve all issues ;)

Inviato dal mio GT-N7000
[Galaxy Note GT-N7000 Android Development] M3TALLICA:
[MENTION=5145944]GeeckoDev[/MENTION]

Would you please add support for third party voltage changing apps ?

I don't know which group my device falls into but voltage control, set CPU, CPU control etc don't show voltage options.
[Galaxy Note GT-N7000 Android Development] M3TALLICA:
Had a random reboot.

Here's the last kmsg.
[Galaxy Note GT-N7000 Android Development] yokonunz:
Using v1 no freezes.

Could be just a coincidence but for now that's the fact.

<<<<<

EDIT

HAD ALSO A FREEZE WITH V1

>>>>>>

Inviato dal mio GT-N7000
[Galaxy Note GT-N7000 Android Development] MaxiJavi:
I also had freezes and some reboots on V2 until I went to V1.

Seems OK now :)
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Ok, I will reduce the voltages then.

[MENTION=2244369]yokonunz[/MENTION] Try the stock CM kernel. It's weird that you have freezes with Raw Kernel v1, it shouldn't happen!
[Galaxy Note GT-N7000 Android Development] yokonunz:
Strange because it doesn't happen on NX. I don't know why...

Do you know where I can find an updated cm kernel?

Inviato dal mio GT-N7000
[Galaxy Note GT-N7000 Android Development] Hank87:
After increasing the voltages I have not had any other freeze, but today I have not had much time to use my phone.

However, until now seems stable. I've increased all the voltages of the GPU to +100 mv, although probably not necessary. I will continue to test tomorrow. :)

Inviato dal mio GT-N7000 con tapatalk
[Galaxy Note GT-N7000 Android Development] yokonunz:
What app have you used?

Inviato dal mio GT-N7000
[Galaxy Note GT-N7000 Android Development] Hank87:
Tegrak overclock

Inviato dal mio GT-N7000 con tapatalk
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
+100mV is higher than the stock voltage :D
[Galaxy Note GT-N7000 Android Development] XxPixX:
Didn't the CyanogenMod team try to do this but couldn't due to huge memory leaks? This was some time ago though, before the drop from insignal I believe...
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Nope, huge memory leaks were caused by the r2p4 driver which was designed for ICS.

I'm currently working on it. There are a lot of barriers here, but I got Hardkernel and Insignal kernel sources which are already using r3p2, and am integrating these drivers into the CyanogenMod kernel. Got them compiling, that's a good start. I also got the Insignal blobs, but libUMP.so is missing. It should be compilable from source though.

There are a lot of great guys there, particulary Turl, hno, ssvc and rz2k from #linux-sunxi who have already dealed with Mali drivers. Also I get some useful answers from [MENTION=3208754]codeworkx[/MENTION] even though he doesn't care anymore. :D
[Galaxy Note GT-N7000 Android Development] gioyx97:
1 question:

The raw kernel r5 have TWRP?
[Galaxy Note GT-N7000 Android Development] dclou:
dear GeekoDev:

I use the cm11 ver. with Carbonrom 4.4.4

It works perfectly, thank you very much for your hard working

Btw, would you please considering about adding the swapfile function into it for the next release if you will^^

That shall be more helpful to users:D
[Galaxy Note GT-N7000 Android Development] Lanchon:
[MENTION=5145944]GeeckoDev[/MENTION]

do you plan to ever release raw for the i9100?
[Galaxy Note GT-N7000 Android Development] Antwone78:
Just to share my feeling on this kernel r9 with CM11. The best one for me !! About battery usage, very good results : went from 100% to 9% more than a day as a normal daily usage ! My battery is 15 months old. Wi-Fi turned on or data for surfin' internet about 3 hours, many calls but no games.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
No, I don't want to release something I can't test.
[Galaxy Note GT-N7000 Android Development] I_android:
[MENTION=5145944]GeeckoDev[/MENTION]

beta5 + r9 is working perfect (smooth and stable). Only very minor thing I have noticed is on beta4 & beta5 there is an option to disable button's back light which works flawlessly on stock kernel, however with your kernel this feature does not work as expected. Could you please fix this in your next release?

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] anona:
I cannot access the internal SD card since I install the B5.

So I go back with B4 , and the internal SD is fine.
[Galaxy Note GT-N7000 Android Development] rajk53:
So the backlight will stay ON if the screen is ON ?

is it faster ? what else...
[Galaxy Note GT-N7000 Android Development] Lanchon:
hi, just a quick note:

the brickbug patch is not enough for safety: the trim bug patch is also required. please see details here:

http://xdaforums.com/android/softwa...ug-aftermath-recovering-t2823051/post54295208

more info: http://xdaforums.com/android/softwa...ug-aftermath-recovering-t2823051/post54295205

(i didn't check your kernel for trim bug patch.)
[Galaxy Note GT-N7000 Android Development] I_android:
No, it will turn back-light on only when you touch the buttons. If you touch screen it will not turn button's back-light on.
[Galaxy Note GT-N7000 Android Development] vanpopel:
So... is Raw kernel r9 safe for our Notes on CM12 Lollipop beta 5?? Or is not enough safety on r5 for touchwiz only??
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
It seems the fix is included in Raw Kernel TW but not in Raw Kernel. Got around 1500 downloads and zero complaints. Also your post says that it only affects Nexus 7 and Nook devices. What should I do? :confused:
[Galaxy Note GT-N7000 Android Development] Lanchon:
you should merge that commit. then when u put out the next kernel iteration, remove the affected ones from the downloads IMHO. not all the info i got from old sources is correct. exynos 4210 devices with trim bug DO EXIST and will brick with your kernel. fortunately, to the best of my knowledge, no notes are affected. i have only observed d710 devices with that bug, and so have other people years back.

i ask that everybody merging TRIM does the full fix. sometime later someone could fork your future super successful superstar kernel to the d710 and the massacre will begin.

there is no rush or immediate risk for your note users. but leaving your tree half fixed plants a mine for someone to trip on later.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Okay, I'll do that ASAP. Helpful as always! :)
[Galaxy Note GT-N7000 Android Development] phoenX80:
Had that issue with b3. Simple reboot fixed it for me.
[Galaxy Note GT-N7000 Android Development] forest1971:
I checked CM11 kernel source and found that 4 out of 6 patches have been applied. I guess that is sufficient. I still applied the other two which maybe redundant!
[Galaxy Note GT-N7000 Android Development] Lanchon:
what 6 patches?

there are only these 2!
[Galaxy Note GT-N7000 Android Development] forest1971:
I mean trimbug there are 6 files that needs to be patched. CM11 has 4 done.
[Galaxy Note GT-N7000 Android Development] Lanchon:
i dont know what you mean. i didn't count the files affected by each fix/commit either. please point to the patches you think need to be applied in CM11's exynos 4210/4412 kernel that aren't. IMHO this kernel already has all fixes needed to safely trim as detailed here:

http://xdaforums.com/android/softwa...ug-aftermath-recovering-t2823051/post54295205
[Galaxy Note GT-N7000 Android Development] forest1971:
I guess so too. Still in "drivers/mmc/core/core.c 100644 → 100755" the changes were only partially made. I guess the redundant part is skipped. maybe u can check and confirm that. tks.
[Galaxy Note GT-N7000 Android Development] Lanchon:
please point to the commits in github
[Galaxy Note GT-N7000 Android Development] forest1971:
https://github.com/CyanogenMod/andr...mmit/3de09ec8e73b7352c37f50a40d696f20be454b8b

https://github.com/omnirom/android_kernel_samsung_smdk4412/blob/android-4.4/drivers/mmc/core/core.c
[Galaxy Note GT-N7000 Android Development] Lanchon:
the commit you are linking in the first link is TRIM bug patch. as you can see, it's committed to CM11:

https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/search?q=mmc_can_discard

you were talking about CM11, and so was i. the second link points to omni. i don't know the state of omni's kernel.

i insist that CM11 has all the required fixes. if you think it's missing commits, please point to them.
[Galaxy Note GT-N7000 Android Development] decat:
Download link doesn't seem to be working here.

Anyone else having this problem too?