yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] j0hnnyth3f0x:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

It's in >settings >about phone >status then look at signal strength. Those are unfortunately issues commonly encountered with 4.2 & 4.2.1, that are supposedly fixed with 4.2.2... we'll see once mmuzzy is able to sync the source and work his magic!

EDIT: Also, I've personally never run into problems restoring from my Google account so I don't believe that would cause issues.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] JayBeezy802:
Ohhhh okay. Since I was running 4.1.1 I never realized 4.2.1 had those types of issues! (I guess I don't use my Nexus 7 enough either haha).

Cool well, I'll wait till the master known as mmuzzy get this updated to 4.2.2 and will keep reporting back!
[Samsung Galaxy Nexus] mikey2487:
hey mMuzzy will you ever have theme chooser in your french vanilla edition or will it always be pure stock?
[Samsung Galaxy Nexus] veloslave:
That is why "Vanilla is part of the name... DaMuzz doesn't really get into that type of mod although adbFreedom has posted some themes in the thread. Read a little deeper and you will find out more.

OTOH... you might wait to see if the 4.2.2 makes any changes that adbFreedom needs to change his mods to comply with. FWIW
[Samsung Galaxy Nexus] mmuzzy:
You are correct sir. :)
[Samsung Galaxy Nexus] swallick:
Your vanilla 'pure AOSP' release is the exact ROM I wanted for my Vzw G Nexus. Thanks, friend. The 2/2/13 release hums along nicely.

Just sent a Paypal your way. Thanks are nice, but I thought that was nicer.
[Samsung Galaxy Nexus] darklordofthesith:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Having better luck this evening there sir Mmuzzy?
[Samsung Galaxy Nexus] AndroidFan23:
Not sure waiting 90 seconds to put the sim and battery back in helped, but I sure noticed a difference.

Btw, I am loving this rom and 4.2

Thanks MMuzzy!!!

---------- Post added at 04:53 PM ---------- Previous post was at 04:46 PM ----------

Yezzir, I also remembering reading that somewhere too and how google did what apple did indicating more bars when in fact the signal isn't as strong on 4.1. Perhaps, 4.2 displays a more accurate signal.
[Samsung Galaxy Nexus] mmuzzy:
I appreciate it :)

I just tried again for kicks and no dice yet.

You're very welcome :)

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

Hopefully we see the update soon. I feel like I'm tethered to the silly computer.
[Samsung Galaxy Nexus] chazzdjr:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Paranoid Android just referred to 4.2.2 as a "merging hell" over on Google +. Lol
[Samsung Galaxy Nexus] mmuzzy:
I'm assuming the guys who are merging are using the old device folders. I haven't seen a complete repo sync yet.
[Samsung Galaxy Nexus] tiny4579:
So when I mentioned I was trying syncing, it was CM10.1 with the AOSP projects that were not forked by CM. I think this AOSP build is the real deal but it's hard to say with 100% certaintly due to the lag of projects with 4.2.2_r1 tagged. It's possible the device repos didn't change. CM is working on updating their ROM but they are wondering the same thing about the device repos not changing. So far with mwalt's build, I'm quite impressed with what I see so far. WiFi seems to still cut off during sleep sometimes but the fluidity changes are nice.
[Samsung Galaxy Nexus] tiny4579:
mmuzzy, I think you have a point about the older device folders. I think a OTA-built ROM is more complete at this point than AOSP. Considering my 2.7 kernel boots fine on an AOSP build at this point and not on mwalt2's ROM, I think AOSP isn't up-to-date yet.
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Thank you, Tiny. That helps a lot. I'm getting mixed signals on how to proceed and that input solidified my feelings about waiting on the repo to be complete.
[Samsung Galaxy Nexus] mwalt2:
That's weird about the kernel, it does suggest that things still aren't complete on aosp. I think I'll wait until they push the updated binaries. They usually always rename them, even if they don't change anything. The gsm rom with some of the toro specific files seems to be working fine for me too :). I just don't like not having the latest and greatest lol. It sure would be nice if we could get an updated verizon factory image. Some of the files we have to use are from 4.1.1, which was a while ago.
[Samsung Galaxy Nexus] trackzero:
Compiling a ROM from AOSP for a specific device...

So, maybe slightly off-topic here...but I mostly use MMuzzy's ROM for my Verizon GNEX, so this is where I lurk the most. :)

I set up Ubuntu, managed to set up a functioning build environment for AOSP, and I've successfully compiled a ROM for the emulator...but then I'm just not able to figure out how I get to the next step and build for a particular device...in my specific case, it'd be either toro or mako...Can anyone point me in the right direction? I feel like I'm just missing a basic command here...

:confused: TIA,

-TrackZero
[Samsung Galaxy Nexus] mwalt2:
If you just set it up using the 4.2.2 branch, aosp seems to be incomplete right now. There are no specific devices on a fresh repo sync. It's done the same way where you type lunch and then the corresponding number to what rom you want to compile. To get a working build for toro from aosp, it requires several things to be added (mostly in the vendor folder and some in /device/samsung/toro). You can look at what I am/was using under the /vendor directory on my github here. I forgot that I haven't uploaded my /device/samsung/toro yet, but I can just .zip it and let you look through it and set things up how you want.
[Samsung Galaxy Nexus] marc.ientilucci:
100% waiting on for a genuine AOSP release, take all the time you need Mmuzzy!
[Samsung Galaxy Nexus] butler360:
Battery drain AFTER airplane mode?

I've seen this with the last two Mmuzzy ROMs I've used (latest, plus a version or three back) a few times. Since Angry Birds now has just ridiculous amounts of ads I will put airplane mode on when I play it. Before airplane mode and during it, the battery drain is completely reasonable. Afterwards it just tanks and I'm left with 4% battery where I would usually have over 50%.

I am attaching a screenshot where his should be apparent. You can see the battery drop off right after mobile signal comes back.
[Samsung Galaxy Nexus] notstevek:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Anyone care to help me with battery life? Screen always takes up up to 70%, it's usually always on darkest brightness, never on 4g, GPS is always off, under clocked to 700mhz, and I get ~4hours on my 2100MAH battery. I originally had to carry an extra around to get me through 7 hour days, until I got fed up and got a 3800MAH battery (which gets about 12-20 hours depending on usage with same settings above..) I don't understand how I see people with 10hour battery life on 4G.

Sent from my MMuZZY'D SCH-i515
[Samsung Galaxy Nexus] RW-1:
Interesting that this morning I got a goo ROM update available notification, never did up till now...
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

The initial drop is likely due to all of the sync and location services gaining back their access and all chunking at the same time.
[Samsung Galaxy Nexus] lumpysherman:
Update message

I did as well receive a Goomanager ROM update notification but no download. Hopes and dreams of an early morning mmuzzy 4.2.2 update blown away in a giant sigh.
[Samsung Galaxy Nexus] AndroidFan23:
Using an HD wallpaper could be the culprit. I've noticed in the past that it drained my battery quicker.
[Samsung Galaxy Nexus] 00negative:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

I recommend looking at someone else's build setup, not sure mmuzzy's is public but you might try rascarlos or cm or aokp they all do it a little different but are good references on how to set it up. Paranoid androids website has a good write up for setting up your build environment as well

But you need the proprietary files from Samsung and Verizon and right now the 4.2.2 source is incomplete or something and causing some issues building
[Samsung Galaxy Nexus] mmuzzy:
I imagine other ROMs must have had this happen too. I didn't touch Goo.im in a few days so it must be something on their end.

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

I'm still watching the repo. I will warn you guys though... it's Valentines day so date night first if we see it later. ;)
[Samsung Galaxy Nexus] notstevek:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

~50kb non live wallpaper and I want to point out it's with every ROM not just my man MMuZZY

Sent from my MMuZZY'D SCH-i515
[Samsung Galaxy Nexus] Magnus_CA:
A couple points...

4 hours of screen on time with a 2100 mah battery is excellent. Anyone that says they get 10 hours screen on time (even in airplane mode) is full of sh!t.

54 minutes into a full charge is not a valid sample size. What does it look when near empty?
[Samsung Galaxy Nexus] AndroJak:
I use GSam Battery Monitor to help me understand what is moving the electrons. When I was on 4.1.2 I think I had my best battery life, I could get 3 - 3.5 hours screen time occasionally on WiFi. For some reason this 4.2.1 seems to be harder on the battery for me, both on WiFI and on 3/4g, hoping 4.2.2 will be better..
[Samsung Galaxy Nexus] RW-1:
Hi gang! Just popping in ...

It was a goo issue, because when I went to check it this morning, I had several server offline messages as well. Checking the thread I knew Mmuzz was still doing the "right thing" by awaiting repo to be correct for devices, etc.

Ok, that said, where is it? :)

No really ... when you release it, I take it my actions will be flash ROM, flash GAPPS, and then will the Zenyth soft keys that adbfreedom made for me for the pre 2/2 release work for me?

Thanks...
[Samsung Galaxy Nexus] mmuzzy:
Nuttin' yet. We keep checking though.

I'd probably assume MODs will be a bad idea until our crack team of Android beautification experts can take a look at things. ;)
[Samsung Galaxy Nexus] notstevek:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

No no no. That's not 4 hours of straight or constant usage. That's like using the phone to send 10 texts and post a status up, and just check the time. Constant use (browsing Facebook or IG without turning the screen off) is about ~1hour

This surprised me just taking this screenshot now and this is on a 2100MAH, but I only sent about 20 texts and posted one status about valentines day for my girlfriend, rest was idle as I was doing brakes on a car / sleeping haha, but I did flash a new kernel and 2/3/13 build last night.

Sent from my MMuZZY'D SCH-i515
[Samsung Galaxy Nexus] RW-1:
I'm sure it's great, but ... not seeing anything breathtaking that would make me want to up to it from this fabulous 4.2.1 we have now, what with the mods and all. :)

And being toro, what may or may not be the most important (depending on if you are having issues) would be new radios, which we wouldnt have anyway, because that occurs when VZ finally releases it, and we all know that will be next week (sarcasm, they are releasing Gingerbread for the GNex, they didnt even realize that it began with ICS hehehe ...)
[Samsung Galaxy Nexus] techspecs:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Bug fixes are always a win.
[Samsung Galaxy Nexus] donnyp1:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Did the source get fixed? I noticed several 4.2.2 on that "other" site
[Samsung Galaxy Nexus] mmuzzy:
I haven't been able to sync yet. It's possible to make a ROM by combining the bits that are, OTA parts, and older files. As for the Toro I'd probably look into mWalt's ROM for anyone that wants to go to 4.2.2 now. I'll update when I can update the way I normally would build the ROM.
[Samsung Galaxy Nexus] donnyp1:
Thanks for the reply. I had noticed all those other roms said "built from source" so I was guessing all was well, but i guess not. Good luck on getting the build going.
[Samsung Galaxy Nexus] Namrepus221:
Finally have 10 postings so I can finally say that I flashed this rom and I so far LOVE it. Thank you MMuzzy!

I've not had any real issues with it aside from the issues I have had with the GNex (the wifi shutting off while sleeping dispite it being set not to being a prime example)

I just love this ROM.

I do have one question. How is the kernel set up? Would it be advisable to use something liek SetCPU to modifiy the governor for the CPU? Or is it pretty much optimized right out of the box?
[Samsung Galaxy Nexus] RW-1:
Gads!

Gang, listen to mmuzz, the race to be first out the door does not guarantee that that ROM will be the winner.

Worth waiting for IMO where it isn't pieced together just to have it.
[Samsung Galaxy Nexus] schteve:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Agreed, no FrankenROMs allowed on this phone!
[Samsung Galaxy Nexus] tiny4579:
Mmuzzy, I think you should check this Google groups thread out:

https://groups.google.com/forum/#!searchin/android-building/4.2.2/android-building/WY6KRt8v738/V0whHCJHZsgJ

Seems like AOSP 4.2.2 is supposed to be out but the manifest didn't get updated and I hope sometime today it will be updated.

Also, I think the reason the 4.2.1 kernels still work fine on these AOSP 4.2.2 built ROMs is that the binaries in AOSP are from 4.2.1 and haven't been updated to 4.2.2. I doubt it has anything to do with the GNex device tree.
[Samsung Galaxy Nexus] RW-1:
I would agree there tiny, thats the major issue with having a VZ Gnex, AOSP may get a major or minor update, but we have to wait as the device specific stuff trickles out, am I right?
[Samsung Galaxy Nexus] mmuzzy:
Thanks Tiny. I saw the thread where JBQ talked about "updating often" but it seemed odd that often=broken. From what you say, it seems like it would be a bad idea to try to update binaries until we have updated device files and kernels anyway. EDIT: I said kernels because of multiple devices. :P

It sounds like it. I'm working on getting framework stuff together now with the new 4.2.2 folders. Currently the only thing that didn't go smoothly is Kevin's Quick Settings MOD, so that will mean a manual laying of hands to try to get that put back in. I was thinking of releasing an update with what I had but perhaps I'll wait until we get the device files and binaries.
[Samsung Galaxy Nexus] tiny4579:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

They pushed the kernel source recently and I updated it today. Im pretty sure they updated the kernel for all devices. Not sure if all have GPU updates in the kernel.
[Samsung Galaxy Nexus] RW-1:
Kevin's MOD is much more involved than even the changes that Google made to QS natively, and a much better implementation IMHO.

Yeah, a lot of work in store, I would wait until all is in order, resist temptation! I know you want to get it out there as much as we want it, but it's all good. One well thought out release will always be better than one release and then 57 updates to make corrections for everything everyone will try to do to it, after all, it's not like the current ROM is sucking by any means :)
[Samsung Galaxy Nexus] mmuzzy:
I'm leaning toward keeping the device files and kernel a matched set until they push them out to the repo for two reasons... I don't normally custom compile kernels for each device and I can't test on most of the devices the ROM is compiled on. Valid or am I missing the mark?

I've been working on putting the Quick Settings MOD in by hand and I'm currently trying to compile it with the 4.2.2 framework now. I really dislike how they have long press to toggle on BT and Wireless in 4.2.2. Fingers crossed.
[Samsung Galaxy Nexus] tiny4579:
Definitely a valid reason. In this case, I don't believe updated device repos will solve anything as the problem is in the precompiled binaries from 4.2.1 being out of date with the new kernel. I can't speak for any of the other supported devices and I can totally understand why you're waiting.
[Samsung Galaxy Nexus] mmuzzy:
Well, I've gotten Kevin's Quick Settings MOD merged into the 4.2.2 framework. A couple subroutines were renamed so I just had to figure out how to call them but it all seems good now. Other than a new kernel and binaries we're good to go on 4.2.2.
[Samsung Galaxy Nexus] chazzdjr:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

I love it when you talk to me like that!
[Samsung Galaxy Nexus] mmuzzy:
I lol'ed :)
[Samsung Galaxy Nexus] SparkyXI:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

I lol'd too.

Haven't been around much because I'm having no problems. Looks like everything is on the up and up, as always. Still can't imagine another ROM on my phone. Keep up the awesome work, as always, and let me know if there's anything I can do to help out
[Samsung Galaxy Nexus] mmuzzy:
I appreciate it. I'm going upload a ROM into Goo.im with most of the 4.2.2 goodies just to see if it looks ok so far. I'm not sure it'll finish before I call it a night since there's only 7 minutes left of Friday here.

To recap what we have:

4.2.2 base

4.2.2 framework

4.2.2 apps

with the Enhanced Power Menu, Expanded Desktop, HSPA+ indicator (vzw won't care), recent apps clear all, and the Quick Settings MOD ported.

But the 4.2.1 binaries, kernel, drivers, until the repo coughs up the rest of the goodies.
[Samsung Galaxy Nexus] mmuzzy:
It's 1am eastern time and I'm uploading a 4.2.2 ROM to play with... see previous posts for what to expect. Let me know how it goes.

This is unofficial so don't tell anyone. ;)

http://tinyw.in/4JCw

edit: It's finished uploading now.
[Samsung Galaxy Nexus] lchupacabras:
It's 4 in the morning. I'm downloading this now. .D.
[Samsung Galaxy Nexus] markculton:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Installing now. Will keep you posted.

Thank you!

(Edit - After installing, every time I boot up I get system UI has restarted message. Also, some quick settings shortcuts are missing - Bluetooth, GPS, and WiFi hotspot. I think I will try wiping data since I only wiped cache and dalvik)
[Samsung Galaxy Nexus] mmuzzy:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Hmm. Clean install go any better? I would do a backup and clean flash. Lots of changes this time.

If no go with that I guess the quick settings are still a problem. They were working for me on the 7 :/
[Samsung Galaxy Nexus] gener1c:
New Bug - When in the camera app and I tried to use effects the app will crash. Didn't know about bit until my daughter tried to use it. Its then only issue I came across. Everything else runs like butter.
[Samsung Galaxy Nexus] RashAPu:
Anyone else having the issue of not receiving notifications for any app? I've gone into APP info, and reset them to default.

P.S. Most excellent ROM, I love it.

Edit: Just restored app preferences to Default (via app info) and opened Facebook, received the message saying (sic) "Push notifications disabled because your phone does not support them"
[Samsung Galaxy Nexus] mmuzzy:
I just tried all the adjustments and the app didn't crash. The only effects I see are scene mode and adjustments like white balance, etc, so I'm not sure if perhaps I'm not finding the right menu. Is this the stock camera? I wonder if you need to clear the app data.

Thank you. Regarding the notifications you might want to check app info and see if they're turned off for the app. I don't believe there is a global setting but I could be wrong. Oops. I missed that you checked it. Sorry. I'm getting notifications and have been on the same install since the 22nd. Not sure what it could be.

If you restored apps from backups you might try uninstall/reinstall of the apps that aren't pushing notifications and see if it helps. If you dirty flashed the ROM and it's all notifications you might want to try a clean flash. Nothing clears a stuck notification like a good flush. ;)
[Samsung Galaxy Nexus] RashAPu:
Thanks for the quick reply, I started poking around, I restored apps from Titanium backup and that seems to be the issue. I've re linked them to the market in Titanium and gmail notifications have started again.
[Samsung Galaxy Nexus] mmuzzy:
Great! Glad you got it.

:)
[Samsung Galaxy Nexus] blame2:
Also confirmed bug eyes and **** doesn't work. Crashes app. Never use it so doesn't bother me...
[Samsung Galaxy Nexus] mmuzzy:
-- snipped off a bunch of munged up posts about the camcorder effects fc'ing --

Ok. I figured it out. I guess I shaved too many files from /system/media from wayback and it only reared its head with Camcorder effects. I'll integrate the fix with the next build which I was planning to do with the next AOSP build release but 'any day now' is taking too long so it'll probably be today. Thanks for all the help and clues. Op updated with fix link also.

Gallery/Camera fix for Camcorder effects fc'ing:

http://tinyw.in/mOni
[Samsung Galaxy Nexus] mmuzzy:
ROM Update

September 2, 2012:

- Fixed Camcorder Effects FC

- Restored missing Face Unlock

I was going to wait for the new build from Google but for now the leak is newer than what I have access to for source. At this point I decided it was better to put out a fixed ROM and rebuild when we get an update to AOSP... hopefully soon.
[Samsung Galaxy Nexus] BOY_:
Thanks for keeping the ROM moving forward! Did anything change other than the camcorder fix and face unlock? Don't want to reflash the the ROM unless necessary.
[Samsung Galaxy Nexus] mmuzzy:
Makes sense. Other than Face Lock and the camcorder effects, there isn't really anything that would necessitate having to reflash. Also both issues were fixable with the zips I posted in op. Thanks. :)
[Samsung Galaxy Nexus] BOY_:
Thanks mmuzzy!
[Samsung Galaxy Nexus] Gerson2407:
I lost nav bar customizations with this build. :(
[Samsung Galaxy Nexus] samuelhadams:
Nav bar customizations?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
I'm sorry to hear that. Unfortunately you'll lose things like nav bar customizations, battery mods, etc, when you flash a ROM because framework changes are overwritten. This happens with any ROM though.
[Samsung Galaxy Nexus] gener1c:
Thanks again Mmuzzy for all the quick fixes, this rom with the new radios is the smoothest stock rom I've used.
[Samsung Galaxy Nexus] THE_SNOOK:
Is there any plan for the foreseeable future to have power widget bar in the notification drop down? I hate the look of elixer 2.

On a slightly different note has anyone else had trouble adding their bank cards to Google wallet? I I can add the prepaid card just fine but when I try to add my Visa it says "unexpected error"

sent from my GNEX
[Samsung Galaxy Nexus] markculton:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

Just tried wiping data and even with a clean install I have the same problem. No worries, going to revert to my backup of your 4.2.1. That thing is a beast!

(Edit - I guess I shouldn't say clean install, I simply wiped data and still have the problem. Perhaps I should have tried wiping data and then installing again. Either way, I'm back on 4.2.1.) :)
[Samsung Galaxy Nexus] mmuzzy:
I need someone to do a full wipe and see what happens with the ROM if anyone wouldn't mind doing a nandroid and flashing the ROM posted a few messages back for me. Thanks.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

I'm in as soon as I dropbox all my pics/videos! Just be a few....
[Samsung Galaxy Nexus] mmuzzy:
Alright, thank you. I appreciate it.
[Samsung Galaxy Nexus] cds36:
Re: [ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.2.1 - JOP40G

I did a full wipe here when booted up I got a system ui crash then all seemed ok but quick setting were blank so I wiped cached and dalvik rebooted then the quick settings tiles showed rss or rsi something like that I should have took screen shots but I reverted back to back up

---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------

This is after doing full wipe and super wipe twice