Hi
I'm using android studio to create my app, now everything has been working fine till last night where now every time i run my emulator it get the message "unfortunately launcher3 has stopped" even before the phones UI loads up; now i been looking at my code and i removed anything new i placed in the code before it would crash however the problem is still there and when i look at the errors on android monitor i i receive problems in Drawable.java, Resources.java, Handler.java, Looper.java, Bitmap.java (all of those are not the ones i manually created) and they contain errors of cant resolve method/symbol. I even stated up a new project with a simple Hello world and same problems (also tried a restart, clean and Rebuild and as well as uninstall and reinstall studio)
Related
I rooted my phone for the first time this weekend and loaded Cyanogen MOD. Everything is working GREAT, except for one issue with Locale. When I go in to setup a a new situation it won't let me add a location condition. I hit the "Add Condition" button, hit Location, and all it does is go to a black screen for a second or two and then takes me back to the "edit situation" screen. After I hit location it looks like it's trying to load the normal location select screen but can't for some reason. Anyone ever see this or have any ideas why it might be doing that? Any help would be greatly appreciated.
The app has worked flawlessly for me and I have always had root but I think the latest update made this feature not work which is unfortunate.
I installed the 4.0.2 Cyanogen ROM yesterday and setup a new location in Locale as recently as an hour ago. Do try an uninstall and reinstall of locale and make sure you're running the latest version of Google Maps.
I already tried un/reinstall of Locale to no avail. I just tried un/reinstalling Google Maps as well, but that didn't work either.
Any other ideas?
Try opening google maps and finding your location in there first. I did that and it magically started working again.
So, nothing I tried worked (even opening google maps first). I started to get more suspicious when I noticed a few other map-enabled apps would work as well (mymaps editor, weatherbug, etc). So I decided there must either be something wrong with the version of the ROM I loaded or something else I had done messed up something with the maps. Loaded the latest version of cyanogen and now it works great. Go figure.
Thanks for all the suggestions anyway.
According to the developers website they know about the issue and its being blamed on people with rooted phones. Their solution is to go back to an OEM build of Android which is total bull**** so I sent them an email letting them know.
"Why can't I open Locations after the latest update?
This happens frequently on rooted phones, phones running unofficial installations of Android, or phones modified in some non-standard way (e.g. running apps off of the SD card). Try restoring your phone to an officially supported version of Android."
http://www.twofortyfouram.com/support.html
Locations doesn't work on hacked phones, because the Android on these phones has a problem loading the Google Maps libraries. This is NOT a bug in Locale, and there is no code change in Locale that would fix the issue.
In order to investigate this issue, I've taken these steps:
1. Contact Google: Initially, this appeared to be a bug in Android. Google investigated and found that only hacked phones had problems, at which point they considered the issue closed.
2. Contact Steve Kondik (e.g. Cyanogen): He is looking into issue, but I haven't heard anything further from him.
At this point, there's just nothing else I can do. I can only suggest reverting to an official version of Android.
- Carter
Hi all,
I'm having a problem that has been described elsewhere but none of the problems sound "exactly" the same as mine, and none of the fixes I have tried have worked
Phone:
Samsung Galaxy S GT-I9000M Bell Canada
standard (not rooted)
Recent Changes:
The only recent (ie in the last week) change I have made to my phone was to install a camera firmware upgrade via Samsung apps. Did that on Jan 26. Since that time I've noticed the issue.
The issue:
Upon opening the Android Market app, after a short while waiting on the "loading..." screen, I receive this message:
"A server error has occurred. Retry, or cancel and return to the previous screen."
If I hit retry, or if I am fast enough on the initial start of the market app, I can actually hit the search button, enter a search term, and it tries to search (but never returns a result)
If I hit cancel it closes the market app.
Then usually, but not always, a few seconds later I receive a force close error message
"The Application Market (process com.android.vending) has stopped unexpectedly. Please try again."
I haven't been able to figure out why this only comes up some of the time.
What I have tried so far:
Clearing data/clearing caches of various apps
uninstall android market updates
uninstall recently installed apps (removed the aforementioned firmware upgrade)
Change Google account password - after changing via a PC, the Market App then prompted me to enter the new password - but then the same result "A server error has occurred..." etc
Tried using WiFi
Tried using 3g
Tried adding an account (settings>manage accounts & sync ... the blue G for google icon and entered my gmail info) This triggers the same force close "The Application Market (process com.android.vending) has stopped unexpectedly. Please try again."
After each change tried a reboot (inc remove battery & wait a 5 minutes)
Trying to avoid doing a factory reset - from other posts it sounds like it hasn't worked for others, and I've had 4 issues in the last 4 months that required a reset ... getting mighty sick of reloading everything!
any help is much appreciated!!
PS. Not sure if this is related - Social Hub force closes every time I reboot the phone - process com.seven.Z7 - only way I've found to fix is to go into samsung apps and reinstall every time I reboot. That sucks, but not as bad as having no market app!
Market is being updated currently.
the same problem
hi
i have the same problem , the market doesn't allow me to download any app , it force close before entering the app page , i tried many things and stil the same problem
it always bring me this error msg
THE APPLICATION MARKET (PROCESS COM .ANDROID.VENFING) HAS STOPPED uNEXPECTEDLY. PLEASE TRY AGAIN
please tell me what i shall do as i can't install any appp on my galaxy
- eclair 2.1
I seem to be the only one with this problem
If I go into Google Now and start typing in the search box, shortly after it goes off to google to get suggestions it closes
If I select a previous search it closes
If I do a voice search it interpretes it, then closes before acting on the instruction
It was working fine up until today.
I've removed recent apps, restarted, removed sideloaded 9non-store) apps and restarted - still no joy.
The only other thing that I've done is mounted it via MTP on my linux desktop to transfer some files earlier. Probably coincidence
I've uploaded a video of the behaviour. (remove spaces in url as <10 posts = no links)
youtu.be/ NgZgjfyRX1I
Any ideas before I do a factory reset?
more info
from ideas on the youtube clip;
I've checked, the system is upto date
I've confirmed the issue existsed with the stock keyboard (I use swype)
Any other ides before I factory reset?
Both my google play, and Android wear are completly updated. However when ever I try to start certain apps it tells me i need to update either google play services or android wear, both of which are the current version. This seems to effect mostly the google apps like google keep. Any Ideas, I just got this about 2 days ago.
This is happening to me too. On the Android Wear phone app, certain actions are either greyed out (navigation) or missing entirely (texting). When I try to open certain apps on the wear I get a grey screen that says "Update Android Wear on your Phone". And that's it. Other apps like custom watch faces will not properly sync or update and give me a "Try updating google play services" error message.
I've tried resetting the watch several times along with resyncing apps, reinstalling the Wear phone app, etc. None of these are fixing the issue.
DRMMR144 said:
This is happening to me too. On the Android Wear phone app, certain actions are either greyed out (navigation) or missing entirely (texting). When I try to open certain apps on the wear I get a grey screen that says "Update Android Wear on your Phone". And that's it. Other apps like custom watch faces will not properly sync or update and give me a "Try updating google play services" error message.
I've tried resetting the watch several times along with resyncing apps, reinstalling the Wear phone app, etc. None of these are fixing the issue.
Click to expand...
Click to collapse
Yup. Same think. Also i see that some people are able to even text via the watch though the phone which i cannnot do.
My watch still says android Software version 5.0.1 but my friend who had his longer has been 5.1.1 for a long it me now. This is one of the big reasons for me to think of rooting and trying a custom ROM but I dont really see any. Or even flash the update myself.
The watch won't update until your phones updated.
Go into settings on the watch, check out the build number. If it contains 'sprat-userdebug' in the string then you aren't on a base rom and you need to flash it stock. Just got mine and apparently this was/is known from a batch that went in to the reseller market. BestBuy got nailed by it and lots of pissed off people.
There is a tool here that can help you get on a stock rom that will allow the OTA updates to happen.
I'm in the same boat, haven't had a chance to try it yet but will report back tonight.
EDIT:
Worked great - flash back to the stock ROM, pair with your phone and it will get the OTA updates. They take awhile and process one by one, but success. Good luck! I had a rough time getting the ADB drivers on Win 8.1, although I think it's my crappy laptop. Worked on a Win 7 machine I had around without issue.
All my google play services were wiped out, Google play crashes when I try to open. Is my tablet hosed? Don't they test these effing updates?
I read somewhere dual apps can cause problems, so I deleted my only dual app on the phone (WhatsApp) and made sure that "user 999" is no longer there ("pm list users" shows only user 0). But the problem with Android Auto still persists.
It simply crashes after the initial configuration. Then subsequently every time I tap on the icon to run it, it crashes and quits right away.
I cleared data for both Android Auto and Google play services. Same problem.
I did some debloating when I started using the phone before installing Android Auto. Could this be the issue, that I debloated something that was essential to Android Auto's operations?
I also have Magisk running on the phone. Tried hiding Android Auto (Google Play Services is already hidden). Same problem.
Any help appreciated ! Running MIUI EEA 10.2.26 by the way.
Found the issue.
In app permissions I allowed the app to access calendar. But I have removed Google calendar from the system with adb tools (I use Outlook so Google Calendar becomes redundant). I guess Android Auto assumes Google Calendar is always there so it crashes when it is not found.
I disable the calendar permission and everything works now.