BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 09-25-2006, 11:21 AM   #21 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Please Login to Remove!

The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.
Also how hard to add stopwatch functionality? Even just a basic one without split time works for me.
Offline  
Old 09-25-2006, 11:40 AM   #22 (permalink)
BlackBerry Extraordinaire
 
cooperpwc's Avatar
 
Join Date: Mar 2006
Location: Toronto Canada
Model: 8700R
Carrier: Rogers
Posts: 1,001
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by obijohn
There are a couple of problems with this.
1) Implementing the feature you describe requires code signing keys issued by RIM (and paid for by the developer). Since I'm releasing this free, I can't afford to pay for the keys. I guess if I was going to charge $59 for an app like ToDoMatrix, then maybe I would consider it as an option.
2) Even if I paid for the keys, this type of alert can only be set by the user outside the app by editing the device profiles. There is no way to select and play a device ringtone/tune directly within an app.

Basically, the app itself cannot access the tunes on the device at all. For some reason, RIM just doesn't allow this. The way the above method works is the app issues a "play notification alert" command and whatever alert tune has been assigned in the user profile will play. And to do this requires the developer paying for code signing keys to get access to the necessary commands to create and access settings in the profiles.

To me, this whole thing is idiotic. Let's say I wrote a countdown timer for Windows. Can you imagine having to open the Windows Control Panel and edit the system Sound Properties to assign a particular tune for the timer to play, instead of simply being able to assign it in the application itself? And on top of this, Microsoft charging the developer a fee for the privilege of using such a wonderful setup? That's just crazy!
I quite agree. And thanks for the explanation. Is it possible to have a choice of a shriller alert (since there is appparently a volume limitation.) For example, you can download an excellent alert at Blackberry Extras called Notifier_EarlierRiserF. It actually sounds pretty nice but at normal volume you cannot miss it. Also having the option of the alert repeating a few times when time has run out would be great.
Just suggestions. The app is already excellent.
Offline  
Old 09-25-2006, 01:28 PM   #23 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Inphektion
The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.
Hmm, that's very odd. I'm pretty sure the 8100 uses OS version 4.2, could you check your version for me? The tone and vibrate functions should work on all OS versions 4.0 and up, at least according to the API docs. I don't know what the problem could be. Please double-check your OS version for me and I'll start digging around the API documentation for 4.2 and see if I can figure out what the problem might be.
Quote:
Also how hard to add stopwatch functionality? Even just a basic one without split time works for me.
Well, this is a count down timer, after all. ;) One possibility, though, would be to allow the "T-Minus" display to reverse and count up from 0, in which case the text would need to change to "T-Plus" (or something) while in this mode. Tell you what, if one other person besides you posts a response here that they also would like this option, I'll add it. Deal?
Offline  
Old 09-25-2006, 01:49 PM   #24 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by cooperpwc
Is it possible to have a choice of a shriller alert (since there is appparently a volume limitation.)
One possibility I've played around with is having a high-pitched chromatic scale ascending very rapidly. This is not really louder but it is more noticeable (the alert is already at 100% volume, some more RIM brain damage in not allowing developers to do what they want). I may add this as an option in a later update.
Quote:
Also having the option of the alert repeating a few times when time has run out would be great.
What I've thought about in this regard is an "annoy me" option, which will cause the alert tone to repeat continuously until manually stopped, similar to an alarm clock which has to be turned off once the alarm sounds. It could also go into a kind of "haywire" mode after a certain period of time, playing random notes all over the place instead of just repeating the same tune over and over. Anyway, this kind of thing is definitely doable in the next update.
Quote:
Just suggestions. The app is already excellent.
Thanks, glad you like it! And keep the suggestions coming (within reason, of course; I don't want to overload the thing with features to the point where it's no longer simple and easy to use).
Offline  
Old 09-25-2006, 02:05 PM   #25 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by obijohn
Quote:
The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.
Hmm, that's very odd. I'm pretty sure the 8100 uses OS version 4.2, could you check your version for me? The tone and vibrate functions should work on all OS versions 4.0 and up, at least according to the API docs. I don't know what the problem could be. Please double-check your OS version for me and I'll start digging around the API documentation for 4.2 and see if I can figure out what the problem might be.
I just pulled up the 4.2 API docs, and the routines I use to play the tone and vibrate have definitely not changed, and in fact the 4.2 API says they are the same as 4.0. I can see no reason why it shouldn't be working. If someone else who has the new 8100 could try it out for me and verify there is a problem, I'd appreciate it!
Offline  
Old 09-25-2006, 02:23 PM   #26 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by obijohn
I just pulled up the 4.2 API docs, and the routines I use to play the tone and vibrate have definitely not changed, and in fact the 4.2 API says they are the same as 4.0. I can see no reason why it shouldn't be working. If someone else who has the new 8100 could try it out for me and verify there is a problem, I'd appreciate it!
Okay, I downloaded the 8100 Simulator (for some reason it wasn't included in the Simulator Pack for the JDE), and the alerts, both tone and vibrate, all work fine. Are you sure you didn't have your phone on silent mode?
Offline  
Old 09-25-2006, 04:56 PM   #27 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Well i had on quiet profile but just changed to normal and didn't hear anything.
version is 4.2.0.42

I have a stopwatch program that I load via alx and it works but it would be nice IMO to just have one program be able to count up or down for me.
You could just have a radio button that has Timer Mode and one that says Stopwatch mode. When it stopwatch mode T-Minus could say t-plus or time and Start timer button could just say start no matter what mode you are in.

ANYONE ELSE WANT THIS FUNCTIONALITY?
Offline  
Old 09-25-2006, 06:10 PM   #28 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Inphektion
Well i had on quiet profile but just changed to normal and didn't hear anything.
version is 4.2.0.42
It works perfectly in the 8100 Simulator (the Simulator even "shakes" when it vibrates). In the simulator, on the device itself, I went to Options->About and it says "v4.2.0.42 (Platform)" so I don't know what to tell you about why yours isn't working.

If someone else who has an 8100 could confirm that the tone and vibrate either work or don't work, I really would appreciate it. This is bugging the heck out of me right now, because everything on my end says it should work on the 8100.

Quote:
I have a stopwatch program that I load via alx and it works but it would be nice IMO to just have one program be able to count up or down for me.
You could just have a radio button that has Timer Mode and one that says Stopwatch mode. When it stopwatch mode T-Minus could say t-plus or time and Start timer button could just say start no matter what mode you are in.

ANYONE ELSE WANT THIS FUNCTIONALITY?
If I implement a "count up" option, it would either: A) stop when it reaches the time entered in the time entry field, in which case alerts would still work; or B) only stop when you click the Pause/Stop button, as a regular stopwatch does, in which case it could continue indefinitely and alerts would make no sense in that context, and neither would the main time entry field.

Option A is certainly doable, but not very useful for a general-purpose stopwatch. Still, if all you want to do is time something, and you know in advance that it's not going to take longer than X amount of time, you could enter that maximum value of X in the time entry field and then the "count up" option would function as a simple elapsed-time indicator. However, the timer would still stop on its own when it reaches that maximum value of X in the time entry field (and play alerts if they were enabled). This option is fairly easy to implement.

On the other hand, option B begins to add a level of complexity to the app that I was trying to avoid, even though it may not appear that much different on the surface than option A.
Offline  
Old 09-25-2006, 07:42 PM   #29 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yea i'm not running races. Most things I need a stopwatch for are under 5 minutes. I could always use the countdown timer entering like 6000 and go from there but just though it would be nice to add stopwatch functionality. Not a big deal though if it is a hassle in any way. I'll keep messing with the alerts and profiles see if i can get it to work.
Offline  
Old 09-26-2006, 10:30 PM   #30 (permalink)
Thumbs Must Hurt
 
anesone's Avatar
 
Join Date: May 2005
Location: Houston, TX
Model: 9530
Carrier: Verizon
Posts: 89
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I tried out the countdown timer and had a problem.
The final countdown doesn't go off for me. I have my profile set to Normal.
I have the timer set to 500, Alert 1 set to 400, alert 2 set for 100, and Vibrate and Restore are checked. Alerts 1 and 2 work fine (short vibration), but the final alert does not do anything. It does restore, but no vibration. When I check the Tone option, Alerts 1 and 2 only trigger a tone (no vibrate), but the final alert does sound a tone and vibrates.

I have an 8700g, OS4.1.0.284.

Any thoughts as to why vibrate only doesn't work?
Offline  
Old 09-27-2006, 06:01 AM   #31 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by anesone
I tried out the countdown timer and had a problem.
The final countdown doesn't go off for me. I have my profile set to Normal.
I have the timer set to 500, Alert 1 set to 400, alert 2 set for 100, and Vibrate and Restore are checked. Alerts 1 and 2 work fine (short vibration), but the final alert does not do anything. It does restore, but no vibration. When I check the Tone option, Alerts 1 and 2 only trigger a tone (no vibrate), but the final alert does sound a tone and vibrates.

I have an 8700g, OS4.1.0.284.

Any thoughts as to why vibrate only doesn't work?
First, there is a stupid bug with the "vibrate only" setting. This is probably what you're describing. It is fixed in the latest update (version 0.5) which I should be uploading some time this morning.

Second, setting Alert 1 to 400 and Alert 2 to 100 wouldn't work with the timer set at 500. The alerts don't have a "seconds" part, so your setting would have Alert 1 sounding at the 4-hour mark, and since the main timer starts at 5 minutes it would never sound. But since you got the short vibration that they make in a "vibrate only" mode, I assume you have them set to 4 and 1, right? Or maybe you had Repeat Every set to 1?

Also, the secondary alerts do not vibrate unless the main alert is "vibrate only". This is a feature, not a bug. The reasoning behind having them "tone only" unless the main alert is "vibrate only", is that you could have the main timer set at (for example) 2 hours, with the repeating alert set to go off every minute, and it would probably not be very good for your device to have it vibrate 120 times in the span of 2 hours. I supposed I could have tone and vibrate settings for each secondary alert, but I didn't want to clutter things up with that many options.

Anyway, the first vibrate problem you described has been fixed in version 0.5. There are a couple of new features as well, so you might want to upgrade when I post it.
Offline  
Old 09-27-2006, 09:39 AM   #32 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I got an "uncaught exception" today.
Looking at the log on the pearl it had this:
Code:
Name: NumberFormatException
GUID: 9c3cd62e3320b498
Time: Sep 27, 2006 07:28:42
No detail message
net_rim_cldc-9
 NumberUtilities
 parseInt
 0x6C5B
net_rim_cldc
 Integer
 parseInt
 0x7365
net_rim_cldc
 Integer
 valueOf
 0x73AE
CountDown
 CountDown
 fieldChanged
 0xED
net_rim_cldc-5
 Field
 fieldChangeNotify
 0x1BE6
net_rim_cldc-7
 ButtonField
 trackwheelClick
 0x5816
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Screen
 trackwheelClick
 0x815A
net_rim_cldc-6
 Screen
 dispatchNavigationEvent
 0x6A58
net_rim_cldc-6
 UiEngineImpl
 processMessage
 0xA99D
net_rim_cldc-4
 Application
 processNextMessage
 0xEE3
net_rim_cldc-4
 Application
 enterEventDispatcher
 0x6A0
CountDown
 CountDown
 main
 0x567
Offline  
Old 09-27-2006, 09:42 AM   #33 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Also the main alert works I just can't get the intermediate ones to do anything.
Offline  
Old 09-27-2006, 01:30 PM   #34 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Inphektion, the exception you saw was probably caused by pressing the Start button with a blank timer or alert field. This bug has been fixed in version 0.5 (just uploaded). Also, make sure your secondary alert times don't contain seconds (i.e., an alert time of 400 would be 4 hours, not 4 minutes). Anyway, install the new version and let me know if you still have any problems.

Version 0.5 also fixes a couple of other bugs (two little ones, and the "vibrate only" bug mention in a previous post). It also adds a couple of features, including an "elapsed time" mode, and an optional fast-and-high-pitched alert tune.
Offline  
Old 09-27-2006, 03:26 PM   #35 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Inphektion, I notice you mentioned you ran it on a Pearl, so I switched back over to the 8100 simulator. Everything seems to work fine, the secondary alerts sound when they are supposed to, no random crashes, etc. But danged if the display doesn't wrap part of the "Elapsed" checkbox. *Pfft*. I'm uploading a quick update which takes the narrower display into account. I thought the display was the same size on the 8100 as the 7100. Oh well.

I've posted an update (0.5.1) to fix this display issue on the Pearl.
Offline  
Old 09-27-2006, 03:37 PM   #36 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

With the latest release (0.5.1) all the features which have been suggested that I think should be included are there, and most of the major bugs have been ironed out (I think, I hope). I don't plan on adding any new features, unless someone suggests something that is glaringly absent or obvious, and instead I will concentrate on fixing any bugs or issues that pop up on the various models and OS versions which are floating around.

Anyone who has mentioned or noticed a problem/bug in the past, please update to 0.5.1 and let me know if the problem is resolved in this release.

Thanks everyone!
Offline  
Old 09-27-2006, 04:58 PM   #37 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

ahh. I finally get it.
I had startT at 200 and then alert at 100 or 30.
with startT at 230 and then alert at 2 and second alert at 1 it works. There is no description in the fields that format for time changes between start T and the alerts. Can you make alerts same format as startT so I can have an alert at 30 seconds? Or if you don't want to make any major changes can you label that the alert needs to be in minutes not seconds like startT?

If i put in 6000 to get one hour, hit pause, reset and start the startT time changes to 10000 and then counts down correctly starting with 5959. Weird. What is the max time supported? is 5959 the max?
If I put in 9000 to do an hour and a half it starts counting down from 13000...

clearly i'm all confused with the time entry here but I think others would be too then.
Offline  
Old 09-27-2006, 05:02 PM   #38 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

ok i see. 13000 is really 1:30:00 in HH MM ss.
and the alert field is HH MM no seconds, correct?
so in alert field if i entered 129 it would alert after 1 minute with the above start time?

I get it now and its completely useable but there has to be a way to make this easier for someone who just installs it and wants to use it.
Offline  
Old 09-27-2006, 05:28 PM   #39 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Model: 7100t
Carrier: T-Mobile
Posts: 71
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Inphektion
ahh. I finally get it.
I had startT at 200 and then alert at 100 or 30.
with startT at 230 and then alert at 2 and second alert at 1 it works. There is no description in the fields that format for time changes between start T and the alerts. Can you make alerts same format as startT so I can have an alert at 30 seconds? Or if you don't want to make any major changes can you label that the alert needs to be in minutes not seconds like startT?

If i put in 6000 to get one hour, hit pause, reset and start the startT time changes to 10000 and then counts down correctly starting with 5959. Weird. What is the max time supported? is 5959 the max?
If I put in 9000 to do an hour and a half it starts counting down from 13000...

clearly i'm all confused with the time entry here but I think others would be too then.
Okay, maybe I should explain it better in the docs. Basically, the time value you input into the main time entry field ("Start T") is corrected for you if it doesn't match the format a clock would use (HHMMSS). That's why when you input 6000 for 1 hour, it converts it to 10000 at the start of the count down. A clock would never display 1 hour as 60 minutes, it would display it as 1:00:00. After 1 second has elapsed, the current time would be 59 minutes 59 seconds remaining, which is what you saw happen. I guess I thought this would be fairly intuitive, maybe I was wrong.

And yes, if you input 9000 it would be converted to 1 hour 30 minutes, because a clock wouldn't display 1 hour 30 minutes as 90. My microwave does this too when I enter 90 seconds (converts the display to 1 minute 30 seconds) so I didn't think it would be that confusing.

I guess adding to the confusion is the fact that the secondary alerts don't use seconds (entering 10 here is read as 10 minutes, not 10 seconds). Both of these decisions were made with the idea of entering values quickly. I figured that no one would want an alert to repeat every 2 seconds.

FAIR WARNING! If this continues to be a problem for people, I will change the secondary alert format to include seconds, although this may cause problems for people who are used to the current format.

The maximum time is 9999 hours 59 minutes 59 seconds (1 second shy of 10,000 hours; well over 1 year). Now that you mention it, I don't really check against this maximum value since I figured no one would actually try to input a time that large, but I probably should. If you tried to input 9999 hours, 99 minutes, 99 seconds, it would cause an overflow since it's more than 10,000 hours. I see a version 0.5.2 around the corner to catch this...
Offline  
Old 09-27-2006, 06:10 PM   #40 (permalink)
Thumbs Must Hurt
 
anesone's Avatar
 
Join Date: May 2005
Location: Houston, TX
Model: 9530
Carrier: Verizon
Posts: 89
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by obijohn
First, there is a stupid bug with the "vibrate only" setting. This is probably what you're describing. It is fixed in the latest update (version 0.5) which I should be uploading some time this morning.

Second, setting Alert 1 to 400 and Alert 2 to 100 wouldn't work with the timer set at 500. The alerts don't have a "seconds" part, so your setting would have Alert 1 sounding at the 4-hour mark, and since the main timer starts at 5 minutes it would never sound. But since you got the short vibration that they make in a "vibrate only" mode, I assume you have them set to 4 and 1, right? Or maybe you had Repeat Every set to 1?

Also, the secondary alerts do not vibrate unless the main alert is "vibrate only". This is a feature, not a bug. The reasoning behind having them "tone only" unless the main alert is "vibrate only", is that you could have the main timer set at (for example) 2 hours, with the repeating alert set to go off every minute, and it would probably not be very good for your device to have it vibrate 120 times in the span of 2 hours. I supposed I could have tone and vibrate settings for each secondary alert, but I didn't want to clutter things up with that many options.

Anyway, the first vibrate problem you described has been fixed in version 0.5. There are a couple of new features as well, so you might want to upgrade when I post it.

You are correct...I did have Alert 1 set to 4 and Alert 2 to 1. I look forward to testing out the new version. Great app btw.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.