Status Update
No update yet.
Comments
va...@google.com
It looks like you are raising an issue as an Android user, rather than an Android Open Source Developer. Our Android Support team will be in contact with you shortly. In the meantime, here are helpful resources:
la...@google.com
va...@google.com
Can you provide the below requested information to better understand the issue:
Android build Which Android build are you using? (e.g. KVT49L)
Device used Which device did you use to reproduce this issue?
Android bug report (new bugreport) After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
Alternate method: After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to
la...@google.com
>>> This problem was confirmed on a Motorola G60s phone running Android version 12 Build S3RLS32.114-25-3
Please refer to the earlier referenced issue with regards to the 'bug' status of this matter:
The same point stands; this is NOT a bug, but a failure to implement a common RFC related to IP routing. Bug reports will not help and are not an appropriate way to take this forward.
If you are not clear on this matter, please refer this thread to someone who understands IP networking at the RFC level so that there's a collective 'oh crap, how can we have failed to implement this' moment. Then you can put it right and join the ranks of all the other operating systems (Windows, Mac, Linux...) that do this properly.
Do not let this fresh issue report wither and die like the previous one because of a lack of understanding of the fundamental networking nature of this matter.
va...@google.com
la...@google.com
namely:
The Motorola G60s mentioned on the initial report
Samsung Galaxy Tab A7, software Android 12 build SP1A.201812.016.T500XXS4CJ1
Samsung Z Fold 4. Not currently available to check build version.
Option 121 support is missing on all these devices.
On 07/01/2023 05:36, buganizer-system@google.com wrote:
Description
ChromeOS Version: 132.0.6834.154
What steps will reproduce the problem?
(1) Connect to an SSH server (2) Disconnect, e.g. by putting the chromebook to sleep (3) Attempt to reconnect
What is the expected result? Can press "R" to reconnect the previous session
What happens instead? Nothing happens, need to manually close the window and open a new one to connect to the session again