Registered Member
|
The installation of Plasma Mobile onto my LG Nexus 5X "bullhead" handset went fine, and I now have Plasma Mobile running on the device.
But in trying to follow the General Tips I've found that `adb` is not able to see the device. Has anyone else had this problem, and is there a way to solve it? The `adb` utility worked fine while Android 7 was running on the device, and I have a udev ruleset to grant access permission to the device in my Linux desktop. But if I run `adb devices` while Plasma Mobile is running, the output is simply:
followed by an empty line. And attempting to run `adb root` returns:
In case of it's relevant, if I go to Settings/"Developer Settings", the "Allow remote SSH access" box is empty/unticked, and if I tap on it the box lights up briefly and then empties again, so it seems that this option is not permitted. The Plasma Mobile build number appears to be `20170703-141145` according to the pm-flashtool cache directory. I'm hoping that someone has a solution for this problem, as I'd like to be able to use adb to remote control the device so that I can add a Wi-Fi connection to Plasma Mobile. (I did attempt to simply run `wifi-setup` from Konsole directly on the handset, but it did not have any effect.) |
Registered Member
|
|
Registered Member
|
I experienced the same thing (nexus 5 with plasma freshly installed connected via USB cable) and saw that launching the adb daemon manually from the device activates the communication with PC.
On your device, type in a terminal:
and then retry the adb command on your pc. In my case, I then saw the device and could go on. Hope this helps. |
Registered Member
|
Hi linuxfandummy,
I opened Terminal and typed adbd. The output was
and then it hangs. While it was hanging there, I tried 'adb devices' from my laptop but the output was the same as NexusSleuth's. What's the difference between Terminal and Konsole, by the way? Thanks in advance. |
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]