yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] jcadduono:
This is due to the errors=panic line in the fstab. Means your data partition is corrupted and you need run fsck on it, actually, back it up with twrp and then restore could work too. If still crashing then maybe your nand is worn out but thats very unlikely. There's no changes between 6.5.3 and 6.5.5 other than adding nfc to sprint ramdisk and forced selinux. Every time I compile a new version I make the number equal to the highest of the others if it's behind.
[Galaxy Note 3 Original Android Development] kpirnie:
Could be my issue as well.

I got a bit of "work" to do, but am going to clean flash with ext4 everything instead f2fs and see what happens. I thought it was along those lines, but still greek unfortunately mate :D

(with all the flashin I do, i have to wonder if mine isnt worn out LOL)
[Galaxy Note 3 Original Android Development] jcadduono:
Sorry no. What advantage are you looking for from intelliplug?
[Galaxy Note 3 Original Android Development] ibosilj:
it was giving me better battery life than mpdecision on temasek kernel and there's that problem that cores can maybe somehow get stuck (not that i experienced it), other than that nothing special, even with mpdecision it's the best kernel i've tried so far regarding battery life, plus spen works on cm
[Galaxy Note 3 Original Android Development] jcadduono:
Shouldn't be any cores getting stuck here. I believe Imoseyon found a way around mpdecision's issues, negating the need to replace it with intelliplug. :)
[Galaxy Note 3 Original Android Development] peped94:
Any news on note 5 port rom ? Is it possible to get this kernel on it ?
[Galaxy Note 3 Original Android Development] jcadduono:
Sorry no news yet, I was focused on the Korean variants this morning.

I'm still looking into it, and have downloaded the Note 5 port for testing already.

(I'm impressed, it's incredibly hacky yet functional, lol, scary even because he is using the same ramdisk for all variants!!!!!!!!!)

Okay Korea & [MENTION=4259265]fbzong[/MENTION], test builds are all up! (aside from lgt and ktt Touchwiz until someone can provide me with their stock kernel images)

Please report back with any issues or success!

Okay, I'm not seeing anything extremely different between note 5 port kernel and stock touchwiz kernel except that he forces selinux to permissive for obvious reasons, and adds "privatemode" support.

Edit: Okay, the environment class paths are quite different lol, here we gooooooooooo.
[Galaxy Note 3 Original Android Development] kouros17:
I had the same problem with v6.5.0 (2015-11-02) on aryamod v7.3 and twrp 2.8.7.0.

I tried everything but the problem remained and I had to change the kernel.
[Galaxy Note 3 Original Android Development] DaOldMan:
You need to check darkera 1.5 because only there they fixed the blinking video recording. I will love Lean on our Phronesis 5.1.1

Thanks a lot!

---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------

Darklord kernels 5.1.1 are here:

https://www.androidfilehost.com/?w=files&flid=34872
[Galaxy Note 3 Original Android Development] jcadduono:
Hey! I finished adding support for DarkLord N5 in my kernel, I'm not sure what this blinking video recording is though, can you explain?

I just need to do a bit more testing before I compile a release version, but first I need to know...

Uhm, where do I find the app drawer on DarkLord N5?

Edit: LOL nevermind, had to long press on home screen, go to home screen settings, and enable app drawer. Wow, so weird having an iPhone.
[Galaxy Note 3 Original Android Development] orbital_71:
which one should i download for N9005. spr, tmo or can?
[Galaxy Note 3 Original Android Development] jcadduono:
eur, I went ahead and clarified that up above.

DarkLord Note 5 kernels are all finished. Try them out and report back, thanks!
[Galaxy Note 3 Original Android Development] lululala:
Hi, did you get the chance to check out the kmsg captured here http://xdaforums.com/showthread.php?p=63668083 for the missing led issue?
[Galaxy Note 3 Original Android Development] jcadduono:
Hey, wanna check if the DarkLord N5 version of my kernel works on Phronesis 5.1.1? I figure since it uses DarkLord N5 as a base and probably doesn't have any init differences, it should work perfectly fine.

yeah I went over it but couldn't find anything. :( I will need more people with broken LEDs to report with their device info, ROM version, idleKernel download link, etc. so I can pin point the issue.
[Galaxy Note 3 Original Android Development] fbzong:
dual boot can not change

https://snapshots.noobdev.io/

I use dual boot;

but your kernel can not change dual boot zip file;
[Galaxy Note 3 Original Android Development] frequentc:
I posted this in the N900T thread, but it's relevant to people here too.

I tried 6.5.0 on CM12.1, and it ran great on an N900T. Seems very fast and stable.

No problems other than the 100% brightness bug mentioned in the first post, which I just double checked isn't in the stock CM kernel.

Battery life was really good. Woke up to 99% battery (about 0.1% drain per hour) over around 6.5 hours, and I had a call during that time, so the notification light was running for a while. Stock CM12.1 battery drain was about 0.2% per hour for me (after my fixes).

Ran antutu benchmark, and the results were good (around 46.3k without overclocking), which is very similar to what I got with the stock CM kernel (46.2k). The newest leankernel 5.2 that just came out got about 44.9k. Spreadsheet with detailed results is attached.
[Galaxy Note 3 Original Android Development] jcadduono:
http://xdaforums.com/showthread.php?t=2447534&page=252#post63697999
[Galaxy Note 3 Original Android Development] fbzong:
your kernel can not

I know method;

others kernel can change;

your kernel can not change;

please try it

thanks;
[Galaxy Note 3 Original Android Development] jcadduono:
what does this mean lol
[Galaxy Note 3 Original Android Development] peped94:
Is it officially support note 5 port rom ? Anyone here has successfully tested it ? How is it ?
[Galaxy Note 3 Original Android Development] cuezaireekaa:
Lol [emoji23] [emoji23] [emoji23]

sent from smn-900t on mnmlROM°w/lean6.5.0
[Galaxy Note 3 Original Android Development] jcadduono:
looks like chenxiaolong fixed dualbootpatcher so it should work with his latest git build if you guys wanna try it out.

version 8.0.0.r1903.g6edead0 or newer.

Officially supported yup! I've tested it myself, but only on N900W8. He's been using the exact same kernel for EVERY variant, so I am hoping by proper variant splitting I might have fixed a few bugs in the Note 5 port as well. :)

OT: What if webmaster@xda really does check emails! (I'm bored, and off to bed I go!)

http://puu.sh/lcmKt/20a82927a7.png
[Galaxy Note 3 Original Android Development] jcadduono:
filesystem errors happen a lot if you undervolt just the tiny bit, that's why i don't recommend undervolting
[Galaxy Note 3 Original Android Development] kpirnie:
Stock voltage :)

I've had issues with f2fs before. Similar, but I don't think it panicked...
[Galaxy Note 3 Original Android Development] ithehappy:
Thanks mate. I have changed both these, disabled Adreno Idler, and changed GPU governor to Performance, and its a quite a lot smoother than before, but I am not entirely sure whether it is still as smooth as the damned stock kernel. :laugh:
[Galaxy Note 3 Original Android Development] kpirnie:
Unfortunately it wasnt filesystem...

back to the drawing board for me :)
[Galaxy Note 3 Original Android Development] bailey2408:
Nope still on ext4.. I find it weird that its so unstable for me when i can install leankernel 6.5.3 which refuses to cause a random reboot and this is loosely based on it now.. thx [MENTION=5672995]jcadduono[/MENTION] for response and recommendation.. but if data partition was going bad would not all kernels start crashing or is it just a failsafe kernel panic tjat was added that other kernels dont have?
[Galaxy Note 3 Original Android Development] jcadduono:
have you tried doing su & cat /proc/kmsg > /sdcard/kmsg.log (allow to run in background) then try to reproduce crash and share kmsg.log after the reboot (pref after piped through xz -9e or 7zip)
[Galaxy Note 3 Original Android Development] kpirnie:
That's cleared on boot right?

Just cleaned installed back to ext4 lol ;)

But, I got one more flash in me today ;) I'll setup a script to run where in the boot process? post fs data? or should I wait until after the bootanimation?

---------- Post added at 04:31 PM ---------- Previous post was at 04:29 PM ----------

Or should I start a log earlier than that? I can go back to early_init...
[Galaxy Note 3 Original Android Development] jcadduono:
No just in terminal emulator or adb, any time before crash, later the better, I only need the crash reason, reboots usually send a reason to kmsg 5 seconds before reboot actually happens.
[Galaxy Note 3 Original Android Development] bladecgn:
*Sometimes* after waking up display is very dark. 6.5.3 with temasek rom.

Otherwise this is an ingenious kernel, very smooth and very good battery life. I love it. Thanky you very much!
[Galaxy Note 3 Original Android Development] kpirnie:
yeah mate, havent messed with it since:

http://xdaforums.com/showpost.php?p=63889939&postcount=374

I wonder if that's it... isn't stock lean

$BB echo "740 740 740 740 750 760 770 780 790 800 810 820 830 840 855 865 880 890 905 920 935 945 960 970 985 1000 1015 1050 1090 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table;
[Galaxy Note 3 Original Android Development] Bushido76:
Hey JC, some pages ago you mentioned, that you sucessfully migrated /cache /data /system to f2fs. Could you sum up the tools and steps you did use?

I did format /cache and /data to F2FS and just wanted make a "clean" start without any partition restore. After a hang in boot process the phone reboots again and all partitions are back to ext4.

Is this normal behaviour? If so, how can I successfully backup /data in ext4 and restore it to f2fs? (I read about a lot of problems when doing so.)

Thanks in advance, B
[Galaxy Note 3 Original Android Development] bailey2408:
Alright here is log.. after 1st reboot it rebooted again shortly after boot again so i had to install dif kernel to get file uploaded.. will be willing to test anything if you can find a problem..thx
[Galaxy Note 3 Original Android Development] jcadduono:
ok that's certainly different, something is trying to set weird cpu clock frequencies and seems like voltages too and the kernel doesn't like it...do you have some kind of kernel tuning app installed? also does it still reboot with phone unplugged, or does it reboot faster when you unplug and plug in your phone repetitively?

you can just back up /data normally from ext4, and to restore to f2fs you need to format data as f2fs (if that fails, go to twrp terminal and do `mkfs.f2fs /dev/block/mmcblk0p25` and it will succeed), then go to twrp options and enable rm -rf while formatting, then restore your ext4 /data back to it.

from what I can tell, it's impossible to back up f2fs /data though. the backup seemingly succeeds, but it will just crash twrp no matter how you try to restore it.

if you use a kernel older than 6.5.5 permissive then it will turn all your partitions back into ext4. you will probably also have to boot with ext4 data partition if starting fresh, then backup and restore that to f2fs once set up. i don't think touchwiz likes booting with blank f2fs /data partition. :\

in totally random other news, look at the size of my collection!

https://idlekernel.com/flash-tools/firmware/

(and it's growing as i find more)
[Galaxy Note 3 Original Android Development] kopitalk:
[MENTION=5672995]jcadduono[/MENTION] Fyi the mkfs.f2fs binary included in twrp-hlte is newer (v1.4.0) than one in your modded twrp-hltecan (v1.1.0).
[Galaxy Note 3 Original Android Development] jcadduono:
cool, okay, i'll throw the binaries from hlte into hltecan twrp maybe that will fix some things

kind of pissed off at twrp dev for holding back updates in other devices that are pretty much the same, but guess i cant blame him with all the devices he manages

this should fix encryption on f2fs but still probably broken restoring f2fs

better idea, i think i will just say don't use hltecan twrp and stick with hlte twrp holy crap there's a huge difference it's like hltecan twrp is wayyyyyyyyyyyyyyyyyyyyyyyyyyyy behind on twrp commits, why does it even exist
[Galaxy Note 3 Original Android Development] Bushido76:
Thank you for explaination. I'm on 6.5.5 so I would not suspect the SELinux mode for the automatic switch to ext4.

At the moment I'm experiencing another problem. Everything worked ok - changing fs - restoring backup - but my phone hangs at the boot loader screen. That shouldn't be a problem, but I can't boot to TWRP (2.8.7) anymore. I can see the blue TWRP screen and then my phone turns off. Is anyone here, who experienced the same effect? Any tricks to get recovery working again? Thx!
[Galaxy Note 3 Original Android Development] kopitalk:
Yes, I discussed this in my earlier post and this is due to corrupted /data partition. The remedy is posted in [MENTION=5672995]jcadduono[/MENTION]'s report in TWRP github here. Anyway what you can do is to do a battery pull, boot to download mode, flash the stock recovery image in ODIN (you can download it from here courtesy of [MENTION=5672995]jcadduono[/MENTION]), boot to recovery, do a factory reset, boot to download mode, flash twrp tar ball in ODIN, and voila you're back in /data ext4 and a working TWRP.
[Galaxy Note 3 Original Android Development] jcadduono:
i'm pretty sure this idea is going to fail horribly but i'm compiling all the latest twrp binaries and whatnot with idlekernel hoping things will be all cool and flawless, let's just hope it's somewhat friendly to cm12.1 ramdisk contents

and woo collection's complete i have all the latest kernels, modems, recoveries, and bootloaders of every model idlekernel supports
[Galaxy Note 3 Original Android Development] Bushido76:
I'll keep me fingers crossed. On my other phones I did use PhilZ recovery and never experienced this bunch of problems - but unfortunately he did stop the development of his recoveries. :(

Maybe you could release an "idleRecovery" in which we can fix some of the most anoying bugs. :)
[Galaxy Note 3 Original Android Development] jcadduono:
My first compile LOL.

The only bug I see so far (aside from the many stock bugs) is that the TWRP boot screen lasts a whole 15 seconds, enough to drive me nuts. Maybe I should LZO the ramdisk.

I actually thought this was really funny:

AND I'm incredibly disappointed now because TWRP terminal doesn't support the read command so I can't choose an option.

Also, as usual, cat /proc/kmsg crashes the terminal ;(

Oh well, I can still use it in adb shell bwahahah!
[Galaxy Note 3 Original Android Development] Kamy:
Sorry for lttle OT,

Altough Philz recovery project is abounded, still works flawless and MTP is semi working though it is totally broken on TWRP. I don't know about f2fs support though. Both TWRP and Philz are based on kit kat recovery.
[Galaxy Note 3 Original Android Development] jcadduono:
OT is fun, I like any sort of discussion in my threads, more for everyone to know, knowledge is power I say. I hope the mods don't come knockin' :D

I think I will build twrp flashables for all variants and just place them alongside the other kernel options. It seems that I've fixed the black screen after boot logo bug from corrupted data partition...somehow. Unfortunately all I'm doing is text file editing because I don't have the android NDK installed or any java environment so I'm not actually compiling twrp just placing system content here and there like a custom ROM I guess lol. I was gonna have all the builds up tonight but the wind up here is crazy. Powers out so I'm gonna get some shut eye and hope the powers back up in the morning to make Finnish pancakes. I mean compile kernels....uhh. Nope, definitely pancakes sorry guys. ;)

Wonder if mtp would work by placing some cm binaries here and there...lol
[Galaxy Note 3 Original Android Development] Bushido76:
Thank you for your support - finally I got it working. :good:

Very strange, that restoring an ext4 backup to a freshly formated f2fs partition is only possible with the twrp-hltecan-recovery hosted on JC's file-space. With TWRP-2.8.7-hlteeur it will corrupt the data partition on european N9005. [MENTION=4476875]kopitalk[/MENTION] reported the behaviour some pages before. Otherwise backing up and restoring f2fs is not working properly in the canadian recovery. Conclusion: We need a recovery version in which both functions are working properly. :)
[Galaxy Note 3 Original Android Development] sbassios:
Hello to all,

I am simple user of my note 3 and i am very pleased from you work and the excellent battery life.i have the phronesis rom on my note 3 and i have the 6.5.3 kernel and i have a little problem with the auto brightness.Did you fix it on 6.5.5 kernel?

Thank you in advance for everything.
[Galaxy Note 3 Original Android Development] Bushido76:
Auto brightness is working great in 6.5.5. I'm not sure, whether the last brightness changes were in 6.5.3 or 6.5.4.
[Galaxy Note 3 Original Android Development] walterrbe:
Hi guys is it ok to flash the zip using CWM?
[Galaxy Note 3 Original Android Development] alek889:
So far,so good!!!!
[Galaxy Note 3 Original Android Development] 6h0st:
Great job! Kernel is working perfectly. Thank you!
[Galaxy Note 3 Original Android Development] mircea89fzr:
Where can I find the changelog? If I open CHANGES at https://idlekernel.com/touchwiz-lollipop/ is says "Page not found".
[Galaxy Note 3 Original Android Development] kpirnie:
Nice collection mate :)

I have a couple things to fix, but I can't see wth the reboot occurs in mine. It's not a full reboot, more like a hot reboot

I'm going to test stock 6.5.5 right now. I'll run the kmsg, and see what I can see :)
[Galaxy Note 3 Original Android Development] kpirnie:
[MENTION=5672995]jcadduono[/MENTION]

Stock 6.5.5 (no mods)

n900t

I rebooted, fired up terminal emu., ran the `cat`, hit home, fired up TiBi, started to run a batch restore.

I am fully f2fs formatted

ot side note... not real sure if I'm looking at the right spot to cure my service/domain issues, but I added them to service_contexts as system_app_service (figuring I don't need any of them to run constantly)

I do understand the concept, I just don't know what properties are available. I looked @ Google and it wasn't too helpful, so now I get to go back 20 years and experiment :D LOL :laugh: :cyclops::cyclops::cyclops::cyclops::cyclops:

EDIT: You happen to know how to kill some of that Battery info? ;)

I have to wonder if the dual mounting has something to do with this... hmmm... bash to the rescue ! ;) :D
[Galaxy Note 3 Original Android Development] kopitalk:
[MENTION=5672995]jcadduono[/MENTION] Have you seen this? I'm not sure if this is related but I'm gonna try it tomorrow.
[Galaxy Note 3 Original Android Development] kouros17:
The same here.
[Galaxy Note 3 Original Android Development] kopitalk:
https://github.com/jcadduono/idleKernel-note3/commits/ik-touchwiz
[Galaxy Note 3 Original Android Development] peped94:
Which one should i flash if im using aryamod 8.0 ? Permissive or enforcing ? Im new on tw 5.0 before this im using note 5 port rom
[Galaxy Note 3 Original Android Development] jcadduono:
This does sound like it could be related to MMC CRC option, but it's possible that there could be some bug in last few commits I took from ext4 however unlikely since it's from 3.4.110 and that's rock stable. Maybe I should set default back to on, try running with mmc crc on for a while and see if it fixes things and report back please.

As far as I know, yes. The installer is like 1 line and I'm sure CWM can handle it!

No brightness changes since uhmm 6.5.2! I don't have any issues with brightness but I don't do much testing on note 5 roms. :/

Fixed that just now, sorry! Also added SOURCE and CHANGES links for note5port. It seems last time I fixed that my scp session closed before the upload finished. ><

I didn't know modifying the context files in the ramdisk did anything. I thought they were used to compile sepolicy. I was just guessing though, is it doing anything?

Battery messages are from healthd and I don't have android NDK installed to compile it with less annoying logging. :/ that's just from touchwiz stock ramdisk. Easiest thing to do when reading kmsg is to cat /proc/ksm | grep '^\<[0-4]\>' and change 4 to level of logging you want. (I like 4, I think it's warnings)

That's a fix applied to the recovery I put in my first post. It shouldn't be necessary with the newer mkfs.f2fs that was modified by motorola to add -r for reserve space. (lack of -r made format data fail, and -r fixes encryption by reserving space at end of fs for encryption footer)

It's clearly stated in DOWNLOAD section :(
[Galaxy Note 3 Original Android Development] Bushido76:
That's correct - changing that file won't do anything to the rom. It contains the default file/process contexts and is used to compile the SELinux policies. Only the policy will decide wether an access is granted or not.

Imagine that changing one text file could disable the complete SELinux security concept? That would be more likely a KNOX out. ?
[Galaxy Note 3 Original Android Development] jcadduono:
https://bitbucket.org/joshua_brindle/sepolicy-inject

lol :D

Chainfire's SuperSU also includes a "supolicy" and a "libsupol.so" that he uses to inject supersu policies into sepolicy.

It's a pretty cool concept.
[Galaxy Note 3 Original Android Development] Bushido76:
This guy is amazing. Without his great ideas flashing our phones wouldn't be same. Thank you very much [MENTION=631273]Chainfire[/MENTION] ! ?

---------- Post added at 08:21 PM ---------- Previous post was at 08:02 PM ----------

Just a short addition in the case you are using the permissive version of idleKernel (6.5.5 is really permissive ?). There shouldn't be any issues concerning security restrictions as SELinux is only running "in background" and will never forbid anything. It's just logging the security issues and posting auditing messages to the logcat. But it does not mean, that your problem is security related.
[Galaxy Note 3 Original Android Development] jcadduono:
Somewhat OT but becomes on-topic when I post TWRP builds here...

Anyone willing to help out bigbiff @ https://github.com/TeamWin/Team-Win-Recovery-Project/issues/520

He needs recovery.log & some kernel logs from dmesg from people having issues with f2fs on TWRP for any hlte models.

If you could pastebin those and post links in the issues thread I linked above that would be really helpful!

(I'm busy with my custom TWRP builds and don't want to provide misinformation through my own logs!)

[MENTION=4476875]kopitalk[/MENTION] [MENTION=3115214]Bushido76[/MENTION] you guys are the helpful types :D

Also my TWRP builds are up.
[Galaxy Note 3 Original Android Development] Bushido76:
I'd like to help but our (HLTEEUR) main problem is the conversion of the data partition from ext4 to f2fs. We have to switch to your HLTECAN recovery to get it working and not to corrupt the data partition. IMO this is a different issue and would need a different error ticket.
[Galaxy Note 3 Original Android Development] jcadduono:
Try going to Mount menu, unmount everything except microsd (assuming your backup is on there) and then Disable MTP. That worked for me on hlte recovery.
[Galaxy Note 3 Original Android Development] Bushido76:
What is included in your builds? The HLTECAN source code + updated binaries + idleKernel?

Unmounting all partitions did solve the corrupted data problem after restoring an ext4 backup to a f2fs partition?