[ROM][Full Android Oreo for Shield TV][v.1.10]

[zulu99]

just bought TPC in the hope it's as simple as just adding a file to get the thing to play pubg when im finally ready!?!?!?

ok so i just rebooted and am stuck on mobile view ie third of screen in middle of tv and I cant for the life of me remember how to put things right, anyone please

Touch profile creator is just an app to create and edit touch profiles for droidmote client. With this app you can't do nothing special that create and edit an xml file that you can load in droidmote client.

You can create and edit touch profiles also on your phone if you upload the screenshot of the game from shield tv to phone.

The touch profile is just an xml file that contain the mapping of buttons to touch actions. Is just you mapping config.


Take a look here, this is a video guide on how to use droidmote:
https://www.youtube.com/playlist?list=P ... kTajlt6TGT


The main concept is, or server and client on same device or server on tv box and client on phone.

To play with hardware controller you must enable also the droidmoteIME


You do not necessarily need full Android to play multi touch games with droidmote. Droidmote is more useful for Android TV than for full Android, but since full Android is more flexible than Android TV, it's just a gift I give to my friends who use droidmote.

[2FG]

so I cant just load the pubg xml and all is working? am also confused as to download software or hardware controller?? what is the diff??

[zulu99]

so I cant just load the pubg xml and all is working? am also confused as to download software or hardware controller?? what is the diff??

Sorry, do you have the eyes to watch this videos ?

https://www.youtube.com/playlist?list=P ... kTajlt6TGT

Or if you need a written guide, everything is wrote here:

https://www.videomap.it/dmcguide.htm

Generally, to play with DroidMote + Hardware Controller, you can install the client and the server on the same android device.

When the Client is installed, you must enable in Android keyboard settings the droidmoteIME

If droidmoteIME is enabled, when you move the stick of your hardware controller, the client automatically connect to the local droidmote server and you will see that you can control the mouse with the right stick of your hardware controller.

Now you have all set.


To play a multi touch game, you must load the touch profile for this game and enable gamepad2touch.
Therefore, on the hardware controller, click ThumL to select the downloaded touch profile and ThumbR to select gamepad2touch mode.
Press START / PLAY to disable mouse mode. ( you can press START again every time you need the mouse or change droidmote settings )




P.S.
If you have Shield TV with Android TV inside, the client on phone and the server on shield tv.
Enable droidmoteIME on Phone and the hardware controller connected to the phone via bluetooth.
Or you can just use the software controller on phone.

[TDD]

Code: Select all

C:\adb\platform-tools>adb devices
List of devices attached
0321518077208   unauthorized


C:\adb\platform-tools>adb reboot fastboot
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

C:\adb\platform-tools>adb reboot fastboot

C:\adb\platform-tools>adb devices
List of devices attached
0321451077208   device

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader...
(bootloader) Bootloader is unlocked now.
OKAY [  2.918s]
Finished. Total time: 2.920s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\system.img"
Sending sparse 'system' 1/19 (65532 KB)            OKAY [  1.725s]
Writing sparse 'system' 1/19                       OKAY [  1.409s]
Sending sparse 'system' 2/19 (65532 KB)            OKAY [  1.704s]
Writing sparse 'system' 2/19                       OKAY [  1.436s]
Sending sparse 'system' 3/19 (65386 KB)            OKAY [  1.705s]
Writing sparse 'system' 3/19                       OKAY [  1.667s]
Sending sparse 'system' 4/19 (63517 KB)            OKAY [  1.683s]
Writing sparse 'system' 4/19                       OKAY [  1.505s]
Sending sparse 'system' 5/19 (65532 KB)            OKAY [  1.734s]
Writing sparse 'system' 5/19                       OKAY [  1.359s]
Sending sparse 'system' 6/19 (63144 KB)            OKAY [  1.631s]
Writing sparse 'system' 6/19                       OKAY [  1.343s]
Sending sparse 'system' 7/19 (65532 KB)            OKAY [  1.686s]
Writing sparse 'system' 7/19                       OKAY [  1.352s]
Sending sparse 'system' 8/19 (63828 KB)            OKAY [  1.670s]
Writing sparse 'system' 8/19                       OKAY [  1.376s]
Sending sparse 'system' 9/19 (65511 KB)            OKAY [  1.760s]
Writing sparse 'system' 9/19                       OKAY [  1.617s]
Sending sparse 'system' 10/19 (62660 KB)           OKAY [  1.626s]
Writing sparse 'system' 10/19                      OKAY [  1.361s]
Sending sparse 'system' 11/19 (65532 KB)           OKAY [  1.734s]
Writing sparse 'system' 11/19                      OKAY [  1.348s]
Sending sparse 'system' 12/19 (62972 KB)           OKAY [  1.683s]
Writing sparse 'system' 12/19                      OKAY [  1.511s]
Sending sparse 'system' 13/19 (65532 KB)           OKAY [  1.695s]
Writing sparse 'system' 13/19                      OKAY [  1.421s]
Sending sparse 'system' 14/19 (63492 KB)           OKAY [  1.650s]
Writing sparse 'system' 14/19                      OKAY [  1.354s]
Sending sparse 'system' 15/19 (64195 KB)           OKAY [  1.696s]
Writing sparse 'system' 15/19                      OKAY [  1.482s]
Sending sparse 'system' 16/19 (64309 KB)           OKAY [  1.687s]
Writing sparse 'system' 16/19                      OKAY [  1.476s]
Sending sparse 'system' 17/19 (64380 KB)           OKAY [  1.696s]
Writing sparse 'system' 17/19                      OKAY [  1.361s]
Sending sparse 'system' 18/19 (65532 KB)           OKAY [  1.730s]
Writing sparse 'system' 18/19                      OKAY [  1.366s]
Sending sparse 'system' 19/19 (55422 KB)           OKAY [  1.495s]
Writing sparse 'system' 19/19                      OKAY [  1.373s]
Finished. Total time: 71.345s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\vendor.img"
Sending sparse 'system' 1/8 (65380 KB)             OKAY [  1.729s]
Writing sparse 'system' 1/8                        OKAY [  1.410s]
Sending sparse 'system' 2/8 (63745 KB)             OKAY [  1.663s]
Writing sparse 'system' 2/8                        OKAY [  1.440s]
Sending sparse 'system' 3/8 (65428 KB)             OKAY [  1.723s]
Writing sparse 'system' 3/8                        OKAY [  1.437s]
Sending sparse 'system' 4/8 (65533 KB)             OKAY [  1.696s]
Writing sparse 'system' 4/8                        OKAY [  1.626s]
Sending sparse 'system' 5/8 (65236 KB)             OKAY [  1.728s]
Writing sparse 'system' 5/8                        OKAY [  1.416s]
Sending sparse 'system' 6/8 (65532 KB)             OKAY [  1.795s]
Writing sparse 'system' 6/8                        OKAY [  1.831s]
Sending sparse 'system' 7/8 (65532 KB)             OKAY [  1.741s]
Writing sparse 'system' 7/8                        OKAY [  1.387s]
Sending sparse 'system' 8/8 (48342 KB)             OKAY [  1.305s]
Writing sparse 'system' 8/8                        OKAY [  1.208s]
Finished. Total time: 30.050s


C:\adb\platform-tools>fastboot flash boot "C:\Shield\magis
k_boot_darcy_7.1.2-v1.img"
Sending 'boot' (14115 KB)                          OKAY [  0.464s]
Writing 'boot'                                     OKAY [  0.306s]
Finished. Total time: 0.793s

C:\adb\platform-tools>fastboot flash dtb "C:\Shield\tegra2
10-darcy-p2894-0050-a04-00.dtb"
Sending 'dtb' (263 KB)                             OKAY [  0.031s]
Writing 'dtb'                                      OKAY [  0.022s]
Finished. Total time: 0.089s

C:\adb\platform-tools>fastboot -w
Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 2977379 4k blocks and 745472 inodes
Filesystem UUID: e64a514e-09ef-11e9-a5eb-eba522d81cd4
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: e66a0ec6-09ef-11e9-8ad4-9f43ac367ceb
Superblock backups stored on blocks:
        32768

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Erase successful, but not automatically formatting.
File system type No partition present with this name. not supported.
Erasing 'userdata'                                 OKAY [  0.131s]
Sending 'userdata' (3032 KB)                       OKAY [  0.093s]
Writing 'userdata'                                 OKAY [  0.085s]
Erasing 'cache'                                    OKAY [  0.024s]
Sending 'cache' (120 KB)                           OKAY [  0.027s]
Writing 'cache'                                    OKAY [  0.021s]
Erasing 'metadata'                                 FAILED (remote: 'No partition
 present with this name.')
Finished. Total time: 0.827s

C:\adb\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.018s

C:\adb\platform-tools>adb devices
List of devices attached


C:\adb\platform-tools>fastboot devices

C:\adb\platform-tools>adb devices
List of devices attached

Please do not use the word bricked when you are in bootloop.

Sorry, you're right. The reason I thought I was bricked is that none of my keyboards can use AD to get into fastboot. They only work after I get into fastboot with `adb reboot fastboot` (which I can no longer do)

But looking at my log, isn't this the wrong version? "fastboot flash boot "C:\Shield\magis
k_boot_darcy_7.1.2-v1.img"" Says 7.1.2, and I have 7.2.1, but there were no other download links. Is this fine?

@2FG So did you update fastboot/adb and then it worked? Because it can't be a roll of the dice whether it succeeds, there must be a mistake I/we made somewhere.

[zulu99]

Code: Select all

C:\adb\platform-tools>adb devices
List of devices attached
0321518077208   unauthorized


C:\adb\platform-tools>adb reboot fastboot
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

C:\adb\platform-tools>adb reboot fastboot

C:\adb\platform-tools>adb devices
List of devices attached
0321451077208   device

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader...
(bootloader) Bootloader is unlocked now.
OKAY [  2.918s]
Finished. Total time: 2.920s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\system.img"
Sending sparse 'system' 1/19 (65532 KB)            OKAY [  1.725s]
Writing sparse 'system' 1/19                       OKAY [  1.409s]
Sending sparse 'system' 2/19 (65532 KB)            OKAY [  1.704s]
Writing sparse 'system' 2/19                       OKAY [  1.436s]
Sending sparse 'system' 3/19 (65386 KB)            OKAY [  1.705s]
Writing sparse 'system' 3/19                       OKAY [  1.667s]
Sending sparse 'system' 4/19 (63517 KB)            OKAY [  1.683s]
Writing sparse 'system' 4/19                       OKAY [  1.505s]
Sending sparse 'system' 5/19 (65532 KB)            OKAY [  1.734s]
Writing sparse 'system' 5/19                       OKAY [  1.359s]
Sending sparse 'system' 6/19 (63144 KB)            OKAY [  1.631s]
Writing sparse 'system' 6/19                       OKAY [  1.343s]
Sending sparse 'system' 7/19 (65532 KB)            OKAY [  1.686s]
Writing sparse 'system' 7/19                       OKAY [  1.352s]
Sending sparse 'system' 8/19 (63828 KB)            OKAY [  1.670s]
Writing sparse 'system' 8/19                       OKAY [  1.376s]
Sending sparse 'system' 9/19 (65511 KB)            OKAY [  1.760s]
Writing sparse 'system' 9/19                       OKAY [  1.617s]
Sending sparse 'system' 10/19 (62660 KB)           OKAY [  1.626s]
Writing sparse 'system' 10/19                      OKAY [  1.361s]
Sending sparse 'system' 11/19 (65532 KB)           OKAY [  1.734s]
Writing sparse 'system' 11/19                      OKAY [  1.348s]
Sending sparse 'system' 12/19 (62972 KB)           OKAY [  1.683s]
Writing sparse 'system' 12/19                      OKAY [  1.511s]
Sending sparse 'system' 13/19 (65532 KB)           OKAY [  1.695s]
Writing sparse 'system' 13/19                      OKAY [  1.421s]
Sending sparse 'system' 14/19 (63492 KB)           OKAY [  1.650s]
Writing sparse 'system' 14/19                      OKAY [  1.354s]
Sending sparse 'system' 15/19 (64195 KB)           OKAY [  1.696s]
Writing sparse 'system' 15/19                      OKAY [  1.482s]
Sending sparse 'system' 16/19 (64309 KB)           OKAY [  1.687s]
Writing sparse 'system' 16/19                      OKAY [  1.476s]
Sending sparse 'system' 17/19 (64380 KB)           OKAY [  1.696s]
Writing sparse 'system' 17/19                      OKAY [  1.361s]
Sending sparse 'system' 18/19 (65532 KB)           OKAY [  1.730s]
Writing sparse 'system' 18/19                      OKAY [  1.366s]
Sending sparse 'system' 19/19 (55422 KB)           OKAY [  1.495s]
Writing sparse 'system' 19/19                      OKAY [  1.373s]
Finished. Total time: 71.345s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\vendor.img"
Sending sparse 'system' 1/8 (65380 KB)             OKAY [  1.729s]
Writing sparse 'system' 1/8                        OKAY [  1.410s]
Sending sparse 'system' 2/8 (63745 KB)             OKAY [  1.663s]
Writing sparse 'system' 2/8                        OKAY [  1.440s]
Sending sparse 'system' 3/8 (65428 KB)             OKAY [  1.723s]
Writing sparse 'system' 3/8                        OKAY [  1.437s]
Sending sparse 'system' 4/8 (65533 KB)             OKAY [  1.696s]
Writing sparse 'system' 4/8                        OKAY [  1.626s]
Sending sparse 'system' 5/8 (65236 KB)             OKAY [  1.728s]
Writing sparse 'system' 5/8                        OKAY [  1.416s]
Sending sparse 'system' 6/8 (65532 KB)             OKAY [  1.795s]
Writing sparse 'system' 6/8                        OKAY [  1.831s]
Sending sparse 'system' 7/8 (65532 KB)             OKAY [  1.741s]
Writing sparse 'system' 7/8                        OKAY [  1.387s]
Sending sparse 'system' 8/8 (48342 KB)             OKAY [  1.305s]
Writing sparse 'system' 8/8                        OKAY [  1.208s]
Finished. Total time: 30.050s


C:\adb\platform-tools>fastboot flash boot "C:\Shield\magis
k_boot_darcy_7.1.2-v1.img"
Sending 'boot' (14115 KB)                          OKAY [  0.464s]
Writing 'boot'                                     OKAY [  0.306s]
Finished. Total time: 0.793s

C:\adb\platform-tools>fastboot flash dtb "C:\Shield\tegra2
10-darcy-p2894-0050-a04-00.dtb"
Sending 'dtb' (263 KB)                             OKAY [  0.031s]
Writing 'dtb'                                      OKAY [  0.022s]
Finished. Total time: 0.089s

C:\adb\platform-tools>fastboot -w
Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 2977379 4k blocks and 745472 inodes
Filesystem UUID: e64a514e-09ef-11e9-a5eb-eba522d81cd4
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: e66a0ec6-09ef-11e9-8ad4-9f43ac367ceb
Superblock backups stored on blocks:
        32768

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Erase successful, but not automatically formatting.
File system type No partition present with this name. not supported.
Erasing 'userdata'                                 OKAY [  0.131s]
Sending 'userdata' (3032 KB)                       OKAY [  0.093s]
Writing 'userdata'                                 OKAY [  0.085s]
Erasing 'cache'                                    OKAY [  0.024s]
Sending 'cache' (120 KB)                           OKAY [  0.027s]
Writing 'cache'                                    OKAY [  0.021s]
Erasing 'metadata'                                 FAILED (remote: 'No partition
 present with this name.')
Finished. Total time: 0.827s

C:\adb\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.018s

C:\adb\platform-tools>adb devices
List of devices attached


C:\adb\platform-tools>fastboot devices

C:\adb\platform-tools>adb devices
List of devices attached

Please do not use the word bricked when you are in bootloop.

Sorry, you're right. The reason I thought I was bricked is that none of my keyboards can use AD to get into fastboot. They only work after I get into fastboot with `adb reboot fastboot` (which I can no longer do)

But looking at my log, isn't this the wrong version? "fastboot flash boot "C:\Shield\magis
k_boot_darcy_7.1.2-v1.img"" Says 7.1.2, and I have 7.2.1, but there were no other download links. Is this fine?

@2FG So did you update fastboot/adb and then it worked? Because it can't be a roll of the dice whether it succeeds, there must be a mistake I/we made somewhere.

don't worry, this was my error. i want write 7.2.1 but i wrote 7.1.2. Anyway the first post is correct and also the files.
with all this versions, Nvidia is confusing also me

UPDATE:
I corrected the name.....

[2FG]

ok so ive given up on the idea of using the controller. Have the server up and running on the satv and client on phone but im getting "The server is not reachable" ip address ok bluetooth on. Please advise

[2FG]

@tdd second time I used the flash all

[zulu99]

ok so ive given up on the idea of using the controller. Have the server up and running on the satv and client on phone but im getting "The server is not reachable" ip address ok bluetooth on. Please advise

Client device and server device must be connected to same router and if possible on same wifi band.
The server can be connected also with ethernet cable.

Regardless droidmote, make sure you can ping the shield tv from the phone.


But 2GF, i must admit that you have a lot of things to learn on android. Your problem is not droidmote or full android, your problem is that you are an user that want do advanced things but with a very low knowledge of android and tech in general.

I'm not criticizing you, once I was like you, too. Then the desire to learn, made me know many things. Keep it up.


Anyway if the client not see the server, can be just because you have bad network config, but an advanced user know in two seconds what is the problem. just this. This is valid for all tcp server and client not just for droidmote.

[2FG]

On that note im going to buy an extremely long Android lead :p

[zulu99]

Maybe someone did not understand the concept well and I want to explain it better.

DroidMote is more useful to Android TV than to full Android because on Android TV is the only way to play multi touch games from your couch, expecially today.

On Android TV, today, thanks to apps like ApkPure, you can install any games and play with DroidMote.

If i create and i will continue to create Full Android, is just because Full Android is more flexible than Android TV and is more compatible with apps and games.

Therefore DroidMote not earn nothing from Full Android, but maybe lose something in term of earning.

If you are an advanced user like me, Full Android is the best solution, but if you are a not tech user, you can still play games with DroidMote also with Android TV.

This is the worst gameplay that i made with PUBG MOBILE but still the Winner