yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Looks that way , I somehow lost the volume buttons working tho , probably something not properly connected , gotta take it back apart and try to solve that tomorrow. I spend so much time in bootloader or recovery that its a must for me . but for now I'm happy with it . I lost 16 GB of storage as I had a 32gb model and the transplant is only 16 but that's trivial to me . I took apart my incredible 2 a few times when replacing LCDs to get it all right lol .

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
I forgot to mention some people broke that... Changing some parts from their cell phones. Maybe you didnt connect it right. (Hope so) lol.
[Samsung Galaxy Nexus] bsmitty83:
Yea its a soldered connection so I may have to resolder it , but if that is the case I may have to take it to my work and try to reconnect it . I do have some soder experience but it'll definitely be a challenge for me if so

Hack The Tuna
[Samsung Galaxy Nexus] seriousia:
Is there any alternative available to touch control?
[Samsung Galaxy Nexus] mangusZen:
It just happened to me :( damn volume buttons are the only part soldered to the mobo, and broke easily if you dont know..I have replaced the usb port stuff and it's ok but I have to wait tuesday for a friend to try to solder volumes back...

May the Tuna never die! Lol

P.s. Congratulation for your newborn I know Im late :(

P.s2 Can you link where you bought the mobo at that price? I cant find anything decent thank you
[Samsung Galaxy Nexus] AbhishekS:
One little off topic question:

When switching to f2fs, everything is wiped. Even the data/media/0 folder.

Now the question is that I have wiped this folder in the past too. After restoring the contents, the dates of the photos and videos aren't the same. They all get arranged to their file names and not the dates as the date for every file becomes the date on which you restore these files.

Any way by which I can restore these contents without messing about the dates of my photos and videos?
[Samsung Galaxy Nexus] drmxmyt:
you could backup them to an flashdrive with otg cable through your phone, and then copy them back to dcim after then. it should be ok as they will the same files. mtp could mess with them if you use pc. or you could adb pull and then push them again.
[Samsung Galaxy Nexus] Charmacas:
Via adb it's the same. I could not solve it yet. I just live with it. ?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] AbhishekS:
I did try with adb also once. Did not help. Are you sure OTG will help?

Yes, but I can't live with it. They are very important to me.

Surely there would be some way.
[Samsung Galaxy Nexus] Hetalk:
Try zipping them before adb pull. The zip archive will preserve timestamp.
[Samsung Galaxy Nexus] AbhishekS:
And how do I zip them? Anyway to zip while transfer?

Because my data is already of 11GB and zipping can't be done as I'll fall short of storage space.
[Samsung Galaxy Nexus] büscher:
The gallery app QuickPic has a setting that corrects the dates of your photos. it takes the exif date when the photo was taken and replaces the "created" date with it.
[Samsung Galaxy Nexus] Hetalk:
Lol. 11 gb of photos. Sorry man. I don't think they can be zipped. At least on the phone.
[Samsung Galaxy Nexus] nikodr:
Would this kernel work with 4.4.3 roms for gnex?
[Samsung Galaxy Nexus] bsmitty83:
EBay lol

Hack The Tuna
[Samsung Galaxy Nexus] pianistaPL:
Yep

Wysłane z mojego AOSP on Maguro przy użyciu Tapatalka
[Samsung Galaxy Nexus] rkpeterson:
Here is a new build of LiquidSmooth converted to f2fs TORO only.

https://www.mediafire.com/?wnbdnwep0mi7wp7
[Samsung Galaxy Nexus] AbhishekS:
Yeah. 7GB photos, 4GB of videos.

And images+videos worth 21GB on Picasa synced via Picasa sync on the Gallery app. :)
[Samsung Galaxy Nexus] bsmitty83:
I got some new kernels building , I'm gonna use the any kernel format so they can be flashed on ext or f2fs . also I reverted the ramspeed commits from mpokang kernel , as they just aren't safe for the gnex . before we get into a huge debate about this , all I'm gonna say is I'm not the only one who came to this conclusion and the linaro teams emails will back this up as well as [MENTION=3390093]MWisBest[/MENTION] . I know people have used his kernel for a while without problems , but for me the risk of memory corruption is too high and I don't want the responsibility of frying someone's phone . and besides that the linaro guys found it was only good for benchmarking . it made no difference in real world usage . so yes your antutu scores may not be as high , but again its not worth it to me to use something unstable for good bench scores .

Anyways , I'll try to update the op when I can . also I'm still planning on redoing the philz recovery , so it will read ext mounts . it still should work to format the partitions , but if you need to read data in ext in recovery it won't

Hack The Tuna
[Samsung Galaxy Nexus] chongns:
Yes, i support that.
[Samsung Galaxy Nexus] DR3W5K1:
Hey Smitty you still going to build with ramdisk when osm0sis gets it done? Also is it just me who can't use synapse and tethering on the test f2fs?
[Samsung Galaxy Nexus] bsmitty83:
I think I'm gonna use ramdisks anyways , I can't get the any kernel version to boot . I haven't tried synapse in a while . also not sure about tethering . it should work on the newest smittyV . the test kernel uses vanirs ramdisk witch doesn't have synapse support or the required hostapd binary for tethering

Hack The Tuna
[Samsung Galaxy Nexus] Atento:
Is there any risks of using his ramspeed optimizations? Is there any overclock on ram speed?

It would be great if you post the email you are referring to.
[Samsung Galaxy Nexus] bsmitty83:
I think there is definite risk . anytime you mess with arm errata there is .

Overclocking the ram has also been proven useless

Here's the convo

http://lists.linaro.org/pipermail/linaro-dev/2011-November/008710.html

Hack The Tuna
[Samsung Galaxy Nexus] DR3W5K1:
Compared building dalvik against the two. Omg that vanir version kills the latest Smitty. Wonder why?

---------- Post added at 12:47 PM ---------- Previous post was at 12:02 PM ----------

Never mind the latest smitty seems to be on par.

---------- Post added at 01:05 PM ---------- Previous post was at 12:47 PM ----------

*golf clap* Sir you have made my phone a transformer. Feels like I own a nexus 5 now.
[Samsung Galaxy Nexus] Charmacas:
Does anyone have problems sending pictures via WhatsApp? Could it be because of the new file system? Any other tip would be appreciated too.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] seriousia:
Naah no such problem here. :):)
[Samsung Galaxy Nexus] michierusama:
Nope. Vídeos neither. Check your network.
[Samsung Galaxy Nexus] osm0sis:
There's a new Xposed module that does it now.

Even better: tar.gz them to a USB OTG drive. :)

11gb would compress a bit and timestamps, ownership and everything would be preserved.

Nice!

AnyKernel won't work because you'd still need to determine f2fs and change the fstab as required. The recovery busybox would need to be v1.22.1 to do this. Kinda the same problem as before. :p

Good read.

They mention synthetic benchmarks but they don't outright say it didn't help, just that there are new errata that could cause corruption with it enabled, so it is potentially dangerous. :(

There were some minor patches at the end of the conversation which seemed approved though, eh?
[Samsung Galaxy Nexus] bsmitty83:
Yea I included those that were safe , MWisBest should get credit for bringing all this up . I never questioned the commits as I should have , although some seem to think that they are safe , I'm not taking the chance for a minimal to zero improvement to anything other than a benchmark

Hack The Tuna
[Samsung Galaxy Nexus] ashclepdia:
lol

and.I was JUST about to mention, maybe you should try just backing up the files to G+(15gb full detail pic/video backups), drive, box, dropbox, mega, or just send em over ftp, wifi direct, or some other means of sharing/backing up directly to computer,

what I mean to say is, at 11gb at this point, don't you think it would be a good idea to put all 11gb of that stuff somewhere else? why does it all NEED to go back on device(thus getting the wrong date as u mentioned) when you could just back them up somewhere that allows you to access them from your device still(like a network shared folder/drive on your computer that your device can access media) if you NEED to be able to access them to show from device. otherwise, you can just free up that 11gb of space.

(I'm in no way trying to attack you for what you WANT to do, I'm just curious, I'm certainly guilty also of having tons of stuff on device that I don't really need including tons of media, 32gb toro and I noticed yesterday I was down to 1.3gb free on /data...so had to delete a nandroid, some video, bunch of cache files and downloads and presto I'm back at 5gb free...once everything finishes backing up to g+ photo backup I'll probably delete all pics and video on device freeing up another prolly 8gb

---------- Post added at 02:34 PM ---------- Previous post was at 02:27 PM ----------

yes PLEASE use ramdisk

I for one have always enjoyed the kernels that come as.boot.img vs anykernel format.

I mean I ALSO enjoy taking another ramdisk and using it with other kernel just to see what happens, but when a kernel comes as full boot.img, in my experience and reading, you find less posts in those threads regarding issues that have almost nothing to do with kernel just because rom did something different. anykernel is fun, and very useful in situations. BUT, lately anyways, if anyone has EVER asked "for an anykernel version for use with xxx", someone has shown them how to break it down or do for them. so then there is chance when dude learns about breaking down and repacking, they may want to go further, so it Just keeps spreading lol

keep killing it dirtyville
[Samsung Galaxy Nexus] Ziyan:
What about at least making them an option in defconfig, default it to disabled, so someone can enable it more easily than finding the commits? I'm one of those who think it's ok, also, there were no reports of anything bad happening in mpo's thread :) and I think the worse that could happen is a hang, as from the commits, I see only software side changes, no OC or things like that. I can imagine that extra RAM speed may help with memory consuming apps like Chrome, and games... also, doesn't the GPU use the system RAM as well? If so, the RAM speed may affect texture operations... or - if the community, and you would agree about this -, this could be enabled in the SuperRam builds (would make sense, as some already thinks SR isn't safe...), and disabled in every other build, so everyone would be happy :good: and if we see problems, we could then tell you, so you could disable it :highfive:

Oh, and my opinion and perception about the SR builds: many people finds it useless to have 60+ mb of extra RAM. However, when running Skype + Facebook Messenger + Barometer + Dashclock with plugins, etc at the same time, I find it quite useful! I usually install the latest kernels, but with SmittyV kernels (with only 690 mb of RAM), I always find that multitasking is worse - I just can't switch from Chrome to Skype, then switch back to Chrome, it nearly always gets killed, which is quite annoying with my super slow 32 kbit/s mobile internet connection :( but with SR builds, I find that it doesn't kill apps that often... and the thing that some people say, that the extra RAM is better for the kernel: I don't think it even uses it if we aren't recording/playing 1080p, as I never noticed any problems or slowdowns with SR builds :highfive:
[Samsung Galaxy Nexus] KiD3991:
Well. I'm a Nexus 5 user previously. Just downgraded because I wanted to join the community here too.

Is there any marginal improvements changing from Dalvik to ART in GNex?

I use DirtyV RSR previously and jumped to the latest for now. I overclock to 1.6Ghz and use it as daily. As well as UV -50MV.

I just need to know the effect of ART on this device...
[Samsung Galaxy Nexus] DR3W5K1:
Some people swear by it others say its slower. It works if that's what your getting at.

Just try it it's just as easy to switch back to dalvik
[Samsung Galaxy Nexus] KiD3991:
Heh. Problem is that I'm already in ART. Facebook does start much much slower(after greenify hibernation).

I just need to know how much the difference is. Thanks for the swift reply. :)
[Samsung Galaxy Nexus] bsmitty83:
Honestly , I don't know what's the worst that could happen , and I really don't want to find out . more than likely I'd keep them if there was any real world improvement , but the linaro team found it was useful for benchmarks , that's it . it won't make your phone faster . as far as I know its a static commit , there is no option at compile time to enable or disable .

The commits are very easy to find and implement anyways . it's only 3 and they are on github .

Again to me its simply not worth it when there is no proof of better performance other than benchmarks . its basically a benchmark hack more than anything . and since I'm no expert I'll definitely listen to the guys from linaro on this one .

I know that it seems like if it benches higher its gotta be good but I havent seen any real world improvement.

So for now I won't build with them . its just a personal choice , and if you really want them there are other kernels with them included . plus my source is always kept up to date , so anyone can build their own version .

Also I made a test kernel with all the errata workarounds disabled , and the first time my phone froze , it smoked the CPU or a component . my phone would not even power on . so not saying it was from those commits but they were present.
[Samsung Galaxy Nexus] Shadow Death:
I haven't noticed any difference in ART over Dalvik with regular real world use. I don't think its a performance upgrade so much as a security upgrade.
[Samsung Galaxy Nexus] ashclepdia:
okay random off the wall question time!

vram

on laptops you can tweak it to use some.onboard ram as vram potentially helping graphic/media playback performance? Or am I way off?

anything similar can be done for GNEX?

the fact that on 4.2+ watching any mkv video format of 720p or higher is HORRID(sometimes even just 720p mp4 files are junk playback)

need way to fix this or help it
[Samsung Galaxy Nexus] brymaster5000:
Once art is fully implemented into apps, which it's a long ways away, you will notice a difference. But for the meantime, switching will have little to no effect. I do believe Google has been moving to art in their recent slew of updates which imo has been killing my battery on the m7...because art isn't working for us yet fully...

my 2¢

Sent from my Lunar Ecliptic One.
[Samsung Galaxy Nexus] amd_h4x0r:
does anyone have a copy of the f2fs kernel above? I can't find it on Dev-Host
[Samsung Galaxy Nexus] osm0sis:
Yeah sorry, I got a bit cocky and took them down once I made my (broken busybox'd) Unified ramdisk. ;)

I'm going to add a hack to make it just assume f2fs if it's not ext4 and put the Unified back up while we wait on that busybox we've got like 3 people working independently on compiling now. :p
[Samsung Galaxy Nexus] bsmitty83:
Got a build going now for you , hoping it'll compile . I added Motorola's f2fs tools , static busybox , and philz recovery . trying to get it all in one shot

Hack The Tuna
[Samsung Galaxy Nexus] pkgnex:
I completely respect your decision to include, or not include, the mpokang RAM speed commits. It's your kernel! If it were me, I wouldn't want to be responsible for messing up people's devices if something went wrong either! I will also probably stick with kernels that do NOT have them, because I'm not much of a risk taker ;).

I do, however, feel compelled to call BS on the "it only helps in synthetic benchmarks" portion of the Linaro guys' claims. I have a few games that absolutely load appreciably faster and run smoother with the commits than without them. My observations that the phone seems overall a little faster with the mpo commits could be placebo effect, but not the opening time on these apps. I've timed it, and it's about 50% faster (coincidentally).
[Samsung Galaxy Nexus] bsmitty83:
That's interesting .... I can't say that its placebo and it probably is from those commits . I wish there was more info on this . Fransisco franko is looking at them from what I hear , if he says that there is no danger I'm more inclined to use them , I just have lots of conflicting info and really not sure anymore what's right or wrong on them

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
Amperific told me that they are proven safe but he never saw the need for those commits. But community wanted to have it and he added it to the kernel. I am a simple tester and reporter so I don't know too much about coding but well... I go with whatever you do!
[Samsung Galaxy Nexus] osm0sis:
Woot! :fingers-crossed:

I'm inclined to agree with you here. You've always had a keen sense for this stuff and I trust your "internal benchmarking". :p

P.S. Franco's Dev Team in the house. :D

Just fired off the email to him with the link. We'll see what he thinks. :)
[Samsung Galaxy Nexus] namtombout:
Smitty you've had many reasons to leave our nexus alone; new phone, official kit kat on that phone, fried board, a new heir yet you're still here. We lucked up getting you. Thanks

Is it because of you and your team that twrp and others have started f2fs development or just coincidence?

Seems similar to what happened with Franco dev team and trickster.
[Samsung Galaxy Nexus] metalspring:
Its possible, but tuna isnt the first device to have f2fs support, most of the other nexus devices also have had f2fs supported roms and recoveries made as well as the moto x having the data partition formatted to f2fs by default. Right now tuna is actually mostly forgotten by a lot of developers as they moved onto new devices :(
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4544860]osm0sis[/MENTION] amp was talkign about the ram reclaim commits,i just commited the mpo ram speed stuff the other day,amp mustve been thinking the wrong thing because we didnt know what commits mpo was using 4 months back
[Samsung Galaxy Nexus] bsmitty83:
This ^^^

I started working on it when I noticed the post in the dev section . I think that once the motox came out , everyone started the f2fs conversion , its just that most moved to newer devices leaving us amateurs to pick up the slack lol . if someone with more knowledge had been here to do it , we probably would have had f2fs long ago . I'll leave the nexus when i get another phone to replace my note2 its funny that I really dev for my "old" phone , not my main . but the nexus is an awesome phone to learn on . very forgiving , super hard to brick , and for building kernels its awesome that everthing is inside the zimage , no modules to worry about .

I'm lucky to have a community to work for is the way I see it , not the other way around [emoji106]

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
DirtyV-R-5.31.14-metaltest2-Unified:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod

I'll push this version of the Unified (f2fs+ext4) ramdisk to Github until we get a working busybox, then it's a simple edit to 1 file and it's good forevah. :cool:

[MENTION=4608636]bsmitty83[/MENTION] Just remember to add the code in for flush_merge before you use it since I used [MENTION=4328678]metalspring[/MENTION]'s f2fs mount options which benchmarked better. :good:

Edit: Done! https://github.com/bsmitty83/DirtyV_tuna/commits/SmittyV-eXp4 -- and the file to be edited once we upgrade the included busybox is fscheck. (see comments)
[Samsung Galaxy Nexus] imam.krismanto:
Please give me link for ROM with f2fs...
[Samsung Galaxy Nexus] jhonnyx:
Please read second post of the thread.
[Samsung Galaxy Nexus] bsmitty83:
I'm using hashcodes f2fs commits , flush_merges should be there

Edit : of course it wasent included in hashcodes source , but I added it [emoji106]

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
Ever consider adding any of these?

FIFO (first in first out I/O scheduler)

https://github.com/metalspring/DirtyV_tuna/commit/05453a7ad4e884f974b58fadbb00f2c9d56b60d2

https://github.com/metalspring/DirtyV_tuna/commit/c8fec8e68c259c011deab3194f39cbda9cb3346c

And a bunch of other cpu governors-

https://github.com/metalspring/DirtyV_tuna/commit/068c8ff73b416f6f1b3ca6d42b06bb6b691e30e9

https://github.com/metalspring/DirtyV_tuna/commit/770d05fbe7da42cf12efc0d2a1fdd00c6050a82e (part of it fixes pegasusq governor, no idea how that disapeared in my commit lol)
[Samsung Galaxy Nexus] bsmitty83:
Fifo yea , but the other govs are really geared for quad cores IMHO , honestly I use interactive all the time

Hack The Tuna
[Samsung Galaxy Nexus] dezful:
Just flashed this on 4.4.3 LiquidSmooth. everything seems well.

Just realized that on 4.4.3, ART is much smoother than dalvik. I can see the smoothness improvement on twitter and line apps, where I couldn't see the difference between them on 4.4.2. ;)
[Samsung Galaxy Nexus] MWisBest:
For what it's worth, it wasn't just Linaro people in that mailing list, it was Texas Instruments people. I'm going to trust that they know their own chip.

The changes aren't exactly for helping increase RAM bandwidth specifically, that's just where the most (synthetic) improvements can be seen.

I think there's maybe a chance that ARM expanded their errata on this issue (double lifefill not working properly) just a tad too high... the part of the chip effected was expanded from a previously lower version number to r3p2, and the OMAP4460 is r3p1-50rel0, so there might just be a chance it was expanded too much to be conservative or something. If I was able to get my hands on a more recent copy of ARM's errata documents I might be able to see if they've updated that errata since the ~2012 version I was able to hunt down, but to get it from ARM you have to log in as a paying customer of theirs or something, which is ridiculous in my opinion. TI has their OMAP4-specific errata PDFs available free of charge, no sign-up or anything required, sucks that ARM can't do the same.

If it is fully proven to be safe, there can certainly be some real-world speed-ups from it, but it's not impressive enough to be worth risks.

My dad has a Droid Razr he doesn't use anymore (he's got a Droid MAXX now, basically a Moto X with a bigger screen and 3000mAh battery), I think that's an OMAP4430, so if he's willing to let me tinker with it and I can get a custom kernel going on there I can see how obvious things muck up from the questionable changes as I'm pretty sure the OMAP4430 would be lower than r3p1.
[Samsung Galaxy Nexus] KreNtal:
Guys is it possible to use f2fs on cyanogenmod? How?
[Samsung Galaxy Nexus] gautam_nexus:
Found this script which converts any ROM to f2fs format.

http://xdaforums.com/google-nexus-5/development/script-convert-rom-to-f2fs-t2748116

hope [MENTION=4544860]osm0sis[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2838735]aosp[/MENTION] can help the dev of the above script to add support for Galaxy Nexus.
[Samsung Galaxy Nexus] giorgis91:
Is this kernel even for 4.4.3 ROMs?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] gautam_nexus:
Yes!:angel:
[Samsung Galaxy Nexus] thagringo:
would this so called "fifo" io sched actually make sense ?

I mean, isnt noop sched just a plain fifo sched already ?

cheers guys !
[Samsung Galaxy Nexus] bsmitty83:
Basically . fifo , noop , sio all are close in operation . not sure which one would be better , but there isn't really much to gain from fifo over the other 2 . personally I use vr .

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Any chance we could try switching to lz4 ramdisk compression? Unified takes slightly longer to boot and I'm wondering if a faster decompress would mitigate that. :)

Is the zImage already using lz4? I thought I saw you add some commits for it somewhere down the line.