Related
Yesterday I dropped my Touch HD. I was sitting down, and it was in the pouch, so I thought there wasn't any damage done. The phone seemed to work like it should. However this morning I noticed that in Opera my screen wouldn't rotate. So I tried different programs like the HTC Album, and the G-Sensor calibration. Neither of those give any sign of life, GSen doesn't work either.
I did a soft-reset, I don't want to hard-reset just now...
I didn't find anything using the search but did anyone else have (or hear of) this problem? Can I assume my G-Sensor is dead? I have warranty so its not that big of a deal, but still...
http://forum.xda-developers.com/showthread.php?t=457985&highlight=sensor
give it a good shake, might be that the part that moves in the gsensor could have gotten stuck
Thanks for the link Juggler (wonder why I couldn't find it), however the solutions there didn't help me. I tried altering the settings in Advance Config Tool like in the other topic, but its still not working (didn't think it was a software problem anyway, but I'll try everything that might help...).
I tried shaking, tapping, and hitting the phone as hard as i dared to (don't want to brake it even more ), with no success.
The people in the other topic also had one of the bubbles in the calibration tool stuck to the left, hitting it on that side got the sensor unstuck. However both of my bubbles in the calibration tool remain dead center, so it looks like the phone isn't receiving any input from the accelerometer at all Its either broken or disconnected then.
I guess I'll have to send it back, unless anyone here has a miracle solution?
The problem seems to be solved... I have hit the phone a lot harder then I dared to do last time, en it's working again
I think it's a strange weakness though, my previous phones have had much more to endure, so I hope this is not a sign for the durability of the Touch HD in general... Especially since I'm not the only one with this problem.
Anyway, problem solved. Thanks for the help!
I think this might be useful to the people who recently bought their DHD or interested in getting one.
These are the issues that I think came up so far:
Bluetooth headset disconnect/reconnect Happen during call and someone else call in
- Solved??
More detail http://forum.xda-developers.com/showthread.php?t=834983
http://forum.xda-developers.com/showthread.php?t=837945
Possible solution: http://forum.xda-developers.com/showpost.php?p=10545249&postcount=32
Android process draining battery after OTA 1.72.405.3
- Solved
solution: http://forum.xda-developers.com/showpost.php?p=10196741&postcount=81
DHD Random Turning Off
- Solved by making sure SIM card is completely inserted into it’s socket
For more information, visit this thread.
http://forum.xda-developers.com/showthread.php?t=854060
com.htc.bgp force close
- Solved
How: http://forum.xda-developers.com/showpost.php?p=6566178&postcount=7
Proximity Sensor Issue
- FIXED via OTA? or faulty first batch?
I don't see anyone complaining about this anymore
LAG ISSUE (/INIT process)
- SOLVED by turning on USB Debugging
For more information, look at the first post in the pinned thread.
http://forum.xda-developers.com/showthread.php?t=826507
BUMP (GAP) between SIM cover and body
- SOLVED by putting the cover in properly as manual suggest.
More information at http://forum.xda-developers.com/showthread.php?p=8979423
FLIMSY plastic SIM cover break in half
- SOLVED by removing the sim cover properly with care. (apply pressure in the middle not along the sides) The manual also suggest this.
Loose Camera Lens/Bezel
- FIXED?? Faulty first batch??
(not everyone have this issue, you probably should get a replacement)
more info http://forum.xda-developers.com/showthread.php?t=813276
Reduced or loss of GSM/3G/WiFi signal when your hand covers the SIM/MicroSD and/or battery cap
- Not really an issue this is due to the antenna being on the plastic covers
(not a big problem if you hold the phone normally on the aluminium body)
Or have a phone cover on (solution like the Iphone4)
Misalignment of Camera Lens
- not an issue
the camera worked fine, no one report shadows from the misalignment. (the outer lens cover is just for protection)
More info http://forum.xda-developers.com/showthread.php?t=827665&page=3 (post #25,26 by HacKage)
Compatibility Issue with Exchange 2010
- Fixed
More info http://forum.xda-developers.com/showthread.php?t=797733&page=3
DHD starts and only shows triangles
- SolvedIssue happens while flashing 1.15 test rom (With S-OFF)
http://forum.xda-developers.com/showthread.php?t=835595
Jerky video recording 720p -Improved after OTA 1.72.405.3-
- Fixed by formating the SD card with 32k cluster size
More info: http://forum.xda-developers.com/showthread.php?t=830822&page=3
Solution2: http://forum.xda-developers.com/showpost.php?p=9666261&postcount=60
Low external speaker
- Fixed Improved after OTA 1.72.405.3
Poor picture quality (camera)
- software
Tips: http://forum.xda-developers.com/showthread.php?t=860008
Nice guide: http://forum.xda-developers.com/showthread.php?t=875230
htcsence.com not working
- Not Fixed/Fixed working fine for most people
More info http://forum.xda-developers.com/showthread.php?t=817833&page=8
Notification LED not working properly
- software related (not many people is complaining about this, not sure if it's fixed)
more info http://forum.xda-developers.com/showthread.php?t=820889
Poor Battery Life
- Subjective
- Interesting Tip (might/might not work) http://forum.xda-developers.com/showpost.php?p=9153120&postcount=294
- Try the /INIT fix too, could improve battery life
Reboot Problem
- Hardware? (not sure)
more info: http://forum.xda-developers.com/showthread.php?t=821117
SMS Notification Issue -after OTA 1.72.405.3-
- Software issue
more info: http://forum.xda-developers.com/showthread.php?t=887098
Inaccurate Compass
- Hardward/Software issue
more info: http://forum.xda-developers.com/showthread.php?t=873865
Random SMS disappearing
- htcsense.com related?? a few people reported this. Not sure of the cause yet.
http://forum.xda-developers.com/showthread.php?t=840582
DLNA not working properly?
- recent issue
more info http://forum.xda-developers.com/showthread.php?t=831755
Dust under Screen
- Hardware Faulty DHD?
You should probably try to get a replacement for this.
more info http://forum.xda-developers.com/showthread.php?t=819263&highlight=dust
Overall Internal Hardware Misalignment (Cover/ Camera/ Screen)
- Hardware Faulty DHD??
You should probably try to get a replacement for this.
More detail http://forum.xda-developers.com/showpost.php?p=9120419&postcount=24
If I am missing something, please tell me (or PM me) so I will update the list.
Also, I might be wrong on some of the things, so tell me so I can change the info.
I want this topic to be a compilation of issues that are common to the DHD. Please do not post asking about little issues that you might have or new issue you stumble upon.
However, if I am missing some big issues or the status of the issue has changed, post it or PM me with the link to the thread discussing the problem.
The exaggerated, sluggish auto-brightness when recording video is an issue. Watch any of the sample videos on YouTube.
HTCsense.com issues not fixed
In Denmark, there are still problems with HTCsense.com - I mess with it to check stability and MANY times I can not connect to my phone to call it, and the SMS service takes a LONG time to react. Also, I have not yet succeeded in remotely locking the phone.
in the very first batch there was (there still is on mine) a problem where i can not use wifi it turns it self off automatically after saying "Unable to scan for networks"
ill try and grab you some debug logs so you guys are more familiar with the problem.
Internal noisereduction is too strong and it makes all photos look like they are waterpaintings, it should be a quick and easy fix for HTC to take care of.
Image sharpening is too strong set at default zero setting, you have to tune it down to get acceptable shots with less sharpening artifacts in them.
Display powerconsumption is ridicously high, it's somthing HTC have to tune in software if possible.
Possibly too strong antialiasing filter contributing to render soft photos.
/ Magnus
HTC Sense is still not working for me...the dashboard doesn't identify my phone's location, the phone does not ring, nor can it be locked or erased. Push messages from the Hub is also not working (HTC Hub via the phone allows me to browse and operate but continues to report that the server is down). The phone number I'm using and related passwords are all correct.
(I'm in Australia).
Im in denmark aswell and have no problems with htcsense.com - perfect sync and responsetime. I had a problem with the updated YouTube app, had the network error many people experienced - but got around it. But after playing a video the hd started lagging like hell.. needed reboot
Sent from my Desire HD using XDA App
I have one to add to the list:
Reduced or loss of GSM/3G/WiFi signal when your hand covers the SIM/MicroSD and/or battery cap.
P.S.
Let's make this list as complete as possible, so we can all point these issues to the HTC customer service.
Will keep an eye on this one!
PLEASE READ THIS: Do not post random issues...PM the OP about your issues and he in return should post a link for the solution or the topic for the issue at hand.
M_T_M
What to do to get 3G?
i set its on GSM only , WCDMA only , auto... romaing on off....
It always goes on Hedge while i have 3G here on my other phone.
thx
nmyseteroious said:
Hey, I think this might be the people who recently bought their DHD or interested in getting one.
After I have extensively reading through almost all the posts in this forum (waiting patiently for my DHD from Handtec). These are the issues that I think came up so far:
Snip, snip
I want this topic to be a compilation of issues that are common to the DHD. Please do not post asking about little issues that you might have or new issue you stumble upon.
However, if I am missing some big issues or the status of the issue has changed, post it or PM me with the link to the thread discussing the problem.
Hopefully, this thread will be pinned so that everyone can see it.
Click to expand...
Click to collapse
I have to thank you for having the courage to do this thread, honestly im tired of the spam fest of doubled threads in this forum just because people dont use the damned search button, every damned time i come here theres 20 more threads with questions that people answered...
I suggest this for sticky!
An issue I am having is:
I will connect my phone to wifi it will connect fine and tell me I am connected.
I could then later on go into the market and try download something I will have wifi bars but the item will pause download. I then come back out to check if my wifi is still connected and it will say authenticating but doesnt change so I then turn the wifi off and back on. It connects again this time when I go back into the market to download something it works fine.
Anyone else have this issue?
funnyclub said:
An issue I am having is:
I will connect my phone to wifi it will connect fine and tell me I am connected.
I could then later on go into the market and try download something I will have wifi bars but the item will pause download. I then come back out to check if my wifi is still connected and it will say authenticating but doesnt change so I then turn the wifi off and back on. It connects again this time when I go back into the market to download something it works fine.
Anyone else have this issue?
Click to expand...
Click to collapse
This is a compilation thread so please post only issues that are recognized and common to many people (providing me with link to the specific thread).
I would suggest you search in the forum whether there is any thread with similar issue. You can try asking it in http://forum.xda-developers.com/showthread.php?t=831804 too.
Sorry man.
I have a link that you can add below the speaker problem:
http://forum.xda-developers.com/showthread.php?p=9119804
This thread contains a comparison video, comparing the N95 vs. Desire HD external speaker quality. Also, a few posts down there I explain my experiences about the comparison.
Also, THE SIM/MicroSD cover issue IS NOT RESOLVED!
Some people had covers that stuck out a bit, but could be solved by attaching the cover properly. However, some people like me have the following problem:
When the hardware got inserted into the aluminum body from the bottom-side, it wasn't inserted far enough, causing the following 3 additional symptoms:
-Gap between top of the screen and aluminum body.
-Gap between SIM/MicroSD cover and aluminum body.
-Camera misalignment - Camera is too low behind the lens.
All these symptoms are caused by the hardware installation process, as it is clear that both gaps are exactly the same (about 0.5-0.7mm). The same counts for the camera, it has the same misalignment in mm's.
To be clear: in my case, the SIM/MicroSD cover gap is caused because the hardware is not pushed far enough into the aluminum body, thus sticking outside too far out of the alu body, and making it impossible to get a proper fit simply because it's physically impossible. It also perfectly explains the gap between the top of the screen and the alu body.
The symptoms clearly all connect to the source of the problem: hardware not inserted far enough into the alu body.
I've made a video for showing the gaps, but it's not perfect. The camera misalignment is only visible if you look closely, because the shade covers the misalignment up.
P.S. Admins PLEASE sticky this thread!
YumYumHD said:
I have a link that you can add below the speaker problem:
http://forum.xda-developers.com/showthread.php?p=9119804
Snip, snip
P.S. Admins PLEASE sticky this thread!
Click to expand...
Click to collapse
Can you get a replacement for that? wanna know because I am suggesting people to get a replacement
nmyseteroious said:
Can you get a replacement for that? wanna know because I am suggesting people to get a replacement
Click to expand...
Click to collapse
I really don't know, I'm in contact with the HTC escalation team about this, but I do hope so.
I'd be interested in any reply you get because I'm noticing the gaps now I'm looking for them and know what to look for. It's irritating because I hate swapping things but if dust gets in it could cause a lot of problems.
nubicurio said:
Hey thanks for taking the time to compile the list! This is exactly what I need to check my DHD against possible hardware issues/problems, and send it back to Amazon for a replacement immediately for faulty hardware, instead of wondering "is it just me..."
Click to expand...
Click to collapse
no problem that's the purpose of the thread anyway. I am bored of seeing people asking for the same thing all the time too.
Not sur eif anyone else is getting this, i've got like 12 bookmarks on the bookmark widget and although it's not too bad, it is quite laggy compared to the rest of the phone when you scroll through them ?
Also i've noticed some small gaps around the phone, theres one around the screen i think where a little bit of dust has got into the cracks but nothing has gone through to the screen as of yet, i've only had it for a little over a week ! not happy with this.
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
Dont know if this helps...but I had my Hd2 screen replaced few months back...and dont have this problem... screen is much better than before though with beter colour saturation....check with HTC as this might be an error on their part..
Sent from my HTC HD2 using XDA App
G-Sensor Not Working after Screen Replacement
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
I have this same problem with one of my HD2's that had the screen replaced.. Everything works perfectly except the "G-Sensor"...
I posted the problem in this thread http://forum.xda-developers.com/showthread.php?t=902129 a while ago, and been watching ever since... Havent seen any solutions, but more reports of the same problem been added to it daily... I'm also assuming that they changed the G-Sensor hardware along with the screen... Beacause it works perfectly in WinMo, and it dont in none of the Android Builds I've tried (CMYLXGOs all versions, Imilka's all versions, RAFDROID, CyanogenMod, etc)...
Everything works good on my Primary HD2, no problems at all... I'm hoping some Chef/Kernel developer might just take some time to check this out...
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
T-Macgnolia said:
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
Click to expand...
Click to collapse
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
cmcmyers said:
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
Click to expand...
Click to collapse
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
T-Macgnolia said:
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
Click to expand...
Click to collapse
It's a good point You have there... But I would be assuming that was the problem if the G-Sensor wasnt working in Windows Mobile... Everything works perfectly in WinMo, including the calibration... Thats another reason we have come to believe its a hardware upgrade or something similar...
I have the same problem. I bought an HD2 from someone in the Marketplace, and I can see from the pry marks on the bezel and the broken adhesive that the screen had been replaced at one point. I also believe there must have been some hardware revision that is still compatible with WinMo, as the same driver works unilaterally, but not with Android. Definitely tried most of the recent ROMs and different combinations of kernels, and cLK/MAGLDR, but it never works.
Charnsingh alludes to the G-Sensor code in the kernel in his [DEV] thread here: http://forum.xda-developers.com/showthread.php?t=1049170 (don't post unless you're a dev though), and says that it's pretty minimalistic. So maybe there's a solution out there, but the developers haven't gotten to the bottom of it. I'm watching that thread intently to see if there's anything cooking or if there's something I can help with.
I think there are quite a few users who are suffering from this.
If the devs need anything they have plenty of people to ask for debug info, etc.
I just wish someone had the time to have a look at this
have got the same issue, new screen, sensors stopped working, all the sensors that is, light, proximity, g-sensor, compass. and everything works in winmo (except the compass, don't know why) the interesting thing is, the proximity sensor does work, it just doesn't turn off the screen, but it does turn off the touch screen, and the g-sensor actually seems to work, i can calibrate, and the relevant files are updated (in /data/misc the bma150_usr and the akmd files are created and/or updated) and if i move during calibration, it is aborted. it seems as if there is something broken in software because the chip data is still being read and used somehow, just not piped to the right places...
Every sensor work fine here with except the g sensor
I guess its a kernel issue and not hardware relates
it work perfectly on wm6.5,but not work on any andriod rom.
i have the same issue
so no one is helping us???
i have the same issue too...
Same here works fine in windows but android will not work.
Also have screen replacement
SOLVED
my issue is solved now after motherboard replacement.
a few notes:
- as i eventually discovered, there was in fact a problem with the compass (aka the magnetic field sensor) which didn't work in any os. with this issue i had a good reason to send the phone back to the repair shop and they replaced the motherboard under warranty.
- i don't know what solved the issue, it's either [A] the working compass (which is somehow needed for auto-rotation to work - in android) or the new motherboard (which does not have compatibility issues with the new screen - in android).
so, please check wheather your compass is working or not.
if not, reflash to stock and send it back for a warranty repair.
I replaced the digitizer in my phone myself and the G-sensor works for me in Android.
LOOOOOOOOOOOOOOOOOOTS of threads and posts since 6 months and still nothing. About those sensors problems / screen replacements and still nothing... It's so sad, the HD2 is dying slowly. Lolz, let's keep the faith!!
+1 same problem...
Any solution???
Thx.
Same.
perfect on Windows.
not working, gyroscope, compass, screen rotation on any android.
no problem with proximity and light sensors.
I had tried screen rotations witout main flex (that holdss, vibration, camera, volume, wifi, buzzer)
And the sad point is I had replaced LCD-Digitizer together these are taken from a dead hd2. So my replaced LCD is 100% orijinal. I did not seperate chasis-button flex also.
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'm sorry if there already is post about this problem, but i couldn't find anything useful so i decided to ask for myself.
The other day i bought a second hand i9505, the problem is that the screen rotates upside down. When i start any app and turn the phone sideways the screen rotates exactly 180 degrees from what it's supposed to be, which is very annoying when watching a youtube clip or taking a photo. The phone was on stock 4.4, at first i thought it was a callibration problem so i installed a stock 4.2.2, but no luck. Then i installed slimrom but still no go, tried different kernels (like 4 or 5) and still nothing.
So my question is is there any way to fix this without taking it to the shop? Like a patch or an app to fix it, and how can i see the values of the gyroscope to see if it is outputting what it's supposed to ?
v41p3r said:
I'm sorry if there already is post about this problem, but i couldn't find anything useful so i decided to ask for myself.
The other day i bought a second hand i9505, the problem is that the screen rotates upside down. When i start any app and turn the phone sideways the screen rotates exactly 180 degrees from what it's supposed to be, which is very annoying when watching a youtube clip or taking a photo. The phone was on stock 4.4, at first i thought it was a callibration problem so i installed a stock 4.2.2, but no luck. Then i installed slimrom but still no go, tried different kernels (like 4 or 5) and still nothing.
So my question is is there any way to fix this without taking it to the shop? Like a patch or an app to fix it, and how can i see the values of the gyroscope to see if it is outputting what it's supposed to ?
Click to expand...
Click to collapse
As you have tried several different ROM's, presumably the error is hardware related. As you bought it as second hand, I'd bet that it was reason of sale (mechanically caused sensor(s) damages are not covered by warranty).
sorry that I could not provide more optimistic assessment.
I figured as much, but thanks anyway. So there is no app to flip the rotation ( invert it so that it is normal ) ?