Related
change N1 behavior/settings & automate tasks based upon connected bluetooth device?
I've had my ATT N1 for the past 1.5 wks and have been loving it. I know with the desktop dock for the N1 that bluetooth can be automatically enabled when docked (at least it does for me). i hope to see this go one step further perhaps. i've tried searching on the market and here on xda, but I haven't found anything that does what i'm thinking of...
I'd like the phone to change various behaviors (eg. sound alerts, screen unlocking, application launching, etc) depending upon the bluetooth device that it is paired with. Essentially, creating setting profiles dependent upon the connected bluetooth device and reverting settings when disconnecting from said devices.
I envision:
-connecting w/ car bluetooth:
disable screen unlocking (having to unlock via pattern while driving is not only annoying but possibly dangerous)
jump to a particular home screen, automatic launching of application such as car home, google maps/nav, music, etc
enable maximum screen brightness (if plugged in and charging could be another modifier. the N1 AMOLED really is pretty bad in direct sunlight and is even worse when trying to view while wearing sunglasses)
set max volume
upon disconnecting, revert to original settings, disable bluetooth
-connecting w/ desktop dock [bluetooth] (bluetooth isn't an absolute requirement here since it can recognize the dock due to the electrical contacts)
disable screen unlocking
silencing most alarms/alerts (so that i can sleep in peace w/o being woken up to by random spam/marketing emails overnight)
upon disconnecting/undocking, revert to original settings
are there any combination of apps/settings that can make this possible? at this point, i'm not too interested in rooting my phone...
thanks
BlueDock (market) plus Tasker (in beta, not yet in the market - http://tasker.dinglisch.net/).
In a future version Tasker will hopefully be able to do this on it's own. But currently you have to hack it useing BlueDock to start an application you don't really need, have Tasker detect the start, kill the app, and then change your settings according to your needs. One drawback is that the app started by BlueDock will only start once the phone is out of sleep mode. So you have to press the unlock button once - no need to swipe to unlock, though.
As for disconnecting you have to abuse the change in the power status.
The setup is quite complex. I will post my setup on the tasker wiki as soon as the next version is released (which will, I hope *gg*, provide a bugfix that make this a little smoother) and I have time. ;-)
I have a widget which I use to indicate whether I want to listen to podcasts (using BeyondPod) or to music. Upon switching on any of my bluetooth devices it will start playback and set the loudness according to the device connected - it will have to be louder with the car bluetooth than with the headset. Upon detecting the car bluetooth it will also start Waze.
interesting. i know what i'm asking is a bit complex. but i'll definitely keep an eye on Tasker. as they're mostly background tasks, any idea as to the battery consumption of these applications? (eg. surprisingly the "Shake Them All" live wallpaper i had installed was consuming up to 10% of battery time recently and was ultimately uninstalled even w/ those cute androids)
My usage pattern says:
40% Display
35% Calls
6% Standby
5% Android System
5% Phone inactive
2% EarthRot
2% Mediaserver
2% Android OS
Tasker isn't even listed.
Within Tasker I have more that a dozen profiles and about 30 tasks.
I just noticed this morning that when I hit the power button the screen only dims now. I swear it used to shut off the display completely before today, and I know for certain that is how it worked on 1.6. This really is annoying, because now when I put it in my pocket the 3 buttons are constantly being depresses and they vibrate, which lights the display again. That coupled with this stupid lock screen that I have to try to open 3-4 times is really making me angry. Maybe it's just me thugh.....
I'm assuming you upgraded to 2.1?
I remember reading somewhere that someone had a similar issue after upgrading to 2.1 but then they re flashed 2.1 a different way and problem went away.
Same issue here, it really eats up my battery life, and I do end up pushing those soft keys all-too often... I am on 2.1 and that is definitely when the problem started, I'm going to try reflashing to see if I can eliminate the issue.
try the steps found here on streaksmart.com. She reports that she has no issues when its done that way. I don't have my streak yet but will follow these steps when i get it.
I had a similar problem before, only the screen would go off and on again and stay on!
Turns out it was an APP that done this.
It is possible an app is causing the problem.
Don't leave wifi on when not using and the problem disappears.
vatk said:
Don't leave wifi on when not using and the problem disappears.
Click to expand...
Click to collapse
+1
I've been experimenting with what's been causing this on mine, and I noticed that sometimes wifi will not shut all the way off. It hangs at "Turning off..."
So I tried not letting it sleep with wifi on, I turn it on if I need it, then turn it off (really a big pain in the butt) but went two days with no "no sleep" problems.
Today I tried leaving wifi on all the time, not two hours later it happened.
Since it's not happening to everybody, I wonder if it has something to do with our wifi setups. Maybe the router brand, or the encryption type, or something?
Last night I powered off the phone before better. I have wifi on all the time and I never shut it off. Today though, I have had no issues with the sleep function. It's still mid afternoon so we'll see if it continues this way. If so I will explore the wifi solution as well.
I was having this problem and somehow this setting was wrong:
SETTINGS>>APPLICATIONS>>DEVELOPMENT>>STAY AWAKE
mine was checked and we all know what that mean. Check yours to be sure if your not up for flashing again. Just a thought in case you overlooked this...
bhyde said:
I was having this problem and somehow this setting was wrong:
SETTINGS>>APPLICATIONS>>DEVELOPMENT>>STAY AWAKE
mine was checked and we all know what that mean. Check yours to be sure if your not up for flashing again. Just a thought in case you overlooked this...
Click to expand...
Click to collapse
Yes, it means the screen will not time out and go off when it's being charged, but you can still turn it off, and mine wasn't plugged in when I couldn't turn it off.
I don't think this is related to what I've been seeing, but thanks.
It seems that Bluetooth did it today. I was fine all day going black on sleep with power button, but once I switched on wireless to connect to my car stereo it never went off again. Even if I turn off the wireless I have to shut down and reboot.
jnovello said:
It seems that Bluetooth did it today. I was fine all day going black on sleep with power button, but once I switched on wireless to connect to my car stereo it never went off again. Even if I turn off the wireless I have to shut down and reboot.
Click to expand...
Click to collapse
Same here. Started car and it showed zero signal strength for the phone on the dashboard display. Pressed the power button on the Dell Streak and the car display then displayed the signal strength. From then on, the screen would dim but not shut off.
Pete
petesbodyparts said:
Same here. Started car and it showed zero signal strength for the phone on the dashboard display. Pressed the power button on the Dell Streak and the car display then displayed the signal strength. From then on, the screen would dim but not shut off.
Pete
Click to expand...
Click to collapse
Was your wifi also enabled (even if not connected to any AP's) when this happened?
a042349 said:
Was your wifi also enabled (even if not connected to any AP's) when this happened?
Click to expand...
Click to collapse
Yes, and I couldn't turn it off once the "screen dim bug" took hold. Today I've rebooted and left Bluetooth OFF and Wireless ON and have not had an issue all day long, and that's making calls, using 3G, wireless and running a pile of apps. I think I can live with no Bluetooth until the next release.
Pete
I don't think it's BT. I think it's wifi not recovering properly from sleep mode.
a042349 said:
I don't think it's BT. I think it's wifi not recovering properly from sleep mode.
Click to expand...
Click to collapse
Fair call. However, I've now had BT off for 6 hours and I'm using 3G, wireless and USB transfers and it hasn't hiccuped yet. This is the longest I've had with no screen dim bug.
I did notice that when I walked out to the car, the Streak could still "see" my home wireless network, then starting the car and the BT pairing and connecting is when the screen dim bug came back.
Maybe it's when both are run at the same time and both are connected/paired?
petesbodyparts said:
Fair call. However, I've now had BT off for 6 hours and I'm using 3G, wireless and USB transfers and it hasn't hiccuped yet. This is the longest I've had with no screen dim bug.
I did notice that when I walked out to the car, the Streak could still "see" my home wireless network, then starting the car and the BT pairing and connecting is when the screen dim bug came back.
Maybe it's when both are run at the same time and both are connected/paired?
Click to expand...
Click to collapse
I agree its looks like its a wifi issue. I always keep my bluetooth off and it still did it.
I got mine fixed... but the problem is i did a bunch of steps and now cant figure out which one actually fixed it. its been running great for 12hrs now.
What I did, since I noticed that wifi sometimes didn't sleep or wake itself up properly all the time (which i think is what's affecting our Streak sleeping), was turn off the wifi sleep. In other words when my device shuts off wifi stays active.
However, I then used "Tasker" from the Market and setup two profiles. When the screen goes off it shuts off 3G, wifi and autosync. Then when the screen comes on it turns on 3g/wifi, waits 20 secs and enables autosync (which then initiates a mail/calendar/contacts sync).
This has worked perfectly, and I get mad good battery life to boot. Now this means I don't get mail/updates (facebook, weather, etc - still get calls and txts obviously) but for me it's not a big deal especially for the battery life.
I may eventually setup more Tasker events to duplicate "Juice Defender" and poll every half hour (3G only, when screen is off only) to get my updates, but for now it's been working great.
I also setup profiles so if I'm not where I have wifi pairings it shuts down wifi. Also if it detects I'm connected via wifi (at home for instance) it disables my lock screen. I also have it set to only start GPS for apps that need it (Maps, Navigation, Places, etc) and that helps save battery too.
Tasker is an awesome app for $3.99. It has a steep learning curve, but there are enough walk-throughs available to teach you how to do the basics.
rebel146 said:
I agree its looks like its a wifi issue. I always keep my bluetooth off and it still did it.
I got mine fixed... but the problem is i did a bunch of steps and now cant figure out which one actually fixed it. its been running great for 12hrs now.
Click to expand...
Click to collapse
Found the fix on Modaco. Have a look at the last page of the thread called "2.1 Bugs ....., Add what you find please....."
I never knew there was an "Advanced" menu for WiFi!
yeah that is not it. I also have mine set to never time out so does that mean it will never shut off either? Anyway, it keeps happening through the day. Wifi and bluetooth do seem to have something to do with it, but I need them both on all the time so the only thing I can do is reboot. Then it is good for a couple hours. Are the any apps that have a reboot? That's one thing I miss on the iPhone.
As being discussed in various threads, some people are having BT problems with EB13 based ROMs.
The Problem
Inability to connect at some future time after having paired device with phone. Rebooting doesn't help. Only solution is to unpair, and re-pair, then device will both pair and connect with phone.
Also seen by some people are audio routing problems after disconnecting BT. Not sure if this is confined to devices that support (and connect) A2DP... more investigation/testing needed.
The Workaround
I tested various conditions to see how the BT subsystem behaved under various usage modes. In particular, across boots, turning BT on and off on the phone, on the device, etc. -- and then observed if automatic connection would re-establish after each combination of conditions.
I found that the problem seems to only happen if I turn off BT on the phone. If I leave it on, pair and connect with a BT device, then I can turn the device on and off at will, and it will automatically connect.
This (normal) function persists across reboots, at least for the few I tested.
I don't know how power-hungry the BT radio is when idle and not connected. My gut feel is that it is a pretty small drain, so leaving BT on all the time as a workaround probably won't have much of an impact on battery drain. I use Juice Plotter, and have a good history with BT off to compare to. I'll post JP measurements/results tomorrow after a 24 hour cycle.
Caveats
I also changed my Epic BT device name before I explored this situation with toggling the BT radio on the phone. While the name change did not correct the problem on its own, I can't rule out that the combination of name change and leaving BT on is what is making things work, rather than just the latter alone. So, to try this workaround, you must also change your BT device name on the phone, and leave BT on. Then, clear pairing and re-pair for the target BT device.
My Request
Would people that are having this problem please try this out, and report back in this thread success/failure, and any other observations. What we see in testing these different modes will be very helpful to the devs in trying to trouble-shoot an fix this problem (which I have no doubt they will long before Samsung does).
It should be noted that some folks are having issue connecting to a device, even after un-pairing and re-pairing. If that is the case, you might try this-
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Also, some folks are reporting an issue with multiple pin requests before a device will finally pair. I haven't seen that one myself, but just thought I'd mention it.
For what it's worth, other than the BT routing issue, I haven't seen any of these pairing or connection issues on my stock rfs Epic. It wasn't until I converted my other Epic to ext4 that Bluetooth had any issues, and they were all fixed by wiping data and have not returned since.
I have tried the workout around before in the past, and it changed nothing. Also I have noticed I seem to have more issues with particular audio bluetooth ear pieces, like BlueAnt Q2. It will show pairing is connected but after a couple hrs on the bluetooth connection is gone, but like I said it shows paired. My cheaper Plantronic ear pieces seem to work much better, except the fact I have to re-pair after each reboot of the Epic.
Ive tried leaving bluetooth on all the time, but after a reboot,
i have to repair ive tried all suggestions to fix it and the only way it seems is once it gets connected is always have the phone on and cant die and bluetooth always has to be on,
even after a long period of time somehow it loses the connection even if bluetooth is on and phone stays on,
There must be somethng the developers can patch with a flashable fix or another work around to get squash this annoying bug.. ill try to get a logcat today and try your method again see if i have luck
I will try to leave mine on and see what happens. Name change did not help.
But short on time. But given the chance I want to go back to bonsai 3.0.1 and see if I have the same problem. I don't recall it giving me a problem.
Edit: of I leave BT on, on the phone and just turn the BT device on/off it will not pair back up.
Edit: May have figured something out. I have been toggling BT with a widget. When I toggle from the notification bar it seems to work (so far). Which would also explain why it quite working as I added apps. As from clean install is used the notification bar and later used my power widget. But I have always used a widget before. I will test this out at work and see if this work around keeps working for me.
Sent from my SPH-D700 using XDA Premium App
I have to re-enter the PIN after every reboot. Mildly annoying.
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
automator said:
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
Click to expand...
Click to collapse
In my experience, the BT radio does not use any power when not connected to a device. If it does, it's not noticeable in Spare Parts or in performance.
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
blackdragon79 said:
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Have the pairing issue with ACS EB13 Frozen ROM 1.0.3/ Twilight kernel. The BT headset I use is Plantronics 975. Never had a problem with any of my phones until now... even my Treo 755 connected properly, not to mention BB Tour FWIW, my headset supports A2DP and I wiped/reflashed ROM/kernel several times without resolving the BT issue. Will leave BT on, but does it mean after every reboot I have to re-pair? That's not good if true, I hope a permanent fix can be found soon.
davidrules7778 said:
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Click to expand...
Click to collapse
I'm using syndicate frozen
Sent from my SPH-D700 using XDA Premium App
Update: For me at least, this workaround is still working 3 days later without a hitch, and across more reboots than I can count.
While I don't _know_ with tech/spec/engr certainty, as mentioned above it seems that BT uses negligible power when it is only listening for connection requests, and has had no discernible impact on battery drain at all.
So, this seems to be a viable workaround for the time being for some of us... it's real. What we need to work on as a community is figuring out what the critical difference is between those for which it works, and those for which it doesn't. KEEP POSTING AS MUCH DETAIL AND INFO IN THIS THREAD AS YOU CAN, EVERYONE... DATA IS WHAT WILL GET US TO THE BOTTOM OF THIS.
Personally, I think the key difference between the two groups is the size of your junk -- People with small equipment seem to be having all the failures
Sent from my mind using telepathitalk
I've had this issue on all Froyo builds. I have tried 7 different BT headsets from Samsmsung, Plantronics, Jabra & Blue Ant, all of them a2dp compliant with the same result, after a while, they stop connecting and I have to re-pair. As for the "workaround" since I have several extended batteries I've never turned BT off, and while it does take much longer to lose pairing, it eventually stops syncing or syncs only the headset protocol but not A2dp. For myself, the only solution I've found is to go back to DI18 which, although has its faults, works flawlessly with BT
I have been trying to get my brother's Epic working properly. It is rooted with EB13 installed. If this bluetooth error is not related to what others are having, let me know and I will create a different thread. I got his motorola H520 paired. I press the button and it starts the bluetooth voice dialing. It beeps and says please speak and then immediately gives and error saying the connection to the bluetooth was lost but the settings shows it to still be conneceted and it is as you can answer calls with the bluetooth without having to reconnect it.
My plantronics backbeat is paired and for phone calls is working, but sometimes no audio through music or video players. I had to un-pair, then re-pair then audio will work for a while.
I am using CWM 3.0.0.6 with midnight ROM with its installed kernal
Happening on my Plantronics Voyager Pro+ - It seems that everytime I pick up my phone the BT disconnects and then after about 15 to 30 seconds reconnects as long as I don't push any buttons.
There is also a lag "thingy" that occurs when I'm on a call and then another person calls - while the the second call is coming in, it seems like the packets get interrupted from the handset to the headset. Then once the incomming call goes to VM, the audio from the current call gets restored. Not sure if this is helpful or not, but I wonder if there are some routines in the BT transmission that have common "hooks" which are used when a second call comes in - Hope that is not too much of a noob statement...
Is anybody else having that "laggy" issue in the same circumstances?
1. There is no way to sync the clock to any internet time.
2. When the battery is fully charged, the screen turns on from standby (and stays on until the pre-set time-out). This is a problem if you leave you SGT plugged in at night. The screen will turn on in the middle of the night, and possible wake you up if you leave it by night table.
3. Bluetooth tethering for internet access does not work. Using my iPhone (with a legit tethering plan), I can connect to SGT via BT. The internet setting actually recognized BT was connected. A blue square icon was also shown in the lower right corner. However, no data was transferred.
4. Launcher crashes. Regularly about once every 1-2 day, Launcher crashes; i.e., pressed the 'house' icon then a blank screen was shown. Same problem with ADW launcher. The only solution was to reboot (like working with Windows computers, needs constant rebooting).
ikeny said:
1. There is no way to sync the clock to any internet time.
4. Launcher crashes. Regularly about once every 1-2 day, Launcher crashes; i.e., pressed the 'house' icon then a blank screen was shown. Same problem with ADW launcher. The only solution was to reboot (like working with Windows computers, needs constant rebooting).
Click to expand...
Click to collapse
The only consistent crash/force close I have ever had is with the Google Listen app. I've never had a problem with the stock launcher, unless we count that annoying WiFi hang thing. But, that doesn't require a reboot either. Maybe you have defective hardware; can you return/exchange it for a new one?
Sent from my GT-P7510 using Tapatalk
1. If your tab is rooted there is. Get one of the ntp apps like ClockSync from the market.
2. No idea how to disable that. My phone does the same thing but the screen is so small that it didn't bother me much. The tablet is another thing, it lights up the whole room, really annoying.
3. Won't help you much when I tell you that bt tethering works great with my Galaxy S via the bt pan profile. All I have to do is enable bt, click the little wrench next to the Galaxy S and enable tethering. Maybe you have to enable something on your iPhone?
4. Never happened to me. You should try to set up your homescreens from scratch.
Btw. you might want to update your pc to something newer than win98 if you really believe in your comment about windows PCs.
I'm having the same problem outlined here:
https://forum.xda-developers.com/showpost.php?p=68864374&postcount=3
Basically, Bluetooth will work fine for a while but my Fitbit will drop out, usually overnight, sometimes throughout the day. This is annoying because it receives notifications like a smart watch. The only solid way to get it to reconnect is to forget the device in Bluetooth settings, turn Bluetooth off and restart the phone. When it comes back up, I open the Fitbit app, it turns on Bluetooth and re-pairs automatically and works great until a few to several hours later whenever it drops off again.
Additional info: When I got this Fitbit, it required a firmware update that failed probably 2 dozen times in a row from my Moto G4. I paired it to an old Samsung phone and the update went through quick and flawlessly the first time.
Aside from that, I've had issues with random restarts. Less so since I've reset the device but they still happen occasionally. Seems to me like I'll wake up and sometimes my Bluetooth is off, an indication that the phone reset during the night. Perhaps my need to restart the phone for Bluetooth issues has mostly eliminated the crash & restart issue, I can't recall the last time I had that problem but it was pretty frustrating, almost every day before I did a factory wipe & reset.
Aside from this, the phone works great. Stable through hour-long calls, loading up many apps at once, it does everything I need. My question is this: Should I hold out for the Nougat update , void my warranty and go with LineageOS or send the phone in to Motorola?
Using the nightly build of LineageOS (March 28) and seeing the same issue with my garmin watch. It took me multiple attempts to install an update via bluetooth yesterday. I thought it was the watch because the sync log said that the watch was disconnecting. This morning, I caught my phone's bluetooth restarting, or what I think is restarting. Specifically, the bluetooth is turning off then immediately turning back on. This is enough to disconnect my watch, and I also think this is what is causing my bluetooth headphones to disconnect periodically. From what I can tell, the bluetooth restart is happening about every two hours. The headphones will reconnect (but I have to restart my music), but the watch will not. I thought that perhaps the bluetooth is turning off to save power. Thus, I disabled battery optimization last week for Bluetooth Exptensions, Bluetooth MIDI Service, and Bluetooth Share, but the bluetooth restart issue persists. Not sure if this is a hardware issue in the G4, or a software issue. I'm really hoping it is a software issue that will be resolved in the Nougat update.
--------------------
Updated to the latest nightly build (April 4), which should be Nougat (Android version 7.1.1). Still having problems with bluetooth. The event log shows this output at the time that my phone last dropped bluetooth:
am_proc_died( 1188): [0,2084, com.android.bluetooth]
Click to expand...
Click to collapse
Log then shows that the service scheduler restarts bluetooth and the process is started. This stop and restart lasts less than 1 second, but it's enough to disconnect my bluetooth devices. Any idea on how to continue troubleshooting why bluetooth is stopping?
Something that you can try, is to go into settings, go to location, tap the three dots, tap scanning, turn off Bluetooth scanning.
I have the same problem with LineageOS 16 Android Pie, I solved it by navigating into the "Settings" and search for "Bluetooth Scanning" then turn it off.
Its description is "Allow apps and services to scan for nearby devices at any time even when Bluetooth is off. This can be used, for example, to improve location-based features and services"
I'm not sure how that really helps with location-based features and services but since it's taking an issue with my Bluetooth, I did not hesitate to turn it off.