Jump to: navigation, search

Samsung Captivate Glide (samsung-i927)

1,966 bytes added, 18 July
Sound config info
| name = Captivate Glide
| codename = samsung-i927
| image = File:sgh-i927i927_neofetch.jpg| imagecaption = Samsung Captivate Glide with its keyboard extended and back lights on, running postmarketOS
| releaseyear = 2011
| originalsoftware = Android 4.0.4
| status_touch = Y
| status_screen = Y
| status_wifi = PY
| status_xwayland =
| status_fde = Y
| status_mainline = P
| status_battery = PY
| status_3d = P
| status_accel =Y| status_audio =Y| status_bluetooth =Y| status_camera =N| status_gps =Y| status_mobiledata =N| status_sms =N| status_calls =N| status_otg = Y
| status = boots
| booting = yes
* ''[[user:benwaffle|benwaffle]]''
* ''[[user:Moocow9m|Moocow9m]]''
== What works ==
* Kernel compilation
* Flash via Heimdall
* Booting
== How to enter flash mode ==
== Installation ==
Using SD card for installation is highly recommended because internal eMMC memory has a limited lifetime. Commands below assume SD card installation, however, in theory, it is possible to boot from USB drive connected via OTG cable. Insert SD card in your PC and run this from Linux terminal:<!syntaxhighlight lang="shell" line='line'>$ cd /tmp$ git clone$ cd pmbootstrap$ ./ init$ ./ install -- add more sections below as necessarysdcard /dev/mmcblkN # change path to your SD card$ ./ flasher flash_kernel</syntaxhighlight>Keep in mind that pmbootstrap requires root permissions. == Sound configuration ==Device package includes ALSA UCM profiles for WM8994 chip. Every input and output is disabled by default, so in order to hear something you need to do some configuration. For example, if you want to enable Speaker output, you'll need to run this from terminal: <code>$ alsaucm -c wm8994aif1 set _verb HiFi set _enadev Speaker</code> Supported outputs are: <code>Speaker</code>, e<code>Headphones</code> and <code>Earpiece</code>.g If you want to disable it, run: <code>$ alsaucm -c wm8994aif1 set _verb HiFi set _enadev Speaker set _disdev Speaker</code> (Note that alsaucm program doesn't track currently enabled devices. WifiWell, photosit actually does, but only in interactive mode) To enable mic, run: <code>$ alsaucm -c wm8994aif1 set _verb Voice set _enadev Headset</code> And you can disable it like the outputs aboveIf you don't want to configure all this on every reboot, then run this as root: <code># service alsa save</code> The configuration will be loaded automatically on boot.If you want to load it manually, then use this command: <code># service alsa restore</code> If you want to adjust the volume or do some additional configuration (set up an internal equalizer, for example), use <code>alsamixer</code> program. -->
== Hardware ==
! Info
| PY
|There's 3-4 power chips: max8907c, max8922, max17043 and unknown chip max8893 controlling camera power - on downstream kernel, it's driver called "m5mo_power", it works on I2C bus number 16 at address 0x3E. 17043 max17043 is supported by 17040 max17040 driver - the only difference is ALRT interrupt, which is sent on low battery.
| Y
| P
|Only gadget mode is Gadget and OTG modes are supported for now. [ OTG does not work yet]. HSIC mode is missing, which makes our modem not working. Not sure if we can make it work in non-HSIC mode. fsa9480 is used for cable type detection - it's supported by mainline kernel, but no Device Tree bindings available. There's a Currently the fsa9480 driver for fsa9480 with DT support in from PabloPL repo, but it's not is used for now.
| Y
| P
|Broadcom BCM4330. Something is happening with firmware: a long list of warnings is displayed on boot. The reason seems to be channel bandwidth - the code internally iterates over (supported) channels and checks for a bandwidth, and if it's not 40MHz, it outputs a warning. On 5GHz band, only 20MHz bandwidth Custom firmware is supported - device successfully scans used for APs on 40MHz and 80MHz bandwidths, but this chip because official one doesn't associate - wpa_supplicant reports and error work properly on 5GHz bandwidth with bssid=00:00:... and status_code=16 (probably timeout code)mainline drivers.
| Y
|There is 4 keys on GPIO: Power, Volume up, Volume down and keyboard HALL sensor.
| YP
|MCS5080. Mainline driver available, but it's bugged, has no DT bindings and not full. A slightly patched version is used with key reading fixed and internal LED support. Doesn't work right now because the driver gets probed before the regulator driver, so chip receives no power and initialization fails.
| Y
|ISA1200. Driver from p4wifi kernel is used, but there's also another driver from CAF(?).
|Broadcom BCM4330. Not testedWorks fine without firwmare.
|Wolfson WM8994. Chip is supported in mainline but Tegra bindings not available. For now, Uses custom board-level driver from p4wifi is used. This one also requires mapping configurationIt's fully-routed with DAPM paths configured so we get no suspend-resume issues.
|SII9234. No extcon support in mainline driver. Enabling this chip causes screen resolution Not tested, but driver seems to be set working. Disabled in Xorg config to avoid resolution issues. If you want to 1024x800 instead of 480x800test it, so you need to enable and configure it's disabled for nowin /etc/X11/xorg.conf.d/40-samsung-i927.conf
|Proximity sensor
|CM3663. No driver in mainline kernel available.
|Back camera
|Fujitsu M5MO. It is supported by mainline, but has no DT bindings. May have it's own PMIC
|Front camera
|Samsung S5K6AAFX. It is supported by mainline, but has no DT bindings. Power controlled by m5mo_pmic in downstream.
|XMM6260. Operates on USB with HSIC mode, but also has GPIOs.
| P
|SIRFstarIV GSD4t. gpsd driver can communicate with the chip, but mainline driver doesn't. gpsd is not tested fully because I don't know any software that can work with it :)
| P
|Other sensors
|These are just not tested, but driver available and probing works: NCT1008 (temperature), MPU3050 (gyro), KXTF9 (accel), AK8975 (compass), SIRFstarIV (GPS, actual chip is unknown. This one is notable because it's supported by new kernel GPS framework).
* {{MR|193|pmaports}} initial MR with downstream kernel (was dropped in favor of mainline kernel)
* {{MR|238|pmaports}} various improvements (bluetooth, audio, xorg config, armv7, etc)
* [ Photos running Mate on 5.1.12 kernel, also lying next to the N900]

Navigation menu