yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ashclepdia:
no asurion?

I think THEY still have em

or.maybe tuna just got mad at you for some reason..

I recall once my GNEX just decided shut.down and not come back on either, no matter which of my 4 batteries I used, then after about 36hrs I tried again after fully charging a battery with my external charger,and presto it came back to life

good luck
[Samsung Galaxy Nexus] MWisBest:
That is probably who it's through, but the customers don't deal with Asurion directly, it's Customer <--> Verizon <--> Asurion.

I went down to the Verizon store today and there was nothing they could do because all of Verizon's systems are down. Down everywhere. They were supposed to be fixed 7 hours ago. They couldn't even activate my old phone.
[Samsung Galaxy Nexus] ashclepdia:
wow that SUCKS

all around just sucks :(

I ACTUALLY JUST READ a post on rootzwiki though where a guy was getting a replacement Gnex via asurion just this past couple days, on vzw, so HOPEFULLY you CAN get what you want either way.
[Samsung Galaxy Nexus] goplaycheckers:
Dude, that sucks!! I'm super sorry to hear that.

One thing to be aware of with Verizon (or Asurion, if you have to go through them) - if you have the 32GB Nexus, and they replace it with another Nexus, it will most likely be a 16GB model. You could potentially use this non-equivalency to argue your case to get a newer model. However, even if you did manage to get a Moto X, it would probably be the non-developer model (I don't think that Verizon ever sold the dev version - I was under the impression that those were only available straight from Motorola - but don't quote me on that).

Working on the assumption that they don't have any more Gnex's but they agree to give you a newer phone, you have a few options (as I see it):

1 - Keep the replacement phone and just cut your losses.

2 - Find a suitable replacement Gnex on Swappa, and then sell the newer phone on Swappa to recoup your costs. If you went this route, you'd want to cancel your insurance through Verizon because it'd do you no good on a phone that they did not supply you with.

Alternatively, you could try to find a cheap Gnex on Swappa/eBay/etc and swap boards/other parts/whatever.

Hope it all works out! Good luck! :)
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=3390093]MWisBest[/MENTION] i feel the pain dude,mine died the other day too,been messin with my sisters lol
[Samsung Galaxy Nexus] clnzx2:
If insurance doesn't take care of it get up with me... I have a board for you.
[Samsung Galaxy Nexus] DR3W5K1:
It appears that a lot of developers tunas have been dying lately.

Sucks!
[Samsung Galaxy Nexus] bsmitty83:
That's exactly what happened to my phone , I replaced the mainboard for 20 bucks . in 15 min
[Samsung Galaxy Nexus] Shadow Death:
Any chance it has anything to do with f2fs causing your phones to die?
[Samsung Galaxy Nexus] DR3W5K1:
Very doubtful
[Samsung Galaxy Nexus] Shadow Death:
My upgrade comes up on the 7th of next month at which point I'll be moving over to the One M8 while hanging on to my Gnex just in case crap happens as it always does. The Verizon reps can't make up their minds so it keeps bouncing around.

I also tried covering the recent version over to f2fs for giggles... Yeah, TWRP didn't like that. So I'm back to ext4 until an official FML f2fs version drops.
[Samsung Galaxy Nexus] smokeydriver:
So obviously the new update isn't coming (which is obviously ok, just SUCKS that your phone died!) I was just wondering if you have a suggestion to fix my SMS multiple sends- do you suggest a clean or dirty flash of the 6-5v2, or something else I should try?

Sorry to but you when your phone's dead :(
[Samsung Galaxy Nexus] JoJoDaClown:
Since your phone pooped out, do you have someone else to test it?
[Samsung Galaxy Nexus] MWisBest:
Verizon's systems have been down since yesterday morning. Not only can they not even check that I have the warranty, they can't even activate my old phone or anything. I don't even think they can sell phones or plans etc. to people right now LOL. If they try to charge me for the warranty replacement I'll throw this 2 (or more, dunno yet) day wait in their face, leaving them, and fib about having my uh, "uncle with a large Verizon business plan" leave them too (since the little people just don't seem to matter to US carriers -.-).

(Oh and to top it off, today when I stopped at the Verizon store I locked my keys in my car. I had to walk home and get my spare keys and walk back. Lovely. My life is just falling apart over here...)

I may just have to take you up on that offer, I appreciate it.

I was actually wondering if it's the eMMC that has gone bad, upon opening my phone I discovered it's a ****ing SanDisk... I tried to boot it up via usbboot/omapboot/whatever and that hasn't succeeded either though. It turns out that the phone will turn on, but it does nothing when it's on. The SoC will get really hot, but that's it.

I hadn't even used F2FS yet.

For now I'd suggest switching to Hangouts or maybe something else as your SMS app.

Depending on how long it takes for me to get my Galaxy Nexus back up and running I may go that route. My problem is that I'm uncomfortable having others test things for me, I like to make sure everything's OK on my device before I send it to others to risk ****ing up their device.
[Samsung Galaxy Nexus] Shadow Death:
So... I just converted your most recent build to f2fs... Don't get all worked up over it. I haven't seen any reason to stay with it over ext4. Ran a benchmark and got the same results as ext4 before it. :(

Edit: maybe it will change but I couldn't tell you. I'm currently pushing my sdcard contense back to the sdcard. Gotta love adb. Transfers files faster than the folder system.
[Samsung Galaxy Nexus] MWisBest:
GREAT NEWS: Somebody (who wishes to remain anonymous) has ordered me a new board AND a new 32GB eMMC module. It should be here July 2nd!
[Samsung Galaxy Nexus] Rushead:
Gotta love those people. I wish we could thank them officially.
[Samsung Galaxy Nexus] rice923:
Official or not, expressing our gratitude here is probably the most appropriate way to show how grateful we are.

This particular thread has shown the most sense of family and community I've ever been a part of. Thanks to all who make this happen
[Samsung Galaxy Nexus] Meticode:
I'm going to officially give FML a full week run for the first time. Over the course of the last year I've mostly ran CM. But ever since CM11 it's been really buggy and the battery life has been more horrible than when the phone was completely stock. I recently tried Shiny and thought that was the most stable Kit Kat release out before I tried it, but the bluetooth worked poorly. To the point where if I went out walking with my BlueBuds X bluetooth earbuds with my phone in my pocket, the music would skip as if the device was 20 feet away or on the borderline of the bluetooth range.

In any case I read through this thread and I hope you get everything sorted out with your replacement. The brief hour I've used it it's been really solid. The main thing I hope for is better battery performance. It was to the point where if I left the phone in sleep for an hour I'd lose like 5% battery.
[Samsung Galaxy Nexus] Shadow Death:
You mean like this?
[Samsung Galaxy Nexus] Meticode:
What's your setup?
[Samsung Galaxy Nexus] MWisBest:
I would definitely recheck the Gapps and make sure you have the ones I linked to, if the ROM flashed to begin with without any errors then the recovery should be fine.
[Samsung Galaxy Nexus] nnbengboy2:
I definitely have the correct ones...but for some reason it keeps getting corrupted. The second install of gapps gave me the play store, but google now was still not installed. I'm going to hope for 3rd time being the charm... :\

Any chance someone has the md5 for the gapps package?

---------- Post added at 09:37 PM ---------- Previous post was at 09:13 PM ----------

So I finally just ended up installing the Velvet (google search) apk manually from a previous download I have. Now everything appears to be functional. I love how speedy everything is! Even coming from a fresh vanilla 4.3 install.

I've had a number of freeze/reboots happen in the past half hour or so of using the ROM. Can't set up tap and pay in Google Wallet. Google Wallet also says that location sharing is off, even though I've triple checked the settings. (maybe related to the gps issues)

Just reporting what I've seen so far. Thanks so much for this amazing build! We have an amazing dev community, being able to put out builds for an unsupported phone DAYS after release.
[Samsung Galaxy Nexus] Rushead:
Once again, MW is best! This is awesome.

Tried dif cameras to no avail.

Austin, what camera did we used to install when the dinc2 sense cam was borked?

Sent from a frequent flasher.
[Samsung Galaxy Nexus] geomonroe:
uuummm. When I was young, wisdom teeth meant laughing gas. Laughing gas is goooood:)
[Samsung Galaxy Nexus] Mars196:
YouTube isn't working for me (Videos not playing), not sure if that's already been mentioned or not. Also the reboot for me at least seems to happen when launching settings, its rebooted 3 times so far.

Edit: NVM, just had a reboot using Google Now lol, was just a coincidence.
[Samsung Galaxy Nexus] prbadboy69:
Hello all, I have found this on another rom that released 4.4 yesterday. The Dev needed GPS fixed and someone posted this for him.

http://forum.xda-dev...d.php?t=2508185

Maybe this can help.
[Samsung Galaxy Nexus] MWisBest:
Alrighty, getting some Pepsi to wake up a bit and then get to work on fixing the camera to start with. :good:

I do like Coke as well, I just get whatever is on sale, I don't even know anybody else who likes both Coke and Pepsi. lol
[Samsung Galaxy Nexus] cujo6801:
To funny I'm the same way...

I buy what's on sale...

sent from the DOG pound
[Samsung Galaxy Nexus] MWisBest:
Glad I'm finally not the only one! :laugh:
[Samsung Galaxy Nexus] t1.8matt:
Pretty cool, had a problem with lag and it did a reboot while i was downloading Maps from the play store and tried to access system settings but it's neat. can't wait to see what becomes of this.
[Samsung Galaxy Nexus] nitsua98:
I just drink water :p

∆∆∆ 4.4 Illuminati symbols??? lol
[Samsung Galaxy Nexus] 47th_Ronin:
I prefer to spell it "Illuminaughty"
[Samsung Galaxy Nexus] MWisBest:
Oh, great news! /sarcasm

Some pipes leaked in my basement (just slightly, seems like condensation) which happened to drip onto my ISP's equipment that they carelessly put right underneath it. I'm now without internet and even TV, and my dad already used up the 12GB of data we share on the Verizon bill which resets tomorrow. Dev work uses a lot of data, but more importantly so did the homework I was working on that's due tomorrow. So unfortunately, I'm not sure when I'll have internet back considering how lazy the people are at my ISP. Maybe I'll dump a bag of rice on their stuff and see if that does any good. Let's hope my dad finally learns to watch how much data he uses.
[Samsung Galaxy Nexus] swordrune10:
suckyness.... good luck!
[Samsung Galaxy Nexus] tattedupboy:
I didn't see anyone else bring this up, but did anyone else have issues with LTE, mainly not having it? I was able to get 3G data, but not LTE.
[Samsung Galaxy Nexus] swordrune10:
i actually forgot to respond.. I'm using 4.2 radios and I seem to have the same problem.. now I'm not sure if it was the reboot or what I did, but I'll say what I did anyways.. I went into the testing menu, *#*#4636#*#* in dialer, and turn it to LTE only mode.. also after that I noticed in settings, more, mobile networks was set to 3g.. I switched that to LTE and rebooted.. after that it was fine.. pretty sure just going into mobile networks would be enough but might as well do it all just in case
[Samsung Galaxy Nexus] MWisBest:
OOOO great news! Seriously! Got the internet fixed, looks like dumping rice on the thing actually helped, haha. Back to homework and then more dev work. :D
[Samsung Galaxy Nexus] schnob:
I've had LTE since I flashed with no issues. Do Google Now's location based features work for anyone?
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
I was so happy to see we have Kit Kat already! This ROM runs very smooth besides the posted issues; I didn't find any others that haven't been posted. I was able to pair with my Motorola T505 (bluetooth FM transmitter). Once GPS and Camera are fixed, this is going to be beastly.

In regards to 4.4 itself: I wish the Google Search Launcher wasn't required to keep the voice commands always on. Hopefully Nova is able to utilize that feature and others that have been added (transparent nav & notification bars). Other than those changes I didn't really see many noticable differences, which I guess is expected in an incremental update. I'm excited to see what the CyanogenMod team does to this.

Thank you for all your hard work putting together this ROM! I'm so glad to know what 4.4 is like :)
[Samsung Galaxy Nexus] terminal13:
Participated
[Samsung Galaxy Nexus] Shadow Death:
Nothing special actually. No undervolting at all. I like my phone to be snappy when I need it and sleep when I don't.

I use the most recent FML build which is in the OP.

I also use DirtyV-RSR 6/28 with these settings:

Edit: I don't mess around with scripts and "tweaking" apps because usually it causes more harm than good. I don't mess with ram managers either since KK has a pretty good memory management setup as is.

Basically I flash the rom, then gapps, then this kernel. These are the settings I use.
[Samsung Galaxy Nexus] Meticode:
And honestly this is the way I've preferred doing it when I've ran other ROMs in the past. Nothing too fancy, just change a few setting here and there. I will definitely try your method with that ROM for a week and see how it goes. Possibly my battery might be crapping out. I can tell.

4h42m not charging

Phone Idle: 27%

Cell Standby: 20%

Screen: 12%

Android System: 11%

Google Services: 9%

Everything else, misc:

...surprised the screen takes up 12%. I had it one for 3m42s. I did a test run last night and after unplugging the phone at 96%, I work up 4.5 hours later and it was at 90%. Seems normal right?
[Samsung Galaxy Nexus] Shadow Death:
The screen is Super AMOLED instead of having LEDs to backlight the phone it I'd self lit. This consumes power itself.
[Samsung Galaxy Nexus] otter34:
Standard battery? I'm pretty sure I've never let a phone sit without using it for 20 hours
[Samsung Galaxy Nexus] Shadow Death:
Yup, stock battery, all the way down to NFC.... I don't know if its the original though as I'm the second owner of this Gnex.

Edit: it did get used quite a bit that day. I got a few calls, commented on XDA a few times between the Gnex forums and the One M8 forums. I also BS'd back and forth between a friend over hangouts.
[Samsung Galaxy Nexus] otter34:
Nice! Do you have it set to auto brightness? I keep going back and forth about whether or not that saves more battery?
[Samsung Galaxy Nexus] Shadow Death:
I actually don't keep auto brightness on. Back when I had my bolt it was a battery killer because it used the camera as a light sensor (if I recall correctly) which would drain battery. I think the Gnex has advancements past that to the point where it doesn't impact as much but to be honest I leave it off anyway out of habit.
[Samsung Galaxy Nexus] MWisBest:
New board and eMMC got here today instead of the expected tomorrow! I replaced just the board first to check if my existing eMMC was OK, which it is. So I grabbed all my data off of there and am setting up the new eMMC and have a new build running as I type! :D
[Samsung Galaxy Nexus] cujo6801:
Who da man?

you da man

I'm glad you got it working bro

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Meticode:
Thank you for your hard work. I've been running this about a day or 2 and this is by far the most stable KK ROM I've ran.
[Samsung Galaxy Nexus] dbt816:
So I cheated and converted FML to support F2FS with the tool from [MENTION=3927368]poo706[/MENTION] :) This is an informational post more than anything, but if it heads off a downstream problem, all the better.

Whenever I tried to change my wallpaper, it would throw an error saying that I had no external storage device. A little digging through logcat showed that a directory create operation failed in /mnt/shell/emulated/0/Android/data with "permission denied". That path is through a fuse filesystem mount. When I bypassed fuse using the path /sdcard/Android/data it succeeded (and I could then change wallpaper). I don't know if it's a problem with the way I rebuilt the system or if there is something weird going on between f2fs and fuse or whatever. No permissions along the directory structure look wrong to me, especially considering the operation failed as root.
[Samsung Galaxy Nexus] MWisBest:
I am uploading a beta build. I want somebody to test this with F2FS, as I am on ext4 currently and will be for a while yet.

1. YOU WILL NEED TO FLASH A KERNEL THAT SUPPORTS F2FS. The stock FML kernel currently does not support F2FS.

2. YOU MIGHT END UP COMPLETELY HOSING ALL YOUR DATA. MAKE A BACKUP OF EVERYTHING!

3. Please, don't use or even download this build unless you're helping with the F2FS testing.

As far as I know, it shouldn't require any sort of modifications.

omni-4.4.4-20140702-toro-FML.zip (158.84 MB)
[Samsung Galaxy Nexus] dbt816:
Think it's safe to dirty flash over my F2FS version of 06/05 FML? I don't see any issues...
[Samsung Galaxy Nexus] MWisBest:
Honestly I have no idea.
[Samsung Galaxy Nexus] dbt816:
LOL! Well, let's find out :)

---------- Post added at 02:08 PM ---------- Previous post was at 01:42 PM ----------

Wipe Cache/Dalvik, load FML, load GApps, load SmittyV kernel... just sat at the Google boot logo... not a boot loop, just sat there. Repeated those steps but didn't load the SmittyV kernel and now it's stuck on the ROM bootsplash. Can't connect with adb to get a logcat (device unauthorized).
[Samsung Galaxy Nexus] MWisBest:
Thank you for the report! I think I know what's going on then. For now go back to your other build I suppose.
[Samsung Galaxy Nexus] dbt816:
Welcome! Glad it helped :)
[Samsung Galaxy Nexus] MWisBest:
Another F2FS beta test, I'm hopeful this has the issues fixed.

Here are some details of how it works (or is supposed to work, anyway):

1. Rather than format /system when flashing the ROM, it instead just runs rm -rf, so it just leaves it as whatever you have it formatted to already.

2. When it mounts the /system partition, it doesn't explicitly specify exactly what type the file system is, it instead leaves it up to the mount program to figure it out.

With this way of doing things, there are no "conversions" or anything required, and the ROM is essentially indifferent to whatever you have your device formatted to. You could format everything to exFAT as far as its concerned!

omni-4.4.4-20140703-toro-FML.zip (158.85 MB)

EDIT: By the way, I'm also looking into whether or not it's feasible to do #2 above but for everything, everywhere, meaning even just booting Android. That would result in completely seamless support for any filesystem, on any ROM (that uses these fairly small changes), with any kernel (so long as it supports the filesystem you've formatted to in recovery)!
[Samsung Galaxy Nexus] oman0123:
You would have no idea how amazing this would be. I changed to f2fs on day 1 and while I enjoy the performance enchantments, it's a pain in my neck to convert because I own a chrome book (whoops) which can't do what I need it to.

I have use a choppy laptop to download ROM, convert, load it into google drive then download it on my phone. Fingers crossed

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] dbt816:
This one booted and is running :) Except that I didn't notice the 4.4.4 and have to go back and load the correct GApps :silly:

I'm having another oddity similar to my previous post. Now my camera cannot store the pics I take to the sdcard because the symlink /storage/emulated/0 is missing. It looks like this should be created by init.tuna.rc, but it's not in there... correct?
[Samsung Galaxy Nexus] terminal13:
So I've been trolling threads a little and see that f2fs is apparently the new it. So considering I work a lot, and have 5 kids at home, can someone point me to a good informational thread on what its benefits are and how to fully convert if I'd choose to? My gnex is running out of time based on the nexus 5 or the one plus device......but wanna keep this going as long as possible

Radiation from my 4.4.3 gnex
[Samsung Galaxy Nexus] dbt816:
So as an experiment to see if I could clear up these symlink/permissions issues, I went back and reformatted /system to ext4. I've seen other posts where folks have issues formatting /system as f2fs. Got that done, reloaded FML/GApps/SmittyV and I'm back to where it just gets stuck at the Google boot logo. Repeated with /system as f2fs and it booted. :confused:
[Samsung Galaxy Nexus] MWisBest:
That is extremely odd. I'll see if I can find what's causing that.

I have no idea how to do the conversion, hopefully somebody can point you in the right direction. Figured I'd at least acknowledge your post so you didn't think I missed it!

Right now F2FS is an all or nothing kinda thing, if I remember correctly you need /data and /cache and /system either all as F2FS or all as EXT4. This is something I hope to solve soon.

I'm still pooped from last night, so I'm going to go back to sleep...
[Samsung Galaxy Nexus] dbt816:
A good place to start is here: http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655

A TWRP recovery that supports F2FS is in the first post and links are in the second post.
[Samsung Galaxy Nexus] Shadow Death:
It's actually very easy, but you WILL need adb installed. I know MWisBest has it installed but I don't know about terminal13. If you don't want to lose what's on your sdcard you need to back that up to a desktop or a laptop.

Then go to bsmitty's dirtyv kernel thread and scroll down to the bottom of the first post. You'll find smitty's custom TWRP recovery there for the toro.

Once you're done backing everything up put that recovery on your sdcard and flash the zip in recovery. This will overwrite your current recovery which means you will need to reboot into recovery. The recovery has an option for that.

After you reboot back into recovery you will need to go into Settings then check "Force data and cache wipe functions to use F2FS" then check the sub box "include system partition". Now you will want to wipe everything, and I mean EVERYTHING, Cache, dalvik, data, system, and sdcard. NOTE: THIS WILL WIPE EVERYTHING!

Once it's finished you will use adb to sideload the rom. At this point you will put your phone into sideload. I believe that is under advanced. You'll select sideload then slide the slider. Once it goes into sideload mode you will go back into your console or terminal.. depending on if you're on windows or linux. You will then navigate to the folder where you downloaded the f2fs rom. Once there you will type "adb sideload <romname>.zip". I think it goes without saying that you replace <romname> with the actual rom zip file name. It will begin to push the rom to the sdcard as sideload.zip (just in case you need that file for some reason later). After it's done pushing that it will install that zip like any other rom. Then you'll install your gapps and the kernel of choice the same way. Once that's done reboot your phone into android. Then copy your files back to the sdcard and boom.. you're converted to f2fs.

I know it's a jumbled up mess but I typed all this out in a hurry. There are faster ways of doing things like using adb to pull files from the sdcard to the folder of your choice on your desktop or laptop. And using adb to push the zips you want to flash to /sdcard/

The task it self is easy but explaining it can be troublesome.
[Samsung Galaxy Nexus] oman0123:
When I tried to flash the f2fs it errored out saying the updater script failed which means that it's not f2fs compatible if I'm not mistaken.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Shadow Death:
It worked fine for me.