I've searched a bit, but not able to find much... Sometimes when daydream kicks on (currently set to 'Clock-Night Mode' and 'while charging') the back and home buttons (sometimes just the back button only) are lit. The buttons being lit doesn't happen EVERYTIME, but often. And, I've not figured out any sort of pattern as to why (I first thought it was a new notification had been triggered {Nope.} or the battery was fully charged {Nope.}).
Any ideas? Running standard OTA 5.0.1, rooted.
--JamesT
Related
The screen keeps blinking back to full brightness, every 30 seconds or so, when it is left alone and the screen dims normally. It is as if something is pressing a button or touching the screen.
When I press the power button and send it to suspend mode, the backlight goes off, and the tilt no longer responds to touch or button pressing. For some reason it pops itself out of suspend and turns back on every couple minutes. My battery life is going down extremely fast. 100% to 40% in three hours.
Any help would be greatly appreciated. I searched the forum but never found a specific topic for this issue.
MiniDevil said:
The screen keeps blinking back to full brightness, every 30 seconds or so, when it is left alone and the screen dims normally. It is as if something is pressing a button or touching the screen.
When I press the power button and send it to suspend mode, the backlight goes off, and the tilt no longer responds to touch down extremely fast. 100% to 40% in three hours.
Any help would be greatly
appreciated. I searched the forum
but never found a specific topic for
this issue.
Click to expand...
Click to collapse
I have the same problem w
th the backlight comming on by itself & battery life depletes extremely fast. I am using HD 15 Nov with 3.29.
In addition to backlight issue my hardware keys are no longer working.
Please has anyone got any advice
i have the same problem. the only thing that seems to work is doing the keypad lock and putting it to sleep. it will occasionally blink like its trying to come back on but doesnt. another thing i did is put my phone in flight mode, locking the keypad and putting it to sleep. when i do that it doesnt blink or anything. sadly i wont receive phone calls or emails and texts. i think the blinking has something to do with phone signal and accessing the networks.
hth
also i noticed that it wakes from sleep when the keypad "unlock" screen pops up.
i think i found a fix
Ok I hope this helps for you because it seems to work for me. I first went to start/settings/sounds & notifications. Then I clicked on the notification tab and unchecked everything leaving only the ringer on for when calls come in. when I did that, for about 5 minutes (longest I tested it at) the phone did not turn on and the backlight didn’t do that weird grayish flash thing. Afterwords I at first was going to go down the list of all notifications and turn things on/off to see what wakes up my phone but i got too lazy and only checked one setting. One thing I noticed is that when I have the beam: autorecieved notification turned on for display a message on the screen I get that weird backlight flickering thing. So for now I just have sound alerts on when I receive any type of messages and a sound alert for reminders. So far so good, my phone hasn’t woken from sleep in 20 minutes.
(moved from wrong forum to right one!)
Here's a silly question,
How do I tell if the N1 is off? Without turning it on?
There have been several times where I've turned it off for the night (force of habit), and later couldn't remember whether or not I had in fact turned it off...
Of course hitting the power button only turns it on if it was in fact off... meaning that I have to wait a whole boot cycle before shutting it down again.
From the thread in the other forum:
Hitting the volume keys doesn't seem to do anything when the phone is sleeping, i.e. it doesn't wake the screen up.
I like the idea of the trackball on wake thing except that it will probably wake the phone up a lot when it's in my back pocket.
any other tips?
v.
Trackballwake is the only way i can think. I used it on Cyanogenmod, and i didnt seem to have a problem constantly waking the phone in my pocket. Give it a shot, if it does cause a nuisance, back to square one.
Hello everyone. I have had my Droid Bionic since day one and I have never had an issue with it. It has been wonderful.
Until today. I am on the stock OS. I had a Live Wallpaper that showed a little Android figure that melts based on the percentage of my battery. I went into my Gallery and clicked on "Set As Wallpaper" on an image I took with my camera on the phone.
At the bottom of the phone, a small popup showed up that said "COMPLETED". When I went to the home screen, there was no wallpaper in the background. It was just black, though the icons were still there and it was responsive. I thought maybe the image was corrupt, so I went and tried another image.
This caused the phone to reboot. When it rebooted, there was a notification bar, the time, the lock screen, and a thing that said No Signal. I tried to unlock it, but the phone was unresponsive.
Then I got a text message, even though I had no signal. The notification light was blinking. I could not unlock the phone. I hit the sleep button, and it went to sleep. I tried hitting it again, and it would not wake up.
I tried pulling the battery and putting it back in, and now it won't properly boot. Right when it boots, it goes to sleep (the little shutdown animation). I texted myself from my sister's phone and the notification light blinks, the phone vibrates, and the screen turns on and shows I have a text on the notification bar. The screen and the buttons are completely unresponsive, however.
I tried calling myself from my home line and I could pick up the call just fine and end the call. I could not, however, go back to the home screen while on the call. The capacitive buttons on the bottom were completely unresponsive. When I hung up the call (by touch), it went to a completely black screen with the notification bar showing that I had some text messages and the time and my service, etc.
I have rebooted the phone five times now by removing the battery and it keeps going to this. I have never rooted the phone (I wouldn't even know how to) and I am concerned because of all of the information that I have saved on the phone.
Yes I have tried removing the SD card. Didn't help.
Any suggestions? :/
UPDATE: Now the phone doesn't even boot, it gets stuck at the Red Eye spinning logo. It vibrates twice and the notification light begins blinking, meaning it is letting me know that I have received text messages... but it isn't actually booting to the Android home screen. Really strange...
You should fxz back to stock
It will wipe your application data but not you're sdcard info or internal storage
Sent from my DROID BIONIC using xda premium
Hard reset using all three external buttons
Try doing a hard reset - it's one of those things they only tell you about at the Verizon store when you're stuck:
Once you have the phone on and at least responsive, press and hold BOTH volume keys, then hold the power button down for 10 seconds (it's really about 6, but 10 will do it for sure). This procedure can also be done to force a reboot when you load a gnarly application that sux and locks your phone up - without having to disassemble everything and pull the battery.
Hopefully with any luck, you're phone will do a back-flip and come up!
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!
I'm having an issue. Ever since the last OTA update when my phone goes into sleep mode I have a hard time getting the screen to come back on ( it still receives notifications and the alarm works etc.. just the screen wont turn on). sometimes I have to hold the power button until the power options screen finally comes on (but this can take upwards of 1 minute to happen ) or sometimes gotta hold the power and home key buttons (like taking a screenshot) or just keep hitting buttons until it finally comes on. It seems to happen more often then not when it is charging ( I tried different chargers and cords both in my home and in the car, it dosent matter) I'm going to try a back up and factory reset today. anything else that anyone would know that could possibly be causing this. Like I said I think it is something in the last update as that is when I noticed it starting. It is stock not rooted