In the cellular options, you can only choose between 2G and 3G, even if your provider and contract is LTE compatible.

Workaround

In phone dial menu, enter Code

*#*#46368676#*#*

Wait a few seconds afterwards, until a new menu is opened (you do not see it is loading, but you have to wait a bit).

Choose the first menu entry, then choose your preferred LTE option.

After changing the preferred network type, it should connect via LTE immediately.

Unfortunately, it seems like this setting cannot be save persistantly; it disappears after reboot.

So as an another workaround, it might be a good idea to use the app 4G Switcher, which enters the digit code for you to enter the extended menu.

Reference

 [:]

Get it via Google Play Store.

 [:]

All you need is a Micro SD card for the copying process.

1. Get your contacts in VCF format. They should be all in one VCF file. You can e.g. extract them from Outlook and merge them.
2. Copy your .vcf file to the Micro SD card and rename it to “backup.dat”. Notice the .dat extension, it is important.
3. Insert SD card in your mobile and start it.
4. Enter: Contacts -> Settings -> Restore contacts (this option is not visible if the phone does not find backup.dat!)
5. Confirm, wait some seconds. Afterwards you should have your phonebook set up.

[:]

Run these commands to install StrongSwan:

apt-get update
apt-get install strongswan
apt-get install strongswan-plugin-eap-mschapv2

Firewall settings:

iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
apt-get install iptables-persistent

After installing iptables-persistent, confirm to save the current rules when finishing the wizard.

Open /etc/sysctl.conf with vi or nano and modify or add these lines:

net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 1
net.ipv4.conf.default.arp_accept = 1
net.ipv4.conf.default.proxy_arp_pvlan = 1

Move ipsec.conf and strongswan.conf original files:

sudo mv /etc/ipsec.conf /etc/ipsec.conf.backup
sudo mv /etc/strongswan.conf /etc/strongswan.conf.backup

New content for /etc/ipsec.conf:

config setup
      strictcrlpolicy=no

conn %default
    keyexchange=ikev2
    

 conn rem
    rekey=no
    leftsubnet=0.0.0.0/0
    leftauth=psk
    leftid=xxx.xxx.xxx.xxx     #your external ip
    right=%any
    rightsourceip=192.168.2.1/29  #(if behind router check your router ip MUST be different, my router ip is 192.168.10.1)
    rightauth=eap-mschapv2
    rightsendcert=never
    eap_identity=%any
    auto=add

New content for /etc/strongswan.conf:

charon {
    threads = 16
    dns1 = 208.67.222.222    #(you can choose yours)
    dns2 = 208.67.220.220
 }

 pluto {
 }

 libstrongswan {
 }

New content for /etc/ipsec.secrets:

: PSK "FREE_CHOICE1"       #(Gateway Preshared Key)
alice : EAP "FREE_CHOICE2"    #(MSCHAPv2 Username)
bob  : EAP "FREE_CHOICE3"    #(MSCHAPv2 Password)

Configure your firewall / router: Open incoming UDP ports 500 and 4500 to be redirected to your VPN server’s local IP address.

Open your BB10 mobile’s connection settings and create a new VPN profile:

Leave the default values for the other settings.

For testing, make sure you have disabled your local WiFi access.

Reference[:]

You are using an IP intercom like 2N Helios IP or a Mobotix product.

You have an electronic door lock like G-U Secury Automatic which is connected to any home automation system like KNX, and you use a server system like Gira Homeserver, Loxone Miniserver, Wiregate or a custom EIBd system.

So you might be looking for an app for your mobile phone (or maybe in-wall tablet) to use it as a doorbell, camery display and remote door lock control.

Some Android apps already exist from the hardware manufacturers, e.g. 2N Helios IP Mobile. But they are quite expensive and error-prone. E.g. it does not work over VPN, does not save the chosen intercom and seems to be buggy when using WLAN connection.

Solution

Because I could not find an existing app which works stable and covers all these features, I wrote one.

You can download it for free via Android Play Store: DXSdata IP Intercom Doorbell

With this app, you can:

• Display any camera image from an HTTP source, e.g. 2N Helios: http://[intercom-ip]/enu/camera640x480.jpg
• Push an app button to open the door (e.g. your KNX server gets the HTTP command and closes a relay which opens the lock)
• Get a popup on your phone or tablet if someone is at your door and pushes the doorbell button (e.g. call your mobile phone’s local IP or DNS name like “http://[your-ip]:8787/?action=bringDoorbellAppToFrontAndRing”)
• Some Android devices which have Ethernet ports (e.g. HP Slate 21 Pro) do not have an option to keep the LAN connection awake. This can be a problem because your doorbell cannot find the device in the network, e.g. to bring the app to front if someone is at the door. So there is an option in the IP Intercom Doorbell app to keep LAN alive.

Scenario

You want to configure a VPN connection to your firewall. It does not work on Android 4.0.4, but the same settings work in 4.1.x and above.

Used in this example: VPN method L2TP IPsec PSK, Samsung GT-P7501, Dell Sonicwall tz 210

Problem

According to some googlecode threads, this is a bug which has not been solved for years.

http://code.google.com/p/android/issues/detail?id=23124

Solution

If possible, upgrade to a higher Android version the official way.

Unfortunately, there seems to be no solution which works without rooting the device, because for devices like the Samsung Galaxy Tab 10.1 the latest official Android version is 4.0.4.

So another way would be changing the OS to Cyanogenmod 10.2 or similar, but it is a matter of opinion to use it because it is not supported officially. CM11 also seems not to be supported on this device.

The most effective way for me finally was to root the tablet and change the “racoon” file.

Steps

Root the device. KingoApp which runs under Windows is very comfortable for doing this.

Look at the google code thread -> #203. Download the modified racoon file.

Establish an ADB connection to your Android device. If you do not want to install the full Android SDK, there are portable packages available (google “adb tools” etc.).

Open cmd, go to your ADB folder, note the location of your racoon file and execute:

1. adb shell
2. su
3. mount -o rw,remount /system
4. chmod 777 /system/bin/racoon
5. exit
6. adb push racoon /system/bin/
7. adb shell
8. su chmod 777 /system/bin/racoon
9. reboot

Then retry your VPN connection.

Scenario

You want to configure a VPN connection to your firewall. It does not work on Android 4.0.4, but the same settings work in 4.1.x and above.

Used in this example: VPN method L2TP IPsec PSK, Samsung GT-P7501, Dell Sonicwall tz 210

Problem

According to some googlecode threads, this is a bug which has not been solved for years.

http://code.google.com/p/android/issues/detail?id=23124

Solution

If possible, upgrade to a higher Android version the official way.

Unfortunately, there seems to be no solution which works without rooting the device, because for devices like the Samsung Galaxy Tab 10.1 the latest official Android version is 4.0.4.

So another way would be changing the OS to Cyanogenmod 10.2 or similar, but it is a matter of opinion to use it because it is not supported officially. CM11 also seems not to be supported on this device.

The most effective way for me finally was to root the tablet and change the “racoon” file.

Steps

Root the device. KingoApp which runs under Windows is very comfortable for doing this.

Look at the google code thread -> #203. Download the modified racoon file.

Establish an ADB connection to your Android device. If you do not want to install the full Android SDK, there are portable packages available (google “adb tools” etc.).

Open cmd, go to your ADB folder, note the location of your racoon file and execute:

adb shell

su

mount -o rw,remount /system

chmod 777 /system/bin/racoon

exit

adb push racoon /system/bin/

adb shell

su chmod 777 /system/bin/racoon

reboot

Then retry your VPN connection.

I ordered a Wireless Charging Receiver like it is mentioned here. You simply need to insert the module between the battery and the back cover, and connect the Micro USB port.

Unfortunately, if you place the module on the default position, it covers almost the whole battery, so NFC does not work any more afterwards.

After some tests, I found out there is a workaround to keep NFC enabled also. The trick is to place the model about 1 cm below its default position. Now the black end line with the Micro USB connector is too long, but you can fold it carefully so it fits under the cover.

If you test NFC now e.g. with an NFC hardware button, you should have a good NFC signal if you place the button near the “Samsung” sign at the back cover.

You use your own Exchange 2010 server with a self-signed certificate. So you need your root certificate to be copied to the client before you can access the server.

Same with Android 4.x, but a quite useless “feature” was implemented with this main version: If you copy and install your certificate the common way (so it gets into the user certificates folder), you get some restrictions for your lockscreen – e.g. you must a password to unlock your screen, even if this isn’t enabled in your Exchange server’s policy.

Workaround

Android is a bit stricter with self-signed (root) certificates, so we have to copy it into the directory where the pre-installed certs reside. Please note: 4.0? (and before?) handles certificates another way, please see this blog instead. This explanation however is for 4.1.

Prerequisites: Rooted phone.

First install your CA certificate the usual way, e.g. send via Bluetooth and copy it to the root of your interal memory card.

Then copy it from /data/misc/keychain/cacerts-added/[yourcertfilename] to /system/etc/security/cacerts. This is a bit tricky because you do not have write permissions to the system partition by default. Maybe there is a root capable explorer app which can re-mount the partition itself (haven’t heard of such one yet), I did it via “adb” anyway.

You can get adb from the Android SDK, you can then run it from Windows command line like “adb shell” and you get access to your phone with usual Linux commands.

Connect your phone, start “adb shell”, run “su” and then re-mount the /system partition like it is explained here (nearly at the page bottom).

If copying succeeded, remove the certificat from the personal store (the original directory) and reboot your phone.

If you still have problems with using non-secure lockscreen options, remove your Exchange account from the phone, check if there are any device administrators left (if yes, delete them), and press settings->security->remove permissions. Then reboot your phone, reconfigure your Exchange account and everything should work fine.

Reference

The simplest, but also expensive way is to register at a GPS locating site where you also get your tracking hardware. You could also buy the hardware yourself, but these items are not cheap basically.

So here is my workaround:

1. Get an old Symbian or Android mobile which has built-in GPS and maybe 3G/UMTS support. You can get such phones used under 50 € at ebay or similar sites. We use them as the tracking device.
2. Register at http://phonelocator.mobi. It is completely free and you do not have to enter any sensitive data.
3. If you don’t have a SIM card for your device, get a cheap (or free) one with a good data flatrate. If you are Austrian, have a look at provider drei which offers 20 MB data per day for free.
4. Insert the SIM card in your tracking phone and get the free Phonelocator app from the store.
5. Log in with the data you registered before. Also set Autostart to On if you want to.
6. Do a test update in the app. The GPS or cell data should be transferred to the Phonelocator website.
7. Find a good place in your car etc. where you get a good GPS signal.
8. You are ready to track.

With “normal” phones this feature may be okay, but e.g. with a tablet like Samsung Galaxy Tab it can be annoying when using the loudspeaker or a headset.

Solution:

Install the app Caffeine. This was the only way I found to make the display stay awake during a call.