Hi there people. I need your help.
As you may know the moto 360 sport features a barometer among other sensors.
As I have been playing around and developing an app for that I found out that actually it does not work correctly.
To be more precise it gets one reading and then stops until reboot, or random. This should not work like so.
I have contacted several developers and all agreed that the sensor does not work correctly.
That leads me to think that either it's a huge software bug or Motorola has screwed us for 2nd time (1st is battery capacity)
What I am asking from you is to download AID64 (shows sensor info) and check if it works for you.
It will be working if you change location (eg walk, change location, or move your hand). If it does not change then no.
Thanks in advance.
P.S. Similar thread in G+ moto 360 community
i believe you refer to pressure sensor, it stays at 738.0 hPa, no change after movement
noxaro said:
i believe you refer to pressure sensor, it stays at 738.0 hPa, no change after movement
Click to expand...
Click to collapse
Yes man. I have already opened a case with Motorola.
You can compare it to how it changes if your phone has one.
It's a big ffff bug. I hope is SW.
Related
Is there any way to calibrate the compass ??
Mine seems to mostly point away from where I know north is.
The compass module works a specific way which renders calibration inapplicable.
It basically measures the field strength and direction of the local magnetic field and decides which way is north/south from that field. It's not like a magnet pointing north or south, it's aligning itself with the field direction. Yeh ok that's the same thing kinda, but it also isn't.
You can calibrate a compass by aligning the N and S with the needle when you're out in the open, where you know the compass is aligned with the earth's magnetic field. The compass in the Hero is showing you which way the local magnetic field is aligned, so it's always pointing magnetic north/south regardless of calibration.
I know that sounds vague, sorry. Basically a compass needle always points north/south, regardless of what value you put behind it to indicate north and south. The Hero compass module is the same. It aligns with field direction, and that IS north/south.
If you hold it near to a large metal object which changes the shape of the local magnetic field, you'll notice the Hero gets confused and asks you (in some applications) to wave the handset about until it re-calibrates itself ie. finds a consistent direction/intensity in field strength.
SO... if you are in an area which has a great magnetic variation (where the earth's magnetic field is not aligned with true north/south; here in Edinburgh I think it's about 4 degrees out) then your Hero will never point north. You're in shropshire so aside from local magnetic field anomalies, you may just have a wonky compass module.
Try a different compass apps, some of the others have calibration specific to themselves built in.
@switchbitch - many thanks for the detailed explanation makes sense.
Its does seem to vary a bit so I'll keep an eye on it.
@kiz - I already have a number of apps using the compass so will do a bit of experimenting.
cheers
I had a similar problem. Started looking for a calibration tool for the compass and came accross this video...
http://www.youtube.com/watch?v=sP3d00Hr14o
It shows the iPhone in the video but it worked for my hero. Now Google SkyMap is actually working, befor it kept getting stuck pointing in one direction and was all jacked up. Even compas programs wouldn't point to any N S orientation. So the figure 8 trick works, and it works every time.
P.s. Sorry for the necro, if this has been resolved already, but it was the first thread that came up with a good search HTC Hero Compass Calibration. Hope it helps.
I use the app "Analog Compass" and that one has a calibrate option. I never tried that though, so don't know exactly if it's accurate and actually gives a good callibration. But it's worth a try (free anyway).
But as said before, if you're in an area where there might be magnetic variations it's not gonna help you. The app will merely 'calibrate' the difference between the value it gets from the sensor and what you set as the new north. So let's say north is couple degrees off (or hell, maybe your north points to south) and you calibrate it's no problem. As long as the magnetic thing keeps pointing to the same point. As soon as it's all over the place and keeps changing, calibration obviously won't help you at all.
Switchbitch said:
The compass module works a specific way which renders calibration inapplicable.
Click to expand...
Click to collapse
Yeah, its always wrong. Even Googles skymap is pointing wrong.
Phone: "The moon is there!"
Me: "Eeh, no, the moon is there - 40 degrees to your right"
Since the output is wrong, there should be a way to calibrate it.
p0wd3r said:
I had a similar problem. Started looking for a calibration tool for the compass and came accross this video...
http://www.youtube.com/watch?v=sP3d00Hr14o
Click to expand...
Click to collapse
THANKS
this "8" really helped my hero pointing to north again (instead of east).
for whatever technical reason - it worked
p0wd3r said:
I had a similar problem. Started looking for a calibration tool for the compass and came accross this video...
http://www.youtube.com/watch?v=sP3d00Hr14o
It shows the iPhone in the video but it worked for my hero. Now Google SkyMap is actually working, befor it kept getting stuck pointing in one direction and was all jacked up. Even compas programs wouldn't point to any N S orientation. So the figure 8 trick works, and it works every time.
P.s. Sorry for the necro, if this has been resolved already, but it was the first thread that came up with a good search HTC Hero Compass Calibration. Hope it helps.
Click to expand...
Click to collapse
Thanks. This helped with my Desire. Downloaded analog compass app and calibrated compass this way. Problem solved.
very useful
I had been looking for a way to calibrate my htc desire compass for months now, even deleted all apps but did not help. tried the calibration method in your video and now it works absolutely fine .. thanks a million
thx
krazeeshan said:
I had been looking for a way to calibrate my htc desire compass for months now, even deleted all apps but did not help. tried the calibration method in your video and now it works absolutely fine .. thanks a million
Click to expand...
Click to collapse
thxxxxxxxx its working
hi, some have encountered problems in the calibration of sesnsor G of htc hero? When i put my device in a Flatbed the for calibration the sensor is not completely blown. i can see it when i play with Teester. Thank you.
Dude without being rude I didn't understand a work of that
thenewshaft said:
Dude without being rude I didn't understand a work of that
Click to expand...
Click to collapse
When I do the calibration of sensor G this is not accurate
I haven't found it pinpoint accurate but it does work for me. I use a program called bubble which acts as a spirit level & it seems fairly accurate to myself.
In what program are you finding your inaccuracies?
thenewshaft said:
I haven't found it pinpoint accurate but it does work for me. I use a program called bubble which acts as a spirit level & it seems fairly accurate to myself.
In what program are you finding your inaccuracies?
Click to expand...
Click to collapse
in the Teeter game. It comes with the phone as default. The "board" isn't leveled correctly. Just see for yourself; start the game and place the phone on the table and you will see the ball drifting by itself.
Hmmmm... even the game Labyrinth Lite (fråm the Market) the ball is drifting. I thought it was a software problem at first but when to programs behave the same way there is something going on.
Yeah, mines the same.
The bubbles appear to jump at the end of the calibration.
Whats more if I set the phone down on an angle deliberately, then the calibration doesn't correct it's almost as if its just a bit of animation and theres no actual calibration taking place.
On Teeter, the ball rolls towards the hTC logo and to the right hand side but more slowly.
One of the level apps I downloaded suggests it off by 2 degrees.
I'm running updated Orange firmware, but it was the same in the original.
Vince
yups, this is the same case for mine too. if i tilt it until the spirit level is "level", i can see the earpiece end of the phone will be higher than the speaker end.
The cool little app "Bubble" http://www.cyrket.com/package/bz.ktk.bubble has its own calibration. I think there's a fault in the underlying OS not reading the accelerometer correct or something... but it too isn't still when just having it on the table... the bubble is moving slightly...
The screen won't turn when I turn the device on it's side and it won't look in the right part of the sky on google sky map.
Did the update break the sensors?
They were broken already, according to some reports. I hope the next update fixes them--it's really annoying! I thought mine were OK at one point, but, alas, they're not.
hi ,
i am on android 4.1.2 leaked version
i purchased a mobile phone with broken screen and replaced it so it has been falled earlier i dont whether the magnetic sensor was working earlier or not
on android ics the autorotation feature was also not working and in jb it is also not working
before writing this thread i have already looked 50-60 of similar threads havings problems with different sensors and autorotation but didnt got solution anywhere
in *#0*# test under sensor everything is giving reading except magnetic sensor it is saying it needs calibration but where and how i dont know
if the hardware has fault in my phone than any one can please tell me where is magnetic sensor in the motherboard so i could do change it
under the motion>sesitivity in jb there is gyroscope calibration option in which its ball is not moving anywhere while moving the phone on the different axis but it is saying calibrated on putting it on flat surface and saying some file missing if we do calibrtion by putting phone in hands.........
in the application gps status each thing is showing readings only the magnetic field and the centre ball in the middle not moving
so is there is any real solution for this problem.............
irbaaz said:
hi ,
i am on android 4.1.2 leaked version
i purchased a mobile phone with broken screen and replaced it so it has been falled earlier i dont whether the magnetic sensor was working earlier or not
on android ics the autorotation feature was also not working and in jb it is also not working
before writing this thread i have already looked 50-60 of similar threads havings problems with different sensors and autorotation but didnt got solution anywhere
in *#0*# test under sensor everything is giving reading except magnetic sensor it is saying it needs calibration but where and how i dont know
if the hardware has fault in my phone than any one can please tell me where is magnetic sensor in the motherboard so i could do change it
under the motion>sesitivity in jb there is gyroscope calibration option in which its ball is not moving anywhere while moving the phone on the different axis but it is saying calibrated on putting it on flat surface and saying some file missing if we do calibrtion by putting phone in hands.........
in the application gps status each thing is showing readings only the magnetic field and the centre ball in the middle not moving
so is there is any real solution for this problem.............
Click to expand...
Click to collapse
To ur last statement:
It seems like it's not working any longer, that's why the "ball" while calibration don't move.
After a few seconds it says calibrated because that it set the actual position as default.
That's why while a normal calibration u lay the phone on a table or kind of it - next time the point is in the middle of this position.
Hope this makes a bit clear why it seems to be defect.
Because changing anything in hardware, I can't give any reply, sorry.
CHEERS
Sent from my GT-I9100 using xda premium
Hannibal226 said:
To ur last statement:
It seems like it's not working any longer, that's why the "ball" while calibration don't move.
After a few seconds it says calibrated because that it set the actual position as default.
That's why while a normal calibration u lay the phone on a table or kind of it - next time the point is in the middle of this position.
Hope this makes a bit clear why it seems to be defect.
Because changing anything in hardware, I can't give any reply, sorry.
CHEERS
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
didnt get exactly
is hardware defect according to you????????????
irbaaz said:
didnt get exactly
is hardware defect according to you????????????
Click to expand...
Click to collapse
Yep for me it seems to be a hardware defect.
U just try to point out why
But anyway I can't help u then, sorry.
CHEERS
Sent from my GT-I9100 using xda premium
if any one has repair solution for this than please let me know because i had visited the samsung service center and they are saying its motion ic has to change and the charges are 30$
so i am looking for a cheap way to sort it
hallo everybody
i've bought a BV6000 (firm ver 20160713 chip MT6755 (Helio P10)) but the proximity sensor is very weak, i've asked on official forum for calibrating\change threshold, but no one have published my question.
now my idea:
on engineering mode i've found ps calibrating tool but nothing happens after calibration and reboot; the default threshold is set to 40 (less than 1cm) and if i could set to 5 or less the range arrive to about 3 cm.
is some days that i try all solutions founded on the web but no one works...
now someone have some skills in calibrating the sensonsor manually? i've also tried with DHD Proximity Recalibrator but give me a kernel error.
maybe edit some files in /sys/devices/als/subsystem/drivers/als_ps is the solution?
any other idea?
thank you!!!
xposed and the module: http://repo.xposed.info/module/com.mrchandler.disableprox
I have an MTK and it kept hanging up when I brought the phone close to my face, so I had to disable it completely.
yeah i've tried this module but is a bit too invasive and need a tasker profile to turn off screen on call, i would remap the threshold (if is possible!)
/sys/devices/als/subsystem/drivers/als_ps there are many files:
a "config" file with
(3 200 0 0 50)
a "status" file with
CUST: 1, (-1 0)
REGS: DF C1 00 06 00
MISC: 0 0
what makes me angry is the farest PS sensibility from engineering mode! (hardware testing>sensor>light/proximity> PS calibration) if only is possible to manually reduce threshold!!
engineering mode ps calibration...
UP! i attach two photos of the engineering mode that show the lower threshold.. but after calibration nothing happens...
I put 4 times complete analysis of proximity sensor issue on Blackview forum. Every time, they delete my post.
None of the calibration would help.
The only solution is to replace one rubber part from phone. More details here:
thank you
at now i have do a tasker scene that block upper buttons and an "immersive mode" shell during call (show up when call+phone app is on screen and hide if not).
is a patchy solution but it works
maybe if i have some other hardware problem i'll try to open the phone
bye!
Could you upload a video of your solution? How did you reach the rubber part?
Thank you!
I could not upload video, because I did not recorded the process, but I will try to describe this process.
Video comparing working BV6000 and broken BV6000 proximity sensors:
https://www.youtube.com/watch?v=s8NYcs-Yo5E
Go to service mode *#9646633* and select
Hardware-->Sensor-->Light/Priximity Sensor-->PS Calibration
If your BV6000 acts like the right yellow model, then you are affected with this issue.
Root cause:
Proximity sensor is good. Rubber part covering sensor is really poor quality and it has a gap just above sensor causing light leaks.
PS reading 0-80 are considered as "far". Phone cannot get proximity readings >100 which are considered as "near", so the phone does not dim the screen at all. This is causing a lot of unwanted touch screens while making a call. If the proximity readings were possible in full range 0-255, then the threshold settings 40-100 would be perfect. This issue cannot be fixed by any calibration.
On my working, green BV6000, this rubber part has a bit different shape and it is made with much softer rubber. The edge which is covering sensor is also much tighter than on the yellow one.
Workaround:
Disassemble the phone, like on video here:
https://www.youtube.com/watch?v=9yLEemeXFnY
You do not need to disassemble the whole phone. Just get to the part, when you can detach main board.
Then turn upside down this rubber part covering proximity sensor. It is not meant to be mounted this way, but it will fit. Basically the part which was close to the screen should go close to sensor. This will make gap between rubber and PS sensor smaller and there will be just tiny light leak. It will not make full proximity range 0-255, but it will improve a lot.
On my phone proximity range expanded from 0-80 to 0-200 after this mod. Phone will dim the screen while making a call, if you head is 1cm above sensor. On working phone 0-255 it dims screen in 2-3cm range.
The only 100% solution:
New working rubber part to be sent to all affected users.
Shame on Blackview, that they not only deleting my posts about this issue on their forum, but also reporting my posts, when I put this analysis somewhere on well known Android forums. This is like they want to cover a problem and not resolve it like they did with faulty OTG boards.
thanks for the brilliant hardware workaround, but if i want to change the values showed in this app
i've seen many phones with different resolution\max range (higher than 1cm!)
how i can edit this values without MTK engineer tool (tried but dont do nothing for this issue)?
thanks to all
PS. BV6000 is a good phone for the price, but this issue is really annoing!
PPS. BV6000 have adups fota search online and be paranoized!
I have tried it by placing the rubber above the sensor both ways but it still doesn't work. Whenever I make a call the screen remains responsive and many apps open up or settings mess up every time. There is no end to it.
Please help. I'm really annoyed with this issue.
Sent from my BV6000 using XDA Free mobile app