Maemo Leste Wiki - User contributions [en]

Wishlist

2021-08-09T14:18:08Z

Clort: /* Applications */ Flite is in devuan repo

If there is an application from Maemo Fremantle or even from a standard Linux distribution that you wish to see in Maemo Leste, please add it on this page.

We do not promise that we can port it right away, but we will try, as far as our resources allow.

To make our this easy for our developers, please include links to descriptions of the application, sources, and other useful information.

== Applications ==

{| class="wikitable"http://maemo.org/packages/view/orecchiette/
! Package name
! Done
! Reason
! User
! URL
! Notes
|-
| osso-notes || Yes (quicknote) || a notes application || [[User:Wizzup]] || http://maemo.org/packages/view/osso-notes/ ; http://wiki.maemo.org/Quicknote || Quicknote currently packaged. Usage notes - http://wiki.maemo.org/Quicknote
|-
| pinball || No || fun || Sicelo || https://packages.debian.org/buster/pinball or http://linball.sourceforge.net/|| any implementation.
|-
| scummvm || https://github.com/maemo-leste/bugtracker/issues/269 || fun || [[User:Wizzup]] || http://maemo.org/packages/view/scummvm/ || latest version please
|-
| [[Games/Brainparty|brainparty]] || Yes || for fun || [[User:Wizzup]] || http://maemo.org/downloads/product/Maemo5/brainparty/ ||
|-
| Picodrive || No || Sega emulator, fun || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/p/picodrive/ || http://maemo.org/packages/view/orecchiette/(has also Psycho Pinball installable)
|-
| Internet radio: mSoma || No || media || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/m/msoma/ ||http://maemo.org/packages/view/orecchiette/
|-
| Cutetube2 || No || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cutetube2/0.5.2/ || could change cutetube into a youtube-dl frontend
|-
| PDF reader || Yes || reading || [[User:Wizzup]] || https://github.com/community-ssu/osso-pdf-viewer/ || libhildonfm has bugs regarding file opening dialogs that need to be fixed
|-
| Calendar app || Yes || orga || [[User:Maemish]] || https://wiki.maemo.org/Qalendar || Probably Qalendar and not fremantle closed. Requires Qt5 port.
|-
| Alarm clock || Yes || orga || [[User:Maemish]] || ? || alarmd and alarm UI already works, there might be a FOSS UI
|-
| Word processor / Abiword || Might already be in debian || orga || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/abiword/2.8.1-2maemo4/
|-
| Simple Brightness Applet || Yes, see https://github.com/maemo-leste/simple-brightness-applet || ? || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/simple-brightness-applet/1.1-1maemo0/ || This is not latest build from extras-devel
|-
|Status bar: Load Applet || No || CPU and RAM usage, screenshot and screen record. || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/load-applet/0.4.6-5/ || Needs to be ported to gst1.0
|-
| Camera App: BlessN900|| No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_non-free_armel/blessn900/0.49-3/ ||
|-
| Image viewer/editor || Yes || || [[User:Maemish]] || https://github.com/maemo-leste-extras/mihphoto ||
|-
| Mail with imap support || No || || [[User:Maemish]] || ||
|-
| RSS Feed Reader: Who knows a good one? || No || Reading/Media || [[User:Maemish]] || ||
|-
| Browser: Dooble || No || internet || [[User:Maemish]] || New homepage: https://textbrowser.github.io/dooble/ Not sure if the old package helps porting http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/dooble/1.52-maemo1/ ||
|-
| OpenMediaPlayer || ? || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/openmediaplayer/20161108-1/ Homepage: http://gitorious.org/qt-mediaplayer ||
|-
| SMPlayer || No || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/smplayer/0.6.9-1maemo7/ Homepage: http://smplayer.sourceforge.net ||
|-
| Unzip addon for filemanager || No || utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/diablo_extras-devel_free_armel/unzip-fm/0.1.3-3/ ||
|-
| D-Theme SimpleBlackGreen || No || fashion || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/d/d-theme-simple-blackgreen/ ||
|-
| Bootscreen: Don't Panic! || No || fun (but neccessity) || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/dontpanic/1.0/ ||
|-
| MMS: fMMS || No || media || [[User:Maemish]] || https://garage.maemo.org/projects/fmms ||
|-
| Homescreen Dockbar Widget|| No || fashion/utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/homescreen-dockbar/0.0.6/ ||
|-
| Hotspot: MobileHotspot || No. || utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/mobilehotspot/0.3.5/ || Either this or something else. This has only wep encryption which should be changed.
|-
| Firewall || No || || [[User:Maemish]] || || Something with easy configuration.
|-
| Swappolube || No || || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle-1.3/free/s/swappolube/ ||
|-
|bnf- Battery information at glance || No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/bnf/1.2/ ||
|-
| cardioalert || No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cardioalert/0.1/ ||
|-
| gnumeric || No || Office || [[User:ric9k]] || http://maemo.org/packages/view/gnumeric/ ||
|-|-
| hamsterfiler || WIP [https://github.com/maemo-leste/bugtracker/issues/499] || utilities/files || [[User:ric9k]] || http://maemo.org/packages/view/hamsterfiler/ ||
|-|-
| alarmed (or cron?) || No || utilities || [[User:ric9k]] || http://maemo.org/packages/view/alarmed/ ||
|-|-
| user friendly tracker || No || utilities? || [[User:ric9k]] || n/a :-) ||
|-|-
| Maps (offline) || Yes || Navigation || [[User:Sicelo]] || || (maep, modrana, cloudgps are all packaged). Ideally something like https://f-droid.org/en/packages/com.github.axet.maps/ from Android, but Modrana, https://github.com/M4rtinK/modrana may be easier as a start. [FoxtrotGPS https://www.foxtrotgps.org] might be the easiest to adapt, it is already packaged in Devuan.
|-
| Orecchiette || No || calls recording || [[User:capitannemo]] || http://maemo.org/packages/view/orecchiette/ ||
|-
| Panucci || No || audiobook || [[User:capitannemo]] || http://maemo.org/packages/view/panucci/ ||
|-
| gPodder || No || podcast || [[User:capitannemo]] || http://maemo.org/packages/view/gpodder/ ||
|-
| Symfonie || No || directory-based audioplayer || [[User:capitannemo]] || http://maemo.org/packages/view/symfonie/ ||
|-
| osso-clock || Yes (clock-ui) || clock and alarms application || pavel || ||
|-
| freecell4maemo || No || freecell game || pavel || ||
|-
| [http://festvox.org/index.html CMU Flite] || In Repo || Accessibility (TTS) || [[User:Buffer|Buffer]] ([[User talk:Buffer|talk]]) 21:48, 2 March 2020 (UTC) || https://github.com/festvox/flite ||
|-
| Cooktimer || No || feature-rich timers || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cooktimer/0.0.4-24/ || latest from extras-devel
|-
| OpenSSH Status Widget || No || openSSH monitor and config. || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/openssh-status-widget/2.2-12/ || Installing this package is the only step required on a fresh n900 to have openssh working
|-
| Recaller || No || record with one tap || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/recaller/2.1.0-5/ ||
|-
| NecroPlayer2 || No || directory-based audioplayer, easy playlist edit, multiple directories, very useful with recaller widget || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/necroplayer2/0.2.3/ ||
|-
| Simpler Brightness Applet || Yes || simple brightness applet with single tap for backlight and long tap for settings || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/simpler-brightness-applet/1.0/ ||
|)
|-
| telepathy-signal || No || The best open source alternative to WhatsApp should be ready for use with Maemo Leste || [[User:Derby]] || https://github.com/signalapp/Signal-Desktop ; https://github.com/AsamK/signal-cli || This is a suggestion to create a Telepathy connection manager for Signal. Although the Signal [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842943 Desktop] and [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926807 CLI] can be installed, they are not yet available in Debian. In any case, it would be great to have a Telepathy connection manager for Signal to provide seamless integration with Maemo.

Motorola Droid 4

2021-07-28T11:30:51Z

Clort: /* Notes */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Motorola Droid 4

2021-07-28T11:30:11Z

Clort: /* Notes */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|aemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Motorola Droid 4

2021-07-28T11:29:18Z

Clort: /* Notes */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|620px|thumb|aemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Motorola Droid 4

2021-07-28T11:28:52Z

Clort: /* Notes */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|620px|thumb|left|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

File:Maemo-leste-droid4-kbd-2021-07.png

2021-07-28T11:25:07Z

Clort: Clort uploaded a new version of File:Maemo-leste-droid4-kbd-2021-07.png

== Summary ==
View of Droid4 Keyboard layout with 'OK' special keys.

Motorola Droid 4

2021-07-28T11:17:26Z

Clort: Added graphic of droid4 keyboard layout

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|620px|thumb|left|maemo-leste droid4 keyboard]]

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

File:Maemo-leste-droid4-kbd-2021-07.png

2021-07-28T11:09:52Z

Clort: View of Droid4 Keyboard layout with 'OK' special keys.

== Summary ==
View of Droid4 Keyboard layout with 'OK' special keys.

Nokia N900

2021-07-14T09:41:41Z

Clort: /* Added source repository for 0xFFFF */

{{Infobox Device
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]
|manufacturer=Nokia
|codename=Rover, RX-51
|dimensions=110.9mm x 59.8mm x 18mm
|release_date=2009-11-11
|category=Supported
|soc=TI OMAP 3430 @600MHz
|dram=256 MB Mobile DDR
|power=
|lcd=800x480 3.5" Resistive TFT
|video=PowerVR SGX530
|audio=
|network=WL1251
|storage=32GB
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=5.1
|sw_serial=Yes, UART under battery, 2.7V max!
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=
|sw_tv=Yes
|sw_3daccel=Yes, closed driver
|sw_vibration=Yes
|sw_audio=Yes (complex, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=Yes, actually CIR, not IrDA
|sw_2g3gdata=Yes
|sw_4gdata=
|sw_bluetooth=No
|sw_fmtx=Yes
|sw_fmrx=No
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=
|sw_backcam=
|sw_idlepower=300mW (needs kernel work)
|sw_standbytime=
}}

== Installation ==

The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.

=== Image installation ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

dd the image to an sd card.

If using a Windows machine, you can use [https://etcher.io/ Etcher]

See the next section on how to boot. (using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613)

=== Bootloader (U-Boot) setup ===

==== Quick ====

If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly:

1. Either download 0xFFFF (binary for x86) from https://maedevu.maemo.org/images/n900/tools/ or build from source from https://github.com/pali/0xFFFF/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

To flash u-boot permanently, you can issue the following command

'''(Be careful though. This will replace the existing fremantle kernel. Only do this if you do not care about the existing maemo installation or you know how to recover from this condition)''')

<code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f</code>

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
cat > /etc/bootmenu.d/30-maemo-leste.item << "EOF" &&
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

4. Reboot the device

=== Increase filesystem size ===

Run the following script: <code>/etc/expandcard.sh</code>

== Serial ==

http://n900.elektranox.org/serial-adapter.html

http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 hours. Power management on the N900 is being worked on: https://github.com/maemo-leste/bugtracker/issues/170

* https://wiki.maemo.org/N900_Hardware_Power_management
* https://wiki.maemo.org/N900_Hardware_Power_Consumption

Run:

modprobe ledtrig-default-on

And:

echo default-on > /sys/class/leds/debug::sleep/trigger

To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.

Currently it does not yet reliably reach any sleep modes.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

== Battery calibration ==

Nokia N900 has bq27200 integrated circuit for monitoring battery state. The datasheet can be found here: http://www.ti.com/lit/ds/symlink/bq27200.pdf. If you are curious, check the section called "Gas Gauge Operation" for how the battery calibration is done in a low level.

Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.

* Fully charge Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* You may use the device as you normally do. You may power it off, power it on, reboot. All as usual. Just don't connect the device to a charger or a PC using the USB cable.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* Wait for about 20 seconds and attach the charger. If the device was powered off because of battery depletion, it's fine. The battery should have done the calibration cycle. Just attach the charger to the device, give it a minute and press power button to start booting.
* If you still see "Battery not calibrated" message, reboot the device.

After the first calibration cycle you will see that it has ~1700 mAh for the fully charged battery. This value is wrong. It's how the battery calibration works in low level: it can't change the fully charged value of the battery in steps that exceed 12.5%. What this means for us: it's needed to repeat the calibration cycle several times to get more accurate value. It may take about 3-7 calibration cycles to get the proper mAh value for fully charged battery. If you spend some time on this process, you will get really accurate battery gauge and you will always know how much charge is remaining.

Tip 1. If for any reason you want to reset the battery calibration value to see the message “Battery is not calibrated” again, you should remove the battery from the device for about 6 hours.
Tip 2. If you replace the battery, you may want to do 1-2 calibration cycles described above to update the gauge for your new battery.

== Accessing MTD ==

List devices:
cat /proc/mtd

Mount:
apt install mtd-utils
mkdir -vp /mnt/fremantle
ubiattach -p /dev/mtd5
mount -t ubifs ubi:rootfs /mnt/fremantle

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-linux
|-
| Serial || Yes || Requires special hardware
|-
| Charging || Yes ||
|-
| Wireless || Yes || Firmware is non-free
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible
|-
| Keyboard || Yes ||
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || closed driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || No hardware
|-
| TV-out || Yes || Enable in alsamixer (Jack Function in alsamixer to TV OUT), enable with <code>xrandr --output TV --mode 800x480 --same-as LCD</code>. Set PAL/NTSC with <code>xrandr --output TV --set SignalProperties PAL</code>, and scale with <code>xrandr --output TV --set TVScale 90</code>.
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Extras/ScummVM

2021-07-09T01:15:58Z

Clort: /* TODO */

{{Infobox Package
|image=[[File:ScummVM_Logo.png|250px]]
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2021-05-21
|website=https://www.scummvm.org/
|maemo_leste_repo=https://github.com/maemo-leste-extras/scummvm
|category=Games
|packager=[[User:Wizzup]]
}}

ScummVM is a program which allows you to run certain classic graphical adventure and role-playing games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed! ScummVM is a complete rewrite of these games' executables and is not an emulator. (From ScummVM website)

Relevant issue: https://github.com/maemo-leste/bugtracker/issues/269

Also see this page for more info: https://wiki.scummvm.org/index.php/Maemo

== Status ==

* Games seems to be playable, with sound and input

* GUI with default theme is too small to be clickable/visable. WIth theme scummvm-remastered (scummremastered.zip) it is possible to set GUI scale to 'Large' and get a readable GUI:

[[File:Leste-scummvm-bigtheme.jpg|500px]]

To get large readable GUI:
<code>edit ~/.config/scummvm.ini
change gui_base=0 to gui_base=240</code>

=== Tested games ===
Neverhood, Ultima 4, Ultima 6, Grim Fandango, Broken Sword 1

==== The Neverhood ====

Change keymap as appropriate, works well.

[[File:ScummVMNeverhood.png|500px]]

== TODO ==

* Implement sane default keys for the devices (there is rudimentary detection for the N900, but we support more devices)
* Use libsdl2 build, didn't compile when [[User:Wizzup]] tried.
* Revise Maemo-Leste configure backend/target to remove 'optification'
* Create Widescreen readable theme
* Fix touchscreen to pointer position de-synchronization. (Starts okay, goes bad).
* Find rendering and build options for low battery use (adventure game sessions can be long)
* Get Maemo-Leste target into upstream SCUMMVM

[[Category:Extras]]

[[Category:Games]]

Extras/ScummVM

2021-07-08T22:00:10Z

Clort: /* TODO */

{{Infobox Package
|image=[[File:ScummVM_Logo.png|250px]]
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2021-05-21
|website=https://www.scummvm.org/
|maemo_leste_repo=https://github.com/maemo-leste-extras/scummvm
|category=Games
|packager=[[User:Wizzup]]
}}

ScummVM is a program which allows you to run certain classic graphical adventure and role-playing games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed! ScummVM is a complete rewrite of these games' executables and is not an emulator. (From ScummVM website)

Relevant issue: https://github.com/maemo-leste/bugtracker/issues/269

Also see this page for more info: https://wiki.scummvm.org/index.php/Maemo

== Status ==

* Games seems to be playable, with sound and input

* GUI with default theme is too small to be clickable/visable. WIth theme scummvm-remastered (scummremastered.zip) it is possible to set GUI scale to 'Large' and get a readable GUI:

[[File:Leste-scummvm-bigtheme.jpg|500px]]

To get large readable GUI:
<code>edit ~/.config/scummvm.ini
change gui_base=0 to gui_base=240</code>

=== Tested games ===
Neverhood, Ultima 4, Ultima 6, Grim Fandango, Broken Sword 1

==== The Neverhood ====

Change keymap as appropriate, works well.

[[File:ScummVMNeverhood.png|500px]]

== TODO ==

* Implement sane default keys for the devices (there is rudimentary detection for the N900, but we support more devices)
* Use libsdl2 build, didn't compile when [[User:Wizzup]] tried.
* Revise Maemo-Leste configure backend/target to remove 'optification'
* Create Widescreen readable theme
* Find rendering and build options for low battery use (adventure game sessions can be long)
* Get Maemo-Leste target into upstream SCUMMVM

[[Category:Extras]]

[[Category:Games]]

Motorola Droid 4

2021-07-08T21:13:22Z

Clort: /* Using a configured Leste sdcard in a different Droid4 */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Extras/ScummVM

2021-07-08T20:12:20Z

Clort: /* TODO */

{{Infobox Package
|image=[[File:ScummVM_Logo.png|250px]]
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2021-05-21
|website=https://www.scummvm.org/
|maemo_leste_repo=https://github.com/maemo-leste-extras/scummvm
|category=Games
|packager=[[User:Wizzup]]
}}

ScummVM is a program which allows you to run certain classic graphical adventure and role-playing games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed! ScummVM is a complete rewrite of these games' executables and is not an emulator. (From ScummVM website)

Relevant issue: https://github.com/maemo-leste/bugtracker/issues/269

Also see this page for more info: https://wiki.scummvm.org/index.php/Maemo

== Status ==

* Games seems to be playable, with sound and input

* GUI with default theme is too small to be clickable/visable. WIth theme scummvm-remastered (scummremastered.zip) it is possible to set GUI scale to 'Large' and get a readable GUI:

[[File:Leste-scummvm-bigtheme.jpg|500px]]

To get large readable GUI:
<code>edit ~/.config/scummvm.ini
change gui_base=0 to gui_base=240</code>

=== Tested games ===
Neverhood, Ultima 4, Ultima 6, Grim Fandango, Broken Sword 1

==== The Neverhood ====

Change keymap as appropriate, works well.

[[File:ScummVMNeverhood.png|500px]]

== TODO ==

* Implement sane default keys for the devices (there is rudimentary detection for the N900, but we support more devices)
* Use libsdl2 build, didn't compile when [[User:Wizzup]] tried.
* Revise Maemo-Leste configure backend/target to remove 'optification'
* Create Widescreen readable theme
* Fix mouse cursor tracking for touchscreen
* Find rendering and build options for low battery use (adventure game sessions can be long)
* Get Maemo-Leste target into upstream SCUMMVM

[[Category:Extras]]

[[Category:Games]]

Extras/ScummVM

2021-07-08T20:11:24Z

Clort: /* Status */

Extras/ScummVM

2021-07-08T20:10:24Z

Clort: /* Status */

{{Infobox Package
|image=[[File:ScummVM_Logo.png|250px]]
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2021-05-21
|website=https://www.scummvm.org/
|maemo_leste_repo=https://github.com/maemo-leste-extras/scummvm
|category=Games
|packager=[[User:Wizzup]]
}}

ScummVM is a program which allows you to run certain classic graphical adventure and role-playing games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed! ScummVM is a complete rewrite of these games' executables and is not an emulator. (From ScummVM website)

Relevant issue: https://github.com/maemo-leste/bugtracker/issues/269

Also see this page for more info: https://wiki.scummvm.org/index.php/Maemo

== Status ==

* Games seems to be playable, with sound and input

* GUI with default theme is too small to be clickable/visable. WIth theme scummvm-remastered (scummremastered.zip) it is possible to set GUI scale to 'Large' and get a readable GUI:

[[File:Leste-scummvm-bigtheme.jpg|500px]]

To get large readable GUI:
<code>edit ~/.config/scummvm.ini
change gui_base=0 to gui_base=240</code>

=== Tested games ===
Neverhood, Ultima 4, Ultima 6, Grim Fandango, Broken Sword 1

==== The Neverhood ====

Change keymap as appropriate, works well.

[[File:ScummVMNeverhood.png|500px]]

==== TODO ====
* Revise Maemo-Leste configure backend/target to remove 'optification'
* Create Widescreen readable theme
* Fix mouse cursor tracking for touchscreen
* Find rendering and build options for low battery use (adventure game sessions can be long)
* Get Maemo-Leste target into upstream SCUMMVM

== TODO ==

* Implement sane default keys for the devices (there is rudimentary detection for the N900, but we support more devices)
* Use libsdl2 build, didn't compile when [[User:Wizzup]] tried.

[[Category:Extras]]

[[Category:Games]]

File:Leste-scummvm-bigtheme.jpg

2021-07-08T19:39:49Z

Clort: Scummvm large theme (before widescreen mod) on Droid4

== Summary ==
Scummvm large theme (before widescreen mod) on Droid4

Motorola Droid 4

2021-07-07T01:38:20Z

Clort: /* Gallery */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall ti-firmware-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
Droid4_Daimonin_Hdmi.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

File:Droid4 Daimonin Hdmi.jpg

2021-07-07T01:37:12Z

Clort: Example of droid4 with hdmi out enabled: xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off

== Summary ==
Example of droid4 with hdmi out enabled:
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off

Motorola Droid 4

2021-06-29T10:02:49Z

Clort: /* Using a configured Leste sdcard in a different Droid4 */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall ti-firmware-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Motorola Droid 4

2021-06-29T10:01:32Z

Clort: /* Using a configured Leste sdcard in a different Droid4 */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate. The calibration script requires stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall ti-firmware-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Motorola Droid 4

2021-06-29T09:55:00Z

Clort: added instructions for recalibrating wifi

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.11.0
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this:

Read modem output:
<pre>
cat /dev/motmdm1 &
</pre>

Online modem:
<pre>
printf "AT+CFUN=1\r" > /dev/motmdm1
</pre>

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

== Using a configured Leste sdcard in a different Droid4 ==

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device:
apt reinstall ti-firmware-connectivity
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

== Old status overview ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

[[Category:Device]]

Tweaking

2021-04-10T11:43:28Z

Clort:

Maemo Leste is very tweakable/hackable/versatile, this page lists some of the things you could change, hopefully grouped in a meaningful manner.

==== Prevent autoremoval of downloaded .deb files ====
The tool 'apt' as an alternative to apt-get uses different configuration.
To prevent apt from auto-deleting downloaded .deb packages do this:
<pre>echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \ > /etc/apt/apt.conf.d/01keep-debs</pre>

===== GConf Settings =====

==== Show current gconf settings ====

<pre>gconftool-2 -R / |less</pre>
<pre>gconftool -S \* |less</pre>

==== Battery icon ====

You can change the animation of the charging icon to show the current charge capacity:
<pre>gconftool-2 -s /apps/osso/status-area-applet-battery/show_charge_charging -t bool true</pre> [edit] ''This doesn't do anything for me - clort''

==== Disable screen rotate ====

You can lock screen orientation to the current (disabling screen rotation) with
<pre>gconftool-2 -s /apps/osso/hildon-desktop/orientation_lock -t bool true</pre>

==== Switch clock display to 24h ====

<pre>gconftool-2 -s /apps/clock/time-format -t bool true</pre>

==== Prevent user rearranging of app menu ====

<pre>gconftool-2 -s /apps/osso/hildon-desktop/key-actions/disable_edit -t bool true</pre>

==== Hide toolbar at bottom of osso-xterm (to get more lines) ====

<pre>gconftool-2 -s /apps/osso/xterm/toolbar -t bool false</pre>

Tweaking

2021-04-10T11:38:39Z

Clort: added preventing apt from autoremoving downloaded .deb packages

Maemo Leste is very tweakable/hackable/versatile, this page lists some of the things you could change, hopefully grouped in a meaningful manner.

==== Show current gconf settings ====

<pre>gconftool-2 -R / |less</pre>
<pre>gconftool -S \* |less</pre>

==== Battery icon ====

You can change the animation of the charging icon to show the current charge capacity:
<pre>gconftool-2 -s /apps/osso/status-area-applet-battery/show_charge_charging -t bool true</pre> [edit] ''This doesn't do anything for me - clort''

==== Prevent autoremoval of downloaded .deb files ====
The tool 'apt' as an alternative to apt-get uses different configuration.
To prevent apt from auto-deleting downloaded .deb packages do this:
<pre>echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \ > /etc/apt/apt.conf.d/01keep-debs</pre>

==== Disable screen rotate ====

You can lock screen orientation to the current (disabling screen rotation) with
<pre>gconftool-2 -s /apps/osso/hildon-desktop/orientation_lock -t bool true</pre>

==== Switch clock display to 24h ====

<pre>gconftool-2 -s /apps/clock/time-format -t bool true</pre>

==== Prevent user rearranging of app menu ====

<pre>gconftool-2 -s /apps/osso/hildon-desktop/key-actions/disable_edit -t bool true</pre>

==== Hide toolbar at bottom of osso-xterm (to get more lines) ====

<pre>gconftool-2 -s /apps/osso/xterm/toolbar -t bool false</pre>

Getting Started

2021-04-10T05:01:22Z

Clort: /* Expand the root partition to fill SD card */

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= Expand the root partition to fill SD card =

A helpful script is included to expand the root partition to fill the microSD card.
After booting and logging in to root, execute/etc/expandcard.sh

This will expand the root partition to fill the microSD card using resize2fs.

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-04-10T00:43:45Z

Clort: /* Expand the root partition to fill SD card */

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= Expand the root partition to fill SD card =

A helpful script is included to expand the root partition to fill the microSD card.
After booting and logging in to root. execute
/etc/expandcard.sh

This will expand the root partition to fill the microSD card using resize2fs.

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-04-10T00:43:02Z

Clort: /* Expand the root partition to fill SD card */

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= Expand the root partition to fill SD card =

A helpful script is included to expand the root partition to fill the microSD card.
After booting and logging in to root. execute
/etc/expandcard.sh

This will expand the root partition to fill the microSD card using resize2fs

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-04-10T00:42:36Z

Clort: added instruction for expanding root partition

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= Expand the root partition to fill SD card =

A helpful script is included to expand the root partition to fill the microSD card.
After booting and logging in to root. execute
/ex/expandcard.sh

This will expand the root partition to fill the microSD card using resize2fs

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Hacks

2021-04-06T23:52:10Z

Clort: /* Fun Hacks for maemo-leste */

==== Fun Hacks for maemo-leste ====

----

apt install -y uxterm imagemagick-6.q16

Add to ~/.bashrc:

alias uxt="uxterm -ti vt340 -fa 'Monospace' -fs 16 -fullscreen"

echo "convert \$@ -geometry 950x484 sixel:-" > /usr/local/bin/imgterm

chmod uog+x /usr/local/bin/termimg

display pictures as sixel graphics in your terminal with:

imgterm avatar-yinlee.png

<gallery>Sixel.png</gallery>

You can also get thumbnails of directories with images with imagemagick and the shellscript [https://github.com/hackerb9/lsix/archive/master.zip lsix sixel thumbnailer]
----

Hacks

2021-04-06T23:51:29Z

Clort: Created page with "==== Fun Hacks for maemo-leste ==== ---- apt install -y uxterm imagemagick-6.q16 Add to ~/.bashrc: alias uxt="uxterm -ti vt340 -fa 'Monospace' -fs 16 -fullscreen" echo "c..."

==== Fun Hacks for maemo-leste ====

----

apt install -y uxterm imagemagick-6.q16

Add to ~/.bashrc:

alias uxt="uxterm -ti vt340 -fa 'Monospace' -fs 16 -fullscreen"

echo "convert \$@ -geometry 950x484 sixel:-" > /usr/local/bin/imgterm

chmod uog+x /usr/local/bin/termimg

display pictures as sixel graphics in your terminal with:

termimg mypic.png

<gallery>Sixel.png</gallery>

You can also get thumbnails of directories with images with imagemagick and the shellscript [https://github.com/hackerb9/lsix/archive/master.zip lsix sixel thumbnailer]
----

File:Sixel.png

2021-04-06T23:44:04Z

Clort: Sixel Graphics in uxterm on Maemo-Leste

Sixel Graphics in uxterm on Maemo-Leste

Development/Modified Software

2021-04-06T23:30:35Z

Clort:

TODO, expand on this, why they are patched, etc:

* gtk2: extra widgets are added, menu patches, integration with virtual keyboard for (any) text field, theming
* SDL: full screen patches, other window manager patches
- SDL1.2 and SDL2 have different issues. Lacking keyboard input in fullscreen is top prio.
* qt5 (?): TBD
* gtk3 (?): Same as gtk2, currently not patched, though.
* xorg-server: Patched modesetting for rotation.

Tweaking

2021-04-06T23:25:50Z

Clort: /* Switch clock display to 24h */

Maemo Leste is very tweakable/hackable/versatile, this page lists some of the things you could change, hopefully grouped in a meaningful manner.

==== Show current gconf settings ====

<pre>gconftool-2 -R / |less</pre>
<pre>gconftool -S \* |less</pre>

==== Battery icon ====

You can change the animation of the charging icon to show the current charge capacity:
<pre>gconftool-2 -s /apps/osso/status-area-applet-battery/show_charge_charging -t bool true</pre> [edit] ''This doesn't do anything for me - clort''

==== Disable screen rotate ====

You can lock screen orientation to the current (disabling screen rotation) with
<pre>gconftool-2 -s /apps/osso/hildon-desktop/orientation_lock -t bool true</pre>

==== Switch clock display to 24h ====

<pre>gconftool-2 -s /apps/clock/time-format -t bool true</pre>

==== Prevent user rearranging of app menu ====

<pre>gconftool-2 -s /apps/osso/hildon-desktop/key-actions/disable_edit -t bool true</pre>

==== Hide toolbar at bottom of osso-xterm (to get more lines) ====

<pre>gconftool-2 -s /apps/osso/xterm/toolbar -t bool false</pre>

Tweaking

2021-04-05T22:55:47Z

Clort: more gconftool things to do

Maemo Leste is very tweakable/hackable/versatile, this page lists some of the things you could change, hopefully grouped in a meaningful manner.

==== Show current gconf settings ====

<pre>gconftool-2 -R / |less</pre>
<pre>gconftool -S \* |less</pre>

==== Battery icon ====

You can change the animation of the charging icon to show the current charge capacity:
<pre>gconftool-2 -s /apps/osso/status-area-applet-battery/show_charge_charging -t bool true</pre> [edit] ''This doesn't do anything for me - clort''

==== Disable screen rotate ====

You can lock screen orientation to the current (disabling screen rotation) with
<pre>gconftool-2 -s /apps/osso/hildon-desktop/orientation_lock -t bool true</pre>

==== Switch clock display to 24h ====

<pre>gconftool-2 -s -t bool /apps/clock/time-format true</pre>

==== Prevent user rearranging of app menu ====

<pre>gconftool-2 -s /apps/osso/hildon-desktop/key-actions/disable_edit -t bool true</pre>

==== Hide toolbar at bottom of osso-xterm (to get more lines) ====

<pre>gconftool-2 -s /apps/osso/xterm/toolbar -t bool false</pre>

Tweaking

2021-04-05T22:37:02Z

Clort: added disable screen rotate setting and settings list entry

Getting Started

2021-04-05T18:57:53Z

Clort: added some info for copying / installing image to microsd

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Tricks

2020-12-24T05:00:59Z

Clort: Added Macchanger Trick, Moved barrier trick from droid4 hints.

List of tricks:

==== Randomize MAC Address ====
Some users may wish to change the MAC address of an interface, for e.g. to prevent wifi networks associating their MAC address with their network usage pattern.

The macchanger package addresses this by either automatically or manually changing the MAC address of enabled interfaces.
<pre>apt install -y macchanger
</pre>
During installation, the package configuration allows user to select automatic change of MAC address when interface is brought up. This may interfere with USB networking. As an alternative, user can manually change the wlan0 MAC.
<pre>
macchanger wlan0 -e -a
ifconfig wlan0 up
</pre>

==== Keyboard / Mouse sharing with PC ====
To use a leste device while working at desktop it can be convenient to share mouse and keyboard of the host pc with the leste device. The 'barrier' client/server program, forked from 'synergy', allows this.
<pre>
https://github.com/debauchee/barrier Barrier software-KVM switch
</pre>
A hildonized maemo-leste binary of the client is not available at time of this writing. Developers and testers may wish to disable undesired modules included with the barrier source, before compiling.

Motorola Droid 4

2020-12-22T01:16:48Z

Clort: /* Stuff to try */ additions by Clort.

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No ||
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Updating Android. This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

[[Category:Device]]

Motorola Droid 4

2020-11-21T14:29:10Z

Clort: /* Gallery */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.8.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Proximity sensor || WIP || needs mce work
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No ||
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Updating Android. This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

[[Category:Device]]

File:Droid4-leste-surf master.jpg

2020-11-21T14:28:40Z

Clort: suckless 'surf' browser - not from debian repo - doesn't have url bar. default.css in ~/.surf/styles/default.css is: pre,textarea,body,input,td,tr,p { background-color: black !important; background-image: none !important; color: #e0e0e0 !important...

suckless 'surf' browser - not from debian repo - doesn't have url bar.

default.css in ~/.surf/styles/default.css is:
pre,textarea,body,input,td,tr,p {
background-color: black !important;
background-image: none !important;
color: #e0e0e0 !important;
}

div {
background-color: #101010 !important;
background-image: none !important;
color: #e0e0e0 !important;
}

h1,h2,h3,h4 {
background-color: black !important;
color: #e02020 !important;
}

a {
color: #5050f0 !important;
}
a:link {color: #20D0FF !important}
a:visited {color: #DF46C0 !important}
a:hover {color: #FFCC00 !important}
a:active {color: #FF00CC !important}

#bottom-result-container #spon_links { display: none !important; }
#bottom-result-container #sponsored_csa1 { display: none !important; }
#bottom-result-container #sponsored_csa2 { display: none !important; }

Motorola Droid 4

2020-11-19T17:27:10Z

Clort: /* Gallery */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.8.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Proximity sensor || WIP || needs mce work
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No ||
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Updating Android. This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
</gallery>

[[Category:Device]]

File:Droid4-leste-pcsx.jpg

2020-11-19T17:26:31Z

Clort: PCSX-ReArmed runs at under 40% cpu use of one core of Omap4

PCSX-ReArmed runs at under 40% cpu use of one core of Omap4

Motorola Droid 4

2020-11-19T14:21:19Z

Clort: /* Gallery */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.8.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Proximity sensor || WIP || needs mce work
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No ||
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Updating Android. This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
</gallery>

[[Category:Device]]

File:Droid4-leste-utox2.jpg

2020-11-19T14:20:51Z

Clort:

Motorola Droid 4

2020-11-19T13:12:02Z

Clort: /* Gallery */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.8.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Proximity sensor || WIP || needs mce work
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No ||
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Updating Android. This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
</gallery>

[[Category:Device]]

File:Leste-glmatrix.png

2020-11-19T13:11:38Z

Clort: Droid 4 and Leste running JWZ's glmatrix screensaver (without hildon compositing)

Droid 4 and Leste running JWZ's glmatrix screensaver (without hildon compositing)

File:Statsfun.jpg

2020-11-19T13:09:54Z

Clort: Droid 4 Maemo Leste running stats script

Droid 4 Maemo Leste running stats script

File:Leste-neverball.jpg

2020-11-19T13:07:52Z

Clort: Droid 4 running Neverball with gl4es shim.

Droid 4 running Neverball with gl4es shim.

File:Cant have 2 much leste.jpg

2020-11-19T13:04:17Z

Clort: Droid4's running Maemo-Leste

Droid4's running Maemo-Leste