-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reversed the chat view to be bottom instead of top posting.
Added a few FCM notification classes, nothing functional yet.
- Loading branch information
Showing
6 changed files
with
185 additions
and
103 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15 changes: 15 additions & 0 deletions
15
app/src/main/java/se/oort/diplicity/FirebaseMessageIDService.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| package se.oort.diplicity; | ||
|
|
||
| import android.util.Log; | ||
|
|
||
| import com.google.firebase.iid.FirebaseInstanceId; | ||
| import com.google.firebase.iid.FirebaseInstanceIdService; | ||
|
|
||
| public class FirebaseMessageIDService extends FirebaseInstanceIdService { | ||
|
|
||
| @Override | ||
| public void onTokenRefresh() { | ||
| String refreshedToken = FirebaseInstanceId.getInstance().getToken(); | ||
| Log.d("Diplicity", "Refreshed IID token: " + refreshedToken); | ||
| } | ||
| } |
70 changes: 70 additions & 0 deletions
70
app/src/main/java/se/oort/diplicity/FirebaseMessagingService.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| package se.oort.diplicity; | ||
|
|
||
| import android.app.NotificationManager; | ||
| import android.app.PendingIntent; | ||
| import android.content.Context; | ||
| import android.content.Intent; | ||
| import android.media.RingtoneManager; | ||
| import android.net.Uri; | ||
| import android.support.v4.app.NotificationCompat; | ||
| import android.util.Log; | ||
| import com.google.firebase.messaging.RemoteMessage; | ||
|
|
||
| public class FirebaseMessagingService extends com.google.firebase.messaging.FirebaseMessagingService { | ||
| @Override | ||
| public void onMessageReceived(RemoteMessage remoteMessage) { | ||
| // [START_EXCLUDE] | ||
| // There are two types of messages data messages and notification messages. Data messages are handled | ||
| // here in onMessageReceived whether the app is in the foreground or background. Data messages are the type | ||
| // traditionally used with GCM. Notification messages are only received here in onMessageReceived when the app | ||
| // is in the foreground. When the app is in the background an automatically generated notification is displayed. | ||
| // When the user taps on the notification they are returned to the app. Messages containing both notification | ||
| // and data payloads are treated as notification messages. The Firebase console always sends notification | ||
| // messages. For more see: https://firebase.google.com/docs/cloud-messaging/concept-options | ||
| // [END_EXCLUDE] | ||
|
|
||
| // TODO(developer): Handle FCM messages here. | ||
| // Not getting messages here? See why this may be: https://goo.gl/39bRNJ | ||
| Log.d("Diplicity", "From: " + remoteMessage.getFrom()); | ||
|
|
||
| // Check if message contains a data payload. | ||
| if (remoteMessage.getData().size() > 0) { | ||
| Log.d("Diplicity", "Message data payload: " + remoteMessage.getData()); | ||
| } | ||
|
|
||
| // Check if message contains a notification payload. | ||
| if (remoteMessage.getNotification() != null) { | ||
| Log.d("Diplicity", "Message Notification Body: " + remoteMessage.getNotification().getBody()); | ||
| } | ||
|
|
||
| // Also if you intend on generating your own notifications as a result of a received FCM | ||
| // message, here is where that should be initiated. See sendNotification method below. | ||
| } | ||
| // [END receive_message] | ||
|
|
||
| /** | ||
| * Create and show a simple notification containing the received FCM message. | ||
| * | ||
| * @param messageBody FCM message body received. | ||
| */ | ||
| private void sendNotification(String messageBody) { | ||
| Intent intent = new Intent(this, MainActivity.class); | ||
| intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP); | ||
| PendingIntent pendingIntent = PendingIntent.getActivity(this, 0 /* Request code */, intent, | ||
| PendingIntent.FLAG_ONE_SHOT); | ||
|
|
||
| Uri defaultSoundUri= RingtoneManager.getDefaultUri(RingtoneManager.TYPE_NOTIFICATION); | ||
| NotificationCompat.Builder notificationBuilder = new NotificationCompat.Builder(this) | ||
| .setSmallIcon(R.drawable.ic_otto) | ||
| .setContentTitle("FCM Message") | ||
| .setContentText(messageBody) | ||
| .setAutoCancel(true) | ||
| .setSound(defaultSoundUri) | ||
| .setContentIntent(pendingIntent); | ||
|
|
||
| NotificationManager notificationManager = | ||
| (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE); | ||
|
|
||
| notificationManager.notify(0 /* ID of notification */, notificationBuilder.build()); | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters