Related
Hello everybody,
I noticed on my hero that applications using g-sensor have some problems:
Skymaps draws the horizon line sloping down from the left to the right.
Teeter game, when I put the phone on a surface (leveled of course) the balls goes to the left and slightly to the top of the screen (teeter is played in horizontal way).
I tried to calibrate the g-sensor but when I do this, the bubbles finish at the same position as at the begining of the calibration. It doesn't keep the calibration data even if I lean the phone consciusly to set the inclination as the leveled one.
Can you help me on this?
Have you noticed this behaviour on your game, skypmap and calibration tool?
Yeah, I've noticed the same thing with my Hero, I have too look slightly down to get the horizon in the middle of the screen in Streetview. I too tried to calibrate the g-sensors, but with no luck. In teeter the ball end up in the top right corner when the phone is laying on the floor..
same here
Thanks for your reply. I'm asking the problem to htc customer service.
They have answered me to try to restore the factory values, I've already tried this but no luck.
I've reported it, so I am waiting their answer.
Same here.
Hi,
from HTC Customer Service has no notification about anyone who has reported the bad behavior of the G-sensors and the imposibility of saving calibration.
So, they told me to ask to the shop for a replacement.
I hope an update appears soon.
I've noticed the very same thing. Skymap horizon sloping, 'bubbles' not centering when calibrating the G-sensor, pointing down to look straight in Street View.
They told you to send yours back? Interesting...
keycoh said:
Hello everybody,
I noticed on my hero that applications using g-sensor have some problems:
Skymaps draws the horizon line sloping down from the left to the right.
Have you noticed this behaviour on your game, skypmap and calibration tool?
Click to expand...
Click to collapse
The Skymap thingie is very easily explained. The earth is actually tilting in angle relative to the sun so what you are seeaing is perfectly normal. We aren't any vikings anymore so we do not believe everything revolves around our earth... you gotta remember that what you are seeing is NOT the horizon... it's the universes "equator" you see...
I have the same problem. I don't a replacement would solve this because i think it's a design fault.
Same problem here, when calibrating it looks like it's going to be OK and then it kicks back to what it was before starting calib. Sounds like a SW fault....
Yes, same here. Contacting support.
So, I hard-resetted the device and re-calibrated it according to HTC Support instructions, but the problem persists. Then I got a number where to call, and I did, and the friendly lady said that she hadn't never (personally) heard about this issue on HTC Hero. I kindly asked her to run a search on their tickets (but don't know the outcome of that).
She instructed me to go back to the shop and replace it with a new unit. I will do that, but I did mention her that there are other people with this same issue and I don't think that it is my unit that is faulty.
I'll let you know if the new unit has the same issue. I'd be surprised if it didn't.
Thiesen said:
The Skymap thingie is very easily explained. The earth is actually tilting in angle relative to the sun so what you are seeaing is perfectly normal. We aren't any vikings anymore so we do not believe everything revolves around our earth... you gotta remember that what you are seeing is NOT the horizon... it's the universes "equator" you see...
Click to expand...
Click to collapse
It is meant to be the horizon, which should be flat. You're thinking of the ecliptic plane which is tilted about 23 degrees relative to the earth's celestial equator; this is visible in the sky map app as 0 degrees on the gridlines that show altitude and azimuth on the celestial sphere.
The yellow line representing earth's horizon should be completely flat when the phone is held in portrait. It slopes on mine aswell.
i also notices this calibration issue, i've tried sensordebug, so sensor is ok, also tried Bubble app, calibration works perfectly there. problem must be in permissions, but i don't know which file is responsible for storing accelerometer data.
maybe, solution could be reflashing hero with its stock rom. or wait for rom update
EDIT: Do you have stock ROM or root and/or modified one ? This information could be useful
Carabei said:
maybe, solution could be reflashing hero with its stock rom. or wait for rom update
EDIT: Do you have stock ROM or root and/or modified one ? This information could be useful
Click to expand...
Click to collapse
I have 100% stock ROM, no rooting or anything.
Me too, i've found almost same problem with htc and accelerometer, with WM device, solution was software fix. also it happend only on some devices, not many of them, i don't know certain number of these problems with hero, but it could be normal fault when flashing ROM after device completion, like with Dream devices there was akmd_set.txt file responsible for accelerometer and compass settings data.
5 minutes ago, i flashed hero with stock ROM, nothing changed.
I have this same problem with htc diamond..!!!
solution for diamond you can find there: http://www.htc.com/au/SupportDownload.aspx?p_id=133&cat=0&dl_id=372
Carabei said:
solution for diamond you can find there: http://www.htc.com/au/SupportDownload.aspx?p_id=133&cat=0&dl_id=372
Click to expand...
Click to collapse
Already tried it. Didn't work
I have problems to use the compass in google skymap and street view. It is completely crazy.... although, it seems to be working well at compass apk for example. Can anyone help me?
Thanks
Ronan
Sent from my XT910 using xda premium
I have this issue too. The compass sensor is fine but its the other sensors that are screwy in my opinion. I've tried recalibrating with no success.
if you place your phone horizontally and just change the azimuth error, Google Maps appears to work with a heading bias. If you move in the others directions, it becomes totally crazy!
At GPS status, with no GPS tracking, the phone's attitude is correctly predicted by compass and accelerometer, so, it is a problem with the way google apps obtain the cell phone body attitude... Let's hope that Motorola fix the API or google adapt their apps to avoid it.
Thanks,
Ronan
my phone is the same.
google map is a little off, but any (i tried 3) compass app is completely out of whack and inaccurate.
what? i need to calculate the feng shui of my new apartment!
although using it as GPS works fine though...
this is a known issue - sky map has been open sourced - I hope google finds it in their corporate heart to squish the bug
The latest Verizon update completely fixes this issue.
I'm on 6.12.173, and I still have the issue...
I was on .173 and still had the problem with apps that want to use the compass including some GPS apps, as well as Sky Map. Called Verizon, convinced them to send a new phone, now running identical software and everything is fine. I am rooted, but not a single problem in any app with compass.
This is a problem on countless phones regardless of manufacturer. Getting them to replace your RAZR won't fix it.
dparm said:
This is a problem on countless phones regardless of manufacturer. Getting them to replace your RAZR won't fix it.
Click to expand...
Click to collapse
Well I am sorry but you are incorrect. My replacement Razr works just fine utilizing the compass. I have tested it on a Compass App, Google Sky, GPS Test App, GPS Status App, as well as Gogle Maps and Star Chart where none of these worked previously. In addition, my grandson as a non rooted Razr, and his compass has worked from day one out of the box.
Now I agree, it is just on some devices, but just let them know, insist on a replacement and hopefully the replacement will not the the problem.
BobC43 said:
Well I am sorry but you are incorrect. My replacement Razr works just fine utilizing the compass. I have tested it on a Compass App, Google Sky, GPS Test App, GPS Status App, as well as Gogle Maps and Star Chart where none of these worked previously. In addition, my grandson as a non rooted Razr, and his compass has worked from day one out of the box.
Now I agree, it is just on some devices, but just let them know, insist on a replacement and hopefully the replacement will not the the problem.
Click to expand...
Click to collapse
i'll have to try that... though I don't know if it will have to go through Verizon Corporate or if a local store can handle it.
But in any case, the compass app I have doesn't deviate from North, and I'm unrooted on the OTA (not copied online) 6.12.173.
traumadog said:
i'll have to try that... though I don't know if it will have to go through Verizon Corporate or if a local store can handle it.
But in any case, the compass app I have doesn't deviate from North, and I'm unrooted on the OTA (not copied online) 6.12.173.
Click to expand...
Click to collapse
I had to go through Verizon to get the exchange. Had it to me the next day and love it as that was my only glitch.
This happened on my old phone as well as my razr. It's annoying, but easy to fix. Just waving the phone around in a sort of horizontal figure eight gets the magnetometer re-calibrated quickly. I think the GPS Status app has or at least had a message that would pop up and tell you when you need to recalibrate the compass and gave the instructions. My old phone needed this almost every time I used the compass. I have gotten some funny looks from people when I wave my phone around, but it works.
Sent from my rooted Kindle Fire using xda premium
Hi.
I have the same problem with the compass, but I noticed that this is not a hardware problem. GMaps and sky maps take position relative to north from a bad sensor. When you lean out your phone to the front and rear, GMaps think that is spinning. The phone in vertical position - west, horizontal - east, so simply with just a slight correction in the code your applications will work properly.
Ok, if anybody have this problem - upgrade to at least 2.3.6.
Dear all,
Can anyone tell me if they are able to use Google Maps, especially for Navigation with Satellite Imagery turned on?
I have a terrible issue whereby after about two or three minutes of driving, first, my location freezes on the map (though notable is that the voice commands stay current and correct based on actual location). Then, the screen starts freezing, jumping, jerking, and generally MASSIVELY GLITCHING and flashing in a completely unviewable state. The voice commands however stay correct. It's just as if the device cannot handle 3D rendering of the imagery at all.
Now here's my big issue...
I am now onto my THIRD Galaxy S3, and this issue is reproduce-able 100% of the time, and over 100% of the devices. That is, it does it every time, and it does it on any and every Galaxy S3 I try to use for Google Navigation. And my devices have deliberately been a mix of some White, some Blue, some from one supplier, some from another.
So what I am asking, is are there any users out there that CAN actually use Google Maps Navigation fine on their Galaxy S3...
By that, I mean for a proper period of time, over a proper journey, deviating away from the set route, and with Satellite Imagery layer turned on. EVERY time I do this, on THREE separate devices, the display goes haywire. So I am trying to establish WHERE the fault is... is it phone software... is it phone hardware (I prey not), or is it a Google Maps issue (you'd think they have noticed by now if it doesn't work with the SGS3 though...)
The only saving grace is that it points to a Maps issue, as when using my NatWest Banking App, to locate ATM machines, when dragging the map about, it freezes terrible, then eventually crashes (just as Google Maps natively does for me a lot), and then eventually FC's... and the underlying mapping it uses is, yes, Google Maps.
So I'm after any feedback at all here.
But worried that it's 100% of the time for me, and on no less than THREE Galaxy S3's I've had so far, mix of white and blue, and mix of suppliers and locations...
Any comments please...?
----
EDIT - just to add device info:
Samsung Galaxy S3, UK Unbranded, both blue and white.
Previous Firmware (with the same issue) was: XXLE8. CURRENT FW: XXLF2
Similar behaviour to what I see on the galaxy note after the so called ics update. Everything was fine on GB. So could be an issue with ICS. Because of that, plus a few other critical issues, I'm now an ex Samsung owner.
I have the same issue.
Sent from my GT-I9300 using Tapatalk 2
Try an older version because I'm using v6.1.1 and no problems so far.
I have experienced crazy flashing and also a black screen while using Google Maps Navigation. It occurred about half way through a 30 min journey. I've seen it happen on both my girlfriends S3 and my own. Also, satellite layer was off.
Could be a bug caused by Samsung's graphics drivers? I hope its fixed soon. I'm currently on IMM76D.I9300XXALE8. There has been no OTA update for me yet and I am in Australia.
Well, that's the end of the S3 for me. The GPS using Google maps + Navigation was (is) a major feature for me. It worked so well on the SGN under Gingerbread and totally corked when I upgraded to ICS. Now I see the S3 ships with ICS and you guys have exactly the same issues.
I spoke to my retailer and went into great depth over what went wrong post ICS and they have noted EVERYTHING and has given me a full refund for the phone. This was my fourth device, Samsung cant/wont get it right and I want no more. I have no idea what my choices are for now, I'm using an old motorola clamshell whilst I ponder. I would recommend anyone having issues with the S3 or Note, just send it back to your retailer for a refund. The product is flawed and little will be done until Samsung see devices returned by the lorry load.
I have a white s3 (UK sim free) with lf2 and 6.8.1 Google maps. I've been using Google maps navigation for 2 weeks as my work pda (with built in tomtom) has been returned.
I've used it all day, 5 days a week, making at least 6 journeys per day with no issues.
I tried it today with satellite view and that too works with no issues. Worked ok with shipped firmware too. Le8 I think it was.
I have had the map jump around/flicker before when turning on a layer but exiting and reopening maps sorted that.
Hope this helps
Sent from my GT-I9300 using xda premium
skibadee said:
...........I have had the map jump around/flicker before when turning on a layer but exiting and reopening maps sorted that.
Hope this helps
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
That was not my experience under GB. Under ICS My experience had nothing to do with layers, and reopening maps is not an option when driving, also, that is not how the software should be behaving. So you too have a faulty unit.
bigstarrynight said:
That was not my experience under GB. Under ICS My experience had nothing to do with layers, and reopening maps is not an option when driving, also, that is not how the software should be behaving. So you too have a faulty unit.
Click to expand...
Click to collapse
I have had similar random bugs on GB and froyo (since my sgs 1) and to say the 1 out of 50 times I use maps it may crash - means my s3 is faulty?
I don't think so
You do realise navigation is still in beta?
Last week Google introduced a bug which killed latitude, few days later another update fixed it.
Sent from my GT-I9300 using xda premium
skibadee said:
I have had similar random bugs on GB and froyo (since my sgs 1) and to say the 1 out of 50 times I use maps it may crash - means my s3 is faulty?
I don't think so
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
We both have different experiences. See how you get on with the S3. Personally, I paid top whack for a flagship product and it doesn't work as it should. It also has the faulty eMMC chip. Under GB it never crashed once, under ICS, its so unstable as to not be reliable and not performing as could reasonably be expected. As I say, see how your S3 goes. I'm certain that not all units will display the same characteristics, but its clear some are. ;-)
bigstarrynight said:
We both have different experiences. See how you get on with the S3. Personally, I paid top whack for a flagship product and it doesn't work as it should. It also has the faulty eMMC chip. Under GB it never crashed once, under ICS, its so unstable as to not be reliable and not performing as could reasonably be expected. As I say, see how your S3 goes. I'm certain that not all units will display the same characteristics, but its clear some are. ;-)
Click to expand...
Click to collapse
Thanks, wasn't aware the eMMC chip issue was present in the s3, I'm sure I ran chainfires app to check when I first got it.
I shall bear that in mind when flashing, seeing as my s2 died a horrible death because of it
Sent from my GT-I9300 using xda premium
Firstly, a BIG thank you to ALL who have contributed to this thread.
Could I ask that those with issues though, tick the poll to say so, as the comments in the thread indicate lots are seeing this issue, but the poll indicates most are having no issue.
Just to add to my own original post though, to say that today, on two separate journeys, Google Maps Navigation worked FINE for me, but with the SATELLITE LAYER TURNED OFF.
That is, standard mapping, and I had no screen issues.
So this only seems to happen when Satellite Imagery Layer is turned ON. In which case it does this 100% of the time for me, across 100% of three different S3's so far, and let me be clear, is so bad, the application is 100% unusable (unless you navigate by voice prompt) as the screen is either entirely frozen, or glitching permanently and incessantly, the whole time.
So my next question though is this... if this IS only a Google Maps Software issue, how exactly do we reach out to Google, to tell them that GMaps is not working, with the latest flagship Android Device...?
Also, as best I recall, I never had this issue with GMaps on my SGS2's both running ICS. But it might have been an earlier GMaps version.
Now, how would I find an earlier GMaps version, to see if that works...?
(Finally, as an aside, why does the SGS2 running ICS, score higher/better scores for 3D graphics, than the SGS3 does, using either Quadrant, CF Bench, or AnTuTu... surely the SGS3 should have BETTER 3D hardware...?)
I tried v6.1.1 and working so far.
http://multiupload.biz/qpmbog3jzau0/Maps_6.1.1_MultiUpload.biz.apk.html
Shadamehr said:
................So my next question though is this... if this IS only a Google Maps Software issue, how exactly do we reach out to Google, to tell them that GMaps is not working, with the latest flagship Android Device...?
Click to expand...
Click to collapse
I doubt it is just confined to GMaps as other issues crop up, not just with me, but other guys on this thread and elsewhere. How to reach out: Android = Google = Gmaps. Samsung are in bed with Google. Throw the phone back to Samsung and use the forums, eventually they will roll over and tell Google to stop snoring, get up and do something. Oh I wish.
Hi,
I'm having similar issues but I get the screen locking on both Google Maps and also Sygic Maps.
Anyone else having this issue with more than one GPS SAT NAV software ?
ash99 said:
Hi,
I'm having similar issues but I get the screen locking on both Google Maps and also Sygic Maps.
Anyone else having this issue with more than one GPS SAT NAV software ?
Click to expand...
Click to collapse
It shouldn't do that. Faulty unit, send it back.
I dont use the Satellite version of Navigation very often, but when you select walking directions it defaults to the satellite map. I was out cycling a couple of weeks ago and selected the walking directions, the satellite map got stuck and glitched exactly as per your description.
The reason your poll is soo heavily weighted as a no is it dosnt mention this issue is specific to using the satellite map.
Just a brief note to say that I too tested an OLDER version, 6.1.1 today, and found that it worked fine on the three journeys I tested it on, with Satellite Imagery turned ON.
So well done to that man - and whilst it still could be a combined Google/Samsung to blame flaw, it does give hope that it is software only issue, that can be fixed with a new version of Google Maps.
As for the point about the poll appearing flawed as it does not specifically state "if Satellite imagery is turned ON", then very good point - my bad!
Contacting Google about this issue:
I've reached out to Google in the only way I can think of...
The following Support Forum thread:
http://productforums.google.com/forum/#!category-topic/mobile/maps-earth-latitude/IlJDfMkgl3U
Hope it's ok to share it here. Mods, if not, please delete the post, not my account *lol*
If anyone else is seeing this issue, can you post there too?
That's not taking anything away from this forum, or attempting to gain anything from this - it's just that this is the ONLY way to let Google know about issues.
So please post there, if this is ok with the Mods here.
Shadamehr said:
I've reached out to Google in the only way I can think of...
The following Support Forum thread:
http://productforums.google.com/forum/#!category-topic/mobile/maps-earth-latitude/IlJDfMkgl3U
Hope it's ok to share it here. Mods, if not, please delete the post, not my account *lol*
If anyone else is seeing this issue, can you post there too?
That's not taking anything away from this forum, or attempting to gain anything from this - it's just that this is the ONLY way to let Google know about issues.
So please post there, if this is ok with the Mods here.
Click to expand...
Click to collapse
That is a very good post, and thanks for making the effort. I hope the Mods do not delete it. I'm sure they wont. We all have to make whatever contribution we can to get the product right. In essence, both the SGS3 and SGN have a uniqueness that is not repeated by any other manufacturer yet. I have tried to seek alternatives that satisfy my needs in the way the two Samsung products can potentially do, but there are no realistic options. However, in their current state, I'm keeping my wallet firmly closed until Samsung/Google get it sorted.
Hi, I'm new to this forum so please help me on my way, thank you guys. So recently I received my Galaxy S3 and I accidentally dropped it on the concrete floor. The screen and external parts of the phone is perfectly fine. Totally fine. But when I'm using Google Maps, until my friend used his Droid Razr, I never did realised that my compass was pointing to the opposite direction. It was all thanks to my friend as I could've been late for an important event. The problem with the gyroscope is that, well, it won't work. The gyroscope calibration under the 'Display' section of settings will always be stuck at the center like as if I did not move the device at all. Beside these two drivers, nothing else is wrong.
Nothing related to your dropped phone
Mine was never dropped and have the same issue...
I think that samsung will have to work on a software update for these two things
this issue happened with my galaxy tab 7 plus also
Turning off smart rotation helped for me.
Sent from my SPH-L710 using Tapatalk 2
So i just wanted to know if anyone else out there/what i should do. I was one of the people whose edge stopped auto rotating but rather than exchange it i waited for a fix and i got one with this latest update. My phone auto rotates fine now but whenever playing a racing game or a game that uses the accelerometer it messes up.
For example, if im in a racing game (asphalt or real racing) my cars always turn to the right. Nothing makes it go left. So what should i do? (If anything) or is anyone else experiencing this?
kenny111008 said:
So i just wanted to know if anyone else out there/what i should do. I was one of the people whose edge stopped auto rotating but rather than exchange it i waited for a fix and i got one with this latest update. My phone auto rotates fine now but whenever playing a racing game or a game that uses the accelerometer it messes up.
For example, if im in a racing game (asphalt or real racing) my cars always turn to the right. Nothing makes it go left. So what should i do? (If anything) or is anyone else experiencing this?
Click to expand...
Click to collapse
i had the same auto rotation problem and i waited for the update as well, but it wasnt resolved when i did. (i have sprint sm-g925p) so i loaded up every rom we have and firmware and checked the hidden diagnostic menu (dial *#0*#) and every time the gyroscope was stuck on the x axis, i also checked the app checkmyandriod which shows a little better diagnostic on all the axis's the gyroscope uses and 2 of them were frozen on a number. so after all that troubleshooting bull**** i called up samsung (i would have called sprint but i bought the phone from a guy on ebay) and told them all the steps i went through and they informed me that many, many s6 edges internals were poorly put together and the fast charge fried the gyroscope when it heated up above a certain temp. the update only masks the true problem of crappy build quality the first few batches somehow had. my suggestion is to bite the bullet and send it in to replalce it, or just keep having the same problem for the life of the phone. Just my 2 cents though.
TookRDerbs said:
i had the same auto rotation problem and i waited for the update as well, but it wasnt resolved when i did. (i have sprint sm-g925p) so i loaded up every rom we have and firmware and checked the hidden diagnostic menu (dial *#0*#) and every time the gyroscope was stuck on the x axis, i also checked the app checkmyandriod which shows a little better diagnostic on all the axis's the gyroscope uses and 2 of them were frozen on a number. so after all that troubleshooting bull**** i called up samsung (i would have called sprint but i bought the phone from a guy on ebay) and told them all the steps i went through and they informed me that many, many s6 edges internals were poorly put together and the fast charge fried the gyroscope when it heated up above a certain temp. the update only masks the true problem of crappy build quality the first few batches somehow had. my suggestion is to bite the bullet and send it in to replalce it, or just keep having the same problem for the life of the phone. Just my 2 cents though.
Click to expand...
Click to collapse
When i updated the phone it fixed the auto rotate BUT i guess the accelerometer is all tripped. Im completely stock no root. Ive done the *#0*# and it says everything running. Id prefer not to replace it, i dont play games on the phone but id like the option too lol. Maybe another fix?
kenny111008 said:
When i updated the phone it fixed the auto rotate BUT i guess the accelerometer is all tripped. Im completely stock no root. Ive done the *#0*# and it says everything running. Id prefer not to replace it, i dont play games on the phone but id like the option too lol. Maybe another fix?
Click to expand...
Click to collapse
I'm not sure if my findings are rare or if it could be something more, but this is what I found:
I ran into this issue after doing a factory reset. The screen would no longer rotate.
Went out to the market to look for a third party app to check the software for the Gyro. I downloaded "Screen Rotation Control"
https://play.google.com/store/apps/details?id=bong.android.androidlock&hl=en
While running this app, the screen rotated no problem. So I uninstalled the app. Now my screen rotates like it did the day I got it.
Hope this might help someone else.
Hi, did you install AOE3 by any chance?
mythos234 said:
Hi, did you install AOE3 by any chance?
Click to expand...
Click to collapse
I have not
wildjeep said:
I have not
Click to expand...
Click to collapse
Fellas it seems to me that your gyroscope is fried, due to overheating issue when using fast charge. Mine works fine, but when I charge mine I make sure it is cool.
nomad10002 said:
Fellas it seems to me that your gyroscope is fried, due to overheating issue when using fast charge. Mine works fine, but when I charge mine I make sure it is cool.
Click to expand...
Click to collapse
My phone auto rotates now (update fixed it) but i just cant play games that require the phones accelerometer