yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mcampbell:
Some phones like some kernels better than others. Mine *hates* Franco's. Have never had any luck with his. Lean, Tiny, Trinity... fine. Franco's... always bad.

For me; others have great luck with it.
[Samsung Galaxy Nexus] standupdad:
Thanks for the reply. I'm not on latest, so maybe that's part of the issue. I've gotten PM's stating that they got the alert, so maybe its time for a clean wipe and update to latest FV.
[Samsung Galaxy Nexus] RW-1:
Cell broadcasts working here in PA, weather and Amber Alerts.

I suppose it is a sad commentary if we are receiving a lot of those lately eh?
[Samsung Galaxy Nexus] KnappyRoot:
I am in SW OH near Cincy and I received it this morning. I am on 3/7 build. As you stated in a later post from above, it might be time to update.

I wish it would save it as a text message though cause once I clicked ok I can't pull it up again.
[Samsung Galaxy Nexus] xolanir:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I can also attest that my GW is in good working condition, well at least on the part that I haven't done anything while flashing any of Muzzy's to bork the secure element (knock on wood). I've not had the opportunity to use it for purchases through NFC, just through the play store. I ALWAYS do a clean flash between ROM's, and then restore from a nandroid backup. Anyone else see anything different?
[Samsung Galaxy Nexus] standupdad:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Thanks, especially for replying so close to me.

Also realize that I'm only a week behind on FV, so this may have been an issue for a long time and just didn't know it... or maybe I broke something on a recent update.

Thanks again folks. I'll be updating tonight.
[Samsung Galaxy Nexus] ohiomoto:
I am in NE Ohio and I go the amber alert on my phone from WV. Think it was last night.
[Samsung Galaxy Nexus] jesta192:
I can confirm that the broadcasts have worked for me recently, at least in a slightly older build. I received a tornado warning about 2 weeks ago (my wife and a coworker did also with different phones). I'm on 2013-02-17.
[Samsung Galaxy Nexus] mwalt2:
It is an accurate statement in some cases. Awhile ago I decided to flash a CM rom from a stock/rooted google rom and forgot to reset the google wallet app. After that, wallet has never worked again on my phone. I had probably flashed 50 roms too, but they were all aosp based or google-image based ones that I had 'made'. The one time I decided to try something different, my secure element quit working for google wallet.
[Samsung Galaxy Nexus] mmuzzy:
I absolutely agree that it can happen. I have seen plenty of posts where people have either had it happen to them directly or received replacement phones with non working secure elements... most likely the reason the phones were turned back in the first place.

edit: as I understand it you consider it like a tamper proof self destruct. we are talking about a money element after all.
[Samsung Galaxy Nexus] dwilliam16:
Never received an alert for weather or amber. 3/07 FV. I would be interested in figuring it out.
[Samsung Galaxy Nexus] johnco1972:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

The strangest thing...

I wiped my dalvic on a whim (was having issues with an app, for some reason I thought that might help). Now I cannot get a GPS lock at all. Was working perfectly before the dalvic wipe. I mean literally a few minutes before I did the wipe.

Also, I have never received notices for amber alerts or storm warnings. I know the setting is turned on. Maybe there aren't any in my area...
[Samsung Galaxy Nexus] Kyle C:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Just realized today, for the first time, that my photosphere isn't working. Bummer. Haha

Edit to comply: Most recent French Vanilla build (3/7?)

Tiny Kernel (stock settings)

Volume button shutter release mod (hasn't been an issue in the past, but could be the culprit)

Themed MMS

Honestly it really isn't an issue for me, personally. I went to use it for fun, it didn't work, so I set my phone down and enjoyed the view all the same. I love this ROM, something like this won't cause me to leave.
[Samsung Galaxy Nexus] RW-1:
Mine works just fine (taking, and viewing and panning within it) though no camera shutter on taking the photos within it, which I don't mind.

Please, if you are going to post that something doesn't work, you MUST give more details, such as the build, kernel in use, any mods in use, add ons for camera if used in this case, etc.

Example: I'm on 3/7 with included kernel, no mods that would possibly interfere (I only ad a softkey mod to this)

Thanks.
[Samsung Galaxy Nexus] Frixtion:
Photo Sphere all good over here. Theme&Mod: adbfreedom's 3/1 blacked out theme and volume rocker wake mod and the kernel that came with the ROM.
[Samsung Galaxy Nexus] Kyle C:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I updated my post with info...

I'll probably wipe and reflash sometime tonight, bored as hell at relatives house. As said in previous post, I'm not worried.

Different question; On a previous Vanilla build, possibly 2/17, my battery life was THE best I've ever seen. Period. I then updated/graded to a FV build. Battery life took a small hit (however, still better than any other ROM/Kernel combo I've tried), is that common going from V to FV?
[Samsung Galaxy Nexus] mmuzzy:
The differences between the two are pretty minimal. I'm surprised that you notice a difference at all actually. They're even running the same kernel. I hope the reflash clears up the camera issue. Good luck. :)
[Samsung Galaxy Nexus] DirgeExtinction:
So, if I'm on French Vanilla 3/7, I just flash adbFreedom's theme in CWM recovery?
[Samsung Galaxy Nexus] georgeascott:
I don't know what I did earlier. All of that deleting and flashing.. I finally got it working as I mentioned in my last post, but now I have no way to transfer files from the pc to the phone. I've uninstalled and reinstalled the drivers over a dozen times with full restarts in between. My gnex refuses to show up in device manager at all though. I realize (and apologize) that this isn't directly related to the wonderful rom here, but the community here has been of such help in the past.

the phone will charge either from the wall or the computer, but no matter how i tinker with it and usb debugging or mtp, ptp, permissions, mounts, i can't get the phone to display the debugging bean or the computer to pick up the device. at all. you smart people have any directions to point me in on this one? hell, i'd even settle for wireless adb if i'd ever read anything good about it. adb devices isn't showing offline either so it's not the new white-list, it's just not showing anything. all of my searching has thus far has just directed me to reinstalling drivers and the 4.2.2 whitelist, i've investigated the usb connector, it's firmly seated with no corrosion, just to be safe and air dusted it, tried different cables and pcs.(win 7 and win8) i'm just clueless here. to make matters worse, i can't confidently wipe it all again because i'm not sure i can put any files back on it once it is done.
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yes

airdroid works well for me and doesn't even need drivers.

Send from my phone.
[Samsung Galaxy Nexus] runandhide05:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Drop box is always an option if your just needing to transfer files.
[Samsung Galaxy Nexus] georgeascott:
thanks for the quick reply guys, I'll look into airdroid. i'll keep messing with it too, going to try rolling back a build and see if my results are any different. i mean.. it's only spring break and i'm too old for fun stuff...
[Samsung Galaxy Nexus] djquick:
Funny you say this because I had the same problem a couple weeks ago. I decided to do a low-level format on my hard drive, then just reinstall Windows 7 from scratch and build on it from there. now all my USB ports work like a charm when I plug in any device.
[Samsung Galaxy Nexus] nitsua98:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

If you have fast charge enabled your phone won't show up as a phone if that's what you did.
[Samsung Galaxy Nexus] mmuzzy:
Good point. I keep forgetting about that. Thanks.
[Samsung Galaxy Nexus] jpinsl:
Install the app ES File Explorer from the Play Store. It can transfer files over the network or WiFi from LAN, Dropbox, Google Drive, Etc.

Also install AROMA File Manager so you can manipulate files from recovery if needed:

http://xdaforums.com/showthread.php?t=1646108

Good luck!
[Samsung Galaxy Nexus] mmuzzy:
ROM Update

March 15, 2013

- Updated Quick Settings Tile MOD (http://xdaforums.com/showthread.php?t=1999125)

- Fixed Korean language dialpad

- init.d support

Happy Friday :)
[Samsung Galaxy Nexus] RW-1:
Curse you! :)

I was going to relax ....
[Samsung Galaxy Nexus] mmuzzy:
Let me guess, the Korean dialpad fix sealed the deal for you? ;)
[Samsung Galaxy Nexus] t1n0m3n:
As a Korean hardcore gangsta rap artist, I thank you.:cowboy:
[Samsung Galaxy Nexus] RW-1:
Riiight..... ;)
[Samsung Galaxy Nexus] Kyle C:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yay for updates!

On another note; is this the error that you receive when your secure element is trashed? If so..... Damn it..
[Samsung Galaxy Nexus] gakirby:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Anyone else getting told to update superuser binary again after the 0315 build

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kyle C:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I get that notification almost every time I reboot my phone...
[Samsung Galaxy Nexus] artjef:
Aw shucks! I was going to go with my wife to the mall and shop. Now I have to tell her I cannot go because Mmuzzy says I have to update my phone.:D
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Oh Muzzy. A Dev slipped me an advanced copy of a highly anticipated next version of a rom several days ago . I am flattered and excited. But yet all I want to do is try your latest build here. It is honestly the best I've found overall for my Gnex. And it keeps getting better thanks to you and this community. For the hundredth time, thank you sincerely for your efforts.
[Samsung Galaxy Nexus] RW-1:
Ok mmuzz ...

Backed up and dirty flashed. Then gapps, then zenyth.

Something is wrong, quick settings.

First, if I long press settings, I get "unfortunately System UI has stopped". Hit ok, and I'm back.

I still had my tiles that I had previously.

However, going into the quick settings app, if I uncheck all of them, (and I see he has made some changes, though not really explained in the thread), and click apply, (allow thru superuser), however the same tiles remain.

So it appears that something is afoot, especially on the long press of settings tile, and the fact I can't effect changes.

Not anything that will kill me here, nor anyone else I suppose, but worth reporting.

(GPS is fine so far too, shhhhhhh...... :) )
[Samsung Galaxy Nexus] mmuzzy:
Dirty flash might be an issue with the quick settings apk. The old apk is QSCP.apk (not used anymore) and the new one is QSM.apk. It sounds like quick settings is confused. The new app has extra checkboxes for the new slidebar, etc.

EDIT: Also, the framework is changed so using the old MODs will most likely be a no no. Sorry. :\
[Samsung Galaxy Nexus] RW-1:
Well, let's see, in /system I only have the QSM.apk, and in the app I have the Brightness and Volume Seekbar option.

If QSCP.apk as elsewhere, where would I look?

Do you think the softkeys would cause this? I'm not sure, but no graphics glitches, etc. on them.

All the other tiles function, just no changes, even after a reboot.
[Samsung Galaxy Nexus] mmuzzy:
I do think it can cause it. The soft key MOD is overwriting a lot of the changed xml files, etc, from the updated MOD. Try dirty flashing without the MOD.
[Samsung Galaxy Nexus] RW-1:
Ok, will go back and reflash the ROM and gapps alone ... Be back shortly.

UPDATE:

Darn, you're spot on mmuzz ... the softkeys were doing it.

Right on reboot I could see the new swiper screen, and long pressing the settings is good.

Ok WillyJay, I need my Blue Zenyth Softkeys! Wah Wah WAAAAH !

(Yes, I'm crying, the stock white is SOOOOO Fugly! :) )
[Samsung Galaxy Nexus] mcampbell:
Yeah, I don't get it quite that often, but way more than I'd like. Kinda miss the old su.
[Samsung Galaxy Nexus] standupdad:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

deleted my link

Trashed my Wallet once... this saved me, so I posted it when I figure how to recover. Have NOT had an issue since. Several upgrades since and always okay.

[EDIT] Because of me borking up my clean flash shortly after writing this, I found myself in this situation again. How did I get around it? I surely didn't go back to my link. I tried something different.

I went into Titanium > Batch Actions > Manipulate Data > Wipe data for user and system apps > Deselect all > Selected Wallet > Tapped on the check mark to start the process.

Went back to the Wallet icon, tapped it, and viola. It set itself back up with the phone's new ID.
[Samsung Galaxy Nexus] ba_hamilton:
Can someone please provide an alternate download link? The goo links don't seem to be working.
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

It seems ok now, at least through goo.im manager.

Send from my phone.
[Samsung Galaxy Nexus] ba_hamilton:
Thank you. It wasn't working still and I remembered that I'm on wifi 90% of the time so I turned off wifi and the download is working over 4g. It wasn't working from my PC but my PC is also on wifi. Must be something wrong with my wifi signal.
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I use esfile explorer already. But it won't help me at all if I wipe everything and don't have a system to install it on and can't adb push.. Twrp has a file manager built in, is that similar to aroma?

Rolling back to the 3.06 build didn't help, unfortunately. And I can't bring myself to wipe my PC in the middle of the semester. But I'll uninstall the USB card and all of its drivers see if that does anything. Thanks again for the suggestions.
[Samsung Galaxy Nexus] Frixtion:
Assuming your running windows, maybe try to restore your system to the latest working point.
[Samsung Galaxy Nexus] RW-1:
Hi gang, what a depressing morning ....

No Zenyth Blue .... :)

Worse yet, I'm in the midst of a Dell Streak 7 Tablet search, I got it for my daughter 1.5 years ago, and she was loving it, it may have been in my car (which I do keep locked and most of the time it's in the console storage unless she is using it).

Searched the house, nothing, searched the car, nothing.

Damn. I'm heartbroken, don't know when I'm going to be able to get her a replacement.

Wife is talking about making a claim on the house insurance, but I don't believe that will fly.
[Samsung Galaxy Nexus] nitsua98:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Get a nexus 7
[Samsung Galaxy Nexus] nighthammer:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Then you could run MMuzzy on it too!

Sent from my Galaxy Nexus running MMuzzy's Jelly Bean 4.2.2
[Samsung Galaxy Nexus] RW-1:
That's the plan, I was thinking the 10, either way though we just don't have it with bills piling up...
[Samsung Galaxy Nexus] jon9314:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

What devices does mmuzzy's ROM run on? Any chance the Asus tf300t?

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] Unzitron:
Here is the TF300 forum on XDA. Check here http://xdaforums.com/forumdisplay.php?f=1582

---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------

As soon as Asus stops sending out OTAs for My TF300T I will be frequenting this page a lot, but for now I am rather happy running 4.2.1 stock ROM.
[Samsung Galaxy Nexus] jpinsl:
Don't make an insurance claim. First off, your deductible is likely more than the value of the claim. Second, multiple or frivolous claims will get your policy cancelled and you will end up paying thousands more to find coverage once cancelled.
[Samsung Galaxy Nexus] pennjersey83:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Just want to let you guys know that Willy Jays 1% text battery mod (3-1-2013) breaks the quick settings tiles. Later guys
[Samsung Galaxy Nexus] barry99705:
PM me if you're interested in an HTC Flyer for really cheap. Mine has been sitting on a shelf since I got my Note2.
[Samsung Galaxy Nexus] mmuzzy:
That sucks, Marc. I hope it turns up.
[Samsung Galaxy Nexus] RW-1:
Thanks guys, interestingly enough, while we had just put a swing set for her this year on layaway, my father in law just told my wife he wanted to buy her one, gave her $700...

What a weekend. I hope it turns up too, my fault, must have left it out on the seat, but don't ever really forget to leave it unlocked. I'm hoping I'm wrong and we find it. I had gotten it for $100 from a friend and it served her well...
[Samsung Galaxy Nexus] deadpixell:
I tried to update to just the new tile mod but now I get this lame blue highlight. Any chance mmuzy you have the quick tile setting zip from the update previous to the 15th? I'd rather not dirty flash to the new one but if I have to I will
[Samsung Galaxy Nexus] mmuzzy:
I'm not sure what you're asking for. You can't use the MOD from Kevdliu's thread on the FV version of the ROM anyway. If you're running the latest version of the ROM it's already in there.
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I think he wants the version before the recent update.
[Samsung Galaxy Nexus] mmuzzy:
I think the easiest thing would be to just flash the last ROM before this release then.
[Samsung Galaxy Nexus] deadpixell:
Yep okay that's what I was asking (not running the FV version). thanks mmuzzy, still the best rom :)

edit: just gonna flash the build I'm on!
[Samsung Galaxy Nexus] mmuzzy:
If you're not running FV you shouldn't have gotten the blue tiles. If you've flashed other MODs that also mod SystemUI it might cause that though.

EDIT: Here is the original Kevdliu Quick Settings MOD that I had patched up for unmodded JDQ39 4.2.2. This might be what you were looking for: http://d-h.st/u8P
[Samsung Galaxy Nexus] standupdad:
Borked up my clean install

Borked up my clean install of 3/15 due to being distracted with my psychotic kids. Needless to say, I have TWRP, but no OS. Looking for an easy and effective method to recover. "sd card" is blank

Even if I have to roll back to stock to go back to mmuzzy, its good. Just need my phone back.

Thanks in advance,

SuD
[Samsung Galaxy Nexus] kmcrane:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Otg cable and usb drive? That's how I flash roms...
[Samsung Galaxy Nexus] jcmm11:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

If you have TWRP just connect with adv push the ROM and install. Or you can sideload it. http://teamw.in/ADBSideload
[Samsung Galaxy Nexus] Frixtion:
If you have a computer and can connect gnex to it try downloading 3/15 to PC create a download folder on SD and paste 3/15 there in. Just a suggestion sounds easy enough will it work I don't know. I wish you luck
[Samsung Galaxy Nexus] mmuzzy:
It could be something like Google Now or something to do with location services. Even with GPS off it'll try to work with the cell signals.
[Samsung Galaxy Nexus] BOY_:
didn't think about Google Now... that's probably it. I have lots of appointments scheduled and Google Now is keeping tabs on it. TY.
[Samsung Galaxy Nexus] ianflo:
I have a question I'm hoping someone can help me with. It may be something with my particular phone cuz this is the second rom ive had where the same thing happens.

when im running navigation, the voice output works at first but doesnt say street names, and then after maybe the first turn or 2, it no longer says distances correct either, instead simply repeating 3x "in 500 feet... in 500 feet... in 500 feet..." when im not even 500 feet away from the next turn. everything else about nav works, except for the TTS. Google TTS is selected in the settings, so i have no other idea what it may be..

thanks in advance
[Samsung Galaxy Nexus] mmuzzy:
Navigation is one of my most used features. I use it so much I even named the voice Twiggy, which annoys my wife (yes, I still call her that).

Anyway, back to the hopefully useful part. Assuming you didn't flash GAPPs over the ROM or something it should work fine. You might try clearing app data/cache for Google Text to Speech and Maps. Also if you dirty flashed the ROM it might be worth backing up and clean flashing.
[Samsung Galaxy Nexus] chan1121:
I've had that happen many times. I don't know why it happens, but to fix, just clear data on maps and it should fix the problem.
[Samsung Galaxy Nexus] demill66:
MMUZZY, I don't know what went into that 9/6 version, but my battery life is better than ever. In addition, on bluetooth dial, after the phone says, "speak now," you get a beep that clearly indicates that the phone is ready to hear your command. Since, "speak now" was often at a low volume, this beep is an excellent addition. As I said before, I don't know how this suddenly happened, but it is a great improvement. Thanks again for all of your work. I love this ROM.
[Samsung Galaxy Nexus] The Horak:
Opposite for me...

I have heard great things for battery life with this ROM, but I can't get past 1.5 hrs screen on time with it. Now, I know, there's more involved than just screen usage. But I don't do too much with this phone other than Texting and listening to music that is stored locally for MAYBE an hour through headphones. Can anyone help me out? What can I do to fix this? I'm on the Samsung extended battery, too. Do I need to use a different governor or entirely different kernel?
[Samsung Galaxy Nexus] thesuzukimethod:
Start with governor (do you have setcpu installed?), and then try a couple different kernels. The question(s) i'd have is(are):

A) what is the highest draw in terms of percentage? (screen on time of 1.5 hours, if the biggest draw, is problematic, fer sher)

B) is the device deep sleeping? (cpu spy), if not, what is causing it to stay awake? (better battery stats)

C) are you using device on 4g? (way more battery than 3g)

other than stock kernel, i've logged the most time with leankernel and found it did a great job saving battery when not in use (interactiveX governor turns off a core (a la hotplugx) when sleeping to really shut down power usage, but i found it ate battery more than expected under "normal" usage (podcasts, Mp3s, email, text, etc). I've been running the stock kernel after clean flash of the 9/6 build, and the overall battery life is better under normal usage but i dont quite get the shutdown powersaving of leankernel durin sleep (but that is a tradeoff i will take).

i've also found (as have many others) that the franco kernels seem to do well under heavier usage - but i had a few issues with build stability of the nightlies and switched to lean for a bit. i have trying th most recent stable build on my list of testers
[Samsung Galaxy Nexus] The Horak:
I loaded CPU Spy onto my phone, and it showed that my phone was in deep sleep for the vast majority of time. But it must have grabbed stats from the time before it was installed, cause it said it had 9 hrs of logging and I just installed it. I am on 3G only. I did a dirty flash of the ROM this morning, but I cleared the Cache and Dalvik Cache before I did. I have bad Cell signal at work, so today will not be the best judge of performance, but I'll see what happens. Thanks for the help!