Related
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
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.
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.
Well I've been a silent observer for two years now and this is my first post. I've seen thousands of people get yelled at for stupid questions and laughed until now. I just realized the question I have is probably stupid to someone... so please don't yell at me and be kind. I DID google the heck outta everything I could think of related to my problem. The closest I found was some guy who had the EXACT SAME problem, posted it and followed up his post with another that said "T-Mobile replaced my phone" which helped me not even a little.
Problem: My GSII T989 Hercules was dropped by darn previous owner and tilted accelerometer readings really screwing with auto-rotate. "Why doesn't this idiot turn auto rotation off??" you may ask. Well it turns out the camera apps that use this really nice 8-mp camera and zero shutter lag pay no attention to the rotation settings and rotate anyway. Why is this a problem? When the phone is held in the portrait position the screen rotates to landscape. When rotated to landscape, it may stay or go into reverse landscape depending on whether I tap my head and rub my stomach. I'm running CM9 4.0.4, no OC, and I have ONLY 0 degrees rotation enabled. Use one of those rotation locker apps? Well Rotation:Settings, Rotation Locker, Auto-rotate widgets, shake and rotate....the list goes on and on. They neither set the orientation or lock it in the correct orientation. I have several phones and just have this one because it's one of my favorites but I'd really rather not spend the money on a main-board because I don't have any money. From loosely related threads I've come up with a solution that just causes another problem and that is to disable the sensor driver "/system/lib/hw/sensors.default.so". After disabling this file the camera apps: stock, ICS+, JB, (lgCamera is the only one that ever behaves correctly but doesn't seem to work well) refrain from auto-rotation. I can't find a driver file specifically for the "orientation-sensor" and I believe it may be virtual; derived from accelerometer and/or gyro. The problem with disabling the sensors.default.so is that ALL sensors are disabled. I really don't mind that except for the proximity sensor which hangs the phone up on a call when it touches my cheek and leaves my face illuminated at night (it's illegal in New Mexico to drive and not use a hands free set). I know I know don't talk and drive.
Things I've considered: selling phone, kicking phone, and finally the most scary... Post a question/request OH or take a screwdriver and knock the accelerometer off the mainboard (but I can't find it). It is way beyond my scope to disassemble the sensors.default.so file and remove reference to the K3DH Accelerometer. I can't even code "hello world" without a few hundred compiling errors. Anyone know how to add a compensation/offset/correction factor to each axis until my x y and z resemble everyone else's?
Thanks...
If I'm on the wrong track or someone has a better idea I would LOVE to hear it!!!!!
I know on cm10 ROMs there is a way to calibrate the accelerometer. So that might help. But since it's dropped and completely screwed up the hardware, then you prolly are out of luck. I would use ultimate rotation control or a similar app to lock your rotation and always have the accelerometer shut off.
Sent from my SGH-T999 using Tapatalk 2
quite often screen rotates to landscape when i am putting phone on the table. sometimes it rotates upside down at all. i suppose it is accelerometer problem? is it possible to recalibrate it? in CIT all test pass. in compass app it shows that phone is rotated 2° to the left. if i lift left side of the phone little bit up, it show 0° and green circle. so how can i recalibrate it? phone is rooted, with unlocked bootloader, installed twrp and miui 12.0.1.0 QEDCNXM stable by xiaomi.eu. thank you very much for your time spent reading this post and all help :good:
p.s. i think i do not know how to use google, cuz did not find anything that helped to resolve this problem
I would be interested in how to do that too, it's weird at what angles the phone assumes that I want to use landscape modes, really annoying sometimes
I can't tell exactly whan it has started, but before it was normal or it was very rare that i did not notice this issue