yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Should flash it over the ROM kernel anyway. AK2 does all the same stuff as the ramdisk and poo's utility doesn't touch the kernel. :good:

I've been running 9.4.14 for the last day and a half with no freeze-ups; I think KSM is still buggy. All I did was disable it.

Making that change, adding barrier=0 to f2fs and adding a couple new tricks to Synapse right now too. :D
[Samsung Galaxy Nexus] poo706:
Not sure what you mean by that. It changes out the boot.img in the rom zip with Fancy or an alternate boot.img if the user chooses a different one.

[poo]
[Samsung Galaxy Nexus] osm0sis:
Ah sorry, didn't realize that. :)

You should consider adding a command-line argument/option to keep the original ROM boot.img for people wanting to use AK2. :good:

Your utility is definitely the best for people wanting to use ALL-F2FS or for those rogue ROMs that like to mount /data ext4 during upgrade, but otherwise, if [MENTION=3389557]hcasquet[/MENTION] wanted, he could just format /system back to ext4 and use most ROM zips normally. Unified v2 ramdisk/AK2 is a pretty well-oiled machine now. :D
[Samsung Galaxy Nexus] poo706:
Interesting idea. Ak2 is needed by people who aren't on 4.4, right? Also I was thinking a while back about changing the formatting of system to "rm -rf /system" (as I do with my unofficial LS roms) so that it wouldn't matter if system was ext4 or f2fs, but no one has been complaining, so I just kinda forgot about it.

[poo]
[Samsung Galaxy Nexus] osm0sis:
We're using AK2 for all installers right now, but yeah, it works on 4.2+, while testing I went back and booted up f2fs on CM10.1! :p

Edit: Just checked out the 9.10 SmittyV zip and [MENTION=4608636]bsmitty83[/MENTION] it looks like you're not using the latest?
[Samsung Galaxy Nexus] bsmitty83:
Not even sure . lol I thought it was

Also probably doesn't matter but I was using nobarrier , I'm sure barrier=0 is the same tho .
[Samsung Galaxy Nexus] osm0sis:
Yup they are the same. I'm going to preemptively add that sucker to the workarounds in dvbootscript though, since old init binaries hated barrier=0 with ext4 so I can't imagine them liking it on f2fs. No doubt Omni will also sh*t the bed. :p

But haha definitely not the latest zip. it doesn't have cmdline check or the SmittyV zram enabling even. :eek:

Edit: [MENTION=4608636]bsmitty83[/MENTION] Looks like I spoke too soon about disabling KSM fixing the lockups issue. I still have it disabled and just got a huge freeze typing in Hangouts, then it seemed to catch up for a second, now the screen blanked and won't turn back on. :confused:

Waited a minute and it came back. Getting you a fresh dmesg now. :D
[Samsung Galaxy Nexus] bsmitty83:
Take notes kids , that's how you report an issue [emoji651]
[Samsung Galaxy Nexus] osm0sis:
I've put it back here with my previous, also excellent bug report post. :laugh:

http://xdaforums.com/showpost.php?p=55365247&postcount=11723
[Samsung Galaxy Nexus] poo706:
Huh, somehow I missed that. I've never had a firm understanding of this whole ramdisk thing. I was under the impression that mixing and matching zimages and ramdisks on 4.4 was a bad thing. Clearly you've been working some magic.

As far as my tool and ak2, the only thing I need to pull off is the option to leave the stock boot.img intact, right?

[poo]
[Samsung Galaxy Nexus] osm0sis:
Correct sir! Thanks! :)
[Samsung Galaxy Nexus] cujo6801:
And here's your reward

Sent from the "DOG" pound
[Samsung Galaxy Nexus] hcasquet:
That would be extremely useful for me, poo. I'll gladly wait for it.

Then, i can use 8-30 UR boot.img as base and then install newer Ak2 versions on top too, as it swap zImage and do the respective modifications. :highfive:

Again, thank you all for the clarification and for the work you all pour into this. :good:

As you see, i am noobish on this kind of things, i will try to learn as i read and understand.
[Samsung Galaxy Nexus] osm0sis:
No, when he does that you'll be able to use your ROM's original boot.img like you're supposed to with AK2. :good:

Like I said, you could also just change /system back to ext4 (while leaving /data and /cache f2fs), then flash an unmodified ROM zip and then our AK2.

There's really no point in having /system as f2fs. ;)
[Samsung Galaxy Nexus] hcasquet:
Of course, i was implying that i could do that trickery too, but, anyways, flash unmodified and then Ak2 would be simplest. :p

I will try next time i update CM11 on the Gnex, keeping the /system partition on ext4. I have noticed that f2fs takes a lot more of space. :eek:
[Samsung Galaxy Nexus] 7175:
Thanks this completely fixed the TWRP black screen issue. :)

Testing 9-10 Dirty V now. The only issue I had with 9-4 was intermittant hiccups. None so far an hour in on 9-10. I'll do some Andy compiling and see how she purrs.
[Samsung Galaxy Nexus] poo706:
The next couple of days are going to be pretty hectic for me, but I'll see what I can do within the next week. I just took the reigns as the official LS maintainer for the 3 gnex variants, so I've got some work to do in that department as well.

[poo]
[Samsung Galaxy Nexus] mrgnex:
Awesome! Take your time. No hurry :) Your life is more important than XDA. Also maybe add a disclaimer that the ROM won't boot if the boot.img isnt touched so there is no confusion about the option and you don't get angry people claiming you blew up their phone ;)
[Samsung Galaxy Nexus] poo706:
Hasn't happened yet, that thread has been quiet for a while now. I was wondering if anyone even still used it.

[poo]
[Samsung Galaxy Nexus] mrgnex:
I do when I update my ROM :) Its awesome and have saved me a lot of time ;)
[Samsung Galaxy Nexus] bsmitty83:
Its useful for full f2fs of course . and while [MENTION=4544860]osm0sis[/MENTION] thinks its useless to convert system to f2fs , I think its faster . I'm on data & cache f2fs and I can tell the system is still ext4
[Samsung Galaxy Nexus] osm0sis:
Ah interesting to know! I was just going on the theory of it all. Anyway, I like my Stock PA GApps, so I can't really spare the 100mb overhead to /system that f2fs causes. ;)

I had an idea for a solution to this awhile back by custom formatting /system to reduce the gc area, care to try that out? /system should have few if any writes, so it shouldn't need the overhead like a cache or data partition does.
[Samsung Galaxy Nexus] Nephilim:
I was just going to suggest this same thing. :p
[Samsung Galaxy Nexus] pianistaPL:
Still the same... :/
[Samsung Galaxy Nexus] GilGameshn1:
Wish to help

Hi ... I wish to help ... if you on roms like CM11 ... u must go to settings/Performance submenu and tick all the "set on boot" options to allow anything to set on boot ... It will stick then ...
[Samsung Galaxy Nexus] pianistaPL:
Uh... I solved my problem ;P I set min CPU clock to 230 MHz (I fortgotten that i had 350) and then min screen stick on 230MHz too.
[Samsung Galaxy Nexus] pvkiniyan95:
just a suggestion

guys if u r using omni or cm11 etc etc with built in performance option try not to use trickster..

my experience was so bad that phone suddenly became unstable and art was horrible, the moment i erased trickster and rebooted everything was fine, seems a contradiction...

btw i m not complaining trickster coz its a gr8 app and i've been its loyal user, just sharing my experience... ;)
[Samsung Galaxy Nexus] TheMan0790:
Oh. I saw Linaro(V3) so figured we were going by that naming. My bad...

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] bsmitty83:
You can go by what "v#" it is , that's how I'm keeping track of what is what
[Samsung Galaxy Nexus] Nephilim:
Almost all roms have a built in performance setting. If you use trickster then the built in just sets it the same as what you select in trickstermod by default so there should not be issues regarding this as long as you leave the built in performance setting alone.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
damn [MENTION=4608636]bsmitty83[/MENTION] , your really being put on the grind dude. *cough cough "day off for smitty ;) " cough cough*
[Samsung Galaxy Nexus] Nephilim:
Hey guys, posted this over on the G+ Community, figure I'll drop it here too just in case it may help some of the newer users.

I've noticed alot of people coming from other kernels complaining about DirtyV causing lockups, freezes and other odd issues even on the new DirtyV builds that are virtually perfect. I would just like to remind you that since DirtyV is in anykernel format it utilizes the roms stock kernel ramdisk. This basically means that if you are using another custom kernel on your current rom you must reflash the rom over itself in order to regain the proper stock kernel ramdisk before flashing DirtyV or any other kernel that is in anykernel format. If you do not then alot of the issues some of you are encountering may be simply caused by DirtyV trying to run properly off of a custom kernels ramdisk.

This does not mean that it won't work right but it's really not meant to use a custom kernels ramdisk because every custom kernel has a different setup and some ramdisk may completely **** up your experience by conflicting with DirtyV (or any other anykernel type kernel).
[Samsung Galaxy Nexus] pattyboi:):
hmm,wouldnt this explain why dirtyv dosent play nice with vanir? considering vanir uses its own kernel and prob is own ramdisk.
[Samsung Galaxy Nexus] Nephilim:
Doubtful since the core of this kernel is based on Vanir kernel hence "DirtyV". (at least I believe it was in the beginning) ;)

Also, I believe regardless of what rom you are on and if it has a custom built kernel for it, that is still the stock kernel for that rom so it's ramdisk should always play nice. The post I made was more-so in reference to using a custom kernel that does not come with the rom.
[Samsung Galaxy Nexus] pattyboi:):
EDIT: talking out of stupidity,my bad. :P
[Samsung Galaxy Nexus] flip360:
Dunno what Vanir Team did to their kernel but must say that it is really a hard choice between theirs and DirtyV :)

Anyway great thread and lots of familliar faces, thanks bsmitty, AK and everyone involved
[Samsung Galaxy Nexus] Blackcrx:
Your earlier releases with 180mhz ran fine for me. No issues at all.

My backup kernel which I'm using now is the modified SR5 made by [MENTION=4328678]metalspring[/MENTION]

I'm running 180-1200. Deadline. Interactive. Undervolted. No issues at all.

Waiting for your next release.
[Samsung Galaxy Nexus] Nephilim:
180mhz is just something he doesn't have in his "Smitty" test builds. I asked about this a few pages back and he said that it'll be there when he releases the next official DirtyV update along with modifiable smart-reflex and dynamic fsync. ;)

Trust me, it's the only reason I didn't try out his Smitty test build, my custom settings require the above 3 items lol.
[Samsung Galaxy Nexus] bsmitty83:
They'll all be back for the normal builds , that's just my config I got rid of stuff I don't personally use
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] try the cpufreq boost patches I posted here http://xdaforums.com/showthread.php?p=49842495
[Samsung Galaxy Nexus] scarcry:
Same for me. I tried Smitty test build but it lagged and was less smooth than his current SR Linaro build for me so I switched back.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] standa75:
I tried clearing trickster data, as well as dirty bflashed test kernel immediately after vanirs Rom, but still wake up problems occurs. I also noticed that sometimes cpu frequency is at 350mhz, but processor has 0% activity.(both min frequencies set to 230mhz).

Odesláno z mého Galaxy Nexus pomocí Tapatalk
[Samsung Galaxy Nexus] gautam_nexus:
I am on all f2fs using poo tool to convert pa r to f2fs. How can I use ext4 system and rest all f2fs? Shall I just use the recovery to just format system to ext4? And what ROM shall j use? Can I use the pa stock rom or do I need to convert using poo tool?
[Samsung Galaxy Nexus] poo706:
As long as the ROM doesn't mount /data as EXT4 and you be sure to install an F2FS-compatible kernel after installing the ROM, you wouldn't need my tool at all. I know SlimKat mounts /data, and I'm pretty sure I encountered AOKP (an unofficial if I remember correctly) that does too. Most don't.

[poo]
[Samsung Galaxy Nexus] Nephilim:
Well it looks like I'm not one of the cool kids anymore, Smitty didn't even give my last question a response. :(

Looks like my issue with micro-freezing and hot reboots while on the charger is only happening on the any-kernel versions of SmittyV, I tried 9-10 and 9-4 and both give me the exact same problems, jumped back and tried out 8-30 and it's been running with not a single issue for over a day now. Sucks because 9-10 was noticeably faster and smoother.
[Samsung Galaxy Nexus] gautam_nexus:
What about PA? Thanks!

So if it doesn't than I just convert my system partition to ext4 in recovery and dirty flash the ROM, gapps and an f2fs kernel. Will that be okay?
[Samsung Galaxy Nexus] poo706:
Send me a link to the PA you want to install. Regarding your second question, sounds correct to me. Might want to reboot back in to recovery after converting /system back to ext4 prior to installing everything, just to be on the safe side.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
No whining allowed lol .

I was gonna try to get an update out before I responded

Next version should be better, just need some time to finish it

Sounds like your ramdisk isn't playing nice with anykernel2 , you still on LS?
[Samsung Galaxy Nexus] Nephilim:
Yep, still on LS but the first thing I always do is flash SmittyV upon installation. I've been on SmittyV 8-15 up until I tried the new ones yesterday.

If I may ask, why switch to AK anyway? I understand some people may like using DirtyV/SmittyV on older roms but why couldn't you just stick with Unified Ramdisk which works for everyone and then once in awhile just make an AK version of it for those that ask?
[Samsung Galaxy Nexus] osm0sis:
Try the ramdisk version on my Dev-Host, Neph.

It still has occasional freezes, so I think it's just the kernel, not the package change.
[Samsung Galaxy Nexus] Nephilim:
Thanks for the tip, if it still has freezes I'll probably just stick with 8-30 for now and then when Smitty releases the next update if I have problems with any kernel format still I'll wait and try out your next ramdisk version. :D
[Samsung Galaxy Nexus] KreNtal:
A Little OP:

Have you heard about the drop of gnex from cm? Will you continue to support this kernel [MENTION=4608636]bsmitty83[/MENTION]??
[Samsung Galaxy Nexus] bsmitty83:
https://plus.google.com/102133860717725543411/posts/jAfCGp9ZHXH

Lol

They dropped toro and toro+ . I honestly don't follow cm anymore . the gnex will definitly survive .
[Samsung Galaxy Nexus] nu_skool:
Bit of a n00b question here so apologies in advance...

If I install Nephilim's script (into /system/etc/init.d) and then unroot will it continue to run at startup? A couple of apps I use don't play nicely with root so I can't have it permanently installed :(

Thanks in advance
[Samsung Galaxy Nexus] Punkiderma:
Same for me on slimkat, I waited a little before posting but now I'm pretty sure.

9-4 and 9-10 gives micro stutters, systemui force closes and also sometimes my screen won't turn on,but the phone receive continues to receive notifications XD
[Samsung Galaxy Nexus] marko207:
Strange thing happend with 8-30, I wanted to reboot my phone and ended in boot loop. Phone was on a charger, fast charge enabled. Except this minor error, everything was ok. No FC, slowdowns etc.

So, I'm back on 8-15...
[Samsung Galaxy Nexus] bsmitty83:
I'm still working on the next version . been trying to update some mm / oom_killer from 3.4 , plus with the next versions of the Dirtys , I'm going to turn off frontswap , zbud , and zswap , they will be on in my personal setup because it needs work and I am going to continue working it on SmittyV and if/when its ready I'll enable it back on the Dirtys .

Also I'll switch back to releases with a ramdisk , and I'll make a multi-V anykernel2 available for those still running >4.4 android

Sorry for the delay , its slow going backporting mm stuff . lol
[Samsung Galaxy Nexus] Nephilim:
Thank you man, couldn't have asked for more perfect response info.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
OP Updated :

All 3 versions

I used AnyKernel2 Installer still due to not being able to get a ramdisk booting lol ( im still working on it )

DirtyV and DirtyV-SR have frontswap , zbud , zcache disabled for smoother performance , zram is available but off by default

added csnappy compression to crypto , some mm commits from 3.4

enjoy , ill try to get a ramdisk build out soon
[Samsung Galaxy Nexus] GilGameshn1:
Thanks for the effort .
[Samsung Galaxy Nexus] Nephilim:
Thanks man, I'll stick with 8-30 for now. Can't wait to try the next SmittyV! :D

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] D1BB:
Thanks! Giving SR version a try.

Edit: touch control no longer works with latest build, "cant load module"
[Samsung Galaxy Nexus] KreNtal:
Can someone report if there are fc, freezes with this latest version? Ty
[Samsung Galaxy Nexus] bsmitty83:
Both dirtyV's should be good , SmittyV with zram on is still a wip , I'm getting a few pauses under certain situations .

But zram with the dirtys should be OK as well as I'm not using frontswap or zcache on them , only smittyV . but IMO dirtyV-SR doesn't need zram really .

SmittyV will be more experimental as I work on some things .
[Samsung Galaxy Nexus] josera06:
Why compatibility with TC has gone?

Enviado desde mi Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Honestly idk , probably because bponury scrapped pgm and its not even available on the Google play store anymore ?

Its a module that he compiles and its closed source so I have no idea what changes I made broke it . sorry . sucks but theres not much I can do about it
[Samsung Galaxy Nexus] KreNtal:
So I'm installing it right now, will report my experience later today.
[Samsung Galaxy Nexus] josera06:
TC still works on the new buid of fancy kernel....

Enviado desde mi Galaxy Nexus
[Samsung Galaxy Nexus] Punkiderma:
For me, 9-14 still has stutters and freeze with screen off (not SOD, since I can see the phone pushing notifications to my PC via pushbullet, but I can't turn the screen on XD)

Back to 8-30
[Samsung Galaxy Nexus] bsmitty83:
Which version ?

Sometimes things can be fixed by cleaning out cache in recovery . but if your on smittyV , there's definitely instability with zram on .
[Samsung Galaxy Nexus] bsmitty83:
Fancy is also a different kernel . [emoji19]

A module needs to be made for each specific kernel . that's why it still works on boype's , but not mine . as I said , idk what caused it and I can't compile a pgm .ko myself so ......
[Samsung Galaxy Nexus] poo706:
I wasn't able to get TC to work on Fancy with the last TC app before it was removed from the Play Store (2.2.1, IIRC). But when I rolled back to an older version of the TC app (1.8.5), the CM11 module worked just fine.

[poo]
[Samsung Galaxy Nexus] KreNtal:
Try to long press the power button when it happens, it works for me.

Instead this version (dirtyV SR) is working fine for me, no more force closes or freezes, thank you [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] dbt816:
No freezes, lags or anything for me on 9-14 SmittyV! It has run perfectly all day... :good:
[Samsung Galaxy Nexus] Jar3112:
I had a freeze with dirty v 9-14, while typing on whatsapp. Didn't manage to take a logcat since I had to pull out the battery..

Sent from my Galaxy Nexus

---------- Post added at 11:11 PM ---------- Previous post was at 11:07 PM ----------

May have been whatsapp though

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Punkiderma:
SR, flashed rom's original boot.img and cleaned dalvik & cache after flash
[Samsung Galaxy Nexus] osm0sis:
Yes. init.d is run by the system during boot, so you don't need to be rooted for it to work. I'd recommend you still keep busybox installed though.

Always seemed to be in Hangouts or Chrome with Google Keyboard for me. Must be some memory hungry app thing.

Switching to 9.14 in a few and trying to figure out the issue keeping Smitty from building a working ramdisk. :good:
[Samsung Galaxy Nexus] Jar3112:
I was using SwiftKey.. Would changing the minfrees help in your opinion?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
It wasn't a problem previously and they haven't changed, but you could see if playing with them works around it.
[Samsung Galaxy Nexus] osm0sis:
Ramdisk boots for me with the one I had bundled with 9.10 on my Dev-Host.

http://v.ht/osmod
[Samsung Galaxy Nexus] poo706:
Those who use my F2FS converter, I updated the Windows and Linux/Mac versions to support AnyKernel and EXT4-formatted /system. Android update coming soon. http://xdaforums.com/showpost.php?p=55451770&postcount=309

[poo]
[Samsung Galaxy Nexus] Nephilim:
If it's not too much trouble would you mind making a SmittyV 9-14 UR? :angel:
[Samsung Galaxy Nexus] osm0sis:
Smitty said it's unstable. :p
[Samsung Galaxy Nexus] Unzitron:
9/14 dirtyv broke my YouTube on Dirtyunicorn and OmniRom.

update: [MENTION=4608636]bsmitty83[/MENTION]

Installed the newest OmniRom nightly without DirtyV and Youtube works fine. What could cause Youtube to FC and give video loading errors?
[Samsung Galaxy Nexus] bsmitty83:
Not sure , I just watched a video on YouTube after I read this .
[Samsung Galaxy Nexus] cmoG530:
I can confirm that YouTube is also working for me on Vanir.
[Samsung Galaxy Nexus] cujo6801:
And on poo's LS

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Unzitron:
Maybe its a setting I had.

Update: Yup. It was some setting. I'll have to narrow down what I did.
[Samsung Galaxy Nexus] motorazrv3:
Touch control is Working with latest dirtyv. Using TC 1.8.5.
[Samsung Galaxy Nexus] D1BB:
Must have something to do with the version of tc we're running, I'm on 2.2.1, and it doesn't work with dirty 9/14. I can use it fine with 9/10 and previous.
[Samsung Galaxy Nexus] gautam_nexus:
I am talking about this ROM http://xdaforums.com/galaxy-nexus/development/rom-paranoidandroid-4-4-t1619582

Sorry for the late reply!
[Samsung Galaxy Nexus] markop90:
The phone become super fast with this kernel... But tonight I had another sod when the phone was on charge and I had a notification (led was blinking).

Now I tried to completely disable led notifications, I've already disable those that show phone charging status, because when I tried to reboot the phone, it bootlooped on bootloader screen.

This kernel doesn't like the led :D
[Samsung Galaxy Nexus] Jar3112:
The bootloop is a known issue. Simply turn it off and on again.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
Had another freeze, followed by another one (longer). Hope this helps!

https://www.dropbox.com/s/v3u6sw9jtvsxln4/log1 (1).txt?dl=0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
All clear, data is not being mounted.

[poo]
[Samsung Galaxy Nexus] gautam_nexus:
So this is what i am about to do:

1. Change System Partition to EXT4

2. Restart Recovery

3. Flash latest PA build ( not converting anything using your tool)

5. Flash supported Kernel

6. Reboot System.

I have one more doubt: I am not sure why your tool is needed now? and what changes you have made to your tool to support Mix file system.
[Samsung Galaxy Nexus] markop90:
I know, I said that I believe the issue is caused by the led not being reset correctly.

However on the last build I had another SOD (with default kernel settings), reflashed stock kernel waiting for the issue being fixed
[Samsung Galaxy Nexus] Jar3112:
Just a supposition, but could it be possible that the freezes are due to a low (or high) value of the maximum heap size of the applications?

Sent from my Galaxy Nexus