This is more of a "what the hell happened" post, more than it is a question or answer.
So i seen this happening to the normal pixels, but havent seen a report for the XL. I was at work when i decided to take the latest update during lunch. after eating i glimpse at my phone to see "update failed", i thought this was odd because as i mentioned earlier, only the smaller variants were receiving this problem. I paid it no attention and just thought to myself "ill factory flash the image later". Break time was over and it was time for me to get to work, i threw my (wired) headset in and played some music to find that my volume at max was only playing at about a quarter of what it usually does (weird). didnt have time to mess with it so i dealt with the abnormally low volume. it wasnt until i got off i went to play a video on facebook, i realized i didnt have media volume!!
After playing around for a second, i found out my pixel had lost ALL OUTPUT as far as noise was concerned. no ringtones, notifications, media, calls, nothing. THought it could have been a rogue app hogging something, so i uninstalled almost everything. I tried restarting, i tried clearing cache, nothing worked. i was messing around with source and compiled a rom for the pixel the other day and said "why not try flashing it". flashed it, still no volume. at this point i grabbed the latest image and allowed it to wipe and flash everything. i now have my volume back. anyone know what could have went wrong?
My wife's small Pixel lost all sound after an ota. It was a verizon phone with bootloader unlocked and rooted, so I was surprised it even took the update on its own. I tried flashing older images, the beta, safe mode, and everything I could think of. Google exchanged it (which was a win because they sent her a google store pixel, not another verizon one)
noidea24 said:
This is more of a "what the hell happened" post, more than it is a question or answer.
So i seen this happening to the normal pixels, but havent seen a report for the XL. I was at work when i decided to take the latest update during lunch. after eating i glimpse at my phone to see "update failed", i thought this was odd because as i mentioned earlier, only the smaller variants were receiving this problem. I paid it no attention and just thought to myself "ill factory flash the image later". Break time was over and it was time for me to get to work, i threw my (wired) headset in and played some music to find that my volume at max was only playing at about a quarter of what it usually does (weird). didnt have time to mess with it so i dealt with the abnormally low volume. it wasnt until i got off i went to play a video on facebook, i realized i didnt have media volume!!
After playing around for a second, i found out my pixel had lost ALL OUTPUT as far as noise was concerned. no ringtones, notifications, media, calls, nothing. THought it could have been a rogue app hogging something, so i uninstalled almost everything. I tried restarting, i tried clearing cache, nothing worked. i was messing around with source and compiled a rom for the pixel the other day and said "why not try flashing it". flashed it, still no volume. at this point i grabbed the latest image and allowed it to wipe and flash everything. i now have my volume back. anyone know what could have went wrong?
Click to expand...
Click to collapse
At least you are knowledgeable enough that you were able to flash the factory image and get your phone working again. Since the Pixel is being marketed to a more mainstream crowd a lot of people likely would have had to RMA the phone. Pixel support will never tell you to unlock the bootloader and flash the factory image. As for what went wrong, something was clearly corrupted when the OTA failed so it must have partially installed before things went wrong. I've had problems like that when flashing custom Roms and the only remedy I've ever found was wiping everything and doing a clean install.
Updated successfully to July security patch yesterday (OTA), no issues... it's smooth
Sent from my Pixel XL using Tapatalk
Just bumping up this thread once more because it happened again. Took august update, rebooted, no media sound.
Calls work, ringtones, all bt and wired sounds work, but no main speaker media sound.
Cleared cache and dalvik, uninstalled any app that wasn't factory, done everything besides a factory reset.
Can't really do the factory reset right now, as I'm not at home, and I'm not comfortable being in a situation where my PC isn't accessible (in case it ****s up).
Any ideas?
Related
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
jedijackie said:
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
Click to expand...
Click to collapse
Well, you've tried everything I would've suggested...tried different kernels, flashed backed to sense, performed a full wipe, etc. I would think that flashing back to stock would've alleviated the issue if it was software related. Perhaps your speaker is starting to fail? I've seen many people reporting needing to replace the speaker. However, it is indeed odd that its intermittent, you'd think that if the speaker was failing, it'd be consistent, and a reboot wouldn't clear it up. Odd, but I don't know what else to suggest. Have you tried tweaking the settings using DSP manager at all? If all fails, and being on stock sense doesn't fix it, I'd unroot and have it looked at by Sprint probably.
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You definitely seemed to try just about everything but did you flash a Stock RUU? I'd nandroid backup and flash it to see if the problem still exists, if you've tried that then you would only have one option left, take it to BB. Best of luck either way.
Huh... haven't tried a Stock RUU. Good call! I'll try now and report back. Thanks Blake.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You're welcome, sorry there isn't more I can suggest. As Blake said, run RUU to unroot, which I would do before you take it in anyways. (What I meant when I said "unroot and take it in). If its still out of wack then, take it in.
Sent from my PC36100 using XDA App
I attached the Stock rooted RUU but visiting HERE should return you to unrooted stock evo.
Hi,
I have an issue that started happening a few weeks ago. I would be using Google Music and listening to a CD (stored locally on my device), and then then the songs would start randomly changing...sometimes it would happen every few seconds...sometimes several times within a second..(as if someone had control of my device). When I go to stop google music (by hitting the X), it would start back up and start playing. [It will NOT jump outside of the playlist/cd selected....and it won't always skip in order....]
I rooted my phone a month or two had have been running EclipticOne6 [Keeping up with the latest releases]...with no issues until a few weeks ago [I thought it might have initially been related to constantly switching skin packs...]
I then went and tried wiping my device [Factory Reset...and even Advanced Wipe (everything including Internal storage)].and doing a fresh full install of 4.4...but that didn't fix it.
Last weekend i wiped it again and a completely new rom [Santod040's stock rom (updated 6/11/14)] and was fine for a few days, then it started reappearing. I've not installed any new programs....it's not constant.....but it's SUPER annoying.
Everything else works just fine on the phone.
Few things I've tried/Notes:
Doesn't happen all the time (sometimes it'll be fine for an hour....sometimes it'll happen almost immediately)
Rebooting/clearing cache doesn't appear to have an effect (no worse/no better)
I even tried another music app (AIMP)...and it did the same thing [In case this was related to some google service]
I've tried disabling any other running programs [Using Greenify and SDMaid]
It doesn't appear to be tied to a "timed" event....ie...doesn't happen every "5" minutes [Like a program wakes up and trips it]
I do use TIBU to restore apps/data (have been using this for years)
Lately, I've been Google restore my apps/settings when setting up the phone with each rom update
Once right after this happened I opened up MX Player (for video)....and the same thing happened....
I'm not new to rooting/unlocking/roms [been beating the heck out of many devices over the years ]
I've done a bunch of searches but can't seem to get a hit related to this
This will happen if I'm holding my phone still (so I don't think this is related to touching the volume button or activating something in my pocket.).....??
Anyone have thoughts / things to try? My next attempt might be to do a factory reset, and wipe everything and start from scratch...but that's a bit drastic. Or worse yet....return it to Verizon and have them give me a new phone (unrooted/locked)....
Thanks in advance,
Rez
Try the decrypted RUU in development section. It could be a bad partition screwing things up and an ruu is the only fix for that.
Sent from my HTC6500LVW using XDA Free mobile app
I had the exact same issue before. And it only happens when I have headphones in. I think its a ROM issue. I havent had it happen in a while though. Im using Nusense
For about a day now my m8 has been having some strange audio issues, and since I haven't found any other discussions surrounding it, I thought I'd drop in here as a last hope.
Essentially, almost any audio that plays from the internal speakers freezes the phone and forces me to soft reset it. Any games/music/videos locks it up, but notification/ringtones play without issue. When I try to play music, the boomsound icon appears in the notification bar, and I can change the volume for about a second before the phone freezes, though no music actually plays.
It seems to have started after I downloaded Sherlock: The Network(which I have since uninstalled), but that may be coincidental. I have a Verizon m8, rooted with S-OFF but stock ROM. I'm backing up things right now in preparation of a factory reset to hopefully resolve the issue, but if anyone has any solutions or suggestions, I'd be more than happy to hear them - can provide more info if needed.
Another edit since I'm now remembering info I was going to originally add: I did an audio test via HTC's Diagnostic Tool - which was hard enough to reach because touch tones would freeze it all up - and could not hear any of the sounds it was apparently making.
Use Titanium to freeze the suspected app, and see if the issue persists.
redpoint73 said:
Use Titanium to freeze the suspected app, and see if the issue persists.
Click to expand...
Click to collapse
I should have noted in the OP (in fact, I'll edit it in now) that I uninstalled said app as soon as the issues began. I've also checked through the running processes in hopes of finding some sound driver that wasn't responding, to no avail.
This started happening to me after installing/uninstalling Hungry Shark. Did you end up doing a factory rest? 3-4 resets a day are quite annoying...
davidwnbrgr said:
This started happening to me after installing/uninstalling Hungry Shark. Did you end up doing a factory rest? 3-4 resets a day are quite annoying...
Click to expand...
Click to collapse
Yup, in the end I had to do a factory reset and didn't reinstall the app (though I'm not sure that was entirely the source of the issue). I've had no problems with the audio since, but I know how aggravating it is to deal with.
Bought 2 Pixel Cs, one seems to have died on me. I got an error while updating Play Services, but after a couple retries it went through. All my apps finished downloading and everything was dandy. I plugged my tablet in to charge for a while and when I booted it back up it had the No Command screen.
With some Googling I found how to wipe cache and wipe data/factory reset, but neither has seemed to have any effect. Every reboot goes into No Command.
If anyone has any advice, I'd appreciate it. I really don't want to have to RMA.
edit: Well, I called Google and they're sending me a replacement, next-day. I'm sad I'm having to replace it, but I can't complain about the service. It was great.
Tallon29 said:
Bought 2 Pixel Cs, one seems to have died on me. I got an error while updating Play Services, but after a couple retries it went through. All my apps finished downloading and everything was dandy. I plugged my tablet in to charge for a while and when I booted it back up it had the No Command screen.
With some Googling I found how to wipe cache and wipe data/factory reset, but neither has seemed to have any effect. Every reboot goes into No Command.
If anyone has any advice, I'd appreciate it. I really don't want to have to RMA.
edit: Well, I called Google and they're sending me a replacement, next-day. I'm sad I'm having to replace it, but I can't complain about the service. It was great.
Click to expand...
Click to collapse
Same issue here. Got my Pixel C (64GB) two days ago, just using it with standard apps, no rooting, nothing. Suddenly it reset and now boots into no command, too. Can not boot into recovery mode, nothing helps. Always ends up with same message of "no command". (And no USB recovery, apparently, for the Pixel C, at this time).
Wondering how many there are out there?
Baffles me that Google devices always have issues, this should not be happening. Apple and Samsung are never this bad with quality control.
jamesrick80 said:
Baffles me that Google devices always have issues, this should not be happening. Apple and Samsung are never this bad with quality control.
Click to expand...
Click to collapse
Quality control?
Pfft!
Btw OP the No command screen IS the recovery mode. If you would've just hit all three buttons you would of known that.
This all seems like use error to me, and nothing to do with quality control or bad products. Hell if you could follow directions you could've flash the factory images and fixed any issue you were having.
Sent from my iPhone using Tapatalk
superchilpil said:
Quality control?
Pfft!
Btw OP the No command screen IS the recovery mode. If you would've just hit all three buttons you would of known that.
This all seems like use error to me, and nothing to do with quality control or bad products. Hell if you could follow directions you could've flash the factory images and fixed any issue you were having.
Click to expand...
Click to collapse
I'm not sure how it could be user error when all I did was log in to my new device and tell it to download the same apps that are on my 6P (by following the on-screen instructions). I have no desire to flash or root or any of that.
My replacement came two days later and has been humming along fine. This is some really quality hardware.
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!