Kurt, Cool. I've had other apps (Music Folder Player) that had/have issues w/ A9.
Take your time. I was hoping to get more done over the holidays myself. My keyboard drawer project got delayed two days. I moved a fan after brushing on a second coat of stain and it blew particals on to the surface. God Bless, GregS <>< Jan 2, 2021 4:35:11 PM Kurt McCullum <[email protected]>: > Greg, > > I've been moving into my new home these past few days. Finding a new place > took far longer than I anticipated. I'll take a look at the Bluetooth > connection in v1.81 when I find my Retro computer boxes. I suspect that your > problem has something to do with Android 9 and above not playing nice with > mComm. Google made some big changes with either version 8 or 9 and I may end > up having to get a newer Android device to test out my code against. > > Kurt > > On Sat, Jan 2, 2021, at 1:17 PM, Greg Swallow wrote: >> All: >> >> Didn't want to get a handful of BlueSMirF Gold boards and put one in each of >> my M100/T102 computers. Picked up this ioGear GBC232A (seller posted it on >> eBay as a GBS301). Anyway, I'm hoping to get it working and connect to my >> motoG6 (Android 9) using mComm. >> >> I've been able to verify connection between an M100/GBC232A and my >> MacbookPro through TERM @ 98N1E. So forgot the device on the MBP and paired >> to motoG6 but mComm v1.81 exits with a message about no COM ports found >> after selecting to connect to the GBC232A from the device list. >> >> Any suggestions? Or, is there an update to mComm? Would need a link as I >> lost whatever link I had to Club100 user files et al. >> >> Thanks, >> >> GregS <>< >
