Mod please delete

[Root Wizard]

Not using f2fs, decrypted, rooted by flashing supersu zip from recovery, the error is basically the phone doesn't stop rebooting after flashing the kernel once it's on the lock screen without any sort of interaction.
I am on francos kernel r54 now so i an not sure if the kmsg i am providing will have information regarding the previous kernel.
Previously when i was having this problem with the flash kernel i had done a clean flash of both the stock rom and pure Nexus and still had this problem.
However when i tried this kernel i just flashed the stock kernel and then this kernel (the stock kernel is a modified image with force encryption disabled)

Well, I cant come to any verdict without a full clean flash and a kmesg from another kernel. I haven't been able recreate this situation either, nor has anyone else reported it. Sorry I am unable to help.

 

[Yoinx]

I had this problem of constant reboots when ghe rom finishes booting on ghe flash kernel.
Now after trying this kernel i have the same exact problem. I guess it makes sense because this is based off of the flash kernel. The thing is that i can't figure out what the problem is, i have tried several different rom combinations clean install/purenexus/stock rom nothing seems to work, i think its my device but then again francos kernel and singularity kernel work just fine.

Are you using a script or saved settings on a kernel tweak app?

If you are, and you're trying to set things that don't exist in the kernel, you'll very often cause a panic.

 

[hassanabid94]

Well, I cant come to any verdict without a full clean flash and a kmesg from another kernel. I haven't been able recreate this situation either, nor has anyone else reported it. Sorry I am unable to help.

No problem, thanks for looking in to it anyway.
I'll make sure to make a kmsg next time i try to flash this kernel and do it with a clean install.
@Yonix
I am not running any script however i do use kernel auditor but i made sure to clear the app data and even uninstall the app when i faced this problem.

 

[Root Wizard]

No problem, thanks for looking in to it anyway.
I'll make sure to make a kmsg next time i try to flash this kernel and do it with a clean install.

Alright, Thanks. Kmesg can help with everything troubleshooting a problem like such.

 

[Nautilus74]

I've tried Flash Kernel (1.1 , 1.2) on my N6 on f2fs (only data) and I had bootloop (I had to create new partitions with fastboot command !)...
....you wrote: "Based off of and forked from Flash Kernel".........

actually MagiKernel works on f2fs ? Someone has tested it?

 

[Root Wizard]

I've tried Flash Kernel (1.1 , 1.2) on my N6 on f2fs (only data) and I had bootloop (I had to create new partitions with fastboot command !)...
....you wrote: "Based off of and forked from Flash Kernel".........

actually MagiKernel works on f2fs ? Someone has tested it?

Confirmed by myself. Been running two days on /data and /cache F2FS flawlessly.

 

[Root Wizard]

Hey everyone! Expect a new beta build Sunday as well as a beta/stable merge! Lots of things will be changed and reworked.

 

[Bundizle]

Hey everyone! Expect a new beta build Sunday as well as a beta/stable merge! Lots of things will be changed and reworked.

Btw i had problems with my speaker crackling sound with flash kernel since day one. Never had it with yours until u changed source and decided to use his kernel. I don't know what might be the problem.

 

[Nautilus74]

I'm trying your v.1.01 on NitrogenOS and f2fs Data partition.
Works flawlessly and it's flowing on OnDemand governor!
Thanks!

 

[Root Wizard]

I'm trying your v.1.01 on NitrogenOS and f2fs Data partition.
Works flawlessly and it's flowing on OnDemand governor!
Thanks!

Actually you should try also /cache on f2fs. It doesnt have any downside and only has upsides. Doesnt even wipe any data.

 

[Root Wizard]

Btw i had problems with my speaker crackling sound with flash kernel since day one. Never had it with yours until u changed source and decided to use his kernel. I don't know what might be the problem.

Hmm, I will look into this. I have not had any speaker issues yet.
EDIT: Have you tried toggling the driver leakage option in KA Mod? Or is this onky happening when low battery? Because if it is only when low battery then this is actually wide spread nexus 6 hardware issue.

 

[Nautilus74]

Actually you should try also /cache on f2fs. It doesnt have any downside and only has upsides. Doesnt even wipe any data.

for a long time I also kept cache in f2fs, but...
...tests say that the reading speed is slightly lower compared to ext4 (as opposed to writing that goes at least twice), therefore, since it is the cache (that a written once, THEN COMES ONLY READ), perhaps it is more correct to leave it to ext4 !

However I have noticed that the following governors decrease the fluidity of the animations of the drawer (I use TSF Launcher):
darkness , elementalx , interactive , nightmare

Instead, the following are perfectly fluid:
conservative, ondemand, blu_active
The first is fine to conserve battery power (but may be insufficient for some games),
the second is fast, but I had an unexpected restart,
blu_active looks perfect !

 

[Yoinx]

for a long time I also kept cache in f2fs, but...
...tests say that the reading speed is slightly lower compared to ext4 (as opposed to writing that goes at least twice), therefore, since it is the cache (that a written once, THEN COMES ONLY READ), perhaps it is more correct to leave it to ext4 !

Technically, this is true of everything on android imo.

You only experience a boost in writing with f2fs. Reading I think it's actually a bit slower.

Since you read far more often than you write on android, I don't believe that you see any real world improvement from f2fs. The only things that write more often than read are you logs (logcat, kmsg, etc) but those are all going to a ramdisk... So you don't actually get any improvement with those by setting anything f2fs.

My 2 cents anyway.

 

[Nautilus74]

I do not agree with you ..... My Nexus 6 is definitely better in f2fs (data partition) during the installation of the applications (and all of us being geeks, we do it often ...: D)
Also do not forget the most important thing of f2fs format: preservation of the memory cells in the long time .... there will be no loss of speed

 

[Yoinx]

I do not agree with you ..... My Nexus 6 is definitely better in f2fs (data partition) during the installation of the applications (and all of us being geeks, we do it often ...: D)
Also do not forget the most important thing of f2fs format: preservation of the memory cells in the long time .... there will be no loss of speed

The memory controller is already supposed to be balancing the writes.

Yes, you get an improvement during the install... But even if you reinstall weekly... This is far less of your usage than reading.

Like I said. Just my opinion... But if F2FS is/was the Holy grail that people make it out to be... More than may one developer (Jaegeuk Kim) would be working on it and more manufacturers would use it by default since it doesn't take much effort to implement.

 

[Root Wizard]

In my opinion, it doesn't make a difference, my daily usage of any filesystem that exists on android hasn't been the deciding factor of what makes a phone fast/slow. I just have it here because, well, it feels cool to be a F2FS hipster instead of an ext4 mainstreamer

 

[Nautilus74]

@Yoinx
thank goodness we are not all equal and that we can have a choice!
Do not implement this option on the kernel for me is rather wrong (and even this choice is fundamentalist .... like a drastic response I received by flar2 (his ElementalX): "it's useless, do not put!"

P.S.:
almost all Samsung mobile use f2fs ....
..... also the Motorola MotoE my son!

 

[Yoinx]

@Yoinx
thank goodness we are not all equal and that we can have a choice!
Do not implement this option on the kernel for me is rather wrong (and even this choice is fundamentalist .... like a drastic response I received by flar2 (his ElementalX): "it's useless, do not put!"

P.S.:
almost all Samsung mobile use f2fs ....
..... also the Motorola MotoE my son!

Probably shouldn't use Sammy as an example for anything *cough* explosions *cough*

No, really. I like it being there as an option. Afterall... That's what XDA is all about, options. Doing whatever you want to do with your device. Well that... and you know... learning to develop.

My dislike of F2FS is the users that post in 20+ development threads "Does this support F2FS?". It's somewhat funny, but annoying at the same time. For 2 reasons. 1. Why don't they just flash and test, that's what XDA is for. 2. If it's that important to you, look through the commits.

 

[Root Wizard]

Probably shouldn't use Sammy as an example for anything *cough* explosions *cough*

No, really. I like it being there as an option. Afterall... That's what XDA is all about, options. Doing whatever you want to do with your device. Well that... and you know... learning to develop.

My dislike of F2FS is the users that post in 20+ development threads "Does this support F2FS?". It's somewhat funny, but annoying at the same time. For 2 reasons. 1. Why don't they just flash and test, that's what XDA is for. 2. If it's that important to you, look through the commits.

Yep, GitHub isnt only for devs, its a great reference for endusers to see what their devs do/change/add.

 

[Root Wizard]

New Stable release update today. Highly advised to take it, as it fixes and adds ALOT over v1.0. Beta and Stable are now even. Let me know if there are any issues with either build.
-RW