Yea, Location Beacons or Proximity Beacons shouldn’t matter here.
I tried the Android Beacon Tools now, and I’m also having trouble. The beacon showed up once for me, and I even managed to connect, but then I couldn’t unlock the beacon, it’d just fail and go back to prompting me for the unlock code each time. So I restarted the app and tried again, and now I can’t see the beacon on the list anymore. (This is on Nexus 5X, which arguably is known to have a pretty problematic Bluetooth stack.)
In the meantime, the iOS Beacon Tools app keeps detecting the beacon, connects immediately, and unlocks just fine.
BTW, from what I see, it’s actually possible to use Beacon Tools to register a beacon in Google’s Cloud without having to provision it/use Eddystone Configuration Service. I enabled an Eddystone-UID packet on my other Estimote Beacon via Estimote app, went to iOS Beacon Tools, found it on the list, added a Description to it, and it now shows up on my Google Beacon Dashboard.
(I’m 99% sure it used to be the case that you had to use ECS with Beacon Tools in the past, otherwise the “Registration” box wouldn’t even show up. I guess they changed that, and I applaud that change :P)
So if you’re just trying to get your beacon registered in Google’s cloud, it might be easier to do it this way. (i.e., keep using Estimote tools to configure the beacon, only use the Beacon Tools for registration)