logo
Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
elgerwell  
#1 Posted : Wednesday, May 14, 2014 3:58:23 AM(UTC)
elgerwell


Rank: Newbie

Joined: 5/14/2014(UTC)
Posts: 4
United States
Location: Texas

Thanks: 1 times
When attempting to connect from a nexus 5 with the playstore client installed I get the error "error: sendto failed: EPIPE (broken pipe)" I get this when connecting to either windows 7 or windows 8 host machines. Our server is running latest stable version and the android phone is running 4.4.2. Any ideas?

Edited by user Thursday, May 15, 2014 1:20:49 AM(UTC)  | Reason: Not specified

John  
#2 Posted : Friday, May 16, 2014 7:32:17 PM(UTC)
John


Rank: Guest

Medals: Level 2: Lent a Helping Hand! 10 Thanks!

Joined: 3/25/2014(UTC)
Posts: 226

Thanks: 5 times
Was thanked: 12 time(s) in 11 post(s)
We used a Nexus 7 device and had no issues -- unfortunately we do not have a Nexus 5 to test on. Are you using the version of the app thats made for Samsung devices or the standard? You can try the other one, whichever you're using. And see if that works.

Also, try just simply going to the support site on the standard browser, outside of the app.
thanks 1 user thanked John for this useful post.
elgerwell on 5/23/2014(UTC)
elgerwell  
#3 Posted : Friday, May 23, 2014 7:01:27 PM(UTC)
elgerwell


Rank: Newbie

Joined: 5/14/2014(UTC)
Posts: 4
United States
Location: Texas

Thanks: 1 times
I have tried both versions of the app and get the same "epipe broken pipe" error on both. With the browser when I attempt to join a session it launches into a play store window to download the app.
Alexander  
#4 Posted : Thursday, May 29, 2014 6:09:05 PM(UTC)
Alexander


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 7/23/2013(UTC)
Posts: 715
Man
Location: Raleigh, NC

Was thanked: 66 time(s) in 63 post(s)
Just to be clear, does this happen when you're controlling Windows machines from the Nexus 5, or the other way around? Does it work with machines running something besides Windows 7/8?



Has anyone else had this issue?
ScreenConnect Team
elgerwell  
#5 Posted : Thursday, May 29, 2014 6:13:59 PM(UTC)
elgerwell


Rank: Newbie

Joined: 5/14/2014(UTC)
Posts: 4
United States
Location: Texas

Thanks: 1 times
This is when controlling windows machines from nexus 5. I have tested controlling win7/8 and server 2003/2008/2012
Alexander  
#6 Posted : Tuesday, June 3, 2014 7:04:08 PM(UTC)
Alexander


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 7/23/2013(UTC)
Posts: 715
Man
Location: Raleigh, NC

Was thanked: 66 time(s) in 63 post(s)
All right, we're going to see if we can reproduce this with a newer version of Android. Is there anything on your device that might be affecting this, like antivirus software for example?
ScreenConnect Team
elgerwell  
#7 Posted : Friday, June 6, 2014 3:54:09 AM(UTC)
elgerwell


Rank: Newbie

Joined: 5/14/2014(UTC)
Posts: 4
United States
Location: Texas

Thanks: 1 times
this is while running a completely stock version of android 4.4.3
kwoodrow  
#8 Posted : Wednesday, July 9, 2014 9:38:26 PM(UTC)
kwoodrow


Rank: Newbie

Joined: 7/9/2014(UTC)
Posts: 2
Canada
Location: Guelph

Getting this same "error: sendto failed: EPIPE (broken pipe)" when using the Android app (Samsung or basic). I'm also using a Nexus 5, with stock 4.4.4. Not sure if it was doing the same thing when i was running 4.4.3.

Tried connecting to XP/2003/2008/Win7/8/Mac, all with the same result.

Has there been any progress made on this?
Alexander  
#9 Posted : Thursday, July 10, 2014 2:15:54 PM(UTC)
Alexander


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 7/23/2013(UTC)
Posts: 715
Man
Location: Raleigh, NC

Was thanked: 66 time(s) in 63 post(s)
Not yet; it's still on our to-do list.
ScreenConnect Team
kwoodrow  
#10 Posted : Thursday, July 24, 2014 12:55:31 AM(UTC)
kwoodrow


Rank: Newbie

Joined: 7/9/2014(UTC)
Posts: 2
Canada
Location: Guelph

I was able to solve this issue finally.

I had forgotten that I'd recently flipped the Android runtime from Davlik to ART to see if battery life might improve. There were reports of some apps not behaving. As Soon as I changed back to Davlik, the ScreenConnect Android app started working again.

Hope this helps anyone out there with similar symptoms.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.