Another thing to be executed on boot.I found the solution:
Disable ADB
CODE: SELECT ALL
su
echo 0x1 > /sys/class/extcon/extcon0/state
Enable ADB
CODE: SELECT ALL
su
echo 0x2 > /sys/class/extcon/extcon0/state

But it's working. Thanks.
Another thing to be executed on boot.I found the solution:
Disable ADB
CODE: SELECT ALL
su
echo 0x1 > /sys/class/extcon/extcon0/state
Enable ADB
CODE: SELECT ALL
su
echo 0x2 > /sys/class/extcon/extcon0/state
Code: Select all
- unlock /system for writing
- write your sh script
- name it in manner of ##name, where ## is two digits which determines order of execution. 00 goes first, 99 last.
- put it in /system/etc/init.d
- set executive permissions for your script (chmod +x)
I don't think like you because the things that you mentioned are not of vital importance and because with Android TV pie you can do almost nothing. But apart this, the vision of Google about Android with project Treble is clear. Manufacturer like Nvidia must put all hardware realated stuff inside the vendor folder and must work with every new Android framework.SteAltH wrote:You can use init.d to autorun your sh scripts!
This ROM has init.d srcipting already activated.
All you have to do is to:And voila!Code: Select all
- unlock /system for writing - write your sh script - name it in manner of ##name, where ## is two digits which determines order of execution. 00 goes first, 99 last. - put it in /system/etc/init.d - set executive permissions for your script (chmod +x)
Zulu99, can we set "vivid colors" option through console? I really need it to be set in autorun, so no user actions be required to get adequate UI look. I'm sharing my Shield TV with relatives and they won't understand how to do these simple "About Phone" tweaks
Also i think that this ROM will need some sort of "injection" of native NVidia framework into android envirorment. Maybe this sounds impossible but that has to be done just to make this ROM compatible with future NVidia hardware adjustments. Of course we can have game recording and some other functional things by third-party apps. But it won't help when we're talking about hardware tasks like adjusting built-in LEDs or controlling gamepad charge state. To get maximum from Shield TV hardware we will need native NVidia control app aka NVidia Settings.
Without that this ROM will be only a trade-off in comparison to factory ROM.
I've tried to make my custom ROM for Shield TV some years ago and failed. I appreciate and admire your work! But NVidia Settings support it the thing that has to be done anyway. In any human and inhuman means! Even if you have to run secondary android envirorment on device just for it.
Zulu99, I believe in you! Thanks!
Code: Select all
D:\Android\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 1.900s]
Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 2985571 4k blocks and 747776 inodes
Filesystem UUID: 416f7f6e-cbd7-11e9-b60a-0bf65fd439cf
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
Sending 'userdata' (3040 KB) OKAY [ 0.108s]
Writing 'userdata' OKAY [ 0.162s]
Erasing 'cache' OKAY [ 0.080s]
Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 41bbf114-cbd7-11e9-a570-71652c387874
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
Sending 'cache' (120 KB) OKAY [ 0.024s]
Writing 'cache' OKAY [ 0.033s]
Erasing 'metadata' FAILED (remote: 'No partition present with this name.')
fastboot: error: Command failed
D:\Android\platform-tools>fastboot reboot
Rebooting FAILED (remote: 'unknown reason')
fastboot: error: Command failed
D:\Android\platform-tools>