https://leste.maemo.org/api.php?action=feedcontributions&feedformat=atom&user=BuZz 2026-04-30T06:55:01Z User contributions MediaWiki 1.45.3 https://leste.maemo.org/index.php?title=Propaganda&diff=1416 2022-10-10T16:40:02Z

<p>BuZz: </p> <hr /> <div>Place all memes of Maemo Leste you find here.<br /> <br /> == Propaganda ==<br /> [[File:Dont-slave.jpg|200px]]<br /> [[File:Great-war.jpg|200px]]<br /> [[File:Join-leste.jpg|200px]]<br /> [[File:Privacy-and-more.png|200px]]<br /> <br /> [[File:Refuse-duopoly.jpg|200px]]<br /> <br /> == Memes ==<br /> [[File:Os-addicts.jpg|200px]]<br /> <br /> == Various ==<br /> [[File:MaemoSealeste.jpg|200px]]<br /> [[File:Advertizing-in-nurdspace.jpg|200px]]<br /> [[File:Maemo-raised-bar.png|200px]]</div>

BuZz https://leste.maemo.org/index.php?title=Propaganda&diff=1415 2022-10-10T16:39:47Z

<p>BuZz: </p> <hr /> <div>Place all memes of Maemo Leste you find here.<br /> <br /> == Propaganda ==<br /> [[File:Dont-slave.jpg|200px]]<br /> [[File:Great-war.jpg|200px]]<br /> [[File:Join-leste.jpg|200px]]<br /> [[File:Privacy-and-more.png|200px]]<br /> <br /> [[File:Refuse-duopoly.jpg|200px]]<br /> <br /> == Memes ==<br /> [[File:Os-addicts.jpg|200px]]<br /> <br /> == Various ==<br /> [[File:MaemoSealeste.jpg|200px]]<br /> [[File:Advertizing-in-nurdspace.jpg|200px]]<br /> [[Maemo-raised-bar.png]]</div>

BuZz https://leste.maemo.org/index.php?title=File:Maemo-raised-bar.png&diff=1414 2022-10-10T16:39:28Z

<p>BuZz: </p> <hr /> <div></div>

BuZz https://leste.maemo.org/index.php?title=Propaganda&diff=1413 2022-10-10T12:00:31Z

<p>BuZz: </p> <hr /> <div>Place all memes of Maemo Leste you find here.<br /> <br /> == Propaganda ==<br /> [[File:Dont-slave.jpg|200px]]<br /> [[File:Great-war.jpg|200px]]<br /> [[File:Join-leste.jpg|200px]]<br /> [[File:Privacy-and-more.png|200px]]<br /> <br /> [[File:Refuse-duopoly.jpg|200px]]<br /> <br /> == Memes ==<br /> [[File:Os-addicts.jpg|200px]]<br /> <br /> == Various ==<br /> [[File:MaemoSealeste.jpg|200px]]<br /> [[File:Advertizing-in-nurdspace.jpg|200px]]</div>

BuZz https://leste.maemo.org/index.php?title=File:Advertizing-in-nurdspace.jpg&diff=1412 2022-10-10T11:52:21Z

<p>BuZz: </p> <hr /> <div></div>

BuZz https://leste.maemo.org/index.php?title=Sync&diff=1401 2022-10-10T00:34:59Z

<p>BuZz: </p> <hr /> <div>This page explains and suggests various ways of synchronizing contacts, calendars and files.<br /> <br /> = Calendar, Notes, Tasks and Contacts =<br /> <br /> Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).<br /> <br /> == Synchronizing with syncevolution CalDav + CardDav ==<br /> <br /> If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:<br /> <br /> &lt;pre&gt;<br /> rm -rf /home/user/.config/syncevolution<br /> &lt;/pre&gt;<br /> <br /> === NextCloud synchronizing ===<br /> <br /> We will be synchronizing the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend. <br /> For contacts, we will synchronize '''evolution-contacts''' using '''carddav'''.<br /> <br /> A few URLs are required, first, the '''main Nextcloud DAV url''', this will appear like:<br /> <br /> &lt;pre&gt;https://my.nextcloud.org/remote.php/dav&lt;/pre&gt;<br /> <br /> then there is the '''url for a specific calendar''', this is called the &quot;Private Link&quot; and you can get it by clicking &quot;Copy Private Link&quot; for a given calendar in Nextcloud, this might look like so:<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/calendars/userhere/calendarnamehere/<br /> &lt;/pre&gt;<br /> <br /> Finally, for your address book (contacts) synchronization, the '''contacts URL''' is needed (in Nextcloud, go to contacts, settings, &quot;Copy Link&quot; for your contacts):<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/addressbooks/users/userhere/contacts/<br /> &lt;/pre&gt;<br /> <br /> Given the above, a setup to synchronize calendar, tasks, notes and contacts could look like this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --configure \<br /> --template webdav \<br /> username=NEXTCLOUD-USER-HERE \<br /> password=NEXTCLOUD-PASS-HERE \<br /> syncURL=MAIN-DAV-URL-HERE \<br /> target-config@nextcloud<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavtodo \<br /> target-config@nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavjournal \<br /> target-config@nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldav \<br /> target-config@nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CONTACTS-URL-HERE \<br /> backend=carddav \<br /> target-config@nextcloud contacts<br /> <br /> <br /> <br /> syncevolution --configure \<br /> --template SyncEvolution_Client \<br /> sync=none \<br /> syncURL=local://@nextcloud \<br /> username= \<br /> password= \<br /> nextcloud<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-tasks \<br /> database= \<br /> nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-notes\<br /> database= \<br /> nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-events \<br /> database= \<br /> nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=evolution-contacts \<br /> nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> All of the above is configuration that only needs to be done once.<br /> <br /> Depending on your exact situation, your initial synchronisation could only use only values from your phone, from your nextcloud, or both. If you want to merge both, my understanding is that the '''slow''' method achieves this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --sync slow nextcloud nextcloudjournal<br /> syncevolution --sync slow nextcloud nextcloudtodo<br /> syncevolution --sync slow nextcloud nextcloudcal<br /> syncevolution --sync slow nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> Use the '''two-way''' synchronization method for '''normal synchronization''' (daily, hourly, etc synchronizations), like so: <br /> <br /> &lt;pre&gt;<br /> syncevolution --sync two-way nextcloud nextcloudjournal<br /> syncevolution --sync two-way nextcloud nextcloudtodo<br /> syncevolution --sync two-way nextcloud nextcloudcal<br /> syncevolution --sync two-way nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> ==== Warning: TLS Chain validation issues ====<br /> <br /> If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''<br /> <br /> == Radicale synchronising ==<br /> <br /> Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:<br /> <br /> # The main DAV url is simple the URL to your radicale server (without the .web part)<br /> # The calendar URL is simply the http(s) URL to the calendar that you want to synchronize<br /> # The contacts URL is simple the http(s) URL of the addressbook that you want to synchronize<br /> <br /> The username (and optional password) are the radicale credentials.<br /> <br /> === Radicale Testing Server ===<br /> <br /> For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.<br /> <br /> &lt;pre&gt;<br /> mkdir -p ~/radicale<br /> cd ~/radicale<br /> python3 -m radicale --config &quot;&quot; --storage-filesystem-folder `pwd` -H localhost:5223 --logging-level info<br /> &lt;/pre&gt;<br /> <br /> Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)<br /> <br /> = Files synchronization =<br /> <br /> TODO<br /> <br /> = Known Issues =<br /> <br /> * Synchronizing calendar to radicale gives errors if there are unnamed calendar events.<br /> * Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.</div>

BuZz https://leste.maemo.org/index.php?title=Sync&diff=1400 2022-10-10T00:34:10Z

<p>BuZz: </p> <hr /> <div>= Synchronization =<br /> <br /> This page explains and suggests various ways of synchronizing contacts, calendars and files.<br /> <br /> == Calendar, Notes, Tasks and Contacts ==<br /> <br /> Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).<br /> <br /> === Synchronizing with syncevolution CalDav + CardDav ===<br /> <br /> If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:<br /> <br /> &lt;pre&gt;<br /> rm -rf /home/user/.config/syncevolution<br /> &lt;/pre&gt;<br /> <br /> ==== NextCloud synchronizing ====<br /> <br /> We will be synchronizing the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend. <br /> For contacts, we will synchronize '''evolution-contacts''' using '''carddav'''.<br /> <br /> A few URLs are required, first, the '''main Nextcloud DAV url''', this will appear like:<br /> <br /> &lt;pre&gt;https://my.nextcloud.org/remote.php/dav&lt;/pre&gt;<br /> <br /> then there is the '''url for a specific calendar''', this is called the &quot;Private Link&quot; and you can get it by clicking &quot;Copy Private Link&quot; for a given calendar in Nextcloud, this might look like so:<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/calendars/userhere/calendarnamehere/<br /> &lt;/pre&gt;<br /> <br /> Finally, for your address book (contacts) synchronization, the '''contacts URL''' is needed (in Nextcloud, go to contacts, settings, &quot;Copy Link&quot; for your contacts):<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/addressbooks/users/userhere/contacts/<br /> &lt;/pre&gt;<br /> <br /> Given the above, a setup to synchronize calendar, tasks, notes and contacts could look like this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --configure \<br /> --template webdav \<br /> username=NEXTCLOUD-USER-HERE \<br /> password=NEXTCLOUD-PASS-HERE \<br /> syncURL=MAIN-DAV-URL-HERE \<br /> target-config@nextcloud<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavtodo \<br /> target-config@nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavjournal \<br /> target-config@nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldav \<br /> target-config@nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CONTACTS-URL-HERE \<br /> backend=carddav \<br /> target-config@nextcloud contacts<br /> <br /> <br /> <br /> syncevolution --configure \<br /> --template SyncEvolution_Client \<br /> sync=none \<br /> syncURL=local://@nextcloud \<br /> username= \<br /> password= \<br /> nextcloud<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-tasks \<br /> database= \<br /> nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-notes\<br /> database= \<br /> nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-events \<br /> database= \<br /> nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=evolution-contacts \<br /> nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> All of the above is configuration that only needs to be done once.<br /> <br /> Depending on your exact situation, your initial synchronisation could only use only values from your phone, from your nextcloud, or both. If you want to merge both, my understanding is that the '''slow''' method achieves this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --sync slow nextcloud nextcloudjournal<br /> syncevolution --sync slow nextcloud nextcloudtodo<br /> syncevolution --sync slow nextcloud nextcloudcal<br /> syncevolution --sync slow nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> Use the '''two-way''' synchronization method for '''normal synchronization''' (daily, hourly, etc synchronizations), like so: <br /> <br /> &lt;pre&gt;<br /> syncevolution --sync two-way nextcloud nextcloudjournal<br /> syncevolution --sync two-way nextcloud nextcloudtodo<br /> syncevolution --sync two-way nextcloud nextcloudcal<br /> syncevolution --sync two-way nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> ===== Warning: TLS Chain validation issues =====<br /> <br /> If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''<br /> <br /> === Radicale synchronising ===<br /> <br /> Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:<br /> <br /> # The main DAV url is simple the URL to your radicale server (without the .web part)<br /> # The calendar URL is simply the http(s) URL to the calendar that you want to synchronize<br /> # The contacts URL is simple the http(s) URL of the addressbook that you want to synchronize<br /> <br /> The username (and optional password) are the radicale credentials.<br /> <br /> ==== Radicale Testing Server ====<br /> <br /> For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.<br /> <br /> &lt;pre&gt;<br /> mkdir -p ~/radicale<br /> cd ~/radicale<br /> python3 -m radicale --config &quot;&quot; --storage-filesystem-folder `pwd` -H localhost:5223 --logging-level info<br /> &lt;/pre&gt;<br /> <br /> Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)<br /> <br /> == Files synchronization ==<br /> <br /> TODO<br /> <br /> == Known Issues ==<br /> <br /> * Synchronizing calendar to radicale gives errors if there are unnamed calendar events.<br /> * Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.</div>

BuZz https://leste.maemo.org/index.php?title=Sync&diff=1399 2022-10-10T00:26:34Z

<p>BuZz: </p> <hr /> <div>= Synchronization =<br /> <br /> This page explains and suggests various ways of synchronizing contacts, calendars and files.<br /> <br /> == Calendar, Notes, Tasks and Contacts ==<br /> <br /> Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).<br /> <br /> === Synchronizing with syncevolution CalDav + CardDav ===<br /> <br /> If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:<br /> <br /> &lt;pre&gt;<br /> rm -rf /home/user/.config/syncevolution<br /> &lt;/pre&gt;<br /> <br /> ==== NextCloud synchronizing ====<br /> <br /> We will be synchronizing the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend. <br /> For contacts, we will synchronize '''evolution-contacts''' using '''carddav'''.<br /> <br /> A few URLs are required, first, the '''main Nextcloud DAV url''', this will appear like:<br /> <br /> &lt;pre&gt;https://my.nextcloud.org/remote.php/dav&lt;/pre&gt;<br /> <br /> then there is the '''url for a specific calendar''', this is called the &quot;Private Link&quot; and you can get it by clicking &quot;Copy Private Link&quot; for a given calendar in Nextcloud, this might look like so:<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/calendars/userhere/calendarnamehere/<br /> &lt;/pre&gt;<br /> <br /> Finally, for your address book (contacts) synchronization, the '''contacts URL''' is needed (in Nextcloud, go to contacts, settings, &quot;Copy Link&quot; for your contacts):<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/addressbooks/users/userhere/contacts/<br /> &lt;/pre&gt;<br /> <br /> Given the above, a setup to synchronize calendar, tasks, notes and contacts could look like this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --configure \<br /> --template webdav \<br /> username=NEXTCLOUD-USER-HERE \<br /> password=NEXTCLOUD-PASS-HERE \<br /> syncURL=MAIN-DAV-URL-HERE \<br /> target-config@nextcloud<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavtodo \<br /> target-config@nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavjournal \<br /> target-config@nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldav \<br /> target-config@nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CONTACTS-URL-HERE \<br /> backend=carddav \<br /> target-config@nextcloud contacts<br /> <br /> <br /> <br /> syncevolution --configure \<br /> --template SyncEvolution_Client \<br /> sync=none \<br /> syncURL=local://@nextcloud \<br /> username= \<br /> password= \<br /> nextcloud<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-tasks \<br /> database= \<br /> nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-notes\<br /> database= \<br /> nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-events \<br /> database= \<br /> nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=evolution-contacts \<br /> nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> All of the above is configuration that only needs to be done once.<br /> <br /> Depending on your exact situation, your initial synchronisation could only use only values from your phone, from your nextcloud, or both. If you want to merge both, my understanding is that the '''slow''' method achieves this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --sync slow nextcloud nextcloudjournal<br /> syncevolution --sync slow nextcloud nextcloudtodo<br /> syncevolution --sync slow nextcloud nextcloudcal<br /> syncevolution --sync slow nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> Use the '''two-way''' synchronization method for '''normal synchronization''' (daily, hourly, etc synchronizations), like so: <br /> <br /> &lt;pre&gt;<br /> syncevolution --sync two-way nextcloud nextcloudjournal<br /> syncevolution --sync two-way nextcloud nextcloudtodo<br /> syncevolution --sync two-way nextcloud nextcloudcal<br /> syncevolution --sync two-way nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> ===== Warning: TLS Chain validation issues =====<br /> <br /> If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''<br /> <br /> ==== Radicale synchronising ====<br /> <br /> Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:<br /> <br /> # The main DAV url is simple the URL to your radicale server (without the .web part)<br /> # The calendar URL is simply the http(s) URL to the calendar that you want to synchronize<br /> # The contacts URL is simple the http(s) URL of the addressbook that you want to synchronize<br /> <br /> The username (and optional password) are the radicale credentials.<br /> <br /> ===== Radicale Testing Server =====<br /> <br /> For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.<br /> <br /> &lt;pre&gt;<br /> mkdir -p ~/radicale<br /> cd ~/radicale<br /> python3 -m radicale --config &quot;&quot; --storage-filesystem-folder `pwd` -H localhost:5223 --logging-level info<br /> &lt;/pre&gt;<br /> <br /> Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)<br /> <br /> == Files synchronization ==<br /> <br /> TODO</div>

BuZz https://leste.maemo.org/index.php?title=Sync&diff=1398 2022-10-10T00:24:21Z

<p>BuZz: </p> <hr /> <div>= Synchronisation =<br /> <br /> This page explains and suggests various ways of synchronising contacts, calendars and files.<br /> <br /> == Calendar, Notes, Tasks and Contacts ==<br /> <br /> Synchronising calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronisation tasks is available in the repository (Syncevolution Frontend).<br /> <br /> === Synchronising with syncevolution CalDav + CardDav ===<br /> <br /> If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:<br /> <br /> &lt;pre&gt;<br /> rm -rf /home/user/.config/syncevolution<br /> &lt;/pre&gt;<br /> <br /> ==== NextCloud synchronizing ====<br /> <br /> We will be synchronising the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend. For contacts, we will synchronise '''evolution-contacts''' using '''carddav'''.<br /> <br /> A few URLs are required, first, the '''main Nextcloud DAV url''', this seems to be of the form:<br /> <br /> &lt;pre&gt;https://my.nextcloud.org/remote.php/dav&lt;/pre&gt;<br /> <br /> then there is the '''url for a specific calendar''', this is called the &quot;Private Link&quot; and you can get it by clicking &quot;Copy Private Link&quot; for a given calendar in Nextcloud, this might look like so:<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/calendars/userhere/calendarnamehere/<br /> &lt;/pre&gt;<br /> <br /> Finally, for your address book (contacts) synchronization, the '''contacts URL''' is needed (in Nextcloud, go to contacts, settings, &quot;Copy Link&quot; for your contacts):<br /> <br /> &lt;pre&gt;<br /> https://my.nextcloud.org/remote.php/dav/addressbooks/users/userhere/contacts/<br /> &lt;/pre&gt;<br /> <br /> Given the above, a setup to synchronize calendar, tasks, notes and contacts could look like this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --configure \<br /> --template webdav \<br /> username=NEXTCLOUD-USER-HERE \<br /> password=NEXTCLOUD-PASS-HERE \<br /> syncURL=MAIN-DAV-URL-HERE \<br /> target-config@nextcloud<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavtodo \<br /> target-config@nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldavjournal \<br /> target-config@nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CALENDAR-URL-HERE \<br /> backend=caldav \<br /> target-config@nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> --template webdav \<br /> database=CONTACTS-URL-HERE \<br /> backend=carddav \<br /> target-config@nextcloud contacts<br /> <br /> <br /> <br /> syncevolution --configure \<br /> --template SyncEvolution_Client \<br /> sync=none \<br /> syncURL=local://@nextcloud \<br /> username= \<br /> password= \<br /> nextcloud<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-tasks \<br /> database= \<br /> nextcloud nextcloudtodo<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-notes\<br /> database= \<br /> nextcloud nextcloudjournal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=maemo-events \<br /> database= \<br /> nextcloud nextcloudcal<br /> <br /> syncevolution --configure \<br /> sync=two-way \<br /> backend=evolution-contacts \<br /> nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> All of the above is configuration that only needs to be done once.<br /> <br /> Depending on your exact situation, your initial synchronisation could only use only values from your phone, from your nextcloud, or both. If you want to merge both, my understanding is that the '''slow''' method achieves this:<br /> <br /> &lt;pre&gt;<br /> syncevolution --sync slow nextcloud nextcloudjournal<br /> syncevolution --sync slow nextcloud nextcloudtodo<br /> syncevolution --sync slow nextcloud nextcloudcal<br /> syncevolution --sync slow nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> Use the '''two-way''' synchronization method for '''normal synchronization''' (daily, hourly, etc synchronizations), like so: <br /> <br /> &lt;pre&gt;<br /> syncevolution --sync two-way nextcloud nextcloudjournal<br /> syncevolution --sync two-way nextcloud nextcloudtodo<br /> syncevolution --sync two-way nextcloud nextcloudcal<br /> syncevolution --sync two-way nextcloud contacts<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> ===== Warning: TLS Chain validation issues =====<br /> <br /> If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''<br /> <br /> ==== Radicale synchronising ====<br /> <br /> Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:<br /> <br /> # The main DAV url is simple the URL to your radicale server (without the .web part)<br /> # The calendar URL is simply the http(s) URL to the calendar that you want to synchronize<br /> # The contacts URL is simple the http(s) URL of the addressbook that you want to synchronize<br /> <br /> The username (and optional password) are the radicale credentials.<br /> <br /> ===== Radicale Testing Server =====<br /> <br /> For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.<br /> <br /> &lt;pre&gt;<br /> mkdir -p ~/radicale<br /> cd ~/radicale<br /> python3 -m radicale --config &quot;&quot; --storage-filesystem-folder `pwd` -H localhost:5223 --logging-level info<br /> &lt;/pre&gt;<br /> <br /> Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)<br /> <br /> == Files synchronization ==<br /> <br /> TODO</div>

BuZz https://leste.maemo.org/index.php?title=Packaging&diff=1397 2022-10-09T23:33:07Z

<p>BuZz: </p> <hr /> <div>The packages we build for Maemo Leste are hosted on Github: https://github.com/maemo-leste<br /> <br /> We use the Jenkins CI https://phoenix.maemo.org along with helper scripts that can be found at https://github.com/maemo-leste/jenkins-integration<br /> The base logic of buildng Debian packages in Jenkins comes from https://jenkins-debian-glue.org<br /> <br /> = Workflow =<br /> <br /> Our workflow consists of having the packages in Git, along with respective branches.<br /> The master branch in git should represent the latest development. When the sources are ready, we create a new branch called &quot;maemo/ascii&quot;, which represents the Devuan suite we base it on.<br /> <br /> Being git-based, our packages require the gbp.conf file inside the debian directory.<br /> <br /> All of our packages contain the exact same gbp.conf, which is the following:<br /> <br /> &lt;pre&gt;<br /> [DEFAULT]<br /> upstream-tag=%(version)s<br /> &lt;/pre&gt;<br /> <br /> This file is used by gbp, which in turn is used by jenkins-debian-glue.<br /> <br /> The rest is standard Debian packaging.<br /> <br /> = Initial packaging =<br /> <br /> TODO<br /> <br /> = Updating a package =<br /> <br /> TODO<br /> <br /> = Links =<br /> <br /> * https://wiki.maemo.org/Packaging<br /> * https://wiki.maemo.org/Extras-testing/Command_line_applications<br /> * https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_a_new_maemo_application#Adding_application_to_menu</div>

BuZz https://leste.maemo.org/index.php?title=Promotion&diff=1389 2022-10-05T13:41:12Z

<p>BuZz: /* Ideas */</p> <hr /> <div>== What ==<br /> <br /> For the upcoming openfest, i had the idea of recording a bunch of videodemos of Leste currentstate on Droid 4, with some show-off stuff.<br /> <br /> == HW == <br /> <br /> I'm using a simple mjpeg HDMI capture unit.<br /> <br /> * just search 'hdmi capture usb' on ali express, one of the units with two HDMI ports, so i can loop it through to a monitor<br /> * https://www.allekabels.nl/computerkabels/4566/1097219/hdmi-naar-hdmi-mini-kabel.html <br /> <br /> There's some confusion about how to setup xrandr, so i'll be looking into that aswell.<br /> <br /> == Ideas ==<br /> <br /> * tasknav view of a youtube video playing + a 3D game<br /> * youtube background playback<br /> * true multitasking<br /> * how well chromium/chrome works!<br /> * sfone frontends<br /> * conversations<br /> * app manager<br /> <br /> <br /> * openlara , devilutionX , GZdoom , pcsx-rearmed , dethrace<br /> * install some devuan/debian upstream program<br /> <br /> <br /> * blender?<br /> * gimp<br /> * puredata with GEM (and gl4es?)<br /> <br /> <br /> <br /> * please add your ideas of stuff that people should see!</div>

BuZz https://leste.maemo.org/index.php?title=Promotion&diff=1388 2022-10-05T13:39:38Z

<p>BuZz: Created page with &quot;== What == For the upcoming openfest, i had the idea of recording a bunch of videodemos of Leste currentstate on Droid 4, with some show-off stuff. == HW == I&#039;m using a si...&quot;</p> <hr /> <div>== What ==<br /> <br /> For the upcoming openfest, i had the idea of recording a bunch of videodemos of Leste currentstate on Droid 4, with some show-off stuff.<br /> <br /> == HW == <br /> <br /> I'm using a simple mjpeg HDMI capture unit.<br /> <br /> * just search 'hdmi capture usb' on ali express, one of the units with two HDMI ports, so i can loop it through to a monitor<br /> * https://www.allekabels.nl/computerkabels/4566/1097219/hdmi-naar-hdmi-mini-kabel.html <br /> <br /> There's some confusion about how to setup xrandr, so i'll be looking into that aswell.<br /> <br /> == Ideas ==<br /> <br /> * tasknav view of a youtube video playing + a 3D game<br /> * youtube background playback<br /> * true multitasking<br /> * install some devuan/debian upstream program<br /> * openlara , devilutionX , GZdoom , pcsx-rearmed , dethrace<br /> * how well chromium/chrome works!<br /> * sfone frontends<br /> * conversations<br /> * app manager<br /> <br /> * please add your ideas of stuff that people should see!</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1387 2022-09-29T11:28:13Z

<p>BuZz: </p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple offline dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How to obtain dictionaries ==<br /> <br /> For usage, you can grab any stardict dictionary and unpack them in MyDocs/mstardict/.<br /> There are many sources to grab such dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries.<br /> <br /> == How to use it ==<br /> <br /> Launch the program, make sure to enable a dictionary and just type a query.<br /> <br /> For text to speech, the program has two options. The first uses plain espeak built-in TTS and a gender selection for reading out the entrynames. The second is called 'Real People' in the program and requires <br /> WyabdcRealPeopleTTS.tar.bz2 and/or OtdRealPeopleTTS.tar.bz2. I'm not sure how the second option is supposed to work. For the espeak one no added files are needed.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> MStarDict_Preferences.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'dictconv' to convert em back and forth. And there's even some dictionaries! 'stardict-english-czech' and 'stardict-german-czech'. You'll have to copy those dictionaries after installing to MyDocs/mstardict/ yourself.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1386 2022-09-29T11:25:27Z

<p>BuZz: /* How to use it */</p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple offline dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How to obtain dictionaries ==<br /> <br /> For usage, you can grab any stardict dictionary and unpack them in MyDocs/mstardict/.<br /> There are many sources to grab such dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries.<br /> <br /> == How to use it ==<br /> <br /> Launch the program, make sure to enable a dictionary and just type a query.<br /> <br /> For text to speech, the program has two options. The first uses plain espeak built-in TTS and a gender selection for reading out the entrynames. The second is called 'Real People' in the program and requires <br /> WyabdcRealPeopleTTS.tar.bz2 and/or OtdRealPeopleTTS.tar.bz2. I'm not sure how the second option is supposed to work. For the espeak one no added files are needed.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> MStarDict_Preferences.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'dictconv' to convert em back and forth. And there's even some dictionaries! 'stardict-english-czech' and 'stardict-german-czech'. You'll have to copy those dictionaries after installing to MyDocs/mstardict/ yourself.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1385 2022-09-29T11:10:09Z

<p>BuZz: </p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple offline dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How to obtain dictionaries ==<br /> <br /> For usage, you can grab any stardict dictionary and unpack them in MyDocs/mstardict/.<br /> There are many sources to grab such dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries.<br /> <br /> == How to use it ==<br /> <br /> Launch the program, make sure to enable a dictionary and just type a query.<br /> <br /> For text to speech, the program has two options. The first uses plain espeak TTS and a gender selection for reading out the entrynames. The second is called 'Real People' in the program and requires <br /> WyabdcRealPeopleTTS.tar.bz2 and/or OtdRealPeopleTTS.tar.bz2. I'm not sure how the second option is supposed to work.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> MStarDict_Preferences.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'dictconv' to convert em back and forth. And there's even some dictionaries! 'stardict-english-czech' and 'stardict-german-czech'. You'll have to copy those dictionaries after installing to MyDocs/mstardict/ yourself.</div>

BuZz https://leste.maemo.org/index.php?title=File:MStarDict_Preferences.png&diff=1384 2022-09-29T11:07:26Z

<p>BuZz: </p> <hr /> <div></div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1383 2022-09-29T11:03:41Z

<p>BuZz: </p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple offline dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How to obtain dictionaries ==<br /> <br /> For usage, you can grab any stardict dictionary and unpack them in MyDocs/mstardict/.<br /> There are many sources to grab such dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries.<br /> <br /> == How to use it ==<br /> <br /> Launch the program, make sure to enable a dictionary and just type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'dictconv' to convert em back and forth. And there's even some dictionaries! 'stardict-english-czech' and 'stardict-german-czech'. You'll have to copy those dictionaries after installing to MyDocs/mstardict/ yourself.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1381 2022-09-29T10:59:56Z

<p>BuZz: /* How to obtain dictionaries */</p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How to obtain dictionaries ==<br /> <br /> For usage, you can grab any stardict dictionary and unpack them in MyDocs/mstardict/.<br /> There are many sources to grab such dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries.<br /> <br /> == How to use it ==<br /> <br /> Launch the program, make sure to enable a dictionary and just type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'distconv' to convert em back and forth.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1379 2022-09-29T10:57:35Z

<p>BuZz: /* How do i use it */</p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How do i use it ==<br /> <br /> For usage, you can grab any stardict dictionary and place them in MyDocs/mstardict/.<br /> There are many sources to grab dictionaries from, buZz setup a mirror thats linked below for a big pile of free dictionaries. <br /> <br /> Then launch the program, make sure to enable the dictionary you just copied and type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'distconv' to convert em back and forth.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1378 2022-09-29T10:55:29Z

<p>BuZz: </p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How do i use it ==<br /> <br /> For usage, you can grab any stardict dictionary and place them in MyDocs/mstardict/<br /> <br /> Then launch the program, make sure to enable the dictionary you just copied and type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'distconv' to convert em back and forth.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1377 2022-09-29T06:45:23Z

<p>BuZz: /* How do i use it */</p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |devices=[[Nokia_N900]],[[Motorola_Droid_4]]<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How do i use it ==<br /> <br /> For usage, you can grab any stardict dictionary and place them in MyDocs/mstardict/<br /> <br /> Then launch the program, make sure to enable the dictionary you just copied and type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'distconv' to convert em back and forth.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1376 2022-09-29T06:22:49Z

<p>BuZz: </p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |devices=[[Nokia_N900]],[[Motorola_Droid_4]]<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> == What is this. ==<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2. It allows you to use stardict compatible dictionaries and reference books, of which many can be found.<br /> <br /> The original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> == How do i use it ==<br /> <br /> For usage, you can grab any stardict dictionary and place them in MyDocs/mstardict/<br /> <br /> Then launch the program, and type a query.<br /> <br /> There's also espeak (and a different one thats just &gt;20000 .wav files??) TTS for reading out the entrynames.<br /> <br /> == Some pictures ==<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;<br /> <br /> == Other links ==<br /> <br /> * https://stardict-4.sourceforge.net/index_en.php<br /> * http://space.nurdspace.nl/~buzz/maemo/stardict-dic/<br /> * https://web.archive.org/web/20170620212527/http://www.stardict.org/<br /> <br /> == Also ==<br /> <br /> Devuan has 'qstardict', 'goldendict' and 'sdcv' in its repos which all support the same dictionary files as input. Also there is 'distconv' to convert em back and forth.</div>

BuZz https://leste.maemo.org/index.php?title=Extras/MStarDict&diff=1375 2022-09-29T06:13:10Z

<p>BuZz: Created page with &quot;{{Infobox Package |image=250px |status=Working |devices=Nokia_N900,Motorola_Droid_4 |date_in_repo=2022-09-16 |website=https://...&quot;</p> <hr /> <div>{{Infobox Package<br /> |image=[[Image:MStarDict_SelectDictionary.png|250px]]<br /> |status=Working<br /> |devices=[[Nokia_N900]],[[Motorola_Droid_4]]<br /> |date_in_repo=2022-09-16<br /> |website=https://github.com/norayr/mstardict<br /> |maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict<br /> |category=Utilities<br /> |packager=[[User:Norayr]]<br /> }}<br /> <br /> MStarDict is a simple dictionary based on code of StarDict written in C++ using Gtk2.<br /> <br /> Original announce thread from 2010 is on https://talk.maemo.org/showthread.php?t=44979<br /> <br /> For usage, you can grab any stardict dictionary and place them in MyDocs/mstardict/<br /> <br /> &lt;gallery&gt;<br /> MStarDict_SelectDictionary.png<br /> MStarDict_Itemview.png<br /> &lt;/gallery&gt;</div>

BuZz https://leste.maemo.org/index.php?title=File:MStarDict_Itemview.png&diff=1374 2022-09-29T06:12:27Z

<p>BuZz: </p> <hr /> <div></div>

BuZz https://leste.maemo.org/index.php?title=File:MStarDict_SelectDictionary.png&diff=1373 2022-09-29T06:11:22Z

<p>BuZz: </p> <hr /> <div></div>

BuZz https://leste.maemo.org/index.php?title=User:BuZz/Opinions&diff=1293 2022-05-19T13:54:57Z

<p>BuZz: /* My dataconnection issues */</p> <hr /> <div>== virtual keyboard ==<br /> <br /> (while using a pinephone) Why do we have to blur the rest of screen in portrait? Maybe we can keep it unblurred there, resize main window and keep keyboard window open while using? <br /> <br /> == QTWebBrowser ==<br /> <br /> I reaaaally want to be able to zoom -out- from 100% , not just in. <br /> * https://github.com/qtproject/qt-apps-qtwebbrowser<br /> <br /> == My dataconnection issues ==<br /> <br /> (on a droid4 running latest -devel) <br /> <br /> Every time i restart icd2 , i see my datasim connection once. I can tap it, and it will connect but not according to UI , i need to press 'No' on the popup for retry, and execute udhcpc -i wwan3 myself. Then its stable for -ages-. <br /> <br /> Opening application manager breaks the connection.<br /> <br /> Also reopening icd2 'internet connections' breaks the connection. (from statusbar, not from settings app)</div>

BuZz https://leste.maemo.org/index.php?title=User:BuZz&diff=1292 2022-05-19T13:50:53Z

<p>BuZz: </p> <hr /> <div>hi, i'm a founding [https://nurdspace.nl NURDspace] member.<br /> <br /> Been messing with maemo a bit on my collection of OMAP devices (770,n800,n810,n900) never really used it as daily driver. Also been using devuan since inception.<br /> <br /> Also bunch of other stuff, i guess.<br /> <br /> Since leste exists i've been messing around with it on a droid4 , been carrying it as daily driver since early 2022 now.<br /> <br /> <br /> Careful, i got [[User:BuZz/Opinions|opinions]]</div>

BuZz https://leste.maemo.org/index.php?title=User:BuZz/Opinions&diff=1291 2022-05-19T13:50:18Z

<p>BuZz: Created page with &quot;== virtual keyboard == (while using a pinephone) Why do we have to blur the rest of screen in portrait? Maybe we can keep it unblurred there, resize main window and keep keyb...&quot;</p> <hr /> <div>== virtual keyboard ==<br /> <br /> (while using a pinephone) Why do we have to blur the rest of screen in portrait? Maybe we can keep it unblurred there, resize main window and keep keyboard window open while using? <br /> <br /> == QTWebBrowser ==<br /> <br /> I reaaaally want to be able to zoom -out- from 100% , not just in. <br /> * https://github.com/qtproject/qt-apps-qtwebbrowser<br /> <br /> == My dataconnection issues ==<br /> <br /> Every time i restart icd2 , i see my datasim connection once. I can tap it, and it will connect but not according to UI , i need to press 'No' on the popup for retry, and execute udhcpc -i wwan3 myself. Then its stable for -ages-. <br /> <br /> Opening application manager breaks the connection.<br /> <br /> Also reopening icd2 'internet connections' breaks the connection. (from statusbar, not from settings app)</div>

BuZz https://leste.maemo.org/index.php?title=User:BuZz&diff=1290 2022-05-19T13:45:56Z

<p>BuZz: Created page with &quot;hi, i&#039;m a founding [https://nurdspace.nl NURDspace] member. Been messing with maemo a bit on my collection of OMAP devices (770,n800,n810,n900) never really used it as daily...&quot;</p> <hr /> <div>hi, i'm a founding [https://nurdspace.nl NURDspace] member.<br /> <br /> Been messing with maemo a bit on my collection of OMAP devices (770,n800,n810,n900) never really used it as daily driver. Also been using devuan since inception.<br /> <br /> Also bunch of other stuff, i guess.<br /> <br /> Since leste exists i've been messing around with it on a droid4 , been carrying it as daily driver since early 2022 now.</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1286 2022-05-04T21:20:20Z

<p>BuZz: /* Torch */</p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati XT894<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.15.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> <br /> The keyboard layout is extended to provide more standard keys.<br /> [[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]<br /> Key mapping can be tested with the 'xev' program.<br /> <br /> It may be necessary to run the follow commands as root in order to get the OK key to function correctly (see [https://github.com/maemo-leste/bugtracker/issues/510#issuecomment-815618591 here]):<br /> udevadm hwdb --update<br /> udevadm trigger<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Using a battery without temperature sensor ====<br /> <br /> Modprobe the pmic driver as follows:<br /> &lt;pre&gt;<br /> cpcap-battery ignore_temperature_probe=1<br /> &lt;/pre&gt;<br /> <br /> ==== Flashing the boot logo ====<br /> <br /> More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO<br /> <br /> &lt;pre&gt;<br /> 15:04 &lt; tmlind&gt; Wizzup: i think the logo on droid4 can be flashed with fastboot flash logo logo.bin or something, can also be just written to logo partition from m-l<br /> [snip]<br /> 09:24 &lt; xsetiadi&gt; https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin<br /> 09:25 &lt; xsetiadi&gt; becarefull, you can bootloop droid4 if you wrong flash partition<br /> 09:26 &lt; xsetiadi&gt; like i do last year<br /> 09:26 &lt; xsetiadi&gt; instead of flashing using command: fastboot flash logo.bin logo.bin i just flash it with command: fastboot flash logo logo.bin<br /> &lt;/pre&gt;<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> sudo modprobe hci_uart<br /> pactl load-module module-bluetooth-discover<br /> blueman-manager<br /> <br /> Pair &amp; trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br /> <br /> ==== Torch ====<br /> <br /> The Droid 4 has a TI LM3559 flash torch controller. This provides flash functionality when taking pictures, usage as a torch, and provides privacy indication (in this mode, the LED flashes in a fast heartbeat pattern). A driver for it exists in mainline, but it requires some DTS work, since it is tied to a camera device. <br /> <br /> If you want to use it in the meantime, direct i2c access can be used as follows (since this is direct access, be careful about each of the commands below):<br /> <br /> &lt;source&gt;<br /> ##Install the prerequisites<br /> $ sudo apt install i2c-tools<br /> <br /> ## Turn LED on in torch mode<br /> $ sudo i2cset -y 2 0x53 0x10 0x1a<br /> <br /> ## Turn LED on in privacy indication mode<br /> $ sudo i2cset -y 2 0x53 0x10 0x19<br /> <br /> ## Turn LED off (in any mode)<br /> $ sudo i2cset -y 2 0x53 0x10 0x18<br /> <br /> ## Use LED for doing a hella bright flash for some time once and then turn off<br /> $ sudo i2cset -y 2 0x53 0x10 0x1b<br /> <br /> &lt;/source&gt;<br /> <br /> == Using a configured Leste sdcard in a different Droid4 ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate. <br /> If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.<br /> apt reinstall firmware-ti-connectivity <br /> If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device<br /> apt download firmware-ti-connectivity<br /> Then copy the .deb to your new device and install that (as root) with<br /> dpkg -i firmware-ti-connectivity_[version]_all.deb <br /> Then (as root) re-calibrate the wifi chip by running<br /> /usr/bin/maserati-calibrate<br /> Then reboot.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> Droid4_Daimonin_Hdmi.jpg<br /> &lt;/gallery&gt;<br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Development&diff=1284 2022-04-28T19:35:13Z

<p>BuZz: /* Developing on a device */</p> <hr /> <div>Maemo Leste development is split up in a few different places.<br /> <br /> == Communication and organising ==<br /> <br /> * Our https://maemo-leste.github.io website is where we post (news) updates, as well as on talk.maemo.org (see this subforum https://talk.maemo.org/forumdisplay.php?f=66 and this maemo.org thread: https://talk.maemo.org/showthread.php?t=100192)<br /> * There is the issue tracker; for filing bugs and keeping track of issues/milestones. https://github.com/maemo-leste/bugtracker<br /> * The day-to-day development and user chatter mostly takes place in the [[IRC channel]]<br /> * We also have a mailing list, at [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br /> * This wiki: for documenting the status of various long-running projects, status per device, etc.<br /> <br /> == Task Summary ==<br /> <br /> For current (semi) impactful tasks, see<br /> <br /> [[Development/Tasks]]<br /> <br /> == Codename ==<br /> <br /> * Maemo Leste is currently based on Devuan Beowulf, which is based on Debian Buster.<br /> <br /> == Guides ==<br /> <br /> * [[Development/Porting Packages]]<br /> * [[Development/Building Packages]]<br /> * [[Development/Modified Software]]<br /> * [[Development/Device Bringup]]<br /> * https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide<br /> <br /> == Technical ==<br /> <br /> <br /> All our git repositories can be found here: https://github.com/maemo-leste<br /> <br /> === Jenkins ===<br /> <br /> To aid development and provide &quot;continous integration&quot; we have a build server, which takes a git repository and builds software and packages it, and will automatically make said package end up in Maemo Leste repositories. This is done by Jenkins, and the instance can be found here: https://phoenix.maemo.org/<br /> <br /> === Developing on a device ===<br /> <br /> All development software and tests end up in 'beowulf-devel' apt source. For enabling this edit '/etc/apt/sources.list' and add this line: <br /> deb https://maedevu.maemo.org/leste beowulf-devel main contrib non-free droid4<br /> <br /> Actual development is mostly done from within Maemo Leste itself. (For Maemo Fremantle developers, this might sound weird, but there is essentially no need for a 'scratchbox' type VM)<br /> <br /> <br /> The current developers mostly work in a [[Virtual_Machine|Virtual Machine]] or on a [[Raspberry Pi 2|Raspberry Pi]].<br /> <br /> === Building a Maemo Leste image ===<br /> <br /> See https://leste.maemo.org/Image_Builder<br /> <br /> <br /> === List of Programs/Daemon specific to Maemo ===<br /> <br /> https://leste.maemo.org/Development/Daemons<br /> <br /> === Crossbuilding ===<br /> <br /> Multiarch is an ability present on modern Debian systems that allows you to build native packages for different architectures. This is nice because you can build packages for an ARM based phone using the full power of your x86 based PC/Mac/Notebook or a server.<br /> <br /> Here we show how you can easily setup a multiarch environment and build a native package for Maemo Leste running on Nokia N900. We are going to make a container (chroot) for this job. It's because we don't want to pollute our main system.<br /> <br /> # Make a container for our development system<br /> DIR=/var/lib/container/stretch<br /> sudo apt-get install qemu-user-static debootstrap systemd-container &amp;&amp;<br /> sudo debootstrap --arch=armhf stretch $DIR http://deb.debian.org/debian &amp;&amp;<br /> echo &quot;strech_cross&quot; | sudo tee $DIR/etc/debian_chroot &amp;&amp;<br /> sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D $DIR<br /> <br /> # Setup build environment inside the container<br /> cat &gt;&gt; ~/.bashrc &lt;&lt; EOF &amp;&amp;<br /> export PKG_CONFIG_PATH=/usr/lib/pkgconfig<br /> export CC=arm-linux-gnueabihf-gcc<br /> export JOBS=$(grep processor /proc/cpuinfo | wc -l)<br /> EOF<br /> dpkg --add-architecture armhf &amp;&amp;<br /> apt-get -y install --no-install-recommends build-essential crossbuild-essential-armhf ca-certificates &amp;&amp;<br /> cat &gt;&gt; /etc/apt/sources.list &lt;&lt; &quot;EOF&quot; &amp;&amp;<br /> deb http://maedevu.maemo.org/leste ascii main contrib non-free n900<br /> deb http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900<br /> <br /> deb-src http://deb.debian.org/debian stretch main<br /> deb-src http://maedevu.maemo.org/leste ascii main contrib non-free n900<br /> deb-src http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900<br /> EOF<br /> wget --no-check-certificate https://maedevu.maemo.org/testing-key.asc &amp;&amp;<br /> apt-key add testing-key.asc &amp;&amp;<br /> rm -f testing-key.asc &amp;&amp;<br /> rm -f /var/cache/apt/archives/*.deb &amp;&amp;<br /> apt-get update &amp;&amp;<br /> exec bash<br /> <br /> # Build Xorg for Nokia N900<br /> apt-get source xserver-xorg-core &amp;&amp;<br /> cd xorg-server-1.19.2 &amp;&amp;<br /> wget https://raw.githubusercontent.com/buildroot/buildroot/88e0f214dcb7c2a99a4425a70673d2aa5f48d720/package/x11r7/xserver_xorg-server/1.20.4/0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch &amp;&amp;<br /> mv -v 0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch debian/patches &amp;&amp;<br /> echo -e &quot;# crossbuild fix\n0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch&quot; &gt;&gt; debian/patches/series &amp;&amp;<br /> apt-get -y build-dep -a armhf . &amp;&amp;<br /> time dpkg-buildpackage -aarmhf -j$JOBS -b &amp;&amp;<br /> echo OK || echo FAIL<br /> <br /> To login the container later:<br /> sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D /var/lib/container/stretch<br /> <br /> To remove the container:<br /> sudo rm -fr /var/lib/container/stretch<br /> <br /> === Cross-distro solution for development inside an ARM/ARM64 chroot on a PC ===<br /> <br /> It's possible to set up an emulated chroot development environment for ARM on x86/amd64 that will work on almost any Linux distro with just a few simple steps. This will work for systemd-less distros including Devuan and even Maemo Leste on x86/amd64. This guide provides an example for how to set up a generic ARM64 development chroot on a Debian-based distro. This method can similarly be used with images (tarballs) for other devices.<br /> <br /> 1. Install the QEMU full system emulation static binaries and [http://binfmt-support.nongnu.org/ support for foreign binaries]:<br /> <br /> $ sudo apt-get install qemu-user-static binfmt-support<br /> <br /> The installation should register ARM binaries for automatic execution via QEMU. You can verify this with '''update-binfmts''':<br /> <br /> $ sudo update-binfmts --display qemu-arm<br /> qemu-arm (enabled):<br /> package = qemu-user-static<br /> type = magic<br /> offset = 0<br /> magic = \x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00<br /> mask = \xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff<br /> interpreter = /usr/bin/qemu-arm-static<br /> detector =<br /> <br /> 2. Find the [http://maedevu.maemo.org/images/arm64-generic/ latest] Maemo Leste ARM64 tarball and download and extract it:<br /> <br /> $ mkdir leste-arm64<br /> $ cd leste-arm64<br /> $ curl http://maedevu.maemo.org/images/arm64-generic/20190226/maemo-leste-1.0-arm64-generic-20190226.tar.gz | gunzip -c | sudo tar xvf -<br /> <br /> 3. From the same directory, configure the chroot with a few resources from your host system:<br /> <br /> $ sudo mount -t proc proc proc<br /> $ sudo mount -o bind /dev dev<br /> $ sudo mount -o bind /dev/pts dev/pts<br /> <br /> 4. From the same directory, create a symlink for the mount table:<br /> <br /> $ sudo ln -s /proc/mounts etc/mtab<br /> <br /> 5. From the same directory, set the locale, enter the chroot and switch to the unprivileged user:<br /> <br /> $ sudo LC_ALL=C chroot . /bin/su - user<br /> <br /> You'll now be ready to use your Maemo Leste ARM64 development environment:<br /> <br /> $ uname -m<br /> aarch64<br /> <br /> Once you have finished with it, you can exit and unmount the resources you previously mounted:<br /> <br /> $ exit<br /> $ sudo umount dev/pts dev proc<br /> <br /> === Localization ===<br /> <br /> See [[Localization]]<br /> <br /> <br /> === TODO ===<br /> <br /> * Discuss where people look to pick up issues (clear answer is the bugtracker, but still)<br /> * How people can make changes and how to send them in</div>

BuZz https://leste.maemo.org/index.php?title=Development&diff=1283 2022-04-28T15:44:14Z

<p>BuZz: </p> <hr /> <div>Maemo Leste development is split up in a few different places.<br /> <br /> == Communication and organising ==<br /> <br /> * Our https://maemo-leste.github.io website is where we post (news) updates, as well as on talk.maemo.org (see this subforum https://talk.maemo.org/forumdisplay.php?f=66 and this maemo.org thread: https://talk.maemo.org/showthread.php?t=100192)<br /> * There is the issue tracker; for filing bugs and keeping track of issues/milestones. https://github.com/maemo-leste/bugtracker<br /> * The day-to-day development and user chatter mostly takes place in the [[IRC channel]]<br /> * We also have a mailing list, at [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br /> * This wiki: for documenting the status of various long-running projects, status per device, etc.<br /> <br /> == Task Summary ==<br /> <br /> For current (semi) impactful tasks, see<br /> <br /> [[Development/Tasks]]<br /> <br /> == Codename ==<br /> <br /> * Maemo Leste is currently based on Devuan Beowulf, which is based on Debian Buster.<br /> <br /> == Guides ==<br /> <br /> * [[Development/Porting Packages]]<br /> * [[Development/Building Packages]]<br /> * [[Development/Modified Software]]<br /> * [[Development/Device Bringup]]<br /> * https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide<br /> <br /> == Technical ==<br /> <br /> <br /> All our git repositories can be found here: https://github.com/maemo-leste<br /> <br /> === Jenkins ===<br /> <br /> To aid development and provide &quot;continous integration&quot; we have a build server, which takes a git repository and builds software and packages it, and will automatically make said package end up in Maemo Leste repositories. This is done by Jenkins, and the instance can be found here: https://phoenix.maemo.org/<br /> <br /> === Developing on a device ===<br /> <br /> All development software and tests end up in 'beowulf-devel' apt source. For enabling this edit '/etc/apt/sources.list' and change the last line to: <br /> deb https://maedevu.maemo.org/leste beowulf-devel main contrib non-free droid4<br /> <br /> Actual development is mostly done from within Maemo Leste itself. (For Maemo Fremantle developers, this might sound weird, but there is essentially no need for a 'scratchbox' type VM)<br /> <br /> <br /> The current developers mostly work in a [[Virtual_Machine|Virtual Machine]] or on a [[Raspberry Pi 2|Raspberry Pi]].<br /> <br /> === Building a Maemo Leste image ===<br /> <br /> See https://leste.maemo.org/Image_Builder<br /> <br /> <br /> === List of Programs/Daemon specific to Maemo ===<br /> <br /> https://leste.maemo.org/Development/Daemons<br /> <br /> === Crossbuilding ===<br /> <br /> Multiarch is an ability present on modern Debian systems that allows you to build native packages for different architectures. This is nice because you can build packages for an ARM based phone using the full power of your x86 based PC/Mac/Notebook or a server.<br /> <br /> Here we show how you can easily setup a multiarch environment and build a native package for Maemo Leste running on Nokia N900. We are going to make a container (chroot) for this job. It's because we don't want to pollute our main system.<br /> <br /> # Make a container for our development system<br /> DIR=/var/lib/container/stretch<br /> sudo apt-get install qemu-user-static debootstrap systemd-container &amp;&amp;<br /> sudo debootstrap --arch=armhf stretch $DIR http://deb.debian.org/debian &amp;&amp;<br /> echo &quot;strech_cross&quot; | sudo tee $DIR/etc/debian_chroot &amp;&amp;<br /> sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D $DIR<br /> <br /> # Setup build environment inside the container<br /> cat &gt;&gt; ~/.bashrc &lt;&lt; EOF &amp;&amp;<br /> export PKG_CONFIG_PATH=/usr/lib/pkgconfig<br /> export CC=arm-linux-gnueabihf-gcc<br /> export JOBS=$(grep processor /proc/cpuinfo | wc -l)<br /> EOF<br /> dpkg --add-architecture armhf &amp;&amp;<br /> apt-get -y install --no-install-recommends build-essential crossbuild-essential-armhf ca-certificates &amp;&amp;<br /> cat &gt;&gt; /etc/apt/sources.list &lt;&lt; &quot;EOF&quot; &amp;&amp;<br /> deb http://maedevu.maemo.org/leste ascii main contrib non-free n900<br /> deb http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900<br /> <br /> deb-src http://deb.debian.org/debian stretch main<br /> deb-src http://maedevu.maemo.org/leste ascii main contrib non-free n900<br /> deb-src http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900<br /> EOF<br /> wget --no-check-certificate https://maedevu.maemo.org/testing-key.asc &amp;&amp;<br /> apt-key add testing-key.asc &amp;&amp;<br /> rm -f testing-key.asc &amp;&amp;<br /> rm -f /var/cache/apt/archives/*.deb &amp;&amp;<br /> apt-get update &amp;&amp;<br /> exec bash<br /> <br /> # Build Xorg for Nokia N900<br /> apt-get source xserver-xorg-core &amp;&amp;<br /> cd xorg-server-1.19.2 &amp;&amp;<br /> wget https://raw.githubusercontent.com/buildroot/buildroot/88e0f214dcb7c2a99a4425a70673d2aa5f48d720/package/x11r7/xserver_xorg-server/1.20.4/0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch &amp;&amp;<br /> mv -v 0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch debian/patches &amp;&amp;<br /> echo -e &quot;# crossbuild fix\n0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch&quot; &gt;&gt; debian/patches/series &amp;&amp;<br /> apt-get -y build-dep -a armhf . &amp;&amp;<br /> time dpkg-buildpackage -aarmhf -j$JOBS -b &amp;&amp;<br /> echo OK || echo FAIL<br /> <br /> To login the container later:<br /> sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D /var/lib/container/stretch<br /> <br /> To remove the container:<br /> sudo rm -fr /var/lib/container/stretch<br /> <br /> === Cross-distro solution for development inside an ARM/ARM64 chroot on a PC ===<br /> <br /> It's possible to set up an emulated chroot development environment for ARM on x86/amd64 that will work on almost any Linux distro with just a few simple steps. This will work for systemd-less distros including Devuan and even Maemo Leste on x86/amd64. This guide provides an example for how to set up a generic ARM64 development chroot on a Debian-based distro. This method can similarly be used with images (tarballs) for other devices.<br /> <br /> 1. Install the QEMU full system emulation static binaries and [http://binfmt-support.nongnu.org/ support for foreign binaries]:<br /> <br /> $ sudo apt-get install qemu-user-static binfmt-support<br /> <br /> The installation should register ARM binaries for automatic execution via QEMU. You can verify this with '''update-binfmts''':<br /> <br /> $ sudo update-binfmts --display qemu-arm<br /> qemu-arm (enabled):<br /> package = qemu-user-static<br /> type = magic<br /> offset = 0<br /> magic = \x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00<br /> mask = \xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff<br /> interpreter = /usr/bin/qemu-arm-static<br /> detector =<br /> <br /> 2. Find the [http://maedevu.maemo.org/images/arm64-generic/ latest] Maemo Leste ARM64 tarball and download and extract it:<br /> <br /> $ mkdir leste-arm64<br /> $ cd leste-arm64<br /> $ curl http://maedevu.maemo.org/images/arm64-generic/20190226/maemo-leste-1.0-arm64-generic-20190226.tar.gz | gunzip -c | sudo tar xvf -<br /> <br /> 3. From the same directory, configure the chroot with a few resources from your host system:<br /> <br /> $ sudo mount -t proc proc proc<br /> $ sudo mount -o bind /dev dev<br /> $ sudo mount -o bind /dev/pts dev/pts<br /> <br /> 4. From the same directory, create a symlink for the mount table:<br /> <br /> $ sudo ln -s /proc/mounts etc/mtab<br /> <br /> 5. From the same directory, set the locale, enter the chroot and switch to the unprivileged user:<br /> <br /> $ sudo LC_ALL=C chroot . /bin/su - user<br /> <br /> You'll now be ready to use your Maemo Leste ARM64 development environment:<br /> <br /> $ uname -m<br /> aarch64<br /> <br /> Once you have finished with it, you can exit and unmount the resources you previously mounted:<br /> <br /> $ exit<br /> $ sudo umount dev/pts dev proc<br /> <br /> === Localization ===<br /> <br /> See [[Localization]]<br /> <br /> <br /> === TODO ===<br /> <br /> * Discuss where people look to pick up issues (clear answer is the bugtracker, but still)<br /> * How people can make changes and how to send them in</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_Bionic&diff=1138 2021-07-24T11:48:30Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Bionic.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Targa XT875<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2011-09-8<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4.3&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, Kionix KXTf9 accelerometer, St L3GD20H Gyro, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.10.4<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Gadgets only<br /> |sw_usb_host=No<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes, [[https://github.com/maemo-leste/pvr-omap4/|SGX540, closed driver|]]<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=untested<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=No, needs kernel work<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No, needs kernel/userspace work<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=70mW, needs sim inserted<br /> |sw_standbytime=91.8h (with HW4X)<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid Bionic with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux system<br /> * Android Tools: fastboot adb<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://phoenix.maemo.org/view/Images/job/leste-image-bionic/<br /> <br /> # Latest maemo-leste-1.0-armhf-bionic-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # droid4-kexecboot.img<br /> <br /> Download or clone https://github.com/IMbackK/bionic-clown-boot<br /> <br /> Follow the instructions in bionic-clown-boot's readme to install kexecboot on your device.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> Wait for sync to complete and insert MicroSD card into The Bionic. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Notes ==<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> As explained at http://muru.com/linux/d4 , the Droid 4 and Bionic both expose 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 Bionic, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> == Unlocking the modem for usage in Europe ==<br /> <br /> Tony suggested these values, Wizzup confirmed it to work on his Bionic in Europe/Amsterdam.<br /> <br /> &lt;pre&gt;<br /> apt install build-essential<br /> git clone https://github.com/tmlind/tcmdrw<br /> cd tcmdrw<br /> make<br /> ./tcmdrw 1877=8703E80400000200<br /> ./tcmdrw 6850=05<br /> &lt;/pre&gt;<br /> <br /> Tony also writes:<br /> <br /> &lt;pre&gt;<br /> 22:34 &lt; tmlind&gt; hmm so i had to do this for 3g gain: tcmdrw 1143=aaff0000, got that value from xt910 firmware i think, otherwise 3g signal was weak<br /> 22:43 &lt; tmlind&gt; Wizzup: great, the 1143 setting is for 1900 frequency only to get decent signal on t-mo in the us<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> 22:37 &lt; tmlind&gt; i also had to do tcmdrw 6850=05 for 3g voice to work properly<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== 3G Internet ====<br /> &lt;pre&gt;<br /> 22:12 &lt; pave1&gt; qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> 22:12 &lt; pave1&gt; route del default<br /> 22:12 &lt; pave1&gt; sudo ifconfig wwan0 up<br /> 22:12 &lt; pave1&gt; dhclient wwan0<br /> &lt;/pre&gt;<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> <br /> == Old status table ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.10.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | USB slave || Yes || <br /> |-<br /> | USB host (OTG) || No || <br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Keyboard || N/A ||<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | 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)<br /> |-<br /> | Phone calls || WIP || Untested<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Wifi || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | IrDA || N/A || Missing in hardware<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || No ||<br /> |-<br /> | Nfc || No || no hardware<br /> |-<br /> | Accelerometer || Yes ||<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration)<br /> |-<br /> | Gyro || No || needs kernel work<br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | AGPS || No ||<br /> |-<br /> | Front Camera || No || <br /> |-<br /> | Back Camera(s) || No || <br /> |-<br /> | Idle power consumption || ~70 mW || Needs sim inserted<br /> |-<br /> | Idle Battery life on new battery || 91.8 h || With HW4X<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1137 2021-07-24T11:46:47Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati XT894<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> <br /> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> route del default<br /> sudo ifconfig wwan0 up<br /> dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> sudo modprobe hci_uart<br /> pactl load-module module-bluetooth-discover<br /> blueman-manager<br /> <br /> Pair &amp; trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br /> <br /> == Using a configured Leste sdcard in a different Droid4 ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate. <br /> If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.<br /> apt reinstall firmware-ti-connectivity <br /> If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device<br /> apt download firmware-ti-connectivity<br /> Then copy the .deb to your new device and install that (as root) with<br /> dpkg -i firmware-ti-connectivity_[version]_all.deb <br /> Then (as root) re-calibrate the wifi chip by running<br /> /usr/bin/maserati-calibrate<br /> Then reboot.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> Droid4_Daimonin_Hdmi.jpg<br /> &lt;/gallery&gt;<br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1115 2021-06-03T17:07:56Z

<p>BuZz: /* BT Audio headset */</p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> <br /> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> route del default<br /> sudo ifconfig wwan0 up<br /> dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> sudo modprobe hci_uart<br /> pactl load-module module-bluetooth-discover<br /> blueman-manager<br /> <br /> Pair &amp; trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> &lt;/gallery&gt;<br /> <br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1114 2021-06-03T02:28:02Z

<p>BuZz: /* 3G Internet */</p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> <br /> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> route del default<br /> sudo ifconfig wwan0 up<br /> dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> sudo modprobe hci_uart<br /> pactl load-module module-bluetooth-discover<br /> blueman<br /> <br /> Pair &amp; trust your device, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> &lt;/gallery&gt;<br /> <br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1113 2021-06-03T02:27:27Z

<p>BuZz: /* BT Audio headset */</p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> # qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> # route del default<br /> # sudo ifconfig wwan0 up<br /> # dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> sudo modprobe hci_uart<br /> pactl load-module module-bluetooth-discover<br /> blueman<br /> <br /> Pair &amp; trust your device, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> &lt;/gallery&gt;<br /> <br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1112 2021-06-03T02:15:18Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> # qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> # route del default<br /> # sudo ifconfig wwan0 up<br /> # dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> ==== BT Audio headset ====<br /> <br /> * sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> * sudo modprobe hci_uart<br /> * pactl load-module module-bluetooth-discover<br /> * blueman<br /> * pair &amp; trust your device, connect audiosink<br /> <br /> Quality seems a bit better in 'offline mode'.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> &lt;/gallery&gt;<br /> <br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1111 2021-06-03T02:13:45Z

<p>BuZz: /* Bluetooth */</p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> |category=Supported<br /> |sw_kernel=5.11.0<br /> |sw_serial=Yes, [[#Serial Cable|special cable]]<br /> |sw_charging=Yes<br /> |sw_usb_slave=Yes<br /> |sw_usb_host=Yes<br /> |sw_touchscreen=Yes<br /> |sw_keyboard=Yes<br /> |sw_screen=Yes<br /> |sw_hdmi=Yes<br /> |sw_tv=<br /> |sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br /> |sw_vibration=Yes<br /> |sw_audio=Yes<br /> |sw_calls=WIP<br /> |sw_sms=Yes, no UI<br /> |sw_wifi=Yes<br /> |sw_ethernet=<br /> |sw_irda=<br /> |sw_2g3gdata=Yes<br /> |sw_4g=No<br /> |sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br /> |sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br /> |sw_fmrx=<br /> |sw_nfc=<br /> |sw_accelerometer=Yes<br /> |sw_compass=Yes, no integration<br /> |sw_gyro=<br /> |sw_proximity=Yes<br /> |sw_als=Yes<br /> |sw_gps=Yes<br /> |sw_agps=No<br /> |sw_frontcam=No<br /> |sw_backcam=No<br /> |sw_idlepower=120mW<br /> |sw_standbytime=<br /> }}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> === Updating Android ===<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> === Setting up kexecboot ===<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> === Install Maemo Leste to the sdcard ===<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> Normally you can just apt update &amp;&amp; apt dist-upgrade to update to the latest version. If for some reason this fails:<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab the latest image from https://phoenix.maemo.org/view/Images/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Bluetooth ==<br /> <br /> 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<br /> <br /> <br /> == BT Audio headset ==<br /> <br /> * sudo apt install pulseaudio-module-bluetooth blueman bluez<br /> * sudo modprobe hci_uart<br /> * pactl load-module module-bluetooth-discover<br /> * blueman<br /> * pair &amp; trust your device, connect audiosink<br /> <br /> Quality seems a bit better in 'offline mode'.<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> ==== Wifi ====<br /> <br /> 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.<br /> <br /> Install necessary tools: <br /> &lt;pre&gt;<br /> apt-get install ti-utils-wilink6 droid4-wlanconfig<br /> &lt;/pre&gt;<br /> Run calibration:<br /> &lt;pre&gt;<br /> sudo maserati-calibrate<br /> &lt;/pre&gt;<br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this:<br /> <br /> Read modem output:<br /> &lt;pre&gt;<br /> cat /dev/motmdm1 &amp;<br /> &lt;/pre&gt;<br /> <br /> Online modem:<br /> &lt;pre&gt;<br /> printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Connect to network:<br /> &lt;pre&gt;<br /> printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Print connected network:<br /> &lt;/pre&gt;<br /> printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Turn off signal reporting:<br /> &lt;pre&gt;<br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Dial a number:<br /> &lt;pre&gt;<br /> printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Hang up:<br /> &lt;pre&gt;<br /> printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Answer incoming call:<br /> &lt;pre&gt;<br /> printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.<br /> <br /> ==== 3G Internet ====<br /> <br /> Using qmicli:<br /> # qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> # route del default<br /> # sudo ifconfig wwan0 up<br /> # dhclient wwan0<br /> <br /> 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.<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> ==== HDMI ====<br /> Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br /> &lt;pre&gt;<br /> xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br /> &lt;/pre&gt;<br /> Return to internal touchscreen display.<br /> &lt;pre&gt;<br /> xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br /> &lt;/pre&gt;<br /> <br /> ==== Keyboard / Mouse sharing with PC ====<br /> To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br /> &lt;pre&gt;<br /> [https://github.com/debauchee/barrier Barrier software-KVM switch]<br /> &lt;/pre&gt;<br /> Developers and testers may wish to disable the googley bits before compiling.<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> Cant_have_2_much_leste.jpg<br /> Leste-neverball.jpg<br /> Statsfun.jpg<br /> Leste-glmatrix.png<br /> Droid4-leste-utox2.jpg<br /> Droid4-leste-pcsx.jpg<br /> Droid4-leste-surf_master.jpg<br /> &lt;/gallery&gt;<br /> <br /> <br /> == Old status overview ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG and USB network<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes || Implemented with Pulseaudio and UCM files<br /> |-<br /> | 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | 4G data || No || Needs kernel work<br /> |-<br /> | SMS || Yes || Works with ofono. Needs Leste UI<br /> |-<br /> | Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br /> |-<br /> | 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<br /> |-<br /> | FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br /> |-<br /> | Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br /> |-<br /> | Gyro || N/A || <br /> |-<br /> | Proximity sensor || Yes ||<br /> |-<br /> | Ambient Light Sensor || Yes ||<br /> |-<br /> | Vibration Motor || Yes || <br /> |-<br /> | HDMI-out || Yes || No UI integration<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br /> |-<br /> | Infrared || N/A || Missing in hardware<br /> |-<br /> | Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br /> |-<br /> | Idle power consumption || ~120mW || Needs sim inserted<br /> |}<br /> <br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Main_Page&diff=899 2020-12-31T11:29:15Z

<p>BuZz: /* Links */</p> <hr /> <div>= Description =<br /> <br /> Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.<br /> <br /> You can find us on '''freenode''', channel '''#maemo-leste'''.<br /> <br /> For an overview of the current status, you might want to check out: [[Status]]<br /> <br /> Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the &quot;supported&quot; devices ship with recent Linux (mainline-based) kernels.<br /> <br /> The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.<br /> <br /> For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.<br /> <br /> If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.<br /> <br /> == Frequently Asked Questions ==<br /> <br /> See [[Leste_FAQ|FAQ]]<br /> <br /> == Supported Devices ==<br /> <br /> See [[:Category:Device]]<br /> <br /> == Latest Images ==<br /> <br /> https://phoenix.maemo.org/view/Images/<br /> <br /> == Development ==<br /> <br /> See [[Development]]<br /> <br /> == Roadmap ==<br /> <br /> === Project milestones ===<br /> https://github.com/maemo-leste/bugtracker/milestones<br /> <br /> === Wishlist ===<br /> <br /> You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br /> <br /> == Talks ==<br /> <br /> See [[Talks]]<br /> <br /> == Links ==<br /> &lt;div&gt;<br /> The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.<br /> <br /> *Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br /> <br /> *Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br /> <br /> *Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br /> <br /> *Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br /> <br /> *Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/<br /> <br /> *Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br /> <br /> *Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]<br /> <br /> *Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )<br /> <br /> *Our Package index: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]<br /> <br /> *Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br /> <br /> *RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]<br /> <br /> *[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]<br /> &lt;/div&gt;</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=730 2020-05-11T22:19:46Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | 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)<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Work with AT commands, needs ofono porting work, and then Leste UI<br /> |-<br /> | Phone calls || WIP || Work with AT commands (good call quality, too), needs ofono porting work, and then Leste UI<br /> |-<br /> | Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available in /sys, but not yet as input device, needs kernel and MCE work https://github.com/maemo-leste/bugtracker/issues/294<br /> |-<br /> | Compass || ? || Available in /sys (after loading ak8975 module. No applications using it yet<br /> |-<br /> | Proximity sensor || WIP || Sensor works, not yet exposed as evdev device<br /> |-<br /> | Ambient Light Sensor || Yes || https://github.com/maemo-leste/mce/pull/8<br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes || No userspace yet (should be in mce)<br /> |-<br /> | Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab latest image from https://maedevu.maemo.org/images/droid4/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this over SSH:<br /> <br /> &lt;pre&gt;<br /> Read modem output: <br /> # cat /dev/motmdm1 &amp;<br /> <br /> Online modem:<br /> # printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Connect to network:<br /> <br /> # printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Print connected network:<br /> <br /> # printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Not sure, do it anyway:<br /> <br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> <br /> Dial a number:<br /> <br /> # printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> <br /> Hang up:<br /> <br /> # printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> <br /> Answer incoming call:<br /> <br /> # printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to &quot;speakerphone&quot; and set the right speaker to &quot;voice&quot; codec, and set volume for both call and voice to something non-zero.<br /> <br /> ==== 3G Internet ====<br /> &lt;pre&gt;<br /> 22:12 &lt; pave1&gt; qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> 22:12 &lt; pave1&gt; route del default<br /> 22:12 &lt; pave1&gt; sudo ifconfig wwan0 up<br /> 22:12 &lt; pave1&gt; dhclient wwan0<br /> &lt;/pre&gt;<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=727 2020-05-06T03:14:07Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=TI OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=PowerVR SGX540 <br /> |audio=<br /> |network=<br /> |storage=16GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | 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)<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Work with AT commands, needs ofono porting work, and then Leste UI<br /> |-<br /> | Phone calls || WIP || Work with AT commands (good call quality, too), needs ofono porting work, and then Leste UI<br /> |-<br /> | Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available in /sys, but not yet as input device, needs kernel and MCE work https://github.com/maemo-leste/bugtracker/issues/294<br /> |-<br /> | Compass || ? || Available in /sys (after loading ak8975 module. No applications using it yet<br /> |-<br /> | Proximity sensor || WIP || Sensor works, not yet exposed as evdev device<br /> |-<br /> | Ambient Light Sensor || Yes || https://github.com/maemo-leste/mce/pull/8<br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes || No userspace yet (should be in mce)<br /> |-<br /> | Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab latest image from https://maedevu.maemo.org/images/droid4/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this over SSH:<br /> <br /> &lt;pre&gt;<br /> Read modem output: <br /> # cat /dev/motmdm1 &amp;<br /> <br /> Online modem:<br /> # printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Connect to network:<br /> <br /> # printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Print connected network:<br /> <br /> # printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Not sure, do it anyway:<br /> <br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> <br /> Dial a number:<br /> <br /> # printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> <br /> Hang up:<br /> <br /> # printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> <br /> Answer incoming call:<br /> <br /> # printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to &quot;speakerphone&quot; and set the right speaker to &quot;voice&quot; codec, and set volume for both call and voice to something non-zero.<br /> <br /> ==== 3G Internet ====<br /> &lt;pre&gt;<br /> 22:12 &lt; pave1&gt; qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> 22:12 &lt; pave1&gt; route del default<br /> 22:12 &lt; pave1&gt; sudo ifconfig wwan0 up<br /> 22:12 &lt; pave1&gt; dhclient wwan0<br /> &lt;/pre&gt;<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=726 2020-05-06T03:01:55Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=8GB flash<br /> |usb=<br /> |camera=<br /> |sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | 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)<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Work with AT commands, needs ofono porting work, and then Leste UI<br /> |-<br /> | Phone calls || WIP || Work with AT commands (good call quality, too), needs ofono porting work, and then Leste UI<br /> |-<br /> | Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available in /sys, but not yet as input device, needs kernel and MCE work https://github.com/maemo-leste/bugtracker/issues/294<br /> |-<br /> | Compass || ? || Available in /sys (after loading ak8975 module. No applications using it yet<br /> |-<br /> | Proximity sensor || WIP || Sensor works, not yet exposed as evdev device<br /> |-<br /> | Ambient Light Sensor || Yes || https://github.com/maemo-leste/mce/pull/8<br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes || No userspace yet (should be in mce)<br /> |-<br /> | Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab latest image from https://maedevu.maemo.org/images/droid4/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> <br /> ==== Phone Call ====<br /> <br /> Make sure there is a SIM in the phone.<br /> <br /> Run this over SSH:<br /> <br /> &lt;pre&gt;<br /> Read modem output: <br /> # cat /dev/motmdm1 &amp;<br /> <br /> Online modem:<br /> # printf &quot;AT+CFUN=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Connect to network:<br /> <br /> # printf &quot;AT+COPS=1\r&quot; &gt; /dev/motmdm1<br /> <br /> Print connected network:<br /> <br /> # printf &quot;AT+COPS?\r&quot; &gt; /dev/motmdm1<br /> <br /> Not sure, do it anyway:<br /> <br /> # printf &quot;AT+SCRN=0\r&quot; &gt; /dev/motmdm1<br /> <br /> Dial a number:<br /> <br /> # printf &quot;ATD+1234567890\r&quot; &gt; /dev/motmdm1<br /> <br /> Hang up:<br /> <br /> # printf &quot;ATH\r&quot; &gt; /dev/motmdm1<br /> <br /> Answer incoming call:<br /> <br /> # printf &quot;ATA\r&quot; &gt; /dev/motmdm1<br /> &lt;/pre&gt;<br /> <br /> Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to &quot;speakerphone&quot; and set the right speaker to &quot;voice&quot; codec, and set volume for both call and voice to something non-zero.<br /> <br /> ==== 3G Internet ====<br /> &lt;pre&gt;<br /> 22:12 &lt; pave1&gt; qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz<br /> 22:12 &lt; pave1&gt; route del default<br /> 22:12 &lt; pave1&gt; sudo ifconfig wwan0 up<br /> 22:12 &lt; pave1&gt; dhclient wwan0<br /> &lt;/pre&gt;<br /> <br /> ==== GPS ====<br /> &lt;pre&gt;<br /> modprobe gnss-motmdm and point gpsd to use /dev/gnss0<br /> &lt;/pre&gt;<br /> <br /> 22:30 &lt; tmlind&gt; 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 :)<br /> <br /> Can try to &lt;pre&gt;<br /> mkfifo /tmp/gps<br /> cat /dev/gnss0 &gt; /tmp/gps<br /> Then point gpsd to use /tmp/gps<br /> &lt;/pre&gt;<br /> <br /> ==== USSD ====<br /> <br /> &lt;pre&gt;<br /> 22:45 &lt; tmlind&gt; fyi, here's how to send USSD to query balance for example: printf &quot;AT+CUSD=1,#999#,0\r&quot; &gt; /dev/motmdm1<br /> 22:47 &lt; tmlind&gt; fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br /> https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br /> &lt;/pre&gt;<br /> <br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=704 2020-03-26T02:14:07Z

<p>BuZz: </p> <hr /> <div>{{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=127x67.3x12.7mm<br /> |release_date=2012-02-10<br /> |soc=OMAP4430<br /> |dram=1024MB DDR2<br /> |power=<br /> |lcd=960x540 4&quot;<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=8GB flash<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0-rc5 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | 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)<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || WIP || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> | Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Updating ==<br /> <br /> * Poweroff device, grab the SD card<br /> * Backup any important files<br /> * Grab latest image from https://maedevu.maemo.org/images/droid4/<br /> * Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=699 2020-03-25T00:32:11Z

<p>BuZz: /* Blinkenlights */</p> <hr /> <div>{{Stub}}<br /> <br /> {{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=<br /> |release_date=<br /> |soc=<br /> |dram=<br /> |power=<br /> |lcd=<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0-rc5 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes ||<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || WIP || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> |Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Postinstall notes for 20200112 image ==<br /> <br /> Current image has some erratas which can be fixed by following the instructions found in this post:<br /> https://github.com/maemo-leste/bugtracker/issues/302#issuecomment-576277674<br /> <br /> === Wifi ===<br /> <br /> Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)<br /> <br /> deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free<br /> <br /> apt install -t ascii-backports wpasupplicant<br /> apt install -t ascii-backports firmware-ti-connectivity<br /> <br /> === Bluetooth ===<br /> <br /> Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/<br /> <br /> $ sha256sum TIInit_10.6.15.bts <br /> 85dc6539436319fa1301277c171f9fd65b716279900bc686a76578ab24cc7793 TIInit_10.6.15.bts<br /> <br /> Note: some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> === Sound ===<br /> <br /> This needs to be executed to enable the sound:<br /> <br /> modprobe snd-soc-cpcap<br /> modprobe snd-soc-motmdm<br /> modprobe snd-soc-audio-graph-card<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=698 2020-03-25T00:31:53Z

<p>BuZz: /* Blinkenlights */</p> <hr /> <div>{{Stub}}<br /> <br /> {{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=<br /> |release_date=<br /> |soc=<br /> |dram=<br /> |power=<br /> |lcd=<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0-rc5 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes ||<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || WIP || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> |Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Postinstall notes for 20200112 image ==<br /> <br /> Current image has some erratas which can be fixed by following the instructions found in this post:<br /> https://github.com/maemo-leste/bugtracker/issues/302#issuecomment-576277674<br /> <br /> === Wifi ===<br /> <br /> Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)<br /> <br /> deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free<br /> <br /> apt install -t ascii-backports wpasupplicant<br /> apt install -t ascii-backports firmware-ti-connectivity<br /> <br /> === Bluetooth ===<br /> <br /> Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/<br /> <br /> $ sha256sum TIInit_10.6.15.bts <br /> 85dc6539436319fa1301277c171f9fd65b716279900bc686a76578ab24cc7793 TIInit_10.6.15.bts<br /> <br /> Note: some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> === Sound ===<br /> <br /> This needs to be executed to enable the sound:<br /> <br /> modprobe snd-soc-cpcap<br /> modprobe snd-soc-motmdm<br /> modprobe snd-soc-audio-graph-card<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=697 2020-03-25T00:26:10Z

<p>BuZz: </p> <hr /> <div>{{Stub}}<br /> <br /> {{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=<br /> |release_date=<br /> |soc=<br /> |dram=<br /> |power=<br /> |lcd=<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.6.0-rc5 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes ||<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || WIP || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> |Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # flash-droid-4-fw.sh<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Check what kernel version your Android OS runs.<br /> For this go to Settings -&gt; About phone. Slide to the bottom, where you can see &quot;Kernel version&quot;.<br /> If you have at least 3.0.8, you may skip &quot;Updating Android&quot; step below.<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> 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:<br /> &lt;pre&gt;<br /> pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br /> sudo bash ../flash-droid-4-fw.sh<br /> popd<br /> &lt;/pre&gt;<br /> <br /> Now, assuming you are in the working directory, install kexecboot:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> If you did &quot;Updating Android&quot; the device should run the firstboot steps.<br /> If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Postinstall notes for 20200112 image ==<br /> <br /> Current image has some erratas which can be fixed by following the instructions found in this post:<br /> https://github.com/maemo-leste/bugtracker/issues/302#issuecomment-576277674<br /> <br /> === Wifi ===<br /> <br /> Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)<br /> <br /> deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free<br /> <br /> apt install -t ascii-backports wpasupplicant<br /> apt install -t ascii-backports firmware-ti-connectivity<br /> <br /> === Bluetooth ===<br /> <br /> Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/<br /> <br /> $ sha256sum TIInit_10.6.15.bts <br /> 85dc6539436319fa1301277c171f9fd65b716279900bc686a76578ab24cc7793 TIInit_10.6.15.bts<br /> <br /> Note: some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br /> Blacklisting the module may help if you have such problems:<br /> echo &quot;blacklist hci_uart&quot; &gt;&gt; /etc/modprobe.d/blacklist.conf<br /> <br /> === Sound ===<br /> <br /> This needs to be executed to enable the sound:<br /> <br /> modprobe snd-soc-cpcap<br /> modprobe snd-soc-motmdm<br /> modprobe snd-soc-audio-graph-card<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Stuff to try ==<br /> <br /> ==== Blinkenlights ====<br /> Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br /> echo cpu &gt; /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br /> echo mmc0 &gt; echo mmc0 &gt; /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=619 2020-02-05T17:31:28Z

<p>BuZz: </p> <hr /> <div>{{Stub}}<br /> <br /> {{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=<br /> |release_date=<br /> |soc=<br /> |dram=<br /> |power=<br /> |lcd=<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Not yet || PowerVR SGX540 (closed driver) - see [[Motorola Droid 4/PowerVR]]<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes ||<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || ? || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> |Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> Now go to the working directory and run:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> The device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Postinstall notes for 20200112 image ==<br /> <br /> === Wifi ===<br /> <br /> Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)<br /> <br /> deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free<br /> <br /> apt install -t ascii-backports wpasupplicant<br /> apt install -t ascii-backports firmware-ti-connectivity<br /> <br /> Installing Bluetooth firmware in order to have working Wi-Fi is also required.<br /> <br /> === Bluetooth ===<br /> <br /> Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/<br /> <br /> $ sha256sum TIInit_10.6.15.bts <br /> 85dc6539436319fa1301277c171f9fd65b716279900bc686a76578ab24cc7793 TIInit_10.6.15.bts<br /> <br /> === Sound ===<br /> <br /> This needs to be executed after each boot by hand ; <br /> <br /> modprobe snd-soc-cpcap<br /> modprobe snd-soc-motmdm<br /> modprobe snd-soc-audio-graph-card<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> Droid4_htop.jpg<br /> Droid4_leste_logo.jpg<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=572 2020-01-26T16:34:46Z

<p>BuZz: /* Gallery */</p> <hr /> <div>{{Stub}}<br /> <br /> {{Infobox Device<br /> |image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br /> |manufacturer=Motorola<br /> |codename=Maserati<br /> |dimensions=<br /> |release_date=<br /> |soc=<br /> |dram=<br /> |power=<br /> |lcd=<br /> |video=<br /> |audio=<br /> |network=<br /> |storage=<br /> |usb=<br /> |camera=<br /> |sensors=<br /> |other=<br /> }}<br /> <br /> == Status ==<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Feature<br /> ! Leste supported<br /> ! Notes<br /> |-<br /> | Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4<br /> |-<br /> | Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br /> |-<br /> | Charging || Yes ||<br /> |-<br /> | Wireless || Yes ||<br /> |-<br /> | Ethernet || N/A ||<br /> |-<br /> | Micro USB || Yes || OTG<br /> |-<br /> | 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)<br /> |-<br /> | Screen || Yes ||<br /> |-<br /> | 3D Acceleration || Not yet || PowerVR SGX540 (closed driver) - see [[Motorola Droid 4/PowerVR]]<br /> |-<br /> | Touchscreen || Yes || Capacitive<br /> |-<br /> | Audio || Yes ||<br /> |-<br /> | 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br /> |-<br /> | SMS || WIP || Reported to work, no UI yet<br /> |-<br /> | Phone calls || WIP || Reported to work, no UI yet<br /> |-<br /> | Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.<br /> |-<br /> | FM Transmitter || N/A ||<br /> |-<br /> | FM Receiver || Not yet ||<br /> |-<br /> | Accelerometer || ? || Available as input device, needs MCE work<br /> |-<br /> | Proximity sensor || ? || <br /> |-<br /> | HDMI-out || WIP || works, but not with hildon-desktop<br /> |-<br /> | TV-out || N/A ||<br /> |-<br /> | Vibration Motor || Yes ||<br /> |-<br /> |Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294<br /> |}<br /> <br /> == Installation ==<br /> <br /> Hardware requirements:<br /> <br /> * Droid4 with fully charged battery<br /> * MicroUSB cable<br /> * MicroSD card<br /> <br /> Software requirements:<br /> * Host Linux or Windows system<br /> * Android Tools: fastboot<br /> * Flashing tools:<br /> ** XZ Utils and coreutils for Linux<br /> ** Etcher[https://github.com/balena-io/etcher] for Windows<br /> <br /> Download from https://maedevu.maemo.org/images/droid4/<br /> <br /> # VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)<br /> <br /> Download from https://github.com/tmlind/droid4-kexecboot.git<br /> <br /> # utags-mmcblk1p13.bin<br /> # droid4-kexecboot.img<br /> <br /> Installation:<br /> <br /> # Create a working directory with above mentioned files in it<br /> # unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br /> # Power off Droid4 and connect it to the host machine with MicroUSB cable<br /> # Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br /> <br /> Now go to the working directory and run:<br /> <br /> &lt;pre&gt;<br /> sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br /> sudo fastboot reboot-bootloader<br /> sudo fastboot flash bpsw droid4-kexecboot.img<br /> sudo fastboot flash utags utags-mmcblk1p13.bin<br /> sudo fastboot reboot<br /> &lt;/pre&gt;<br /> <br /> The device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br /> <br /> Now, flash the Maemo Leste image to your sdcard:<br /> <br /> On Linux:<br /> &lt;pre&gt;<br /> xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE<br /> sync<br /> &lt;/pre&gt;<br /> <br /> On Windows: Use Etcher<br /> <br /> Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br /> <br /> You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.<br /> <br /> == Postinstall notes for 20200112 image ==<br /> <br /> === Wifi ===<br /> <br /> Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)<br /> <br /> deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free<br /> <br /> apt install -t ascii-backports wpasupplicant<br /> apt install -t ascii-backports firmware-ti-connectivity<br /> <br /> === Bluetooth ===<br /> <br /> Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/<br /> <br /> === Sound ===<br /> <br /> This needs to be executed after each boot by hand ; <br /> <br /> modprobe snd-soc-cpcap<br /> modprobe snd-soc-motmdm<br /> modprobe snd-soc-audio-graph-card<br /> <br /> == Notes ==<br /> <br /> 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.<br /> <br /> If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br /> <br /> Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br /> <br /> Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br /> <br /> == Serial Cable ==<br /> <br /> 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/<br /> <br /> While using the serial cable, if you lose the connection, the following may help:<br /> <br /> &lt;pre&gt;<br /> 18:43 &lt; tmlind&gt; sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br /> the console login propt later<br /> 18:45 &lt; tmlind&gt; try plugging in a pc usb cable then back to uart cable in case that might help<br /> &lt;/pre&gt;<br /> <br /> == Gallery ==<br /> <br /> &lt;gallery&gt;<br /> Motorola-Droid4-20200125.jpeg<br /> Droid4-neofetch.JPG<br /> &lt;/gallery&gt;<br /> <br /> [[Category:Device]]</div>

BuZz https://leste.maemo.org/index.php?title=File:Droid4-neofetch.JPG&diff=571 2020-01-26T16:23:18Z

<p>BuZz: </p> <hr /> <div></div>

BuZz