Yes , here it is again but now on the G3 (Verizon). I have done all the many suggested things after googling this message yet it still happens (not always) but pretty regularly at boot up. Anyone else seeing this on their G3?
already done:
rest apps preferences
re-enabled download manager
uninstalled new beta Google play store and reinstalled the stock one
uninstalled swiftkey (just in case)
maybe a few other odds and ends I forgot just now.
Noticed after I installed google keyboard.
I uninstalled it and it works fine. Proper load. I hate this lg keyboard. Come on paranoid android roms
Yeah, I have that google keyboard as well for the new L skin. I wonder why keyboards have this effect. I remember the swiftkey on did this for a while on the G2. Well as long as I know that is causing it I might be able to live with it for now. It's just not knowing which was getting to me.
Related
Hi people!
All of a sudden going into "handle programs" in settings on my HTC Desire force closes com.android.settings. BAM! I've tried rebooting several times, no difference. Even tried uninstalling the last application I installed but it still force closes. Now uninstalling through the market works fine, so it does through the astro program handler, but why does my core settings app all of a sudden crash bigtime?
I've not rooted the device and I don't have much fishy stuff on it, the most fishy thing I guess is the HTC IME modded keyboard from jonasl that adds the microphone button and a milllion other neafty tricks. I'm not sure if this started happening then or later. Any ideas?
Kristian
I had the same issue. I had been installing ALL sorts. I had to back up what I could and do a factory restore to resolve it.
I hadn't installed the Voice Search workaround yet at that point so it wasn't that. I think I narrowed it down to one of the app killer programs. I uninstalled that and it's been solid since. On top of that I never really gave the phone a chance without it and now I have there was no need for it in the first place.
Aitese said:
I had the same issue. I had been installing ALL sorts. I had to back up what I could and do a factory restore to resolve it.
I hadn't installed the Voice Search workaround yet at that point so it wasn't that. I think I narrowed it down to one of the app killer programs. I uninstalled that and it's been solid since. On top of that I never really gave the phone a chance without it and now I have there was no need for it in the first place.
Click to expand...
Click to collapse
- So you found it was one SPECIFIC program that when being installed caused this problem? That's what I am gussing too, I just don't know WHICH program.
Did just uninstalling that particular program fix the issue or did you have to do the factory restore to fix it even after uninstalling the offending program?
Locale may cause this behavious, do youhave that installed?
le3ky said:
Locale may cause this behavious, do youhave that installed?
Click to expand...
Click to collapse
I was smiling when I read this because I was just thinking "could it be locale, that was recently installed", and YES not only is it installed but it's one of the prime suspects, timewise.
It's the beta version that apparently still works here in sweden where there is no pay market. So that program is known to cause this, crap! I'd really prefer keeping it as it's my "don't bother me at night" app. Is it known to cause any other problems or just the fact that the stock progarm handler app FC's?
TigerSoul925 said:
- So you found it was one SPECIFIC program that when being installed caused this problem? That's what I am gussing too, I just don't know WHICH program.
Did just uninstalling that particular program fix the issue or did you have to do the factory restore to fix it even after uninstalling the offending program?
Click to expand...
Click to collapse
Well I like I said, I think it could have been that program. My problem was only solved after the restore. I put back everything else but that one app and it's fine.
Ok so I did uninstall locale, nothing changed, I scratched my head, and cursed. Then I also installed the two plugins I had installed for it, namely the battery/charging plugin and the all vols plugin and guess what? TAADAA it works again as expected. Either it was locale in combination with those plugins or one of the plugins themselves.
I don't really care which because I just found "settings profiles" which is everything locale is bundled into one program and as a matter of fact I only need one rule making this free for me, great!
Still don't know which of the plugins or locale or combination caused this but I guess this is a word of caution to others going down a similar road.
i've been getting similar errors and i DID have locale installed but i'vs since uninstalled it and the plugins and it's still broken. :-(
guess I was lucky then, make sure you uninstall ALL plugins for it, for me it related 100% to locale or it's plugin (or both).
Been using Swype since before the beta closed (July?). I had my EVO replaced in September, but I was able to install Swype on the new phone without any problem. And it has been working fine.
I rooted my stock 2.2, and Swype continued to work just fine.
This past Sunday, Swype would open but not "swype" (I could still type like normal). So I force closed it and restarted, rebooted, switched keyboards and back, etc. Nothing I tried would get it to work.
Finally, I un-installed it. Now it won't re-download it. I get an error message telling me that my device is not an Android phone. That's news to me (and I'm sure to Sprint, HTC, and Google).
I also un-installed the installer, but continue to get the same message.
Swypes web site says I can un-register my phone and re-register it, but only one time. I don't want to do this if I can avoid it because then I will be screwed if this happens again. Plus, like I said, it was running fine till this past Sunday.
I wrote to them asking for help but still have not heard back. Anyone have any other suggestions?
It probably expired. Unfortunately we are not allowed anymore to distribute the Swype apk so you are going to have to wait until Swype releases the real version, or find the apk on your own. Your not even supposed to have Swype on your phone so emailing them wont do anything.
Thats odd because I redownload swype all the time everytime I flash a new rom. I dont back up my apps . So you are saying you are logging on to the Swype Beta site and it wont let you redownload a new installer?
Did u have your phone on WiFi along with being logged in on Swype.com on the same wireless network? I had that problem the other day, and I just turned off WiFi on my phone and I was able to re-download the installer.
EVO on Tapatalk
fmedina2 said:
It probably expired. Unfortunately we are not allowed anymore to distribute the Swype apk so you are going to have to wait until Swype releases the real version, or find the apk on your own. Your not even supposed to have Swype on your phone so emailing them wont do anything.
Click to expand...
Click to collapse
I believe you are incorrect. As I said, I AM in the beta program. I am supposed to have it on my phone.
As to the other replys, the Swype site is telling me that my HTC EVO with rooted STOCK 2.2 IS NOT AN ANDROID PHONE!!!
WiFi or no WiFi, it wont let me download the installer!!!
If I don't hear from them by tomorrow I guess I'll use my one opportunity to change the registered phone.
Titainium Back saved the day!
Guess I'm old and slow, but I just remembered one reason why I rooted was to install T.B.
It let me restore Swype and I'm back in business!
Of course, I have no idea why it stopped working in the first place, so it could happen again. Also, I have no idea why my phone isn't an Android!
ultra keyboard is a good alternative too if you ever needed one
Had the same issue. FAQ on Swype's website says it could be a problem with your browser on your phone, either in desktop mode or not using stock internet client.
I was actually using stock internet, but on ICS 4.03. So I changed my default browser to XScope and was able to download the installer.
I am updating my old HTC Incredible to give to a friend who demolished their smart phone and cant updated right now.
I have it currently at 4.08.605.15 ... seems okay.
But when I hit Market, it loads a web page to Google Play rather than opening up the market app...
Not quite sure what is going on.
Note that I currently have the phone on wifi only.. no VZW service...but I don't think that should matter.
UPDATE...
Just finished posting this... and I look at the phone and the New Market (google play) Icon is now there... strange...
krelvinaz said:
I am updating my old HTC Incredible to give to a friend who demolished their smart phone and cant updated right now.
I have it currently at 4.08.605.15 ... seems okay.
But when I hit Market, it loads a web page to Google Play rather than opening up the market app...
Not quite sure what is going on.
Note that I currently have the phone on wifi only.. no VZW service...but I don't think that should matter.
UPDATE...
Just finished posting this... and I look at the phone and the New Market (google play) Icon is now there... strange...
Click to expand...
Click to collapse
Play Store (aka Market) will update itself if you give it half a chance and a data connection, so the change of icon is not surprising. Is it working now?
Yep.... was a bit confusing since I thought the apps had not loaded properly. Guess I never gave it a chance to update until I set it down to post.
Just put the phone through the various apps it comes with... works great... haven't picked it up for sometime since replaced it with my Rezound.
Recall it being the best phone I'd had up to that time.
musical_chairs said:
Play Store (aka Market) will update itself if you give it half a chance and a data connection, so the change of icon is not surprising. Is it working now?
Click to expand...
Click to collapse
I am having the same problem. No data connection, just "WIFI". When you said data, is this the only way the play store will update? I just flashed Touch of blue V:2.2 Not trying to hijack but keep the threads together since they are the same issue.
EDIT: I figured it out! After resetting the phone a couple times it worked. You have to be quick and click on the market while looking for the "accept" button to appear. It will only be there for 1 second and if it's not hit in time you will be redirected to the google play website. Hope this might help someone else.
I'm surprised this is still an issue even with Android 6.0, but... Has anybody ever figured out why it doesn't seem to work at all for apps?
Over many phones, many ROM's, and many versions of Android, I *always* have the options checked for this feature. Almost never does Google restore my apps from the store. I've seen it work maybe 5% of the time, where after signing in, the Play Store will start reinstalling all the apps I had previously.
So, has anybody ever figured out a trick for this? We posted this issue to Google years ago. By Android 6.0, it seems like this is a really stupid issue to have, especially for people who don't know how to back up apps or are switching to a different version of Android (where the app should be downloaded again, not restored from a local backup).
Mates,
I don't know if the Kevo/Kwikset app folks are dumb, lazy or if there is some fee they have to pay to support new phones, but hear my tale of woe, with a happy ending (a minstrel on a mandolin is playing in the background as you read this).
I put Kevo locks everywhere when they first came out with android support. When they work, it is one less key I have to carry, one more thing my everpresent phone can do. They were announced as partners for the Gear S2 which, as we all know, is bull. The tech writers who said it worked were clearly Samsung lapdogs.
The Kevo website says that the app won't work on the Galaxy S7 edge but it did. Right from the start, right out of the gate. Then T-Mobile rolled out a patch last week and it stopped. Nothing. Bupkus. Google Play says the app is not supported by my device.
A little bit of searching led to the actual newest Kevo apk. I downloaded it, deleted the old app, installed it and voila! Back in business. The new version supports remote open and close, which I haven't checked yet- I bought an upgraded lock but it isn't installed.
So, there you have it. I have no idea why Kevo/Kwikset/Unikey didn't test with the newest phones, why they don't know it works or whatever. Their developers are much more interested in supporting iOS and the sheeple that use it, but it will work for us too!
where did you find the latest? i looked for almost 2 hours and the best i could come up with was the 0.99 beta in the google groups. had to sideload an app that lets you change your device to trick Play into letting you install it.
Googled Android kevo apk, found version 1.2.57.2p everywhere. I presumed that was the latest since it has the remote buttons on it.
yeah i saw those results as well, but none of the apk downloaders worked for me. several even said their 'device' was incompatible, which was the same problem i was having.
I'm in the same boat. I have an S7 Edge and while kevo still works with just the proximity and tap lock to open...I've never been able to get the tap to unlock/lock work. Even on my moto360 (gen1) kevo force closes non stop. Another problem I had was my old S5 was on Lollipop and it worked, but then Tmo rolled out the update to MM and now it doesn't even see the lock. I've had multiple emails to Kevo and the only thing I get is that "We're sorry, we have no plans to support MM".
If you got anything to help out with Kevo working on Marshmallow, then I'd appreciate it as well!
I might be a little late on the the subject but I had the Kevo app since the beginning from my Note 4 on KK all the way up to My Note 5 on MM. I rarely use my Moto 360 (1) to open the door but this time I did and the watch went haywire and kept showing a notification indicating that the app is no longer working. So I decided to uninstall the Kevo app and then proceeded to sync the watch and phone, stopping the annoying notification. When I went to the app store to reinstall I found the "phone not compatible"..
Well, decided to sideload to have the Kevo app to look and work the same way I had it before.. after several attempts I figured it out. 1st sideload the Kevo 0.9.58p apk, sign in, then sideload the updated version 1.2.57.2p and it will finally look and feel like the updated one on Lollipop. Sefar is right, why the devs were so lazy in checking for compatibility is beyond me but it works.!!
Sent from my SAMSUNG-SM-N920A using Tapatalk