Hi all,
I have an elocity A7 Tablet running 2.2 Dexters ElocityA7 Modv1.2, full root access.
I managed to get usb ADB functionality working correctly after forcing the usb mode to client - i can run shell commands etc...
When I first attempted to launch applications from Eclipse I was getting messages stating /sbin/sh : am: not found. I finally managed to get that corrected by editing the am/pm files and creating the correct references with vi.
So now the applications finally install from Eclipse - HOWEVER - they do not launch when I attempt to run or debug. The Apps do get installed correctly, it just appears it Eclipse can't start the activity.
-USB debugging is enabled
Console output when I attempt to run:
==============================================
Code:
[2011-09-25 19:40:58 - test] Android Launch!
2011-09-25 19:40:58 - test] adb is running normally.
[2011-09-25 19:40:58 - test] Performing com.test.TestActivity activity launch
[2011-09-25 19:40:58 - test] Automatic Target Mode: using device '028041454220f4d7'
[2011-09-25 19:40:59 - test] Application already deployed. No need to reinstall.
[2011-09-25 19:40:59 - test] Starting activity com.test.TestActivity on device 028041454220f4d7
At this point nothing further happens - The logcat below just displays the debugger detaches but I don't know exactly why.
LogCat Output when I attempt to run:
==============================================
Code:
09-25 19:40:56.242: DEBUG/AndroidRuntime(12380): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
09-25 19:40:56.242: DEBUG/AndroidRuntime(12380): CheckJNI is OFF
09-25 19:40:56.242: DEBUG/dalvikvm(12380): creating instr width table
09-25 19:40:56.252: DEBUG/dalvikvm(12380): Unable to stat classpath element '/system/framework/com.nvidia.graphics.jar'
09-25 19:40:56.272: DEBUG/AndroidRuntime(12380): --- registering native functions ---
09-25 19:40:56.322: ERROR/BluetoothHidDeviceService.cpp(12380): register_android_server_BluetoothHidDeviceService: Registering HIDD Native Methods
09-25 19:40:56.402: DEBUG/AndroidRuntime(12380): Shutting down VM
09-25 19:40:56.402: DEBUG/dalvikvm(12380): Debugger has detached; object registry had 1 entries
09-25 19:40:56.412: INFO/AndroidRuntime(12380): NOTE: attach of thread 'Binder Thread #3' failed
09-25 19:40:56.592: DEBUG/dalvikvm(1331): GC_EXPLICIT freed 1088 objects / 60016 bytes in 35ms
Grateful if anyone has any ideas or can point me in a direction to determine what the cause may be? I know eclipse is configured correctly as I can launch and debug on my Sony Arc 2.3.3 - I think this might be related to a setting on the A7 system
I've narrowed it down to being a problem with my 'am' command - it's not actually doing anything. Anyone know the proper setup for the am command?
Currently this is what I have:
/sbin/am
--EMPTY-- I think this is the problem. If i delete this file however the am command is not found. Do i need to point this somewhere?
/system/bin/am
# Script to start "am" on the device, which has a very rudimentary
# shell.
#
#!/system/bin/sh
base=/system
export CLASSPATH=$base/framework/am.jar
exec app_process $base/bin com.android.commands.am.Am "[email protected]"
Wow as if - problem solved.
#!/system/bin/sh
Needs to be the FIRST line in the file.
Related
Hi all! I've a linux machine.
So this is its boot text:
Code:
#FIRST FOLDER:
Loading, please wait...
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...
#SECOND FOLDER:
done.
Setting parameters of disc: (none).
Setting preliminary keymap...done.
Activating swap...done.
Checking root file system...fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 163709/15171584 files, 2893294/60671488 blocks
done.
Cleaning up ifupdown...
Loading kernel modules...done.
Setting aup networking...
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
done.
Mounting local filesystems...done.
Activating swapfile swap...done.
Cleaning up temporary files...
Configuring network interfaces...done.
Setting kernel variables...done.
Starting portmap daemon...
Starting NFS common utilities: statd.
Cleaning up temporary files...
Setting up ALSA...done.
Setting console screen modes.
Skipping font and keymap setup (handled by console-setup).
Setting up console font and keymap...done.
Loading IPsec SA/SP database:
- /etc/ipsec-tools.conf
done.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Starting NFS common utilities: statd.
Starting portmap daemon...Already running...
Starting enhanced syslogd: rsyslogd.
Starting deferred execution scheduler: atd.
Starting ACPI services...
Starting anmc(h)ronistic cron: anacron.
Starting system message bus: dbusUnknown username "nm-openconnect" in message bus configuration file
Starting network connection manager: NetworkManager.
Starting virtual private network daemon:.
Starting GNOME Display Manager: gdm3.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting bluetooth: bluetoothd
_
I wonder if someone can help me, translating this text like it would be and android boot... Please! Help me!
its like the post from windows
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!
Greetings-
I am trying to run a sample app on my new Note 3. I see the device with adb. I have enclosed a copy of log cat. I get the following three errors in the eclipse console:
[2013-12-18 13:02:55 - NFCMediaShare] Dx
trouble writing output: already prepared
[2013-12-18 13:02:56 - Dex Loader] Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
[2013-12-18 13:02:56 - NFCMediaShare] Conversion to Dalvik format failed: Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
Sean
Hi friends ,
I just cannot get rid of the issue with the 8 things I tried (see below). I need your help pls, it has taken me alot of time and still unsolve.
I am running on window7, 64bits. I am building the "hello world" program and follow the instruction from Andriod developer website. At first, everything went well including the installation. I even manage to run the program on my Samsung S5. However, in a while, I notice something is wrong after I edited the code, so I delete and re-install the SDK and ADT package, objective is to bring the code back to the same factory state. I had tried installing both version of 32bits and 64bits Eclipse package but encounter the following problem when i click RUN as Android application:
******************** Return the following txt: ************************
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at 'D:\ADT\sdk\platform-tools\adb.exe' and can be executed.
**********************************************************************
I did the following troubleshooting:
1) Restart the computer and my phone (samsung S5)
2) Check that there is a connection icon on my PC (USB connected between phone and PC)
3) Update adb in the SDK using the SDK manager
4) Make sure i go to the "help-->Install new software" in the Eclipse and key in the dl-ssl weblink every time i re-install the Elipsce package.
5) Make sure I click "help-->check for update" in the Eclipse every time i re-install the Elipsce package.
6) Checked that I am the adminstrator of my PC
7) Run command at command prompt. I did the follwoing steps:
a. Close the Eclipse if running
b. Go to the Android SDK platform-tools directory in Command Prompt
c. type adb kill-server
************************* Return the following txt ************************
* server not running *
--> adb server is out of date. killing...
ADB server didn't ACK
* fail to start daemon *
**********************************************************************
d.then type adb start-server
Return the same txt as above.
8) I suspect some other process is occupying the port 5037 which the adb access. So I attempt to find the PID (process id) of the process which occupied the port 5037 by giving the command "D:\Android\sdk\platform-tools>netstat -aon|findstr 5037"
************************ Return the following txt *****************************
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 3640
TCP 127.0.0.1:5037 127.0.0.1:50506 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50507 TIME_WAIT 0
**********************************************************************
Then I go to PC Task Manager, but there is no PID with 3640.
I also type at command prompt the below:
tasklist /fi "pid eq m3640
************************* Return the following txt ************************
No task are running which match the specified criteria
**********************************************************************
Seems that the adb is not responding to any re-installation, or restarting of PC and device. The task manager shows PID 3640 but couldn't see any process related to it.
I am a electronics engineer and much a novice in this field of computer.
pls help
Hi
I'm trying to run pidgin in ubuntu touch which is installed on Nexus 5.
I did try to run it in libertine container, however it fails with the follwoing error.
Code:
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Failed to connect to Mir: Failed to connect: not accepted by server
(EE)
I have also tried to run it without the container using the following desktop file
Code:
[Desktop Entry]
Name=Pidgin Internet Messenger
GenericName=Internet Messenger
Comment=Chat over IM. Supports AIM, Google Talk, Jabber/XMPP, MSN, Yahoo and more
Exec=pidgin
Icon=pidgin
StartupNotify=true
Terminal=false
Type=Application
Categories=Network;InstantMessaging;
X-MessagingMenu-UsesChatSection=true
X-Ubuntu-Touch=true
X-Ubuntu-Gettext-Domain=pidgin
X-Ubuntu-XMir-Enable=true
To run pidgin I am using the following script, launching it from phone's command line
Code:
#!/bin/bash
DISP=:1
Xmir :1 -mirSocket /var/run/mir_socket --desktop_file_hint=/home/phablet/pidgin.desktop -debug &
sleep 0.5;
DISPLAY=:1 pidgin &
However, Xmir failed with the following error.
Code:
ARM architecture: Defaulting to software mode because glamor is not stable
XMir initialized with 2 visuals:
Visual id 0x28: ff ff00 ff0000, 24 planes
Visual id 0x29: ff ff00 ff0000, 24 planes
Realize ROOT window 0xb8a6d530 id=0xea "": 1080x1920 +0+0 parent=(nil)
depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
override=0 _NET_WM_WINDOW_TYPE=0()
WM_TRANSIENT_FOR=(nil)
WM_HINTS=<none>
Aborted
I checked that unity is running, and the resullt of "ps aux | grep unity" was
Code:
unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 1
I also checked that mir_socket is created and reachable under /var/run and /run directories
There are no errors in lightdm file
But Xorg log file shows the following error
Code:
[ 89.205] (II) No BusID or DriverName specified - opening /dev/dri/card0
directory
[ 89.205] (WW) Falling back to old probe method for fbdev
[ 89.205] (WW) Falling back to old probe method for modesetting
[ 89.206] No devices to configure. Configuration failed.
[ 89.206] (EE) Server terminated with error (2). Closing log file.
The directory /dev/dri is missing on my phone. Although libdrm2 is installed
Any ideas how to overcome this problem?
Mqhash said:
Hi
I'm trying to run pidgin in ubuntu touch which is installed on Nexus 5.
I did try to run it in libertine container, however it fails with the follwoing error.
Code:
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Failed to connect to Mir: Failed to connect: not accepted by server
(EE)
I have also tried to run it without the container using the following desktop file
Code:
[Desktop Entry]
Name=Pidgin Internet Messenger
GenericName=Internet Messenger
Comment=Chat over IM. Supports AIM, Google Talk, Jabber/XMPP, MSN, Yahoo and more
Exec=pidgin
Icon=pidgin
StartupNotify=true
Terminal=false
Type=Application
Categories=Network;InstantMessaging;
X-MessagingMenu-UsesChatSection=true
X-Ubuntu-Touch=true
X-Ubuntu-Gettext-Domain=pidgin
X-Ubuntu-XMir-Enable=true
To run pidgin I am using the following script, launching it from phone's command line
Code:
#!/bin/bash
DISP=:1
Xmir :1 -mirSocket /var/run/mir_socket --desktop_file_hint=/home/phablet/pidgin.desktop -debug &
sleep 0.5;
DISPLAY=:1 pidgin &
However, Xmir failed with the following error.
Code:
ARM architecture: Defaulting to software mode because glamor is not stable
XMir initialized with 2 visuals:
Visual id 0x28: ff ff00 ff0000, 24 planes
Visual id 0x29: ff ff00 ff0000, 24 planes
Realize ROOT window 0xb8a6d530 id=0xea "": 1080x1920 +0+0 parent=(nil)
depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
override=0 _NET_WM_WINDOW_TYPE=0()
WM_TRANSIENT_FOR=(nil)
WM_HINTS=<none>
Aborted
I checked that unity is running, and the resullt of "ps aux | grep unity" was
Code:
unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 1
I also checked that mir_socket is created and reachable under /var/run and /run directories
There are no errors in lightdm file
But Xorg log file shows the following error
Code:
[ 89.205] (II) No BusID or DriverName specified - opening /dev/dri/card0
directory
[ 89.205] (WW) Falling back to old probe method for fbdev
[ 89.205] (WW) Falling back to old probe method for modesetting
[ 89.206] No devices to configure. Configuration failed.
[ 89.206] (EE) Server terminated with error (2). Closing log file.
The directory /dev/dri is missing on my phone. Although libdrm2 is installed
Any ideas how to overcome this problem?
Click to expand...
Click to collapse
Unfortunately, the only real good method of running X11 applications on Ubuntu Touch is via Libertine. That's odd that it won't connect to Mir. /dev/dri should indeed be missing from your phone, most phones do not expose DRM/DRI to the OS as they don't always have native support for it (for example, Qualcomm devices require the msm_kgsl_drm kernel module, however that module doesn't compile properly on newer kernels.)
On Android devices, an abstraction layer known as Libhybris is used for handling graphics and hardware by wrapping the native Android drivers and using them.
The only thing I could suggest is possibly creating a new empty libertine container and install only pidgin on it to see if it could possibly be an issue with your container, last time I used Ubuntu Touch, Pidgin worked out of the box in Libertine.
Thank you for your reply
ShadowEO said:
The only thing I could suggest is possibly creating a new empty libertine container and install only pidgin on it to see if it could possibly be an issue with your container.
Click to expand...
Click to collapse
Unfortunately, I did try to create a new container but same error. No change . I even tried to run firefox but same error
ShadowEO said:
last time I used Ubuntu Touch, Pidgin worked out of the box in Libertine.
Click to expand...
Click to collapse
What phone were you running ubuntu touch on?
Mqhash said:
Hi
I'm trying to run pidgin in ubuntu touch which is installed on Nexus 5.
I did try to run it in libertine container, however it fails with the follwoing error.
Code:
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Failed to connect to Mir: Failed to connect: not accepted by server
(EE)
Click to expand...
Click to collapse
How exactly did you get to this point? Which UT image? Was libertine included? The scope? The app? Did you install parts of it via apt? How did you run it? Where/how do you read the error?
I have also tried to run it without the container using the following desktop file
Click to expand...
Click to collapse
When you say without the container what exactly do you mean? If you only make the desktop file yourself, then there still is only one pidgin executable and that is the one in the container, right ... I don't know how to connect the two.
Code:
[Desktop Entry]
Name=Pidgin Internet Messenger
GenericName=Internet Messenger
Comment=Chat over IM. Supports AIM, Google Talk, Jabber/XMPP, MSN, Yahoo and more
Exec=pidgin
Icon=pidgin
StartupNotify=true
Terminal=false
Type=Application
Categories=Network;InstantMessaging;
X-MessagingMenu-UsesChatSection=true
X-Ubuntu-Touch=true
X-Ubuntu-Gettext-Domain=pidgin
X-Ubuntu-XMir-Enable=true
To run pidgin I am using the following script, launching it from phone's command line
Code:
#!/bin/bash
DISP=:1
Xmir :1 -mirSocket /var/run/mir_socket --desktop_file_hint=/home/phablet/pidgin.desktop -debug &
sleep 0.5;
DISPLAY=:1 pidgin &
However, Xmir failed with the following error.
Code:
ARM architecture: Defaulting to software mode because glamor is not stable
XMir initialized with 2 visuals:
Visual id 0x28: ff ff00 ff0000, 24 planes
Visual id 0x29: ff ff00 ff0000, 24 planes
Realize ROOT window 0xb8a6d530 id=0xea "": 1080x1920 +0+0 parent=(nil)
depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
override=0 _NET_WM_WINDOW_TYPE=0()
WM_TRANSIENT_FOR=(nil)
WM_HINTS=<none>
Aborted
Click to expand...
Click to collapse
So, firstly, I think libertine should work, so I'd focus on that first. Secondly, if you want to explore an alternative route, I had things working in the past with:
* install via apt
* write a shell script like yours (search the internet for that desktop_file_hint, it seems to have some magical hidden meaning, you do not want to set it to pidgin, but I think to some uhm, whatdidtheycallit, "unconfined" app I think)
* write a desktop file and point it to shell script, and launch it by tapping on the display