After finding the GATT characteristics using the nRF Connect app, I decided to give Bluetooth scanning a try using an Ubertooth dongle. Using GATTtool, I was able to connect again to the droid directly.
Breakdown of the BLE advertising data packet:
Scanned Droid w/ Ubertooth, no remote on:
systime=1572470349 freq=2402 addr=8e89bed6 delta_t=156.842 ms rssi=-58
40 1a cb be 75 82 06 cd 02 01 06 09 ff 83 01 03 04 44 81 82 07 06 09 44 52 4f 49 44 6c 1b 12
Advertising / AA 8e89bed6 (valid)/ 26 bytes
Channel Index: 37
Type: ADV_IND
AdvA: cd:06:82:75:be:cb (random)
AdvData: 02 01 06 09 ff 83 01 03 04 44 81 82 07 06 09 44 52 4f 49 44
Type 01 (Flags)
00000110
LE General Discoverable Mode
BR/EDR Not Supported
Type ff (Manufacturer Specific Data)
Company: To Be Assigned
Data: 03 04 44 81 82 07
Type 09 (Complete Local Name)
DROID
Data: cb be 75 82 06 cd 02 01 06 09 ff 83 01 03 04 44 81 82 07 06 09 44 52 4f 49 44
CRC: 6c 1b 12
GATTtool Connect (w/ invalid file descriptor error):
pi@raspberrypi:~ $ sudo hcidump –raw
HCI sniffer – Bluetooth packet analyzer ver 5.50
device: hci0 snap_len: 1500 filter: 0xffffffff
< 01 0B 20 07 00 60 00 30 00 00 01
> 04 0E 04 01 0B 20 00
< 01 0C 20 02 01 01
> 04 0E 04 01 0C 20 00
> 04 3E 20 02 01 00 01 CB BE 75 82 06 CD 14 02 01 06 09 FF 83
01 03 04 44 81 82 07 06 09 44 52 4F 49 44 D6
< 01 0C 20 02 00 00
> 04 0E 04 01 0C 20 00
< 01 0D 20 19 60 00 60 00 00 01 CB BE 75 82 06 CD 00 18 00 28
00 00 00 2A 00 00 00 00 00
> 04 0F 04 00 01 0D 20
> 04 3E 13 01 00 40 00 00 01 CB BE 75 82 06 CD 27 00 00 00 2A
00 00
< 01 16 20 02 40 00
> 04 0F 04 00 01 16 20
> 04 3E 0C 04 00 40 00 01 00 00 00 00 00 00 00
> 04 05 04 00 40 00 13
