yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jordanishere:
At least the source is there so the notification shade can be modded to have real toggles.
[Samsung Galaxy Nexus] codfos:
I think there will be some changes to how this works. I bet, like a lot of things I have noticed, this is the groundwork for something else. If they included a check box to adjust what the "toggle" should do (like take you to the wifi settings screen or just toggle wifi on and off) I would be pretty happy.
[Samsung Galaxy Nexus] marhensa:
http://xdaforums.com/showthread.php?t=1999125

https://github.com/kevdliu/JB-MR1-QuickSettings

:laugh: :laugh: :D

:good: :good: :good: :good: :good:

many 4.2 roms already implement this mod.

http://xdaforums.com/showthread.php?t=1996726
[Samsung Galaxy Nexus] CADude:
That's what I'm saying.
[Samsung Galaxy Nexus] un.droid:
i dont like the idea its not a real toggle.. but only a shortcut to the settings menu.
[Samsung Galaxy Nexus] adrynalyne:
Good thing they aren't called toggles by Google ;)
[Samsung Galaxy Nexus] jesusice:
And thus the thread comes back full circle. Again.
[Samsung Galaxy Nexus] CMNein:
This thread should die.

Oh, and BTW, there's an airplane toggle in the quick settings, I hate toggles in my quick settings :cyclops:
[Samsung Galaxy Nexus] arlyn:
Who cares. they're better than nothing and cyanogenmod will fix them. It's really typical google. In CM10, in the notification drop down, clicking on the clock brings you to the clock, clicking on the date brings you to the calendar. Google, however feels it's better for selecting either to bring you to Time and Date settings. Which would be awesome if I could travel time, but changing the physical date and time on my phone is something I do pretty rarely, as someone who cannot travel time, and in our time-travel free world, Time and Date settings is the least likely goal of someone hitting a clock or date.
[Samsung Galaxy Nexus] kyokeun1234:
Got problem with your stock android experience? There's a mod or ROM for that ;)
[Samsung Galaxy Nexus] MikeyMike01:
Not everyone wants to put ROMs on their phone. I certainly don't.

Sent from my iPhone
[Samsung Galaxy Nexus] Citizen_Snips:
Not trying to start a war here, but why not? If you aren't happy with the stock experience then why not try a new ROM? Most custom ones are built with the idea of improving on stock and adding features most people wish stock had. Sure sometimes you might run into a redraw or a little glitch here and there but for the most part all of the features in custom ROMs do exactly as they're supposed to. The best part is, if you don't like it then it will take you all of five minutes to return the phone how it was. All I'm saying is don't knock it til you try it. Then again maybe you did. Idk. Just my opinion. I love custom ROMs. It's the reason I got my nexus. What other phones have custom development on this level?

Apple - Innovating new ways to take your money
[Samsung Galaxy Nexus] foosion:
The most common reason I hear for people not wanting to use custom roms (among those who know how to do it) is that there's always something that doesn't work (sometime more than a "little glitch").
[Samsung Galaxy Nexus] Citizen_Snips:
Could you be more specific maybe? I'm not aware of any serious issues regarding a major feature in a custom ROM that is completely broken and does not work. Generally they fix it or remove it until they can fix it.

Apple - Innovating new ways to take your money
[Samsung Galaxy Nexus] sbodyontheweb:
coast cdeperm

i cant sleep because of that and the fact that multi user is not enable on phone
[Samsung Galaxy Nexus] adrynalyne:
Then your user title is misleading and should be removed along with your signature.

Why list custom roms and then tell people you don't run them? Makes your work 100% untrustworthy. If you won't run your work, then neither will anyone else.
[Samsung Galaxy Nexus] MikeyMike01:
I didn't tell people not to run them. People can do whatever they want to to their devices. I said I don't want to.

And you'll note I don't use any of the devices I made ROMs for anymore. When I did, of course I ran them. I had no choice... the stock experiences of those devices were unacceptable.

All I was ever doing was making my phone more tolerable and sharing it with others.

Sent from my iPhone
[Samsung Galaxy Nexus] zephiK:
Flash a mod and it becomes real toggles. Fnv rom has this already.
[Samsung Galaxy Nexus] marhensa:
the cycle of this thread:

1. stupid aosp, why do they put this quick settings instead of real toggles?

2. hey, the name is quick settings, not quick toggles!

3. sure, but surely google have to learn, cyanogenmod / many custom roms has the advantages of the toggles

4. um, i like the way google create this rom for end users, which likely not everybody changes their phone settings so often

5. that's stupid, i want toggles so badly! and i need it, it has to be there, officialy!

6. hey, at least there's a mod for that, to change it to toggles

7. not everybody loves modding their phone, we want the stock rom experiences

8. well this is xda, smartphone modding forum

9. back to the no 1.

my little advice for the cons:

google is not gonna read this thread anyway.. there's a small chance for that.

installing a little mod is not gonna hurt you.

and nandroid backup is your friend anyway, if you find it unstable and makes your phone turns into bacon, you can always go back to the previous settings.

we regular people here in xda developers, are wanting stuff devs do with their device, right?

we are here trying their mods, giving a feedback, reporting bug, and yada yada...

if you don't like it,

stay stock until google heard this and make and action,

or just simply try the mods, and giving a feedback to the devs.

just my 2 cents.

Sent from Galaxy Nexus - Android Jelly Bean 4.2
[Samsung Galaxy Nexus] codfos:
This. The whole post above is awesome. When will you be happy? Never. When will there ever be something that users will be 100% happy with? Never.
[Samsung Galaxy Nexus] zerocool79346:
I'm just really unsure of why you are still here. I understand that you were a dev at one point and so congrats and respect for that, but you've made it pretty clear you're jaded with Android as a whole and now like iOS, so why continue posting here? Serious question. I certainly wouldn't waste my time on a forum for a device or OS that I don't care for, thus why I don't frequent iOS or WP forums.
[Samsung Galaxy Nexus] squidder:
Wow u switched to iPhone?
[Samsung Galaxy Nexus] squidder:
And y is everyone bashing the op? He's 1000% correct. @op don't mind the trolls. O n BTW op I have an empty pool in the backyard and I was wondering if u could possibly fill it up with those crybaby tears of yours. "Wahhhh Google didn't give me toggles my life is over"
[Samsung Galaxy Nexus] Greenforty:
After I installed the android 4.2 update on my device (yesterday) I noticed that my device was much slower and more laggy. I also tested my speed at a quadrant full benchmark were I scored below average (see pic.). Could someone tell me what I can do about it, maybe there are more people with this problem?
[Samsung Galaxy Nexus] MikeyMike01:
Quadrant scores are a poor indicator of, well… anything other than the ability to run Quadrant.

Sent from my iPhone
[Samsung Galaxy Nexus] AmericanCon:
Let's all just talk about how much iPhone sucks now.

Innovation died with Steve Jobs.
[Samsung Galaxy Nexus] jadephyre:
I think that they didn't include real toggles in the quick-settings is a really shoddy job on their part.

Looking at all the preliminary information that was posted on various websites, I expected something like the toggles in ROMs like CyanogenMod.

Not really a dealbreaker for me as I have not encountered any of the other bugs mentioned by users of 4.2, except the Birthday-Date Bug.
[Samsung Galaxy Nexus] xHausx:
Closing this now as it's going off-topic and is just encouraging flaming.
[Samsung Galaxy Nexus] jp555soul:
Hey, received my update OTA and all works well except Bluetooth. The option won't ever move to "On". Wouldn't even notice this except that I have the Sony Smartwatch. Has anyone else noticed this?

Thanks
[Samsung Galaxy Nexus] xyzulu:
Have you restarted your phone?
[Samsung Galaxy Nexus] jp555soul:
Yep...twice
[Samsung Galaxy Nexus] jp555soul:
Regained root and trying a fix perm before doing a complete wipe.
[Samsung Galaxy Nexus] jp555soul:
Fix perm didnt work so I did a factory reset and it still doesnt allow me to turn on bluetooth.
[Samsung Galaxy Nexus] zlogic42:
It's possible that the radio update has failed. I've once had a similar issue when upgrading a Nexus S from GB to ICS. The phone component was completely broken - and the phone behaved like it was in flight mode. Had to reflash the stock GB image, then repeat the upgrade to ICS.
[Samsung Galaxy Nexus] jp555soul:
Well since this was OTA, I dont really want to reflash it, any other ideas?
[Samsung Galaxy Nexus] jp555soul:
Anyway to flash just the BT radio?
[Samsung Galaxy Nexus] andQlimax:
Power off, take battery out for more than 10 seconds and it will be ok

That's how bluethoot problems get fixed in all android devices..usually...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] thegtfusion:
reflash the normal radio via fastboot. download the stock 4.2 images from here (https://developers.google.com/android/nexus/images), extract it and flash the radio image via fastboot.

command:

that should do it. if that doesnt do it, flash the full stock images via fastboot

commands :

you will notice that when you unzip the stock image download , that you have 2 images and a zip. that's why you do fastboot update -w nameofthezip.zip. the -w wipes the device.

good luck mate :)
[Samsung Galaxy Nexus] jp555soul:
+andQlimax Thanks but no luck with that either.
[Samsung Galaxy Nexus] jp555soul:
+thegtfusion The second option worked. Thanks for the info and clear directions.
[Samsung Galaxy Nexus] Prax:
Anyone know if the new radio firmware pushed the galaxy nexus to Bluetooth 4.0? It has long been known that the chip in the galaxy nexus is capable of BT 4.0 but for what ever reason Samsung decided not to enable it in the software.
[Samsung Galaxy Nexus] thegtfusion:
No problem :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Royal2000H:
I don't think it was Samsung's fault, I think it was Google's fault. The chip was in the phone, but Google didn't build 4.0 support into Android itself. I wonder, like you, if Android 4.2 updates this.
[Samsung Galaxy Nexus] usama_ah:
I'm having the same Bluetooth problems as the OP. I upgraded to 4.2 and now I can't turn Bluetooth on. It seems the solution is to do a full re-install using the factory images?

Before I do that, I just wanted to check if anyone else was having this problem and possibly found a shorter/easier way? (Not that I'm not grateful for the solution listed, I'm just trying to avoid having to re-configure all my preferences, etc.)

Thanks.

UPDATE:

- I tried just flashing the radio but it did not work for me. I'll keep an eye on this thread, if nothing else develops I guess I'll have to flash the stock images. And then re-root. Sort of a pain but I kind of need bluetooth.

UPDATE 2:

- It's been a while since I flashed full images. Do I lose my files and images (from my camera) if I do the full stock flash? I mean does it erase all my personal data, or just my particular Android setup?

Thanks.
[Samsung Galaxy Nexus] Pinak.ahuja:
If you flash userdata.img it is going to erase your internal sd so you better backup.
[Samsung Galaxy Nexus] xaueious:
You will lose everything with the commands posted. Get rid of '-w'.
[Samsung Galaxy Nexus] costinu:
I had the same problem yesterday. I downloaded the stock image and used flash-all.bat that was included. Now everything is ok.
[Samsung Galaxy Nexus] usama_ah:
Thank you pinak and xaueious. I'll be sure to back up data just in case.

I wonder why this is happening. Perhaps it's because my phone was originally a yakju? But I thought hardware between the two was the same however.
[Samsung Galaxy Nexus] rdubbs007:
Just wanted to report that I too got the update this evening. I use my bluetooth with a home phone system that connects to my cell and rings all the handsets in the house. SO.... I noticed pretty immediately that it wasnt working.

I downloaded the files from here: https://dl.google.com/dl/android/aosp/takju-jop40c-factory-1a47c890.tgz (direct link to the takju 4,2 files on google). I put these files in my platform-tools folder as we should all know to do by now.

Connected good old SDK in fastboot mode and ran the following commands:

Confirm that data is intact and Bluetooth now works great. I am wondering if this failed initially because we had Bluetooth on and running when installing?
[Samsung Galaxy Nexus] jhgxda:
Bluetooth not working

Hello,

Is there a way to re-flash the radio without using fastboot flash (as I understand it, you need to have an unlocked bootloader to do that, which I don't).

I updated to the 4.2 OTA this morning and have been without bluetooth since.

I am on the stock Nexus from the play store, except I have rooted previously via these instructions:

http://xdaforums.com/showthread.php?t=1894717

Or is there a better way to fix this?

Thanks,

Joe
[Samsung Galaxy Nexus] theroblog.com:
Same Problem

Same problem.

Had to totally wipe, flashing radio did not fix it.

Pics look all there, Dropbox had them with autosync.

Lost su. :(
[Samsung Galaxy Nexus] adbFreedom:
First step is to unlock that bootloader... you could just flash the radios in your custom recovery after that (no need for complete factory images)
[Samsung Galaxy Nexus] usama_ah:
Thus far no one has had luck with just flashing the radio (myself included).
[Samsung Galaxy Nexus] eskeyy:
I just flashed radio, boot, recovery and system without wiping and bluetooth now working and I have my data and settings, I lost just root (reroot using superSU)
[Samsung Galaxy Nexus] brie987:
This worked for me! Thank you so much. I used Galaxy Nexus Toolkit by Wug Fresh in Fastboot and did the above. Worked perfectly. Again. Thanks.
[Samsung Galaxy Nexus] usama_ah:
Yup, this worked well for me. I did of course lose root as you posted. I thought I might be able to retain it with Voodoo but no dice.

So to "reroot using superSU," how exactly do I do that? it says "there is no SU binary installed, and SuperSU cannot install it. This is a problem!"
[Samsung Galaxy Nexus] eskeyy:
Use version for cwm: CWM-SuperSU-v0.98
[Samsung Galaxy Nexus] NexusDro:
DDoes the update use the new Bluetooth stack that Google and Qualcomm made?
[Samsung Galaxy Nexus] nkedge:
Had the same issue. All I did to fix it was re-flash the update zip (http://android.clients.google.com/p....signed-takju-JOP40C-from-JZO54K.e587de13.zip) in CWM. Bluetooth is back and everyone's happy.
[Samsung Galaxy Nexus] grippa:
In Car Bluetooth?

Bluetooth works fine over here, but ever since I upgraded to 4.2, my car bluetooth is having issues. It seems to connect fine, however, phone book doesnt sync anymore, cant answer or call from the car bt. I can however dial through the phone while connected to the car bt and audio routes fine. Anyone else having the same issue?

Found someone else having the same issue here:

http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39753
[Samsung Galaxy Nexus] merkman:
I'm a AT&T Galaxy Nexus user. I've been using my phone unlocked with basic rooted roms for some time, mainly so I can run a custom boot image and animation. However, whatever rom I've ever used... without changing the Bluetooth "stack", I can't interface with my 2012 Honda CR-V. The Phone Book won't download to the car, despite pairing the BT successfully. And after going to 4.2, I can't replace the stack as I could previously. If I do, the Bluetooth won't turn on at all.

A recap of my history trying to resolve this issue can be found here...

http://xdaforums.com/showthread.php?t=1679994

So right now with the stock BT, the Bluetooth connects when enter the car. But after 30 seconds, it drops the connect. Reconnects about 10 seconds later, but will drop in the middle of calls, etc. And the phone book is unavailable.

Using the APK mentioned in my link above, I was able to pair my phone, use the phone book features in the car dash, etc. But one problem STILL remained. I could not disable the Phone "Media" connection. It was CONSTANTLY connected, and manually removing the checkbox on the phone, or manually stopping that connection wouldn't last... it would reconnect again seconds later. :(

That said, I'll gladly go back to that setup if I can use the phone in the car reliably again. The negative about having the media on is when I'm listening to the radio or a CD, Google Navigation audio is going to the car BT channel and can't be heard. So it's a listen to audio through the car, and have no turn-by-turn, or vice versa.
[Samsung Galaxy Nexus] grippa:
interestingly i've never had an issue, i've been rooted but on stock rom. everything worked just fine until i upgraded to 4.2 :S
[Samsung Galaxy Nexus] MountainDrew:
Awesome, this worked great. If you have an unlocked bootloader already, this is the way to go.

My phone was originally a yakjuux (canadian), which I had converted over to takju when 4.1.1 came out. Bootloader unlocked, rooted, otherwise full stock, including stock recovery. I have since installed the 4.1.2 and 4.2 OTA updates via "ADB sideload".

All I did to fix it was:

copy e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip to root of sdcard

adb reboot-bootloader

fastboot boot recovery-clockwork-touch-6.0.1.0-maguro.img (boots into CWM without installing it, stock recovery still intact)

Install zip from sdcard

Select e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip

Reboot now

No to preserve CWM

Yes to fix root

Booted up, everything was exactly how I left it, root still intact, bluetooth is working again. Yay.

Thanks everyone.
[Samsung Galaxy Nexus] Gbcue:
Having the same problem as the OP. The bluetooth slider switch moves to the ON position for a split second and then goes back to OFF. Rebooting/battery pulling doesn't do anything. Apparently many other people are having other bluetooth problems (stuttering or something), whereas I can't even turn it on.
[Samsung Galaxy Nexus] :
yep, i had to turn the phone on and off again to make it work, its stuck at "turning bluetooth" off.
[Samsung Galaxy Nexus] usama_ah:
Fortunately, that problem has actually been solved. Check out the earlier posts.
[Samsung Galaxy Nexus] Gbcue:
This post? http://xdaforums.com/showpost.php?p=34139805&postcount=22

I can't figure out which post it is without wiping my phone/data.
[Samsung Galaxy Nexus] eskeyy:
in my post is without wiping as well as flashing update, this second method looks more simple, but both works
[Samsung Galaxy Nexus] usama_ah:
That's exactly right, that post is one method of two that will allow you to retain data.

And this second, clever method allows you to retain root if you have it.

For the first you definitely need an unlocked bootloader. For the second, I'm not sure, perhaps you can boot into CWM without actually having an unlocked bootloader.
[Samsung Galaxy Nexus] MountainDrew:
Nope, you need an unlocked bootloader for both of those methods.
[Samsung Galaxy Nexus] jhgxda:
Do you think it would work to apply the update nkedge linked to using the stock recovery "apply update from ADB" option?

(Method 4 in this link: http://xdaforums.com/showthread.php?t=1419170)

Joe
[Samsung Galaxy Nexus] akira02rex:
After updating to 4.2 my vehicle, 2013 Subaru wrx, no longer displays track information when streaming audio.
[Samsung Galaxy Nexus] dalesd:
I have a similar setup to MountainDrew. Stock, unlocked and rooted. Bluetooth stopped working after OTA update to 4.2.

All of this works for me up to Select e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip

I can see the file there in /sdcard/ when I look in adb shell, but when in Clockwork recovery, it's not there to select. The menu says:

At the bottom it says:

E:Can't mount /sdcard/

Do I want "- apply /sdcard/update.zip"?
[Samsung Galaxy Nexus] jrkelley14:
Bluetooth keyboard has worked great for me today on 4.2 although its mmuzzy' aosp, not stock.
[Samsung Galaxy Nexus] cenwesi:
Yes, there is something wrong with the BT stack/drivers on 4.2. My new motorola elite bt disconnects randomly and reconnects. On cm10 v4.1.2 it doesn't do this.
[Samsung Galaxy Nexus] nkedge:
Yes, I think that should work fine. Any of the methods in efrant's thread should have the same effect.
[Samsung Galaxy Nexus] Gbcue:
You have to choose ZIP from sdcard, not update.zip.
[Samsung Galaxy Nexus] dalesd:
This worked perfectly. Lost root, but got BT back. WiFi works better now too.
[Samsung Galaxy Nexus] jnralp00:
My Bluetooth turns on but is unstable I have to manually connect it to sync in my truck and once I connect, it randomly disconnects and reconnects.
[Samsung Galaxy Nexus] M_Shaaban:
My Bluetooth turns on but can't get it to connect to anything, also the Bluetooth toggle icon doesn't turn on
[Samsung Galaxy Nexus] rbensch:
I have the same Problems with my car.

Try to enable wifi with always on too, this is only a workaround, but it makes BT stable for me.
[Samsung Galaxy Nexus] daystrom:
This requires an unlocked bootloader correct and doing so will wipe just my sdcard partition?
[Samsung Galaxy Nexus] Diliprajgor:
After doing 4.2 update OTA. My Bluetooth also stopped working and the Bluetooth switch never goes to ON status. I did just simple thing. installed ZD box all in 1 tool. Killed the service "bluetooth Share" & NFC service using zdbox. After that my bluetooth worked like charm no issues till now. May be there is some explanation to it y it worked. I am not rooted my phone, my bootloader is also still locked. my phone is takju bought from play store.

I didn't try NFC after this so i am not sure if it is working as i killed the process but i don't care much about it as I am not using NFC. I just care about Bluetooth now.

Hope this helps some people.

THank you!
[Samsung Galaxy Nexus] g126:
Hurray BT is back!

I can confirm the above method works, kudos to MoutainDrew!

:victory:

However, I used cwm.img instead of recovery-clockwork-touch-6.0.1.0-maguro.img (does essentially the same thing, boots into CWM without installing CWM (hence recovery remains intact) but I was not presented with the option of preserve CWM or fix root. As a result I temporally lost root but restored it with Voodoo OTA RootKeeper.
[Samsung Galaxy Nexus] Taomyn:
Used this method as well, worked like a charm. Can't properly test out BT at the moment but at least it comes on now :victory:
[Samsung Galaxy Nexus] jhgxda:
Ok, I tried using the adb sideload method in the stock recovery (with some difficulty; the version of adb I had originally didn't support the sideload command so I had to update it).

It seems to work, goes through update procedure and returns me to the recovery menu where I reboot. But after the reboot I still don't have Bluetooth.

Tried it a couple times with no success :(

Any idea where to go from here? I would like to keep root and my user data and my bootloader is not unlocked.

Thanks,

Joe
[Samsung Galaxy Nexus] foiltape:
Leave it alone

Why is it that my phone is working perfectly with the recent ROM & mods, but I can't leave it alone? Maybe that's what I'll be thankful tomorrow. Mmuzzy for the ROM, mwalt for the GPS fix, and the dev community for general awesomeness.
[Samsung Galaxy Nexus] MetalMessiah78:
I haven't had any problem with Bluetooth turning on, but I have been having problems with A2DP sounding garbled since the update. Anyone having problems with this?