User: makis1024 explained previously,
V9.2 is rooted by SuperSu
v54.5 -(Ugoos based firmware?) -root can be selected either by SuperSu or Magisk methods.
Otherwise they look identical(?)
User: makis1024 explained previously,
Ok, fixed.Is there any way to clear the default browser app in slimbox 15 on x96max plus2.
See pic attached, can I unselect the radio button? Or is there other way to clear.
The problem is, is when running other programs and chosing an external player, my players don't all show up.
ever since I've selected a default browser as soul.
My other box where the default browser is still set to none (nothing selected) I get 15 players show up to select from.
This box with soul browser selected as default browser removes VLC player from the list even if it was already chosen is the default player.
If I select Activity Stub then VLC will show up but I'm still missing 10 other players. The program that I'm trying to select a player in is bubbleUPnP. But players missing in other apps as well, seems hit and miss in different apps for MX player to show up in the popup list to chose an external player.
It's odd these boxes are the same hardware with the same programs installed but act so different when trying to use external players.
I might have to factory reset if all else fails.
Thanks Rainey
Hi Reaper Man & @SlimHouse,slimBOXtv 11.4 (Android 11, based on factory firmware)
Changes:
• Corrections in the display of icons in the navigation bar (ATV)
• Corrections in the operation of the power button in the navigation bar
• Fixed display of thumbnails in recent
• Fixed setting wallpaper for TVLauncher (ATV)
• Fixed downloading applications from the market for ATV and AOSP
• New logo and bootanimation in the style of Google TV
• Updated built-in applications
<key component="com.droidlogic/.GlobalKeyReceiver" dispatchWhenNonInteractive="true" keyCode="KEYCODE_F1" />Hi Reaper Man & @SlimHouse,
With Version 11.* AOSP (Android 11). KEYCODE_RED is mapped to "settings" and KEYCODE_BLUE is mapped to "all apps". Such mappings cause conflicts with apps that actually use those keys (such as StbEmu). I have tested the SlimBox firmware on both Tanix X4 and X96Max+ Ultra boxes and they both behave the same way. The original factory firmware doesn't behave like this. I am wondering what was added in SlimBox to define such mappings, and if there is a way to turn them off. Thank you for your help!
Which file is this? Thanks!<key component="com.droidlogic/.GlobalKeyReceiver" dispatchWhenNonInteractive="true" keyCode="KEYCODE_F1" />
<key component="com.droidlogic/.GlobalKeyReceiver" dispatchWhenNonInteractive="true" keyCode="KEYCODE_F2" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_SETTINGS" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_PAIRING" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_F6" />
perhaps it
I located the global_keys.xml inside framework-res.apk. It didn't define anything related to KEYCODE_RED or KEYCODE_BLUE. I copied framework-res.apk from the original factory stock firmware to replace the file in SlimBox, The result is still the same. Those two keys are still being mapped. So it's not framework-res.apk.<key component="com.droidlogic/.GlobalKeyReceiver" dispatchWhenNonInteractive="true" keyCode="KEYCODE_F1" />
<key component="com.droidlogic/.GlobalKeyReceiver" dispatchWhenNonInteractive="true" keyCode="KEYCODE_F2" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_SETTINGS" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_PAIRING" />
<key component="com.droidlogic/.GlobalKeyReceiver" keyCode="KEYCODE_F6" />
perhaps it
\system\framework\framework-res.apk
As I said in the previous post, \system\framework\framework-res.apk is not the source of the mappings. I replaced the file with the one from the factory stock, and the mappings are still there. Any other ideas where the mappings might be defined?
I located the global_keys.xml inside framework-res.apk. It didn't define anything related to KEYCODE_RED or KEYCODE_BLUE. I copied framework-res.apk from the original factory stock firmware to replace the file in SlimBox, The result is still the same. Those two keys are still being mapped. So it's not framework-res.apk.
It took me a while, but I finally found it. The mappings are implemented in /system/framework/services.jar, in a method named interceptKeyBeforeDispatching(). Now I just need to figure out how to modify it.
PhoneWindowManager.smaliIt took me a while, but I finally found it. The mappings are implemented in /system/framework/services.jar, in a method named interceptKeyBeforeDispatching(). Now I just need to figure out how to modify it.
.method public interceptKeyBeforeDispatching(Lcom/android/server/policy/WindowManagerPolicy$WindowState;Landroid/view/KeyEvent;I)J
Most probably you will never get an Ugoos port (like 54.3) for IT6334. I wish that I am wrong, but sadly I don't think so....I am using Rk1 and H96max x3 (with wi-fi module IT6334 (blue board ). The best running so far on x3 modules is version 54.3. Excellent work and thanks for sharing a great smooth running firmware. Can I please request 54.3 for H96MAX x3 (For revision with wi-fi module IT6334 (blue board ). Many thanks
Is it not only the difference of WiFi and Bluetooth chip drivers?Most probably you will never get an Ugoos port (like 54.3) for IT6334. I wish that I am wrong, but sadly I don't think so....
Any number of things:i have a magicsee n5 max x3 and i had an error on boot sent me to recovery i did a factory reset. it boots up. but now i'm trying to update and when i connect to PC via usb i get the connect then disconnect sound right after. any idea whats going on? thanks
Never had to press start 1st. But I'll give it a try. And it's not bricked. It booted after a factory resetAny number of things:
Chances are you need to press> Start< before you attach the USB cable.
(Before proceeding...you do know how to Unbrick your device?)
A littlereading for you
Amlogic USB Tool Troubleshooting. - FreakTab
Amlogic USB Burn Tool not recognizing your China Box? Did USB Burn Tool Work before, but now ..hours of fail?? Amlogic Worldcup Drivers..no longer installedforum.freaktab.com
On 3.1 or higher you have to wait before pressing the start button until the PC recognize the tv box. On any 2 Amlogic burning tool you have to push the start button right away and connect the tv box to the PC with pressed start button.
cat /dev/block/boot > /sdcard/boot.img
3. Extract boot.img from stock firmware
You need to have a stock rom for your device.
Ideally a zipped rom, so that you can extract the "boot.img" out of it.
In case you have an img-file, than you need to extract "boot.img" out of it via Amlogic toolkit:
GitHub - natinusala/linux-amlogic-toolkit: Allows to unpack and repack AMLogic images for Android 7 without the Customization Tool
Allows to unpack and repack AMLogic images for...github.com
By this you can extract the stock boot.img from the stock firmware.