My phone provider recently enabled IPv6 for data users.
https://www.google.fr/amp/s/www.bbo...en-ipv6-sur-mobile-avec-bouygues-telecom/amp/
in short, it says to edit APN settings and alter the PROTOCOL setting.
I see this setting on Android 7 on Oukitel (K6000 Plus), but not on Android 4.4 (HTC One M8).
Android 4.4 does show full IPv6 connectivity on wifi, and presents a LinkLocal IP on rmnet0.
Since rmnet0 has a LL, what's the trick to enable IPv6 discovery ? is it a limitation on Android 4.4 ? Is there a hidden setting I can tweak with am/pm/adb ? my phone is rooted. In example, on a classic Linux, I would try to echo 1 somewhere in /sys ....
If absolutely required, but I would like to avoid this method, I can put my Bouygues Sim card on the Android 7 phone to write down the IP and gateway, to manually set them on the HTC; not sure it would work; Android usually dislikes when I do this kind of workarounds ...
Related
Hi, guys!
I'm developing an app called TracePing. It is a network diagnostic tool which combines the functionality of the 'traceroute' and 'ping' programs and is similar to mtr.
Neither my provider nor my router don't support IPv6 yet, so I can test it only with link local hosts.
Can anybody who has IPv6 test any IPv6-enabled hosts like ipv6.google.com, xs4all.nl, etc?
Root is needed for IPv6 hosts because because ping6 executable has no SUID bit on ICS and up. There is no way to ping ipv6 without it. Basically, ping6 executable is useless without root...
Thanks!
I have recently been trying to flash and root my NEXUS 6 device to try and get VoLTE to work on it ; The instructions I received (at a high level) involved flashing the device with a custom ROM (I have tried LMY47D, LMY47M and LYZ28K) , rooting It, updating the qcril.db (to include my MCC/MNC) , updating the apns-conf.xml (to add my IMS APN) and finally modifying the framework-res.apk to enable the 'config_carrier_volte_available' flag for my MCC/MNC.
After doing all the above, I can confirm that I am now seeing the extra option in SETTINGS->MORE->MOBILE NETWORKS called 'Enhanced 4G LTE Mode' which I have enable along with the extra config that can be done from the *#*#4636#*#* menu.......Unfortunately , my device does not try to REGISTER with the IMS network nor do I see any extra settings on the phone (like IMS calling) to configure IMS specific settings. I have checked the android logs and can see the UE is successfully loading the IMPI,IMPU,DOMAIN and P-CSCF from the ISIM Module however nothing seems to happen.
My one observation is that my added APN (in the apns-xml file) does not show up in APN settings and I have to manually add the IMS APN., so my suspicion is that perhaps I am either not setting this properly or perhaps there is more to all this....Therefore I would like to present this challenge to the clever brains in this forum and would appreciate any guidance that I can get,
Dear all,
I'm searching for some help regarding system certificates on Android.
First of all, a little bit of context : I'm in charge of the migration of mobile devices from one Airwatch server to another. All devices are managed by MDM (Airwatch MDM Agent) that allows deployment of configuration profiles and apps. One of those profiles is called "CertAuth" and pushes some certificates that are needed to access internal ressources.
A few months ago, we have discoverd that one of the system certificates (Thawte Primary Root G3) was missing on some devices, mainly old versions of Android.
So we decided to push this certificate through the "CertAuth" profile.
Now the problem whith that method is that once the devices are unenrolled from the first server, profile "CertAuth", all corporate content and apps are removed (normal behavior). As Thawte Primary Root G3 certificate is part of the system certificates, it cannot be removed. So it is simply disabled.
This certificate is needed to access the target server, so once devices try to enroll, they receive some error message "cannot connect to host". Connection is simply refused due to the disabled Thawte G3.
Of course it can be manually enabled, but as you all may know, basic users are not always able to find the correct option in the device settings...
So (finally) my question is : is there any way to remotely enable this system certificate (little swich OFF/ON) in order to void manual action on more than 5000 devices?
By using a script or something that would be deployed on devices as third-party content/not removable content?
Hello,
I would like to clear all WiFi configurations from an app (programmatically) but not found any solution.
What I tried and it doesn't work.
WifiManager.removeNetwork
I try to use WifiManager.removeNetwork and found that it doesn't work on Android M+
then I try to set WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN to 0 with the command:
Code:
settings put global wifi_device_owner_configs_lockdown 0
and then try to WifiManager.removeNetwork again but it still doesn't work.
Remove configurations from /data/misc/wifi/wpa_supplicant.conf
Turn off WiFi then modify /data/misc/wifi/wpa_supplicant.conf and re-enable WiFi again. This method work properly on Galaxy S8 but doesn't work on Sony X Performance (my customer's main device)
WifiManager.factoryReset
This method used by Network Settings Reset (in Settings) but it is hidden and requires system privilege.
Use service call wifi <code>
To call WifiManager.factoryReset from a shell, you can use service call wifi <code> however the code depends on the Android version and the Manufacturer modifications. I found that code of factoryReset method is 63 on Android 7.0 and 7.1.1 but it doesn't work on my devices.
Device Owner
found that Device Owner App can make system setting modification, however to make an app as Device Owner requires to remove all account from device. (after make app as device owner, I can use WifiManager.removeNetwork to remove any Aps)
http://florent-dupont.blogspot.fr/2015/01/android-shell-command-dpm-device-policy.html
Can you please suggest me other solutions? (ROOT is acceptable but not a system app)
Thank you.
The "service call wifi" is soo much depending on the Android version.
On Android 9 the call for resetting wifi to factory default is:
adb shell service call wifi 59 s16 wlan0
The proper call number can be found in the IWifiManager function. Like for Android 9:
android/android-9.0.0_r35 : android/net/wifi/IWifiManager.java
Count "case TRANSACTION_" from first to last. That gives you the call number. Pretty basic but it works!
To remove stored wifi networks:
cmd netpolicy list wifi-networks #to get list, index 0...
To remove network:
service call wifi 16 i32 1 #remove the second network in the list
(note 3rd doesn't become 2nd after this command!)
No root needed.
Remember this is for Android 9! Other versions may have other call numbers.
Edit: latest wifimanager here
Cheers
Before I upgraded to Android 8 or 9 I was able to edit a file
p2p_suplicant.conf to change Wifi Direct name and passwords.
That's not the case on Android 9.
Where can I change these values?
I am running Android 10 on GP 3aXL. I have two Devices A and B connected via Wi-Fi direct. On device A, i have a proxy server running. I want to share my internet connection with device B. When i scan wifi on device B, I see SSID with the name of the remembered group on device A. I try to connect and it is asking me for the password. Where is this password info located? Tx.
m4f1050 said:
Before I upgraded to Android 8 or 9 I was able to edit a file
p2p_suplicant.conf to change Wifi Direct name and passwords.
That's not the case on Android 9.
Where can I change these values?
Click to expand...
Click to collapse
How?? What do you have to change in p2p_supplicant.conf to change Wifi direct username and password?
I'm trying to tether wifi using wifi direct, I looked into this 2 yrs back, did everything I could to change pass so that, I get a fixed pass everytime, not a randomly generated one, but I couldn't get anything to work, I thought it's not possible and gave up
You're saying you've done that, I really want to know