yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Oehr:
FYI: atm, TWRP and Android does not work with encrypted F2FS data partition. Once a F2FS formatted /data partition gets encrypted, TWRP (and android) rejects every password one enters. This is also the case if you convert the data partition from EXT4 to F2FS after data has been encrypted. Once its done, the password will not work

osm0sis is currently trying to fix this for the DirtyV kernel: http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655/page1150
[Samsung Galaxy Nexus] MWisBest:
Thank you for the heads up!
[Samsung Galaxy Nexus] osm0sis:
I think Moto's fallback method you use should work fine with f2fs encryption for the FML kernel, but I could be wrong (someone will need to test). I've got something worked out for custom kernel ramdisks that should be universal for ROM commits (Moto fallback/non-Moto fallback) now as well, so it's just the recovery we need. :D

First thing that comes to mind is whether you could add the Moto method to TWRP's source. That'd be by far the most elegant solution, and of course no problem at all for compatibility since the recovery is self-contained. :)
[Samsung Galaxy Nexus] Elibl:
Now I know why converting /data didn't work while cache was no deal at all. Was thinking what the hell I'm doing wrong and didn't remember that I encrypted once some time ago... Not even fastboot erase or format did help. Is it normal that I NEVER have to enter the encryption password? I read at boot should be the normal behavior but not for me^^ thx [MENTION=4544860]osm0sis[/MENTION] for addressing it though
[Samsung Galaxy Nexus] Oehr:
seems to be something different. if you dont get prompted for pass, you clearly didnt encrypt it. TWRP should have also prompted for a pass on start...
[Samsung Galaxy Nexus] Elibl:
Don't know i do remember that i did the encryption but only to data and maybe cache don't remember but maybe pa just couldn't handle it correctly cause the only time I was asked for the password was at boot after f2fs conversion of data. I know the reason can also just be the impossibility to mount data... But as I remember that I did it :-/.

gets one asked at every mount? remembering that data never gets flashed...
[Samsung Galaxy Nexus] osm0sis:
Thank you for taking the time to test that definitively for us all!

[MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] osm0sis:
P.S. Since you're around, what were your thoughts on the feasibility of adding the Moto fallback fstab system to TWRP so that f2fs encrypted will work?
[Samsung Galaxy Nexus] Oehr:
update time! osm0sis fixed the dirtyv kernel. it is now assuming that cache (which doesnt get encrypted) and data (which gets encrypted) use the same filesystem type. read more about it here:

http://xdaforums.com/showpost.php?p=54952929&postcount=11503

http://xdaforums.com/showpost.php?p=54954165&postcount=11508

any chance you can implement this in the next TWRP update, so that its properly working again with all kinds of encryption?

EDIT: whatever osm0sis said lol
[Samsung Galaxy Nexus] MWisBest:
I haven't really done much with the TWRP code before, in fact I think the only thing I ever did with it was to update it to work with the latest libpng, so off the top of my head I don't know however I will certainly check and see!
[Samsung Galaxy Nexus] MWisBest:
New test build available! Made some changes that should hopefully fix booting of the new kernel. If you still are having issues booting it, please try doing a totally clean flash (factory reset)! This was something I had to do so maybe others have to as well.

Also included is memtest and memtester:

memtest is a program for testing memory bandwidth

memtester is a program for testing memory corruption

Due to Dev-Host being slow, I'm going to try uploading to Google Drive instead. Let me know if it is any better!

omni-4.4.4-20140825-maguro-FML.zip (159.56 MB)
[Samsung Galaxy Nexus] Loureiro:
All fine, no problems booting with your kernel after dirty flashing.

Also play store images aren't corrupted anymore as you said earlier.

Thanks man, slick build.
[Samsung Galaxy Nexus] qtoo941:
31 of august is coming so new stable release will be uploaded soon. Can't wait to see it. By the way is it possible to make some optimizations on "ondemand" governor and "noop" scheduler. Thank you in advance.
[Samsung Galaxy Nexus] MWisBest:
Still awaiting feedback from people who had issues with the kernel in the previous build! I need to know if I should continue with this kernel and add all the bells and whistles to it or if I should go back to the old one for now and just improve it a little.

Thanks for the feedback, glad to hear it's booting for somebody!

I can do that if you don't mind waiting an extra stable build (meaning whatever one comes after the next stable build) on the vibration feedback in quick tiles.
[Samsung Galaxy Nexus] iviarck:
I am one of the people who had boot failures on the last build. This version boots.

However.

Dirty flash - systemui in FC loop.

Clean flash - boots and runs. In settings, turn on "Contextual header" option for notifications and back to systemui fc loop.

Wound back to nandroid backup of last stable build.

Hope that's of help.
[Samsung Galaxy Nexus] qtoo941:
Actually i really wanted to see this add-on in fml but i thought it would be easy to find the commits. I don't want to make your work even more complicated. So i don't care. Just asked if there was no problem in adding vibration feedback on quicktiles. About my second request - if you got aome knowledge about kernels i would be happy if you optimize ondemand and noop governor/scheduler because i am using them on every kernwl. But if you must go through some difficult procedure you better don't do it. Only if its possible. I really don't want to make your things more complicated.
[Samsung Galaxy Nexus] Gingerbread1611:
I also had the boot problems in the previous version, but now it works perfectly fine thank you!
[Samsung Galaxy Nexus] MWisBest:
Thank you for the feedback! I'm definitely moving forward with this kernel then. I'm not going to make a guarantee that it's what I use for the next FML release, you never know what bugs might pop up, but I'm very optimistic about it!
[Samsung Galaxy Nexus] Suo.Eno:
[MENTION=3390093]MWisBest[/MENTION]

Just for sake of discussion/speculation though: how much stuff from FML are deemed "safe" to be committed to Omni (since you're Omni's all gnex maintainer now)? What's the official policy on that like? Don't get me wrong I'd prefer to see FML remain edgy as it is, just curious about your dev workload is all.
[Samsung Galaxy Nexus] CYoung234:
I dirty flashed this today, and so far it runs fine. I do not see the memtest or memtester anywhere, though. Can you tell me how to access them? Thanks!
[Samsung Galaxy Nexus] MWisBest:
Well, it depends on what it's pertaining to in regards to safety. The "fancy CFLAGS" and Link-Time Optimization? Not happening. The new kernel? A definite possibility!

Generally with the official OmniROM work I do, it's just things I find while working on FML. It's really not much additional work. I could probably be doing a better job with it honestly, but I'm at least keeping tuna alive and kicking in OmniROM!

Glad it's running good! memtest and memtester are command line programs, you can use them via a terminal emulator on your phone or through an adb shell.
[Samsung Galaxy Nexus] jesan9:
i'm getting systemui fc loop with Contextual header and the gallery is not showing the photos :S
[Samsung Galaxy Nexus] MWisBest:
Made some headway with the new kernel today... in case you didn't notice, microphone button(s) aren't working in the new kernel. Something that I would've never noticed had it not been for the awesome cable I got thanks to your guys' donations :eek:, I use it pretty much every other day! So I got that fixed, not sure if I broke anything else in the process though...

So now I'm going to get some of the usual features added to the kernel, make an attempt at fixing the camera issues, and eventually toss out a new test build. :good:

The contextual header thing is a mystery right now, I'm thinking a fresh build on my end will resolve it. For some reason it isn't effecting toro.
[Samsung Galaxy Nexus] CYoung234:
Lockup after phone call

This is the test build that I installed yesterday. Logcat attached.
[Samsung Galaxy Nexus] MWisBest:
Were you using Bluetooth?

There's also something else I noticed in your logcat I keep forgetting to fix that I'm fairly certain is unrelated to the lockup. To make sure I don't forget about it I'm putting a reminder to myself here: reservedVectorImpl
[Samsung Galaxy Nexus] Loureiro:
I've reached 60 hours uptime with your last test build. No bugs observed from kernel side, no lockups, no sods. I guess it's safe to use this kernel as base to the upcoming development ;)
[Samsung Galaxy Nexus] CYoung234:
I was not using Bluetooth, but it was turned on. I have a bluetooth headset, but do not use it here in Paraguay, as there are enough other distractions on the roads, like cows and pigs wandering across them, along with many, many moto drivers without lights at night....:p
[Samsung Galaxy Nexus] sergialess:
Don't worry, take you time. BTW, is this rom supporting F2FS right now?.
[Samsung Galaxy Nexus] daniil1410:
Yes.
[Samsung Galaxy Nexus] sergialess:
Thanks, Flashed and working very well so far. This rom is pretty fast, even with the stock kernel and settings.
[Samsung Galaxy Nexus] AbhishekS:
That's alright. Your builds are always worth the wait. :D ;)
[Samsung Galaxy Nexus] MWisBest:
College is kicking in to full swing now. Gas is going to cost me $30/week, and it's going to cost me a zillion hours of time, so my time for FML has really taken a huge hit. I'm thinking I'll need to switch to a different system of FML releases, where I have a Beta build and a Stable build. The hold-up for me releasing a new build lately has been that it doesn't feel complete and stable like previous releases, and it's been two months since the last official build which is just ridiculous and is pissing me off. Another contributing factor to the delay is that I'm writing a lot of my own code for this build, especially with the kernel. The majority of the things I've done with FML code-wise previously have just been fixing bugs and things like that, and not writing a kernel driver from basically nothing like I am now. Right now I'm working on "Charger Control". This is intended to be a replacement for the current "fast charge" stuff. The idea is to allow for 'slow charging' via wall chargers in addition to the usual option of allowing 'fast charging' via regular USB ports. The life of the battery can be improved by charging it at a lower current, so this way people who don't need to charge their battery super fast (like me usually) can have their battery not 'degrade' so much.
[Samsung Galaxy Nexus] CYoung234:
Just a quick note. This last build you posted appears to break Skype. I was able to use Skype with the 7/5 build but not with the last one.
[Samsung Galaxy Nexus] pianistaPL:
Bro, i just want to say that last test build is working amazing with latest DirtyV kernel. When i'm using Omni, i can see how buggy and slowly are CM or PA... Your optimized Omni is really something special :)
[Samsung Galaxy Nexus] pa.pn2:
Test build? Where to find that?
[Samsung Galaxy Nexus] sagara.sandaru:
Is there still that noticeable delay when pressing home or recent button as mentioned on OP? I'm currently on PA and I have this same issue. I just want to know if this is still a problem in FML too before I go through backing up all my apps and reinstalling which takes more than 2 hours for me coz I have lots of apps :( I'm thinking about going back to 4.3 so I wanna give another 4.4 ROM a chance before I do that. :)
[Samsung Galaxy Nexus] qtoo941:
Just check my signature ;)

[MENTION=3390093]MWisBest[/MENTION], man thank you for your awesome work and knowledge but i am no longer a maguro owner so i cannot test and use your ROM. It was pleasure for me! Good luck and have fun :)
[Samsung Galaxy Nexus] pianistaPL:
http://xdaforums.com/showpost.php?p=55035133&postcount=420
[Samsung Galaxy Nexus] GamaX320:
this ROM support CM11 theme chooser?
[Samsung Galaxy Nexus] nachiket_xda:
Nope

[MENTION=3390093]MWisBest[/MENTION], what about making a test build with theme chooser? Just one build and no support afterwards, is it possible? I know you don't have time, ignore this if not possible
[Samsung Galaxy Nexus] daniil1410:
[MENTION=3390093]MWisBest[/MENTION] , I know that asking for ETA is against the rules and I totally support that. But my phone is too laggy on PA now and I want to flash back to FML. Will you release an update the next 2-3 days or should I just flash the latest test build? I understand if you are too busy. Thank you.
[Samsung Galaxy Nexus] Bazzu:
I still have omnirom FML 20140705 (~ 1 month and was perfect) with r54 but recently i have 4-5 reboots every day :(...is kernel fault?

Should i upgrade to r56/r57 :)?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] morfances:
Yes
[Samsung Galaxy Nexus] Loureiro:
MWisBest, noticed today video recording is out of sync with audio. Also 1080p recording is laggy. ;)

The issue is present on those two last build at least
[Samsung Galaxy Nexus] Bazzu:
[MENTION=3390093]MWisBest[/MENTION] how is it going :)?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
ETA ninja ?
[Samsung Galaxy Nexus] aliesz:
Could I update this ROM with delta rule?
[Samsung Galaxy Nexus] Bazzu:
Lol :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] aliesz:
Why this Rom has only first page on its launcher!?
[Samsung Galaxy Nexus] AbhishekS:
If the test builds are good enough to be used as a daily driver then I am in, because Galaxy Nexus is my only device and I can't really afford using 'alpha-level' test builds. :P
[Samsung Galaxy Nexus] MWisBest:
Like I said, the only thing that should be totally broken is the camera and video decoding/encoding. For me that's fine as a daily driver, for others not so much.
[Samsung Galaxy Nexus] Loureiro:
Yeah, count me in.
[Samsung Galaxy Nexus] Bazzu:
Last version of the rom and last r57 and i now i have again some strange reboots:(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] mono28aug:
just converted to f2fs

ok, so i just converted my data and cache partition to f2fs and i left my system partition untouched and adb pushed Fml rom, pa gapps and franco kernel . My phone is running all good now but i have a question here, since i left my partition untouched which means its still on ext4 and not f2fs, so now if i want to flash another rom like paranoid then do i need to convert the data and cache back to ext4? or i can just flash normally with recovery
[Samsung Galaxy Nexus] lollipop:
To change to another rom like PA,you must have a kernel that support f2fs(like fancy kernel or dirty-v) and you must convert the rom with this tool : http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702

and no need to convert back data and cache to ext4
[Samsung Galaxy Nexus] mono28aug:
Thanks but I was on mixed partition so I just flashed the pa rom and f2fs supported kernel :) :P but can't really tell the difference between FML and pa now I think both are running quite faster than before
[Samsung Galaxy Nexus] MWisBest:
WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOT.

I got hardware video decoding working with the new GPU drivers!!!!!!!!!!!!!!!!! I've been obsessed with this for weeks and working non-stop on it. Any time not spent on school, has more or less gone to working on this.

Camera is still borked, and I presume hardware video encoding as well (how can I test that without the camera..?), but it's certainly close!

See the main post for a test build and more information! :)
[Samsung Galaxy Nexus] pvkiniyan95:
I know, i am asking too much....a f2fs compatible test edition will be gr8
[Samsung Galaxy Nexus] gautam_nexus:
I believe its f2fs compatible.
[Samsung Galaxy Nexus] AbhishekS:
It already is F2FS compatible. Which format your system, data or cache maybe, FML gets installed irrespective of that and will keep your file formats intact.
[Samsung Galaxy Nexus] pianistaPL:
Hmm, test version isn't f2fa compatible I guess because kernel doesn't support f2fs (I guess ;P)
[Samsung Galaxy Nexus] pvkiniyan95:
u r right buddy, the test version isn't f2fs compatible....
[Samsung Galaxy Nexus] CommanderDuplex:
Awesome work dude!

I want to try that build, can i switch back to older version if i got some troubles with the beta ?
[Samsung Galaxy Nexus] MWisBest:
Not sure what's up with F2FS... it's working fine for me.
[Samsung Galaxy Nexus] pvkiniyan95:
The beta edition stops at Google logo in f2fs...
[Samsung Galaxy Nexus] MWisBest:
Try having system formatted as ext4, and data and cache as f2fs.
[Samsung Galaxy Nexus] pvkiniyan95:
no luck...same result :(
[Samsung Galaxy Nexus] MWisBest:
I figured out where I goofed in the maguro build. F2FS isn't the problem, ext4 won't make a difference. Unfortunately I'm at school and can't do much at the moment. Hopefully I can get a working build up tonight. Sorry guys!
[Samsung Galaxy Nexus] pianistaPL:
Sorry for what? :D You are amazing bro, keep going, we all are delighted with your work :)
[Samsung Galaxy Nexus] MWisBest:
New build is up, should work now!
[Samsung Galaxy Nexus] apollo07:
I'm sorry to bring bad news, but still it doesn't boot, it stays on google logo on system with ext4 and with system on f2fs
[Samsung Galaxy Nexus] MWisBest:
GRR. I dev on toro so I can't exactly test my maguro builds ... sorry about the hassle everybody.

Give this a shot. You'll have to disable signature verification when flashing, I didn't bother signing this...: http://xdaforums.com/devdb/project/dl/?id=9005
[Samsung Galaxy Nexus] apollo07:
It boots :D , thanks
[Samsung Galaxy Nexus] rjshrjndrn:
Is there any performance up gradation with this latest gpu drivers ?
[Samsung Galaxy Nexus] pvkiniyan95:
exactly..sorry for what.....u da mvp bro:highfive:
[Samsung Galaxy Nexus] pvkiniyan95:
boots now perfectly....btw just did a test of flashing this particular boot.img to liquid smooth and it didnt boot....never mind, just saying.

gr8 work buddy
[Samsung Galaxy Nexus] gautam_nexus:
I am also keen to know this...can anyone give some benchmark score comparison or something ?
[Samsung Galaxy Nexus] pvkiniyan95:
All i can say now is there is no frame drop in notification drawer at any point.:good:

benchmarks on the way
[Samsung Galaxy Nexus] sagara.sandaru:
Can you check how is the video playback and gaming performance? Thanks :)
[Samsung Galaxy Nexus] pvkiniyan95:
I usually don't trust benchmarks but...

Hoooollllly baaaaallllssss....

I think its unverified coz I keep LCD density at 280...

Video playback is gr8 and gaming is as usual, I don't play a lot of high end games for me shadow fight 2 works gr8 as usual
[Samsung Galaxy Nexus] lollipop:
can you show me the score of GPU in antutu
[Samsung Galaxy Nexus] pvkiniyan95:
Here u go
[Samsung Galaxy Nexus] h4xx0rr:
Kernel?
[Samsung Galaxy Nexus] drmxmyt:
HW video aceleration works. but on some files it still stutters. described here: http://xdaforums.com/galaxy-nexus/help/hw-video-acceleration-problem-4-3-t2403257 this issue still persist. not a big deal tho.

thanks so much [MENTION=3390093]MWisBest[/MENTION] for your hard work.

edit: this trick http://xdaforums.com/galaxy-nexus/general/how-to-to-solve-hw-video-playback-t2559138/post48229757 used to solve the issue, but would changing it to older version is a good thing or stupid since so much work have done to update our gpu drivers.
[Samsung Galaxy Nexus] pvkiniyan95:
FML kernel
[Samsung Galaxy Nexus] pianistaPL:
Wow, nice score! Are you using full f2fs with this ROM?
[Samsung Galaxy Nexus] pvkiniyan95:
Yup
[Samsung Galaxy Nexus] AbhishekS:
What exactly isn't working in the camera right now?
[Samsung Galaxy Nexus] MWisBest:
The kernel has to sorta "pair up" with non-kernel things for this to work properly, that's why I'm hoping to get everything fixed before L, then we can get all the ROMs using this and avoid any fragmentation it could otherwise cause.

What the... holy moly man. These builds are only being compiled with GCC 4.8 for the ROM and GCC 4.7 for the kernel, and you've even got more room to bump up the CPU frequency as well!

Right now I wouldn't suggest changing it to the older version, however I will certainly be experimenting with that Ducati binary! Nice find man.

That's what I'm trying to figure out. :)
[Samsung Galaxy Nexus] eternal70:
Oh god, i don't know what to said. Too many thanks to you !!!:)
[Samsung Galaxy Nexus] rjshrjndrn:
i love you man!!!
[Samsung Galaxy Nexus] imam.krismanto:
wow...
[Samsung Galaxy Nexus] MWisBest:
New build is up! There's still a few bugs to fix with the camera, currently it only takes pictures that are 4.5MP in size, any other size (including the default 5MP, and ALL sizes on the front camera unfortunately) will cause the camera to crash upon pressing the shutter button. Video recording checked out OK on all resolutions for me though.
[Samsung Galaxy Nexus] CommanderDuplex:
the new beta works pretty good I have to say!

for a not optimized kernel the entire device runs very smooth and I saw some animations that i never saw before :laugh:

Edit:

camera doesnt worked for me, I can start but when I click on the shutter... it crashed ... (4,5mpx or 5mpx are no difference)
[Samsung Galaxy Nexus] gautam_nexus:
i am about to flash the latest Beta copy..do I need to use poo's tool before flashing the beta? My System partition is EXT4 and rest is all F2FS. Thanks!
[Samsung Galaxy Nexus] MWisBest:
Try a few different camera apps, the "Camera360 Ultimate" app just worked on every resolution for me.

Nope, you don't need to use it at all. The included kernel has F2FS support, and you can have any combination of F2FS and EXT4 you want. You can even have just cache as F2FS and have data and system as EXT4 for example!
[Samsung Galaxy Nexus] gautam_nexus:
Thanks! Is the Kernel optimized like Fancy /Dirty? or is it a stock kernel with just the updated GPU binaries?
[Samsung Galaxy Nexus] MWisBest:
It's... somewhere in between stock and DirtyV. That'll change over time though, I just haven't wanted to push the envelope too much in the kernel when there's so many changes and updates happening all at once.
[Samsung Galaxy Nexus] MWisBest:
Just updated the main post: multiple camera apps in the Play Store work at all resolutions for me. Try "Camera ZOOM FX" in particular.
[Samsung Galaxy Nexus] Ziyan:
http://xdaforums.com/galaxy-nexus/devs-only/making-gpu-drivers-t2801072/post53951831 Just? :eek:
[Samsung Galaxy Nexus] pianistaPL:
Haha, that's right :) The most important is to get fully working kernel with new drivers, then bringing features from other kernels will be pretty easy I guess :)
[Samsung Galaxy Nexus] Bazzu:
I need to have a stable rom with everything working..so i'm waiting so much for a stable version! [MENTION=3390093]MWisBest[/MENTION] I BELIEVE IN YOU :D:D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
Look at this, [MENTION=3390093]MWisBest[/MENTION] [MENTION=2633638]Ziyan[/MENTION] :) http://www.xda-developers.com/android/galaxy-nexus-gets-new-life-with-updated-gpu-drivers/
[Samsung Galaxy Nexus] freshgiammi:
We pointed this out in the Hangout chat ;)

-

UI has never been so smooth on KK for me. Newer DDK are really great.

As you an see here, from a screen that MWisBest gave us, progress is near, and so is a full working camera!

https://lh3.googleusercontent.com/-...AAC1k/QBPBX_iS0Bc/w319-h567-no/2014-10-07.jpg

OMAP4XXX team ftw!
[Samsung Galaxy Nexus] pvkiniyan95:
camera zoom fx works gr8 coz for me stock camera crashes at all pic size...

btw congrats to [MENTION=3390093]MWisBest[/MENTION] and [MENTION=2633638]Ziyan[/MENTION] for making it to the xda portal news section...
[Samsung Galaxy Nexus] devil188:
Well, I've got a situation here: I can't get past the first configuration because systemui is always crashing. (Beta build)