Related
Hi, this thread is here for posts that has no room in technical discussion related to this rom. From tech discussion, irrelevent posts will be deleted without excuse, without reason. So here's the correct place for them...
Well done
I just wanted to say well done for the new fast clean rom. I'm finally over 2.5!
Everything I need to work works and well and fast. Thankyou !
Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again.
the bt works fine with car set
"Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again."
it's available for wizards - search their forums: http://forum.xda-developers.com/showthread.php?t=313656
"the bt works fine with car set "
nice to hear...go on with testing
WIFI confirmed
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Excellent, a new rom to try!!
I can't believe I have only just found this. I could have been playing with it this evening. Its a little late to start messing now!!!
Thanks for all the hard work Nocturne.
nocturne.op.15 said:
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Click to expand...
Click to collapse
i think the wifi control panel only works with built in hardware. thats why its removed from the official charmer roms.
hope you are right. i wil think about removal of it for the next ver.
nocturne.op.15 said:
hope you are right. i wil think about removal of it for the next ver.
Click to expand...
Click to collapse
I dont know if that's such a good idea. Some people use SDIO wifi cards and find those wifi settings useful.
Cheers,
vlodeck
as reported from my beta man, loskarlitos, and as reported above, this wifi settings applet seems to be working only with built-in wifi modules, settings are inactive for sdio cards.
Wifi SDIO owners, please share your experineces - than i can build fully functional rom stripped down from useless parts
Hi,
first of all amazing rom. Really really fast. It syncs great under Vista. To flash from Vista you have to use the "Another Flash Method". I encountered no problems with the 12 apps running, alarm or landscape problem.
Only the Calender and Contact buttons are still hardcoded to Start and Back.
problem with alarm was solved - it was really caused by underclocking charmer down to 95mhz (I'm using BatteryStatus for dynamic overclocking. 95MHz is simply not enough power to bring alarm window up and system behaves strange)
problem with changing landscape/portrait disappeared and never came back - but will keep it in buglist until this is really confirmed
lagge number of running apps stil remains - if lot of apps running, softkeys are not working as they should...hope somebody could try this on another wm6 device?
Calendar and Contacts issue
Been testing this rom for a day or two - I get the problem where Calendar and contacts won't start (whether from soft keys or the Start menu) and I have to soft-reset to egt it working. I admit I have been using iContact as well so I will uninstall that for a few days and see if the problem goes away.
closing some apps does not help? it helps for me...
customization?
Hi, when i flash yours new rom and make HR system was start and customization from old wm5 was started. In rom 4.4 customization was not started after HR, is this was changed in this release?
sorry for my english....
This was reported and will be modyfied in next ver. Till then, just skip the customization after HR
Ring tone changes....
Hi, next thing is that my ring tone changes to default without my command. I've seen this before in previous roms but in 4.4 it was ok.
I installed this last night. Seems nice and fast.
I noticed that the phone pad SIP and MMS are missing. (Installed these manually)
Also, i'm afraid the Bluetooth A2DP appears to still be the older, poorer quality version.
Cheers
phonepad sip is missing because i don't like it - it is not necessary. everybody can install it easily manually. but it will not eat precious memmory for us who does not use it ,-)
MMS support is there - no problem with it, thing you report is a bit strange...
it's hard with A2DP. Some testers were reporting it's the best A2dp they have seen - you tell the opposite. The worst thing is that i cannot test it - i do not have a2dp device :-( is possible that transfer quality is also dependent on used HW?
regarding those ringtone changes - i was testing this today (about 10 calls, some restarts etc - no problem. aren't you using any 3rd party software for phone profiles or things like that? I saw this with pocket zen phone..if not, try please to search for some dependency of this behavior so i can repair it
Thanks Nocturne.
I'm really starting to think I've flashed the wrong ROM. I've got so many on my PC now.
Can you confirm what I should be seeing under Device Information?
Thanks
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
1) I dont think that was ever a default thing? Did you install something and forget? have a cooked rom? There are A2DP solutions in this forum, "Use the Search luke."
2) No, its shagged. I installed the windowslive50.cab file I had on universal, it works now.
3) No idea, mine works fine. Hard reset? Check your sim?
I can get online with my WLM but it does sometimes take a resync of the whole account to do it.
Skype did say (unless changed recently) that they were still working on transferring calls to bt headsets. Which means, currently, that it does not work through anything other than headphones and the mic on the phone.
Comm Manager
Hello,
It is possible to change the green color from the Comm Manager ?
Thanks
French Keyboard
I have upgraded my french Advantage and all is OK apart for keyboard layout. On my old Universal (also french keyboard) I had changes the registry for hklm/software/oem/qwerty layout to 1040C (hex) and it had worked.
On the advantage this does not seem to change anything, any ideas?
Also has anyone got integrated VoIP working? I have used a CAB file from Universal to activate it and SIP Config Tool to do the set up but it does not allow me to select VoIP from today menu.
Anyone got this set up and working? Integrated VoIP is the reason I upgraded to WM6!
Messenger Etc....
Live Messenger stops working correctly after a soft reset. Initially it works fine. Contacts show as offline, although they are still able to contact me and vice-versa.
As far as I can ascertain push email still functions correctly.
I cannot confirm whether this is related to MS's side (rather than the program) as I haven't had chance to check if anyone else experiences the same problems.
Have tried installing the separate CAB file but I am subsequently told that I do not have the necessary permissions (or something like that).
This comes from tests on a T-Mobile branded Ameo (not the brand new one I'm selling, if anyone decides to cross-check!)
I haven't come across any other problems. Seems a bit less laggy than the original T-Mobile ROM, loads up web pages slightly faster too it seems.
No other issues as yet.
Ive had no probs at all since installing the messenger cab.
Still using it now.
Do we know what version of WLM is on this new ROM?
I've pulled \windows\wlmmessenger.exe to desktop and looked at the Version tab...10.6.28.2700 is what comes out.
Pyrofer - can you do the same on your cabbed version and let me know what the version number says? Not always an accurate guide but worth a shot. Also the digital signature is 3rd May 07.
Cheers
Ant
EDIT - never mind, just seen ur post in general Athena tab...10.6.0026.1400
I wonder what is different? If anything? I also wonder whether this is actually a final release of the ROM that's just been leaked early, as WLM is a pretty central component to web using Athena owners (myself very much included) and for it not to work after a soft reset...hmm.
Hi royalmail,
I've got exactly the same problem you mention about the phone.
I was unable to answer calls.
So I belive you've use the second file to upgrade to WM6 (HTC001 ... with ipl...).
You have to go back to WM5 WWE using the last ROM posted in the Athena upload folder in the XDA FTP. After flashing your Athena to WM5, Use the first ROM posted (the one with a readme file included).
And voila! No problem at all since I've done it this morning, everything works fine!
Hope this helps!
Hi Thibale,
I flashed with the t-mobile version. the phone dead only once so far, though i am not sure it's caused by WM6. Anyway, thx for sharing your info.
royalmail said:
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
Click to expand...
Click to collapse
See if this helps
http://www.silentservices.de/btIO.html
Also, read through the forum regarding some of your other issues.
Try to disable your GPRS and see if your calls start coming through.
Pyrofer said:
Ive had no probs at all since installing the messenger cab.
Still using it now.
Click to expand...
Click to collapse
Thanks for all the input.
@Pyrofer, could u upload yr WLM5.cab here? thanks in advance.
Hello,
I setup my voip on the PK3.0 rom, its dialing and it almost works. Except that I can not hear anything, I can speak and the other party hears me just fine, but I can not hear them, anyone came across this? What can you recommend to fix this?
bump, still no resolution to this, it works fine one way. But I can't hear anything the other person is talking....
Anyone?
marek101 said:
Hello,
I can speak and the other party hears me just fine, but I can not hear them
Click to expand...
Click to collapse
This isn't going to help much but .... sounds like the perfect setup to me.
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
I would be very much interested, how would you go about by debugin' this ?
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
Hi!
I start by stating that I finally got it "working"! Yeahh! This "thing" costed me a hard reset and a lot of frustration. Let me write down what I think is the issue/"solution".
I say "working" because it is almost impossible to get the sound out of the Athena, unless you use a bluetooth headset (I haven't tried the wired one) and the supplied Voice Dialer.
To keep it short, for the Athena X7501 here is what you need to do to have "native" VoiP working partially as thought:
Connect the BT headset
Leave the Voice Dialer activated (Cyberon Dialer, provided in the original ROM). That means that the relevant entry in the registry shouldn't be set to '0': HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\LaunchAPEnable
Connect to your VoiP Servce and launch the phone. Now you should see your VoiP provider as agent. Dial the number (Good luck with the ipdialplan.xml) and you see that the Voice Dialer pops-up! Ignore it. The relevant communication port is happily already taken by the VoiP. You hear the sound on your bluetooth Headset. If you like, you can now transfer the sound to the speaker!
To my understanding, after having spent hours on this issue, I think that this is due to a DLL modified by HTC. Don't ask me which one. There is NO registry entry you can play with to solve it, unless you 're really lucky with the DLLs provided. It seems that there was some kind of agreement to make life very difficult to those trying to communicate through VoiP. I personally use VoiP only at home and don't bother too much. Maybe all this is history in the cooked ROM. Let's see.
If you don't need the Voice Dialer, then I suggest you use Fring. It works well both ways. However to use a Bluetooth Headset, you need to deactivate the Voice Dialer in the registry.
I hope this helps.
Rgds
Dod
P.S. The above are applicable to the original US Rom of X7501
There has been a discussion at Skype with respect to 6.1 and Skype failing to work correctly http://forum.skype.com/index.php?showtopic=112059
Maybe this might be of help.
Strange problem. Maybe you can try with software like fring.
Ran it on pk3 without any trouble and now running it with the 6.1 rom and still working fine
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.
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.