Develop Bugs

Rotate screen clockwise.

I have done a quick search but not found anything useful about why the screen on the desire only rotates in one direction. I have come from WM phones which all rotate both ways as does the iphone so I hope its not just my handset. If anyone knows of an app for this that I have not found then Thanks for any advice.

Just a quick reply, mine only rotates anti-clockwise so It's not Just yours m8. Hopefully someone will point us in the right direction

There is only 1 way to auto-rotate
This also fricked me in the past when I tried to auto-rotate and it did not.
Panic attack that I got faulty device.
It is not

Thanks for that. Must be in the software then. I wouldn't have have thought it would be that difficult to implement. How annoying.

Some custom roms let you autorotate 360 degrees, i.e. even upside down (The latest Cyanogen does that on my G1)
I am actually happy my desire doesn't auto rotate to the right, so I can lie on my side in bed and read the phone without it rotating. I imagine if/when this phone is rooted this is a feature that can be easily added to a custom rom.

Didn't even realise it didn't turn the other way lol. I agree with the above poster though, my iPod Touch rotates both ways, and it's a real pain.

[Q] Compass started acting up after upgrading to Froyo

I have upgraded my HTC Desire to Android 2.2. Unfortunately I have realized that after that update, an embedded compass started acting up. I mean it's not showing the North anymore. It seems to me that it's not an issue with some particular application as I have tried with several ones available on the Market and it needs to be some bug with new OS. Anyway here is what I have figured out and what I have already done in order to get this sorted out. At this point of time, it even looks like I have just some kinda workaround:
Once I pick out 'Calibrate' menu item in Compass v1.1 (developed by Snaptic, Inc.) and then according to the instruction, start off waving my phone in a figure 8 pattern to reset the magnetometer on my device, it's not gonna fix the issue but when I start rolling my phone in a hand (side to side then top to bottom) and then it seems to me that the issue is sorted out as finally compass points out the North, but after I close the application and open it again (or open any other compass based app) the magnetometer is broken again So all what I can do is to reset the magnetometer as per above-mentioned instruction again. It just looks like the device is not able to save some compass calibration setting anymore.
Anyway I was just wondering if some of you already faced this same issue and know how to fix it permanently. I would appreciate it, if you could share any thoughts with me. Thanks in advance.

Hey folks, I don't believe that nobody experiences that issue too. Maybe you just haven't noticed that yet? Anyway could you please just check if your compass works as intended after the upgrade to Android 2.2? Personally, I really believe it's a bug with Froyo.

I think mine is also acting weird.
Wenn starting Google Maps and using streetview in compass mode it only looks up and down and I cannot look from left to right.
When i roll the phone a few times in my hand it starts working.
But after closing Google Maps and starting it again I have to do the rolling again

I was wondering that compass problem too. With ver.2.1 everything worked like a dream as I use compass mostly geocaching. After updating in every app I've tried the compass stucks pointing to approx. to the lower left corner of the screen. Sometimes calibration helps but it stuck again after a while even the app is running all the time.
"Compass" app kinda could wake up after waiting a while but usually it doesn't. In any other software won't work at all as I've tried, 5secs after calibration but nothing more.

JLillia said:
With ver.2.1 everything worked like a dream as I use compass mostly geocaching..
Click to expand...
Click to collapse
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...

I can't say if it worked properly with 2.1, didn't use the compass a lot before.
With 2.1 I needed to calibrate it a few times, but probably not as much as I need to do now. I'm using the "compass" app and it directly tells me it detected an abnormal magnetic field. After calibrating it again, it points north. Haven't checked the correct north with a real compass, so it may have a slight difference.
I put my phone down at the table at 0 degrees N. I turn off my screen, and turn it back on. It is now pointing 90 degrees E. But the interesting thing is.. the east is actually located west, compared with the previous north :?
When I rotate my phone it displays only E or SE, always between 90 degrees E and 130 degrees SE. I can't even find north.
I can rotate my phone 180 degrees (Pointing south), it displays 130 degrees. When I calibrate the phone and I rotate my phone 180 degrees (Still south) it displays 160 degrees S. Which is kinda strange. And when I try to find the 180 degrees point, and rotate my phone again, it displays 35 degrees NE.
After another calibration the values seems to be okay...
My conclusion? Don't trust the compass at all unless you have a real compass to compare.

That person with the exact opposite experience is me
I complained on 2.1 here with many others about the compass going haywire every time you took it off-screen and its lack of stability and consistency. HTC 2.2 totally fixed this issue for me. I've calibrated it once about a week back and it's still accurate every time I'm opening it and in Google Earth.
Beware, the compass draws a lot of power in use so it'll drain the battery very fast. About as fast as playing a 8Mbps 720p VC-1 vid.
-----------------------------------
- Sent via my HTC Desire -

My problem is kinda dame that with Nakebod.
As I said compass stucks pointing to the lower left corner, it infact tells I'm holding the phone towards 120-130 decrees east, where ever I turn the phone to. Calibration helps for a while as after that the compass points approxamtely to north which is enough direction to me, but after a while or at least after swithing apps or taking compass background and back on, it stucks again to the 130 decrees.
Of course I am not using this kind of device as "for real" but I'd like to have it at least somewhat accurate. As geocacher I use compass as a tool with my hobby and I was quite happy with Desire because of the quite accurate GPS but after the update the compass is practically useless.

Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.

Try calibrating your magnetometer by waving your phone in 8-shaped moves.

I emailed HTC customer care also about the issue and the answer was to factory reset the phone. Of course that was the first thing I had already done at the minute I noticed the problem in first place so I wasn't quite fond of the idea. In fact I have reseted phone three times after the update and allways the result was the same; compass stucks.
Well, I thought that maybe I have some weird app that messes up the compass so I tried one more time...
At first after the reset I downloaded only EStrong file manager, compass and c:eo. Compass worked most of the time! I kept resuming backups and compass did stuck occasionally but not very often (+ abnormal magnetic field). I am not sure what I did leave out of the phone but now the comapss works quite fine. It is a lot more sensitive for magnetic fields than in 2.1 but usually calibration works to it.
So, the conclusion is, that even for some reason first times the reset didn't work, it did help after all. Just backup your data and give it a try. Doesn't cost more than some time. The compass DOES stuck still but is most of the time usable.
At least I left out MoreLocale2, Metal detector and some games. And I DIDN'T calibrate G-sensors after reset.
So, there is still some issues with update and compass but it COULD also be somewhat application related...

G-Sensor calibration might be the answer! Following the first factory reset yesterday which cleared the compass problem initially I reinstalled all apps and calibrated G-sensor to find the problem came back. Then I factory-reset once more last night and reinstalled all apps but didn't do the re-calibration, left the phone on for the night - no problem in the morning. Feel tempted to re-calibrate to proof the point now.

Please inform here how did it do if you re-calibrate. I have an ongoing geocaching challenge, so I won't try that until I'm sure that I don't need the compass for couple of days. After that I'm going to test if calibration is the problem as soon as possible.

I have the same problem. Have tried everything but hard reset. Still, compass worked a lot better on 2.1 :-(
Sent from my HTC Desire using XDA App

nitemarc said:
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...
Click to expand...
Click to collapse
My compass works fine on HTC Desire on Android 2.2.

Try 3d compass, and use its calibration option. Always works for me.
Sent from my HTC Desire using XDA App

nitemarc said:
Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.
Click to expand...
Click to collapse
Wonder how does HTC support team's SLA look like in terms of resolving client's tickets as my one hasn't been resolved yet... Anyway it seems to me that HTC is not going to confirm that OTA update to Froyo could caused that compass issue.
That's why I decided on factory data reset and it looks like that helped with getting this issue sorted out. After the hard reset, my first step was an initial compass calibration and that's really all what I did. The digital compass is not maybe so precise and accurate as it used to be on Android 2.1 but finally roughly (I would say with 15° margin) points out the north so there is a progress

Just to add my 2c, I can confirm that the compass has become useless since I upgraded to 2.2 on my device. Doing the figure 8 in Compass app has short lived benefits.
Sent from my HTC Desire using XDA App

Neither does my compass react in any application (tried Compass, Places directory, Google Navigation) after update to Froyo.
Calibrating with the 8 movement or G-sensor calibration does not help at all.
However, it always starts working normally when I tilt the phone to the side (so that I look on the slim side of the phone) and then start a short forward and backward rotation with the rotational axis going thru the display.
I need to repeat this every time I unlock the phone and the compass keeps on working until i lock the phone again or until I switch the application.
Weired.

I have the same problem, and it is a bit annoying. The compass works correctly if I wave the phone like in the video posted, but I have to do this every time I start an app that uses the magnetometer. My phone was not like this on 2.1.

[Q] Shaking Device/words with friends

any one have an issue with this phone when it comes to apps that require you to shake the device??
my screen rotates quick but when it comes to apps that use a shake function no such luck...noticed this with words with friends...my tiles constantly move instead of me shaking it to move them...tried another app (magic 8ball) to shake no movement...Running eb13 and genocide kernel rooted ext4 if that matters

I am having the same issue with the Words With Friends app. The letters constantly move around.
Maybe its some sort of accelerometer issue?
EDIT: I'm running stock EB13 2.2, updated with the update.zip file.

ShootMe works just fine for me - I Odin'd directly to EB13, and have been running the under-development SyndicateROM Frozen (Lost Carrier edition ) and the ACS kernel team's kernel since.

The wwf tiles shaking happened to me at first after I updated to 2.2 I got it to stop by force stopping it and re-opening the app.
Sent from my SPH-D700 using XDA App

I had to do that horizontal calibration to kinda fix it. Idk whats up with that though...it was an issue on DK28 as well and someone brought that up on another website, they werent on the Epic so its not specific to the Epic. Idk whats going on with that shake crap. But its annoying. I have to place one tile on the board just so it'll stop and so i can actually look at what i got and make a move >.<

I have found a temporary workaround. If you do a horizontal calibration, like the above poster suggested, but, have the phone turned upside down (Screen touching the table) it seems to fix the problem.
I just held the phone down with the part of the screen with the "Calibrate" button hanging over the table so that I could still press it.
Could be related to the same bug that is affecting the compass pointing in the wrong direction.

I second that. You have to do the calibration lag fix that ppl have posted a few times. Turn the phone on its screen and calibrate. That fixed the letter shaking for me.

thanks for the input the upside down calibration def did the trick...to bad the shake thing cant be fixed but hey it is what it is..

Going to manage applications and then force closing the app (WWF) while it was running stopped the constant tiles moving as well as giving me the ability to slightly shake the phone to move the tiles.
I am running stock everything on 2.2.1 Epic 4g
(thinking about rooting only to fix the LED notifications and battery pop-up, otherwise this phone is fast enough for me)

The WWF tile issue is also caused by overclocking. Set all your speeds and voltages back to stock and it will act correctly.

Cavalicious said:
Going to manage applications and then force closing the app (WWF) while it was running stopped the constant tiles moving as well as giving me the ability to slightly shake the phone to move the tiles.
I am running stock everything on 2.2.1 Epic 4g
(thinking about rooting only to fix the LED notifications and battery pop-up, otherwise this phone is fast enough for me)
Click to expand...
Click to collapse
how are you going to fix the LED notifications?

[Q] Accelerometers won't see above horizon?

Hey folks, I've got SyndicateROM Frozen running, and have the following problem:
When I use Google SkyMap, it won't let me see above the horizon. If I use GPS Test, which shows pitch/roll, it'll detect up to 90 degrees up, but doesn't seem to register anything higher than that. I mean: when I hold the phone flat on a table, no problem. Pick it up, and face it in front of me so the screen faces me, no problem. Tilt it upward so the camera is looking at the sky, and it doesn't seem to register.
I've tried calibrating compass, accelerometers (with the GPS Test tool, and with sensorcalibutil_yamaha), but to no avail. Tried the calibration tool in system settings, too.
This happens with any Froyo build/ROM I've tried. Did battery pull, etc., no go.
Anyone have any suggestions?

Finally someone else has asked about this. There is an app called "Surveyor" that is used to measure distances with the camera but ever since I started using custom ROMs it isn't able to find horizon. Any help with a possible fix would be appreciated.
Sent from my SPH-D700 using XDA Premium App

I had a problem similar to this (the compass was pointing way off and very erractic). I used an app called Sensor Debug and found that my pitch axis was reading -178 lying flat on a table. I went into the phones display settings and chose the Horizontal Calibration, put the phone upside down flat on a table, but hanging over it so I could reach under and push the Calibrate button. This worked for me like a champ! (Calibrate upside down). I noticed this after the OTA Froyo.

I have the same issue as the OP. I tried installing that sensor debug and it showed 0 for pitch and 0 for roll when laying flat... note... I put it flat but with the camera hanging over the edge of the table.
Anyways, Google Skymap fails for me too...

bump... any word... hopefully from a dev on what is happening?

Not flat with the camera hanging off... upside down flat.. screen side down.. with enough of the screen hanging off to hit the calibrate button..
Sent from my SPH-D700 using XDA App

Hmph.
Welp, looks like I've got to post here, as I'm a new enough member and don't have the necessary # of posts to post to the Developer forum!
In case anyone from the ACS/SyndicateROM team is reading this: AWESOME JOB. Flashed EC05 and Takiya (1.1.0) without a hitch. Amazing that it just keeps all data/settings. I can't thank you guys enough!
Back to the point of this thread: Accelerometers are still not working correctly, even with EC05. I've re-tried:
- Android horizontal calibrate (under settings) both screen up and screen down
- system/bin/sensorcalibutil_yamaha, both screen up and screen down
- Battery out/battery in
- Recalibrate from within GPS test.
Good news is compass works, GPS works. Within GPS test there's a pitch/roll sensor. Doesn't seem to want to register above 90 degrees.
If someone is running EC05/SyndicateRom 1.1.0, would you try running Google SkyMap and see if you can see above the horizon? Basically, I can tilt down and look at the Nadir, but when I tilt up, no matter how far I tilt up, in landscape or portrait mode, it won't show anything above the horizon.
Thanks!
EDIT: Er, the app I use is called "GPS Status," it has the pitch/roll/calibrate stuff.

It seems to work for me (running SRF 1.1.0).
Unless I'm just interpreting what I see incorrectly, but if I start out pointing down, and gradually shift to pointing up, it crosses what I assume is the horizon (because it has directions like north/south written on it) and keeps going.
I'm pretty sure it worked for me on previous versions of SRF though.

Proximity Sensor

hello friends, I need to know, how much energy can be spent, the proximity sensor
using Tap Tap app.
I'm looking for the best option to unlock the screen without touching the power button
T989

Im not quite following. Whats the Tap Tap app have to do with the proximity sensor and are you wanting to keep the screen live with the app open?
Sent from my SAMSUNG-SGH-I727 using Tapatalk

I think he's referring to the "always on" feature, keeping the proximity sensor always working so that the phone can be unlocked by waving your hand over the phone a set number of times (without even touching the phone physically)
However, battery life would only be a small concern IMO.. I would be more worried about the durability of the sensor being constantly on.. as in, would it cease to function eventually from over usage?

Update: it seems the "always on" setting is being reported as shutting off on it's own despite settings after an extended period of time. Reports vary from ten minutes to several hours/overnight, so the amount of time before it fails to stay active is unclear.
Personally I'm not sure of that's a bug or intentional. There are a couple of logical reasons to force the auto shut off after some time
1. Security - If you're not using your phone for an extended period of time, then it should lock back up, because frankly some people are idiots. Also who would want their phone easily accessed because they took a nap or ran to the store and forgot their phone? If you're not near it, you don't need to show off the feature (which let's be honest, that's the coolest thing about it. Who wants to constantly wave their hand over their phone like a weirdo with no one watching? You're not a wizard bro no matter how many RPG's you play)
2. Sensor Durability - the app won't last long if there's people in the play store leaving ratings like "proximity sensor doesn't work anymore, even after uninstalling. Factory reset didn't fix, I'm suing you ****er!". Plus if the Dev's worth supporting he's already tested and knows that's an issue, then he or she's protecting their customers
All of this information comes from user reports in the Google Play store and various threads. I have not installed the app and do not plan to until I see consistent commenting that issues have been addressed or resolved by the Dev (and yes I will be watching)
Seems like a "show off" app and I'd like to give it a shot when I'm sure it's functional. Typically in this case I'd just install, see what happens then email the Dev. However when it comes to hardware (proximity sensor) I'm a little more cautious since my phone is running like a champ with a flawless screen..I can't risk an exchange.
Sent from my T989 hunting for Siri Connor

Just thought I would point out that, when using an AT&T Skyrocket UCLA3-based ROM, the proximity sensor turns itself off if you leave the Phone app so that the screen doesn't keep turning off if you try to pull down the notification tray