Jump to content

Samsung Galaxy Mini 2 (samsung-jena): Difference between revisions

From postmarketOS Wiki
Halamix2 (talk | contribs)
m Removed info about old fork, added more precise RAM info
Drebrez (talk | contribs)
mNo edit summary
Line 8: Line 8:
| originalsoftware = Android 2.3.4
| originalsoftware = Android 2.3.4
| pmoskernel= 3.4 from Cyanogen
| pmoskernel= 3.4 from Cyanogen
| chipset =  Snapdragon S1 / MSM7227A
| chipset =  Qualcomm MSM7227A Snapdragon S1
| cpu = ARM Cortex-A5 800 Mhz
| cpu = ARM Cortex-A5 800 Mhz
| gpu = Adreno 200
| gpu = Adreno 200

Revision as of 21:07, 29 August 2018

Samsung Galaxy Mini 2
Samsung s6500d
Samsung s6500d
Manufacturer Samsung
Name Galaxy Mini 2
Codename s6500d, s6500, jena
Released 2012
Hardware
Chipset Qualcomm MSM7227A Snapdragon S1
CPU ARM Cortex-A5 800 Mhz
GPU Adreno 200
Display 320×480
Storage 4GB
Memory physically 512MiB, limited by kernel to ~385MiB (faulty dices?)
Software
Original software Android 2.3.4
postmarketOS
Category testing
Pre-built images no
Mainline no
postmarketOS kernel 3.4 from Cyanogen
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


Contributors

What works

  • Boots
  • SSH through USB
  • display
  • flashing

What does not work

  • Restart after ~2 minutes 22 seconds
  • No input (keys and screen)
  • osk-keyboard
  • Wi-Fi
  • XWayland
  • FDE
  • Not mainlined
  • No charging with turned off phone (is it even supported?)
  • 3D acceleration
  • Accelerometers and other sensors
  • Audio
  • Bluetooth
  • Camera
  • GPS
  • Mobile data
  • SMS
  • Voice

To do

Note informations below may be chaotic and change often

SMSM_RESET

Most annoying problem sunce everything on the phone has to be done within 2 minutes. After about 2mins 22secs phone reboots with dmesg showing SMSM: Modem SMSM state changed to SMSM_RESET This message is hardcoded into arch/arm/mach-msm/smd.c

Probably caused my modem, check all MODEM and MSM*_MODEM_* related options in menuconfig (there is one called reset, one reboot and one just modem) or find binary blobs if possible.

Touch screen

The screen as well as two touch buttons (menu and back) are combined together as /dev/input/event1. It displays some sort of animation when pressing buttons in postmarket demos window in weston but only for first press or two. weston-calibrate does not work


Home button and volume buttons are /dev/input/event1, where power button is recognised as /dev/input/event6

Mainline

Currently we have working 2.6 kernel, no DTS files for qcom-msm7227a.

Get data form all over the kernel source code (mainly arch/mach-msm/board-<board name>.c for starters and recreate it in .dts file(s).

Useful links (mainly dts stuff)

The Mainline Kernel – our docs about mainlining

Qualcomm mainline porting — our sparse docs about Qualcomm mainlining

Device Tree – The Disaster so Far(pdf) – introduction to DT and basic knowledge how to move from board files do DT

Device Tree for dummies(pdf) – a little bit more complex infoa bout DT files

Halium project docs on mainlining – has a nice list where to look for ready solutions

Qualcomm SOC Mainlining Project – sadly no MSM7227a

Allwinner SOC Mainlining Project – not useful for this phone

Devicetree.org specification

Documentation/devicetree/ inside linux kernel files, should contain newest documentation about dts files, should be most reliable source of information

How to enter flash mode

Press power button and hold home button and VOL-

Alternatively, plug in microUSB plug with GND and ID pins connected through 300KΩ resistor. (so-called USB jig)

Installation

For now see Installation Guide and Flashing on Porting to a new device

Partitions

fdisk -l /dev/mmcblk0
omitting empty partition (25)
Disk /dev/mmcblk0: 3.7 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device          Boot   Start     End Sectors  Size Id Type
/dev/mmcblk0p1  *          1      40      40   20K 4d QNX4.x
/dev/mmcblk0p2            41     340     300  150K 45 unknown
/dev/mmcblk0p3           341   41300   40960   20M  c W95 FAT32 (LBA)
/dev/mmcblk0p4         41301 7634943 7593643  3.6G  5 Extended
/dev/mmcblk0p5         49152   51151    2000 1000K 46 unknown
/dev/mmcblk0p6         51152   53151    2000 1000K 47 unknown
/dev/mmcblk0p7         53152   57151    4000    2M 5d unknown
/dev/mmcblk0p8         57152   81727   24576   12M 48 unknown
/dev/mmcblk0p9         81728   87871    6144    3M 4a unknown
/dev/mmcblk0p10        87872   94015    6144    3M 4b unknown
/dev/mmcblk0p11        94016  110399   16384    8M 90 unknown
/dev/mmcblk0p12       110400  134975   24576   12M 91 unknown
/dev/mmcblk0p13       134976  143167    8192    4M 92 unknown
/dev/mmcblk0p14       143168  151359    8192    4M 93 Amoeba
/dev/mmcblk0p15       151360  152383    1024  512K 95 unknown
/dev/mmcblk0p16       152384 1176383 1024000  500M 82 Linux swap / Solaris
/dev/mmcblk0p17      1176384 1483583  307200  150M 94 Amoeba BBT
/dev/mmcblk0p18      1483584 3396415 1912832  934M 83 Linux
/dev/mmcblk0p19      3396416 3420991   24576   12M 65 Novell Netware 386
/dev/mmcblk0p20      3420992 3470143   49152   24M 9a unknown
/dev/mmcblk0p21      3470144 3478335    8192    4M 63 GNU HURD or SysV
/dev/mmcblk0p22      3478336 3580735  102400   50M 67 unknown
/dev/mmcblk0p23      3580736 7429803 3849068  1.9G 64 Novell Netware 286
/dev/mmcblk0p24      7429804 7437995    8192    4M 58 unknown