david

I'm creating this topic for people to discuss the WiFi signal strength of their Pro1 phones. This can be used to report on tests that have been done and any tips for improving the signal strength, hence the range of the device and the speed of data transfers at greater distances.

This may or may not be related to this issue: https://source.android.com/devices/tech/connect/wifi-low-latency

A possible bug: - Multiple users have seen that pinging their wireless access point on their LAN, over wifi, results in 20+ ms latency most of the time. Testing on one network showed that a pixel 1 phone running Android 10 reports about 5 ms. A Samsung Galaxy S Relay 4G running Cyanogenmod 11 (Kitkat/4.4.4.) shows 1-2 ms usually. This could possible lead to longer page load times for web pages and some delays in gaming applications. More information can be found here: UPDATE: It has also been shown that speed testing tools, like speedtest and fast.com show lower l

That is what I thought too, but then I thought that I was just always assuming that (because I always have it enabled) or that Android changed something. What I can say is that the Pro1 is working the following ways for me (not on latest OTA updates though): 1) When I plug into a Windows 7 laptop without USB debugging enabled, the phone does not show when I use PTP nor when I use File transfer (MTP) settings. 2) When I plug into a Windows 7 laptop with USB debugging enabled, the phone does show the internal storage when I use PTP, but does not usually show the SD card storage. I

More testing... Just in case it was only a problem with ICMP (the protocol ping uses), I found a way to test TCP latency. By using the app PingTools Network Utilities, and changing the Ping feature's settings to use TCP, I get the same results -- 20+ ms typical latency (TCP pinging port 80 on my router). It also has an option to test with HTTP, which gives slightly higher latency. Testing over the USB tethered network to my laptop gives the normal, low latency pings again (using the TCP test in PingTools). The main reason why all of this is important is because if there is add

:-) It certainly is the answer to lowering ping latency from the Pro1! LOL

Well, in theory, yes, but it could be something in the software that is looking at LAN addresses and adding latency for some unknown reason. That was the only reason for asking for that test. I did another test. I plugged the phone into my laptop and enabled USB Tethering. I then pinged the phone from the laptop and got 1-5 ms times. I pinged the laptop from the phone and got the same. So the network stack by itself is not wholly doing this. And the terminal application is not doing this. The common variables seem to be wifi to an address outside the phone. I have tried 2.4 and 5.

I did the same test with localhost. It is something within the network stack that is slowing down when it is accessing outside the phone. I even set my old phone as a hotspot and got the same results. However, if I set the Pro1 as a hotspot and connect to it from my old phone, I get *under* 1 ms pings, consistently. I downloaded a couple ping apps and they get the same results pinging the wireless access point. For those of you who are getting fast pings reported in speed test apps, who are on fiber, can you try pinging google.com or some other known endpoint on the internet?

Yes, this test is for wifi, with the ping command, in a terminal shell, to its access point. Speedtest must be measuring in some weird way, although fiber optic definitely has lower latency. Are you on fiber optic, @EskeRahn? To your point @EskeRahn, yes, it sometimes reports faster pings. That is another reason I am thinking something is holding it back the other 99% of the time.

I *thought* I had to enable usb debugging to get the Pro1 to connect over USB to Windows to do file transfers. I will test turning off usb debugging to see if it still connects.

Was that test done over wifi or cellular? I am talking about over wifi, by running the ping command, in a terminal shell, pinging the address of the wireless access point 6 feet away. I checked that "battery saver" was off. I also went into battery optimization and turned it off for the terminal app, but that didn't make a difference. If you got 2ms ping over wifi, to a remote speedtest server, then i would question the results. You would have at least one hop to get to the wireless access point and then one or more hops to get to your internet provider's gateway to the inter

I'm not sure what adb debugging is. I get it when i enable usb debugging and then connect to the computer with usb.

It handles that use case by asking you to trust the computer you are connecting to. However, I did find out that there is another setting in the developer options for remembering the USB preference. So it might be that google messed this up (changed it to forget on purpose), but allowed a work-around for those people who enable the developer options.

I'm curious what other people are getting for latency when they ping their wireless access point with their Pro1 phones. I'm generally getting 20+ ms. My old Relay 4G is getting what I would expect, which is 1-2 ms. A Pixel 1 I tested got about 4-5 ms (I think it is running android 10). I'm curious if it is android that has gotten more stingy over the years (trying to save power) or if their is something about the Pro1 that is holding back, or a combination of the two. But either way, I'd be interested in what other people get. I'm doing this through terminal programs and getting the

abielins would probably be happy if you got one of these, @EskeRahn

Agreed:

Found it on USA ebay too. Same source, however, so still a long delay. https://www.ebay.com/itm/Black-Silicone-Rubber-Strip-Self-Adhesive-Seal-Gasket-300x10-20-30x0-5-1-2-3mm/333378056295 I'm plan on putting these on my phone case. They might also work for dampening the noise of the phone when opening. https://www.amazon.com/Dragon-Grips-Clear-Hexagons/dp/B07DD5XRXF

Okay, I got an email back from Zagg about their InvisibleShield screen protectors. They re-confirmed what the online chat person told me. The Pro1 and Elephone phones aren't in their database. The person did say that stores/kiosks that have the ability to do "on demand" screen protectors should be able to make them for the Pro1. Now, whether that is factual information remains to be seen, but that's what they said.

Did you tap the gear icon in the pop-up that you get to from pushing the volume-up/down buttons? That will allow you to adjust the volumes for all the various sounds.

Default, with no boxes checked.

I believe that choice is just for whether you want it to treat it as the combined internal and external storage or if you want to treat it as fully external. I installed it the same way. As for the PTP, I was surprised when I did see the SD card through PTP. I'll have to test on my old phone, but I didn't think it showed the SD card in that mode. It is possible it only shows certain folders that are marked as media folders. It is possible that my non-OTA'd phone just has some bugs that have been worked out in the meantime. I'll report back later after more testing in the coming days.

Hey, I'll take a false estimate at 100% over a false estimate at 70% (probably where my old phone would have been if I let it sit for 6 hours) any day! LOL It did drop to 99% a few minutes after I started using it. It is also possible that it has a *very* good idle state (in addition to false estimates). Not being calibrated properly also did cross my mind. I have been through that process many times with past phones, to try to get them to recalibrate. This one works so well that I don't want to mess with it yet by fully depleting it. :-)

Or, you'd realize you are really an android. :-)

When I first glanced at that, I thought it was saying 262 WPM! Let's just say I was suspecting it wasn't accurate. LOL

I will try it on another computer. Glad to see that someone has MTP working. Do you see both for PTP? I let the phone format it for FAT32, so I doubt that is it. Anything is possible though.