Has bluetooth been fixed on any 4.2.2 ROM yet?
I've been having the following issue on the ParanoidKangdroid ROM which from what I've been reading is typical of the BT issue
If I use BT to make a call from my car, or stream audio then turn BT off, it won't re-enable without rebooting. Whilst my company requires my phone to be off whilst I work, I play with the spirit of their rules by sending it to airplane mode instead, in order to still use time based alarms.
pTeronaut said:
Has bluetooth been fixed on any 4.2.2 ROM yet?
I've been having the following issue on the ParanoidKangdroid ROM which from what I've been reading is typical of the BT issue
If I use BT to make a call from my car, or stream audio then turn BT off, it won't re-enable without rebooting. Whilst my company requires my phone to be off whilst I work, I play with the spirit of their rules by sending it to airplane mode instead, in order to still use time based alarms.
Click to expand...
Click to collapse
I haven't come across any roms that have completely fixed it. Even the stock 4.1.2 rom was giving me a lil trouble. I learned to leave it on, or reboot if I needed it. I'm guessing that your not to worried about battery power since you leave it on all day just for alarms. So why not just leave it on?
It's amazing how much the battery doesn't drain when you turn off all of the radios (except for wifi*, will I'll expand on later) for 7 hours 50 minutes of an 8 1/2 hour period, only using the phone for 40 minutes during that period.
* I leave wifi on to automate "Work Mode' using Tasker. Tasker uses Wifi to detect one of the networks at work, which when detected, activates Airplane mode (which another couple of profiles deactivate airplane mode for break & lunchtime.) , turns on a number of Gentle Alarms, and undoes everything when the network is no longer in range.
I use Secure Settings to remove wifi from the list of radios controlled by airplane mode so that Tasker can still check for the work wifi, and I could do the same for BT, but I'd like to reduce as much unnecessary battery usage as possible.
ON JamieD81's roms especially Carbon Rom not having any issues I use it daily in my car connect to the phone and plays music no searching for devices staying on the screen works right away and quickly connects.
hairypork said:
ON JamieD81's roms especially Carbon Rom not having any issues I use it daily in my car connect to the phone and plays music no searching for devices staying on the screen works right away and quickly connects.
Click to expand...
Click to collapse
Does it come back on again after toggling it off without rebooting? I',m currently using Jamie's last ParanoidKangdroid build and I have to reboot to regain BT after turning it off.
I have not found a way to do it without rebooting. Really hoping the next Cm release fixes this, as someone who uses bt all the time for music, I probably hate this more than random reboots
I just tried it on the Carbon Rom and it worked perfectly I can turn it on then off then on no problems.
hairypork said:
I just tried it on the Carbon Rom and it worked perfectly I can turn it on then off then on no problems.
Click to expand...
Click to collapse
Sorry to be a pain, but...
Can you use your BT (not just connect to a paired device but, stream audio or make a call), then turn it off, and turn it on again?
It has no problems I connected in the car on my way to and from work, went to the store today no problems no reboot I turned it off then on then off. And I can make calls and stream music on my car stereo and laptop.
hairypork said:
It has no problems I connected in the car on my way to and from work, went to the store today no problems no reboot I turned it off then on then off. And I can make calls and stream music on my car stereo and laptop.
Click to expand...
Click to collapse
I'll give it a shot, but I'm skeptical... why would Carbon Rom be different than any of the other current CM bases? I'm even using the stable Nexus ROM from Jamie and it still has this problem consistently... But alas, I will give it a shot!
FWIW, I have just installed Jamie's latest Slimbean ROM which he advertised as having a new kernel in the hope that the kernel has addressed this issue.
hairypork said:
It has no problems I connected in the car on my way to and from work, went to the store today no problems no reboot I turned it off then on then off. And I can make calls and stream music on my car stereo and laptop.
Click to expand...
Click to collapse
On carbon now, so far so good!
magnumforce2006 said:
On carbon now, so far so good!
Click to expand...
Click to collapse
Nevermind, problem started again today, DOH
Installed Carbon last night, and found that Bluetooth turned itself off and refused to come back on again without a reboot within ten minutes of initially turning it on.
I use Bluetooth daily. I'm on AOKP http://forum.xda-developers.com/showthread.php?p=42101680
So far it's working flawlessly, where as before on 4.2.2 roms Off had the same experience as you.
Sent from my SGH-I717 using Tapatalk 2
Bubbajoe40356 said:
I use Bluetooth daily. I'm on AOKP http://forum.xda-developers.com/showthread.php?p=42101680
So far it's working flawlessly, where as before on 4.2.2 roms Off had the same experience as you.
Sent from my SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Bluetooth wouldn't start on the second boot up with that Rom :-\
Wow. Sorry to hear
Sent from my SGH-I717 using Tapatalk 2
Seems like it's just a deeply embedded problem with all of these Roms, and for whatever reason, some treat others devices nicer than others. I went back to Jellybeer, which only has this issue every once and awhile. Still there though.
Related
Hope I'm not duplicating anything, but there seems to be a lot of BT related questions and none answered in one unified place. Also I think the BT Dev thread should be left to the devs (to keep it easier for them to work on things, rather than help us mere mortals ).
This applies to CM7 (latest nightlies, Tablet Tweak RCs) ONLY (as far as I know).
So, if bluetooth does not turn on, there a few things that you can try.
Do a HARD reset (that is, hold down the power button until the NookColor turns off, then start it back up.
Fix Permissions in ClockworkRecovery:
Boot into CWR (w/SD, load it in. With CWR installed on eMMC, go to ROM Manager > Reboot into Recovery. Alternatively, hold down the power plus "N" button for ~8 seconds (from a shutdown NookColor).
Try both!
An interesting thing to note is some users (myself included) can only start up bluetooth within a pretty short window of time after the NC has booted up. Not sure why timing is important, but could be a factor for those who cannot start up BT after some given time of operation.
I found this tip that may work after a fresh (read: wipe system/data) install, but may also work after flashing a nightly over a nightly.
If you're ready to turn on Bluetooth, there's a trick. If you don't do this, Bluetooth will just refuse to turn on / be enabled.
Turn off wifi (Settings > Wireless & Networks > Wi-Fi)
Reboot
Turn on Bluetooth (Settings > Wireless & Networks > Bluetooth)
Turn on wifi
It seems a bit odd, but that's what you have to do. From then on out it'll work fine.
Click to expand...
Click to collapse
Credit here (step 2)
For a list and description of devices that work with the NC, check this out:
Known functional Bluetooth devices
For tethering data via BT, try android-wifi-tether. While it can be used to create an access point on your phone via wifi, you can also opt to use BT to create the tether. This works well in conjunction with TetherGPS which I use to provide GPS info to the NC from my G1 while using CoPilot Live to show navigation (I don't have data on the G1).
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
ace7196 said:
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
Click to expand...
Click to collapse
me too. I went back to 4/4 since them. If I leave BT on all the time, it is on when I boot, but if I turn off BT and reboot, it won't come on without a hardboot (holding down power.)
Fix permissions is NOT needed, just a hard boot.
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
For the last few days Ive been trying to get BT working w/ my car stereo, using phiremod 5.3
I have no problems enabling Bluetooth (first time I had to reboot a few times and fix permissions)
With it flat against the stereo, I'm 'paired but not connected' and getting it to actually connect usually takes 4 - 5 tries.
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.
Seems like it changed something on my end...
Just figured I'd mentioned it.
(I can go back to the other kernel, or a different version of cm7, and see if I get the same connecting/ stuttering problem, if you thing it would help)
Btw- thanks so much for sharing all of your hard work!
breebauer said:
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.!
Click to expand...
Click to collapse
I dont' know if anyone who's building from source wants to take a look at this patch committed 3 days ago on the omapzoom tree to frameworks/base, but it seems to address a bluetooth corruption problem.
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out this posting:
http://forum.xda-developers.com/showthread.php?t=1024963
I believe you also need the Bluetooth GPS Provider app from the market.
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
I'm running Phiremod v5.3 cm7 from emmc and cm7 nightlies from sd card. I usually have a data sd card but can switch it out. I have updated the cm7 sd card before. Not sure which nightly and OC I used last. Could use ClockWorksMod to flash this kernel to Phiremod v5.3. Could replace the kernel, uImage, on the SD card. Usually there are different kernels for emmc and sd card.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Question: will 'Wireless Tethering' work in place of 'tether-wifi'? Or does it -have- to be 'tether-wifi'? Thanks!
any software will work that tethers.:-D
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Apparently the latest version of Copilot has introduced this error. I have spoken with tech support regarding the issue and they told me that they are aware of the problem and will release an update early next week that will fix the problem. Apparently if you have version 8.2.504 it works, but the new version breaks it. The dev won't send me a copy of the old version, so I guess I'll just have to wait and hope.
lschroeder said:
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
Click to expand...
Click to collapse
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
breebauer said:
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
Click to expand...
Click to collapse
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
khaytsus said:
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
Click to expand...
Click to collapse
Thanks! That makes a big difference...
(For some reason, I was thinking it was on the upper left corner- not sure why)
chisleu said:
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Click to expand...
Click to collapse
I was just using google voice to text from several feet back. In fact it was hard to read the small print from that distance. I did not realized that keyboards have a larger range then headsets.
Testing Bluetooth Keyboard JP now. Force closes, so just switched to swift keyboard I downloaded from amazon app store for free. To get out swift keyboard and get a null keyboard, I hit the back key on the xoom keyboard, then the virtual swift keyboard no longer shows up.
@chisleu do you have a link or instruction to modify bluetooth keyboards so that keys can have their mappings corrected. Xoom has some correct and some wrong or disabled under CM7.
Couldn't get BT to work at all however powering down while the wifi is off, and turning the bluetooth on before the wifi made it works on the first try. Was streaming Slacker to my stereo in a matter of minutes. Wifi doesn't seem to interfere with the BT audio stream at all, audio sounded crisp and perfect. Range however was still limited to a foot or so.
Hoping there is a possible hardware mod that can hook up an antenna to the BT chip. I'd be in heaven if I had full BT functionality on this beast.
FYI, Although I don't have any RF experience I'm still an electrical engineer so if anyone can toss me a bone on the PCB layout or pinouts of the nook I might be able to try stuff to boost the range.
What is the feasibility of adding dial-up networking client support to CM7? Some folks are able to tether their NC to their phone using an ad hoc wifi network, and others have had success via a Bluetooth personal area network (PAN) using the "pand" utility. Unfortunately, I have a Blackberry phone, and it does not support the PAN profile. It does, however, support dial-up networking (DUN) over Bluetooth (confirmed with a Windows laptop).
According to https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq, "dund" is the client utility that is needed to establish a dial-up connection from Android to another device. When I run this command on the NC, it says "dund: not found". I'm not a developer and don't know how much effort would be involved in adding this functionality to the build. Is it just a matter of including the binaries, or is there additional development work involved?
Thanks in advance..
I think this is the proper place for this, but feel free to call me names if it's not.
I just bought a Focus, and was using the Sync system with my Thunderbolt with no issue. Then about a week ago, I switched over to using CM7, now I can't make an outgoing call. There's no volume in the car, and if I manually turn Bluetooth off on the phone, I can hear the person I'm calling, but they can't hear me.
The weird thing is that if I get an incoming call, I can answer it through the car, and everything works without problem. I also don't have any issues like this with other Bluetooth devices. I've tried deleting the connection between car and phone, and re-pairing them, but get the same result.
Anyone who could suggest something would be my hero!
only thing I can think of is that cm7/aosp roms use a different BT stack then sense based roms (stock or otherwise). I'm guessing this stack which is usually better, isn't doing something right. I would try a sense based rom and see if your problems resolve.
vodkaequalslove said:
I think this is the proper place for this, but feel free to call me names if it's not.
I just bought a Focus, and was using the Sync system with my Thunderbolt with no issue. Then about a week ago, I switched over to using CM7, now I can't make an outgoing call. There's no volume in the car, and if I manually turn Bluetooth off on the phone, I can hear the person I'm calling, but they can't hear me.
The weird thing is that if I get an incoming call, I can answer it through the car, and everything works without problem. I also don't have any issues like this with other Bluetooth devices. I've tried deleting the connection between car and phone, and re-pairing them, but get the same result.
Anyone who could suggest something would be my hero!
Click to expand...
Click to collapse
I'm using TheROM V4 (aosp) rom, and previously was using CM7. Have been able to sync with SYNC with no problems. I would try deleting the BT connection in your car first, then re-pair your phone. If that doesn't work, try downloading and flashing CM7 again. If that does not work, and you like AOSP ROMs, then try one of the other ones (OMGB, OMFGB, TheROM, or Thunderstick).
Sometimes my sync starts acting up in my 2009 focus. Only thing that remedies it is a master reset on your sync under system settings and then pair the device again.
Sent from my ADR6400L using Tapatalk
You also might want to check if your sync system has the latest updates from syncmyride dot com.
Sent from my ADR6400L using Tapatalk
The Ford is the problem. Get a Chevy will fix the problem. lmao
I have had my Omate Truesmart for about two weeks now and I have loved it. When I turned my watch on this morning the bluetooth refuses to turn on. It was working last night but this morning it won't stay on. I have tried from the notification bar and from the settings wireless and networks. Neither approach works. When I slide the toggle to on from settings it immediately jumps back to off.
rschouten said:
I have had my Omate Truesmart for about two weeks now and I have loved it. When I turned my watch on this morning the bluetooth refuses to turn on. It was working last night but this morning it won't stay on. I have tried from the notification bar and from the settings wireless and networks. Neither approach works. When I slide the toggle to on from settings it immediately jumps back to off.
Click to expand...
Click to collapse
Reboot
overground said:
Reboot
Click to expand...
Click to collapse
Tried that already.
rschouten said:
Tried that already.
Click to expand...
Click to collapse
Hmmm. That sucks.
A reboot always fixes it when mine does that.
I'll let you know if I find anything else.
overground said:
Hmmm. That sucks.
A reboot always fixes it when mine does that.
I'll let you know if I find anything else.
Click to expand...
Click to collapse
Ok, let me know if there is any information that I can provide. I am running the stock ROM from 2014120. With the patch from Loki.
rschouten said:
Ok, let me know if there is any information that I can provide. I am running the stock ROM from 2014120. With the patch from Loki.
Click to expand...
Click to collapse
Do you have recovery?
If you have recovery, wipe cache and dalvik cache and then try...
You could have same problems like many other.
If wiping won't to the job, it could be hardware issue, maybe to open it and check connections.
But contact Loki first...maybe he has better idea...
Sent from my C6903 using Tapatalk
rschouten said:
Ok, let me know if there is any information that I can provide. I am running the stock ROM from 2014120. With the patch from Loki.
Click to expand...
Click to collapse
Loki suggested on G+ to try disabling Quick Boot, then rebooting.
It's in Settings>System>Accessibility
Yes, you have to turn off quick boot to recover bluetooth, or pull the battery or let the battery run all the way down. Otherwise it doesn't really reboot, and Bluetooth will still not work.
Sent from my Nexus 5 using Tapatalk
Has anyone had any luck with the Network Access Point service unavailable problem yet? I have never been able to connect via Bluetooth to my TS.
Sent from my GT-I9300 using xda app-developers app
overground said:
Loki suggested on G+ to try disabling Quick Boot, then rebooting.
It's in Settings>System>Accessibility
Click to expand...
Click to collapse
Just for reference. This did solve the problem. I am now back up and running. In regards to network access unavailable I had solved that with mine since I have it paired with Glass I had to enable bluetooth tethering. Then the error went away then the problem is that it always asked to connect and I had to manually disconnect it otherwise it would severely drain my battery.
I have also tried enabling Bluetooth tethering but still cannot connect. I don't seem to be able to connect with my laptop either. I can't send files at all. I might just have to be patient and wait for an update.
I am using the latest cm nightlies and Ubuntu 13.10 if it makes any difference.
Sent from my GT-I9300 using xda app-developers app
sevs3 said:
I have also tried enabling Bluetooth tethering but still cannot connect. I don't seem to be able to connect with my laptop either. I can't send files at all. I might just have to be patient and wait for an update.
I am using the latest cm nightlies and Ubuntu 13.10 if it makes any difference.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Tethering is broken. At this time, with the poor base firmware Omate (and others like SimValley) is being given to work with. we get BT audio and not much else.
Lokifish Marz said:
Tethering is broken. At this time, with the poor base firmware Omate (and others like SimValley) is being given to work with. we get BT audio and not much else.
Click to expand...
Click to collapse
I have had Bluetooth tethering working on my stock omate and with the custom rom. I have it connected to my google glass as just a headset and with bluetooth data connection. I cannot get the my glass app to recognize it but I can get the internet sharing working over bluetooth.
rschouten said:
I have had Bluetooth tethering working on my stock omate and with the custom rom. I have it connected to my google glass as just a headset and with bluetooth data connection. I cannot get the my glass app to recognize it but I can get the internet sharing working over bluetooth.
Click to expand...
Click to collapse
That's the only tethering that works. Can't do it they other way (x201 > phone > internet) so it's still broken really.
Lokifish Marz said:
That's the only tethering that works. Can't do it they other way (x201 > phone > internet) so it's still broken really.
Click to expand...
Click to collapse
I see. So it can provide bluetooth tethering but not consume it.
Iconbit Callisto
I've heard that this watch and the TS is pretty much the same watch. I'm having trouble with connecting with BT with my HTC One XL. I tried connecting a BT headset to it and it paired and connected. When I tried my laptop and my phone, they pair, but immediately disconnect; or rather, they don't connect at all in the first place. Has anyone had, and resolved, this issue with the Omate?
The BT issues affect ALL x201 smartwatches. So if it gets fixed on any x201, this forum will go nuts with folks applying the fix.
Lokifish Marz said:
The BT issues affect ALL x201 smartwatches. So if it gets fixed on any x201, this forum will go nuts with folks applying the fix.
Click to expand...
Click to collapse
I saw a video from Cnet with the Omate and that BT icon at the top of the screen showed that it was connected... Can the TS's the people on XDA at least connect to their phones through BT or is that an on & off thing for all of these watches? Ugh.. I wish I was proficient at programming and other things so that I could help out with designing ways to improve on these smartwatches...
htcfan85 said:
I saw a video from Cnet with the Omate and that BT icon at the top of the screen showed that it was connected... Can the TS's the people on XDA at least connect to their phones through BT or is that an on & off thing for all of these watches? Ugh.. I wish I was proficient at programming and other things so that I could help out with designing ways to improve on these smartwatches...
Click to expand...
Click to collapse
Me too! I really don't want to bother with adding a SIM card. The watch is great but I'd really want to use it with internet connectivity. Just curious... if this does work... will it affect my data plan same way as a hot spot? Sorry if its a newbie question.
bluetooch
syounger64 said:
Me too! I really don't want to bother with adding a SIM card. The watch is great but I'd really want to use it with internet connectivity. Just curious... if this does work... will it affect my data plan same way as a hot spot? Sorry if its a newbie question.
Click to expand...
Click to collapse
petite question l icone dans la barre des notifications du bluetooch doit étre bleu quant il est activer ?
I upgraded my phone to KK back in late december and have been on it ever since but one problem has plagued me since then and I'm hoping to get some insight here. heres the problem...
When im connected to wifi (and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.Often i turn my screen on and get a barrage of notifications that i should have gotten hours ago. Ive tried all the sleep modes and Ive tried turning off wifi optimization.Nothing works and I know for fact it did not do this on JB.
I DO get text messages and phone calls instantly though but nothing else will wake my phone up. While i do enjoy the deep sleep, i would like to get my notifications in a reasonable amount of time without having to turn the phone on to check them.
Has anyone else had this "problem"?
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
SteveMurphy said:
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
Click to expand...
Click to collapse
Yeah i know and I've googled it to death for a few months now. I'll check g settings but idk why that would stop gmail. It's like when I'm on Wi-Fi w/ the screen off its just a plain old dumb phone. I turn the screen on and the notifications just flood in.
Edit: nothing in g settings is muted. The only thing i can think of is i don't have app data synced in accounts.
I think i figured it out. I had "sync app data" unchecked in accounts. So far I've been getting notifications screen on and off. Now if someone will just play back to me on wwf...
EDIT: i may have spoke too soon. It still doesnt wake up without turning on my screen
hey @SteveMurphy do you by chance use the active display?
razen_kain said:
hey @SteveMurphy do you by chance use the active display?
Click to expand...
Click to collapse
I did when I was using Omni and it worked great. I haven't used it since running RR, however.
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
razen_kain said:
[...](and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.[...]
Click to expand...
Click to collapse
cyril279 said:
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
Click to expand...
Click to collapse
No i never turn mobile data off. I just meant that notifications come as expected when I'm on mobile data but on Wi-Fi, once the phone hits deep sleep (<a minute) i won't get notifications unless i turn the screen on.
I ask about active display because i remember when on resurrection ROM i was using it and getting notifications then and kind of forgot about it but I'm on PAC 4.4 now and it's doing it again. However i was using the init.d scripts they have baked in but have them all turned back off now to see if that fixes it.
It's the strangest thing I've seen. It's like when I'm on Wi-Fi and turn the screen off it just disconnects from all data even though i can plainly see that it is not. Angela has the same phone with the same settings as mine but on RR 5.0.5 and she gets notifications fine.
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
razen_kain said:
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
Click to expand...
Click to collapse
cyril279 said:
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
Click to expand...
Click to collapse
Well all my testing so far has lead me no where with the exception of using that app. So far, I've not been able to reproduce the problem while using it. The question is,"what is it doing" to make it work....
EDIT: The app does not fix it....
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
razen_kain said:
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
Click to expand...
Click to collapse
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
Click to expand...
Click to collapse
Its 4.4 and I have faced this issue on every rom Ive tried since switching to KK. Im starting to wonder if it's not an issue with my wifi. Im wondering if maybe my wifi is suspending my connection when my phone goes quiet.
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms...
Click to expand...
Click to collapse
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
SteveMurphy said:
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
Click to expand...
Click to collapse
It's always good to have you around buddy.
[SOLVED] Not Receiving Notifications on WiFi
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Great news, glad it was an easy fix!
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
Great news! Now you just need to install DD-wrt on your router and turn it from a $40 router to a $400. I know you like to tinker but check it out. ITs free and its just firmware for certain routers. It turned my old wrt54g into a baus
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
I'm having the same issue with KitKat CM11 ROM on my HP Touchpad (which is WiFi only), and will have to try this. Notifications come in instantly on my iPhone/iPads, but my Touchpad gets some serious delays...sometimes right away, and sometimes delayed.
By the way, did "Sync App Data" setting for an account have anything to do with push notifications, or is that more for backup purposes?
---------- Post added at 02:32 PM ---------- Previous post was at 02:04 PM ----------
Oh darn, mine is still delayed even with the push notification fixer installed and WiFi heartbeat at 5min. Even after I've just rebooted my Touchpad, actively using it, and not even 5 minutes has passed. Delay was 8 minutes and then the notifications came streaming in.
With Android/KitKat, do you have to have the app open in the background for push notifications to go thru? Or run the app at least once after a reboot?
Whenever I now try and switch bluetooth on it instantly snaps the button back to the off position, I have tried turning it on in loads of different ways and it just won't come back on...
It was working fine till yesterday, I installed Swapp Link app and let it manage the BT connection and now it won't switch on... I have remove / reinstalled the app and restarted phone etc, nothing has fixed it.. any ideas? ;(
death_entry said:
Whenever I now try and switch bluetooth on it instantly snaps the button back to the off position, I have tried turning it on in loads of different ways and it just won't come back on...
It was working fine till yesterday, I installed Swapp Link app and let it manage the BT connection and now it won't switch on... I have remove / reinstalled the app and restarted phone etc, nothing has fixed it.. any ideas? ;(
Click to expand...
Click to collapse
Do you have any app like Liama or similar?
Maybe that app has rule to switch your BT?
If you don't have it, try to restart TS and wipe both cache from recovery (if you have it)
Sent from my C6903 using Tapatalk
nope nothing like that, I even disabled "2x battery" battery saving app and that's not helped either :S not sure why it suddenly just stopped as I haven't add any software onto it....
death_entry said:
nope nothing like that, I even disabled "2x battery" battery saving app and that's not helped either :S not sure why it suddenly just stopped as I haven't add any software onto it....
Click to expand...
Click to collapse
Bluetooth also suddenly stopped working for me. And it is not possible to turn it on. To make things more interesting - I didn't install anything on my omate since I upgraded to TEST_RELEASE_Omate_2100_TrueSmart_20140314.zip on the day when my omate 8GB/1GB 2100 arrived more than a month ago. It worked fine all this time, and without any visible cause it just stopped today.
I wanted to tether to ipad to provide internet connection, while riding in a bus, and suddenly snap - bluetooth turned itself off. I tried restarting omate. I couldn't figure anything to get it back to work.
it happened exactly 6 hours ago. About the time when you made your post.
cosurgi said:
Bluetooth also suddenly stopped working for me. And it is not possible to turn it on. To make things more interesting - I didn't install anything on my omate since I upgraded to TEST_RELEASE_Omate_2100_TrueSmart_20140314.zip on the day when my omate 8GB/1GB 2100 arrived more than a month ago. It worked fine all this time, and without any visible cause it just stopped today.
I wanted to tether to ipad to provide internet connection, while riding in a bus, and suddenly snap - bluetooth turned itself off. I tried restarting omate. I couldn't figure anything to get it back to work.
Click to expand...
Click to collapse
I will probably flash the bluethooth tether rom and see if that fixes it
death_entry said:
I will probably flash the bluethooth tether rom and see if that fixes it
Click to expand...
Click to collapse
please let me know if it helped. I will try the same, albeit I have no idea right now how to do it
I've had this happen on my regular phone. A hard reset has always fixed it.
Bushrod said:
I've had this happen on my regular phone. A hard reset has always fixed it.
Click to expand...
Click to collapse
how to do a hard reset of omate, without voiding the warranty? Do I need to wait until battery runs out?
No, just turn off quickboot and power the watch down. When you turn it back on Bluetooth will probably reinitialize and work again. For a while.
Sent from my Nexus 5 using Tapatalk
trent999 said:
No, just turn off quickboot and power the watch down. When you turn it back on Bluetooth will probably reinitialize and work again. For a while.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It worked! Thanks
cosurgi said:
I worked! Thanks
Click to expand...
Click to collapse
Yep that fixed it for me too
Wonder why quick boot knocked it out lol....
Easier than a hard reset!
death_entry said:
Yep that fixed it for me too
Wonder why quick boot knocked it out lol....
Click to expand...
Click to collapse
Quickboot didn't knock it out. The defective TrueSmart MTK firmware and hardware combination cause all sorts of problems with using Bluetooth, including some that require a full power cycle reset. That is not possible with Quickboot enabled unless the battery runs down or is removed.
Sent from my Nexus 5 using Tapatalk
Glad to see your BT and TS are working fine now...
All el devices could be "fixed" by restarting it.
They are all using RAM and/or dalvik cache and that has to cleared sometimes...
Dalvik cache is a "place" where Android decompile apk files for quicker access, so when you wip dalvik cache from recovery you are clearing everything so system has to decompile apk files again and RAM is cleared also...
It's like fresh start and it "fix" many software issues that way...
If you have ADB tools and rooted device, you can use adb reboot from adb shell, no need to open your watch, lose warranty and pull battery out...
Sent from my C6903 using Tapatalk