Hi there,
by browsing a bit on the filesystem of my Hero, I uncovered some files called audio.conf, main.conf and input.conf in the /etc/bluez-directory.
Editing the contents (eg. discoverabletimeout) in it didn't do anything though -.-
I was wondering, if it's possible to get the bluetooth, working on the phone, to get its settings from these files, rather than from somewhere else (wherever that may be -.-)?
Running VillainRom 5.4, btw...
Sorry if I have misread your post, but doesn't Bluetooth work now on 2.1 ROMs?
I managed to transfer a photo to my friends phone last night via Bluetooth. I just went into the Gallery, selected a photo and then chose Bluetooth from the Sharing options. Worked straight away.
I'm using SenseHero 2.1
It DOES work, but you might want to tweak it a little
e.g. disable the timer for discovering the phone, etc...
Come on, there has to be some way...
This little **** won't connect to my handsfree anymore and I think this is related to some settings within these .conf-files...
So, after applying the official 2.1 Update, this little f***** keeps connecting, disconneting, connecting, disconnecting, connecting...
I'll never gonna buy HTC-stuff again... Fed up -.-
Related
Does anyone else have issues using the Ford SYNC Services with their Droid? Everything pairs fine and I can make and receive calls as well as stream music via BT. However, if I try to use their "services" option to check traffic or get directions it will dial in and then when I get to a point where it tries to locate me but just freezes and never completes the task.
Both my wife and I have only had this issue once we bought the Incredible. Our previous phones were the Palm Pre and it never had this issue.
Any help would be appreciated.
km2010 said:
Does anyone else have issues using the Ford SYNC Services with their Droid? Everything pairs fine and I can make and receive calls as well as stream music via BT. However, if I try to use their "services" option to check traffic or get directions it will dial in and then when I get to a point where it tries to locate me but just freezes and never completes the task.
Both my wife and I have only had this issue once we bought the Incredible. Our previous phones were the Palm Pre and it never had this issue.
Any help would be appreciated.
Click to expand...
Click to collapse
I just logged in to post this same issue. So yes I am having the exact same issue. I'm heading over to syncmyride.com to see if there is anything there.
This may be related to limitations with the Bluetooth implementation on the Incredible. I had problems (and crashes) trying to use my Incredible with a Bluetooth GPS device. When I called HTC support, they told me that HTC can only recommend connecting to Bluetooth headsets.
Here is a thread (somewhat technical) which supports the idea that HTC has incomplete Bluetooth support on the Incredible http://community.htc.com/na/htc-forums/android/f/91/t/2336.aspx.
If everyone who has Bluetooth issues takes the time to call HTC support (866-449-8358 in US/Canada) and file a complaint on the issue, maybe this will eventually be fixed.
286 said:
This may be related to limitations with the Bluetooth implementation on the Incredible. I had problems (and crashes) trying to use my Incredible with a Bluetooth GPS device. When I called HTC support, they told me that HTC can only recommend connecting to Bluetooth headsets.
Here is a thread (somewhat technical) which supports the idea that HTC has incomplete Bluetooth support on the Incredible http://community.htc.com/na/htc-forums/android/f/91/t/2336.aspx.
If everyone who has Bluetooth issues takes the time to call HTC support (866-449-8358 in US/Canada) and file a complaint on the issue, maybe this will eventually be fixed.
Click to expand...
Click to collapse
Thanks, I will be calling for sure. I had no issues with previous phones, including non-rooted and rooted Eris with my Alpine BT radio. Now I've had hit or miss connections to the radio, and have even had the radio power off when calls come in. Something is not quite right.
286 said:
This may be related to limitations with the Bluetooth implementation on the Incredible. I had problems (and crashes) trying to use my Incredible with a Bluetooth GPS device. When I called HTC support, they told me that HTC can only recommend connecting to Bluetooth headsets.
Here is a thread (somewhat technical) which supports the idea that HTC has incomplete Bluetooth support on the Incredible
If everyone who has Bluetooth issues takes the time to call HTC support (866-449-8358 in US/Canada) and file a complaint on the issue, maybe this will eventually be fixed.
Click to expand...
Click to collapse
Will definitely continue to call. However, on a side note its not a BT issue b/c I can call straight from my phone as well even if its not paired via BT and I still get the same issues. Seems like many are having tons of q's about the Incredible b/c call waiting times are extremely long.
Finally got through to someone at HTC. No progress there. The claim that its an issue the different companies. Microsoft vs Android. HTC believes that android has blocked MS from using the location features. I do not agree with this and am quite dissatisfied with HTC customer support. I will keep on looking into this issue and hopefully find a solution
Found a Solution
I finally found a solution. This is what I did to get SYNC working:
1: Goto phone settings
2: Select Wireless & networks
3: select BT Settings
4: Select Advance Settings
5:Make sure FTP Server is checked
Now you will be able to use Vehicle health report and other SYNC Services such as Directions, Traffic, etc...
Hope this helps
km2010, That's great. I'll be trying it on the drive home tonight. FTP!?! Why would you even think of trying that?
I know sounds crazy! Lol I figured since SYNC works via voice over data I thought maybe if I enable ftp maybe it will be able to send whatever info is needed. So far no problems and everything is working wonderfully.
It didn't work for me Maybe it's a combination of settings. I tried GPS on and off, but neither made any difference. I'll keep trying.
On my phone I have use wireless network and gps enabled. Also before doing all of this I did a master reset with SYNC and I unpaired/removed SYNC from the BT settings of the Incredible. That way I was able to establish a fresh connection with our vehicle and the Incredible. Hope this helps
It might... I'll try this weekend.
Well I tried it all... Deleted pairing from SYNC, reset the phone, turned on FTP and GPS, paired the phone. And still nothing.
I doubt the GPS setting has anything to do with anything. My old WinMo did not have GPS and it worked perfectly with SYNC. Still it's wierd that yours works and mine doesn't. Could it be the OTA for the phone (I installed it) or updates to SYNC - don't know if there are any.
Our sync is version 3.1. Are you using Google voice. If so the number u set is some 760 area code number.... other than that not sure b/c but my Incredible & my wife's Incredible worked.
not using GV. It dials the 800# fine, it dies when trying to get the vehicle location. Which is very odd! My old phone did NOT have GPS and SYNC worked flawlessly. Even odder - now I can get traffic or directions to work once in every 10 attempts, and never back to back.
I have a new 2010 F-150 and am having the same problem with the HTC Incredible. Ford's solution - use another phone for my free 3 year trial of Traffic.
There must be a fix... hopefully when Froyo hits, this will be resolved!
Jon
jmorisey said:
I have a new 2010 F-150 and am having the same problem with the HTC Incredible. Ford's solution - use another phone for my free 3 year trial of Traffic.
There must be a fix... hopefully when Froyo hits, this will be resolved!
Jon
Click to expand...
Click to collapse
Our vehicle is a 2010 as well. Have you tried:
1: Remove and unpair Sync in the Incredible's settings
2. Delete all devices from your vehicle by going to BT Setting on you Truck's stereo and select delete all
3. Then turn BT off on your phone
4. Turn BT back on on you phone
5. Make sure Sync in not listed as an added device, if it is still listed try to unpair/remove it until it is no longer listed as an added device.
6. If SYN has been successfully unpaired and deleted from the phone, then Goto phone settings Select Wireless & networks, then select BT Settings, Select Advance Settings, and Make sure FTP Server is checked
7. Repair the phone to you Truck and it should work.
Now you will be able to use Vehicle health report and other SYNC Services such as Directions, Traffic, etc... This worked for both my Incredible and my wife's Incredible. Our friends who tried this had success as well.
Hope this helps
km2010 said:
Our vehicle is a 2010 as well. Have you tried:
1: Remove and unpair Sync in the Incredible's settings
2. Delete all devices from your vehicle by going to BT Setting on you Truck's stereo and select delete all
3. Then turn BT off on your phone
4. Turn BT back on on you phone
5. Make sure Sync in not listed as an added device, if it is still listed try to unpair/remove it until it is no longer listed as an added device.
6. If SYN has been successfully unpaired and deleted from the phone, then Goto phone settings Select Wireless & networks, then select BT Settings, Select Advance Settings, and Make sure FTP Server is checked
7. Repair the phone to you Truck and it should work.
Now you will be able to use Vehicle health report and other SYNC Services such as Directions, Traffic, etc... This worked for both my Incredible and my wife's Incredible. Our friends who tried this had success as well.
Hope this helps
Click to expand...
Click to collapse
I have tried ALL these steps, however not it this specific order. I have ran a health report as well as been able to occasionally receive directions (3 times) but it has never been on a consistent basis.
I will try these steps tonight, thank you for your time and advice - its much appreciated.
Jon
Not entirely sure but it may have to be in exact order. At least that's how I got it working.
Sent from my ADR6300 using XDA App
km2010 said:
Not entirely sure but it may have to be in exact order. At least that's how I got it working.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Tried your suggestions, unfortunately - no of them worked. I was able to use my wifes Samsung SAGA - so I know its not a harware issue on the vehicle.
Thanks for trying to help!
Jon
After trying out several ROMs I have noticed that my wi-fi randomly disconnects, but only for (Non-HTC/Sense) ROMs.
I'm running OpenDesire at the moment, which I really like, but the arbitrary disconnetion of wi-fi is driving me crazy.
As far as I can tell, it has done this with the other Non-Sense ROMs I have tried as well, and I have no idea why.
Wi-fi does switch on, but (part of) the problem _seems_ to be that the phone has trouble actually getting an IP; other than that, and why it does this, I have no idea.
The settings (in *#*#4636#*#* test mode) are basically the same as they are for, say, the official HTC Sense OTA or Pinky, for which wi-fi seems to work perfectly.
Although, to be honest, I'm not entirely sure what I'm looking at/for...
Anyone have any ideas?
Any help would be much appreciated
It's not having an issue with getting an IP, it's having an issue with authentication.
The first thing I noticed with these roms is they do not re-prompt to enter a password again if you have mis-typed it at all. This leads to wpa_supplicant client to effectively force a connection and get a refusal in quick succession. The wpa_supplicant client on the phone then disables the connection until you step in and either choose to reconnect or edit the password manually.
The issue we are having is related to this;
After being connected to WiFi for a fair period of time, it re-authenticates with the base station/router as it's supposed to do.
From memory, the re-auth happens every 60 minutes and most decent routers are able to change this.
At this point, the client (phone) tries to re-auth and fails (for whatever reason). Instead of prompting for a password (as it should do). It tries 3 times in total and stops.
After the last failed attempt, it disables the connection that it failed to connect to and jumps back to mobile data (if available).
So. Yes, there is a major issue with the wpa_supplicant in non-sense roms. Could we get the devs to investigate this, as it's really getting to be a major pain in the arse!
I see... Thanks for the clarification. Nicely explained.
So, short of jumping ship to Sense, there's really not much I can do then, other than wait for someone more skilled than me to come up with a solution?
No workaround, third party app, router setting or anything?
Unknown at this moment in time.
I'm investigating this in my own limited knowledge of Android and Linux systems, so far I've not come up with anything solid.
As far as settings you can change on your router, it all depends on your router and it's firmware.
I've got three different routers here:
A) Trendnet TEW-435BRM v4.00.07 : No way to change Key Renewal length
B) Linksys WRT160Nv2 v2.0.03 : Able to change Key Renewal length
C) MZK-MF150 v1.00.16 : Able to change Key Renewal length
Check your router, try increasing the length and have a play around. It's not a fix, the issue is either in the AOSP kernels or the wpa_supplicant module.
My NetGear WNR2000 does not seem to have any (easy) way of configuring Key Renewal Length, but I'll have a look around. Else, I guess I'll just have to bite the bullet and go with Sense for a while...
At least now I know it's not just me. That's always comforting.
Thanks for the help acolwill!
No problems at all.
I have been trying to locate an app that will automatically restart the WiFi if a disconnection takes place, however, I've yet to find one :|
Anyone out there know of one?
eham, there's an app on the market called "WiFi Auto ReEnabler"
Give it a try, as it may well be the answer you've been looking for!
Sounds very promising indeed. Will get right on that.
Tried an app called Wifi Fixer, but that was a bust. Actually somehow managed to make things worse (for me, anyway).
Thanks for the tip. I'll be back with an update...
Ok, so "WiFiReEnabler" does actually do just that; re-associate with the network everytime the screen wakes. Unfortunately, what it doesn't do is stay resident.
It will let itself get killed by the system very easily, so I still have had a few times where I had to manually deactivate and activate wifi because WiFiReEnabler didn't have my back.
If the developer could make this a helper app/system service, this seems like it could be a decent workaround though.
I did however find an app called "Fix My WiFi" (£0.99 in Market) that seems to take care of the problem nicely, and quietly, so far (about 16 hours and counting, fingers crossed).
It also has some options to set different levels of aggressiveness, and notifications, which I like.
I also found a free app called "Wifi Reassociate" that seems to address the same issue. Haven't gotten around to trying it yet, as Fix My Wifi still seems to be doing its job.
Still, a tip for anyone with the same problem.
With that (hopefully) outta the way, I'm off to celebrate the anniversary of my birth.
Be well, friends.
I have posted this in other forums with no luck. I was hoping that maybe someone here had some answers...
I have a 2011 Ford Explorer with SYNC v2.7 (latest version until next month). It has capability to download phonebook information including photos. It is also capable of supporting SMS.
When I got the truck, I was on 2.1 (TMO-USA). The phone paired fine and people on the other end told me I sounded great. Photos from phonebook did not show up. When I tried to access messaging in SYNC, it told me phone did not support this.
I upgraded to 2.2.1 and the phone still pairs easily. Still no photos, and now SYNC recognizes that the phone has messaging capability. BUT... SYNC only randomly picks up the text messages. As near as I can tell, if I get a message just before I get in the car and start it, then there is a good chance the system picks up the message.
Lastly, now with 2.2.1, the person on the other end tells me that I sound like I am in a wind tunnel. I removed and re-synced the connection and still same thing.
QUESTIONS-
1) Anyone know what might be preventing the SYNC system from displaying my photos?
2) Anyone know why the messaging works on occasion?
3) Anyone else experience the "wind tunnel" effect?
4) Is there anything that can be done (maybe different ROM) to resolve this?
Thanks
I would advice you to try with another phone this way you might exclude the car as the reason. I suggest this because I have the feeling that the car might be the fault and the software that is incompatible with the official bluetooth standards.
If it works with other phones (maybe even Android) then the situation clears a little bit and you have a more clear way to follow.
Keep us up to speed.
After upgrading to ND8, I was really disappointed that Bluetooth would not stay connected in my car. It paired find and would happily connect. The car then sent a MAP request and a PBAP request. I accepted both (just as I would with 4.3) and all seemed to work. I could play audio and use the phone, and the car even reported that the phonebook transfer succeeded. But then somewhere between 2 and 10 minutes, it would disconnect. Then in about 15 seconds it would reconnect and be fine for another 2 to 10 minutes. And this repeats non-stop. This made phone calls almost impossible.
At first I guessed I got a bad flash. I re-flashed stock, I flashed Wicked X, then I re-odin-ed. Nothing helped. After looking at similar threads for other phones, I tried playing with WiFi settings, but that didn't do anything. Tried some Xposed settings... nope.
Finally I found that if I repaired the phone (deleting the old records on both the car and phone) and this time I refused the PBAP request, all was fine. No more disconnects!!! I don't really need my car accessing my phone book, but it was nice with 4.3 to see caller names and pictures on the car display during a call. Also I have found that an initial MAP requests is being made when bluetooth connects, but when I receive a text, I no longer get a notification on the car. So MAP is not working.
Are other people finding that MAP and BPAP are working for them on ND8? I haven't seen this reported, so I have to imagine this is not a common problem. Everything worked fine for me with 4.3 so it seems my car does support MAP/BPAP, but now there is some incompatibility and I am not sure if the bug is with ND8 or my car.
Car is a Toyota Rav4 EV. Phone is a Sprint 16G SG3.
For the MAP issue, I am wondering if I need to use Samsung Messaging to get MAP? I use Hangouts. 4.4 added a new way to select a default messaging app. In 4.3 it seemed that both apps were active, but I had turned off notifications in Messaging. In 4.4 only Hangouts is active.
It is so frustrating that the Bluetooth stack changes from version to version isn't it. You'd think they would only add features rather than break things, right?
Well, luckily I haven't had disconnect issues, but the MAP profile you are mentioning for text messages, well it comes up on the screen, but doesn't display the originator of the message in the Toyota Entune's nav screen the way it used to. Seems to display message header garbage rather than the text message originator like it used to do.
I've also noticed that the display of title metadata on the cars screen for what's currently playing isn't showing the title changes as often like it was working on 4.3.
Sent from my Nexus 7 using Tapatalk
After a bit more experimenting it seems that I was wrong. It seems that MAP is what is causing the disconnects and not PBAP. I had tested disabling MAP and PBAP together for many days which made me confident that I had found a solution. But I assumed that, of the two, PBAP was the issue. Next I tested disabling PBAP only and it seemed to be working fine so I decided my assumption was right. But I didn't test that long enough and the problem returned. I am now running with PBAP enabled and MAP disabled and it looks to be working, but its still early. I'll report back after some long drives which will test it much more effectively.
I assumed PBAP because looking through threads, others have reported disconnect issues with PBAP on other phones. It seemed a logical conclusion, but BZZZZTTTTT! OK, more after further testing...
My experience is that if I have my Sony Smartwatch 2 connected I do not have random Bluetooth audio disconnections, however if the audio accessory is the only Bluetooth device connected it will disconnect every 10 or 15 minutes. Not sure if that is helpful.
Fred
Hey folks!
I just picked up the BS3 after being generally disappointed for most of a year with the Razer Phone 2. I got the EU version (I guess?) and have been having general issues with the wireless.
Periodically, almost the entire suite of wireless connectivity just drops. My WearOS watch (Ticwatch Pro 2020) will disconnect, and the custom watchface I use via Watchfaces disappears. Wifi usually keeps working so I may not notice the drop right away, but if I'm on my phone's cellular connection, nothing goes through even though it shows signal and LTE. In my car on my way home from work this morning I was on the phone with my captain, and the bluetooth connection to my car started cutting in and out, to the point that I had to turn bluetooth off to finish the call. There was no issue up to that point, while driving and listening to Audible.
I am suspecting/hoping it was user error in setting the device up. I backed up my RP2 to Google Drive, because I didn't want to lose my apps/data (I was mostly hoping my Swype settings and game logins would transfer over, since Swype died and I'm being a luddite, and the games require the hassle of 'transfer IDs') and have my text messages transfer over easily. I think it also possibly transferred the core device stuff like cellular and bluetooth settings as well, though am not sure.
Turning airplane mode on and off seems to 'reset' things and it'll reconnect to stuff, for a while again at least. I noticed I am somehow still getting at least some push notifications on my watch even though it shows as disconnected. I am a firefighter, on AT&T's Firstnet, so am also not sure if maybe the Firstnet bands might be being finnicky with the BS3.
Thanks ahead of time for any help and suggestions!
ETA: I also get the "Xiaomi SIM activation failed" alert every time I restart the phone, and sometimes after reboot the keyboard doesn't load. ? I get the feeling ill need to reflash again, but knowing where I went wrong first would help! Also curious if there is a stock Android ROM because this JoyUI seems a hassle, and I just don't want all the Xiaomi stuff.