Well if calibration was savable, why is it necessary to calibrate the existing compass/level every time it's launched?
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.
New Accelerometer Supplier Could Be Causing Incorrect iPhone 5s Level and Compass Measurements
- Thread starter MacRumors
- Start date
- Sort by reaction score
Well if calibration was savable, why is it necessary to calibrate the existing compass/level every time it's launched?
A larger offset equals more resolution. I think the issue is a software one and that the offset values are only going to +/- 20 instead of +/-95.
My 0.02 is that its easily fixed by expanding the range of offsets for the 5S/5C and subsequent hardware revisions that feature this sensor.
The Bosch MA220 offers power consumption savings and is has up to 5 times the sensitivity. the issue now is that the software must be using -20 to 20 instead of -95 to 95 during calibration (which should be when the offsets are recorded), which is why we are consistently seeing 3-4 degree variances.
Cheers
Chris
My 0.02 is that its easily fixed by expanding the range of offsets for the 5S/5C and subsequent hardware revisions that feature this sensor.
The Bosch MA220 offers power consumption savings and is has up to 5 times the sensitivity. the issue now is that the software must be using -20 to 20 instead of -95 to 95 during calibration (which should be when the offsets are recorded), which is why we are consistently seeing 3-4 degree variances.
Cheers
Chris
HAHAHAHa, apple have quality control ? good one....
Isnt apples quality control just Johnny Ive saying, "sure looks pretty, release it, the idiots will buy it and we can fix it down the road if they shout loud enough"
That's the artificial horizon, which is better than the actual horizon.
You're horizoning wrong.
Who said Apple is about no match quality. Now, you know what quality is all about in apple today. Apple is falling.
this.... This is all really silly. The accelerometer works fine. None of you were using the level to begin with, now your'e mad because something you never use, doesn't work they way you thought it would....if you ever used it in the first place?
I use it to play games and it was quite a nuisance with my 4 degrees off 5S which I returned a couple of days ago for a refund.
If you think games are trivial, check out this guy's case: https://forums.macrumors.com/posts/18139104/
This is an easy software fix.
The BIAS tolerance is at issue. That relates to the consistency of what output is given by the chip for "0" from chip to chip.
Before it was a 1 degree variance and so they made a single calibration at apple to be used for all phones since the worst deviation would be 1 degree at level.
Now it can be 5. They can no longer use a pre-set calibration.
I am betting using the other sensors on-board they can extrapolate what zero is. Worst case a one time user interaction on first run like the other set ups done i.e. Do you want to use iCloud, location services, etc.
They could even have the OS ask a user to calibrate the first time an app using the sensors requests data, like the allow access to camera roll prompt. This method would require no changes by developers.
In any case I have been able to compensate easily in my code, so Apple surely can as well.
The BIAS tolerance is at issue. That relates to the consistency of what output is given by the chip for "0" from chip to chip.
Before it was a 1 degree variance and so they made a single calibration at apple to be used for all phones since the worst deviation would be 1 degree at level.
Now it can be 5. They can no longer use a pre-set calibration.
I am betting using the other sensors on-board they can extrapolate what zero is. Worst case a one time user interaction on first run like the other set ups done i.e. Do you want to use iCloud, location services, etc.
They could even have the OS ask a user to calibrate the first time an app using the sensors requests data, like the allow access to camera roll prompt. This method would require no changes by developers.
In any case I have been able to compensate easily in my code, so Apple surely can as well.
Do you really think it only affects an ability to use the device as a level? Or are you just trolling?
Indeed, it is impossible to accept that no one at Apple saw this issue and reported it, and they decided to launch anyway.
If the average user can find such a blatant and obvious fault (and let's face it, it's not like some obscure setting buried seep in an app, it's an in your face feature, esp given the new chip)
This would of been so easily spotted.
We have to accept the head of Apple got told of this, had meetings talking about this problem and decided to launch.
Any other scenario is simply not possible.
I don't have a 5s but I don't see a setting in the iOS control panel that allows for saving a calibration. For my iPod touch, I calibrated the sensor for that app only. What should be done is that Apple puts the calibration in the control panel and makes the calibration available to all apps using the sensor.
I use accelerometers from Bosch Sensortech in my designs too. Apple probably switched from ST Microelectronics to Bosch Sensortech because the parts are quite a bit smaller.
There is even a much smaller part from Bosch Sensortech that will be available next year. Maybe they will use it the iPhone 6 (my next new phone).
I wasn't aware that the zero offset was that much more than normal. (Luckily my design does a self-calibrate every time I turn it on). It seems like it should be a relatively simple software fix.
There is even a much smaller part from Bosch Sensortech that will be available next year. Maybe they will use it the iPhone 6 (my next new phone).
I wasn't aware that the zero offset was that much more than normal. (Luckily my design does a self-calibrate every time I turn it on). It seems like it should be a relatively simple software fix.
They are certainly more than aware of the problem, and are no doubt working on a permanent and sound solution.
Doable, but not that simple really, given that future components will be 100% accurate (hopefully), and those already built into existing iPhones, may not all have exactly the same deviation.
It's all about secrecy and compartmentalization.
Antennagate happened because every user outside of the lab had to put a camouflage cover over the phone.
It didn't help that Apple employees are discouraged from gathering and talking together about new devices. In some other companies, such problems would've been discovered over cooler talk.
There has to be an opportunity for people to say stuff like, "You know, I kept dropping calls the other day ", and someone else replying, "Hey, me too!". This is how things get found out in real life.
See secrecy above. It's always been Apple's Achilles' heel for things like this.
It's quite possible that the developer themselves never noticed, since they probably used a single unit, perhaps even one that got constantly reset while trying out new code.
I've seen that a million times, where something worked for the developer all day long, and only failed when it got into the hands of more people.
For example, the first iPhone had a problem with the audio being too low in phone calls. This wasn't really noticed until a few hundred people had one for AT&T field trials before it went on sale. In a quiet lab, it was of course okay.
They allow calibrating from time to time. Put the phone on level surface. Tap it. it will calibrate to 0.
currently the calibrated value will be ignored once the compass app is killed. Apple can fix this by store the calibrated value permanently or just leave it as user will need to calibrate the value each time they use the compass (well I'm not sure who is even use this app on daily basis).
For games, ideally they allow to calibrate the position. Let say I'm resting on my bed and playing the games. I don't want the 0 position is same as I'm on standing/sitting position.
I'm interested in upgrading my 4s next month (contract with Verizon ends, switching to T-Mobile) and I'm a little concerned about this. Now, maybe in 4-6 weeks, all new 5s units coming out of the factory will have this fixed. I just know the four display 5s models in the Apple Store which I tested flat on the table were all -1. Now, I didn't expect the table to be level, so the readings appeared to be alright, at least to me. Is there something that I'm missing?
Bear in mind that the iPhone4 antenna was no different 4-6 weeks after launch. Nor was it different when it was still on sale 2.9 years after launch. If there's a fix it will be software.
