The accelerometer on my Razr Maxx works promptly and perfectly except under two conditions. The first -- if I'm lying down, say on a couch or in bed, and holding the device over my head facing down. In this position the device will almost immediately shut off over and over. It won't reboot, just shut down. I can always restart it the same way I would from any "sleep". I can get the device to stay on merely by rotating it to face "up" no matter whether I change position or location or run or do not run any particular application. Is this common? Is it by design for some reason? The second -- if I have Button Savior installed, the Maxx accelerometer will work but there will be a significant delay in responding. Like 15-30 seconds delay! No Button Savior - no delay. Install Button Savior - delay. Uninstall Button Savior again - no delay. This troubles me as I really like Button Savior even on devices that have "hard" buttons. Having these controls right under my thumb is the fastest way to navigate, for me. Button Savior (updated) works perfectly for me on other Android phones, on my rooted Nook Color (CM7), even on my rooted Nook Touch. Any cures for either ill?
Hi
The accelerometer issue... does this happens from the first day you bought it? I trying searching similar issues, could not find anything. I am almost sure it is physical defect of some kind, you should probably take it back for replacement.
I don't know if the accelerometer issue related to Button Savior began when I first installed the app (as opposed to coming from a particular app update, for instance) as it took a long process of elimination to find the connection. As to the "upside down" issue I believe it has always done that. However -- it only does it if I TURN ON the device while it is upside down. If I start using it facing up, say watching a video, and then turn it upside down the video continues to play flawlessly. Bizarre!
I know there is an option to use the light sensor to detect when your phone is in your pocket, and turn off. Maybe it's on on your phone, and it's detecting lower light when you flip it over and shutting the screen off?
ok, so i misunderstood the issue, i thought the phone turns off completely...
if it only goes into "silent" or "lock" mode... maybe you installed some kind of app that does that when you flip? or maybe your player has one of those settings? like... say you are in a meeting, with your phone on the table, it rings... you just flip it and it goes silent.... some android build have that as a default setting already...
here, check this so u understand better what i mean :
http://www.appbrain.com/app/flip4silence/org.failedprojects.flip4silence
hope this helps!
tried updating yet? i had the same problems prior to the 65.1.40 update
Related
When I do a soft reset, my phone is fine and everything works okay. However, after the first time the screen cuts off to standby, when it resumes the buttons on the bottom panel (Home, Back, Call, End, Select) no longer function. I can confirm that they all function perfectly prior to standby, and after the fact, none of them.
I'm wondering if this is a known issue, and if there's anything I can do to patch it or look it up. I've tried a few different roms, and it's a constant issue. Even after a full wipe with Task29 and a reflash with two separate roms, the behavior sticks. As soon as the phone comes back from standby mode the buttons just fail.
If it's at all relevant this is a Sprint Touch Pro. If no one can help me and there's no alternative I ask for help finding a way to disable standby entirely. Sure keeping the LCD on constantly will drain the battery, but being able to use the answer and hang up buttons, and the camera FAR outweighs that.
Well, I haven't been able to find anyone with a solution, but I've worked around the issue a bit by installing Keepawake 1.1 and setting it to run when manilla is running. Now my phone never sleeps, and the face buttons work. I'm currently looking for a small piece of metal I can mount over the power button to prevent accidentally triggering standby mode. Then my phone will be mostly usable again. Hopefully someone can shed some insight as to the cause of it all, but for now at least I may have found a way to work around it. We'll see how it affects my battery life.
edit:
Most helpful recommendation (aside from a solution to the root of the problem): could anyone recommend a way to disable the power button, or possibly remap it to launch task manger or something useful?
edit2: Remapped the power button to lock the phone using RaphKeyboardConfig. Works okay for now. Between this and keepalive, my phone won't go into standby if left on it's own.
Hey, I was just playing with my phone this morning and noticed a strange problem... The top part of my screen, just under the notification bar, does not respond when touched, if an app is running. For example, I cannot hit the location/search/layers button in gmaps, or the search button in market (this is only in portrait mode btw), but on the main screen, it responds just fine. This problem did not exist yesterday either, and I have already tried rebooting, and that did not fix it...
Might want to provide a bit more info if you want help.
I.e. What rom are you using, what kernel, any speedtweaks, etc.
Oops, sorry, it just seemed to fix itself randomly, but I am running CM7 1.2/MR2 radio, no other tweaks, just in case anyone else has the same issue in the future...
NoHesHere said:
Hey, I was just playing with my phone this morning and noticed a strange problem... The top part of my screen, just under the notification bar, does not respond when touched, if an app is running. For example, I cannot hit the location/search/layers button in gmaps, or the search button in market (this is only in portrait mode btw), but on the main screen, it responds just fine. This problem did not exist yesterday either, and I have already tried rebooting, and that did not fix it...
Click to expand...
Click to collapse
Im hoping it was just a fluke for you, but keep an eye on the issue, if it happens more it would sound like you could have a bad digitizer (its what controls the touch screen)
So it happened again today, not sure what set it off, but this time it wasn't just the top part of the screen. Phantom presses would happen, the notification bar would go halfway down and then pop right back up, the 4 buttons on the bottom wouldn't respond... I did a battery pull, and it seems to have fixed it for now, should I be contacting verizon to replace this one? It is a replacement of my original one (which bricked)...
I was just sitting on the couch, and the screen on my phone came on by itself. Not to the lock screen or anything, but the screen looks like its on its dimmest setting (barely on at all) and the search button at the bottom is very dimly lit up. Happened twice in the past 20 minutes...anyone else? I'm going to reboot and see what's up.
Are you using a third party sms app? There's a usually a setting that wakes the phone when a text is received.
I've used Handcent without any problems so far. But to be clear, this 'waking up' of the screen is NOT like when you press the button to turn on your phone. When I noticed the problem the screen was so dim that if you're not in a darkened room you probably wouldn't even notice, it's very faint and the only other thing that was lit up was the 'search' button and it too was very dim. At first I thought it was just the reflection of the tv across my phone screen thats how dim the screen was, but it was definitely on and no buttons being pushed would completely wake it up until I pushed the power button to turn on the screen completely like normal. Weird....but after a reboot I didn't see it do it again. I'm wondering if others might not be having this issue and not even have noticed, thus poor battery life for some people?
This happened to me once before. A rebooted fixed the issue for me too.
Sent from my EVO 3D using Tapatalk
Have you used one of the temp roots. I had the same problem when I used one of them and when I restarted the phone it seemed to clear up the issue. I have noticed that powering of the screen while its in 3D mode can cause weird issues too sometimes.
Strange. No this is a stock device I haven't tried the temp root yet. Since the reboot I've been watching it closely and it seems to be fine. I suppose this thread should have been posted in with the one already discussing bugs, but I wasn't sure. Thanks for your kind replies!
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.