ANDROID APP SEARCHING Bluetooth Ever and ever!

I’ve had it up to here ! It took me two days to connect to the application and I even bought a second-hand Android tablet.
The Android app and Bluetooth synchronization only worked for 5 days and today I have been trying to connect again for 3 hours. I followed all the procedures and reinstalled the application. It’s not working and I’m starting to get angry.

You should smash it and then throw it out the window.

Yes i will return the nano Cortex at shop Thomman EU RMA this day.

Very disapointed with the bluetooth app Android .

Under the bluetooth parameters the nano definitely no longer appears at long.

I tried with 4 different devices … :face_with_symbols_over_mouth:

I’d recommend to email support@neuraldsp.com so they can log your issue and hopefully provide resolution.

1 Like

Of course, I have already contacted the support service but the response from the manual did not resolve my problem at all.

I also reset the nano for a final test then sent the device to money back to the store today.

So very very disapointed…

might just be a faulty unit then. no worries, most of them seem to work

yes I’m sure of it because the reputation acquired by the quad Cortex is well established. I was just tense to feel the potential of the nano Cortex machine without being able to take advantage of it.

1 Like

i just mean don’t be discouraged :slight_smile:

same here, what next , just return it, only?

Anyone else having problems, definitely try to test with a new android or iOS device as older phones and tablets with bluetooth version 4 don’t seem to work. Apparently the Nano requires bluetooth version 5 or greater. I don’t believe Neural has confirmed this, but they really should if they haven’t already.

1 Like

My Bluetooth connection is hit and miss on my Samsung S23. Sometimes connects immediately. Sometimes need to use the Nano buttons to connect. Sometimes nothing works, I restart the phone, and connection works again.

2 Likes

I’ve experienced the same issue the other day on the iPhone iOS, what helped me was to just restart both devices the NC and the iPhone. Hope this helps someone else at least.

1 Like