MobileSheets Forums

Full Version: Pixel Slates not finding leader (another Pixel Slate) at all
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I just updated my Pixel Slates to version 145.0.7632.154 (Official Build) and discovered that Pixel Slates (followers) cannot find and connect to leader (another Pixel Slate) via Bluetooth. Mobilesheets version is 3.9.33 (build 576).

I restarted multiple times after the update. 
Eventually I deleted previous connections in the ChromeOS and paired tablets again.
To connect them via new pairing again worked BUT after another restart they can't see/find leader in "Manage Device Connections" modal window.

To delete paired connections in the OS and then go through pairing every time is painful. 

It looks like Google changed something because everything was working fine in ChromeOS 144 (apart from slow connecting Airturn page turner as I mentioned before recently).

When I started with Pixel Slates in 2019 the leader (that time Master) discovery took some time (between 30sec to a minute). Later on (two three years ago) it changed to nearly instant Leader discovery.
Now followers can't find Leader at all unfortunately. 

Hope it could be resolved.
When I toggle on and allow "Discoverable" function in "Manage Device Connections" ChromeOS 144 can still see the leader. ChromeOS 145 can't.

When I ticked "Reconnect devices at startup" it did not find the leader either and I received "Group Chromebook_E36B not found."

However I also tried to to see if the Leader with ChromeOS 145 is discoverable with other Android devices which I have and I can confirm Amazon Fire 11 tablet and Pixel phone can see the leader. 

Anybody else having issues connecting ChromeOS 145 device with another ChromeOS 145 device?
(03-03-2026, 07:06 PM)Zubersoft Wrote: [ -> ]If you go to Settings->About, do you have version 3.9.34? 

Hi Mike, could you please clarify - if version 3.9.34 available for Android too?
I can't see that version on Google's Playstore.
My version is 3.9.33 (576), on the other hand I can see trial version has 631 build. 

I was hoping you could have look at ChromeOS problem with followers not finding leader with previously paired ChromeOS tablets please:
https://zubersoft.com/mobilesheets/forum...14851.html
Version 3.9.33 is the latest for Android at the moment.

I did read thispost, but I have no idea what to suggest or what to do about it, which is why I did not respond yet. I have not changed a line of code related to that, so if it stopped working after updating ChromeOS, then I imagine Google changed something. I may have to add BluetoothLE support as another option to see if that works better (that's on my list of things to do anyways). I don't have two ChromeOS devices anymore (just the one Google Pixel Slate), so I don't have a way of testing the connectivity between two Chromebooks. You said it works between ChromeOS and Android, so that won't help.

Mike
I powerwashed two of these Pixel Slates, reinstalled Mobilesheets, paired them together via MS normally, restarted and unfortunately I can confirm same problem remains.

Reported problem via OS feedback but have not much hope.

Just have to wait.
Updated my Pixel Slates to version 145.0.7632.216 (Official Build). No change. 
However I discovered these particular Chrome OS tablets were transitioned (in March 2026) to a new Bluetooth "Floss" stack instead of BlueZ.

If you go to chrome://flags/ and change "Use Floss instead of BlueZ" flag to disabled this will revert Master-Followers functionality to normal as before (to be tested at the gig).

For now...
God knows how long will that particular flag will stay in there!

I've no idea why that "Floss" (the Android Bluetooth stack) is causing problems. 
Anybody?
I'll have to research whether bluetooth RFCOMM has issues with the Floss bluetooth stack. I do think supporting BluetoothLE may help a lot with these issues.

Mike