yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] modernbummer:
Muzzy, I just wanted to say thank you for this ROM. It has pretty much been my daily driver since I've rooted. I've tried leaving it several times for others, but I end up just restoring back to it. It is rock solid and stable. Thanks again.
[Samsung Galaxy Nexus] BOY_:
MMuzzy, I'm trying different kernels to see if why my battery life just doesn't seem as good as it should be and I've noticed that Maps is consistently showing up in my usage and I don't know why. I don't have any map-related apps running, GPS is turned off, still shows up after a reboot... any thoughts? Also, I'm getting TWS all of a sudden and I'm sitting under a repeater here at work. I know TWS is a major battery drain.

Stumped.
[Samsung Galaxy Nexus] mmuzzy:
I haven't put much time into troubleshooting the app. I've heard everything from make sure you aren't connected to wifi, make sure you are the first time, clear cache and try, and uninstall/reinstall the app. I find the only way that works reliably for me is to login to my profile on WiFi to use it. Data is hit or miss and I'm not sure why.

Thanks :)

I was a crack flasher with the best of them when I had a Dinc. JB has me calmed down a bit.

TWS is a major drain is right. If my signal is low I usually go airplane mode. Believe it or not, if you're below a cell site, you might be in a bad signal area especially if the building has a lot of shielding in the walls. The radiation pattern of an antenna fans out away from it.

RF is tricky business. ;)
[Samsung Galaxy Nexus] BOY_:
Thanks mmuzzy, cell repeater to prevent that (4 signal bars, on wifi) :confused: Any thoughts on why Maps is showing up?
[Samsung Galaxy Nexus] dxh3378:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Muzz,

I'm not sure if this is a bug, or what, but I transferred a file with box, and I can't get the notification to clear, no matter what I do, any thoughts?

Btw, super fantastic build, I'm on 2-17, haven't even updated yet things are running so we'll.

Thanks for all your great work,

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

Reboot :D
[Samsung Galaxy Nexus] mmuzzy:
Thanks. Does the condition persist after a reboot? Try clearing app cache, fix permissions, etc. If this is an ongoing problem with the app you could shut off notifications from the Box app in the app info screen.
[Samsung Galaxy Nexus] jmagsho:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I think it is a bug with the latest box update. I have seen it too, on both my phone and my N7. The N7 is totally stock, so I do not believe it is a rom issue.
[Samsung Galaxy Nexus] dxh3378:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Thanks yall, I'll give your suggestions a go and report back.

Update:

Reboot cleared the notification, so it seems to be an app bug.

Thanks again guys

D
[Samsung Galaxy Nexus] billykxda:
Can this ROM affect reception at all? I did the 3/5 French Vanilla update and an update to the new 4.2.2 radios. My 4G has been very poor, so I went back to the previous versions of the radios. My 4G still sucks, big time.

Is there something I am overlooking here?

Would re-flashing the ROM and the previous radios at the same time help at all?

I am reaching for straws here!
[Samsung Galaxy Nexus] tiny4579:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

ROM doesn't affect signal. What you're suggesting will not make a difference.
[Samsung Galaxy Nexus] billykxda:
Thanks Tiny.

I guess I need to find the latest "official" JRO03O radios and just go with flashing them.
[Samsung Galaxy Nexus] RW-1:
Here:

http://rootzwiki.com/topic/12864-radiosvzw-all-radios-in-flashable-zip-updated-6-mar-2013/
[Samsung Galaxy Nexus] Frixtion:
I am experiencing poor 4g service also with latest build which I reported the night of release. Can you explain what would cause this. Whatever is causing it couldn't be fixed with a restore of the ota I had backed up, the issue seemed to carry over. I thought getting a new sim might help so I did and it didn't. What did help was restoring stock 4.1.1 and applying the ota update again. I don't know much but I know I rarely loose 4g until the latest build. Mmuzzy said once you have the radios you have them unless whatever. I'm thinking there's something in the ROM that isn't easily overwritten like a radio. I don't know but I'm on the ota and that's where I'm gonna stay. All this over gps
[Samsung Galaxy Nexus] mmuzzy:
Ok. I don't know how to answer. There are unrelated things that are being treated like they're related. The bootloader and radio persist when you flash a ROM because they aren't part of the ROM. Restoring stock 4.1.1 flashed one set of radio and bootloader and then, assuming you put the leaked 4.2.2 OTA image on, then it would overwrite them with yet another set of radio and bootloader. In any case, I'm glad you have a solution that works for you.
[Samsung Galaxy Nexus] SparkyXI:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Or, to shorten this even further, if you're getting worse reception, go back to the radios you had before. They have nothing to do with the ROM.

Bear in mind also that the newer radios may be worse in your area, and better in others.

Also... YOUR. MILEAGE. MAY. VARY.
[Samsung Galaxy Nexus] Frixtion:
I appreciate both of your responses. The argument I have is I updated from 4.1.1 to the ota on the night it was leaked and ran it for a day or two with no 4g/ gps issues. I can't remember which French Vanilla build I applied after, I think 3/5 and had no issues. After updating to the 3/7 build immediately after I restored my settings I was struggling to get 4g. Now I'm running the 4.2.2 ota leak and 4g is as strong as it usually is. I think I'm the only guy on this thread that has actually ran the 4.2.2 ota leak on his device and not just decomplied out the parts they wanted. I'm going to stick with the ota for a while, I'll still follow the thread but I will remain silent and try French vanilla again in the future. My join date may say January but I actually joined back when the og droid first came out. I just never logged in and forgot my username. The reason I created a new account was because I liked the attitude of people in this thread and still do. Thanks mmuzzy for being cool , adb freedom you da man don't shoot your eye out and everybody else be easy.
[Samsung Galaxy Nexus] mmuzzy:
I don't even look at join dates. I could care less. I make no assumption of anyone's background or that they're imagining an issue. I simply don't understand why you're having trouble. Take care and I'm sorry the ROM gave you issues.
[Samsung Galaxy Nexus] Quod:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Definitely shouldn't be a problem with the rom. Here's a screen showing the radios I'm using and getting a full 4 bars.
[Samsung Galaxy Nexus] tiny4579:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I have a theory but its just that, a theory. When you reverted to 4.1.1 you got the 4.1.1 radios. Once you flashed 4.2.2 ota you updated the radios again but this time in an official manner with an official recovery. One of the senior admins at rootz recommends never to flash radios on a nexus through recovery but flash the full image through fastboot. Maybe since you took the ota you flashed it in a way that was supported officially and that helps your 4g service. Just a thought.
[Samsung Galaxy Nexus] Frixtion:
I'm not b.s.ing or trolling or imagining this but 4g isn't behaving as it usually does. Does anybody know what I can do to get back the French vanilla goodness whilst keeping my 4g in line? Are the latest radios included in the 3/7 build. Im going out on a limb here but if they weren't would it improve my oddst?
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

My ROMs don't include radios. Ever.

Send from my phone.
[Samsung Galaxy Nexus] Frixtion:
So when everyone has been updating they are relying on mwalts ota radios to get the new radios, otherwise they have the jop30 radios. Is that what your telling me. I'm getting a better understanding of all the radio talk that was going on a week ago.

I'm thinking people in the future coming from the official ota 4.2.2 to French vanilla are going to run into the same issues I'm having.

I always believed in do it right the first time or do it again, thats why i updated 4.1.1 to 4.2.2 like i did and that's why I always clean flash
[Samsung Galaxy Nexus] mwalt2:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

He ran the ota at first though. I'm curious, what would flashing a radio in recovery do that is different from fastboot? Does the rootz admin have a reason for this?

GPS can certainly be affected by a rom, but radios and bootloaders are on different partitions and 99.9% of custom roms do not have radios (as has been said). The lte ril is part of the rom, but I'm pretty sure it's part of aosp and the 4.2.2 version is probably in mmuzzy's rom.
[Samsung Galaxy Nexus] mmuzzy:
The other part was he said the signal issue persisted even to 4.1.1 until he went back to a stock image.
[Samsung Galaxy Nexus] jpinsl:
All the radios are linked in the first stickied post of this forum
[Samsung Galaxy Nexus] Frixtion:
I made a nand backup of 4.2.2 ota before I flashed I think 3/5 build. After flashing 3/7 4g starting taking a poop. Then I tried to restore the 4.2.2 ota backup and it seemed the issues carried over. So i then restored a even older 4.1.1 and updated to 4.2.2 offical again and the problems are gone.

I didn't have the issues with 4g on the 3/5 build but it was immediately present on 3/7 I wish i knew why. When flashing 3/5 i was coming from updating 4.1.1 to 4.2.2 ota offical.

1.updated 4.1.1 - 4.2.2 ota leak

2.made a back up

3.clean flashed 3/5 (all good)

4.clean Flashed 3/7 (4g poops out on 3g a lot)

5.restored backup made #2 4.2.2 ota 4g issues still present

6.restored a stock 4.1.1 backup updated to 4.2.2 nota leak 4g problems not present

No worries guys I'll try again on the next update I just got bad joo joo w/3-7 thanks for your thought's
[Samsung Galaxy Nexus] billykxda:
VZW has had outages all over today (3/9). I thought I had radio problems but it turns out that it was a VZW issue.

I went back to the 4.2.2 radios.

All is well, and very fast.

Maybe this was at the bottom of your issue as well?

Is your 4G healthy?
[Samsung Galaxy Nexus] tiny4579:
The rootz admin stated this because he believed that something as critical as a radio or bootloader shouldn't be flashed through a custom recovery where there could be new bugs. OTA's are flashed through stock recovery and fully tested prior to releasing. This is why he recommended fastboot. That doesn't make flashing through recovery wrong though and I noticed the issue trying to flash your LTE radio via fastboot. It wouldn't take. I know someone, probably you, mentioned it.

Well, that would make sense why my data was screwy today and had issues connecting without my changing anything and the quicker battery drain maybe. Where'd you hear about that?
[Samsung Galaxy Nexus] RW-1:
I have to agree, have flashed radios through fast boot, and recovery and have never seen any difference, and I trust mwakt2's work on what he turns out.

Its a strange one to sort out...
[Samsung Galaxy Nexus] andrewlax120:
i don't see how a rom could mess with reception
[Samsung Galaxy Nexus] JPBeard21:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

If the ril is outdated, it could give inaccurate signal bar readings.
[Samsung Galaxy Nexus] Frixtion:
I very rarely have full bars of 4g since I've had the gnex, but also rarely only in a consistent group of locations do I see 3g. The past couple days I have been on 3g where it was always 4g. When I went into vzw to get a new sim I had of course full bars of 4g and the salesman spoke nothing of any outages. I will try 3/7 again with the news of vzw problem. I have never had any issues with mmuzzys builds and I'm hoping its just bad timing. Thanks again everyone I would be thanking you all but I've reached my limit but as soon as I can I will.
[Samsung Galaxy Nexus] tiny4579:
There were some people complaining about outages on the VZW message boards. It looks like my area could have been affected. It may have not been national outages.

https://community.verizonwireless.com/message/943427#943427
[Samsung Galaxy Nexus] Frixtion:
I didn't see anyone from my area complaining but I'm sure this is what's going on now. I never thought of checking the vzw message boards, I will next time. Sorry for raising a red flag guys, I kinda feel like a butthead now. My poor gnex has been through a lot today so I will flash 3/7 again tomorrow.

Mmuzzy when i said i had joined years ago i meant it to be a compliment that your rom and thread were worth creating a new account. Lucky you huh buddy
[Samsung Galaxy Nexus] SparkyXI:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yep... Looking like folks all over the country experiencing intermittent outages. I must say, the part of Phoenix I'm in has horrible 4G coverage, which hasn't been all too helpful. I'll be glad to get back to good ol' St Paul.
[Samsung Galaxy Nexus] klobkelosh:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I was wondering why I was burning through battery today....thanks for the top
[Samsung Galaxy Nexus] johnco1972:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Has anyone noticed the 3/8 vanilla ROM being laggy? Mine seems to lag and be "joggy" during some scrolling and swiping away screens. I've read this complaint about the leaked Verizon ROM too

Fyi-- this is a clean flash
[Samsung Galaxy Nexus] tincbtrar:
There was definitely an outage today in NYC...I didnt have any data for most of the morning/afternoon.

Thought about flashing stock image because I did something wrong...but im glad I didnt cause everything works fine now.

Great ROM btw muzzy. Works like a champ with tiny's kernel.
[Samsung Galaxy Nexus] shadowstewie:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I just flashed and mine is doing it as well as opposed to the 4.2.1 build I had on. It can be compared to having a frame rates drop.

Hopefully this can be fixed :/
[Samsung Galaxy Nexus] Frixtion:
You can try under developer options/ check force GPU rendering and then reboot. This may cause some apps to misbehave or crash but you should notice a difference.
[Samsung Galaxy Nexus] jon9314:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'm glad all worked out. I just flashed stock and applied the ota to get the system dump. lost all backups and was nervous about the latest. But after flashing it is all good and smooth as ever.

Thanks to all who make this ROM a success.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] billykxda:
Hey Tiny. Look here:

https://community.verizonwireless.com/message/943415

Outages all over the US on 3/9.

I spent more than an hour swapping out different versions of the radios with only brief, random connections to the tower across all of the versions I tried. There was no rhyme/reason. Once I realized that others were having the problem as well, I just put the latest 4.2.2 radios back on and just waited for service to return. It did later on Saturday. It's been perfect since. Frustrating!

Funny thing is, others in my house with LG and HTC 4G phones never saw a hiccup. Although I didn't dig into it, it looked like Samsung phones were the one's with the difficulty. I am in MD and another MD'er (different area in MD) also with a Gnex who posted here was without a connection for the same period of time. Phone-specific outages? Hmmmmm.....
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

The test radios must have borked the VZW network. ;)
[Samsung Galaxy Nexus] tiny4579:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I know. I posted a link above from.Verizon's forums. It must have gotten lost with the other posts.
[Samsung Galaxy Nexus] SparkyXI:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Were the FK radios for testing only? If so, lulz and lulz.
[Samsung Galaxy Nexus] jmagsho:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'm not surprised. The Samsung radios are crap compared to just about every other manufacturer out there. I've owned many different brands over the years as have many others here, and in my experience the Motorola ones are the best and the Samsung ones are the worst.

Here's hoping that Google makes the next gen Nexus on Motorola hardware.

---------- Post added at 09:27 AM ---------- Previous post was at 09:17 AM ----------

I am seeing the lag too, ever since I flashed the 3/7 build. I thought it was me because I dirty flashed over 3/5. I may run the super wipe tonight and try a clean flash and see what happens.
[Samsung Galaxy Nexus] gadzooks64:
I have to agree.

I bought my FIL a Razr M for his birthday last week. Sat next to him yesterday and noticed he was getting 4g signal while I was only getting 1 bar of 3g. Le sigh.

I can't wait to see what the Motorola X phone is all about.
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

It's all about a locked boot loader. I don't buy Motorola because they have such an anti user attitude like that.
[Samsung Galaxy Nexus] johnco1972:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Moto is a bit user-unfriendly about the locked boatloader. Moto always had great signal. I don't know how good LGs smart phones are (ie nexus4)
[Samsung Galaxy Nexus] Frixtion:
Well I'm back on 3/7 FV and 4g is back to normal. It was just bad timing that I flashed 3/7 in the early hours of 3/8 12am and 4g was acting up. The outage for me carried over until early afternoon of 3/9 coincidentally ending after flashing 4.2.2 ota. I went as far as getting a new sim before making a stink about it and pointing the finger at 3/7 build. The vzw rep said I had a older sim so at least I have the new red sim. Sorry mmuzzy for any frustration I caused and thanks everyone for trying to help.

It was funny watching the vzw guy struggle to figure out how to navigate around my phone. I had expanded desktop on and use lmt launcher and adw to hide the dock. He was a younger guy and I expected him to be somewhat into his phone but he wasnt, he didnt know to much.
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I've had nothing but problems out of my gfs RAZR M. Particularly with radios and WiFi.. But especially the WiFi. Had to install this WiFi "fixer" app that probably does the same thing as power cycling the WiFi, but it seems to work if you run it about 3 times.

Compared to my gnex, I thoroughly despise her phone... Even after I rooted, safe strapped it and installed an unofficial cm ROM.

Her mom and brother have the same phone also. Her brother's, I don't know much about, but her mom's has had the same WiFi issues since day one and I've had to tinker with it here and there.. I suppose the only good thing is they aren't heavy users like the rest of us.
[Samsung Galaxy Nexus] jmagsho:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

On a whim, I decided to wipe cache, dalvik, and run fix permissions in recovery before resorting to a full wipe and reflash. After doing so, the lag seems to be gone...
[Samsung Galaxy Nexus] Wdswds:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

This may have been asked before, I searched the thread and didn't find anything about this, but has anyone gotten wallet to work? Which version is working?
[Samsung Galaxy Nexus] JayBeezy802:
I flashed 3/7 French Vanilla which has the updated Superuser and Wallet. I have never used wallet before so I set it up and it worked just fine. I was able to pay by tapping with my phone on the pay terminal. In the banner it still says my device is not supported but other than that it works just fine.
[Samsung Galaxy Nexus] Frixtion:
If you ask Google the wrong question you get the wrong answer. Lesson learned.
[Samsung Galaxy Nexus] darkhawkff:
Incorrect sir!

I'm using Google Wallet. In fact, I used it to pay for my gas and groceries the other night on my VZW Galaxy Nexus.

Search the forums, there's a thread about Google Wallet with the latest APK somewhere. You obviously can't get it through the play store, but it's out there and can be used.

---------- Post added at 05:30 AM ---------- Previous post was at 05:28 AM ----------

The 'Unsupported Device' just means that your phone is unlocked. This is not abnormal if you're unlocked and have a ROM flashed. Ignore it, it really doesn't mean anything overall.
[Samsung Galaxy Nexus] pcloadletter1:
Just activated wallet on the 3/7 FV build without errors. Have never used it, but my CC and transactions showed up. Corruption of the secure element was an known issue in the past if one did not uninstall and or logout of GW before flashing a rom. AFAIK there is no fix.
[Samsung Galaxy Nexus] Frixtion:
Stupid post I made
[Samsung Galaxy Nexus] DavidFlory:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I am also using Wallet with no problems.
[Samsung Galaxy Nexus] JayBeezy802:
Most obviously know that the VZW GNexus is not a supported device, that doesn't mean it cannot work on our phones. Many people use it just fine, however, you must log out of Wallet and Uninstall it before you flash a new rom since you can bork the secure element.
[Samsung Galaxy Nexus] Frixtion:
According to this thread http://xdaforums.com/showthread.php?t=1365360 dark hawk's explanation of unsupported device is partially correct. Look under troubleshooting.
[Samsung Galaxy Nexus] ohiomoto:
I'll chime in and say that 4G was down in my area on Saturday. This has happened several times since I've owned the GN. I usually reboot and if that doesn't help, I try to ignore it for a day before I start to worry about my phone or SIM card. I always assume it's VZW and so far that has always been the case.

As for the Samsung radios, they do suck. I was using a Palm Pre Plus before I started playing around with ICS on a Fascinate and my GN purchase. The Palm radios were much so better. Bluetooth and Wifi rocked too. Wifi would stay connected to my home network halfway around the block!

I will say this though. The GN has never dropped a call on me. It doesn't ring at my house 1/2 the time but if it gets the call, it keeps it.
[Samsung Galaxy Nexus] RW-1:
I must be lucky, but to be truthful, I believe I've received fair performance on my Gnex radios in my area compared to my OG at the time.

I hate the speakerphone performance though.

Must have been a heck of a weekend for some of you, I did have occasional data drops this weekend in Eastern PA, but I attributed that to heavy Ingress usage (I made level 8 this weekend :) )
[Samsung Galaxy Nexus] johnco1972:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I must not have rebooted my phone enough times before I made that post. :) it seems like it takes 2-3 reboots for everything to smooth out.

A side note on radios -- I'm on the fk radios and have no GPS or other signal issues (fingers crossed it stays that way)
[Samsung Galaxy Nexus] the sandman89:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Download links not working
[Samsung Galaxy Nexus] mmuzzy:
It seems Goo.im is on a bad run lately. No one's files are showing up.
[Samsung Galaxy Nexus] the sandman89:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Bummer. Really wanted to try this rom guess I'll have to wait until goo is fixed
[Samsung Galaxy Nexus] mmuzzy:
Sorry about that. I wish there was a way to mirror the ROMs without me having to upload another 12 or so to another server. I haven't figured out the perfect hosting/mirroring combo yet.
[Samsung Galaxy Nexus] the sandman89:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

It's all good it's not your fault I'll just run my current rom for a little bit longer