Infeasible
Status Update
No update yet.
Comments
vi...@google.com
for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?
i donnot understand why is the data the same?
vi...@google.com
the fractional part of the location data is exactly the same.
vi...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Please provide a 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)
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 and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Please provide a 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)
For steps to capture a bug report, please refer:
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 and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Description
1. open hotspot at DUT
2. one client connected this hotspot
3.run speedtest at client
4. found speed is very slow than ref
analysis: DUT's cellular nic enable gro, transfer one large packet to kernel sometimes, then transfer to clat for processing. After processing, send it to the TUN. TUN receive this packet, forward it to wlan. When forwarding, it was found that the packet size exceeded MTU, reply ICMP to speedtest server immediately.
from 002-1029_095939--1029_100043\tcpdump.cap：
1) receive one large packet, size is 2508:
41505 2024-10-29 17:00:04.896774 64:ff9b::4e0a:a103 2a00:f41:18b0:38ca:39d3:4bf:35f3:c0c3 TCP 2416 31872 2508 http-alt(8080) → 51812 [ACK] Seq=4048662303 Ack=116708023 Win=31872 Len=2416 TSval=3298733802 TSecr=3625573412 [TCP segment of a reassembled PDU]
2) after clat, tun receive this large packet:
41550 2024-10-29 17:00:04.975651 78.10.161.3 192.0.0.4 TCP 247706 31872 2488 0x0000 (0) http-alt(8080) → 51812 [ACK] Seq=4048662303 Ack=116708023 Win=31872 Len=2416 TSval=3298733802 TSecr=3625573412 [TCP segment of a reassembled PDU]
3) when forward this packet, ip_forward found packet's size is larger than mtu, so replay icmp:
41551 2024-10-29 17:00:04.976037 192.0.0.4 78.10.161.3 ICMP 249 596 0xa2c6 (41670),0x0000 (0) Destination unreachable (Fragmentation needed)