yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] bauner:
It seems to be an encoder problem, but I don't have looked deeper in it
[Galaxy Note GT-N7000 Android Development] forest1971:
Just updated my lp kernel for beta 4. Seemed to worked well and no prob with gaming so far. Run subway surfer and let's golf 3 for half an hour each and all went smoothly. Then try epic citadel: for the first time it can complete the benchmark which never did in previous betas.Result vary from one time to another and not so high. At least it can complete the test!
[Galaxy Note GT-N7000 Android Development] dev_freak:
I can't find the download link in the OP.
[Galaxy Note GT-N7000 Android Development] forest1971:
Uploading!:laugh:
[Galaxy Note GT-N7000 Android Development] dev_freak:
[MENTION=4576973]forest1971[/MENTION] I love the recovery you use the most of all custom recoveries. I think it is awful that the development of philz recovery touch is stopped.

I found out, while installing philz, that it doesn't work with beta 4, cm12 is unbootable, after installing default kernel it does work. Hope the philz with this kernel works while flashing.
[Galaxy Note GT-N7000 Android Development] forest1971:
Here is the Kernel_V4, for Beta4: https://www.dropbox.com/s/vt9fcknuil3fra0/Forest-LP-Kernel_V4(for-Beta4).zip?dl=0

Same as V3_TS, except the update init to work with Beta4.

oc oled needs more testing.

Enjoy!:victory:
[Galaxy Note GT-N7000 Android Development] dev_freak:
[MENTION=4576973]forest1971[/MENTION] is the oc oled the screen? Or is it something different?
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Yep, you're right.

The OC ups the screen refresh frequency.
[Galaxy Note GT-N7000 Android Development] mjrifath:
Is any chance fo no oc. Same as stock. Sorry if I ask wrong thing.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] forest1971:
Yes u do. Reversed to stock CPU from V3TS.
[Galaxy Note GT-N7000 Android Development] mjrifath:
Thanks Gotcha :D
[Galaxy Note GT-N7000 Android Development] akkintosh:
how to update init ......?plz if u can halp me out
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Flash Kernel_V4
[Galaxy Note GT-N7000 Android Development] akkintosh:
can u plz provide me a link towards it......

and also tell me plz

how cn i stop those cell broadcast alertss frustrated.....of them
[Galaxy Note GT-N7000 Android Development] I_android:
Go to Settings>More>Emergency broadcasts> and disable everything.....then you might need to reboot as well.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
The link was in Forest's original post:

Kernel_V4, for Beta4: https://www.dropbox.com/s/vt9fcknuil...a4%29.zip?dl=0
[Galaxy Note GT-N7000 Android Development] akkintosh:
what if i uninstall cellbroadcast apk
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Will work the same.
[Galaxy Note GT-N7000 Android Development] Lanchon:
disable it so that it stays disabled after updates
[Galaxy Note GT-N7000 Android Development] akkintosh:
k i will do it thanks
[Galaxy Note GT-N7000 Android Development] FabreFaction:
TRIM worked on my KK N7000 with the INSANE chip

I have been running KK V7_T on Dirty Unicorns V8.2 (Omni based ROM) for about a week now without any problems.

No FCs, reboots, screen locks, etc. which is great as with the default kernel in this ROM I got quite a few.

So I decided to look into TRIM, having read the following in the changelog:

1. Added trim support: to ensure smooth running and fast backup-restore. (credits to [MENTION=4141005]Lanchon[/MENTION])

2. Merged FPBug fix: to fix the music stop bug by [MENTION=4141005]Lanchon[/MENTION] and [MENTION=5948587]zeitferne[/MENTION]. For details look at this thread

As [MENTION=4576973]forest1971[/MENTION] suggested, I ran an eMMC check using this app from Google Play and I have an INSANE chip.

So I ran the CHECK MEMORY (tapped the Check Memory words on the apps front screen) and it came back saying all is good.

It took around 400 seconds and came back with "Congratulations. Test Passed."

So does this mean I have an INSANE chip but the V7_T kernel makes it safe because it has the FPBug fixes??

Not sure, but what the hell, I decided to give TRIMming a go.

So I downloaded the app Forest1971 gave as an option to run a trim job.

On launching the app I went to the LAGFIX screen.

I ticked all the partitions to be TRIMmed.

NOTE: there is no /preload partition to select, so you can't completely replicate the ADB method using this app, but as /preload isn't used in the ROM I am using I am guessing this isn't a problem.

Hit the Run! button.

It took a couple of minutes to complete the TRIM, but no freezes so all looked good.

Decided to reboot just to make sure nothing nasty had happened.

All okay.

Not sure if I am lucky I didn't brick my phone, or if the FPBug fixes have sorted the problem with INSANE chips, but at the moment I don't mind as it looks like all is well.

I haven't really noticed any speed up, but then after a week of use I'm not sure I would.

The GUI seems snappy, transitions and scrolling are smooth, but they were with V7_T from the outset.

Anyway, nice work, I can now TRIM and all seems good.

Can I recommend this to you?

I think you're fairly safe if the results of the CHECK MEMORY function in "eMMC BrickBug Check" are positive, but as always, there is a risk whenever you tinker with your device, so on your head be it.
[Galaxy Note GT-N7000 Android Development] zeitferne:
The FPBug and the eMMC brickbug are not technically related, it just so happens that [MENTION=4141005]Lanchon[/MENTION] is involved in the fixing of both. The brickbug was already fixed by Samung, but because they previously denied that it even was there, custom ROM developers did not trust them and disabled TRIM completely. Since Lanchon's kernel now runs fine everywhere despite having TRIM enabled, it seems clear now that the distrust was unjustified in this case. Read this thread by Lanchon for more details.
[Galaxy Note GT-N7000 Android Development] Lanchon:
several bugs are loosely referenced as brickbug and can brick an emmc beyond repair. the right combo of fixes in the kernel and a format workaround makes trim safe again. this was contrary to the established belief in the developer community, including those that fixed brickbug the first time around. many different emmc models and firmware revisions for those had to be tested before it could be considered safe. including initial research, the process lasted roughly 6 months. i was able to pull this off because thankfully the original maintainers of CM (now Omni) documented a lot of info years ago, and because many people here were willing to test.

regarding "I haven't really noticed any speed up, but then after a week of use I'm not sure I would": by installing a trim kernel, the device trims automatically every night (R/W partitions). so when you manually trimmed, the speed up was already there. now you can only subjectively compare the performance against your recollection of your last non-trim kernel.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Thanks for that, very useful.

I read the thread by [MENTION=4141005]Lanchon[/MENTION]

And I read the EMMC Bugs post on the CyanogenMod Wiki, and looked up my chip on the same page:

EMMC Model: VYL00M

Impact: data corruption

Details: Samsung eMMC wear leveling data corruption bug

Samsung eMMC wear leveling data corruption bug

Status: fix available since March 2012

Fix type: eMMC firmware patch applied by kernel on chip power-on

Patch: https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8^!/

This bug affects Samsung eMMC parts VYL00M, KYL00M and MAG4FA with firmware revision 0x25 (the firmware revision which fixes the secure erase bug); devices with these parts include the Galaxy Nexus and the AT&T Galaxy Note (SGH-I717) (note that the International Note (GT-N7000) contains an earlier fwrev vulnerable to "Superbrick").

In some cases, the wear leveling code on these parts will randomly insert 32 KB (one flash page?) of zeros into the storage, causing data corruption. Samsung has provided a kernel patch to Google which applies a firmware hotfix every time the chip is booted, fixing the problem.

This problem also occurs in fwrev 0x19, but has not been observed there, and is in any event far less severe than the infamous "Superbrick" secure erase bug, as the user only needs to perform a wipe data/factory reset operation to recover.

So it looks like my chip is not a Device Brick (INSANE) chip after all.
[Galaxy Note GT-N7000 Android Development] Lanchon:
i really doubt your conclusion. have you checked your fwrev? if u r sure of what you say, please post a screenshot of emmc brickbug check.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Here's a screenshot.

First time I've posted a picture directly from my device so not sure how it will turn out.
[Galaxy Note GT-N7000 Android Development] Lanchon:
told u. check the table again.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Welcome back Brick Bug, all is forgiven!!!!

Ahhhh.............

Thanks for pointing that out.

For anyone following this, there are two entries in the table for EMMC Model VYL00M.

Those with fwrev < 0x25 have the device brick bug, otherwise known as the eMMC secure erase bug

My fwrev is 0x19

Welcome back Brick Bug, all is forgiven!!!!

So I have the Brick Bug, but don't need to worry as this kernel is appropriately patched....... right???
[Galaxy Note GT-N7000 Android Development] urviagarwal:
I have been using CM11.0111 since two days along with forest V 7_T kernel. Previously I was on 1031 version.

I would say I am very happy with the current setup. The ROM Kernel combination gives great battery time. My battery life has increased by a factor of 1.5. The ROM is fast and snappy with lot fewer FCs and soft reboot.

I had flashed over the previous version without data/cache wipe.

I would easily recommend to anyone who wants to try the combo..

Thanks to Forest for his efforts..
[Galaxy Note GT-N7000 Android Development] stephendt0:
Testing this Kernel now, so far so good. I wonder why this kernel doesn't show up in the list of kernels in the Dev-DB? Would be a good idea to add it to the Dev-DB, makes this thread easier to find.
[Galaxy Note GT-N7000 Android Development] abufrejoval:
Works just fine with Bauner's Beta 5

Running it with Beta 5 for a couple of days now: Some oddities and some benchmark failures, but they aren't kernel specific (no better with GeekoDev's or bauner's kernels).

Very smooth, stable and as fast as the hardware permits otherwise.
[Galaxy Note GT-N7000 Android Development] forest1971:
Forest-KK-Kernel_V8_T

The PegasusQ governor in Forest-KK-Kernel_V7T seems to be too aggressive and some freezes were reported from cm11 users. New version _V8T should now fix it.

Release one version first for CM11. Other versions needs more testing.

- Forest-KK-Kernel_V8T for CM11: (Download move to post 702)

The kernel is butter smooth, running cool in daily use and ready to handle heavy games!

Trim should be used one time after installing rom: download lagfix app from here: http://xdaforums.com/showthread.php?t=2104326

Enjoy!:victory:
[Galaxy Note GT-N7000 Android Development] urviagarwal:
Thanks, I have flashed the Kernel... Working great..
[Galaxy Note GT-N7000 Android Development] forest1971:
Testing feedback is all good. So here are three kernels putting together in one place:

1. Forest-KK-Kernel_V8T_CM: https://mega.co.nz/#!BNBlib6Z!1OBnN-lOrZ486VydOltOh2xO4KYyLs7rGdK4o7H2O4g

2. Forest-KK-Kernel_V8T_Omni: https://mega.co.nz/#!AZZwXDqQ!LdvU6p4Y3qRwg5P2vfcLv7nU0p8hg5kpKcSsaXKLUu4

3. Forest-KK-Kernel_V8T_Slim: https://mega.co.nz/#!AIhByR4a!LoavwbC_7x0WXPNDfAiUEnTIwMzwE_NgVSf-LTgv6us

Enjoy it! :victory:
[Galaxy Note GT-N7000 Android Development] I_android:
Are you planning to update LP kernel as well?
[Galaxy Note GT-N7000 Android Development] Copkiller2010:
Does beta4 kernel works with beta6?
[Galaxy Note GT-N7000 Android Development] :
I don't understand what this statement is asking.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Glory Glory N7000

I've been running this kernel on Dirty Unicorns 8.2 for a several hours now without any problems.

Silky smooth and buttery.

Transitions and scrolling are great.

3D gaming performance is great.

Not too much heat and battery drain is definitely no worse than previous iterations of this kernel.

Thanks for keeping our device singing [MENTION=4576973]forest1971[/MENTION]

I did not expect the N7000 to have such an awesome lifespan.

My config is below, and in my signature, just in case you're wondering.....................

ROM: KitKat 4.4.4 Team D.I.R.T Dirty Unicorns V8.2 20141104-1817 UNOFFICIAL TEST BUILD

KERNEL: Forest KK V8 T(Omni)

GAPPS OFFICIAL Up-to-Date PA-GOOGLE APPS + gapps-config.txt

Radio: N7000XXLT3

Partitioning: 8Gb DATA Application Partition with PreLoad

---------- Post added at 10:53 PM ---------- Previous post was at 10:17 PM ----------

It's a question not a statement :)

Apologies, I used to be an English teacher.......................

Good to see you're still active in the N7000 community [MENTION=4703968]AndroidSlave[/MENTION] :good:

---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------

From the NightOwl Beta thread:

If you want to use another kernel make sure that it's ready for Beta4 (Kernel for Beta4 will work in Beta5/Beta6 too)

So the short answer is YES, it should work without any problems according to [MENTION=799465]bauner[/MENTION], Check the OP

Enjoy [MENTION=240047]copkiller[/MENTION]

---------- Post added at 11:09 PM ---------- Previous post was at 10:59 PM ----------

No explicit need to update the LP kernel because..................

From the NightOwl Beta thread

If you want to use another kernel make sure that it's ready for Beta4 (Kernel for Beta4 will work in Beta5/Beta6 too)

So the current [MENTION=4576973]forest1971[/MENTION] LP Kernel should work without any problems according to [MENTION=799465]bauner[/MENTION], Check the OP
[Galaxy Note GT-N7000 Android Development] :
Thank you for the important correction. I will take my doctorate and wipe my behind with it. Cheers.
[Galaxy Note GT-N7000 Android Development] I_android:
I mean to say one with OC oled for LP.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
Apologies for the slow reply, I've been off the grid in parts foreign for while.

I seem to remember there being problems with OC OLED for L, you'll have to check out the history of this thread and the RAW Kernel thread for details I think.

Sorry, don't know any more than that as I haven't really paid attention to the L stuff as I am happy with KK at the moment.
[Galaxy Note GT-N7000 Android Development] forest1971:
Tested few different things during weekend to improve for LP kernel:

- compile with Linaro toochain 4.7, 4.8 and 4.9

- compile with oracle java 6 and 7

Found that java 6 and toolchain 4.8 is the best for me.

So here is Forest-LP-Kernel V5

Note: I changed the download link back to Mediafire (now it is working again) since devhost does not work with mobile download.

Change log:

- Fine-tune PegasusQ governor for stability.

- Applied s3cfb patch by [MENTION=5145944]GeeckoDev[/MENTION], making the colour more vibrant & exciting.

- Update Philz recovery to the latest version 6.0.59. Now the recovery also has LP flavour with material-style navigation button.

- Compile with Linaro toolchain 4.8.

- OC oled to 59Hz

Compatible with CM12-Beta4-7 roms

Credits to [MENTION=5145944]GeeckoDev[/MENTION] [MENTION=4666971]Phil3759[/MENTION] and others!
[Galaxy Note GT-N7000 Android Development] KalZakath:
Your kernel is amazing, rock stable, fast and has cool Vivid colors. Big up for you work.
[Galaxy Note GT-N7000 Android Development] kazuna69:
verified and tested ! :silly:

thanks [MENTION=4576973]forest1971[/MENTION] :highfive: :victory:
[Galaxy Note GT-N7000 Android Development] urviagarwal:
Flashed over Bauner's CM12 yesterday..

I think Battery management is better than stock.. Also ROM is more smoother and less laggy comparatively..
[Galaxy Note GT-N7000 Android Development] Camalio:
Sorry to ask, but we have to flash it after complete flash of CM12, am I right ?! I'm planning to go lollipop but 'm worried about the uselessness of dear SPen.
[Galaxy Note GT-N7000 Android Development] urviagarwal:
Yes.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Hello [MENTION=4576973]forest1971[/MENTION]. Great work on LP kernel

I am currently using the KK_V8, phone works great.. but when the phone is put for reboot into recovery, it get stuck there and after about a minute it powers off. I thought it was the rom, so did clean install. Tried with default CM11 kernel and its fine. Tried with V7, its fine.. But v8 installed and the same issue. It it really a kernel issue?
[Galaxy Note GT-N7000 Android Development] forest1971:
Hi buddy, good to know u like the kernel. Will double check and let u know. For being sure could u upload the zip and send to my inbox? Recently there is a prob with mediafire so i have to use different site for sharing file and may have uploaded a wrong version. Cheers.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Sent link as PM
[Galaxy Note GT-N7000 Android Development] forest1971:
Strangely,

I tested again the one u sent and the one uploaded. For both cases recovery works for me.

I suspect there are two possibilities:

1. I am on CM11 Jan19, maybe a newer cm rom does not like the recovery?

2. u had a bad flash somehow.

Could u download again from the link on mega and let me know how it goes?

tks
[Galaxy Note GT-N7000 Android Development] urviagarwal:
I had the same problem when I was using CM11 Jan 26. I reverted back to CM11 Jan 11 version and working fine. For me Jan 11 was most stable with least FCs and soft reboot.

I have reverted back to CM11.0111 from CM12 as I could not handle the lag and slow response. ?
[Galaxy Note GT-N7000 Android Development] forest1971:
Hm, if so I will investigate and fix the recovery prob when I can.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
I can confirm that the stock kernel of 1st Feb works fine. V7 and v8 behave the same with reboot recovery. Earlier I thought it was just v8.
[Galaxy Note GT-N7000 Android Development] droidbond:
It might sound a lil noobish to ask but does this version supports trim? Sorry if its a very obvious question but i am not able to understand whether it is or not..
[Galaxy Note GT-N7000 Android Development] forest1971:
Yep.
[Galaxy Note GT-N7000 Android Development] Sheikh Isa:
Hii [MENTION=4576973]forest1971[/MENTION] thnx for the awesome kernel i love your work very much using it on bauner beta7 and thnx for the philz recover update to latest version 6.59 but u have written that's it's. 6.0.50? :confused:
[Galaxy Note GT-N7000 Android Development] Sheikh Isa:
separate philz recover

[MENTION=4576973]forest1971[/MENTION] can u provide us the separate Philz recover. 6.59 the updated one.. As Flashable zip plz i will be thankful to you.. Thanks.

:)
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
That's not how it works.
[Galaxy Note GT-N7000 Android Development] Sheikh Isa:
I didn't get you sir..? :confused:
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Recovery on N7000 is integrated to the kernel. So if you need the updated recovery then Forest will need to rebuild a kernel with the updated files.
[Galaxy Note GT-N7000 Android Development] Sheikh Isa:
Thanks for the replay and info.. So i cannot get the separate Philz recover updated version bcz on philz official it's only 6.48.4 so in the v5 kernel it's up to date v6.59 any way thanks..
[Galaxy Note GT-N7000 Android Development] urviagarwal:
My battery stats for CM11.0111 with Forest V8_T. Not bad I guess.

It is 6 times more than what I was getting with CM12 Beta7.
[Galaxy Note GT-N7000 Android Development] abufrejoval:
I like this kernel best!

For each of bauner's releases I try the included kernel fist, then GeekoDev'd and then yours: It typically wins out with the least amount of stuttering and best benchmark results, while all of them are stable and working.
[Galaxy Note GT-N7000 Android Development] forest1971:
[MENTION=4677768]nokiamodeln91[/MENTION]:

Problem found.:victory: It is not of the recovery but because of the reboot command under the advanced reboot menu of the cm11 Nightly Feb01. Instead of reboot recovery it actually tell the phone to shutdown.

The workaround is to use an app from Gplay: either HC Ktool or Quickboot reboot should work.

Cheers
[Galaxy Note GT-N7000 Android Development] forest1971:
Good to know u like the kernel.

Btw, there is no win or loose buddy. We are just enjoy making some kernels for fun :laugh:! So it is not a good things to make comparison. Instead you can enjoy and thank all of us. GeeckoDev and Bauner are advanced developers and they can do amazing things! :good::good: I am only following their footsteps.
[Galaxy Note GT-N7000 Android Development] ishanbhatnagr96:
How much sot are you getting?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Hey.. Thanks for looking into it.. Is there any particular reason why the stock kernel does the reboot recovery alright? If it's the code?
[Galaxy Note GT-N7000 Android Development] forest1971:
Um dunno. Will try to check.
[Galaxy Note GT-N7000 Android Development] m_rajaganesh:
Shall I use this v5 kernel on recurss ROM 5.3.1 version. If not please advice the kernel for rr ROM 5.3.1 + version. Thankyou in advance.
[Galaxy Note GT-N7000 Android Development] forest1971:
Yep
[Galaxy Note GT-N7000 Android Development] urviagarwal:
I didn't make record... Screenshot was taken yesterday... in any case I don't think sot is displayed except in Graph form in CM11?
[Galaxy Note GT-N7000 Android Development] abufrejoval:
Couldn't agree mere that the biggest win is how you share each others stuff without hesitance and restrictions and I get all the features put together in a menu to chose from!

I'm actually surprised there remain any noticible and measurable differences at all, since you all seem to put the latest and greatest from each other into your pot and there should be little magic in heating and stirring... :)
[Galaxy Note GT-N7000 Android Development] mahmoud fayed:
I installed your kernel with NightOwl cm12 Beta7 (wiped cache and dalvik after), but the CPU frequency is always 1400Mhz for no clear reason (tried to change governor but no luck). What should I do?
[Galaxy Note GT-N7000 Android Development] xirusnet:
Strange, after installing ForestV5 kernel on Nightowl 8.0.3 no-frills is showing ondemand and row. Shouldn't this be pegasushq and cfq?
[Galaxy Note GT-N7000 Android Development] forest1971:
CPU will stay at highest for sometime after booting to cope with background app starting. It should come down after few minutes. Otherwise, there is something wrong with your phone which is not related to the kernel. Cheers.

For some reason the setting from previous kernel (I guess the stock NightOwl) will override the default value. It is easy to change back using No-frills or similar apps. I prefer pegasusq over ondemand. Cheers.
[Galaxy Note GT-N7000 Android Development] jaguar85:
I am planning to flash Nightowl ROM.....

currently I am using custom sweet rom (JB) with philz kernel.

My Q is do I need to flash nightowl kernel or not before flashing nightowl rom???

Also can i 1st flash forest kernel then factory reset, wife dalvik-cache and then install rom????

I am confused :confused:
[Galaxy Note GT-N7000 Android Development] User_99:
Read the Nightowl thread and you will find the answer!
[Galaxy Note GT-N7000 Android Development] tamaraxxx:
[MENTION=4576973]forest1971[/MENTION]: will their be new updates off the kernel witch can be expected soon? i'm using your kernel on the RR lollipop but experience soon lag the last few days.