[Q] Galaxy tab 10.1 google now crash - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hello, i am in need of some help. i recently flashed a custom rom ( Android 4.2.2 Jelly Bean CM10.1 Nightly) to my galaxy tab 10.1
i have installed google search and flashed the correct gapps file to it using CWM.
whenever i go to use the speech recognition option to the right of the google search bar, google now crashes.
any ideas would be great!:laugh:

---

rykanator said:
Hello, i am in need of some help. i recently flashed a custom rom ( Android 4.2.2 Jelly Bean CM10.1 Nightly) to my galaxy tab 10.1
i have installed google search and flashed the correct gapps file to it using CWM.
whenever i go to use the speech recognition option to the right of the google search bar, google now crashes.
any ideas would be great!:laugh:
Click to expand...
Click to collapse
You installed Google Search from the Play Store, and not from a backup, right? You could try going to Apps/Google Search and clearing cache. I've heard that's worked.

---

Disable the Hotword detection in setting, under languages and inputs and it will no longer crash.
Sent from my GT-P7500 using xda app-developers app

---

John Kester said:
Disable the Hotword detection in setting, under languages and inputs and it will no longer crash.
Click to expand...
Click to collapse
I had this problem too, and disabling "Hotword detection" worked for me, thanks.
More specifically, it is under Settings-> Language & Input -> Voice Search

---

Google Now / Google Search crash problem solved
rykanator said:
Hello, i am in need of some help. i recently flashed a custom rom ( Android 4.2.2 Jelly Bean CM10.1 Nightly) to my galaxy tab 10.1
i have installed google search and flashed the correct gapps file to it using CWM.
whenever i go to use the speech recognition option to the right of the google search bar, google now crashes.
any ideas would be great!:laugh:
Click to expand...
Click to collapse
Google Now / Search Crashes? SOLVED
I had the same issue in my Samsung Galaxy Tab 10.1 CM 10.1 (JB4.2.2)
My problem has been solved after changing language settings to English (Australia).
I tried the following steps & its working perfectly now.
1. Uninstalled Google search from settings - Apps - Google Search.
2. Open Play store & install Google search again
3. Dont open Google search now.
4. Change Language settings to English (Australia) in Settings -> Language & input -> Language
5 Open Google search now & skip the Now setup at the startup (select May be Later)
6 Go to settings page in Google Search (Right bottom corner) & select voice and verify the Language shows English (Australia).
7. Select Google Now & Enable it by selecting ON.
AL RATHEESH. R
[email protected]

---

alratheesh said:
Google Now / Search Crashes? SOLVED
I had the same issue in my Samsung Galaxy Tab 10.1 CM 10.1 (JB4.2.2)
My problem has been solved after changing language settings to English (Australia).
I tried the following steps & its working perfectly now.
1. Uninstalled Google search from settings - Apps - Google Search.
2. Open Play store & install Google search again
3. Dont open Google search now.
4. Change Language settings to English (Australia) in Settings -> Language & input -> Language
5 Open Google search now & skip the Now setup at the startup (select May be Later)
6 Go to settings page in Google Search (Right bottom corner) & select voice and verify the Language shows English (Australia).
7. Select Google Now & Enable it by selecting ON.
AL RATHEESH. R
[email protected]
Click to expand...
Click to collapse
Wow! Thanks for this information. Working great now!
---------- Post added at 11:50 PM ---------- Previous post was at 11:46 PM ----------
drdunga said:
I had this problem too, and disabling "Hotword detection" worked for me, thanks.
More specifically, it is under Settings-> Language & Input -> Voice Search
Click to expand...
Click to collapse
Thank you also. I followed your advice at the same time. lol No stone unturned!

---

please help
CinDroid said:
Wow! Thanks for this information. Working great now!
---------- Post added at 11:50 PM ---------- Previous post was at 11:46 PM ----------
Thank you also. I followed your advice at the same time. lol No stone unturned!
Click to expand...
Click to collapse
hi guys ,
i have the same problem
I tryed to do exacly what you say 3 times and no use ? ;
can you guys help ?
koop

---

libc.so?
I have the same problem, it seems after the last Google Search update.
Before I was using English (Generic), and Google Now with "OK, Google" hotword detection was working fine.
I changed to English (US) to use the hotword detection from any screen, but now it always crashes as soon as it tries to recognize what I say (but saying OK Google still triggers the voice search).
I don't want to disable the hotword detection because that's the only reason I'm using Google Now anyway.
The report's stack trace contains some really cryptic information, it seems from a native library, and I suspect it may have to do with the CyanogenMod nightlies updates. I am using Android 4.4.4 from cm-11-20140806-NIGHTLY on a Samsung Galaxy S II (gti9100).
Going through the stack trace, it first references the file libc.so (from /system/lib/libc.so), I remember also some references to this file somewhere in the nightly logs, so maybe that's the cause?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

brunofin said:
I have the same problem, it seems after the last Google Search update.
Before I was using English (Generic), and Google Now with "OK, Google" hotword detection was working fine.
I changed to English (US) to use the hotword detection from any screen, but now it always crashes as soon as it tries to recognize what I say (but saying OK Google still triggers the voice search).
I don't want to disable the hotword detection because that's the only reason I'm using Google Now anyway.
The report's stack trace contains some really cryptic information, it seems from a native library, and I suspect it may have to do with the CyanogenMod nightlies updates. I am using Android 4.4.4 from cm-11-20140806-NIGHTLY on a Samsung Galaxy S II (gti9100).
Going through the stack trace, it first references the file libc.so (from /system/lib/libc.so), I remember also some references to this file somewhere in the nightly logs, so maybe that's the cause?
Click to expand...
Click to collapse
Same issue here, different phone and I'm on SlimSaber ROM... Please let me know if you find a solution
---------- Post added at 09:50 PM ---------- Previous post was at 09:43 PM ----------
Actually just found a solution http://forum.xda-developers.com/gal...le-hotword-screen-crash-t2824787/post54439615

---

Noed said:
Same issue here, different phone and I'm on SlimSaber ROM... Please let me know if you find a solution
---------- Post added at 09:50 PM ---------- Previous post was at 09:43 PM ----------
Actually just found a solution http://forum.xda-developers.com/gal...le-hotword-screen-crash-t2824787/post54439615
Click to expand...
Click to collapse
Man, thank you bery much for pointing that out! fixed my issue as well!
For those who wants to know the solution, I'm quoting it from another thread located here: http://forum.xda-developers.com/gal...le-hotword-screen-crash-t2824787/post54439615
LooseSeal said:
Open Google Search and go into Settings > Voice. Make sure 'Bluetooth Headset' is ticked. That fixed the issue for me.
Click to expand...
Click to collapse
Btw, curti a sua foto valeu!