Nvidia Shield K1 not working with HarkRF device

Hello

I am trying to connect HackRF to my K1 and run HackRF app from App Store. After I try to connect I get general error message stating “It failed to connect”. So I looked at logcat and I see this

01-10 22:08:08.218 348 831 E nvaudio_hw: nvaudio_out_set_parameters: Could not find the usecase (0) in the list
01-10 22:08:08.222 24769 24769 I hackrf_android: initHackrf: Found 2 USB devices.
01-10 22:08:08.222 24769 24769 D hackrf_android: initHackrf: deviceList: vendor=6408 product=550
01-10 22:08:08.222 24769 24769 D hackrf_android: initHackrf: deviceList: vendor=7504 product=24713
01-10 22:08:08.222 24769 24769 I hackrf_android: initHackrf: Found HackRF One at /dev/bus/usb/002/005
01-10 22:08:08.227 800 1361 I ActivityManager: START u0 {flg=0x10000000 cmp=com.android.systemui/.usb.UsbPermissionActivity (has extras)} from uid 1000 on display 0
01-10 22:08:08.258 24769 24769 D hackrf_android: Permission request for device /dev/bus/usb/002/005 was send. waiting…
01-10 22:08:08.260 1313 1313 D ShieldTech_Services: Starting service
01-10 22:08:08.343 800 809 I art : Background partial concurrent mark sweep GC freed 8640(530KB) AllocSpace objects, 2(40KB) LOS objects, 15% free, 22MB/26MB, paused 6.982ms total 102.944ms
01-10 22:08:08.346 1313 1313 D RSMouse : mFeatureEnabled=true mPackageEnabled=true
01-10 22:08:08.369 800 818 I ActivityManager: Displayed com.android.systemui/.usb.UsbPermissionActivity: +105ms
01-10 22:08:09.891 800 920 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@a13de0c attribute=null, token = android.os.BinderProxy@174522
01-10 22:08:09.893 1313 1313 D RSMouse : mFeatureEnabled=true mPackageEnabled=true
01-10 22:08:09.896 900 1480 D OpenGLRenderer: endAllStagingAnimators on 0x9be90480 (RippleDrawable) with handle 0x9bfe4420
01-10 22:08:09.913 24769 24769 D hackrf_android: initHackrf: Permission granted for device /dev/bus/usb/002/005
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: create Hackrf instance from /dev/bus/usb/002/005. Vendor ID: 7504 Product ID: 24713
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: device protocol: 0
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: device class: 0 subclass: 0
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: interface count: 2
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: [interface 0] interface protocol: 255 subclass: 255
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: [interface 0] interface class: 255
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: [interface 0] endpoint count: 2
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: [endpoint 0 (IN)] address: 129 attributes: 2 direction: 128 max_packet_size: 512
01-10 22:08:09.913 24769 24769 I hackrf_android: constructor: [endpoint 1 (OUT)] address: 2 attributes: 2 direction: 0 max_packet_size: 512
01-10 22:08:09.959 800 809 I art : Background partial concurrent mark sweep GC freed 2310(108KB) AllocSpace objects, 0(0B) LOS objects, 15% free, 22MB/26MB, paused 1.584ms total 101.948ms
01-10 22:08:10.027 24769 24769 E hackrf_android: constructor: Couldn’t open HackRF USB Device: openDevice() returned null!
01-10 22:08:10.027 24769 24769 E hackrf_android: constructor: Couldn’t open HackRF USB Device: Couldn’t open HackRF USB Device! (device is gone)
01-10 22:08:10.027 24769 24769 E hackrf_android: initHackrf: Couldn’t open device /dev/bus/usb/002/005
01-10 22:08:10.036 24769 24769 E HackRFSource: Error while opening HackRF: Couldn’t open device /dev/bus/usb/002/005
01-10 22:08:10.139 800 888 D UsbHostManager: Added device UsbDevice[mName=/dev/bus/usb/002/006,mVendorId=7504,mProductId=24713,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Great Scott Gadgets,mProductName=HackRF One,mVersion=2.0,mSerialNumber=0000000000000000406464c8238a2c4b,mConfigurations=[
01-10 22:08:10.139 800 888 D UsbHostManager: UsbConfiguration[mId=1,mName=Transceiver,mAttributes=128,mMaxPower=250,mInterfaces=[
01-10 22:08:10.139 800 888 D UsbHostManager: UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=255,mSubclass=255,mProtocol=255,mEndpoints=[
01-10 22:08:10.139 800 888 D UsbHostManager: UsbEndpoint[mAddress=129,mAttributes=2,mMaxPacketSize=512,mInterval=0]
01-10 22:08:10.139 800 888 D UsbHostManager: UsbEndpoint[mAddress=2,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]
01-10 22:08:10.139 800 888 D UsbHostManager: UsbConfiguration[mId=2,mName=CPLD update,mAttributes=128,mMaxPower=250,mInterfaces=[
01-10 22:08:10.139 800 888 D UsbHostManager: UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=255,mSubclass=255,mProtocol=255,mEndpoints=[
01-10 22:08:10.139 800 888 D UsbHostManager: UsbEndpoint[mAddress=129,mAttributes=2,mMaxPacketSize=512,mInterval=0]
01-10 22:08:10.139 800 888 D UsbHostManager: UsbEndpoint[mAddress=2,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]]
01-10 22:08:10.139 800 888 W UsbSettingsManager: no meta-data for ResolveInfo{e54b3c2 com.estrongs.android.pop.pro/com.estrongs.android.pop.view.FileExplorerActivity m=0x108000}
01-10 22:08:10.150 800 888 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:765 com.android.server.usb.UsbSettingsManager.deviceAttached:742 com.android.server.usb.UsbHostManager.endUsbDeviceAdded:225 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.-wrap0:-1

In there you see one line that looking into project on gitHub It is coming from this line

https://github.com/demantz/hackrf_android/blob/master/app/src/main/java/com/mantz_it/hackrf_android/Hackrf.java#L291

I see that past Nvidia K1 firmware updates addressed some USB issues but not sure which.

Just so you know if I plug USB pen drive I see working.

Anyone here has HackRF? and got it working? If Nvidia dens are checking this out could you please let me know if you need any additional information?

Looks like we have an update coming out next week that might fix this issue, although it is a longshot. Can you let me know sometime in the next few weeks if the issue has been resolved?

If not, you may want to trying contacting our team here: www.nvidia.com/support

Let me know if you have any further questions.

I did send email. Will wait for dev answer :) Thank you

I just want to report that I upgraded to 7.0 that was released yesterday and same issue. This was not addressed yet. Were you referring to 7.0 update? Or was there different update you were referring comping up?

Also I did send email to above link and so far not one responded. So I am not sure if my errors writing here are going anywhere :)

Anyone has issues with USB?

That may have been the update. I’d go ahead and ping them again with a follow-up email if you don’t get a response by early next week. They get a lot of requests, so just add a reply to your original email if you can.

If there is anything you need from me logs or what ever let me know.

Any news about this item? I reported this directly to Nvidia for about year since I got this unit and noticed few updates stating OTG USB fixes. But still in my case it is not working. Is this fixable at all? I am trying to reach all channels to get this resolved and always I do end in dead end :) If this is not fixable by Nvidia I would like to know to move to different unit. I think year waiting is plenty of time…