Database Develop

Device switches on by it's self

When I switch off my XDA IIs by button or SW button in most of the cases the device switches on it self for one more time.
Is there anyone who can help?
Thanks guys!
:?:

I have the same problem, I had a bluetooth headset paired to it, maybe that is it, I only got the XDAIIs today so I have not had much time to watch it but it happened tonight and the XDA mini never does it.

Each time the BT headset is switched on or off and pairs up or releases, when a text message arrives, when you come out of a signal blackspot and reconnect and find you have missed calls etc.
Basically anything that results in a visual change caused the device to switch on.
Very annoying. Don't know the solution.
I share your pain.
Joe

I'm using http://www.trancreative.com/nicestart.aspx to keep the device locked, but it will turn on/off, but now it's locked so i dont delete data when it turns on in my pocket.
No matter what you do, the device will turn on at least once every hour.
I read somewhere that it does this to check the battery status.

I had the same problem once. Please open ActiveSync, switch the device off and see if ActiveSync is trying to connect..
Of course there can be lots of other reasons...

Yes I didn't mention on my post that activesync also seems to be a player in this problem.
If activesync is running, somehow the device syncs at varying intervals from 5 mins-1hr and switches it on to do so.
I used the attached to kill activesync to stop it happening.
Hope it helps.
Joe

I just unchecked the "Use mobile schedule to sync with this PC" setting and the problem was solved.
Though this seems to be a bug in ActiveSync..

Thanks
Works fine, great!

i had this problem on my old rom, and since i upgraded to 1.40, it aint done it since. maybe u need to upgrade.

WiFi not surviving sleep.

I have read some accounts of WiFi problems after sleep & I am now seeing it. I am auto-nootered for 1.1 & was previously auto-nootered 1.0.1 & had no problems. Now the WiFi doesn't reconnect after a long sleep. Don't know how long is the magic time, but it works fine after a short (1 Min. ? nap), but several minutes kills it. All I do is turn WiFi off & back on & it is fine.
Cheers,
kev

bugeyed1 said:
I have read some accounts of WiFi problems after sleep & I am now seeing it. I am auto-nootered for 1.1 & was previously auto-nootered 1.0.1 & had no problems. Now the WiFi doesn't reconnect after a long sleep. Don't know how long is the magic time, but it works fine after a short (1 Min. ? nap), but several minutes kills it. All I do is turn WiFi off & back on & it is fine.
Cheers,
kev
Click to expand...
Click to collapse
I have the same problem. Toggling WiFi off/on doesn't always cause it to reconnect. If it doesn't reconnect, I have to go to Settings -> Wireless and it reconnects

There's multiple threads on this issue in the last few days. It seems to be a post 1.1 issue. Stock and adhoc are affected. I have yet to find an app that helps, though forcing wifi off with profile settings seems to make things worse. Currently experimenting with wifibuddy as a quick route to settings. Setting wifi to stay on if charging during sleep seems to prevent the problem.
NC via XDA

soft locker keeps your phone running except for the screen so that wifi stays on and doesnt disconnect. you can get it in the market

jay0911 said:
soft locker keeps your phone running except for the screen so that wifi stays on and doesnt disconnect. you can get it in the market
Click to expand...
Click to collapse
+1 on Softlocker

****e! That means that B&N will have to push another update/fix on us! I thought I could rest for a while & not worry about them breaking my root. Ironically, I need this fix.
Cheers,
kev

I also have this problem. What i accidentally discovered is that if I ping my nook from any other machine on the network my connection to the network (on the nook) is restored. Looks like some caching issue.

I haven't had this issue unless I do a hard reboot by powering system down. After that, I tend to have to reset the Wifi connection. I ended up flashing my SD to the honeycomb port and everything seems better and I don't have to worry about B&N messing with an automatic update.

+1 for SoftLocker as well.

A little more experimenting and... cwm back to 1.01 and all is well. Then on 1.1 all is well until the adhoc is implemented. Now seeing how bad the hit is on battery life if I use wifibuddy to keep wifi from sleeping. THIS SUCKS

Avoid 1.1
Wifi was working great for me until 1.1 update. Had the same problems where wifi would disconnect and reconnect. Even tried Fryo. I had to revert back to 1.0.1 to avoid the problem.

+1 for softlocker free... that app is awesome and i haven't noticed any major battery decline from leaving it on all day with pandora streaming.

A combination of setting a static IP with Wifi Static and using Soft Locker has my wifi working perfectly 99.999% of the time. I still occasionally get a disconnect that requires a quick toggle via the settings menu but it is very rare, like once every few days.

[Q] Hp TouchPad running Android - Wifi force close

I've tested this with a3.5, Xron and Miui and they all get this problem. Maybe installing certain apps trigger this to happen but wifi will eventually slow down when trying to connect to a signal and will be essentially non functional since the OS will basically freeze and then tell you to force close wifi and it requires a wipe and fresh install to fix.
Has anyone else run into this problem?

Check this and see if it helps you.
http://forum.xda-developers.com/showpost.php?p=20863566&postcount=14

StEVO_M said:
Check this and see if it helps you.
http://forum.xda-developers.com/showpost.php?p=20863566&postcount=14
Click to expand...
Click to collapse
I don't think its the same issue. In those instances you can still try to change which wifi signal you want to connect to, I think it just loops from connecting and it would disconnect. I think this issue is common and dropped connections occur as well.
But I'm talking about a situation where if you even try to enter the wifi options it will force close.

iamsamsamiam said:
I don't think its the same issue. In those instances you can still try to change which wifi signal you want to connect to, I think it just loops from connecting and it would disconnect. I think this issue is common and dropped connections occur as well.
But I'm talking about a situation where if you even try to enter the wifi options it will force close.
Click to expand...
Click to collapse
Before I changed it, it would take forever to get it to release the connection. I just kept hitting "Wait" rather than "Force close" it would take several minutes but would eventually come up and allow me to Forget the network.
It sure sounds like the same, not saying it is, but very similar.

I experienced this problem for the first time yesterday in area where was about 20 WIFI networks. Never ever it happened in my house on A2. A3 A3.5 or XRON2.8
http://rootzwiki.com/topic/13779-now-i-believe-that-there-is-wifi-problem/

I have the same issue today, Wifi setting is forced to close, and cannot connect to any Wifi signals. I think it's a bug and it related to the time or date. Because I didn't do anything and it just happened.
No new apps install, no setting changed, and the device was keep on, so it just happens.
Hope someone can find out where the problem is...so sad this happen on New Year's eve....

i have this problem also, the solution i found was letting the touchpad go dead and than begin to connect wifi again.

Similar wifi comments here: rebooting [or maybe toggling/other disconnect] with wifi on/remembered would get it into a state where it was scanning and connecting over and over without really ever working. this was only happening once it was 'remembered'. Going through the wifi settings to forget in this state involved hitting 'wait' a few times and then i'd reboot and readd. 1st wifi connect is always solid for me.
I've found: market.android.com/details?id=com.brilliapps.wifiandmorefixer
Does the same thing except it is one click. I rebooted after the first go, but now no longer. i run this and then readd wifi - all set.

gear live connection issues

So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.

Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features

mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.

freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.

My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.

jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.

UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.

[Q] LGR going offline after "OK Google" command

Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?

Maybe your Wifi/3G connexion is in sleeping mode and is too long to unsleep ? the watch can not connect so quickly ?

You sound like having BT reception issues on the phone. This behaviour might be triggered by the bluetooth interface itself (on the phone - bad design) or by bad drivers (also on the phone) or by interferences from the wifi module. Is your wifi on all the time?
Regular wifi is on 2.4GHz, the same frequency as BT. Wifi, however, uses more Rx/Tx power compared to BT so, under certain bad antenna designs, WiFi can just mess-up BT.
On my phone (Z1C) is the other way around: having BT ON will cause bad performance on 2.4GHz WiFi .... so I just stopped using the 2.4 band for WiFi.
Give it a try, Worst case scenario: use another phone.

Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!

Troxelke said:
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Click to expand...
Click to collapse
Update: i tried several things with the WIFI / BT settings and on/off, but no luck. I have forwarded the above issues to Google, maybe they can help me out. I will keep you informed ... in the meantime anybody else some useful tips? Thanks!!!

Troxelke said:
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Click to expand...
Click to collapse
which phone are you using? are you on custom rom or kernel?

doki81 said:
which phone are you using? are you on custom rom or kernel?
Click to expand...
Click to collapse
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?

Troxelke said:
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Click to expand...
Click to collapse
try to pair your watch with your friend phone and to check this is not a problem coming from your phone. sometimes certain kernel do have issue with some of the bluetooth device.

Hello everyone. Sorry for my English, because I am using a translator. I decided to write this post, because it happened to me the same trouble and I found her cause. In anticipation of its Nexus 6, I decided to temporarily buy fairly cheap option LG G60 (X135). When watch came to me, I noticed the same problem. I then tried to connect them to the Moto G (1st generation), and there is the same. but by chance, in the evening, in my hands was LG G90 and I connected watch to this phone. Everything works without any problem. it turns out that despite the declared characteristics (Bluetooth 4.0) in all devices, it works quite differently everywhere. I hope with Nexus no problems.

Hi all, after opening this thread I tried several things and have some new insights:
- new update (5.0.1) solved my issue with going "offline" after a voice command. Now it works perfectly! But only if I am not connected to my carkit.
- if my watch is connected and try to use the carkit the sound is still bad. So I would like to have my watch disconnected if my carkit connects:
-- this could be done by only allowing 1 device to pair with my phone and prioritize carkit to be first and watch to be second.
-- this could be done by actively unpairing the watch if I receive a call (and connect when call is over).
The first option would be the most reliable and most simple. I tried to find an app that restricts only having 1 pairing and having a prioritize option ... but I cannot find such app. People any options?
Thanks!

Hi guys, in response of the above, the app TRIGGER might do the job, but it seems closing the Android Wear app or disconnect via Bluetooth does NOT disconnect your watch! Has anybody succeeded in using TRIGGER to disconnect / connect the watch with a automatic job?