-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Android Question 4.4 kitkat no longer work applications using the magnetic sensor !!!
- Thread starter Spectre
- Start date
- Similar Threads Similar Threads
Try this example: http://www.b4x.com/android/forum/threads/orientation-and-accelerometer.6647/
Does it work for you?
Which version of B4A are you using?
Does it work for you?
Which version of B4A are you using?
Upvote
0
Hi,
Hope this could help : I already had such issue while using initialize2 (nothing returned by the sensor). Solved by initializing with the initialize only.
Hope this could help : I already had such issue while using initialize2 (nothing returned by the sensor). Solved by initializing with the initialize only.
Upvote
0
I'm getting this too. All of my apps that use Magnetics 'fail' on KitKat. Am using B4A 3.8.
I am working on debugging my easiest app first to try and suss out what's going on. My initial search points to weird readings from the Sub Sensor_SensorChanged (Values() As Float) although I could be wrong. I will update this thread as I discover more
I am working on debugging my easiest app first to try and suss out what's going on. My initial search points to weird readings from the Sub Sensor_SensorChanged (Values() As Float) although I could be wrong. I will update this thread as I discover more
Upvote
0
Ignoring my own Apps for a minute. I've retried the Sensor Example project on my new phone running 4.4.3.
The magnetics sensor reports back, X=0,Y=0,Z=-1,541,952,432,780,780,000,000 regardless of actual real changes in magnetic strength.
This is the same issue that appears to be tripping up my own app.
EDIT: I am using Phone v2.25 if this makes any difference..
The magnetics sensor reports back, X=0,Y=0,Z=-1,541,952,432,780,780,000,000 regardless of actual real changes in magnetic strength.
This is the same issue that appears to be tripping up my own app.
EDIT: I am using Phone v2.25 if this makes any difference..
Last edited:
Upvote
0
And just for clarity, all the other readings update fine, it's just the Magnetics values that are frozen with those values you see on the screenshot.
Let me know if you require any more information
Attachments
Last edited:
Upvote
0
Probably related to this Android bug: https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=62876
I tested it with Nexus 4 running Android 4.4.4 and didn't encounter this issue.
I tested it with Nexus 4 running Android 4.4.4 and didn't encounter this issue.
Upvote
0
I think my issue may be something else and/or related to the 4.4.3 bug you higlighted as I've found that all compass based apps fail so it looks to be a non B4A issue. Just incase anyone else finds their way here I'm now discussing this over at http://forums.androidcentral.com/htc-one-m8/400898-htc-one-m8-gps-compass-sky-map.html as it's a more relevant.
Upvote
0
I wonder if this has anything to do with the bug I had on my phone? The compass would always point exactly 90 degrees from where I was facing, no matter how many times I calibrated it. Using 4.3, but maybe a software fix was broken when upgrading to 4.4? My problem was fixed using this method.
I would add one step to the link above, Step 2.5) if the keyboard pops up, press back to dismiss it.
I would add one step to the link above, Step 2.5) if the keyboard pops up, press back to dismiss it.
Upvote
0