Jump to content

Samsung Galaxy S6 Edge (samsung-zeroltexx): Difference between revisions

From postmarketOS Wiki
Unah (talk | contribs)
m Fixed capitalization of "Sxmo"
Halamix2 (talk | contribs)
mNo edit summary
 
(14 intermediate revisions by 8 users not shown)
Line 6: Line 6:
| imagecaption = Samsung Galaxy S6 Edge
| imagecaption = Samsung Galaxy S6 Edge
| releaseyear = 2015
| releaseyear = 2015
| originalsoftware = Android 5.0-7.0
| originalsoftware = Android
| chipset = Exynos 7420 Octa
| originalversion = 5.0
| extendedversion = 7.0
| chipset = Samsung Exynos 7420 Octa
| cpu = Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
| cpu = Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
| gpu = Mali-T760MP8
| gpu = Mali-T760 MP8
| storage = 32/64/128 GB
| storage = 32/64/128 GB
| display = 1440 x 2560 Super AMOLED
| display = 1440 x 2560 Super AMOLED
| memory = 3 GB
| memory = 3 GB
| architecture = aarch64
| architecture = aarch64
| 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 = P
| status_usbnet = Y
| status_flashing =  
| status_flashing = P
| status_touch = Y
| status_touch = Y
| status_screen = Y
| status_screen = Y
| status_wifi =  
| status_wifi = Y
| status_xwayland = N
| status_xwayland = N
| status_fde =  
| status_fde =  
Line 26: Line 29:
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
| status_accel = <!-- The sensor that measures proper acceleration works -->
| status_accel = <!-- The sensor that measures proper acceleration works -->
| status_audio = <!-- Using the device's speakers/headphone jack works -->
| status_audio = Y
| status_bluetooth = <!-- It's possible to pair and use other devices via the bluetooth protocol -->
| status_bluetooth = <!-- It's possible to pair and use other devices via the bluetooth protocol -->
| status_camera = <!-- Taking photos and videos works. -->
| status_camera = <!-- Taking photos and videos works. -->
Line 33: Line 36:
| status_sms = <!-- Sending and receiving short messages works as intended. -->
| status_sms = <!-- Sending and receiving short messages works as intended. -->
| status_calls = <!-- Talking to other people over the cellular network. -->
| status_calls = <!-- Talking to other people over the cellular network. -->
| status_otg = Y <!-- USB-OTG adapters work, e.g. to connect an USB flash drive to the device -->
| status = <!-- Text displayed in the "not booting" table on the Devices page , e.g "kernel compiles, doesn't boot" -->
| status = <!-- Text displayed in the "not booting" table on the Devices page , e.g "kernel compiles, doesn't boot" -->
| booting = yes <!-- The device is booting at all, can be yes/no *IMPORTANT* -->
| booting = yes <!-- The device is booting at all, can be yes/no *IMPORTANT* -->


<!-- you can also use these lines if you need to: -->
<!-- you can also use these lines if you need to: -->
| pmoskernel = 3.10.61
| pmoskernel = 3.10.108
<!-- see Unixbench page on wiki -->
<!-- see Unixbench page on wiki -->
| whet_dhry = 3096.2
| whet_dhry = 3096.2
Line 47: Line 51:
== Contributors ==
== Contributors ==
* [[user:Aleksas|Aleksas]]
* [[user:Aleksas|Aleksas]]
* [[user:St.S|St.S]]


== Maintainer(s) ==
== Maintainer(s) ==
Line 65: Line 70:
Create a [[Android_Recovery_Zip_Installation|recovery zip]] and flash it with TWRP.
Create a [[Android_Recovery_Zip_Installation|recovery zip]] and flash it with TWRP.
<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
== Hardware / sensors ==
Results from <code>sudo hwtest</code> on SM-G925T:
<div class="toccolours mw-collapsible mw-collapsed" style="width:600px; overflow:auto;">
hwtest
<div class="mw-collapsible-content">
{| class="wikitable feature-colors"
! style="text-align:left;"| Category
! style="text-align:left;"| Model
! style="text-align:left;"| Path
! style="text-align:left;"| Status
! style="text-align:left;"| Value
|-
|framebuffer
|
|/sys/class/graphics/fb0
| class="feature-yes"| Working
|U:1440x2560p-59
|-
|framebuffer
|
|/sys/class/graphics/fb1
| class="feature-yes"| Working
|
|-
|input
|certify_hall
|/dev/input/event18
| class="feature-yes"| Working
|
|-
|input
|hall
|/dev/input/event17
| class="feature-yes"| Working
|
|-
|input
|dt2w_power_key
|/dev/input/event16
| class="feature-yes"| Working
|
|-
|input
|gpio_keys.31
|/dev/input/event15
| class="feature-yes"| Working
|
|-
|input
|Headset
|/dev/input/event14
| class="feature-yes"| Working
|
|-
|input
|ssp_context
|/dev/input/event13
| class="feature-yes"| Working
|
|-
|input
|meta_event
|/dev/input/event12
| class="feature-yes"| Working
|
|-
|input
|interrupt_gyro_sensor
|/dev/input/event11
| class="feature-yes"| Working
|
|-
|input
|step_cnt_sensor
|/dev/input/event10
| class="feature-yes"| Working
|
|-
|input
|sig_motion_sensor
|/dev/input/event9
| class="feature-yes"| Working
|
|-
|input
|gesture_sensor
|/dev/input/event8
| class="feature-yes"| Working
|
|-
|input
|temp_humidity_sensor
|/dev/input/event7
| class="feature-yes"| Working
|
|-
|input
|grip_sensor
|/dev/input/event6
| class="feature-yes"| Working
|
|-
|input
|proximity_sensor
|/dev/input/event5
| class="feature-yes"| Working
|
|-
|input
|light_ir_sensor
|/dev/input/event4
| class="feature-yes"| Working
|
|-
|input
|light_sensor
|/dev/input/event3
| class="feature-yes"| Working
|
|-
|input
|hrmled_sensor
|/dev/input/event2
| class="feature-yes"| Working
|
|-
|input
|hrm_sensor
|/dev/input/event1
| class="feature-yes"| Working
|
|-
|input
|sec_touchscreen
|/dev/input/event0
| class="feature-yes"| Working
|
|}
</div>
</div>
Results from <code>sensors</code> (package lm-sensors) on SM-G925T:
<div class="toccolours mw-collapsible mw-collapsed" style="width:600px; overflow:auto;">
sensors
<div class="mw-collapsible-content">
<pre>
exynos-therm-virtual-0
Adapter: Virtual device
temp1:        +37.0C  (crit = +75.0C)
max77843-fuelgauge-virtual-0
Adapter: Virtual device
temp1:        +29.0C
ac-virtual-0
Adapter: Virtual device
temp1:        +31.5C
battery-virtual-0
Adapter: Virtual device
temp1:        +29.0C
</pre>
</div>
</div>
For reference, sensor information from sensorssandbox (f-droid) on SM-G925T; note that in addition to hardware-based sensors, it presumably includes software-based / derived sensors:
<div class="toccolours mw-collapsible mw-collapsed" style="width:600px; overflow:auto;">
sensor details (sensorssandbox)
<div class="mw-collapsible-content">
{| class="wikitable feature-colors"
! style="text-align:left;"| name
! style="text-align:left;"| vendor
! style="text-align:left;"| version
! style="text-align:left;"| type
|-
|MPU6500 acceleration sensor
|Invensense
|1
|1
|-
|YAS537 magnetic sensor
|Yamaha corp
|1
|2
|-
|MPU6500 gyroscope sensor
|Invensense
|1
|4
|-
|LPS25H barometric sensor
|STMicroelectronics
|1
|6
|-
|TMD49XX proximity sensor
|AMS, inc
|1
|8
|-
|TMD49XX RGB sensor
|AMS, inc
|1
|5
|-
|YAS537 uncalibrated magnetic sensor
|Yamaha corp
|1
|14
|-
|Samsung step detector sensor
|Samsung, inc
|1
|18
|-
|Samsung significant motion sensor
|Samsung, inc
|2
|17
|-
|MPU6500 gyrosope sensor uncalibrated
|Invensense
|1
|16
|-
|MPL game rotation vector
|Invensense
|1
|15
|-
|MPL rotation vector
|Invensense
|1
|11
|-
|Samsung step counter sensor
|Samsung, inc
|1
|19
|-
|Grip sensor
|Semtech
|512
|65560
|-
|TMD49XX RGB IR sensor
|AMS, inc
|1
||65578
|-
|Interrupt gyroscope sensor
|Invensense
|1
|65579
|-
|Samsung tilt detector
|Samsung, inc
|1
|22
|-
|Samsung pick up gesture
|Samsung, inc
|1
|25
|-
|Screen orientation sensor
|Samsung, inc
|3
|65558
|-
|Motion sensor
|Samsung, inc
|1
|65559
|-
|Gravity sensor
|Samsung, inc
|3
|9
|-
|Linear acceleration sensor
|Samsung, inc
|3
|10
|-
|Orientation sensor
|Samsung, inc
|1
|3
|}
</div>
</div>
The following refers to SM-G925F (zeroltexx) and SM-G920F (zerofltexx): Some of the sensors, as well as the infrared (remote control) sender LED, can be activated by first initializing the sensorhub with a firmware blob (which Android does within the "lhd" daemon). This firmware blob is actually compiled into the downstream kernel already (readable in device /dev/bbd_patch), but needs to be uploaded to the sensor hub chip using a special packetized protocol in /dev/bbd_packet. An example Rust program for doing that is available [https://gitlab.com/st.s/init_sensorhub here].


== See also ==
== See also ==
Line 71: Line 371:
* [https://twrp.me/samsung/samsunggalaxys6edge.html TWRP for Samsung Galaxy S6 Edge]
* [https://twrp.me/samsung/samsunggalaxys6edge.html TWRP for Samsung Galaxy S6 Edge]
* [https://github.com/jcadduono/nethunter_kernel_noblelte/tree/twrp-6.0 Kernel used (TWRP's kernel)]
* [https://github.com/jcadduono/nethunter_kernel_noblelte/tree/twrp-6.0 Kernel used (TWRP's kernel)]
* `{{MR|2105|pmaports}} Newer port, using different kernel
<!--
<!--
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 78: Line 379:
* [https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100 Replicant wiki page]
* [https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100 Replicant wiki page]
-->
-->
<!--
If you manage to get your device packages merged, uncomment links below.
* {{Device package|samsung-zeroltexx}}
* {{Device package|samsung-zeroltexx}}
* {{Kernel package|samsung-zeroltexx}}
* {{Kernel package|samsung-zeroltexx}}
-->

Latest revision as of 11:42, 1 February 2025

Samsung Galaxy S6 Edge
Samsung Galaxy S6 Edge
Samsung Galaxy S6 Edge
Manufacturer Samsung
Name Galaxy S6 Edge
Codename samsung-zeroltexx
Released 2015
Type handset
Hardware
Chipset Samsung Exynos 7420 Octa
CPU Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
GPU Mali-T760 MP8
Display 1440 x 2560 Super AMOLED
Storage 32/64/128 GB
Memory 3 GB
Architecture aarch64
Software
Original software Android
Original version 5.0
Extended version 7.0
postmarketOS
Category testing
Pre-built images no
postmarketOS kernel 3.10.108
Unixbench Whet/Dhry score 3096.2
Features
Flashing
Partial
USB Networking
Works
Internal storage
No data
SD card
No data
Battery
No data
Screen
Works
Touchscreen
Works
Multimedia
3D Acceleration
No data
Audio
Works
Camera
No data
Camera Flash
No data
Connectivity
WiFi
Works
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
Works
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

Maintainer(s)

Users owning this device

  • Aleksas
  • Crashniels (Notes: PostmarketOS)
  • Grimler
  • JulianGro (Notes: working condition, not in use, stock Android)
  • KrakinTheKonsole (Notes: RIPPED Audio hardware.)
  • Sanzoghenzo (Notes: faulty screen, wifi not working on Android)
  • St.S (Notes: booting w/USB,ssh access,display,touch,wifi,audio,bluetooth;camera,sensors,ir-tx with some user-space helper programs)
  • ZeroCool32 (Notes: Sort-of broken; locks up most of the time, reboots by itself (due to faulty battery, runs LineageOS)


What works

  • Xfce4, Mate, Sxmo user interfaces

Installation

Create a recovery zip and flash it with TWRP.

Hardware / sensors

Results from sudo hwtest on SM-G925T:

hwtest

Results from sensors (package lm-sensors) on SM-G925T:

sensors

For reference, sensor information from sensorssandbox (f-droid) on SM-G925T; note that in addition to hardware-based sensors, it presumably includes software-based / derived sensors:

sensor details (sensorssandbox)

The following refers to SM-G925F (zeroltexx) and SM-G920F (zerofltexx): Some of the sensors, as well as the infrared (remote control) sender LED, can be activated by first initializing the sensorhub with a firmware blob (which Android does within the "lhd" daemon). This firmware blob is actually compiled into the downstream kernel already (readable in device /dev/bbd_patch), but needs to be uploaded to the sensor hub chip using a special packetized protocol in /dev/bbd_packet. An example Rust program for doing that is available here.

See also