coondogg97
Member
I upgraded first thing this morning but haven't had a chance to really check out any differences yet. Still doesn't support remote login to a locked computer.
DroidForums.net | Android Forum & News
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Does phonemypc just not work?
- Thread starter mike_kauble
- Start date
small issue
love this app by the way. its exactly what i was looking for in the mobile remote desktop area.
works like a charm when im on wifi but when i turn that off and use the EDGE network on Sprint (i dont have 3G coverage where i am most of the time), i log in and click the computer i want to connect to in the phone app. after that it takes a sec or 2 and throws an error:
Authentication failed.
Is this just cuz my EDGE connection just isnt fast enough and it times out? havent had a chance to try 3G yet due to i have to travel to do that..
love this app by the way. its exactly what i was looking for in the mobile remote desktop area.
works like a charm when im on wifi but when i turn that off and use the EDGE network on Sprint (i dont have 3G coverage where i am most of the time), i log in and click the computer i want to connect to in the phone app. after that it takes a sec or 2 and throws an error:
Authentication failed.
Is this just cuz my EDGE connection just isnt fast enough and it times out? havent had a chance to try 3G yet due to i have to travel to do that..
SoftwareForMe.com
Member
@mikser100,
Edge just doesn't have enough bandwidth for a good remote-control experience. We have some thoughts about how to provide "something" while on 3G, similar to our thoughts about optimizing video streaming, but we won't get to working on that for a while yet.
The error you're experiencing is a bug. We made some changes recently to our networking code to better support users on Satellite internet, and in the process we made the code unnecessarily sensitive to network latency. We are working on a fix for that and will release it as soon as it is available.
Edge just doesn't have enough bandwidth for a good remote-control experience. We have some thoughts about how to provide "something" while on 3G, similar to our thoughts about optimizing video streaming, but we won't get to working on that for a while yet.
The error you're experiencing is a bug. We made some changes recently to our networking code to better support users on Satellite internet, and in the process we made the code unnecessarily sensitive to network latency. We are working on a fix for that and will release it as soon as it is available.
SoftwareForMe.com
Member
Darrell is right: it works well on 3G. But with this new bug, approximately 1 out of 100 users are experiencing intermittent errors when using 3G, and a couple cannot connect at all. Also, using Edge generates the error you describe, rather than just running very slowly.
Ironically, we have devices on Sprint, T-Mobile and Verizon, and we cannot duplicate the issue on 3G (so it always works for us), and we've tried in several West Coast cities and suburban areas from Seattle to San Diego.
Nonetheless, we will have it fixed. And, the program should never give you an error and exit like it does on Edge; it should work, albeit slowly.
Ironically, we have devices on Sprint, T-Mobile and Verizon, and we cannot duplicate the issue on 3G (so it always works for us), and we've tried in several West Coast cities and suburban areas from Seattle to San Diego.
Nonetheless, we will have it fixed. And, the program should never give you an error and exit like it does on Edge; it should work, albeit slowly.
coondogg97
Member
Darrell is right: it works well on 3G. But with this new bug, approximately 1 out of 100 users are experiencing intermittent errors when using 3G, and a couple cannot connect at all. Also, using Edge generates the error you describe, rather than just running very slowly.
Ironically, we have devices on Sprint, T-Mobile and Verizon, and we cannot duplicate the issue on 3G (so it always works for us), and we've tried in several West Coast cities and suburban areas from Seattle to San Diego.
Nonetheless, we will have it fixed. And, the program should never give you an error and exit like it does on Edge; it should work, albeit slowly.
Can you please check your PMs.
Softwareforme: Hows it going??
On Monday, January 18th you released PhoneMyPC v1.0.15.
I have not read an more information about your upgrades with extra features such as SOUND, and being able to log on to a PC and having security turned back on.
So.. I was just wondering if anyone from Softwareforme would like to comment on how the upgrades are comming along.
Thanks for a great product.
On Monday, January 18th you released PhoneMyPC v1.0.15.
I have not read an more information about your upgrades with extra features such as SOUND, and being able to log on to a PC and having security turned back on.
So.. I was just wondering if anyone from Softwareforme would like to comment on how the upgrades are comming along.
Thanks for a great product.
SoftwareForMe.com
Member
Hello,
Our January 18th release focused on bug fixes, updates for users with some network topologies that didn't work properly with PhoneMyPC, and the addition of some highly requested features (App password, better PC key support, etc.).
After that release we found that our changes to the network code had rendered the product too sensitive to network latency. Some customers were having intermittent network errors, and a few could not connect at all.
So, we further divided our efforts so we could get all the work done that needed to be done. While Remote login is our #1 priority, we will always drop everything and do bug fixes if we need to support our current users. As our Beta page explains, there will be bugs, and all the features we want are not there yet. But we would like to at least guarantee that we will be most attentive to keeping the software "at least as good as it was when you downloaded it." So, you should never have to worry about losing functionality, or at least if you do (such as in the case of this networking goof), it will be temporary.
So, here is our status:
1) A fix to the network issue will be released today. It also includes a few other minor fixes.
2) Remote login will be deployed later this week to a small group of pre-release testers. We are still working to get the installation experience simplified and ready, but the public release date will largely depend upon how things go with our pre-release testers.
3) Our Sound guy has audio capture working on XP and is working on the other OSes. While he will continue to get this ready to be added, there are no other resources on this work because remote-login is our priority.
4) File-copy. Due to customer requests, this will certainly be the next addition after Sound. This will be a very easy feature to add, and should follow shortly after sound. There is no work being done on this now.
That is our status.
Our January 18th release focused on bug fixes, updates for users with some network topologies that didn't work properly with PhoneMyPC, and the addition of some highly requested features (App password, better PC key support, etc.).
After that release we found that our changes to the network code had rendered the product too sensitive to network latency. Some customers were having intermittent network errors, and a few could not connect at all.
So, we further divided our efforts so we could get all the work done that needed to be done. While Remote login is our #1 priority, we will always drop everything and do bug fixes if we need to support our current users. As our Beta page explains, there will be bugs, and all the features we want are not there yet. But we would like to at least guarantee that we will be most attentive to keeping the software "at least as good as it was when you downloaded it." So, you should never have to worry about losing functionality, or at least if you do (such as in the case of this networking goof), it will be temporary.
So, here is our status:
1) A fix to the network issue will be released today. It also includes a few other minor fixes.
2) Remote login will be deployed later this week to a small group of pre-release testers. We are still working to get the installation experience simplified and ready, but the public release date will largely depend upon how things go with our pre-release testers.
3) Our Sound guy has audio capture working on XP and is working on the other OSes. While he will continue to get this ready to be added, there are no other resources on this work because remote-login is our priority.
4) File-copy. Due to customer requests, this will certainly be the next addition after Sound. This will be a very easy feature to add, and should follow shortly after sound. There is no work being done on this now.
That is our status.
2) Remote login will be deployed later this week to a small group of pre-release testers. We are still working to get the installation experience simplified and ready, but the public release date will largely depend upon how things go with our pre-release testers.
Great news, just what I was hoping to hear. Thanks to all your dev guys for the efforts.
I am not a developer, but I do assist our dev guys with issues on our EMR app. Quite a bit of work is involved in updates. More than I ever knew.
-Mike
OmegaXzer0
New Member
I just purchased PhoneMyPc, and I am using a Motorola Droid. I keep getting a force close when I try to open up the app. I have already set up the software on my computer, but I have only reached the screen where I can choose the computer to remotely connect to once out of at least 50 tries. I have tried using wifi and my 3G connection to no avail. Any help would be greatly appreciated.
SoftwareForMe.com
Member
Hi OmegaXzer0,
We had a temporary service outage last night--our second, and longest--due to a Denial of Service attack. It has been fixed and the software should work now.
Moreover, just 30 minutes ago we published an update that improves the reliability of the networking code.
About this outage: we lease servers from one very reliable company. However, in the very near future, we will be distributing our servers both across several companies as well as geographically. This will improve performance, and make service interruptions like this one a thing of the past.
We had a temporary service outage last night--our second, and longest--due to a Denial of Service attack. It has been fixed and the software should work now.
Moreover, just 30 minutes ago we published an update that improves the reliability of the networking code.
About this outage: we lease servers from one very reliable company. However, in the very near future, we will be distributing our servers both across several companies as well as geographically. This will improve performance, and make service interruptions like this one a thing of the past.
Steveindajeep
Member
Any news on this update to allow access to a locked computer?
I have an email from you saying it was going to be fixed before new years.
I have an email from you saying it was going to be fixed before new years.
Similar threads
- Replies
- 3
- Views
- 3K
- Replies
- 3
- Views
- 3K
- Replies
- 0
- Views
- 1K