Okay, all caught up. No change from yesterday afternoon. Going to get ready to fly today... my buddy fixed his little parachute guy and one of the planes I have is capable of carrying him, so I have to bring that one today. I also want to put a test-flight on my Blackhawk. Then it's home for a quick dinner and watching the Giants/Eagles game tonight at 8:30. I'm so nervous... the Eagles are in a sad state right now but this is also the time of year the Giants start their annual decline. Go Giants!
Hope it's a software issue and not hardware. I REALLY hope. That's a show-stopper right there... just like buying a gift-wrapped Lexus that won't get out of 1st gear.
Let's hope THAT'S the delay... they have GOT to get this fixed or there will be a flood of returns in the first week.
Hey guys, I was on vacation for a week (cruise, no internet), anyone care to give me an overview what I missed? Was hoping I would come home to be able to buy a nexus, guess not
Not sure if this has been posted yet i.e. the video. It could be the cause of the delay? I believe they some said it is a software problem, but it looks like a hardware issue. Tell me your thoughts
I can only see it being a hardware issue if the volume rocker itself is sticking, or if there is a conflict in the chipset. You would THINK that such a hardware issue would have come up in early testing, though.
I'm leaning toward a software issue, as ICS has final control over the functions of the phone - including volume. Seems to me that ICS is, for some reason, resetting the volume down to zero: every time you turn it up, the software takes it back down.
Should be a relatively quick fix... unless the fix affects something else. Which - in the case of something as complex as ICS - could be very well happening.
Not sure if this has been posted yet i.e. the video. It could be the cause of the delay? I believe they some said it is a software problem, but it looks like a hardware issue. Tell me your thoughts
THIS, doesn't look good. Just seems odd that none of the reviews of the phone prior to release mentioned any sort of problem like this. Seems like if this was a hardware design problem, it would have shown up LONG before now. I mean there is no telling how long Google employees and execs have been using this phone daily.
Hey guys, I was on vacation for a week (cruise, no internet), anyone care to give me an overview what I missed? Was hoping I would come home to be able to buy a nexus, guess not
Hope it's a software issue and not hardware. I REALLY hope. That's a show-stopper right there... just like buying a gift-wrapped Lexus that won't get out of 1st gear.
Let's hope THAT'S the delay... they have GOT to get this fixed or there will be a flood of returns in the first week.
It could be something like key debounce or another component of the A/V subsystem code writing to the wrong property of the volume API... Too many possibilities to list but that's "how" it 'could' be s/w. It could just as easily be h/w - bad switch, case torsion/flexion affecting switch operation, etc.
I can only see it being a hardware issue if the volume rocker itself is sticking, or if there is a conflict in the chipset. You would THINK that such a hardware issue would have come up in early testing, though.
I'm leaning toward a software issue, as ICS has final control over the functions of the phone - including volume. Seems to me that ICS is, for some reason, resetting the volume down to zero: every time you turn it up, the software takes it back down.
Should be a relatively quick fix... unless the fix affects something else. Which - in the case of something as complex as ICS - could be very well happening.
The issue (clickable above the video) seems to imply the issue is most often seen when the phone is connected via 2G, is streaming something, and loses its WiFi connection or WiFi is turned off. So I suspect some firmware driver updates will fix this pretty soon. Looks to need a Samsung driver fix, to me.
I don't know much about what would be indicative of software vs. hardware, but in reading the problem reports submitted to google, it appears to be a problem with how streaming data on 2G is handled. Us Verizon folk should have a totally different radio, and be on LTE all the time , so I'm hoping we won't experience this problem too. If we do, at least we'll get the update from Google quicker.
RAWRRRR! Today starts the beginning of a new week. The week that is rumored that our Nexus will release. Or it could be next week on Cyber Monday. Either way, we're only a week away!
Well, the OTA may not be ready. The software fix that resolves the volume control might, for example, interfere with the display drivers. Can you imagine how many people will return their phones and get something else rather than wait for a fix? Verizon, Google and Samsung would take a huge bath on Nexus.
I listen to my mp3s on my phone all day, every day. That would flat-out drive me nuts! Can't hear people on a call, either. It's a beautiful paperweight without that fix in place - a fix that doesn't break something else. Waiting days, weeks or even months for a fix would be unacceptable. It's a potential mega-Bionic.
I don't know much about what would be indicative of software vs. hardware, but in reading the problem reports submitted to google, it appears to be a problem with how streaming data on 2G is handled. Us Verizon folk should have a totally different radio, and be on LTE all the time , so I'm hoping we won't experience this problem too. If we do, at least we'll get the update from Google quicker.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.