Settings: modify AOSP RU translation

Changed "data_usage_menu_metered" and "data_usage_metered_title" to
state it configures Mobile hotspots, not something like APNs.

Change-Id: I40db1da7d6f4a801de5a06c6a5790580da080ebd
Settings: preferences use keys, not ids

Change-Id: I23fad40f85235db1fd2c5724ba9d3580828b14d7
settings: Remove "mobile plan"

 * Useless menu item.

Change-Id: I0b35017cb9a52600cde5d31065f007210f916a41
Bluetooth: Release pan proxy object while coming out from tethering menu

A case where user is going into tethering menu & coming out repeatedly
(2000 iterations) irrespective of Bluetooth state(ON or OFF). Setting
application get crashed after 1386 iterations. Each time TetherSetting
& BluetoothPan object were leaked, because connection of the pan profile
proxy to the Service was not closed by tetherSetting while coming out
from tethering menu. Releasing the pan proxy object while coming out
from tethering menu to avoid memory/objects leak.

Change-Id: I06a5e1ed37a024695fddb1e95f62b72fd56510d3
CRs-Fixed: 622489
Fixes error message during pairing of HOGP devices

When incorrect pin key is entered by user in
the pairing pop up while pairing with a HOGP
device, no error message regarding the failure
is displayed to the user.

CRs-fixed: 618905
Change-Id: I1a5a8baf9ef6c71bf285a28b3e1839fe5ddbca95
Bluetooth: Increase allowed duration to connect to a profile

This patch increases the duration allowed between the first device
connection attempt (immidiately after bonding) and profile connection
after service discovery from 5 seconds to 30 seconds to allow
HOGP connections for slow connection conditions.

Change-Id: I5b17bd0bd2b560709e6e67e2d83f9bca7ea2509d
CRs-Fixed: 612105
P2PSetting:Avoid p2p_find on group removal event

Immediately after group termination p2p_find is being issued
from settings and this causing issue whenever user sends
connection request immediately after group_removal_event.

Change-Id: I6ae90a1d710e0e977a1dbc171398fd270dc30183
CRs-Fixed: 622597
Packages : Fix for Softap turn ON/OFF fail issue.

If Softap is enabled using third party applications which make use
of WifiManager APIs, Softap enable fails. This is due to improper
handling of Softap State change event.

To resolve this issue, handle the Softap state change intent with
proper initialization of variable "mWaitForWifiStateChange".

CRs-Fixed: 634896
Change-Id: I63f8845ec3e8ebfa8ec09a7b1a1bc4ee175336cf
[2/2] CPUFreq Tile

Change-Id: If84df3f2779434af78c3eb842d049a62b9f159a7