Related
So, I've been running 4.03 with the UCKF1 radio since December, but I'm really wanting a stock update from Google. Why haven't they released anything for the 9020a at all? It's just a different radio from the 9020T and now the 9020T has seen 2 ICS revisions, while if I chose to only use the official OTA process, I'd still be on GB. Is Google finally going to release something for the 9020a now?
I don't believe anyone here can answer you with 100% certainty.
I still believe however that if we didn't see a release, there's a reason. But people aren't too good at the waiting game.
I'm starting to think 9020A may not be a nexus.
Sent from my Nexus S using xda premium
I am pretty sure you won't see a difference. Might as well stick with what you have. Also 4.0.4 is out too
Sent from my Nexus S using XDA
Waiting for 4.0.4 for my nexus s...
Sent from my Nexus S using XDA
i don't undestand why manufacturers hates "a" versions, already happened to me with a Sony E. X10 "A" version, never was updated correctly.
well it just a matter to wait and see....
According to JBQ, Google is waiting for Operator Approval. Same thing with Sprint...
fdlm82 said:
i don't undestand why manufacturers hates "a" versions, already happened to me with a Sony E. X10 "A" version, never was updated correctly.
Click to expand...
Click to collapse
Google is waiting for AT&T's approval before the i9020a release. At least that is what JBQ from Google implied today.
bozzykid said:
Google is waiting for AT&T's approval before the i9020a release. At least that is what JBQ from Google implied today.
Click to expand...
Click to collapse
Probably waiting for a new CarrierIQ binary
d-h said:
Probably waiting for a new CarrierIQ binary
Click to expand...
Click to collapse
AT&T doesn't have anything to do with the software. They are just sent the ROMs for testing. Unless you are implying Google is adding it to Nexus devices?
d-h said:
Probably waiting for a new CarrierIQ binary
Click to expand...
Click to collapse
At times like this I really do hate the North American carriers. I was pretty misinformed up to this point as to the nature of android updates on the nexus phones. I was always under this blissfully ignorant impression that it was fully under google's control to push updates at their sole discretion. Sort of like the advertising led me to believe.
So now that false belief has become painfully apparent to me, replaced with the knowledge that the carriers still have the ultimate say.
I doubt very much now that this update will be seen any time soon OTA in Canada if Telus has any say in the matter. Hopefully AT&T will authorize it soon so we can at least get a factory image we can flash ourselves.
Yes this wait is hella annoying especilly since i've been forced to use i9020t as base for mine but for those who are adventurous you can download the factory image for the i9020t from https://dl.google.com/dl/android/aosp/soju-imm76d-factory-ca4ae9ee.tgz and slectively flash boot.img and system.img.
You just need to unlock bootloader (backup first it wipes device) download the archive, extract the boot.img and system.img and flash them.
The commands are:
fastboot flash boot boot.img
fastboot flash system system.img
d-h said:
Probably waiting for a new CarrierIQ binary
Click to expand...
Click to collapse
Can't tell if trolling or not.....
What else is there that would require carrier approval?
Then again, perhaps the carriers selling the 9020A have been diligently testing a new radio file over the last three and a half months.
Sent from my Nexus S using xda premium
They need to test a new radio because the at&t radios are slow on 3g. I have to use the older kb3 radio just to get barely usable 3g speed
Sent from my SAMSUNG-SGH-I727 using xda premium
I made an XDA account just to comment on this issue.
When I bought my i9020a Nexus S from AT&T, I was under the impression that the only difference between this and the T-Mobile model was the radio/antenna. I was also under the impression that updates would be carrier-agnostic, since it is a Nexus device after all.
So why the hell does T-Mobile always get the updates instantly, seemingly not having to wait for approval? T-Mobile is a carrier just like AT&T, but it seems like T-Mobile users don't have to wait for carrier approval like we do on AT&T.
What is there to approve? Is approval from AT&T really necessary for changing the radio file?
ScOULaris said:
I made an XDA account just to comment on this issue.
When I bought my i9020a Nexus S from AT&T, I was under the impression that the only difference between this and the T-Mobile model was the radio/antenna. I was also under the impression that updates would be carrier-agnostic, since it is a Nexus device after all.
So why the hell does T-Mobile always get the updates instantly, seemingly not having to wait for approval? T-Mobile is a carrier just like AT&T, but it seems like T-Mobile users don't have to wait for carrier approval like we do on AT&T.
What is there to approve? Is approval from AT&T really necessary for changing the radio file?
Click to expand...
Click to collapse
You'll excuse carriers for not wanting to cripple their networks because some radios might be misbehaving...
Seriously, I don't get it. Why so impatient? Is anyone in a life or death situation regarding the ICS release?
Not too long ago, everyone found GB to be nice and dandy, now everyone wants to flee from it like the plague. The update will come in due time, and I for one largely prefer a polished version rather than one with issues.
So far the ICS release has seen enough bugs, some that even warranted a pull on the plug. I don't feel the rush to upgrade to something that won't work right...
My 2 cents
So all of us using a 9020a on a carrier other that AT&T are at the mercy of AT&T when it comes to updates on our Nexus phones? That wasn't what I signed up for when I chose a Google branded device on my Canadian carrier...
polobunny said:
Seriously, I don't get it. Why so impatient? Is anyone in a life or death situation regarding the ICS release?
Click to expand...
Click to collapse
I don't think there would be as much outrage if ICS hadn't been released for any version of the Nexus S yet.
It's not that people are upset that they don't have ICS; they're upset because some versions of the Nexus S have gotten updates while theirs have not.
Google promoted the Nexus line of phones as getting updates "as soon as they are available," because the updates are independent of the carriers, since they're supposed to come directly from Google. People were sold on the promise that there wouldn't be several months of delays between new Android versions and Nexus phone updates because it was a "pure Google" phone.
The news that apparently the carriers need to "approve" Nexus builds before Google pushes them out flies in the face of what Google told people they were getting.
The T-Mobile Nexus S now has 4.0.4, and my AT&T Nexus S doesn't even have 2.3.6 yet. So much for always having the latest available version.
That's why people are upset.
r.asimi said:
So all of us using a 9020a on a carrier other that AT&T are at the mercy of AT&T when it comes to updates on our Nexus phones? That wasn't what I signed up for when I chose a Google branded device on my Canadian carrier...
Click to expand...
Click to collapse
The delay is probably not just AT&T. Canadian carriers are known for taking longer to test updates than even AT&T. Who exactly Google is waiting on right now is not exactly clear.
Any word on if Jelly Bean is still on coarse to be released later this month?
Or had it been delayed again...
richport29 said:
Any word on if Jelly Bean is still on coarse to be released later this month?
Or had it been delayed again...
Click to expand...
Click to collapse
According to mobilesyrup, "early February" now. Looks like it isn't too far away.
Sent from my XT925 using Tapatalk 2
Dammit
http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/GeneralCareSupport/thread-id/355
I got my Fido RAZR HD from Canada yesterday - presumably Fido have the same update schedule as Rogers?
Still waiting for a SIM unlock code at the moment, so I can't even use it yet, booo
danifunker said:
According to mobilesyrup, "early February" now. Looks like it isn't too far away.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
I'll believe it when it's released. I was told "Late November" when I bought my Razr HD. Slipped nearly 3 months already. I'm expecting March, honestly. I think there's something in Rogers bloatware that isn't transitioning to JB well, and that's the holdup. No other good reason for it to take this long, since other XT925 have JB since Dec.
Hah, yeah you may be right about the bloatware it should be exactly the same as the international version (e.g. Euro models got JB late November), but with slightly different radio firmware...
It is pretty strange and frustrating rolling back from a two year old Nexus S on 4.1.2 to a brand new RHD on 4.0.4!
I know the feeling. My last phone was a Motorola Defy on CMX 4.1.2, and that phone started on Eclair.
Mods, this thread should be moved the Q&A since it isn't development related.
Next, about Rogers; I don't believe that it's their bloatware. I think they have resource problems with carrier testing. All of the updates I've seen issued from Rogers Motorola devices have had build dates months behind then when it was actually released. I wouldn't be suprised if the Rogers JB 4.1 build is dated October 2012. I think Rogers should setup some kind of early testing program for people who want updates on their phones faster, which would allow the user population to do the testing for them. I'm an IT guy and expect some problems with my technology, if I can help the company sort out bugs faster than they can find them I think we would all be a lot happier.
FYI, the Fido and Rogers firmware are the same build. When you put in a Fido SIM card, it removes the Rogers bloat and installs the Fido bloat.
Finally, until anybody has actually used a Verizon branded Motorola device, please don't talk about "bloatware" like it's so bad... We have like 8 apps that we can freeze, you should see what's on some of those VZW phones...
Haha, ok agreed on the Verizon bloatware... let's maybe just call it fluffware or something
Interestingly, when I got my Fido device, I put my T-Mo UK SIM in straight away and it did not prompt me to install crap at startup (i.e. with this).
So afaics, there is no fluffware on my phone!
Sad and annoying to hear about Rogers' testing bottleneck, but one has to wonder why they need to test so extensively anyway (vs. Euro operators for example). I mean, even Verizon beat them to the punch this time, and they have a horrendous rep for delaying firmware updates!
Su
I read somewhere saying that Samsung is rolling out Lollipop to all LTE models in the USA. My question is, will this update roll out work like it does for phones....meaning will this update have to go to the carrier first and then to the users? I hate to lose root, but I'm really hoping the update will improve performance. I bought the note pro the day it hit the stores and I am in bad need of better performance.
Please chime in on what you know about this update.
Thanks in advance.
chrispyutec said:
I read somewhere saying that Samsung is rolling out Lollipop to all LTE models in the USA. My question is, will this update roll out work like it does for phones....meaning will this update have to go to the carrier first and then to the users? I hate to lose root, but I'm really hoping the update will improve performance. I bought the note pro the day it hit the stores and I am in bad need of better performance.
Please chime in on what you know about this update.
Thanks in advance.
Click to expand...
Click to collapse
I guess I'm the only one who has an AT&T LTE version of the note pro. I guess the MOD can go ahead and remove this post being that it appears to be a space waster.
Thanks
You're not the only one with the device. Other than iPhones, I believe AT&T always gets the updates from the manufacturers and then adds their bloat before releasing via OTA.
I've got one and have been waiting too, don't know what's going to happen to root. Adding more apps into multi screen is really all i need root for anymore. I used to use it for controllers for games, but haven't used that in awhile.
It sucks being an AT&T kid huh? boooo, we get no love, lol Damn you AT&T!!!!!!
AT&T fail - January 2016 and still no update
If AT&T can't update in a timely manor, they need to stop selling devices.
I'm never buying from AT&T again.
Once Google fiber rolls to Atlanta, I'll be 100% free from the clutches of AT&T.
If they are not selling to you, they are selling you.
I bet the NSA is AT&Ts only repeat customer.
AT&T pushed the Lollipop update quite awhile ago.
So about a year ago my SM-930FD was stolen and I got an old iphone 6, well for no apparent reason it stopped getting any service and I've decided to go back to Android. I was debating between the Pixel XL and the S7 and I'm going to get the S7 but it's been a while and things have changed (a lot)
Could anyone suggest if I should get the F or U? I'm in the USA on T-Mobile. I remember it being a pain in the ass to get things like VoLTE working before and I think Samsung had only just allowed us to switch to Nougat before it was stolen.
Anyway I have been reading and all but I'd really appreciate some first hand advice. Or should I just go with the Pixel XL?
Honestly the the fact that I was able to update my iPhone 6+ to ios 12 was really nice, except that it just broke and that's not so nice.... I know we rarely get more than 1 major update with any android device and even then over a year after its release.
anyway thanks
Depends what you want.
Only the G930F / Exynos SoC can have custom ROM's installed.
The G930U with the Snapdragon SoC can't do that, but the modem will better support US carrier networks and bands.
Google delivers Android 13 December 2022 update for Pixel 7 and Pixel 7 Pro
Google has announced a major feature update for Pixel smartphones running Android 13. As of the December 2022 update, the likes of the Pixel 7 and Pixel 7 Pro support a dedicated reader mode and can share digital car keys with other compatible smartphones, among other changes.
www.notebookcheck.net
I put mine on the beta channel release. Coming from a P6P, using straight talk, it would not accept the sim.
Called Straight talk, which was useless. They said I had to buy a new sim card. Saw on a thread here that the
beta channel rom fixed it. Sure enough! After reboot, the sim card worked!
I was expecting 5g update, disappointing...
Nothing here. UK Sim free.
eagledipesh said:
I was expecting 5g update, disappointing...
Click to expand...
Click to collapse
I wouldn't hold your breath. They either chose horrible hardware, don't know how to fix it, or won't because we will buy a new Pixel. With that being said, I actually think that the 7 Pro is an improvement over the 6 pro. My battery and performance is dramatically improved because of the updated Tensor chip and I don't have the cell standby bug that plagued me in the 6 pro.
eagledipesh said:
I was expecting 5g update, disappointing...
Click to expand...
Click to collapse
This isn't the full release notes.
That article from notebookcheck.net referencing the Google Blog only concerns the "Android Feature Update", which is for GMS Android users. There is also a "Pixel Feature Drop" which Pixel users will likely get tomorrow. Plus there will likely be other "fixes" and whatnot.
biggiesmalls657 said:
I wouldn't hold your breath. They either chose horrible hardware, don't know how to fix it, or won't because we will buy a new Pixel. With that being said, I actually think that the 7 Pro is an improvement over the 6 pro. My battery and performance is dramatically improved because of the updated Tensor chip and I don't have the cell standby bug that plagued me in the 6 pro.
Click to expand...
Click to collapse
Unfortunately for me the bug still exists P7P. I am not sure if different hardware release have different modems. But my phone is useless at the moment.
xpact said:
Unfortunately for me the bug still exists P7P. I am not sure if different hardware release have different modems. But my phone is useless at the moment.
Click to expand...
Click to collapse
What's your setup? I'm rooted custom kernel and 1 ESIM using Xfinity Mobile. I also didn't restore settings with 6 pro backup. I flashed BL and modem before clean flashing stock to root
biggiesmalls657 said:
What's your setup? I'm rooted custom kernel and 1 ESIM using Xfinity Mobile. I also didn't restore settings with 6 pro backup. I flashed BL and modem before clean flashing stock to root
Click to expand...
Click to collapse
I am in 5G unsupported country and I am using physical SIM I have tried to disable DSDS but it didn't seem to stick. I have tried with stock and beta QPR1 same result. Which custom kernel would you recommend? I think the issue is with the radio and the Samsung Shannon 5300G. I am not sure if there is a radio firmware I could try.
"I am in 5G unsupported country"
I fail to understand the complaints from people who live in "unsupported" countries!
Why would you even consider buying ANY phone that is unsupported in any way?
The fault is yours not Googles! YMMV
jaseman said:
"I am in 5G unsupported country"
I fail to understand the complaints from people who live in "unsupported" countries!
Why would you even consider buying ANY phone that is unsupported in any way?
The fault is yours not Googles! YMMV
Click to expand...
Click to collapse
Probably because they wanted a pixel but Google only officially sells phones in like 4 countries (exaggerating but probably not by much). I want phones available outside of the USA all the time but my wonderful carrier (verizon) and to a degree the other carriers as well suck and want big money to certify the ability to use their towers (bands). Stuck mainly with iSheep, Samdung, One Plus (already settled) and Google (constant hardware problems).
It will be difficult for me to make you understand anything since you fail to understand simple things like why anyone would pick a Google phone instead of another brand. Anyway I had Nexus and Pixel phones in the past and they have worked just fine. I was very well aware 5G and VoLTE don't work and I was not after these features. I would be perfectly fine with just 4G. Mine Pixel 6 Pro and Pixel 2 XL worked flawlessly. I might have a faulty hardware I am not sure at this point. If you could not help me at least don't blame me for my choices, the money I have spent are mine not yours. Like I have said I know since the beginning some of the feature would not work and this was a risk I was willing to take since I wanted a "clean" android and rootable + unlocked bootloader (there are not many phone manufacturers offering such features). I was not expecting the Pixel to not support any well established telecom standards. Aside from that I live in Europe and I bought the phone from neighboring country. It is not from Japan or US/Canada with different bands.
@xpact , it might be your phone or possibly faulty modem hardware. I am in the US using the 7P7 (rooted, unlocked) without any issues (I keep 5G off) 99% of the time. Once in a while I have to restart my phone or turn airplane mode on and off because I would randomly lose service. Its pretty rare though and even less now after the November update.
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
foamerman said:
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
Click to expand...
Click to collapse
You can install the global one.
foamerman said:
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
Click to expand...
Click to collapse
I bought the unlocked P7P from Google and Verizon is my carrier. I have only been flashing the generic firmware to avoid VZW bloatware as much as possible. I haven't had any issues.
xpact said:
It will be difficult for me to make you understand anything since you fail to understand simple things like why anyone would pick a Google phone instead of another brand. Anyway I had Nexus and Pixel phones in the past and they have worked just fine. I was very well aware 5G and VoLTE don't work and I was not after these features. I would be perfectly fine with just 4G. Mine Pixel 6 Pro and Pixel 2 XL worked flawlessly. I might have a faulty hardware I am not sure at this point. If you could not help me at least don't blame me for my choices, the money I have spent are mine not yours. Like I have said I know since the beginning some of the feature would not work and this was a risk I was willing to take since I wanted a "clean" android and rootable + unlocked bootloader (there are not many phone manufacturers offering such features). I was not expecting the Pixel to not support any well established telecom standards. Aside from that I live in Europe and I bought the phone from neighboring country. It is not from Japan or US/Canada with different bands.
Click to expand...
Click to collapse
I'm in Europe too and have the p7p from Germany, all works fine, no faulty hardware at all. Where did you buy your phone? I'm on stock firmware but had rooted it and there was also no problems, I often think to myself wtf you are always doing with your phones?
Thanks guys. I'm off to see the Wizard.
Gerr1 said:
I'm in Europe too and have the p7p from Germany, all works fine, no faulty hardware at all. Where did you buy your phone? I'm on stock firmware but had rooted it and there was also no problems, I often think to myself wtf you are always doing with your phones?
Click to expand...
Click to collapse
I bought it from Germany as well ) The previous pixel I had I bought it from UK and the Nexus 6P from UK as well. But the ones from UK I did not bought on first date but few months after they might had different hardware modem revisions.