yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Firewalker1980:
I've had bootloops ever since I got the GNex... Reboot, Reboot to recovery both work only half or less than half of the time. Reboot to bootloader is the only thing that works good so far. I've had it on all rom/kernel/ext4-F2FS combinations. I feel your pain! ;)
[Samsung Galaxy Nexus] chongns:
what smoke you feed to you Gnex? [emoji33]
[Samsung Galaxy Nexus] büscher:
I'd also like to report on 6/15:

current uptime of my phone: 2 days 17 hours (very long :p) -> still no lags, all smooth.

@osm0sis: suspend_trim on f2fs doesn't seem to work:

130|root@maguro:/ # logcat -d | grep -i fstrim
1|root@maguro:/ #

I also had google logo bootloops, but since 6/9 and a clean flash of my ROM they are gone

I have no idea what [MENTION=4608636]bsmitty83[/MENTION] did or not, but since some versions of DirtyV my wifi's don't get lost anymore :good:

If I don't change anything to the kernel (no TC-module, no custom values in synapse) the kernel is very stable. Just applied all my settings and inserted TC-module without reboot (after this 2 days and 17 hours uptime) and will report if anything goes wrong in the next few hours.

One thing I had 3 or 4 days ago: My battery stats were borked, also after a very long uptime. The ROM maintainer told me that has nothing to do with the ROM. The stats (settings and BBS) told me an "On Battery" since some minutes where it was on battery for hours. also the minutes reset frequently. Also out of nowhere my phone suddenly thought it gets charged (screen on, my alarm app opens and sleepbot got activated -> that's what it is doing if I plug in my phone after 8pm). A reboot did the trick.
[Samsung Galaxy Nexus] pvkiniyan95:
Happy it helped ;)
[Samsung Galaxy Nexus] Ziyan:
Just fixed a couple of compilation warnings. Idk if they change anything, but it's good to have cleaner output while building, isn't it?

I've also modified my noobish script so everything needed to build the kernel with ramdisk is included, and it's only one command. :p
[Samsung Galaxy Nexus] dezful:
The same here. suspend_trim on f2fs doesn't seem to work. :)
[Samsung Galaxy Nexus] xzilem:
I already switched to Nexus 5 since last week but I'm still coming back here to read dirtyv thread because this thread is full of knowledge :good:
[Samsung Galaxy Nexus] Grarak:
I hope you know that you can also commenting out code with

/* */

#ifdef 0 #endif
[Samsung Galaxy Nexus] Ziyan:
Yeah, I just don't like ifdef's since text editors usually don't highlight the code as commented out, and I previously had problems with /* */ (like when there's another comment block inside it), so I mainly just use //'s, it may look a bit ugly, but it's one click with a decent editor too :)
[Samsung Galaxy Nexus] Grarak:
actually the standard text editor of ubuntu should highlight #ifdef 0
[Samsung Galaxy Nexus] dbh369:
I used dalvik, ext4 and f2fs, omni metal and commotio, smitty v and had boot loops on all, now suddenly on liquid no loops! I'm suspecting some kind of corruption too

Ps, not using exposed

---------- Post added at 02:20 PM ---------- Previous post was at 02:09 PM ----------

If I understand your question, in TWRP under Settings, check the boxes under "Force data, cache wipe partition to format F2FS" or something like that. Also check the box for System under it. Then wipe to reformat.
[Samsung Galaxy Nexus] sam45:
For some reason the "Force data, cache wipe partition to format F2FS" doesn't stick in TWRP after rebooting
[Samsung Galaxy Nexus] dbh369:
I had that on an earlier version, do the wipe and then flash the Rom, don't reboot
[Samsung Galaxy Nexus] osm0sis:
Depending on your ROM the actual vold fstrim daemon that runs after 24h uptime may or may not work; ROM patches are required to make it recognize f2fs. I think rkpeterson added it in his last LS-f2fs, and he got them from Vanir's Gerrit but I have no idea what Vanir's got for f2fs builds currently.

As for suspend_trim (different thing), are you two certain you have suspend_trim enabled in Synapse?

Please anyone on f2fs please report your ROM, whether you've installed a third-party Busybox over your ROM's (like Stericson's; preferably you haven't but it'd be good to get one report with as well) and also the output of these commands:

su;
busybox mount -o remount,rw /system;
/system/xbin/busybox fstrim /data;
/sbin/bb/busybox fstrim /cache;
/sbin/fstrim /system;
busybox mount -o remount,ro /system;
[Samsung Galaxy Nexus] büscher:
I'm on latest CM-Remix from burstlam, with built in busybox "BusyBox v1.22.1 bionic (2014-05-29 17:30 +0200)"

the above commands give me:

first: fstrim: FITRIM: Not a typewriter
second: fstrim: applet not found
third: fstrim: FSTRIM: Not a typewriter

is it still the case that supsend_trim is enabled if you set it once? I didn't apply my synapse-settings until the post I wrote, but I thought that it still behaves like the first days of suspend_trim...

And if I enable it, do I still have to wait 24 hours or will it recognize my systems uptime?

If it gets my uptime it should have done trimming until now, but still empty lines after

logcat -d | grep -i fstrim

edit: noooooes... reboot while updating supersu :crying: 3 days and 2 hours uptime
[Samsung Galaxy Nexus] Shadow Death:
I'm sure this has been asked before but I've never had any luck with XDA's search for individual posts. Does this kernel or more directly the RSR kernel not have Draft N support for WiFi?
[Samsung Galaxy Nexus] pianistaPL:
Adios, Spain :D:cowboy:
[Samsung Galaxy Nexus] Ziyan:
Sorry for spamming the thread with my experiments, but there are so many great devs here :)

I went to omapzoom, and found dozens of commits, many of them was easy to cherry-pick. Some of them aren't really necessary for us, but I think keeping up-to-date with omapzoom is good... anyways, I'm still new to kernels (I'm halfway to get my software engineer diploma, so I understand the language, but it's so huge...), so would someone say something about the commits? This is what I found in their 3.0 repo which we don't have, then I went to their 3.1 repo, and there are dozens of commits which could be cherry-picked too... I think it would worth checking & merging them, but again, I'm still new to kernels, I can do it, but if you guys say it doesn't worth it, I'm not gonna waste my time :good:
[Samsung Galaxy Nexus] osm0sis:
Like I said, suspend_trim is completely separate from Android's 24h uptime vold trim daemon. suspend_trim is for devices that don't often reach 24h uptime because people are flashing nightlies or deltas, and runs roughly after 20min of screen on time, but only once the screen is then off for over 1 minute.

It does still just need to be set once unless you wipe data, since the setting lives in /data/trimhelper, but don't bother, not a typewriter means that we're out of luck with the standalone fstrim as well. :(

I'll ask some other devs.
[Samsung Galaxy Nexus] büscher:
ah yeah got those suspend_trim rules.

but we would see fstrim in logcat no matter which trim function (vold or suspend_trim) was active?

so neither of them work on my installed rom atm.
[Samsung Galaxy Nexus] midnightdevil66:
Is this normal for held awake time? Seems like the kernel is responsible for most of it. I'm running vanir with smittyv 6/15.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Agreed. It sounds like your ROM doesn't have the vold patches for f2fs. Could you use a ROM we know does (the LS rkpeterson posted a few days back) for a while so we can at least verify it works that way? :)

This is open to anyone running that LS build as well. Don't reboot for over 24h, fully charge your device then take it off the charger and leave it alone for 2 hours.

Then run:

su;
logcat -d | grep -i trim;

It should look something like this:

http://xdaforums.com/showpost.php?p=51512069&postcount=7283
[Samsung Galaxy Nexus] büscher:
the only reason why I was able to get 3 days uptime is that I have to learn for my exams in 2 weeks... before the exams I wont be able to mess with my phone, I know how this turns out [emoji16]

after that I'm all back [emoji106]
[Samsung Galaxy Nexus] osm0sis:
Good luck on your exams!

In the meantime, it would definitely be helpful if some other people could volunteer. :)
[Samsung Galaxy Nexus] bsmitty83:
I'm working on it .... I hate typing op's lol .

I never imagined that this thread would catch fire like it did . this started just as a kernel I made and put out because I use it . I'm glad everyone likes it but remember , I wrote the op like a week ago , now were on pg a million . and if you think its hard for YOU to keep up with .........
[Samsung Galaxy Nexus] Hetalk:
I put a little FAQ on post#2. See if that helps and let me know if you want to change something.

In fact, everyone's welcome to suggest changes.

That way, we can have less obvious questions and more fun material on the thread.:good:
[Samsung Galaxy Nexus] vlc_marcos:
Which kernel are you using? For now im slimkat rom, what is your advise for a guy that wants battery first of all :D
[Samsung Galaxy Nexus] ILA:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4278473]Hetalk[/MENTION] You should put that in the OP or the F.A.Q. and there would be much less posts like that. :)
[Samsung Galaxy Nexus] bsmitty83:
Check 4 posts back plz ......:thumbup:
[Samsung Galaxy Nexus] Hetalk:
Added. Thank you. :good:
[Samsung Galaxy Nexus] ILA:
I did and I have read the FAQ which was really helpfull, but it's still missing the 4.7 vs 4.8 question. That's why I tagged [MENTION=4278473]Hetalk[/MENTION] :)
[Samsung Galaxy Nexus] bsmitty83:
both your cores were online , lol the horizontal bars are the indicators of clock speed , the readings just go from offline to your maximum frequency . ive done it myself ....;)
[Samsung Galaxy Nexus] ashclepdia:
You should have known better than to think a new kernel on the 'aging' wise ol' Gnex wouldn't garner tons of attention, ESPECIALLY after you had shown your face consistently within the 3.4WIP/DEV thread LMFAO!

I've never really been a ROM hopper kinda user(I mainly used eclipse....man I wish there was a 4.4 eclipse build! :( lol) but kernels, yea that's a whole nother story :D I'm sure I am not alone in my excitement when I saw this new build pop into the forums. I just felt the need to chime in here and say THANKS! With some threads slowing down around here it was AWESOMESAUCE too see something new come in from someone who seems so dedicated and excited THEMSELVES about the development and also be so laid back and helpful.

This right here is why I love the modding community. I know I don't have to say this but keep it up brotha! I love coming in to see 6 new pages of stuff all the time lol!
[Samsung Galaxy Nexus] bsmitty83:
For sure dude , besides the internet , I literally have nobody to talk android with , everyone I know uses apple or has zero interest in deving or Android bs . I'll always be active and updating as long as I got the device .
[Samsung Galaxy Nexus] erghetto:
lol, change friends XD

your thread has so much popularity also because yours is the only kernel updated constantly. the only!

personally i always use fancy becuase i recon it's the best, absolutely, but in next days i'll try this for sure. i'm very curious about it
[Samsung Galaxy Nexus] ashclepdia:
Yea similar here too. No one IRL around me that I know of roots or anything with their device (but for some reason they ALL want ME to do things for their device.... But the main thing they ask is "oh so you can get free apps can't you? Can u tell me how?" I always have to respond with yea, besides Pandora, just go to Play Store...and if u don't like ads put airplane mode on when playing LMFAO)

Anyways, I haven't tried out your kernel yet (my phone is in dire need of a deep cleaning/full factory wipe, the works lol.. I've jumped Roms few times lately with tons of kernel flashes in between ever since my camera stopped working on vanir. And I rarely wipe data so my device is crying for me to clean it up lol) this kernel will be the first thing I try out. I'm considering using vanir again or just going stock for a bit. Been a while since I was THIS excited to try out new kernel so once again I wanted to say thank you for that :D

(AND the other devs who have been around, I'm just LOVING reading this thread)

Also wanted to just get a reply or two into this thread so I could get the 600 gmail notifications a day when new posts come in hahahaha

cd ~/myself

sudo ./go_back_to_lurking

killall rambling.ash

That is all :D
[Samsung Galaxy Nexus] erghetto:
which version (one of bigmem, i want to keep 1080p) do you suggest? i don't ask about difference between linaro and saberomod because, first: someone could kill me if still read the same question XD second: i however wouldn't understand even you explained me XD
[Samsung Galaxy Nexus] Vekhez:
Ah, well that's just what I noticed right before a freeze.
[Samsung Galaxy Nexus] Vekhez:
Do it, and then give it to Smitty to make it install when you have the kernel installed, so they can read it and find if they have installed the wrong one.
[Samsung Galaxy Nexus] piterdemon:
Maybe stupid question, why linaro 4.8 doesnt work good on our phone ?

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy Nexus] bsmitty83:
Apparently its not just the nexus , its the toolchain itself .
[Samsung Galaxy Nexus] Hetalk:
That would be awesome. :good:

I got a few questions on the 2nd post.

Lol. You know me better than this, dude. :D
[Samsung Galaxy Nexus] ashclepdia:
Trouble is, people ask before installing lol

I would hope at least that's what they are doing lol. That could be cool tho, faq/control app that installs upon flashing hmmm
[Samsung Galaxy Nexus] bsmitty83:
Might have a late night test release . working on interactive ...
[Samsung Galaxy Nexus] dbh369:
I'm getting Not a typewriter for these too, I assume that trim isn't supported. This is on liquid that was supposed to be patched...

My performance is getting very laggy, guessing that is because of no trim ?

Btw, I tried rebooting to get better performance, little help but boot loop is back...

---------- Post added at 12:43 AM ---------- Previous post was at 12:40 AM ----------

Ps, this is the Rom I'm running and fstrim isn't working...so would vold?
[Samsung Galaxy Nexus] osm0sis:
Yeah. vold has its own fstrim and has been specifically patched to add f2fs support to the existing ext4 support. It could most definitely still work where the others don't. Please let me know. :)
[Samsung Galaxy Nexus] pattyboi:):
thank you for the git to look through :P
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2765426]styr[/MENTION] Power on the VM? :D

Static, stripped pleased. :fingers-crossed:
[Samsung Galaxy Nexus] DR3W5K1:
Commands to get vold fstrim going?
[Samsung Galaxy Nexus] osm0sis:
Always running since Jelly Bean 4.3. ;)
[Samsung Galaxy Nexus] bsmitty83:
have you tried the prebuilt busybox binaries ? they are statically built .

www.busybox.net/downloads/binaries/

Hack the Tuna
[Samsung Galaxy Nexus] osm0sis:
We need at least 1.22.1, hence all the trouble in the first place. :)
[Samsung Galaxy Nexus] bsmitty83:
whoops, totally thought it said 1.22.1 , forget it . lol I'm going to sleep for a few hrs
[Samsung Galaxy Nexus] creeve4:
I'm stuck at the Google boot logo after doing the following:

1. formatting to F2FS

2. flashing the latest F2FS version of Liquidsmooth (LS-KK-v3.1-F2FS-2014-06-14-maguro)

3. booting to System

4. rebooting to recovery and flashing DirtyV-URSR-6.15.14

5. attempting to to reboot to System

I am able to pull the battery and boot to recovery, but Android will not boot past the Google boot logo.

After reflashing Liquidsmooth I can boot to System. Seems like an issue with DirtyV-URSR-6.15.14.

Any ideas?

[MENTION=4544860]osm0sis[/MENTION]

E:\>adb shell
shell@maguro:/ $ su;
su;
root@maguro:/ # busybox mount -o remount,rw /system;
busybox mount -o remount,rw /system;
root@maguro:/ # /system/xbin/busybox fstrim /data;
/system/xbin/busybox fstrim /data;
fstrim: FITRIM: Not a typewriter
1|root@maguro:/ # /sbin/bb/busybox fstrim /cache;
/sbin/bb/busybox fstrim /cache;
fstrim: applet not found
1|root@maguro:/ # /sbin/fstrim /system;
/sbin/fstrim /system;
fstrim: FSTRIM: Not a typewriter
1|root@maguro:/ # busybox mount -o remount,ro /system;
busybox mount -o remount,ro /system;
root@maguro:/ # busybox mount -o remount,ro /system;
[Samsung Galaxy Nexus] styr:
I forgot, ofc, but i`m on medical leave these days so i might aswell do it :D
[Samsung Galaxy Nexus] DR3W5K1:
Flash kernel directly after rom *WITHOUT* rebooting.

Report back please.
[Samsung Galaxy Nexus] styr:
Here, try this one, but i doubt it that i`ll get it right on the 1st try:P
[Samsung Galaxy Nexus] gohamstergo:
Dat battery life tho...

(Wifi and basically zero usage. Rarely happens.) But still pretty dang good standby battery usage. Have wakelock blocks on a bunch of stuff too.
[Samsung Galaxy Nexus] osm0sis:
Thanks! We're getting there! :D

Looks like it's got the patches and configuration we need, but it's still a dynamic compile against bionic and we need static so that it can run at early-boot before /system is mounted.

In my experience ~500kb = dynamic compile, ~0.9mb-1.2mb = static compile. Apparently a straight static compile could be up to 1.8mb (like the one with MultiROM), but stripping the .o file before compiling it to binary will bring it down to ~1.0mb (like Stericson's) which is what we're after. :good: :)
[Samsung Galaxy Nexus] xergio24:
Hi guys, sorry for the noob question but I think this should be on the FAQ...

I flashed the latest DirtyV Kernel (DirtyV-UR-6.15.14.zip) using TWRP 2.7.1.0.

And now what? is there supposed to be a DirtyV menu somewhere? 'cause I'm not seeing any.

I also downloaded büscher's scrit and put the file on system/etc/init.d with the permissions like he says on the post but then what? how do I activate that script?

And once again, the thread has more than 10.500 posts, I think this should be included in the FAQ.

Searching for the answer in a thread that long is not so easy.

BTW I'm using CM11 Nightly 20140615 (came from stock kernel, ext4 file system).

Thanks in advance! =)
[Samsung Galaxy Nexus] qu4nd:
You flashed a kernel and expected what?
[Samsung Galaxy Nexus] styr:
Take #2, compiled standalone, not from the rom`s environment.
[Samsung Galaxy Nexus] bsmitty83:
you need to use the recoveries located in the op , they are the only ones with f2fs menu choices . official twrp has f2fs support but it needs to be built with the option for the nexus which it isn't ,

as for scripts they are activated by a reboot . automatically. or you can run from a terminal emulator , adb , or an app that executes scripts .

most of this info is in the FAQ , script usage can be found in a lot of places.

Hack the Tuna
[Samsung Galaxy Nexus] büscher:
you flashed a kernel, that wont give you any menu - that's the "software-core" of our phone.

and my script just runs, you won't see anything. you can check if the values are applied (trickstermod or synapse) or you can see it if your screen flickers and changes the colors after boot.

---------- Post added at 02:23 PM ---------- Previous post was at 01:32 PM ----------

-- all my fault
[Samsung Galaxy Nexus] Godra:
What proceses you blocked?
[Samsung Galaxy Nexus] Rushead:
Not to be rude, but I think we need a WTF button. Too many WTFs and you're banned for a day? Just an idea.

If you don't know what a kernel is or does, you need to Google Android basics and read from there. Nowhere in the >10,000 posts in this thread will you find the answers you're looking for. Nor should the op have that information. Sorry.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] michierusama:
Thanks. IMEI reported so they can not use it. But my data was personal and I dont care I just deleted credit cards info from play for some time. Today I feel better. But Im kinda scared and frustrated...
[Samsung Galaxy Nexus] creeve4:
Same result...

Nobody else is experiencing this with this combination of ROM and Kernel?

Edit:

Re-downloaded the kernel for the third time and it is now working. The other two downloads must have been corrupt.
[Samsung Galaxy Nexus] lollipop:
sorry boys for asking,but i'm really confused

witch is the recommended kernel to use between the three (smitty or dirty-v or dirty-vSR)

please answer me
[Samsung Galaxy Nexus] dbh369:
No recommended, but personal preference depending on features you want, see 2nd post for explanation. Personally I use smitty V but try them all and see which you like
[Samsung Galaxy Nexus] xergio24:
No no, I don't want to use f2fs (for now), I just didn't knew that scripts were activated automatically... that info is not on the FAQ and is not in büscher post either.

Thanks for the response =)

so... just puting the script without the extension I'm good to go... (and the permissions of course)... ok! thanks büscher! =)

Well I was expecting some kind of new option on the configuration menu were I could easily change the kernel settings, or at least an option to select a certain script to be "active".

Well, you are indeed being a little rude... I know what a kernel is, as I said before, I thought it would be some kind of menu somewhere to change some kernel settings, just that.
[Samsung Galaxy Nexus] DR3W5K1:
Download Trickster mod or synapse from the playstore to control the kernel
[Samsung Galaxy Nexus] büscher:
you have to download "Synapse" from play store if you'd like to fully customize your kernel settings.

but either you use a script (which may is a bit outdated because I also switched to synapse - more settings easily available) or you use synapse. I recommend not to use both at the same time.
[Samsung Galaxy Nexus] gohamstergo:
Wakelock blocked pretty much any app i know doesn't need to be doing stuff in the background. But most importantly, denied "wake up" and "keep awake" from Google play services and Google services framework in App Permissions. Also, went into Performance > Wakelock Blocker and blocked "RILJ." Now at 48% after 22.5 hours.
[Samsung Galaxy Nexus] lollipop:
i'am using dirty-vSR because it has 758mb ram and smitty has 689mb ,i thaught the kernel witch has more ram will be the best one

Am I right ??
[Samsung Galaxy Nexus] a3361035:
Compared to ext4 as seen in [1].

Sequential Read: 29.59 MB/s vs 27.03 MB/s ( 9.5% better)

Sequential Write: 7.61 MB/s vs 7.53 MB/s (10.6% better)

Random Read: 6.02 MB/s vs 7.3 MB/s (17.5% worse)

Random Write: 0.48 MB/s vs 0.24 MB/s (100% better)

Anandtech uses the same benchmark in their tests and even tested the Galaxy Nexus once. [2]

Compared to modern devices this is all very slow. [3]

Can someone actually compare ext4 vs f2fs on the same rom/kernel with fsync really on. [4] Also note the emmc version. [5]

Personally i would never use a FS officially labeled experimental [6] and would even wager that random read is the most important metric as that will prolly be the most common IO operation.

[1] http://xdaforums.com/galaxy-nexus/general/nexus-storage-performance-time-trim-t1971852

[2] http://www.anandtech.com/show/6130/the-16gb-nexus-7-storage-performance

[3] http://www.anandtech.com/show/7903/samsung-galaxy-s-5-review/7

[4] http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53040340#post53040340

[5] http://wiki.cyanogenmod.org/w/EMMC_Bugs#How_do_I_check_my_device.27s_eMMC_details.3F

[6] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/fs/f2fs/Kconfig#n2

Someone answer that.

It's news to me that F2FS has that much space overhead. If i would have to guess i would say the kernel forgets to clean. [1]

How much space is it losing on /system? ~100MB on a 644MB partition is 15.5% overhead.

How much space is it losing on /data?

How much space is it losing on other partitions?

[1] http://en.wikipedia.org/wiki/F2FS#Cleaning_process

Instead of all those repacked ROMs couldn't we just have a ramdisk which still mounts /system as ext4. Even the Moto X does.

Or people should stop the repacking already if they can't compile the ROM and cherrypick/add any patches.
[Samsung Galaxy Nexus] büscher:
very interesting post, thank you!

but one thing: owning a nexus device (made for developers) means trying new, experimental stuff... (at least for me) ;)