So i have searched everywhere for a solution to this problem. I have been running mostly Droidkang and Beanstalk with chaos kernel but have tried a few other ones and the kernels that come in the roms. I'am using cwm advanced it also happened on twrp. I have tried pa gapps and banks gapps. also tried core and standard. With all the different combos i tried i still had Google talk to text cause a random reboot sometimes (not every time) mostly when I hit the home or back button when Iam done. Sometimes it works fine other times it random reboots almost a hot boot because its pretty fast. I tried a stock based rom and it didn't seem to be doing it but I only tried few times. If anyone has a solution for this i would be stoked its not the end of the world but semi annoying when trying to talk to text while multi tasking. I would be more than willing to do whatever is needed on my side to help catch it on a bug report just not 100% how to if it reboots? I was going to post this on a ROM or kernel thread but it seemed to be doing it on all the CM or NON stock based roms. Thanks to anyone who maybe able to help or has fixed it for them selves and trust me I did search so if I missed a tread about this subject i'am sorry for the post.
when using Google hangouts and I use Voice to text and click back on the typing area without stopping voice record it reboots almost every time on Beanstalk. I can't be the only one dealing with this . anyone?
Related
I keep having issues with the voice to text feature on 2.3.x roms. The text to speech will sometimes work from the start, however it will stop working. The time it takes to stop working is very random. When it stops working it just says no speech heard. Has anyone had this issue, or know a possible fix. Rebooting the phone does not fix it.
Roms tired
CM7 7.0.3
CM7 Various Nightlies
AOSP
GINGERBEAST
Your help is appreciated as I don't want to keep running stock.
timistim said:
I keep having issues with the voice to text feature on 2.3.x roms. The text to speech will sometimes work from the start, however it will stop working. The time it takes to stop working is very random. When it stops working it just says no speech heard. Has anyone had this issue, or know a possible fix. Rebooting the phone does not fix it.
Roms tired
CM7 7.0.3
CM7 Various Nightlies
AOSP
GINGERBEAST
Your help is appreciated as I don't want to keep running stock.
Click to expand...
Click to collapse
Just a quick heads up.... Make sure to post questions in the General Forum. Here's a link that may help you.... http://forum.xda-developers.com/showthread.php?t=1124046&highlight=voice+to+text
I always use the Voice Search widget (4 x 1) and it works without a hitch for Voice-To-Text. If you're not using it, just install the widget, put it on one of your Home Screens, push the Mic icon to the right of the Google Search field, and it'll give you a quck demo on what to do. Good luck.
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.
Hi there
First some specs:
Nexus 4
PA3.99-RC2
Franco.kernel.plus 188.
SuperSU root
Latest gapps
I have tried asking in the the Paranoid Android Google+ discussion forum, but no useful answers yet. This is x-posted in N4 forum as well, but I thought asking here in general could give give answers from people with other devices too.
The problem:
When I use my phone I get random glitchy/clicky sounds from the top speaker (I'm pretty sure it's from there). It's a very quick glitch/click, and then it stops. It doesn't happen in a specific pattern, meaning that it's not like it comes whenever I press the back button or anything - it just happens sometimes. Sometimes more often than other. When I try to recreate the sounds (tapping a lot of menus, settings, apps, etc.) I find it difficult to recreate. It is REALLY random, perhaps mostly after I haven't used my phone for a while, and I turn it on!
Have anyone tried this, and knows a solution? It didn't annoy me at first, but now it really does.
As far as I remember it started when I upgraded to PA3.99. However, I have tried RC-1 and RC-2 and I have also tried stock kernel, Hellscore kernel and different Franco-kernel versions.
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.
I don't know if any of you guys are experiencing the same problem as I am because I have looked all over the internet but there's no solution. So I'm on Paranoid Android 7.2.3, Snapchat crashes after 2 or 3 seconds into launching the app. After a few crashes, it makes to the login page but every time I tap log in, it just freezes at that screen without even changing the log in button into logging in. I have tried to log in both rooted and unrooted. It just doesn't work. Anyone can share their solution?
OngZL said:
I don't know if any of you guys are experiencing the same problem as I am because I have looked all over the internet but there's no solution. So I'm on Paranoid Android 7.2.3, Snapchat crashes after 2 or 3 seconds into launching the app. After a few crashes, it makes to the login page but every time I tap log in, it just freezes at that screen without even changing the log in button into logging in. I have tried to log in both rooted and unrooted. It just doesn't work. Anyone can share their solution?
Click to expand...
Click to collapse
i think its because its using the new GPU drivers, sultan had the problem too took him a while to fix.
considering Paranoid Android has quite a lot of bugs, i suggest looking elsewhere.
I've been using aospextended sultanized and i promise you now its amazing, i usually flash new roms constantly because im not satisfied but this ones got me locked. :good:
idonttakedrugs said:
i think its because its using the new GPU drivers, sultan had the problem too took him a while to fix.
considering Paranoid Android has quite a lot of bugs, i suggest looking elsewhere.
I've been using aospextended sultanized and i promise you now its amazing, i usually flash new roms constantly because im not satisfied but this ones got me locked. :good:
Click to expand...
Click to collapse
Will try it some other day because I just flashed PA a few hours back