RealTimeClockListener

Similar Questions

• How to use RealtimeClockListener

  I hv used this code to get the time every minute works very well it give me time to evry minute but if I close the application, then it does not work, I mean after the app how would this code in background.to get closing time

  SerializableAttribute public class BackgroundApp extends UiApplication implements RealtimeClockListener
  {
  /**
  * Entry point for application
  @param args command-line arguments (not used)
  */
  public static BackgroundApp PAP = null;
  Public Shared Sub main (String [] args)
  {
  Create a new instance of the application and make the currently
  who runs the thread of the application of the event dispatch thread.
  PAP = new BackgroundApp();
  theApp.enterEventDispatcher ();
  }

  /**
  * Creates a new object MyApp
  */
  public BackgroundApp()
  {
  Push a screen onto the stack in the user interface for rendering.

  addRealtimeClockListener (this);
  }

  public void clockUpdated() {}
  int h is Calendar.getInstance () .get (Calendar.HOUR_OF_DAY);.
  int minute = Calendar.getInstance () .get (Calendar.MINUTE);
  System.out.println(""+Hour+":"+minute);

  }
  }

  You need:

  .addRealtimeClockListener ();

  Please, next time, debug it, and tell us that the method has been called not in the first Post.

• RealtimeClockListener clockUpdated does not

  Hey. Thanks for all help people, maybe it's my last Q for quite awhile, I hope: I implemented a RealtimeClockListener like this, but the clockUpdated method does not work (initially tried to use a Timer, but my past app on startup and exits, so I need something that can continue in the background after I got out of the app) as I did with my addPhoneListener).

  Any ideas appreciated (pl explain in detail, even with the code examples? -

  ... excerpt begins...
  MonthlySpend ms = new MonthlySpend();
  ms.addRealtimeClockListener (new ClockListener());
                          
  }
  }
  }
    
  / public static class ClockListener implements RealtimeClockListener
  {
         
  public ClockListener() {System.out.println ("\n\n\nNew ClockListener\n\n\n") ;}
         
         
  Public Sub clockUpdated()
  {
  System.out.println ("\n\n\nAnother minute passed\n\n\n");
             
             
  }
  }

  ... from end...

  I am in general agreement with Martin, but I think that the earpiece of the phone could stay, but you'll certainly use your RealtimeClockListener.

  You're supposed to leave applications running?  Good question. in your case, because you want to use the RealtimeClockListener, you don't have the choice.

  If you do as suggested and make your app a module system and the autostart, it starts and can do its thing.  However, there will be an icon.  Despite this, as I suspect that you have extended UiApplication, there will be an icon in the Task Switcher.  Unless you raise a screen at the beginning, someone select this will see a blank screen. If you can push your Options screen (at startup) and then have someone select via the Task Switcher if they want to change your Options.  You must pay attention to requestBackground rather than System.exit (.).

  You can also try to set requestForeground to false in your UiApplication, which he will hide the Task Switcher, but I'm not sure of the utility that is in fact in your case.

  Alternatively, rather than extend UiApplication, you can extend the Application.  Now you lose the icon on the Task Switcher, but as a result, you also lose the ability to have a screen that is associated with your application.  If you do this, then watch the OptionsProvider API, you can add your Options to the standard BlackBerry Options screen.

  Anyway, the easiest thing for you to do immediately is not to distinguish the Autostart and the start icon.  If you do this, when your application starts with the reset of the device, it will stay there with in the background, the screen Options.  When you use the icon (or TaskSwitcher), it will display your options.  Make sure that you do not leave it.  This mans removing alternative entry and the system.exit() at startup.  To do this, and you should see all this work.  Then you can play round with how you want to handle the User Interface.

  Hope it makes sense.

  Edit for clarification

• Refreshing BlackBerry maps

  
  

  Here is an example of code that I wrote a few days back...

  I used RealTimeCloclListener which is used to update the location of every minute...

  public class MappingFieldSelfTrial extends UiApplication implements RealtimeClockListener{
  
          /**
           * Pushes the main screen onto the display stack
           */
      private double DEFAULT_LAT = 45.504512;
      private double DEFAULT_LONG = -73.557029;
      private RichMapField map = MapFactory.getInstance().generateRichMapField();
      private MapDataModel Mapdata = map.getModel();
      private MapLocation julieHome = new MapLocation( DEFAULT_LAT, DEFAULT_LONG, "Julie - Home new", "Home" );
          public MappingFieldSelfTrial() {
                  pushScreen(new RichMapScreenTest(DEFAULT_LAT,DEFAULT_LONG));
                  this.addRealtimeClockListener(this);
          }
  
          /**
           * Main Entry point for the application
           */
          public static void main(String[] args) {
                  MappingFieldSelfTrial myClass = new MappingFieldSelfTrial();
                  myClass.enterEventDispatcher();
  
          }
  
          public void clockUpdated() {
  
              DEFAULT_LAT = DEFAULT_LAT+ 1; // new location latitude
              DEFAULT_LONG = DEFAULT_LONG+1; // new location longitude
              UiApplication.getUiApplication().invokeLater(new Runnable()
              {
                  public void run() {
                     Dialog.alert("Timer alert"+DEFAULT_LAT);
                  }
              });
              Mapdata.removeAll();
              setLocation(DEFAULT_LAT,DEFAULT_LONG);
          }
  
          private void setLocation(double DEFAULT_LAT, double DEFAULT_LONG ){
              julieHome.setLat(DEFAULT_LAT);
              julieHome.setLon(DEFAULT_LONG);
              Mapdata.add((Mappable) julieHome );
              map.getMapField().update( true );
          }
  
  private class RichMapScreenTest extends MainScreen {
  
      /**
       * The map field that will be displayed on the screen.
       */
      RichMapScreenTest(double DEFAULT_LAT, double DEFAULT_LONG) {
  
              add(map);
  
              Mapdata.add((Mappable) julieHome );
              map.getMapField().update( true );  // To automatically update zoom and center point
      }
  }
  }
  

• Stall network detection

  Currently, I'm trying to understand how to implement a network dropout detector in my application.  I use HTTP and so often keep a socket opened for a long time and do a lot of things on it.  Therefore, a random network dropping out really hurts to ease of use and I need to address without delay as the BONE to cause a timeout.  I was wondering if anyone could share any advice or code on how best implemented it.  I know that Peter has mentioned something himself, of course anything either would be useful.

  I thought a lot lately about the different ways that I could approach this problem:

  The simplest way possible, in theory, would be a kind of timer.  I would like to start it at the beginning of any sequence of operations of e/s, and "kick after (possibly before) each successful socket read or write."  The problem is that there is no effective obvious way to do it with the BlackBerry API.  (at least not without coarse abuse TimerTask.)

  Another option would be to have a TimerTask that runs whenever the is open, controls a set of variables on regular intervals.  I would update these variables around every success in reading/writing, and it could make its conclusions on this basis.  Of course, this raises a lot of questions on what the TimerTask interval should be, when start/stop, etc..

  Any thoughts/ideas?

  For a general watchdog, I use RealtimeClockListener.  But he gets only a kick every minute which is probably too long for the detection of dropping out of your network.  But you can use it to make sure that your stall network Detection still works.

  Personally, I have a dislike of timers because they seem to be just the threads with time management, handling I can do myself.

  And that's what I would do in this case.  I understand that you don't need that level of detail, but I'll put it in other players who are maybe not as clever as you are.

  I would like to have a watchdog thread, in a shared storage (probably RuntimeStore), all the time.  It has two States, while waiting for a timeout and idle.  In both States, she waits on the synchronized object StallDetection (I just made that name, it's just an object).  He uses wait/notify on this object to tell the Thread to do some work.

  This thread has two special methods, startTimeout() and cancelTimeout().

  Use Thread will startTimeout on this thread, through Assembly and time-out interval.  This startTimeout method will set the timeout and save the connection object, and then notify the StallDetection object.  This will give the wire in life, ii will find that it has a connection, but the timeout did not, then he will change his timeout so that he wakes up in the time limit.

  Now, there are only two possible situations:

  (a) the network Thread called cancelTimeout to cancel the timeout, because it has a good answer.  cancelTimeout clears the connection just waiting for the Thread.  When the thread wakes up, he'll find the elapsed wait time, but there is no connection to cancel, so it will be simply define another timeout, in the distant future and wait again.

  (b) the network Thread is suspended and does not cancel the timeout.  Then the Thread will wake up and see there is a link to cancel and cancel.

  It is essentially an implementation of a timer, without start-up costs and stop all the time.  I think it's better in your situation where you have a network of Red wire all the time.  But perhaps not an ad hoc http connection.

  Rather than use the two methods on the Thread, it should probably put up a model of the observer and so could be useful for a number of other situations.

  I would use the RealtimeClockListener to just check this thread is alive (isAlive()), then start it again if not.

  I would be interested in other options if people have other ideas and of course improvements on this!

  And I hope this helps.

• How to access my application UI of another point of entry?

  I have a user interface with another application entry point. In the other entry point, I put the fix times and always check this time around (using RealTimeClockListener). If the smartphone to go at this time, it will grow a screen of my application user interface. And he pushed successfully. In this screen have an ex "New button" button, usually when I run my application user interface and click it, it will push a new screen.  But in this case, when the screen is pushed to the other entry point, I can't do action on this screen, I click on "new"button and no display of thing...

  How can I solve this problem?

  You can use a shared in the store of runtime service. or after a global event.
  ApplicationManager allows to validate a global event and register a GlobalEventListener with your application class to listen to it.

• How can I update time and show it.

  I have to show the current time in a tab in my application...

  my date format is hour: minute (hh: mm)

  Show I want to upadte my dateField in every minute...

  How can I do this... I don't want to use wire...

  BlackBerry API has a RealTimeListenerinterface...

  It has a clockUpdate() function

  I can solve my problem with this interface...

  Help, please...

  Or if you know how to do it with wire you can also answer...

  The RealtimeClockListener interface is the perfect tool for this.

  Here is a snippet of code showing how you can use this to a DateField.  Note how the listener is added when the field is displayed and removed when it is not.  Code is not compiled, probably syntactically incorrect, but I hope you get the idea.

  public class updatingdatefield extends DateField implements {RealtimeClockListener}

  ....

  public void onDisplay() {}

  Application.getApplication () .addRealtimeClockListener (this);

  }

  public void onUnDisplay() {}

  Application.getApplication () .removeRealtimeClockListener (this);

  }

  public void clockUpdated() {}

  final UpdatingDateField myDateField =;

  UiApplication.getUiApplication () .invokeLater (new Runnable() {}

  public void run() {}

  myDateField.setDate (System.currentTimeMillis ());

  });

  }

  I would avoid using timer for this.  This one uses just one wire under the covers in any case!

• TimerTask

  I have an application that I want to add a background process that needs to execute a task once per day. I studied with the help of another point of entry with a RealtimeClockListener and also just begin a TimerTask with a schedule fixed. Any advice? RealtimeClockListener is called each minute, so it seems best to use a TimerTask. If I leave a TimerTask to my main application and the farm of the app, is the TimerTask always configured to run? Do I have to reprogram the TimerTask at each reboot of the device even with a schedule fixed or the BB OS does that automatically? Operating of the TimerTask, is the UiApplication market too so that I can access it from within the TimerTask?

  EDIT: Read further, seems that a timer is executed in a thread of the application, so I want another entry point again and put my TimerTask in there, correct?

  Thank you

  You can use http://www.blackberry.com/developers/docs/7.1.0api/net/rim/device/api/system/ApplicationManager.html... long, boolean) to schedule an application to run at a specific time.

• How we prevent frim backlight dimming (maybe crazy Blackberry that the interaction that happened?)

  I have an app that for long periods of time the user watches the screen,

  But even I put the backlight for the maximum wait time, it's not enuff.

  Is there a way to prevent the screen from dimming or is there a work-around, like cheating the blackberry into thinking that the entry that's happened?

  I guess you can get slowed down information DeviceInfo, but this does not dimming of light... I thought to repeat a call to activate the backlight all 255 seconds... but is it necessary to have a thread that loop just never do this?

  My apologies, I missed that.

  If I was going to this, I would touch reset in an RealTimeClockListener interface.  This is called every minute, so you don't need to have your own Thread.

  But before coming to the RealTimeClockListener to do, I'll make sure he has the permission to do so, using ApplicationPermissions.  I recommend that you don't ask for permission on update() RealTimeClockListener code, but use

  UiApplication.getUiApplication () .invokeLater (...);

  (not invokeAndWait to seize the eventLock, as he will pick up this treatment) to initiate the treatment that he asked.

  That seems like a better approach?

• Creating Application reminder

  For all developers,.

  I am trying to create demand for reminder, reminder of anniversaries.  Here's my problem:

  1 record the event

  How can I record the event and to check when to fire a reminder to the user? He's using PIM or Todolist?

  2. display the customized reminder dialog box

  I learn about PIM for calendar of the event or ToDoList, but the problem is when the callback is triggered, it shows the Calendar dialog box or a task request task. I want to show my custom dialogue box to remind the user when the callback is triggered. How can I do?

  Thank you for your answers

  http://www.BlackBerry.com/developers/docs/7.1.0api/NET/rim/device/API/system/RealtimeClockListener.h...
  Add it by calling
  http://www.BlackBerry.com/developers/docs/7.1.0api/NET/rim/device/API/system/application.html#addRea...

  save it to the system and it is called every minute, so you can control every minute if your event is on. As it is called very often the treatment should be inexpensive, of course.

  You can configure a different entry point to give your application a part of background process that would deal with the audit:
  http://supportforums.BlackBerry.com/T5/Java-development/set-up-an-alternate-entry-point-for-an-appli...

  When the time is right you could display a global dialog as an alert and open your main application a confirmation key, for example.

• On-screen display clock

  Hello guys

  What is the best way to display a digital clock on the title screen? I know that there is no api available, but it should how to display the current time on the screen.

  Thank you very much

  Nitin

  On the screen, have a DateField created with DateField.TIME and DateField.READONLY.

  In your method of application, implement RealTimeClockListener and clockUpdated().

  In the clockUpdated, have something like this:

  public void clockUpdated() {
    final Date now = new Date();
    UiApplication.getUiApplication().invokeLater(new Runnable() {
      public void run() {
        myDateField.setDate(now);
        invalidate();
      }
    });
  }
  

  It's just one of the ways to do this - I gives the general idea, you can improve on it, as desired, with the help of other fields, play with the format (take a look at the DateFormat constructor parameter of the DateField), etc.

  If you need a better granularity of one minute, implement a TimerTask and plan at intervals you want rather than using RealTimeClockListener.

• Questions about the functionality of callback and SMS?

  
  

  You must first create a background application. Therefore extend the Application class. Then, you already said you use persistence. DateTimeUtilities comes in very handy when handling / comparison of DateTime. Then implement the RealTimeClockListener that is raised every minute to check if the date is a specific date in your persistence. Or you can use TimerTask and trigger every hour or every 24 hours. To warn the user of your application to background:

  synchronized(Application.getEventLock()){    UiEngine ui = Ui.getUiEngine();
      Screen screen = new Dialog(Dialog.D_OK, "Look out!!!",
          Dialog.OK,           Bitmap.getPredefinedBitmap(Bitmap.EXCLAMATION),         Manager.VERTICAL_SCROLL);
      ui.pushGlobalScreen(screen, 1, UiEngine.GLOBAL_QUEUE);
  }
  

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800332/800505/800608/...

• Drain the battery... need some advice

  I have an application that runs in the background and runs at every 15,30,60 min based on what the user has configured for. I made a quick call to a Web site gets a little info and then farm the connection. I have a realtimeclocklistener to track the number of minutes configuration is passed since the last update.

  The problem is the same when it is updated every 60 minutes just, he sits there and drains the battery life. Also the connection arrows top right will go up randomly even after that he made the update. I don't know if it's just consciousness or if that is the question.

  Here is the code I am accounting for the data

      public void retrieveData(){
          //Vars
          HttpConnection httpConn = null;
          OutputStream os = null;
          DataInputStream is = null;
          StringBuffer sb = null;
          String separator = "|";
          int chr;
          int index;
          synchronized(this){
              try{
                  httpConn = (HttpConnection)Connector.open(myURL, Connector.READ);
                  httpConn.setRequestMethod(HttpConnection.GET);
                  httpConn.setRequestProperty("Content-Type", "text/plain");
                  if(httpConn.getResponseCode() == HttpConnection.HTTP_OK){
                      //Vars
                          os = httpConn.openOutputStream();
                          os.flush();
                          sb = new StringBuffer();
                          is = httpConn.openDataInputStream();
                          while ((chr = is.read()) != -1) { sb.append((char) chr); }
                          String response = new String(sb.toString().getBytes(),"UTF-8");
                          Vector nodes = new Vector();
                          index = response.indexOf(separator);
                      //Code
                      while(index>=0) {
                          nodes.addElement( response.substring(0, index) );
                          response = response.substring(index+separator.length());
                          index = response.indexOf(separator);
                      }
                      nodes.addElement( response );
                      String[] result = new String[ nodes.size() ];
                      if( nodes.size()>0 ) {
                          for(int loop=0; loop
  I watched a lot of samples and other code online, and I don't see anything wrong with my code.
  Any help will be much appreciated.
  			 
  That everything seems OK to me.  I would be very surprised if this empty code battery a lot, especially if he did invoke every 60 minutes.  Sure that it does not have anything in your RealtimeClockListener you treat?  Also makes the Thread performing the closing down?  It would seem that you could drive this treatment completely out of the RealtimeClockListener, just start the Thread when you want.  If you did that, then I think that your application would have a minimal impact on the battery.
  		   

• Day of Calendar Code Base

  I want to have a certain function to be executed at a given time on a certain day of the week (choice of users)

  Could be M T W T F S S or maybe M T W T F (days) + the selected time.

  Timer task is the best way to implement this in which case I have to manually manage the repitition?

  I don't see how I could do that as I would always need to plan the event for the next whenever it is run once, but if the phone is off, I suppose, that he does not know that he lack the event, in which case the entire calendar system will be broken.

  One option would be to begin the task of timer for every single week day (i.e. a timer for Monday, another for Tuesday etc. for everyday you need to). This timer task repeats every 7 days.

  Another option would be to implement the RealtimeClockListener and check that each minute if certain conditions are met, then you can run the appropriate code

• Location provider gel...

  Hi all

  Here is my problem, I have a great app must locate a Blackberry all the time, when possible. I made one to or 4.5 and knit perfectly until the OS6.0. So I did another in the OS6.0 with new features. The problem is at the same time (after 12 hours of work, maybe more, the locationProvider seem, unable to restore properly and not give rise more.)

  Here a part of the code,

  /** BlackBerryLocationProvider instance */
  private BlackBerryLocationProvider bbProvider = null;
  /** Reference to current BlackBerryLocation */
  private BlackBerryLocation bbLocation = null;
  
  /**
     * Initializes criteria according to the modes selected by the user.
     */
    private void SetupCriteria() {
      m_modeAutonomous=false;
      m_recoitPosition= false;
  
      bbCriteria = new BlackBerryCriteria();
      bbCriteria.setPreferredResponseTime(RESPONSE_TIME);
  
      bbCriteria.enableGeolocationWithGPS(BlackBerryCriteria.FASTEST_FIX_PREFERRED);
  
      bbCriteria.enableGeolocationWithGPS();
      int i= 0;
      while(i < 20) {
        i++;
        try {
          int cpt=0;
          while (!LocationInfo.isModeAvailable(GPSInfo.GPS_MODE_ASSIST) &&
                 !LocationInfo.isModeAvailable(GPSInfo.GPS_MODE_CDMA_MS_BASED) ) {
            if(cpt>5) break;
            //ClLog.instance().Ajouter("MODE pas encore actif");
            ClUtil.Pause(2);
            cpt++;
          }
  
          if(LocationInfo.isModeAvailable(GPSInfo.GPS_MODE_ASSIST)) {
              ClLog.instance().Ajouter("BB Critere Depart : Assist");
              bbCriteria = new BlackBerryCriteria(GPSInfo.GPS_MODE_ASSIST);
          } else {
            if(LocationInfo.isModeAvailable(GPSInfo.GPS_MODE_CDMA_MS_BASED)) {
              ClLog.instance().Ajouter("BB Critere Depart : CDMA MS Based");
              bbCriteria = new BlackBerryCriteria(GPSInfo.GPS_MODE_CDMA_MS_BASED);
            } else {
              ClLog.instance().Ajouter("BB Critere Depart : Autonomous");
              bbCriteria = new BlackBerryCriteria(GPSInfo.GPS_MODE_AUTONOMOUS);
            }
          }
  
          break;
        } catch(Exception e) {
          //ClLog.instance().Ajouter("TropVite...5 Sec");
          ClUtil.Pause(5);
        }
      }
    } // setupCriteria  
  
  private void setupProvider() {
      try {
  
        bbProvider = (BlackBerryLocationProvider)LocationProvider.getInstance(bbCriteria);
  
  if (bbProvider != null) {
          int frequency = (!m_recoitPosition)?2:5;
          int timeout = -1;
          int maxage = -1;
          bbProvider.setLocationListener(new CiLocationListener(), frequency, timeout,maxage);
        } else {
  Criteria");
        }
      } catch (Exception e) {
        ClLog.instance().Ajouter(e.toString());
      }
    } // setupProvider
  

  and update the location

  /**
    * CiLocationListener implementation
    */
    private class CiLocationListener implements LocationListener {         
  
      public void locationUpdated(LocationProvider provider, final Location location) {   
  
        //ClLog.instance().Ajouter("BB locationUpdated");
        bbLocation = (BlackBerryLocation)location;
  
        if (bbLocation.isValid()) {
          //ClLog.instance().Ajouter("VALID"); 
  
          try {
            //g_application.AfficherPosition(bbLocation);
            PositionNotify(bbLocation);
          } catch(Exception e) {
            ClLog.instance().Ajouter("Impossible d'afficher la position : " + e.toString());
          }
  
          if(!m_recoitPosition) {
            m_recoitPosition=true;
            setupProvider();
          }
        } else {
          //ClLog.instance().Ajouter("INVALID"); 
  
          if(m_resetNow){
            resetProvider();
  
            if(m_modeAutonomous){
               SetupCriteria();
            }else{
              SetupCriteriaAutonomous();
            }
  
            setupProvider();
  
            return;
          } else {
            if(m_nbEchec < 5) {
              m_nbEchec+=1;
              ClLog.instance().Ajouter("Invalid fait rien");
            } else {
              // on reset le provider
              m_nbEchec=0;
              m_resetNow= true;
            }
          }
        }
      }
  

  I do not use the providerStateChanged because some mobile have difficulty to raise notify State of prodider properly...

  I don't know why the supplier freeze and how to reset it for good.

  I use the standard discount provider, but he seems not enough.

  private void resetProvider() {
      ClLog.instance().Ajouter("Resetting LocationProvider");
      bbProvider.reset();
      bbProvider.setLocationListener(null, -1, -1, -1);
      bbProvider = null;
      m_resetNow=false;
    }
  

  If someone has a queue or a suspicion comment please, I'm waiting...

  I use a Bold 9780 OS 6 and also a Curve 9300 OS6.0

  I thank in advance.

  PS. What is the procedure to contact RIM directly to helping help?

  Not quite.

  App starts up, between the Dispatcher and starts a Thread GPS Manager.

  (1) GPS Manager Thread attempting to get a location, directly (without using the listener location), it will timeout or work.  If it expires, the treatment will be just to wait a little longer and then try again.

  (2) when operating, GPS Manager starts a listener in location (separate category) and then waiting.  He wakes informed or after 3 minutes (for example)

  (3) the listener location add places to a queue of places.  It can also inform the wireless GPS Manager if he thinks he needs to be reset, as in providerStateChanged.

  (4) when the GPS Manager Thread wakes up, he decides if he was awakened to reset the supplier location or just after the time interval.  If the time interval it checks only the things are going OK.  If he decides or said that GPS is need to be reset, it resets it, removes the references to the former location listener and then goes back to the setting switch (1).

  (5) separate Thread Transmission will send the locations collected in (3), the queue may perform a validation and send only those at the correct interval.

  (6) RealtimeClockListener made sure GPS Manager wire and wire are running.  Otherwise, begins just them.

  You should be able to understand RealtimeClockListener by yourself...

  Re detect when GPS is available again, there is no right answer here, as you already know.  However, I think that three minutes is too short I would go.