Related
Well, there are already a couple of applications out there already, but i was playing with the SDK and just trying some stuff out in visual studio so i thought, why dont i just release it?
Its a first release, it does work, has some basic calibration and im trying to make a bit more visually appealing that just some bars
So,
version 0.2:
- Updated graphics of the "Circle" compass/meter. Now actually looks like a compass thingy
- Added the ability to actually save the calibration data, and to let you know its doing something and its done.
- Created an CAB Installer to install the addon.
- Made all pictures internal resources.
version 0.1:
shows an Water level for the X and Y Axis, an circle "meter" and an light meter. There arent any big bugs that i know off, but i didnt implement the "maximal" meter bars yet. That means the measure bars can go a bit beyond the container
Requirements:
You do need the Compact framework 2.0, it will (unfortunatly) not work without it! But seeing as everyone already has the lightsaber application i guess its not that much of an issue
Other:
If anyone has some suggestions or comments (bad or good..) just let me know..
Source:
I added the source code if anyone is interested. Its not some good code, and the calibration could be alot more detailed, but perhaps it helps someone
Oh, and if anyone reflects the application and starts to rant about how my code sucks, i didnt optimize it or plan ahead, i just started to code some
1. congrats and keep the good work! it is refreshing to see a newbie that brings something to the forum and don't start with a wining post.
2. i really hope you'll receive only positive feed back (not so common here ) and allow me to be the first one to say: no, i don't think yr code sucks
3. is the calibration function working?
4. can you explain what "lumens" are doing here. lumens is an international measure unit for light. are u trying to use the internal light sensor to measure the light? this could be a good idea and i'll be very interested.
Lumens is the light sensor =)
Awesome app, calibration works perfectly and saves the setting ok and that light sensor is a nice addon.
Would love to see this made into a .cab installation and perhaps make this app work with the AppToDate program for easy updates.
Look forward to future updates
This is going in my favourite apps
Ignore my double post
awesome it is! great app.
explain please what is with light measuring pls....only measuring or calibrating the automatic light level also?
thanks!!!
No, it measures the amount of light the light sensor receives. I will eventually add an cab installer, but seeing as its still in the "works" i am not bothering with it yet
The calibration works, its not as awesome as the BubbleLevel one yet. When you press the button let the diamond lay there for 3 seconds, and then it calibrates. I wont update the backlight.
The light sensor only shows the value, it doesnt update the backlight it self. I tried doing that, but i can only turn the backlight on very bright, very dim and off. Not somewhere in between
Calibration
Nice app! I like the light sensor also, i finally found out where the light sensor really is
It calibrates fine but does it actually saves it somewhere? the moment i close the app and start Teeter, still not calibrated.
So far non of the apps around here were able (for me) to save the calibration. Some people mentioned success though and since I have tried by now all available roms and on none the calibration works, i get this idea that there are several versions of the sensor (hardware) around...
Anyhow, good to see a new app like this and success with it!
No, the calibration it not saved yet, i will add that soon. The problem with the calibration data is that its reset on reboot. The only tool that i know of comes from a different telephone (Raphael or something) and does save the calibration. But not all roms work with this.
So the calibration from almost all applications will only work on the application itself
Wow, thats the best waterlevel prog here around! Nice graphics, but still very simple. And the lights measurment is very nice too!
Very good work! Thanks!
icon maybe?
I updated te first post with version 0.2. I added some more graphics (lightmeter still had to be done ) an saving of the calibration data for this app only.
@ KukurikU:
Well, i created a simple icon. I tend to like simple stuff that easily identifies a software app..
i put my diamond on a real level meter, bring the level meter to 0,0,0 and pressed "calibrate" and now i can use my diamond as a level meter.....until next reset..
Thanks Wiebbe, nice little app. Will be very useful with my missile launcher!
Accuracy is a little off, well a lot off, on vertical measurements, try to get it to read 90 degrees, could this be an issue with the G sensor itself?
uniqueboy said:
Accuracy is a little off, well a lot off, on vertical measurements, try to get it to read 90 degrees, could this be an issue with the G sensor itself?
Click to expand...
Click to collapse
hard to tell who is to blame. look at the experiment/calibrate method described in my previous post.
i found my diamond to be "off" by 1.4-2 degrees (am i lucky or what?!) and after calibration 0,0 it stayed this way after playing with it quite a bit.
edit: sorry, my bad, now i get it...you r right, on vertical about 7 degrees off... getting 97-96 degrees.
Well, its not that the accuracy is really off. The SDK returns a certain value and its kinda hard to precisely convert it
Ill see what i can do, working on a different way to calculate the angle now.
edit:
Its odd, when i place the diamond vertically against a flat surface (whick should be 90 degrees) the build in Angle says 98 (from the raw data) my calculated one says 92. so its hard to decide which one is correct
After some more testing, it seems that all other applications have the same "error". Bubblelevel says 97 degrees as well when i place it against an 90 degree angle object. Same goes for SpiritLevel. I made a new way to calculate it which seems to be more "accurate" with the angles. But it still wont be 100%! Well, the number of degrees isnt 100% accurate, the bar it self ofcourse does work properly!
Does the output from the G sensor give X,Y,Z or just X,Y ? That coul be a problem when measuring the vertical. If it's just X,Y then maybe when tipped past a certain threshold an error message should be given, or even an audible warning.
The SDK in rawdata form gives back the following:
Angle for X
Angle for Y
Tilt value for Y
Tilt value for X
Tilt value for Z
The angle values are really in degrees, the same as SpiritLevel. They output around the same values as i output.
The tilt values are something from 0 till 1000+, you can see these in BubbleLevel as well at the calibration. I used the angles before, but these arent very correct.
Ill see if i can get myself a watermeter and an setting where i create an real 90 degrees setting so i can calculate a bit what the real values should be
It could be my house is like 97 degrees sloping, but i doubt that ^^
dont forget that an angle of 97 is possible if you tilt it above the 90 degrees value..
I too live on a hill.
Hey guys , i need some help here..
I dropped my Jasjam in the water , and now i've got a lot of problems :
1 - My Keyboard backlight sensor ain't working anymore , the keyboard is lit all time , this is really annoying and eating my battery , a fix , software , anything ?
2 - The Keyboard keys r going crazy , ex. when i press v it writes dv , when i press e it writes eg , when i press "space" it writes "c " , this is very annoying too coz i can't use it to write and i hate touch writing.
Both r hardware probs , i know , but maybe there is a software fix or something for the first prob.
Is there a way around prob 2 without opening the phone coz i can't do that , is there a way i can dry the water beneath the keys or something
BTW : i've tried hardreset , different roms , keyboard layout , etc. nothing worked.
Help Plzzzzz
I hope, you took the battery out as soon as it was possible...
Take it out again, and let it dry for a couple of days. It's still wet inside.
You might also use a hairdryer, but carefully, don't fry it!
If this doesn't help, you'll have to go to a store equipped with an ultrasonic cleaner.
Sorry mate but you'll really want to open that phone, especially the plastic cover.
You just need to find a torx screw driver with sizes between 1-5 [I forgot the specific ones you'll need] and a tiny frearson screw driver [that the + shaped hole].
Considering the age of the TyTN, it's probably no longer under warranty anyway.
Air drying without opening it can take months, seriously
Thanks all ,
Sadly , i didn't remove the battery at all.
I don't know if it's still wet , i mean the phone is working fine just the keyboard light and crazy keys problem.
Sadly too , i can't seem to find this screwdriver here in Egypt
And yes of course , the warranty is no more.
I may try the hairdryer , hope it works...
BTW : what plastic cover do u mean ??
Again thnx 4 help guys ...
medo_punsher said:
Hey guys , i need some help here..
I dropped my Jasjam in the water , and now i've got a lot of problems :
1 - My Keyboard backlight sensor ain't working anymore , the keyboard is lit all time , this is really annoying and eating my battery , a fix , software , anything ?
2 - The Keyboard keys r going crazy , ex. when i press v it writes dv , when i press e it writes eg , when i press "space" it writes "c " , this is very annoying too coz i can't use it to write and i hate touch writing.
Both r hardware probs , i know , but maybe there is a software fix or something for the first prob.
Is there a way around prob 2 without opening the phone coz i can't do that , is there a way i can dry the water beneath the keys or something
BTW : i've tried hardreset , different roms , keyboard layout , etc. nothing worked.
Help Plzzzzz
Click to expand...
Click to collapse
Ive fixed a few "wet" phones (even my own old tytn 1 that fell into a river) by turning it of as soon as possible, take everything apart(stylus, battery,sd-card etc) shake as until all visible water is gone and put it all into a bowl of rice. that has fixed 2 phones, the other 4(inluding my tytn 1) i had to disassamble totally(unscrew,take apart housing,disconnecting flatcables and so on) and then put all parts into a kitchentowel and then onto a plate and into my kitchenown on about 60 degrees celsius for few hours - assemble and voila =) truth be told, it dosnt always work but i just might.
good luck
another way
remove your battery ASAP
Electric + water = corrosion
when this happened to me with mp3 player, I put it in the car for 3 days.
when parking in the outside, The car gets to 50-60 degree inside (Even more)
if your phone is in the car, it will dry, no damage will happen to it.
Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
I have the same issue.
pub00515 said:
Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
Click to expand...
Click to collapse
I tested it on my sgs2 with maps and I don't seem to have the issues that you are experiencing. I even downloaded STLView and did not have this "instability" problem. Perhaps your handset is faulty?
Another possible reason is that you might have been trying to use your sgs2 in the bermuda triangle. It has been documented that the bermuda triangle wrecks havoc on electronics.
Are you sure maps use gyro ? I guess they use primarily compass and G-sensor, while of course, gyros can help too.
Did you try to calibrate the gyro sensor?
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
pub00515 said:
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
Click to expand...
Click to collapse
Yeap, tried it in landscape and tilted it up and down and it seems to move only up and down only.
If the device is in a case/cover which has Magnetic Lock then the issue is normal.
issue is NOT gyro related, what's described here is unstable accelerometer and/or compass readout. i guess it's mainly due to missing magnetic calibration (try to do the "8" pattern with the phone, AND turn the phone twice around each axis). if the problem persists, than it's maybe within technological limits (and everyone faces it, although the people here are more upset about it). also possible is magnetic interference due to huge amounts metal etc...
Yes .. people often confuse accelerometer (G-sensor), electronic gyroscopes, and compass. All do different things, but all can be used in applications like maps.
I also noticed that the magnetometer of my s2 is kind of imprecise.
I have continuously swinging head indication, of about +/- 15 degrees. Moreover, the correspondance from phone orientation and indication is not linear. I get higher sensitivity towards one direction and lower towards the opposite direction...
However what I did notice, is that the magnetometer, responsible for the compass, is very sensitive not only to nearby magnets, but even to metal objects at considerable distance. So perhaps it is all just this sensor beind a tad too sensitive.
Sent from my GT-I9100 using XDA App
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Yes, there definitely must be something wrong with the gyro and/or the magnetometer.
Some time ago I opened a specific thread on this subject in this forum, got many "reads" but no replies whatsoever...
So strange nobody did actually notice it so far.
pub00515 said:
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Click to expand...
Click to collapse
Now that's interesting. Could be !
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Btw. it's common that that electronic compasses are much more sensitive to metal objects, that's not Samsung's mistake. But the sensors should not be linked.
Edit: I downloaded some sensors monitoring application. And gyroscopic sensor itself for sure is not sensitive to magnetic fields and works as it should, same for accelerometer. But then there are some IMHO virtual sensors: linear acceleration and rotation. They seem to be synthesized from more sensors, and the rotation does react on magnet.
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Dr.Sid said:
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Click to expand...
Click to collapse
Mine does the same. Actually I can get even 15 degrees deviation. I noticed that it seems to depend on the location I am, despite apparently there should be no magnetic objects nearby. I am pretty sure that if if you try rotaring your phone at constant angular speed in the horizontal plane (with it horizontal on a table for instance) with a "compass" app running you will notice that the indicaton on the screen speeds up considerably when the phone is pointing to the north, and slows down when is pointing to the south.
Which Gingerbread version are you guys running?
I'm still waiting for the 2.3.4 update.
It would be interesting if someone could try this with 2.3.4, perhaps it works with the update?
Thanks...
Mark
pub00515 said:
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Click to expand...
Click to collapse
hi mark,
again, what you (we) experience here has nothing, i repeat nothing, to do with the GYRO. what you mean is the accelero- and magnetometer! a gyro knows nothing about it's current position (it only detects deviations, read about a coriolis vibratory gyro for more details about the mems gyro the sgs2 is using)
most programs i know are not using the gyro for positional information, for example google maps, google sky... they are all using the magnetometer in combination with the accelerometer ONLY!
regards,
markus
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
pub00515 said:
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
Click to expand...
Click to collapse
hi mark,
sorry - i didn't meant to be rude...
nor did i know your background; the thing nowadays is, a hell lot of people are talking technical nonsense all the time, which is quite frustrating...
i have to admit as i'm no software developer i didn't know the thing with the rotation_vector, what's sure for me was that the actual situation is caused from the accel/mag sensor, simply because of its behavior. that it would be way better to use the gyro as well for all this applications is absolutely true.
so let's hope either samsung or google will provide a fix, as you said!
glück ab, gut land!
markus
I've just started with Android apps and having a tiny little device like this Flipout, the most obvious first app for me to try was a compass.
I tried several of the free ones, all of which worked fine on my Desire Z, but were 'screwy' at best on the Flipout.
Supposedly, the Flipout has Accelerometer, Altimeter, Digital Compass and GPS sensors, yet the compass apps not only are strangely oriented but plain don't work - They don't point North and even away from all possible interference sources just jump around.
Are Flipouts normally just screwy, or is there something I can do to fix this issue?
Thanks,
Dylan.
Also now finding the tilt mechanism is reversed, ie left & right functions only happen when I tilt the device forward and back.
Can anyone please help with this?
DylanKeyne said:
Also now finding the tilt mechanism is reversed, ie left & right functions only happen when I tilt the device forard and back.
Can anyone please help with this?
Click to expand...
Click to collapse
The sensors appear to be screwed up because the default orientation of the flipout/charm is landscape whereas most other phones have portrait mode as default orientation. Hence most applications are built for portrait orientations.
Hence there although the display might be shown in portrait mode, the sensor values are obtained from the landscape orientation.
Some application detect this issue and assign sensor values appropriately but that only a small minority.
I would suggest that you use a Display Orientation Changer available on Google Play and hence force the application to run in landscape mode.
Regards
HSR
My thanks to you HSR, but alas I have no luck so far.
Are there any particular orientators you'd recommend? I've tried four different orientator apps on all available settings. None have fixed the issue and one just outright crashes.
I'm using Smart Compass and Penguin Skiing as test apps, as I know they work perfectly and precisely on my Desire Z
Is this a hardware issue?
Using the orientators seemed to change not only the screen orientation, but the sensor's as well. In short, it turned everything 90º, rather than just the bits I needed.
DylanKeyne said:
My thanks to you HSR, but alas I have no luck so far.
Are there any particular orientators you'd recommend? I've tried four different orientator apps on all available settings. None have fixed the issue and one just outright crashes.
I'm using Smart Compass and Penguin Skiing as test apps, as I know they work perfectly and precisely on my Desire Z
Is this a hardware issue?
Using the orientators seemed to change not only the screen orientation, but the sensor's as well. In short, it turned everything 90º, rather than just the bits I needed.
Click to expand...
Click to collapse
Hey, try this. it seems to work for me.
http://forum.xda-developers.com/showthread.php?p=28022264&highlight=orient#post28022264
http://forum.xda-developers.com/showpost.php?p=24844428&postcount=953
Nope... :crying:
I've tried that one, both the version here and the one on Google Play.
Tried two more this evening as well. No luck.
Some of them do turn the display but the sensors alter with them, so whichever way the screen is, the compass moves North 90º from where it should be and the game controls are still twisted.
From the links I posted, try the one from the forum and force the display to landscape. Try the free version of doodle jump and check if it alters properly.
Doodle Jump - Este elemento no es compatible con tu dispositivo...
Is there another that is compatible?
Really starting to regret this Flipout - Tried 4 different unlocking shops in town today and none have been successful!
DylanKeyne said:
Doodle Jump - Este elemento no es compatible con tu dispositivo...
Is there another that is compatible?
Really starting to regret this Flipout - Tried 4 different unlocking shops in town today and none have been successful!
Click to expand...
Click to collapse
:s oh, try any motion sensor app which runs only in portrait mode, in forced landscape mode using the app in the 2nd link I posted.
By unlocking you mean carrier unlocking?
I tried several more with the forum orientator you linked to - Same result, I'm afraid.
The screen orients back and forth just fine, but when you change that, the tilt sensor maintains the same crossways alignment.
Sorry, yes I meant Carrier Unlock (Orange UK).
The first 3 shops came back with 8 digit codes of failure. The 4th one got a 16 digit code but it also failed to work. They're trying something else which will take 2-3 days, apparently...
DylanKeyne said:
I tried several more with the forum orientator you linked to - Same result, I'm afraid.
The screen orients back and forth just fine, but when you change that, the tilt sensor maintains the same crossways alignment.
Sorry, yes I meant Carrier Unlock (Orange UK).
The first 3 shops came back with 8 digit codes of failure. The 4th one got a 16 digit code but it also failed to work. They're trying something else which will take 2-3 days, apparently...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1376037
This is for Charm but you could try this for sim unlock.
Regarding orientation issue, have your tried with the keyboard opened and with keyboard closed.
Any difference then?
Sorry that some things I told do not work, its probably because im a moto charm user and the keyboard swivel must be invoked in different ways.
No, no difference with the phone open or closed. Tried that each time I changed something else as well.
Will try that unlock when I get back home, though.
Update - Phone is SIM unlocked. The helpful shop texted through a code that they guaranteed would work, which it clearly did.
No closer to resolving the sensor orientation issue though.
Is it just me being stupid/missing something/having this problem on the Flipout, or does anyone else have it?
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
oriolas said:
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
Click to expand...
Click to collapse
test the sensor on *#0*#
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
oriolas said:
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
Click to expand...
Click to collapse
Hi
recently am facing issues with this s view.
I am not using a s view cover but still the phone shifts to s view suddenly. But only for a second or so and again comes back to normal.
this happens quite often for me when am just holding the phone. Or trying to make a call.this is annoying.
Is my s4 broke.. am worried.
please help me out to solve this
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
The flip view cover contains a magnet which screws with the compass, rendering it useless. If you're using the cover remove it and see if it helps.
krico said:
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
Click to expand...
Click to collapse
Was that answer for me.... please let me know... how to work this out and how does this work
No dude. It was for the person trying to calibrate their compass.
Calibrations doesn't help ...
I've got CM 5.1 + newest GAAPS and calibration of compass last only for few seconds-2/3 minutes tops and then it's gone and compass again showing wrong directions not even restarting Google Maps - (usually 180* degree opposite to the actual direction). Funny thing, when I downgraded to original Orange Kit Kat 4.4.2 compass worked precise so It assured me, that there is not problem with hardware only software. I cannot use: *#0*# because my I9505 says "Problem with the connection or wrong MMI code" (translating from polish).
All other things including GPS, accelerometer and other sensors works perfectly well.
Anybody know the solution?