yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Howie Dub:
kevdliu's qs works perfectly on mmuzzy's. can't change icon order like on 4.2.2, but that's minor. make sure to delete the one that comes with the ROM first before flashing the mod; otherwise you will have 2 qs apps. I believe the one with the ROM is name QSM.apk.
[Samsung Galaxy Nexus] RW-1:
Order can change here, I had no issues with it.

I'd like to see the complete 4.3 cam and gallery in the ROM from AOSP source, I think any issues we have may stem from something missing though I don't have an edit issue right now.
[Samsung Galaxy Nexus] jon9314:
Where did you find the quick settings mod? Is it a zip that can be flashed?
[Samsung Galaxy Nexus] vicw:
I installed the ROM without deleting the previous Apk, and my subsequent reboot attempt was pretty ghastly. The phone just sat with the initial Google/unlocked icons for what seemed like forever. I finally panicked to a battery pull, more than once, which didn't help. At one point it did boot itself normally, but crashed shortly after, and went back to the failing mode.

In the end, I just let it sit on the startup screen for a really extended time, and it came up. All seems well again, and I have found found two copies of "Quick Settings Control Panel 1.0" app in Titanium Backup, one active and one uninstalled.

Update: I just found QSM. APK & QSCP. APK in /system/app, both dated 1 Aug 08. I wonder if it is safe to just delete the old app, and which is which?
[Samsung Galaxy Nexus] RW-1:
Whole thread on it, go up one level ... :)

On the QS to remove, a couple of people have posted already, it's the QSM.apk

The one with kev' s install gives you QSCP.apk. So you could just delete QSM and reboot and you should be ok

I had opened system/app and removed it before tossing it onto the phone to flash :)

I also had removed superuser to avoid any clashes there as well.
[Samsung Galaxy Nexus] Howie Dub:
thanks RW-1...I was so used to being able to move the tiles on other ROMs that I forgot that the order you select them is the order they'll be in.

here you go...http://xdaforums.com/showthread.php?t=1999125

It should be safe to delete the old apk. I had flashed the mod thinking that it would replace the old apk and ended up with both. Just deleted the old one and everything has been okay so far. The old apk is QSM.apk.

Also, I didn't see anyone mention this, but there's an update to SuperSU 1.45. I lost root when I updated to it. Had to uninstall the update, clear data and cache, and reflash 1.43. Just FYI.
[Samsung Galaxy Nexus] vicw:
Thanks for the help. I found the files and deleted QSM. APK. I then had a normal reboot and the QS mod is working for me.

Regarding SuperSU 1.4.5, I had updated to 1.4.5 prior to the OS update, and also flashed it as part of the update. I haven't encountered any rooting problems with it yet.
[Samsung Galaxy Nexus] RW-1:
Interesting on 1.45, not seeing an update notification on it, but if already rooted I wouldn't see why one would lose it going thru the update. Glad you sorted it out though.

Update: I'm on 1.45, must have updated it....

Your welcome Howie, though I think the volume bar will go to the top no matter what order you click it in this version. No deal breaker there :)
[Samsung Galaxy Nexus] Howie Dub:
Weird. I had an app that needed root access and it said I didn't have it. Tried opening another app that already had su permission and it wouldn't open because it said I needed root. Opened SuperSU and it said I needed the binaries and it couldn't DL them. Had to uninstall and reflash to get root again.
[Samsung Galaxy Nexus] RW-1:
Perhaps you thought you flashed it but didn't?

I had thought I flashed QS and did, but flashing softkeys afterwards undid those changes, so I took and tossed the softkeys into Kev's systemui so I'd have both. Worked out nicely!
[Samsung Galaxy Nexus] Howie Dub:
no clue what happened. pretty sure I flashed it b/c I was able to remove the old QS app with the file manager and I believe you need root to do that. In any case, it's working now, thank goodness.
[Samsung Galaxy Nexus] klobkelosh:
That just happened to me too...think it's a4.3 weirdness
[Samsung Galaxy Nexus] nitsua98:
Yeah superuser in general got f**'d when Google changed some stuff in 4.3. The supersu now is hacky and not as good as previous versions.
[Samsung Galaxy Nexus] Milleniumlance:
fancy kernel just release an alpha custom kernel for 4.3, its really smooth, cant overclock past 1.4Ghz or you get a crash

#Update im loving this kernel on Muzzy 4.3 no crashes yet, done several benchmarks battery drain is average for overclock. it has iOS levels of smoothness
[Samsung Galaxy Nexus] vrahn:
Which gapps do I download. There's many files in the 4.3 folder
[Samsung Galaxy Nexus] Milleniumlance:
Gapps Core 4.3
[Samsung Galaxy Nexus] vicw:
The 4.3 Camera app looks good to me, too.
[Samsung Galaxy Nexus] wavedashdoc:
So are there any advantages to flashing the new bootloader for 4.3? Anyone having any issues with it?
[Samsung Galaxy Nexus] Milleniumlance:
no issues
[Samsung Galaxy Nexus] Magnus_CA:
Same thing happened here. I think it was the 1.45 update. I used the Cleanup->Reinstall job in SuperSU, rebooted, and reinstalled from the play store. So far so good.
[Samsung Galaxy Nexus] vrahn:
I just flashed this build good so far. Would like to see some features. I'm use to halo and the app bar on the side. Might try another ROM. Let's see what this does for awhile
[Samsung Galaxy Nexus] Stigy:
Just wondering if there's any chance of the next build trying to enable BLE?

People found commits that disabled it when they were building 4.3 for toro and were thinking that if you just undo the two changes they made that BLE would work on our phones.
[Samsung Galaxy Nexus] BackInA88:
I'll be waiting just can't live without the blue soft keys and the circle battery.:silly:

Want BLE as well.

I'm running rock solid and great battery on Mmuzzy 4.2.2

Steve
[Samsung Galaxy Nexus] neur0tk:
I just loaded up the pre Fancy kernel for the 4.3 ROM so far so good no issues as of now
[Samsung Galaxy Nexus] johnhimm:
Hahaha can't live without blue softkeys?
[Samsung Galaxy Nexus] darklordofthesith:
So the new bluetooth stack isn't in our build yet? I didn't even notice. You can't get any better than a Mmuzzy rom ! Thanks kind sir for the update. Working flawless.
[Samsung Galaxy Nexus] Stigy:
Starting from this post onward is some BLE discussion if anyone wants to give it a shot. I've never compiled a ROM or else I would.

http://xdaforums.com/showthread.php?p=44007684
[Samsung Galaxy Nexus] RW-1:
Not too concerned about BLE. Either it will work, or it won't - either a bug or to me, more likely a chip set limitation as implemented on the specific model. I'm hoping former, as we'll all be looking as to whether or not most features of KLP will apply to the GNex when released.

Going to hold off on the boot loader for now.
[Samsung Galaxy Nexus] xolanir:
Was the new bootloader not baked into the vanilla ROM? If not, could you please give me a link to it so I can flash it separately through ADB?

Other than that, this ROM is running excellent both on my N7 & Gnex as always Muzzy, thank you!

Sent from my Nexus 7
[Samsung Galaxy Nexus] mnbrightblade:
The new 4.3 ROM is running well on my GNex as well. I'm now waiting for an updated Franco kernel.
[Samsung Galaxy Nexus] lumpysherman:
kernel usage

I'm using Tiny's 4.2 kernal. Do I need to go back to stock before I upgrade or running the 4.3 vanilla take me back to stock?

Thanks,
[Samsung Galaxy Nexus] RW-1:
Bootloaders and radios are not part of any ROM.

None has been released specifically for the VZ GNex (toro), the one in other threads was modified to be flashable from the sprint version, and should work, however since im on 4.3 with no issues at the moment i'll wait for now. Check the FTL ROM thread, I believe a link is there for that boot loader.
[Samsung Galaxy Nexus] neur0tk:
Nope just do a wipe and load the 4.3 ROM/SuperUser/Gapps .zips in the OP and you will be good to go
[Samsung Galaxy Nexus] xolanir:
Thx for the info brother! Will check it out.

Sent from my Nexus 7
[Samsung Galaxy Nexus] vicw:
Operation looks really good with MMuzzy 4.3 and the QS Mod.

The only anomaly I'm experiencing is that the Audible app displays 3 identical and persistent notifications, saying that "Audible is Running". Selection of the notification brings up the App status, with the options to Force Close or Uninstall. They go away when I exit the app. I've uninstalled and reinstalled the app, but no change in behavior. The Tunein Radio app also shows a single notification with the same behavior. Is anyone else experiencing this?
[Samsung Galaxy Nexus] klobkelosh:
Believe it or not, that is a "feature" of 4.3 - all apps running in background must have a persistent notification.
[Samsung Galaxy Nexus] RW-1:
Yes. I agree there.

I have one app issue, WiFi radio thermostat, lost display of the indoor temp, but was in contact with Dev's, they're aware and working on that.
[Samsung Galaxy Nexus] vrahn:
I'm curious if halo will be coming to this ROM?

I like the quick toggle for wifi and data rather than it take me to WiFi and data itself. Unjust Dev in the fascinate forum has this as a feature in his rom
[Samsung Galaxy Nexus] RW-1:
Probably not, however it might be something that one could flash to add it.

Let's remember we're just beginning 4.3 here, FV isn't yet compiled, and we may still see a possible KLP by the end of the year. :)
[Samsung Galaxy Nexus] vicw:
I thought that might be the case - and it's a good idea, I think, but I don't get why I'm seeing 3 of the notifications from Audible, and if my GN is unique with that behavior, or common to the app in this environment.
[Samsung Galaxy Nexus] NickZee10:
Hey all,

I downloaded MMuzzy's 4.3 and I'm in the process of installing. Did a clean wipe, but when I go to install the zip, it fails and says "Warning: No file_contexts"

What does this mean?

I even downloaded the zip twice just incase one failed..they are both doing this. Any advice?

Nevermind - I was thinking it was causing the installation to fail.
[Samsung Galaxy Nexus] klobkelosh:
You could try disabling notifications for audible and see if that works.
[Samsung Galaxy Nexus] RW-1:
Or it will be something they will have to address to be 4.3 compatible...
[Samsung Galaxy Nexus] vicw:
What I'm really hoping to establish is whether others are getting the triple notification from the Audible app on 4.3, MMuzzy Rom.
[Samsung Galaxy Nexus] dxh3378:
Just wanted to chime in here.

Thanks for the ROM Muzz! Everything seems to be running super slick.

If anyone is interested, the LMT dev has an updated version of the app to be compatible with 4.3

I was also able to use the fullscreen toggle found here http://xdaforums.com/showthread.php?t=1497558

But in order for the fullscreen to work you must first add this "qemu.hw.mainkeys=1" at the end of /system/build

I am however having an issue with the amazon appstore not downloading anything, which is a real bummer, because I was able to grab Swiftkey one day when it was the free app of the day. Anyone else having any issues/or solutions to this? Or do you think Amazon has not caught up to 4.3 yet?

Anyway, thanks again for the fantastic ROM!!
[Samsung Galaxy Nexus] vicw:
I was able to download, install & run the Free App of the Day "Azada" without any problems. I haven't used the amazon source for months, and it did an update to rev 5.0010.160.BC635001010 before the download.
[Samsung Galaxy Nexus] dxh3378:
Weird,

I just tried to get the FAOTD, and got the same download error. I did restore the app with Titanium, but after the initial error, I cleared the data for the app and re logged in, with the same results.

I may just uninstall it and try getting the Appstore apk directly from Amazon again.

Thanks for the repy,

D

Edit:

Did a fresh install of the apk, and I am still getting the download error. I checked and it is the same version you have, nor do I have any sort of data restriction enabled that might be preventing it. I even removed some of the old duplicate devices under the device management, that had piled up due to my crack-flashery.
[Samsung Galaxy Nexus] xweb10:
Not Muzzy specific, but does anyone now if Bluetooth MAP (Message Access Profile) is enabled for the Gnex with 4.3? I want my car to read my texts/emails.
[Samsung Galaxy Nexus] abremel:
Quick Settings

Anyone else having trouble with the quiksettings in the latest build? Whenever i try to apply changes to the tiles the quicksettings app crashes.
[Samsung Galaxy Nexus] ithamatam:
How is the battery life on 4.3?
[Samsung Galaxy Nexus] vicw:
I don't think I'm having any problem with changes. I never tried to change anything before on the app, so I'm not familiar with normal behavior, but I was able to apply changes, and the results were as I expected.
[Samsung Galaxy Nexus] billykxda:
Just surveyed the past couple of pages since the 4.3 drop. Looks like there are still some loose ends. Might wait until the dust settles a bit more. Don't have the time to do repeated flashing right now.

Sure do appreciate Mike's dedication to keeping GNex'ers at the forefront of Google tech.

Thanks Mike!
[Samsung Galaxy Nexus] RW-1:
Oh stop the drama... If I flashed it, what does that tell you? :)
[Samsung Galaxy Nexus] JoJoDaClown:
Most important thing is to remember to flash with the gapps for 4.3. I didn't really find a decent one out there. Running the Gapps 4.3 for AOSP that's on the forum. It wants me to install a Chinese keyboard app, though.
[Samsung Galaxy Nexus] RW-1:
I used the linked Banks 4.3 Gapps core, and am fine, no issues with it.
[Samsung Galaxy Nexus] wmarcin:
I don't know if anyone mentioned it already: how's battery life on 4.3 relative to the 4.2.2 ROM.

Sent from my Fatty Tuna Belly.
[Samsung Galaxy Nexus] mnbrightblade:
Mine was off the charger from 8 am to after 10 last night with moderate usage throughout the day and I still had 20% left when I put it on the charger for the night.
[Samsung Galaxy Nexus] n99hockey:
I am not sure if this the OS forcing this or the app, but this was not showing on 4.2.

Anyone have anything like this showing up?
[Samsung Galaxy Nexus] mnbrightblade:
Which notification toggle is that?
[Samsung Galaxy Nexus] Stigy:
This is probably what it is: http://www.reddit.com/r/Android/comments/1j6lut/for_43_apps_that_abuse_the_notification_service/
[Samsung Galaxy Nexus] RW-1:
See the earlier discussion a couple pages back, this is a persistant notification, part of 4.3, because that app is running in the background.

***A note to all, SU 1.50 just hit the play store, trying to install the binary using "Normal" will FAIL. Reboot, and use the TWRP/CWM method.***

(I gleaned this by looking at reviews in store before updating it)

Mine installed with no issues (TWRP), no loss of root, etc.
[Samsung Galaxy Nexus] mnbrightblade:
Do you have to reflash everything or just the SuperSU package?
[Samsung Galaxy Nexus] Reginald476:
Just SuperSU.
[Samsung Galaxy Nexus] RW-1:
Nothing. Selected SU to use TWRP and it flashed the binary. Rebooted and was good to go.
[Samsung Galaxy Nexus] treubber:
The OP states that native tethering is included, but is that for Vanilla 4.3 or for the 4.2 editions?
[Samsung Galaxy Nexus] RW-1:
Both. Included tethering works as advertised. I tested it this weekend on 4.3
[Samsung Galaxy Nexus] demill66:
Sorry, but I'm a little slow with this stuff. Does this mean that I can download from the store, but when it asks to update binaries, I have to do it through another method. If so, would you mind putting up a short description of how that is done.

Thanks.
[Samsung Galaxy Nexus] RW-1:
No problem.

Yes, you may update from the store, but you MUST have flashed it at one point when installing the ROM, OR YOU WILL NOT HAVE ROOT TO BEGIN WITH.

In superSU, when it tells you it needs to install new binaries, you answer yes (or ok, whatever it was :) ).

You are then presented with two options, normal - in which the app will try to install it.

Or by TWRP/CWM - in which the app will setup a reboot to recovery and the recovery will flash it. then reboot for you.

From 1.43 to 1.45 - I used normal, and had no issues on muzzy 4.3

From 1.45 to today's 1.50, it appears that using normal will hang, BUT, if you choose to allow it to install the binaries thru recovery, it will work fine. at least, that is what has been posted in the app's reviews, and my experience this morning.
[Samsung Galaxy Nexus] billykxda:
I used to flash ROM's and kernels like crazy last year and early this year, finally ending up with Muzzy's March release. Haven't done a thing since, b/c life is awesome on my GNex runnin Muzzy 4.2.2.

After scanning the helpful posts here, I seem to be unsure of how to proceed with 4.3! I used to have this flashing thing DOWN!

When I check my GNex now, I don't appear to have SuperSU installed at all. I can find "Superuser" 1.0.1.8 installed. When I checked SuperSU on the Play Store, it has a notice indicating that I have to re-root. Really? If so, I've got some work to do!! It's been a long-ass time since I rooted.

If someone has captured all of the necessary directions/instructions to install Mike's 4.3, please point me in that direction - I don't want to have any of the helpful fellow forumites here spending time writing all that stuff for my benefit alone. With some instructions, I know I can noodle it through - there just seems to be more stuff to do this time around.

Thanks in advance!

**Update**

When I go to the Play Store on my PC and access the SuperSU page, the Play Store says that the app is "Installed". How the hell does that happen without being listed in my apps? Obviously missing something here...
[Samsung Galaxy Nexus] RW-1:
Billy billy billy .... Same here, hadn't done since the security update last week.

Ok ...

On computer, open the ROM and remove superuser from /system/app (What I did using winrar before sending to the phone for flashing)

(Othere report you don't need to, but you can remove superuser.apk from /system/app after the first boot)

Flash in this order: (clean flash or dirty? both have been reported ok at this point by members here, I decided on a claen flash, do a factory reset in recovery, wipe cache/dalvik)

The ROM.

Banks Core Gapps for 4.3.

SuperSU

Quick settings (if you desire)

then reboot, be prepared for a long first boot, but other than that, that's really it.
[Samsung Galaxy Nexus] therealciviczc:
I did mine as follows...

Downloaded the ROM, and the Banks Core Gapps for 4.3. I wiped in TWRP, Installed the ROM, Installed the Gapps, and wiped cache, booted system. Once I booted, it showed I had an update for SuperSu. I ignored that. I went to the browser, and downloaded SuperSu 1.5 from the chainfire website as a .zip file. I rebooted to recovery, went to install, installed SuperSu 1.5 from there, rebooted, and SuperSu works fine. I still have root. So if I'm understanding where you are now, just go download the SuperSu zip from their website instead of the apk from the market, install it with TWRP it, and you'll be back in business.

This is the link to the zip...

http://download.chainfire.eu/344/
[Samsung Galaxy Nexus] billykxda:
Thanks Dude.

I appreciate it.

---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------

Thanks!
[Samsung Galaxy Nexus] Milleniumlance:
No Google Now?!?! i usually get a notification before work about traffic and nothing ....Crap
[Samsung Galaxy Nexus] RW-1:
try going into it (Google now), no problems here though you have to turn it on if you did a fresh install so to speak.

Chainfire released super su 1.51, looks like that 16 is a few things, I could install the binaries in normal mode just FYI ...
[Samsung Galaxy Nexus] Milleniumlance:
figured it out, google search wasnt installed, im making Noob mistakes
[Samsung Galaxy Nexus] thewilliams1:
My Home Key isn't working and all google sync is crashing.

Doing a re-flash .. hope that helps.

** Definitely a bad download.. reflashed and got the home key to work and google to sync, but the playstore wouldn't connect and contacts wouldn't load. Will give it another go when I have more time.
[Samsung Galaxy Nexus] RW-1:
don't sweat it, inadvertentIy turned off the Google Voice typing and wondered why I didn't have a microphone on my keyboard for a while.

I also decided to uninstall voice search itself, because Google now takes over for that that still seems okay.

---------- Post added at 03:25 PM ---------- Previous post was at 03:08 PM ----------

Try a clean flash.

People. Common sense rules are in effect.
[Samsung Galaxy Nexus] thewilliams1:
Yeah, I did .. when making a jump like this, I do what I call a sterile flash.. wipe everything multiple times... Per my edit above: ** Definitely a bad download

.. not my first rodeo..

Cheers!
[Samsung Galaxy Nexus] exzacklyright:
I flashed this and now I don't have root. Wtf??
[Samsung Galaxy Nexus] RW-1:
I hear ya...

Exz reflash SU
[Samsung Galaxy Nexus] JoJoDaClown:
You need to reinstall the binaries for supersu or whatever you use. 1.51 is out now for supersu, so might as well update it anyway.

Most people are saying they needed to install the zip through bootloader to get it to install correctly, FYI.
[Samsung Galaxy Nexus] darklordofthesith:
Exactly the same thing I did. Not one lick of a problem.
[Samsung Galaxy Nexus] factor0815:
Android Keyboard broken

I am having trouble with the Android keyboard being greyed out. error "Android Keyboard failed to respond Wait or cancel ?"Did a full wipe and tried several times to run new Rom with the same result. Could it be a bad DL or any other suggestions?

Edit After reflashing Rom and SU everything works fine...but.... I cannot download the Gapps package correctly. Any help will be appreciated. I clicked on the link to Bank's Gapps in the OP, but when I try to flash any of the files, they all show as bad files. What am I doing wrong? I tried to flash a different Gapps package, but that's when my Android keyboard went bad.
[Samsung Galaxy Nexus] urphonesux:
What is the best way to boost volume?

New to the nexus and this ROM :)

Currently running fancy kernel using trick mod
[Samsung Galaxy Nexus] RW-1:
I would recommend a clean install, ROM then gapps (banks core 4.3) then SU...

You could DL the gapps to a computer then transfer to the phone if need be. I use WiFi file explorer for that.
[Samsung Galaxy Nexus] factor0815:
Thank you..that did it!!
[Samsung Galaxy Nexus] JoJoDaClown:
You installed the wrong 4.3 gapps initially... I did the same thing.

Download either Banks or Gapps for AOSP, then start up your phone into bootloader, hook it up to a PC via USB, within the bootloader you can mount the phone data. Move the zip file over to your phone, then install gapps.

May want to also download and move 1.51 SuperSU while you're at it, and install that too.
[Samsung Galaxy Nexus] RW-1:
No problem... Enjoy!
[Samsung Galaxy Nexus] thewilliams1:
Wow, I'm an idiot.

Found my problem... A zip-file labled as 4.2 is not going to give you a 4.3 ROM.. just FYI

;)
[Samsung Galaxy Nexus] exzacklyright:
So I'm guessing it was a bad idea to install franco kernel over this.... "constant FC's"..... the process com.android.phone has stopped.
[Samsung Galaxy Nexus] RW-1:
Was it cleared for 4.3? If not then ....
[Samsung Galaxy Nexus] Reginald476:
Check out Misledz Nexus Louder, I have been using that with 4.2 Mmuzzy for a long time. I have yet to try it with 4.3 but he has 3 test builds and is waiting on a replacement GNex to fix a couple of issues but from the thread it looks to be working just fine.
[Samsung Galaxy Nexus] pkgnex:
The official Franco Kernel nightly (384) is not 4.3 compatible. However, if you read a few pages back in the Franco kernel thread, [MENTION=4544860]osm0sis[/MENTION] has recommends a "hybrid" version that reportedly works well. (Franco is on vacation until today, I think.)