Difference between revisions of "Alcatel OneTouch Pop 7S (alcatel-pop7lte)"

From postmarketOS
Jump to navigation Jump to search
(Add initial device page for alcatel-pop7lte)
 
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Infobox device
 
{{Infobox device
 
| manufacturer = Alcatel
 
| manufacturer = Alcatel
| name = OneTouch Pop 7S (P330X)
+
| name = OneTouch Pop 7S (P330X)
 
| codename = alcatel-pop7lte
 
| codename = alcatel-pop7lte
| image = File:CHANGE_ME_TO_DEVICE_CODENAME.jpg
+
| image = File:alcatel-pop7lte.jpg
| imagecaption = No image yet
+
| imagecaption = Alcatel OneTouch Pop 7S
 
| releaseyear = 2014
 
| releaseyear = 2014
| originalsoftware = Android 4.4.2 (KitKat)
+
| originalsoftware = Android 4.3 or 4.4.2
 
| chipset = Qualcomm MSM8226 Snapdragon 400
 
| chipset = Qualcomm MSM8226 Snapdragon 400
 
| cpu = 4 cores up to 1.2 GHz Cortex-A7 (32bit)
 
| cpu = 4 cores up to 1.2 GHz Cortex-A7 (32bit)
 
| gpu = Qualcomm Adreno 306 GPU
 
| gpu = Qualcomm Adreno 306 GPU
| storage = 16/32 GB flash memory, microSDXC slot (up to 64 GB)
+
| storage = 16 GB eMMC 4.5 flash memory, microSDXC slot
 
| display = 1024×600 px, 7.0" in (17.78 cm) diagonal, WSVGA IPS LCD display (touchscreen: FocalTech FT5436)
 
| display = 1024×600 px, 7.0" in (17.78 cm) diagonal, WSVGA IPS LCD display (touchscreen: FocalTech FT5436)
 
| memory = 1 GB
 
| memory = 1 GB
 
| architecture = armv7
 
| architecture = armv7
 
<!-- 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 = <!-- USB networking does work? then put Y here and delete this comment -->
+
| status_usbnet = Y <!-- USB networking does work? then put Y here and delete this comment -->
| status_flashing = <!-- Flashing with "pmbootstrap flasher" works? Put Y here. It works the same for everything coming below. -->
+
| status_flashing = P <!-- Flashing with "pmbootstrap flasher" works? Put Y here. It works the same for everything coming below. -->
| status_touch = <!-- Touch screen is working? You can also answer these questions with P for partially. -->
+
| status_touch = P <!-- Touch screen is working? You can also answer these questions with P for partially. -->
| status_screen = <!-- The display is working? -->
+
| status_screen = Y <!-- The display is working? -->
| status_wifi = <!-- Wireless network works? -->
+
| status_wifi = P <!-- Wireless network works? -->
| status_xwayland = <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? -->
+
| status_xwayland = Y <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? -->
 
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? -->
 
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? -->
| status_mainline = <!-- Instead of a Linux kernel fork, it is possible to run mainline. -->
+
| status_mainline = N <!-- Instead of a Linux kernel fork, it is possible to run mainline. -->
| status_battery = <!-- Charging the battery with charging-sdl is possible -->
+
| status_battery = P <!-- Charging the battery with charging-sdl is possible -->
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
+
| status_3d = N <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
| status_accel = <!-- The sensor that measures proper acceleration works -->
+
| status_accel = N <!-- The sensor that measures proper acceleration works -->
| status_audio = <!-- Using the device's speakers/headphone jack works -->
+
| status_audio = P <!-- Using the device's speakers/headphone jack works -->
| status_bluetooth = <!-- It's possible to pair and use other devices via the bluetooth protocol -->
+
| status_bluetooth = P <!-- It's possible to pair and use other devices via the bluetooth protocol -->
| status_camera = <!-- Taking photos and videos works. -->
+
| status_camera = N <!-- Taking photos and videos works. -->
| status_gps = <!-- The Global Positioning System sensor works.  -->
+
| status_gps = N <!-- The Global Positioning System sensor works.  -->
| status_mobiledata = <!-- Connecting to the Internet via cellular network. -->
+
| status_mobiledata = N <!-- Connecting to the Internet via cellular network. -->
| status_sms = <!-- Sending and receiving short messages works as intended. -->
+
| status_sms = N <!-- Sending and receiving short messages works as intended. -->
| status_calls = <!-- Talking to other people over the cellular network. -->
+
| status_calls = N <!-- Talking to other people over the cellular network. -->
 
| 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 = no <!-- The device is booting at all, can be yes/no *IMPORTANT* -->
+
| booting = yes <!-- The device is booting at all, can be yes/no *IMPORTANT* -->
 
| pmoskernel = 3.4.0
 
| pmoskernel = 3.4.0
 
<!--
 
<!--
Line 48: Line 48:
  
 
== Maintainer(s) ==
 
== Maintainer(s) ==
 +
* [[user:thejsa|thejsa]]
 
<!-- Only if this device doesn't run on linux-postmarketos yet! -->
 
<!-- Only if this device doesn't run on linux-postmarketos yet! -->
 
<!-- This person needs to be willing to answer questions from users of this device -->
 
<!-- This person needs to be willing to answer questions from users of this device -->
Line 59: Line 60:
  
 
== How to enter flash mode ==
 
== How to enter flash mode ==
 +
I have as yet been '''unable to find a way to ''directly'' enter fastboot''' on this device, nor have I been able to find any hint of custom Android ROM / custom recovery development for this or info on sites like XDA-Developers.
 +
 +
However, one is able to reboot into the bootloader from a running Android system through ADB by running `adb reboot-bootloader` on one's host system.
  
 
== Installation ==
 
== Installation ==
 +
In theory you should be able to directly install onto the device, but due to the aforementioned difficulties getting into fastboot I have not tried this. All of my testing has been undertaken by installing onto an SD card (<code>pmbootstrap install --sdcard [device]</code>) and directly booting the kernel using <code>pmbootstrap flasher boot</code>.
 
<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
 
<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
 +
 +
== Bootloader unlocking ==
 +
I was able to unlock the bootloader on my device with a simple <code>fastboot oem unlock</code>, although I did not test if this works if the device is still carrier locked (in the UK, these devices were mainly sold cheaply -- and carrier locked -- by EE and O2; I was able to obtain a carrier unlock code for my device for under £1 from an eBay seller as EE is slow and charges £9 at time of writing).
 +
 +
== Touchscreen ==
 +
The touchscreen in this device uses a FocalTech FT5436 controller - firmware is compiled into the kernel, is required for the driver to build, and is stored as <code>.i</code> files in the kernel tree in <code>drivers/input/touchscreen</code>. (I agree, this is yucky.)
 +
 +
tslib and libinput recognise the screen and tslib calibration seems to recognise touch inputs, but Weston does not (suspected driver issues?)
 +
 +
Touch input seems to work in xfce4, however (at least for moving the cursor), although incorrectly rotated (needs calibration).
 +
 +
== WiFi ==
 +
WiFi firmware is packaged but the prima/pronto driver appears to be missing in Alcatel's kernel tree :-(
  
 
== See also ==
 
== See also ==
 +
* {{MR|1072|pmaports}} Initial merge request
 
<!--
 
<!--
 
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):

Latest revision as of 18:24, 9 May 2020

Alcatel OneTouch Pop 7S (P330X)
Alcatel OneTouch Pop 7S
Alcatel OneTouch Pop 7S
Manufacturer Alcatel
Name OneTouch Pop 7S (P330X)
Codename alcatel-pop7lte
Released 2014
Category testing
Original software Android 4.3 or 4.4.2
postmarketOS kernel 3.4.0
Hardware
Chipset Qualcomm MSM8226 Snapdragon 400
CPU 4 cores up to 1.2 GHz Cortex-A7 (32bit)
GPU Qualcomm Adreno 306 GPU
Display 1024×600 px, 7.0" in (17.78 cm) diagonal, WSVGA IPS LCD display (touchscreen: FocalTech FT5436)
Storage 16 GB eMMC 4.5 flash memory, microSDXC slot
Memory 1 GB
Architecture armv7
Features
USB Networking
Works
Flashing
Partial
Touchscreen
Partial
Display
Works
WiFi
Partial
Xwayland
Works
FDE
Mainline
Broken
Battery
Partial
3D Acceleration
Broken
Accelerometer
Broken
Audio
Partial
Bluetooth
Partial
Camera
Broken
GPS
Broken
Mobile data
Broken
SMS
Broken
Calls
Broken
USB OTG



Contributors

Maintainer(s)

Users owning this device

  • Thejsa (Notes: Damaged touchscreen, cellular doesn't work)


How to enter flash mode

I have as yet been unable to find a way to directly enter fastboot on this device, nor have I been able to find any hint of custom Android ROM / custom recovery development for this or info on sites like XDA-Developers.

However, one is able to reboot into the bootloader from a running Android system through ADB by running `adb reboot-bootloader` on one's host system.

Installation

In theory you should be able to directly install onto the device, but due to the aforementioned difficulties getting into fastboot I have not tried this. All of my testing has been undertaken by installing onto an SD card (pmbootstrap install --sdcard [device]) and directly booting the kernel using pmbootstrap flasher boot.

Bootloader unlocking

I was able to unlock the bootloader on my device with a simple fastboot oem unlock, although I did not test if this works if the device is still carrier locked (in the UK, these devices were mainly sold cheaply -- and carrier locked -- by EE and O2; I was able to obtain a carrier unlock code for my device for under £1 from an eBay seller as EE is slow and charges £9 at time of writing).

Touchscreen

The touchscreen in this device uses a FocalTech FT5436 controller - firmware is compiled into the kernel, is required for the driver to build, and is stored as .i files in the kernel tree in drivers/input/touchscreen. (I agree, this is yucky.)

tslib and libinput recognise the screen and tslib calibration seems to recognise touch inputs, but Weston does not (suspected driver issues?)

Touch input seems to work in xfce4, however (at least for moving the cursor), although incorrectly rotated (needs calibration).

WiFi

WiFi firmware is packaged but the prima/pronto driver appears to be missing in Alcatel's kernel tree :-(

See also