Radek Polak pson...@seznam.cz writes:
On Thursday, May 17, 2012 12:55:13 AM Robin Paulson wrote:
it printed this, i'm not sure what it means:
QDBusObjectPath: invalid path
Method call /-DefaultAdapter() failed:
QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter)
I'm also seeing
On Sunday 10 June 2012 14:23:20 Neil Jerram wrote:
rfkill state:
-8--
root@neo:~# rfkill list
0: GPS: GPS
Soft blocked: no
Hard blocked: no
1: Bluetooth: Bluetooth
Soft blocked: yes
^^ this looks like bluetooth if off. Can you try unblock it? IIRC it
Radek Polak pson...@seznam.cz writes:
On Sunday 10 June 2012 14:23:20 Neil Jerram wrote:
rfkill state:
-8--
root@neo:~# rfkill list
0: GPS: GPS
Soft blocked: no
Hard blocked: no
1: Bluetooth: Bluetooth
Soft blocked: yes
^^ this looks like bluetooth if
On Sunday 10 June 2012 18:25:56 Neil Jerram wrote:
Presumably, then, the right fix for this is either to ensure somehow
that the rfkill block bluetooth happens after QtMoko startup, or to
make QtMoko start up even if bluetooth is off. The latter would be
better, because someone might have
Thats solves my problem too. I have disabled bluetooth (and GSM) in my
GTA02 in init script, left device some time unused (and forgot about
this small change) and then woder why crashes.
Dne 10.6.2012 23:24, Radek Polak napsal(a):
On Sunday 10 June 2012 18:25:56 Neil Jerram wrote:
Radek Polak pson...@seznam.cz writes:
On Thursday, May 17, 2012 12:55:13 AM Robin Paulson wrote:
it printed this, i'm not sure what it means:
QDBusObjectPath: invalid path
Method call /-DefaultAdapter() failed:
QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter)
It looks like
On Monday, June 04, 2012 09:38:17 AM Neil Jerram wrote:
I wonder if it would be a generally useful idea to catch and show qpe's
output in cases like this, and then give the user the choice of
restarting or powering off? I think that might be less alarming that
seeing the UI restarting
On 17 May 2012 18:35, Radek Polak pson...@seznam.cz wrote:
It looks like bluetooth adapter and bluez are not working. You can try:
/etc/init.d/bluetooth stop
or
update-rc.d -f bluetooth remove
First commands stops bluetooth and after that qtmoko will start ok. Second
one disable
On Thursday, May 17, 2012 12:55:13 AM Robin Paulson wrote:
it printed this, i'm not sure what it means:
QDBusObjectPath: invalid path
Method call /-DefaultAdapter() failed:
QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter)
It looks like bluetooth adapter and bluez are not
On Wednesday, May 16, 2012 02:30:36 AM Robin Paulson wrote:
any suggestions what to do? i've checked the connections on the screen
and they are fine. i wonder if it's anything to do with the
calibration of the touchpad? is there anyway to manually edit it, i.e.
a .conf file somewhere?
You
On 16 May 2012 22:28, Radek Polak pson...@seznam.cz wrote:
You can try to start qtmoko from ssh:
ssh root@192.168.0.202
/etc/init.d/qtmoko-neo stop
. /opt/qtmoko/qpe.env
qpe
It should print something useful.
it printed this, i'm not sure what it means:
QDBusObjectPath: invalid path
On Thu, 17 May 2012 10:55:13 +1200
Robin Paulson robin.paul...@gmail.com wrote:
On 16 May 2012 22:28, Radek Polak pson...@seznam.cz wrote:
You can try to start qtmoko from ssh:
ssh root@192.168.0.202
/etc/init.d/qtmoko-neo stop
. /opt/qtmoko/qpe.env
qpe
It should print
hi all,
i broke the screen on my freerunner a while back (although it still
displayed, and the touch part sort of worked), and put a new one in
last week, bought from a seller on ebay.
i booted the freerunner up, and the screen appeared to work fine, boot
text was moving across the screen.
13 matches
Mail list logo
