Samsung Galaxy Note II LTE (samsung-t0lte): Difference between revisions
Jack Kekzoz (talk | contribs) m kernel upgraded |
Jack Kekzoz (talk | contribs) |
||
(35 intermediate revisions by 8 users not shown) | |||
Line 6: | Line 6: | ||
| imagecaption = Galaxy Note II | | imagecaption = Galaxy Note II | ||
| releaseyear = 2012 | | releaseyear = 2012 | ||
| originalsoftware = Android 4.1.1 on Linux 3.0.31 | | originalsoftware = Android | ||
| pmoskernel = | | originalversion = 4.1.1 on Linux 3.0.31 | ||
| chipset = Exynos 4412 Quad | | pmoskernel = 6.10.0 | ||
| chipset = Samsung Exynos 4412 Quad | |||
| cpu = Quad-core 1.6 GHz Cortex-A9 | | cpu = Quad-core 1.6 GHz Cortex-A9 | ||
| gpu = Mali-400 MP4 | | gpu = Mali-400 MP4 | ||
Line 15: | Line 16: | ||
| memory = 2 GB | | memory = 2 GB | ||
| architecture = armv7 | | architecture = armv7 | ||
| type = handset | |||
<!-- 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 | ||
Line 42: | Line 44: | ||
<!-- you can also use these lines if you need to: | <!-- you can also use these lines if you need to: | ||
if the device haven't originally ran Android OS, e.g. Nokia N900 | if the device haven't originally ran Android OS, e.g. Nokia N900 | ||
see Unixbench page on wiki | see Unixbench page on wiki | ||
| whet_dhry = 0.0 | | whet_dhry = 0.0 | ||
Line 64: | Line 65: | ||
If you have installed a custom recovery, then when the phone is powered off, press and hold down the {{Button|Home}}, {{Button|Volume Up}} and {{Button|Power}} buttons to turn it on in Recovery mode. | If you have installed a custom recovery, then when the phone is powered off, press and hold down the {{Button|Home}}, {{Button|Volume Up}} and {{Button|Power}} buttons to turn it on in Recovery mode. | ||
== Preparation == | |||
<code>pmbootstrap init</code> will prompt to choose a (near-mainline) kernel, which depends on the device display panel, see [[Samsung_Galaxy_Note_II_(samsung-t03g)#Hardware | samsung-t03g display]]. | |||
== Installation == | == Installation == | ||
Line 72: | Line 76: | ||
== FDE == | == FDE == | ||
FDE works | FDE works ON OSK-SDL - not tested on unl0kr yet - although not with hardware acceleration. | ||
== Audio == | == Audio == | ||
Line 78: | Line 82: | ||
== Bluetooth == | == Bluetooth == | ||
Note: as of ~v24.06, only the non-free firmware package is available. The following is retained for informational purposes only. | |||
Without the non-free firmware package, there may be some limited Bluetooth functionality [https://redmine.replicant.us/issues/1928]. If this occurs, it is probably because there is some code in the ROM of the BCM4334 chip. It is recommended to toggle Bluetooth off in this state, as the chip is designed to only work properly with the firmware patch, and unexpected issues may occur without it. | Without the non-free firmware package, there may be some limited Bluetooth functionality [https://redmine.replicant.us/issues/1928]. If this occurs, it is probably because there is some code in the ROM of the BCM4334 chip. It is recommended to toggle Bluetooth off in this state, as the chip is designed to only work properly with the firmware patch, and unexpected issues may occur without it. | ||
Line 91: | Line 97: | ||
In the long run, the Replicant project hopes to ask Cypress Semiconductor Corp. if they are willing to release the source code to the firmware under a permissive licence [https://redmine.replicant.us/issues/1937]. | In the long run, the Replicant project hopes to ask Cypress Semiconductor Corp. if they are willing to release the source code to the firmware under a permissive licence [https://redmine.replicant.us/issues/1937]. | ||
== Touchkeys == | |||
The Back touchkey can be used for navigating back (mainly in Firefox, but also in other contexts). The Menu touchkey does nothing by default, but it can be assigned in the phosh settings. | |||
If you wish, you can run this script in a terminal in the background to give you some haptic feedback and to illuminate the touchkey LEDs for 1 second when they are touched - you will need to install evtest beforehand though. It is a bit of a hack, so won't be bundled in postmarketOS by default: | |||
<pre> | |||
#!/bin/sh | |||
device='/dev/input/by-path/platform-i2c-gpio-4-event' | |||
event_back='*code 158 (KEY_BACK), value 1*' | |||
event_menu='*code 139 (KEY_MENU), value 1*' | |||
evtest "$device" | while read line; do | |||
case $line in | |||
($event_back) fbcli -E button-pressed | |||
echo 1 > /sys/class/leds/tm2-touchkey/brightness | |||
sleep 1 | |||
echo 0 > /sys/class/leds/tm2-touchkey/brightness ;; | |||
($event_menu) fbcli -E button-pressed | |||
echo 1 > /sys/class/leds/tm2-touchkey/brightness | |||
sleep 1 | |||
echo 0 > /sys/class/leds/tm2-touchkey/brightness ;; | |||
esac | |||
done | |||
</pre> | |||
== Camera == | |||
When Megapixels 2.0 is released, Back camera will be able to take photos with no need to run commands beforehand, thanks to a recent added feature. Photos will be taken at a resolution of 2304x1296. | |||
[[File:IMG20241211141850.jpeg|200px|thumb|left|Merry Christmas from my t0lte running Megapixels 2.0 in postmarketOS on Linux 6.10.0]] | |||
== Hardware == | == Hardware == | ||
Line 105: | Line 144: | ||
|- | |- | ||
| Panel | | Panel | ||
| Samsung S6EVR02 LCD panel | | Samsung S6EVR02 / Magnachip EA8061 LCD panel | ||
| N | | N | ||
| But | | But they are in the exynos4-mainline repo [https://gitlab.com/exynos4-mainline/linux/-/blob/exynos4/6.10.0/drivers/gpu/drm/panel/panel-samsung-s6evr02.c 1] [https://gitlab.com/exynos4-mainline/linux/-/blob/exynos4/6.10.0/drivers/gpu/drm/panel/panel-magnachip-ea8061.c 2]. | ||
|- | |- | ||
| Touchscreen | | Touchscreen | ||
Line 131: | Line 170: | ||
| Modem | | Modem | ||
| MDM9615 | | MDM9615 | ||
| | | N | ||
| | | This modem is also found in [[Samsung_Galaxy_S_III_LTE_(samsung-m3)|samsung-m3]] (GT-i9305). | ||
|- | |- | ||
| Fuel gauge | | Fuel gauge | ||
Line 152: | Line 191: | ||
| S5K6A3 | | S5K6A3 | ||
| Y | | Y | ||
| [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/s5k6a3.c Image sensor driver], [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/platform/samsung/exynos4-is/fimc-is-sensor.c | | [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/s5k6a3.c Image sensor driver], [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/platform/samsung/exynos4-is/fimc-is-sensor.c Attached imaging processor driver]. The FIMC-IS ISP does a lot of the heavy lifting for the sensor, which is why the sensor driver is small. Requires non-free firmwares. Hopefully will be working soon with Megapixels 2.0 (in development). | ||
|- | |- | ||
| Back Camera | | Back Camera | ||
| S5C73M3 | | S5C73M3 | ||
| Y | | Y | ||
| [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/s5c73m3/s5c73m3-core.c Driver] | | [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/s5c73m3/s5c73m3-core.c Driver]. The sensor driver is lacking a section of code to enable full V4L2 compatibility. See [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/s5c73m3/s5c73m3-core.c#n876 this FIXME]. Thankfully, Megapixels 2.0 has a workaround to handle this kind of problem. | ||
|- | |- | ||
| Flash LED & Vibrator (MFD) | | Flash LED & Vibrator (MFD) | ||
| MAX77693 | | MAX77693 | ||
| Y | | Y | ||
| [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mfd/max77693.c Driver] [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mfd/max77693. | | [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mfd/max77693.c Driver] [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mfd/maxim,max77693.yaml Device tree binding] | ||
|- | |- | ||
| Notification LED | | Notification LED | ||
Line 365: | Line 404: | ||
* {{MR|3022|pmaports}} Add WiFi support | * {{MR|3022|pmaports}} Add WiFi support | ||
* {{MR|3062|pmaports}} Add vibration support | * {{MR|3062|pmaports}} Add vibration support | ||
* {{MR|3192|pmaports}} Fix swapped touchkeys | |||
<!-- | <!-- | ||
Link to related GitLab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234): | Link to related GitLab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234): | ||
Line 373: | Line 413: | ||
--> | --> | ||
* {{Device package|samsung-t0lte}} | * {{Device package|samsung-t0lte}} | ||
* [https://gitlab. | * [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/community/linux-postmarketos-exynos4 Kernel package] | ||
* | * [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/community/firmware-samsung-midas Firmware package] (Common board firmware for Exynos Note 2 and S3 devices) | ||
* [https://fcc.report/FCC-ID/A3LSGHT889/1797529ACPM-7500-SG1 FCC's t0lteatt and t0ltetmo Schematics] | * [https://fcc.report/FCC-ID/A3LSGHT889/1797529ACPM-7500-SG1 FCC's t0lteatt and t0ltetmo Schematics] |
Latest revision as of 21:21, 29 December 2024
![]() Galaxy Note II | |
Manufacturer | Samsung |
---|---|
Name | Galaxy Note II LTE |
Codename | samsung-t0lte |
Released | 2012 |
Type | handset |
Hardware | |
Chipset | Samsung Exynos 4412 Quad |
CPU | Quad-core 1.6 GHz Cortex-A9 |
GPU | Mali-400 MP4 |
Display | 720x1280 AMOLED |
Storage | 16/32/64 GB |
Memory | 2 GB |
Architecture | armv7 |
Software | |
Original software | Android |
Original version | 4.1.1 on Linux 3.0.31 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | yes |
postmarketOS kernel | 6.10.0 |
Flashing |
Partial |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
Works |
Screen |
Works |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
Works |
Audio |
Partial |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
Works |
Bluetooth |
Partial |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
Works |
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 |
Contributors
- Jack_Kekzoz
Users owning this device
- BlackEyedSquid (Notes: Verizon model (t0ltevzw), locked bootloader (KitKat update))
- Jack Kekzoz
How to enter flash mode
When the phone is powered off, press and hold down the
, and buttons to turn it on in Download mode.If you have installed a custom recovery, then when the phone is powered off, press and hold down the
, and buttons to turn it on in Recovery mode.Preparation
pmbootstrap init
will prompt to choose a (near-mainline) kernel, which depends on the device display panel, see samsung-t03g display.
Installation
You can install postmarketOS either by flashing the rootfs to an sdcard, and then flashing the kernel using Heimdall when the phone is in Download mode, or you can install it via a recovery zip. It is not possible currently to flash rootfs in Download mode, as Heimdall has issues with flashing rootfs currently (see Heimdall). Please note that for the recovery installation, if you enable FDE, you need to ensure your custom recovery supports the cipher you are using.
Display
There is an issue with the display in that the brightness is too high when it turns on. Simply turning down the brightness, even a little, makes it jump to the correct setting.
FDE
FDE works ON OSK-SDL - not tested on unl0kr yet - although not with hardware acceleration.
Audio
Speaker and (main) mic work, but not headphone, as the kernel driver needs work to support that. In its current state the headphone audio is very crackly.
Bluetooth
Note: as of ~v24.06, only the non-free firmware package is available. The following is retained for informational purposes only.
Without the non-free firmware package, there may be some limited Bluetooth functionality [1]. If this occurs, it is probably because there is some code in the ROM of the BCM4334 chip. It is recommended to toggle Bluetooth off in this state, as the chip is designed to only work properly with the firmware patch, and unexpected issues may occur without it.
If you enable the non-free firmware package, then Bluetooth has partial functionality only:
- File sharing works (tested to and from a Motorola smartphone running stock Android 9)
- Keyboards work (though for some reason during pairing, the keyboard only became visible after it was paired with the smartphone.)
- Audio is NOT working properly, though that may be to do with a lack of configuration in Alsa UCM files.
- Internet sharing has not been tested.
In the long run, the Replicant project hopes to ask Cypress Semiconductor Corp. if they are willing to release the source code to the firmware under a permissive licence [2].
Touchkeys
The Back touchkey can be used for navigating back (mainly in Firefox, but also in other contexts). The Menu touchkey does nothing by default, but it can be assigned in the phosh settings.
If you wish, you can run this script in a terminal in the background to give you some haptic feedback and to illuminate the touchkey LEDs for 1 second when they are touched - you will need to install evtest beforehand though. It is a bit of a hack, so won't be bundled in postmarketOS by default:
#!/bin/sh device='/dev/input/by-path/platform-i2c-gpio-4-event' event_back='*code 158 (KEY_BACK), value 1*' event_menu='*code 139 (KEY_MENU), value 1*' evtest "$device" | while read line; do case $line in ($event_back) fbcli -E button-pressed echo 1 > /sys/class/leds/tm2-touchkey/brightness sleep 1 echo 0 > /sys/class/leds/tm2-touchkey/brightness ;; ($event_menu) fbcli -E button-pressed echo 1 > /sys/class/leds/tm2-touchkey/brightness sleep 1 echo 0 > /sys/class/leds/tm2-touchkey/brightness ;; esac done
Camera
When Megapixels 2.0 is released, Back camera will be able to take photos with no need to run commands beforehand, thanks to a recent added feature. Photos will be taken at a resolution of 2304x1296.

Hardware
Part | Name | Mainline kernel support | Notes |
---|---|---|---|
GPU | Mali-400 MP4 | Y | Driver |
Panel | Samsung S6EVR02 / Magnachip EA8061 LCD panel | N | But they are in the exynos4-mainline repo 1 2. |
Touchscreen | MMS152 | Y | Driver |
WiFi | BCM4334 | Y | brcmfmac driver. Requires nonfree firmwares. |
Bluetooth | BCM4334 | Y | Driver. Requires nonfree firmware. |
GPS | MDM9615 | ||
Modem | MDM9615 | N | This modem is also found in samsung-m3 (GT-i9305). |
Fuel gauge | MAX17047 | Y | Driver |
MFD | MAX77686 | Y | Driver |
Audio codec | WM1811 | Y | Midas-specific driver. This driver is thought to be an upstreamed version of samsung-m0's downstream driver. t0 driver needs upstreaming for full audio functionality. Main driver |
Front Camera | S5K6A3 | Y | Image sensor driver, Attached imaging processor driver. The FIMC-IS ISP does a lot of the heavy lifting for the sensor, which is why the sensor driver is small. Requires non-free firmwares. Hopefully will be working soon with Megapixels 2.0 (in development). |
Back Camera | S5C73M3 | Y | Driver. The sensor driver is lacking a section of code to enable full V4L2 compatibility. See this FIXME. Thankfully, Megapixels 2.0 has a workaround to handle this kind of problem. |
Flash LED & Vibrator (MFD) | MAX77693 | Y | Driver Device tree binding |
Notification LED | AN30259A | Y | Driver Device tree binding |
Accelerometer/Gyroscope | LSM330DLC | Y | Accelerometer driver, Gyroscope driver, Device tree binding. |
Touchkey | Cypress ??? | Y | Driver |
Magnetometer | AK8963C | Y | Driver, Device tree binding |
Proximity/Light sensor | CM36651 | Y | Driver, Device tree binding |
MHL | SII9244BO | Y? | This driver might work with samsung-m0 but not t0, or for both m0 and t0. Device tree binding |
Sensor Hub | Samsung Sensor Hub | Y | Drivers, Device tree binding. This is required to get many sensors working. |
Pressure Sensor | BMP182 | Y? | As reported by sensor-readout (f-droid) under android.
BMP180 (CONFIG_BMP280) Drivers, Device tree binding |
Partitions
Output of sudo parted /dev/mmcblk2 print
:
Model: MMC MAG4FB (sd/mmc) Disk /dev/mmcblk2: 15.8GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:
Number | Start | End | Size | File system | Name | Flags |
---|---|---|---|---|---|---|
1 | 4194kB | 8389kB | 4194kB | BOTA0 | msftdata | |
2 | 8389kB | 12.6MB | 4194kB | BOTA1 | msftdata | |
3 | 12.6MB | 33.6MB | 21.0MB | ext4 | EFS | msftdata |
4 | 33.6MB | 37.7MB | 4194kB | m9kefs1 | msftdata | |
5 | 37.7MB | 41.9MB | 4194kB | m9kefs2 | msftdata | |
6 | 41.9MB | 46.1MB | 4194kB | m9kefs3 | msftdata | |
7 | 46.1MB | 54.5MB | 8389kB | PARAM | msftdata | |
8 | 54.5MB | 62.9MB | 8389kB | BOOT | msftdata | |
9 | 62.9MB | 71.3MB | 8389kB | RECOVERY | msftdata | |
10 | 71.3MB | 164MB | 92.3MB | fat16 | RADIO | msftdata |
11 | 164MB | 432MB | 268MB | ext4 | TOMBSTONES | msftdata |
12 | 432MB | 1866MB | 1434MB | ext4 | CACHE | msftdata |
13 | 1866MB | 4014MB | 2147MB | ext4 | SYSTEM | msftdata |
14 | 4014MB | 4601MB | 587MB | ext4 | HIDDEN | msftdata |
15 | 4601MB | 4610MB | 8389kB | OTA | msftdata | |
16 | 4610MB | 15.8GB | 11.1GB | ext4 | USERDATA | msftdata |
See also
- pmaports!2751 Preparatory merge request for LCD panel
- pmaports!2759 Initial device merge request
- pmaports!2913 Add partial audio support
- pmaports!2953 Add partial Bluetooth support
- pmaports!3012 Add camera flash/torch LED & notification LED support
- pmaports!3022 Add WiFi support
- pmaports!3062 Add vibration support
- pmaports!3192 Fix swapped touchkeys
- Device package
- Kernel package
- Firmware package (Common board firmware for Exynos Note 2 and S3 devices)
- FCC's t0lteatt and t0ltetmo Schematics