Related
Hi all,
In my Renault BT Car Kit (originally designed by Parrot) it seems to be impossible to access my phone's contacts. I have had it working with one of the earliest Tom Codon ROMs by changing a setting in the advanced settings, bet ever after I have not been able to get it working again.
I have searched the forum several times, but it seems that I am not looking good enough.
The problem is not in my car, since I never changed it's ROM, and my wife's phone (Elf) is working great.
My phone is working great otherwise.
Tanks,
TC.
When you paired the phone with the "car" did you answered Yes to the question where you are asked to allow access to the phone contacts?
Thanks! That would be something hard to overlook , but sadly, there is no such question. Neither from the phone, nor fron the 'car'. The 'car' gives <empty> when accessing names. I have tried copying contacts to the SIM, but that also has the same result.
I have tried many (many! also the original from the provider) different ROMS the past year or so, and all of them have the same 'problem'.
When my wife purchased the Elf, the 'car' allowed it immediately, just as her previous phone (some samsung thing). It is just with the Nike that it has trouble with.
Also the Diamond of my collegue that drives the car every now and then, communicates without hassle.
The stupid this is that it has worked with a previous ROM, and I cannot find (in my memory or the internet) how to activate it again. It's more an annoyment than really really a nessesity (is that a proper word ?). I have also been looking into the advanced configuration of both the Elf and the Nike to spot a difference, but nothing seems available.
I am thinking of calling the 'car' "Christine", and just stop trying, but as a technician, I want to have this working, because it has worked before.
thanks,
T.
I assume that your wife's name is not Christine!
Did you try with WM 6.1 and 6.5, including the original ROM? Did you tried to upgrade the carkit firmware? I am using a Parrot CK-3100LCD carkit but I have no problems with my Niki since the first time I was using it.
The pairing process was started from both sides or only from one side?
No, my wife is not Christine... but Stephen King wrote a book once...
The pairing always starts from both ways, I cannot find 'Christine' from any phone without starting the pairing from both sides.
All different WM versions available for Nike have the same problem. (I have had about 30 different ROMs on my phone, just for the fun of it, only 1 has worked properly after changing 'something' in the advanced settings)
I really have no idea what kind of parrot it is, because it has been re-branded by Renault while integrating it into my Clio. I have for that same reason not tried to upgrade the ROM in 'Christine'.
Strange, very strange what's happening. Did you tried some other radio ROMs?
strange... I know...
I have been on the road for a couple of days, have installed a new ROM prior to leaving, but still the same problem occurs: I can call whomever I like, via the phone itself, and I can answer the phone normally by using the the car's controls.
In the Netherlands it is not allowed to use the phone other then via a carkit, so dialing a number is not really an option here.
I have tried several person's ROMs, also radios (although I have not been able to find a link to the recently used 1.71 version, anyone a link?), and all have the same, except for that once...
thanks!
Did you tried with another Nike (from a friend or coworker) to see what's happens? Do you see (on the car screen) the digits or the name of the callers? Did you tried pairing only from one side? Did you contact Renault for a firmware upgrade of the bluetooth carkit?
A coworker has the same problem with the original ROM in a different car (Volkswagen),
I see only <empty> when accessing the name area from the car,
I have tried pairing on different ways, all with the same result
I have not contacted Renault or Parrot , since ny coworker has the same problem AND it has worked (once) before.
It is just a strange, not really big issue, but I would like to have it out of the way.
Hello,
I have an xda prophet for quite some time now, with wm5.
I updated to wm6 and radio rom to the latest one.
After that I had problems with the connection to GPS module. I can see the module, I set paired device, set com port everithing's work fine, I recieve GPS data for a period of time (1min-10min), after that I loose conection.
I get an error that "com6 is stuck in a system call". Tried com7 same thing.
When this happens, I can not turn off bluetooth, whatever I set, led blinks like is on, status remains on, but it is not working.
After reset work's again. Sometime I get also "bluetooth hardware error" (if I keep insisting setting bluetooth after freeze) or "unrecoverable GPS error".
I tried these days changing radio rom to: Prophet_G3_G4_RadioRom_v2.61.21
and WM6.5, same thing happens.
Anyone had such experiences ? is related to rom updates or is a hardware mallfunction?
thanx,
Nemo
Nemo-ro said:
Hello,
I have an xda prophet for quite some time now, with wm5.
I updated to wm6 and radio rom to the latest one.
After that I had problems with the connection to GPS module. I can see the module, I set paired device, set com port everithing's work fine, I recieve GPS data for a period of time (1min-10min), after that I loose conection.
I get an error that "com6 is stuck in a system call". Tried com7 same thing.
When this happens, I can not turn off bluetooth, whatever I set, led blinks like is on, status remains on, but it is not working.
After reset work's again. Sometime I ge also "bluetooth hardware error" or "unrecoverable GPS error".
I tried these days changing radio rom to: Prophet_G3_G4_RadioRom_v2.61.21
and WM6.5, same thing happens.
Anyone had such experiences ? is related to rom updates or is a hardware mallfunction?
thanx,
Nemo
Click to expand...
Click to collapse
Well i would say try another ROM 6.0 or 6.1 as 6.5 is a beta platform and has many bugs
The good thing with 6.0 or 6.1 is that you can troll through the threads checking for a all working stable build
If the above don't work you could try flashing the nvid ROM this will downgrade back to original wm5 but also put everything back to original working order if not a Hardware issue
Thank you for the reply, I thought to try this and also to downgrade back to wm5. Meanwhile I searched this forum alot, and it seems I found a fix.
I edited the registry:
HKLM\Services\OBEX
(Change the "Keep" setting to "0")
HKLM\SOFTWARE\Microsoft\Obex
(Change "IsEnabled" to "1")
In my case the first entry was set to "1" by default, I changed it to "0"
The problem seems to be gone, I hope I'm not saying that too early, but yesterday I had GPS connected for a long period several times without freeze.
Thank you again, great comunity, great forum, loaded with valuable info.
PS. Admins, if you think this thread is useles please delete. Although I searched the forum alot before I posted, I did not found such problems. The fix I found was on a thread also BT related, but different problem.
So yes, I was too early. Problem still present. I will start downgrading later to see what I can fix. Any other ideeas ?
Hey, I need help on something.
I have my x10 and I tried several 2.2 roms, such as MIUI and others. But I am finding a bug with my bluethooth headset in all of them. When playing music, there is at some points a pause of about 1 second, at different times. If somebody calls me when using the headset, after the phone call, the head set seems to not be connected at all so I have to connect it again.
Some 2.2 roms even freeze and restart after the phone call.
I am using the MW 600 from Sony Eriksson.
Can anyone help on this?
If you're using wolfbreak's 2.2 rom, try installing the bluetooth fix that he has posted on the first page of his thread.(http://forum.xda-developers.com/showthread.php?t=945264&highlight=music+skips+bluetooth)
if that fails, check post 6728 here:
http://forum.xda-developers.com/showthread.php?t=945264&highlight=music+skips+bluetooth&page=673
and post 6741 here:
http://forum.xda-developers.com/showthread.php?t=945264&highlight=music+skips+bluetooth&page=675
If this doesn't solve your problem, please search the thread of the ROM that you are currently using. I'm sure other people have had similar problems and possible solutions would be posted there.
In the future if possible, always do a search before posting
Thanks, I tried but it did not fix the problem. I am finding this situation with every 2.2 rom, and I have seen others with the same problem. If somebody calls me with the headset, after the phone call I cant keep using it for music, so I have to switch it off and on again.
I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:
- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine
- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again
- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound
So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.
I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.
Any help would be greatly appreciated!
*bump*
Some additional info:
This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.
Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.
I would be happy to pay whoever can fix this problem..
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
ItzCrooK2UxD said:
With an issue like you are describing it may be helpful to list the headunit model too.
Click to expand...
Click to collapse
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.
ItzCrooK2UxD said:
I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Click to expand...
Click to collapse
I've covered everything like that in about 100 different ways, none of which made any difference.
ItzCrooK2UxD said:
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
Click to expand...
Click to collapse
Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.
Thanks for the tips!
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Apoc_ said:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
ItzCrooK2UxD said:
Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me.
Click to expand...
Click to collapse
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.
Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.
I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far!
ItzCrooK2UxD said:
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
Click to expand...
Click to collapse
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Apoc_ said:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Click to expand...
Click to collapse
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
YoghurtPL said:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
Click to expand...
Click to collapse
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).
So far I haven't been able to pull anything related from the logcat.
Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
Update:
- Updated carkit to latest firmware. No change, still same problem
- Have not been able to capture anything unusual in the logs
- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.
- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.
Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1
In the meanwhile I have upgraded to Android 4.1.2: still the same problem.
I have also discussed this matter with quite a few other Samsung smartphone owners, and all of them appear to be having the same issue. Most of them just don't seem to be bothered to spend time on looking for a fix.
Also, I have figured out that this problem is specific to media streaming. I'm able to use my phone on the carkit for calls at any time, without having to reboot first. Only when I try to listen to music, the problem occurs.
Anyway, I have ruled out that this problem is specific to me or my devices - this appears to be a global issue. So I'm completely puzzled as to why there's not a lot more fuss going on about this.
If anyone has any more suggestions for a resolution of this problem, please share.
S3 bluetooth connection problem
Had the same problem with my S3 and renault megane III handsfree bluetooth system.(Arkamsys software version 2.2.0.19 auditorium)
I downgraded to 4.0.4 baseband I9300CELH1 (stock) and problem seems fixed
hope this helps.
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Carkit bluetooth issue
Apoc_ said:
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Click to expand...
Click to collapse
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Bennes18 said:
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Click to expand...
Click to collapse
BB only, try this :
http://forum.xda-developers.com/showthread.php?t=2106424
Confirmed the update thing, i have updated the S3 to version 4.1.2 BB I9300CEELL1 and have no bluetooth issue whatsoever, car audio still on 2.2.0.19 byt the way
Pretty strange ... , but glad its working !
I have the same issue with a Ford Focus =/
also, while using CM or Omega, the music title never changes.
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
please read how to get answer quickly in my signature
and provide logcat just after the error occurs
this will help
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
First of all, JellyBlast is a banned rom here. So lets not have anymore discussion on that. As for the headset problem, you can use the SoundAbout app from Google Play. Do post the result. Hope I Helped
Thanks for the replies guys. I will have a go at the catlog later when I get home and post the results.
The problem doesn't happen every time so hear with me while I try to get it to do it so I can post the log.
Sorry for mentioning 'that' rom, I was just using that as a point of reference as it was the only rom I have tried.
The headset issue isn't that the headphones don't work though, it is that using the Bluetooth headset causes the phone to crash when answering a call (not making one though), and I thought that using the sounds out app was to fix the headphone socket issue?