[Q] "Speaker On" in Android Revolution HD 3.0.3 - HTC Sensation

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

Related

[Q] Package installer won't work... can't press button

I just upgraded to cm7 and now sometimes when I try to install an app from an apk file it wont let me hit the install button.
If I am using Amazon appstore it works, the same type of screen comes up and I can install stuff. But when installing from a downloaded apk (like from here) the button just doesn't work... it isn't greyed out or anything but is simply unresponsive.
Sent from my CM7 SCH-i500
Hey I have this same problem, did you ever figure out this issue? Thanks!
Please let me know if anyone knows how to fix this issue, I'm having the same problem
Bump this
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)
Hi all, I'm facing the same problem, but I don't have screen filter installed. What else have you tried?
Here's my main post about this.
I've also heard that Juice Defender can cause this problem. Sadly, like you, I still can't fix it on my phone!
Anyone?
AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.
I can confirm: disabling TEAM Battery Bar solve the problem! thanks
Arcangel Loki said:
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)
Click to expand...
Click to collapse
Thanks, that fixed my problem on my Galaxy S2 with LPQ ICS rom. Probably should report it to the dev for fixing...
in my case Juice Defender was a problem, since I don't have any screen filters installed
uninstalling Juice Defender fixed my phone
EDIT Friend of mine has the same phone (SGS2) with the same ROM installed, JD never caused any problems with his phone
The only difference between my JD settings and his - I got brightness control enabled, so maybe that was a problem, not JD itself
Arcangel Loki said:
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)
Click to expand...
Click to collapse
I'm currently on SGS2 rooted stock LPQ and just figured it out myself that Screen Filter is actually doing something so that the install button cant be pressed. Has anyone informed the dev?
Edit: just mailed the dev of Screen Filter hoping for confirmation and fix
'Lux Auto Brightness' is causing the same issue, so seems that all the applications trying to adjust screen brightness will cause the issue.
By the moment I disable it, I am able again to install apks... really weird
Also, not clear why only the install button is effectively disabled, as cancel bitton works and the 'show all perms' drop down , also works
kjdiehl said:
AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.
Click to expand...
Click to collapse
Good call! That was the exact app that was causing me problems as well. Here's hoping to a quick fix!
sageDieu said:
I just upgraded to cm7 and now sometimes when I try to install an app from an apk file it wont let me hit the install button.
If I am using Amazon appstore it works, the same type of screen comes up and I can install stuff. But when installing from a downloaded apk (like from here) the button just doesn't work... it isn't greyed out or anything but is simply unresponsive.
Sent from my CM7 SCH-i500
Click to expand...
Click to collapse
"Upgraded"
Sent from my XT912 using xda app-developers app
Thank you
kjdiehl said:
AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.[/QUOTE
i encountered the same issue and after reading your post and searching hard on my n7000, i finally found what causes it...on my n7000 it was glove box. After uninstalling my phone is back to normal again
Click to expand...
Click to collapse
Thanks for all the infos, guys. For me, it was both Lux Auto Brightness and Twilight. I disabled them using task manager and everything went smoothly from that. Explains why no matter how much I reboot, it doesn't fix things. I also have avast Mobile Antivirus installed and it has a constant display notification but it doesn't cause any issues. I am guessing it has something to do with code wired to the phone's hardware? As all the apps causing problems had to do with overlapping device setting control over screen brightness or hue.

[Q] Deactivate the Search-button?

My search button is flickering, firing itself off in bursts, and I want to completely deactivate it. The flickering was/is apparent in Clockwork recovery --> Key test as well.
It first happened using a 2.3.4 deodexed rom (been using it for a month or so, but all of a sudden it started firing off), then I flashed a CM7 based rom which completely killed the button. I figured it was a hardware issue, but to be sure I flashed an ASOP rom (ZuluZulu) and after a couple of hours of use the search button button started firing off again. Between the periods of bursts, the button is as dead as ever, meaning it's lit, but does not respond (haptic feedback, opening the search app) at all.
Since I don't use the button at all, deactivating it completely would not only resolve the issue but save me the trouble of accidentally hitting it once in a while as well
I've searched a bit and found this answered thread over at Google: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
TS 4/21 said:
I have a nexus s running 2.3.3 and I will be using it normally and all of a sudden it will start a voice search without reason but, it opens and closes it really fast for as long as it wants. It only stops when I lock the phone and it does it in all my apps. I don't want to have wasted my money on a p.o.s phone just cause i can't stop it from wanting to search. Help it happens all day and more than ten times a day.
Click to expand...
Click to collapse
Google 6/3 said:
Hello again everyone,
Good news -- we've identified the source of this problem which is entirely software based. We're developing a fix which we can deploy with an over-the-air update. I don't have a timeline for when that'll happen yet, but when it's ready I'll let you know.
Click to expand...
Click to collapse
I don't know if it has anything to do with anything as not even wipe + re/flash different roms changes it though.

Phone freeze during incoming call or end call

As title, any one encounter the issue? Sometimes cannot answer phone call since the phone freeze with lock screen. And also sometimes I cannot end call since the screen is freeze. Anyone encounter the same issue? Can share your comment here? Or Workaround? Thanks for any help
Same issue here, bezel and mainboard changed and the problem persists, canĀ“t be bothered to send it back a third so i use the "No Lock" app, bad workaround but at least im sure i can answer calls now..
It only fails when it has been idle in my pocket for awhile and a call comes in.
Do You use custom ROM or Stock? Which version?
Do you have your phone underclock while its screen off? If yes, what CPU controller youre using?
Sent from my HTC Sensation 4G with Beats
I'm on stock and have the problem even after hardreset and no apps installed.
This is a common problem and no solution for it, i'm hoping on ICS.

No audio after deep-sleep

Hi to all,
I'm using revolver 4.2.0 ROM on ASUS TF101. I've noted that the audio does't work after deep sleep. It happens often If I use skype.
I have to restart my device every time.
Has anyone observed this kind of bug?
Thanks
http://forum.xda-developers.com/showthread.php?t=1523358&page=4
Solved
Thor_Asgard said:
http://forum.xda-developers.com/showthread.php?t=1523358&page=4
Click to expand...
Click to collapse
Solved updating to JB AOSP. Seems to happen only with Skype working in background.
Thanks
I've installed skype once on my TF101... I'll look tonight if it's still installed ! It was a long time ago, and i've done a few reset since then !
We just have to wait for Asus to release JB so lol
edit : skype uninstalled ! I'll see if I still have sound problem...
No issue this weekend... so far so good !
Thanks gianoct for the tip !
I've spoke too fast.
For one week now, I reboot twice a day to have sound back !! :crying:
This is happening to me too (AOKP JP and CM10), with Skype not having ever been installed. If I reboot, the sound will work flawlessly, but when I turn the screen off I'll hear the lock "click", and when I turn the screen back on I'll get a garbled half-click unlock, and no sound thereafter until a reboot. Going to grab a logcat tonight and see if I can at least figure out a kernel or framework error to work from.
Ok, let us know what you find in your investigations...
Thor_Asgard said:
Ok, let us know what you find in your investigations...
Click to expand...
Click to collapse
I've temporary solved coming back to ICS, withe revolver ROM.
It doesnt' happen as often as before, but sometimes (one time at week) the device is completally mute and I've to restart it.
I don't konw why.
Thanks to everyone for the support.
gianoct said:
I've temporary solved coming back to ICS, withe revolver ROM.
It doesnt' happen as often as before, but sometimes (one time at week) the device is completally mute and I've to restart it.
I don't konw why.
Thanks to everyone for the support.
Click to expand...
Click to collapse
I've had this with the stock rom and it's persisting with revolver. Generally seemed to be related to the issue with touchscreen sensitivity being *#@! after deep sleep, though at least touchscreen seems a LOT better with revolver - haven't even had to use the app which fixes that yet.
Found a solution. With the KAT kernel and K.A.T. app you can reinit the DSP and audio comes back! This kernel works with CM10, don't know about revolver

[Q] All sound dropping out

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.

Categories

Resources