The small ~7" 16:9 displays need smaller, higher res elements,
without making TVs look terrible when docked (without forcing
wm-based dpi changes). Use 214 (~tvdpi) for density and use tvdpi
assets on atv and xhdpi assets on mobile.
Change-Id: I1d5847ef5dbb11a83e403788f4f8d757b0ec55cd
* Inputs are duplicated because the CEC HAL directly processes them while
the RC device is handled as a standard input device. This disables the
latter to stop the duplication.
Change-Id: Ifa07683b4f0509e8027630a15af6e0dbd1636452
This works together with a change to U-Boot to allow kernel and
userspace HDMI-CEC functionality to be disabled manually (or
automatically on vali). Now users who do not care about CEC do not
have to suffer from the CEC volume UI platform bug.
Change-Id: I34a89c78052193c38dc8217841a816615f135fb2
* Again, we do not plan to support vali display hacks for the
time being. If so, we will add env and do it that way.
* filter-out CEC for vali because common trees assume that unified
devices will all support CEC or none.
Change-Id: I1df0d895de870a3ebd76825fe278997e83435922
For optimal nx wifi/bt performance we want:
- nx dumped bt patchfile for tuning
- mdarcy wifi firmware for p2p support etc.
- mdarcy clm_blob for country mapping
- nx dumped wifi nvram with patched ccode for tuning
(copied to all skus)
Change-Id: I854756c89cf8b367d3f6604183f87e346689737a
We are migrating from coreboot to an ATF loader
built into hekate-ipl. This will load sc7 bins etc. along
with ATF (bl31) and U-Boot (bl33), which will chainload
kernel (as is currently the case). This also migrates to new
R2P method/driver as the new loader/ATF will stash a
copy of the bootloader in RAM so we do not have to
load a hekate payload.
Change-Id: I11e4a1810829ab3ac4c8830fd03afd6054e40bad
Completely redo DockService to:
- Work around NVIDIA hwcomposer issues
- Properly support docking
- Actually use set display preferences
Change-Id: Ic1ea73c113f291bcbe40ecd4ecca3288c88368b4
vali does not have display out, and we will not support hw hacks
at the moment. This could change, in which case we will add env
in bootloader and set prop from cmdline for hdmi display.
Change-Id: I769b8ed1d1efcc4e4aae57697c632352c98eb55a
This is a squash of the following loosely kept history:
```
Rename device settings, override the common version, and build it
Change-Id: Ifff795f77ccc299d284eed56b050dfd59c8563a3
Set display resolution, disable HW overlays and unlock screen automatically when docked
devicesettings: Add power profiles support and cleanup scaling
Code cleanup and fix docked display size setting
devicesettings: Add DPI scaling
Always disable HW Overlays
Properly handle multiple external displays rather than hardcoding ID
devicesettings: Add fan profile support
Remove internal display dpi scaling
Add nice devicesettings icon
devicesettings: Fix atv scaling by restoring past resolution on undock
devicesettings: Fix icon colour and reset power profile on unlock
Expose DeviceSettings in leanback launcher
In the future a leanback variant should be made.
DockService: Updates to support ATV display handling
devicesettings: Add HWC wake rotation workaround
Remove HW overlays workaround from DockService and use prop instead
devicesettings: Add fan coefficient setting for perf profiles
Change-Id: Idf524a50ac96e1adc299b109be9319f6cc161cd9
Cleanup DockService
dockservice: update log statements
- Adds log statement on entering HDMI disconnected block
- Changes display index logging from error to information
```
Co-authored-by: Thomas Makin <halorocker89@gmail.com>
Co-authored-by: CTCaer <ctcaer@gmail.com>
Co-authored-by: Billy Laws <blaws05@gmail.com>
Co-authored-by: Aaron Kling <webgeek1234@gmail.com>
Change-Id: I0013b598431c7ec28e95de92343f4aa25b9ee5e5
For some reason bcm fw patchfiles take way too long to load, at
least on nx and some other reference devices. 200ms seems to be
the standard as per reference devices in bcm libbt, and this
rectifies bt issues with bcm bt on nx.
Change-Id: Ifccb1129f6ac2e183490a608fafc1b230d4ece0d
* 00-android - Used to configure the hekate boot menu.
* *.bmp - Displayed by hekate in the boot menu.
Change-Id: I01016e166c5dfc4b5f50a4d1a81b8f5f3b47a8ae
* We don't care about other nv devices.
Co-authored-by: Nolen Johnson <johnsonnolen@gmail.com>
Co-authored-by: Thomas Makin <halorocker89@gmail.com>
Co-authored-by: Billy Laws <blaws05@gmail.com>
Change-Id: Ib2f7711c87df2b25d8497eebdb9e71975566a3ab
NVIDIA's hwcomposer implementation has a number of crippling issues
which we manually work around.
* It completely breaks down when default rotation is anything but 0,
so the DTB has been modified so HWC treats the display as being in
portrait (natural rotation of the panel). SurfaceFlinger now handles
the default orientation settings (ORIENTATION_270) and lock screen
rotation has been enabled previously via overlay.
* It lacks proper display duplication, so pending an OSS docking
handler service, `stb_mode` has been enabled to attempt to replicate
stock Switch behavior. NOTE: at the moment, the 2nd display out shows
as rotated 1080p.
Change-Id: Ic7d46ed0c61c9aea44faf2e91bd102f9d7360fde
* We don't need `update_js_touch_fw.sh` which is the only
thing housed in `init.loki_e_common.rc`.
Change-Id: I0025fc0fd7297af276964a73e54195cd30513be6
* 116 is the standard gpio keycode on tegra for the power button.
* Foster uses the power button to act as the pairing button.
* NX devices don't use gpio for the power button, instead wiring
it to the max mfd. So it is safe to remove this line.
Change-Id: Ib9524e76277ec0d9d7c38e717f5486d7123535a1
tmakin
Nolen Johnson
Billy Laws
Bruno Martins
