ADB suddenly doesn't detect my device anymore

Question

[update 1] During the below attempts to make this thing work, I rebooted several times. However this morning I turn on my computer and now the device is listed... However I will keep my question open for a few days to see if this odd behavior comes back.[/update 1]

adb under Arch Linux (32bits) suddenly stopped reporting my phone, which it usually does. I tried all the following commands both as sudo and normal user, with the same lack of result.

[antoine@amadeus /home/antoine/]$ sudo gvim /etc/udev/rules.d/51-android.rules  

In which I wrote:

SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0ccf", MODE="0666", OWNER="antoine"

Then I did:

[antoine@amadeus /home/antoine/]$ sudo udevadm control --reload-rules

The device was there:

[antoine@amadeus /home/antoine/]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 012: ID 0bb4:0ccf High Tech Computer Corp. 
Bus 006 Device 002: ID 046d:0a15 Logitech, Inc. 
Bus 006 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 006 Device 004: ID 046d:c52f Logitech, Inc. Wireless Mouse M305

So I killed the adb server

[antoine@amadeus /home/antoine/]$ sudo adb kill-server
[antoine@amadeus /home/antoine/]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Yet it didn't work:

[antoine@amadeus /home/antoine/]$ sudo adb devices
List of devices attached 

[antoine@amadeus /home/antoine/]$ 

Then I tried to update adb with :

[antoine@amadeus /home/antoine/]$ sudo android update adb
adb has been updated. You must restart adb with the following commands
    adb kill-server
    adb start-server

Then modified the adb_usb.ini file (both in root and in ~):

[antoine@amadeus /home/antoine/]$ sudo gvim /root/.android/adb_usb.ini 

I wrote:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0bb4

Then :

[antoine@amadeus /home/antoine/]$ sudo adb kill-server
[antoine@amadeus /home/antoine/]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[antoine@amadeus /home/antoine/]$ sudo adb devices
List of devices attached 

[antoine@amadeus /home/antoine/]$

This whole thing was working just fine yesterday and the day before and so on. I have not updated my system nor anything since then. I am puzzled.

Answer 1

OK, I had this exact same problem with a Samsung Galaxy Mini, and my setup is an Ubuntu box running oneiric.

I had not touched the laptop before this stopped working so I was pretty sure the configuration on the laptop was sound. The only thing I've done (before this started happening) was install 2 apps from Google Play on the device. A Messenger Client and some other app which I really do not recall the name nor what it was for.

For some reason, which I have not yet figured out, my laptop stopped being able to detect the galaxy mini for debugging purposes. I tried all tricks described here (several changes to udev confs, checking adb confs , killing/stopping/restarting everything with different orders) and only one thing got the device to get detected again and it was :

Reseting the phone.

Not elegant but it was the only thing that got my galaxy mini to get detected again by ADB. Hope this helps.