Jump to content

ASUS Transformer Pad (asus-tf300t): Difference between revisions

From postmarketOS Wiki
Replace Category:Unsupported device with Category:Not booting and remove Category:Device (since the infobox template sets that anyway!)
MartijnBraam (talk | contribs)
No edit summary
Line 22: Line 22:
* jonty-comp
* jonty-comp
* Jasper (working on [[ASUS Transformer Pad Infinity]])
* Jasper (working on [[ASUS Transformer Pad Infinity]])
* MartijnBraam


== What works ==
== What works ==


* Compiling CM13 kernel ([https://github.com/LineageOS/android_kernel_asus_tf300t GitHub])
* Compiling CM13 kernel ([https://github.com/LineageOS/android_kernel_asus_tf300t GitHub])
* Compiling 4.14-rc3 with tf300t specific patches
* Flashing via Android recovery zip (Boot image included)
* Flashing via Android recovery zip (Boot image included)
* System boots
* System boots
Line 37: Line 39:
The framebuffer issue is an interesting one as it works without issue on CM13-based Android ROMs with the same kernel and defconfig.  Possible toolchain issue or patch needed for GCC6.
The framebuffer issue is an interesting one as it works without issue on CM13-based Android ROMs with the same kernel and defconfig.  Possible toolchain issue or patch needed for GCC6.
Devices with a working framebuffer output modesetting information in <code>dmesg</code> after loading the tegradc driver, but the PMOS compiled kernel does not.  Common fixes including setting values in <code>/sys</code> have no effect yet.
Devices with a working framebuffer output modesetting information in <code>dmesg</code> after loading the tegradc driver, but the PMOS compiled kernel does not.  Common fixes including setting values in <code>/sys</code> have no effect yet.
== Fastboot issue ==
It seems like the bootloader doesn't handle flashing the boot and userdata partition correctly, the official firmware package flashes an "Android blob" to the staging partition with fastboot which triggers an flashing screen on the tablet which copies the data to the correct partitions.
It looks like someone made a tool to generate the android blob files here: https://github.com/AndroidRoot/BlobTools

Revision as of 20:58, 17 January 2018

ASUS Transformer Pad
ASUS Transformer Pad
ASUS Transformer Pad
Manufacturer ASUS
Name Transformer Pad
Codename tf300t
Released 2012
Hardware
Chipset Nvidia Tegra 3 T30
CPU Quad-core 1.2 GHz Cortex-A9
GPU ULP GeForce
Display 1280x800 IPS
Storage 16/32 GB
Memory 1 GB
Software
Original software Android 4.0 on Linux 3.1
postmarketOS
Category testing
Pre-built images no
Mainline no
Features
Flashing
No data
USB Networking
No data
Internal storage
No data
SD card
No data
Battery
No data
Screen
No data
Touchscreen
No data
Multimedia
3D Acceleration
No data
Audio
No data
Camera
No data
Camera Flash
No data
Connectivity
WiFi
No data
Bluetooth
No data
GPS
No data
NFC
No data
Modem
Calls
No data
SMS
No data
Mobile data
No data
Miscellaneous
FDE
No data
USB OTG
No data
HDMI/DP
No data
Sensors
Accelerometer
No data
Magnetometer
No data
Ambient Light
No data
Proximity
No data
Hall Effect
No data
Haptics
No data
Barometer
No data


None of this work has been merged upstream. Check out the work-in-progress here or contact jonty-comp on IRC.

Contributors

What works

  • Compiling CM13 kernel (GitHub)
  • Compiling 4.14-rc3 with tf300t specific patches
  • Flashing via Android recovery zip (Boot image included)
  • System boots
  • Most sensors/cameras/devices seem to be detected (e.g. accelerometer values can be read from /sys etc)

What does not work =

  • Flashing via fastboot (device appears to write successfully but then locks up and does not apply the uploaded image)
  • Framebuffer (stuck on ASUS bootloader graphic)

The framebuffer issue is an interesting one as it works without issue on CM13-based Android ROMs with the same kernel and defconfig. Possible toolchain issue or patch needed for GCC6. Devices with a working framebuffer output modesetting information in dmesg after loading the tegradc driver, but the PMOS compiled kernel does not. Common fixes including setting values in /sys have no effect yet.

Fastboot issue

It seems like the bootloader doesn't handle flashing the boot and userdata partition correctly, the official firmware package flashes an "Android blob" to the staging partition with fastboot which triggers an flashing screen on the tablet which copies the data to the correct partitions.

It looks like someone made a tool to generate the android blob files here: https://github.com/AndroidRoot/BlobTools