So I've had a recurring issue. Seems to be happening with any and all JB Sense ROMs really.
After fresh installing a ROM my phone would be working perfectly fine. Then some time after that, any time I receive a call the phone will lock up after I choose to pick up or right after I click send if I'm dialing out. No matter what, I will have not be able to hear anything. No dial tone, no voicemail, no voice on the end of the line. Sometimes a cache/dalvik wipe will fix this, most times it doesn't.
Another problem I've been having is that sometimes volume just stops working completely. No notification sounds, no ringtones, no key presses. Again, sometimes a cache wipe will fix this. Most times it doesn't. Usually these two problems come hand in hand.
EDIT: When I try to search something by voice on Google Now/Search, that also fails. So Mic seems to be an issue as well. But only when everything else is messed up.
I've posted this question on several ROM threads but no help so far. Any help with these problems would be greatly appreciated.
Related
About half the time, when I try to answer an incoming call, my Verizon TP2 will only mute the ring without answering the call. It responds the same whether I use the touch screen to answer or press the send key, and whether or not the phone is locked or unlocked when the call arrives. Has anyone had a similar problem or know of a fix? Thanks.
I got this behavior the first time I finished getting the phone set up how I wanted. I eventually had to hard reset to fix it.
I think it was probably s2u2 interfering with the nonstandard dialer / answer bits on the phone. Even uninstalling it didn't help though. I have not bothered to try reinstalling s2u2 after the reset though to see if it causes the problem again.
i have this same problem. as i recall there was some registry tweak you could do to fix it, but i cant remember it to save my life. I have the worst problem with being on the internet and trying to answer a call. anyone know of a fix? whenever i am on opera and try to answer an incoming call it just freezes and i have to exit opera and call the person back. anyone with a fix for this other than a hard reset?
i had the same problem before i flashed to 6.5 on my vzw tp2. I also suspected that it was because of s2u2: I followed to uninstalling and i kept on getting a message about s2u2.exe not being a valid app or something. I also thought it could have been because of the dialer i had. The dusk dialer...for sense2.1 while i had manilla. after the flash i reinstalled s2u2, and will see if this persists to happen again.
It happened to me for the first tiem twice yesterday, my phone awoke and I could see my taskbar icon switch to 1x but I didn't see a call then I got a voicemail, when I called the person back they said it rang 6 times and went to voicemail, and it happened again later where i saw the call box and slide to answer come up but the screen was stuck and I couldn't answer it, not even with the hardware key.
Same thing is happening to me. The first time someone calls it won't answer whether I use the soft key or the hard key and the screen just freezes. However when the person calls back, it answers immediately when I click the answer button. I don't have S2U2 or any other phone/lock apps which interfere with answering a call.
Same here guys, I have been having the same issue, but as I can see for weeks now I haven't been able to nail down a solution either...
I too have had the same issue for several weeks. More prevalent when the screen is locked. Rings once and goes to voicemail.
stupid double post.
I've only run across this issue when I am using too much RAM. Try using cleanram and closing out tasks that you are not using.
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
reddington said:
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
Click to expand...
Click to collapse
have you tried s2u2 and their call answering interface?
been having this crazy lag in placing calls with the sense dialer which can take up to 40+ sec!! where, for example, if i select the option of calling a certain contact, i press the button and like nothing happens for like 30-40 sec, and then the calling screen appears!!
Been searching for any solutions, and thou many people apparently had it on several devices, no concrete solution is out there. tried clearing the calls log, removing several synced accounts (exchange, fb…), and other suggestions as well, but all in vain!! the only thing that temporarily works is rebooting, where there is no lag in the first 3-4 calls made, but after that the lag is back and it can takes up to 40+ sec (literally) to place a call, and whenever I doubt pressing the call button and try placing the call again it just queues it and it ends up dialing the number again after the 1st call is placed and putting the previous one on hold and so on!!
is there anyone else facing the same? would truly appreciate any help or suggestions (preferably not a hard reset!) as this problem is really causing me so much trouble?
PS: I am rooted and on stock ROM
Are you running stock, or a Sense ROM developed on XDA?
Col.Kernel said:
Are you running stock, or a Sense ROM developed on XDA?
Click to expand...
Click to collapse
Thanks col.kernel. I am on the stock ROM!
Not seeing that issue on my phone on either stock rooted rom, nor on Bulletproof rom.
Hey there. I got a bit of a problem with my Nexus S, which I've had since January. I didn't notice it much at first, but now it's worse than ever. When someone calls and I push the button to pick it up, the buttons disappears, as if it takes it, but it keeps ringing. Then sometimes, after about 5 seconds, it still takes it. Problem is that most of the time when it does this, I can't hear the person in the other end, but they can still hear me. This is only a problem on incoming calls, not outgoing.
The reason why I ask for help now, is that I noticed when installing a SDK build of ICS, I didn't have this problem, everything was all right. But today, when installing a AOSP build, it starts doing this again.
This problem persists across wipes, and different radio images.
My belief is that there must be some system files in the SDK builds that fixes this problem.
If anyone has a suggestion on how to fix this, other than me digging through system files and trying to replace random files and see if it works, please tell!
Regards, Adam Honoré.
If you feel like you need a better explanation, Please tell.
I can upload a video demonstrating it.
Gonna bump this with new info.
I forgot to mention that after calls, when I press the hangup button, it just stays there for about 10 seconds before hanging up.
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.