Hi, I'm having a re-occurring problem with my in-call volume randomly getting stuck on maximum regardless that the volume is turn down to min. I've tried rebooting w/ and w/o taking out the battery, restoring and reflashing. Nothing seems to stick. Is there a patch I've missed about this or a thread I've overlooked? I've searched around and only came across some really old posts for another model experiencing anything like this. I'm currently running LeeDroid 3.1.6 ROM flashed with the latest LeeDroid kernel and all the mods.
Yours Noobly,
Panz
Related
ok i already searched this and i googled it many times but still havent found anything.
i have cyanogens 3.4 rom and the hero 1.2 theme with apps to sd.
so every once in a while my phone keeps setting itself to the ringer without me pressing anything, i notice this because i always have it on vibrate,
can anyone direct me to a fix??
thanks
Many are having problems with G2x turning off, but i am havint trouble makeing it turn off since getting one with 2.3.3 on it.
I have used both xboarder56 (unmodified except for root OTA) and EB 2.3.3 latest two versions. When I try to turn it off, it starts the shutdown with the TMo animation and jingle, and then opens up the home screen - which is frozen.
Everything else works OK - wondering if anyone else has encountered this?
gaww said:
Many are having problems with G2x turning off, but i am havint trouble makeing it turn off since getting one with 2.3.3 on it.
I have used both xboarder56 (unmodified except for root OTA) and EB 2.3.3 latest two versions. When I try to turn it off, it starts the shutdown with the TMo animation and jingle, and then opens up the home screen - which is frozen.
Everything else works OK - wondering if anyone else has encountered this?
Click to expand...
Click to collapse
I am updating my post this way to get it on top again (response has been overwhelming so far).
I also noticed when the home screen comes back up, it notifies that is is now safe to remover the SD card, and a SD Card Icon appears in the status bar. The status bar is active, but everything else is frozen.
I've been having a kind of weird problem I have been having lately since I flashed ARHD 3.0.3. It seems that 90% of the time I either make or accept a call, my phone will automatically turn "Speaker On" and I will get the notification right over my speakerphone soft key on the dialer as if I had pressed it myself.
I have tried a few different things to get this problem resolved, but to no avail. I'm currently using Volume+ to increase my phone's speaker volume and have uninstalled the app to see if that was the cause; it wasn't. I also did a full wipe and new flash with the superwipe script in CWR. I am currently running ARHD 3.0.3 with the DC v0.5 (although this problem was also present in v0.4). I can't seem to find what this problem is caused by, and as I haven't seen or heard of anyone with a similar problem in the development thread, it's very possible that it's not the fault of the ROM or DC script.
If anyone is also having this problem or has any insight into why the phone would do this, let's me hear from you so we can try to figure out what the source of this problem is. Thanks guys
I run Android Revolution for the Desire HD, and I too have to exact issue you describe above. I have checked I am not pressing the speaker button with my cheek by not lifting the phone to my face for a few seconds but almost immediately after answering or placing a call the speaker automatically comes on. Its very frustrating (I also used Volume+ app a while ago when I broke the volume buttons on my phone but I got new buttons a while ago so the app was uninstalled)
Michaelearljohansen said:
I've been having a kind of weird problem I have been having lately since I flashed ARHD 3.0.3. It seems that 90% of the time I either make or accept a call, my phone will automatically turn "Speaker On" and I will get the notification right over my speakerphone soft key on the dialer as if I had pressed it myself.
I have tried a few different things to get this problem resolved, but to no avail. I'm currently using Volume+ to increase my phone's speaker volume and have uninstalled the app to see if that was the cause; it wasn't. I also did a full wipe and new flash with the superwipe script in CWR. I am currently running ARHD 3.0.3 with the DC v0.5 (although this problem was also present in v0.4). I can't seem to find what this problem is caused by, and as I haven't seen or heard of anyone with a similar problem in the development thread, it's very possible that it's not the fault of the ROM or DC script.
If anyone is also having this problem or has any insight into why the phone would do this, let's me hear from you so we can try to figure out what the source of this problem is. Thanks guys
Click to expand...
Click to collapse
I think I posted a thread about this same issue the other day, I had he same issue and thought it was the ROM but I found out from someone on here that GOsms pro had a bug(app updated fixing it) where the speakerphone automatically turned on. So try that if you use GO, if not then I'm not sure!!
Sent from my HTC Sensation Z710e
thebowers131 said:
I think I posted a thread about this same issue the other day, I had he same issue and thought it was the ROM but I found out from someone on here that GOsms pro had a bug(app updated fixing it) where the speakerphone automatically turned on. So try that if you use GO, if not then I'm not sure!!
Click to expand...
Click to collapse
I'll give that a shot. I am currently using GO, so maybe uninstalling/reinstalling the newest version will help. I'll post my findings.
Sent from my HTC Sensation 4G using xda premium
Hello,
my tablet is producing a very loud "pop" noise when speaker turns off (ie. after any sound). Galaxy Nexus seemed to have the same (hardware) issue, but I believe that mine is caused by software, as it started after I flashed CyanogenMod 10.1 (latest nightly). I'm running following setup right now:
DhollmenCM (but I flashed cyanogenmod over it, not sure if it's still here)
CyanogenMod 10.1 latest nightly
GApps for CM 10.1
Before installing CM everything worked well (but the original ROM is **** and I need profiles). How am I supposed to fix this?
I've had that before as well. Do you by chance have any audio enhancing software installed besides DSP Manager? Programs like Volume+ are notorious for this.
DSP Manager has everything disabled, nothing else is installed.
First I would try to remove DSP just to see if that's the problem.
Here is a simple app that I use to remove apps that the ROM's have in them that I don't want. I usually do it after I flash because I don't feel like opening the ROM on the computer and removing them ahead of time.
https://www.dropbox.com/sh/u4wijb1zwzdd3pn/4TyYtOpd1x
If removing DSP doesn't solve your issue and you didn't have this problem previously, I would reflash wiping "everything" before flash, including data. Since at that point there would be no way to be certain what is causing it. I don't believe the kernel could be the problem as I am running CM10.1 and the Dhollmen kernel as well and don't have any issues.
I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.
pzduniak said:
I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.
Click to expand...
Click to collapse
But did you wipe the system before flashing?
This is critical to make sure you have a clean installation, without it there are pieces that get left behind and cause all sorts of issues. If you have wiped, then it sounds like you have developed a hardware issue. Did it get dropped any time recently?
pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!
mtran2988 said:
pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!
Click to expand...
Click to collapse
I had been having this popping problem for a while now, and Google brought me here. I went ahead and changed the lpa.decode to false like you suggested and it worked like a charm! Thanks mtran2988!
Hey guys, I've been having this issue for weeks and it seems that it doesn't matter what ROM I'm on.
All sound will inexplicably drop out. I mean system sounds, the ringer, notifications, music, in-call, podcasts - everything. Nothing in particular seems to trigger it and sometimes it eventually just comes back on it's own. It seems that sometimes I can get it to come back on by turning the volume up and down repeatedly (may just be a coincidence though). This occurs multiple times a day.
I've tried numerous 4.3, 4.4, and even 4.2.2 sense ROMs, and it still occurs. Pretty annoying because what good is a phone that never rings or notifies you, and you can't even talk to people when you dial them.
I can't confirm this, but this may have all begun when I updated my hboot to 2.15 for the new 3.4 kernel based ROMs. Can't quite remember because it's been like this for quite awhile now.
Anyways, if anyone has any ideas it would be greatly appreciated. I'll try to post a logcat the next time it happens.
DRUMROT said:
Hey guys, I've been having this issue for weeks and it seems that it doesn't matter what ROM I'm on.
All sound will inexplicably drop out. I mean system sounds, the ringer, notifications, music, in-call, podcasts - everything. Nothing in particular seems to trigger it and sometimes it eventually just comes back on it's own. It seems that sometimes I can get it to come back on by turning the volume up and down repeatedly (may just be a coincidence though). This occurs multiple times a day.
I've tried numerous 4.3, 4.4, and even 4.2.2 sense ROMs, and it still occurs. Pretty annoying because what good is a phone that never rings or notifies you, and you can't even talk to people when you dial them.
I can't confirm this, but this may have all begun when I updated my hboot to 2.15 for the new 3.4 kernel based ROMs. Can't quite remember because it's been like this for quite awhile now.
Anyways, if anyone has any ideas it would be greatly appreciated. I'll try to post a logcat the next time it happens.
Click to expand...
Click to collapse
No idea? How come I seem to be the only person with this issue? Haha
I'm currently using Dark Jelly S 28.1 (the last version with the 3.0 kernel). Seems to be a bit better. Anyone have any links or zips of other 3.0 based ROMs? The lionks in all the threads are dead. Guess they took down the zips when everyone started switching to 3.4 and 4.3/4.4.
DRUMROT said:
No idea? How come I seem to be the only person with this issue? Haha
I'm currently using Dark Jelly S 28.1 (the last version with the 3.0 kernel). Seems to be a bit better. Anyone have any links or zips of other 3.0 based ROMs? The lionks in all the threads are dead. Guess they took down the zips when everyone started switching to 3.4 and 4.3/4.4.
Click to expand...
Click to collapse
Well I tried some other 3.0 roms thanks to some very helpful people in another thread I created http://forum.xda-developers.com/showthread.php?p=48029123#post48029123 but I am still having sound issues.
I tried reflashing the 2.15 firmware and the sound was back until I received a call. After I hung up, I lost all sound.
I'm not very knowledgeable when it comes to this stuff, but I ran a logcat and noticed a view errors relating to sound (SoundPool: error creating audio track, Audiotrack: could not get audio output for stream type 1, AudioPolicyManagerALSA: getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION, etc). Not sure what this means or how I can go about fixing it. Looking at running an RUU to see if that will help but I'm on Linux so it's a bit more complicated than just running the .exe and I'll have to reroot anyways so hopefully someone can shed some light on this for me. Attached is a log showing the errors.
I am having the exact same problem with my HTC one S. For no apparant reason all sounds stop (speaker, music, notifications, can't make or recieve phone calls)
My problem started when I was running stock software. It got so bad that I had no choice but to S-OFF, Root and install a custom rom to see if that solved the problem. I currently am running MaximusHD and I love it. But the problem is back.
After searching throught the logs there seem to be two main errors "failed to enable the mixer controls for the speaker" and "AudioPolicyManagerBase(261)".
Does anyone have any idea of how i can disable or reinstall the service that is tied to this?
Bump... I also seem to having this problem. I'm running stock rom, rooted. S-On.
Randomly, my audio stops working. Sometimes a reboot fixes it, sometimes not. Sometimes a hard reboot (holding power down) works, sometimes not. More often than not, rebooting to recovery, then booting sytem fixes it.
I know it's not hardware because during this occurrence, some software (e.g, google voice search) gives an error but runs fine when things are normal.
I tried looking at logcat (I'm new at this) but nothing jumped out. Would love some help getting to the bottom of the problem as it's really annoying to randomly not be able to answer calls.
So this problem is happening more and more to my phone. Since my post earlier this month, I've tried Stock rom, liberty rom, and CM11, and the no-audio problem happens randomly on all of them.
This is really frustrating, as it makes the phone unusable. I'm very close to giving up and just getting a different phone.
Interesting find... I removed Lookout Security, and this appears to have solved 80-90% of the problem.