Guy's,
I've installed the new Homeup APK and Nicelock on my Ultra and it work perfect.
Did the same on my Plus and when I want to use the app via Nicelock I get the following message pop up:
"Homeup disabled because One UI Home is not supported"
Ofcourse I've rebooted my devices several times, uninstalled the app several times etc but nothing works. Only get this pop up but Homeup app wont start.
Someone an idea how to solve the issue?
UPDATE: had to update ONE UI to the latest version and then it worked. Issue Solved.
Related
My watch or phone has suddenly decide it will not message or make calls, my phone is a Galaxy S4, I have not installed anything on either device to change the status quo and yet every call or message request is answered by try again on your phone , the phone itself works fine, I have restarted both devices, any ideas?
You could try unpairing then repairing the watch from both devices . if not reset
Sent from my HTC One_M8 using XDA Free mobile app
Tried that after I posted, reset watch, but not phone, resetting the phone would be a last resort. I'm going to try it with another device Tomorrow so I can identify which device is the problem.
Same problem here
I have Nexus 4 with KitKat and Moto 360 with 5.0.1 and have the same problem. It started today. Tried clock reset android wear and Google Now reinstall, none of which helped.
I don't know if this is any help but on mine if I restart the phone I found I could text again from the watch, I would try to initiate a call and then I would get the error again, back to send a text and same problem.....BUT....if I restart the phone and only use the watch to send texts then it's fine, not a full fix I know but I'm hoping the update from 4.4.2 will fix it, just odd that it started overnight, everything was fine Friday??
Also, it won't register on my watch when a call is incoming on the phone.
Same issue here, though I am trying to use the "Note to self" feature: moto360 with a droid turbo, no lollipop yet.
Doesn't work even after a phone reboot, nor after getting Google Now setup. Anyone make progress on this?
Just got my 360, linked to an Oppo Find 7 (4.3). Having a lot of these "try again on your phone errors". Couple times it has worked, but often it doesnt.
Does the error signify a bluetooth link error or what?
Not Moto 360 but LG W Watch R...
.. with the same issue from today so this might no be a Moto Issue.
I took a screen shot of the watch, see attachment
The phone and watch are connected according to the companion and I do get notifications and cards on the watch
I've reset the watch an repaired, didn't work.
Restarted he phone as suggested by majreaper, didn't work
Phone: Xperia Z2, Android 4.4.4
Lg Watch R: Wear 5.0.1
My issue is solved
I have solved by downgrading Google Now app to version 3.6. Now I can initiate call and send texts from Moto 360 5.0.1 again. Using it with Nexus 4 KitKat 4.4.4.
What I did:
1. Go to setting > appplications > all
2. Find Google app
3. Uninstall updates
4. Get 3.6 version apk from apkmirror. http://www.apkmirror.com/apk/google-inc/google-search/google-search-3-6-16-1614640-arm-apk/
5. Install it.
You might want to disable autoupdates for Google app for now. It can be done in Play Market.
That fixed it for me, thanks samfromlv!
The above works for me at least.
I just tried the above suggestion and un-installed the google app update although I didn't install the link shown. I just downloaded the latest from the play store (as an update) and it solved the issues I was having (again at least for now). So worth a shot for anyone having this issue. Was tearing my hair out over this
I noticed today that the ADM does not locate my phone anymore. I dont think I installed anything out of the ordinary that would cause location problems. just general apps/games, rooted, xposed framework....
3rd party apps find my phone fine, just not ADM. I tried this method --> Android Device Manager Not Locating Phone Fix however it proved futile as well.
Any suggestions?..Or is anyone else facing this problem?
Thanks for the assistance.
I am running into the same issue as well.. The other day I tried following several guides to get to work, but in the end I signed into and out of my google account a few times, went into my google settings online and deleted all my old mobile devices, and eventually ADM starting working properly.
Unfortunately I just checked it today and ADM can't locate my device again. I don't know what the issue is now or how to fix it and keep it working.
Just tested with a ZF2 and ADM worked fine here.
ZF2 4GB
No Root
FW: Z00A-2.17.40.12_20150515_6168
- Steve
Hmm well I'll be getting another ZenFone shortly and I'll be giving my gf this one.. I'll factory reset it first n see if it makes a difference.. will respond according to the results
Sent from my ASUS ZenFone 2 using Tapatalk
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
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.
Just updated my Redmi Note 8 Pro this morning
went to look at Revolut account via app
double tapped on app - appeared very quickly on screen then disappeared
it shows up as 'active' but as soon as I tried to use it it disappeared again
anybody else had this problem - and any solution ?
I have the exact same issue with the exact same phone model. I updated it today and it's been giving me issues with Revolut ever since. Rebooting won't work.
Absolutely ridiculous how each update seems to bring bigger issues than fixes... If anyone knows any possible solution it would be greatly appreciated, it's terrible being locked out of my bank app due to an irreversible update
tremoceiro said:
I have the exact same issue with the exact same phone model. I updated it today and it's been giving me issues with Revolut ever since. Rebooting won't work.
Absolutely ridiculous how each update seems to bring bigger issues than fixes... If anyone knows any possible solution it would be greatly appreciated, it's terrible being locked out of my bank app due to an irreversible update
Click to expand...
Click to collapse
In the end I reinstalled the app - and it worked
Same issue with update 12.5.2 on Redmi Note 8 Pro.
I had to reinstall Revolut in order to make it work.
I updated to 12.5.2 and same issue - but I had to factory reset the phone anyway as it was running so hot - now Revolut works BUT the battery drain is huge
DRAGOSCB33 said:
Same issue with update 12.5.2 on Redmi Note 8 Pro.
I had to reinstall revolute in order to make it work.
Click to expand...
Click to collapse
Revolute? What app is that? One is Revolut
AlphaBravo said:
Revolute? What app is that? One is Revolut
Click to expand...
Click to collapse
I added my mistake the final "e", Revolut is the correct name. Thanks!
I have same problem after installed new 12.5 MIUI.
Solution:
On PC download extension ‘APK Downloader’ and install it in Chrome, Fox…
On PC go for google play store and search for Revoult, then download APK by new extension.
Copy revoult.apk to your phone (//download).
Use Files Menager in your phone, use APK and install it.
Done, Google Play store still showing red incompatibility message, but it works.
Good luck!