yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johnfoam:
Out of curiosity, are there any differences between your rom and mwalt's mrom? Seems like you guys are both going for the same type of experience - stock stable JB. I've not tried his yet, but was curious if the difference is just in the way that you guys compile the build or something else?
[Samsung Galaxy Nexus] mmuzzy:
I really can't answer what the differences are but I was say there would probably be a similar experience on either ROM since we were both going for the same result, yes. He and I have have PM'ed in the past and shared info. He's helped me with a few roadblocks and hopefully the other way around too.

I'm sure you'd be happy on either ROM whatever you decided to use. I'm glad we have a large number of ROMs to chose from. Having had phones that the dev community died off on, this is much better. ;)
[Samsung Galaxy Nexus] MarkGbe:
i noticed one issue yesterday. When connected to wifi, and when trying to upload a video via the youtube app, it doesn't get past "pending".

I looked in settings and found that If i changed the upload setting from "upload only on wifi" to "user any connection", it starts working immediately.

I confirmed that my wifes phone works fine and i flashed a different JB rom(mrom) and it works fine there as well.

Something weird going on?
[Samsung Galaxy Nexus] mmuzzy:
It could have been something with your connection at the time. There is also a setting in Wifi to avoid weak connections that might be ticked. It could be something going on with the app too. It could have been cache, permissions, etc. Unfortunately it's just one of those things where you could flash back to mine and it would work. No idea but there's nothing wrong with mROM so, as they say, if it works don't fix it.
[Samsung Galaxy Nexus] type_2:
I heard a lot of good things about this rom and would love to give this a shot, but I just had a couple of questions.

I initially flashed some other 4.2 rom but it didn't work out well then I flashed back to 4.1.2. The first 4.2 flash put everything in the sdcard/0 folder and then when I flashed back to 4.1.2, it made another copy in the regular sdcard folder. So my question is this: is there anyway I can wipe my sd card (don't care too much what's on there) after i install this rom and not screw anything up? My plan is to install this rom and backup my apps and what not, then wipe everything so that's there's no duplicates etc. Would that completely screw me up?
[Samsung Galaxy Nexus] erasable:
Anyone else having Bluetooth audio problems on the newest build? When I say problems I mean pairs, connects, but then no sound.
[Samsung Galaxy Nexus] whozamazinka:
Hey, thanks kmadengangnamguy!

(I've gotten a kick out of all the butchering as well.) ;)

I have thought that....that I wouldn't lose much time just taking a backup and then taking the plunge. And I do like that second pulldown. I already upgraded my recovery to the latest TWRP in anticipation, and took a nandroid. (All that talk of multiple '0' folders!) However, I was really comfortable with CWM, and while I really like TWRP, I guess I'm a bit gun shy now too that I might end up deleting everything trying to prep for a ROM install. I think I read that you go into 'wipe', and then just move clockwise in a circle wiping cache, dalvik, system, and then factory reset. Is that the proper way? (I know there are places on XDA where you can get this information, but it seems to vary so much, I don't trust it completely.)

Also, for a backup, do you just do system,data,boot,cache, and efs? I didn't have all those choices in CWM.

If I restore back to a 4.1.2 ROM, do I just move my files from the '0' folder back to the root? Or can I just leave them where they are?

Thanks kma...I feel honored to have both you and mmuzzy answer my question! I appreciate your time.

JR
[Samsung Galaxy Nexus] mmuzzy:
I've had very good luck as well. I actually really like 4.2.x overall. I don't push my phone as much as some do though. Well, I abuse it with flashing ROMs but that might also be why I don't have some problems.

I'd copy backups and nandroids off the phone to be completely safe. Then you can factory restore if need be to clean up the filesystem and not lose anything. (Sorry I thought I had answered this one because it was similar to the one below)

Nice! Thank you. :)

We do have users who other than the lack of metadata are using the BT audio with good success.

And I feel honor to have you using the ROM. ;)

My feeling on the files is to do a nice off the phone backup just in case something really bad happens. Then you can experiment to your hearts content with the files and know you can even do a factory restore to clear the filesystem completely if need be.

I'm sure kmagameguy (copy/paste) has his own method too though.

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

This weekend is going to be about hardware more than anything. I'm going to redo my NAS computer to be Linux based which will allow me to use 2 machines for building. I'm also redoing my source directories to make more efficient use of space as well as replacing the drive that holds it with a 1TB drive. As I find myself working on more diverse hardware and software projects my files were getting a little out of hand.

So if I don't post right away it doesn't mean I'm slacking off. ;)
[Samsung Galaxy Nexus] runandhide05:
Hey that post was a hole five minutes ago muzzy...slacker.

[/busten chops]

Have fun with that, and if u want to send me a 1t ssd too I'll take one.
[Samsung Galaxy Nexus] mmuzzy:
Nothing but the finest state of the art drives here, my friend. Oh wait... never mind, I forgot it isn't 2007. ;)

Plus I can't get past the fact that SSD drives have limited read/writes. I guess I still trust the mechanical drives more.
[Samsung Galaxy Nexus] Andrew025:
You'll generally never really reach the read/write limit in its lifetime. I've had an Intel ssd on full duty for over a year and the r/w lifetime is still at 100%.
[Samsung Galaxy Nexus] mmuzzy:
I didn't realize there was a way to tell that. That's good to know. Thank you.
[Samsung Galaxy Nexus] avlfive:
I've had this problem all along on 4.2. All builds. Not sure why.
[Samsung Galaxy Nexus] Wartickler:
OP OP OP!

Buahahaha!! :D

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 pretty much covered it all - make an offline backup of your nandroid just in case. Full disclosure - I've never gone back to 4.1.x now that I'm on 4.2 so I have no idea if going back will be as simple as restoring a nandroid or if the new folder structure will cause issues. I'm sure someone else around here can chime in with a conclusive answer. If you want to be safe when restoring back to 4.1, copy everything off of your sdcard and onto a computer, then wipe everything including sdcard from your recovery, and then just use adb or mounted USB to put the nandroid backup in the freshly wiped sdcard root directory and restore. Once you're up and running again you can just put all the files back on your sdcard.

Whenever I do a backup I usually just leave the default options - backing up everything can't hurt though. When you go to prepare for a full wipe just do cache, dalvik, then system/factory reset. The order shouldn't really matter much as each option (except maybe dalvik) are in different partitions on the internal memory. As long as you hit all of them, any order should be fine. I used CWM for the longest time (back on my OG Droid and for a good while on my Gnex until 4.2 first dropped), but I've got to say I've grown quite fond of TWRP. Being able to queue up zips to flash was enough to convert me, and I had always had a bit of wonkiness with CWM anyway that doesn't seem to exist in TWRP (Fixing permissions is ludicrously faster in TWRP than CWM). I think it will grow on you after a few uses.
[Samsung Galaxy Nexus] BOY_:
Yep, fresh kernel flash last night. WiFi optimization off = all good.

Mmuzzy, understood. In the off chance you can edit the setting, you have my vote, blessing, and encouragement to do so ;):)
[Samsung Galaxy Nexus] jcmm11:
So I tried xenon, just for the hell of it (back on here now). But I noticed that the quick settings there had both a sync and lte toggle. Since he credited kevdiu I'm wondering if there's any way we could get those toggles on here. That is about the only thing I'd say I'm missing.

Yes I can work around it, but it would be real nice not to have to.

Still love this ROM. The only thing that may pull me away is minco, once the next version is released. We'll see. Depends on exactly what they do with it :)
[Samsung Galaxy Nexus] mmuzzy:
Strange optimization if it has the opposite effect.

I think they expanded that on their own beyond Kevin's toggles but I'm not exactly sure.
[Samsung Galaxy Nexus] bunklung:
I just flashed this rom.

Anyone noticed they get a data error with the weather channel app?

Right now that's the only thing that seems broken.

I tried all sorts of things with the app, but could not get it to work.
[Samsung Galaxy Nexus] BOY_:
Right?!?!
[Samsung Galaxy Nexus] techspecs:
Like the scroll cache making scrolling chunk up...
[Samsung Galaxy Nexus] artjef:
Try removing and reinstalling from Play. I have had to do that with Weather Bug occasionally.
[Samsung Galaxy Nexus] mcp770:
Ahhh gotcha. I turned that off right away first time I flashed because people were hating on it. Good to know they were right.
[Samsung Galaxy Nexus] SparkyXI:
Okay. Thanks everyone for dealing with my crap - sorry to halfway thread-jack here. You guys are a ton of help, which is why I came here with my questions first.

Here's how my situation ended up: I was able to get Mobile Odin to work, which got me back to stock 4.0.3. However, I forgot to lock the bootloader first (derp), and it seems the stock recovery is borked. At this point, I'm over it, and it's in a box ready to be shipped back to Sammy.

New phone is on, charged, and ready to root/unlock/Muzzify.

Thanks again for all your help, friends.
[Samsung Galaxy Nexus] bunklung:
I tried this, no luck. I get a "problem receiving data" error.

Tried Weather Bug and it worked! I guess I will stick with Weather Bug. Thanks.
[Samsung Galaxy Nexus] italiano1964:
I apologize if this is off topic or has been already discussed in a previous post. I am on the latest mmuzzy and have been updating regularly to every new release. I noticed a little while ago that I am unable to access the music section in the Play Store and therefore cannot purchase music within the Store. It's just nowhere to be found. Any ideas? Am I missing something? If I use Sound Search to find out the title of a song, I get the option to purchase but have to do it through the browser because the Play Store option comes up with nothing.

Thank you for your help.
[Samsung Galaxy Nexus] mcp770:
Assuming you haven't installed anyone else's gapps or a leaked play store apk... try going into phone settings apps all and clear the cache and data for the play store app then see if it's back.
[Samsung Galaxy Nexus] gt5oh:
So far changing the Animations speed back to .5x has stopped the SOD problem I have been having..
[Samsung Galaxy Nexus] italiano1964:
No, I haven't installed anything. It's pure mmuzzy. Thank you anyway, but your suggestion didn't work. I wonder if I should try a complete wipe and re-install the latest from mmuzzy.
[Samsung Galaxy Nexus] klobkelosh:
I'm gonna turn mine back off. if I start having SOD again, I'll flee a bug report with aosp. Thanks for helping diagnose

Of course, someone already did: https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=40019

Please star the issue if you have the SOD issue and can confirm animations add the cause.
[Samsung Galaxy Nexus] SparkyXI:
Woot. Back in action.

A question: is there any reason to leave the bootloader unlocked?
[Samsung Galaxy Nexus] blempka:
Anybody else having trouble with wireless tethering? I know third party apps still haven't been updated for 4.2 but native tethering only seems to work for computers. I can't seem to get my Vizio costar or Xbox to work with it. Any ideas?
[Samsung Galaxy Nexus] buddyfriendo:
Changing the animation speeds is whats causing this? I've had them on various kernels and I always have mine set to 1.5, I wonder if that was the problem.
[Samsung Galaxy Nexus] techspecs:
The process wipes the phone so if you think you might tinker again in the future you may want to leave it unlocked. Mine stays unlocked.
[Samsung Galaxy Nexus] klobkelosh:
It's the best candidate so far...add long as mine are set to .5 or 1x I don't have SOD problems.
[Samsung Galaxy Nexus] buddyfriendo:
Interesting! Definitely gonna give it a whirl for the next 24 hours, I miss using trinity.
[Samsung Galaxy Nexus] simonmiller1:
Please forgive my possible overlooking of obvious info, but I've only been on this rom for a week or so. I'm on the latest build, and was having really horrible battery drain. I saw something about the WiFi Optimization and also flashed Tiny Kernel 2.3.0. Is there anything else I'm missing? I haven't been off the charger long enough to tell if this helped, but I figured I'd post this and maybe get some additional info.

Thanks in advance
[Samsung Galaxy Nexus] mcampbell:
Turned it back to 0.5x from what?

I was getting SOD's on "off" setting, but now am on 1.0x and so far ok, but they're so transient it's hard to say if this was it.
[Samsung Galaxy Nexus] Wartickler:
Don't worry about it. You'll never hear from that phone again (:

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] mcampbell:
Try 1.0 or 0.5. This is still a bit of voodoo and snake oil, but people are having luck with it.
[Samsung Galaxy Nexus] Wartickler:
Do you ever intend ever to ever flash ever again ever another ROM ever? Then don't relock your bootloader...ever.

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] jamontoast1291:
I saw the mods, but was hoping to find one that included a transparent status bar. I've seen the mod for other mods, but I'm not really familiar with this kind of stuff to compile them myself. Also, is there an easy way to change the color of the status bar icons? Basically what I wanted to do was make the signal icons and clock white and transparent status bar. Are either or both of these possible?
[Samsung Galaxy Nexus] mmuzzy:
I'd grab the app Better Battery Stats or something similar to try to figure out what's draining it but those two things are a good start.

That's a good question for our resident MOD experts kmagameguy or adbFreedom. I'm sure anything is doable but I don't know if they'd consider it easy or what they might recommend for getting it done.

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

On another note:

Hard drive is replaced. I now have 675GB free instead of 20GB. That'll help. Thankfully Parted Magic got it done without losing anything and allowed me to sneak to North Conway with the family today while it cooked.
[Samsung Galaxy Nexus] adbFreedom:
Just to be clear, do you want the pulldown where the notifications are to be transparent or the actual status bar where the time/signal/battery are? Either way, I can handle it for you. I also saw willyjay popping up lately in this thread and he has his own stash of nice mods he can bring to the table
[Samsung Galaxy Nexus] mmuzzy:
Thanks adbFreedom as always! And holy cow. Another amazingly talented person. I've used his mods on other ROMs. How cool is that? :)

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

On yet another note...

Redoing my ROM source to try to consolidate things. Too bad I didn't do this when I actually needed space. This will allow me to more easily match ROMs across platforms (phew). So if I break things, I'm sorry. I'll be running the ROM first to be sure it won't be painful and obvious in the unlikely event it happens.

The first test will be to add the 'clear all' button to the recent apps menu. It seems pretty harmless to add...

Edit: and maybe a the screenshot option in the power menu too
[Samsung Galaxy Nexus] SparkyXI:
I'm still campaigning for a notification LED settings mod. There. I said it. :)

Being unrooted and off of this ROM had me going through withdrawls there for a few hours.
[Samsung Galaxy Nexus] mmuzzy:
Welcome back :)
[Samsung Galaxy Nexus] SparkyXI:
Thanks buddy. Good to be back. The wife and I have been talking about getting a Nexus 7 soon. Glad to see you messing with that as well. You know I'll be flashing if we get one. :good:
[Samsung Galaxy Nexus] mmuzzy:
You'll love it. I'm glad to hear you'll be staying with us over there too. :)
[Samsung Galaxy Nexus] SparkyXI:
I have no doubt. ;)
[Samsung Galaxy Nexus] mwalt2:
Not necessarily. You can use an app in play store called boot unlocker for nexus devices. It locks by changing the bits in the code directly with no wiping on unlock. It's more secure if you also use the stock recovery and USB debugging off. That way some one will have to unlock the bootloader via fastboot and wipe your data in the process if they want to get into your locked phone.
[Samsung Galaxy Nexus] AlpineM3:
How's this running for y'all?
[Samsung Galaxy Nexus] nitsua98:
Running like Forrest gump.
[Samsung Galaxy Nexus] Sethnelson1:
this ROM is amazing and stable. I recommend running Tiny's kernel. then download trickster modgreat battery life from the market and apply boost settings in the interactive governor settings portion. Simply amazing.
[Samsung Galaxy Nexus] mmuzzy:
lol!

Thank you. I love Tiny's kernel. Good stuff.

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

Added a couple small things while testing things out after installing the new hard drive and consolidating device source. Screenshot function in the power menu (CM) and the clear all feature in the recent apps menu that Tiny pointed me to in the CM commits. That's what you're supposed to see in the second attachment, not the bug eyes from the Amazon app of the day. ;)

I'll upload tomorrow morning after I'm sure I haven't forgotten to test something, which I'm prone to do at 1:15am.

Night guys.
[Samsung Galaxy Nexus] solarpolitiks:
I had a similar problem to this on my last gnex but that one had a definite hardware problem and since this time it occurred on this ROM I figured I'd post here.

This was the first ROM I installed on my Galaxy Nexus. Essentially I got my GNex day one and updated it to 4.1.1 stock. I then took the toolkit and one click rooted the device unlockin the bootloader, installing CWM Touch, etc. I loaded this ROM up on to my phone and installed. I obviously wiped data, cache, dalvik, I even formatted system before flashing.

I ran this ROM with no real issues for about 2 or 3 days but today I get a text and as the notification plays the phone slows down to the point where I go to drag the notification bar down and it doesn't move. I hear a click and the phone reboots.

After this, the phone just doesn't function properly. I reboot and the text notification comes back on (As I didn't get a chance to read it before it rebooted) and the phone stalls and reboots. It just does this over and over. I had already deleted the ROM off of the phone so I couldn't reflash it or anything so I figured the next option would be to flash to stock. I open up the tool kit and download the Verizon google stock image and flash it and let it format the Userdata before flashing over the image. I relock the bootloader while I'm here too.

It goes to reboot and still has the same issue. It reboots probably 3 or 4 times with a couple of battery pulls in between until I finally get it running long enough to get past set up.

After getting it set up I get crazy slowdowns and reboots UNTIL I disabled all notification and touch sounds. Now it runs smooth.

Again, this might not even be ROM related but it did happen on this ROM and this is the only ROM I used since rooting the device. If we can't find a solution the device is completely stock and I can call in for a replacement but maybe there's a reason this is happening.
[Samsung Galaxy Nexus] dmoney2005:
Ok so I must have missed this but does anyone still have the email vibrate issue? How do you fix?
[Samsung Galaxy Nexus] SparkyXI:
Are you going to add the screenshot thing as a mod? You should add this as a mod. :)
[Samsung Galaxy Nexus] Amin Sabet:
I love this ROM and Tony's kernel. When I use Trickster's mod I see settings for boost and input_boost. Should I set both of those to on? What do they do?
[Samsung Galaxy Nexus] RW-1:
Hi Muzz, I agree, the screenshot option to the power menu should be a mod, not baked in. The OS already has a default method for obtaining a screenie that is not obtrusive IMO.

I could go for the clear all, as long as it doesn't muck up the works, or my Zenyth softkeys :)
[Samsung Galaxy Nexus] :
Prepare for it. The clear-all would conflict with all softkey mods. You're in good hands though - adbFreedom looks to be back on the case and with willyjay popping in once-in-a-blue-moon you could probably poke either of them to update mods.
[Samsung Galaxy Nexus] d11dog11:
What do the boost settings do?
[Samsung Galaxy Nexus] klobkelosh:
I concur

---------- Post added at 10:21 AM ---------- Previous post was at 10:19 AM ----------

Would you consider baking tiny kernel into this rom? That would be the bomb, and its pretty much stock kernel if you don't mess with settings.
[Samsung Galaxy Nexus] mmuzzy:
Point taken. Thanks for the input as always everyone.

Yeah I was aware of that and afraid of that too. :\

Thankfully you guys have my back.

Yes I would. Tiny has been very active in the thread and a huge contributor of fixes. But, having said that, we would continue to be moving away from stock with a non stock, albeit superior kernel.

Thoughts?
[Samsung Galaxy Nexus] Wartickler:
Just started yesterday. Phone is plugged in overnight and doesn't charge. Wake up this morning and notice. Try two other chargers and nothing so it's not the charger. Reboot while plugged in. Upon boot phone shows charging. Unplug charger and phone is still showing charging. Stops showing charging after ~2 minutes. Plugged back in and shows charging. Unplugged and stops showing charging. Seems to be back to normal for now.

Phone State

Toro

MMuzzy (12/8)

Tiny (2.2.1)

kmagmalavahot BackMenuHomeRecentSearch mod

runandhide05 5x4 w/rotation

wartickler 5 dots Lights Out XML mod

No new apk's for a couple weeks

Stable for as long as I've been on MMuzzy (11/16)

One note of interest: I'd never actually seen home screen rotation until this morning which could be a clue...

Possible reasons? Go:
[Samsung Galaxy Nexus] factor0815:
Bluetooth

Do you think there will be a fix, or do you think I'm s.o.l. on getting the metadata? I know a lot of vehicles use the AVRCP 1.3 protocol. I can't understand why this hasn't been fixed already.
[Samsung Galaxy Nexus] mcampbell:
Sounds like a defective USB port.
[Samsung Galaxy Nexus] margelef:
According to the Google bug report here http://code.google.com/p/android/issues/detail?id=35737 the issue is fixed in 4.2. However I still experience it on the latest TOM. If I'm paired with the car and no audio is playing, voice search won't initialize.
[Samsung Galaxy Nexus] SparkyXI:
Whoa, man... be careful. This literally just happened to me. My USB port ended up frying itself. I was able to get Sammy to replace mine, because I was in warranty. Remember all the crap I've been asking about on the forum a few 10 pages back? This was why.

Are you in warranty? If so, have them replace it. Please heed this: While your USB port still seems to work for data, go back to unrooted stock ASAP. You may not get the data port functionality back, and you'll hate yourself for not having it.

Are you out of warranty? If so, I ordered a new component USB ribbon cable to repair mine, but they gave me a new phone instead. This leaves me with a ribbon cable I won't use. I could repair your phone for you on the cheap.
[Samsung Galaxy Nexus] BOY_:
Alright Mmuzzy, I'm in crack flash mode. Can we expect an update today?