Related
Hi!
I've had problems with Bluetoot. Iäm not sure if they are connected with this, but I just noticed that the device name keeps on changing randomly.
Settings - System - About - Device ID - Device name: HTC3
I've tried to change that to something that I like and would actually identify the phone in BT connections. Yes, I can change it. But next day, or after boot (which happens about ever day anyways), this value is always on the form HTC[[:number:]]+ ... I.e. HTC + 1 or 2 numbers.
Do you guys have the same problem?
Haven't had that problem.
But the device has several different device names:
Network/wifi device name
Bluetooth device name
WinMo device name
(others if you use other services)
They can all be unique or all the same. The problem is that it's not easy to figure out where to set each of them. Luckily, Advanced Config Tool makes it easy, so use it to set up the device names you want.
fhsieh said:
Haven't had that problem.
But the device has several different device names:
Network/wifi device name
Bluetooth device name
WinMo device name
(others if you use other services)
They can all be unique or all the same. The problem is that it's not easy to figure out where to set each of them. Luckily, Advanced Config Tool makes it easy, so use it to set up the device names you want.
Click to expand...
Click to collapse
We'll I have that problem. Do you have different ROM, mine is 1.90.401.1 WWE (Radio 1.02.25.19)?
I tried downloading the Advanced Config Tool, but I get unexpected error saying that I need newer .NET Compact Framework. Is that right? Where can I get .cab for that?
ROM 1.90.405.1 WWE, Radio 1.02.25.19
Advanced Config tool here:
http://julien.schapman.free.fr/touchxperience/advanced-configuration-tool.php
Yes, you need to install .NET compact framework, which you can also find at the link above.
EnOleEikka said:
Hi!
I've had problems with Bluetoot. Iäm not sure if they are connected with this, but I just noticed that the device name keeps on changing randomly.
Settings - System - About - Device ID - Device name: HTC3
I've tried to change that to something that I like and would actually identify the phone in BT connections. Yes, I can change it. But next day, or after boot (which happens about ever day anyways), this value is always on the form HTC[[:number:]]+ ... I.e. HTC + 1 or 2 numbers.
Do you guys have the same problem?
Click to expand...
Click to collapse
yup i have this problem too...the solution is to install config3.2 and change under bluetooth setting for the bluetooth name.... this will solve this problem.
After searching for hours and hours for a way to disable voice dialing + dial last number function from my Bluetooth headset, i've decided to code my own solution, in a form of AT commands audio gateway extension. Since others may find this useful as well, i am packing it in a cab and posting it here.
All it does is putting a small audio gateway extension replacement DLL (just 4kbytes) in windows directory and changes the MS audio gateway extension settings in registry to use this replacement DLL. All the DLL does is responding with "ERROR" on the voice dial and last number dial commands from the headphone, that it. This does the trick.
To install: install the cab, reset the device
To uninstall: remove using the system control panel, reset the device
As simple as that. No guaranties. It replaces a system DLL functionality after all, don't blame me if renders your device unbootable, unusable, blows it up or even kills you... well, you know the drill, use it on your own risk. I'll be happy if someone else finds this useful.
it is embarrassing when you don't know about calling somebody
I appreciate your perfect solution
installed in kaiser with WM 6.5 OS and nokia BH-102
I tried many things and it is working perfectly
thanks
Thanks worked perfect for my wired headphones with a faulty call button.
Wired headphones?! Are you sure? Cause i would really doubt any wired headphones would allow AT commands audio gateway extension, or, in fact, communicate using AT commands.
But, if it really works... if the system actually simulates those commands and passes those through the extension... maybe i'll finally make my wired remote work with something other than the damn AudioManager program.
I am too lazy to go to my car right now (thats where the wired remote currently is), but tomorrow i am totally going to see if this really blocks the call button on that wired remote. If it does, i am going to see if the other buttons also pass through the extension, and, well, you know whats next. But i really really doubt it, its probably just a coincidence or something.
Thanks for the info.
Yes wired headphones? mine are just cheap hands free ones off ebay but pressing the button does nothing now,which is great it use to dial my last number sometimes without pressing it too.
I tried it on HD2 (Leo) but it is not working
is there any way to let it works on it
thanks in advance
I found the BT audio gateway service not loading the dll on startup on some of the devices. Try installing SK tools, go to services menu, stop the BT Audio Gateway service and then start it again, while having my cab installed. If it suddenly works and blocks the dial button after the service restart, then there may be a 'solution', as simple as making a little app that restarts the service after the device is fully loaded. Not a perfect solution, but well, if it works, then why not.
BTW, can someone point me to the right direction on how to restart WM services programatically ? What API does this ?
thanks for quick response
I tried what you said. I used Task Manager v2.9 the BT Audio Gateway already stopped and I could not start it
it says the system cannot open the device or file specified.
I have replaced the dll file manually and still
when I clicked "find in registry" it is located in HKLM/Services/BTAGSVC
BTAGSVC.dll
Replaced the DLL manually ? The BTAGSVC one ? With mine ?!?! Don't !!!
Read my post again to understand how the trick works. My DLL is by no means not a BTAGSVC replacement. What i means in my last post is that for some reason, when BTAGSVC initially loads, at the device start, it won't load the AT extension DLL (my one). I would assume this may happen because the file system is not mounted yet, or some similar reason, i don't know. And the reason i told you to try restarting the BTAGSVC is to try & see if it helps to start the service when the device is fully loaded.
Again, do not replace the BTAGSVC with my DLL, you can lose the BT audio functionality this way.
no I did not replace BTAGSVC with yours (BTAWGS)
I tried exactly what you have said. I was saying that service belongs to this file as stated in registry.
you told me te restart the service and I told the service is already stopped plus I could not start it for that error
recently I could not find BTAWGS dll file in windows folder
my question: this dll file (BTAWGS) does it exist in the original rom and your cab replace it?
regards
from my readings in this great forum
I think the bluetooth stack especially in hd2 is different than other htc devices and it is has different driver
it is WIDCOMM driver, is that true?
if so that means your file isn't gonna work
If the device is using non-MS Bluetooth stack - there is a near-100% chance my trick is not going to work, sorry.
thanks for the direction
but if I want to edit the dll file
what is the best program to do so
and what is the values that I have to change
can you tell me what you have changed in your dll file
Just in case anyone is still interested, i've now got an HD2 and found a way to disable the bluetooth dial on it. It's a bit nasty/hackish, though. Do the following:
1) Copy the "BTTrayCE.exe" from the device to your PC using any available method.
2) Open the "BTTrayCE.exe" with any available hexeditor
3) Look for "+BLDN" and "+BVRA", replace them with something like "xxxxx"
4) Replace the file in Windows directory with the patched file using any available means.
NOTES: The "BLDN" stands for "Bluetooth - Last Dialed Number", "BVRA" stands for "Bluetooth Voice Recognition Activation", those are, in fact, the AT commands your bluetooth headset sends to the phone when you push that nasty button by mistake.
I am trying to figure out how to stop the audio notification that is played when my samsung intercept connects to the network. I work in a heavily shielded building which can cause my phone to lose connectivity several times per hour.
I have searched everything I can think of (forums, google, etc) and I have not found a solution.
My first thought was to simply replace the media file. As far as I can tell this notification does not use a standard media file (ogg, mp3).
Most media files are located here:
system\media\audio
I searched for (then played) every media file on the device and was not able to find it.
Does anyone know how to turn this sound off. Note, you cannot access this setting through standard menus.
I have seen many similar posts for other devices and no solutions.
I know a little c#. Can someone point me in the right direction about how to identify and/or resolve this?
daveg01 said:
I am trying to figure out how to stop the audio notification that is played when my samsung intercept connects to the network. I work in a heavily shielded building which can cause my phone to lose connectivity several times per hour.
I have searched everything I can think of (forums, google, etc) and I have not found a solution.
My first thought was to simply replace the media file. As far as I can tell this notification does not use a standard media file (ogg, mp3).
Most media files are located here:
system\media\audio
I searched for (then played) every media file on the device and was not able to find it.
Does anyone know how to turn this sound off. Note, you cannot access this setting through standard menus.
I have seen many similar posts for other devices and no solutions.
I know a little c#. Can someone point me in the right direction about how to identify and/or resolve this?
Click to expand...
Click to collapse
Is ur phone rooted?
Hit THANKS if I helped
Sent from my Blade using xda premium
Ever since i bought this THL W8 16GB i have been searching for a solution for this Bluetooth bug.
The problem persists as following:
It shows on all Bluetooth devices i tried 3 different ones.
When calling away with the SIM set to 3G connection over Bluetooth carkit or headset the Mic is disformed but i can hear other side just fine.
On hang up both Sims lose connection and regain it after searching.
However if the SIM is set to 2G only the problem is not there and everything is just fine.
The network i am using is on 1800 mHz.
When abroad in different country I suspect 900mHz (Bytel france) the problem does not show either.
Already tried many roms for this phone 2 different stock ones and several modded ones.
All have the same result.
So i decided to open this tread since i know i am not the only one with this bug.
I'm open to suggestions and willing to experiment on this.
16-12-13 SOLVED:
Looks like i found a fix for this, problem is in one of the parameters of the audio speech enhancement settings.
this is what i did :
enter engineer mode through moble uncle tools or gravity mod.
go to hardware testing
select audio
select speech enhancement
change common parameter to BT earphone
change parameter0 to parameter12
change the value to 20488
press back several times
reboot phone and test it
i came to this solution by comparing the differences to my jiayu in witch this was recently solved.
Keep in mind for the Bleutooth disconnection problemen you can use a different modem.img as mentioned in this thread but it will reduce reception by half so for this there is no working solution
Have been searching for more info on this issue, and as far as i can find it is a jelly bean bug.
More has been logged about it from disconnecting bluetooth issues to robotic sound when using handsfree.
Just bought a Jiayu G4 advanced next to my Thl W8 and both have the same problem.
Only thing is that the G4 does not break connection with both sim networks after calling away over bluetooth just garbles up the sound from the mic.
And the same as the Thl it gives not a single problem over GSM calling only when using 3G it garbles up the sound.
Probably will have to wait until new android version comes out.
Looks like jiayu fixed this issue for the g4 advanced.
Just installed the latest 20131022 Rom and no more Bluetooth problems
Hopefully THL will implement this fix also, if not them perhaps someone else will.
Sent from my ThL W8 using xda app-developers app
Making little progress sofar..
Got the bluetooth working with one less problem.
The thing is now that after switching some files from a phone(the jiayu) that had the same problem but does not annymore after an update the 2nd problem is gone.
no more disconnections of the network, but still garbled up sound through the mic.
More testing to be done... to be continued
edit: the replaced file is located in system\etc\firmware the file to replace is modem.img
i placed the file of the jiayu g4 advanced (from anny unzipped cwm rom)
solved
16-12-13 SOLVED:
Looks like i found a fix for this, problem is in one of the parameters of the audio speech enhancement settings.
this is what i did :
enter engineer mode through moble uncle tools or gravity mod.
go to hardware testing
select audio
select speech enhancement
change common parameter to BT earphone
change parameter0 to parameter12
change the value to 20488
press back several times
reboot phone and test it
i came to this solution by comparing the differences to my jiayu in witch this was recently solve
I have just made the suggested changes and can report that outgoing calls are now perfect but that incoming calls still disconnect from the network, unfortunately my network is Three and if I connect to the 2G signal I don't get any data connection.
Sent from my ThL W8 using xda app-developers app
Ant007 said:
I have just made the suggested changes and can report that outgoing calls are now perfect but that incoming calls still disconnect from the network, unfortunately my network is Three and if I connect to the 2G signal I don't get any data connection.
Sent from my ThL W8 using xda app-developers app
Click to expand...
Click to collapse
The solution for that it's to replace the modem.img
I am using one from a jiayu Rom.
Using a file explorer with root.
Look at the description above.
Any chance you could send me a copy of the modem.img file that you are using? I tried one that I found online and lost all phone connections, luckily I had backed up my original one.
Sent from my ThL W8 using xda app-developers app
Ant007 said:
Any chance you could send me a copy of the modem.img file that you are using? I tried one that I found online and lost all phone connections, luckily I had backed up my original one.
Sent from my ThL W8 using xda app-developers app
Click to expand...
Click to collapse
You have PM
All now working ok, thanks for your help with solving this issue.
Sent from my ThL W8 using xda app-developers app
skit75 said:
16-12-13 SOLVED:
Looks like i found a fix for this, problem is in one of the parameters of the audio speech enhancement settings.
this is what i did :
enter engineer mode through moble uncle tools or gravity mod.
go to hardware testing
select audio
select speech enhancement
change common parameter to BT earphone
change parameter0 to parameter12
change the value to 20488
press back several times
reboot phone and test it
i came to this solution by comparing the differences to my jiayu in witch this was recently solve
Click to expand...
Click to collapse
~
thanks! This solved the problem i had when pairing BT with car kit PARROT mki9200!!
Now people can ear my and I dont have to shout every time!
Regards!
Hello, on my Thl W8, bluetooth headset is paired. I get a2dp but I have no audio on phone calls. I tried many things, like installing the stock rom, gravitymod2,samsung style, I tried the settings you mentioned above but nothing. Any help would be appreciated.
Did you try any other BT headsets? Did you check what is selected in the BT setting next to the device that is paired? Did you try the headset on a different phone?
These are the things that first come to mind.
And when installing the other rom's did you do a full wipe?
The setting posted in this tread is only for sound quality when calling.
skit75 said:
Did you try any other BT headsets? Did you check what is selected in the BT setting next to the device that is paired? Did you try the headset on a different phone?
These are the things that first come to mind.
And when installing the other rom's did you do a full wipe?
The setting posted in this tread is only for sound quality when calling.
Click to expand...
Click to collapse
Thank you for answering, I tried 5 different headsets that work on other phones. I tried everything that you mentioned on your post. I know that this thread is for the sound quality but I did not find anything else that has to do with MTK device and no phone audio. You were the closest one.
Difficult problem, can't say i have the solution for you as i haven't seen that one yet.
But if you did do a full wipe before flashing as in dalvic, cache and data then all settings should be new.
If that doesn't help and the problem started out of the blue (like not after a Rom update or something) then the Bluetooth module might be broken.
skit75 said:
Difficult problem, can't say i have the solution for you as i haven't seen that one yet.
But if you did do a full wipe before flashing as in dalvic, cache and data then all settings should be new.
If that doesn't help and the problem started out of the blue (like not after a Rom update or something) then the Bluetooth module might be broken.
Click to expand...
Click to collapse
I'm trying to fix this thing 2 weeks now, it started out of the blue, but the only reason I'm still trying is because I can hear music, videos and notifications through Bluetooth but no phone audio. It is just weird. Is it possible for the Bluetooth module to break and send only the a2dp? I have sent an email to THL but no answer yet. :bump:
How did you flash your phone? Cwm? I would try the flash sp program it usually rewrites more than cwm.
skit75 said:
How did you flash your phone? Cwm? I would try the flash sp program it usually rewrites more than cwm.
Click to expand...
Click to collapse
When I flashed the stock rom I did it with sp tools. The only thing I do not know to configure is audio on engineering mode. I tried also different configurations on /etc/Bluetooth/audio.conf, but no luck.
ad6 said:
When I flashed the stock rom I did it with sp tools. The only thing I do not know to configure is audio on engineering mode. I tried also different configurations on /etc/Bluetooth/audio.conf, but no luck.
Click to expand...
Click to collapse
It should not be necessary to configure that after flashing because after flashing it should be overwritten.
I'm sure of that because every time I flash my thl I need to restore the parameter mentioned in this tread.
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used.
So if I drove the car last, and then my wife drives, it won't connect to her phone without manually selecting it from the list of devices. It will be stuck trying to find my phone which isn't in the car.
I complained to the manufacturer about this silly bug (Atoto) and they issued an update that made it search for other phones. It seems to work pretty well now, but I'm wondering - is this normal behavior for FYT units? If so, what did Atoto do to fix it? I got a Bluetooth update file, it only flashed the BT system and not the rest of Android. I'm not sure what it did, but wondering if I purchase a different FYT unit, will I run into this yet again?
dishe2 said:
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used.
So if I drove the car last, and then my wife drives, it won't connect to her phone without manually selecting it from the list of devices. It will be stuck trying to find my phone which isn't in the car.
I complained to the manufacturer about this silly bug (Atoto) and they issued an update that made it search for other phones. It seems to work pretty well now, but I'm wondering - is this normal behavior for FYT units? If so, what did Atoto do to fix it? I got a Bluetooth update file, it only flashed the BT system and not the rest of Android. I'm not sure what it did, but wondering if I purchase a different FYT unit, will I run into this yet again?
Click to expand...
Click to collapse
can you confirm which update you got?
is there a specific patch name i could quote when i talk to them?
i just updaed to the 2023/02/02 release and still have this issue
It's strange they did not include this bug fix in the latest firmware update
thanks for any info you can provide
How do you check for updates?
The Bluetooth 1 system is separate from the rest of the Android OS.
Bt2 is the standard Android stack that you'd normally find on a phone or tablet, But BT1, in order to receive an incoming signal from your phone, is external hardware that exists outside of Android and seems to interface via an app that they call BT1. This does not get updated the same way as the OS does.
In other words, the firmware updates are usually only targeting the Android partition and does not update the MCU, Bluetooth, or other external components. You need to ask them for a Bluetooth update, It is performed by going into BT1 and then clicking on update Bluetooth firmware from within that screen with the file on a storage card or USB. It does not format the rest of the system, it really just update BT1 alone and can be done while the device is on. However I think that they recommend you reboot after performing the update since it is pretty heavily tied into how the rest of the radio operates.
The only thing that I don't like about the way Atoto handles customer support is their updates. They say they are going to be getting better about this in the future hopefully, but right now you need to specifically ask them for updates and there is no way to check for them.
dishe2 said:
The Bluetooth 1 system is separate from the rest of the Android OS.
Bt2 is the standard Android stack that you'd normally find on a phone or tablet, But BT1, in order to receive an incoming signal from your phone, is external hardware that exists outside of Android and seems to interface via an app that they call BT1. This does not get updated the same way as the OS does.
In other words, the firmware updates are usually only targeting the Android partition and does not update the MCU, Bluetooth, or other external components. You need to ask them for a Bluetooth update, It is performed by going into BT1 and then clicking on update Bluetooth firmware from within that screen with the file on a storage card or USB. It does not format the rest of the system, it really just update BT1 alone and can be done while the device is on. However I think that they recommend you reboot after performing the update since it is pretty heavily tied into how the rest of the radio operates.
The only thing that I don't like about the way Atoto handles customer support is their updates. They say they are going to be getting better about this in the future hopefully, but right now you need to specifically ask them for updates and there is no way to check for them.
Click to expand...
Click to collapse
i have reached out to Atoto. in order to asist in getting the correct file from them, can you please quote the filename they gave you, as a the moment they dont seem to know what i am talking about. this may help them find what it is i need.
thanks in advance
@dishe2
did it take long for you to get a response form them and the file in question?
they keep responding at the speed of only 1 email per day
between 5-6 am
constantly asking more info from me about my order
instead of telling me everything they need from me
its extreemly frustrating
have you been able to find the name of the file they shared with you?
so i can let them know exactly what I am looking for?
Maybe if you share the bluetooth update files people can review what this is about as I have not heard about BT update only.
roti86 said:
Maybe if you share the bluetooth update files people can review what this is about as I have not heard about BT update only.
Click to expand...
Click to collapse
yeah, thats all i wanted, was the file/files
at least their names
anyways, support has gotten back to me
I will provide the info I have as well as what hey expect from you in case any of you need the same fix
I figure the least I can do is share the info I have
they did not give me a file to be used in the BT files menu
wha they gave me was a config.txt and lsec6316update
lsec6316update appears to be the same file that is found in a normal update and triggers an actual update process
config.txt seems to simply contain system values and their configs, some of them not even available in the hidden menu
_____the config.txt appears to be specific to your device model
this did seem to trigger a "normal" , "full" update
but as soon as it hit the fastboot/adb/update screen
it simply seemed to apply the config file and then ask to unplug the drive
it then proceedd to boot
after booting the unit will now still search for last connected phone
but if not found within ~10-15 seconds
it tries the next one in the list and so on
I have reached back to support to thank them and ask about future updates
I still sont know if this "change" will be included in the next firmare update or not
or
if at that time a different "fix" may be needd
or
if you simply need to include the config file with the nex upate, as that seems to just be part of the structure
I will follow up when i ge more answers from Atoto
now for details needed when reaching out to them
so you dont have to struggle like I did 1 email at a time with no insight
1- screenhot of the "about device" in sysem showing the MCU version
2- further deails of the MCU by tapping 4 times and scrolling to the bottom of the black screen with all the details
3- date and vendor/site your unit was ordered from
4- order number
5- exact full model number of your unit
6- screenshot showing order and unit exact model
Bluetooth reconnects OK for me, but only on days ending with y
Uis7862 mcu type 116 fyt. Rock on.
pchtc said:
they did not give me a file to be used in the BT files menu
wha they gave me was a config.txt and lsec6316update
lsec6316update appears to be the same file that is found in a normal update and triggers an actual update process
config.txt seems to simply contain system values and their configs, some of them not even available in the hidden menu
_____the config.txt appears to be specific to your device model
Click to expand...
Click to collapse
Would you care to share the contents of the config.txt file?
That appears to be something I haven't seen before.
j0hn83 said:
Would you care to share the contents of the config.txt file?
That appears to be something I haven't seen before.
Click to expand...
Click to collapse
here are the contents of theconfiguration file
nothing really sands out in terms of a parameter that would forcefully scan other paired devices, but its working now
pleas keep in mind that my unit is an A6 PF (performance)
#test
ro.fyt.launcher = com.android.launcher8
sys.fyt.bluetooth_type=1
ro.sys.touchGesture=1
sys.fyt.systemobd=true
persist.lsec.enable_a2dp=true
ro.lsec.btname=Bluetooth 2
ro.fyt.subwoof=5
ro.fyt.message=0
sys.fyt.ec_version=6
persist.sys.ahd = 1
ro.build.go_lasttop=true
ro.fyt.splitscreen=0
sys.fyt.bluetooth_show_voice=true
persist.fyt.alwaysshowsim=false
persist.fyt.showgesture=false
persist.btpair.ssp=1
ro.fyt.amsens=22
ro.fyt.def.sb.aux=2
ro.fyt.def.sb.radio=9
ro.fyt.def.sb.player=5
persist.bta2dpvol.gain=7
persist.fyt.buildnumber=AICE UI 11.0
persist.fyt.productseries=Device Name:ATOTO A6 Performance
ro.fixed.wifi=1
ro.fyt.uiid=2
persist.fyt.enablebtvoice=true
ro.fyt.backcar_radar_enable=0
# persist.syu.backui3rd = true
persist.btmic.gain=4
persist.btautoconnect.count=3
persist.syu.single360=false
bt#ATOTO#0000
# true/false ÊÇ·ñµÚÈý·½µ¹³µÓ¦Óã¬Ä¬ÈϹØ(false)
# sys.syu.reserving_service_pkg = "com.envo.mono.android"
#µÚÈý·½µ¹³µÓ¦ÓðüÃû ±±¾©Ë«÷Ùöè°üÃû£º"com.sjs.vrbackcarapp"
# sys.syu.reserving_service_action = "com.envo.mono.android.service.MonoService"
#µÚÈý·½µ¹³µÓ¦ÓÃaction ±±¾©Ë«÷Ùöèaction£º"com.sjs.vrbackcarapp.AutoStartService"
Thanks for sharing. I don't understand coding but it seems its specific for ATOTO A6 Performance. I suppose its not a copy paste for others units. It has to be adapted. I wonder why other manufactures don't apply a patch like this. Could it be hardware related?
Battoussai said:
Thanks for sharing. I don't understand coding but it seems its specific for ATOTO A6 Performance. I suppose its not a copy paste for others units. It has to be adapted. I wonder why other manufactures don't apply a patch like this. Could it be hardware related?
Click to expand...
Click to collapse
I think it is the property "persist.btautoconnect.count=3".
If you can't find the first, go to the 2nd, and optionally go to the 3rd
surfer63 said:
I think it is the property "persist.btautoconnect.count=3".
If you can't find the first, go to the 2nd, and optionally go to the 3rd
Click to expand...
Click to collapse
Hello Surfer63.
Sorry for this and i'm trying not to be a PITA but your code skills are impressive so my question (and feel free to don't reply) is:
My config.txt only contains this:
bt#VW-PHONE#0000
ro.fyt.launcher=com.android.launcher6
sys.fyt.bluetooth_type=6
sys.lsec.carplay.OTGHdPort=3
sys.syu.dvd_external=1
persist.fyt.selectcolor=3
# ÅäÖÃÀ¶ÑÀÀàÐÍ
# 0£ºÄÚÖÃÀ¶ÑÀ£»
# 1£ºRDA£»
# 2£ºIVT£»
# 3£ºWQRDA£»
# 4: WQBC5
#
sys.syu.dvd_external (9853Íâ¹ÒµúºÏ) 0,1
Should I edit and add the line you refered to "persist.btautoconnect.count=3" after the "persist.fyt.selectcolor=3"? Or it is not that simple?
Thanks in advance.
Battoussai said:
Should I edit and add the line you refered to "persist.btautoconnect.count=3" after the "persist.fyt.selectcolor=3"? Or it is not that simple?
Click to expand...
Click to collapse
First of all: I am not sure that this is the correct property. This one is also new to me, but it is not one of the other properties. So it is an educated guess that this is the correct one.
It doesn't matter where you put the line. There is no specific order. So you can put the line wherever you want in the config.txt.
Hey, OP here. Just wanted to clarify a few things:
I originally asked the question because it came to my attention that the Atoto units handle Bluetooth a little bit differently than other FYT devices.
I was curious to see how others handle it and if they have the same reconnect issues that the Atoto ones do. I'm fairly certain that very little (if anything) would translate over to other brands, however I'm not fully aware of how other brands do it (I've owned 4 Atoto units so far and can't vouch for any others aside from what I've read here). And even stranger, the "fix" differs between Atoto's own devices (the A6 PF is a 8581 devices, and the S8 is a 7862- I own both units and both have BT updates to change how this works after I explained the problem to them, however the updates are very different).
In Atoto's platform, there are two bluetooth UIs:
1) BT2, which is the standard Android Bluetooth stack. It can be used like any other BT connection in an Android device, good for things like a keyboard or other input devices, OBDii dongles, file transfers, internet tethering, etc.
2) BT1, which is a customized Bluetooth UI to act as a receiver (all the headunit-related functions such as handsfree calls and streaming audio, which aren't part of the AOSP Bluetooth stack). They call this custom one BT1, while the standard Android Bluetooth system gets demoted to BT2, probably because they assume this is the most often used one for anyone expecting headunit-style functionality.
I'm not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto (@surfer63, is that about right?).
I'm not 100% sure how it works, but it appears that BT1 might actually rely on separate hardware that exists externally from the rest of the Android system, and only interfaces with it via an app (similar to the way the FM tuner works). Essentially it is a Bluetooth receiver that goes into the MCU mixer and controlled inside the app called BT1. The proof to me that this is the case is that:
1) You can "see itself" when searching for bluetooth devices in BT2. I haven't tried this because it feels like a paradox that would unravel the universe at first, but apparently BT2 can see BT1 as an available Bluetooth speaker, and connect to it for audio.
2) After a factory reset, BT1 retains its paired devices information (because it exists outside of Android).
3) BT1 UI has its own "reset" and sometimes even "update" function (S8 Ultra, more on that in a minute), which implies it is operating on a different set of rules than the rest of the system.
When they initially made the update for my S8 Ultra, I was given a file to "flash the firmware of the bluetooth module". It is NOT a system update, but an update that must be initiated only inside of BT1. It does not effect the rest of the system, it does not even reboot the system. You click update, wait for it to finish, then click reset Bluetooth for good measure.
On the A6 pf (5851 device), I was given an actual firmware update to test when they "fixed" it. And not just a new lsec6316update and config file, but a full blown update. It could be that the rest of the update wasn't necessary and just a line in the config was changed, but I'd doubt that since they said the unit currently did not work the way I asked, and their engineers had to "work on a fix".
Either way, the bottom line here is that the Atoto units work different from each other (S8 vs A6 pf) and both of those work differently from every other FYT device I think, so none of this is cross-device useful IMO. I believe this is why they recommended I tell people to contact customer support rather than share the fix online for others, it appears to be very device specific. And for the record, it works much better on the S8 than the A6. The A6 gets stuck if it sees the previous device when it boots up, whereas the S8 can tell when it gets disconnected to start searching for other previous devices. The systems don't work the same way.
dishe2 said:
I'm not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto (@surfer63, is that about right?).
Click to expand...
Click to collapse
The FYTs do indeed have one BT app and a "crippled" bluetooth stack. As I do not have an Atoto I can't say anything about the other parts of your theory/explanation, other then that it sounds quite logical.
dishe2 said:
.'m not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto
Click to expand...
Click to collapse
Other FYT units operate the exact same.
They have 2 Bluetooth systems installed that behave the same way as your Atoto.
Either way, the bottom line here is that the Atoto units work different from each other (S8 vs A6 pf) and both of those work differently from every other FYT device I think, so none of this is cross-device useful IMO
Click to expand...
Click to collapse
The config.txt commands to change the behaviour of the Bluetooth pairing are FYT config lines and shouldn't be specific to Atoto.
I'll have a play with my unit later and try see how they change the behaviour but I suspect they will have similar outcomes.
j0hn83 said:
Other FYT units operate the exact same.
They have 2 Bluetooth systems installed that behave the same way as your Atoto.
Click to expand...
Click to collapse
@dishe2 mentions "In Atoto's platform, there are two bluetooth UIs:"
On my Mekede 500s I only have one 190000010_com.syu.bt.apk, and it doesn't have an alternative UI for "BT1" and "BT2". Neither is there an second BT apk, nor can I access it from the Settings.
This is already a 7 year old issue that prevents us to connect anything else than the "allowed" BT devices.
Can you please explain how I get to the other other UI with the standard BT functionality?
On my Mekede M500s you can access "Bluetooth 2" by using Marios shortcut app or using his FYT management centre app.
It's a completely separate Bluetooth chip to the BLINK Bluetooth app that handles calls (190000010_com.syu.bt.apk).
The 2 Bluetooth devices have different mac addresses.