Hi
Does anybody know if there have been changes to the bluetooth system (bluetooth stack) between 30B and 30F?
I am having troubles with my smartwatch, I often have to pair again - somewhere I read this is due to the bluetooth stack on the phone, so I am kind of hoping there have been enhancements between these versions. Currently I am on fulmics 4.0 with xceed kernel.
Hello
Did you resolve your problem? Since I passed to the V30N, I have the same issue.
Related
Okay I need some major help. During an exhaustive search to find out why my Cingular 8125 does not have BT Stereo capabilities I found this forum. According to a couple of threads the v2.17 ROM Upgrade should fix this issue. Well I ran the upgrade and not only do I still not have the wireless stereo, but under my device information....my ROM version is showing 1.8.11.1 WWE....NOT 2.17. I dont know what to do......does anyone have any ideas? In addition I cannot find a thread that tells me how to unlock my SIM. My model number is WIZA100.
unlocking -
http://forum.xda-developers.com/viewtopic.php?t=33796&highlight=
BT stereo fix
http://forum.xda-developers.com/viewtopic.php?t=48535&highlight=
As far as the ROM flashing goes - I had a similar problem where the OS ROM wasn't updating. Mine was from one summiter ROM version to another, but I found that flashing back to the original Cingular ROM (using summiter's stock 1.8 Cingular ROM) and then flashing with the 2.17 ROM worked.
Thanks CameronJ....so, did you run the add on seperate from the ROM upgrade in order to the A2DP working? According to summiter, the 2.17 upgrade was supposed to include the A2DP. Ah well....I will try the addon and see if that works for me. Thanks again.
I actually don't really care about A2DP - I don't use my phone for listening to music - so I can't help you with that question unfortunately.
Same issue
I have the same problem but doing as you said did not correct it. Any ideas what I might be doing wrong?
Joe
Re: Same issue
darmiejm said:
I have the same problem but doing as you said did not correct it. Any ideas what I might be doing wrong?
Joe
Click to expand...
Click to collapse
Your problem is with the OS upgrade not taking? Are you sure that you have unlocked your phone? What's your current OS version?
I have an Eonon GA2114 - rk3188, 800*480, KLD2 2.77 MCU, BC6B BT board
With the original Eonon ROM bluetooth is unusable. There is no default device name or PIN. If I type in these, they disappear after reboot. It does not detect either phones or OBD, nor is it detected by phones.
With other KLD ROMs bluetooth is active, can be paired to both phones and OBD but all sound is muted during calls (both ways)
With Joying ROMs, including Malaysk, BT works as it should.
This is clearly a software issue, anyone has any clues about where should I start looking? Are these manufacturers using different BT stack implementations maybe?
Anybody can provide a working rk3188 800*480 Eonon ROM? Not the October 19 ROM also available on this forum, that one has the issue described above.
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Sn00k said:
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Click to expand...
Click to collapse
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
m00n61 said:
waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
At present there is no need to have a bugged (and unfixed by Google) Lollipop 5.0.x on these units, Kitkat 4.4.4 is still the best IMHO.
We'll see in the future what will happen with Marshmellow...
m00n61 said:
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Sn00k said:
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Click to expand...
Click to collapse
MCU and OS ROM image are independent, even if the Chinese keep sending both you can burn only the Android ROM and leave the MCU untouched.
Anyway, I am currently using this ROM. A more detailed installation procedure is in the first post of the thread.
Go to factory settings and adjust the bt module there. Code is 126.
I was seeing the same thing when I found that option and began playing around.
My LG G3 wifi and bluetooth stucked at turning on. Tried factory reset and flashed the ROM but still not working. Have not tried changing to another Kernel yet, you know one? Could it be hardware problem? I read Marshmallow update would be the solution...or install another rom. Please someone give a solution
gsmunlockremote said:
Wifi and bluetooth adress can be fixed with profesional tool
Click to expand...
Click to collapse
A oc
What kind of professional tools are we referring here?
probably a hardware issue...
Hi there!
First of all, someone in the forums mentioned that this (your) problem could be caused by the battery, that changing the battery may solve the issue.
Second, I had the same problem on my G2 and I believe this sort of problem occurs mostly on all kind of LG devices. I wrote a detailed post of what I have researched, you might want to check it out here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Good luck!
i heatead the wifi antenna at 180°C and now are working !!
Hello everybody,
I write this thead because i have a issue major with bluetooth and particulary with control lockscreen with a device connect. My Bluetooth is ok when i connect a device, but when i want to use the fonction throw miui or Google account to control my smartphone with device connected impossible to see the device. In Google account with smarlock no device see, in miui with unlock with a Bluetooth devince after , actualiz nothing to do, no device. Has everyone this problem and thre is a solution for it be functionnaly ?
I have miui 9.5.19.0 no root and no twrp installed
Thks a lot
Hi there. Does anyone has this bluetooth issue?: After reboot I have to forget and pair my devices again. I see saved devices,but cant connect.
I have pie 10.9.0.0.