Please i have problem in my device KGL . The problem is the bluetooth mic not work after i upgraded to latest malysk firmware . When i checked the default factory setting . I found that the default application for BT is BC6 this is the defult for me and bluetooth was working fine in this driver . After the firmware upgrade bluetooth mic not work . The only way the mic work is to change the BT application to BC6B and in this case the sound is very bad and low . I dont know is it MCU problem or what? My mcu version is KGL 2.83 i tried to downgrade to 2.80 but no change . So please how can resolve this problem
Malaysk has stated before not ever firmware is compatible with every unit what work before might not work if upgraded to the newest version. I am on the latest version and have 0 issues.
Sent from my SM-N910T using Tapatalk
I know . I just need to know how i solve this problem now . I changed the rom to the previous one and still the same problem
I suppose the question is.. did you upgrade the MCU at the same time as the Rom?
What MCU and Rom where you on before you upgraded to the new versions..?
If you have documented this..then try to go back to that same setup and see if it all works.. note if you do this I suggest full wipes..
The other thing you are saying here is that you don't have an option to choose the Bluetooth settings that you where using before..?
If this is correct you can only hope that reverting back to original setup will allow you to choose this setting again..
Then this all points too.. not every machine is going to behave as they should on upgrades..
The variables are.. MCU settings..which no one has cracked yet due to no source..
And the way it interacts with the Android base..
As a note; I haven't touched my MCU..and was able to access my bluetooth settings that I had before..I need to check the pic I posted as I have them in there..
Now i found the problem but dont know how to solve it . My Bluetooth Module:BC6 Stereo Module,A2DP . In the factory setting when i choose BC6 mic not work . When i choose BC6B mic work but with very bad voice . Befor this problem happend the defult setting for bluetooth is BC6 and mic was work perfect with it . So any help ?
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've got a real problem with tha activation of the GPS.
I've made all the forum says but now i can't restart COM6 and RIL (i've got the message Device load error).
I'm desperate and i don't find any solution...
Could someone help me... PLease
you need to change the COM port on the devies for it to work.
When you carry out the pairing click on com... then creat a new port and change it to one that is not currently being used.
I set mine to com 3.
I then soft reset the device and all worked ok.
Hope this helps.
D
Sorry but i don't see what you want i do.
Please could you give me more details (sorry i'm a biginner)...
Ok, So you have paired your device with the GPS.
Your bluetooth is on. In the Bluetooth manager area there is a COM tab.
Select this and create a new com port that is not already in use.
Hope this is ok for you.
D
OK, i'm sorry i told about the internal GPS of the Qtek 9600.
I want to activate it...
Who told you that there's GPS in it?
You may have noticed that this is a WM6 Forum.
Have a look at this two threads to learn everything about GPS:
http://forum.xda-developers.com/showthread.php?t=292466
http://forum.xda-developers.com/showthread.php?t=291181
Hello guy`s i have litle problem with my Bluetooth so i had 2 Blackstones and i flash them befor a while with ROOM Davideuck V-5 WWE room version and yesterday i found this problem that i can`t recive a files via Bluetooth!
For example i try to send t myself one ringtone from few diferent phone brand like Nokia SE and Samsung always give me error that the conecction is failed... and all this seems very strange because befor the flash the phone when he was with the stock room i never had a problem like this!
So i try to send a file from another HTC Crouse to my Blackstone and again give me error and was writen something like "the other PDA dont support OBEX etc" so this mean my device Blackstone don`t support this OBEX and i don`t know what mean this OBEX exactly?
So im able to sending files without a problem by Bluetooth but i can`t recive anything.. do u have some idea what mean this OBEX and why i had problem like this?
Thanks in advance!
ANY HELP PLEASE??!! WHat i can do to resolve the problem
tsalta said:
ANY HELP PLEASE??!! WHat i can do to resolve the problem
Click to expand...
Click to collapse
did u check on the "Beam" setting ? on V-4 it was off by default
lcw622 said:
did u check on the "Beam" setting ? on V-4 it was off by default
Click to expand...
Click to collapse
Ohh Yes thank you what a idiot im i forgot to chek this now work
Thanks for the advise
lcw622 said:
did u check on the "Beam" setting ? on V-4 it was off by default
Click to expand...
Click to collapse
I have the same problem and it didn't help to check the beam setting.
Do you mean Settings => Connections = > Beam?
If so, it is checked. I already HR'd it and it still doesn't work. I can only send via Resco Explorer. Could not beam out without Resco. Do not receive any beam in (even after being visible and checking the Beam setting)..
Anyone can think of a reason?
I'm using stock ROM and Radio..
Thanks.
Bluetooth trouble
Hi there, yes i do have same problem recieving any files through my bluetooth for my HD, i had try everythings to solve the problem and by the end i had contacting HTC offical technical service department but still they couldn't help their advice was to do hardware reset, but i refuse to do so because i don't want to loose everything i had downloaded. Anyone out there has any suggestion around not having to do hardware reset. The only messages come up when i try to tranfer file by bluetooth to another hanset are Quote: "Service File Tranfer is not found on Device" Plz help
i have a similar issue with not being able to recieve files but being able to send no probs,i have 2 other phones in my house a lg kc550 and a samsung j600 and when i search for bluetooth devices they dont even find my hd but when my brother came round with an older htc phone it found mine but couldnt send to me.beam is on and bluetooth is set to visible,using stock rom and radio any help would be appreciated thanks
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.
i cant connect my gpad to my cars bluetooth !
my car says pairs fail ! and nothing happen in my tablet
i tried many roms to solve this problem and one rom did this , miui (https://forum.xda-developers.com/lg-g-pad-83/development/rom-miui-v7-t3228505)
sadly this rom isnt suitable for daily use .
any one can help me solve this problem with any way (with any good rom )?
excuse me for my bad english