yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dwilliam16:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Goo is back up, but it can't find the files :confused:

EDIT file popped up but download failed
[Samsung Galaxy Nexus] mmuzzy:
I don't think the site went down... just the files aren't there. I'm not jumping to conclusions on that one but let's just say that would suck.
[Samsung Galaxy Nexus] aalbertson:
Ugg, yeah I wiped my phone completely before realizing goo was down for the files. needs to get fixed ASAP!
[Samsung Galaxy Nexus] RW-1:
Got to be their site, database related, even doing the install recovery script (which I use to check if a newer version of TWRP is out) results in "no recoveries found for your device"

either that, or everyone got banned from goo at the same time hehehe ...

---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------

Completely, as in the SD partition as well?

That does hurt ...

Even on goo's main web page, browsing dev's returns for "Z" named dev's, that's it.

They lost data big time.... MMuzz I'd contact someone over there ...
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Here comes the black market hosting. :D This who have a local copy will be posting on ebay. Lol
[Samsung Galaxy Nexus] dwilliam16:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Too bad this would overload dropbox...

Torrents? ;)
[Samsung Galaxy Nexus] mmuzzy:
There's always something like dev-host. I just prefer Goo.im because of the multiple ways to grab the ROMs. I lose steam after uploading 12 ROMs the first time so the idea of mirroring 'just in case' doesn't appeal to me normally... let alone the bandwidth. Ugh.
[Samsung Galaxy Nexus] Quod:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'll upload 3/7 fv to Drive. I think it can be shared with 200 people so that should be good until goo is straightened out.
[Samsung Galaxy Nexus] dwilliam16:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

When I get it I will try and do the same
[Samsung Galaxy Nexus] Quod:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Mmuzzy's French Vanilla 3/7

https://docs.google.com/file/d/0B0Jkb52HeCYzYTJRNksxdGpvd3c/edit

If anyone needs the latest gapps let me know.
[Samsung Galaxy Nexus] RW-1:
Homeboys in a van under the freeway.

"Hey... c'mon over here, got a ROM for ya .... cheap."

"Yeah ... it's just as good as MMuzz's ...."
[Samsung Galaxy Nexus] Quod:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I just made the file public so if you tried to download before now you can try again.

My first time sharing a file on drive :)
[Samsung Galaxy Nexus] dwilliam16:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

OK, so here is my contribution to this Goo-less day.

toro_signed_030713_212927

https://www.dropbox.com/s/733r0ulr33fobs6/toro_signed_030713_212927.zip

Gapps

https://www.dropbox.com/s/ln1oymj2emx9zlw/gapps-jb-20121212-signed.zip

Vzw 4.2.2 radios ( just because)

HTTPS://www.dropbox.com/s/fvpkptyxfha8htq/VZW_JDQ39_radios.zip

2100 mAh battery...thing.. :-/

https://www.dropbox.com/s/yxfsxned7sfq2ys/Mmuzzy_021713_2100mAh.zip

Hope this works. Let me know cause all of this was done on the phone waiting for a bus. Love unlimited 4G :)
[Samsung Galaxy Nexus] artjef:
Looks like either a database issue or they lost a couple of drives. The only files showing up are: teameos through zyr3x. It is definitely Monday.

---------- Post added at 05:08 PM ---------- Previous post was at 04:48 PM ----------

They seem to be be in the middle of file recovery. Developer files now available are: slukk through zyr3x.

Looks like they have more problems, the server is offline.

Everything seems to be back up and available.
[Samsung Galaxy Nexus] jesssiii:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Too bad Mmuzzy's not called Zzummy?
[Samsung Galaxy Nexus] nitsua98:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Goo is back just FYI
[Samsung Galaxy Nexus] mmuzzy:
I... don't get it. :P
[Samsung Galaxy Nexus] nitsua98:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

:D
[Samsung Galaxy Nexus] mmuzzy:
Oh I missed that. I had read Marc's comment but I must have spaced out. :P I realized Goo.im was working backwards when they were about at S. After a couple F5s I decided it wasn't going to go faster by my watching it.
[Samsung Galaxy Nexus] xweb10:
Great ROM. For some reason, since 3/6 release, I am having a heluva time getting a GPS lock. What are the tricks to get this locked?
[Samsung Galaxy Nexus] mmuzzy:
Most importantly, be running 3/7 release. I haven't heard anyone say they've had GPS lock issues since that build. If you are on it and you dirty flashed try using an app like GPS status to refresh the A-GPS data.
[Samsung Galaxy Nexus] peacewise:
goo looks to be back up.
[Samsung Galaxy Nexus] xweb10:
Mmuzzy - Thanks for the reply. I am on 3/7 now. I have dirty flashed since 3/1 and would really like to stay away from a clean flash at this point, but I gotta do what I gotta do! I am using GPS Status, too. Very odd. I'll try some more tests.

GPS has always been horrible on the GNEX but horrible is better than no lock. ;)
[Samsung Galaxy Nexus] mmuzzy:
I probably flash more than most and I always clean flash. I do a nandroid and titanium backup of the apps/data (not system). I clean flash with the steps on OP and then restore my apps making sure I'm not restoring the ones I don't mean to. It's the best of both worlds, you get a clean install and all your apps back too. I know it's not optimal to do the app data restore but I've rarely had an issue. It's all about being mindful of what you're restoring.

If nothing else do the nandroid and then clean flash to see if it'll be a fast lock with the clean install. That would be my advice.
[Samsung Galaxy Nexus] xweb10:
Ok. Rebooted, got new GPS data and it locked after about 1 minute.
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

So I realized that I had a ton of Roms taking up space and started clearing things out. I must have deleted something I wasn't meant to because now I'm getting FCs with gallery/camera and an occasional FC with GTalk.

I'm running the 0307 FV (up to date gapps, radios etc) and camera was working fine yesterday somewhere around 3am. I didn't venture into the system files so I'm curious what I could have possibly trashed to trigger all of this.

I don't keep enough apps to worry about backing them up and always clean flash with super wipe. Which I suppose is what I'm going to do now.

Any chance anybody has a clue to what I might have deleted from the 'sdcard' partition to cause this? Pretty sure I only got rid of ROM zips and maybe a folder or two left behind from apps that are no longer installed.

(Sorry for being such a wordy person..)
[Samsung Galaxy Nexus] mmuzzy:
Try doing a dirty flash and see if the FCs stop. That'll at least tell you if it was something deleted that shouldn't have been. Otherwise try clearing some app cache especially for the offending apps, permission fix, etc.

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

Kevdliu is working on the Quick Settings Tile MOD! Hopefully we'll have something new in an upcoming build. Please consider donating if you can to Kevin. His work ends up in a ton of ROMs and I don't even think people realize it. http://xdaforums.com/showpost.php?p=39036973&postcount=566
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Just tried the dirty flash, no dice. Going to try the app cache and the permissions now.

***clearing app cache and permissions led to some strange results. but basically, it still wasn't working as it should, so i ran super wipe and did a fresh install. camera still wasn't working, so i went to recovery and formatted everything i could find.. including the OS apparently.. never re-installed the sdk after upgrading to win8 (which i'm hoping will still work, as I didn't see it listed as officially supported), so working on that now so i can try adb side-loading the ROM over...

i swear, sometimes i think i have an evil subconscious that screws things up on purpose just to give me something to do..
[Samsung Galaxy Nexus] BackInA88:
Willy, will this work on 3/7?

I like your battery and zenyth keys with the blue glow back ground.

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

I reverted to stock using the gnex toolkit after spending most of the night trying to format everything possible and wiping caches and fixing permissions with no luck. Completely clean Stock setup is still giving me force close with camera and gtalk.

I'm done for now. Tomorrow (later) I'll get root back and see what's going on in dmesg. That's all I can think of. I'd rather have french vanilla without a camera than this stock 4.1 though, that's for sure.

Sometimes my ps3 needs a good firm smack on the side to read a disc... maybe I'll try that approach next... :banghead:
[Samsung Galaxy Nexus] mmuzzy:
Completely stock image is giving you FCs? Even before restoring anything? If so, it might be time to consider something other than a software issue.
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yeah that's what I'm afraid of. I had two gnexes before this that ended up with faulty WiFi. Dmesg would say something like wlan0 err device not found..

all I did was update the radios and gapps (and delete a ton of obsolete ROM zips) wouldn't think it would screw up this horribly from that.
[Samsung Galaxy Nexus] jesssiii:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Sounds like a gapps problem to me. Try reflashing gapps or using a different gapps package.
[Samsung Galaxy Nexus] mmuzzy:
I would agree but he spent the night trying everything including going back to stock using the gnex toolkit. At that point, even the SDCARD partition is factory fresh. I'm thinking that if he still had the FC it probably isn't anything to do with software.
[Samsung Galaxy Nexus] RW-1:
That does sound bad if back on stock. But my advice now would be to ADB the stock image, bootloader and all back on it instead of the gnex toolkit, just to be absolutely sure ...

My methods for ROM'ing is to make a backup, then depending on the ROM either a clean or a dirty, you can always (hopefully) go back to the backup made.

Funny thing though, when I first went to TWRP, I guess I did make it permenant, but didn't realize it, so there I was, with each flash, hitting ADB to re-push teh recovery and then use it hehehe .....
[Samsung Galaxy Nexus] 1fzfe:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I know this sounds weird, but turn it off, pull the battery, reinsert and boot back up. Had the exact same thing happen to me several months ago and nothing would fix it but this.

This is in reference to the gtalk / camera force close issue.
[Samsung Galaxy Nexus] pkopalek:
Looking for a 4.2.2 ROM that everything actually works in?

Unlike CM, AOKP, PA, and virtually all of the others, this one is it.

Latest FV, Tiny, (1.35 with intX gov), and the 4.2.2 radios.

More stable than the BONE STOCK 4.1.1.

And everything works.

We need more developers like this. With a phone whose source is open (a Nexus device), there's no reason that this (everything working, virtually) can't be accomplished with CM, AOKP, and all of the others. I, for one, can't stand when functions (that came with my phone) don't work. This ROM is the bee's knees. Thanks for this.
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Well said. You certainly don't get to 850 pages with a bad product. Unless there are a lot of complaints I guess... So maybe you do. But that's not the case here at all. This guy knows what's going on.
[Samsung Galaxy Nexus] mmuzzy:
Good procedure. Pretty much what I do which an occasional off-phone backup copy.

I was starting to formulate the same thought too. A battery pull could clear things that persistance in power source might retain until a battery pull. Good idea.

Thank you. :)

Thanks. It is funny though. A ROM that strives to be stable without slapping on features everyday, and I was guilty of trying to please everyone at one point too, can slip quietly off the main page on occasion. I had to learn to be ok with that. It happens on some of the less populated device forums. As for the number of pages, I guess I should start a new thread for Key Lime Pie, this one has gotten a bit hard to search.
[Samsung Galaxy Nexus] factor0815:
Bluetooth Metadata

Has anyone actually had success in getting metadata from their phones to their Bluetooth enabled car stereos. My Toyota used to show the artwork and song info on the display until 4.2 came along. It will transfer my phone book info, but no longer gives the song info.The phone itself connects and sounds great.

I asked about this back on March 6th, but no replies here. It's a great feature, and I'd hate to roll back to 4.1 . Any suggestion would be greatly appreciated.
[Samsung Galaxy Nexus] mmuzzy:
As far as I know, that's still the case in 4.2.x because of the new BT stack. I haven't heard of any improvements to that situation.
[Samsung Galaxy Nexus] hotelmrrsn:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Just came by to say thank you for the work you've put into this ROM. As others have said just above me, I was looking for something very close to stock that "just works". While I enjoy tinkering a bit, I don't enjoy data drops, unexplained lag, UI redraws, and the like. So, as mentioned above, if your'e looking for a close to stock experience that "just works" (and works smooth as butter i must add) then this is the ROM for you. Again, thank you for the time you've spent building and communicating. ROM's like this one give my phone legs, I no longer feel the need to go buy something new.
[Samsung Galaxy Nexus] Frixtion:
This just a suggestion regarding georgeascott's issues. Im going to do my best to explain please forgive me if its thought to be irrelevant or unclear.

i at one point reverted to 4.1.1 after being on 4.2.1 on 4.1.1 there wasnt the emulated storage i thought this might be a good time to clean up the o/emulated storage side. I deleted everything from the o/emulated side and thought the next time i restored 4.2.1 CWM would just move everything over for me from the original 4.1.1 sdcard to 4.2.1 o/emulated but it didnt. I had to revert back to 4.1.1 copy all the files and folders from SD and paste to the o/emulated then restore 4.2.1 and all was good. But without doing that i was getting all kinds of force closes.

If what I said was completely wrong or irrelevant to his issues forgive me i just wanted to share my experince of a similar issue and possibly help.
[Samsung Galaxy Nexus] georgeascott:
pulling the battery is something i tried a number of times. including reseating the sim card even though i didn't think it would have an effect.

like Mmuzzy hinted at earlier, I was worried it was going to end up being a hardware issue, so i took the sucker apart. I don't see anything alarming so on a whim decide to boot it up without the sim card or the outer shell. lo and behold, i have a working camera.. i don't get it. perhaps my earlier idea of smacking it around a bit would have worked just as well.. Now if i can only get the shell back on and back to FV without messing anything else up.
[Samsung Galaxy Nexus] ericstephani:
I am using the 3/7 build, did a clean flash, and used GPS Test to initiate an update of AGPS and still experience very long lock times. A friend who has a VZW GNEX on the stock rom gets a lock within a few seconds when we are right next to each other. I can see 7-9 satellites in GPS Test view but now of them are "used".

What does the - GPS Lock Tweak (convolution) feature do?
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

It was an alternative gps config file. It's not the one in the rom now though, we're using the stock one.

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

I am using this ROM and loving it, I have a question as I don't follow the mod scene as much as I like. There are two features I would like to add to my ROM. A launcher that rotates in landscape and force close on long back press. Does anyone have a recommendation on which launcher I should use that is simple and how I can attain force close on long back press?
[Samsung Galaxy Nexus] georgeascott:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Thanks again for all of the great suggestions earlier. Still not sure what caused my issue or even what truly resolved it, but I'm finally up and running this awesome ROM again (and I've got a sparkling clean system underneath it all).
[Samsung Galaxy Nexus] GalaxyNexus1st:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'm getting horrible battery life, so bad most of the time ill take my sim out of my Nexus and put it in my Droid 4. Im using Franco kernel. Anyone else having this problem?
[Samsung Galaxy Nexus] marc.ientilucci:
i have also noticed pretty poor battery life. i chalked it up to having gmail, exchange, facebook, twitter, instagram, google talk,google + all running with push notifications... the only thing i dont get is that ive had these all running in the past before and since they are running on "Push" notifications they houldn't be polling for updates causing batter drain. when i check app's nothing really stands out that is sucking battery life. i keep screen brightness on auto, however i dont use wifi.

i will say, if i was able to get incredible battery life on his phone back in the day on CM8 or 9 (i forget which one they skipped over to get to ICS) then i feel its possible to get great battery life now.

i use stock kernel with no type of mods (besides the ones included in the ROM)
[Samsung Galaxy Nexus] GalaxyNexus1st:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Yeah I was on mobile network look at how bad it is. I also use the very apps

You use
[Samsung Galaxy Nexus] Magnus_CA:
This is not an accurate statement. There is no need to log in and uninstall wallet before flashing. I've performed over 50 clean installs and never bothered doing anything special with Wallet. I just used it yesterday without issue yet again.

Great ROM mmuzzy.
[Samsung Galaxy Nexus] factor0815:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I flashed Franco's latest nightly and my battery life was cut in half. I always had good luck with his kernels in the past, but this one was problematic. Flashed my backup and all is well.
[Samsung Galaxy Nexus] GalaxyNexus1st:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'm also running Franco and its the worst!
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Try the AK Cylon or Tiny's kernel.
[Samsung Galaxy Nexus] KnappyRoot:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

I'm running Tiny and getting good battery life (especially when I don't use my phone!).
[Samsung Galaxy Nexus] lumpysherman:
I was using Tiny's, the new radios, and beats mod and was getting horrible battery life. Went to the 3/07 using stock kernel, 4.1.1 radios, and no beats mod. Doesn't sound as nice but better battery life.
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Beats probably uses some extra battery but the tiny kernel was likely not the cause of your drain unless you were overclocking. Tiny's kernel is very efficient with the battery.
[Samsung Galaxy Nexus] dwilliam16:
Love this. If nothing else works, smack it around - at least you'll feel better. :cyclops:

Sort of goes along with "If it's not broke, fix it 'til it is!"
[Samsung Galaxy Nexus] standupdad:
Cell Broadcasts and Amber Alerts

mmuzzy (or anyone else able to help..)

This is something that I searched for, but couldn't find a post about... Cell Broadcasts and Amber Alerts.

I don't think much about it because if you don't get a broadcast, you just don't think something's broke... until a coworker says that they got a broadcast on their phone and wondered if I got it too, and then 2 more asked (It was an Amber Alert for the douche Step-dad that took his 16 y/o stepdaughter and her kid. I'm in Ohio and they may have come here).

We're all on Verizon. Three of us with smart phones, one with a dumb phone. I'm the only one rooted and/or with a custom ROM (French Van). My Nexus, a Note 2 (not modified), Moto RazrM (not modd'd) and a Brightside. I'm running FV 3/1, Air Kernel 580 (for 4.2.x)

I checked the settings, and they're checked/enabled.

Any thoughts about why it may not work from the Hive?

SuD
[Samsung Galaxy Nexus] mmuzzy:
The cellbroadcastreceiver.apk is compiled instead of copied as a binary. I added it as a build target so every time the repo is sync'ed if there were any changes to the app they'll be in the new apk. I know I've received weather alerts this past winter through it but I can't say when I last received another type of alert. It's one of those things that's difficult to test normally.
[Samsung Galaxy Nexus] standupdad:
Thanks for the direct reply mmuzzy. Do you have any thoughts on what I can do, test, flash or install?

I didn't get any alerts this winter, but then again I'm in SW Ohio, and there wasn't a lot of severe weather, but I know I got them before on my previous phone, HTC Rezound. I can't say that I remember ever getting any from y i515, but I've only had it 7 or 8 months.
[Samsung Galaxy Nexus] mmuzzy:
Honestly I can't understand why the compiled apk would be different from the ota but the only thing I can say is swapping out that apk. I have no problem with just bundling that one but it seems strange that it would matter. As for testing it, the alerts come from the carrier. I would hope they wouldn't restrict alerts to non rooted phones and I have no reason to believe they do.
[Samsung Galaxy Nexus] standupdad:
Unfortunately, I don't know anyone locally that's got the phone and rooted to see if they are getting their alerts. And since 3 other Verizon coworkers got the alert, I expect that the service is working... sans mine. Why would they send it only to non-rooted? I don't expect that's the case because my phones have always been rooted and/or modified in one way or another and gotten the alerts.

Are you able to pm me your's, and I can install it separately. I don't want to de-rail you for anything that you're working on because this isn't a fire that seems to be affecting the community. No need to make something available to the community unless they're all having the same issue. This is why I chose to post here instead of sending you a PM. I was hoping others would chime in and say... "Working. Always has." or "You know... I don't ever remember getting alerts". I was really hoping that someone from the Dayton, Ohio area could chime in, if there is anyone here, because they should have gotten the same alert.

Most people around here freak out when their phone goes off, and I tell them where they can change the settings. In truth, why would you? I want to know if my neighbor's kid is missing. I want to know the make and model of the vehicle I should be looking for when something causes the alert in the first place. I've got 3 kids. 1 has to wear a bell around his neck so we always know where he is. I'd prefer a collar and an electronic fence, but some say that's cruel to tear up your lawn.

Anyone here in the community have anything to add about the success of their Alerts coming through.
[Samsung Galaxy Nexus] jon9314:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.2 - JDQ39

Works for me. Got one this morning. Amber alert for w.v I am in n.e.Ohio. I'm on latest French vanilla

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2