Database Info

[Q] Reboot Bug - Is it really so prominent?

I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.

It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.

The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674

silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.

apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.

I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone

I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.

I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.

It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.

Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.

apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!

I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.

I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.

Weird, I don't have this bug

If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks

Do I have a faulty device?

This is my second s3... It's "updated" with baseband version I535VRLG1. I have not rooted because I don't want to risk ruining my chances of getting a new one if I have to...
Here are my current issues:
No Sim card error
Network Communication Issues (Connection will just drop randomly)
Keeps dropping 4g
Slow Speeds (4g as low as 1244 kbps down, 3g as low as 66 kbps down)
Slow GPS lock-on (Took 5-10 minutes at one point)
Some gaps between screen and bezel

If you can enumerate 6 things wrong with your phone then why are you asking us if it's defective? :laugh::laugh:
Get a new one man. None of that is normal as you imply by listing it all.

bobloblaw1 said:
If you can enumerate 6 things wrong with your phone then why are you asking us if it's defective? :laugh::laugh:
Get a new one man. None of that is normal as you imply by listing it all.
Click to expand...
Click to collapse
Maybe because I'm sick in the head, as well as a quality engineer who finds faults in anything...
I just feel like an a-hole because I made a big stink over my first one because of a loose home button... Now this new device has more issues than the first.
I also do NOT want a refurbished device. I want new.

As long as you're in the 2 weeks period you'll get a new one.
Also, as funny as this sounds, all these problems can happen if your sim card is faulty.

Mine is also an "updated" device with all those stickers. No problems here. Return it if you're having trouble
Sent from my SCH-I535

Madcat81 said:
As long as you're in the 2 weeks period you'll get a new one.
Also, as funny as this sounds, all these problems can happen if your sim card is faulty.
Click to expand...
Click to collapse
I got my phone on the 14th, but it's been less than 2 weeks since I got my replacement.... Does that count?
Maybe I should just try a new sim card first.

Madcat81 said:
As long as you're in the 2 weeks period you'll get a new one.
Click to expand...
Click to collapse
That is not 100% true.
I had a defective Rezound (badly overheating and killing the 2750 battery in 1/2 day) & it was almost new.
They wanted me to accept a refurb & until I threatened to just take it back for a refund they absolutely refused to give me a new one....

OT: but do they even have refurb S3's yet??

jmorton10 said:
That is not 100% true.
I had a defective Rezound (badly overheating and killing the 2750 battery in 1/2 day) & it was almost new.
They wanted me to accept a refurb & until I threatened to just take it back for a refund they absolutely refused to give me a new one....
Click to expand...
Click to collapse
So what ended up happening?
cmg5461 said:
OT: but do they even have refurb S3's yet??
Click to expand...
Click to collapse
They might. It seems like there has been a lot of issues with this phone already...
I wonder if I should take it back to the store (different one than I already returned my first one at), or over the phone.

Kreeker said:
So what ended up happening?
.
Click to expand...
Click to collapse
At that point, they gave in & sent me a new one in the box (I still have it)

Just called up, and they are sending me out a new ("certified") phone. Hoping this one fixes the issues, and is new....
All I did was list those exact issues up above, and he said well those are hardware issues and I'm going to have to send you a new one. I was ready for a big pain. Why can't the people in the stores be like this?

Flash always lit?

Anyone else have their flash led always dimly lit? Even when the phone is off my camera flash is dimly lit.

This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk

msavic6 said:
This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
I'm not sure Google Fit is the only possible source for this problem.
I have the same problem as OP. I got my S6 (non-edge, 32GB) about 24 hours ago and last night noticed the faint yellow glow on the back of the unit. I haven't been impressed by the battery life (admittedly a very limited time with it so far) - but this could explain the less than stellar battery life so far.
I don't have Google Fit installed (in fact if I go to the play store, I get a message saying that it's not compatible with this version"). S-Health is disabled too.
One other thing, when I use the flashlight feature, I notice that the light isn't nearly as bright as on the S3 - not sure if this is relevant, it is the same LED.
I rebooted the system, and even turned it off, the faint light stays on. If the unit wasn't sealed I'd pull out the battery just to confirm this light can go out :-/

I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.

verboten said:
I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.
Click to expand...
Click to collapse
Just dropping into say I also have the issue . 32GB, Standard S6, T-Mobile. I will call them and get a new one overnighted as well.

Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now

demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
I know I've done that on both of my s6s and still occurs.

demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
No disrespect taken, man those are hard to get off (thanks for confirming this, it looked like there were).
However, that might explain the flashlight function being a bit dimmer than on the S3, but it wouldn't explain the constant light source itself.

How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.

Mine doesn't have this dim light at all I checked and I closed all the lights to make sure nothing is coming out . I don't know I wish I can help

KristianKenneth said:
How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.
Click to expand...
Click to collapse
I think it would be difficult to see unless you ask them to let you into a dark storage room without windows That's how I can verify mine is still doing that during the day, though at night when I wake up with the phone next to me, the glow is comparatively quite substantial.
Plus, you'll have to wait about a week before you can see them in the store.

I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.

tenxo said:
I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.
Click to expand...
Click to collapse
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.

poweroutlet said:
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.
Click to expand...
Click to collapse
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m

tenxo said:
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m
Click to expand...
Click to collapse
I think you are right, unless you have the phone next to you at night you probably won't notice it., still odd, I would have expected others to notice it too. And, even as dim it is, it can't help with battery life. I hope it's a software issue and can be easily patched that way.

Edit: just noticed tonight that my phone does in fact have the LED issue. It's odd because I spent some time yesterday in the dark looking for the problem and it was no where to be found. Been laying in bed messing with my phone while it's charging, decided to flip it over and low and behold, dimly lit flash on :/.
-Matt

Roflwafflez said:
Mine does not seem to be having this issue. I checked it out last night in a completely dark room and couldn't see anything. To see if I could get an idea of what it looked like though, I turned on the torch for about 20 seconds, then turned it off and looked again and it did replicate the faint glow that it seems most people are speaking of, however it faded away in about 30 seconds.
-Matt
Click to expand...
Click to collapse
This is making me think some S6s just have this defect where the LED never turns off and some don't. I think it might be best just to return my S6 and repurchase the phone after its official release date. I think these earlier phones might be more prone to defects. My gut feeling is that this is something that won't be fixed via software. I don't think exchanging the phone for a new one will help too much given that so many other S6s also have the issue, you have a good chance that the new phone you get will also be defective.

poweroutlet said:
This is making me think some S6s just have this defect where the LED never turns off and some don't..
Click to expand...
Click to collapse
My guess is it's a hardware issue (perhaps they used a different supplier/component for this part) since all of the phones are presumably running the same software (some with the OTA update that was waiting from T-Mobile - like myself, others perhaps without it). If it can be patched with software is another issue.
Actually, perhaps it would be useful to know if those experiencing the problem have applied the OTA update and those without haven't. My hunch is it won't be a factor, but curious, so people reporting should state their situation.
For my non-edge S6 (black 32 GB) I have the OTA and my flash stays on dimly all the time.

I noticed this last night and I thought it could have just been some sort of burn in from using the flashlight. (64gb regular tmo S6)
It's basically impossible to tell with any sort light around whether or not this is happening, even just with residual light, but mine does seem to be dimly lit in a pitch black room.
Could it have something to do with the selfie feature on the camera? Using the heart rate monitor as a picture button, that is.

I have a 64 GB T mobile regular GS6 with the OTA and I do have the issue.

Intermittent freeze and no sound when making calls: hardware or software issue?

For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.

davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.

reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.

Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!

No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC

cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.

New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC

cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.

davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,

Question Static

So, WHats up guys?
Finally jumped back on the Pixel train and got my 7 Pro last night. After all the fun updates i noticed that when i make a call now, there is a strange opening of a call with a tiny bit of static and then it goes to normal. Anyone else experience this? It doesn't hinder the call in any way, i just found it strange.
PSA
Absolutely loving the phone. Near 24hr after a charge with 24% left but i forgot to check SOT but im sure it was close to 6hrs which is good for me.

I did see one other post that was similar to this. I've never had that issue, and iirc nobody who replied to that post did either.

xunholyx said:
I did see one other post that was similar to this. I've never had that issue, and iirc nobody who replied to that post did either.
Click to expand...
Click to collapse
Thanks. I should've checked the threads before i posted. Yeah its weird. Noticing that its only to one number so,maybe its their line??

Hi Avid_droid.
Yes, you are not alone in this regard.
I don't know if it's a coincidence, but my wife threw my cell phone from the table (half a meter more or less), and since then the following happens to me:
I make a call and I hear some interferences, something like "Clack clack", sometimes there are many, sometimes only 1 ... sometimes none ... it's very strange.
However, I think it has nothing to do with the drop... maybe it used to happen to me before and I didn't notice.
Sometimes I can go days without hearing that interference, and I think that everything is fine, but I hear it again. I have restored the phone several times and that does not solve anything.
Fortunately, it's not something that prevents me from making calls or using the phone normally, but when you spend a lot of money on a phone you get screwed by these things.
The bad thing about this is that I have read that if you talk to Google they will send you a refurbished phone, plus you will be 1 week or more with nothing.... I think I'll live with this problem (if it doesn't get worse).

Hugo.cb said:
Hi Avid_droid.
Yes, you are not alone in this regard.
I don't know if it's a coincidence, but my wife threw my cell phone from the table (half a meter more or less), and since then the following happens to me:
I make a call and I hear some interferences, something like "Clack clack", sometimes there are many, sometimes only 1 ... sometimes none ... it's very strange.
However, I think it has nothing to do with the drop... maybe it used to happen to me before and I didn't notice.
Sometimes I can go days without hearing that interference, and I think that everything is fine, but I hear it again. I have restored the phone several times and that does not solve anything.
Fortunately, it's not something that prevents me from making calls or using the phone normally, but when you spend a lot of money on a phone you get screwed by these things.
The bad thing about this is that I have read that if you talk to Google they will send you a refurbished phone, plus you will be 1 week or more with nothing.... I think I'll live with this problem (if it doesn't get worse).
Click to expand...
Click to collapse
Yeah it doesn't interfere with call or quality it's just odd right? It wasn't there yesterday and today it returned. I think maybe software issue cause I didn't experience it prior to updating.

avid_droid said:
Yeah it doesn't interfere with call or quality it's just odd right? It wasn't there yesterday and today it returned. I think maybe software issue cause I didn't experience it prior to updating.
Click to expand...
Click to collapse
Yes, it's not the end of the world, but I have to say I'm very disappointed with the overall call quality.
I have an old Huawei mate 20 that has much better call quality than the Pixel, .. and it's a 2018 phone!
Resignation.

Finally, and after a few days in which the problem was more frequent, I have decided to use the google warranty and return it for repair. I've upgraded to an iPhone 14 Pro Max, and I guess I'll sell the Pixel 7 Pro if it comes back repaired correctly.

Hugo.cb said:
Yes, it's not the end of the world, but I have to say I'm very disappointed with the overall call quality.
I have an old Huawei mate 20 that has much better call quality than the Pixel, .. and it's a 2018 phone!
Resignation.
Click to expand...
Click to collapse
I've been experiencing far more robotic voice calls the past couple days

avid_droid said:
I've been experiencing far more robotic voice calls the past couple days
Click to expand...
Click to collapse
From what I have read, it is ultimately a hardware failure and the only option is replacement.

Hugo.cb said:
From what I have read, it is ultimately a hardware failure and the only option is replacement.
Click to expand...
Click to collapse
I replaced my device the other day and best thing I did. No issues as of late.

I have to wait for my cell phone to arrive in POLAND (from Spain) and wait for it to come back... ****ing disgusting.

Hugo.cb said:
Hi Avid_droid.
Yes, you are not alone in this regard.
I don't know if it's a coincidence, but my wife threw my cell phone from the table (half a meter more or less), and since then the following happens to me:
I make a call and I hear some interferences, something like "Clack clack", sometimes there are many, sometimes only 1 ... sometimes none ... it's very strange.
However, I think it has nothing to do with the drop... maybe it used to happen to me before and I didn't notice.
Sometimes I can go days without hearing that interference, and I think that everything is fine, but I hear it again. I have restored the phone several times and that does not solve anything.
Fortunately, it's not something that prevents me from making calls or using the phone normally, but when you spend a lot of money on a phone you get screwed by these things.
The bad thing about this is that I have read that if you talk to Google they will send you a refurbished phone, plus you will be 1 week or more with nothing.... I think I'll live with this problem (if it doesn't get worse).
Click to expand...
Click to collapse
Exactly the same sound occurs to me sometimes just occasionally to remind me that it exists

avid_droid said:
So, WHats up guys?
Finally jumped back on the Pixel train and got my 7 Pro last night. After all the fun updates i noticed that when i make a call now, there is a strange opening of a call with a tiny bit of static and then it goes to normal. Anyone else experience this? It doesn't hinder the call in any way, i just found it strange.
PSA
Absolutely loving the phone. Near 24hr after a charge with 24% left but i forgot to check SOT but im sure it was close to 6hrs which is good for me.
Click to expand...
Click to collapse
Yes, mine does this as well. I've noticed it but not paid attention to it til i read this yesterday. I thought it was my Pixel Buds Pro (Which take FOREVER to connect when I take one out of the case to answer a call) - but today I'll try to use the phone itself to answer calls and see if it's still there

Hugo.cb said:
I've upgraded to an iPhone 14 Pro Max,
Click to expand...
Click to collapse
That's an upgrade?

HipKat said:
That's an upgrade?
Click to expand...
Click to collapse
Sorry.. I think you are right about this.
I actually think the Pixel 7 Pro looks like a better phone to me than the iPhone 14 Pro Max, but I bought one for a bit of a change of scenery.
I really regret it, I will surely return the iPhone 14 Pro Max if the Pixel 7 arrives repaired. I hope so.

After several days in RMA, Google has sent me an email telling me that the phone had an AUDIO problem and that it will be repaired.
Which seems strange to me because the audio in multimedia applications was perfect.... But well, when I have the phone in my hands I will tell you.

Well, the phone has arrived home. So far so good, although I have not tested it too much.
I will keep you informed.
EDIT :
After several calls, the problem continues. I'm throwing in the towel, I'm not going to go another week without a phone. As a bonus, I also have some dirt on the lenses, which I didn't have before.
I'll put up with this interference and strange noises on every call until I send the phone to hell in a few years.

Hugo.cb said:
Well, the phone has arrived home. So far so good, although I have not tested it too much.
I will keep you informed.
EDIT :
After several calls, the problem continues. I'm throwing in the towel, I'm not going to go another week without a phone. As a bonus, I also have some dirt on the lenses, which I didn't have before.
I'll put up with this interference and strange noises on every call until I send the phone to hell in a few years.
Click to expand...
Click to collapse
May be a hardware issue. That's what it seemed like with mine. There is no static any more but the small pop is still there. Pop on my Buds Pro and issue is resolved. Now the watch is another piece of bad judgement. I'm on my second one and thank the creator they gave it to me for free. $349 for a watch that sounds like it has a badly blown speaker is hardly worth it. It does what I need it to do though, time and messages.

avid_droid said:
May be a hardware issue. That's what it seemed like with mine. There is no static any more but the small pop is still there. Pop on my Buds Pro and issue is resolved. Now the watch is another piece of bad judgement. I'm on my second one and thank the creator they gave it to me for free. $349 for a watch that sounds like it has a badly blown speaker is hardly worth it. It does what I need it to do though, time and messages.
Click to expand...
Click to collapse
Latest news, Google is sending me a new terminal.
The truth is that I'm starting to be unconvinced about the purchase, and it is likely that I will end up buying an s23 ultra or similar.

Hugo.cb said:
Latest news, Google is sending me a new terminal.
The truth is that I'm starting to be unconvinced about the purchase, and it is likely that I will end up buying an s23 ultra or similar.
Click to expand...
Click to collapse
For me now, there is nothing to complain of about the phone. I like mine. My wife has the 23U and I don't like it. It's slows way down and feels like a 60hz phone. Also with the load speeds, I don't like Sammy. I walk around all day withy Pixel 7 Pro and my 13 Pro Max everyday. Didnt like the esim thing either.