958859 - [ADB] "adb devices" does not return device after System start

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Binyamin]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Steps to reproduce:

"adb devices" returns attached device just on progress of device start and shutdown (while System black screen).
"adb devices" no more returns the device after the System is fully started and appears Firefox OS UI (after blue screen with Firefox OS logo) - the "List of devices attached" is empty and for example "adb reboot bootloader" returns "error: device not found".

Tested on Win7 64bit, Geeksphone Peak with recent Firefox Nightly.
Fallowed http://downloads.geeksphone.com/drivers/Manual_flash_geeksphone-eng.txt steps on driver and Nightly build install http://downloads.geeksphone.com/peak/master/latest_master.html

Comment 1

[Binyamin]

Even FASTBOOT MODE does not return adb devices.

Comment 2

[Binoy Balu]

Attachment: bugfx958859.txt

this is to start the adb server . would work if we place it in code as in starting .

Comment 3

[Binyamin]

(In reply to Binoy Balu from comment #2)
> Created attachment 8358883 [details] [diff] [review]
> bugfx958859.txt
> 
> this is to start the adb server . would work if we place it in code as in
> starting .

When System is already started (fully loaded), this still does not return the device ("List of devices attached" will be empty):
adb kill-server
adb start-server
adb devices

Comment 4

[Théo Chevalier]

Remote debug settings in Settings has changed. Flashing the latest build then turning the setting from "Disabled" to "ADB and Devtools" fixes this bug.

Comment 5

[Binyamin]

(In reply to Théo Chevalier [:tchevalier] from comment #4)
> Remote debug settings in Settings has changed. Flashing the latest build
> then turning the setting from "Disabled" to "ADB and Devtools" fixes this
> bug.

Did you tested on Geeksphone Peak/Keon with Firefox OS Nightly build?

I just tried your advice, and it did not fix me anything:

1. step:
Settings > Device information > More Information > 
Developer > Remote debugging > ADV and Devtools

2. step:
Restart device

3. step:
adb devices

or:

adb kill-server
adb start-server
adb devices


Result: "List of devices attached" is empty.
Expected result: "List of devices attached" must return the name of attached device.

Comment 6

[Théo Chevalier]

Yes, I tried on Ubuntu with both Keon and Peak, with Nightly builds 20140110 and ADB 1.0.31.
I did nothing more than your steps.

Did you make sure the screen was unlocked before running |adb devices| ?

Comment 7

[Binyamin]

(In reply to Théo Chevalier [:tchevalier] from comment #6)
> Yes, I tried on Ubuntu with both Keon and Peak, with Nightly builds 20140110
> and ADB 1.0.31.
> I did nothing more than your steps.
> 
> Did you make sure the screen was unlocked before running |adb devices| ?

I tried on other USB plug and it identifies now the device. Thanks!

Comment 8

[Binyamin]

Geeksphone Peak device is hanged on master build 05/13/2014 and there in no way to read the device with ADB, "adb devices" return empty line. I tried to restart, enable/disable Remote debugging in Settings, but no change.

Comment 9

[Meghraj Suthar (:romec)]

Hello, I found this bug is same related to my problem so i am gonna comment here,

I tried with my keon advice, after flashing FxOS2.0 but when i run the command in terminal [Ubuntu],

adb devices it shows:

List of Devices attached
???????????????   no permissions

But i have enabled all the services one by one, "Adb Only" and " Adb Devtools".
(Make sure i am getting this issue after updated to FxOS2.0, before that i got default Fx1.4 [may be] at that time i did it and it worked. But not working now)


Thanks!
Meghraj Suthar

Comment 10

[Binyamin]

All Geeksphone phones are manufacture broken (USB, GPS and GSM are few of them), unfortunately Geeksphone will not fix it and will not compensate or credit anyone. I posted earlier this issues in Geeksphone forum, but Geeksphone instead of solving it, blocked my access and removed all those posts. It is a shame that Mozilla still cooperates with them.

Comment 11

[BMO Automation]

Firefox OS is not being worked on