FR: Add API to manage Gmail templates [174678306]

Assigned

Feature Request

Status Update

No update yet.

Description

ne...@mimestream.com

created issue #1

Dec 2, 2020 08:01PM

A short description of the request:

Feature Request: Add API to create, edit, and delete a user's Gmail templates.

What is the purpose of this new feature?

To allow 3rd party email clients to have UI to manage these templates.

I am the developer of Mimestream and receive a lot of requests for this.

What existing APIs would this affect?

New API would need to be created for this.

Please provide any additional information below.

I'm filing this feature request separately from what is arguably more of a bug / bare-minimum request to avoid unexpected data loss, see https://issuetracker.google.com/issues/168223591 and https://issuetracker.google.com/issues/173628037

Comments

ma...@google.com <ma...@google.com> #2Dec 3, 2020 08:26AM

Assigned to ma...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue on latest public build)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.

ne...@mimestream.com <ne...@mimestream.com> #3Dec 3, 2020 08:39AM

The easiest way to reproduce the issue is by using an app like Nordic's nRF Connect for Mobile from Google Play.

Prerequisites:
Any BLE device you can create a GATT connection to

Steps to reproduce:

Open nRF Connect for Mobile
Discover the BLE device
Create a connection to the BLE device
Pull from the left side of the screen in nRF to reveal the log window (or look at logcat on a connected computer)
Terminate the BLE connection by powering off or taking the BLE device out of range

Expected result:
If the BLE device is taken out of range, the GATT status value in onConnectionStateChanged() should be '8' (GATT_CONN_TIMEOUT), like on all previous Android versions with BLE support.
If the BLE device terminates the connection, the GATT status value in onConnectionStateChanged() should be '19' (GATT_CONN_TERMINATE_PEER_USER), like on all previous Android versions with BLE support.

The GATT status should only be '0' when the app closes the connection via a call to BluetoothGatt#disconnect().

Actual result:
In Android 12, regardless how the BLE connection is terminated the GATT status is always '0'.

See attached screen shot ('Comparison.png') for a comparison between an older Android version and Android 12.

Pixel 12:
GATT_CONN_TIMEOUT, disconnect reason 8:
2021-11-29 11:48:13.635 13689-13722/? D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=9 device=xx:xx:xx:xx:xx:xx

GATT_CONN_TERMINATE_PEER_USER, disconnect reason 19:
2021-11-29 11:53:02.644 13689-21741/? D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=9 device=xx:xx:xx:xx:xx:xx

Bugreport
https://drive.google.com/file/d/19ASZ6bVYXRuhRt_NjsRs_-YnWOiUGcyN/view?usp=drive_web (bugreport-flame-SP1A.210812.015-2021-11-29-11-53-20.zip)

Message last modified on Dec 3, 2020 08:39AM

ma...@google.com <ma...@google.com> #4Dec 3, 2020 09:46AM

Correction to #3:
The headline 'Pixel 12' should have been: 'Pixel 4, Android 12'. 😀

hi...@gmail.com <hi...@gmail.com> #5Dec 30, 2020 09:02AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

is...@google.com <is...@google.com> Jan 8, 2021 07:07AM

Status: New

jp...@google.com <jp...@google.com> Jul 13, 2023 02:35AM

Assigned to wo...@google.com.

jm...@gmail.com <jm...@gmail.com> #6Dec 23, 2024 07:29PM

If you look into the HCI snoop log, you can see that the disconnect reasons (0x08 and 0x13), are correctly shown there. Though I noticed that in the HCI log, there is a 'Status: Success (0x00)' field. Is this the one which is now passed on to the onClientConnectionState() / onConnectionStateChanged() methods?
If that is the case, then how do we get the 'disconnect reason' through the API in Android 12?

Android 12:

GATT_CONN_TIMEOUT, disconnect reason 8 ((0x08):
HCI log:

44563	10:48:13.617287	0.000839	controller	host	HCI_EVT	7	Rcvd Disconnect Complete
Frame 44563: 7 bytes on wire (56 bits), 7 bytes captured (56 bits)
Bluetooth
Bluetooth HCI H4
Bluetooth HCI Event - Disconnect Complete
    Event Code: Disconnect Complete (0x05)
    Parameter Total Length: 4
    Status: Success (0x00)
    Connection Handle: 0x0002
    Reason: Connection Timeout (0x08)

Log cat:
2021-11-29 11:48:13.635 13689-13722/? D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=9 device=xx:xx:xx:xx:xx:xx

GATT_CONN_TERMINATE_PEER_USER, disconnect reason 19 (0x13):
HCI log:

45054	10:53:02.634023	16.743903	controller	host	HCI_EVT	7	Rcvd Disconnect Complete
Frame 45054: 7 bytes on wire (56 bits), 7 bytes captured (56 bits)
Bluetooth
Bluetooth HCI H4
Bluetooth HCI Event - Disconnect Complete
    Event Code: Disconnect Complete (0x05)
    Parameter Total Length: 4
    Status: Success (0x00)
    Connection Handle: 0x0003
    Reason: Remote User Terminated Connection (0x13)

Log cat:
2021-11-29 11:53:02.644 13689-21741/? D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=9 device=xx:xx:xx:xx:xx:xx

Android 11:

GATT_CONN_TIMEOUT, disconnect reason 8 ((0x08):
HCI log:

19997	11:20:16.335340	0.001857	controller	host	HCI_EVT	7	Rcvd Disconnect Complete
Frame 19997: 7 bytes on wire (56 bits), 7 bytes captured (56 bits)
Bluetooth
Bluetooth HCI H4
Bluetooth HCI Event - Disconnect Complete
    Event Code: Disconnect Complete (0x05)
    Parameter Total Length: 4
    Status: Success (0x00)
    Connection Handle: 0x0040
    Reason: Connection Timeout (0x08)

Log cat:
12-02 11:20:16.348 10268 25440 26308 D BluetoothGatt: onClientConnectionState() - status=8 clientIf=11 device=52:31:2C:E1:EF:82

12-02 11:20:16.349--BluetoothRemoteDevices -- ACTION_ACL_DISCONNECTED, device is 52312C, reason is 8, linktype is 2

GATT_CONN_TERMINATE_PEER_USER, disconnect reason 19 (0x13):
HCI log:

20386	11:21:13.816370	3.541896	controller	host	HCI_EVT	7	Rcvd Disconnect Complete
Frame 20386: 7 bytes on wire (56 bits), 7 bytes captured (56 bits)
Bluetooth
Bluetooth HCI H4
Bluetooth HCI Event - Disconnect Complete
    Event Code: Disconnect Complete (0x05)
    Parameter Total Length: 4
    Status: Success (0x00)
    Connection Handle: 0x0040
    Reason: Remote User Terminated Connection (0x13)

Log cat:
12-02 11:21:13.826 10268 25440 26126 D BluetoothGatt: onClientConnectionState() - status=19 clientIf=11 device=52:31:2C:E1:EF:82

12-02 11:21:13.828--BluetoothRemoteDevices -- ACTION_ACL_DISCONNECTED, device is 52312C, reason is 19, linktype is 2

da...@gmail.com <da...@gmail.com> #7Dec 23, 2024 09:54PM

Same situation with Android 12L Beta on Pixel 4 :( - still always returns 'status = 0'.

Pixel 4, SB1.211112.006