Related
EXCHANGE IT!
sorry! I'm just really excited, I wasn't getting any GPS signal so I took it back to the corporate store, saved a quick ti backup to my sd, swapped the phone and BAM! I now get perfect GPS locks within SECONDS of activating maps!
also! I had some weird Facebook errors, only few would sync, wouldn't sync all the time etc. etc. NO PROBLEMS ANYMORE all my contacts sync and match up perfectly.
seriously the phone is now like it should be.
I asked the corporate rep (same guy I've been going to for years) he told me that the first batch of captivates went out with corrupt firmwares, but they weren't bad enough that they would have noticed anything wrong (or they did and chose to ignore it...) anyways, round two of the phone is fixed up and great!
My firmware: 2.1-update1
my baseband: I897UCF6
my kernal 2.6.29
that is the LATEST firm/base/kernal and If you can't get your phone to OTA update to it, I HIGHLY suggest you make a Ti backup and exchange it, you'll be out a few hours of your life but the phone will WORK
I bought my Captivate on launch day, and I've been running the same firmware/baseband/kernel since day one. You were misinformed about an initial batch of bad firmware.
That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.
Same here. Got it on release day and have the same firmware. I have not noticed any issues yet.
jmreed97 said:
That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.
Click to expand...
Click to collapse
well my GPS didn't work out of the box but i just figured it was because I was in the mall. but as soon as I got the new one, it started right up.
facebook sync wouldn't sync properly either, and now it is syncing 100% fine
the phone would randomly shut down, it's been 4 days no shut downs
I dunno, I waited to post this to make sure it wasn't a fluke, maybe its just mine but it seems legit and my launch day device was definitely NOT 2.1-update1, I checked it right before I turned it in and it was just 2.1
yup, same here, got it on launch day, same info, but no dice on a consistent GPS lock.
you just got a bad phone dude. my friend got a launch day phone and his ate his external sd card, had a dead pixel, and would random shut off. just one of those thangs!
I got mine on launch day and have same firmware and everything. We didn't all happen to get a few bad phones. Samsung has manufactured phones that are bad from the beginning and they won't admit to it yet. This is worse then antennagate with apple.
Atleast then all you had to do was stick a piece of tape on the corner and voila! no problems. I wish fixing the issues with this phone were that easy. But we have the brightest minds at xda trying to fix our issues and they are still stumped by gps... nearly a month after release.
And even if xda minds can fix the issues... I find it extremely frightening that part time developers that do this for fun can fix issues faster then samsung can even admit to it(lag fix for example..) The more and more I think about this whole issue... the less I feel confident about Samsung as a mobile manufacturer.
V DidDy 210 said:
my baseband: I897UCF6
Click to expand...
Click to collapse
Are you sure it is I897UCF6, or is it I897UCJF6 ? Mine has a J.
Mine has JF6 also.
:facepalm:
everyones GPS works for the first day or two.
Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.
I returned my Phone yesterday and can confirm the GPS issue still exist on the replacement. Also, according to the sales rep this was from a newly shipped batch, so take it for what its worth.
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.
IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.
Click to expand...
Click to collapse
The Gps problem is a known problem for last few months, so i wouldnt be holding my breath for any fix to be coming out anytime soon. I am sure they will get around to it eventually if they do. Seems to me they are more concerned getting galaxy s phones out in multiple markets
IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market.....
Click to expand...
Click to collapse
According to who?
i have the same firmware as you bro, everything is the same with the same GPS issue as everyone else.
IsaiahC said:
Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.
Click to expand...
Click to collapse
So to follow up from yesterday, I installed a lag fix and messed my phone up pretty badly. I flashed back to stock rom and took it back to AT&T and exchanged it for a new one.
I HAVE ABSOLUTELY NO TROUBLE GETTING A LOCK IN UNDER 1-3 SECONDS EVERY TIME. Also, as a note, the SIM tray in the back of the phone is different than the one I had previously.
I'm not telling you to go exchange your phone but AT&T has an under 30 money back or exchange return policy. Just tell them you called Samsung or AT&T already and they told you to bring it in for a new one because it has trouble establishing a GPS lock.
Anyone try gps status app?
Run that first, get a lock then go to maps, should get a lock fast...
I Had my phone for 2+ weeks and gps works, not great but works (locks under 2 minutes if I can point to the sky, drop signal occasionally, pretty accurate).
I had random shutdowns and went through all the troubleahooting over the phone and when I went to turn it at their warranty center per the phone support, the tech at the warranty center did a master reset and said the randon shutdowns are a software glitch with an app i downloaded. (it was looping the boot sequence over and over untill i pulled the battery on stock jh7.) I also mentioned my gps hasent worked since day one (august) and he said an update is coming this week to fix that i said that the last update was supposed to be the fix he says this is the fix. So maybe this week? By the way he said i have a 1 year warranty and if its not right they will replace it. At what point are they going to be replacing our phones?
Sorry but had rant a little its getting a little annoying now
We hear updates are coming almost every week. I will be glad to see it when it comes but I will not get my hopes up. I will believe it when I see it or in this case download it.
Agreed, they will tell you what you want to hear to get you out of their face. It's customer service 101 (I was a golf pro for 16 years so I know).
Bottom line is if you are unhappy with the phone he told you your have a year to replace. If you are insinuating they are going to replace all our phones because of the GPS fault, you got another thing coming. Right now they are more concerned with selling new phones for the holidays. When that rush is over then maybe they worry about making anything right.
My two cents.
has samsung all together abandoned this phone in favor of the newer nexus s? I sure do hope not.
we are waiting on the carriers to release the Froyo update... they have had them for awhile now... more than likely expect the release in Q1 of 2011
i doubt we will get an update
seriously, i'll be a miracle if samsung does end up fixing these issues. they have been present since day one.
Samsung has released Froyo to the carriers for the entire SGS line. We are waiting on AT&T, not Samsung.
As far as the GPS goes, the Rogers Wireless Captivate has a GPS that is flawless by all reports. Samsung claims they released a fix for the GPS. Based on these two pieces of information, I think we are at AT&T's mercy on this too...
Sent from my SAMSUNG-SGH-I897 using XDA App
jonjonk said:
has samsung all together abandoned this phone in favor of the newer nexus s? I sure do hope not.
Click to expand...
Click to collapse
IIUC, Samsung has released the update. We're waiting on AT&T not Samsung...that is if I've got it right.
Mike
I think I'll hang out til about a week after 1/1 for an "official" 2.2..then I'll spend some time reading up on these forums on what/how to flash 2.2 and see what happens. I'm not a tinkerer, and IMO the stock Captivate is great-GPS works fine, I don't have any major needs for anything more, but it is tempting
We don't really know if AT&T has the final build or not. But the Samsung Twitter account still says 2.2 by the end of the year
cappysw10 said:
Agreed, they will tell you what you want to hear to get you out of their face. It's customer service 101 (I was a golf pro for 16 years so I know).
Bottom line is if you are unhappy with the phone he told you your have a year to replace. If you are insinuating they are going to replace all our phones because of the GPS fault, you got another thing coming. Right now they are more concerned with selling new phones for the holidays. When that rush is over then maybe they worry about making anything right.
My two cents.
Click to expand...
Click to collapse
Yeah, the holidays will have them hoppin' to sell and that means customer service can easily go by the way side.
BTW, since it costs the gov't 1.67¢ to produce a penny..your two cents worth is actually 3.34¢ worth.
Mike
MicroBeta said:
Yeah, the holidays will have them hoppin' to sell and that means customer service can easily go by the way side.
BTW, since it costs the gov't 1.67¢ to produce a penny..your two cents worth is actually 3.34¢ worth.
Mike
Click to expand...
Click to collapse
Holy hell.....I'm rich. I hope that doesn't put me in a higher tax bracket come Jan.
mattbeau said:
I had random shutdowns and went through all the troubleahooting over the phone and when I went to turn it at their warranty center per the phone support, the tech at the warranty center did a master reset and said the randon shutdowns are a software glitch with an app i downloaded. (it was looping the boot sequence over and over untill i pulled the battery on stock jh7.) I also mentioned my gps hasent worked since day one (august) and he said an update is coming this week to fix that i said that the last update was supposed to be the fix he says this is the fix. So maybe this week? By the way he said i have a 1 year warranty and if its not right they will replace it. At what point are they going to be replacing our phones?
Sorry but had rant a little its getting a little annoying now
Click to expand...
Click to collapse
Out of curiosity what app did you download that was causing random shutdowns. I'm having random shutdowns now, when my battery is around 45-46%. But I noticed that it doesn't happen when data connections are turned off.
vikdmon said:
Out of curiosity what app did you download that was causing random shutdowns. I'm having random shutdowns now, when my battery is around 45-46%. But I noticed that it doesn't happen when data connections are turned off.
Click to expand...
Click to collapse
Nothing in particular; facebook, memento pro, xda, astro, slacker radio.... Ect ect. I have been running stock for a while now and i have no idea why it started. I just noticed my pocket kept "launching rockets" repetedly and found my gone looping a boot. Thats the main reason i was going to return it. But alas it hasent had any reboot problems since. So maybe this might work for you. If it starts again, However, ill probably try to return it again.
Sent from my SAMSUNG-SGH-I897 using XDA App
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.
So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
woody1 said:
So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
Click to expand...
Click to collapse
My opinion is to wait for the November or December update and then upgrade to Android 11.
I'm still on Android 10
woody1 said:
So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
Click to expand...
Click to collapse
No issues with A11; Oct update smoothed out a few rough edges that weren't that jagged to begin with. Every update brings drama from the fringes. Gotta decide what camp you fall into.
Are there any Android Auto issues with the current version of 11? I think there were some at one point. BTW, I'm upgrading from an OG Pixel XL which is still going strong.
Weird mine came with 11 out of the box.
Limeybastard said:
Weird mine came with 11 out of the box.
Click to expand...
Click to collapse
You're in the UK? I think your release date was later than other countries so that's probably why.
WAusJackBauer said:
You're in the UK? I think your release date was later than other countries so that's probably why.
Click to expand...
Click to collapse
I'm based in USA although an expat. I bought mine from Best Buy today.
Just my 2 cents. I just got my 4a yesterday and it came with 10, i updated to 11 during setup. I have ZERO issues. I was actually a little worried reading stories about issues, but i don't have a single issue.
tCizler said:
Just my 2 cents. I just got my 4a yesterday and it came with 10, i updated to 11 during setup. I have ZERO issues. I was actually a little worried reading stories about issues, but i don't have a single issue.
Click to expand...
Click to collapse
Of course you didn't. For every negative report there are vastly larger numbers of perfectly happy users. Widespread issues draw a huge response over multiple boards that easily stand out from run-of-the-mill grumbling.
DB126 said:
No issues with A11; Oct update smoothed out a few rough edges that weren't that jagged to begin with. Every update brings drama from the fringes. Gotta decide what camp you fall into.
Click to expand...
Click to collapse
Plus if you DO have problems after "use 10 for a bit, install 11" then you'll probably end up factory resetting and doing all your reinstallation, config again.
(I recall from back when i could be bothered fiddling with cyanogenmod that nobody was interested in bug reports if you did a "dirty flash" - you had to do a factory reset first as it cured all sorts of problems. i wonder if google doesn't test stuff properly and you end up in the same situation and that's why factory resetting fixes so many problems).
The devices came with 10/11 based basically of release date in your state/region you live. I for example live in Italy and I bought mine from Google directly. It arrived 8 Oct with already 11 installed and with Oct security patch. No issue here with 11, as the major part of the other people. Let's say that's generally is expected to have some problems when there is a major release come out, as with any other software piece, not only android, but generally a couple of update fix all. And it seems so with Google security patch too.
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
woody1 said:
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
Click to expand...
Click to collapse
On Android 11 because phone shipped with it .
Should be no need to reset first.
No touch screen issues with Spigen protector.
Android auto works fine with the assistant lagging from time to time. However that could have been due to poor service....
woody1 said:
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
Click to expand...
Click to collapse
It's best to factory reset AFTER updating.
Also I'm fairly sure by now every region would have the October security update.
I did the update this afternoon. The update was for the September release, but then there was a 2nd update which brought it up to October. The phone seems to be running well after the updates. It seems a little zippier than before.