Related
Hi everyone - I actually don't know who else to ask but this issue has been driving me mental for the last couple of months. After days and nights of investigating and looking through various forums and articles, I think I can find (or try at least) the words to describe my problem more...technically))
So OK, first off the device is Huawei Ascend G510-0100 running KitKat under the Cyanogenmod platform but the issue was already present with the factory's 4.1 ROM. I thought rooting the phone, installing just brand-new everything and having a bloatware/clutter-free Android OS would rectify all the causes of this nightmare but no. I'm not the only one with this problem: Google-search the issue and you'll find numerous forum threads where users seek for a solution to this "software loophole" as well as one of my friends (Galaxy S2) and another one with the HTC One X+ so I rule out my phone's model, OS version or just my device being faulty from the list of potential causes.
So - every time I turn my WiFi off on purpose or when I go out of my house (where logically my phone looses home's wireless signal) - the location services and the app synchronization processes stumble, mess up, run into and furthermore cause internal system mess-ups from such "unexpected" losts of internet. After that I can't make a phone call, send SMS or run USSD codes (checking credit balance etc) but I can still receive calls and texts - basically I fail to reach my cellular services but the service can still reach me. Turning Airplane Mode on and then off or simply restarting the phone altogether temporary fixes the cellular problem until the next time the internet becomes unreachable to Play Services. I tried turning location and sync off, tried different location/sync options...I wish I could disable Play Services but then I wouldn't be able to use the Play Store - | tried messing around with probably every single option available and possible but the Play Services still failed me and.......I honestly don't know what am I missing and where to look next
Edit: (I never use the mobile data btw)
Any suggestions? Anybody? I'm hopeless at this point :crying:
Thank you all...
...
Anyone? Please...
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
Click to expand...
Click to collapse
I'm not getting extended disconnects; just failing to answer questions about half the time. If it fails, I can try again and it often works.
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
I'm experiencing the exact same thing on my Gear Live. Its paired with stock S5. I just tried for like 5 minutes to get it to save a note and it would think for a while and then just disconnect.
mosi76 said:
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
Click to expand...
Click to collapse
This is exactly everything I've noticed as well.. Seems to have gotten waaaaay worse after yesterday's update
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Click to expand...
Click to collapse
Happens to me, too. Completely random though. Repairing the watch fixes it, but it is indeed annoying. We will have to wait for Google to fix this together with all the other bugs.
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
What about trying to reply using voice within a received Hangout or email? I'm always getting an error "Can't reach Google at the moment". Am I the only one? But if I select a default reply from the available list, I can reply with no problems...
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
I found it only improves it a little, but it's not a full fix. Sometimes my watch works the whole day without connection problems and then suddenly multiple times in a short period of time.
I've read that the gear live has the same problem, so I guess it's android wear wide. Hopefully google is going to bring out an update soon which fixes all the annoying bugs.
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
Like stated by the previous post this is a simple fix. The only one that can truly fix the issue is Google. I have used this for a week and not had any issues relating to bluetooth disconnecting. One issue I noticed was Google Search sometimes breaks after using it multiple times in a short amount of time. I usually have to just force stop Google Search every 3 days also.
This has always been an issue I had even before Android Wear. If I used Google Now too much I couldn't get the "Okay Google" command to work. It seems this also happen when using wear too much. A simple force stop fixed it, but it is annoying when you want it to just work. Another thing I noticed was custom roms are having issues with Android Wear in my case.
Every time I use a custom rom on my Nexus 5 and try to use my LG G Watch I have constant disconnects and Google Search issues. Maybe Android Wear isn't playing nice with custom roms, but after using rooted stock for the last week I am experience very few issues compared to when using different custom roms. I noticed whenever I used a custom rom I got the "Connected, running sync loop". I have no idea if this causes the constant disconnects, but on stock with the simple "Connected" I have no issues.
I started out with the same problem using a Gear Live with a Sony Xperia Z1 Compact. The thing that fixed it for me was turning off battery saving mode on the phone - called stamina on the Xperia - that was turning off BT to save power. Now I rarely see the disconnected message.
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
SIlvRav said:
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
Click to expand...
Click to collapse
I have found this issue for Android Wear for my LG G watch R and Galaxy Note 3. If I use watchmaker, I have it set to vibrate twice upon disconnect and vibrate once upon connect. It is constantly disconnecting and immediately reconnecting (2 vibrations, followed immediately by a single vibration). This is extremely annoying and I see the same problem stated in the beginning, the voice search is constantly disconnected or cannot reach the server.
Cheers,
B.D.
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Up?
I also see strange problems on the Y550-L01 connected to GPS.
In my case the GPS does not disconnect completely, but during car navigation the signal gets lost from time to time (tested with different navigation apps).
This is only the case when the Y550 is NOT connected to the charger. If I connect it to the power supply, GPS works quite reliable and accurate!
For me this sounds like a software problem (maybe connected to a power saving mode?). I hope a firmware update will fix this soon.
Even to me this is a firmware issue. Before of your answer, I was really beginning to think it's a fault of my phone. Now that I'm not the only one, I went back to think of a bug.
If it is a power save problem, then try to use this app to stop the power save mode :
https://play.google.com/store/apps/details?id=eu.thedarken.wl
(ultra light : 35K, free/no adds)
"Wake Lock gives you control over the Android Power- and WifiManager.
For example, you can force the PowerManager to keep the screen on or have the CPU still running in standby mode or make sure the Wifi connection keeps running at full performance.
You can use it on any android phone or tablet.
Use it to keep the screen on in full brightness or dimmed mode during movies or slideshows.
To make sure the CPU is still running in the background doing your tasks when you press the standby button."
Thank you for the report.
It seems that the new huaweï G620S has the same GPS problem :
https://www.google.fr/search?q=G620S+GPS+problem+fix
Any news of an Huaweï update ? Hope yes...
magooz85 said:
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Click to expand...
Click to collapse
Hi! Better post your question in our small Huawei Ascend Y550 thread. Maybe there someone of us can help.
If you understand German:
http://www.android-hilfe.de/huawei-...gation-unzuverlaessig-nur-im-akkubetrieb.html
These folks have the same proplem, but no solution.
Try it while a charger is attached.
Hi everyone.
I work in the support section of a small software company that supplies a software suite to hospitals, we have 2 PC applications and an Android application that work in tandem. At one of our sites they have been having an issue whereby some of their devices (Motorola Moto G2, Android 4.4.2) will randomly reset the date and time to random years (1970, 2040, etc) which is problematic as our software is a real time system that requires the use of time stamps from the devices. If they don't have the correct date and time then it can impact the way the software works, to the point where the devices will no longer connect into the system. I will also note that we use an application (SureLock) to lock the phone down so that it can only use our application.
I have tried several solutions to this problem, including making sure that the automatic date and time settings are not switched on, making sure that the batteries are not completely draining, etc. but have been unable to come up with a solution and I cannot find other users who have the exact same problem.
Some excerpts from my open ticket:
"...the issue was related to the date and time on the devices changing to random years (i.e. 1974, 2036, etc). This has been an issue in the past and so they now untick the "Automatic date & time" and "Automatic time zone" settings within android and set the date and time correctly which solves the issue. But the phones are still randomly changing their date and time even with those settings unticked."
"...We charge our phones fully every day, so it would be extremely rare for a battery to be fully drained. Think it must be something else happening."
"...
Motorola – Moto G – Android version 4.4.2
Date/Time not set to automatic – but we have noticed that this makes no difference – problem still occurs whether the automatic is ticked or not.
Issue occurs on random phones and at differing times of day."
"... Problem is still occurring but not so often. I was keeping a track of when it happened but there did not seem to be any pattern. The only thing I noticed was that one of our Operators who has a cochlear implant seemed to have it happen by far the most often. Could there be some interference from the implant?"
I found one other thread on another forum but it was in relation to the Samsung Galaxy Centura, and this was solved by either unticking Automatic Date & Time or checking the calendar application's time settings. I have tried both of these to no avail.
I am at a loss as to what to try next, any help or info would be much appreciated.
Hello fellow developers,
I am having trouble with an Android app I am working on that is programmed to send GPS data to a web service every 2 hours. The issue is that after about a day, the service appears to be interrupted on the phone, and data is no longer sent.
To troubleshoot this issue, I have tried the following with no success:
I have checked the app for error messages or exceptions, but none are being thrown when it stops sending data to the web service.
I have set an alarm to see that keeps the app working in non-interactive mode. It works for a few days and then stops again even with the alarm set and going off everyday.
I have checked the web service logs, but there are no errors or issues on that side that would prevent the data from being received.
I have tested the app on multiple devices, and the issue occurs mostly in Sony Xperia, Samsung S22 etc.
I have tried different intervals for sending the GPS data to the web service (e.g., every 10 mins), but the issue persists.
I have tried wakelock/caffiene apps to keep the CPU running.
All Android settings are set to not let the app go to sleep and to ignore battery optimization for my app, and it is also a foreground service.
I am wondering if anyone has any insight into what could be causing this issue and how to fix it? I appreciate any help or advice you can offer!