- #BLUESTACKS 2 ONE TIME SETUP INSTALL#
- #BLUESTACKS 2 ONE TIME SETUP UPDATE#
- #BLUESTACKS 2 ONE TIME SETUP WINDOWS 10#
- #BLUESTACKS 2 ONE TIME SETUP ANDROID#
Will this process work for everyone? Of course not. I closed out BlueStacks, unplugged the charge 4 from its cradle and determined that enough was enough and that I would return it to Best Buy the next day.Īnd then…the little sound the next day coming from somewhere on my desktop.
#BLUESTACKS 2 ONE TIME SETUP ANDROID#
I checked to make sure that the charge 4 appeared in the list of devices on the android version of the fitbit application. Next, I set up the device on a Windows phone as I had numerous times where the charge 4 connected with Bluetooth successfully but, nonetheless, failed to download the required app it craved (reaching this point on a windows phone was not unusual). I opened the android fitbit app and tried to setup the charge 4, but it balked because it couldn’t connect with bluetooth. #BLUESTACKS 2 ONE TIME SETUP WINDOWS 10#
I downloaded the android version of the fitbit app on my Windows 10 computer using Blue Stacks. I can’t tell you exactly what I did to make it work, because I literally tried everything multiple times, except for this sequence: To my amazement, it had somehow managed to download whatever it had been looking for and resurrected itself from brick status to fitbit buddy, without my intercession, as though I were the problem all along. I never give up, but I gave up.Īnd then…The next morning I heard a little dull, buzzing sound coming from somewhere on my desk and discovered that it emanated from the charge 4/brick. I escaped out of BlueStacks and took the charge 4 out of its cradle and let it lie there like the skulking failure it was. I wasn’t able to setup a device in the emulator because BlueStacks doesn’t support Bluetooth, however, I did, for the billionth time, setup the charge 4 on my wife’s Windows phone, where it synced just fine but still wasn’t able to escape the endless setup mode loop with the scrolled message indicating that an application had to be downloaded. Using BlueStacks, an android emulator for Windows 10, I downloaded an android version of the Fitbit application. So, Saturday, after deciding that the watch had somehow bricked itself, I tried one last possibility. I simply could not reach a stage where the charge 4 would download the app and escape that endless loop. To reach this point, the device would indeed finally sync with Bluetooth on my wife’s Windows phone but near the end of the setup process it also indicated that selection of a dominant wrist was not supported (this was indicative of a failed setup procedure).Īnyway, I tried and re-tried every plausible suggestion on the various fitbit forums and everywhere else and discovered that none of them worked for me. 
I bought a Fitbit Charge 4 for my wife on a Friday and spent some of that day and way too much of Saturday trying to get it to move past the setup mode where a message scrolls on the tiny screen demanding that it be allowed to download some app. It seemed to be giving it a rest for a few hours and then trying again. I don't know what I did to solve the problem though. It now works after about 8 hours of screwing around and i don't need a replacement.
#BLUESTACKS 2 ONE TIME SETUP INSTALL#
It took me longer to re install my wife's Fitbit back onto her her phone and thus save my life. I gave up with the cell phone and did the whole setup on the PC in about a minute. I setup withe number code and ignored the update.
#BLUESTACKS 2 ONE TIME SETUP UPDATE#
I got the code and connected to the phone, it then tried to do an update and crashed. Saturday morning (today) I thought one last try. Their tech guy made me use my wife's Cell phone to do the setup, 2 hours with him, weggnored the update had the code setup at least three times and still only got their logo. I spent around 2 + 1 hours screwing around with it on Thursday, when I got it.Īnother 3 hours including 2 with their tech support, who told me the same story "it won't work on Windows 10" eventually got a Warranty replacement Certificate sent to me.
0 kommentar(er)
