Database Users

Google Now crashing

Not sure when this started. I unlocked and rooted before I had even started up, and since then just used the Trinity kernel and toolbox, but apart from that completely stock. It was working, but now it force closes when bring up the results. For example if I ask for the weather it will be half way through the reply then back to the home screen. Happens both on typing and voice search.
Only two threads I can find are below, none of them have a fix
http://forum.xda-developers.com/showthread.php?t=1784694
http://www.xoomforums.com/forum/motorola-xoom-general-discussion/18016-google-now-crashing.html
I have deleted the cache and disabled/enabled google search. Any ideas?

philipwll said:
I'm having this problem as well with my Nexus 7. I'm not sure what's wrong with it. it's just so frustrating. I tried to download the offline language pack but still didnt work. Like u said no other post online available for this solution yet. Wondering if many people get this.
However one thing did happen, my nexus 7 ran out of batt and turned off by itself. I then plugged it into a power source and turned it on. I run an app and suddenly some blur screen like the TV tuned out came on and all i can hear is some buzzing sound. then i plugged off the power and i charged it again and everything was alright apart from the Google Now thing!!!!!
when the batt ran out, all the memories seems to be wiped out... such as time and date.. seems strange when they built such high tech stuff and they do not have memories to keep track of time and date?!
i really hope this gets resolved soon
Click to expand...
Click to collapse
Another N7 user

New version of Google Search downloaded today seems to fix

[Q] N4 USB stopped working yesterday

I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.

I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this

BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course

Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...

BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.

Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists

When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta

Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4

tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!

Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4

Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.

tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post

[Q] Some little help.

Hi everybody.
I received my mojo friday, and everything was going well. I rooted it, and it was fine.
But now:
1) yesterday i noticed that mojo didnt connect to my home wifi (before yeasterday it always worked), so i tried to "forget" the hotspot, i tried to switch off the wifi connection and so on, but nothing happens. My laptop, my phone, and my xbox360 working fine. What could i do?
2) last thing, about my tv, that cut the edge of the mojo screen (i cant see navigation bar, so i couldnt see if there are any notification or whatever.. ), i tried to change the screen setting on the tv menu, but nothing happens.
So, im sorry if i posted some stupid questions, but for this kind of stuff im a real noob, and i hope somebody could help me.
Thanks for help!

I'm not much help, but did you install the latest firmware? I've only used the first and last firmwares and had no real problems with wifi, but other people have mentioned wifi issues with other firmwares here.
As for your screen problem, one of the early threads in this forum talks about tv settings you can try to change. Each TV is different, and my off-brand tv didn't have the options mentioned in the thread, so as a result I can't maximize the screen size.
Good luck!

Vomitor696 said:
Hi everybody.
I received my mojo friday, and everything was going well. I rooted it, and it was fine.
But now:
1) yesterday i noticed that mojo didnt connect to my home wifi (before yeasterday it always worked), so i tried to "forget" the hotspot, i tried to switch off the wifi connection and so on, but nothing happens. My laptop, my phone, and my xbox360 working fine. What could i do?
2) last thing, about my tv, that cut the edge of the mojo screen (i cant see navigation bar, so i couldnt see if there are any notification or whatever.. ), i tried to change the screen setting on the tv menu, but nothing happens.
So, im sorry if i posted some stupid questions, but for this kind of stuff im a real noob, and i hope somebody could help me.
Thanks for help!
Click to expand...
Click to collapse
Hi Welcome
# as P901 said upgrade to the lastest firmware (although I prefer v202 because of the running apps 'MadCatz' button works better)
ftp://86.54.116.234/pub/software/mojo/firmware/
If you have ouya and onlive, then your' already on the latest.
Try a hard reboot (off/on)/plain mode & and forget settings
#2, overscan, search the forum for it, you'll need to find your TV's manual and turn it off

Thank you guys!
By the way i solved the problems with wifi and the ctrlr.. The wifi problem was given by the wrong data and hour.. I unplug everything before going to sleep, and this will reset the mojo clock. Anyway i will download that firmware..
For the tv.. Mine is a 32" inch by haier, there are some screen costumization (automatic, zoom 1, zoom 2, 16:9 and 4:3).. But when i try to apply nothing changes. I saw on the playstore, there are some app who change the screen resolution. Do you think this will work even on a tv?

Little edit.
I checked my version, and is 205.. I have Ouya, but when i try to install Onlive from the market a message says that is not compatible with my mojo.. WTF?!

Somewhere in the mojo settings their is the option to manually resize the screen, sorry I can't be more help than that. Its been about 8 months since I did mine. Just search the options menu hard.
Also in options go to about devise and click about devise 7 times in a row to enable the developers options the same way as you do every android devises to enable the extra options in case its in there.
---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------
Vomitor696 said:
Little edit.
I checked my version, and is 205.. I have Ouya, but when i try to install Onlive from the market a message says that is not compatible with my mojo.. WTF?!
Click to expand...
Click to collapse
Weird tbf the mojo is half arsed but its compatible on mine running 205. If when you do get it working make sure before you log in on the first menu, go to settings and change the screen quality from 1080 to 720p this will drasticly reduce the input lag experienced on the mojo. Hate to dissapoint but onlive is no where as smooth on the mojo as it is on the micro console or PC app am afraid and has horrific input lag, driving and shooters are nearly unplayable at times.

Vomitor696 said:
Little edit.
I checked my version, and is 205.. I have Ouya, but when i try to install Onlive from the market a message says that is not compatible with my mojo.. WTF?!
Click to expand...
Click to collapse
with the latest firmware, in google settings you can change your resolution.. but it wont fix your overscan issue.
RE onlive, it's only available in the US(canada??,EU??) , everywhere else SOL
I noticed after root on 205 firmware, the play store didnt have as many apps available, now I use Market Helper, see my modern combat post.
---------- Post added at 09:23 AM ---------- Previous post was at 09:13 AM ----------
Ash180287 said:
horrific input lag, driving and shooters are nearly unplayable at times.
Click to expand...
Click to collapse
I keep the dongle in 'line of sight' with the controller for better performance and bettery saving.
I have my mojo under the tv with the back (USB ports/cables etc) facing me.
You might have yours somewhere obscured?
And the controller lags bad on low batteries

About Onlive, ok, i sideloaded it from the market and its work really bad. Looks like watching an old vhs movies at slow mo. ahahaha And anyway, i could get an account because im not from USA.. :/ Whatever.
For the tv, ok, i will wait to have money to buy a new tv, probably around christmas time. We will see.
In the next days i should receive my blutooth keyboard, write on the android keyboard with point and click is a very pain in the ass I cant tell im satisfied from my mojo, now, but i see big potential on it. Wait and see..

Vomitor696 said:
About Onlive, ok, i sideloaded it from the market and its work really bad. Looks like watching an old vhs movies at slow mo. ahahaha And anyway, i could get an account because im not from USA.. :/ Whatever.
For the tv, ok, i will wait to have money to buy a new tv, probably around christmas time. We will see.
In the next days i should receive my blutooth keyboard, write on the android keyboard with point and click is a very pain in the ass I cant tell im satisfied from my mojo, now, but i see big potential on it. Wait and see..
Click to expand...
Click to collapse
I was thinking side loading it too.. but then thought it would be worth it
Yeah I don't know any games console which do keyboard well enough to be useful... so keyboard is a must for lots of typing.

gwaldo said:
I keep the dongle in 'line of sight' with the controller for better performance and bettery saving.
I have my mojo under the tv with the back (USB ports/cables etc) facing me.
You might have yours somewhere obscured?
And the controller lags bad on low batteries
Click to expand...
Click to collapse
I think the lags between the action/button on the controller being pressed it registering and completing on the online server then the footage what you've done being streamed to the console.
Just saying there's a noticeable difference between the onlive MC and mojo when it comes to performance.
Vomit or had you changed the screen quality from 1080p to 720p at the first menu screen before you log in? That should help stop it looking like a vhs tape. But won't help with the controls.

Killing Floor calamity does not move past the press A to continue screen.

Its not locking up since the screen is still moving.
I have tried all buttons.
I have tried reinstalling the game a couple times.
I have restarted the shield tv.
The controller works in other games and the home screen just fine.
Anyone else have this problem?
Any ideas?

-RioT- said:
Its not locking up since the screen is still moving.
I have tried all buttons.
I have tried reinstalling the game a couple times.
I have restarted the shield tv.
The controller works in other games and the home screen just fine.
Anyone else have this problem?
Any ideas?
Click to expand...
Click to collapse
Just played this with my wife on co-op the other day. Had no issues. Did they just put out an update by any chance? If they did, then it was working at least before it.

theinspector said:
Just played this with my wife on co-op the other day. Had no issues. Did they just put out an update by any chance? If they did, then it was working at least before it.
Click to expand...
Click to collapse
It's strange. I imagine it works for people cause I see no one complaining.
Does it require 2 controllers?
Is there a way to check for updates in the play store on Android TV?
Sent from my LG-H811 using Tapatalk

I have the same issue. It happens on other games as well. Have not found a solution yet.

nanner87 said:
I have the same issue. It happens on other games as well. Have not found a solution yet.
Click to expand...
Click to collapse
had similar problems when i have the keyboard dongle plugged in. try disconnecting it if you have any mouse or kb plugged

Oh I gave up on this. I'll try unplugging the keyboard and mouse. Thank you.
Sent from my LG-H811 using Tapatalk

Mad Catz CTRLR - new one not re-syncing after it sleeps

Hey all. Hoping someone has a clue with this.
I bought a brand new CTRLR from Amazon to accompany my existing stock CTRLR, and decided to sync it up and use it for a while to give the stock one a break.
It's largely OK but I notice that if the controller sleeps, say, when watching a film, if I then press the HOME button to re-sync it, it doesn't work. Usually on the stock pad you would just hit the HOME button and the pad would resync and you could use it as normal. This doesn't happen with the new CTRLR, and I have to hold in the button as if I've just put the console on. Sometimes that doesn't work properly either and I have to switch to mouse mode and swipe the app away and start again. It's a bit of a pain.
Any ideas? Thanks all.

I can tell I'm really inspiring you guys to a response!
Anyway, I'm hopeful I've fixed it. At first I tried leaving the dongle in from the stock pad, even though as a retail boxed CTRLR it shouldn't need it, but that seemed to fix one thing and break others. However, I did a firmware upgrade last night and this seems to have worked.
I'm aware there's a bug open for this on KODI at the moment that some have reported. Some people seem to have the same issue. My concern with this was that it seemed to affect other apps, not just KODO. For example, if I left the pad untouched while Retroarch was running and let it go to sleep, I could not wake it. I *think* this may be resolved after the firmware upgrade but I have more testing to do.

At risk of talking to myself, but if it possibly helps anyone it does indeed seem to be fine now. Controller wakes properly after firmware upgrade on all apps apart from Retroarch. As such I can only assume there is an issue with Retroarch. Looking through their forum it does seem to suggest some sort of issue with their Android controller settings, so hopefully that will get spotted and fixed.