<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>droid 4 on Sebastian Reichel</title>
    <link>/tags/droid-4/</link>
    <description>Recent content in droid 4 on Sebastian Reichel</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© 2017-2022 Sebastian Reichel - &lt;a href=&#39;https://creativecommons.org/licenses/by-sa/3.0/&#39;&gt;CC-BY-SA&lt;/a&gt;</copyright>
    <lastBuildDate>Wed, 06 Nov 2019 23:42:00 +0100</lastBuildDate><atom:link href="/tags/droid-4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Motorola Droid 4 - Automated Tests</title>
      <link>/2019/11/0026-testing/</link>
      <pubDate>Wed, 06 Nov 2019 23:42:00 +0100</pubDate>
      
      <guid>/2019/11/0026-testing/</guid>
      <description>I would like being able to test patches on the Droid 4 without having to carry a development phone around all the time. Testing on my day-to-day phone is not a good idea, since that means being offline during the tests. A simple solution would be to do the testing remotely, which should also allow doing automated tests for KernelCI. Unfortunatley doing this on a phone is a bit harder than on an average development board due to the hardware design.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - Camera Info</title>
      <link>/2018/02/0025-droid-camera/</link>
      <pubDate>Sun, 11 Feb 2018 19:00:00 +0100</pubDate>
      
      <guid>/2018/02/0025-droid-camera/</guid>
      <description>Multiple people asked camera related questions during my talk as FOSDEM (and after it). I did some basic reverse engineering, so let me share what I know.
The Droid 4 works with a OMAP4430, which has a imaging subsystem (ISS). It is documented quite well in the datasheet and there is a Linux kernel driver available in staging (omap4iss), which was written by Laurent Pinchart (thanks!). This module provides two MIPI CSI-2 interfaces to connect camera sensors.</description>
    </item>
    
    <item>
      <title>FOSDEM 2018</title>
      <link>/2018/02/0024-fosdem/</link>
      <pubDate>Tue, 06 Feb 2018 12:00:00 +0200</pubDate>
      
      <guid>/2018/02/0024-fosdem/</guid>
      <description>I gave a talk at FOSDEM about the current mainline kernel support for the Droid 4 and its open issues. If you follow this blog you probably already know the information I presented and I&amp;rsquo;m not a good presenter (sorry!). If you are interested anyways, you can find the recording and my slides on the following here:
Slides Video Recording (mp4) Video Recording (WebM/VP9) Video Recording (Youtube) &amp;ndash; Sebastian</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - August Update</title>
      <link>/2017/08/0022-droid4/</link>
      <pubDate>Sat, 26 Aug 2017 22:42:00 +0200</pubDate>
      
      <guid>/2017/08/0022-droid4/</guid>
      <description>It has been some time since my last post about the Droid 4. 4.13 will most likely be released next week, so let&amp;rsquo;s have a look at newly added features related to the Droid 4:
crypto acceleration for AES and 3DES support for ISL29030 (proximity and ambient light sensor) USB phy support battery monitoring support bluetooth Unfortunately the list for 4.14 will be a lot shorter (or even empty), since most other submissions are still in review (or need work).</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - Update</title>
      <link>/2017/05/0019-droid4/</link>
      <pubDate>Sat, 13 May 2017 20:30:00 +0200</pubDate>
      
      <guid>/2017/05/0019-droid4/</guid>
      <description>The 4.12 merge window will most likely close on Sunday, so its a good time to check the Droid 4 status matrix. This merge window lots of changes were queued:
New drivers: real time clock (RTC), power button, analogue digital converter (ADC), battery charger, LEDs (RGB, capslock status, android buttons)
DTS additions: LCD (no driver yet), HDMI, Keyboard/LCD backlight (no driver yet), Touchscreen, Temperature sensor, Accelerometer, Compass, Regulators, RTC, Power button, ADC, USB PHY (no driver yet), Battery charger, LEDs, Keyboard, Poweroff, USB configuration for modems</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - WL1285 and GPS</title>
      <link>/2017/03/0015-wl1285/</link>
      <pubDate>Thu, 23 Mar 2017 03:44:00 +0100</pubDate>
      
      <guid>/2017/03/0015-wl1285/</guid>
      <description>Today I had another look at GPS for Droid 4. In theory it has 3 different chips, that have GPS receivers: WL1285C, MDM6600, WG3LTE. The Cyanogenmod changelog for the Droid 4 contains a hint, that WL1285C&amp;rsquo;s GPS module is the one actually used:
Don&#39;t hold st_wakelock until BT/GPS is used for the first time Also the stock kernel contains a driver for GPS from WiLink. WiLink based chips come with either SPI or SDIO connection for WLAN and a shared UART for Bluetooth (BT), FM radio, GPS and NFC.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - Update</title>
      <link>/2017/03/0014-droid4-update/</link>
      <pubDate>Mon, 20 Mar 2017 08:05:00 +0100</pubDate>
      
      <guid>/2017/03/0014-droid4-update/</guid>
      <description>Some time has gone by since my last post, so lets have a look what changed for Droid 4:
I prepared a CPCAP LED driver I published updated patches for the N950 display (also used for D4) Milo Kim published TI LMU backlight driver supporting D4&amp;rsquo;s LM3532 Tony published a CPCAP ADC driver Tony published a simple CPCAP battery charer driver Tony published CPCAP usb phy Tony published Motorola MDM6600 patch for qmi_wwan Tony published lots of droid 4 DTS patches adding Touchscreen LCD backlight GPIO poweroff Temperature sensor HDMI support (incl.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - Modem</title>
      <link>/2017/02/0013-droid-4-modem/</link>
      <pubDate>Thu, 23 Feb 2017 11:29:00 +0100</pubDate>
      
      <guid>/2017/02/0013-droid-4-modem/</guid>
      <description>Today I had a first look at the modems of the Droid 4. Conclusion Modem 1 (2G/3G): Name: MDM 6600 USB ID: 22b8:2a70 Drivers: bpwake - wakeup ttyO0 via gpio mdm6600_ctrl - modem gpio control via sysfs mdm6600_modem - usb-serial driver (unused?) qcusbnet - qmi driver, mainline provides alternative ts27010mux - 3GPP 27.010 mux ldisc for ttyO0 Modem 2 (4G) Name: W3GLTE USB ID: 22b8:4267 Drivers: wrigley_ctrl - modem gpio control via sysfs oob-wake - usb wakeup via gpio cdc-ether - usb network device Both modems require a GPIO control driver for powering them up/down.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - RTC driver</title>
      <link>/2017/02/0012-droid-4-rtc/</link>
      <pubDate>Mon, 20 Feb 2017 08:50:00 +0100</pubDate>
      
      <guid>/2017/02/0012-droid-4-rtc/</guid>
      <description>With Debian up &amp;amp; running I had a look at what needs to be done in the mainline kernel. Tony is working on the ADC parts, which are required for the battery/charger work and mentioned he will have a look at USB. He also mentioned, that somebody with spare cycles could take care of CPCAP&amp;rsquo;s rtc &amp;amp; watchdog. I had a look at Motorola&amp;rsquo;s vendor kernel and as far as I can see CPCAP does not come with a watchdog (unlike twl4030/twl6040).</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - Debian</title>
      <link>/2017/02/0010-droid-4-debian/</link>
      <pubDate>Fri, 17 Feb 2017 09:58:00 +0100</pubDate>
      
      <guid>/2017/02/0010-droid-4-debian/</guid>
      <description>In the last post I rooted the Droid 4 and installed LineageOS with SafeStrap as bootloader. Today I took care of getting the mainline kernel running and preparing a rootfs.
After some communication with Tony I got the kexec stuff running (at the end the problem was my compiler generating binaries not suitable for Android). Instead of getting a compiler toolchain for Android I decided to rewrite the binary into a shellscript, so that no compiler is required.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4 - rooting</title>
      <link>/2017/02/0009-droid-4-root/</link>
      <pubDate>Thu, 16 Feb 2017 10:53:00 +0100</pubDate>
      
      <guid>/2017/02/0009-droid-4-root/</guid>
      <description>Yesterday I received the Motorola Droid 4 from my previous article. It came in a reasonable condition with a few scratches in the case (none in the display) and some of the back cover&amp;rsquo;s clips being broken. First impression: The phone feels a bit more clumpy than the N950, but much less than the N900. The sliding mechanism feels qualitatively worse than Nokia&amp;rsquo;s and the same goes for the keyboard quality.</description>
    </item>
    
    <item>
      <title>Motorola Droid 4</title>
      <link>/2017/02/0006-droid-4/</link>
      <pubDate>Tue, 07 Feb 2017 23:00:00 +0100</pubDate>
      
      <guid>/2017/02/0006-droid-4/</guid>
      <description>Tony Lindgren is currently working on mainline kernel support for the Motrola Droid 4 (Wikipedia, GSMArena, iFixit Teardown). He documented his work to get serial over USB on the following page: http://muru.com/linux/d4. I just got myself a used one via Ebay, since it&#39;s a decent upgrade from the Nokia N9xx phones. It&#39;s also quite cheap (30$ in US, 50€ after import to DE (shipping + customs)). Last but not least there is no newer phone available, which has a proper hardware keyboard.</description>
    </item>
    
  </channel>
</rss>
