App Name

BerrySpeedy

Latest version



I just finished coding my first release of this app. The main reason for this is that I always wanted to see what bandwidth I was giving by using BIS-B and by using my carrier APN. Maybe it would be a nice idea to compare results from carrier to carrier with BISB/APN from regions all over the world.

OTA install link:

http://ota.deltatech.com.mx/

Usage:

After running the app, you're presented with 2 options, Transport, and the Size of the download speedtest. If you select TCP, be sure to have your APN configured correctly under Options->Advanced->TCP. For the sizes, theres a 10K, 100K, 500K and 1M.


Screenshots



Note: This app connects to one of my servers located on a US datacenter, and has 100mbit connect. Hopefully that wont be a bottleneck (considering that I doubt anyone will acheive 200KB/s from any BB)

Check worldwide results

URL: BerrySpeedy

Changelog


1.43
- Bug fixes for some bb models
- Shows version on app title

1.3
- The program now sends some anonymous information about the device (carrier, country, cellid, signal strenght, network type, model number, OS). With this information now it will be possible to create some reports of speeds by carrier, country, or even how well a particular unit performs (ie 3G Blackberries). Expect a web page where all this information can be shown.
- If no WIFI is available it now hides it from the transport list
NOTE: If you are still using the 1.0, please update ASAP since for this version I had to upgrade the server core, which right now runs on another port.


1.2
- Fixed a typo on the port server

1.1
- Fixed some app hangs when the tunnel cant be created and/or server problems
- Added an autoupdate check when apps starts.
- Changed the 10K to 50K (to make it a more 'reliable' test result for slow users)

1.0
-Initial Release

Please report any bugs to this thread.

Hello,

I'm getting around 17KB/s here in Europe via BIS-B. The TCP option does not work for me (Curve 8310 with 4.5 OS) even with correctly configured APN.

Regards, Dejan.

Hey, nice! I'll be trying this out and report back.

Nice little app!

I am getting the following results:

BIS-B - 18kb/s

Wifi - 173 kb/s

I don't have tcp enabled to check right now. I am in Toronto Canada.

Cool application...

Does your provider have a strict firewall for which apps it runs?? This app uses a Socket connect and the dst port is a high port (4545) It could be that they might be blocking that. Anyone with a 8310 got it to work correctly?

Wirelessly posted

Doesent work on att 8310

Try again.. I just upgraded the server side component (plus i didnt noticed it was down like 20 mins ago). This app needs to connect to my server in order to work properly, so if I have problems on my side.. you wont be able to connect

TCP: 115 KB/S
BIS-B: 11 KB/S

Does this mean I should configure all of my applications to use TCP instead of BIS-B if they have that option?

Is there a general setting I can change on the phone to make it use the faster connection?

Exactly... remember that BISB has to tunnel all your data to RIM servers, plus it seems they speed limit this connections (I cant seem to acheive more than 20k/sec over BISB, while I get 50k/sec on TCP) It should be faster, and have lower latency. BUT.. if you do international roaming, they just count the BISB for the 'unlimited' international data plans.

So when I'm using the web browser on the phone, is it using BIS-B or TCP for that connection?

Does the phone only use TCP for applications when it gives the option to manually specify using it?

It always uses BISB if you use the web browser. You could try using Opera Mini, it supports APN. And another thing to note.. for BISB, theres a socket transfer limit, i think that its currently set at 3megs, after that it forces it to close (hence you never see a streaming app that uses BISB). So with APN, you could easily download files over 3megs, and do streaming, compared to using BISB (that is if the app supports selecting which that is)

I just released an update... please if you want to continue using this app upgrade.. sometime next week I might upgrade the comunications protocol, and in order to work the app needs to be updated. For now I added an auto update when new version is out, and some fixes when errors happens (exceptions).

I upgraded and now I am getting connection errors when using BIS-B and TCP.

TCP returns:

Error: General socket error

BIS-B returns:

Error: java.io.IOException: could not connect to LeetWebHosting.com - Webhosting that suites your needs at net.rim.utility.transport.tcp.nio.TCPChannel.conne ct(TCPChannel.java:168) at net.rim.protocol.iplayer.connection.handler.device .defaulthandlernio.Core.startChannel(Core.java:123 ) at...

My bad!! I forgot to change the test port I was using on this build.... I just uploaded 1.2 with the correct port... run it again and it will prompt u for the update...

Verizon Pearl:

500K

BIS-B:
Min: 531ms
Avg: 648ms
Max: 830ms
- Speed: 7 KB/S

TCP:
Min: 207ms
Avg: 277ms
Max: 517ms
- Speed: 34 KB/S

On 1MB I got 48 KB/S

Wow, now that I changed the connection in Opera from HTTP to Socket, there's no going back to the BB browser.... Opera is SO much faster now!
Why don't all apps (i.e., GOOGLE MAPS!!) allow this option?

500K:
BIS-B: 24 KB/S
TCP: 75 KB/S

Edit: I can't actually confirm the Opera HTTP vs Socket setting; it may have merely been a placebo effect.

Ok another update now available.. Please update to 1.3 when u guys have a chance. For the changelog check the first post

Woah! Three times faster than my VZW Pearl on BIS-B, twice as fast on TCP.

Verizon...it's the Network? Sprint sure looks good there...

OK, after upgrading to 1.3, it just seems to hang whenever running a test. No matter what setting I choose, I will click Run and then I see the data activity arrows blinking, then after a few seconds they go away, and the app just runs forever never finishing.

I have the exact same problem since 1.3 and I'm on Sprint also.

What device / OS ?

Pearl 8130
OS 4.5.0.97

Pearl 8130, 4.5.0.97 Sprint for me.

Hanging for me as well...device/os in sig

I just released an update to see if it now stops in case of the error and shows the exception... please try updating and see if it returns an error now...

"Error: null" for both TCP and BIS-B

Could you update again.. 1.41, it should now append a Code to the Error... when u have it please let me know which is...

Error: null Code: 7

Build 1.42 available.. hope that fix that exception.. give it a try and please report back if success

BIS-B
Error: null Code: 8

TCP
Error: Timed out

Just updated 1.43.. hopefully that will be the last exception this units throws (guess it was thou that those berries have different classes to get cell tower info)

Who said it would be easy to develop apps for all blackberry models

Using 1.43
Error: null Code 8 for both BIS-B and TCP
Don't know if this helps but I do know that CDMA devices get different cell tower info

I added some extra validations for the CDMA networks to prevent that error.. please try 1.44

it says the page you are trying to load could not be found... when trying to download .44

LOL.. I knew i forgot something.. and that was upload the actual files They're up now

I kept clearing my browser cache. The web site says 1.44, but when I get to the download screen, it says 1.43...

Edit: I opened the program and it says 1.44.

Both BIS-B and TCP are working!

I got 1.44 and it appears to be working now.

By the way, why does the program always ask me if I want to save changes when I exit, then it doesn't change whatever changes I made?

I'd rather it just not ask at all.

Rogers Unlocked BB Bold on .169
3G

BIS-B @ 500kb
Speed: 13kb/s

TCP @ 500kb
Speed: 107 kb/s

WiFi @500kb
Speed: 266kb/s

I did each test 3 times, those were the highest numbers i got from each.

1.43 seemed to work for me if I remember correctly.

BIS-B @ 500kb
Speed: 9kb/s (Got 12 earlier tonight)

TCP @ 500kb
Speed: 66 kb/s (Got 98 earlier tonight)

Maybe dumb question - is speed affected by being in a building or outside? I got much faster speeds earlier tonight when I was (coincidentally?) outside.