How to make start time and end time 12 am to 12 am?

Question

I want my step counter to display steps from 12 am to 12 am I cant find a way to that is working. I am using Google's fitness API

here's the code:

        Calendar cal = Calendar.getInstance();
        Date today = new Date();
        cal.setTime(today);
        long endTime = cal.getTimeInMillis();
        cal.add(Calendar.MONTH, -1);
        long startTime = cal.getTimeInMillis();

        java.text.DateFormat dateFormat = DateFormat.getDateInstance();
        Log.e("History", "Range Start: " + dateFormat.format(startTime));
        Log.e("History", "Range End: " + dateFormat.format(endTime));

//Check how many steps were walked and recorded in the last 7 days
        final DataReadRequest readRequest = new DataReadRequest.Builder()
                .aggregate(DataType.TYPE_STEP_COUNT_DELTA, DataType.AGGREGATE_STEP_COUNT_DELTA)
                .bucketByTime(1, TimeUnit.DAYS)
                .setTimeRange(startTime, endTime, TimeUnit.MILLISECONDS)
                .build();

        final DataReadResult dataReadResult = Fitness.HistoryApi.readData(mGoogleApiClient, readRequest).await(1,TimeUnit.MINUTES);

Answer 1

java.time

You are using terrible old date-time classes that were supplanted years ago by the java.time classes defined in JSR 310.

LocalDate

First, get the date of interest. If you want “today”, you must specify a time zone.

The LocalDate class represents a date-only value without time-of-day and without time zone or offset-from-UTC.

A time zone is crucial in determining a date. For any given moment, the date varies around the globe by zone. For example, a few minutes after midnight in Paris France is a new day while still “yesterday” in Montréal Québec.

If no time zone is specified, the JVM implicitly applies its current default time zone. That default may change at any moment during runtime(!), so your results may vary. Better to specify your desired/expected time zone explicitly as an argument.

Specify a proper time zone name in the format of continent/region, such as America/Montreal, Africa/Casablanca, or Pacific/Auckland. Never use the 2-4 letter abbreviation such as EST or IST as they are not true time zones, not standardized, and not even unique(!).

ZoneId z = ZoneId.of( "America/Montreal" ) ;  
LocalDate today = LocalDate.now( z ) ;

If you want to use the JVM’s current default time zone, ask for it and pass as an argument. If omitted, the JVM’s current default is applied implicitly. Better to be explicit, as the default may be changed at any moment during runtime by any code in any thread of any app within the JVM.

ZoneId z = ZoneId.systemDefault() ;  // Get JVM’s current default time zone.

First moment of the day

12 am to 12 am

A day does not always run from 12 AM to 12 AM!

Never assume when a day begins or ends. A day is not always 24 hours long, it can be 23, 23.5, 25, or any other number of hours dreamed up by the politicians defining the time zone. In some zones on some dates, the day may not start at 00:00, it may start at some other time such as 01:00. Let java.time determine when a day begins and ends.

Half-Open

Generally the best approach in defining a span-of-time is the Half-Open approach. In this approach, the beginning is inclusive while the ending is exclusive. This avoids the challenge of trying to determine the exact split-second end of the day. A day starts at the first moment of one date and runs up to, but does not include, the first moment of the next date.

ZonedDateTime zdtStart = ld.atStartOfDay( z ) ;  // First moment of the day as seen in the wall-clock time used by the people of a particular region as defined arbitrarily by their politicians (a time zone).
ZonedDateTime zdtStop = ld.plusDays( 1 ).atStartOfDay( 1 ) ;  // First moment of the day of the *following* date.

Epoch reference date, & granularity

The Google API for DataReadRequest.Builder::setTimeRange takes count of some granularity since some epoch reference date. Unfortunately, nether the limit of the granularity nor the epoch reference is specified – and there are many epoch references in use.

I will take a guess at seconds being the finest granularity, and guess at 1970-01-01T00:00Z being the epoch reference. This epoch is used by the java.time classes and by the terrible old java.util.Date class.

long secondsSinceEpoch_Start = zdtStart.toEpochSecond() ;
long secondsSinceEpoch_Stop = zdtStop.toEpochSecond() ;

Make your call to the API.

            …
            .setTimeRange( 
                secondsSinceEpoch_Start , 
                secondsSinceEpoch_Stop , 
                TimeUnit.SECONDS
            )
            …

---

About java.time

The java.time framework is built into Java 8 and later. These classes supplant the troublesome old legacy date-time classes such as java.util.Date, Calendar, & SimpleDateFormat.

The Joda-Time project, now in maintenance mode, advises migration to the java.time classes.

To learn more, see the Oracle Tutorial. And search Stack Overflow for many examples and explanations. Specification is JSR 310.

You may exchange java.time objects directly with your database. Use a JDBC driver compliant with JDBC 4.2 or later. No need for strings, no need for java.sql.* classes.

Where to obtain the java.time classes?

• Java SE 8, Java SE 9, Java SE 10, Java SE 11, and later - Part of the standard Java API with a bundled implementation.
  • Java 9 adds some minor features and fixes.
• Java SE 6 and Java SE 7
  • Most of the java.time functionality is back-ported to Java 6 & 7 in ThreeTen-Backport.
• Android
  • Later versions of Android bundle implementations of the java.time classes.
  • For earlier Android (<26), the ThreeTenABP project adapts ThreeTen-Backport (mentioned above). See How to use ThreeTenABP….

Answer 2

you can try like this

            Date date1 = new Date();
            SimpleDateFormat  formatter1 = new SimpleDateFormat("MMddyyyy"); 
            String format = formatter1.format(date1);
            SimpleDateFormat  formatter = new SimpleDateFormat("MMddyyyy hh:mm:ss"); 
            Calendar cal = Calendar.getInstance();
            Date today = formatter.parse(format+" 00:00:00");
            cal.setTime(today);
            long start = cal.getTimeInMillis();
            System.out.println("start time:"+start);
            Date date=formatter.parse(format+" 23:59:59");
            cal.setTime(date);
            long end = cal.getTimeInMillis();
            System.out.println("end time: "+end);

            Date tem= new Date();

            cal.setTime(tem);

            long present = cal.getTimeInMillis();

            System.out.println(present);

Answer 3

If you need the start of day, you should set it as such:

Calendar cal = new GregorianCalendar();
cal.clear(Calendar.HOUR); cal.clear(Calendar.AM_PM);
cal.set(Calendar.HOUR_OF_DAY, 0);
cal.set(Calendar.MINUTE, 0);
cal.set(Calendar.SECOND, 0);
cal.set(Calendar.MILLISECOND, 0);
// after all this we'd have the start of day.
// works good if extracted to separate method, which is the unfortunate truth of working with  old calendar classes

// minus one milli because Fit API treats includes end of range
long end = cal.getTimeInMillis() - 1;

cal.add(Calendar.MONTH, -1);
long start = cal.getTimeInMillis();

I also may suggest to import and use Joda library for this (prefer Android-specific version). Using Joda (and java.time package once Java 8 is available on Fit, with minor change), you can write equivalent code like this:

DateTime date = LocalDate.now().toDateTimeAtStartOfDay();

long end = date.getMillis() - 1;

long start = date.minusMonths(1).getMillis();