NEWSS:AddNotification - Revision history

DaniElectra: /* Header structure */

2024-01-14T17:01:28Z

Header structure

← Older revision		Revision as of 20:01, 14 January 2024
Line 57:		Line 57:
	\| 0x3		\| 0x3
	\| 0x1		\| 0x1
	\| u8 flag: 0 = non-SpotPass notification, 1 = SpotPass notification.		\| u8 flag: 0 = non-SpotPass notification, 1 = SpotPass notification (zero for system notifications)
	\|-		\|-
	\| 0x4		\| 0x4

DaniElectra: /* Header structure */ Update regarding BOSS notifications

2024-01-14T16:50:28Z

Header structure: Update regarding BOSS notifications

← Older revision		Revision as of 19:50, 14 January 2024
Line 68:		Line 68:
	\|-		\|-
	\| 0x6		\| 0x6
	\| ~~0x2~~		\| 0x1
	\| unknown		\| u8 flag: unknown
			\|-
			\| 0x7
			\| 0x1
			\| padding?
	\|-		\|-
	\| 0x8		\| 0x8
Line 76:		Line 80:
	\|-		\|-
	\| 0x10		\| 0x10
	\| ~~0x8~~		\| 0x4
	\| ~~unknown~~		\| u32 nsDataId: set by the sysmodule when handling BOSS notifications
			\|-
			\| 0x14
			\| 0x4
			\| u32 version: set by the sysmodule when handling BOSS notifications
	\|-		\|-
	\| 0x18		\| 0x18
Line 85:		Line 93:
	\| 0x20		\| 0x20
	\| 0x8		\| 0x8
	\| ~~unknown~~		\| padding?
	\|-		\|-
	\| 0x28		\| 0x28

DaniElectra: Fix typo

2023-07-25T07:28:27Z

Fix typo

← Older revision		Revision as of 11:28, 25 July 2023
Line 67:		Line 67:
	\| u8 flag: 0 = message doesn't have a browser link, 1 = message has a browser link		\| u8 flag: 0 = message doesn't have a browser link, 1 = message has a browser link
	\|-		\|-
	\| ~~0x5~~		\| 0x6
	\| 0x2		\| 0x2
	\| unknown		\| unknown

DaniElectra: Fix typo

2023-07-24T20:43:04Z

Fix typo

← Older revision		Revision as of 00:43, 25 July 2023
Line 65:		Line 65:
	\| 0x5		\| 0x5
	\| 0x1		\| 0x1
	\| u8 flag: 0 = message ~~has~~ a browser link, 1 = message ~~doesn't have~~ a browser link		\| u8 flag: 0 = message doesn't have a browser link, 1 = message has a browser link
	\|-		\|-
	\| 0x5		\| 0x5

DaniElectra: Add flag for browser link on message

2023-07-24T20:42:13Z

Add flag for browser link on message

← Older revision		Revision as of 00:42, 25 July 2023
Line 64:		Line 64:
	\|-		\|-
	\| 0x5		\| 0x5
	\| ~~0x3~~		\| 0x1
			\| u8 flag: 0 = message has a browser link, 1 = message doesn't have a browser link
			\|-
			\| 0x5
			\| 0x2
	\| unknown		\| unknown
	\|-		\|-
Line 97:		Line 101:

	=Message=		=Message=
	This is an UTF-16 string for the notification message text, this buffer includes the null-terminator. The maximum size in bytes is 0x1780.		This is an UTF-16 string for the notification message text, this buffer includes the null-terminator. When the message has the browser link flag set, the URL it's located after the null-terminator of the message text as a UTF-8 string, also with null-termination. The maximum size in bytes is 0x1780.

	=Image=		=Image=

Steveice10: Add maximum sizes for messages and image data.

2015-10-08T04:18:48Z

Add maximum sizes for messages and image data.

← Older revision		Revision as of 08:18, 8 October 2015
Line 97:		Line 97:

	=Message=		=Message=
	This is an UTF-16 string for the notification message text, this buffer includes the null-terminator.		This is an UTF-16 string for the notification message text, this buffer includes the null-terminator. The maximum size in bytes is 0x1780.

	=Image=		=Image=
	The MPO data is optional. This is displayed on the top-screen by the notifications applet.		The MPO data is optional. This is displayed on the top-screen by the notifications applet. The maximum size in bytes is 0x10000.

	=Response=		=Response=

Steveice10: Add to and clean up notification header info.

2015-10-08T04:16:40Z

Add to and clean up notification header info.

← Older revision		Revision as of 08:16, 8 October 2015
Line 45:		Line 45:
	\| 0x0		\| 0x0
	\| 0x1		\| 0x1
	\| u8 flag: 0 = ~~notification header data not set~~, 1 = ~~notification data set~~("notification exists" flag).		\| u8 flag: 0 = invalid, 1 = valid ("notification exists" flag).
	\|-		\|-
	\| 0x1		\| 0x1
	\| 0x1		\| 0x1
	\| u8 flag: 1 = ~~not "~~read~~" by the notifications applet~~, ~~0 otherwise.~~		\| u8 flag: 0 = read, 1 = unread
	\|-		\|-
	\| 0x2		\| 0x2
	\| 0x1		\| 0x1
	\| u8 flag: 0 = ~~disable~~ JPEG, 1 = ~~enable~~ JPEG.		\| u8 flag: 0 = image data is not JPEG, 1 = image data is JPEG.
	\|-		\|-
	\| 0x3		\| 0x3
	\| 0x1		\| 0x1
	\| u8 flag: ~~when [[NEWSS:GetNotificationHeader]] is used where this flag is value 1, news~~-~~module then uses [[BOSS_Services\|boss:P]] command 0x04070080 with the input u64 loaded from offset 0x8 in this header. When that's successful~~, ~~[[NEWSS:GetNotificationHeader]] copies the output u8 from that BOSS command to out_notificationheader+4~~.		\| u8 flag: 0 = non-SpotPass notification, 1 = SpotPass notification.
	\|-		\|-
	\| 0x4		\| 0x4
	\| 0x1		\| 0x1
	\| u8 flag		\| u8 flag: 0 = opted in to this notification, 1 = opted out of this notification
			\|-
			\| 0x5
			\| 0x3
			\| unknown
	\|-		\|-
	\| 0x8		\| 0x8
	\| 0x8		\| 0x8
	\| u64 programID ~~that this~~ notification ~~is associated with, this is~~ zero for system notifications.		\| u64 programID: notification source (zero for system notifications)
	\|-		\|-
	\| 0x10		\| 0x10
			\| 0x8
			\| unknown
			\|-
	\| 0x18		\| 0x18
			\| 0x8
			\| u64 jumpParam: specified by source app and later retrieved via APT to identify which notification, if any, it was launched from
			\|-
			\| 0x20
			\| 0x8
	\| unknown		\| unknown
	\|-		\|-
Line 76:		Line 88:
	\|-		\|-
	\| 0x30		\| 0x30
	\| ?		\| 0x40
	\| UTF-16 string for the notification title		\| UTF-16 string for the notification title
	\|}		\|}

	This structure is ~~normally~~ 0x70-bytes.		This structure is 0x70-bytes.

			When [[NEWSS:GetNotificationHeader]] is used where the u8 flag at 0x3 is value 1, news-module then uses [[BOSS_Services\|boss:P]] command 0x04070080 with the u64 programID at offset 0x8 in this header. When that's successful, [[NEWSS:GetNotificationHeader]] copies the output u8, the SpotPass opt-out flag, from that BOSS command to the u8 flag at 0x4. Otherwise, the opt-out flag is 0 for opted in.

	=Message=		=Message=

Steveice10: Make it clear that there are 0x18 bytes between programID and datetime.

2015-04-14T15:00:09Z

Make it clear that there are 0x18 bytes between programID and datetime.

← Older revision		Revision as of 19:00, 14 April 2015
Line 66:		Line 66:
	\| 0x8		\| 0x8
	\| u64 programID that this notification is associated with, this is zero for system notifications.		\| u64 programID that this notification is associated with, this is zero for system notifications.
			\|-
			\| 0x10
			\| 0x18
			\| unknown
	\|-		\|-
	\| 0x28		\| 0x28

Yellows8: /* Header structure */

2014-12-12T20:58:00Z

Header structure

← Older revision		Revision as of 23:58, 12 December 2014
Line 65:		Line 65:
	\| 0x8		\| 0x8
	\| 0x8		\| 0x8
	\| u64		\| u64 programID that this notification is associated with, this is zero for system notifications.
	\|-		\|-
	\| 0x28		\| 0x28

Yellows8: /* Header structure */

2014-12-12T17:10:47Z

Header structure

← Older revision		Revision as of 20:10, 12 December 2014
Line 56:		Line 56:
	\|-		\|-
	\| 0x3		\| 0x3
			\| 0x1
			\| u8 flag: when [[NEWSS:GetNotificationHeader]] is used where this flag is value 1, news-module then uses [[BOSS_Services\|boss:P]] command 0x04070080 with the input u64 loaded from offset 0x8 in this header. When that's successful, [[NEWSS:GetNotificationHeader]] copies the output u8 from that BOSS command to out_notificationheader+4.
			\|-
			\| 0x4
	\| 0x1		\| 0x1
	\| u8 flag		\| u8 flag
			\|-
			\| 0x8
			\| 0x8
			\| u64
	\|-		\|-
	\| 0x28		\| 0x28