Here goes. I have the 4.1.1 Omega v32-XXDLJ5 ROM with Siyahkernel v1.7rc2 on my I9300.
Now the problem is, the ROM was working perfectly without any hitches, but today when I tried using Google Voice app, the voice failed to take my input and kept asking me to tap the microphone icon onscreen. I can see that it is registering the voice (with the visual representation surrounding the microphone icon), but there is no feedback. Upon checking further I found that the same issue is with Samsung's Assistant as well. It is not providing any feedback.
Unfortunately that's not the end. I also found that the dictation in messaging etc. of Google voice isn't working either. So, basically, they all are listening to my voice but not providing any reply/feedback.
Same issue had happened to me before 10 days. At that time I had felt that I might have tweaked with some setting somewhere which resulted in this issue (did a nandroid restore to resolve it). But this time around, i haven't done anything which would have caused this issue.
Can anyone help me to find the cause of this issue, and if anyone knows what/where the fault is, your help in resolving this issue will be appreciated.
I know I can reflash the rom/restore the nandroid backup, but it also means having to re-install everything/some from scratch, which is a pain. And also, those don't identify the source of the problem. And this being the 2nd time, it might very well be repeated a 3rd or more number of times.
Did you try fix permissions in CWM.
I have the CWM 3.60, but i get a notice that this ver of CWM should be used with CF-CWM v1.1 or newer, so, various options have been diabled. Maybe that's why I don't have the fix permissions option. Any idea about this?
NB: Found the option in CMR and it fixed the issue right up. Thnx a lot buddy
Related
Google Now worked correctly on my phone, until 1st of August. Since then, it is having a strange problem. Not just voice, even if I try to search using text (typing it into the box), it briefly shows the results and crashes immediately. Its not a 'crash' as such, it just shows the home screen directly, and no force close or not responding message.
Anyone else experiencing this? What could be the problem?
ROM: CM10 latest build - tried reinstalling, tried installing older build but no luck
EDIT: Fixed it!! Under "Phone Search", you'd need to disable one (or more) options in order to make it work correctly. For me, it was Google Chrome. Its working fine now.
I had the same problem of it not showing up after my GApps flash. Caught unaware, I started installing/updating the Google Apps, then saw this thread and reflashed the proper GApps file. Unfortunately, that caused all sorts of weirdness. What I found to work after everything was to reflash JB, reboot back into recovery, and flash GApps IMMEDIATELY after the JB flash. Now I have Google Now with all my apps. No special settings changes or anything. It just works now.
thehrushi said:
EDIT: Fixed it!! Under "Phone Search", you'd need to disable one (or more) options in order to make it work correctly. For me, it was Google Chrome. Its working fine now.
Click to expand...
Click to collapse
I am having the exact same issue, with the exception that I tried disabling everything under phone search, and it still crashes immediately
I can open google now but as soon as I start to type it closes (similar to OP, no FC message or anything, just back to the homescreen). I can't even click settings within google search (same result, just closes). I think it was working after upgrading to JB. I think it started to act weird after integrating with my system rom using Titanium Backup. I don't think there's a way to de-integrate, is there?
Do you think installing the APK on top would help? Or do I need to start over?
Also, FWIW, I'm on the moto droid razr maxx HD, so this sounds like a software, not hardware, issue.
mikepfly2 said:
I can open google now but as soon as I start to type it closes (similar to OP, no FC message or anything, just back to the homescreen). I can't even click settings within google search (same result, just closes). I think it was working after upgrading to JB. I think it started to act weird after integrating with my system rom using Titanium Backup. I don't think there's a way to de-integrate, is there?
Do you think installing the APK on top would help? Or do I need to start over?
Also, FWIW, I'm on the moto droid razr maxx HD, so this sounds like a software, not hardware, issue.
Click to expand...
Click to collapse
Yes it's a software issue i also experienced this problem, what i did was i went to manage application and cleared data and lo and behold it was working fine....
By the way this is a Galaxy S2 forum.... You should go to your specific device section to post.
Sent from my Galaxy Tab 7.0 Plus
Just hit the Damn thanks button instead of thanking me in your post
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
I have tried most of the JB Roms for the Galaxy S3, trying to see what would bother me less in every rom as a missing or not working feature.
I am facing the same problem with almost all roms (but not with all).
As soon as I bring back my applications and data through Titanium backup (never restoring the system files of course) then when I go to Settings/Applications Manager and try to scroll through the installed applications it always freezes and I get the message "Unfortunately, Settings has Stopped" and I get back to home screen.
As I said I did not had the problem only with a couple of roms (not remembering which ones though) but having it most of those I flashed.
All the roms have always been flashed on totally blank mediums since I have always used full wipes (tried to reflash a couple of them on top just to see if this would fix the problem but it did not)
Note that all applications do scroll normally and very fast in other programs also listing the installed applications, either through Titanium Backup or even in the drawer where all apps literally fly when scrolling.
Any help or advice would be greatly.
Does it work ok before you restore apps from Titanium Backup? If it does, try just restoring the apps one at a time and testing after each one. I suspect there's a duff application in there that's been restored, and that's causing the problem
Alternatively just reinstall the apps from the Play Store rather than using TB.
Thank you anthropolyte, man you are fast.
Thought of many things related to JB (because up until v4.0.4 I did not have this issue with - almost - the same applications installed) but I did not think for a moment that a specific application could be the issue. I will re-flash the rom later today and try it your way.
I will report back in case someone faces the same issue.
You're welcome - good luck!
Dear jsfero, did you manage to solve that problem? I'm just facing the same. Firstly I thought it was due to blackm* app but after uninstall it nothing changed. Then I thought it may have to do with apps in drawer showing the same name. Then I kept one and uninstalled the other. Nothing changed. I'm just a bit bored with this situation. My only difference is that I occurred to me also with ICS, not only with JB or CM10.
Could you provide me with some light about this issue?
Many thanks in advance.
Zentenario said:
Dear jsfero, did you manage to solve that problem? I'm just facing the same. Firstly I thought it was due to blackm* app but after uninstall it nothing changed. Then I thought it may have to do with apps in drawer showing the same name. Then I kept one and uninstalled the other. Nothing changed. I'm just a bit bored with this situation. My only difference is that I occurred to me also with ICS, not only with JB or CM10.
Could you provide me with some light about this issue?
Many thanks in advance.
Click to expand...
Click to collapse
Unfortunately, after having tried almost everything from re-flashing to re-downloading all my apps, I could not manage to find out the source of this problem.
It is only just by accident that I found out that a couple of ROMs are not causing any problem and the phone works perfectly well. The one I do remember and I do use now as my main daily usage ROM is the one from Sotmax.
Now, I don't know if this problem is the outcome of a 'bad' combination or bad coexistence of certain programs from kernel or Rom, all I know is that my exact same Titanium back with over 300 apps is the same one I tried on all the Roms so I doubt that the problem is coming the applications side. It was always as if the amount of applications / data was too high for the Roms to handle and crashed the application. And all the sudden one day, I simply realized that with Sotmax's Rom and same applications installed via Titanium did not cause any problem or malfunction.
I even changed kernels, from stock to Siyah and now Perseus, the problem seems to be gone for good with this Rom. I am sure that I must have found a one or two other Roms which did not cause the problem either, unfortunately I did not like them that much to keep them and remember which one they were.
HTH
I had the same problem as well unfortunately, also couldn't access App info/app size
Had to uninstall some apps, then reinstalled them again
But I can't install broken Sword without getting the problem again
Sent from my GT-I9300 using xda premium
Yes, I can confirm that Broken Sword game causes App Info to crash. Another one that I found is from Samsung Apps called "Catch The Monkey". Troubleshooting this was time consuming as I had to uninstall each app in the sequence (refering to appbrain.com which has the sequence of apps I installed from Google Play) and keep testing whether App Info crashes or not.
Hello, guys this is really a big issue for me and i have no clue what can be causing this problem.
I am currently running SlimSaber Latest 4.4.4: 20150810 http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-slimsaber-i9100-t2350201
But have also had this problem on ResurrectionRemix lolipop, dont remember the exact version i had installed at that time.
I have tried to change the TTS from Pico to Google text to speech and Ivona..no luck, the navigation voices will just stop working sooner or later for no apparent reason, i will hear a "ding" sound instead of any voice guidance.
If i "clear data" for Google Maps, sometimes, not all the time, the problem will get fixed temporarily..but will appear again in no time.
I have tried reinstalling Google Maps, reinstalling the TTS, changing the TTS...nothing works, and if something does work, it is only temporary, for 1-2 days at most.
Please, do you guys have any suggestions on what i can do to fix this ?
1noob said:
Hello, guys this is really a big issue for me and i have no clue what can be causing this problem.
I am currently running SlimSaber Latest 4.4.4: 20150810 http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-slimsaber-i9100-t2350201
But have also had this problem on ResurrectionRemix lolipop, dont remember the exact version i had installed at that time.
I have tried to change the TTS from Pico to Google text to speech and Ivona..no luck, the navigation voices will just stop working sooner or later for no apparent reason, i will hear a "ding" sound instead of any voice guidance.
If i "clear data" for Google Maps, sometimes, not all the time, the problem will get fixed temporarily..but will appear again in no time.
I have tried reinstalling Google Maps, reinstalling the TTS, changing the TTS...nothing works, and if something does work, it is only temporary, for 1-2 days at most.
Please, do you guys have any suggestions on what i can do to fix this ?
Click to expand...
Click to collapse
Someone...anyone ?
1noob said:
Someone...anyone ?
Click to expand...
Click to collapse
What is your partition details (System+Data) and which gapps you are using?
sudiptarout said:
What is your partition details (System+Data) and which gapps you are using?
Click to expand...
Click to collapse
Thanks for the reply.
I am using the gapps located here slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4 **Version** Slim_mini_gapps.4.4.4.build.8.x-385.
I am not sure where to look up the partition details but i have not repartitioned anything so i believe everything should be default.
Thankfully, i have found a strange and yet seemingly reliable fix for my problem after at the very least 2 weeks of trying to figure out why voice navigation stops working.
The fix i've found is very easy to do and i have no idea why it works but it seems to be working all the time, found it only a few hours ago but it passes the phone restart test & google maps restart (something which none of the other things i've tried did), i must first start the navigation and select vehicle / car as my method of transportation, after that, i switch back to what i normally use which is "on foot" and the navigation voice will work.
This is the issue of incomplete voice directions. The voice directions need to be downloaded when you are using the Google Maps and it depends on your internet speed. If there is no voice direction, you will hear "chime" sound instead of the voice direction.
Check out the help from google.
https://support.google.com/maps/answer/3273406?co=GENIE.Platform=Android&hl=en
Step 5 under Fix voice navigation problems
1noob said:
Hello, guys this is really a big issue for me and i have no clue what can be causing this problem.
I am currently running SlimSaber Latest 4.4.4: 20150810 http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-slimsaber-i9100-t2350201
But have also had this problem on ResurrectionRemix lolipop, dont remember the exact version i had installed at that time.
I have tried to change the TTS from Pico to Google text to speech and Ivona..no luck, the navigation voices will just stop working sooner or later for no apparent reason, i will hear a "ding" sound instead of any voice guidance.
If i "clear data" for Google Maps, sometimes, not all the time, the problem will get fixed temporarily..but will appear again in no time.
I have tried reinstalling Google Maps, reinstalling the TTS, changing the TTS...nothing works, and if something does work, it is only temporary, for 1-2 days at most.
Please, do you guys have any suggestions on what i can do to fix this ?
Click to expand...
Click to collapse
Hello there.
Sorry to bother you, but I'm having some really serious problems. I am using a Oneplus One, though I don't think the problem is device specific. Every time I open a conversation in the messaging app, it crashes. I thought no big deal, I'll just download another messaging app. I tried Chomp, Textra, and Google Messanger. All of them had similar problems; they would crash. It seems to be a problem with the app trying to call conversations from the phone. I also cannot receive any messages. I can, however send them via Google now. I am using sultanxda's MarshMallow ROM, which is amazing. This problem is not, however rom specific. The first CM13 nightlies recently came out so I decided to test it out. I dirty flashed it and encountered the same provlem. I then clean flashed it and it worked fine. So I decided to experiment. I restored my sultan backup and wiped the system partition, then dirty flashed the sultan rom again. The messaging app worked fine, but I had problems with Google Play services and android.phone crashing. Then restored sultan again and this time did a factory reset(TWRP style). Again, messaging worked fine. I believe the problem to be some kind of root enabled app, but I have not idea what it could be. Disabling root also doesn't help, so that might not be the problem after all. The only root apps I have are Xposed, lucky patcher, and Awesome Pop-Out Videos. Uninstalling these don't help either. I know this is a complicated question, but I really need help. If I don't get an answer soon, I'll just have to factory reset and start over. Please help me if you can!
So not mention lucky patcher. You will not find any help with it installed.
With out the proper troubleshooting on your part there is nothing that can be done. A logcat will tell you what is causing it.