yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Battoussai:
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.
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] j0hn83:
Other FYT units operate the exact same.

They have 2 Bluetooth systems installed that behave the same way as your Atoto.

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.
[FYT Android Head Units] surfer63:
@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?
[FYT Android Head Units] j0hn83:
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.
[FYT Android Head Units] surfer63:
Never too old to learn something new. Obviously I did not pay attention enough to Mario's FMC apk.

Nice challenge for tomorrow at ascension day.
[FYT Android Head Units] dishe2:
In Battoussai's case, his unit was an A6 PF, what fixed my S8 would not have worked for him, which I guess is why they said other users should contact them for a fix bc it is unit specific. I'm glad I didn't share something that might have bricked his unit.

I don't think it was just a line in config text. They would have been able to do that a lot sooner if so.
[FYT Android Head Units] Battoussai:
Well, I did flashed my unit with the supplied config line and it made no diference. My unit still connects to the last phone used. My wife's phone is ignored - I have to pair it manually.

Please beware my unit isn't a Atoto A6. It is a D-Noble FYT unit with core 7862 specific for VAG models (VW, Skoda and Audi).

I already contacted the supplier (who is manufactor) a long time ago when I noticed this "bug" and after a couple of whatsapp messages the support team said the engineer told them that issue could not be solved - it was supposed to act like that. Annoying....
[FYT Android Head Units] dishe2:
Oh wow- ok that makes sense.

Atoto gave me the same runaround first as well, telling me this was the intended purpose because of some sort of security features... unlocked the headunit via paired phone or something like that. That doesn't make any sense, I explained because A) I don't use any kind of screen lock, whoever is driving my car has access to the unit, and B) If they previously paired their phones, I'm obviously OK if they have access to the car! None of that made any sense at all and I persisted, telling them I should have gone with a standard carplay/AA unit that had proper bluetooth support for less money. We have three people in my household using this car (myself, my wife and my daughter who just got her license), and it is unnecessarily complicated to remember to swap to your phone when driving. They actually voiced some requests to go back to the stock radio instead!

Eventually Atoto caved in and had their engineers make a solution. They said it would take some time because they needed to test it and everything, but honestly they got back to me in a matter of days which was incredible!

It sort of reminded me of those who maintain custom roms, someone requests a feature and they roll it out because they are a small team. This is why I bought another radio for our other car from them as well (the A6).

I'm not 100% sure, but I feel like based on the back-and-forth and time of turnaround, the solution was engineered by a small team at Atoto instead of from FYT. Or maybe in tandem, I don't really understand how the hierchy works between OEMs.

But when I wanted it for my A6 PF, the solution was different because it uses a different BT chip. And they needed time to get back to me on that one as well.

Does your bluetooth app have a button to update the firmware like mine did? I could see about sending you the file if you want to show your manufacturer. Or you can tell them Atoto has a solution, why don't they too. I'm not sure if it's safe to flash this on yours in case it bricks your bluetooth module.
[FYT Android Head Units] j0hn83:
The are different Bluetooth apps from different suppliers that seem to act differently. It might be worth trying a few out.

My Mekede M500s will automatically switch between different phones and won't only try the last device connected.

Yesterday I flashed an Atoto S8 2nd gen AllAppUpdate.bin and everything works perfect, including their Bluetooth app. However it behaves different and won't switch between 2 phones automatically.

I also can't find a way to pair from the app instead having to pair from the phone.

The Atoto BT2 app takes me to the Bluetooth 2 connection page in the standard Android settings however this doesn't work on the Mekede's.

I'm going to download a bunch of AllAppUpdate.bins from different resellers and try various Bluetooth (BT1) apps.

I quite like the Atoto launcher with the ability to create widgets and multiple home screens that are fully customisable. Will write more in a separate thread later.
[FYT Android Head Units] dishe2:
Yes, I also really like Atoto's launcher more than the others. It has a very uncluttered and close-to-stock AOSP feel which I really like. And honestly, after reading about the way other manufacturers handle customer support and things like the standard bluetooth connections, I'm liking them as a brand more and more.

That's interesting re: the BT2 app. You're saying it doesn't work on your unit even with Atoto's allappupdate? So your Android Bluetooth stack is actually gimped on a level beyond the app layer?

Meanwhile, like I said earlier, the bluetooth "fix" for my S8 2nd gen was NOT in the allappupdate.bin, it was a separate firmware update inside BT1. It survived hard resets and even retained my paired devices. When I did a twipe_all command and flashed the latest firmware, it actually went back to connecting to only the last phone used.

I had to contact Atoto to fix it after that. I couldn't figure out what was wrong but a lot of weird things I couldn't fix started happening. Apparently, the twipe_all messed up a lot of configuration that their regular full firmware updates didn't put back in place. I actually needed to contact customer support flash another config file from them to get everything working normally again.

I can't say for sure, but it seemed almost like I was using a different bluetooth receiver. It behaved differently. Whenever anything would play from my phone (notification chime, etc) it would pause whatever was playing on the head unit for the duration of playback, then switch back to what was playing. The sound wouldn't play (it only does that if the source is switched to blueooth, that works much like the radio and aux input, only unmuted when active), but it paused the rest of the system which I found interesting. And annoying. Get a lot of texts during a song and it sounds like the music is glitching and buffering.

Then Atoto sent me the config file I'm attaching here.

After flashing that, my Bluetooth behaved like it did before the twipe_all, properly switching to other paired devices and no longer interrupting the rest of the system when sound plays. But I had to repair my devices again. It feels like something in this config told the system to use a different bluetooth module, and this config was missing from the standard firmware flash because without a twipe_all command it wouldn't be necessary I guess. I don't know, it's all very odd.
[FYT Android Head Units] Battoussai:
Yeah that's what I've said to customer support, there are plenty of families and the designated driver isn't always the same. It doesn't make sense to scroll BT menus every time I change driver. But they didn't came up with an answer about it.

I will check better for that alone button to update BT but I'm almost sure it does not have that.

Please see attached photos of my About Device. Thanks for all your information.
[FYT Android Head Units] j0hn83:
It probably did. That's exactly what sys.fyt.bluetooth_type=X does

On my unit changing it from 1 to 0 changes the Bluetooth module that BT1 uses to that of the BT2 chip.

Edit: to add to that, changing to sys.fyt.bluetooth_type=7 adds a new option in the BT1 app settings, "Bluetooth Firmware Update".

What file type was the Bluetooth update file Atoto sent you? Do you still have it? (I have no intention installing it only to analyse it).
[FYT Android Head Units] dishe2:
That's super fascinating. What does that mean? Your bt1 app will open the Android settings for Bluetooth? Or it will just use that radio chip for BT, allowing standard compatible devices to pair?

Because as I understand it, the purpose for the additional BT module is that Android doesn't actually accept incoming audio connections (it can only connect to other BT speakers, it doesn't know how to BE a speaker/receiver), and so therefore a special external module had to be added to allow incoming connections and then interface with Android via an app.

If you switch modules in that config line, does your phone no longer pair for calls/A2DP streaming? If that internal BT chip can handle those things, I must admit I don't understand the purpose of the 2nd module.

This just keeps getting curiouser. Yes, I think I have the file still (and if not, I can get it- I have gotten pretty friendly with a representative of the brand on social media), I should just share it for anyone willing to try it at their own risk. I feel like maybe if the right people looked at it, it could help more people?

EDIT: Found it in an email support had sent me. The file name is BT.bin, which isn't very helpful lol. If you want to play with it at your own risk, I can drop it somewhere. It's only about 1.4MB in size.
[FYT Android Head Units] dishe2:
What the heck, why not. Here's the file. PLEASE ONLY USE AT YOUR OWN RISK. I don't know what will happen if you use this on the wrong hardware.

Other things to note are that they had asked me to send them a screen shot of my BT Version and System info in order to engineer an update that fixed it. If you want to see what those were to determine if your system might be compatible with mine, this is what I sent them (these are the before shots):
[FYT Android Head Units] j0hn83:
It uses the BT2 chip in the BT1 app.

I can see the mac address in the BT1 changes to that of the BT2 chip when I set sys.fyt.bluetooth_type=0.

The BT2 chip doesn't change (as in they don't swap).

Like I said earlier, in the default state (sys.fyt.bluetooth_type=1) only my Mekede BT1 app works. I connect both phones and my ODBII to the BT1 app.

The BT2 connection won't work. It pairs but fails to stay connected.

I just successfully paired my phone to BT2 with Bluetooth tethering which works but it is incredibly slow. So it's not as broken as I 1st thought.

With sys.fyt.bluetooth_type=0 set anything that I pair in the BT1 app is already paired in the BT2 app.

I think both Bluetooth modules are capable of both at the hardware level, just Android itself isn't designed to accept incoming Bluetooth audio connections. Just like an Android phone isn't capable of being a Bluetooth headset.

BT2 is just a shortcut to the standard Android Bluetooth settings menu which is why BT2 can't be used for calls/audio.

So the Chinese got clever and made the BT1 app to handle incoming Bluetooth audio.

That's certainly my understanding of how it works.

Thanks for sharing the Bluetooth .bin file.

Edit: a little unrelated, but is there a way to access the factory settings on the Atoto s8 gen2?
[FYT Android Head Units] dishe2:
I agree re: how and why BT has two modules, this has been my experience too. But I'm surprised to see that Bt1 can use the bt2 chip and pair items to both. Essentially, the software (bt1 and 2) can use both at the same time? Like, if a phone is paired to bt1 and you have it tethering thru bt2, will it ring and take the call? Because if so I must admit that I don't understand the purpose of having 2 chips if software can use one chip for both.

Also, I wonder if there's a difference in quality using one or the other re: phone calls and mic input....

Re access to the factory settings... The factory settings as in the FYT secret menu? Or the AOSP settings screen?
[FYT Android Head Units] dishe2:
A bit unrelated (but still somewhat related), in my thread here, I have been trying to get some sort of universal player control in a widget. A lot of people have mentioned the Ubiquity Widget, and there's even a Teyes based custom launcher someone has it integrated into.

I tried it, and it does not work with Bluetooth, only apps like Spotify or installed media players. It seems like others have implied it should work with Bluetooth also, is it possible that it does not work because of my odd Atoto Bluetooth setup compared to other FYT radios? Or does Ubiquity not work with Bluetooth for anyone?
[FYT Android Head Units] surfer63:
I don't know, but the source code is here.

Someone with enough time and knowledge could search through it and mayber adapt it.
[FYT Android Head Units] surfer63:
I now see that I recompiled the source code for Android 10 on 8 April. I had completely forgotten.

But I did not change anything in the source code itself.

I just did a quick search but can t find anything. I really think your desired BT functionality needs to be completely built from scratch.
[FYT Android Head Units] dishe2:
That's what I would have thought until people kept recommending this one, there's even a launcher here based on it working (I think you responded to me in that thread).

Agama and vivid do it, and that widget linked above does too, so it's been done before, but I don't understand how.
[FYT Android Head Units] dishe2:
UPDATE: Holy smokes you guys, I tried VIVID launcher again yesterday. I remember it was buggy as heck on my FYT unit when I tried it last year, I went back to the stock launcher pretty quickly. But I installed it again to demonstrate to someone how a music widget might work if designed correctly because it was one of the few that got everything right, especially integrating Bluetooth control.

OMG you guys, they really upped their game! It seems like they not only fixed compatibility with FYT radios, but actually figured out how to do something people told me was impossible on my Android head unit: Automatically switch to Bluetooth when it plays.

Right now, it gives me a music widget with universal controls and now playing data, which I wanted (including album art when applicable), and if I play something over Bluetooth, it WILL ACTUALLY PAUSE THE LOCAL PLAYBACK AND SWITCH SOURCES TO BLUETOOTH.

My goodness. I have to do some more testing but this is kind of amazing so far. This is how all default launchers should have worked from the factory! I really liked the stock Atoto launcher but I might just switch to this full time because this is what I always wanted it to do. I know I took my own thread wildly off topic so I'll stop here but for anyone that stumbled into this I wanted to supply a solution.
[FYT Android Head Units] TPMunster:
Hi!

Did anyone try installing the BT.bin on a Joying UIS7862 unit?

I tried getting through to Joying support, explaining the problem and referring to your experience with Atoto, @dishe2 , but they didn't want to move a finger or even look into it further - just stating, "This functionality cannot be achieved on our units"...

It's really a deal breaker that these units only reconnects to the last used phone 😔
[FYT Android Head Units] Samitro1:
Have the same problem, this is stupid. Everytime you have to enter the menu and connect to BT instead of it connecting automatically. I have reported to Joying.
[FYT Android Head Units] marchnz:
They won't care.
[FYT Android Head Units] Samitro1:
Apparently they don't, this is terrible experience considering Joying is the most expensive one. Looks like I'll return my unit and get something else. I tried in Nova Launcher to create a settings widget on home screen that take me to Android Bluetooth settings straight but selecting a device there does nothing, it has to be done through their settings which means multiple clicks and angry wife ... Joying device is going back.
[FYT Android Head Units] WarSpaz:
Yeah, I noticed the same thing with my unit. In my unit i cant even see a list of connected units. The only thing showing is the currently connected phone
[FYT Android Head Units] Samitro1:
yeah I noticed this when an iphone is connected, you have to disconnect it before and hope it does not connect quickly before you connect the other device.
[FYT Android Head Units] Samitro1:
BTW. I have tried to create a tasker widget and add it to home screen to connect to specific bluetooth device but that doesn't work either as it triggers connect from Android Bluetooth settings and it is not possible to connect / discconnect fromm there. If I could find a command that would work, with tasker it would be possible to create a widget. Any ideas?
[FYT Android Head Units] j0hn83:
It might be possible to connect from the Android Bluetooth settings with a tweak.

Backup your unit with the backup script in post #5 of @surfer63's excellent thread.

Take the config.txt come from the backup and change "sys.fyt.bluetooth_type=X" (x being your number) to "sys.fyt.bluetooth_type=0"

Then put this config.txt along with your lsec6315update on a clean USB stick formatted to FAT32 and put it in your unit and let it update.

This makes both BT1 & BT2 (if you have such an app) use the SoC's bluetooth chip for calls, meaning the phone will show up in the Android Bluetooth settings.

That might allow you to use tasker how you want, or it might just change the behaviour of how Bluetooth connects for the better.

If it doesn't help just change the 0 back to whatever number it was and flash it back again.

I'm not very familiar with Joying units. Hope this helps.

Edit: a very handy little tip I noticed on 4pda is that if you take a couple of the lines from the config.txt that Atoto use (and other resellers like Datong) you can use both Bluetooth chips at the same time for more than just Bluetooth tethering.

This allows you to use the BT/Bluetooth app for calls/media and the BT2 app (or the Android Bluetooth settings if you have no BT2 app) for things like OBDII and Bluetooth keyboards/lights/etc.

Edit 2: What I didn't notice before is that the above config.txt change also adds a shortcut to the Android Bluetooth settings inside the FYT settings page. Credit to @brymbrym for spotting this and posting it in this post here
[FYT Android Head Units] surfer63:
If you are using the 0 option like @j0hn83 describes above, you can use below method from android java to start the general bluetooth settings.

public static void startBluetoothSettings(Context context) {
Intent intent = new Intent(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
context.startActivity(intent);
}

And otherwise you might be able to use the intent "android.provider.Settings.ACTION_BLUETOOTH_SETTINGS" from Tasker.
[Moto Z Questions & Answers] akikoo:
I have a Lenovo Moto Z (XT1650-05, sheridan model). According to fastboot, it's in securestate: flashing_unlocked.

I tested flashing TWRP 3.3.1-0 into the recovery partition and it worked, but I can only start TWRP once it's flashed

and I haven't rebooted the phone.

Now the question I have is, can I flash griffin ROMS into it? I see many different ROMS here at XDA, but they seem

all to be for griffin.

At https://wiki.lineageos.org/devices/griffin/ the page also mentions the code for sheridan, XT1650-05

Supported models:
XT1650-03
XT1650-05

so I'm hoping if someone could tell me if it's possible or not.

Thanks,

Aki

Edit: now that I tried to download the installation package from URL https://download.lineageos.org/devices/griffin, I get this error "This device does not exist"
[Moto Z Questions & Answers] akikoo:
I updated my XT1650-05 with the files:

lineage-19.1-20230218-UNOFFICIAL-griffin.zip

MindTheGapps-12.1.0-arm64-20220605_112439.zip

and

twrp-3.3.1-0-griffin.img for the recovery and it worked! :) I'm a happy guy now.

Edit: also Magisk install succeeded but it was a bit complex.
[Moto Z Questions & Answers] SirRGB:
me too

nice to hear people like using what I did :)
[Moto Z Questions & Answers] akikoo:
I couldn't make Magisk hide itself from my banking app so I reflashed the phone again without it.
[Moto Z Questions & Answers] akikoo:
@SirRGB I have a curious problem with your ROM. If I set the preferred network type to LTE only,

I can't make or receive phone calls. But if I set it to LTE/WCDMA, the phone calls work fine.

My SIM should support VOLTE.

Is there some fix for this issue?

Best regards,

Aki
[Moto Z Questions & Answers] SirRGB:
Well I personally dont use it as daily driver, so I didnt check volte. Im sorry if it doesnt work and will look into it, but no promises made. You can however check the 18.1 (A11) builds of Nolen, whose builds will soon be official. They are also a little better security wise since those builds contain enforcing sepolicy and ecnryption. Note that gapps are included.

Odd Solutions Downloads

updater.oddsolutions.us
[Moto Z Questions & Answers] akikoo:
@SirRGB Unfortunately the phone doesn't allow me to use LTE-only as the preferred network mode with that 18.1 build by Nolen either. The call hangs up immediately. I contacted my network operator if they can see if there's something wrong. Thanks for helping out

P.S. Finland is getting rid of the 3G cell towers at the end of this year :)
[Moto Z Questions & Answers] SirRGB:
Thats odd, I didnt expect it to be dead in older versions as well. Can you send logs? (Matlog is the easiest way if you arent familiar with adb)
[Moto Z Questions & Answers] akikoo:
I've used adb shell quite often but if you have some instructions on what to run I'd be grateful.
[Moto Z Questions & Answers] akikoo:
> I contacted my network operator if they can see if there's something wrong.

The cell operator said that my SIM has VOLTE and it should work all right.