Hi
I bought the Note II 2 days ago, and I ended trying Google Street View in compass mode... Nice software...
As probably you know, in this mode the orientation of the handset controls what you see on the screen, offering a better 3d experience than simply sliding your finger on the screen to change the viewpoint (try it: maps --> select a place with street view available --> enter street view mode --> press "menu" left virtual touch --> select compass mode, and play with it!).
This is all nice and well, except that I experience on my phone a serious random jitter (mostly azymuthal) in the street view: a few degrees more or less, not much but enough to make you dizzy after a while. This happens also in Google Skymap.
I tried to recalibrate the gyroscope, also had a look in the hidden "test" menu (dialed *#0*#), and installed marketplace compass apps which offer calibration tools... to no avail. I also changed position in my flat to check for stray magnetic fields effects, but nothing new.
I know there are other devices forum threads where this type of problems is explored (not much as far as i know), the point here is I would like people with Note 2 at hand to check if they experience the same type of problems: I'd like to know if this could be related to a hardware problem, or if it is another screw up by Google/Samsung ...! :silly:
What do you think ?
Same thing here, I've had my T-Mobile GNote2 for just under two weeks and when I tried the compass this am I found the same jitter you describe, using GPS Test app and the diagnostic mode you found. Started a thread in T-Mobile GNote2 here, looks like it wasn't a priority for Samsung.
I'm getting gitter in Street View too. Damn annoying.
Sent from my Galaxy Note 2 using Tapatalk 2
Bad jitter here too .... and this was one of the features that seemed best to try out on the larger screen... Hopefully there will be a software fix. If some people would post that they have no jitter in street view compass mode, then I'd go see if it was just my/some units with the defect and exchange while in my 14 days.
I can confirm the jittering on my Note 2. It's pretty annoying. Calibration hasn't worked for me.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
In other compass apps, I can't experience any jittering. So I think it must be directly related to Street View and how they read/process the values from the compass. Maybe the interpolation is wrong?
Well, I can tell you that I exchanged TWICE my Note II since I posted the problem on the forum (one was exchanged for another reason)... and the jitter was and is here on the three handsets.
The last one I got works marginally better, but the effect is still quite annoying.
mc-garry said:
I can confirm the jittering on my Note 2. It's pretty annoying. Calibration hasn't worked for me.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
In other compass apps, I can't experience any jittering. So I think it must be directly related to Street View and how they read/process the values from the compass. Maybe the interpolation is wrong?
Click to expand...
Click to collapse
I tried a few compass apps. They mostly had the jitter as well... and the *# test menu showed the same jitter back and forth on the compass :=/
Are you all running on stock rom and kernel? So maybe we can isolate the source for the jittering.
Jittery here too... On stock rom/kernal
Sent from my GT-N7100 using Tapatalk 2
Hm, stock rom/kernel...why doesn't Samsung test this stuff before releasing. Now we need to find out, if it's a software failure or a hardware problem. I have tested this compass app and there is no jittering. Can anyone confirm this?
Search for "com.apksoftware.compass" in the play store. Cannot post external links, as I'm quite new.
I have slight jitter in compass mode on street view too.
Stock ROM, no root.
Sent from my Nexus 7 using Tapatalk 2
I've tried several other stock/non-stock roms and kernels. All have the same problem. Has anyone contacted Samsung about this?
mc-garry said:
Hm, stock rom/kernel...why doesn't Samsung test this stuff before releasing. Now we need to find out, if it's a software failure or a hardware problem. I have tested this compass app and there is no jittering. Can anyone confirm this?
Search for "com.apksoftware.compass" in the play store. Cannot post external links, as I'm quite new.
Click to expand...
Click to collapse
That's exactly what I'm saying! I actually called Samsung's main technical services department and the person I spoke to didn't have a clue what I was on about, so I had to describe it to her carefully. And by the way, yes I've tried it on all the available compass apps on the play store and they all have the same issue. To compare, I used my dad's S3, totally fine. This is one of the reasons I bought the phone in the first place, to use the street view in compass mode after seeing it on the S3 but its a total letdown, which leads me to believe that its very likely a hardware issue, and that's what I'm dreading.
Ilker123 said:
That's exactly what I'm saying! I actually called Samsung's main technical services department and the person I spoke to didn't have a clue what I was on about, so I had to describe it to her carefully. And by the way, yes I've tried it on all the available compass apps on the play store and they all have the same issue. To compare, I used my dad's S3, totally fine. This is one of the reasons I bought the phone in the first place, to use the street view in compass mode after seeing it on the S3 but its a total letdown, which leads me to believe that its very likely a hardware issue, and that's what I'm dreading.
Click to expand...
Click to collapse
Maybe it also could be a software problem. I don't think that Samsung includes defect hardware sensors in all of their Note 2 devices (therefor they have extensive hardware tests). I hardly believe they hadn't had the time to write a proper kernel driver with interpolation for the magnetometer. And probably all other kernels base on the kernel sources, Samsung has published. So this could be an inherited problem. Would be interesting if the Note 2 and the S3 share the same magnetometer sensor. Can somebody elaborate on this? If so, then we need to compare the kernel sources for both sensors and try do debug the problem step by step.
mc-garry said:
why doesn't Samsung test this stuff before releasing.
Click to expand...
Click to collapse
they were probably too busy making the rest of the phone as awesome as it is :laugh: ps - im getting the jitter as well
mc-garry said:
Maybe it also could be a software problem. I don't think that Samsung includes defect hardware sensors in all of their Note 2 devices (therefor they have extensive hardware tests). I hardly believe they hadn't had the time to write a proper kernel driver with interpolation for the magnetometer. And probably all other kernels base on the kernel sources, Samsung has published. So this could be an inherited problem. Would be interesting if the Note 2 and the S3 share the same magnetometer sensor. Can somebody elaborate on this? If so, then we need to compare the kernel sources for both sensors and try do debug the problem step by step.
Click to expand...
Click to collapse
So you're telling me this problem may be fixed with either a 4.2 or 5.0 update? One can only wish right now.
Jitter here too. Very annoying. Quite shocked this got past QC.
Tried multiple roms and kennels, always the same.
Well I'm now on stock 4.1.2, and sad to say its the same problem. Absolutely nothing has changed. I think we're stuck with this issue guys, such a shame
it is a big samsung problem. it is on the S3 as well...
I had the same problem. I tried several compass applications from the market and celebrated the compass several times. The only thing that really helped to get the digital compass get stable is to turn off all wireless functions, including the phone, as well as the phone sound and power saving functions. I turned off anything that might produce a megnatic field in the phone, and then calebrated the compass again. Now the compass works fine after turning on everything.
Sent from my GT-N7100 using xda app-developers app
Related
Hey guys wondering all these Rom makers or Google/htc made any multi touch fix?
With all the custom kernels and open source roms, has any developer attempted to fix this issue?
Would like to play games without on screen keyboard issues due to multi touch, this also affects typing fast.
Thanks
Hardware not software please do some research
Thanks. So does the s-lcd have the same issues?
Ronaldo_9 said:
Thanks. So does the s-lcd have the same issues?
Click to expand...
Click to collapse
the type of screen does not make a difference its the bit that lets the phone detect touch that is the issue here.
All HTC devices detect only one touch, and then detect the "size" of that touch which allows it to have pinch zoom when it detects a change in the size.
It cannot detect 2 individual touches.
please delete
bedeabc said:
Wait a minute, the Desire does have a basic multi touch digitiser... pinch to zoom in the browser etc. proves this. The EVO guys have developed a multi touch keyboard fix btw
Click to expand...
Click to collapse
you obviously didn't read what I just posted then.
It cannot touch 2 different touches at one, it detects one LARGE touch when two fingers are on, and then when you "pinch" it detects the size of that LARGE touch getting bugger or smaller.
Search for "Multitouch Visible Test" in the market.
That is an app for displaying the detected finger touches.
Lennyuk said:
you obviously didn't read what I just posted then.
It cannot touch 2 different touches at one, it detects one LARGE touch when two fingers are on, and then when you "pinch" it detects the size of that LARGE touch getting bugger or smaller.
Click to expand...
Click to collapse
the desire dosent have multi touch, but dual touch instead, the issues people are having with games is beacause the desire gets confused When two fingers are placed close to each other or they cross the same axis because the data points get flipped, this is because of the way dual touch works, When you touch the screen with two fingers one by one, you get three points of reference: 1) Fixed Point – location of first finger, 2) Real Point – hardware detection point when two fingers are placed and 3) Fake Point – location of second finger. Interestingly, the hardware does not ‘know’ about this position – instead it is calculated by the application.
Is this translated in a hardware level or just driver?
Lennyuk said:
you obviously didn't read what I just posted then.
Click to expand...
Click to collapse
Both rude and falsely assumed.
I loaded the page a long time before you replied and only saw your reply after I had submitted mine. I edited my post immediately after seeing yours.
bedeabc said:
Both rude and falsely assumed.
I loaded the page a long time before you replied and only saw your reply after I had submitted mine. I edited my post immediately after seeing yours.
Click to expand...
Click to collapse
ok then, sorry
And as mentioned you are wrong, as the desire do detect 2 points/fingers. Any multitouch test app from the market will show that.
mortenmhp said:
And as mentioned you are wrong, as the desire do detect 2 points/fingers. Any multitouch test app from the market will show that.
Click to expand...
Click to collapse
no, what we have said is correct, the apps show an output but its not true multitouch.
All you have to do is try any multitouch app and do a google search to see all deivces up until now (after desire) made by HTC have dual touch, not multitouch
basically speaking it can detect certain multitouch gestures but not everything.
well i can play sonic and a load of other games and snesoid on the genisoid with run and jump buttons together, which tells me it's at least dual touch, to be honest the screen isnt really big enough to get 3 or 4 fingers on it properly and see what you are doing anyway
I will record a video of the hardware limitation of the touchscreen in HTC Desire.
lollylost100 said:
I will record a video of the hardware limitation of the touchscreen in HTC Desire.
Click to expand...
Click to collapse
or just search on youtube, loads have been done already.
I am not on about the lack of multitouch, there is a bug with two points with two near x, or y, axis points; they join together for some strange reason.
Link to video: http://www.youtube.com/watch?v=noQBUDy-WCQ
This is why multitouch keyboards dont work and there are problems with the PSX4droid emulator when having both dpad and control buttons on top or both on bottom.
I read somewhere that there was code in Android for a that filtered the Droid's multitouch results, that results in the Droid not having the axis flipping issue (does still have the sticking issue when close). Is there any way this code can be implemented on the Desire?
I think a developer called Phhusion on the Acer liquid forum in Modaco solved this software wise.
mr.r9 said:
I think a developer called Phhusion on the Acer liquid forum in Modaco solved this software wise.
Click to expand...
Click to collapse
NO...
i am reading the post but... it's a work around... and it is works quite well, quite...
It does not resolve the bug!
Or gyro stabilized camera.
My train of thought might be too naive; (phone has gyroscope, phone has camera, why not!) but really is it something possible to give to our DHDs? A videocamera with which no matter how the phone was rotated, the horizon in the recorded video will always stay horizontal. They got used in MotoGP.
Here's a video example for anyone unfamiliar with them - skip to 40seconds in
motogp.com/en/videos/2010/Rossi+debuts+Gyroscopic+OnBoard+camera
Anyone got any idea? Or maybe I should actuallt ask in general android apps.
It wouldnt be impossible but it would take quite a lot of processing power and would take a lot of time to make. And I'm not sure if anybody has that sort of time.
You sure the phone has a gyroscope? Your not confusing it with the accelerometer are you?
YdLeet said:
Need post count, sorry!
Click to expand...
Click to collapse
And that isn't the correct way to build it either.
Oh ok, thanks a lot. That provided some food for Googling on these things.
Silly marketing got me again; so a g-sensor is actually an accelerometer which is different from a gyroscope and not as accurate at measuring movement (tilt/pitch in specific). DHD has accelerometer only while iPhone 4 and upcoming Sensation are also equipped with a gyroscope (or gyro-sensor).
Hey,
can anyone tell me how to calibrate the G-Sensor in the Gaaxy Nexus Prime? In games and apps using this sensor it seems that the y-axis is about 5 degrees leftside when i hold the smartphone straight up. This means for example that the figure in doodle jump moves slowly left, although the Nexus is holded erect...
Googled for an solution by myself, but nothing helped so far. Even apps like BubbleLevel, which have the calibration tool, calibrate the sensor just for this app... and not in general.
Thanks
Try calibrating with this app and see if it helps.
https://market.android.com/details?id=com.eclipsim.gpsstatus2
Sent from my Galaxy Nexus using XDA App
Ignore everyone telling you to use an app to do it, because you can't. Android has no concept of global calibration regarding the sensors.
I have 3 Android phones, they all have wrong default calibration, from a few degrees (Galaxy Nexus) to about 30 degrees (Xperia X10 Mini Pro.. unusable).
You used to be able to calibrate in gingerbread by modding axis offset values in the AK8973Prms.txt file in data/misc. ICS doesn't seen to have that file, at least not in the same place.
HTC Desire, Desire HD have its calibration app.
zapek666 said:
Ignore everyone telling you to use an app to do it, because you can't. Android has no concept of global calibration regarding the sensors.
I have 3 Android phones, they all have wrong default calibration, from a few degrees (Galaxy Nexus) to about 30 degrees (Xperia X10 Mini Pro.. unusable).
Click to expand...
Click to collapse
He asked for help and I tried to help him with what work for me in the past. No need to tell him to ignore people. It's a simple process that involves rotating the phone on 3 of its axis. If it helps, then great. But it certainly wouldn't hurt for him to try, would it? No need to be condescending; it's not like I'm trying cause him harm.
Sent from my Galaxy Nexus using XDA App
waiaung1 said:
He asked for help and I tried to help him with what work for me in the past. No need to tell him to ignore people. It's a simple process that involves rotating the phone on 3 of its axis. If it helps, then great. But it certainly wouldn't hurt for him to try, would it? No need to be condescending; it's not like I'm trying cause him harm.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I think that method works well for compass calibration for apps like maps and sky, but it is temporary and doesn't seem to affect pitch and roll. GPS status let's you calibrate pitch and roll but only within the app, it doesn't affect system calibration. The file i mentioned above did allow manual system calibration under gingerbread. Not sure how to accomplish under ics. A post i saw suggested that gnex and ics automatically calibrate if you leave the unit to sit alone for a bit. I don't buy it, but that's the only info i have found.
In case anyone is interested in how it was done under gingerbread, see my post at http://forum.xda-developers.com/showthread.php?p=16592139
klobkelosh said:
In case anyone is interested in how it was done under gingerbread, see my post at http://forum.xda-developers.com/showthread.php?p=16592139
Click to expand...
Click to collapse
It's not Gingerbread, it's for that specific sensor with that specific driver. The Galaxy Nexus uses a Bosch BMA250 which has an NV memory where calibration settings can be stored but doing so is not trivial. More information at http://www.bosch-sensortec.com/content/language1/downloads/BST-BMA250-DS002-03.pdf
zapek666 said:
It's not Gingerbread, it's for that specific sensor with that specific driver. The Galaxy Nexus uses a Bosch BMA250 which has an NV memory where calibration settings can be stored but doing so is not trivial. More information at http://www.bosch-sensortec.com/content/language1/downloads/BST-BMA250-DS002-03.pdf
Click to expand...
Click to collapse
Aah good to know. I'll check that out. Thanks
A clip showing how bad the screen banding can get. Just recorded it.
http://www.youtube.com/watch?v=7tJJJzAe0QU&feature=youtu.be
THIS FIXED IT FOR ME, big thanks to - jedi5diah
Attention! I found out that the damn FASTBOOT option is causing a lot of problems esp related to camera and browser screen glitches.
My wife's one X is on fastboot and had a auto reboot and a few force closes and screen glitches started to appear, compared to mine with fastboot off from first day had non of the above mentioned issues.
Go to settings/Power then uncheck fastboot option and restart your phone.
pardon me if this has been mentioned.
That's not banding, banding us when gradients are not smooth. What you see are graphical glitches, these are usually graphics driver issues.
Is it a driver issue? If it is then won't all units be effected? Or some with ealier firmware? I am using 1.26.401 and do not have this problem.
DazzXP said:
Is it a driver issue? If it is then won't all units be effected? Or some with ealier firmware? I am using 1.26.401 and do not have this problem.
Click to expand...
Click to collapse
I don't own a One X (yet) but maybe it's a setting or it depends on the codecs of the movie used. On my SGS2 there is a setting to force 2d hw acceleration under development options, try toggling it
have this issue aswell. comming up sometimes in browser.
ok i watched the video and i can see it's occurring in a specific scenario when the menu drops down
I can safely say it might very well be a kernel problem, most custom GB kernels on the Desire HD had a similar problem when an HD video is played in portrait, only the official kernel worked well but then we had to wait for HTC to give us the source
but why some have it and others don't? despite being on same firmware?
usually a device have different configurations internally, such as two/three different sources for the screen, camera or sensors, there might be a conflict with a specific combination and hence again a kernel problem
or a random Tegra3 related memory leak that needs plugging
third possibility might be a defect somewhere in the device or SOC, but after watching this video i think its unlikely
DazzXP said:
Is it a driver issue? If it is then won't all units be effected? Or some with ealier firmware? I am using 1.26.401 and do not have this problem.
Click to expand...
Click to collapse
I'm pretty sure it's a graphics driver issue. I'm running 1.26.401.2
hamdir said:
ok i watched the video and i can see it's occurring in a specific scenario when the menu drops down
I can safely say it might very well be a kernel problem, most custom GB kernels on the Desire HD had a similar problem when an HD video is played in portrait, only the official kernel worked well but then we had to wait for HTC to give us the source
but why some have it and others don't? despite being on same firmware?
usually a device have different configurations internally, such as two/three different sources for the screen, camera or sensors, there might be a conflict with a specific combination and hence again a kernel problem
or a random Tegra3 related memory leak that needs plugging
third possibility might be a defect somewhere in the device or SOC, but after watching this video i think its unlikely
Click to expand...
Click to collapse
What do you think, could this be kernel problem to.
http://forum.xda-developers.com/showpost.php?p=24475367&postcount=46
I don't know if i should DOA it, you pay hell of money and you get this feeling.
This is a widespread hardware problem not a driver issue. Some samples have it and others don't even though they are on the same software version.
b-george said:
What do you think, could this be kernel problem to.
http://forum.xda-developers.com/showpost.php?p=24475367&postcount=46
I don't know if i should DOA it, you pay hell of money and you get this feeling.
Click to expand...
Click to collapse
yea i already know this one, seems similar to the above, unless the nudging on the screen is physically causing it, can also be graphics acceleration drivers issue
like i said on the Desire HD whenever video acceleration get messed up it shows similar corruption and its all software related, we know T3 accelerates video by NEON in each core and also in the battery saver core, its definitively an NV mess
if nativestranger is correct then HTC have a disaster on their hands, still even hardware issues if figured out can be plugged by software like HTC disabled the 2d core in certain Sensation configurations
I have the same issue, dont know if i should exchange it or just wait for an update... Gonna send this video to HTC.
http://db.tt/uPvJkvYn
Sent from my HTC One X using xda premium
WarheadNOR said:
I have the same issue, dont know if i should exchange it or just wait for an update... Gonna send this video to HTC.
http://db.tt/uPvJkvYn
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i understand how pissed you must be
but yea same, it can be either software or hardware
I have the same problem and i dont know what to do, wait or return?
Is it software or hardware? If its software its np to wait but if its hardware i wanna return it asap :/
Can all one x user try do like this video and see if your get same bug?
https://www.dropbox.com/sh/qigl22ogcciur67/1C17INr6PJ/20120406_160836.mp4
It's very sporadic. I just got the YouTube glitch too, when the video is in HD it glitches like crazy. These glitches also happens in the browser and the notification bar. But sometimes it.dosent look like in the video, it more like "noise" on the screen, but never lasts long enough to get it on camera... So people might.not be able to reproduce it.
Sent from my HTC One X using xda premium
That issue is software related, the video directly above it appears to be a sence UI problem. the one on the main tread i can't replicate even with 2d hardware rendering.
DazzXP said:
That issue is software related, the video directly above it appears to be a sence UI problem. the one on the main tread i can't replicate even with 2d hardware rendering.
Click to expand...
Click to collapse
Nice find, when i change launcher i can't get the bug. Can you other try it to?
Edit: you don't need to change launcher, pull down the status bar when you are in a app that is not sene or htc related.
similar problem
I've had it happen twice in camera mode with the same banding, and once with full screen banding and green blocks... getting a replacement tomorrow
b-george said:
Nice find, when i change launcher i can't get the bug. Can you other try it to?
Edit: you don't need to change launcher, pull down the status bar when you are in a app that is not sene or htc related.
Click to expand...
Click to collapse
can you explain more? did you figure it out?
b-george said:
Nice find, when i change launcher i can't get the bug. Can you other try it to?
Edit: you don't need to change launcher, pull down the status bar when you are in a app that is not sene or htc related.
Click to expand...
Click to collapse
I tried with GOlauncher and i couldnt provoke it to glitch, i fastpressed the notification bar but nothing happend so i guess its a Sense 4.0 problem?
---------- Post added at 12:47 AM ---------- Previous post was at 12:22 AM ----------
Could you try this:
Go into safemode:
1. Press " power key " for power on device
2. Wait until "HTC logo" appears on screen
3. Press and hold " Volume down key " until entering OS
4. " Safe Mode " text will appears on the lower left of screen Safe mode will disable all 3rd party apps and only preinstalled apps will work, this is done because some of 3rd party apps can interfere with your phone functionality.
In safe mode try to fastpress the notification bar couple/plenty times
to try provoke the glitches, i cant provoke them.. In safe mode all 3rd part apps are off, could this problem have to do something with 3rd party apps?
Anyone have this working http://forum.xda-developers.com/showthread.php?t=1965249&page=2
I followed these steps for the camera in this post
http://forum.xda-developers.com/showthread.php?t=1966384
but instead of using adb I just used root explorer, sphere and panorama seems to be working fine for me. And yes I can confirm the keyboard is working just download the apk and install then activate in language and input settings
TheMayor5152 said:
I followed these steps for the camera in this post
http://forum.xda-developers.com/showthread.php?t=1966384
but instead of using adb I just used root explorer, sphere and panorama seems to be working fine for me. And yes I can confirm the keyboard is working just download the apk and install then activate in language and input settings
Click to expand...
Click to collapse
Did you alter build.prop?
I just installed with root explorer as well.. rebooted and have 2 cameras and 2 galleries.. old and new.
It is just very, very, very slow...
Yes I altered my build.prop. but same here, sphere mode is unusable it's so slow but everything else works fine. I wonder why it's so slow. Im gonna try another method.
Tried several different updated and patched versions and nothing seems to work for sphere mode. It takes the first picture and then slowly creeps to the next but that's not how it's supposed to work. Anyone have any ideas how to fix this. I heard that any phone under 1gb of ram can't use it but the M should be ok as it has 1 gb
Ok after reading bad info that told me the Razr M came with a gyroscope I just found out that it does not have one. Photo sphere require a gyro. Sorry Razr M users, no photo sphere for us just yet.
Is there an advantage using the camera app from that build over the razr one?
Sent from my XT907 using Tapatalk 2
I really don't think so, it's short on options as far as effects and shot modes but the gallery makes up for it in it's editing options. I thought the camera shots looked a little worse than stock. I haven't taken too many shots. I'll take more tomorrow and post what I think about the quality in more detail.
---------- Post added at 02:19 AM ---------- Previous post was at 02:17 AM ----------
The only reason I wanted it was for sphere mode, which freakin sweet. look it up on youtube if you haven't already. It's made me want to get a different phone lol. But I love my Razr M and that's just something I can live without for now.
So what S do we need to do to get just the new gallery?
Sent from my XT907 using Tapatalk 2
Does anyone know whether the gyroscope hardware is actually in the phone, and it's a matter of the hardware being disabled via the kernel?
I would try to poke around myself, but I don't have the phone...I'm debating between dev versions of the M and HD. I've read Sphere does work on the HD since the gyroscope is enabled.
Gyroscope
The phone does have the hardware, unsure if the JB update actually has it working though.
http://www.engadget.com/2011/11/08/behind-the-glass-a-detailed-tour-inside-the-motorola-droid-razr/
smstutler said:
The phone does have the hardware, unsure if the JB update actually has it working though.
Click to expand...
Click to collapse
That article isn't for the M
smstutler said:
The phone does have the hardware, unsure if the JB update actually has it working though.
http://www.engadget.com/2011/11/08/behind-the-glass-a-detailed-tour-inside-the-motorola-droid-razr/
Click to expand...
Click to collapse
No it doesn't : http://smartphones.venturebeat.com/compare/161-358/Motorola-DROID-RAZR-vs-Motorola-DROID-RAZR-M
Oops sorry.
Sent from my XT907 using xda premium
I tried elixir 2 to test this. It says gyroscope is not a available. However I don't see the reason why moto would disable this function if it does exist inside the phone. I tried Google earth and star charts and they work fine. I believe the phone uses a combo of accelerater and magnetic sensors to give location. What would be the point of having gyroscope and purposely disable it? Don't moto make its money off RAZR HD and Max HD?
Edit: my bad, I didn't read that article.
Ok so this article review states that this phone has gyroscope.
http://www.theverge.com/products/droid-razr-m/6085
Perhaps maybe they really do have it disabled...