Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] Beelink GT1 / Alfawise S92 TVStock Nexus ROM (Android TV 6.0)
Collapse
This is a sticky topic.
X
X
-
Guest
Originally posted by asadmari View Post
-
@Magendanz These apk in your ROM wont work (or even install at boot) as thy need to be signed with the same key as the other apk in your rom that use android:sharedUserId="android.uid.system"
priv-app/GamepadPairingService
priv-app/GlobalKeyInterceptor
priv-app/RemoteControlService
Can see in the pic below of logcat
I have been to pair the new xbox one controller via bluetooth without "GamepadPairingService" so unsure about its use as we are using the bluetooth implementation found in phone/tablet rather than the ATV version which is always on i believe.
Dont know what GlobalKeyInterceptor is or what it does
RemoteControlService is this needed for the nexus remote app to work ?
Edit:
FuguPairingTutorial.apk also has no use here really, as you will only see it if you reboot at the setup wizard then it will play an .mp4 clip of how to put the nexus player remote into pairing mode which wouldn't do anything even if you had one as Bluetooth is not utilized on here like atv and is off by defaultLast edited by tillaz87; 18 May 2017, 09:04.
Comment
-
actually after looking at GlobalKeyInterceptor its also targeting a higher version of android so wont work, needs changed, version api 23 here (GitHub)
Code:android:versionCode="24" android:versionName="7.0" platformBuildVersionCode="24" platformBuildVersionName="7.0"
GamepadPairingService needs signed same as "android:sharedUserId="android.uid.bluetooth"
Last edited by tillaz87; 18 May 2017, 22:58.
Comment
-
Guest
It's been a bit of a challenge getting APKs from the OpenGApps TVStock variant that don't have these issues. I've basically had to hand select them and re-sign some with the platform key. Clearly, I missed a few based on the logcat and will correct the problem this weekend. As for the target version of GlobalKeyInterceptor, the minSdkVersion and targetSdkVersion reported by aapt.exe in the metadata are both 16, and so it still should run on Android 6.0 even if it was built on SDK 24.
That said, I've found cases where the APKs were calling APIs with extra parameters only introduced in more recent SDKs. That's a bug that would normally be caught in compatibility testing, but Google seemed to have skipped this for Android TV priv-apps that ship only with new SKUs and aren't upgraded by the Google Play Store.
Comment
-
Originally posted by Magendanz View PostNo, I've made the decision to stick with the standard SystemUI (navigation and status bar) for Android TV that's used by Google in their Nexus Player. If you want the SystemUI for standard Android, you can substitute it from the Nano variant, but I find the way Android TV apps populate the notifications bar with recommendations for the Leanback Launcher to be distracting. Apparently, Google did too.
Comment
-
I've just been comparing our framework with the nexus player and mi box and noticed they are all very similar except a few things that i'm going to merge. most interesting are the configs
here are the changes i'm making
Code:1) Missing code from global_keys.xml for GlobalKeyInterceptor 2) Add and set missing ATV ui sounds to audio_assets.xml 3) Changes to input_method_extract_view.xml to match atv 4) Add missing atv animations and apply to styles.xml to match atv also set default theme to match atv 5) integer.xml change config_defaultUiModeType to match atv 6) Multi user enabled in bools.xml and AndroidManifes.xml same as stock atv 7) Change config files (bools.xml) to match nexus player some possible fixes below <!-- Boolean indicating whether the wifi chipset has dual frequency band support --> config_wifi_dual_band_support">false to true (we have the hardware 5gz and 2.4) <!-- Whether to start in touch mode --> config_defaultInTouchMode">true to false --- fix remote not working for start of setupwizard ? <!-- Override the DPad detection behavior for configuration purposes --> config_hasPermanentDpad">false to true --- fix remote not working for start of setupwizard ?
Comment
-
One of these has fixed the remote not working on first boot with first two parts of setup wizard, testing the rest of changes now
<!-- Whether to start in touch mode -->
config_defaultInTouchMode">true to false
<!-- Override the DPad detection behavior for configuration purposes -->
config_hasPermanentDpad">false to true
Comment
-
here are the changes to framework-res to better config like atv. i didn't bother doing the changes for multi user as i would have to resign
still a few things from stock atv l want mainly with the bluetooth and CanvasPackageInstaller so looking at them next
I included the old- files so can compare. see posts below for GT1.zipLast edited by tillaz87; 19 May 2017, 23:08.
Comment
-
app/FrameworkPackageStubs is also missing which is in the mi box and nexus player firmware
here is the version from mi box deodexed no sure what it does but all below are google apps in both mi player and nexus player.
all from system/appLast edited by tillaz87; 19 May 2017, 18:55.
Comment
-
so AtvRemoteService is for this to work https://play.google.com/store/apps/d...mote&hl=en (ATV remote app)
but what is RemoteControlService.apk (com.google.android.athome.remotecontrol) for ?
as its not in the mi box or shield tv. only the nexus player. looking at the manifest its something with bluetooth
Edit:
are TVsettings.apk does not utilize code to use com.google.android.tv.remotepairing (GamepadPairingService) like the nexus player Source (line114) so its no use to us.
i think the same about RemoteControlService so just removing them as are bluetooth pairing is handled different to nexus player.
Edit:
Info for com.google.android.athome.globalkeyinterceptor (GlobalKeyInterceptor.apk) which also isn't found in shield or mi box.
not much use to use ether.
Edit: if removed, and used framework-res changes above remove lines from global_keys.xml like attached
Attached FilesLast edited by tillaz87; 19 May 2017, 23:07.
Comment
-
Guest
Sorry about the 24-hour delay, but I ran into some issues with SELinux security contexts that were causing Ethernet to stop working. Took some time to track down the cause. Anyway, I want to extend a special thanks to tillaz87 for all the work he did diffing framework resources, and I think the result shows a level of UI polish that was missing before. (Now, if we can just figure out a way to allow screen casting from our phones and tablets, I'll consider this project pretty much complete.)
Here's a quick summary of the changes. As always, please let me know right away if you spot any issues.
Changelog (20170523):- New Nexus logo splash.
- Added Leanback UI sounds.
- Modified build.prop to spoof the Xiaomi Mi Box, which should circumvent some device checks.
- Modified build.prop to enable 4K output in YouTube for Android TV.
- Modified several UI settings (inc. animations & themes) in the framework to match those on the Xiaomi Mi Box and Nexus Player.
- Added FrameworkPackageStubs.apk and CanvasPackageInstaller.apk, which are present on Xiaomi Mi Box and Nexus Player.
- Removed GlobalKeyInterceptor.apk, GamepadPairingService.apk and FuguPairingTutorial.apk, which are specific to Nexus Bluetooth remotes.
- Added kernel modules (device drivers) for Sony PS3 and Dragonrise USB HID game controllers.
- Updated for latest Open GApps build (20170523).
- Updated to TWRP Recovery 3.1.1-0.
- Resolved issues with Google Keyboard and Google Leanback Keyboard, and so both are now available to set as default IME.
- Added SELinux security contexts during sparse file system creation.
- Fixed keyboard focus issue on first screen of Setup Wizard (SetupWraith).
One last request: I've now got a much better understanding of how to pre-load kernel modules so that drivers are present for any devices you might attach via USB. Other than game controllers, what devices of this type would you like to see supported?
Comment
What's Going On
Collapse
There are currently 3558 users online. 0 members and 3558 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment