Hello,
I would like to ask question, hoping someone will be able to help me solve this problem.
I have the fossil 5 garrett and somehow i stop getting the notification although everything is setup well at the phone and the watch.
The only thing that solve this problem is Uninstall the wear os in my phone and install it again, but then again after one or few days the notifications dissappear again.
It doesn't make sense to Uninstall and install the wear os every few days. I thought maybe it's something with the app power setup and i changed it to manually so the app will work all the time but still i dont get the notifications at the watch.
Do you have any idea what can cause this problem of notification dissappear?
Thanks,
Nessi
My Fossil Gen 5 also loses notifications at times, seemingly if it hasn't undergone a restart after a few days. It sometimes auto-restarts when placed on the charger. A small inconvenience, but this keeps it working well. For restart, press center crown button for Apps, then Settings, scroll for Restart.
Related
I've turned off the section under battery "Turn off if not used for X minutes." This just started recently happening as well, I don't have too much software, and the ram looks fine. Every time it comes out of sleep there is a 3-5 second freeze that will not allow me to do anything, including dialing numbers, going to any screens, closing anything, etc.
I need to know how to fix this incase anyone is running into the same issue. The only recent software i've installed is the AIM 2.0 hacked, and I don't leave it running. This leads me to my next question, is there a way to get the phone to continue to stay connected once the screen goes out, it seems that is whats causing it to sleep, and cuts off my aim. (This isn't what is causing the freeze however, the app is completely closed, as are all others.)
I could desperately use some help, at this point its causing me to miss phonecalls as I press the pick up button, it doesn't register and by the time it does, they've already been forwarded to voicemail.
sometime i have the same problem...
So it definitely is about 18-30 seconds, not 5 like I had assumed. I'm awful with time, my apologies. I could desperately use a remedy
hi all,
i having my 1st Android phone (HTC Legend), but my set suffering Standby on Death (SOD), not sure if the right term. When it on standby, I not able to wake the phone; only way to remove the battery and on the phone again.
However, during it 'freeze' mode, try calling the phone; won't ring but caller doesn't get any engaged tone keep trying connect tone.
Please advise if any1 experience the above or any steps I can do.
** Try searching the web, only found SOD on Win phone.
Cheers.
Edit/Delete Message
The same thing happend to me yesterday, for the first time (I pulled out battery to reset it). I had a few random resets last few days, but I do use my legend for app development testing, so i'm not sure if i somehow provoked the problem.
Offtopic, but just looking at logcat output of a normally running Legend you get impression that there are a lot of unfinished stuff, especially HTC applications (news widget is terrible)
I'm also seeing the same random resets on my Legend. Not sure what when wrong. I have a bunch of apps installed but I don't know if this relates to any of them.
It happened again just now. Restarts on daily basis now
just make a hard reset
Ok. I did a hard rest. And i don't want to install any apps, let it run in vanilla flavor for 2-3 days and see if it happens again.
If it does, that means it must be caused by one of the apps installed before
I had some SOD's, but after a complete clean and reset to original setting, everything disappeared.
Maybe it was a problem coming from installed software...
clean reset, wiped out everything. reset after 15hrs of up time. i'm going to RMA this thing
Hi all - first post here...
I have not long had my first HTC handset - and I really like it, but nearly every day I get this 'SOD'...as described here.
I had to remove the battery to wake it up again only this morning.
I have noticed, that it only seems to do this when it can't recieve the weather data (under the HTC clock)? the handset never seems to hang etc while it has this data?
Have others seen this? Could it be a bug?
Why not bring all SOD threads to one?
As I see all SOD's are same on all devices.
There is bunch of symptoms but if you have sod than you are experiencing some or all of the symptoms.
General help is to hard reset few times than flash shipped ROM then hard reset again few times then flash your favorite custom ROM or leave shipped, and reset again few times. And finaly set network to GSM+AUTO in Phone band configuration. Or try to change SIM with another network operator.
All of this helped some people but there is many who did not solve the SOD with this nor anything else.
I know I am posting in more than one thread same thing and it is not double or triple or X posting it is just help request for people who could finaly understand what is problem and help us all.
Sory, and thanks in advance.
Weather is not problem on my device, I did try turn it off, disable auto update of everything .... no difference.
Even I leave it connected to USB and it have the internet connection all time and I do not have SOD, I have DIM of death screen dims not turn of and if I disconect it and pres power to go to stand by or to turn off screen I can not power on device until i pull battery out few times - 4 - 5 timesto be precise or sometimes even more.
I got a new replacement unit and it works fine since. I guess my old unit was really defective
Sent from my Legend using XDA App
I have had to have my handset replaced now. My SOD contiuned and then the Mic gave up and no-one could hear me in calls - made it unusable as a phone. I also had battrey issues where the phone wouldn't charge and the battery meter read wrong.
All seems fine with this replacement handset.....
I have a Nexus 5 (4.4 stock). No Exchange accounts configured. I do use Pushbullet and NILS adn also have a Garmin GPS paires via Bluetooth.
I bought a Moto 360 so installed Android Wear. It started crashing instantly. I rebooted - same thing. I uninstalled/reinstalled - same thing. I can successfully launch Android Wear for like a minute directly after rebooting and then it crashes and proceeds to show the "Unfortunately , Android Wear has stopped." error like every 30 seconds. I have managed to pair my phone and watch but using my phone with this constant pop-up is more than just a pain...
Any ideas ?
Hi,
I have the exact same issue since this morning.
I have a MOTO 360 for more than one month, paired with a Nexus 5 (running KitKat) and everything was running fine ... until today.
I know have this "Sorry, Android Wear has stopped running" message every 30 seconds on my phone.
I've remove/installed Android Wear (client), factory reset my watch, removed developer options, the Bluetooth association... It does not help.
Android Wear won't start and I can't connect it to my watch. But the message is still here, again and again.
I suspect that the very last update of Google Service play is behind that (this thing is the worst part of Android) but I can't sort this issue.
Have you been, by chance, able to sort this issue?
Thanks,
M
I'm having almost exactly the same problem as you aimache. I've got a moto 360 paired to my Oneplus One, which is running on Cyanogenmod 11S.
I've had my moto 360 for 3 weeks and it was working fine, until suddenly about two days ago, the android wear app started crashing and I'm now getting pop ups on my phone literally every few minutes to tell me that "Unfortunately, android wear has stopped". If I try to open the android wear app it crashes after 1-2 seconds, so I can't do anything in it at all.
Oddly, the moto 360 seems to still somehow be pairing with my phone and receiving google now cards, but isn't getting any of my notifications like emails, texts, or calls.
I have no idea what caused the issue, but it's very frustrating and I would love it if someone could find a fix!
---------- Post added at 12:42 AM ---------- Previous post was at 12:21 AM ----------
I've just cleared the cache of Google Play Services in settings, and that seems to have fixed the issue. I can now open the android wear app with no problems and it's not crashing at all any more.
Fingers crossed it will continue to work :fingers-crossed: So try clearing the google play services cache on your phone and hopefully it will fix the problem for you too
Well I've tried clearing the Google Play Services cache but no luck...
Me too
Just wanted to add to this thread - having the same problems with Android Wear app. Bought a Zen watch, Android Wear crashes before I can even get it paired. I get to the screen about "select your device" see the watch and usually get as far as getting the pair request on my watch. It never completes the pairing. Sometimes crashes right away, sometimes a few seconds, sometimes 10 or 12 seconds but never yet successful. Have tried clearing app cache and app data. Will try uninstall/reinstall with reboot between but not very hopeful.
Kinda sucks cuz the watch is useless without. Hopefully it IS just an app update and we'll have in a day or two. Otherwise it goes back
Nexus 5 running 4.4 based Cataclysm rom.
Help! my 15 month old Umi Super shut itself off (battery almost full) and now won't reboot. The Umi logo appears as normal, then goes to the pulsing android thing. and stays like that for a few minutes until the screen goes blank. I have to hold the power button for a couple of minutes to start the sequence again.
I haven't rooted it (wouldn't know how, or feel confident doing so) Only thing I've done recently was update the OS to Nougat, using the update feature on the phone, so it's completely unmolested apart from the update. Since then, I've lost the fast charge facility, and it auto-locks the screen, and won't display the clock overnight, like it used to do. And all the settings menus have radically changed (for the worse). Can't even turn off the Auto-lock feature, just set the delay.
Is the update to blame? Can I undo it and revert to Marshmallow? Can someone please help? All my contacts are in the phone memory...
Sorted!
Don't know what happened but it eventually rebooted itself. I then deleted all the recently installed apps, and it's now working again. Must have been a rogue app, but I don't know which one. Slowly and methodically worked through the setup menu and found, in the Security submenu, some settings I hadn't previously found and was able to set a safe location at home where it doesn't Autolock. I have my phone back! And I take it all back. Nougat is a big improvement on Marshmallow, once you know how it works. Happy Days!
I have an Explorist Gen 4 that I've started having issues with. It's practically brand new although I hadn't used it for 6 months or so. I've got a Oppo Reno 2 running Android 10.
First issue is that touch seems to start having issues after the watch has been on for 30 mins or so. I can touch to wake it up, but then any touch/scrolling does not seem to register from then. If I restart it, all is normal again for a little while, so I think this is a software thing.
So I tried resetting the watch and reconnecting it to my phone, but it just won't connect any more. Most of the time the watch says it's connected, but the phone sits on popup showing the bluetooth pin.
Sometimes the watch gets stick on "Oppo would like to connect".
Sometimes the watch says connected and the watch is in the list of bluetooth devices, but wear os doesn't see it as connected.
The whole thing seems to be a mess.
Anyone seen any of this before, or have any ideas?
Edit:
OK, so I managed to get it to connect after messing about and adding it to bluetooth manually (which is not meant to work).
But the swipe/touch issue after a period of time is still an issue. It's pretty much only as good as a regular watch right now.