Finally caught up! 4.2.2 (JDQ39)

Got mine in after a driver update...

ADB devices showed my phone until it rebooted in recovery, but then it would drop with device manager showing the yellow exclamation and ADB reporting no devices.

At this point, I used DM to update the driver & manually choose Samsung as the mfg and ADB Composite Device as the item. No reboot necessary and the driver was already available on the PC...yellow warming went away & side load command worked right away.

This was using an unlocked, unrooted GNex, the latest SDK, and Win8 x64.

Radios seem much better! I had data drops *all* the time where both wifi & cell signal indicators would disappear & I'd be dead in the water for 30sec or so while they renegotiated. Not a single drop in several hours of playing... we'll see how it goes with more time. Signal strength doesn't seem any different, just signal stability.

(Hey, where are the developer options in settings now?)
 
Last edited:
I don't even know what that is!

I have never flashed a factory image ROM but I have been flashing custom recoveries, so whne you flash a custom ROM you also need to flash a gapps file (google apps) file too. maybe if you use a "stock" ROM there's no need. I am interested in the flash because I can not get the Blue Tooth to work with the new custom ROM.

Can anyone else shed some light on this?

Thanks
 
I have never flashed a factory image ROM but I have been flashing custom recoveries, so whne you flash a custom ROM you also need to flash a gapps file (google apps) file too. maybe if you use a "stock" ROM there's no need. I am interested in the flash because I can not get the Blue Tooth to work with the new custom ROM.

Can anyone else shed some light on this?

Thanks

You need the Bluetooth Fix, most likely. I saw it listed in a Carbon thread on Rootz and again on some AOKP thread. I'm standing down from 4.2.2 roms until that's fixed. My life (err commute) depends on Bluetooth!
 
You should become acquainted with the Dark Arts of Flashing before you venture into such territory.

May I suggest my Don't Panic guide, listed below? :)

So D-
should I flash the latest gapps with this? so annoyed that I can not get the BT to work AOKP Build 5 even wih the BTfix file.

Xanth
 
You need the Bluetooth Fix, most likely. I saw it listed in a Carbon thread on Rootz and again on some AOKP thread. I'm standing down from 4.2.2 roms until that's fixed. My life (err commute) depends on Bluetooth!

I tired the fix but it did not work for me. I tried to go back to AOKP Milestone 1 and the 2012-12-12 gapps but the phone locked up guess i could not go back to 4.1 after a 4.2 flash.
 
I tired the fix but it did not work for me. I tried to go back to AOKP Milestone 1 and the 2012-12-12 gapps but the phone locked up guess i could not go back to 4.1 after a 4.2 flash.

Bluetooth fix should be in place on the AOKP 4.2.2 builds now. They commented that once the 4.2.2 merge was done it would be fixed. Well they are on their 2nd 4.2.2 build and 4.2.2 is officially in AOSP now and no mentioning of the bug remaining.
 
Bluetooth fix should be in place on the AOKP 4.2.2 builds now. They commented that once the 4.2.2 merge was done it would be fixed. Well they are on their 2nd 4.2.2 build and 4.2.2 is officially in AOSP now and no mentioning of the bug remaining.

Only one way to find out.
 
Only one way to find out.
I'm running the latest. I haven't turned on BT to see if it links to my wife's car but judging from what I saw in the code submissions on AOKP's updates it appears they have added/merged in all the BT stuff for 4.2.2
 
I'm running the latest. I haven't turned on BT to see if it links to my wife's car but judging from what I saw in the code submissions on AOKP's updates it appears they have added/merged in all the BT stuff for 4.2.2

So you haven't used that one way to find out to actually find out?

:)
 
So you haven't used that one way to find out to actually find out?

:)
Not yet. Wife's car is buried under almost a foot of snow plus take into consideration for overnight drifting... :p
 
I'm running the latest. I haven't turned on BT to see if it links to my wife's car but judging from what I saw in the code submissions on AOKP's updates it appears they have added/merged in all the BT stuff for 4.2.2

I have AOKP Build 5 with 2013-03-01 gapps, I can not get the blue tooth to connect for my ear bud or my wifes ear bud, but my ear bud works on a stock GNx. and the BTFix patch file did nothing for me. I have done a clean flash 3 times and still nothing. going nuts. : (
 
Okay. Here's what I got...

Running the latest AOKP with the new GAPPS 2013-03-01. No patches, just flash and profit ;)

1362595294161.jpg

Ran outside and Sync'd right up via Bluetooth to my wife's 2010 Ford Fusion Hybrid phone and audio system.

1362595393539.jpg

1362595413824.jpg

FWIW, I'm using the Sprint GNex but the AOKP builds should be identical. Played a quick song from my phone over her system and checked my voice mail using the phone system in her car connected to my device.
 
Okay. Here's what I got...

Running the latest AOKP with the new GAPPS 2013-03-01. No patches, just flash and profit ;)

View attachment 62614

Ran outside and Sync'd right up via Bluetooth to my wife's 2010 Ford Fusion Hybrid phone and audio system.

View attachment 62615

View attachment 62616

FWIW, I'm using the Sprint GNex but the AOKP builds should be identical. Played a quick song from my phone over her system and checked my voice mail using the phone system in her car connected to my device.

Nice. Speaking of SYNC, if I clean flashed, would I have to reset that thing?!
 
Yeah. Noticed mine listed as Galaxy Nexus 2. That's because my phone was already linked from when I was running AOKP 4.1.2. But when I moved up to 4.2.2 I wiped my entire device (everything) and started fresh.
 

Trending Posts

Forum statistics

Threads
957,200
Messages
6,971,851
Members
3,163,740
Latest member
wokulbo1