Hi!
My Sensation has been experiencing some weird behaviours.
Although the rotation is locked on the rom (I tried several, all same issue), it still rotates. The only way to stop this is through the launcher options and force vertical mode.
It wakes up during the night, out of the blue. Nothing running, no processes waking it up.
Sometimes I'm browsing stuff (like this morning, browsing the TB backup list), and it kept going back like I pressed "Back" button.
Now, I tried several roms since, all same behaviour (Sense, AOSP, CM, etc..).
Used an app to test the sensors, they all seem to be responding accordingly, although I don't exclude a sensor issue, for some reason it shows normal behaviour in everything else. The rotation works properly as in, turning the way it should, but if it's locked, why it keeps rotating?
Did anyone ever experienced anything like this? I searched on google / xda, there's some odd cases here and there and either they ended up being sensor files being corrupted or uncalibrated.
Anyone care to shed a light on this?
Thank's a lot
Update: New sympthom, on Sense 3.6, it seems like Dock Mode is being called randomly too. This makes me consider a sort of loose contact or alike :S
Anyone?
Related
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
I noticed my touchscreen becoming unresponsive when loading particular websites. Even had it freeze once (only time it ever froze on me)
What were you doing when it does this? Do you have the multitasking reg edit on?
exilkubaner said:
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
Click to expand...
Click to collapse
I know this is an old thread but this is the only reference to the exact same problem that I'm having. I'm having difficulty putting this down to hardware as the screen becomes responsive again when locking and unlocking which might point to software.
It could be a hardware issue that is resolved by locking then unlocking the phone but I don't know enough about the construction of it to have an opinion.
The advice I've had from htc is to wipe the 'phone and start again but I don't expect that to solve it (especially as their call handling system refers to Window Mobile 7 - the second large commercial organisation I've seen that on in recent weeks without looking too hard!).
Has anyone else seen this since the original post or @exilkubaner was a solution found to your problem?
Hi,
I have exactly the same problem. I hard reset my HTC 7 Pro, but no success, my screen doesn't respond until i lock/unlock the device.
So, any one have resolved this issue since the first post ?
Regards
Had the same issue, but I didn't have any roms installed.
Brought it in to Sprint and they found that I had a fried ribbon connecting the screen to the phone. Replaced under warranty.
It happened again, I determined that it was caused by my click in belt clip/holster. When I pull the phone out, it pulls the screen away from the keyboard a bit.
^Wow. Nice find. I'll have to be careful with mine now as I could easily run in to the same problem pulling it out like that.
Hi all,
after upgrading to Lollipop, I have been experiencing a few "glitches" with the screen orientation a couple of times. Even though I've been holding my phone pretty straight upwards, the screen suddenly starts to rotate to landscape mode. Is there a way to recalibrate the gyroscopes (if they are responsible for that)? EDIT: OK, seems that it is actually the accelerometer...
The phone is stock unrooted, only thing is that I am running Nova launcher, could that be an issue? Has anybody else seen this?
Hello people,
I have been experiencing a weird issue lately with my OPO. It seems that for no apparent reason, my accelerometer's X-axis gets stuck in 0.000m/s² value, resulting in the inability to rotate the screen to landscape mode. And, again for no apparent reason, it starts working correctly... until the time it breaks again!
It's really crazy. Last night for example it was broken, I was browsing xda from chrome just to find a possible solution, and suddenly it started working, device just turned from portrait to landscape! When I woke up it was not working again. Sometime around the afternoon it started working again -without me doing anything-, not even handling the phone, it was flat on my desk! After 8 hours of working, it got stuck again right as I was writing this post...
Even when it's stuck however, If I try to shake the device very hard (to the point that it almost flies off my hands) I get a very small reading, around ~0,050m/s² to ~0.200m/s².
(readings were taken with Sensors app)
A reboot does not fix this. I have tried lots of configurations, it's not app/xposed related since it also happens after a full wipe and after flashing the 44S fastboot image. It's not kernel related (I think...) since it happens both with Stock and Franco. So it's either hardware, or related to the ROM.
I believe (and really hope) it's not hardware related since it started a while after flashing 44S, before that the accelerometer worked flawlessly. Also, I may be ignorant here, but if it was hardware it would break down once and for all, it wouldn't work intermittently, right? Either way, the device of course was never dropped or hit so as to damage the sensor in any way.
I've also read one report of the exact same problem on the OPO forum, but could not contact the poster, and several other reports of the accelerometer breaking down (and later being fixed) but in CM nightlies.
I have already tried to calibrate/reset through several apps but without any success. Is there anything else I can try to, erm, "un-stick" it? Maybe there's a configuration file I need to delete or something or a specific way to reset/calibrate it in CM. Or even tapping the device in a specific place? (lol I'm reaching here, but I can't think of anything else).
I have already reported the issue to Jira, if someone is experiencing the same please provide your input here.
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.
My phone is a LG Optimus G (a F180 converted to E975, stock Euro firmware), but from googling this issue it seems to be a problem that can strike any phone with no readily apparent solution...
I first noticed it while playing Star Wars KOTOR, where it'd get stuck; flipping the phone (to better orient the charging lead) started leaving the picture upside down. Initially, I could fix it by long-pressing the home button to get at my notification bar and toggling auto-rotate off and on, before it crapped out entirely (necessitating an orientation-locking app), which led me to think it was a software issue...
But after googling the problem and seeing how widespread it is, I'm thinking maybe these sensors are just prone to failing? I saw all sorts of possible solutions offered, which apparently work for some, but it seems nothing solves it for many, including factory resets and flashing firmware... I uninstalled KOTOR when I was done with it, but to no avail. I don't fancy figuring out how to flash the firmware again, but if that's what it takes...
Does anyone know anything about this issue? Am I stuck with a slightly crippled phone now?