yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Lanchon:
did u have trouble with cm-11-20141007-NIGHTLY-n7000 or just flashed oct 15 for no reason?
[Galaxy Note GT-N7000 Android Development] Lanchon:
btw, is anybody building unofficial Ms for this device?

soon there will be a new M out and ill be doing a new nightly. is there a particularly stable recent nightly?
[Galaxy Note GT-N7000 Android Development] ishanbhatnagr96:
I flashed it directly on 15th build as some other user flashed the same on 23rd build.
[Galaxy Note GT-N7000 Android Development] twerg:
Can this kernal work in Omnirom? No matter what 4.4.4 rom I use the note just feels crap, slow and with plenty of lags, have tried 2 kernal so far; the stock and R6 Raw. Have tried various tweaks in Andriod Tuner and again no joy
[Galaxy Note GT-N7000 Android Development] kohmax:
No it can't.
[Galaxy Note GT-N7000 Android Development] jogai:
Whats your FwRev?

The table says:

But in the must read post it says:

So I think it would be safe. I'm planning to do the same on my VYLOOM eMMC. (After you sir ;))
[Galaxy Note GT-N7000 Android Development] Lanchon:
its safe. the only emmc bug not yet proven safe is trim bug. it should be but we dont find any to test.
[Galaxy Note GT-N7000 Android Development] damir_nis:
quick question

does it need to be same nightly as trim kernel or i can use any trim on the latest nightly on N7000 thank you
[Galaxy Note GT-N7000 Android Development] der_Kief:
Lanchon already answered that here :D
[Galaxy Note GT-N7000 Android Development] blackomegatm:
Ok, ok, it's official, this is the first time I'm using a custom rom since my motorola milestone and CM7.

I had no reason to move to a custom rom on the note because none of then offered me a reasonable performance advantage over the stock rom. Acctually most of them were worse.

Now with trim, I expect things to change, to I'm giving it a try.

My phone is affected with the trim bug

EMMC chip

Type: VYL00M

Date: 10/2011

CID: 15010056594c30304d19a1066416aee5

FWRev 0x19

BrickBug?

Yes. Insane chip

Whatever.

I installed it anyway, and I'm gonna give it a run even if it bricks the phone. Living without is hell anyway.

I'll post benchmark results later as first I'm trying the rom out to see if anything is broken.
[Galaxy Note GT-N7000 Android Development] Lanchon:
UPDATE: this project now supports all roms and kernels!

if you are not running CyanogenMod M snapshots, please see this post.
[Galaxy Note GT-N7000 Android Development] ValouSydney:
Does it mean that I can use this kernel with AryaMod V8?

Because just after installing the rom it runs like a charm but unfortunately after a couple of days and even with Greenify, it starts to become very very slow...!
[Galaxy Note GT-N7000 Android Development] Lanchon:
no, it means you can carefully read the linked post and follow instructions.
[Galaxy Note GT-N7000 Android Development] der_Kief:
Hi Lanchon,

does that mean that we have to build the CM kernels ourselves or do you still continue to build them for the CM nightlies ? Sorry if i dont understand your post correctly :)

GT-N7000 mit/with Tapatalk
[Galaxy Note GT-N7000 Android Development] Lanchon:
no! you just follow the instructions on the linked post.

please help me by telling exactly what is unclear on that post, thanks!
[Galaxy Note GT-N7000 Android Development] blackomegatm:
2 days running CM with the trim kernel.

No problems so far.

Performance is great, doesn't even seen like the same phone as before....
[Galaxy Note GT-N7000 Android Development] Hank87:
Hi [MENTION=4141005]Lanchon[/MENTION], I have readed your post in the galaxy s2 section, I have a n7000 with stock based rom 4.1.2, for trim my phone I don't need a kernel that allow to do it? I can just download the lagfix app and trim?
[Galaxy Note GT-N7000 Android Development] daneuchar:
PARANOIDANDROID 4.6 Beta 5

Hi I am currently running on PARANOIDANDROID 4.6 Beta 5 can i use this kernel will it support my version ?
[Galaxy Note GT-N7000 Android Development] Hank87:
This is my chip:
[Galaxy Note GT-N7000 Android Development] Lanchon:
stock 4.1.2 is trim enabled. but FOLLOW MY INSTRUCTIONS!!! if you have trim bug you will KILL your device!!!
[Galaxy Note GT-N7000 Android Development] Lanchon:
read the OP and the relevant section.
[Galaxy Note GT-N7000 Android Development] ishanbhatnagr96:
Beta 5 messes the recovery. I wonder how you'll flash it..
[Galaxy Note GT-N7000 Android Development] Hank87:
Sorry, I have readed the instructions but is not very simple!

Yes I have the bug, because I have 0x19 fwrev, so I can't trim. Ok!
[Galaxy Note GT-N7000 Android Development] Lanchon:
follow my instructions!!! there are many bugs. i think you dont have trim bug. you probably have brickbug, and its ok to trim with brickbug. however, if you dont understand the posts then i recommend that you DO NOT trim.
[Galaxy Note GT-N7000 Android Development] Hank87:
Yes, the table says: Samsung eMMC secure erase bug, so I should can trim, it's correct?
[Galaxy Note GT-N7000 Android Development] Lanchon:
yes you can. but read everything first!
[Galaxy Note GT-N7000 Android Development] Hank87:
Just trimmed, tested with androbench first and after trim, there is no big difference in the values, but in normal usage now feels faster to load apps.
[Galaxy Note GT-N7000 Android Development] sulkie:
Trimmed CM11 and there were improvements. But I've tried it also on 4.1.2 just for fun, i guess, and LagFix reported that trimming is not supported. Any ideas?
[Galaxy Note GT-N7000 Android Development] Lanchon:
your kernel does not support it. you are probably not on stock kernel
[Galaxy Note GT-N7000 Android Development] sulkie:
You are right about that. I was on philz kernel, which I just read has this line in the description "Patched kernel to avoid brick bug issues on ICS 4.0.4". Im guessing that also prevents trimming.

Oh well, works well enough for CM.

BTW, Lanchon, do you think that running the latest CM nightlies with your kernel could cause some issues?
[Galaxy Note GT-N7000 Android Development] Lanchon:
crystal ball is being unclear on that one... i guess not? anyway, expect a new kernel within 24hs of CM M12 release, which should happen right about... oh, this crappy ball!!
[Galaxy Note GT-N7000 Android Development] Lanchon:
UPDATE: the n7000 didn't get CM11 M12, so i'm releasing a kernel for the latest nightly instead:

cm-11-20141111-NIGHTLY-n7000

EDIT: WARNING: bad nightly! please read next post...
[Galaxy Note GT-N7000 Android Development] der_Kief:
Problems with installing cm-11-20141111-NIGHTLY-n7000

After flashing ROM it is stuck at CM boot screen.

Problem is also discussed here

So this version of the ROM is a no go (at least for me)
[Galaxy Note GT-N7000 Android Development] Lanchon:
i see... 20141110 seems to be working. i suggest you flash that one and my 1111 kernel, it should work fine.

do you want a 20141112 kernel? just tell me which AFTER you tried it. going without trim for a day or two is not a problem.
[Galaxy Note GT-N7000 Android Development] Lanchon:
those on nightlies from November 3rd or before, would still be upgrading if switching to M12, so you may want to hold off on this latest nightly. (newer nightlies would be a downgrade.)

i might build an M12 myself, is there any interest?

since there will be no newer features on CM11, only bugfixes, it seems nightlies will be kinda stable going forward anyway.
[Galaxy Note GT-N7000 Android Development] der_Kief:
Yeah that sounds very good :good:
[Galaxy Note GT-N7000 Android Development] Lanchon:
ok, nightlies are back! and with nightlies not taking anything but bugfixes anymore, in a few days nightlies will be as stable as M snapshots, so it doesn't seem worth it for me to build an M12. given that i build blind (have no device) there would surely be some problems anyway.
[Galaxy Note GT-N7000 Android Development] Lanchon:
UPDATE: it's reported on the nightly thread that the official 2014-11-11 nightly doesn't boot (not caused by my kernel), so i'm releasing a new kernel for the latest nightly:

cm-11-20141113-NIGHTLY-n7000

(thanks [MENTION=5929147]der_Kief[/MENTION])
[Galaxy Note GT-N7000 Android Development] Lanchon:
anybody is on cm-11-20141113-NIGHTLY-n7000? is it a good nightly?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
I never had issue with any of the nightlies. I am currently on 22nd with your 13Nov kernel and its fine.
[Galaxy Note GT-N7000 Android Development] blackomegatm:
reporting back

I guess I'm using cm11 and this kernel for about 3 weeks to a Month now.

So far performance is amazing. Typing on The keyboard or doing searches are só much more responsive. Switching apps too, much faster.

Trim is here to stay!

My only complaint is a few wakelocks on cm11 that causes my phone to heat up a lot some times and eats my battery away in a matter of minutes.

I saw a new kernel for a recent nightly a few posts before, I guess it's time to update my ROM. I have absolutely no patience to learn how to compile a kernel so i'll depende on you a little longer lanchon. You have my thanks.
[Galaxy Note GT-N7000 Android Development] Lanchon:
your problem is a known problem of all exynos 4210 devices (includes S2). all kitkat kernels and roms have it.

google lanchon i9100 music bug fix. yes, its for M10. yes its for the i9100. never mind, just flash it! remember to flash it over every CM update you flash.

(btw, a newer nightly wont help)
[Galaxy Note GT-N7000 Android Development] daedric:
Lanchon, i did google it but the results were obscure. Could you please link ?

One big important question. Enabling support in the kernel for trim is not enough to make a rom trim enabled.

First, no partition is mounted with discard, so that option is excluded.

Second, one common way to check for Android trimming the partitions, acording to anandtech, is logcat -d | grep -i fstrim . We should get something like:

I/fstrim ( 169): Starting fstrim work...
I/fstrim ( 169): Invoking FITRIM ioctl on /cache
I/fstrim ( 169): Trimmed 115343360 bytes on /cache
I/fstrim ( 169): Invoking FITRIM ioctl on /data
I/fstrim ( 169): Trimmed 888254464 bytes on /data
I/fstrim ( 169): Invoking FITRIM ioctl on /persist
I/fstrim ( 169): Trimmed 0 bytes on /persist
I/fstrim ( 169): Finished fstrim work.

We got no such thing. I've manually runned trim via a app, it did indeed run with huge amounts of bytes, but it's not being executed regularly.
[Galaxy Note GT-N7000 Android Development] mjrifath:
Hi Sir,

Is there any chance of makin CM12 kernel with working recovery..

Thanks for you precious time given to Note community.

Cheers!
[Galaxy Note GT-N7000 Android Development] azlav:
i used fly-on script which always keep a log when a function supported by it being evoked, such as trimming,and if i trim using lag free, the log will show that the trim works
[Galaxy Note GT-N7000 Android Development] Lanchon:
partitions SHOULD NOT be mounted with discard. discard trims online and makes some devices slow (4210s included). i personally removed the mount option. android 4.3+ trims by itself every 24 hours (vold i think does that). people have confirmed they find the logs of that on some devices. you should find it there too after leaving the thing on charge overnight (and other requirements).
[Galaxy Note GT-N7000 Android Development] Lanchon:
re: music bug fix...

my google is as good as yours and not better!!! its a zip file you have to flash, its in one of my posts on the i9100 music bug thread. its there, find it!
[Galaxy Note GT-N7000 Android Development] moviecut:
Whouldnt it be easier, if you whould link that file in the first post here? I searched for it and could find it anywhere... Thank you.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy Note GT-N7000 Android Development] daedric:
Agree, discard is NOT the way to go. I was just stating that we're not on that path.

Regarding trim, it's probably available, but not working properly.

When we manually run fstrim on a partition, this after a boot, the amount of trimmed bytes should be near the partition free space. After this, it's the kernel task to keep track of which blocks need trimming. If we run fstrim again immediately after the first run, we should get 0 or near 0 bytes trimmed. But we get again the amount of free space on the partition. The device is not keeping track of the blocks, either by bug or on purpose (to force trim all free space every time). <-- Disregard, i'm not entirely sure about this. I'll keep this post for now, but i might be mistaken.
[Galaxy Note GT-N7000 Android Development] Lanchon:
why do you state it's not working properly? the linux kernel has been apt to trim for ages!

is your observation about fstrim is a generalization from your experience? or is it documented to work that way? if so, can you provide a pointer?

what you say simply doesn't ring true. of course it depends on file system, mount options, etc, but in the general case, if a partition is not mounted with DISCARD, it just makes no sense for the file system to track discarded blocks. it would be a complete waste of ram. the behavior you see makes intuitive sense to me, and the behavior you expect doesn't, that's why i ask for documentation.

in any case, this thread and especially the i9100 thread are full with success stories, proving you wrong by example.
[Galaxy Note GT-N7000 Android Development] Lanchon:
no! this thread is about a trimming kernel, nothing to do with fusebug

here's lanchon music bug fix
[Galaxy Note GT-N7000 Android Development] Lanchon:
ok, we crossed each other posts lol :)
[Galaxy Note GT-N7000 Android Development] daedric:
This is not proof of what i was stating: http://unix.stackexchange.com/questions/109812/fstrim-trims-more-than-half-of-partition-size-even-though-partition-mounted-with

True, it does no harm, but it's slow as hell :)

Another:

http://serverfault.com/questions/489267/trim-persistence-across-reboots

What i'm clamining might be related with the eMMC controller and not the kernel/trim itself.
[Galaxy Note GT-N7000 Android Development] Lanchon:
the second quote is as obvious as it is wrong, and not applicable anyway.

the first quote just says that "0 bytes trimmed" is no cause for concern. it doesnt say it MUST return that, or anything applicable to our discussion. when it says the kernel remembers which blocks are trimmed: which kernel? with what build configuration and modules? under what circumstances?

i see no point to this. you need to produce proof or at least some tentative evidence that not seeing "0 bytes trimmed" is a problem. there is strong indication that trim is working: device speed ups beyond any doubt.

i will not research why our kernel is not memorizing previously trimmed blocks, unless you can show that that is indicative of a problem. especially given that it would be silly and wasteful for our kernel to remember. the right thing to do is NOT to remember in our case.
[Galaxy Note GT-N7000 Android Development] daedric:
You're correct, we need to get our facts stright, or else we'll be distorcing facts to support theories instead of theories to support facts.

I now have a uptime of 6 days, logcat -d | grep -i fstrim returns nothing... i must be missing here something...

fstrim -v /data or /cache works well...
[Galaxy Note GT-N7000 Android Development] Lanchon:
sorry for the absence. in the companion i9100 trim kernel thread there are people who posted the relevant log excerpts. please make sure that you are searching for the right thing. if it's not there, it's a problem. it's not a kernel problem, but for whatever reason, your android is not triggering the maintenance. if so, could you/would you do a bit of research? i'm sure it must be a common problem.

i just searched my OPO and no results, but i rebooted today.
[Galaxy Note GT-N7000 Android Development] jogai:
/efs corrupt

my /efs partition got corrupt while running this kernel. The kernel isnt trying to trim this partition I hope?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Trim will only happen when you use the Lagfree app which only uses /system, /data and /cache.
[Galaxy Note GT-N7000 Android Development] Lanchon:
very sorry to hear that. you are the only person that reported a problem for any of the 4210 devices on trim kernel. corruption looks like an unrelated issue though.

the most important thing: do you have a bacup???

could you post your eMMC details?
[Galaxy Note GT-N7000 Android Development] jogai:
Yeah, got a backup, but I'm trying all day to restore it... I only have acces to recovery..

Details:

VYL00M 0x19
[Galaxy Note GT-N7000 Android Development] Lanchon:
thats the most common firmware and has been proved safe to trim.

im afraid if you want help you r going to need to post A LOT more detail about ur situation. what do you mean you only have access to recovery? you cant boot android? then how do you know your efs is corrupted? please describe ur complete software setup, including any hacks, repartitioning, etc., what works, what doesnt, and any observations and anything out of the ordinary. and what did you try and what were the outcomes.
[Galaxy Note GT-N7000 Android Development] jogai:
Thanks for the questions. Sorry for the late reply, I was ill. As I think its unrelated to this kernel I posted my question in a separate thread: http://xdaforums.com/galaxy-note/help/efs-partition-gone-t2971903

On top of that: No hacks, only the nightly & this kernel. No repartitioning. Recovery and Download mode works.
[Galaxy Note GT-N7000 Android Development] Lanchon:
ill answer there

TL;DR:

you seemed to have used a guide for a different phone model and you overwrote your bootloader with an unrelated partition image
[Galaxy Note GT-N7000 Android Development] jogai:
Yup, and I should've checked my fstab first, because there I could find the right device, but you know it by heart probably ;)

Flashing your custom kernel now!
[Galaxy Note GT-N7000 Android Development] daedric:
Uhhh no. From 4.3 fstrim should be executed by Android itself regularly, and it's output available on the logcat. http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices

So, if our logcat isn't showing it, it can be one of two problems:

Android is not running fstrim.

Android is either running fstrim from a place it isn't available, or calling fitrim() directly and incorrectly.
[Galaxy Note GT-N7000 Android Development] Lanchon:
i dont think CM has disabled auto trim for this family. maybe CM has a general problem in that regard in some installations. someone should google... ;l
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Yeh right but i was specifically mentioning our device builds affected by brickbug.
[Galaxy Note GT-N7000 Android Development] Lanchon:
specifically on the 4210 devices (i9100 at least) with my kernel, people posted logcats of the autotrim feature in action.
[Galaxy Note GT-N7000 Android Development] daedric:
Maybe in our (official) CM builds it's disabled to prevent fstrim erros on logcat...

BTW Lanchon, how about a 5.0 version? :D
[Galaxy Note GT-N7000 Android Development] Lanchon:
but again, people pasted trim logs for the i9100 using CM official plus my kernel. these are essentially the same device.
[Galaxy Note GT-N7000 Android Development] daedric:
Agree, but the maintainer isn't right?

This made trim show up on logcat (from the i9000)

Uhm... maybe this?
[Galaxy Note GT-N7000 Android Development] Lanchon:
i don't understand your question.

i dont have any 4210 device to test. the kernel trims for sure. if your android doesnt do a maintenance trim (other's do) you'll have to investigate; i can't do it. start by google the maintenance conditions. see in the log if maintenance is ever triggered, and if not why, and go from there.
[Galaxy Note GT-N7000 Android Development] sibere:
Fstrim or not?

Hi and first of all thanks for your kernel and all the hard work you're putting in it.

I have a N7000 running CM11 nightly. I have installed your kernel and tried to run fstrim manually on /cache to see the results.

I was very pleased that I had a positive result with a xxxxx number of bytes trimmed.

I have also a LG GPAD 8.3 running kitkat and I did the same on this device.

First attempt, I had the same kind of result with xxxxx bytes trimmed. Then I immediately did the same again and I had a return of 0 bytes trimmed, which is making sense because nothing was written on the partition (/cache) in the mean time.

So I tried this on my N7000. And to my very surprise, each time I'm running the fstrim -v /cache command, I'm getting a result with the same amount of bytes trimmed when it should be 0 on the second attempt and the following as nothing should have been written on the /cache partition.

I tend to think that even there is a return of xxxxx bytes trimmed (approx corresponding to the space left on the partition), nothing is actually trimmed.

Am I wrong?
[Galaxy Note GT-N7000 Android Development] Lanchon:
don't worry, it does trim. the kernel remembering the what was trimmed only uses up scarce ram, it better not. makes sense if fs is mounted with DISCARD, but not otherwise.
[Galaxy Note GT-N7000 Android Development] sibere:
I just checked the mount options and it is not mounted with discard.

Good news that it is trimming anyways.

I just repartition mmcblk0 to extend /data by a few Gb. I had 200mb left and I think that even with trim enabled, it was causing some lags. It's easily done with adb in recovery mode and parted :)

now that I have a lot of free space plus your trim kernel, my good ol' Note 1 flies again :)
[Galaxy Note GT-N7000 Android Development] Lanchon:
check out my fpbug kernel :) building trim versions as i write
[Galaxy Note GT-N7000 Android Development] Lanchon:
UPDATE: great news, we have fixed FPBug!!!

TRIM kernels with FPBug fix are online, upgrade and enjoy your stable and fast phones!
[Galaxy Note GT-N7000 Android Development] DDPlayer:
Special thanks for you working, Lanchon!
[Galaxy Note GT-N7000 Android Development] abufrejoval:
3 Kernels, each with a must-have, none with all?

So you have TRIM and FPbug fix and which recovery?

RAW has TWRM (sorry, but much more control with mounts file systems and better suited to my fat fingers) and 60Hz panel refresh

Forest has overclock and FPbugfix but perhaps no TRIM and CWM recovery

Also dunno what bauner actually puts into his ROM, but that's what I currently run with a RAW kernel (very nice, overall!, but no TRIM nor overclock)

I know Christmas has come and gone, but I'd still like:

- FPbug fix

- TRIM support

- overclock

- 60Hz panel refresh (or variable!)

- TWRM

- Asix USB Ethernet support enabled

- MHL adapter support (well, I guess that's impossible for lack of source)

Any chance for a late present?
[Galaxy Note GT-N7000 Android Development] illolatt:
Hi Lanchon.

Many thanks for your work.

(Sorry for my english)

I have 2 N7000 (I and my wife), both with brickbug chips (VYL00M, fw 0x19).

After 2 years, the phones had so much delay in every thing that I decided, even if worried about brickbug, to try an update.

Following CM thread and yours, I installed CM 11, then your kernel. I varied also the partition for /data from 2 Gb to 6 GB.

Fstrim works on both phones. Probably a bigger data partition reduces the risk.

Anyway up to now it seems all ok!

Now some, probably good, news for daedric.

For some days I had the same problem you (daedric) report: in the logcat I never found any log of the maintenance trim, but manual trim worked well. I read that many conditions are to meet to start it.

Some days ago, I checked the log as soon as I awoke in the morning, 6 am. The maintenance was reported. Some hours after it was not reported anymore. Same behavior with my wife's phone.

The following days, sometimes I found fstrim in the log, some days I didn't.

So, perhaps it's difficult to "capture" the maintenance trim in the log becasuse of:

1) All the conditions have been met

2) I'm not an expert, but it seems that the log covers a short interval, so, if you search in the log after too many hours from the event (that typically should happen during the night), you'll not find it anymore.

Greetings