Samsung Galaxy Tab 3 8.0 (samsung-lt01): Difference between revisions
touch screen doesn't work with otg keyboard fix |
No edit summary |
||
(159 intermediate revisions by 8 users not shown) | |||
Line 2: | Line 2: | ||
| manufacturer = Samsung | | manufacturer = Samsung | ||
| name = Galaxy Tab 3 8.0 | | name = Galaxy Tab 3 8.0 | ||
| codename = samsung- | | codename = samsung-lt01 | ||
| model = SM-T310, SM-T311, SM-T315 | |||
| image = File:samsung-lt01wifi.jpg | | image = File:samsung-lt01wifi.jpg | ||
| imagecaption = | | imagecaption = Photo of the Galaxy Tab 3 8.0 running postmarketOS | ||
| releaseyear = 2013 | | releaseyear = 2013 | ||
| originalsoftware = Android 4.2.2 | | originalsoftware = Android | ||
| chipset = Exynos 4212 Dual | | originalversion = 4.2.2 | ||
| pmoskernel = 6.10.0 | |||
| chipset = Samsung Exynos 4212 Dual | |||
| cpu = Dual-core 1.5 GHz Cortex-A9 | | cpu = Dual-core 1.5 GHz Cortex-A9 | ||
| gpu = Mali-400MP4 | | gpu = Mali-400MP4 | ||
Line 13: | Line 16: | ||
| display = 800x1280 | | display = 800x1280 | ||
| memory = 1.5GB | | memory = 1.5GB | ||
| architecture = | | architecture = armv7 | ||
| type = tablet | |||
| whet_dhry = 638.8 | |||
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | <!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | ||
| status_usbnet = Y | | status_usbnet = Y | ||
| status_flashing = Y | | status_flashing = Y | ||
| status_touch = Y | | status_touch = Y | ||
| status_screen = | | status_screen = P | ||
| status_wifi = | | status_wifi = Y | ||
| status_fde = | | status_fde = | ||
| status_mainline = | | status_mainline = Y | ||
| status_battery = Y | | status_battery = Y | ||
| status_3d = | | status_3d = Y | ||
| status_accel = | | status_accel = Y | ||
| status_audio = | | status_magnet = N | ||
| status_bluetooth = | | status_light = Y | ||
| status_proximity = - | |||
| status_hall = Y | |||
| status_audio = Y | |||
| status_bluetooth = Y | |||
| status_camera = N | | status_camera = N | ||
| status_gps = | | status_gps = N | ||
| status_mobiledata = - | | status_mobiledata = - | ||
| status_sms = - | | status_sms = - | ||
| status_calls = - | | status_calls = - | ||
| status_nfc = - | |||
| status_ethernet = - | |||
| booting = Y | | booting = Y | ||
| status_otg = Y | | status_otg = Y | ||
| status_barometer = - | |||
| status_powersensor = - | |||
| status_cameraflash = - | |||
| status_keyboard = - | |||
| status_touchpad = - | |||
| status_usba = - | |||
| status_irtx = N | |||
| status_irrx = - | |||
| status_stylus = - | |||
| status_haptics = - | |||
| status_dvb = - | |||
| status_sdcard = Y | |||
| status_emmc = Y | |||
| status_fossbootloader = N | |||
}} | }} | ||
=== Maintainer(s) === | |||
* [[User:knuxify|knuxify]] | |||
== Users owning this device == | |||
{{Device owners}} | |||
== How to enter flash mode == | |||
Enter download mode by holding down the {{Button|Power}} and {{Button|Volume down}} keys simultaneously until the download mode warning screen shows up, then press {{Button|Volume up}} to dismiss the warning. (Holding down the home button is not necessary on this tablet, unlike on other Samsung devices.) | |||
== Installation == | |||
See [[Installation/Using pmbootstrap]]. This section contains the device-specific information related to installing with pmbootstrap. | |||
In <code>pmbootstrap init</code>, select <code>samsung-lt01</code> as the device. You will be prompted to select a variant: | |||
* <code>wifi</code> for the SM-T310; | |||
* <code>3g</code> for the SM-T311; | |||
* <code>lte</code> for the SM-T315. | |||
=== | === Flashing === | ||
= | To flash the image to the device, enter download mode by holding down the {{Button|Power}} and {{Button|Volume down}} keys simultaneously until the download mode warning screen shows up, then press {{Button|Volume up}} to dismiss the warning. | ||
First, flash the kernel: | |||
<syntaxhighlight lang="shell-session"> | |||
$ pmbootstrap flasher flash_kernel | |||
</syntaxhighlight> | |||
The device will reboot; boot it back into download move with the above key combination. | |||
Then, flash the rootfs. To flash to the userdata partition (recommended as it has more space, but will wipe your Android data!): | |||
<syntaxhighlight lang="shell-session"> | |||
$ pmbootstrap flasher flash_rootfs --partition USERDATA | |||
</syntaxhighlight> | |||
If you want to flash the rootfs to the system partition, drop <code>--partition USERDATA</code> from the above command. | |||
== Parts and their status == | |||
{{note|If the DRM driver crashes (screen gets stuck, lines start to get blurry/dimmer), '''power off the device immediately''' as leaving it on '''WILL''' (temporarily) damage your display! Usually the damage goes away after anywhere from a few minutes to about half an hour, but it's better to be safe.}} | |||
Current issues: | |||
* RAM is limited to 1GB due to some weird quirks in how the later RAM is treated by the downstream kernel | |||
* Backlight forgets settings after suspend, resulting in choppy brightness changes | |||
* In Phosh, moving the mouse cursor around in landscape mode will cause the DRM driver to crash ("vblank wait timed out") | |||
* On one of my tablets, the screen sometimes has weird black lines on it; usually fixes itself on panel restart. Need to figure out if this is a hardware issue or if it could be worked around (the display seems to behave weirdly on startup too, maybe it's just the hardware...) | |||
* OTG works, but peripheral mode might not work after switching to OTG (if you see messages about DWC gadget init after plugging in an OTG cable, it will likely not work). This is yet to be fixed. | |||
* When plugging in headphones, the "media" key is detected to be pressed, causing a media player to be launched. (TODO, maybe it should be remapped to play/pause?) | |||
For the status of all components, see the tables below: | |||
< | {| class="wikitable feature-colors" | ||
! Element type | |||
! Element | |||
! Works? | |||
! Notes | |||
|- | |||
|Chipset | |||
|Exynos 4212 | |||
| Y | |||
| | |||
|- | |||
|Graphics | |||
|Mali-400MP4 | |||
| Y | |||
| | |||
|- | |||
|Charging IC | |||
|max77693 | |||
| Y | |||
|Supported in mainline. | |||
|- | |||
|Audio | |||
|WM1811 | |||
| Y | |||
|Speaker and headphone jack works, internal mic works (but peaks - TODO). | |||
|- | |||
|PMIC | |||
|S5M8767 | |||
| Y | |||
|Supported in mainline | |||
|- | |||
|Fuel gauge | |||
|MAX17050 | |||
| Y | |||
|Supported by MAX17042 driver | |||
|- | |||
|Touchscreen | |||
|MELFAS MMS252 | |||
| Y | |||
|Pretty much identical to the other Melfas touchscreens in mainline. Using mms114 compatible for now. Both touchscreen and touch keys work. | |||
|- | |||
|Buttons | |||
|gpio-keys | |||
| Y | |||
|Volume up/down, power and home button. | |||
|- | |||
|WiFi, Bluetooth | |||
|BCM4334 | |||
| Y | |||
|Driver in mainline. | |||
|- | |||
|Display | |||
|S6D7AA0 LSL080AL02 | |||
| P | |||
|Driver in kernel fork. See also: [https://knuxify.github.io/blog/2023/04/tab3-display.html Blog post about getting the display working]. Moderate to heavy glitching on some tablets, pending investigation. | |||
|- | |||
|Backlight | |||
|LP8556TMX | |||
| Y | |||
|PWM-controlled backlight controller. Seems to have a weird issue where setting it to 100% causes the backlight to shut down (though this is lazily worked around in my fork). Also seems to forget ROM settings after suspend. | |||
|- | |||
|Camera | |||
|Sony ISX012 and Siliconfile SR130PC20 | |||
| | |||
|Both aren't in mainline | |||
|- | |||
|IR | |||
|ABOV Semiconductor MC96FR332AUB | |||
| | |||
|The kernel option is IR_REMOCON_MC96, but REMOCON just seems to be Samsung's designation for remote controllers (given that they use it in part numbers for their TV remotes). The Kconfig description says it's a Micom(ABOV) device (Micom seems to be a generic term for microcontrollers). It's an 8-bit microcontroller, programmed with a custom firmware bundled in the kernel as <code>drivers/irda/irda_fw.h</code>. Chip markings say ABOV 332AUB 1427. Also used on the GT-N8000. [https://abov.co.kr/en/products/product_device.php?category=legacy_mcu_series&device=MC96FR332A Official site/datasheet for what seems to be the same model], [https://datasheet4u.com/datasheet-pdf/ABOV/MC96FR332A/pdf.php?id=925807 datasheet mirror]. [https://github.com/refractionware/linux/tree/tab3/ir WIP work in my kernel tree], IR led lights up but does not actually work as a remote - wrong configuration or driver bug? | |||
|- | |||
|MHL | |||
|sii9244 | |||
| | |||
|sii9234 driver seems to initialize fine, can't test because I don't own a dock; currently disabled, since this is the same chip as in the S3 and likely suffers from the same issues (phosh not starting up with dock unplugged) | |||
|- | |||
|Modem | |||
|XMM6262 (3G), Qualcomm ??? (LTE) | |||
| | |||
|XMM6262 seems to be supported by replicant but isn't yet in mainline; Qualcomm modem might be MDM9615, since that's what the S3 4G uses; didn't check the code to make sure | |||
|- | |||
|GPS | |||
|BCM47521 | |||
| | |||
|No clue about mainline support, seems to be unsupported | |||
|} | |||
=== Sensors === | |||
==== Shared ==== | |||
{| class="wikitable feature-colors" | |||
! Element type | |||
! Element | |||
! Works? | |||
! Notes | |||
|- | |||
|Hall effect/flip cover sensor | |||
|gpio-keys | |||
| Y | |||
|Simple sensor connected via GPIO. | |||
|- | |||
|Accelerometer | |||
|STMicroelectronics K2DH | |||
| Y | |||
|Seems to be compatible with LIS2DH12 | |||
|- | |||
|Magnetometer | |||
|YAS532 | |||
| P | |||
|Enabled in DTS and seems to be detected, but the values don't seem to make much sense? TODO | |||
|} | |||
==== WiFi ==== | |||
{| class="wikitable feature-colors" | |||
! Element type | |||
! Element | |||
! Works? | |||
! Notes | |||
|- | |||
|Light sensor | |||
|CM3323 | |||
|Y | |||
|Driver in mainline | |||
|} | |||
==== 3G/LTE ==== | |||
{| class="wikitable feature-colors" | |||
! Element type | |||
! Element | |||
! Works? | |||
! Notes | |||
|- | |||
|"Grip sensor"? | |||
|AD semiconductor ASP01 | |||
| | |||
|Appears to be a "Capacitive Touch/Proximity Sensor"; [https://web.archive.org/web/20231226220926/http://pdf-html.ic37.com/pdf_file_U1/20200531/pdf_pdf/uploadpdf/AD/ASP01_datasheet_1232585/200124/ASP01_datasheet.pdf datasheet]. Not 100% sure what this is used for. | |||
|- | |||
|Proximity sensor | |||
|CM36653 | |||
| | |||
|Not in mainline; likely similar to CM36651 | |||
|} | |||
== See also == | |||
* {{MR|283|pmaports}} - initial MR | |||
* {{MR|4435|pmaports}} - mainline MR | |||
* {{pmaport|device-samsung-lt01}} - device package | |||
* [https://github.com/gr8nole/android_device_samsung_lt01-common Android device (common)] | |||
* [https://github.com/gr8nole/android_device_samsung_lt01wifi Android device (lt01wifi)] | |||
* [https://github.com/gr8nole/android_kernel_samsung_smdk4x12 Downstream kernel] | |||
* [https://github.com/gr8nole/proprietary_vendor_samsung Vendor files] |
Latest revision as of 19:39, 1 February 2025
![]() Photo of the Galaxy Tab 3 8.0 running postmarketOS | |
Manufacturer | Samsung |
---|---|
Name | Galaxy Tab 3 8.0 |
Codename | samsung-lt01 |
Model | SM-T310, SM-T311, SM-T315 |
Released | 2013 |
Type | tablet |
Hardware | |
Chipset | Samsung Exynos 4212 Dual |
CPU | Dual-core 1.5 GHz Cortex-A9 |
GPU | Mali-400MP4 |
Display | 800x1280 |
Storage | 16GB |
Memory | 1.5GB |
Architecture | armv7 |
Software | |
Original software | Android |
Original version | 4.2.2 |
FOSS bootloader | no |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | yes |
postmarketOS kernel | 6.10.0 |
Unixbench Whet/Dhry score | 638.8 |
Flashing |
Works |
---|---|
USB Networking |
Works |
Internal storage |
Works |
SD card |
Works |
Battery |
Works |
Screen |
Partial |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
Works |
Audio |
Works |
Camera |
Broken |
IR TX |
Broken |
Connectivity | |
WiFi |
Works |
Bluetooth |
Works |
GPS |
Broken |
Miscellaneous | |
FDE |
No data |
USB OTG |
Works |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
Works |
Magnetometer |
Broken |
Ambient Light |
Works |
Hall Effect |
Works |
Maintainer(s)
Users owning this device
- Knuxify (Notes: SM-T310, 2x, mainlined!)
- Lordkaczuha (Notes: (SM-T310) 2x one cracked but touch works other doesn't accept touch inputs afaikt. also have plenty of replacement parts if anybody wants some lol.)
How to enter flash mode
Enter download mode by holding down the
and keys simultaneously until the download mode warning screen shows up, then press to dismiss the warning. (Holding down the home button is not necessary on this tablet, unlike on other Samsung devices.)Installation
See Installation/Using pmbootstrap. This section contains the device-specific information related to installing with pmbootstrap.
In pmbootstrap init
, select samsung-lt01
as the device. You will be prompted to select a variant:
wifi
for the SM-T310;3g
for the SM-T311;lte
for the SM-T315.
Flashing
To flash the image to the device, enter download mode by holding down the
and keys simultaneously until the download mode warning screen shows up, then press to dismiss the warning.First, flash the kernel:
$ pmbootstrap flasher flash_kernel
The device will reboot; boot it back into download move with the above key combination.
Then, flash the rootfs. To flash to the userdata partition (recommended as it has more space, but will wipe your Android data!):
$ pmbootstrap flasher flash_rootfs --partition USERDATA
If you want to flash the rootfs to the system partition, drop --partition USERDATA
from the above command.
Parts and their status
If the DRM driver crashes (screen gets stuck, lines start to get blurry/dimmer), power off the device immediately as leaving it on WILL (temporarily) damage your display! Usually the damage goes away after anywhere from a few minutes to about half an hour, but it's better to be safe. |
Current issues:
- RAM is limited to 1GB due to some weird quirks in how the later RAM is treated by the downstream kernel
- Backlight forgets settings after suspend, resulting in choppy brightness changes
- In Phosh, moving the mouse cursor around in landscape mode will cause the DRM driver to crash ("vblank wait timed out")
- On one of my tablets, the screen sometimes has weird black lines on it; usually fixes itself on panel restart. Need to figure out if this is a hardware issue or if it could be worked around (the display seems to behave weirdly on startup too, maybe it's just the hardware...)
- OTG works, but peripheral mode might not work after switching to OTG (if you see messages about DWC gadget init after plugging in an OTG cable, it will likely not work). This is yet to be fixed.
- When plugging in headphones, the "media" key is detected to be pressed, causing a media player to be launched. (TODO, maybe it should be remapped to play/pause?)
For the status of all components, see the tables below:
Element type | Element | Works? | Notes |
---|---|---|---|
Chipset | Exynos 4212 | Y | |
Graphics | Mali-400MP4 | Y | |
Charging IC | max77693 | Y | Supported in mainline. |
Audio | WM1811 | Y | Speaker and headphone jack works, internal mic works (but peaks - TODO). |
PMIC | S5M8767 | Y | Supported in mainline |
Fuel gauge | MAX17050 | Y | Supported by MAX17042 driver |
Touchscreen | MELFAS MMS252 | Y | Pretty much identical to the other Melfas touchscreens in mainline. Using mms114 compatible for now. Both touchscreen and touch keys work. |
Buttons | gpio-keys | Y | Volume up/down, power and home button. |
WiFi, Bluetooth | BCM4334 | Y | Driver in mainline. |
Display | S6D7AA0 LSL080AL02 | P | Driver in kernel fork. See also: Blog post about getting the display working. Moderate to heavy glitching on some tablets, pending investigation. |
Backlight | LP8556TMX | Y | PWM-controlled backlight controller. Seems to have a weird issue where setting it to 100% causes the backlight to shut down (though this is lazily worked around in my fork). Also seems to forget ROM settings after suspend. |
Camera | Sony ISX012 and Siliconfile SR130PC20 | Both aren't in mainline | |
IR | ABOV Semiconductor MC96FR332AUB | The kernel option is IR_REMOCON_MC96, but REMOCON just seems to be Samsung's designation for remote controllers (given that they use it in part numbers for their TV remotes). The Kconfig description says it's a Micom(ABOV) device (Micom seems to be a generic term for microcontrollers). It's an 8-bit microcontroller, programmed with a custom firmware bundled in the kernel as drivers/irda/irda_fw.h . Chip markings say ABOV 332AUB 1427. Also used on the GT-N8000. Official site/datasheet for what seems to be the same model, datasheet mirror. WIP work in my kernel tree, IR led lights up but does not actually work as a remote - wrong configuration or driver bug?
| |
MHL | sii9244 | sii9234 driver seems to initialize fine, can't test because I don't own a dock; currently disabled, since this is the same chip as in the S3 and likely suffers from the same issues (phosh not starting up with dock unplugged) | |
Modem | XMM6262 (3G), Qualcomm ??? (LTE) | XMM6262 seems to be supported by replicant but isn't yet in mainline; Qualcomm modem might be MDM9615, since that's what the S3 4G uses; didn't check the code to make sure | |
GPS | BCM47521 | No clue about mainline support, seems to be unsupported |
Sensors
Element type | Element | Works? | Notes |
---|---|---|---|
Hall effect/flip cover sensor | gpio-keys | Y | Simple sensor connected via GPIO. |
Accelerometer | STMicroelectronics K2DH | Y | Seems to be compatible with LIS2DH12 |
Magnetometer | YAS532 | P | Enabled in DTS and seems to be detected, but the values don't seem to make much sense? TODO |
WiFi
Element type | Element | Works? | Notes |
---|---|---|---|
Light sensor | CM3323 | Y | Driver in mainline |
3G/LTE
Element type | Element | Works? | Notes |
---|---|---|---|
"Grip sensor"? | AD semiconductor ASP01 | Appears to be a "Capacitive Touch/Proximity Sensor"; datasheet. Not 100% sure what this is used for. | |
Proximity sensor | CM36653 | Not in mainline; likely similar to CM36651 |
See also
- pmaports!283 - initial MR
- pmaports!4435 - mainline MR
- device-samsung-lt01PMOS - device package
- Android device (common)
- Android device (lt01wifi)
- Downstream kernel
- Vendor files