Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple already HAVE officially acknowledged the problem to those customers who contacted them because the issue affects them. Those people have a contact at Apple who has updated them on the status of the issue (see above post). There is no procedure as an upcoming software update will fix this, and there isn't a hard and fast timeline for that. As soon as the fix is written, it is put on a prioritization schedule for release, likely sooner than later given some of the previous comments. Apple has a warehouse full of faulty phones with which to develop and test a fix. They're not likely to test externally before releasing the software update.

----------



They HAVE told people what to expect: a software update that will fix the issue.

This is the DEADEST horse I've ever seen beaten.


Ya!!!! Lets have more threads discussing some REAL ISSUES here people!!!

Like how some people hate the iOS 7 icons. How Apple is doomed due to the lackluster 5s upgrade. Or better yet if a white phone is girly!

/S :rolleyes:

God forbid we discuss a real freaking problem.
 
I know its hard as I have been guilty of it too. But please try to avoid bickering with the non believers or people that feel this is a non issue. Macrumors shut down the original thread due to bickering. Please if you can take it off line, swap phone numbers and discuss it or use PM that would be great. Please don't give them what they want and that is to get the thread closed.

Don't shoot the messenger.
 
Just been on to support again. It's a known fault, apple are looking in to it and a software update will fix this. I should not have been given a replacement for this problem apparently.

Make of that what you will. I am going to retire from this thread now :)

Thanks for sharing

----------

Ya!!!! Lets have more threads discussing some REAL ISSUES here people!!!

Like how some people hate the iOS 7 icons. How Apple is doomed due to the lackluster 5s upgrade. Or better yet if a white phone is girly!

/S :rolleyes:

God forbid we discuss a real freaking problem.

How about we discuss how much we like/don't like the iPhone 6's apparently different sized screen?
 
Anyway, back on topic. If it is fixable through a software upgrade I can't see 7.0.3 being the remedy. More than likely it will be 7.1 which I believe the new iPads minus the motion issues will be loaded with.....
 
Sensorgate

I have read most of the posts on this thread. Yes sad, but I feel really upset that I've got a 5S which is now going back. This is not how Apple want us to feel, and it shouldn't be how we feel.

So here's a summary:

You are probably wasting your time calling Apple. This issue has gained little traction in the press so it will probably not be at the top of the fix list. It's not like Antennagate. It is almost certain that Apple will be aware of the problem.

If you own a 5S and it is outside the 14 day period, there's little point in exchanging your phone. A refurb is not what you have just paid a lot of money for. Wait and see what happens. It is very likely that Apple will correct the problem, possibly sooner than you think.

If you are within the 14 day period, then it make sense to return your phone for a refund. As I said in an earlier post, I can't even check my 5S because I have a 4S sim. If it were to be a hardware issue and you keep the phone, then you'll get a replacement, but it will be a refurb.

I hope this helps anyone who can't decide what to do.
 
Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side). Most other apps (like the iHandy ones) attempt to null out a world rotation, which is why when you calibrate them and then look to the side, the level is wrong again. The disadvantage of my approach is that I can't use the nice sensor fusion/filtering provided by Apple (because I can't tell the beginning of the algorithm to use my calibrations) so I have to merge the gyro/accelerometer myself using my own algorithms.

With my two-step process I can calibrate to an accuracy equal to or greater than an iPhone 5 (with no calibration). It appears to be reasonably consistent such that you could calibrate once and keep that calibration for a while. Ideally, Apple would just build something like what I have straight into their next iOS update, and do a better job at calibration before the phones leave the production lines.
 
born with big boy pants mate. time for you to be mor man than sheep.

If you check my history I was the biggest Android fanboy. I woke up once I realized that Samsung cares more about releasing model after model instead of updating their older phones. Just yesterday they announced a curved phone and this week the Verizon Note 3 is being released with the latest software. Meanwhile my Note 2 and Note 10.1 are 2 software revisions behind. Samsung is sell first and update later. And no telling when the Note 3 will receive 4.4 kitkat. I now consider Samsung to be out of control. And let’s not forget about all the bloat and locked bootloaders you get on a Verizon device.
So the people here complaining about an issue that could be potentially fixed via software or a potential device swap or/in house fix(once the problem has been identified) is peanuts compared to the lack of support after you buy a Samsung flagship. I still love Android and will rank the Nexus 5 over the iPhone 5s but Verizon will not carry it. And I don’t want to root and hack my daily driver anymore; I just want it to just work. We just have to wait for a fix by Apple. The people here are going nuts swapping device after device without official confirmation.
I’m far from a sheep my friend.
 
I know its hard as I have been guilty of it too. But please try to avoid bickering with the non believers or people that feel this is a non issue. Macrumors shut down the original thread due to bickering. Please if you can take it off line, swap phone numbers and discuss it or use PM that would be great. Please don't give them what they want and that is to get the thread closed.

Don't shoot the messenger.

I'm not bickering, but we're at 1200+ posts with people posting the same stuff:

  1. My armchair engineering background qualifies me to share the opinion that it's a software/hardware problem that can/can't be fixed.
  2. When is Apple going to publicly announce the issue and tell us exactly when it's going to be fixed?
  3. I went through 4 phones and they were all bad, so now I hate Apple and am switching to Android.

I'm affected, too. But this thread would be infinitely more helpful and perhaps more widely referenced by legitimate news sources or blogs if it were limited to those who have been in contact with Apple and have real information to share, not just their opinion about what is wrong and why Apple won't say anything publicly.
 
Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side). Most other apps (like the iHandy ones) attempt to null out a world rotation, which is why when you calibrate them and then look to the side, the level is wrong again. The disadvantage of my approach is that I can't use the nice sensor fusion/filtering provided by Apple (because I can't tell the beginning of the algorithm to use my calibrations) so I have to merge the gyro/accelerometer myself using my own algorithms.

With my two-step process I can calibrate to an accuracy equal to or greater than an iPhone 5 (with no calibration). It appears to be reasonably consistent such that you could calibrate once and keep that calibration for a while. Ideally, Apple would just build something like what I have straight into their next iOS update, and do a better job at calibration before the phones leave the production lines.
This is great news! Sounds it can be fixed via software!
 
I'm not bickering, but we're at 1200+ posts with people posting the same stuff:

  1. My armchair engineering background qualifies me to share the opinion that it's a software/hardware problem that can/can't be fixed.
  2. When is Apple going to publicly announce the issue and tell us exactly when it's going to be fixed?
  3. I went through 4 phones and they were all bad, so now I hate Apple and am switching to Android.

I'm affected, too. But this thread would be infinitely more helpful and perhaps more widely referenced by legitimate news sources or blogs if it were limited to those who have been in contact with Apple and have real information to share, not just their opinion about what is wrong and why Apple won't say anything publicly.

Completely agree.
 
Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side). Most other apps (like the iHandy ones) attempt to null out a world rotation, which is why when you calibrate them and then look to the side, the level is wrong again. The disadvantage of my approach is that I can't use the nice sensor fusion/filtering provided by Apple (because I can't tell the beginning of the algorithm to use my calibrations) so I have to merge the gyro/accelerometer myself using my own algorithms.

With my two-step process I can calibrate to an accuracy equal to or greater than an iPhone 5 (with no calibration). It appears to be reasonably consistent such that you could calibrate once and keep that calibration for a while. Ideally, Apple would just build something like what I have straight into their next iOS update, and do a better job at calibration before the phones leave the production lines.

Finally, some sense, after two or three pages of mostly off-topic discussions...
I, for one, am very grateful of your insight. Thanks for sharing.
 
How do you know it's a refurb and not new? Was it unmarked with stickers on?

It was in a small white box which I then had to put my original in to send back. Have no idea if it's a 'refurb' or not.

I assumed they don't have refurbs available yet but assumption is a dangerous this :)
 
Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side). Most other apps (like the iHandy ones) attempt to null out a world rotation, which is why when you calibrate them and then look to the side, the level is wrong again. The disadvantage of my approach is that I can't use the nice sensor fusion/filtering provided by Apple (because I can't tell the beginning of the algorithm to use my calibrations) so I have to merge the gyro/accelerometer myself using my own algorithms.

With my two-step process I can calibrate to an accuracy equal to or greater than an iPhone 5 (with no calibration). It appears to be reasonably consistent such that you could calibrate once and keep that calibration for a while. Ideally, Apple would just build something like what I have straight into their next iOS update, and do a better job at calibration before the phones leave the production lines.

So its like a software driver to bypass the hardware (M7?), which should provide accurate readings if were calibrated properly? So the CPU just retake the workload from the M7? What if Apple decides to 'build...straight into...update'? Does it mean that a major part of M7 will become useless, even if future 5s are properly calibrated?
 
So its like a software driver to bypass the hardware (M7?), which should provide accurate readings if were calibrated properly? So the CPU just retake the workload from the M7? What if Apple decides to 'build...straight into...update'? Does it mean that a major part of M7 will become useless, even if future 5s are properly calibrated?

Kind of, it's not clear where some of the more advanced filtering happens anyway, whether it's on the M7 or the A7. It's not a huge computational cost either way, the primary advantage of the M7 is to be able to record motion data while the rest of the A7 is turned off, additionally the M7 records things like large scale motion and steps taken, where this advanced filtering isn't needed. The M7 is just another ARM processor anyway, so if the filtering was happening on the M7, I'd assume they could still update it.
 
Many have been told it's a hardware problem and been given replacements. The point of Apple issuing a statement is
  1. Officially acknowledge the problem
  2. Clear up any discrepancies arising from previous statements
  3. Outline the likely procedure and timetable for a fix
  4. Receive feedback from the user base to help develop and test a fix

I've been told a couple of times by an Apple Supervisor that they're working on it and that it seems like a software issue. They will not make a statement because it will make things worse for them but better for us. If it can't get fixed by a software release, they'll have a silent recall and all those people that don't use the compass/level or play gyro games will never know that an issue exist. And that will result in Apple having to replace fewer devices.
 
I originally reported this issue to tcook and got an email and phone call from one of his Corporate Executive Relations people in Cuppertino. He originally wanted me to exchange the device and set up and exchange in the store for me. I let him know that all the ones in the store had the issue and decided not to swap. I emailed him today for a follow up if he has any more info on the issue being hardware or software. He called me back directly and said at this point hang on to the phone and keep the software up to date. I told him I would take it as a hint and he said you should always keep your software up to date.

Based on other posts I have seen on here with correspondence with Apple I am leaning very much towards a software update. Im not expecting it in 7.0.3 as they may have not had time to get it in but it sure wold be nice.
 
How was the figure of 8 thing supposed to work? Is there any reasoning behind it except being a nicer way of saying wave the phone all over the place to hopefully get a decent average?

You're pretty close. The reason for calibrating by turning in a circle or waving in a figure 8, is that in a perfect world, the readings would form a perfect circle or sphere.

In real life, of course, there are internal deviations due to speakers, circuit traces, radios, etc. This deviation needs to be figured out on a per-device basis, although model tests can come up with a general baseline to start from.

compass_calibration.png

As someone who's had his own share of wacky bugs, I'd love to know what caused this one.

As I said before, it could be a unit conversion error, or a communications error between the M7 and A7 ( 32 bit variable vs. 64 bit variable?), or perhaps a code mistake using the default model calibration constants instead of individual calibration values.

Often code works in the lab because the developer uses one device, which is reset quite often. Errors don't show up until you begin mass field testing, which in this case obviously failed to notice the problem.
 
Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side). Most other apps (like the iHandy ones) attempt to null out a world rotation, which is why when you calibrate them and then look to the side, the level is wrong again. The disadvantage of my approach is that I can't use the nice sensor fusion/filtering provided by Apple (because I can't tell the beginning of the algorithm to use my calibrations) so I have to merge the gyro/accelerometer myself using my own algorithms.

With my two-step process I can calibrate to an accuracy equal to or greater than an iPhone 5 (with no calibration). It appears to be reasonably consistent such that you could calibrate once and keep that calibration for a while. Ideally, Apple would just build something like what I have straight into their next iOS update, and do a better job at calibration before the phones leave the production lines.

As a fellow developer, I said as much in this thread a couple days ago.

Most here just want to argue, and your information will just be forgotten/ignored shortly.

Meantime you and I enjoy a stress free wait for the OS update that will address the issue.

FWIW - I'm able to deal with the sensor data issue easily in my code including the startup jump from the sensors on launch.
 
You're pretty close. The reason for calibrating by turning in a circle or waving in a figure 8, is that in a perfect world, the readings would form a perfect circle or sphere.

In real life, of course, there are internal deviations due to speakers, circuit traces, radios, etc. This deviation needs to be figured out on a per-device basis, although model tests can come up with a general baseline to start from.

View attachment 439867

As someone who's had his own share of wacky bugs, I'd love to know what caused this one.

As I said before, it could be a unit conversion error, or a communications error between the M7 and A7 ( 32 bit variable vs. 64 bit variable?), or perhaps a code mistake using the default model calibration constants instead of individual calibration values.

Often code works in the lab because the developer uses one device, which is reset quite often. Errors don't show up until you begin mass field testing, which in this case obviously failed to notice the problem.

My only concern is, why is this issue shows different readings for different phones.

1. If it was code bug, all phones should show the same numeric "off" reading. Also, 4s does not have this issue on iOS 7.
2. If it was 64-bit only then why 5c are showing the same behavior.

This kind of concludes that it is specific to each phone (newer ones) and could point to HW or assembly issue (w.r.t the M7 positioning etc?).

May be I am wrong.
 
iPhone 5s accelerometer/gyroscope/compass values incorrect

Hi guys,

I'm a developer of apps that use the gyro/accelerometer/compass, so this issue is very important to us. I've managed to successfully calibrate away the problem using a two-step process that calculates and then nulls out the zero-g offsets (a calibration flat on the phone's back and then on the phones side).

I doubt this calibration method would work on my phone as I have different offset values for each side of the phone in addition to the back.

If I put my phone with the home button on the bottom in the level app and tap the screen and the rotate is 90 degrees clockwise so the home button is on the left, the display reads 85 degrees. It's not accurately determining the rotation.

As such it would need 5 separate calibrations.
 
Last edited:
My only concern is, why is this issue shows different readings for different phones.

1. If it was code bug, all phones should show the same numeric "off" reading. Also, 4s does not have this issue on iOS 7.
2. If it was 64-bit only then why 5c are showing the same behavior.

This kind of concludes that it is specific to each phone (newer ones) and could point to HW or assembly issue (w.r.t the M7 positioning etc?).

May be I am wrong.

He explained why it's different on different phones. Deviations due to model (layout) and tolerances (assembly and manufacture of device and chips.)
 
If it was hardware, wouldn't all the 5s's show the same reading or at least the ones from the same batch?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.