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
Related
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
Hi everyone, I was just wondering if anyone else has had a problem with notifications going silent on CM7?
I searched and found a couple of threads about the issue, but no fix or workaround was mentioned.
I had the problem before on my EVO as well, so I wonder if it's an app I'm installing. The only constant between the 2 phones was CM7. I have tried updating to the nightlies and it still occurs.
Basically, I boot up my phone. Get a message or email notification and all is working well. I then go about my day and notice I have a few more messages but no sound was made. Now notifications will remain silent until I reboot once more, and the cycle starts all over again. Sometimes they work longer, sometimes I get 1 notification and all others are silent again.
What I've tried:
I tried messing with a profile to see if that was causing issues. No go...
I have tried switching to Oxygen which worked great but I had to switch back to CM7 because MMS did not work for me at all on that rom. MIUI also worked well but I have some contacts I like sending directly to VM and their DND did not allow that, just silent ring and answer/hangup, so back I go to CM...
Can anyone help me out?
Thanks so much!
I did notice the same thing on my Nexus S 4G! I was running CM7, as well. And a reboot seemed to fix it.
Never solved what caused it, but it didn't happen often enough to where it was a big concern of mine.
Yea a reboot fixes it for me too, but then it will happen again. I wonder why that is. Maybe it's something I'm doing?
Did you guys ever find a solution for this aside from rebooting? This has happened to my samsung infuse (running on infused 1.5) a few times already and it is pretty frustrating. I believe it's happened a few times on the stock rom as well. I've tried uninstalling programs one by one to see if I can find the culprit, but no dice. It just doesn't happen consistently enough for me to pinpoint the app or problem. Thanks in advance!
Seems to be somewhat common but no fix to be found...
Using CM7.1
Was working perfectly for a month.
Seemed to happen out of no where, no new apps installed or settings changed. The phone will vibrate for incoming calls, haptic, everything except SMS.
Using GoSMS but it does the same with the stock messanging app. Vibration is turned on in all the system and messanging settings. In fact, when I test settings in GoSMS it reports "vibration on".
Tried clearing the dalvik cache and tried installing this app but it won't show anywhere in the app drawer and I can't find it anywhere on the phone despite the market saying its installed. Unfortunate becasue it seems this app was designed for this very issue with desire/insprire.
Anyone have a fix for this or a method I could get the above app to install properly?
Thanks.
edit.....It's looking like an app issue......
never mind on the rom repair part....sorry
mods can delete....g
Gregsarg was actually probably right the first time. It doesn't seem to be an APP issue (as all MMS apps have the same lack of vibrate), but a broader issue.
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
I also tried the GoodVibrations.apk and it only shows in airdroid, mybackup, and managing all apps... It doesn't even have the 'open' command on the market menu after installing it >.>
Wulamoc said:
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
Click to expand...
Click to collapse
Thanks. Unfortunately I didn't see this suggestion before it was edited out. What exactly is meant by install CM7 on top of itself? Through clockwork I presume?
Yeah, just flash the SAME rom again (after backing up AND without wiping anything), and your settings should stay in place.
There is also a setting in the stock CM sms app that controls vibration, which is turned off by default.
Yeah vibrate in the stock SMS program is on. While I haven't gotten around to reflashing just yet I have noticed a few other things that lead me to believe its a ROM issue. Sometimes when I put the phone on silent it turns off all system vibrations even after coming off silent. I have to go back in and turn vibration back on. This is intermittent. Also, out of the blue the phone started vibrating during calls, come to find out "vibrate every 45 seconds during outgoing calls" was magically turned on.
It WILL vibrate when an SMS arrives if I'm on a call. Swell.
Flashed the new 7.2 nightly and the problem still exists. Everything remained intact after the flash so I figure I'll just do a full wipe/factory reset and flash the new nightly again and start over. Hopefully whatever caused this won't carry over with titanium restoring apps.
Do the full wipe, install the rom... then get a friend to send you text messages BEFORE you restore from Titanium, and then after....
Easy to isolate if you're carrying the issue from ROM to ROM.
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now..
*signed
mrrick said:
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now
Click to expand...
Click to collapse
That did it thanks! Saved me from having to do a full wipe. Phone is back to vibrating with SMS and I can change the vibration pattern. Nice.
Cool, glad it worked for you. I really wish I knew what happened though, it's kind of bugging me.
Meh, technology..
*signed
Well I'll add this... Out of curiosity I removed the vibrate tools app and everything is still operating as designed. So whatever that app turned on has stuck.
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.
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.