Closed Bug 1166971 Opened 9 years ago Closed 9 years ago

Klif phone won't connect to WebIDE, adb devices always returns "???????????? no permissions"

Categories

(Firefox OS Graveyard :: Developer Tools, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nefzaoui, Unassigned)

References

Details

As the title says,Tunisia's launched Klif phone's adb devices always returns "???????????? no permissions" and thus, dev tools (WebIDE) can't access the device.
Software version is 2.0
Blocks: klif-phone
Hi Ahmed, thanks for reporting this bug!

Could you please copy/paste the following information into this bug?

1. cat /etc/udev/rules.d/51-android.rules

2. lsusb # when the device is connected
|adb devices| and |adb shell| works for me, but I didn't try the WebIDE.
Flags: needinfo?(nefzaoui)
Anyone else having issues when connecting a Klif to WebIDE? I can't get my hands on one, so I can't try to reproduce.
Hey everyone, 

I've just tried the Klif with WebIDE and it works fine, the device showed in the devices list "FirefoxOS (Orange Klif)" and I tried installing some apps with success.
From comment 4, it sounds like the Klif works in general, so there is probably something specific to Ahmed's setup in comment 0.

Closing for now since we don't have more info to debug further, but please reopen if more details become available!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(nefzaoui)
Apologies for the huge delay.
I just added this file[1] to my rules.d/ directory and now `adb devices` prompts 

List of devices attached 
QKPFBIORK7SKKJLB        device

And WebIDE works.

Thanks all!

[1]: https://raw.githubusercontent.com/M0Rf30/android-udev-rules/master/51-android.rules
Resolution: INCOMPLETE → FIXED
Glad to hear it's working!  We usually reserve FIXED for the case of making code changes to resolve an issue, so I'll set this one as WORKSFORME, since it's working as expected.

In any case, the important thing is that it now works for you. :)
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.