So after updating to the newest version of Google Now, it now force closes. Any idea as to why? I was able to roll back to the previous version and it works fine now.
Edit: After reading some of the development forums this issue seems to be affecting the JB based ROMs (CM10/AOKP). If you're running one of these, it's likely the problem relates to the oes texture problem. Sadly that problem isn't likely to be fixed.
It's helpful to note if you're running any custom ROMs/scripts. There are many circumstances that could cause an app to FC, and more info could help us point you in the right direction.
Sent from my DROID X2 using xda app-developers app
I am running CM10 Alpha 2
Its most likely what ROMFlashah said. It probably has to do with the textures. Our ROM doesnt have these so when it tried to use them, it force closes. The same thing that happens with Gmail and others. Its sad to think we will no longer be able to use any update they put out for google now from now on.
Related
Anyone else having issues with the new Google Play Market? Literally every app I open up reads as incompatible with my device. Is this the case for anyone else? I'm currently on Vegan Froyo... is this just an issue for this ROM, or is it with all roms? Personally its becoming incredibly frustrating; many of my existing apps don't update, I'm forced to scour the dark ends of the internet for apks of paid apps I already own.
I tried the Market fix.. but that seems to have made issues worse. Any hope??
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
What apps fail? Give some examples so that others can
tell you if they work on their Vegan Froyo. Apparently
tapatalk works for you .
What is "ro.product.device=" in your /system/build.prop ?
A bad value/corruption there can cause incompatible messages.
I am on TNT Lite, which a Froyo distribution, and Google Play
works without any problems.
This is when an old CWM backup might have helped. Do you have any around?
My latest magic bullet for Froyo is "Fix Permissions" from CWM.
Give it a shot if all else fails.
--
I also am having a ton of issues with the new and "improved" google experience... the playstore will not load at all on my gtablet. I am running gtabcombover and really like the ROM... it was flawless until the market went stupid on us.
as soon as i try to open the app, i get the "accept" button but before I can even push it, the thing FC's and no matter what I cant make it even initialize. I am really hoping there is a painless and simple fix for this mess. And even more hoping that google hasnt completely cut all rooted devices out of the loop!
any help would be greatly appreciated
thanks
I'm having the same problem as the OP, except I'm using Roebeet's TnT Lite Froyo ROM. I've also tried the Market fix with no luck. Any ideas for solving the problem would be appreciated.
Every app that needs to be updated comes back with a "incompatible with your device" error. Market fix didn't make things worse for me, just didn't help much. I'll have more time for experimenting over the weekend, and, will post if I find an answer. Hopefully it's not due to Google Play seeing it as being a rooted device.
It's probably not because the device is rooted. I am running G-harmony and play works fine for me.
Google Market updated itself to the Google Play store without any problem on both VEGAn-TAB 7.1 and GtabCombOver 3.4.2. I was also able to update all of my apps as usual.
I'm using cm7 rc1 and market is hosed. I have tons of paid apps that are "incompatible" and wont update. I tried build.prop edits but nothing is working. If VeganTAB 7 is working I may switch back to it. Was using beastys rom and Google play made it so half my apps wouldn't update that's why I tried cm7.
Update:
VeganTAB 7 works great with Google play and all my apps updated.
Mantara said:
I'm using cm7 rc1 and market is hosed.
Click to expand...
Click to collapse
Try this suggestion out the next time around, instead of resorting to installing a different ROM.
Google Woes 2
I have a rooted G-Tab with Calkulin’s ROM v1.1 and clemsyn 2.6.32.9 kernel. Everything was running great with no problems. Google changed to Google Play and something has happened with the authenication. Downloads fail (all of them) and the Market fix does not work.
Gtab using Flashback 10.3 Google play
Similar issues here as well, My apps are updating ok but when I go to open Google Play to search for an app it crashes/forces closes. Been searching threads and found none that give clear fixes for this. THANKS GOOGLE!!!!
@aNiMeMaN14
If you know how to edit the build.prop you could try to edit the line for the manufacturer replace what's there with Samsung just remember to make a note of what was there to start. It worked for me but I'm on the DRH ice rom you you may not see it in the overall search but in you put in the name of the app you want it should come up and allow you to download n install. REMEMBER IF YOU ARE NOT COMFORTABLE DONT DO IF YOU MAKE A MISTAKE COULD CAUSE YOU TO NVFLASH AND REBUILD FROM START HAVE BACKUP. TRY THE ONE IN THE CWM ROM.
there is a modded market available now thanks to the people here on Xda
http://forum.xda-developers.com/showthread.php?t=1582422
I really dont understand this. I have erased and installed this ROM MULTIPLE times. I just switched from SHIFT AOSP ICS3.2.1 (DHacker) to Liquid smooth roms 3.2 release with MR4 Support. Every time i go to google play it tells me multiple apps wont work with my phone. Is there ANY way to disable google play doing this? Its the same apps, some of them i have downloaded the APK to install them but then google play wont update them and when they come out with an update ill have to go find the apk all over again which is annoying. I really dont understand i went from a CM7/AOSP based rom to another CM7/AOSP based rom and it hates it.
I had the same problem once, never figure out why. It just got fixed by itself I guess. But try rebooting the phone my best guess ...
By the way liquid 3.2 its my main Rom and daily driver too.
Sent from my ADR6400L using xda premium
Go under apps and clear data
Luke
I think this has something to do with your ROM being Sense or AOSP. Try backing up your ROM, switching to sense, run GP and see if they show up there, then a fresh install of your AOSP ROM.
Sent from my ADR6400L using Tapatalk 2
So I finally figured it out. Rooted a friends phone and had the same problem. Come to find out it's all resolution based. I changed the resolution back to stock, clear data, waited a little after a reboot, clear data again and I was now compatible. There should be an override.
Yeah I was going to say when you started this friend don't mess with the DPI because it breaks the market.
This doesn't belong in development it belongs in general
Hello, I've tried all of the google now zips from this thread
http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
google now does load up and work for 1 or 2 questions but then the phone will freeze and either reboot or lockup, I've checked the file permissions and everything is correct, I'm wondering if anyone else has tried this on their ICS Atrix 4G, mine is unlocked from Bell Canada running CWM and Turl's most recent CM9
I've had the same problem with Google Now on ICS and have tried everything before finally upgrading to Jelly Bean (I can't live without Project Butter anymore). All those different builds, each one having different issues, right? I have always thought it was just me, but now I see I am not alone... Or maybe it's just us...
Anyway, every single one of my attempts to make it work have failed.
I do have a solution for you though: Maluuba (https://play.google.com/store/apps/...ce=google&utm_medium=organic&utm_term=maluuba)
It's an app available for free on the Google Play Store. It's a bit different from Google Now, it's more like a Siri alternative.
Sent from my MB860 using Tapatalk 2
I'm running the latest 9/16 build of CM9 on my Note with AT&T and for the last 4 weeks or so have had NO problems. Starting yesterday I was getting "unfortunately, maps has stopped" messages. Got a couple of them, then all was good, today it started again. I reverted back to 9.1 stable but am still getting the same message. I found a thread in the Nexus 7 forum regarding the same issue but no resolution. I have the latest maps version 6.12.0 and have my GNex and Xoom at my desk with me (GNex running on T-Mobile and the Xoom on Verizon) with no issue whatsoever. I did clear cache and data in the map app and rebooted as was one possible solution in the Nexus 7 thread but that didn't seem like it was a permanent fix based on the other comments.
*AT&T is currently converting my area to LTE (outside of Philadelphia) as we speak though I can't imagine that impacting the maps app but I figured I would mention it just in case.
Any help or suggestions would be appreciated.
This may be wildly coincidental, but I experienced the same messages after trying to install Google Now on CM9. I then re-wiped and re-flashed without issue.
I've been running the latest version since it was posted and I have not added anything new...strange I have not had a single error message since 3 this afternoon??
Sent from my SAMSUNG-SGH-I717 using xda premium
Have you checked permissions for maps ??
Or fixed permissions for all apps ??
Often times the permissions are wrong ...and the app will produce errors or force close ...
Just thinking out loud ...g
Also ....
Maps is highly dependent on the services framework ....
You could also delete your account info and set it up again ......using the data wipe option ...then load maps again ...g
Again ...just a thought ...g
I have never touched the permissions don't know even where to go to check them?? I will do a little research when I get into work and see if I can figure it out thank you for your advice.
Sent from my SAMSUNG-SGH-I717 using xda premium
Hi everyone,
I have tried to search for a solution to my problem but I haven't been very successful. If anyone knows of links to possible resolutions to my problem, please reply with them.
I have an issue with the chrome browser starting with a completely black screen. At first I thought it was only my last phone (RAZR HD), but the problem is also present on my Verizon Note 3. If it were just an issue on a single phone, I'd probably ask in specific phone forums, but it's happened on two different phones now.
I'm presuming that the problem might be caused by an app I'm using, but the problem is intermittent so I can't tell if the issue subsides when I uninstall certain apps.
Any help or insight in this issue is appreciated.
Thanks
I have the same issue. Seems in my case its ANY 4.3 rom. It started after an update to Chrome around the fifteenth or so of November. It'll work but if I change tabs or switch apps it will turn black when resuming. Older versions of Chrome don't have the problem. I've gone back to a 4.2.2 root box rom with no problems.
Sent from my SGH-I747 using Tapatalk
Drdavbo said:
I have the same issue. Seems in my case its ANY 4.3 rom. It started after an update to Chrome around the fifteenth or so of November. It'll work but if I change tabs or switch apps it will turn black when resuming. Older versions of Chrome don't have the problem. I've gone back to a 4.2.2 root box rom with no problems.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
The latest update to chrome doesn't render the pages immediately.
This would most likely be to open chrome faster.
However, users are reporting that they don't get past a black screen.
This is common.
Go complain to google devs though, not here. (The bug tracker they have)
Right on. Will do. Not so much complaining as just sharing with the OP. Thanks for letting us know its very common. My searches have not returned much information at all. Including Google searches and searches here and on XDA.
Thanks again!
Sent from my SGH-I747 using Tapatalk
I see. My RAZR HD was still on 4.1.2 and this was an issue there too. Thanks for the information.
Side note: I'm glad I wasn't the only person having difficulty searching on this subject.
sorry for the huge bump but if anyone was wondering my dpi was 350 and this issue stated when my Rom was changed to a 350 DPI. I used xposed and App Settings to change the DPI of chrome to 480 and no more black screens
EDIT(2 hours later):Nope it just came back.