New BlackBerry Commercial
New BlackBerry Commercial

February 27, 2009
You might also like -
|
|
|
|
filed in Uncategorized on Feb.27, 2009

|
|
|
|
filed in Uncategorized on Feb.27, 2009

It looks cool, I guess, but I’m not sure how it’s better than the current system.
|
|
|
|
filed in Uncategorized on Feb.26, 2009

When sending an email using Gmail, the same email arrives in the inbox. (Duplicate Emails). This is how to stop it. This is also related to duplicate calendar appointments issue.
Every time I’d send an email on Gmail, I’d grimace at the buzz that would follow on my phone. Why is it necessary for me to be notified that I sent an email? The annoyance only increased when I realized that when I invite people to appointments in Calendar, I’d get a duplicate appointment in my Calendar that I had to delete.
The solution is simple but a tedious process.
It should work for all Verizon BlackBerry BIS users and not just for the Storm
1. Setup your BIS account. (If you haven’t already, and most likely you haven’t.)
-a. Using your phone brower, go to www.blackberry.com/go/vzw
-b. Click, Create New Account
-c. After going through the End User Agreement, create a username and password.
2. From a non-mobile computer, go to the same site before (www.blackberry.com/go/vzw).
3. Log in using the Username/Password you just created.
4. Under “Valid Email Account”, click on the filter picture under “Filters” related to your Gmail email.
5. Click “Add Filter”.
a. fill in.
Filter Name: [me]
Apply Filter when: ["From" field]
contains: [igetemail@gmail.com]
b. click “Do not forward messages to device”
c. click save
That’s it. The site should take you to a page that says “Filters for: (your email).” Check to see if what you just did is there.
No more sent emails in inbox.
No more duplicate appoints sent to the Calendar.
Try it out!
An update to the BIS scheduled to come out in March or April ‘09 is supposed to fix this issue without having to set it up.
|
|
|
|
filed in Uncategorized on Feb.25, 2009

Converting “seems faster” into actual numbers
From leak to leak, I’ve read many mini-reviews of new users saying the leak seems faster or quicker or more responsive. But is it really? The leaks do seem faster, but by how much? I decided to run a few tests to see if it was faster. I’m going to find the speed by measuring the time it takes from when the battery is inserted to after the verifying software bar is done.
Applications on test phone:
blackberry core
language – english
supplemental – english
blackberry application center
blackberry attachment service
blackberry maps
blackberry messenger
blackberry s/mime
brickbreaker
browers
dod root certificates
email setup
facebook
memopad
phone
tasks
word mole
documents to go
I deleted most of my apps off the phone to keep it at the bare minimum. I’m not sure why I decided to keep facebook on the phone. On an odd side note, I couldn’t delete Slacker using DM, but could off the phone.
Test Data:
| .103 | .109 | |
| Application Memory | ||
| - Free Space | 47.4 | 48.9 |
| Battery Pull Times – 10 pulls | ||
| - best time | 3:05 | 2:41 |
| - worst time | 4:34 | 5:07 |
| - average | 3:30 | 3:09 |
Analysis:
At first, .109 didn’t look too promising. The first three pulls came out to 3:41, 5:07, and 3:41. But afterwards, I didn’t get a pull that took longer than 2:48. Much faster than the fastest .103 could pull out. Matter a fact, if I remove the first three trials, .109’s average is a whopping 2:44. Removing the three worst trials of .103 makes it’s average 3:16. That’s an improvement of 32 seconds!
I think a better judge of speed, though, is just comparing the best times because it shows the phone at its fastest without any long boot time anomalies. The best times tended to be close to the mode of the trials as well. .109’s best time was faster than .103’s by 24 seconds.
It’d be interesting to do the same tests for .75 or even for .65 just to see how much better the BlackBerry Storm has gotten, but that’ll be for another time.
Conclusion:
.109 is 24 seconds faster than .103
|
|
|
|
filed in Uncategorized on Feb.24, 2009

filed in Uncategorized on Feb.23, 2009