#alarmmanagement | Explore Tumblr Posts and Blogs

apphale · 3 years

Text

Top Android Projects with Source Code

This article is also going to help you if you’re an enthusiast looking forward to explore and enhance Apphale your Android skills. The reason is that we’re here to provide you the best ideas of Android Project with source code that you can choose as per your choice.

These project ideas are simple suggestions to help you deal with the difficulty of choosing the correct projects. In this article, we’ll see the project ideas from beginners level and later we’ll move on to intermediate to advance.

Android Projects with Source Code

Before working on real-time projects, it is recommended to create a sample hello world project in android studio and get a flavor of project creation as well as execution: Create your first android project

1. Calculator build a simple calculator app in android studio source code

Android Project: A calculator will be an easy application if you have just learned Android and coding for Java. This Application will simply take the input values and the operation to be performed from the users. After taking the input it’ll return the results to them on the screen. This is a really easy application and doesn’t need use of any particular package.

To make a calculator you’d need Android IDE, Kotlin/Java for coding, and for layout of your application, you’d need XML or JSON. For this, coding would be the same as that in any language, but in the form of an application. Not to forget creating a calculator initially will increase your logical thinking.

Once the user installs the calculator, they’re ready to use it even without the internet. They’ll enter the values, and the application will show them the value after performing the given operations on the entered operands.

2. A Reminder App

Android Project: This is a good project for beginners. A Reminder App can help you set reminders for different events that you have throughout the day. It’ll help you stay updated with all your tasks for the day. It can be useful for all those who are not so good at organizing their plans and forget easily. This would be a simple application just whose task would be just to remind you of something at a particular time.

To make a Reminder App you need to code in Kotlin/Java and design the layout using XML or JSON. For the functionality of the app, you’d need to make use of AlarmManager Class and Notifications in Android. In this, the user would be able to set reminders and time in the application. Users can schedule reminders that would remind them to drink water again and again throughout the day. Or to remind them of their medications.

3. Quiz Application Android Project: Another beginner’s level project Idea can be a Quiz Application in android. Here you can provide the users with Quiz on various general knowledge topics. These practices will ensure that you’re able to set the layouts properly and slowly increase your pace of learning the Android application development. In this you’ll learn to use various Layout components at the same time understanding them better.

To make a quiz application you’ll need to code in Java and set layouts using xml or java whichever you prefer. You can also use JSON for the layouts whichever preferable.

In the app, questions would be asked and answers would be shown as multiple choices. The user selects the answer and gets shown on the screen if the answers are correct. In the end the final marks would be shown to the users.

4. Simple Tic-Tac-ToeAndroid Project: Tic-Tac-Toe is a nice game, I guess most of you all are well aware of it. This will be a game for two players. In this android game, users would be putting X and O in the given 9 parts of a box one by one. The first player to arrange X or O in an adjacent line of three wins.

To build this game, you’d need Java and XML for Android Studio. And simply apply the logic on that. This game will have a set of three matches. So, it’ll also have a scoreboard. This scoreboard will show the final result at the end of one complete set.

Upon entering the game they’ll enter their names. And that’s when the game begins. They’ll touch one of the empty boxes present there and get their turn one by one. At the end of the game, there would be a winner declared.

5. Stopwatch

Android Project: A stopwatch is another simple android project idea that will work the same as a normal handheld timepiece that measures the time elapsed between its activation and deactivation. This application will have three buttons that are: start, stop, and hold.

This application would need to use Java and XML. For this application, we need to set the timer properly as it is initially set to milliseconds, and that should be converted to minutes and then hours properly. The users can use this application and all they’d need to do is, start the stopwatch and then stop it when they are done. They can also pause the timer and continue it again when they like.

6. To Do App

Android Project: This is another very simple project idea for you as a beginner. This application as the name suggests will be a To-Do list holding app. It’ll store the users schedules and their upcoming meetings or events. In this application, users will be enabled to write their important notes as well. To make it safe, provide a login page before the user can access it.

So, this app will have a login page, sign-up page, logout system, and the area to write their tasks, events, or important notes. You can build it in android studio using Java and XML at ease. Using XML you can build the user interface as user-friendly as you can. And to store the users’ data, you can use SQLite enabling the users to even delete the data permanently.

Now for users, they will sign up and get access to the write section. Here the users can note down the things and store them permanently. Users can also alter the data or delete them. Finally, they can logout and also, login again and again whenever they like.

7. Roman to decimal converter

Android Project: This app is aimed at the conversion of Roman numbers to their significant decimal number. It’ll help to check the meaning of the roman numbers. Moreover, it will be easy to develop and will help you get your hands on coding and Android.

You need to use Android Studio, Java for coding and XML for interface. The application will take input from the users and convert them to decimal. Once it converts the Roman no. into decimal, it will show the results on the screen.

The users are supposed to just enter the Roman Number and they’ll get the decimal values on the screen. This can be a good android project for final year students.

1 note · View note

jacob-cs · 7 years

Text

이미 만들어진 PendingIntent 를 삭제하는 방법

PendingIntent는 생성시에 Intent obj와 고유한 id를 parameters로 받아들이게 되는데 삭제하는 경우 이들을 이용한다.

예를 들어 AlarmManager를 이용한 PendingIntent의 경우는

아래와 같이 해결한다. ref) https://stackoverflow.com/questions/9493776/how-to-remove-already-defined-pending-intent

Rewrite the code in CancelAlarm() function

PendingIntent pintent = PendingIntent.getService(context, IDs[i], send, PendingIntent.FLAG_CANCEL_CURRENT | PendingIntent.FLAG_ONE_SHOT);

With The Same Intent send and Same Id IDs[i] and then Cancel that pintent like this,

pintent.cancel();

#pendingintent #cancel #delete #android #intent #alarm #alarmmanager

0 notes

101now · 2 years

Text

Android Background Processing [SUBSCRIBER]

<p>Learn about all the cool concepts from background processing in Android! Use the WorkManager, JobScheduler, Services, AsyncTasks and the AlarmManager.</p> <p>Learn what each concept brings to the table, and how they affect your app’s performance!</p>

View On WordPress

#Programmers

0 notes

probelalkhan · 7 years

Text

New Post has been published on Simplified Coding

New Post has been published on https://www.simplifiedcoding.net/android-scheduled-task-example/

Android Scheduled Task Example using AlarmManager

So here is another useful thing in Android Development. Today we will see an Android Scheduled Task Example using AlarmManager. Scheduling tasks sometimes are very important. For example your apps needs to execute a particular task daily at a specific time defined by the user. Then we can do it using the AlarmManager in android. So lets start.

Contents

1 Android Scheduled Task Example using AlarmManager

1.1 Creating a new Project

1.2 Building UI

1.3 Creating a Broadcast Receiver for the Alarm

1.3.1 Creating BroadcastReceiver

1.3.2 Registering BroadcastReceiver

1.4 Setting the Alarm

1.5 Android Scheduled Task Example Source Code Download

1.6 Conclusion

Android Scheduled Task Example using AlarmManager

Creating a new Project

As always we will be creating a new Android Studio Project. So here I am with my project named AlarmManagerExample.

Building UI

Inside activity_main.xml we will create the following UI. This is pretty simple we have only a TimePicker and a Button.

For the above UI you can use the following XML code.

<?xml version="1.0" encoding="utf-8"?> <RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent" android:layout_height="match_parent" android:padding="10dp" tools:context="net.simplifiedlearning.alarmmanagerexample.MainActivity"> <LinearLayout android:id="@+id/linearLayout" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_centerVertical="true" android:orientation="vertical"> <TimePicker android:id="@+id/timePicker" android:layout_width="wrap_content" android:layout_height="wrap_content" /> <Button android:id="@+id/buttonAlarm" android:layout_width="match_parent" android:layout_height="wrap_content" android:text="Set Alarm" /> </LinearLayout> </RelativeLayout>

Creating a Broadcast Receiver for the Alarm

We need a Broadcast Receiver to fire the alarm when our app is not running.

Creating BroadcastReceiver

So create a java class named MyAlarm.java and write the following code.

package net.simplifiedlearning.alarmmanagerexample; import android.content.BroadcastReceiver; import android.content.Context; import android.content.Intent; import android.util.Log; import android.widget.Toast; /** * Created by Belal on 8/29/2017. */ //class extending the Broadcast Receiver public class MyAlarm extends BroadcastReceiver //the method will be fired when the alarm is triggerred @Override public void onReceive(Context context, Intent intent) //you can check the log that it is fired //Here we are actually not doing anything //but you can do any task here that you want to be done at a specific time everyday Log.d("MyAlarmBelal", "Alarm just fired");

Registering BroadcastReceiver

We also need to register this BroadcastReceiver in the Manifest file. So here is the AndroidManifest.xml file where you need to register your receiver just before the </application> tag.

<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="net.simplifiedlearning.alarmmanagerexample"> <uses-permission android:name="android.permission.WAKE_LOCK" /> <application android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:roundIcon="@mipmap/ic_launcher_round" android:supportsRtl="true" android:theme="@style/AppTheme"> <activity android:name=".MainActivity"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity>  <receiver android:name=".MyAlarm" android:enabled="true" android:exported="true" /> </application> </manifest>

Setting the Alarm

Now the final step is setting up the Alarm. We will do this inside MainActivity.java.

package net.simplifiedlearning.alarmmanagerexample; import android.app.AlarmManager; import android.app.PendingIntent; import android.content.Context; import android.content.Intent; import android.os.Bundle; import android.support.v7.app.AppCompatActivity; import android.view.View; import android.widget.TimePicker; import android.widget.Toast; import java.util.Calendar; public class MainActivity extends AppCompatActivity //the timepicker object TimePicker timePicker; @Override protected void onCreate(Bundle savedInstanceState) super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); //getting the timepicker object timePicker = (TimePicker) findViewById(R.id.timePicker); //attaching clicklistener on button findViewById(R.id.buttonAlarm).setOnClickListener(new View.OnClickListener() @Override public void onClick(View view) //We need a calendar object to get the specified time in millis //as the alarm manager method takes time in millis to setup the alarm Calendar calendar = Calendar.getInstance(); if (android.os.Build.VERSION.SDK_INT >= 23) calendar.set(calendar.get(Calendar.YEAR), calendar.get(Calendar.MONTH), calendar.get(Calendar.DAY_OF_MONTH), timePicker.getHour(), timePicker.getMinute(), 0); else calendar.set(calendar.get(Calendar.YEAR), calendar.get(Calendar.MONTH), calendar.get(Calendar.DAY_OF_MONTH), timePicker.getCurrentHour(), timePicker.getCurrentMinute(), 0); setAlarm(calendar.getTimeInMillis()); ); private void setAlarm(long time) //getting the alarm manager AlarmManager am = (AlarmManager) getSystemService(Context.ALARM_SERVICE); //creating a new intent specifying the broadcast receiver Intent i = new Intent(this, MyAlarm.class); //creating a pending intent using the intent PendingIntent pi = PendingIntent.getBroadcast(this, 0, i, 0); //setting the repeating alarm that will be fired every day am.setRepeating(AlarmManager.RTC, time, AlarmManager.INTERVAL_DAY, pi); Toast.makeText(this, "Alarm is set", Toast.LENGTH_SHORT).show();

Now thats it you can run the application.

Now after setting the alarm even if you close your application. The method will be fired at the specified time. And you can do anything you want as a scheduled task. Right now it will do nothing and will print a message on log as you can see below.

Android Scheduled Task Example Source Code Download

If you are having some troubles doing the project. Then here is my source code for you.

Android Scheduled Task Example Source Code Download

Conclusion

So you can use AlarmManager to schedule your tasks. But remember only use AlarmManager when you really want to execute your task at a specified time. If you want to schedule tasks other than a time constraint then you should use JobScheduler. We will discuss about it in the upcoming posts.

So thats all for this Android Scheduled Task Example guys. Feel free to leave your comments if having any feedbacks or suggestions. If the post helped you please SHARE and give us a LIKE. Thank You 🙂

#AlarmManager Android #Android Scheduled Task Example

0 notes

tetbekat · 5 years

Text

تحميل تطبيق Naptime Premium - Boost your battery life over 9000% v6.8 (Pro) Apk

يعمل Naptime على تقليل استهلاك الطاقة في جهازك أثناء إيقاف تشغيل الشاشة عن طريق تمكين وظائف توفير الطاقة المدمجة في نظام Android. أسرع الخمول يعني طاقة أقل يتم استهلاكها دون داع. بشكل افتراضي ، قد يستغرق التجسس بعض الوقت حتى يعمل Naptime على زيادة سرعة هذه العملية تلقائيًا من أجلك. يمكن أيضًا تعطيل موقع بيانات W-iFi للجوّال وبلوتوث تلقائيًا بمجرد بدء التجوال. تعمل معظم الميزات إذا لم تكن متجذرًا ولكن لديك الخبرة الكاملة التي ستحتاج إليها لتصفية جهازك.

التعليمات

س: وضع بلا جذور؟

لاستخدام ميزات Naptime دون الجذر ، تحتاج إلى منحها إذن DUMP عبر ADB على جهاز الكمبيوتر الخاص بك عن طريق تنفيذ هذا الأمر: adb -d shell pm grant com.franco.doze android.permission.DUMP تحتاج أيضا إلى منح إذن WRITE_SECURE_SETTINGS: adb -d shell pm grant com.franco.doze android.permission.WRITE_SECURE_SETTINGS

بعد أن يتم منح هذه الأذونات اثنين عليك أن تكون قادرا على استخدام فترة النوم بحرية.

س: لا أتلقى إعلامات أو تتوقف تطبيقات بث الموسيقى عن العمل بعد إيقاف تشغيل الشاشة. من فضلك توقف!

مع 'Doze العدواني' يتم تجريف الإغفال بعد إيقاف الشاشة. يعتبر Doze حاليًا أقوى آلية لتوفير البطارية على نظام Android. تنطبق القيود التالية على تطبيقاتك أثناء التواجد في Doze: · يتم تسليم إعلامات الدفع ذات الأولوية العليا فقط ؛ تم إيقاف الوصول إلى الشبكة ؛ · يتجاهل النظام أقفال الاستيقاظ ؛ · يتم تأجيل إنذارات AlarmManager القياسية إلى نافذة الصيانة التالية: · لا يقوم النظام بإجراء عمليات مسح Wi-Fi ؛ لا يسمح النظام بتشغيل محولات المزامنة ؛ لا يسمح النظام بتشغيل JobScheduler ؛ تطبيقات مثل Gmail التي تستخدم إشعارات ذات الأولوية العادية ، يتم تسليمها أثناء نافذة الصيانة أو عند استيقاظ جهازك. هذا هو السلوك القياسي ولا يمكن تغييره على الرغم من أنه يمكنك اختيار تطبيقات لتجاوز الإغفال. انتقل إلى الإعدادات -> البطارية -> تجاوز السعة -> تحسين البطارية -> جميع التطبيقات -> التطبيق الخاص بك -> عدم التحسين هذا سيسمح لتطبيقات مثل Spotify بتجاوز التجريف الإجباري والعمل بالفعل على إيقاف الشاشة.

س: ما ميزة "القائمة البيضاء لتطبيق Sensors"؟

إنه يعمل جنبًا إلى جنب مع ميزة "تعطيل الكشف عن الحركة" ويسمح لك باختيار ما يصل إلى تطبيق واحد (آسف Android يقصرنا على تطبيق واحد فقط) لطلب معلومات الاستشعار حتى إذا قمت بتعطيل اكتشاف الحركة. على سبيل المثال ، يسمح للتطبيقات مثل Google Fit بالاستعلام عن مقياس التسارع أو الجيروسكوب لحساب خطواتك.

س: لماذا يتم عرض شاشتي في بعض الأحيان مرة واحدة بعد الفحص؟

قد يحدث هذا إذا كنت تقوم بتعطيل مستشعرات الحركة. السبب في ذلك بسيط لتشغيل إعدادات سطوع النظام وتدويره تلقائيًا بعد الفحص على أنه يجب تشغيله / إيقاف تشغيله (وإلا فلن يعمل) ، وبالتالي قد يتحول إلى وميض (حتى لو كان لبضع ميلي ثانية فقط).

س: لا يعمل ماسح بصمات الأصابع الخاص بي عندما أقوم بتعطيل اكتشاف حركة المستشعر!

لسوء الحظ ، لن تعمل جميع الأجهزة بشكل جيد عند تعطيل الكشف عن مستشعر الحركة وفي هذه العملية قد تتوقف بعض المجسات والوظائف الأخرى عن العمل. لا يوجد شيء يمكنني القيام به حيال ذلك والخيار الوحيد هو عدم استخدام هذا الإعداد ممكّن. هناك أيضًا بعض التوافق الغريب مع هواتف LG حيث لا يتم تشغيل الشاشة مرة أخرى إذا تم تمكين هذا الإعداد.

للتحميل

source https://www.tetbekat.com/2019/09/naptime-premium-boost-your-battery-life.html

0 notes

eddiecowell · 5 years

Text

SIMPLE ANDROID APP IDEAS FOR PROGRAMMING

In this blog post we want to take a look at some simple Android app ideas for beginning programmers. Those will be offline apps without any advanced third party libraries. They will help you learn important basic concepts, not avoid them. If you are already an advanced developer, this post is not for you. You should do something more difficult instead.

The quickest learning method is to getting down and doing the actual work. It is also a good way to read programming books or watch courses. But they will be useful for nothing if you don’t practice what you’re learning. If you ever tried to read a book about coding without actually trying it out yourself, you might have experienced situations where a concept totally made sense to you when you first read it. However, when you later tried to reproduce it, you completely forgot how the syntax looked or how to even begin. I definitely had situations like this.

We all want the stuff that bring knowledge to us and do actual work, which means we have to write code. Once you understand the basic concepts and know how to build a simple layout, it’s much more fun to practice by creating an actual app. Usually, it is not exciting when doing exercises in books and it might make you think that programming is as much fun as doing math homework. Building little programs on the other hand is exciting and gives you a sense of accomplishment after you’ve done it. So let’s start with simple Android app ideas first.

Remember don’t give up too quickly if you stumble at problem you can not solve alone! Youtube is a place where free tutorials available, therefore, it may help you solve your problems. Furthermore, you will learn much faster by solving problems yourself.

Here are some simple Android app ideas:

Tic Tac Toe

I think there is no developer who didn’t build a Tic Tac Toe game when he first started out. Maybe there are some but Tic Tac Toe is a really nice project to practice coding in a fun and enjoyable way. That’s because the logic behind it is simple enough that even though it’s challenging at first, pretty much everyone can do it. But you will have to ponder a bit to figure it out. (This does not include creating a computer player/AI, that’s a lot harder).

Countdown Timer / Stopwatch

A countdown timer and stopwatch are app ideas that you will probably not hear that often, but they are actually pretty cool and fun to build. They are also quite challenging to actual hand on. First of course you have to get the timer running. But then you also have to properly format the time, which is usually given in form of milliseconds. Transforming milliseconds into seconds, minutes and hours without accidentally counting anything twice can easily take a few hours to figure out (if you don’t look at the solution). There are a lot more tricky problems when building such a timer, but it’s also a lot of fun and you actually create something useful that you can put on your own phone.

After you’ve finished the project you could also build some more advanced timers, like a Pomodoro timer, which automatically counts and alternates between different time intervals.

Random Number Generator / Dice Roller

With something as simple as a random number generator you can do some pretty cool stuff, like picking a random color, flipping a coin or throwing a virtual dice. Very useful for people who can’t make decisions. It’s a rather simple project, but you still have to think a little bit and figure out how to handle click events, how to create a switch statement and how to use the random number generator class, which is a bit tricky as well.

Calculator

Calculator can create simple Android app ideas that comes in a great project to train your logical thinking and programming skills. Adding or subtracting two numbers in code is pretty simple, but making the app actually behave like a conventional calculator, that for example adds entered digits to the end of the line, has a character count limit and shows the last result after executing a math operation, is a bit more tricky. But tricky is good, because it means you will learn a lot from it.

If that’s too easy for you, try building a scientific calculator. If it’s too hard, try your hands on a tip calculator first, where you just calculate the percentage on a number input or split a bill up into multiple parts.

Reminder App

Why not build a reminder app that shows you notifications for different events throughout the day? Together with the AlarmManager class and some simple input fields you can create an app that sends you notifications on your phone at scheduled times. Maybe build an app that reminds you to brush your teeth 2 times a day or to not forget taking your medication.

Single Note App

An app that can only save and load one single note might be not the most useful tool for your day to day life, but it’s a good way to learn how to write a text file to the internal storage of an Android device. You will use some really raw Java stuff here, like FileInputStream, FileOutputStream and a lot of try/catch blocks.

To Do List / Grocery List

If you want to store large amounts of data offline in structured way and retrieve it later, you have to learn how to use databases.

A to-do list, grocery list or any kind of list app is a great way to start getting into this topic, because the database structure is usually pretty simple and without any complex relationships. Here we use SQLite, which is built into Android by default, so you can use it right out of the box without adding or preparing anything. If you want to show the database entries in your app, you have to learn about RecyclerView too, because a RecyclerView is necessary to display a large list of data in a memory-efficient way. In the playlist linked here we do exactly that. We build a grocery list app with SQLite and a RecyclerView, where we can add different items with a name and an amount, order these entries by their timestamp and swipe them off the list to permanently delete them from the database.

SQLite is pretty low-level and requires a lot of boilerplate code. It’s very easy to make mistakes because the syntax can be confusing and the compiler won’t show you many warnings for wrong SQLite statements. There is an Android library called “Room” that abstracts a lot of this low-level SQLite stuff and makes it easier to use, but nevertheless I think it’s good to start with raw SQLite as a beginner and then switch to Room when you feel like you understand it.

SQLite Multiple Choice Quiz

If you don’t already have enough of SQLite, creating a quiz game is a good way to practice it a bit more. The database schema is slightly more advanced than in the grocery list app and we use some more complicated query methods, but this time at least we don’t need to build a RecyclerView. What we will learn instead are things like how to restore the application state after configuration changes, how to use SharedPreferences to save smaller amounts of unstructured data, how to send variables between different activities (screens) and more. Therefore, this simple Android app will help you have more ideas and experience in programming.

Budgeting App / Calorie Counter / Any Tracker

Another simple but useful idea would be an app that keeps track of some metric in your life, like your finances or nutrition. You would have to figure out how to take user input, how to process it and make your calculations on it, how to store the data and then how to display it in a useful way. And since you are the developer, you can give your app any functionality you want, display the statistics you need and this way build the perfect tracker for yourself.

Bài viết SIMPLE ANDROID APP IDEAS FOR PROGRAMMING đã xuất hiện đầu tiên vào ngày Cowell Asia.

source https://co-well.vn/en/tech-blog/simple-android-app-ideas-for-programming/

0 notes

fbreschi · 5 years

Text

Android AlarmManager As Deep As Possible

http://bit.ly/2IKasJ8

0 notes

saromglobal · 2 years

Photo

A Complete Guide for Choosing the Right Pasteuriser For Your Business

Choosing the right pasteuriser is a critical decision for any business in the food and beverage industry. A pasteuriser helps to eliminate harmful microorganisms, making the products safer and longer-lasting. With the right pasteuriser, you can ensure that your products maintain their quality and taste, while also increasing their shelf life. Here are the steps to help you choose the right pasteuriser for your business.

To read the full blog, visit: http://bitly.ws/zZNk

#pasteuriser #saromglobal #alarmmanagement #powerplantprocess

0 notes

dmtechnolab · 4 years

Text

Android WorkManager Tutorial - Performing Tasks in Background - Android Coding by DMTechnolab

Android WorkManager Tutorial – Performing Tasks in Background – Android Coding by DMTechnolab

Another important thing introduced with Android Jetpack is WorkManager. In this Android WorkManager Tutorial we are going to learn how we can use the WorkManager API to schedule the tasks that we want to run in the background. I have already posted a tutorial about Android AlarmManager. But now we should use WorkManager as it is recommended and very easy. Android WorkManager Tutorial – Video An…

View On WordPress

#Android #Background #Coding #dmtechnolab #Performing #Tasks #Tutorial #WorkManager

0 notes

jeeteshsurana · 5 years

Link

Every 30 min. tracking in android studio kotlin

__________________________________________________

GPSTracker

__________________________________________________

import android.annotation.SuppressLint

import android.app.AlertDialog

import android.app.Service

import android.content.Context

import android.content.Intent

import android.location.Address

import android.location.Geocoder

import android.location.Location

import android.location.LocationListener

import android.location.LocationManager

import android.os.Bundle

import android.os.IBinder

import android.provider.Settings

import android.util.Log

import java.io.IOException

import java.util.Locale

/**

* Created by JeeteshSurana.

class GPSTracker(private val mContext: Context) : Service(), LocationListener {

// flag for GPS Status

internal var isGPSEnabled = false

// flag for network status

internal var isNetworkEnabled = false

// flag for GPS Tracking is enabled

/**

* GPSTracker isGPSTrackingEnabled getter.

* Check GPS/wifi is enabled

var isGPSTrackingEnabled = false

internal set

internal var location: Location? = null

internal var latitude: Double = 0.toDouble()

internal var longitude: Double = 0.toDouble()

// How many Geocoder should return our GPSTracker

internal var geocoderMaxResults = 1

// Declaring a Location Manager

protected var locationManager: LocationManager? = null

// Store LocationManager.GPS_PROVIDER or LocationManager.NETWORK_PROVIDER information

private var provider_info: String? = null

init {

getLocation()

}

/**

* Try to get my current location by GPS or Network Provider

@SuppressLint("MissingPermission")

fun getLocation() {

try {

locationManager = mContext.getSystemService(Context.LOCATION_SERVICE) as LocationManager

//getting GPS status

isGPSEnabled = locationManager!!.isProviderEnabled(LocationManager.GPS_PROVIDER)

//getting network status

isNetworkEnabled = locationManager!!.isProviderEnabled(LocationManager.NETWORK_PROVIDER)

// Try to get location if you GPS Service is enabled

if (isGPSEnabled) {

this.isGPSTrackingEnabled = true

Log.d(TAG, "Application use GPS Service")

* This provider determines location using

* satellites. Depending on conditions, this provider may take a while to return

* a location fix.

provider_info = LocationManager.GPS_PROVIDER

} else if (isNetworkEnabled) { // Try to get location if you Network Service is enabled

this.isGPSTrackingEnabled = true

Log.d(TAG, "Application use Network State to get GPS coordinates")

* This provider determines location based on

* availability of cell tower and WiFi access points. Results are retrieved

* by means of a network lookup.

provider_info = LocationManager.NETWORK_PROVIDER

}

// Application can use GPS or Network Provider

if (!provider_info!!.isEmpty()) {

locationManager!!.requestLocationUpdates(

provider_info,

MIN_TIME_BW_UPDATES,

MIN_DISTANCE_CHANGE_FOR_UPDATES.toFloat(),

this

)

if (locationManager != null) {

location = locationManager!!.getLastKnownLocation(provider_info)

updateGPSCoordinates()

}

} catch (e: Exception) {

//e.printStackTrace();

Log.e(TAG, "Impossible to connect to LocationManager", e)

}

/**

* Update GPSTracker latitude and longitude

fun updateGPSCoordinates() {

if (location != null) {

latitude = location!!.latitude

longitude = location!!.longitude

}

/**

* GPSTracker latitude getter and setter

* @return latitude

fun getLatitude(): Double {

if (location != null) {

latitude = location!!.latitude

}

return latitude

}

/**

* GPSTracker longitude getter and setter

* @return

fun getLongitude(): Double {

if (location != null) {

longitude = location!!.longitude

}

return longitude

}

/**

* Stop using GPS listener

* Calling this method will stop using GPS in your app

fun stopUsingGPS() {

if (locationManager != null) {

locationManager!!.removeUpdates(this@GPSTracker)

}

/**

* Function to show settings alert dialog

fun showSettingsAlert() {

val alertDialog = AlertDialog.Builder(mContext)

//Setting Dialog Title

alertDialog.setTitle("Title")

//Setting Dialog Message

alertDialog.setMessage("Dialog")

//On Pressing Setting button

alertDialog.setPositiveButton("Yes") { dialog, which ->

val intent = Intent(Settings.ACTION_LOCATION_SOURCE_SETTINGS)

mContext.startActivity(intent)

}

//On pressing cancel button

alertDialog.setNegativeButton("Cancel") { dialog, which -> dialog.cancel() }

alertDialog.show()

}

/**

* Get list of address by latitude and longitude

* @return null or List<Address>

</Address> */

fun getGeocoderAddress(context: Context): List<Address>? {

if (location != null) {

val geocode = Geocoder(context, Locale.ENGLISH)

try {

return geocode.getFromLocation(latitude, longitude, geocoderMaxResults)

} catch (e: IOException) {

//e.printStackTrace();

Log.e(TAG, "Impossible to connect to Geocoder", e)

}

return null

}

/**

* Try to get AddressLine

* @return null or addressLine

fun getAddressLine(context: Context): String? {

val addresses = getGeocoderAddress(context)

if (addresses != null && addresses.isNotEmpty()) {

val address = addresses[0]

return address.getAddressLine(0)

} else {

return null

}

/**

* Try to get Locality

* @return null or locality

fun getLocality(context: Context): String? {

val addresses = getGeocoderAddress(context)

if (addresses != null && addresses.isNotEmpty()) {

val address = addresses[0]

return address.locality

} else {

return null

}

/**

* Try to get Postal Code

* @return null or postalCode

fun getPostalCode(context: Context): String? {

val addresses = getGeocoderAddress(context)

if (addresses != null && addresses.isNotEmpty()) {

val address = addresses[0]

return address.postalCode

} else {

return null

}

/**

* Try to get CountryName

* @return null or postalCode

fun getCountryName(context: Context): String? {

val addresses = getGeocoderAddress(context)

if (addresses != null && addresses.size > 0) {

val address = addresses[0]

return address.countryName

} else {

return null

}

override fun onLocationChanged(location: Location) {}

override fun onStatusChanged(provider: String, status: Int, extras: Bundle) {}

override fun onProviderEnabled(provider: String) {}

override fun onProviderDisabled(provider: String) {}

override fun onBind(intent: Intent): IBinder? {

return null

}

companion object {

// Get Class Name

private val TAG = GPSTracker::class.java.name

// The minimum distance to change updates in meters

private val MIN_DISTANCE_CHANGE_FOR_UPDATES: Long = 10 // 10 meters

// The minimum time between updates in milliseconds

private val MIN_TIME_BW_UPDATES = (1000 * 60 * 1).toLong() // 1 minute

}

__________________________________________________

BootReceiver

__________________________________________________

import android.app.AlarmManager

import android.app.PendingIntent

import android.content.BroadcastReceiver

import android.content.Context

import android.content.Intent

import android.util.Log

import com.justcodenow.reportingapp.util.Constant

import java.util.*

/**

* Created by JeeteshSurana.

class BootReceiver : BroadcastReceiver() {

override fun onReceive(context: Context?, intent: Intent?) {

if (intent!!.action == "android.intent.action.BOOT_COMPLETED") {

//reset alarms on update

cancelHourlyAlarm(context!!)

setHourlyAlarm(context)

} else if (intent.action == "android.intent.action.MY_PACKAGE_REPLACED") {

//reset alarms on update

cancelHourlyAlarm(context!!)

setHourlyAlarm(context)

}

private fun setHourlyAlarm(context: Context) {

val alarmMgr = context.getSystemService(Context.ALARM_SERVICE) as AlarmManager

val intent = Intent(context, AlarmReceiver::class.java)

intent.putExtra(Constant.IntentKeys().ALARM_REQ_CODE, Constant.HOURLY_ALARM_REQ_CODE)

intent.action = AlarmReceiver.ACTION_ALARM_RECEIVER

val alarmIntent = PendingIntent.getBroadcast(context, Constant.HOURLY_ALARM_REQ_CODE, intent, PendingIntent.FLAG_CANCEL_CURRENT)

alarmMgr.setRepeating(AlarmManager.RTC_WAKEUP,Constant.triggerAtMillis ,Constant.interValTime, alarmIntent)

// alarmMgr.setInexactRepeating(AlarmManager.RTC_WAKEUP, Calendar.getInstance().getTimeInMillis() + 1000, 5 * 60 * 1000, alarmIntent);

}

private fun isHourlyAlarmRunning(context: Context): Boolean {

val intent = Intent(context, AlarmReceiver::class.java)

intent.action = AlarmReceiver.ACTION_ALARM_RECEIVER

val isWorking = PendingIntent.getBroadcast(context, Constant.HOURLY_ALARM_REQ_CODE, intent, PendingIntent.FLAG_NO_CREATE) != null

Log.d("Tag", "alarm is " + (if (isWorking) "" else "not") + " working...")

return isWorking

}

private fun cancelHourlyAlarm(context: Context) {

if (isHourlyAlarmRunning(context)) {

val alarmMgr = context.getSystemService(Context.ALARM_SERVICE) as AlarmManager

val intent = Intent(context, AlarmReceiver::class.java)

val pIntent = PendingIntent.getBroadcast(context, Constant.HOURLY_ALARM_REQ_CODE, intent, PendingIntent.FLAG_UPDATE_CURRENT)

if (pIntent != null) alarmMgr.cancel(pIntent)

}

__________________________________________________

AlarmReceiver

__________________________________________________

import android.Manifest

import android.content.BroadcastReceiver

import android.content.Context

import android.content.Intent

import android.content.pm.PackageManager

import android.location.LocationManager

import android.os.Build

import android.text.TextUtils

import androidx.core.app.ActivityCompat

import com.justcodenow.reportingapp.data.local.PreferenceManager

import com.justcodenow.reportingapp.service.GpsIntentService

import com.justcodenow.reportingapp.util.Constant

/**

* Created by JeeteshSurana.

class AlarmReceiver : BroadcastReceiver() {

companion object {

const val ACTION_ALARM_RECEIVER = "ACTION_ALARM_RECEIVER"

var mPreferenceManager: PreferenceManager? = null

}

var roleID: String? = null

private var manager: LocationManager? = null

override fun onReceive(context: Context?, intent: Intent?) {

val prefs = context!!.applicationContext.getSharedPreferences(Constant.MyPrefsFile, Context.MODE_PRIVATE)

mPreferenceManager = PreferenceManager(prefs)

manager = context.getSystemService(Context.LOCATION_SERVICE) as LocationManager

roleID = mPreferenceManager!!.getValue(Constant.roleId, "")!!

if (isUserLoggedIn()) {

if (roleID == Constant.manager || roleID == Constant.salesPerson) {

if (checkPermission(context)) {

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

context.startForegroundService(Intent(context, GpsIntentService::class.java))

} else {

context.startService(Intent(context, GpsIntentService::class.java))

}

private fun isUserLoggedIn(): Boolean {

return !TextUtils.isEmpty(mPreferenceManager!!.getValue(Constant.sharedLogin, ""))

}

private fun checkPermission(context: Context): Boolean {

return ActivityCompat.checkSelfPermission(context, Manifest.permission.ACCESS_FINE_LOCATION) == PackageManager.PERMISSION_GRANTED && ActivityCompat.checkSelfPermission(context, Manifest.permission.ACCESS_COARSE_LOCATION) == PackageManager.PERMISSION_GRANTED

}

__________________________________________________

Manifest

__________________________________________________

<intent-filter>

</intent-filter>

</receiver>

<service

android:name=".service.GpsIntentService"

android:enabled="true"/>

__________________________________________________

implementation fun callService

__________________________________________________

fun callService() {

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

startForegroundService(Intent(this, GpsIntentService::class.java))

} else {

startService(Intent(this, GpsIntentService::class.java))

}

if (!isHourlyAlarmRunning(this)) setHourlyAlarm(this)

}

private fun setHourlyAlarm(context: Context) {

val alarmMgr = context.getSystemService(Context.ALARM_SERVICE) as AlarmManager

val intent = Intent(context, AlarmReceiver::class.java)

intent.putExtra(Constant.IntentKeys().ALARM_REQ_CODE, Constant.HOURLY_ALARM_REQ_CODE)

intent.action = AlarmReceiver.ACTION_ALARM_RECEIVER

val alarmIntent = PendingIntent.getBroadcast(context, Constant.HOURLY_ALARM_REQ_CODE, intent, PendingIntent.FLAG_CANCEL_CURRENT)

alarmMgr.setRepeating(AlarmManager.RTC_WAKEUP, Constant.triggerAtMillis, Constant.interValTime, alarmIntent)

}

private fun isHourlyAlarmRunning(context: Context): Boolean {

val intent = Intent(context, AlarmReceiver::class.java)

intent.action = AlarmReceiver.ACTION_ALARM_RECEIVER

val isWorking = PendingIntent.getBroadcast(context, Constant.HOURLY_ALARM_REQ_CODE, intent, PendingIntent.FLAG_NO_CREATE) != null

Log.d("Tag", "alarm is " + (if (isWorking) "" else "not") + " working...")

return isWorking

}

#News Updates #Every 30 min. tracking in android studio kotlin

0 notes

infotainmentplus-blog · 6 years

Photo

Android Jetpack: What do the recent announcements mean for Android’s Support Library? The official Android docs describe Android Jetpack as “a set of libraries, tools and architectural guidance.” This vague description has left many developers wondering what Android Jetpack really is. Taking a look at the list of Android Jetpack components just raises even more questions — there’s clearly a ton of crossover with existing Android libraries and projects. A good chunk of the components seem to be taken straight from the Support Library, such as AppCompat. So, is Android Jetpack just a rebranded Support Library? Is it a replacement? Can you use the two side by side, or should we all be migrating our apps to Jetpack? The Support Library components aren’t the only familiar features in the list of Jetpack components. All of the Architecture Components (Lifecycles, LiveData, Room and ViewModel) are now part of Jetpack, too. To add to the confusion, at Google I/O 2018 we learned future Support Library updates will be published to the android.support namespace and to a new androidx namespace, as part of AndroidX. This brings us to a grand total of three projects that seem to have some overlap with Jetpack — and we’re still no closer to figuring out what Jetpack actually is! If Google I/O 2018 has left you with more questions than answers, then in this article we’ll be taking a closer look at the Support Library, Architecture Components and AndroidX projects, and demystifying how all of these puzzle pieces fit with Android Jetpack. What is Android Jetpack? Android Jetpack provides a series of unbundled libraries not tied to any particular version of Android, giving developers a way to support newer features on older versions of the Android operating system. In addition to backward compatibility, Jetpack promises to help you get more done, with less code, by providing the boilerplate to handle repetitive tasks like managing the application lifecycle. Android Jetpack components are divided into these categories: Foundation- This covers core system capabilities, such as AppCompat. UI- This is the category for UI-focused components, including Fragment and Layout, but also for components that aren’t restricted to smartphones, such as Auto, TV, and Wear OS by Google (formerly Android Wear). Architecture- This is where you’ll find modules to help you handle the challenges surrounding data persistence and the application lifecycle. Behavior- This category contains modules such as Permissions, Notifications, and Sharing. Android Jetpack also introduces five brand-new components: WorkManager WorkManager is a job dispatching service that lets you schedule tasks, specify some optional constraints, and then leave WorkManager to handle the rest. When you use WorkManager to schedule a task, it’s guaranteed to run as soon as the conditions are met. If you schedule a battery-intensive task to run when the device is charging, then this task will execute as soon as the device is connected to a power outlet, even if the user has exited your application or rebooted their device in the meantime. By default, WorkManager executes the task immediately in a new background thread, but if your application isn’t running it’ll choose the most appropriate way to schedule the task, based on factors such as API level and whether the device has access to Google Play services. Depending on these factors, WorkManager may schedule the task using JobScheduler, Firebase JobDispatcher, or a custom AlarmManager and BroadcastReceiver implementation. Navigation If you’re going to provide a good user experience, then your app’s navigation needs to feel intuitive and effortless. By using the Navigation component in combination with Android Studio 3.2’s new navigation editor, you can design, edit, and generally fine-tune your application’s navigation. The Navigation component also makes it easier to implement a navigational structure that’s based on fragments, by automatically handling much of the complexity surrounding FragmentTransactions. Paging Trying to download and present a large amount of data all at once never leads to a good user experience! The Paging components helps you avoid the lag typically associated with loading large data sets, by breaking data down into chunks, known as “pages.” By focusing on displaying a subset of data as quickly as possible, Paging reduces the amount of time the user is left waiting for something to appear onscreen. Plus, since you’re only loading the portion of data that’s currently visible, Paging uses system resources such as battery and data allowance in a much more economical way. Paging can load content from local storage or over the network, and works out-of-the-box with Room, LiveData, and RxJava. Slices Slices are designed to drive user engagement, displaying a snippet of your application’s content in places where many Android users spend a significant amount of time, like in Google search results and Google Assistant. Slices can display a range of static and interactive content, including images, video, deep links, toggles, and sliders, and they can be dynamic, updating to reflect events that are happening inside the related application. Android KTX This is a collection of modules consisting of extensions that optimize the Android platform APIs for Kotlin. Using these extensions, you can make your Kotlin code more concise and readable, for example by using the androidx.core:core-ktx module, you can turn: sharedPreferences.edit() .putBoolean("key", value) .apply() Into: sharedPreferences.edit { putBoolean("key", value) } Note that Android KTX doesn’t actually add any new features to the existing Android APIs. Is Android Jetpack replacing the Support Library? The Support Library was designed to help developers support recent platform features on devices running earlier versions of Android, by providing backwards compatible implementations of important classes and methods. The Support Library doesn’t guarantee backwards compatibility across all devices, but if it can’t provide a complete set of functionality for a particular device, it’s designed to gracefully fall back on equivalent functionality. Occasionally, you may encounter a framework call that you still need to wrap in an explicit SDK version check. If this sounds a lot like Android Jetpack, there’s a reason for that. Android Jetpack takes the existing Support Libraries and wraps them in a new set of components. However, Android Jetpack isn’t designed to replace the existing Support Library, as Google currently plans to release updates to both the Support Library and Android Jetpack. While Jetpack components are designed to play nicely together, they can operate independently. This means it’s not necessarily a question of “Jetpack or the Support Library?” There’s no reason not to use Jetpack components and the Support Library side-by-side, which is exactly what we’re doing in this snippet from our Scheduling background tasks with WorkManager article: dependencies { implementation fileTree(dir: 'libs', include: ['*.jar']) implementation "android.arch.work:work-runtime:1.0.0-alpha02" implementation "com.android.support:appcompat-v7:27.1.1" implementation "com.android.support.constraint:constraint-layout:1.1.0" androidTestImplementation "com.android.support.test:runner:1.0.1" androidTestImplementation "com.android.support.test.espresso:espresso-core:3.0.1" Here, we’re using Jetpack’s WorkManager component alongside several components from the Support Library. Where do the Architecture Components fit in? If you’ve read through the list of Jetpack components, then you’ll have noticed that it also includes all of the Architecture Components: Lifecycles. This is a library for managing application lifecycles and avoiding memory leaks, by creating lifecycle-aware components that respond to changes in the lifecycle status of other components. ViewModel. UI-related data is often lost in configuration changes like screen rotations. Since ViewModel objects are retained across configuration changes, you can use this class to ensure your data remains available, even after an Activity or Fragment has been destroyed and then recreated. LiveData. A lifecycle-aware data holder class that helps you avoid memory leaks, by only updating application components when they’re in an active STARTED or RESUMED state. Room. This SQLite object mapping library aims to take the pain out of database management by creating a local cache of your application’s data that remains accessible, even when there isn’t an active internet connection. These components are now only available as part of Android Jetpack, but since the dependencies remain the same, this is more of a rebranding than something you need to act on. At this point we know Jetpack combines Support Library components like AppCompat with the Architecture Components announced at Google I/O 2017. You can keep using the modules in the Support Library, switch to their Jetpack equivalent, or use a combination of the two, although the Architecture Components are now considered part of Jetpack. This leaves us with Google I/O 2018’s final Support Library-related announcement: AndroidX. Do I need to switch to the androidx.* namespace? Today, many consider the Support Library an essential part of Android app development, to the point where it’s used by 99 percent of apps in the Google Play store. However ,as the Support Library has grown, inconsistencies have crept in surrounding the library’s naming convention. Initially, the name of each package indicated the minimum API level supported by that package, for example support-v4. However, version 26.0.0 of the Support Library increased the minimum API to 14, so today many of the package names have nothing to do with the minimum supported API level. When support-v4 and the support-v7 packages both have a minimum API of 14, it’s easy to see why people get confused! Even the official Android docs admit this is a problem: “When working with any recent release of the support library, you should not assume that the the v# package notation indicates a minimum API support level.” To clear up this confusion, Google is currently refactoring the Support Library into a new Android extension library (AndroidX) package structure. AndroidX will feature simplified package names, as well as Maven groupIds and artifactIds that better reflect each package’s content, and its supported API levels. With the current naming convention, it also isn’t clear which packages are bundled with the Android operating system, and which are packaged with your application’s APK (Android Package Kit). To clear up this confusion, all the unbundled libraries will be moved to AndroidX’s androidx.* namespace, while the android.* package hierarchy will be reserved for packages that ship with the Android operating system. The AndroidX refactoring map contains the specific mappings between the old and new classes, and the old and new build artifacts, but as a general rule you can expect to encounter these mapping patterns: android.support.** > androidx.@ android.databinding.** > androidx.databinding.@ android.design.** > com.google.android.material.@ android.support.test.** > androidx.test.@ Another important change is that the AndroidX artifacts will update independently, so you’ll be able to update individual AndroidX libraries in your project, rather than having to change every dependency at once. Those frustrating “All com.android.support libraries must use the exact same version specification” messages should become a thing of the past! According to the Google blog, we can expect to see parallel updates to the android.support-packaged libraries throughout the duration of the Android P Preview timeframe, but the stable release of 28.0.0 will be the final feature release packaged as android.support. Regardless of whether you move to Android Jetpack, stick with the Support Library, or use a mixture of the two, eventually you’ll have to switch to the new androidx.* namespace. There are two ways to make the shift to AndroidX: Create a project that supports AndroidX out of the box This requires adding the following to your project’s gradle.properties file: android.useAndroidX=true android.enableJetifier=true Refactor an existing project Android Studio 3.2 has a refactoring feature that can update your code, resources, and Gradle configuration to reference the AndroidX artifacts and classes. To refactor your project, select Refactor > Refactor to AndroidX… from the Android Studio toolbar. Wrapping up Now we’ve explored all the Google I/O announcements, and how existing components overlap with Android Jetpack, we’re finally ready to answer our original question(s)! Android Jetpack takes the existing Support Library components, combines them with last year’s Architecture Components, and adds a few new components. There are no plans to abandon the Support Library just yet, so if a component is available via the Support Library and Android Jetpack, you can still choose which implementation to use. However, version 28.0.0 will be the last release of android.support. After that you’ll have to move to the androidx.* namespace. Are there any other Google I/O announcements that left you with more questions than answers? Let us know in the comments below! , via Android Authority http://bit.ly/2KMVy74

0 notes