I have a few issues with my GS7 and am hoping someone here may be able to advise me.
1) Every now and then, approximately once or twice an hour, I get a notification sound or vibration (depending on setting), but no actual notification. I used a program to create a shortcut to the notification log and every time I look there is no notification in that log that corresponds, anybody have any ideas how I can work out what this is?
2) In a similar manner, I'm always getting the notification to choose my keyboard, even though I use Swiftkey and have the stock keyboard disabled. Any tips?
3) I have a wireless charging stand which until recently worked without issues, or none I remember. A few times recently I've taken my phone off in the morning and it's not at 100%, any idea what might stop it charging? The only thing I can think is that if I've woken up and disturbed the phone to check the time etc maybe that's causing it?
Any thoughts on these would be appreciated.
Any ideas anyone?
Same SwiftKey issue here no idea how to fix it.
i oressed the on/off button the home button and volume down buttton together and now have a blue screen ...saying downloading do not turn off target ...help needed how do i get my phone back to normal
Press and hold home + power for about 30 seconds, should come out of download mode.
Related
I have been experiencing a periodic problem where the screen on my Fuze will be on, and it will not dim or go to sleep. Even if I press the power button it does not shut off. So the screen stays on completely and will, of course, eventually wear the battery down. While this is happening, it is not frozen - I can still use TF3D. The only way to get the screen to go off is to do a soft reboot, after which it will perform normally (including the power booting working like it should). This happens about once a day.
This generally seems to happen when the phone is charging. When I unplug it, the bar at the top still shows the phone as connected to the power. I also notice that the battery seems a little warmer than usual at the times when charging causes this to happen.
In searching the forum I found one other user who had this issue, but did not see any fixes. Coincidentally or not, that other user was using Blackberry Connect, which I am also.
Anybody else have this problem? If so, any proposed solution?
While I am at it, I have a Blackberry Connect issue as well. The phone will periodically (usually, but not always, in the middle of the night) just stop receiving Blackberry Connect e-mails, even though everything in the Blackberry software looks normal. Again, I need to soft reboot to fix it. If anybody has experienced this or has a solution, it would be helpful also.
Thanks in advance.
my button seams to have quit working all together, soft reset doesnt help, tryed the hard reset mabe im,doing it wrong. it never ressets data basicly has the same efect as a soft reset.
not sure if its a hardware or software issue at this point. it randomly pops up the are you sure you want to quit txt.
Battory compleatly drained overnight, put it on chager and power button works again. No settings where lost that i see, kind of rules out a hardware issue.
today i noticed an odd issue with the lights on the navicap on my TP, When the screen switches off the lights on the navicap stay illuminated (The home, back, answer and hangup buttons) the light round the dpad/scroll wheel dont light up tho, i dont know how long this has been going on though as i have only just noticed it
does anyone know why this mite happen or any ideas to solve it
cheers
I also can confirm this issue.
Seems to happen only when the light has been activated in landcape mode.
I can recreate this failure every time I reply to a SMS:
Slide open keyboard
Keyboard and navipad lights come on
Reply to sms
Press power button
...and tada! The light is stuck on
The light will go off if I press the center dpad button before I turn off the device, or if I turn back on the device and tap the button.
This problem has followed me through 3 ROMs: the stock ATT Fuze ROM, the new ATT ROM, and an older EnergyROM (8/11/09, not sure which version anymore).
I can also confirm that this problem exists across multiple phones running stock software. My first Fuze had this problem, my current Fuze has this problem, and my friend's Fuze does too. Very odd.
Not a showstopper, but I figure it's the only annoyance I really have to put up with day to day, now that I've got the phone configured the way I like it.
Anyone have any ideas?
Thanks in advance!
Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.
Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2
Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you
So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
I've gotten no help from ZTE themselves - they want me to do a factory reset and didn't even bother to read what my problem is. This is with the stock ROM for a ZTE Blade 10. I touch the power button and the screen doesn't stay off, instead turning on every time I move it (in the same vein as a "Lift to Wake" problem). This burned a huge hole in my battery the first day I had it, butt dialed a couple of people by opening my Contacts on its own, swiped important notifications away (including texts and reminders), and played with apps. I've managed to stabilize it some by tweaking some settings, but I haven't found a setting that disables this entirely.
I have screenshots of my settings in a second post, since I'm not allowed to post them in the original post.
Worth noting is that I have a custom lockscreen app, HiLocker, for which I set a five-second timeout. It does not seem to be the app, since the problem still presents itself when I disable it. Ergo, I either have to choose between changing that to instantly locking (thus making me enter my pattern again when my screen times out, even if I'm in the middle of using the phone) or keeping as is and dealing with this problem. I don't want this to be a choice. I want this five-second thing, but I want the power button to be absolute and keep the screen off until I push it again. My phone doesn't seem to understand something so basic: That's what the power button is for.
Does anyone know if there's a solution for this? Any pointers would be appreciated, thanks!
I hope this works.
https://i.imgur.com/uwdn8V5.png
https://i.imgur.com/aqd16Ko.png
https://i.imgur.com/RuhrvAV.jpg
Bump. Seems I can do that every 24 hours, and it's on the bottom of the page, so...
Still seeking any feedback. Anyone have any idea, or do I need to flash a ROM for the first time in half a decade?
One last try... can anyone help me?