Thats a relief for me as I lost my phone and was worried someone might adb into
it and get my data.
I know its probably still possible to access some stuff via PC but at least not
over adb :)
Sorry for the OT.
Regards,
Simeon
Am 23.04.2015 um 14:23 schrieb Mike Sheldon:
One additional thing,
Hi Alberto,
That's very interesting that the keyboard is running and hasn't
crashed, but still isn't displaying. Have you ever paired with a
bluetooth keyboard?
There should be some log files in /home/phablet/.cache/upstart/ with
names starting maliit-server.log, could you email them to me?
-phone] [BQ] keyboard doesn't show up
To: Alberto Pagliarini bat...@gmail.com
Cc: ubuntu-phone@lists.launchpad.net ubuntu-phone@lists.launchpad.net
Date: Thursday, 23 April, 2015, 12:27
Hi Alberto,
Thanks for letting us know, there's a couple of things you
could do to
help:
1) Run
One additional thing, make sure you unlock your phone (i.e. enter your
pin on the lock screen), prior to accessing it over adb, for security
reasons we prevent adb accessing the phone while its still locked.
Cheers,
Mike.
On Thu, 2015-04-23 at 12:56 +0100, Mike Sheldon wrote:
Hi Alberto,
hi,
Am Donnerstag, den 23.04.2015, 12:56 +0100 schrieb Mike Sheldon:
Hi Alberto,
If you're using Ubuntu 14.04 you might need to manually let adb know
about the BQ vendor ID, which can be done by creating a file called:
~/.android/adb_usb.ini
better use the android-tools-adb package
Hi,
I'm on Ubuntu 14.10 and I have already attached the device in the past to
use tethering.
Now I have upgraded adb to ppa suggested from Oliver but it's not revelead
using adb devices.
I also performed adb kill-server and adb start-server but nothing new
happens.
I'm stucked :(
I can give it
Hi Mike,
I'm having trouble to run commands. I connected the phone via usb (dev mode
activate), I see the device mounted but I can't reach it from adb. adb
devices return an empty list :( Connected another android phone it is
detected. Some suggestions?
If I reboot the BQ will I lose important
Hi Alberto,
Thanks for letting us know, there's a couple of things you could do to
help:
1) Run status maliit-server
And let us know what the output is
2) Run system-image-cli --info
And paste the output
3) See if there's a file in /var/crash called
_usr_bin_maliit-server.32011.crash
Hi Alberto,
If you're using Ubuntu 14.04 you might need to manually let adb know
about the BQ vendor ID, which can be done by creating a file called:
~/.android/adb_usb.ini
On your desktop, and adding the line:
0x2a47
I think you might need to run adb kill-server and adb start-server
to
9 matches
Mail list logo
