yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Yes at one point while I was building vanir to make a recovery I did add all the ROM side f2fs support . including this . but AFAIK [MENTION=2838735]aosp[/MENTION] used just straight up commotio for testing . mind you this was simply a test build to get f2fs to work . the ROMs still need the support added . most ROMs are going to have support soon since cm is adding everything . but ill try to work on a ROM . I'm kinda stuck till I have a working device .

Hack The Tuna
[Samsung Galaxy Nexus] DR3W5K1:
Im getting the shakes guys. "I got these cheeseburgers man"

I need a fix. Can't try f2fs yet no PC until this weekend. So until then I guess I'm screwed.
[Samsung Galaxy Nexus] michierusama:
I saw an app on play store to convert roms to have f2fs support.

https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs

I emailed to see if its possible to add galaxy nexus. I did not try to use it. So I don't know if it works or not.
[Samsung Galaxy Nexus] DR3W5K1:
Sorry about your phone buddy. It's easy to replace the USB port if you can get one.
[Samsung Galaxy Nexus] michierusama:
I bought one some time ago exactly those and did not work ew....
[Samsung Galaxy Nexus] Gabboplano:
There is not a "best setting", you have to try everything by yourself
[Samsung Galaxy Nexus] abhishek93:
I am using wpa2-psk..

And one more thing on default vanir kernel i am able to connect to wifi but not on this kernel..
[Samsung Galaxy Nexus] bsmitty83:
My WiFi works , I'm not saying yours does , but its something else , some setting that's not working etc...
[Samsung Galaxy Nexus] abhishek93:
I'll give it another try...

I guess my wifi must be misbehaving...

Edit - sorry..it's working now.. it was my wifi..

Finally i can use your kernel :)
[Samsung Galaxy Nexus] NeverSeparate:
Mine worked also. Thats why I asked about the encryption. But this kernel apparently doesn't have the drivers that break wep anyway.
[Samsung Galaxy Nexus] ruben46_:
Let´s give a try. Thanks for your work
[Samsung Galaxy Nexus] kuronosan:
I had some SODs, which mostly happen when the screen is off and I get a push notification. The kernel works great otherwise.
[Samsung Galaxy Nexus] bsmitty83:
Try raising your min screen off freq
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

How high you think the GNeX PowerVR SGX 540 can clock and run smoothly at?

PVR Monitor system profiler - http://goo.gl/d6Z46y

GPU benchmark 3D - http://goo.gl/BVd3sp
[Samsung Galaxy Nexus] bsmitty83:
Idk but I'm gonna find out soon :eek:
[Samsung Galaxy Nexus] bsmitty83:
Got a couple new builds up , links in the op , old version can be found through my SIG .

SuperRam on the left , dirtyv reg on right lol

The sr version is only a few superram commits so far . I still need to do more to get more than 761 MB of ram

Enjoy :beer:
[Samsung Galaxy Nexus] Nephilim:
Is the new SR version the update for the Dirty-Kang-SR-v1 that I was beta testing?
[Samsung Galaxy Nexus] bsmitty83:
No it started from the same point but I created a new branch .
[Samsung Galaxy Nexus] Nephilim:
Gotcha.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] link for 3.4 WiFi drivers I dont tether or use useless wep but love free hotspots edition?
[Samsung Galaxy Nexus] bsmitty83:
Lol , yea I'll hook you up , lemme do a couple things and I'll build a copy
[Samsung Galaxy Nexus] Nephilim:
If you are using WEP for a secure internet connection you would be better off just leaving your connection open. I would suggest just doing what AK did back in the day on his kernel, use the 3.4 drivers but create a revert zip for those that need it and add it to the OP. :) :good:
[Samsung Galaxy Nexus] aosp:
Simple fix for tethering ;)

Fix and Clean for Wifi 3.4 · 0b66554 · anarkia1976/AK-ramdisk · GitHub - http://goo.gl/Z7QTos
[Samsung Galaxy Nexus] poo706:
Both the superram and v2 versions make my toroplus not wake up until I've pressed the volume or power buttons 3-5 times. Never had this problem with the first 4.8 kernel.

[poo]
[Samsung Galaxy Nexus] pattyboi:):
for me as well on my toro with latest vanir.
[Samsung Galaxy Nexus] metalspring:
Hmm, I'd say my linaro omni builds are pretty smooth as well, but I might be a little biased on it ;) lol

(made with linaro 4.8, full -O3 optimization, plus some extra toolchain optimization as well, plus a couple little things to make it as smooth as possible)
[Samsung Galaxy Nexus] Nephilim:
Yes, I've heard nothing but good about your Omnimetal from all that has used it!!!! :good:

BTW, I dig the color settings you showed me. Very natural, I prefer a little more "pop" so that's why you see mine are a little higher on the calibration lol, but yours are quite excellent!
[Samsung Galaxy Nexus] fracama87:
Anybody knows the meaning of each voltage? Call me paranoic but before try the [MENTION=2853378]Nephilim[/MENTION] uv settings I want to know what I'm touching... Study engineering made me think to much :D

Last 3 are pretty obvious...
[Samsung Galaxy Nexus] Kaemo:
Your ROM is the only ROM I've seen where the transition between Notifications and Quick Settings doesn't lag. I don't know how you did it, but I love it. However...

You might think it's stupid, but there are only two reasons why I don't use your ROM.

1: GEL always reverts to a 6x4 grid when you reboot. I can change it back, but I reboot my phone a lot.

2. The Notification Drawer header is gray instead of black, like in stock.

I'm really OCD about this kind of stuff XD
[Samsung Galaxy Nexus] Nephilim:
Okay, I gotta say, DirtyV_SR2_Linaro + LiquidSmooth_1/25 + ART + Neph_Custom_Settings = The Smoothest Experience I have had on my Gnex ever!
[Samsung Galaxy Nexus] irland2bite:
Mr. [MENTION=4608636]bsmitty83[/MENTION], have you ever think woman might not be using Dirty V ? I think you can start or build new one and name it Clean V or Healthy V..Just saying..Anyway, this kernel is awesome ! :thumbup:
[Samsung Galaxy Nexus] Nephilim:
hahahaha, you're f*cking ridiculous man!
[Samsung Galaxy Nexus] irland2bite:
And [MENTION=2853378]Nephilim[/MENTION], I saved your personal setting on Keep n name it Neph with Dirty V, my wife saw it n say "I dont wanna get AIDS cause of this f**king Neph"
[Samsung Galaxy Nexus] fracama87:
found some interesting info

http://xdaforums.com/showthread.php?t=2115590&page=532#5315

So vaux_3 on gms should be higher 2800-2900 for be safe... but need test...

[MENTION=2853378]Nephilim[/MENTION]

if somebody as a problem with your values these could be useful to find which one is too low :)

you could put also in op of your thread, so people can understand better what is doing.

I'm going to bed it's really late here...
[Samsung Galaxy Nexus] clnzx2:
Same here except my own settings...performance is silly. Will need some more time to judge battery but so far it looks good
[Samsung Galaxy Nexus] swarlesbarkely:
Is art working with the update? The last one I tried (1/24 or so?) didn't play nice at all
[Samsung Galaxy Nexus] wavedashdoc:
I was always wondering about the Vaux3 was. I am on the verizon Galaxy nexus. I'll try the 2500 vs 2800 suggestion.
[Samsung Galaxy Nexus] Vekhez:
See you think I don't know these things :P
[Samsung Galaxy Nexus] Nephilim:
lol. :p
[Samsung Galaxy Nexus] lazydognet:
I've been using Vanir with mpokang and have been pretty happy with both the performance and battery life.

I just installed Dirty_V on my gnex. The benchmark scores are less than with mpokang (and yes I realize those marks don't always mean your gnex is running smooth and lag free, but it usually is a general indicator for me).

I'll have to see how the battery life is tomorrow.

Thanks to the dev for the kernel.

LDN
[Samsung Galaxy Nexus] metalspring:
Benchmarks will be hard pressed to match mpokang unless the mysterious "50% increase ram performance" code that mpokang has is figured out :(
[Samsung Galaxy Nexus] Nephilim:
Sometimes I feel like Mpokwths just lurks these threads without logging in and snickers at all of us with a sinister grin.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
I did send him a message for when/if he ever logs back in asking if he could at least give some kind of clue what he did to improve ram speed

Even without the specific commits, if we had some idea what he did I'm sure AK or bsmitty could figure out how to add it in

[MENTION=2838735]aosp[/MENTION], do you have any thoughts on what it might be since you seem to be the walking encyclopedia of kernel commits?
[Samsung Galaxy Nexus] lazydognet:
LOL..... That did make me laugh!
[Samsung Galaxy Nexus] wavedashdoc:
Honestly I went back to mopkang SR. Did a clean flash of the latest cm. Installed DirtyV2 first tested it, lag with keyboard and animations not as smooth. Then installed Mopkang and all lag gone, animations couldn't be smoother.

I have a question why are the clocks set differently on Dirty? (Ex 350 vs 384, 1228 vs 1200) Why not use the factory clocks of the phone, Mopkang and Franco? I would really like to know.

Again props to everyone who is contributing once more to this great phone.

Also I was think Neph, maybe we should get you a VZW nexus, since there seems to be some difference in hardware.
[Samsung Galaxy Nexus] osm0sis:
It is. My Synapsed version is like an interim preview build with ramdisk fixes and Synapse improvements above and beyond what's in the last official nightly. :good:

Yup, it's in there. Busybox added it in 1.22.0 and most ROMs are using 1.22.1 now, the problem is that they all use a dynamically linked compile against bionic, and we need a statically linked version like Stericson's included in the ramdisk to be able to run it before system has been mounted during the boot.

Problem with Stericson's 1.22.1 is he forgot to enable blkid's fstype displaying option in the Busybox build config. Like I said, I emailed him to request it but if one of you could provide a static Busybox build with that enabled I could have this thing done today. :)
[Samsung Galaxy Nexus] bsmitty83:
I'll try to find some time to do this . I'm thinking it will be easier just to cc the busybox source outside the ROM , I think all you need to do to make it static linked is change the LD flags to -static

I got it building with the ROM (vanir) so hopefully it'll be what you need . it will also include the f2fs tools in the ROM as well . when its done I'll shoot you a link

Hack The Tuna
[Samsung Galaxy Nexus] Sik-1:
im searching the thread for the philz recovery, but cant seem to find any, are the ones on his page updated to the f2fs, because the dates on the latest he has doesnt match up
[Samsung Galaxy Nexus] bsmitty83:
Check the op [emoji106]

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Awesome! As long as it's 1.22.1, static, and has blkid fstype display enabled in the build config (all the ROM ones seem to) it'll work! :)

Hopefully it'll be about 1mb like Stericson's. If all else fails I just found a 1.8mb one in Tasssadar's MultiROM zip which should also work (but is huge, and slow). :good:
[Samsung Galaxy Nexus] metalspring:
Looks like cm is paying attention to tuna again lol-

http://review.cyanogenmod.org/#/q/s...ndroid_kernel_samsung_tuna+branch:cm-11.0,n,z
[Samsung Galaxy Nexus] Shadow Death:
Is that supposed to be compatible with the Toro? I tried it and it refused to mount any of the mount points including the sdcard.
[Samsung Galaxy Nexus] bsmitty83:
I think I screwed up the ext4 part .it'll format to f2fs ok , but don't read ext . I'll fix it soon for now use twrp if you need to see ext .

Hack The Tuna
[Samsung Galaxy Nexus] Shadow Death:
Cool, I thought maybe I screwed up somewhere and just couldn't figure out what I did. lol
[Samsung Galaxy Nexus] milojoseph:
congrats on your 1000 post thread man.... I told you i will be around lurking in this dirty thread... I still my nexus and flashed 6/4 awesome... soon put it on ebay....... you guys are good developers all of you... :D

---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------

lml on tapatalk for some odd reason said 1000 so im early so what lmfao
[Samsung Galaxy Nexus] AbhishekS:
This is the first post of the 1000th page! Wooohooo!!

Long live Dirty_V. :D
[Samsung Galaxy Nexus] DR3W5K1:
Someone will get banned eventually and I will have the first post. Mwahahhh
[Samsung Galaxy Nexus] paarthdesai:
no need to request f2fs conversion of your rom anymore

i found an app which does that in a matter of seconds :D :)

you're welcome :D

https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs

requested the dev to add support ..he will be doing it pretty soon
[Samsung Galaxy Nexus] dezful:
No maguro if I'm not mistaken, eh?

Sent from my Galaxy Nexus using Electricity
[Samsung Galaxy Nexus] pianistaPL:
Yes, but support is coming.

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] thoiloidainhan:
Gotta be on the 1000th page!!! Dirty v still works with 4.4.3??? If it doesn't, 4.4.3 can wait. Amazing what u devs can do with this dated phone. Ive got a nexus 7 (2012) with far more superior HW yet the performance is no where near my nexus. Gaming is laggy and it gets so hot charging and playing simultaneously. None of these is a problem with the gnex with dirty v and vanir. Thanks so much
[Samsung Galaxy Nexus] pirigu:
hello could you give me the zip of the kernel you have? do not find in op ... thanks in advance
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION] , didn't forget about ya , my build failed at some point last night with an internal GCC error . gonna try to sort it out . the only busybox pkg I could find it compiled was a 1.5mb labeled "busybox.a" . I don't think it ever finished

Hack The Tuna
[Samsung Galaxy Nexus] bsmitty83:
I still haven't been able to test anything without a device , so im getting anxious because there is so much still to do . hopefully that board gets here soon

Hack The Tuna
[Samsung Galaxy Nexus] bsmitty83:
I'll give post #10000 to my son ......[emoji39]

Hack The Tuna
[Samsung Galaxy Nexus] chongns:
that kernel is from metalspring test zip for f2fs, for normal rom, you can get the smitty 04/06 in the OP
[Samsung Galaxy Nexus] pirigu:
perfect thank you very much! coated onto the drain and install :)
[Samsung Galaxy Nexus] dbh369:
I finally got around to benchmarking, and I'm getting 2.9 write on Zen 512, any idea why?

sent from my Dirty-Vanir GNex rocking f2fs.
[Samsung Galaxy Nexus] paarthdesai:
9 mbps write and 30mbps read for me ondemand plus and noop at 512
[Samsung Galaxy Nexus] chongns:
i not sure why, but now this is my config and result

ROM: FML 4.4.3

Kernel: Smitty V (metalspring f2fs test build)

Triskster mod: follow Nephiline setting, but CPU max 1.2Ghz

additional setting:

vm.dirty_ratio - 30

vm.swappiness - 10

vm.vfs_cache_pressure - 40

result

Read: 27.66MB/s Write: 21.88MB/s
[Samsung Galaxy Nexus] lostman.it:
Commotio B66 + Vanir + F2FS = WOW! :D
[Samsung Galaxy Nexus] xxSAKISxx:
[MENTION=4608636]bsmitty83[/MENTION] i want to ask you a question. I am completely noob as about development but as i understand f2fs change the filesystem of our nexus so the noob question is you think in the future we be able to use f2fs in our nexus without need to use adb so we can flash a rom after change file system? in my noob mind now this seems impossible since when we change the file system we wipe nexus completely including internal storage. Thx for your hard work and from my side gratz for your new family member.
[Samsung Galaxy Nexus] bsmitty83:
Well the only other way I guess it could be done without adb would be to use the system partition to store a ROM zip , then format data and cache , then move the ROM zip to data partition and then wipe system . the only reason for adb is to push a ROM to the data partition that's clean . on a phone with both internal storage and an sdcard , its done by moving everything to the sdcard .

Its a good question , I'm really not sure of it can be done , but the process is quite simple as is , although I understand as some people don't have PC access .

Hack The Tuna
[Samsung Galaxy Nexus] Reinvented:
What a freakin' stud!

I can't wait until he is old enough to realize his dad is a hero in this communities eyes :)
[Samsung Galaxy Nexus] chongns:
As current way by CWM and TWRP,it wide data without wide media. i believe this will very soon for F2fs also.

As for the first time convert from ext4 to f2fs, we need to clean format the partition is unavoidable, but this step can be done by updater script.

when those script or code are complete, you can just flash the f2fs rom as normal as now for the ext4 rom.

this is very similar for my old phone of galaxy sl when we change the file system to ext4.
[Samsung Galaxy Nexus] osm0sis:
When recoveries "format" without wiping /data/media they're really just deleting (rm -rf). Not formatting. To change filesystem type you must format, so a complete wipe of /data will always be necessary for the initial conversion.

Damn! The 1.8mb build from MultiROM works but it's terribly slow to boot, I think because it's such a fat cow. :p
[Samsung Galaxy Nexus] chongns:
yes, you are right. tat mean, to who which is first time convert the partition, need to be back up the internal sd, cause Nexus have no such big partition to hold the backup of the /data/media when formatting. but it still able to hold the rom zip file and gapp flash zip.
[Samsung Galaxy Nexus] osm0sis:
Not sure I follow you here, but the only good mobile option (ie. no ADB) would be to backup /data/media to a decent size USB drive via OTG, that way you could save the entire ~11gb max sdcard to move back later.

If all you care about are the ROM and GApps zips, formatting /cache or /system first and moving them there like Smitty suggested should be fine. Just use AROMA Filemanager (also moved to cache post-format) and you can do it all while in recovery.
[Samsung Galaxy Nexus] GilGameshn1:
Yes it is ... [emoji106]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Unfortunately, maybe any busybox compiled with static links will be about that big?

Also [MENTION=4608636]bsmitty83[/MENTION] how did you try to compile the busybox? I mean did you try building an entire rom or just the busybox?

I think you can try compiling only busybox by running . build/envsetup.sh then cd'ing to the busybox directory and running mmma (Builds all of the modules in the supplied directories, and their dependencies.) not sure how to add the static link variable though unless you add it to the busybox makefile? Also, I personally have never used mmma so I'm not exactly sure how it works, but I'm going to give it a shot and see :P
[Samsung Galaxy Nexus] bsmitty83:
I tried just compiling busybox by the instructions on the busybox website , just like a kernel , but it didn't work , I never tried like you said . but I'm using purityrom kk busybox , and from what I can tell its built static by default

Hack The Tuna
[Samsung Galaxy Nexus] sagara.sandaru:
I think those results are depend on how much free space you have. After I flashed the f2fs rom I got around 20MB/s of write speed but after I copied my previous backups and other data I got around 10MB/s. I went back to ext4 after testing f2fs for few days and after installing the ext4 rom I got 19MB/s of write speed. Reading speed was nearly same on both f2fs and ext4
[Samsung Galaxy Nexus] frickinjerms:
[MENTION=4328678]metalspring[/MENTION] I was able to get your 5/23 omnimetal to boot with f2fs using the 6/4 dirty-v-f2fs boot img in the OP by putting it directly in your zip and adding some changes to the updater-script that were posted in the cm-remix thread :D AFAIK that worked possibly?
[Samsung Galaxy Nexus] metalspring:
Hmm, looks to be about the same way using mma works in the external/busybox directory

(mma actually seems more appropriate than mmma), my build failed almost instantly since the toolchain wasnt set, but then again I did try to build without lunching for a specific device hoping it would make a busybox that osm0sis could use on any device

Edit: so far it seems like this is working

. build/envsetup.sh

lunch vanir_maguro-userdebug

cd ./external/busybox

add -static to the LDFLAGS in /external/busybox makefile

mma

Will have to wait and see if it finishes though, if it works and is actually statically linked
[Samsung Galaxy Nexus] osm0sis:
Stericson's is 1mb on the nose and would work but he forgot to enable the fstype display in blkid. :)

If it is static by default then I could just use it as-is.. I'll hunt it down. :good:
[Samsung Galaxy Nexus] metalspring:
Hmm, idk, its probably missing this though, so it might not detect f2fs-

http://vaniraosp.goo.im/#/c/11784/
[Samsung Galaxy Nexus] osm0sis:
If it's v1.22.1, that commit was added to official busybox sources in v1.22.0 so it'll be there. :)

Hopeful! :D
[Samsung Galaxy Nexus] bsmitty83:
It should be I think I checked the history and it had the right commits . I've been doing a million things at once tho so I'm not that reliable lol

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Purity ROM mako KK's busybox is dynamic (~500kb). :(

Generally in my experience, 400-500kb = dynamic, 800kb-1mb+ = static. :good:
[Samsung Galaxy Nexus] metalspring:
Idk, I think the busybox built in rom source is more or less a sum of all it's parts kind of thing. Basically meaning that while the core of the busybox might get updated, different utilities it uses also need updated to include new functions (In our case e2fsprogs would need updated).

Also I think there are 2 ways to go about compiling busybox for android, one is the way I'm trying (building it from within a rom source) or downloading and cross compiling the official busybox source for android (which would probably end up in a gigantic busybox lol).

Then again I'm no expert and may be completely wrong lol
[Samsung Galaxy Nexus] bsmitty83:
https://github.com/KitKatPurity/platform_external_busybox

LOCAL_FORCE_STATIC_EXECUTABLE := true

LOCAL_MODULE := static_busybox

LOCAL_MODULE_STEM := busybox

LOCAL_MODULE_TAGS := optional

LOCAL_STATIC_LIBRARIES := libclearsilverregex libc libcutils libm libuclibcrpc

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
But in the configs static is turned off

Btw, I think we were both right and wrong. You need to set the config options like you would for a kernel but you need to actually build it the way I did with mma
[Samsung Galaxy Nexus] bsmitty83:
I see , I didn't even think about the ROM build using the busybox config file . I thought the mk file took care of it lol . I'm so green modding ROMs its ridiculous

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
My build failed, but I think that was due to not having kernel source (one of the many things busybox apparently relies upon), but look here-

make[1]: Leaving directory `/home/metalspring/android/vanir/external/busybox'

cp external/busybox/.config-full external/busybox/.config

echo "CONFIG_CROSS_COMPILER_PREFIX=\""arm-eabi-"\"" >> external/busybox/.config

cd external/busybox && make prepare

make[1]: Entering directory `/home/metalspring/android/vanir/external/busybox

Looks very similar to a kernel :P
[Samsung Galaxy Nexus] iluvamk:
Just so I am clear. . .If you format to f2fs then both the ROM and kernel MUST built for f2fs?
[Samsung Galaxy Nexus] bsmitty83:
Holy crap , my board showed up today , only took 2 days . so I'll start tearing into it later tonight or tomorrow hopefully I'll have a working nexus again soon

Hack The Tuna
[Samsung Galaxy Nexus] dbh369:
Maybe take a couple pics? Thinking about a boardectomy
[Samsung Galaxy Nexus] bsmitty83:
I think I can do that [emoji6]

There are a lot of great disassembly videos on YouTube as well but this is basically it

http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
Its quite simple. If you have the tools.
[Samsung Galaxy Nexus] bsmitty83:
We back in business lol . very easy replacement . the hardest part is separating the back plastic covering the board from the phone . all in all it took less than 20 min .

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
So it was the board after all lol. Good job.