iPhone With Windows 10 Enterprise Via Bluetooth Low Energy (GATT)
Bluetooth pairing is requested when logging into Windows even though pairing has already been completed. After that, even if the pairing is done, pairing will be asked again at the next login to Windows every time when the Windows is restarted.
Our iOS app acts as a Bluetooth central and the other as a peripheral (Bluetooth Driver on Windows).
when the app is trying to connect using Bluetooth Low Energy (GATT) at step 5 as mentioned below, new pairing is requested from windows every time when the PC is restarted.
Steps to reproduce the problem:
log into Windows and connect the app to the Windows computer
See the paring request on Windows and on iPhone,
Pair on both Windows and iPhone
Turn off the Bluetooth toggle on iPhone and then turn it on
Restart windows and see the login screen
Start the app on your iPhone and try to connect,
See the paring request on iPhone
With the above steps, if this issue is not reproducible, try rebooting the iPhone instead of changing the Bluetooth toggle at S4.
we also observe the iPhone device is receiving this log from Windows:
default 15:38:27.555377+0530 SpringBoard Received request to activate alertItem: <SBUserNotificationAlert: 0x105916a90; title: Bluetooth Pairing Request; source: bluetoothd; pid: 88>
We observed that looks like the issue reproduces more consistently when the windows restarts or reboots.
On the pairing request alert dialogue on iPhone, If I press "cancel", the app disconnects from the peripheral (Windows). If I press "pair", the peripheral nothing happens. However, Windows continues sending me pairing requests whenever the machine is restarted or rebooted.
We did not observe this behaviour with the Android Device. Windows and Android work without any problem (i.e. No new Pairing is requested once the device is paired in any situation).
In the below screenshots, we could see that the iPhone is already paired in Windows Bluetooth Settings but the Paring is requested from Windows on iPhone to pair again and in the background, our app is successfully connected to Windows using Bluetooth Low Energy (GATT).
Environment:
Windows details
Edition Windows 10 Enterprise
Version 22H2
Installed on 5/5/2021
OS build 19045.2486
Experience Windows Feature Experience Pack 120.2212.4190.0
iPhone OS - iOS 15.6.1 and 16.1.1
Is this a known bug with Windows 10 Enterprise?
Is there any way to get around this issue?
Sample Code to reproduce the problem on iOS:
Our iOS app acts as a Bluetooth central and the other as a peripheral (Bluetooth Driver on Windows)
Initializes the central manager with a specified delegate and dispatch queueself.cbManager = [[CBCentralManager alloc] initWithDelegate:self queue:bleManagerQueue];
Scans for peripherals that are advertising services to discover other Bluetooth devices, passing in the UUID of the service it’s searching for.
[self.cbManager scanForPeripheralsWithServices:(NSArray<CBUUID *> *)serviceUUIDs options:(NSDictionary<NSString *,id> *)options;]];
When the central manager discovers a peripheral with a matching service UUID, The method saves the peripheral as the property discoveredPeripheral and calls connect to it.[self.cbManager connectPeripheral:
[[self.currentConnection device] peripheral] options:nil];
Step 3, when trying to establish a connection to a peripheral, pairing is requested even though pairing has already been completed. After that, even if the pairing is done, pairing will be asked again at the next logon to Windows.
Is this a known bug with Windows 10 Enterprise?
Is there any way to get around this issue?
iPhone Already Paried
Pairing Request on iPhone from Windows
Is this a known bug with Windows 10 Enterprise?
Is there any way to get around this issue?
Related
I have 5000 devices enrolled with EMM using android management API and recently I am getting issues with multiple devices out of nowhere and getting and error prompt after scanning the QR code on re-enrollment. All of my enrolled devices are Samsung Tab with the older version of android(7-9) and the issue doesn't seem to be related to the android version. Also, The issue has been experienced for the device which was earlier enrolled and was working fine but recently has this issue, we tried re-enrolling it but it gives us the same following error prompt after QR scan.
Cannot create a work profile - The security policy prevents the
creation of a managed device because a custom os is or has been
installed on this device
For your kind information, there is no custom os installed on the device and the device is not rooted or bootloader is not unlocked. I have researched a lot over the internet but cannot find a solution to the problem I have tried following approaches but it doesn't seem to work in my case
To fix this, you will need to update the time on the device by either connecting to wifi or cellular data (insert SIM-card), or by manually changing it in the set-up screen. After this is done you will be able to provision the device.
Tried DPC Identifier method for enrollment, When prompted to sign in on fresh factory reset device, enter afw#setup, which downloads Android Device Policy. Scan a QR code or manually enter an enrollment token to provision the device.
None of the above seems to work for me, I have also seen that its an issue related to Samsung Knox version, so can anyone from Samsung or google help me debugging and solving this issue, will removing the Knox app from the device work in my case.
Eagerly awaiting for the response as most of my device has started getting affected with this issue, please let me know your thoughts and resolution on this.
Not sure if that's an option for you as you have multiple devices, but on my single device, manually downloading and installing "google apps device policy" resolved the issue.
Been a lurker for a while and posting for the first time
Work as IT helpdesk and found a fix for us (context below)
We use Azure, InTune and Samsung Knox
Needing to assign a Knox profile so an application installs and runs
How we fixed this
Unassigned Knox profile
Ran tablet normally, skipping setup of Google, Samsung account and security
Running Samsung updates until current (24th Feb 2021)
Reassign the Knox profile
Factory resetting through settings
run through the setup process
Error has stopped at this point
You can either use Wi-Fi or SIM Card Data for OS updates through Knox
I had the same problems and this is how i fixed it. I have Samsung Tablet Android 10 and need to set it up under Enterprise.
Straight out of the box, you expand the OS, set up Network connection and than type in the google gmail space: afw#mobicontrol. This Does Not install the custom OS. Once expanded the OS has all the bloated software in tact plus the Mobicontrol app. I kept getting an error 'Can't Create Work Profile because Custom OS is installed on this device'. I did a factory reset but did so by powering it off than using the Power Button and Up Arrow to force it to the Android Recovery Screen. There is a factory reset option to choose from. "This Does Not Work". It still keeps the bloated software in tact.
You need to expand the Android OS first than do a reset. Go to SETTINGS. than ABOUT. at bottom is a RESET option. Choose that. Choose Factory Reset. This will delete all those apps. It reboots. Now you can enter afw#mobicontrol at the google email screen and it will install the custom OS and works under Soti.
Reset From the SETTINGS and do a Factory Reset. Than type in AFW#MOBICONTOL and the custom OS will work.
In my application, I am using STm32L4R5VG as a host MCU. I want to upgrade the firmware of host MCU in run time over USB through the Android mobile app.
I have looked into USB DFU mode, but in that case, my device will enumerate as ST USB and also I need to enable the boot loader with boot pin.
In actuality, my device will connect with the Android mobile app using the CDC class device and enumerates as VCP. So I want to send the firmware file from Android mobile to host MCU over VCP and write into Bank2 of internal flash (as current code is in Bank1). Once the file transfer is done, the device will reboot on its own and check for the latest firmware and boots from Bank2.
I am stuck at how to write at bank2 securely during run time and perform self reset to boot from Bank2.
If anyone already worked on this or know about this then please guide me or point to the link where I can get details for this.
I can request a web service running on IIS Express/Parallels from Mac OS with...
http://windows:57239/api/hello
This works fine from the iPhone simulator, but not from an iPhone device connected via USB, when debugging in XCode.
Is it possible to make this work? I would like to debug my API with in-app purchases.
I switched my Parallels instance to Bridged networking mode and let the Wifi's DHCP assign an IP address to it. Then I used this IP address from the iPhone app.
Not entirely satisfying because the IP will vary, but its very cool having an iPhone trigger a break point in Visual Studio running on a virtual instance of Windows.
I have created an application in sybase envioronment for iOS application and I deployed the same in Mac OS.
I registered a new device in Sybase Control Center device users, and the same configuration I have given to my iPhone simulator in Mac Sybase settings but it's never getting registered to SCC, always showing the activation status as Pending.
Can anyone help in solve this issue?
Finally i got a solution to my question. The error was not because of any problems with code or the deployment. The problem is windows firewall in SUP server machine is keep on blocking the port that we are trying to communicate with Sybase Control center and the iPhone device.
I just deployed my app to my iPhone for the first time. Every time it launches it vibrates before running, and it runs fine. The build is a Debug | iPhone one of my app.
Any ideas why it vibrates when it launches and how to stop that? It's definitely not something I coded up and I don't have any exceptions or issues when running in the simulator.
The vibration happens when you build the application in debug mode, and run the application without a debugger waiting. The MonoTouch soft debugger vibrates to inform you that it couldn't find the debugger.
Running the app in Release | iPhone mode solves this.
The number of vibrations is used to notify the user of a problem setting up debugging at startup. The full list (that will be maintained as we expand or modify it) is here:
http://monotouch.net/index.php?title=Documentation/Debugging
As of today:
Device Diagnostics
An application compiled with debug mode that has been deployed on the iPhone will try to contact MonoDevelop on startup on the IP address and port that MonoDevelop had at the time of the build.
If there is an error setting up the debugger, it will vibrate one of more times:
One vibration: The application was compiled with debugging support, but it is unable to reach MonoDevelop on the specified IP address and port to setup stdout/stderr
Two vibrations: It is unable to parse the address configured.
Three vibrations: Could not setup stdout/stderr to the application.