Related
My bro and I both bought the above units and have upgraded to the GPS rom. Just wondering if anyone else has noticed the unit switches on by itself. We are both experiencing this problem but also have the same programs running. The button lock feature is set on.
That's right. My Trinity is alive, too ;-)
I'm using the dopod rom about one week and I noticed that today for the first time.
There's no application running in the background. It's still alive ;-)
I do not care about this problem.
Hi,
Any software you are running?
Best regards,
Gilbert
Today programs are as follows:
cLaunch
Today Agenda
Battery Pack / Program Bar
PPCProfiles
I will try and eliminate one by one to see if it is software related.
Anyone else using one of the programs and having the unit switch on by itself. This issue bothers me as I see its going to be a drain on the battery.
Activesync may be the culprit
Many PPC WM5 devices tend to turn themselves on. It is usually an Activesync setting that periodically turns on the device and tries to connect to a non existant server. Best bet is to set up a dummy server on Activesync on the PPC, then set the sync settings to Manual, then delete the dummy server.
Sorry if you already have done this, but it certainly solved the issue for me.
Camstech said:
Many PPC WM5 devices tend to turn themselves on. It is usually an Activesync setting that periodically turns on the device and tries to connect to a non existant server. Best bet is to set up a dummy server on Activesync on the PPC, then set the sync settings to Manual, then delete the dummy server.
Sorry if you already have done this, but it certainly solved the issue for me.
Click to expand...
Click to collapse
Hey Camstech, could you please give me a detailed description of how to set this up?
Thanks
My phone seems to do this too, but from what I can see, it is because of bad 3G coverage and the phone has to roam to GSM and back. Only happens at work where I got bad coverage (2/4).
AFAIK this issue is common to ALL devices and all versions.
I understand that you DO NOT TURN THE PDA OFF (Holding the on/off button), just go to "standby". So there are many Apps that tend to "awake" rather than TURN ON your PDA. It's like Sleep mode vs Hybernate in Windows. Agenda or scheduled items may turn your PDA active, even SMS messages that don't fully arrive, phone reconnecting, GPRS or UMTS changing status, profiles that are set to change over time, incoming calls, etc.
I think this is not specific to a certain ROM but to the fact that you have a full time connected and running computer in your pocket....
Hope it helps.
Looking Glass said:
AFAIK this issue is common to ALL devices and all versions.
I understand that you DO NOT TURN THE PDA OFF (Holding the on/off button), just go to "standby". So there are many Apps that tend to "awake" rather than TURN ON your PDA. It's like Sleep mode vs Hybernate in Windows. Agenda or scheduled items may turn your PDA active, even SMS messages that don't fully arrive, phone reconnecting, GPRS or UMTS changing status, profiles that are set to change over time, incoming calls, etc.
I think this is not specific to a certain ROM but to the fact that you have a full time connected and running computer in your pocket....
Hope it helps.
Click to expand...
Click to collapse
I would have to agree to a point, as I have noticed when PPCProfiles changes automatically to my car mode (bluetooth on) the pda turns on. So you are right that it's programs possibly turning it on but this never happened on my O2 mini (WM2003SE). I'm hoping a new ROM may fix this issue.
I have disabled the "auto switch template" on PPCProfiles which changes over to bluetooth at a certain time of the day and it appears to have stopped the pda turning on by itself. So far so good for 1 day. Curious if anyone else is using PPCProfiles and are experiencing this. Does anyone else use other phone profile programs with switching templates that does not turn on their pda by itself?
frigit said:
I have disabled the "auto switch template" on PPCProfiles which changes over to bluetooth at a certain time of the day and it appears to have stopped the pda turning on by itself. So far so good for 1 day. Curious if anyone else is using PPCProfiles and are experiencing this. Does anyone else use other phone profile programs with switching templates that does not turn on their pda by itself?
Click to expand...
Click to collapse
Whoops!
Where can I find PPCProfiles. I dont seem to have that kind of settings in my original HTC P3600....
Very interesting.
saminegm said:
Whoops!
Where can I find PPCProfiles. I dont seem to have that kind of settings in my original HTC P3600....
Very interesting.
Click to expand...
Click to collapse
You can find the program link below. I never had any issues when using this program on my O2 mini. It still works on my dopod d810 just that I have disabled the auto switch template.
ps the chrome template is the nicest
http://www.modaco.com/Latest_Version-t205779.html
Correction to my thinking it was PPC profiles. It is actually happening when the bletooth is turned on ( hence ppc profiles switching over to car mode - bluetooth). I disabled ppc profiles and turned on bluetooth and strangely enough the dopod kept turning on.
Is anyone else experiencing this problem when they have bluetooth on?
frigit said:
I have disabled the "auto switch template" on PPCProfiles which changes over to bluetooth at a certain time of the day and it appears to have stopped the pda turning on by itself. So far so good for 1 day. Curious if anyone else is using PPCProfiles and are experiencing this. Does anyone else use other phone profile programs with switching templates that does not turn on their pda by itself?
Click to expand...
Click to collapse
Mine sometimes turns itself on when it automatically checks my email accounts, but not always. I wonder if it isn't the 3G/Edge switch that is explained earlier. My house is in a 3G fringe area. I believe it doesn't try and wake itself up when the Wifi is on. My Prophet never did this, it would only wake up for an alarm, call, or SMS.
The main issues are reduced battery life and if you have your phone in your pocket and it wakes up, buttons can be accidentally pressed before it goes back to sleep.
It's my only gripe with the HTC One.... When the phone's connected to my router, it flies!!
But... if I put the screen off and put it in my pocket for a while, then get it back out to do something else requiring net access...WiFi's switched off (and yes, it IS set to 'always on' in the WiFi sleep policy btw...) and I have to wait until it re-connects to the router again (which seems to take ages if you're waiting...)
I've been doing some Googling on this and it's quite common with HTC phones apparently....not everyone has it obviously, but I've found no real helpful cure yet if you DO have the problem.
I was thinking of rooting and installing a custom ROM to see if they're any better for me, but the last I knew, if you're rooted, you can't get Sky Go, and it's something I use a LOT, so that's put the blocks on that idea
Any suggestions?
There is two options. One in the power saver and one in the power menu in settings that disable data when the screen is off including wifi. Turn those off.
ste1164 said:
There is two options. One in the power saver and one in the power menu in settings that disable data when the screen is off including wifi. Turn those off.
Click to expand...
Click to collapse
I hope this helps when I'm at work. I work at a hospital and having my connection to WiFi helps when I walk through areas with no singal I can then switch to WiFi calling. My phone unlike my galaxy s3 always disconnects from the secure guest services. My sgs3 hardly ever did that unless I didn't use it all night. I have to constantly re sign in every time my phone is taken out of my pocket.
Sent from my HTC One using xda app-developers app
Nope. Unticking BOTH options hasn't made a difference. Still having to wait for the phone to re-establish itself with the router after periods of inactivity....
I'm having this issue too has anyone found a permanent solution to the problem?
racingmatt1 said:
I'm having this issue too has anyone found a permanent solution to the problem?
Click to expand...
Click to collapse
I've found after updating OTA to 4.2.2 today, the problem now seems to have gone....hopefully (might just've been lucky so far...dunno really yet!)
Have you updated too yet?
Willie_Heckerslyke said:
I've found after updating OTA to 4.2.2 today, the problem now seems to have gone....hopefully (might just've been lucky so far...dunno really yet!)
Have you updated too yet?
Click to expand...
Click to collapse
I am still on 4.1.2 and I'm in the US so we don't have the update yet.
This was one of the first things I noticed after connecting my HTC One (Sprint US) to my home Wi-Fi. It would hold the signal for a bit, maybe a few minutes, and then it would either simply no longer transmit data or the Wi-Fi itself would turn off and back on, with the subsequent connection never establishing a usable data link. Oddly enough, I got my wife an HTC One at the same time (subsidized upgrade for contract renewal), and hers appeared to be working fine, so I was concerned that I had a faulty device. Also, our previous devices (Moto Photons...) worked fine with the Wi-Fi at home as well.
After trying a myriad of settings changes, I found that only one thing worked reliably well: toggling the Wi-Fi off and then back on always resulted in a successful re-establishing of good data throughput to the router and back to the device. I decided to try and see how it performed on other Wi-Fi networks.
I took the device to my place of employment and without fail, the device stayed connected to the Wi-Fi there for the entire 8-10 hours, which only seemed to confirm that there was an issue with my home connectivity with my device only. As annoying as it may be, I am reduced to toggling the Wi-Fi off and back on when I use the phone at home, and I will remain optimistic that this 4.2.2 update fixes my problem, and if not, then I've done enough tinkering with the router at home as well as the phone to be satisfied I tried everything within my power to remedy the situation.
I am seeing the following issue:
I have a Droid 4, patched to run in GSM networks, flashed with CM 10.2.1. In this configuration, bluetooth used to work on this phone at least one month ago (because that's when my wifes new phone was bought and there my phone is listed as a paired device). Some time during the last month, I wiped my phone and reflashed the same CM 10.2.1 onto it (quite a lot of cruft had accumulated and I was having battery issues and was just too lazy to track down the specific culprits).
And now, when I try to turn on bluetooth in the settings menu, the button moves to the "on" position but stays grey and nothing happens. When I close settings and reopen it, the button is in the "off" position again.
Also, when looking in "about phone" -> "status" -> "bluetooth address", the entry text says "unavailable".
Any ideas as to
* how to further debug this?
* how to get bluetooth working again?
resolved ..
Hello everyone.
To report back, the reason it wasn't working is that I was an idiot.
Notably, when scrolling through the list of installed apps yesterday (looking for something utterly unrelated) I noticed an app called "Disable Service". Hmmm, I thought to myself, I vaguely remember using this a few months ago when trying to tweak battery lifetime. So I opened it and found out that I had deactivated, among other things, all Bluetooth related background services, thinking "I never need Bluetooth anyway", probably.
So yeah. Reactivating them led to, surprisingly enough, Bluetooth working again.
Sorry for the noise.
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.
I use a special application (Blackberry Enterprise Server) on Android and I've had problems with disconnects.
The application opens a VPN back to the network to push email and notifications to the phone. The whole idea of this application is security (VPN) and always on for notifications, email, calendar etc.
So on Marshmallow the app disconnects after an hour or so (closes down the VPN) and won't receive anything until you wake the phone back up again. Totally broken as far as I'm concerned. Happens on my S6 Active and a Blackberry Priv. BB Support sheepishly admits that its a problem and says their workaround is to keep the phone plugged into a charger and the VPN won't disconnect. Total crap!!! They also told me the problem would be fixed on Nougat which would allow them to get to the app and disable the power saving feature for that app which is causing it to disconnect. OK, some hope.
In the meantime I find this app in the play store called "disable doze" and put it on my BB Priv. It stops doze from kicking in and shutting down the VPN. On the priv it actually works. Now my VPN stays connected all the time like it should. I'm ecstatic! I try it on my S6A and it doesn't work. Still getting the VPN disconnected. Bummed because I really like the S6A and want to use that as my DD.
So I come here to XDA and see the NOUGAT beta for S6A and get all excited. I flash it to my phone and set up BB Software. Now I find that the wifi shuts down after 5 minutes on Nougat. I read tons of threads about wifi turning off after 5 minutes disregarding the "always keep wifi on" setting in nougat. So far no way that I can see to get wifi to stay connected.
WTF!!! I totally understand all the power saving stuff to extend battery life, but they put provisions in there to allow those who need to be able to disable. WHY ISN'T IT WORKING? Is this related to the S6A or is it across all hardware? I don't have anything else on Nougat to test.
Any ideas on what else I could try. Love that S6A but if it's not going to stay connected I just can't use it.
Roveer
Nougats in beta right now for the S6A, this isn't official firmware.
I understand its beta, but flaw like this always seem to find their way into the final builds. I'm reading threads all over the place (not just S6A) about this issue so I don't think it's just a beta thing. I'm not sure I understand why if there is a setting in the wifi to keep it on _always_ including sleep / doze etc that it basically does NOT do that.