Related
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
matt2053 said:
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thats what i suspect. Its just a pain to have been waiting for 4 days for something that probably wont fix anything and then to have to start the whole thing over again with samsung. O well
stanleywinston said:
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
Click to expand...
Click to collapse
Deal with the retailer you bought the phone from, and get a replacement from them.
oscillik said:
Deal with the retailer you bought the phone from, and get a replacement from them.
Click to expand...
Click to collapse
I'll give it a go. Im guessing they wont do a doorstep swap like i'd get from t mobile though. Hopefully i wont be without it for long. In our short time together i've grown quite attached to this phone (and almost got used to not touching the volume button)
Couple of questions (you may have already done these -apologies if you have)
Have you tried a factory reset? If not, maybe worth trying it, could be an app doing wierd things.
Also, try running a logcat trace when replicating the issue - see if it helps point in the direction of the issue.
Does the phone still crash when you're in the bootloader? (This _may_ help to rule out application related issues)
I have tried a factory reset. Weird thing is that im pretty sure that it didnt do it for the first few hours that i was playing with it. It was just at the point that i had it all set up that i first noticed it so assumed it was a rouge app and did a factory reset. When it rebooted i signed in and hit volume and it crashed so its definately not an app.
I almost believed that it was the normal volume bug because if i go somewhere more remote in the house, away from all electrical stuff, i can hammer at the buttons for a while before it crashes so maybe ive just got a more extreme version of the bug. Just noone else seems to have anything close. Volume control works fine in a call and when the screen is off but i havent tried in bootloader yet. I'll give it a go
I've been having a a bit of a strange bug with my GN...
When i unlock and open for instance messaging app to look at SMS's...i see the screen dim a lot and come back again. If i open up settings screen dims like an LCD panel with no backlight. If i click back, screen comes back again or if i lock and unlock screen, all is OK.
I've done some fiddling about and it only seems to happen on apps with white backgrounds i.e. messaging, gtalk, gmail etc. If i open dark background apps i.e. phone app, settings or gallery it doesnt happen.
But for all those other apps when i launch them, screen appears to flicker (dim) and come back again...messaging is the only one where it dims completely in settings.
Has anybody else noticed this?
And more wierdness...in the messaging settings menu, if i scroll to the bottom the brightness goes completely and then comes back again, and starts flickering a lot...
maybe i'll try turning off auto brightness and see if it still does it...
I've had a couple of customers come in already saying they always felt like the brightness was on notch to low sometimes or just very dim. Considered it user error, just got my nexus in the mail and after set up brightness just dropped randomly to almost nothing...
soooo guess we'll see
ah well still did it with auto brightness off
wonder if i've got a borked phone or if others do it and they just dont notice...
EDIT: if anybody's interested in seeing it i've just uploaded a vid here
And i know i still have the front screen cover on...havent wanted to take it off yet!
Restored stone to factory settings this morning and i've not installed anything else or changed any settings (other than turning off NFC, wifi and mobile data)...and it still does it.
Think i might have a defective handset then...annoying though, it's only 2 weeks old but the place i got it from states
Phones that are faulty out-of-box as determined by our warehouse can also be returned for an extended period of up to 7 days from date of delivery.
Click to expand...
Click to collapse
So if i can't get a replacement out of them, what are the odds of samsung replacing it for a new handset?
Hmm pretty sure it's hardware, set desktop picture to something quite bright/white and sure enough when i was scrolling through the 5 homescreens brightness was flickering from one to the next...
What are the odds of getting a replacement handset after 2 weeks? :|
I had this same issue when I got my phone. I had a yakjuwx build in my phone.
Ever since I flashed over to yakju I haven't experienced it.
You may want to check and see what you have.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
I had this same issue when I got my phone. I had a yakjuwx build in my phone.
Ever since I flashed over to yakju I haven't experienced it.
You may want to check and see what you have.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi, thanks for the reply.
Mine is already running yakju from new :/ I might try re-flashing it tonight though just for the hell of it.
Is this not a bit weird that it happens only on bright/wight screens/backgrounds/apps? And that it's suddenly fine when you lock the screen...
If it was a laptop i'd be fitting a new panel to it but then i dont know what amoled's are like (especially combined with a light sensor)
Nope, still does it after a re-flash :/
Got a replacement handset now...
Like my first one, it was one of the early opened and re-sealed with samsung label handsets (and they hadnt put the battery door on properly, fingerprint on the SIM card slot!)
But anyways, waiting for the OTA update on this one
It's obviously running ITL41D and no OTA has come through yet whereas on my first handset it came through pretty much straight away.
Would the fact i've already had the OTA on one handset stop this coming through? :|
Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk
I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Dakotahorse said:
Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse
hudtwalcker said:
I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Click to expand...
Click to collapse
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk
So I found a solution for the issue in my case, it does seem to be software but it's really weird cause the issue continues in any firmware, it started when I was on 6.0.1 PI2, then I flashed Nougat and had the same problem (I hated it and battery drain was killing me) I went back to 6.0 and changed to the PK2 version and the issue continued, it was really weird cause it would cut out in audio messages, games but not music, I also tried every single suggestion on every forum and post I could find EXCEPT the Soundabout app, today I gave up, installed soundabout, selected media to speakers and bam, problem solved, I still need further testing, but it seems ok for now, keep in mind that I also have "prevent USB audio routing" on and "Easy Mute" off.
Dakotahorse said:
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse
Im trying the soundabout app now, I orginally had it set to automatic and was still having the issue, now I set it to speaker and so far so good.
as this worked for me but idk about others... I was told to remove all paired bluetooth devices (on/off doesnt matter) then go to settings>connections>more connection settings>nearby device scanning then turn off... worked for me... (sorry for zombifying an old post but as this is still current with mine and many devices i decided to help)
samsung galaxy s7
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....
Andra1997 said:
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....
Click to expand...
Click to collapse
Is anything still wrong? Or does the sound work both with and without headphones?
Hi. I dropped my phone and have the same problem now. Did you get any useful help?
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
I didn't notice this on the unit that I sent back!
Thanks.
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
fury683 said:
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
Click to expand...
Click to collapse
Thanks for the suggestions.
No screen protector fitted or anything obscuring the sensor.
Next time it happens, I'll check to see if it might need cleaning.
One theory I have, is that this phone has been upgraded with the November patch and maybe there's something in there that has caused this issue.
Has anyone else noticed this after the Nov update?
Thanks.
jscsltd said:
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
Click to expand...
Click to collapse
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
I know there is a bug when using the pixel buds and unplugging them either before a call or during it would stop the proximity sensor from working.
a reboot was the only thing that would fix this issue for me
xweb10 said:
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
Click to expand...
Click to collapse
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
How do I test my proximity sensor?
jscsltd said:
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
Click to expand...
Click to collapse
I am trying to get to the bottom of this. Do you happen to have a Samsung Gear watch? I have the S3 and removed the "phone calls" option from the Pixel Bluetooth menu and so far this issue has not occured, but I am still testing.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
swieder711 said:
How do I test my proximity sensor?
Click to expand...
Click to collapse
There are apps on the play store.
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
jscsltd said:
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
Click to expand...
Click to collapse
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
xweb10 said:
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
Click to expand...
Click to collapse
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
jscsltd said:
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
Click to expand...
Click to collapse
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
xweb10 said:
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
Click to expand...
Click to collapse
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
jscsltd said:
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
Click to expand...
Click to collapse
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
baginz10 said:
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
Click to expand...
Click to collapse
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
xweb10 said:
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
Click to expand...
Click to collapse
I've switched off the ability to take calls on the S3 and can now switch to phone speaker with ease.
I'm hoping I can re-enable the S3 capability when an update by either Google or Samsung fixes the issue.
jscsltd said:
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
Click to expand...
Click to collapse
Sorry I wasn't clear I've done an RMA with google so just wanted to see if anyone else had done the same even though they didn't purchase direct from them. Last year with the 2XL they would send the new one out once the faulty device was sent at the post office, they must have known from the tracking. This time it's via UPS and is going straight to Poland! Not due to arrive until the 4th. If a replacement doesn't get sent out tomorrow or Monday looks like I'll be waiting a while. I even noticed screen burn in when resetting it. Changed to Samsung displays and still burn in from the nav bar just like last year. I wish I'd gone back to carphonewarehouse now to get a replacement!
Wow, I never would have thought of the Samsung gear watch interfering. I have the newest one (the one after the s3) and had the same issue with the screen staying awake while on a call. It was the one thing I really didn't like about the phone. Seems like the symptoms are the same Pixel 3xl, verizon, Samsung Galaxy watch and a restart fixes the issue for a while. I just tried what you suggested. Thank you very much for posting your idea.
I've been dealing with a similar issue, but not exactly,
My screen turns off when I hold the phone against my ear, but the display still seems "active".
My cheek is still bringing the notification area down, toggling my quick settings or even going into the settings app (if my phone was unlocked while I answered a call).
It's been super constant and annoying because one time my flashlight was toggled in an elevator, which was a bit awkward.
Another time my clock app opened and changed my alarm time and then turned it off entirely.
Luckily I could feel the vibration so I knew something was going on but this is a really strange issue.
I have already setup a RMA since the phone has a speaker distortion problem as well, so we'll see what happens once the new device arrives.
So I have a very weird issue and I'll try to explain the best I can;
For some reason, ever since the S10+ I've had issues with Samsung phones, I think its something to do with the proximity sensor that's now under the glass, I'll explain as I'm getting similar and more issues on my S20 Ultra.
So last year when I had an S10+ and when I was on a call, which I mainly use my left ear (I think my right ear is a few db less so I use my left) I would quite frequently seem to activate the menu (top right) and therefore end up pressing things with my ear, unbeknown to me, sometimes I'd add a 2nd person to the call or simply put the other person on hold! This happened a lot and I was close to sending it off for repair even though I used apps to test to ensure the proximity sensor was working correctly but in the end, I sold it and got an OnePlus 7 Pro, which I didn't have an issue with. During my time with the S10+ I noticed that even though I held the earpiece to my ear I could see the screen light up and that's where I think I'd end up pressing the screen accidentally as I've just explained.
Roll on to now where I'm facing similar issues but also I'm finding if I need both of my hands and therefore use my left shoulder to keep my phone against my ear the call disconnects as if I'm hanging up. Now it seems a straightforward resolution which is not to do that but I've never had this issue before and I've tested it out quite a bit when I do this the screen isn't on and my face is nowhere near the end button!! It's really driving me crazy at the moment and annoying my other half who's normally on the phone to me when this happens!!
Anyone got any suggestions or thoughts, does it happen to anyone else or am I just being stupid??
I haven't gone down the route of resetting the phone yet but I'm going to consider it.
T.I.A
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Xode said:
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Click to expand...
Click to collapse
I did that the other day, however, when I moved the screen away I saw it light back up....
maverick1103 said:
I did that the other day, however, when I moved the screen away I saw it light back up....
Click to expand...
Click to collapse
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
View attachment 5012913
S20U-Exynos
Xode said:
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
S20U-Exynos
Click to expand...
Click to collapse
Thanks, I've already got that enabled, will just have a play around.
maverick1103 said:
Thanks, I've already got that enabled, will just have a play around.
Click to expand...
Click to collapse
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
vrgolin said:
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not yet, still having issues.