project slimBOXtv

Search This thread

Rainey222

Senior Member
Oct 17, 2020
78
16
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
Ok, fixed.

It seems after doing the above it didn't seems to help. " select Activity Stub"

But after a reboot all is normal, all players are listed as a choice when picking an external player.
 

lchang.atsoft

Senior Member
Oct 9, 2020
56
2
Version 11.* (Android 11) maps KEYCODE_RED to settings and KEYCODE_BLUE to all apps. Such mappings cause conflicts with apps that actually use those keys (such as StbEmu). Wondering if there is a way to disable those mappings. Thanks!
 

lchang.atsoft

Senior Member
Oct 9, 2020
56
2
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
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!
 

makis1024

Member
Dec 22, 2017
24
5
Slimhouse took the firmware from Ugoos AM7 X4 as base and created TWRP and firmware for different China boxes. All other China tv box manufacturer put some stuff together and a crappy firmware and sold X4 CPU , for low budget customers. If they would create own firmware like Ugoos firmware they wouldn't sale their boxes for 50 bugs, but for double that price.
On the other hand why should a customer buy a China cheap tv box with s905x4 and android 11 and not a s905x3 with android 9 and put slimbox Rom wich works like a charm? Slimbox for sure will fix in the future his firmware for X4 tv boxes but for the moment his x3 Roms are state of art.
 
Last edited:

SlimHouse

Member
Dec 30, 2009
33
107
Moscow
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!
<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
 

lchang.atsoft

Senior Member
Oct 9, 2020
56
2
<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
Which file is this? Thanks!
 

lchang.atsoft

Senior Member
Oct 9, 2020
56
2
<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.
 

lchang.atsoft

Senior Member
Oct 9, 2020
56
2
\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.
 

SlimHouse

Member
Dec 30, 2009
33
107
Moscow
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.smali

.method public interceptKeyBeforeDispatching(Lcom/android/server/policy/WindowManagerPolicy$WindowState;Landroid/view/KeyEvent;I)J

replace with another
 

Reaper Man

Senior Member
Dec 22, 2021
219
143
slimBOXtv 9.3 (Android 9)

Changes:
• Amendments to the settings for choosing the type of recent
• Replaced ViPER4Android with a better version
• ViPER4Android built-in startup in settings
• New logo and bootanimation in the style of Google TV
• Updated built-in applications
• System amendments

Download ATV or AOSP
 

Kash8383

New member
May 3, 2021
3
0
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
 

ath156

Senior Member
Jul 15, 2017
204
57
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
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....
 

hks18psigst

Senior Member
Aug 16, 2009
383
27
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
 

Reaper Man

Senior Member
Dec 22, 2021
219
143
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
Any 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 little :sneaky: reading for you
 

hks18psigst

Senior Member
Aug 16, 2009
383
27
Any 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 little :sneaky: reading for you
Never had to press start 1st. But I'll give it a try. And it's not bricked. It booted after a factory reset

thank you for the help i installed 2.1.6 of usb burning tool and it worked. i had 2.2.3.3..
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    slimBOXtv 42.6 & 54.6 (Android 9)

    Changes:
    • Added Acceleration button (clear memory) in TVLauncher (ATV)
    • Keyboard LeanKeyKeyboardPro is used as the main
    • Device certification in Play Protect
    • Added a large wallpaper pack for your launchers
    • Updated built-in applications
    • System amendments

    Download ATV or AOSP
    2
    slimBOXtv 11.8 (Android 11)

    Dev:SlimHouse

    Changes:
    • Amendments to the icons of the status bar and the notification curtain
    • In the settings For developers added Debugging settings
    • ViPER4AndroidFX changed to version for android 11
    • Updated built-in applications
    • System amendments

    Download ATV or AOSP
    2
    "Differences between different branches of firmware.

    There are no noticeable differences!
    In terms of functions, settings, interface, everything, if possible, is brought to uniformity and similarity.
    On your particular TVbox model, there may (or may not be) minor nuances. It is impossible to identify and describe them.
    We test, choose a branch ourselves. If something doesn't work, try another one.
    ---------------
    --- sbx_42.1x - base stock ugoos 0.4.2 (android_9);
    --- sbx_54.1x - base stock ugoos 0.5.4 (android_9).

    The Ugoos firmware stock has been upgraded for the console, with the Slim modification.
    Has advantages:
    - faster loading and response,
    - working video scaling,
    - turn on the set-top box with any IR remote control (item in the settings).
    - remembering the state of power when it is turned off.
    ---------------
    --- sbx_9.x - base set-top box stock (android_9);
    --- sbx_11.x - the basis of the stock prefix (android_11).

    The stock of the set-top box is pumped as in Ugoos firmware, with the refinement of Slim."
    , Telegram
    1
    What do you mean, can you explain ?
    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.
    1
    slimBOXtv 11.9 (Android 11)

    Changes:
    • Fixed setting wallpaper for TVLauncher (ATV)
    • The Hardware Monitor has been added to the System Panel settings
    • Updated built-in applications
    • System amendments

    Download ATV or AOSP
  • 96
    sbx_romlogo.png


    A project to create firmware for TV boxes and sticks with an Amlogic processor.

    Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9)

    Amlogic S905X4, S905W2, S905Y4 (Android 11)


    slimBOXtv ATV and AOSP are two custom firmwares suitable with some modifications for many android TV boxes.


    Version 9.3 (Android 9)

    • Amendments to the settings for choosing the type of recent
    • Replaced ViPER4Android with a better version
    • ViPER4Android built-in startup in settings
    • New logo and bootanimation in the style of Google TV
    • Updated built-in applications
    • System amendments

    Version 9.2
    • Added to the settings Autostart application
    • Power indicator goes off in sleep (Vontar X3 and similar)
    • Minimum set of built-in programs (Copyright)
    • Added new bootvideo, logo, bootanimation
    • Updated built-in applications
    • System amendments

    Version 9.1
    • Fixed pairing of Bluetooth devices
    • Changed interface settings
    • Fixed work Miracast
    • Updated and activated ViPER4AndroidFX
    • Added presets for ViPER4AndroidFX convolver
    • Added selection of bootvideo, color settings icons, logo
    • Disabled from updates in the market Atv Remote Service and Google splash screen
    • Increased the number of notification icons in the status bar to 10
    • Updated built-in applications
    • System amendments


    Version 42.5, 54.5 (Android 9)

    • Replaced ViPER4Android with a better version
    • ViPER4Android built-in startup in settings

    Version 54.4
    • Added UPlayer
    • Vontar x3 dim power indicator during operation and during sleep
    • Amendments to the display of processor temperature on the display
    • New logo and bootanimation in the style of Google TV
    • Updated built-in applications

    Version 54.3
    • Fixed problems with Chinese font
    • Added to the settings Autostart applications
    • Minimum set of built-in programs (Copyright)

    Version 54.2
    • Added new bootvideo, logo, bootanimation
    • Updated built-in applications
    • System amendments

    Version 54.1
    • Changed interface settings
    • Updated and activated ViPER4AndroidFX
    • Added presets for ViPER4AndroidFX convolver
    • Added selection of bootvideo, color settings icons, logo
    • Disabled from updates in the market Atv Remote Service and Google splash screen
    • Increased the number of notification icons in the status bar to 10
    • Updated built-in applications
    • System amendments


    Version 11.4 (Android 11)

    • Corrections to the display of icons in the navigation bar (ATV)
    • Amendments to 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

    Version 11.3
    • Rollback Magisk to version 24.3
    • Now root access works immediately after the first start of the system
    • Added new bootvideo, logo, bootanimation
    • Added to the settings Recognition of the command Ok, Google (Disable)
    • Minimum set of built-in programs (Copyright)
    • System amendments

    Version 11.2
    • Fixed work ViPER4AndroidFX

    Version 11.1
    • Changed interface settings
    • Added presets for ViPER4AndroidFX convolver
    • Added selection of bootvideo, color settings icons, logo
    • Updated built-in applications
    • System corrections


    Version 114.3 for Ugoos X4, X4Q, AM7, TOX3 (Android 11)

    • Dark theme for system app installer
    • Additional shutdown timeouts in screensaver and power saving mode
    • Added UPlayer

    Version 114.2
    • Fixed downloading applications from the market for ATV and AOSP
    • Updated built-in applications

    Version 114.1
    • Added selection of Image Scale
    • Added to the settings Autostart application
    • Installer of APK files with displaying the number of the current and updated version of the application
    • Added default launcher selection
    • Added ViPER4AndroidFX and convolver presets
    • Additional transition animation speeds
    • Added selection of bootvideo, bootanimation, color settings icons, logo
    • Disabled signature verification
    • Disabled logging to dropbox
    • Added selection of cursor, background in TVLauncher, font
    • Disabled from updates in the market Atv Remote Service, Google Screensavers, TVLauncher
    • Updated built-in applications
    • System corrections


    Supported TV boxes


    8
    SLIMBOX ver 8

    • Updated google services and apk
    ВЂ Returned the choice in the settings of a dark or white theme
    • Returned additional image settings
    • Updated firmware
    • In AOSP, I returned the recent stocks and closed the menu button
    • Added debug settings
    • Added additional power settings
    • Various system corrections
    7
    I have found out how to root SlimRom with Magisk:

    1. Root SlimRom via the settings
    Then you will have "Superuser" rooting.

    2. Install TWRP
    You don't need to, but you can install your TWRP image permanently via the TWRP app:

    3. Extract boot.img
    You need to extract "boot.img" in TWRP:
    Code:
    cat /dev/block/boot > /sdcard/boot.img

    4. Patch the stock boot.img with Magisk manager app
    Install Magisk manager apk.
    Press the upper install button and select the stock boot.img.
    Magisk will create a patched boot.img.

    5. Now unroot in SlimBox settings

    6. Flash the patched boot.img in TWRP by selecting install, then image, then choose the file, to "boot"

    7. Finally flash Magisk.zip in TWRP


    Thats it.
    5
    14.7 is out!!!
    5
    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:

    By this you can extract the stock boot.img from the stock firmware.

    This is only good for android 7 images, Android 9 (which most people are using) is totally different.
    To root slimbox you only need patch the current boot.img
    In twrp :
    cat /dev/block/boot > /sdcard/boot.img

    Then use magisk to patch the img

    Reboot to twrp

    Flash the patched boot.img to boot.

    Reboot