* so it recognizes the device as HD playback eligible.
Change-Id: Ic28cc9a45155a354d7b9b5e2ca665e46bfe34027
Signed-off-by: Hasaber8 <rohanhasabe8@gmail.com>
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
Testing response times to time.android.com from around the globe reveals
in ms:-
Europe <30
Middle East <68
North America <150
Johannesburg 183
Buenos Aires 220
Tokyo 226
Sydney 276
Hong Kong 285
Brisbane 295
Mumbai 349
Beijing 4691
Shanghai 4906
Russia n/a
Whilst time.android.com is NOT used for GPS NTP, North American time servers
are, by specifying north-america.pool.ntp.org as default in the framework,
to align with pixel devices. I am assuming similar response times to these
servers from around the world.
Great for North America and it appears Europe but it does not address the
global issue. Also, the pool.ntp.org project forbids both hardware and
software vendors from using these default zone names.
http://www.pool.ntp.org/en/vendors.html
It makes sense, therefore, to leverage the ntp.org's existing 'android' vendor
name to make the default ntp server for GPS purposes:
1.android.pool.ntp.org this will return a random but accurate NTP server in
close geopraphic proximity to the device.
Testing on my own build in the UK seems to improve hot and cold TTFF
considerably.
Change-Id: I144af45757efa35b32daf034eece6e046d2bde79
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
Add AID_VENDOR_THERMAL group, so that the clients of thermal-engine can
be in this group to gain access to thermal-engine sockets.
Change-Id: I10faf04ce1e26bbeb893e934d5d405d8815f452a
Enable Qualcomm codec 2.0 bufferqueue block-pool for
reducing 10% of power consumption on 1080p@30fps video playback
Test: Full video manual test
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
This property controls if the user has to enter the PIN code manually
after disconnecting the phone from the car using the bluetooth SAP
profile. When SAP profile is used, it's equivalent as moving the SIM
card from the phone into the car, and thus the default behavior is to
request the PIN code from the user. Anyway, this is usually annoying for
the user, as he might not check the screen and suddenly becomes
unreachable.
Test: adb shell getprop | grep "sap_silent_pin"
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
Add system property to differentiate devices that support enablement of
dual SIM mode from those that don't, even if they have two or more SIM
cards.
Bug: 123537730
Test: Compilation, test application
Change-Id: I6b25b778fcac40b4f7d2faa1de11f3c84ac040eb
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
* The anti-falsing implementation from HumanInteractionClassifier
regularly prevents easy swipe to unlock or to pattern / pin
on the keyguard lockscreen, requiring multiple attempts
until accepted due to a hardcoded evaluation (5.0f)
while normal usage shows better results without it
* Another solved situation is remote device access like
Vysor or TeamViewer were the device is almost impossible
to swipe properly from a computer client
Change-Id: I0c2590f56e2cf6d6cd4ff3af2341a985670168e3
Signed-off-by: Adrian DC <radian.dc@gmail.com>
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
Window animations now have rounded corners, meaning that
the shader that we use is more expensive than it used to be.
Because of this, we need to adjust the SF offsets, to make sure
that we'll have enough time to finish the GPU composition without
dropping frames.
These offsets as similar to blueline's, adjusted slightly because
we were getting false "frame missed" signals if composition
starts too early.
Change-Id: I8173e12b006bc1cab6b4cb0b3a5db9f9b3489819
Signed-off-by: ronaxdevil <pratabidya.007@gmail.com>
