-
-
Notifications
You must be signed in to change notification settings - Fork 39
Description
Heyo! Recently I discovered that if you have the Meta AI disabled, the package for it (com.oculus.assistant) will send out a silent notification when you press the shortcut (Oculus/Meta button + grip). I made an Automate script that waits for that notification to get sent out then it launches Lightning Launcher. I feel like this should be pretty easy to implement directly into the launcher itself, and personally I find this way better than dealing with navigator lol.
I'm not sure how notification access is implemented in code but once implemented it can be granted by launching com.android.settings/com.android.settings.Settings$NotificationAccessSettingsActivity then just having the user allow Lightning Launcher in that screen. As for the notification, it's just a completely empty notification coming from com.oculus.assistant. Here's a json of the data from a notification logger:
Notification data
{
"packageName": "com.oculus.assistant",
"postTime": 1752613532096,
"systemTime": 1752613532300,
"offset": -25200000,
"version": 16,
"sdk": 34,
"isOngoing": false,
"isClearable": false,
"when": 1752613532094,
"number": -1,
"flags": 96,
"defaults": 0,
"ledARGB": 0,
"ledOn": 0,
"ledOff": 0,
"ringerMode": 2,
"isScreenOn": true,
"batteryLevel": 41,
"batteryStatus": "discharging",
"isConnected": true,
"connectionType": "wifi",
"hasAppointment": false,
"isGroupSummary": false,
"actionCount": 0,
"isLocalOnly": false,
"people": 0,
"tickerText": "",
"title": "",
"titleBig": "",
"text": "",
"textBig": "",
"textInfo": "",
"textSub": "",
"textSummary": "",
"appName": "Oculus Assistant Service",
"priority": 1,
"nid": 70000,
"key": "0|com.oculus.assistant|70000|null|10086",
"visibility": 0,
"color": 0,
"interruptionFilter": 1,
"listenerHints": 0,
"matchesInterruptionFilter": true
}