yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] kazuna69:
Gezz thanks!!

XD

I'll thanks you tomorrow! :highfive:
[Galaxy Note GT-N7000 Android Development] KalZakath:
Cm12 with your new kernel is blazing fast :)
[Galaxy Note GT-N7000 Android Development] forest1971:
Trim Support

any plan to include Trim support as well in future?[/QUOTE]

As U wished Trim support version already provided in here: http://xdaforums.com/showpost.php?p=57916161&postcount=521

Worked like a charm and make things much faster :victory::victory::good::good: !
[Galaxy Note GT-N7000 Android Development] KalZakath:
As U wished Trim support version already provided in here: http://xdaforums.com/showpost.php?p=57916161&postcount=521

Worked like a charm and make things much faster :victory::victory::good::good: ![/QUOTE]

Checking atm, will give feedback later.
[Galaxy Note GT-N7000 Android Development] abzjji:
My device has an "insane" chip. That means i have to download the Kernel without TRIM support right?
[Galaxy Note GT-N7000 Android Development] forest1971:
Your choice. If feel unsure then choose one without. Cheers.
[Galaxy Note GT-N7000 Android Development] KalZakath:
I am having insane and using trim kernel. Fast as hell and no issues. Big up for [MENTION=4576973]forest1971[/MENTION]
[Galaxy Note GT-N7000 Android Development] abufrejoval:
Should still be safe!

Mine is also reported as 'insane' but if I look at the documentation around the eMMC bug, the dangerous operation which may result in defective eMMC blocks is a 'secure erase' command, which isn't ever issued during normal operations.

In fact the secure erase SATA command affects the entire disk, which in the case of an eMMC should never be used, because it would literally erase everything, including recovery and at least the latter stages of the bootloader. Perhaps these eMMC chips support a partial secure erase for things like wiping of partitions... I really don't know. In any case the modifications from Samsung ensure that the secure erase command is never issued by any kernel that has the fix (which includes this one) and therefore there should be no danger.

TRIM is a block level operation and ok to use even with the eMMC chips that have the defective firmware.

---------- Post added at 04:07 PM ---------- Previous post was at 03:58 PM ----------

I had the same issue when coming from OmniROM KK.

There is an old trick, reported way back on this forum, which seems to do the job:

1. unplug any charger

2. switch to airplane mode

3. shut the phone off

4. remove the battery

5. wait (nothing excessive, couple of seconds should do)

6. insert battery

7. turn the phone back on

8. deactivate air plane mode

9. switch to standby

10. wait (perhaps a minute or two)

11. verify two minutes of deep sleep via CPU spy or similar

Ich habe keine Ahnung warum das funktioniert, aber bei mir hat es das Problem gelöst. Es übersteht dann auch reboots etc. und selbst den Wechseln von Kerneln. Lediglich beim Wechsel zwischen KK und LP könnte es wieder nötig werden.
[Galaxy Note GT-N7000 Android Development] abufrejoval:
How do I adjust GPU clock?

First of all, thanks! The LP version runs quite well on BETA3.

Of course I was so eager trying TRIM I overlooked that the trim enabled version was a separate post =:-o

And then I forgot to properly benchmark before and after ~8-o

But the first pass through /data took a long time and thus seemed to get a lot done.

I then took a long time to verify that 1.6GHz overclock would actually be safe with my device and AnTuTu's stability tests seems to imply it is.

I then wanted to adjust the GPU overclock to see the impact on graphics benchmarks and found that while AnTuTu's CPU master seems capable of setting the CPU clock, the GPU clocks seem inaccessible to that application.

Is there a command line option or do I need to use some custom tuning app?
[Galaxy Note GT-N7000 Android Development] Copkiller2010:
[MENTION=2917899]forest.[/MENTION] Can u create a trim kernel for beta 1 based RR Rom ? Beta2 and 3 are battery eater for me. I dont know why.

Gesendet von meinem GT-N7000 mit Tapatalk
[Galaxy Note GT-N7000 Android Development] avincric:
[MENTION=4576973]forest1971[/MENTION]

the test says 'YES.insanechip'.so if i download the trim version of your kernel, i need to do TRIM with the trim-apk you provided, right? and if yes, then how often?

thanks very much
[Galaxy Note GT-N7000 Android Development] forest1971:
once a few day or once a week would be ok.
[Galaxy Note GT-N7000 Android Development] I_android:
you have to trim using the trim-apk only once....then the kernel would do it automatically, you don't have to use trim-apk again. That's why dev's have enabled trim support in the kernel itself.
[Galaxy Note GT-N7000 Android Development] forest1971:
Maybe, let me see. Cheers
[Galaxy Note GT-N7000 Android Development] I_android:
[MENTION=4576973]forest1971[/MENTION]

do we need to use trim-apk regularly? I think Lanchon said in his detailed explanation that we don't have to use this apk again kernel will automatically trim at night while charging. Please refer to Automatic trimming section at http://xdaforums.com/showpost.php?p=54724225&postcount=1
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
In Lollipop the partitions are trimmed when wiping or installing a new ROM. Our recovery disables this feature for safety reasons but it doesn't make sense since the kernel is safe now.

Then /data and /cache are trimmed on a schedule by Android 4.3+. Other partitions need to be trimmed manually as it's not done by the recovery in our case. /system only needs to be trimmed once since its content doesn't change over time.
[Galaxy Note GT-N7000 Android Development] No.12:
So, how often we need to trim?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
When installing a new ROM trim /system, /data, /preload and /cache once (the recovery is supposed to do it). Then /data and /cache will be automatically trimmed by the system on a fixed schedule.
[Galaxy Note GT-N7000 Android Development] No.12:
One more question. I have insttaled beta3 rom, used app forest provided for trim, but there is no preload trim to choose inside.

So, I need to use it once, and system will do schedule triming afterward?

Thanks again.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
You can do it once and for all using adb shell and "fstrim -v /preload" since this partition is never used for non-Touchwiz ROMs.
[Galaxy Note GT-N7000 Android Development] avincric:
[MENTION=4216554]No.12[/MENTION]

even the lagfix app apk,provided by forest1971 will do the TRIM , i think,even though you may need to do trim once every few days.
[Galaxy Note GT-N7000 Android Development] forest1971:
Noticed something interesting about trim:

- Before trimming (the first ever done on my Note for so long now) the size of my LP Beta rom back up is more than 2.2G and it took 10-15 minutes depend on internal or external card used.

- After trimming: the back up size is now only 1.3G and it took only 1.5 minutes to back up to internal sdcard!:victory:

That means too much garbage is lying there in the partition and mistakenly considered as useful data by the recovery/system.

This is a huge benefit of trimming. Kudos to [MENTION=4141005]Lanchon[/MENTION]! :good::good::good::good::good:
[Galaxy Note GT-N7000 Android Development] Lanchon:
are you sure you didnt turn on compression? the size of the backup shouldnt have been affected at all. not by a byte. smaller backup means less data. if u have an older backup you can compare the contents of the tarballs on a pc and see whats going on. if you didnt clear apps caches etc, didnt uninstall stuff, didnt compress the backup, then some of your partitions may be corrupted at the file system level. id do fscks from recovery.
[Galaxy Note GT-N7000 Android Development] forest1971:
No compression turned on at all, but I did delete the 0 folder left from earlier beta.

Still, restore also become fast. Before it tool 4-5 minutes for beta, now only 1.5 minutes! There must be something good about free space, data mistaken by recovery!

BTW, thanks a lot for your great work to make our device work much better!:good:. Keep up the great work!

Cheers
[Galaxy Note GT-N7000 Android Development] Lanchon:
it can be much faster to backup and restore, that is ok. but backup size should be the same. trim should be invisible to userland except for increased performance and less battery usage. thank you!!!
[Galaxy Note GT-N7000 Android Development] carabao72:
hello,

I tried to read the many messages on the kernel Forest-LP-Kernel_V2_T. But one English being a high level, I would like to have confirmation on the problem of the brick.

- My note is part of the notes with the brick problem

tried with: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en

- He is currently started under the [ROM] [5.0.2] NightOwl BETA 3 [CM12], with the cwm 6.5.0

Since I work in a protected cwm brick problem (for wipes), can I use the kernel Forest-LP-Kernel_V2_T or cwm then has nothing to do with the brick of the problem and the use of kernel forest ?

Sorry for my questions, but I'm a little lost, given the number of message.

french: bonjour,

J'ai essayé de lire les nombreux messages sur le kernel Forest-LP-Kernel_V2_T: . Mais on anglais n'étant d'un haut niveau, j’aimerai avoir la confirmation sur le problème du brick.

- Mon note fait partie des notes ayant le problème de brick

essayé avec : https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en

- Celui tourne actuellement sous la [ROM][5.0.2] NightOwl BETA 3 [CM12] , avec le cwm 6.5.0

Vu que je fonctionne sous un cwm protégé du problème de brick (pour les wipes) , puis-je utiliser le kernel Forest-LP-Kernel_V2_T ou alors le cwm n'a rien avoir avec le problème du brick et l'utilisation du kernel forest ?

Désolé pour mes questions, mais je suis un peu perdu, vu le nombre de message.
[Galaxy Note GT-N7000 Android Development] tysonraylee:
what sorcery is this!! my device is now too fast to comprehend :D

running RR 5.2.7 beta 3 + Forest LP v2 trim kernel on insane chip and the performance gain is certainly noticeable. Though the device went into bootloop after flashing it but a wipe cache/dalvik solved it maybe it was because i restored a backup and flashed the kernel over it anyways everything is fine now.

Once the device booted i noticed the gain in responsiveness of the device which i guess means that it already did the trimming but i went ahead and did the trimming manually via terminal too just to be sure :)

Since triming is now active does wiping means trimming too? i mean if i wipe a partition manually in recovery does it trims it before/after wiping?

also is trim required after a partiton wipe?

and as Geeckodev mentioned we only need to trim /system partition before installing a new rom? does this mean i run the commands in terminal or use the lagfix.apk everytime before i want to install a new rom?

Thank you very very much for your work and time :D

I wish this came to our device earlier but its here nonetheless and its working perfectly :D

Bless you O white wizards of mountains (Lanchon,forest1971,GeeckoDev) :D Hope to see more from you :)
[Galaxy Note GT-N7000 Android Development] forest1971:
Good to know that it works fine even with insane chip !:victory: tks!

It is noted that trim is still disable in Philz recovery.

Should trim after install new rom to complete the work not done by the recovery. Otherwise do as suggested by GeeckoDev.

Cheers
[Galaxy Note GT-N7000 Android Development] I_android:
[MENTION=4576973]forest1971[/MENTION]

on bauner beta3 after flashing your kernel power off charging (animation) is not working. Could you please check as bauner says that in beta3 the init's have changed to support low power mode and offline charging animation.
[Galaxy Note GT-N7000 Android Development] Copkiller2010:
I dont know what the reason. I flashed the v2 trim kernel with RR beta3 (full wipe done) and again my big Problem. I changed CPU speed From 1600 to 1200 => 200 without changing gouvanour. Trim and Speed really nice. Now mY Problem: I charged my phone at night. This morning my phone completly empty an NY "complete" phone was ultra ultra hot. Directly removed battery and wait for cooldown. Used my second battery to revert back Tod slimkat. What is the Problem. RR Rom, kernel vor kernel CPU Speed Settings ? Please help. Thanks
[Galaxy Note GT-N7000 Android Development] 01000010:
Tried Forest-LP-Kernel-V2-T on NightOwl beta3

I've trimmed and used it for a day but I got several reboot and I reverted to beta3

GT-N7000 - Bauner's NightOwl beta3
[Galaxy Note GT-N7000 Android Development] KalZakath:
After one day of usage of v2T on cm12:

*phone is overheating

*getting soft reboots,

*getting hard reboots when realy hot with sound of something inside cracking.

Reverted to stock bauners kernel.
[Galaxy Note GT-N7000 Android Development] forest1971:
Thanks, I was not aware of the change of init in Beta3. Now it is updated! Trim proved safe so only one version is made :victory:

Forest-LP-Kernel_V3_T change log:

- Update inits changes in CM12 Beta3

- Now kernel support Off-power charging and battery animation.

- Kernel suport trim function., same as V2_T!

- Use with NightOwl Beta3 only! (Not recommended for RR5.2.7 since few probs found in this combination)!

How to do a manual trim? look at this post: http://xdaforums.com/showpost.php?p=57916161&postcount=521

Download:

http://www.mediafire.com/download/movs7gu4oe6yb1n/Forest-LP-Kernel_V3_T.zip

- Enjoy!

Edit: Anyone who is on Beta3 and using my V2 kernel should update it to my V3-kernel for added benefits and avoiding bugs!

Thanks and Credits to [MENTION=799465]bauner[/MENTION]
[Galaxy Note GT-N7000 Android Development] mjrifath:
Hi Forset,

Thanks for your kernel. Is it possible to make without OC..

Sorry for the trouble.
[Galaxy Note GT-N7000 Android Development] forest1971:
No mate. No-frills is your friend.
[Galaxy Note GT-N7000 Android Development] zeu55:
man.. i am really impressed with the battery backup with v3 kernel and beta3 . feels like on stock jb rom. however the minor issue with the rom is heating issue. though it has reduced a lot after beta3 and v2 kernel. still after some use heat goes up but not as much like earlier beta 2
[Galaxy Note GT-N7000 Android Development] forest1971:
Should give kernel a. little more time to settle. Cheers.
[Galaxy Note GT-N7000 Android Development] varinder jaswal:
Hi [MENTION=4576973]forest1971[/MENTION]..

I flashed V3T over RR beta3 and found that there is problem with GPS... GPS is not working at all... I tested it with GPS test app which also showing 0 signal... Then I reverted to the stock kernel..and GPS working again... Is it only me who is having GPS problem with v3t? Please guide... Thanx...
[Galaxy Note GT-N7000 Android Development] forest1971:
Dont know. Have not tested enough. It seems V3 is not for RRbeta3 due to some customization with the rom. I am checking with Varund. For now not recommended. Cheers.
[Galaxy Note GT-N7000 Android Development] carabao72:
Hello,

In the modus operandi, we always speak that the kernel is compatible with the remix beta3! Is it true?
[Galaxy Note GT-N7000 Android Development] Lanchon:
read my i9100 trim kernel thread for info

---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------

trim /system AFTER flashing, if you want to be obsessive about it. (or if you enlarged the /system partition.)

android on other devices never trim /system, even with big partitions, so it is clearly not very important (though that could be fixed at some point).

much better is to empty (if applicable) and trim /preload. (unless you reduced /preload.)

---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------

under no circumstance should a kernel/recovery EVER TRIM ON WIPE!!! this is explicitly excluded from my post detailing how to safely enable trim. enabling trim on wipe CAN BRICK devices. if you want, just trim after wiping.

there is no guarantee that ext4 utils will not be invoke under an unsafe kernel (unless you can guarantee your kernel/recovery will never make it into a rom) so they shouldnt trim.
[Galaxy Note GT-N7000 Android Development] tysonraylee:
trimming after flashing also makes sense as if I am not going to flash a ROM/kernel that supports trim then there is no point in trimming before a flash :)

Thank you very much for the explanation :D

REVENGE SOLVES EVERYTHING
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
The thing is the recovery is tied to the kernel (included in the zImage) on our devices, so if the kernel is safe, we can ship a trimming recovery without worrying about it, right?

I believe /system is trimmed only once when wiping because its content never changes.
[Galaxy Note GT-N7000 Android Development] Lanchon:
trim capable kernel yes. ramdrive with "trim on wipe" in the userland tools of the recovery bundled with that kernel, no! no secure erasing nor nonsecure erasing on wipe please!

your kernel could forked, then 6 months later integrated with a rom, and that rom could be flashed under an unsafe recovery. please dont mine the field. no trim on wipe, it is not needed anyway.

---------- Post added at 04:27 PM ---------- Previous post was at 04:16 PM ----------

more info: cm maintainers are under the impression that these userland tools can run under under a kernel different than the bundled one under some circumstances. i simply take their word.

and before someone argues, even nonsecure erasing on wipe could brick. some devices are affected by trim bug (not brickbug) and nonsecure erase could trigger it. in fact, given the name of the bug, it seems it would.

there are no trim bugged i9100 or n7000 in existence. but there are some d710. and they share the same codebase.
[Galaxy Note GT-N7000 Android Development] forest1971:
Thank you [MENTION=4141005]Lanchon[/MENTION] and [MENTION=5145944]GeeckoDev[/MENTION] for shading more light on the topic and for being extra cautious about restoring trim capacity in recovery!:good:

Anyway, i do not touch the recovery original from Philz which has trim disabled. So no way to trim using recovery in my kernel.

What i recommend is to do trim one time after flashing new rom or restore a rom and booted into android. This seems to make the rom run smoother for me. i understand there is stuff from old rom which trim help to deal with.

Cheers!
[Galaxy Note GT-N7000 Android Development] forest1971:
It should but the rom may have script/apps which change kernel behaviours.

I tested with RR5.2.7 but it did not work out well. There are few probs.

So the conclusion is: I do not recommend using V3_T kernel with RR5.2.7!

Cheers,
[Galaxy Note GT-N7000 Android Development] abdullahchoudhary97:
My favorite settings:

- Governor/Scheduler: Pegasusq/Row

- CPU min 500 Mhz max 1600 Mhz.

how can i change settings...???
[Galaxy Note GT-N7000 Android Development] avincric:
download 'no frills CPU' from play store
[Galaxy Note GT-N7000 Android Development] forest1971:
Forest-KK(CM11)-Kernel_V6_T now with trim support & more!

For folks who are still stick with KK roms (CM11, Omni, Slim) here is the update version with sweet changelog :p:victory::

Forest-KK-Kernel_V6_T changelog:

1. Added Trim support: to ensure smooth running and fast backup-restore. (credits to [MENTION=4141005]Lanchon[/MENTION]) More on trim look at this post

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

3. Rework GPU to three steps: 134-200-267 Kernel now run smoother and cooler than V5 while still handle heavy games easily!

4. Re-enable logcat function (which was disable in earlier version)

5. included OC CPU and Philz recovery as in earlier version

The kernel is really smooth and running cool! KK for N7000 should indeed be stable now!

Important note:

- There are 3 versions for CM11, Omni and Slim you need to use correct version for your rom.

Instruction:

- Flash the kernel zip file in recovery

- Give some time for kernel to settle and enjoy! U may want to to one manual trim after flashing for more smoothness!

Downloads:

- V6_T for CM11: http://www.mediafire.com/download/3163aluzkyzlxxy/Forest-KK-Kernel_V6_T_CM11.zip

- V6_T for Omni: http://www.mediafire.com/download/yw9dmagh658hwac/Forest-KK-Kernel_V6_T-Omni.zip

- V6_T for Slim: http://www.mediafire.com/download/5vger45tmjpmf0s/Forest-KK-Kernel_V6_T-Slim.zip

Credits to:

[MENTION=4141005]Lanchon[/MENTION]

[MENTION=5948587]zeitferne[/MENTION]

[MENTION=5145944]GeeckoDev[/MENTION]

[MENTION=373710]others[/MENTION]
[Galaxy Note GT-N7000 Android Development] AA1973:
You're welcome. Maybe relevant for you [MENTION=4576973]forest1971[/MENTION]

http://tegrak2x.blogspot.de/2011/04/tegrak-overclock.html?m=1
[Galaxy Note GT-N7000 Android Development] forest1971:
Great info buddy. Will do.
[Galaxy Note GT-N7000 Android Development] surender2121:
[MENTION=4576973]forest1971[/MENTION] Have you tried this kernel with some other Kitkat ROM? And getting same result or somewhere similar or close to this cause this is the Best you get with N7000 and this is awesome. :good:

I tried PA and C-ROM with this kernel but didn't get something like this.

P.S. - CM don't have much features that's why i didn't tried this one. :rolleyes:
[Galaxy Note GT-N7000 Android Development] AA1973:
Many things depend on battery life

Network connection

Quantity of media files for media scanner

Applications used

Running services in background

Location on or off

Brightness

Auto sync on or off

...

Not only ROM and kernel are important...

Most important is (IMHO) the second screen where you clearly see that he had a very good mobile network signal. Nearly everything is green!

Sorry for /OT.
[Galaxy Note GT-N7000 Android Development] surender2121:
I Know this. :D

I asked this because maybe its more suitable with CM and that's why he got this much. And not every person use same app or same functions that's why i asked him if he get somewhere similar or close to this with some other ROM. :p
[Galaxy Note GT-N7000 Android Development] forest1971:
Stop making redicilous statement and expect others to do spoon-feed service. Go do some tests and post screenshots by yourself.
[Galaxy Note GT-N7000 Android Development] surender2121:
LOL Okay. I'll flash CM tommorrow and test it. :p

By the way, Thanks for this kernel :good:
[Galaxy Note GT-N7000 Android Development] gtsfreak:
Tried it with latest cm build performance was awesome but battery was draining a lot so restored nandroid backup
[Galaxy Note GT-N7000 Android Development] forest1971:
Just in case, you should give kernel and rom at least two days to fully settle down to really see how batery petformce.

Anyway, CM is still in Nightlies so it is normal that it has higher batery drain than stock 4.12 based roms.
[Galaxy Note GT-N7000 Android Development] Oracle_Eldorado:
is this kernel compatible with this rom ?

http://xdaforums.com/showthread.php?t=2244754
[Galaxy Note GT-N7000 Android Development] Jackwu696:
No. This version of Kernel is for KK ROMS. What you are referring to is a TW ROM. Use [MENTION=4576973]forest1971[/MENTION] 's helloworld kernel for it.

---------- Post added at 07:34 AM ---------- Previous post was at 06:58 AM ----------

2nd day using your kernel with C-ROM, Marvelous performance and hell No significant heating! Great Job well done bro
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
Great performance..
[Galaxy Note GT-N7000 Android Development] rikusuicide:
do you have random reboots ?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
On CM 11 after prolonged time... yes and... but thats on stock kernel as well... so.....
[Galaxy Note GT-N7000 Android Development] panamera2011:
I do not think depends on the kernel, I'm testing the last CM11 11-20140507 nightly with Xposed installed and everything works fine.

No random reboots :good: