ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #12379
Re: [BQ] keyboard doesn't show up
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 reload this; I'm not certain if permissions are setup correctly on
14.04 either, so you might need to run "sudo adb start-server".
The crash file (if there is one) and the system info will still be the
same after reboot, however I would be very interested to know if the
service is running prior to rebooting if possible.
Thanks,
Mike.
On Thu, 2015-04-23 at 11:48 +0000, Alberto Pagliarini wrote:
> 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 informations for you?
>
>
> alb
>
> Il giorno gio 23 apr 2015 alle ore 13:27 Mike Sheldon
> <mike@xxxxxxxxxxxxx> ha scritto:
> 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" (the number may differ),
> if there
> is could you send it to me?
>
> To restart the keyboard manually from the command line you
> can run
> "restart maliit-server".
>
> Thanks!
> Mike.
>
> On Thu, 2015-04-23 at 11:16 +0000, Alberto Pagliarini wrote:
> > Hi all,
> >
> >
> > I left my phone in charge all night and this morning I'm
> annoyed to
> > this issue. When I tap on an input field it get rightly the
> focus but
> > the keyboard doesn't show up.
> >
> >
> > I guess that rebooting the device solves the issue but
> before that I
> > want to know if I can help developers opening a bug with
> relevant
> > logs. So what logs should I attach?
> >
> >
> > Moreover, is there a way to restore keyboard without
> rebooting? Like
> > to launch some commands from shell?
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References