Develop Bugs

Whats up with Google and the Nexus

You know when you buy a nice shiny new Nexus, you'd expect to be leading the way in the Android version race...
But what the hell is Google doing with the Galaxy Nexus? Handsets are still at 4.0.1 and 4.0.2... but the Nexus from last year and the Xoom officially have 4.0.3.
Whats up?

player911 said:
You know when you buy a nice shiny new Nexus, you'd expect to be leading the way in the Android version race...
But what the hell is Google doing with the Galaxy Nexus? Handsets are still at 4.0.1 and 4.0.2... but the Nexus from last year and the Xoom officially have 4.0.3.
Whats up?
Click to expand...
Click to collapse
That is what the source is for

There are already other threads on this.
The Nexus S OTA isn't even pushed to everyone. It's on hold right now.
The Xoom's ICS push is only for the WiFi version and only for specific people who signed up for it.
Who says that the GN will even get an OTA 4.0.3 update? They may even wait for 4.0.4 or whatever at this point. Who knows. But theres clearly a reason why they're not releasing it. They're not finished and just holding onto it for no reason...
If you really want it that bad you can install a custom ROM based on 4.0.3, or compile it yourself from source and flash it. Or, just wait for the OTA and chill!

BlackDino said:
That is what the source is for
Click to expand...
Click to collapse
^this right there^

Xoom ICS has gone out to the general pop.

I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?

player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
Totally.My.Thoughts.
One thing I'm curious about: Why on Earth was OTA for SNS halted?! My SNS with 4.0.3 was fine, IMO

If you are going to root and put a rom on your phone why do you honestly care? There are so many threads on this already. No PHONE is being pushed 4.0.3 right now anyways.
Sent from my Galaxy Nexus using xda premium

holy hell guys the OTA for the nexus s was halted because they found some bugs during rollout, so they stopped. and they stopped galaxy nexus because of that as well. when they fix the bugs, they will continue the roll out. do you guys think google is doing this on purpose, they want to NOT give our the update to all as some master plan. or the more likely answer, they are fixing serious bugs.

RogerPodacter said:
holy hell guys the OTA for the nexus s was halted because they found some bugs during rollout, so they stopped. and they stopped galaxy nexus because of that as well. when they fix the bugs, they will continue the roll out. do you guys think google is doing this on purpose, they want to NOT give our the update to all as some master plan. or the more likely answer, they are fixing serious bugs.
Click to expand...
Click to collapse
The thread should end on this note
Sent from my Galaxy Nexus using xda premium

Do you know how to read version numbers? 4.0.3 Small release. If it were something like 4.1, ok, but a small release like this...chill out seriously.

player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Click to expand...
Click to collapse
It is out officially.
Build.
It.
Your.
Self.
The difference between a Nexus and every other Android phone is that you can take the LATEST publicly available source code and build a 100% fully functioning ROM with it. No matter how you slice it, you're not going to be able to build a 100% functioning Stock Android build for any other phones. They are hacked together. They are frankenbuilds. Yes other phones have 4.0.3 releases, but none of them are 100% functional. Not sure if you noticed, but for those phones you'll see a list of "what works" and "what doesnt work". For the Nexus phones, you can just build directly from Google's source and it will just work.
See: Nexus S vs Galaxy S. Although the Nexus S and the Galaxy S are identical in almost every way, the Nexus S has had ICS for months now. And you can build 4.0.3 for the Nexus S and it will Just Work.
The Galaxy S ICS releases otoh are FILLED with "known issues" - feel free to check yourself.
Just because it's not an OTA doesn't mean it's not available. You want a pure AOSP build that will be identical to an OTA that Google would push? Just build it yourself.
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
They updated the Nexus S 4G a few times before they ever rolled out updates to the mainline Nexus S. There's really no rhyme or reason to when they roll out OTAs. If you care so much about having the latest official build though, again, build it yourself from their source code. What else do you think they do? The OTA for 4.0.3 will/would be built from the same identical 1's and 0's, bits, and bytes, that is already available quite openly in the AOSP tree. It's been available for months.

i was on 4.0.1 standard with no OTA updates. doesnt matter because the nexus is made to be customised, and be a developer edition device.
i was happy to flash 4.0.3 and a custom kernel. if you arent, then i think that buying a nexus was not the wisest of decisions.

I think people just want a quality official update direct from Google. Not knocking anything the developers do, but they aren't official builds. I'd rather have something I know Google wants out there running on my phone. For all we know, there are issues with 4.0.3 which is why it hasn't been actually placed on the Nexus S and Galaxy Nexus. Yet, you are so eager to say put it on yourself.
Sent from my Galaxy Nexus using XDA App

I would rather wait a little linger for a more stable build.
Sent from my Galaxy Nexus using Tapatalk

player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
Could be because of 4g??
Sent from my Galaxy Nexus using Tapatalk

jsntrenkler said:
I would rather wait a little linger for a more stable build.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I've been using Androids since the Eris came out. Seriously, 99% of the time the ROMs/kernels put out by the devs here and on other sites are more stable than the official OTAs by the companies.

And I've been using Android since the G1, minus a small timeout on WP7, and custom ROMs always came with quirks left and right, that in their entirety always managed to piss me off in some way. If they don't do stupid **** in the kernel (I especially like the enabling of Linux kernel features just because they sound nice), they mess around with the userland, trying to improve things into breaking.

Tom Servo said:
And I've been using Android since the G1, minus a small timeout on WP7, and custom ROMs always came with quirks left and right, that in their entirety always managed to piss me off in some way. If they don't do stupid **** in the kernel (I especially like the enabling of Linux kernel features just because they sound nice), they mess around with the userland, trying to improve things into breaking.
Click to expand...
Click to collapse
Google tells you how and what to build a completely untouched version of their code. If that bugs ya, and is not official enough for ya, then you are missing the point of this device. The device is officially supported by AOSP for yakju and mysid. If the idea of a source built rom bugs you just because its not on a Google sanctioned buildbox, then thats a shame.
I understand what you are saying about customized builds, but its easy to make a completely stock Google approved experience. Download source, setup vendor, and then make. Then you can use fastboot to flash. No need for clockwork, no need for root. If there is a demand for this, I would be happy to make both maguro and toro builds. I won't even root them and they will be odexed.

Once i get some time i plan on compiling myself a fully stock ics rom. Cause i can and that is the point of this stupid thing.

A quick word about JB hate.

We've seen lots of complaining in the last couple of days about what is and isn't working in these ports.
It seems GPS may or may not be working correctly, that it may or may not be due to the Leap Second.
WiFi, Bluetooth, volume... if you have these issues, they can mostly be remedied. If not, gratz.
The fact is, these Roms are ports of development previews on a phone slightly but importantly different than yours running an OS that hasn't been released yet.
I was deeply amazed and impressed that some developers had working ports to CDMA the very night it was announced for GSM.
I'd you are running one of these JB ports and you find that it works well enough as a daily driver, consider yourself fortunate and hit the thanks button on the OP, maybe even donate.
If you are trying it out, but find that it lacks the stability or functionality that you require, click the thanks button on the OP anyway because they spent the time to give you something now for free that which you would otherwise have to wait weeks for, or, considering VZW's track record, maybe never.
This is how I'm looking at it- I'm getting to preview the latest update for free before it officially comes available. Just like those lucky bastards at Google I/O, except how much did they pay per ticket?
Thanks, devs, for doing what you do.
Sent from my Galaxy Nexus using xda premium

Jubomime said:
This is how I'm looking at it- I'm getting to preview the latest update for free before it officially comes available. Just like those lucky bastards at Google I/O, except how much did they pay per ticket?
Thanks, devs, for doing what you do.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
They paid $900 per ticket. But they get $1200 or so free of stuff. So they actually received 300 for going to it if you look at it that way.
Nevertheless I'm very pleased with JB. Everything is working beautiful for me. I using daily driver now without any issues. Just the stock JB at that. I'm not much for all the features of Roms. More into kernel tweaks which I do miss from glados kernel. But Franco is doing fine for now.

M3drvr said:
They paid $900 per ticket. But they get $1200 or so free of stuff. So they actually received 300 for going to it if you look at it that way.
Click to expand...
Click to collapse
Thats why I put going to Google IO one year at least on my bucket list.

i think people are forgetting these roms are from nandroids! lol!

I most definitely appreciate the efforts. I ran the Vicious JB stock port on my VZW Gnex but in the end, I couldn't stick with it because the Verizon framework apps don't work on Jelly Bean yet. This means I couldn't use the My Verizon or NFL Mobile apps, and that's a deal breaker. I understand that you can blame Verizon for requiring the back end framework in order for their branded apps to work, and that's all fine and well, but at the end of the day, I couldn't run them.
Be that as it is, I still appreciate the efforts of those developers to have a working CDMA port the same night. Thanks to all who do what you do. I'm a software developer myself so I know how tedious this crap can be.

Half of the JB "hate" posts are not "my app doesn't work, JB sucks!" but rather "my app doesn't work, I'm posting it in case someone has stumbled upon a fix"

The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).

CMNein said:
The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).
Click to expand...
Click to collapse
Thanks for such an insightful comment. Any more bright ideas?
Sent from my Galaxy Nexus using xda app-developers app

chancy319 said:
Thanks for such an insightful comment. Any more bright ideas?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No, it succinctly indicates the issue at hand.
Sent from my Galaxy Nexus

oldblue910 said:
I most definitely appreciate the efforts. I ran the Vicious JB stock port on my VZW Gnex but in the end, I couldn't stick with it because the Verizon framework apps don't work on Jelly Bean yet. This means I couldn't use the My Verizon or NFL Mobile apps, and that's a deal breaker. I understand that you can blame Verizon for requiring the back end framework in order for their branded apps to work, and that's all fine and well, but at the end of the day, I couldn't run them.
Be that as it is, I still appreciate the efforts of those developers to have a working CDMA port the same night. Thanks to all who do what you do. I'm a software developer myself so I know how tedious this crap can be.
Click to expand...
Click to collapse
I used My Verizon on JB. You just need to install the VerizonSSO apk in order for it to work...I can upload the file if you need it.

well you know what the say "everything's amazing these days, nobody's happy"

[email protected] said:
I used My Verizon on JB. You just need to install the VerizonSSO apk in order for it to work...I can upload the file if you need it.
Click to expand...
Click to collapse
Would you mind? I can find download locations out there but I'm not sure what version's needed.

CMNein said:
The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).
Click to expand...
Click to collapse
I hate you for making me google bronies.

jesusice said:
I hate you for making me google bronies.
Click to expand...
Click to collapse
Bring on the hate :cyclops:

These aren't "ports" of Jelly Bean roms. They are the real deal made specifically for this chipset and device. And, everything works.

I had to look up bronies as well.... I am sending along my hate alone with jesusice

akira02rex said:
These aren't "ports" of Jelly Bean roms. They are the real deal made specifically for this chipset and device. And, everything works.
Click to expand...
Click to collapse
That sort of depends. There are some changes that have to be made to a ROM for the GSM model to be 'ported' to the CDMA models. So, it's a 'port' for those phones, because only the GSM developer preview was 'released'.

They do realize other top phones are just getting ice cream sandwich, and we Nexii already have Jelly Beans sweet taste in our mouths?? Ridiculous!
Sent from my Nexus Prime

One of those lucky ones everything is working just fine, still couldn't see any issues, and I flashed my phone on the 28/06

Funny how ICS was the major update but jb is more of a complete experience.
butter and jelly please...

Android 4.1.2 released to AOSP

https://groups.google.com/forum/?fromgroups=#!topic/android-building/2rkEoKMnhzU
Let the fun begin! Trying to find a changelog...

Oooooo
Sent from my Galaxy Nexus using Tapatalk 2

now that´s nice ! it´s not even my birthday

I smell OTAs coming!

I knew it wouldn't take long before someone HAD to post this...Lol
Sent from my Galaxy Nexus

Future variants of
the grouper hardware will have a minor change in one of the components
(the power management chip) that will not be compatible with 4.1.1.
Click to expand...
Click to collapse
What..........................

Mach3.2 said:
What..........................
Click to expand...
Click to collapse
My guess is they did something to the power management chip to stop the screen flicker.

Mach3.2 said:
What..........................
Click to expand...
Click to collapse
Most likely there is a new revision of the hardware with a new power management chip and it will have to run 4.1.2 or later.

oldblue910 said:
My guess is they did something to the power management chip to stop the screen flicker.
Click to expand...
Click to collapse
I had some real bad flickering a few day back, maybe i'll send it in for RMA after the new grouper hardware comes out.

As others have said and JBQ confirmed 4.1.2 is a minor update on top of 4.1.1 the new revision of hardware deals exclusively with future revisions of the Nexus 7 (grouper), not maguro or toro (Samsung Galaxy Nexus) devices. Apparently these new revisions are shipping with a new power management chip that is completely incompatible with 4.1.1 as new driver/bootloader tweaks are necessary. https://groups.google.com/forum/?fromgroups=#!topic/android-building/2rkEoKMnhzU

As per the update notification on the Nexus 7, Android 4.1.2 "improves performance and stability and fixes bugs." Not too helpful, but it's a start.

rrohanjs said:
As per the update notification on the Nexus 7, Android 4.1.2 "improves performance and stability and fixes bugs." Not too helpful, but it's a start.
Click to expand...
Click to collapse
Are update notifications ever useful?
I smell a whole bunch of roms updating to this even though it does nothing for the gnex. Oh well...4.2 is coming so i'm happy.

aooga said:
Are update notifications ever useful?
I smell a whole bunch of roms updating to this even though it does nothing for the gnex. Oh well...4.2 is coming so i'm happy.
Click to expand...
Click to collapse
The notification also says the stock launcher now supports supports landscape mode. Whether or not we see that on the GN is anyone's guess.

bozzykid said:
The notification also says the stock launcher now supports supports landscape mode. Whether or not we see that on the GN is anyone's guess.
Click to expand...
Click to collapse
No we're not...landscape launchers on phones are really useless IMO.

Awesome
Sent from my Samsung Galaxy Nexus using Tapatalk.

aooga said:
Are update notifications ever useful?
I smell a whole bunch of roms updating to this even though it does nothing for the gnex. Oh well...4.2 is coming so i'm happy.
Click to expand...
Click to collapse
I doubt that a 31 MB update just fixed the launcher rotation and Google waited 4 months after it was released to fix it. As stated I'm sure there are some bug fixes and other misc fixes.

not excited untill a complete changelog shows some awesome changes, but I won't expect too much of such a minor update. Anyways, updates are a good thing (most of the times)
edit: I was going to add that I hope the LG Nexus will bring some more changes with it's OS, but Android Police seems to know better :
It's also a good time to bring up the fact that the LG Nexus prototype that we saw yesterday was also running 4.1.2. Today's announcement seems to add further credibility to that story.
Click to expand...
Click to collapse

I hope it bring some bug fixes for galaxy nexus too!
Sent from my Galaxy Nexus using xda app-developers app

miketoasty said:
I doubt that a 31 MB update just fixed the launcher rotation and Google waited 4 months after it was released to fix it. As stated I'm sure there are some bug fixes and other misc fixes.
Click to expand...
Click to collapse
The update is required for the new Nexus 7 hardware since previous versions aren't compatible. So if they are shipping them soon, then they need to have a proper build. Also new drivers and a new bootloader is included.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
gubshi said:
not excited untill a complete changelog shows some awesome changes, but I won't expect too much of such a minor update. Anyways, updates are a good thing (most of the times)
edit: I was going to add that I hope the LG Nexus will bring some more changes with it's OS, but Android Police seems to know better :
Click to expand...
Click to collapse
Since the device is most likely already in the manufacturing stage, it makes sense they would ship a stable build on it. Most likely Google employees are dogfooding a newer version however that will probably be available on launch day or soon after.

bozzykid said:
Since the device is most likely already in the manufacturing stage, it makes sense they would ship a stable build on it. Most likely Google employees are dogfooding a newer version however that will probably be available on launch day or soon after.
Click to expand...
Click to collapse
Well, I guess you're right. But it has to be available on launch, what else is the purpose of a new nexus?

[Q] Miracast on gnex once we install 4.2

I am just making sure i understand things right.
Every device with wifi and android 4.2 will support miracast correct?
So once 4.2 drops we will be able to run miracast from our gnex phones correct?

JustusIV said:
I am just making sure i understand things right.
Every device with wifi and android 4.2 will support miracast correct?
So once 4.2 drops we will be able to run miracast from our gnex phones correct?
Click to expand...
Click to collapse
I think it will. The Galaxy Nexus does support Wi-Fi Direct which is necessary for Miracast but we'll only know when the OTA update is released.

m-p{3} said:
I think it will. The Galaxy Nexus does support Wi-Fi Direct which is necessary for Miracast but we'll only know when the OTA update is released.
Click to expand...
Click to collapse
what does OTA have to do with it.
Once AOSP 4.2 drops we will have all sorts of roms to test with.

Wifi-Display™ by TI is necessary for Miracast, from what i remember.
Sent from my i9250

I am bumping this since AOSP has dropped.
Can anyone confirm?
Sent from my Transformer Pad TF300T using Tapatalk 2

So i am running 4.2 now. I do not think this is working as everyone was hoping.

Are there even any Miracast hardware (hdmi dongles or something) available to the consumer that support Miracast? I dont know of any, yet.

WiredPirate said:
Are there even any Miracast hardware (hdmi dongles or something) available to the consumer that support Miracast? I dont know of any, yet.
Click to expand...
Click to collapse
Are you revering to a product like the PTV3000?

JustusIV said:
Are you revering to a product like the PTV3000?
Click to expand...
Click to collapse
Kind of.. That does say it's Miracast. I saw on G+ where Phil from AC was going to do a review on it, but he said not to buy it yet. And these Amazon reviews agree that it's a pass. The price point is right for sure. Too bad.
http://www.amazon.com/Netgear-PTV30...dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1
Any Miracast boxes/dongles that actually functions correctly I guess would have been a better question.

I have one in hand.
It does WiDi and miracast
You flip between which you want.
I cant get the win 8 tablet to connect to the widi and none of my android 4.2 devices have the miracast functional :/
Some of its the devices fault some not.
They are saying they will update the firmware to support win 8 by the end of the year or something. not sure when android miracast stuff will be working.
*EDIT*
this amazon review
"This device says it will work with Miracast, but I have a Samsung Galaxy Nexus, Samsung Galaxy SIII, and an Asus Nexus 7"
this isnt the fault of the PTV3000
even with android 4.2 it isnt enabled yet.

So back to the main question, does gnex with 4.2 have miracast function?

JustusIV said:
I have one in hand.
It does WiDi and miracast
You flip between which you want.
I cant get the win 8 tablet to connect to the widi and none of my android 4.2 devices have the miracast functional :/
Some of its the devices fault some not.
They are saying they will update the firmware to support win 8 by the end of the year or something. not sure when android miracast stuff will be working.
*EDIT*
this amazon review
"This device says it will work with Miracast, but I have a Samsung Galaxy Nexus, Samsung Galaxy SIII, and an Asus Nexus 7"
this isnt the fault of the PTV3000
even with android 4.2 it isnt enabled yet.
Click to expand...
Click to collapse
Oh well damn you know better than any of us, you must have started this thread before getting 4.2 or the ptv?. Anyways. Disappointing 4.2 Miracast feature doesn't work on the only box available with Miracast (to my knowledge).

WiredPirate said:
Oh well damn you know better than any of us, you must have started this thread before getting 4.2 or the ptv?. Anyways. Disappointing 4.2 Miracast feature doesn't work on the only box available with Miracast (to my knowledge).
Click to expand...
Click to collapse
Yes i did
I kinda feel like google took us for a ride on this one
http://phandroid.com/2012/11/19/psa-nexus-7-and-nexus-10-do-not-support-miracast-wireless-display/

JustusIV said:
Yes i did
I kinda feel like google took us for a ride on this one
http://phandroid.com/2012/11/19/psa-nexus-7-and-nexus-10-do-not-support-miracast-wireless-display/
Click to expand...
Click to collapse
I know that feel. They say allot of stuff they think we want to hear, maybe they PLAN on actually doing what they say, maybe they make it up 10 minutes before announcing it. I wouldn't be surprised either way. Android Update Alliance? Sure. Right. I'll hold by breathe for that one. [email protected]? The lightbulbs controlled by your phone.. I'm sure Google will be able to complete this task before seven companies on kick starter do right? That's pretty much every damn announcement from last years keynote, all just a big show that they never made good on, and never even mentioned again. Did they even release the accessory developers kit they were talking about that year? I never read anything else about it.
Oh well. Guess I'm sticking to DLNA and AirPlay.

Got the Android 4.2 factory image on my Galaxy Nexus (yakju JOP40C) and there's no Miracast option available.
I guess only the Nexus 4 is the only certified smartphone for it right now.

Hi.
Are there any news on this?
My Galaxy Nexus has Android 4.3. I just got access to a Miracast dongle (I work at an online retailer) and it doesn't work.
WiFi Direct connects to the dongle, but it lacks the Miracast support. There is no option to enable "Wireless Display".

shinji21 said:
So back to the main question, does gnex with 4.2 have miracast function?
Click to expand...
Click to collapse
half yes.
GN's miracast so-so working, but miracast menu hidden by google.
if you familiar with handling custom ROM, this ROM enabling miracast in GN on 4.2.2.
4.3 with miracast not yet available.
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/Ota-packages
Sent from my GT-I9100 using xda app-developers app

[Q] Android Key Lime Pie 5.0

Guys, do you guys have any idea, or what do u guys thing , is GNEX getting the key lime pie upgrade?

yes we will. we will get it slightly after google i/o.

If we do...eh good I guess. If we don't, too bad

Yes.
Sent from my Nexus 7 using xda app-developers app

I doubt it, supporting old phones is rarer than finding 1000$ on a hotdog these days
I think jb is the last official update for the gnex
Sent from my Galaxy Nexus using Tapatalk 2

im sure we will. gnex is not that old. if not an official update, many custom roms will appear thanks to our devoted and skilled devs.

Well not that old cos It's still a good device that provides great user experience. I agree but when we're talking about such fast developing technology and update policy two years means a lot!
As far as I remember Google hasn't officially announced devices to get KLP yet so we can just speculate. But I wouldn't be much surprised if we didn't get it.

negrobembon said:
I doubt it, supporting old phones is rarer than finding 1000$ on a hotdog these days
I think jb is the last official update for the gnex
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
lol wat
The phone is ****ing 1 good year old.

madd0g said:
lol wat
The phone is ****ing 1 good year old.
Click to expand...
Click to collapse
Gnex was released october 2011 iirc, that makes about 1,5 years, by the time android 5.0 comes the Gnex will almost be around for 2 years, yes.

Non-google phones of that age have been supported. There's more reason to thingk the GNex will be included than not.
Sent from my Galaxy Nexus using xda app-developers app

The Nexus S got Jelly Bean, I see no reason why the G Nex wouldn't get KLP

Didn't Google promise to support nexus devices over at least a set month period? Around the time ICS came out I want to say they said 18 months, or maybe more. Even if they don't, we will see ROMS worked up for them. And if you look at the old nexus devices, updates didn't happen due to hardware limitation. Unless they got some new feature that demands a hardware feature be on the phone and we don't have it, I doubt they will stop updating us.

In terms of CPU/GPU GNEX is unfortunately not even close to 2012 flagships (not to mention 2013 beasts). I am not saying that our TiOMAP won't be able to handle KLP but it can be used as an excuse. I hope not.

forever_lol said:
In terms of CPU/GPU GNEX is unfortunately not even close to 2012 flagships (not to mention 2013 beasts). I am not saying that our TiOMAP won't be able to handle KLP but it can be used as an excuse. I hope not.
Click to expand...
Click to collapse
If your correct that means that KLP couldn't run on most mid end devices.
Sent from my Galaxy Nexus using Tapatalk 2

madd0g said:
If your correct that means that KLP couldn't run on most mid end devices.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am not saying anything. I've no idea about KLP's requirements. No idea what google decides either. We're all just speculating here. I was basically trying to figure out a possible excuse not to give us KLP. And CPU/GPU is GNexus' weakest side comparing to 2012 and newer handsets. That's all.
* In 2012 HTC One S with S4 Krait was also considered a mid end device.

It may or may not come out for our devices, technology advances pretty quickly, if we get it, good, if not, too bad, Google did not owe us anything.