My wife has a fully carrier (tmobile) stock S5 and as of last night has not been able to get rid of the "ringtone" volume slider on her phone (top of the screen). I have reset the phone 3 times but the volume notification shows up and goes to max setting on its own. I try to turn it down but it resets to max and the popup won't go away.
Anyone else have this issue? I feel this is an hardware issue since i have the same phone and never have had this problem and it won't fix itself after 3 resets. We both are on Android 5.0 latest OTA update.
Please help
Related
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
This is the single most frustrating bug I have ever encountered, within a month on two different phones. I was using a Galaxy SII running Kitkat ROMs and this bug occurred on each ROM - and I've just bought a Lenovo S860 which was officially updated to kitkat yesterday and now this same darn thing just happened again!
The bug: After a normal day or two's usage a simple reboot results in the screen/display staying on permanently. It does not respond to the Power button at all - although the power button works perfectly if I need to reboot or power off the phone.
Each time the only solution I can think of is to factory reset which is so frustrating. I don't know why this bug has happened to me on two different devices now; the common features I can think of are that on each phone I had Developer options enabled (but 'keep screen on during charging' unchecked) - I use Dynamic Notifications as a primary lockscreen. I keep display timeout at 1 minute. Other than that I use a few very standard News/Productivity apps none of which have anything to do with keeping the display on and rendering the power button useless.
Lenovo S860 that I'm currently on is not rooted and is full stock so I haven't tinkered around with the system at all either.
I would appreciate any help, any hint or guidance or just plain anything. I'm literally afraid to reboot my phone now, I can't keep setting up the phone after a reset every two or three days.
My wife's Oneplus X stopped responding to the alert slider after the latest Oxygen update... She's on 2.2.1 and just realized that she wasn't hearing the phone ring when calls came in.
I've found a couple of other people mentioning this on the Oneplus forums, but nobody has a solution yet. Anyone here seen the problem, and (hopefully) have a solution?
In order to tell if it's a hardware or a software problem, try to do a full wipe and then re-flashing full rom.
Lovely. Only solution is to wipe the phone? And then have to re-load all the apps, re-set-up the phone, etc...
Nobody else has seen this happen? OS 2.2.1, audio stuck on "No Interruptions" regardless of slider position. Volume keys just pop up the "No Interruptions" window.
Snowflake6 said:
Nobody else has seen this happen? OS 2.2.1, audio stuck on "No Interruptions" regardless of slider position. Volume keys just pop up the "No Interruptions" window.
Click to expand...
Click to collapse
First reflash over the full rom zip abnd wipe cache and dalvik cache,
It won't reset the phone
Then you can try to reboot in "safe mode". Power button, then let the finger on "Eteindre".
A window will appear, then it will reboot. Try to move the button after reboot.
Last idea, try to install "vibrate mod" app.
https://play.google.com/store/apps/details?id=com.nqk.vibratemodeextended
Snowflake6 said:
My wife's Oneplus X stopped responding to the alert slider after the latest Oxygen update... She's on 2.2.1 and just realized that she wasn't hearing the phone ring when calls came in.
I've found a couple of other people mentioning this on the Oneplus forums, but nobody has a solution yet. Anyone here seen the problem, and (hopefully) have a solution?
Click to expand...
Click to collapse
I have indeed the same issue, My phone (OnePlus X) was working fine until it seems to have No Interruptions permanently stuck on - no amount of tweaking with the notification or priority settings seems to work, and my phone is fully updated. Pressing the volume buttons just brings up 'No Interruptions' and a greyed out volume bar. Also if I go to settings and try to change the volume bar that doesn't help. I also tried a hard reset to sweep everything out but that didn't help out neither.
I have the same problem - every position gives 'no interruptions' pop up. No adjustments on settings helped. Phone only 2 months old. It's on 2.2.2...
I don't think it your software. Probably hardware problem. In 2.2.2 everything was fine with tri state key.
Omicron Technics
Having the same problem with my OPX. I have sent mine in for repair.
Factory reset didn't help.
I'll let you know if the problem is fixed when I get my phone back...
_breez_ said:
Having the same problem with my OPX. I have sent mine in for repair.
Factory reset didn't help.
I'll let you know if the problem is fixed when I get my phone back...
Click to expand...
Click to collapse
Phone fixed.
Motherboard got replaced by the service center.
If you have the same problem, send yours in...
I have an S6 Edge, model SCV31, currently running android 7 (updated last night).
Due to my work, I've been in the habit of always having my phone in silent/vibration mode. This has been the case, with this same phone, for around two years. Maybe two or three days ago there was a notification on my lock screen telling me that my phone was on silent and that I may miss calls. I was given the option to take my phone off silent, or say "it is okay". I have never had this notification before. Normally if I receive a notification I don't care for, I long press on it and turn off notifications for whatever is causing it. I could not long press on the notification, and touching the screen to unlock my phone caused the notification to disappear. This was while running android 6. Around the same time these notifications started I was emailed by my service provider that I would soon be able to download android 7. I received the notification a few times before updating, both while charging and not. I was hoping the update would reset/fix whatever triggering the notification, but have still been receiving it since.
I have not been able to force the notification to reappear. I have tried turning on sounds and turning them off again, restarting my phone, and leaving my phone charging for a few minutes (I initially noticed it while charging) to no avail. Until now, I haven't thought of taking a screen shot, but if necessary I will try to remember when next it occurs.
Does anyone know what is causing this notification and how to turn it off?
Thank you in advance,
JB