yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mmuzzy:
It doesn't seem to be a ROM issue but I know better than to say it isn't. Maybe a battery app with better reporting. I think others use Better Battery Stats. I'm curious to see what's causing it.

Hmm. I just enabled the Japanese IME in Language settings and then when the keyboard is up you can chose input method to select Japanese. It did change the keyboard to have the different character set. Perhaps I'm misunderstanding though.

Actually the ROM is the latest source available in the AOSP repository. The leak for Verizon is JRO03O and Sprint's is even newer. Their build is either JRO03R or JRO03U, I can't figure out which is right since the screenshots and actual image seem to conflict.

I made a judgement call and stuck with source. It isn't a huge difference and technically it's still JellyBean 4.1.1. I'll update as soon as the repo is updated, which should be soon.
[Samsung Galaxy Nexus] Soundfx4:
Ahhh, okay I got ya. All these build things confuse me >.< I just found the build JRO03O along with the radios that came with it (FF02/FG02) and I haven't even heard of JRO03R or JRO03U until you mentioned it (but then again, I've only been looking for toro verizon information/roms/radios). I've been desperately trying to fix the problem with my signal, and a friend mentioned it may be a problem with how the ROM is talking to the radios...anywho, I've been searching, reading, and researching for the past couple of days (I haven't had time until recently) and...I dunno. haha. I downloaded this though, and will give it a shot, or I might just wait for the repo to be updated, but I'll likely try several things until that time. But my phone isn't very stable right now anyway (random restarts, freezing and having to pull the battery, etc) so it's about time for a fresh wipe/flash! :D

Thanks!
[Samsung Galaxy Nexus] mmuzzy:
Radios are normally separate from ROMs unless they're the actual OTAs so you can flash them and run whatever ROM you want. Signal has nothing to do with the ROM. Good luck. :)
[Samsung Galaxy Nexus] AGeleff:
Also, my NFC appears to have died after flashing this latest version of the ROM. Weird.
[Samsung Galaxy Nexus] Soundfx4:
-nods- the build I found was an "OTA" update, and those radios were packaged in. What I understand is that they are just new radios that are being released with JRO03O. Or something like that, don't take what I say word for word, much could be misinterpreted :p It'll just be easier to link what I read :D

http://www.droid-life.com/2012/08/2...ean-radios-ff02fg02-for-verizon-galaxy-nexus/

and

http://www.droid-life.com/2012/08/29/download-jelly-bean-jro03o-update-for-verizon-galaxy-nexus/

I think what my friend meant was that he heard of issues before where the ROM didn't handle the information from the radio well and it caused issues (he knows what he's talking about, he's very knowledgeable about this stuff, I am likely repeating it wrong if it doesn't make sense @.@ lol)

Thanks! :)
[Samsung Galaxy Nexus] mmuzzy:
Very. What are you basing it on? If you went to use it and it didn't work you might want to try it at a different register or store. NFC has worked every time for me.

Ok. First of all I said that they were packaged with OTAs, that build is the OTA. Yes, it will have the radios if you get the OTA. However, ROMs based off of it won't always have the radios. Case in point is mwalt's ROM based off tghe OTA... build JRO03O and no radio.

I'm glad you have a friend who you can ask these things. I'm here to help, but not to argue. If that's what this is than I'm done with this topic. ;)

EDIT: That sounded harsher than I meant. If you look at the threads for just the radios from the leak you'll see that they're basically there because it's perfectly fine to flash with any ROM. Sorry for the way I worded the text, hopefully the wink let you know I wasn't serious.
[Samsung Galaxy Nexus] AGeleff:
Friend of mine is flashing this ROM at the moment. His device has been stuck at the glowing X for about twenty minutes now. Any hints?
[Samsung Galaxy Nexus] mmuzzy:
It doesn't sound like cache was wiped enough perhaps? Cache, Dalvik, and in the mounts menu, system. If you're wiping fresh I do those and factory wipe too. You know that though but sometimes it's easy to miss one.

It shouldn't take anywhere near that, just a few minutes tops.
[Samsung Galaxy Nexus] kioshi:
You should try a different register or store. I got off work and used Google Wallet the very first time. Sure, it shows 2 same transactions charged but it went through. Nothing wrong with NFC on latest build.

@mmuzzy: Apologize for misunderstanding, I meant if the JPN keyboard were to be ever removed from future builds, I'd have a hard time finding the apk to flash it to your builds :)

Battery life is okay with this ROM. I'm using Francos kernel and new radios from Verizon. Solid signal with the forest behind me!

@Soundfx4: The signal has nothing to do with this ROM, please read carefully.

Keep up the good work mmuzzy.
[Samsung Galaxy Nexus] dustrho:
Yes, that is with the stock browser. I even rebooted and it was still doing it.
[Samsung Galaxy Nexus] mmuzzy:
Hmm. I really don't think there'd be any harm in removing the service. It's mostly a nuisance for the end user. If you want to try to disable it I think you can, assuming you have a file manager like root explorer. It's at system/bin/bugmailer.sh, I think you can just delete it... or move it to sdcard to be safe but I don't think it will hurt anything to keep it from running.

EDIT: I just deleted it on my phone and rebooted. Everything seems normal and no weird error messages.
[Samsung Galaxy Nexus] Moonkae:
I had better battery life with stock kernel actually, try giving that a shot?
[Samsung Galaxy Nexus] BOY_:
Refresh my memory, if I dirty flash over Franco's kernel, will I keep franco's or will the kernel be updated? I know if I do a full wipe I'll start fresh. I also think that I had better battery life stock.
[Samsung Galaxy Nexus] thesuzukimethod:
re: the radios/ROM discussion

I've been using this ROMS iterations since late July, and i flashed the newest (leaked) radios as soon as they were out (mid/late august?). if anything signal marginally improved, although I'm on a 3g/4g transition spot (in the middle of town! the only 3g hole in town! cmon verizon /siderant).

my (limited) understanding of the ROM/Radio interface is the Radio Interface Layer (RIL, part of the ROM (at a system level?), as i understand it) is meant to match (ideally*) the version of the radio you are running

@soundfx - your friend may have been talking about this.

meaning running a 4.04 or 4.1.1. based ROM with 4.02 radios is not ideal..as the newer ROMs have the updated RIL. i really dont know what version of RIL is in the source (i suspect JB?) so the new radios should be an improvement? (please note: this is at best a laypersons explanation...experts, please smack me down, especially if you can give a clear explanation of how this works)

of course, my * (by ideally above) is that i ran 4.02 radios til mid august b/c i didnt realize i'd never updated them even though i was on 4.04 roms (and JB as soon as they leaked). and aside from continued problems with the 3g4g transition zone, it didnt really change much when i updated radios, although there was some incremental improvement in the handoff from the 4.02 radios forward.
[Samsung Galaxy Nexus] mmuzzy:
The kernel will be replaced with stock if you dirty flash. Well obviously if you clean flash too. ;)

I stand corrected. I was thinking that ril was more for interface and control functions but yes it passes signal strength state too. Thanks, you're right, it was probably what his friend was referring. There are lots of moving parts to that one.
[Samsung Galaxy Nexus] BOY_:
Thanks, I like ridin dirty :cool:
[Samsung Galaxy Nexus] thesuzukimethod:
heh heh - not sure i'd take what i say as something to correct yourself with.

From something/somewhere that i read - and i will not be able to find the link from where i read this, sorry - is that my sense was that RIL generally changed along with ICS/JB build versioning, and that RIL/radio combos that were of similar/same versions tended to work together (the "science" on this seems spotty...especially since some updates might not change a particular piece)....

My sense was that these changes were at a system level (i.e. i dont think ROM makers are messing with this, or even have reason to...again, correct me if wrong) and my point was that i thought (please: experts correct me) was that all ROMs based off the same source/build would have the same RIL...so you shouldnt see differences in signal from ROM to ROM (if they are based off same source, and you dont change radios....) is this right?
[Samsung Galaxy Nexus] billykxda:
Haven't been back here in a while. Still runing Muzzy's ROM from late December.

I've got some catching up to do!

-bk
[Samsung Galaxy Nexus] mmuzzy:
Ah. There you are. That's ok, we saved your seat. ;)
[Samsung Galaxy Nexus] billykxda:
Hey Mike - thanks for leaving the light on.

I plan to flash the latest - probably French Vanilla - you didn't have all these "flavors" last I was here!!!
[Samsung Galaxy Nexus] willyjay:
I'll get a text battery % mod made up for the 3/1 build this evening.
[Samsung Galaxy Nexus] willyjay:
Here's the 1% text battery for the 3/1 build

http://www.mediafire.com/download.php?tzdk6dz1gtgck3k
[Samsung Galaxy Nexus] RW-1:
Hi Mmuzz,

Question, can we check the volume fix's are still in place?

I only ask because everything else being equal, I went to go get voicemail just now, and usually I can listen to it at full volume without going thru speakerphone, it "seems" lower now, volume sliders were all full.

no other mods on volume applied by me, I run the rom, Zenyth blue softkeys and that's about it. Included kernal (just listing), new radios (same).

If so, I'll live with it, but if you don't ask .... :)
[Samsung Galaxy Nexus] andrewlax120:
holy crap. fastest my phone has ever been...french vanilla odexed with akcylon is just beautiful. speed, great battery, and incredibly smooth

you can odex with this app if anyone is interested

http://xdaforums.com/showthread.php?t=1514576
[Samsung Galaxy Nexus] chagersc:
rom is running great!

one question - is it possible to exclude 'company' from the t9 dialer?

with it in the contact's title, i get a lot of unwanted contacts popping up instead of 'george' or whatever...

thanks!
[Samsung Galaxy Nexus] jpinsl:
My GPS was working and stopped after dirty flashing the 3/1FV. This has really messed with my ability to play Ingress.
[Samsung Galaxy Nexus] stuckintheskull:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Clean flash would help.
[Samsung Galaxy Nexus] tiny4579:
Check out these binaries. They may help:

http://xdaforums.com/showthread.php?t=2172006&page=2
[Samsung Galaxy Nexus] tiny4579:
No, it won't make a difference here.
[Samsung Galaxy Nexus] mmuzzy:
Thanks, WIllyJay. OP updated. :)

I did check that actually. The value in the audio_hw.c file I normally change is on the high end so I'm not sure why.

Excellent. Thank you. I personally don't notice that much of a difference but I'm easy. ;)

Thanks. Hmm. I'm not sure how you'd exclude unless you got fancy with the naming. Maybe something like start company entries with a letter you wouldn't normally start with like 'xCharles'. I do things like that with filenames at work to get them out of my way. ;)

I'd start with a clean flash too. That seems to be the key with the new build and GPS I think. EDIT: Although it seems to have helped some we'll look into it further based on Tiny's input.
[Samsung Galaxy Nexus] mmuzzy:
Thank you, sir. :)

So those who are having GPS/WiFi issues try the binaries that Tiny linked from the leaked OTA. Thanks.
[Samsung Galaxy Nexus] trogdor3222:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Trust me, I hear that. I literally work in Times Square (only 5 floors up from street level) and can never keep a connection even while sitting next to the window. Guy in my office with a Note II has no problems, neither do the iPhone users. The leaked radios seem to help a bit, especially on the train ride to/from LI.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jpinsl:
I got lucky, formatting cache and dalvik brought the GPS back to life without having to clean flash.
[Samsung Galaxy Nexus] mmuzzy:
I know it shouldn't matter for GPS but for some reason formatting cache and dalvik seems to help. I'm glad it worked for you also. Thanks for the update.
[Samsung Galaxy Nexus] tiny4579:
No it doesn't make sense, especially since dalvik has nothing to do with GPS.

The binaries you have in your build may be part of the issue. I'd recommend the gps.omap4.so, sirfgps.conf, lib_gsd4t.so from the 4.2.2 OTA.
[Samsung Galaxy Nexus] mmuzzy:
Agreed. And yet I've seen multiple posts this afternoon where clearing cache has cleared it up. Maybe it isn't the clearing cache and more to do with a reboot. I have no idea.
[Samsung Galaxy Nexus] tiny4579:
Lol, I just updated my post but you posted too fast.
[Samsung Galaxy Nexus] mmuzzy:
I'll swap them out and update soon. Thanks for the help.
[Samsung Galaxy Nexus] Cornflakius:
I actually just came here to see if anyone was able to have this. It's a bit annoying to drive and not have this feature, so if you can make it, it would be amazing! :highfive:
[Samsung Galaxy Nexus] klobkelosh:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Those new binaries (the same ones I posted in the gps, Wi-Fi, and Bluetooth driver zip) do help, especially with gps lock and deep sleep issues.
[Samsung Galaxy Nexus] mmuzzy:
Thanks for doing that. We'll package them up into a ROM here shortly and get it uploaded.
[Samsung Galaxy Nexus] blahb:
Where to put ROM

I know know this is a NOOB question and I've been doing this too long to ask it but where are you guys putting the ...zip file before doing the clean flash method in TWRP?
[Samsung Galaxy Nexus] mmuzzy:
ROM Update

March 5, 2013

- GPS files from OTA merged

(thanks klobkelosh, Tiny4579, mwalt2)

I just put mine in a staging folder like Downloads on the SDCARD partition.
[Samsung Galaxy Nexus] blahb:
Thanks for the info. I've been putting them at the root of sdcard but they keep getting deleted during the clean flash method from the OP through TWRP. Should I be using CWM?
[Samsung Galaxy Nexus] BOY_:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Just keep them in the download folder :what:. If you use the superwipe script they will be safe anywhere on the sdcard.
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39
[Samsung Galaxy Nexus] BOY_:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39
[Samsung Galaxy Nexus] JayBeezy802:
Just dirty flashed this and forgot to flash GAPPS and ran into some issues.

Went back, cleared cache, cleared dalvik cache, flashed updated rom, flashed GAPPS, same issues (No softkeys present, asking me to install Gmail, etc.)

Before all of this I flashed the newest "test" radios (on to the 3/01 or 3/03 FV ROM I forget which) and everything appeared fine (I made a Nandroid obviously as well incase).

I'm now doing a clean flash in hopes to clear my issues! It appears to be okay so far...I'm such an idiot sometimes haha
[Samsung Galaxy Nexus] wavedashdoc:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

New build GPS not able to lock on at all :/ anyone else having rt his issue.
[Samsung Galaxy Nexus] Rem3Dy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Works fine here.
[Samsung Galaxy Nexus] mmuzzy:
Hmm. Can I have more feedback on GPS please?
[Samsung Galaxy Nexus] AndroJak:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

GPS working fine for me muz

2-17 with the binary patch.
[Samsung Galaxy Nexus] RW-1:
Interesting. Downloaded but am holding on install. The updated GPS files, newer Lib's than we were running?
[Samsung Galaxy Nexus] stuckintheskull:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Wiping dalvik and cache seem to be helping some. I would start with that. Good luck.
[Samsung Galaxy Nexus] jon9314:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Works great here 3/1 with binary patch. And dirty flashed since 4.2 dropped. No problems at all

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] mpressive:
Dirty flashed from 03/1 rom this am and thus far, phone hasn't been able to connect to Google Servers (sitting on grey icon). Also, had soft key mods installed. Are those safe to re install with new rom? tx!!

---------- Post added at 08:56 AM ---------- Previous post was at 08:38 AM ----------

Redownloaded GAAPs and that looks like it solved my issues. Still need clarification if it's okay to download battery circle mods with the newest ROM.
[Samsung Galaxy Nexus] mmuzzy:
The 3/1 mods will absolutely work with it. The changes are only to the proprietary files.
[Samsung Galaxy Nexus] pkgnex:
Mmuzzy, does the 3-5 build have all 3 of Tiny's ota binary patches (wifi, gps, and bluetooth) or just gps? Also, in your opinion would flashing the binary patch file Tiny posted be equivalent to (and faster than) flashing the whole new rom if I'm already on the 3-1 build? Thanks!
[Samsung Galaxy Nexus] mmuzzy:
I only grabbed the files from the OTA for GPS. Give it a bit. I think I'm going to take a step back and redo the binaries today. I don't like the inconsistency I'm seeing. I just want to make sure I didn't miss something.
[Samsung Galaxy Nexus] pkgnex:
I'll patiently wait for you to do your magic. My only problem right now is getting a gps lock on the 3-1 build, and I honestly don't need gps that often. Thanks for all you do and your fast response to questions on this thread.
[Samsung Galaxy Nexus] mmuzzy:
Thanks. You're issue is what I hoped was resolved yesterday with the files grabbed from the ota but it wasn't 100 percent positive when I put out the update yesterday.
[Samsung Galaxy Nexus] wavedashdoc:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yeah still no GPS lock after 15 min. Worked fine on the 3/1 build. Even flashed Tiny's separate update just to see if that would fix it. No luck.
[Samsung Galaxy Nexus] mpressive:
Awesome!! I'm back in business. Tx!!
[Samsung Galaxy Nexus] ohiomoto:
Just updated (clean flash) and installed new radios. Everything seems fine. Maps located me impatiently and Navigation pick me up within 20 seconds. This was the first time I used it and I'm sitting in my office.
[Samsung Galaxy Nexus] blahb:
Thanks MMuzzy, :good:

I just quit trying to use TWRP and went back to CWM and had no problems. Running 3/1 w/updated GAPPS. Only issue now is my gallery doesn't work at all, no thumbnails, no previews... Any words of advise anyone?

I'd help reporting GPS issues but my office is in a brick building and I never get a lock inside 5 minutes no matter what build I'm on.
[Samsung Galaxy Nexus] mmuzzy:
Excellent. That sounds promising. Thank you. :)

Phew. Ok, one down. ;)

The issue with your ROM file getting deleted and gallery not working sound almost like a case of going from 4.1.x to 4.2.x. I think the missing ROM files might be in the /0 folder perhaps... this might also be the case with your pictures actually not being where the Gallery sees them. If not, there is a separate Gallery install in the Gapps link in OP that you can flash which also has picasa sync. It might be worth giving a shot.
[Samsung Galaxy Nexus] ohiomoto:
MMuzzy, I finally got around to making a donation. Should have done it a long time ago. My Galaxy Nexus is now working how it should have when it was released! Thanks for all of your hard work.
[Samsung Galaxy Nexus] billykxda:
Mike,

Finally flashed my Gnex from the 12/22/12 release to the latest French Vanilla ROM.

I did a squeaky-clean flash and everything is perfect - first time. As always.

I hit the Donate button again!

Thanks for your hard work on Gnex ROM's.

-bk
[Samsung Galaxy Nexus] mpressive:
Just sent $10 your way as well. Can't believe that I hadn't done that until now. Your efforts and attentiveness to supporting this endeavor has been a godsend. My phone has never performed as well as it does now. Thank you!!!
[Samsung Galaxy Nexus] ohiomoto:
A little payday for MMuzzy! :good:
[Samsung Galaxy Nexus] nighthammer:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Hey MMuzzy. I posted this in the ToroPlus thread yesterday but I've gotten no response. Do you have any clue what would cause my data to drop off when I activate the native AP? It worked on the last build but giving me crap now......

Sent from my Galaxy Nexus running MMuzzy's Jelly Bean 4.2.2
[Samsung Galaxy Nexus] factor0815:
Bluetooth Stack

Has the latest 4.2.2 addressed the continuing Bluetooth issues regarding obtaining metadata. I have a new Toyota, and everything worked great on 4.1..contact sync, song art and detailed info. Now I get no song info whatsover on the last 4.2.2. Does the new release fix this?
[Samsung Galaxy Nexus] subsonicbug:
mmuzz, just fyi while you work whatever magic you do that makes my phone awesome..

dirty flashed the 3/5 update over the 3/1 FV Rom (which was a successful clean flash at the time along with new gApps and radios, but did notice a somewhat slow gps response).

GPS seems to be locking quickly for me now in maps,navigation,gps test etc..
[Samsung Galaxy Nexus] keith7120:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

WillyJ. I tried your mods with the latest rom. All works fine until u try to connect the usb to a computer. Process. Media. Error pops up. I will wait till your next release
[Samsung Galaxy Nexus] jmark13:
I get the same error and I'm not using Willyjay's mods. If i go to settings -> storage, I also get a force close error of settings. I flashed the 3-1 ROM with GAPPS, and adbFreedom's 2-17 camera shutter and theme mods. Other than that everything works fine. Adb said to lay off his mods till he updates, so I know I will need to clean flash now that his mods are updated.
[Samsung Galaxy Nexus] blahb:
Maybe so but was using TWRP after clean flash, no OS, and couldn't find /0 when trying to install ROM, so restored to 4.1.1 from GN Toolkit...

You are correct, when I first tried the clean flash coming from 4.2.1 (FV 12/22 I think) using TWRP instead of CWM I deleted the ROM .zip so I had no OS to boot to. To my knowledge the only recovery I could do was a stock 4.1.1 recovery through Galaxy Nexus Toolkit. Luckily I had done Nandroid, Apps, SDcard backup through the toolkit as well.

So I got stock 4.1.1 up and running, moved required files over to the download folder, clean flash in CWM, flashed ROM, boot, Flashed radios, boot, restored apps, boot, restored sdcard, recovery fix permissions, boot and issues. Later flashed gapps-jb-picasa-20121011-signed.zip fix, I can now see files in the gallery when they are selected but no preview in filmstrip view. When I can see them they tile together slowly ~1 second AND camera can't save an image.

Odd behavior Image Path: /storage/emulated/0/DCIM/Camera/IMG_...jpg

BTW GPS seems okay for me so far.

I will grab 3/5 build when I get home and try that. If you have any advice as to how I should restore sdcard info please let me know. As of know I'm using GN Toolkit.
[Samsung Galaxy Nexus] pkgnex:
Update... After rebooting into recovery and wiping cache & dalvik, then driving around for a few minutes, my gps seems to be locking without much delay now. Still rocking 3-1 french vanilla.
[Samsung Galaxy Nexus] AznInertia:
I did a clean flash of the 3/5 ROM and unable to get a GPS lock at ALL.

- Cleared cache/dalvik.

- CLeared google map cache

- Under location access I'm trying to see if GPS satellites only can get me a signal (if I use wi-fi&mobile network in conjunction I am able to get a lock)

- Seems like something is wrong with getting a hardware lock just using my gps chip

Update, on GPS Compass map I am able to lock on 3-5 satellites

- Google Maps I have to wait a few minutes for lock on, if i check off both GPS Sat and wifi&mobile I get instant lock. Hurray