Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone 4 Signal Issue Can Be Fixed With a Software Update?
- Thread starter MacRumors
- Start date
- Sort by reaction score
You're a very angry person. I'm sorry Jay Cutler hasn't worked out, but there's no reason to take that out on others.
I, personally, will wait until I see some proof on this. But, at least in theory, I've argued all along that it could potentially be a radio software fix. I think people underestimate how much grunt work software does on these phones.
With 4.1 Beta I actually show less reception now. Most of the time I can't even get 4/5 bars. Signal where I live is excellent. Should be full signal all the time. Before the update I would show full signal on the iPhone 4 but when indoors it would drop at times to 1 or 2 bars.
Oh btw what is an a$$? I tried to look it up in the dictionary but I couldn't find anything. Did you and the other "experts" of the English language just define this?
Also, I never claimed not to be a total sarcastic jerk (in fact quite the opposite). What I didn't claim to be is completely informed about something I've never had any experience with. That's really my problem with your little friends. Unfortunately none of them had the expertise after their initial bulletproof statements to stand up for themselves, so your little weak insult had to suffice for all of them. Maybe I was a little to harsh on you because you had to make up for all of their shortcomings. Then again...maybe not.
This reminded me of "as the apple turns", and gave me a pang of nostalgia. Greatest blog ever.
I think people fail to remember, it's just a phone. Is there an antenna issue? Yes! Today Apple will either announce a fix, or they wont, recall it, or wont, offer a free bumper or wont, or offer money/giftcard or they wont. The fact of the matter is everyone is still within their 30 day return policy, and if you aren't happy with however Apple chooses to remedy the situation you can return your phone, get a refund, and go buy another brand. No one is forcing you to keep the iPhone, and hell, if you love it that much, just get a case, or bumper and go on with your life. People are acting like its the end of the world.....really, its juts a cell phone.
I'm pretty sure I hit the mark. Not only that, I am pretty sure you are a substandard programmer at best. Because the really good programmers have nothing to prove - they don't have the need to play Mr. Know-It-All in a macrumors forum.
D
Denbowski
Guest
Software has been fixing hardware problems since the second day that we had software.
History Lesson:
In the very early '80s, Digital began to see VAX-11/780 systems crashing with a pagefault in memory that was locked down as non-pageable. Not common, but definitely a problem - people get very pissed off when a VMS system crashes.
Eventually we found a customer that was getting this crash very frequently (a couple of times a week). Analysis of the crashes showed nothing wrong - the page was resident. The hardware had no problems - tested fine.
The engineering teams came to the conclusion that the pagefault exception triggered by the hardware was spurious and false.
The software fix was to put a check in the PGFLIPLHI exception logic to check to see if the page was resident. If so, then ignore the pagefault exception and continue. If not resident, then crash.
Problem fixed in software, the only cost being that a real PGFLIPLHI crash took about two microseconds longer....
Another hardware problem occurred on an entire line of early MicroVAX systems. Memory refresh (RAM loses its state if not periodically refreshed) would fail to happen if a bank (256 KiB to a MiB) of memory wasn't touched in several seconds. All kinds of mayhem would ensure when a big chunk of memory would zero itself.
The *software fix* was to put a loop in one of the operating system's periodic housekeeping routines to read one byte of each bank of memory.
Eventually we found a customer that was getting this crash very frequently (a couple of times a week). Analysis of the crashes showed nothing wrong - the page was resident. The hardware had no problems - tested fine.
The engineering teams came to the conclusion that the pagefault exception triggered by the hardware was spurious and false.
The software fix was to put a check in the PGFLIPLHI exception logic to check to see if the page was resident. If so, then ignore the pagefault exception and continue. If not resident, then crash.
Problem fixed in software, the only cost being that a real PGFLIPLHI crash took about two microseconds longer....
Another hardware problem occurred on an entire line of early MicroVAX systems. Memory refresh (RAM loses its state if not periodically refreshed) would fail to happen if a bank (256 KiB to a MiB) of memory wasn't touched in several seconds. All kinds of mayhem would ensure when a big chunk of memory would zero itself.
The *software fix* was to put a loop in one of the operating system's periodic housekeeping routines to read one byte of each bank of memory.
So, to defend Apple, if they can modify the software so that the "death grip" attenuation is no worse than other cell phones (like the 3GS), then I would call it fixed in software.
Even if it takes a coating on the antenna plus software changes, that's fixed without a full redesign.
The VAX case is also interesting - in that the hardware bug had been present for several years, but hadn't been noticed. It didn't appear on the radar until operating system upgrades changed something in the timing or the way memory was used.
Software has been fixing hardware problems since the second day that we had software.
History Lesson:
In the very early '80s, Digital began to see VAX-11/780 systems crashing with a pagefault in memory that was locked down as non-pageable. Not common, but definitely a problem - people get very pissed off when a VMS system crashes.
Eventually we found a customer that was getting this crash very frequently (a couple of times a week). Analysis of the crashes showed nothing wrong - the page was resident. The hardware had no problems - tested fine.
The engineering teams came to the conclusion that the pagefault exception triggered by the hardware was spurious and false.
The software fix was to put a check in the PGFLIPLHI exception logic to check to see if the page was resident. If so, then ignore the pagefault exception and continue. If not resident, then crash.
Problem fixed in software, the only cost being that a real PGFLIPLHI crash took about two microseconds longer....
Another hardware problem occurred on an entire line of early MicroVAX systems. Memory refresh (RAM loses its state if not periodically refreshed) would fail to happen if a bank (around a MiB) of memory wasn't touched in several seconds. All kinds of mayhem would ensure when a MiB of memory would zero itself.
The *software fix* was to put a loop in one of the operating system's periodic housekeeping routines to read one byte of each bank of memory.
So, to defend Apple, if they can modify the software so that the "death grip" attenuation is no worse than other cell phones (like the 3GS), then I would call it fixed in software.
Even if it takes a coating on the antenna plus software changes, that's fixed without a full redesign.
The VAX case is also interesting - in that the hardware bug had been present for several years, but hadn't been noticed. It didn't appear on the radar until operating system upgrades changed something in the timing or the way memory was used.
Could I have a source on that?
It looks like it could be a good source for my final essay. (On a topic slightly related)
Well good luck with your life. Hopefully you become a criminal defense lawyer when you get old enough to formulate an argument. All the idiots out there could surely use your help. If you were a little more observant you'd see that all my posts were to people who claimed to "know-it-all" in macrumors forums. I'm ultimately not surprised at your lack of observatory skills.
I didn't ask for the job, it's a civic duty. Besides, weren't you the one who showed up to "police" me for being an "a$$"?
Software has been fixing hardware problems since the second day that we had software.
History Lesson:
In the very early '80s, Digital began to see VAX-11/780 systems crashing with a pagefault in memory that was locked down as non-pageable. Not common, but definitely a problem - people get very pissed off when a VMS system crashes.
Eventually we found a customer that was getting this crash very frequently (a couple of times a week). Analysis of the crashes showed nothing wrong - the page was resident. The hardware had no problems - tested fine.
The engineering teams came to the conclusion that the pagefault exception triggered by the hardware was spurious and false.
The software fix was to put a check in the PGFLIPLHI exception logic to check to see if the page was resident. If so, then ignore the pagefault exception and continue. If not resident, then crash.
Problem fixed in software, the only cost being that a real PGFLIPLHI crash took about two microseconds longer....
Another hardware problem occurred on an entire line of early MicroVAX systems. Memory refresh (RAM loses its state if not periodically refreshed) if a bank (several MiB) of memory wasn't touched in several seconds. All kinds of mayhem would ensure when a few MiB of memory would zero itself.
The *software fix* was to put a loop in one of the operating system's periodic housekeeping routines to read one byte of each bank of memory.
So, to defend Apple, if they can modify the software so that the "death grip" attenuation is no worse than other cell phones (like the 3GS), then I would call it fixed in software.
Even if it takes a coating on the antenna plus software changes, that's fixed without a full redesign.
GTFO, someone with experience in an industry backing up statements with knowledge and facts?
AidenShaw that may be true and all but remember this is a HARDWARE ISSUE, because all the tenured Ph.D wielding signal engineers w/ low post counts and suspiciously recent join dates said so.
Apple fixed the algorithm that displays signal strength to a new one that AT&T specified.
You have the same signal strength as before. Apple did modify the scale and how it show.
There is some other topic about this in this forum, look for it.
you have 3 bars, but the same signal strength.
Did you lose a lot of calls? Were you ever able to stand in one location and not make a call while another ATT customer could? Was your ability to make a call dependent on how you held the phone? Or was it simply a number of bars issue that bothered you?
Even BBC News is covering the fact that "Jobs is making a statement of the problem riddled iPhone 4" with the 'expert' speculating that "Apple are good at telling people things but not so good when it comes to listening" ... and that this event has not helped its reputation any.
So .... best of luck to ol' Stevie .. you know when the UK makes this piddling wee story a major one ... that this event ... IS of major importance to Apple - because even if Mr. Jobs doesn't think it is of consequence ... most do ...
His best bet is to start the conference with an apology for misunderstanding and any inconvenience caused.
Explain that this reception problem is purely :
Hype
Software related
Hardware related
All three ....
Either way he has to provide acknowledgement.
Provide a solution.
Proof that the solution works.
If a recall is required then it must be swift and easy to do.
If a recall is not required ... it wouldnt do any harm to give a wee 'discount for yer hassle' at Apple Stores ... even if Apple aren't really at fault.
No matter what route they take ...it HAS to be succinct, concise and clear ... because if folks get ANY whiff of wobbliness or prevaricating ... the Apple brand WILL lose its reputation for reliablity and efficiency.
The fan base wont budge ... even iPod users wont raise much of an eyebrow... its the potential buyers out there that have to be reassured.
Er.. thats it ....
Cheers!
What we do know is however Steve does this conference he will have to make sure he 'holds it the right way' ....zzzzzzzz
So .... best of luck to ol' Stevie .. you know when the UK makes this piddling wee story a major one ... that this event ... IS of major importance to Apple - because even if Mr. Jobs doesn't think it is of consequence ... most do ...
His best bet is to start the conference with an apology for misunderstanding and any inconvenience caused.
Explain that this reception problem is purely :
Hype
Software related
Hardware related
All three ....
Either way he has to provide acknowledgement.
Provide a solution.
Proof that the solution works.
If a recall is required then it must be swift and easy to do.
If a recall is not required ... it wouldnt do any harm to give a wee 'discount for yer hassle' at Apple Stores ... even if Apple aren't really at fault.
No matter what route they take ...it HAS to be succinct, concise and clear ... because if folks get ANY whiff of wobbliness or prevaricating ... the Apple brand WILL lose its reputation for reliablity and efficiency.
The fan base wont budge ... even iPod users wont raise much of an eyebrow... its the potential buyers out there that have to be reassured.
Er.. thats it ....
Cheers!
What we do know is however Steve does this conference he will have to make sure he 'holds it the right way' ....zzzzzzzz
Software has been fixing hardware problems since the second day that we had software.
History Lesson:
In the very early '80s, Digital began to see VAX-11/780 systems crashing with a pagefault in memory that was locked down as non-pageable. Not common, but definitely a problem - people get very pissed off when a VMS system crashes.
Eventually we found a customer that was getting this crash very frequently (a couple of times a week). Analysis of the crashes showed nothing wrong - the page was resident. The hardware had no problems - tested fine.
The engineering teams came to the conclusion that the pagefault exception triggered by the hardware was spurious and false.
The software fix was to put a check in the PGFLIPLHI exception logic to check to see if the page was resident. If so, then ignore the pagefault exception and continue. If not resident, then crash.
Problem fixed in software, the only cost being that a real PGFLIPLHI crash took about two microseconds longer....
Another hardware problem occurred on an entire line of early MicroVAX systems. Memory refresh (RAM loses its state if not periodically refreshed) would fail to happen if a bank (256 KiB to a MiB) of memory wasn't touched in several seconds. All kinds of mayhem would ensure when a big chunk of memory would zero itself.
The *software fix* was to put a loop in one of the operating system's periodic housekeeping routines to read one byte of each bank of memory.
So, to defend Apple, if they can modify the software so that the "death grip" attenuation is no worse than other cell phones (like the 3GS), then I would call it fixed in software.
Even if it takes a coating on the antenna plus software changes, that's fixed without a full redesign.
The VAX case is also interesting - in that the hardware bug had been present for several years, but hadn't been noticed. It didn't appear on the radar until operating system upgrades changed something in the timing or the way memory was used.
Rockin the VAX! We still got a few sitting around. Still running OpenVMS on Alpha too.