Audio Lollipop bug - Verizon HTC One (M8)

So after a few weeks of using Digital highs GPE Lollipop build I ended up having this issue where my bottom speaker will just stop functioning entirely and I'd have to reboot to fix it, I decided this was a software issue and not a hardware issue so I flashed a new ROM, Liquid smooth. Now my issue is less annoying but still unbearably frustrating, instead of a reboot required, when I listen to music or higher pitched songs it will just give out again but I can fix it by killing my music app and restarting it. I believe this has to do with lollipop and isn't related to my phones speakers being broken but what do you guys think? I'm frustrated as hell about this.

S1L3nTShaDoWz said:
So after a few weeks of using Digital highs GPE Lollipop build I ended up having this issue where my bottom speaker will just stop functioning entirely and I'd have to reboot to fix it, I decided this was a software issue and not a hardware issue so I flashed a new ROM, Liquid smooth. Now my issue is less annoying but still unbearably frustrating, instead of a reboot required, when I listen to music or higher pitched songs it will just give out again but I can fix it by killing my music app and restarting it. I believe this has to do with lollipop and isn't related to my phones speakers being broken but what do you guys think? I'm frustrated as hell about this.
Click to expand...
Click to collapse
just a thought have you tried reverting to a 4.4.4 rom to see if it fixes it? just to be sure it is not a hardware problem, i am curious how you came to the conclusion that it was not a hardware problem. if you think this because restarting the app or phone fixes it you may be mislead, could be the amp or some circuit is cutting out and then resetting have seen this in other types of amps. i could be completely off about this but it is something to consider.
if you were running 4.4.4 before and did not have the issue then that would be my suggestion. and if you find out that it is definitely software then you might want to try re installing the latest firmware again if you have not already tried this.

Azag Thoth said:
just a thought have you tried reverting to a 4.4.4 rom to see if it fixes it? just to be sure it is not a hardware problem, i am curious how you came to the conclusion that it was not a hardware problem. if you think this because restarting the app or phone fixes it you may be mislead, could be the amp or some circuit is cutting out and then resetting have seen this in other types of amps. i could be completely off about this but it is something to consider.
if you were running 4.4.4 before and did not have the issue then that would be my suggestion. and if you find out that it is definitely software then you might want to try re installing the latest firmware again if you have not already tried this.
Click to expand...
Click to collapse
First off thanks for the reply, secondly, I haven't tried converting and it only started happening a month after Lollipop use so perhaps you're right and I was wrong to jump to the conclusion. However I only thought this because using a dif ROM the issue changed from reboot required to fix it to simply restarting the app im using. Leads me to believe it is ROM related. And I'll fix my MultiROM n boot up the old 4.4.2 rom i have n see if it works properly in a bit. Will report back when I'm done.

S1L3nTShaDoWz said:
First off thanks for the reply, secondly, I haven't tried converting and it only started happening a month after Lollipop use so perhaps you're right and I was wrong to jump to the conclusion. However I only thought this because using a dif ROM the issue changed from reboot required to fix it to simply restarting the app im using. Leads me to believe it is ROM related. And I'll fix my MultiROM n boot up the old 4.4.2 rom i have n see if it works properly in a bit. Will report back when I'm done.
Click to expand...
Click to collapse
No problem, I understand how frustrating these things can be and i seen you had no replies thought I might share my thoughts.
You may be correct about it being The Rom, since after the change of rom changed what it took to reset it. Only thing that bothers me is why did it take a month before the problem surfaced, unless you added some other app that is somehow causing the problem.
Have you tried putting phone in safe mode and see if problem persists, if not it a app or something you have installed after that first month.

Related

Help! No sound after ICS update

I've been using it for 8 months without any problem (always have most updated FW). Now, since I've updated to ICS (OTA) last Saturday I have consistent audio problem - there is no sound at all (by any app). I need to restart it and get the sound back, but then after a while, it happens again. FYI, everything is stock, without root, etc.
Is it a known problem of the new ICS? Anyone has a solution for this problem?
Many thanks!
I noticed a issue with no sound. After reboot it works fine.
Sent from my HTC Sensation 4G using XDA App
same thing happened to me...asus used to be the only one who was good at updates but not lately...anyway, try backing up all your apps and going to settings and doing a full/factory reset. helped out mine with the sound issue and it hasnt happened since. see if that will work for you as well
yes,reboot or factory reset can solve the problem..
but now i cant use usb thumbdrive on dock,are u?
i dont have the dock so i couldnt tell you. usb to computer and microsd are working fine for me though
Happens to me about once a day, no sound (from media, notifications, anthing). A quick reboot solves it. I've already done a factory reset to try and solve the "reboots while sleeping", but that didn't fix either one of those issues.
mine was on silent mode after ics update something to check before a reboot, it is usually the simple things.....
A few reboots into ICS, my sound was gone. I rebooted it, and it came back. It happened again a few reboots later. Tried rebooting to fix it, but it never came back. I tried reflashing 3.1.1 again, still no go. I eventually caved and RMA'ed it on Monday. I had to unroot it
My sound has gone away twice on me. The first time was started a movie & there was no sound. I wanted to use the HDMI out anyway & I did have sound on the TV. Again last night I lost sound again & had to reboot. I never had this problem with HC.
more then likely its a hardware issue. its just a coincidence that u just upgraded. with everyone with a transformer upgrading, any problem that follows will be directly linked. I have speaker issues as u all described. I can push the bottom of my tab and my speakers cut back in once I loose sound.
get a bluetooth speaker or send it for Rma. I went with the first option.
I don't think it's a hardware issue (at least in my case) - I've never had this problem before ICS update, and the problem will go away right after a restart. It sounds to me a firmware problem; probably some conflict between the new ICS with existing apps
Honestly, I'm quite regret to have it updated...
I'm having the same issue too (intermittent loss of audio, returns after reboot) - definitely related to firmware/software, not a hardware issue.
Sent from my GT-I9100 using xda premium
pigacc said:
I don't think it's a hardware issue (at least in my case) - I've never had this problem before ICS update, and the problem will go away right after a restart. It sounds to me a firmware problem; probably some conflict between the new ICS with existing apps
Honestly, I'm quite regret to have it updated...
Click to expand...
Click to collapse
Do a factory reset and cold boot.
You can't expect all your honeycomb apps to work on ICS without causing issues.
Avoid doing that reset + cold boot.
After two of them + several other tries, my sound keeps mutting.
Lets hope the update fixes this.
I too have this problem after ICS update. I noticed, sometimes after I put into silent mode, it stay muted until a reboot.
I do believe it is ics firmware issue, Tf201 get fix with lastest build so I hope Tf101 get fix too.
Yep, I get this as well. Shame!
Firmware related most likely. Mine is doing it too. A reboot fixes the issue. Hard reset won't likely correct the issue as I did a factory reset prior to installation. Possibly a piece of software causing it, but I am not going to mess with it as I only have 1 program installed.
After the update to ICS, my daughter's TF201 no longer has any audio.. speakers or headphone.
I've done the factory data reset and the data wipe. No change. Sadly, I have an RMA and hope they can figure it out. Before I ship it off, do you have any suggestions?
Thanks.
Just another 'me too' post. I have 2 transformers in the house. Upgraded one (a B80) to revolver and lose audio a few times. Reboot brings it back. When it goes away, no sound from speakers or headphone jacks. Next time it happens I'll try and grab a logcat.
Haven't tried it on my older rev TF yet, I think i'll hold off a bit.
The B80 was wiped and done with a clean install. User apps restored via TB, but no settings were carried over from HC.

[Q] Softkey Issue

Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...

LTE turning itself off? [updated]

This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
-[edit++]-
It appears it was an issue with Juice Defender. Will update if issue persists.
Sonic Offline said:
This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
Click to expand...
Click to collapse
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
RevelationOmega said:
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
Click to expand...
Click to collapse
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Sonic Offline said:
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Click to expand...
Click to collapse
Yes, saving battery by turning it off. Keep updated.
RevelationOmega said:
Yes, saving battery by turning it off. Keep updated.
Click to expand...
Click to collapse
It appears that was what it was. I have had zero issues since uninstalling it, which makes me sad. I liked Juice Defender, and have been using it on my phones for several years. :c

[Q][H]Touchscreen issue

Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Nikouy said:
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Click to expand...
Click to collapse
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
You_got_owned123 said:
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
Click to expand...
Click to collapse
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Happy to know I am not the only one having this issue , good that we are on the same boat.
I'm travelling in a few days and can't go abroad with the phone in this "working" conditions so I will have to downgrade for sure. Any 5.0 ROM to recommend? A solution for 5.1 would be better
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
guih said:
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
Click to expand...
Click to collapse
I flashed Slim ROM, touches delay improved a bit but I was experiencing some lag on the hardware keys.
I just flashed last bacon firmware (from April 09) and RobbieL811 ROM and seems to be running smoothly, I wonder if it was a firmware issue. Thoughts?
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Infinityyy said:
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Click to expand...
Click to collapse
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
gsmyth said:
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
Click to expand...
Click to collapse
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Infinityyy said:
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
Click to expand...
Click to collapse
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Nikouy said:
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Click to expand...
Click to collapse
we're not alone man, multiple threads are popping up with people suffering from similar issues, including on reddit: http://www.reddit.com/r/oneplus/comments/33ky0u/open_post_to_oneplus_with_all_our_love_and/
I am having the same severe issues as well.
The nightmare begun after the 05Q update.
Ever since that update, no matter what I've tried, the touch problem is here.
I've tried numerous Roms + kernels combinations with no use.
OP support was trying twice to reset my phone to full factory reset to both Oxygen & CM11s with no use.
That is so frustrating.
i have the same problem, but only when i go outside and the weather is nice

Desperate for help

Hey guys!
I have posted before but since then the issue has exacerbated to the point where I'm at my wit's end.
I have the SM-P907A AT&T version of this tablet. I bought it second hand and started experiencing issues almost immediately, although nothing as bad as what I'm going through now.
It began with the odd blue-screen and very rare restart. It quickly escalated when I created multiple profiles (user ids). The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Thusly, I factory reset my tablet and hoped that would fix the issue; to no avail. Then I decided to Odin flash the stock ROM. Again no joy. Restarts were persistent and regular when the tablet wasn't connected to a power supply. I then rooted the tablet, installed Titanium Backup Pro and proceeded to freeze all apps/odex-es related to Samsung Knox. As some have posted, doing this helped them out. Not lucky enough, I guess.
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
No, proppably not
kalaris said:
Hey guys!
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
Click to expand...
Click to collapse
I don't think that using the multi user functionality has anything to do with the issues you are experiencing. I have 3 user on my tablet and using it for a year now. Both on KitKat and Lollipop that I am using now. Both rooted, KitKat with Xposed also. Never had issues with blue screens and reboots.
Issues with US devices have been posted regularly and explanations have been posted. Don't focus on multiuser for the issues you experience.
I' am using the SM-P905 International version (EUR)
PDA: P905XXUABOG1
CSC: P905EURABOG1
Ridiculous
Okay guys. Seriously ridiculous. I downloaded the lollipop ROM but got an error when adb sideloading it because it requires the previous firmware P907AUCU1ANK2 for it to update properly whereas I have the one older than that: P907AUCU1AND7.
Can someone help a brotha out? Post a link from where I can download it?! Maybe share their stock rom file?! Pretty please? I've managed to find only TWO results on google. One is a mobilefileserver result requiring that I Pay $60. The other is a Chinese site requiring that I pay significantly less but in a way which is baffling me at the moment.
Any good guy out there who can help??????
A member posted links to it in 5.1.1 upgrade posts...
Sent from my SPH-L300 using XDA Free mobile app
zomg! thank you! how'd i miss this?!
kalaris said:
The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Click to expand...
Click to collapse
Random restart is the problem of cracked battery connector. Re solder the battery connector will fix it permanently.
Read the thread " Flickering Screen " in Galaxy Note or Tab Pro, you will see they all have similar problem like yours and the fix is simple.
No software or upgrade will fix the hardware problem, regardless Kitkat or Lollipop.

Categories

Resources