Tether shutdown

13 replies [Last post]

Thu, 04/29/2010 - 13:11

smorloc

Offline

Last seen: 1 year 44 weeks ago

Joined: 09/22/2009

Using Tether over Bluetooth continues to be a problem for me.
So far, the company has not been helpful at all and doesn't appear
to be interested in pursuing what anyone would consider a serious
problem. Regardless, I'm going to post another problem I've
captured.

I was recently testing 1.1.04 to see if it solved my issues with
Tether's communication silently stopping from the BlackBerry
to the PC (alas, the problem still exists), and noticed another
problem. Tether silently terminated on both the PC and Blackberry.
I have not found any log on the PC and the Tether log on the
BlackBerry continues to be useless. The BlackBerry (LGLG) has
some potentially useful information. I have appended the output
to the end of this email.

The following is my configuration:

- Blackberry Tour, Verizon, latest v5.0.0.591
- Dell Windows 7 64-bit notebook
- iogear Bluetooth adapter
- BlackBerry's Tether is version 1.1.04
- Computer's Tether is version 1.1.02
- I have a good cell phone signal.
- Tether never reports an error

Regards,
Steve

====
a net.rim.bluetooth - DD13 - 4/29 11:41:56
a net.rim.bluetooth - EC01 - 4/29 11:41:53
a net.rim.bluetooth - Device name: XXXXX, address: 00:02:72:AA:07:A5 - 4/29 11:41:53
a net.rim.bluetooth - DC00 - 4/29 11:41:53
a net.rim.udp - clos 0/104 - 4/29 11:41:48
a net.rim.tunnel - Clos- - 4/29 11:41:48
S Java Exception - NullPointerException - 4/29 11:41:48
| No detail message
| Tether(4BCE0749)
| BlueTooth
| write
| 0x182
| Tether(4BCE0749)
| ReceiveThread
|
| 0x341B
| Tether(4BCE0749)
| ReceiveThread
|
| 0x3495
| Tether(4BCE0749)
| ReceiveThread
| run
| 0x3052
S Java Exception - NullPointerException - 4/29 11:41:48
| No detail message
| Tether(4BCE0749)
| BlueTooth
| write
| 0x182
| Tether(4BCE0749)
| ReceiveThread
|
| 0x341B
| Tether(4BCE0749)
| ReceiveThread
|
| 0x3495
| Tether(4BCE0749)
| ReceiveThread
| run
| 0x3052
d net.rim.udp - RXst 52 - 4/29 11:41:48
d net.rim.udp - RXST 1 - 4/29 11:41:48
d net.rim.udp - RXst 52 - 4/29 11:41:48
d net.rim.udp - RXST 1 - 4/29 11:41:48
d net.rim.udp - OPEN - 4/29 11:41:48
a net.rim.tunnel - STac- - 4/29 11:41:48
a net.rim.tunnel - Open- - 4/29 11:41:48
a net.rim.udp - open udpsocket://xx.xx.xx.xx:xx;localPort=4779 - 4/29 11:41:48
a net.rim.udp - clos 1707392/20556186 - 4/29 11:41:47
a net.rim.tunnel - Clos- - 4/29 11:41:47
d net.rim.udp - RXST 0 - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
d net.rim.udp - TXss - 4/29 11:41:47
d net.rim.udp - RXST 1 - 4/29 11:41:47
i net.rim.lstp - MXsd - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
i net.rim.lstp - RCsd - 4/29 11:41:47
d net.rim.udp - RXST 1 - 4/29 11:41:47
i net.rim.lstp - LNdn - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
a net.rim.bluetooth - DD16 - 4/29 11:41:47
d net.rim.udp - RXST 1 - 4/29 11:41:47
d net.rim.udp - TXwa - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
d net.rim.udp - TXsb 56 - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
d net.rim.udp - RXst 52 - 4/29 11:41:47
d net.rim.udp - TXss - 4/29 11:41:47
d net.rim.udp - RXST 4 - 4/29 11:41:47
d net.rim.udp - TXwa - 4/29 11:41:47
d net.rim.udp - TXsb 56 - 4/29 11:41:47
d net.rim.udp - TXss - 4/29 11:41:47

Thu, 04/29/2010 - 13:58

hhzhao

Offline

Last seen: 28 weeks 5 days ago

Joined: 01/06/2010

From several posts I have seen, it appears there are some performance issues related to Windows 7 (64bit) environment. I am sure Tether developer is looking into that.

So far, Tether with XP and Windows 7 (32bit) seems fairly stable. Those who reported issues under those environment are mainly configuration and/or installation related.

Thu, 04/29/2010 - 14:17

smorloc

Offline

Last seen: 1 year 44 weeks ago

Joined: 09/22/2009

I'm not buying it. To have Tether silently exit
and/or stop transmitting data seems like a
Tether problem. The engineers should consider
this a priority and investigate it. Instead, when
I contacted tech support, I was pretty much
rebuffed. As a developer myself, I'm very
surprised by the lack of robustness of the
Tether application and the poor techincal
support.

Regards,
Steve

Thu, 04/29/2010 - 15:28

hhzhao

Offline

Last seen: 28 weeks 5 days ago

Joined: 01/06/2010

Not mean to create any argument here, but you have admit, majority users on XP and Windows 7 (32bit) have not experienced your specific issue.

Each of us has different sets of value when in time to value the services from vendor. As an early adapter to Tether, I have went trough some frustration. But I have benefited from the tech support from Tether, and eventually the issues were resolved. I am happy about my experiences.

So generalization of Tether performance and support staffs will not be fair.

Just my 2 cents.

Thu, 04/29/2010 - 16:06

smorloc

Offline

Last seen: 1 year 44 weeks ago

Joined: 09/22/2009

A company should support their customers, not just the majority. The comment is ridiculous. Companies (hopefully) provide support for the benefit of the minority of their customers. I am a paying customer and the product behaves in an unreasonable fashion that can lead data loss. Neither through their support channel and this forum have appeared to take the problem seriously.

I think your blaming my problem on my 64-bit is part of a blind devotion to Tether. I disagree with the assertion that the problem is predominantly at Windows 7 64-bit one. Regardless, half the program is not running on a 64-bit OS (the BlackBerry part) and the other part silently fails.

I firmly believe that whatever abnormal exits and communications loss the Tether application is currently encountering can at least be DETECTED & REPORTED. Even if you choose to blame a Bluetooth adapter, the service provider, the device or the host operating system. I believe that the Tether application fails because it is NOT detecting or reporting the catastrophic event.

Like it or not, this is a Tether issue...

Steve

Thu, 04/29/2010 - 18:59

autobot

Offline

Last seen: 19 weeks 2 days ago

Joined: 02/11/2010

Your issue is a Tether problem since you're a customer. Sometimes an issue can't be resolved or support can't immediately provide a resolution since the developers have to find the cause first. The same can be said for all software support, even a company like Microsoft cannot resolve all issues in a short amount of time.

Thu, 04/29/2010 - 20:05

smorloc

Offline

Last seen: 1 year 44 weeks ago

Joined: 09/22/2009

I am a developer and have supported customers
of both retail and custom applications we have
produced. I understand the difficulties of
supporting folks.

Please address my assertion that Tether should
not silently fail. I have seen nothing
from a Tether representative that agrees with
this statement. I have seen no acknowledgement
this this is not acceptable behavior. I have
seen plenty of excuses, such as those I mentioned
in my last post. I believe I am holding Tether
to a reasonable standard. If there are problems
that customers are reporting that is costing
them time, productivity, etc then a company
should take those reports seriously, acknowledge
the problems if they are legitimate and attempt
to fix them in earnest. If the Tether developers
are able to reproduce the problem, then it should
be acknowledged. If they are not able to, then
they should be contacting folks like me and
trying in earnest to track down the source of
the errant behavior.

BTW, my experience is that Microsoft has a
great support mechanisms in place for their
many (many!) products.

Steve

Fri, 04/30/2010 - 13:33

autobot

Offline

Last seen: 19 weeks 2 days ago

Joined: 02/11/2010

The developers indeed take each issue seriously, they work everyday with customers such as yourself to get issues resolved.

I am sorry that you feel unsupported, I have seen your issue described by other customers and our developers are working with a couple of people to find the cause.

Please give them adequate time to find a resolution.

Tue, 05/11/2010 - 03:22

lee.harless

Offline

Last seen: 1 year 39 weeks ago

Joined: 02/24/2010

It could be that the company has been infiltrated by saboteurs, from Verizon or some other corporation. Espionage happens every day in big business. If they feel that this is a threat, it could be sabotage, in hopes that the product will be abandoned by the user base. ...just sayin'. ..it could happen.

--
Roger Lee Harless, Jr.
Multimedia Artist/Filmmaker
Apex, North Carolina

Tue, 05/11/2010 - 14:37

phankinson

Offline

Last seen: 1 hour 34 min ago

Joined: 02/19/2009

That's a very odd post. I can assure you that we have not been sabotaged by Verizon or any other company.

We are working in collaboration with smorloc by email now, trying to resolve his issue.

--
Patrick Hankinson
Community Manager

Sat, 06/05/2010 - 22:10

#10

lee.harless

Offline

Last seen: 1 year 39 weeks ago

Joined: 02/24/2010

Well, not quite as odd as you may think, but I respect and trust that you're working on the issue.

As of today, I'm using a brand new macbook pro, with a storm2, over bluetooth. i'm using the latest version for the blackberry (1.1.0.7?), and 1.1.0.2 on the macbook pro. my storm2 uses the ver.5 os.

to use tether, i will open the program on the blackberry, and then the macbook. i select bluetooth on both devices and tether starts up and works just fine. most times, it begins receiving packets and everything works fine, for a little while and then out of the blue, it will just stop working and i will have to quit the program on both devices and start the process over. i have come to count on it's failure to maintain connection.

If you would like, i'm all for cooperating, to let you know what's happening with my rig. in fact, as i was writing this, it failed once. i'm in a hotel room.

the software remains open and the macbook version UI shows that there are packets flying through the connection, but nothing happens when i click on a link.

i'm not very technically adept with things like this, so the industry lingo is over my head. i know just enough to use the technology, but not to diagnose, or dig much past how to start up the software and how to shut it down, so anything you ask me to do will have to have instructions attached.

--
Roger Lee Harless, Jr.
Multimedia Artist/Filmmaker
Apex, North Carolina

Mon, 06/07/2010 - 13:06

#11

phankinson

Offline

Last seen: 1 hour 34 min ago

Joined: 02/19/2009

When running Tether on your BlackBerry, click on "View Log" and let me know what it says.

--
Patrick Hankinson
Community Manager

First name
Last name
Email address
Verify Email
BlackBerry Android iPhone
I'd like to receive Tether discounts and updates.

Tether shutdown

Product

Our Company

Get Started

Select your Smartphone

Select your Smartphone

Tether shutdown

Product

Our Company

Tether Community

Get Started

Select your Smartphone

Select your Smartphone