yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mmuzzy:
Here you go :) http://xdaforums.com/showthread.php?t=2043869

Thank you. I haven't ruled out something like the Note for my next phone. My usage is tablet-esque and occasionally use the GNex as a phone so a large screen makes sense for me.

I love it. Since we don't have to worry about the carrier piece I think I'll actually get to enjoy just using that one more than the GNex.

Great idea. Thank you!

-------------------

I'll be working on upgrading my build environment and redoing my NAS box to be linux so I have two PCs I can build on. If I go silent for a bit this weekend I'm working on making things better for ROMs, that's all.

Happy Friday Everyone!
[Samsung Galaxy Nexus] Wartickler:
scandiun seems to have figured out something like that. I know he's mentioned it a couple times on my Internal Memory Data Recovery thread: http://xdaforums.com/showthread.php?p=34185439..

EDIT: Well I didn't see all the other posts before I replied to that (tnx XDA app) but there appear to be at least a couple ways to do this.

Any news on results?

Sent from my Galaxy Nexus

"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
[Samsung Galaxy Nexus] marker2002:
MMS not working for me

NEVERMIND... I just searched after I posted this and saw that others were having similar problems...

original message -

I don't get a lot of picture messages but last week I had a notification in my notification bar from a friend, when I clicked on his name it brought me to my texts messages but his name wasn't even in my list of messages. I didn't even think anything of it. Yesterday this happened again, different friend, this time I messaged him, (had to start a new convo because again he wasn't in my list of recent messages), he said that he sent me a picture. I didn't get the picture.

Has anyone else had this problem? Not sure if it's because it's the start of a new text/convo thread or MMS messages in general. I'm going to try to do some tests today with it.

I'm on the 12-08 build
[Samsung Galaxy Nexus] Wartickler:
*guffaws*

Sent from my Galaxy Nexus

"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
[Samsung Galaxy Nexus] mmuzzy:
What? I like that rule. ;)
[Samsung Galaxy Nexus] drizzt5:
It's a good rule... You could even get many owners of the device to chip in and distribute the cost.
[Samsung Galaxy Nexus] ohiomoto:
I agree. That's one thing I hate about Android. Some apps have to be exited from within the app while others can be swiped away. This is an area webOS ruled. If you swipe a card off of the screen, it's gone. No worries that it might still be running in the background. If the card is gone, then the app is not running. WYSIWYG! (And webOS muti-tasking still rules too. :) ) Android has made great strides since ICS was introduced, but this is one area I think still needs some work.
[Samsung Galaxy Nexus] mmuzzy:
I would never actively solicit money from people to buy a device but I will certainly be judging my next device on where the most people are heading. Mostly because this is a smart group and I know it'll probably be the best choice anyway.

Tiny pointed out that it wasn't actually killing the processes but merely clearing them from the recent apps list. I guess I misunderstood what it was. I don't use the feature but I see the merits.
[Samsung Galaxy Nexus] RW-1:
+1 ... I've had no SOD's or any other real issues with the 4.2.1 builds other than what we've worked on, or issues I created myself. the builds have been great!
[Samsung Galaxy Nexus] SparkyXI:
No real news on results yet. I have the bootloader locked back up, however I'm having a hell of a time flashing back to full unrooted stock without having a USB port. I feel like I need to find something flashable via recovery. I'm still on the hunt, and my new phone should be delivered today (I have 8 hours to figure it out). Any help is still greatly appreciated.

EDIT: By the way, I *am* able to connect with ADB via WiFi, however my problem is that when I reboot to bootloader, it kills the wifi connection. I've also tried Mobile Odin to no avail.

EDIT 2: I have a hunch that the reason Mobile Odin isn't working is because of the new SD filesystem (/0). That's just a hunch though.
[Samsung Galaxy Nexus] Wartickler:
Just a thought: try flashing an older factory image to avoid the new /0?
[Samsung Galaxy Nexus] smileyanz:
I'm not going to name anyone but there has been big issues on the latest ROM and if anyone has been following the top devs and also the tweets you will know its been really difficult right across the board. Gaming for instance, on a whole its still behind the 4.1.2 and 4.1.1 , ask any gamer and your get the same answer. Memory probs and battery drain is still largely an issue with kernels and Franco himself has issues with it and that's just a few. Personally I and many others don't think its going to get much better for a certain amount of people out there who use there mobiles for gaming etc..

Or perhaps it could be that we play with our phones to much and push them to far with over clocking !!!...Bring on the Roadrunner the next real upgrade to the jellybean. Think perhaps Google is getting ready for the switch but that's just guessing on my part!!!!
[Samsung Galaxy Nexus] billykxda:
I'll weigh-in on MMuzzy 4.2.1 ROM stability. I've been using it since it's release and I haven't had one single problem. No SOD's, no restarts, no weirdness whatsoever. It's a great ROM, for sure.

I run it on a VZW GNex with Franco's r344 kernel
[Samsung Galaxy Nexus] SparkyXI:
Interesting concept. Maybe I'll flash Muzzy's most recent 4.1.x and see what that does for me. Good call. Will report back.

Update: Well it seems that the unsuccessful use of Mobile Odin has borked my TWRP... More to come...
[Samsung Galaxy Nexus] ohiomoto:
Yeah and what's the point of that? So you don't have to look at what's draining your battery or so you simply forget what you left running? :) I never understood this.

Also, what the heck did I do in the post you quoted? It's all messed up. I'm surprised you could even read it!! LOL
[Samsung Galaxy Nexus] Wartickler:
Or perhaps...

Yet another suggestion: perhaps an older recovery that DOESN'T try to address the /0?
[Samsung Galaxy Nexus] tiny4579:
Move everything to /data/media from /data/media/0 and delete /0 and the recovery will point /sdcard to /data/media on the next boot.
[Samsung Galaxy Nexus] SparkyXI:
Problem is that I can't flash another recovery without a USB cable.

Trying this. Thanks.
[Samsung Galaxy Nexus] techspecs:
I assume it doesn't boot up right? Otherwise you can flash with goomanager.
[Samsung Galaxy Nexus] SparkyXI:
No, it boots up just fine.

History refresh - USB port is fried and I need to send back to Samsung. I have to return the phone to unrooted stock before I do so. Tried using Mobile Odin, which did not work, and seems to have jacked my Recovery. No issues locking/unlocking the bootloader.
[Samsung Galaxy Nexus] notstevek:
I have the newest touch recovery, even before updating it had the newest non touch because most roms required it for this reason. I made a new nandroid, that appears in recovery but not in the folder (even tried renaming it to muzzy and searched from / on and couldn't find it) only see the old one. The rom works perfectly so I don't care, thanks muzzy. Only thing I'd like is a 3g/4G toggle :)
[Samsung Galaxy Nexus] klobkelosh:
I'd fill in my details but, I confess, I have no idea how to edit Google drive docs.

I'll fill out two lines...one for my setup when having sod, and one with my current no-sod setup. Also, would you add a column for animation settings? Thinking that is the culprit atm

Edit- sorry I see you have animation there.
[Samsung Galaxy Nexus] SparkyXI:
So here's where I'm at. USB Port totally dead. Can't boot into recovery, CAN boot into fastboot. Phone boots up fine to the ROM.

I think my only saving grace at this point is to somehow be able to flash files through Fastboot somehow via wifi, or find a script that will do it for me on the back end.

Any other thoughts?

EDIT: Looks like Fastboot via wifi is not possible, by design.

EDIT 2: TWRP Recovery is back in place, thanks to Goo.im.
[Samsung Galaxy Nexus] adbFreedom:
Have you looked into using wug fresh's toolkit? I've never used it, but it may be possible through wifi?

http://www.wugfresh.com/nrt/
[Samsung Galaxy Nexus] SparkyXI:
Haven't gotten that far yet. My current thought was this: Flash an older bootloader and an older stock rom in TWRP and call it good.

Downloaded the toolkit, I'll see what I can do with it. EDIT: No love without a working USB port.

I know with 100% certainty that if I'm accessing the phone via ADB wirelessly and it reboots, that connection goes away. That's why I believe a backend script may be necessary.
[Samsung Galaxy Nexus] sonicboomin:
lockscreen widgets

Is 4 lockscreen widgets the max? i can't add after 4
[Samsung Galaxy Nexus] :
Shot myself in the foot there - I had set the darned thing to publicly viewable but missed the option for allowing it to be publicly editable (On first glance thought they would be one-in-the-same). Updated now, you should be able to follow that link and start editing cells on the fly.

4 would be the maximum, yes.
[Samsung Galaxy Nexus] factor0815:
I have only had one problem with this and all other 4.2.1 Roms. The Bluetooth stack! I can no longer see any song track info or artwork on my car's display. It worked perfectly on my previous Roms. I've read quite a few posts about it, but no answers yet. I can still make BTphone calls and stream music, and I get all the phone call and phone book info.
[Samsung Galaxy Nexus] mmuzzy:
I know the thread is a tad on the long side to expect to find everything but it has been answered before. The new stack, which I think they call Bluedroid, is a totally new stack from the original Bluez bt stack before it. It doesn't support AVRCP 1.3 like the old bt stack the 4.1.x ROM were patched for. In a nutshell, this missing AVRCP was what gave you your metadata.
[Samsung Galaxy Nexus] Cornflakius:
This ROM + Tiny's Kernel = Win.

He's fixed some issue with Deep Sleep and now it's beautiful.

Much better battery life for me now :)
[Samsung Galaxy Nexus] SparkyXI:
Tried this. Thanks for the suggestion, but it seemed to mess up the file system even more.
[Samsung Galaxy Nexus] ba_hamilton:
The only time I ever had SOD's was when I was on another kernel besides Tiny's and the default kernel. EVERY other kernel gave me SOD's. I don't even experiment with other kernels now.

My Nexus 7 is now rocking Mmuzzy's new Grouper rom. I've been Mmuzzified :cool:
[Samsung Galaxy Nexus] tiny4579:
Deep sleep != SOD. They're not the same. Cornflakius's post said I fixed deep sleep issues and you were talking about SOD's. Just checking to make sure you're aware.
[Samsung Galaxy Nexus] ba_hamilton:
Sorry my fault :o. Yes I know the difference. Sorry for the confusion. But my statement still stands. The only kernels that has worked for me is Tinys and the default.
[Samsung Galaxy Nexus] SparkyXI:
Ohhhhh-tay. I've successfully flashed back down to Mmuzzy's 090212 version (4.1.1 JRO03L). All I need now is a stock ROM to flash over that, since the 4.2 file system changes are no longer in play.

---------- Post added at 03:31 PM ---------- Previous post was at 03:22 PM ----------

Wondering if someone in the dev community would be so kind as to creating a couple of flashable files for me from the "mysid-imm76k-factory-98d21321" tarball (found here: https://dl.google.com/dl/android/aosp/mysid-imm76k-factory-98d21321.tgz): One that flashes the stock radios, bootloader, and stock recovery; and one more that flashes the ROM itself. Is that a difficult/time-consuming task?
[Samsung Galaxy Nexus] techspecs:
Whew. My next suggestion was to locate an area directly behind a car tire, place the phone there and go for a drive around the block to cool off. ;)
[Samsung Galaxy Nexus] tiny4579:
Since adb works over wireless technically you can flash everything in the zip with flash_image after pushing the files over adb in recovery. since you probably already have the latest radios you can skip them.
[Samsung Galaxy Nexus] SparkyXI:
Nooooo flash all teh things!

My thought now is that if I can get a stock image older than 4.1.1 onto the phone, it'll auto-update OTA, therefore getting me back to stock.

Persistence. :)

---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------

Wifi ADB in recovery isn't possible. Are you saying I can pull the ROM zip file from the tarball and flash that?
[Samsung Galaxy Nexus] BOY_:
Mmuzzy, had an issue come up after flashing Tiny's latest kernel last night that looks like it's a ROM issue. I'm on 12/8 and started having my battery run down crazy fast. Google Services was hogging almost 50% of my battery with most of it in keep awake. Turns out WiFi Optimization was on and soon as I turned it off, all was fine.

Can you shed any more light on WiFi Optimization? It seems like it decreases the refresh rate of the radio and that caused Google Services (particularly various syncing apps) to slam the battery. Not that I don't think it sounds like a great feature but when I had it on I got the opposite effect!

Perhaps you could default if to off in future builds? And along those lines, I wonder if people complaining of bad battery before you baked this in have checked to see if "report from my location" is selected in Map settings? This is another feature that should default off IMHO. Only an issue on a clean flash, but nonetheless, a likely culprit for unnecessary headaches.
[Samsung Galaxy Nexus] JkdJedi:
Amen dude!
[Samsung Galaxy Nexus] mmuzzy:
That Wifi Optimization is a 4.2.x feature which is on by default. It's nothing I added or configured differently.
[Samsung Galaxy Nexus] whozamazinka:
A question about 4.2

So, I know this question is completely off topic, and doesn't belong here. That being said, this is the 4.2 ROM that I'd like to install, and I've been following this thread for a few weeks now. I really appreciate the way that folks partaking in this thread respond to each other, and are committed to being respectful and helping each other out. Several people have said it earlier in the thread, but the mmuzzy thread is something special!

SO, that is why I am asking here (instead of 'general'), to basically direct the question to the good people of this thread. I mean mmuzzy no disrespect and am not trying to hijack his thread. In fact, I'm hoping he chimes in...I value his opinion. If one or two people answer, that would be lovely, and then we could get back to the business at hand: this awesome ROM! :)

Also, as far as searching the threads for this question before: Believe it or not, I have searched XDA and the wider internet, and haven't found anyone asking this particular question directly. Plus I want to hear from you folks, the ones that are using 4.2.

So, with that heap of disclaimers, my question:

Is the upgrade to 4.2.1 from 4.1.2 worth it?

Let me focus that question a bit with some additional data:

Currently I'm running 4.1.2 with all of the 4.2 apps.(camera, gallery, clock, gmail, keyboard) I want to upgrade to 4.2.1 because I like to be bleeding edge, but there are a few things that give me pause. For one, I dislike the 4.2 lockscreen.(minor, I know.) The extra pulldown settings menu is cool in 4.2, but I more or less have that with the CM widget bar, so I don't need it. I don't need the screensaver. The Gnex doesn't get HDR with 4.2, as far as I can tell from the comments.

With my limited knowledge of 4.2.1, the only reason to upgrade for me would be if it was faster, smoother, or had better battery life compared to 4.1.2.

For those of you using 4.2 (and in particular this ROM), are any of those things the case? Is there some other compelling reason that I might be missing? If not, it seems like I should probably just stay where I'm at, no? Spend that extra flashing time with my family instead?:o

Please let me know if I'm missing something glaring. And thanks for putting up with this mostly off-topic question.
[Samsung Galaxy Nexus] Wartickler:
I gotta say, after all this, that you really didn't have to go through all this. They are going to blow this phone away as soon as they receive it.... just sayin'.

Sent from my Galaxy Nexus

"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
[Samsung Galaxy Nexus] mmuzzy:
From what you've said you've already gotten most of the features you want and the big changes in 4.2 you don't like anyway. 4.2.1 is better than 4.2 was in a number of ways but it's probably not worth the initial headache at this point for you.

I had that thought too but I'd probably be trying to get it as stock as possible also for peace of mind. Or at least make sure it didn't boot up, by killing the battery of course.
[Samsung Galaxy Nexus] mcp770:
In response to Boy_ are you sure you were on the newest tiny kernel? 2.2.1 had a bad issue with deep sleep that was fixed on the redesigned 2.3.0. Since 2.3.0 on the same setup of mmuzzy I had instant improvement. Just curious because it sounds like you had the bad kernel.
[Samsung Galaxy Nexus] whozamazinka:
Thanks mmuzzy! I kinda thought that, but was just looking for confirmation from someone actually running 4.2.1. I don't know many people with a Gnex.:p

I appreciate your thoughts...thank you!
[Samsung Galaxy Nexus] klobkelosh:
Cells added...thanks for doing this. Let me know what you find.
[Samsung Galaxy Nexus] :
If I might jump in - the notification pulldown quick settings is one of the sole reasons I made the jump to 4.2.1 from the 4.1 build of Bugless Beast that I was enjoying. Some people have issues, others (myself included) seem to be extremely lucky and have had nothing but a smooth experience with the upgrade. If I were you, I'd make a backup of your current setup, install the latest recovery (either CWM or TWRP, whichever is to your preference), and give this ROM a shot. If you end up not liking it, it's just a simple restore operation in your recovery to go back to 4.1.

You're very welcome - I like looking at data. My only hope is that more people will also add to the list so we can see what some of the common factors may be, in order to give better troubleshooting advice in the future until Google can step in and setup some fixes.
[Samsung Galaxy Nexus] adbFreedom:
Someone asked for a volume rocker wake mod a while back and I'm not sure why that just popped into my head this afternoon, but I had some free time so if you are still around ... here you go. Built with 12-11 release android.policy.jar

https://www.box.com/shared/3j1z8qxb1wbpka3wpl6v
[Samsung Galaxy Nexus] SparkyXI:
So what's the possibility of using TWRP's command line function to potentially flash a stock tarball? Anyone?
[Samsung Galaxy Nexus] rustid:
I blew my speaker in my old phone somehow, and Verizon replaced it with a refurb. When I flashed it I would lose all data and voice connectivity all together. It comes back, but it can still be annoying. I called Verizon and they sent me another refurb to replace that one, and i just saw the empty triangle again a few minutes ago. I am in Portland, and we have very strong LTE here (30/10 mbps is not uncommon), but both of my refurbs have been losing signal on the 4.1.1 roms.

I was using the rom from 8-15 on my phone that doesn't lose signal, and I just flashed the 8-17 rom on this new phone. Other than that they are the same. I might also try different radios.
[Samsung Galaxy Nexus] mmuzzy:
In the first poster's case he actually had a hardware problem. After he got his replacement phone today it's been smooth sailing for him. Unfortunately we don't have newer radios than we had with the last OTA for 4.0.4 and the ROM doesn't contain any. So the poor signal would have existed before the flash and would carry into another. I hate to say it, but the fact it was a refurb and it's a known problem, I wouldn't say it would be out of the question the refurb has the same issue but I hope not.
[Samsung Galaxy Nexus] rustid:
Yeah, I don't think it is a problem with the rom by any means. I think it is just crappy hardware, and I will most likely request another phone if the issue presents itself again. I guess I meant to imply that it is probably hardware, since my phone with just the messed up speaker works flawlessly, other than the messed up speaker.
[Samsung Galaxy Nexus] mmuzzy:
I hope you get it straightened out OK. Refurbs can be a pain.
[Samsung Galaxy Nexus] pyroscott:
I went through 5 refurb phones before they sent one from Samsung apparently. It seemed to be new instead of refurbished. They kept losing sound in the earpiece.
[Samsung Galaxy Nexus] Testman08:
I am really enjoying your rom everything just works... :D thank you for sharing it. I do have a couple of questions... is there a way enable recovery access on power menu? And which file manager do you use?
[Samsung Galaxy Nexus] mmuzzy:
Ouch. I'm surprised they made you go through 5 refurbs before getting a new one. Glad it finally worked out.

Thanks!

I actually just added a MOD link to an Enhanced Power Menu in OP that I tested last night. As for file managers, I normally use ES File Explorer or Root Explorer. Either one will work for most things.
[Samsung Galaxy Nexus] seattlecard:
Okay - here is my review after ten days (running the second release of this ROM). Overall excellent, very pleased.

Here are the two issues I have noticed - might not be a ROM issue, but thought I'd see if anyone else had feedback:

1. Volume keys wake the device. Is there a way to turn this off so just the power button wakes the device?

2. I did not successfully receive an MMS message containing a picture yesterday. It said: "Message Size: 0KB null" and next to that, "Downloading" but never downloaded, no matter what I tried.

Anyway - thanks again, I plan to run this for a long time. Good battery life with the extended battery, plus franco kernel.
[Samsung Galaxy Nexus] mmuzzy:
Thanks :)

The volume keys shouldn't wake the device. I'm not sure if you flashed any mods where that might be a side effect but that shouldn't be happening. I have been receiving MMS messages as recently as last night. I've been getting a steady stream everything from pics of Vermont to the homemade pot pie my daughter made.

I believe you're on the 0515 version of the ROM. The reason I put out the 0817 was because of a couple things that I knew about that I wasn't happy with but there could have been other things I didn't catch too. I don't believe the volume keys waking up the phone should be happening on any release though.

I guess my recommendation would be if you're on 0815 release then please grab the 0817 version. Because of the unexplained behavior I'd probably recommend you backup your stuff and do a clean install. Sorry. I know that's a pain in the butt. However, I think you'll end up with a better experience. :)
[Samsung Galaxy Nexus] THE_SNOOK:
mmuzzy i like the ROM. its quick and responsive. Thank you!
[Samsung Galaxy Nexus] mmuzzy:
ROM Update

If anyone is feeling adventurous and wants to try another build of the ROM. I'm testing mostly backend stuff that makes the build go quicker but it also has the GPS lock tweak as well as the other fixes. Everything looks good to me but input would be appreciated before I update the OP.

Thanks :)

http://goo.im/devs/mmuzzy/ROM/toro_signed_082112_213223_test.zip
[Samsung Galaxy Nexus] samuelhadams:
I've noticed some duplicate ringtones and notification sounds.
[Samsung Galaxy Nexus] mmuzzy:
I guess it's pretty good if there aren't any functionality issues. Thank you. I'll take a look and try to get rid of the duplicates.
[Samsung Galaxy Nexus] johnfoam:
Been running this for several days now (rev 8/17) and all is working beautifully. Thank you for all of your great work! I hope you stick around and continue your development!
[Samsung Galaxy Nexus] mmuzzy:
Thanks, and thanks for using it :)

It's been fun for me. I'm learning a lot as I go and I'm looking forward to pushing things a little further as time goes on.