I bought a Nano Cortex a few days ago, but the Bluetooth connection dropped while I was recording in Logic. The app was still open on my iPhone at the time. I tried restarting the app and re-pairing from the device, but it wouldn’t reconnect. I finally got it working again only after power cycling the unit.
Is this normal? If so, I’d like to suggest developing a PC app that works via USB cable for a more stable connection.
It looks like others on the gear page are having the same issue. Since they are saying it started after the new NanOS update, hopefully it gets fixed in the next update.
After reading your post, it looks like I’m experiencing the same issue. I’m also using an iPhone 16 with the latest version of iOS, and the Nano firmware and Nano app are both up to date.
I experienced the same behavior: after reinstating pairing on the pedal, the pedal thinks the connection has started (the blue ring “searching” circle goes away).
Unfortunately still no change in tone from support nor confirmation they cannot reproduce the issue themselves.
they asked me to send in my device on my cost and only if still under warranty.
please if anyone is also experiencing this issue reach out to support with your experience so we can have this fixed.
This was not an issue before they removed the internet requirement for the app.
to reproduce just connect your phone to the nano cortex and leave it connected with the screen on the preset blocks while you play. Eventually the connection will drop and not let you reconnect without resetting the nano cortex power.
Wonder if there is some power setting that is disconnecting the BT? I haven’t been able to duplicate the issues using both iPad Pro and iPhone 14 Pro. I hope support is able to determine the source of the disconnects.
I have an iPhone 17 Pro Max and I’m experiencing the same problem: Bluetooth disconnects and the blue indicator spins. I have to restart the unit to connect to my iPhone. I also remember that before, it would sync automatically just by opening Cortex Control and going to Nano; now I have to press Exit and Capture every time.
Thanks for your efforts. The same symptoms occurred both when powering the device via the MacBook Pro’s USB-C and when using the Kemper Player’s 9.0V DC / 2.5A PSU. In both cases, the Nano Cortex was connected to the MacBook via USB-C and being used as an interface. These issues typically show up anywhere between 10 minutes and an hour into use. I have sent an email to support with these details.
Updated information: If I connect the Nano Cortex to an external 9V PSU and don’t use it as an audio interface, meaning there’s no USB cable connected, the Bluetooth connection doesn’t seem to drop.
Additional info: After staying connected with the screen on for over two hours, the Bluetooth connection dropped. However, after 2–3 attempts, I was able to pair without rebooting the Nano Cortex.
I lose BT connectivity occasionally. I turned off Bluetooth on my DAW computer and moved the Nano. I wonder if it’s too close to that computer and the BT transmitter caused the iPhone 16 to lose the connection. It’s all 2.4 ghz radio frequency RF. I just don’t want an offending device between the Nano and the iPhone so the Nano RF gets jammed by the computer RF by overpowering or interfering with it. Time will tell. I have a wireless 2.4 ghz keyboard/mouse combo also.
I agree with your opinion. In addition to a desktop program, a USB-connected mobile app is also necessary. After updating my iPhone 16 Pro to the latest iOS version and also updating my MacBook Pro’s operating system to the latest version, I haven’t experienced the issue yet. However, since each person’s runtime environment is different, a USB connection is definitely required.
I’m having the exact same issues since July ‘25 when i bought the unit. In November I sent the unit back to Neural for inspection, but they found nothing wrong with it.
The NC loses connection to my phone/Ipad after 15-30 minutes, even when using the app. After that it does not connect at all to the phone (capture + exit doesn’t help), but it needs to be rebooted. After reboot it usually connects, but not always. Second/third reboot helps, but then again it will cut the connection after a while.
When the app/phone and NC are connected everything seems to work fine.
NC Factory reset: done
Phone booted: done
Ipad booted: done
App uninstalled/installed: done
Power: USB C adapter (meeting specs, tried four different adapters and three different cables) and 9V 660mA adapter.
Any hot fix/firmware updates would officially be announced here and via NDSP’s normal channels. Again, trying not to re-hash but support is definitely aware of this thread and is preferring anyone experiencing issues with BT disconnects to continue to email support@neuraldsp.com. So if you guys have issues, email support so that they can log each issue and hopefully figure out the resolution.
That being said, I tested multiple scenarios yesterday with my Nano using my iPad Pro 12.9” 4th gen, iPhone 14 Pro and an older iPhone all running the most current updates and app. My NC is updated with the most current firmware etc.
In summary, my BT connection remained solid with no drops for the almost 8hrs that I played while testing different scenarios. Note that I also have very few 2.4 GHz devices and mostly use 5GHz as 2.4GHz devices can sometimes interfere with BT connections. The scenarios I tested included enabling/disabling the cell service, varying the distance between my BT device and NC, resetting my network settings, enabling/disabling USB, disconnecting/reconnecting other BT devices and factory resetting the NC etc. I just can’t seem to duplicate the BT connection drops.
During some of my research I have read that apps with constant BT scanning permissions (e.g., Amazon Alexa, Tile, fitness trackers) can sometimes hijack and or drop connections. Maybe something you guys can check/test on your end. It might be one common denominator or multiple variables but we don’t know as it obviously doesn’t impact everyone therefore its vital to keep hammering away with support to get it resolved.