Intermitent SSL_PROTOCOL_ERROR when using Android hotspot - android

When browsing the internet using the Wi-Fi hotspot of my Android phone (Xiaomi Redmi Note 10 Pro), some requests fail with the following error: net::ERR_SSL_PROTOCOL_ERROR
Here is a screenshot of the error I'm getting in Chrome for Mac OS:
I noticed that it is happening only on specific websites (I have no issues on Stack Overflow for example).
This seems to be happening regardless of the LTE network quality.
I tried using the Wi-Fi hotspot from another phone, and everything is working as intended.
Anybody have an idea on how to debug this issue?
Thank you

I fixed the issue, turns out the default APN was not correctly configured.
I re-configured my APN with the config given by my phone provider (for Orange in France, the config is here: https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/installer-et-utiliser/se-connecter-et-parametrer-un-reseau/se-connecter-a-un-reseau-mobile-3-4g/comment-ajouter-un-point-d-acces-internet-apn-sur-votre-mobile-xiaomi-sous-android-_321636-856633)

Related

Android - Connecting Android Phone and Gain Span Module

I am connectiong a Gain Span wifi module to an android phone and I need the android phone connected as the Group Owner. Currently I am starting the group negotiations from the device that has the Gain Span module connected.
This works with devices such as the Nexus 5, Samsung Galaxy s2 and Samsung Galaxy s4. But when trying this with a Nexus 6p it fail all of the time. I currently thing that the issue I am having is the group owner intent on the Nexus 6p is set by default wierdly low and I need to change it before the GainSpan module initiates the group formation.
Problem is I can't seem to find a way of doing this so I still don't know for sure this is my issue.
Edit (13/10/2016):
Now thinking that the issue isn't with the GO intent. I am currently initiating the group negotiations from the gain span module using the commands:
at+p2ppd=mac,0
at+p2pgrpform=mac,listenChan,0,,1,0,0
I would prever to initiate this from the phone side as currently I have to hard code the name of the device to ensure the correct phone is connected to. This means I need to respond to a 'p2p-prov-disc-req' response from the GainSpan side, but I am unsure of how to do this. The programmers user guide says that the correct reponse is the command 'at+p2pprovok' but still im unsure of what else needs to be done.
Also I realise that the question has changed now but still open solution to the original problem. Also I have realiszed the s2 connects every time and it takes allot of attempts to get the s4 to connect and the nexus 6p doesn' connect.
Edit (14/10/2016):
Ok solved the 6p issue, it was because the 6p was connected to a via wifi to my office network. Problem is the other phones where connected to the same network and worked. Any Ideas why only the 6p would behave this way.
Per the documentation, the higher the number, the higher the odds that you will be the group owner, however this might not be 100% sure. Has the group information been persisted on the phone? Check the WiFi Direct settings on the phone and see if the group has been saved. If so, delete it and try to connect again, specifying the highest number possible.
You can edit the values of your Wifip2pConfig object. Including the groupOwnerIntent
Right ive managed to get it working on the 6p, problem is I had to disconnect it from the office wifi for it to connect. The 6p must do something wierd when being connected to network as the Galaxy s2(which worked always) was connected to the same network and so was the Galaxy s4(which worked some of the time).
So I have solved the problem but it would be more convienient if I could connect to both the internet(WiFi) and the GainSpan Module(WiFiDirect). Any Ideas why this only caused an issue on the 6p.

Android location only works on WiFi

I'm having a problem trying to get locations in a Geocatching app on Android.
For some devices my app caches all the locations and for others devices only get locations on WiFi network. Despite on this, I checked on https://maps.google.com/locationhistory and Google got all locations.
I want to get data from both, mobile and WiFi. Is there anything I'm doing wrong? How can I make it work in all devices?
I'm using ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION permissions btw.
This is an example the device that works ok, it collects mobile data as it follows the correct path:
And this, an example of the device that only works on WiFi. It links three points where I had WiFi connection.
Thanks in advance for your time!
EDIT: More info.
I get correct behaviour with HTC One, Android 4.2.2 and Nexus 5, Android 6.0.
With Sony Xperia Z3, Android 5.1.1 I only get locations when connected to WiFi.

Stuck on "Connecting to WiFi" screen while provisioning Android Lollipop device

I am trying to auto connect with WiFi when provisioning Android Lollipop device using below NFC tags:
p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_SSID, "-----");
p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_PASSWORD, "----");
It seems it is getting connected with WiFi but stuck on Connecting to Wi-fi... Screen and it is not finishing with provisioning process.
Can anybody guide me to resolve this issue?
You need to surround SSID with double quotes :
p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_SSID, "\"my SSI\"");
To make it work I had to set the also the flag android.app.extra.PROVISIONING_WIFI_SECURITY_TYPE.
Specify only the two EXTRA for SSID and PASSWORD as stated in the docs isn't enough. Probably the default security type remains NONE.
Yes, it's broken in L MR0 (Android 5.0).
However, it's my experience that it has been fixed in L MR1 (Android 5.1).
It works for us now (I work at Sony Mobile).
The fix went into ManagedProvisioning git:
https://android.googlesource.com/platform/packages/apps/ManagedProvisioning/
I've tried several things without success. The feature seems broken.
You should probably enter the WiFi info manually.

Android Wifi Direct inter-workability between ICS and JellyBean

I was testing WiFi Direct on my Android Devices. I have a Galaxy Note running 4.0.4, and a Nexus 7 running 4.2.1. I followed exactly from the official API on WiFiDirect.
After the devices found each other, if I try to make them "connect", I'll be able to see an invitation of WifiDirect connection, but after I "accept" this invitation, the status of this device changed to "invited", while on the other device (which sent the invitation initially) got no response. Thus a wifi-direct connection can never be made among the two device.
I then tried the official Wifi-Direct Demo program... but it doesn't seems to work also.
After I rooted my Galaxy Note and upgraded it to 4.1.2, this problem disappeared.
But I wonder if anyone encounter same problem as I did? And if so how did you solved it?
Thanks a lot.
To find the exact reason you have to look at the log report of wpa_supplicant(this can be seen from the log report using android debug bridge(adb) available in adt bundle with eclipse # http://developer.android.com/sdk/index.html ).
I have faced a similiar problem while trying to connect androd 4.0 tablet with ubuntu laptop.The problem was with the dhcp server which was supposed to assign an IP address after the Group negotiation is successful but it wasn't respondig may be due to difference in the versions or some other reason.This wasn't a bug with wifi direct.
I fixed it by assigning a static IP address to the p2p_wlan0 interface on both the devices.

My App works over WiFi. But not over 3G in android? Any Guesses?

I have developed an App that target version is 4 (Android 1.6) upto 7 (Android 2.1). I tested this app on the dev phone 2 (Google-Io-Device 1.6 version). I am doing some xml parsing stuff through Internet. i set the <uses-permission> on my Manifest. it works fine in WI-FI Network. But its not working in the Motorola Droid 2.1 with 3G Network. Is there any more specific stuff to do for 3G network? Any Idea?
Thanks in advance.
Edit:
My App works over WiFi Network. But not over 3G Network. Any Guesses?
Only android.permission.INTERNET. It's most likely that the server you're connecting to is only accessible from your local network, if it's behind a router/firewall. An easy test is to try to open the same URL you're trying to hit in the system Browser app.
It'd also be helpful to see the traceback from logcat.

Categories

Resources