<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Maemotalk &#187; maemo</title>
	<atom:link href="http://maemotalk.feelslikeburning.com/category/maemo/feed/" rel="self" type="application/rss+xml" />
	<link>http://maemotalk.feelslikeburning.com</link>
	<description>for the Nokia 770</description>
	<pubDate>Thu, 08 Feb 2007 17:20:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>to Makotonen / Re:2006 beta Video Player</title>
		<link>http://maemotalk.feelslikeburning.com/2006/06/16/2006-beta-video-player/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/06/16/2006-beta-video-player/#comments</comments>
		<pubDate>Fri, 16 Jun 2006 15:22:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/06/16/2006-beta-video-player/</guid>
		<description><![CDATA[after having looked at the maemo 2.0 beta, and viewing the video several times, I have to admit the video performance is very good (for at least the discovery video included on the firmware), and much better than the 2005 firmware.
It runs at 352&#215;208, and appears to have a very good frame rate on the [...]]]></description>
			<content:encoded><![CDATA[<p>after having looked at the maemo 2.0 beta, and viewing the video several times, I have to admit the video performance is very good (for at least the discovery video included on the firmware), and much better than the 2005 firmware.<br />
It runs at 352&#215;208, and appears to have a very good frame rate on the 770, even at full screen.  I tried out some of my older video clips at lower resolution, and they did not appear to be any better than on the old firmware. So i am assuming that the discovery video has been optimized to work well on the 770 with the 2.0 video player.</p>
<p>The question i throw out to the nokia Video Player team is this..<br />
Can you share the magic with the rest of us on how to transcode our videos so they look that good on the 770? Is the resolution critical? what are the video / audio codec settings?<br />
What is it that makes the discovery clip look so much better than most clips (on the 770)? How can we too optimize our videos for the 770?<br />
Hopefully<br />
ubergEEk</p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/06/16/2006-beta-video-player/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Top Down Software Development:part 2</title>
		<link>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-2/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-2/#comments</comments>
		<pubDate>Tue, 06 Jun 2006 19:11:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-2/</guid>
		<description><![CDATA[Use Cases Continued / User Characterization

The next step we will look at is user charactization. A few examples of these are:

Student - This user will likely have a cell phone, possibly a laptop, and have to haul everything with them on foot (net weight is critical). The 770 would fit a use niche in applications [...]]]></description>
			<content:encoded><![CDATA[<p><u><strong>Use Cases Continued / User Characterization<br />
</strong></u></p>
<p>The next step we will look at is user charactization. A few examples of these are:</p>
<ul>
<li>Student - This user will likely have a cell phone, possibly a laptop, and have to haul everything with them on foot (net weight is critical). The 770 would fit a use niche in applications where a laptop is too cumbersome to use, and a cell phone is insufficent. Examples include waiting in queues, at bus stop, between classes, or on foot on campus. Most campuses (in US) now have ubiquituous WiFi, so campus / internet connectivity can be assumed.</li>
<li>Traveler - This user will have a cell phone, a laptop, possibly a blackberry, etc. Time will be spent at airports, train stations, hotels. etc. The 770 would once again fit a use niche in specific applicatations where a laptop is to cumbersome, and the cell phone is insufficient. Examples of these locations would include public transport, or in meetings where a laptop would be distracting. WiFi cannot be considered ubiquituous, so Internet access would either be through BlueTooth cellular access or not available. Once again, net travel weight is critical.</li>
<li>Power User / Geeky Soccer Parent - This user would generally carry around the 770 as a pocket utility as part of their office or home life. This type of user would likely make sure that WiFi was available for general information retrieval or access to network resources when in home or work locations, but would have to be functional in many non-connected locations. This user may also use it as a family calendar.</li>
</ul>
<p><u><strong>Application Models</strong></u></p>
<ul>
<li>Reference library - The 770 could be used as a compendium of information. This could include Wikipedia types of information, IMDB content, CIA world factbook, or Google Maps, Google itself, or more specialized content - such as NIST Special Publications (all in PDF). The ability to carry / access this depth and volume of content in your pocket, and display to this level is unmatched. This application model fits the 770 very well.</li>
<li>Ebook Reader - The 770 could be used as a portable personal library. The ability to carry thousands of pages of reading content could reduce the net travel weight of the user significantly.</li>
<li>Games / Simulations - The ability to entertain during dead time with no additional weight is important. However, the limited input controls and interactivity prevent many arcade and FPS games from consideration.</li>
<li>Personal information store / Wiki - The 770 could be used as a personal store of information for recall, such as a Wiki or PIM type of application. Once again, it has the capability to store photos, numbers, notes, addresses, etc. It can be massively more flexible than a PIM dedicated device. I would expect that the content will primarily be entered / developed on a workstation, and then synchronized to the 770. This would allow a very rich level of content to be displayed on the 770 with minimal user input.</li>
<li>Wireless Remote Control (for networked devices) - The 770 could be used as a remote control device to manage networked devices.</li>
</ul>
<p><u><strong>Connectivity Models</strong></u></p>
<p>There are essentially 3 connectivity models that are applicable to the 770.</p>
<ul>
<li>Disconnected - No connectivity of any type. This would be typical of some workplace environments, airplanes, camping, or WiFi / Cellular data deadspots (yes they really do exist).</li>
<li>WiFi Connected - Connectivity to local network and Internet through a WiFi access point. Generally good bandwidth.</li>
<li>Cellular Paired - Connectivity to Internet through a cellular data connection. Moderate to poor bandwidth, and often metered.</li>
</ul>
<p><u><strong>Use Case Development</strong></u></p>
<p>At this point we now have a few user classes, application classes and connectivity classes. By mixing and matching these we can come up with a story for use.</p>
<p>Use Case 1 - College student uses 770 to store information, schedule, class notes. Also uses it for media player and ebook reader for entertainment (downtime waster). Has continuous access to campus LAN through WiFi and acess to Internet. General purpose use is to check school email, chat, bus schedules, wikipedia, google. Will have Internet connectivity more than 90%.<br />
Use Assessment - this is being used as a convergent internet access device by the user. A flexible PIM / Wiki capability would be useful, but should be syncable to some network resource so that it can be managed / modified (and protected) from the 770 and some network terminal. Some of the information accessed would be suitable for caching locally. This would both increase battery lifetime and local performance. Examples include bus schedules, or pertinent wikipedia articles, IMDB pages, or local maps.<br />
Application Extrapolation - Based on this use case, the following non-standard applications would be &#8216;useful&#8217;:</p>
<ul>
<li>Web Browser with on demand caching capability, similar to Scrapbook for Firefox ( https://addons.mozilla.org/firefox/427/). This would allow local caching of relatively static content for continual reference. Performance would be increased and battery life extended.</li>
<li>PIM / Wiki (net syncable) - A flexible personal information store for storing the sundry details of busy campus life.</li>
</ul>
<p>Use Case 2 - Power User uses the 770 to check webmail from multiple sources, store personal information, ebook reader, maps, web articles, etc. Will have Internet connectivity in about 25% of locations or less. Is different from student in the following ways: Less likely to use chat regularly, more likely to be offline, more likely to have a much wider variety of &#8217;stuff&#8217; on the 770, since it is more of a tool / toy for the power user and more of a working utility for the student.</p>
<p>Use Assessment - The information accessed by the power user needs to have access to many online resources with a certain degree of static-ness, but with distinctly dynamic characteristics. Examples would include an online family calendar (eg google calendar), or web mail. The user would like to have a local (offline) copy of this information for browsing during downtime even if internet access is not available.</p>
<p>Application Extrapolation - Based on this use case, the following non-standard applications would be &#8216;useful&#8217;:</p>
<ul>
<li>Web browser with both on demand caching capability, similar to scrapbook, but with aggressive synchronization capability. If i site was marked for local caching and synchronization, it would aggressively attempt to synchronize when a connection became available. This would assure a minimal staleness for dynamic pages.</li>
<li>IMAP mail client with local caching - this would allow the user to view / manage email even when offline.</li>
</ul>
<p><u><strong>Conclusions</strong></u></p>
<p>Based on thes two very rudimentary use cases for the 770, i would have to conclude that the 770 would benefit from:</p>
<ol>
<li>Calendar application that would sync with say&#8230; Google Calendars?</li>
<li>Flexible Caching / Synchronizing web browser.</li>
<li>Native WebClipper for offline reading. Something like a Plucker but integrated with a view and user friendly. More like the old AvantGo, but completely integrated on the 770.</li>
<li>Network Syncable PIM / Wiki. Something to store free format (or flexible format) personal information.</li>
</ol>
<p><u><strong>Wrapup for Now</strong></u></p>
<p>These are two examples of use cases for the 770. As you can see it is relatively easy to just make up a use case story, and by following it logically through, you can define useful applications.</p>
<p>enjoy in moderation</p>
<p>ubergEEk</p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-2/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Top Down Software Development:part 1</title>
		<link>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-1/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-1/#comments</comments>
		<pubDate>Tue, 06 Jun 2006 13:06:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<category><![CDATA[packaging]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-1/</guid>
		<description><![CDATA[disclaimer - I will preface this by saying that none of the content is purposeful flamebait. These are primarily observations, and generalizations. Like any generalizations, there are always specific counter examples. However, from a statistical perspective, these generalizations apply to most open source projects.
This is unlike most of my previous posts on Maemo, since this [...]]]></description>
			<content:encoded><![CDATA[<p><u><strong>disclaimer </strong></u>- I will preface this by saying that none of the content is purposeful flamebait. These are primarily observations, and generalizations. Like any generalizations, there are always specific counter examples. However, from a statistical perspective, these generalizations apply to most open source projects.</p>
<p>This is unlike most of my previous posts on Maemo, since this is about the process and approach to open source software for a niche product. Well maemo is about open source and the 770 is a niche product.</p>
<p><u><strong>Software Classes </strong></u></p>
<p>One of the most significant issues with open source software is the lack of top down design. The majority of open source software falls into the following categories:</p>
<blockquote><p>(a) Me-Too software - Open source software that is developed specifically as an open sourced alternative to commercial software. These are often very good packages, and in many cases exceed the commercial packages in capability. However, they are product followers, and innovation is limited to out-doing the commercial package.</p></blockquote>
<blockquote><p>(b) Technology demonstrations - Open source software that provides a solution without a problem or a set of poorly defined problems. Sometimes they are called bottom up software, since they are developed around a technical capability rather than a solution to a problem. These are the software packages that  get installed, elicit a few &#8216;cool&#8217; responses, and then are ignored or un-installed.</p></blockquote>
<p>As i said above, there are exceptions to these two categories, but not many (statistically).  The last category is what we are all shooting for:</p>
<blockquote><p>(c) Innovative and unique solutions - Open source software that solves a non-obvious problem. The solution fits the problem, and does so with minimal effort, and becomes indispensible.</p></blockquote>
<p>As i stated, the last category is the holy grail of applications, and the best most of us shoot for is a good Me-Too product. In any case, we should look at a methodology that may help us develop more high quality (a) and maybe even a few (c) products for Maemo.<br />
<u><strong>Maemo / 770 Characterization<br />
</strong></u></p>
<p>The use case methodology is particularly applicable to the 770 / Maemo package. First we look at the 770 device and do a compare contrast to other products it can be compared to. From that we can make the following assessments.</p>
<p>(a) Display - There are many handheld compute devices and large screen mobile phones. However, the 770 display is at least 2x any other mobile device (of merit).</p>
<p>(b) Wireless connectivity - With both bluetooth and wifi, and relatively easy pairing with a cell phone as a data link, it is truly a portable internet device.</p>
<p>(c) Keyboard - The lack of a physical keyboard narrows down the application or use models, but the availability / capability of pairing with a bluetooth keyboard implies a separate implementation model.</p>
<p>(d) Wired NIC - The lack of a wired NIC has been pointed out in at least one or two reviews as a compromise. After use, I am hesitant to call it a compromise and probably a deliberate choice.</p>
<p>Taken cumulatively, these assessments point towards a new (perhaps) computing paradigm. Some would call it a personal area network, some may call it distributed wireless computing. This is contrary to the concept of converged computing, where every year a single device has more and more disparate features in order to replace multiple non-converged devices.</p>
<p>In the distributed wireless computing paradigm, each node or device should serve a small set of logical functions. These nodes would communicate with the other nodes in a coherent manner in order to comprise a system. Examples are a nodes in this type of a system would include a (a) keyboard (for user I/O) (b) display / touchscreen for user interface, (c) network / internetworking through WLAN or cellular data link, (d) GPS bluebox (bluetooth function with no physical I/O) for positional information.</p>
<p><u><strong>Use Case Characterization </strong></u></p>
<p>Given that the 770 fits this model of use, we still have to compare it to other devices in this space. Examples include the HTC mobile phones or the Treos.</p>
<p>If we posit that the most signficant feature of the 770 is the display (in this space) we should look to use models that are primarily visual. Obvious examples include</p>
<ol>
<li>Ebook Reader - The popularity of FBReader lends credability to this example. Evince is much better than the built in PDF reader, but could be better with large files. Both are on my A-list of maemoapps.</li>
<li>Video Player - We all know this, and we wish the native player was much better than it is. Look at what has been done on a Treo with TCPMP. So much more could be done on the 770.</li>
<li>Instant messaging - with external keyboard.</li>
<li>Remote Managment interface - This has been touched just a little bit in the user community. As we speak there are more and more wifi or networked devices in the enterprise and in home applications. Examples inlclude the Linksys Tilt / Pan / Zoom WiFi video camera at $300. There are lighting control systems, home control systems, and soon (if not already), home entertainment systems that are WiFi / ethernet managable. So rather than a number of wireless remote controls for you garage door, security system, etc, you could have a wifi controlled access point on your 770. Or a way to turn off the lights in your house with one button in your pocket.</li>
</ol>
<p>I have not really addressed the use case model yet, but I am out of time for now. In the next segment, i will discuss some about the classes of users that we target these use cases at. Some people would call that demographics, but they would be wrong.</p>
<p>Later segments will include discussions on Enterprise Architecture and how it is relevent everywhere, not just the enterprise.</p>
<p>got to go</p>
<p>ubergEEk</p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/06/06/top-down-software-developmentpart-1/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Maemo 2.x Wishlist</title>
		<link>http://maemotalk.feelslikeburning.com/2006/06/05/maemo-2x-wishlist/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/06/05/maemo-2x-wishlist/#comments</comments>
		<pubDate>Mon, 05 Jun 2006 20:02:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/06/05/maemo-2x-wishlist/</guid>
		<description><![CDATA[I know it is too late for a wishlist, but the 770 really needs the following (IMO):

Lightweight browser - This is supposed to be an internet tablet. The heaviest builtin application is the browser and it is the only one that has given me &#8216;memory low&#8217; complaints. Oh Mimimo, where art thou?
Better PDF reader - [...]]]></description>
			<content:encoded><![CDATA[<p>I know it is too late for a wishlist, but the 770 really needs the following (IMO):</p>
<ol>
<li>Lightweight browser - This is supposed to be an internet tablet. The heaviest builtin application is the browser and it is the only one that has given me &#8216;memory low&#8217; complaints. Oh Mimimo, where art thou?</li>
<li>Better PDF reader - The current one is paged based, and evince supports continuous scrolling (much better-but evince doesn&#8217;t handle large files well). Since a significant role the 770 serves for me is ebook reader, and all of my work related content is PDF, this is key.</li>
<li>IM client - But we know that is coming already.</li>
<li>Lightweight IMAP client - becoming less important as web email portals are getting better.</li>
<li>A really performant video player - Take some hints from the guys that did TCPMP. They managed to turn a treo into a video playing device. It is just amazing. The 770 hardware should be capable of so much more.</li>
<li>Better memory management in all applications</li>
<li>Package manager that supports pre / post script execution. Really.</li>
</ol>
<p>Anyway - Just my rant for the day. Please - no flamewars.<br />
ubergEEk</p>
<ol />
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/06/05/maemo-2x-wishlist/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hypothetical MaemoMapper Basemap Scripts</title>
		<link>http://maemotalk.feelslikeburning.com/2006/06/02/hypothetical-maemomapper-basemap-scripts/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/06/02/hypothetical-maemomapper-basemap-scripts/#comments</comments>
		<pubDate>Fri, 02 Jun 2006 18:51:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[googlemaps]]></category>

		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/06/02/hypothetical-maemomapper-basemap-scripts/</guid>
		<description><![CDATA[Based on my earlier post about hosting a Google maptile basemap, it is clear to me that i should really avoid posting anything that may be licensed, no matter how good my intentions.
But many expressed interest in the scripts. I won&#8217;t post the scripts but will have a discussion on what interesting things i found [...]]]></description>
			<content:encoded><![CDATA[<p>Based on my earlier post about hosting a Google maptile basemap, it is clear to me that i should really avoid posting anything that may be licensed, no matter how good my intentions.</p>
<p>But many expressed interest in the scripts. I won&#8217;t post the scripts but will have a discussion on what interesting things i found in tthe process of developing these scripts.</p>
<p><u><strong>GoogleMap Tiles </strong></u></p>
<p>Google maps are really just a series of square tiles for 17 zoom levels, arranged in x/y quadrants.</p>
<ul>
<li>zoom=17 / x=0 / y=0 : The whole world</li>
<li>zoom=16 / x=0-1 / y=0-1 : The world divided into 4 quadrants with North America at 0,0</li>
<li>zoom=15 / x/y=0-3 : The world divided into a 4&#215;4 grid with Alaska at 0,0 (roughly)</li>
<li>zoom=14 / x/y=0-7 : should be getting obvious by now&#8230;</li>
<li>zoom=13 / x/y=0-15</li>
<li>zoom=12 / x/y=0-31</li>
<li>zoom=11 / x/y=0-63</li>
<li>zoom=10 / x/y=0-127</li>
<li>zoom=9 / x/y=0-255</li>
<li>zoom=8 / x/y=0-511</li>
<li>zoom=7 / x/y=0-1023</li>
<li>zoom=6 / x/y=0-2047</li>
<li>zoom=5 / x/y=0-4095</li>
<li>zoom=4 / x/y=0-8191</li>
<li>zoom=3 / x/y=0-16383</li>
<li>zoom=2 / x/y=0-32767</li>
<li>zoom=1 / x/y=0-65535</li>
</ul>
<p>(and i did all of those numbers in my head&#8230;.)<br />
Fundamentally each decreasing zoom level subdivides each tile at the level above into 4 quadrant tiles, and so on. So we have 1 tile at 17, 4 tiles at 16 and 2^16 squared (a crapload.. squared) at level 1.</p>
<p><u><strong>latitude / longitude conversions</strong></u> - redacted (jan 2007) - After reading this many months later, I believe that my ability to communicate the method about the lat/long conversions was flawed and misleading.  I was trying to represent a simplified approach to the Mercator projection that Google uses, but failed. My apologies.</p>
<p><u><strong>Scale</strong></u> - redacted (jan 2007)</p>
<p><u><strong>Tile file format</strong></u> - If you take a look at the tile files stored in the MaemoMapper directory, they all have the &#8216;.jpg&#8217; extension. However, they are not jpg files, they are PNG files. That also happens to be what the GoogleMap tiles are served as, so rest easy, no conversion necessary.</p>
<p><u><strong>Directory format</strong></u> - MaemoMapper expects the tiles to be organized in a very specific manner. The upper directory name is the zoom level, and the next directory name is the longitude index (xgrid index). Each file is named as the latitude index (ygrid index). These indices correspond to the GoogleMap tile indices, so once again no conversion is necessary.</p>
<p><u><strong>Monochrome Tiles</strong></u> - After i started getting a few sets of basemaps from the server, i noticed a large number of tiles that were exactly 103 bytes. It turns out that these correspond to featureless monochromatic tiles, like the middle of the ocean. Interestingly, about 73% of the tiles at level 10 were this size. Well i considered this a real waste of file space since each one of these could be interpolated / extrapolated from higher level tiles, and each one used a file sytem block (much larger than 103 bytes). To address this issue, i wrote a script to delete all files from the directories that were less than 104 bytes.</p>
<p><u><strong>Scripts</strong></u></p>
<p>I am not going to post the scripts, the GoogleMaps tile URL, or the mapsets. I am just not interested in getting a cease and desist letter. However, I will give you these clues. The prune script is exactly 1 line of 34 characters. The bulk downloader is about 11 lines long of sloppy , trivial code with two loops.</p>
<p>If that isn&#8217;t enough for you to write your own, then i feel better about not giving guns to babies.</p>
<p>In closing, i would like to say thank you to Google for creating a resource like GoogleMaps that is so easily accessible for geeks and hackers such as ourselves. I would also like to say, that I respect the ownership of this content by Google, and think that time will tell what color this gray area will turn into eventually. Personally I feel that the Google brand benefits in value and respect by pervasively becoming a resource that is usable by open source community (eg MaemoMapper).</p>
<p>But i am <u>not</u> the final arbitor on this subject, so nuff said.</p>
<p>Disclaimer - I do not endorse or encourage anybody using the above information to aquire, absond, steal licensed intellectual property. I simply found out some information that I thought was uber-interesting enough to share.</p>
<p>License - I am placing all content of this blog posting under the creative commons license (http://creativecommons.org/)</p>
<p>ubergEEk</p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/06/02/hypothetical-maemomapper-basemap-scripts/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Maemo Mapper Basemaps - Should I provide / host them?</title>
		<link>http://maemotalk.feelslikeburning.com/2006/05/31/maemo-mapper-basemaps-should-i-provide-host-them/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/05/31/maemo-mapper-basemaps-should-i-provide-host-them/#comments</comments>
		<pubDate>Wed, 31 May 2006 16:19:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/05/31/maemo-mapper-basemaps-should-i-provide-host-them/</guid>
		<description><![CDATA[I have been playing with the maemo mapper application (without a GPS) and have found it to be useful. Google maps has done a really impressive job of providing a 2^16 level of detail for at least a few parts of the globe. I am really looking forward to the time when it is truly [...]]]></description>
			<content:encoded><![CDATA[<p>I have been playing with the maemo mapper application (without a GPS) and have found it to be useful. Google maps has done a really impressive job of providing a 2^16 level of detail for at least a few parts of the globe. I am really looking forward to the time when it is truly global, and includes roads and cities on all the continents, not just parts of north america (currently there is no real detail below USA) and most of europe, japan. Missing are any detail in South america, africa, australia, asia, the former USSR countries, and the middle east.</p>
<p>My quandary is that on one hand the content is owned, licensed, distributed, and all rights reserved, etc on the map content (and the corresponding map tiles) by Google.  Simply stated, i don&#8217;t believe that it is legal for me to download and host these files, no matter how much I acknowledge and proclaim that Google owns them. However, on the other hand, i know that bandwidth and hosting costs. Everytime we download the same set of map tiles, Google pays for the cost of hosting and delivering the respective files. Out of respect for Google, I also feel we should do what we can to minimize this resource burden on Google.</p>
<p>Perhaps this is a bit of peeking into Pandora&#8217;s box, but I have written a script to download and correctly structure the Google map tile files for Maemo Mapper. I currently have several of the high levels in nice tar.gz files suitable for loading on the 770 as a basemap for Maemo Mapper. I even went so far as to write another script to prune out the completely monochrome files (representative of a featureless part of some ocean - 301 bytes), and then package up the remainder.<br />
The question that I throw out is this - Should I provide these base map files to the community? I do not believe that i should provide the scripts, since then we would be abusing the ownership rights and the resource rights (by providing the means for thousands of people to download wholesale from the map tile server).<br />
I look forward to some comments / opinions.</p>
<p>thank you</p>
<p>ubergEEk</p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/05/31/maemo-mapper-basemaps-should-i-provide-host-them/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Updated - thttpd webserver for maemo</title>
		<link>http://maemotalk.feelslikeburning.com/2006/05/12/thttpd-webserver-for-maemo/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/05/12/thttpd-webserver-for-maemo/#comments</comments>
		<pubDate>Fri, 12 May 2006 15:50:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/05/12/thttpd-webserver-for-maemo/</guid>
		<description><![CDATA[I have repackaged the debian arm thttpd webserver for the 770. At this point it is completely functional, but the package lacks some of the niceties that I expect of finished packages. Such as a script to clean up orphan logs and pid files, or a script to create a link in the /etc/init.d directory [...]]]></description>
			<content:encoded><![CDATA[<p>I have repackaged the debian arm thttpd webserver for the 770. At this point it is completely functional, but the package lacks some of the niceties that I expect of finished packages. Such as a script to clean up orphan logs and pid files, or a script to create a link in the /etc/init.d directory or start automatically at reboot. I will get to that later.</p>
<p><img src="http://maemo.feelslikeburning.com/images/P0002192.jpg" /></p>
<p>At this point i am trying to figure out how to use this server standalone (ie when i am not internet connected). Opera keeps complaining about a lack of connection and doesn&#8217;t really seem comfortable displaying a webpage without an active connection.</p>
<p>To install the <a href="http://maemo.feelslikeburning.com/thttpd/thttpd_2.23beta1-maemo_2006may12a.deb">package </a>do the following:</p>
<p><u><strong>Install</strong></u></p>
<ol>
<li>Install the thttpd package</li>
<li>Open xterm, enter &#8217;sudo gainroot&#8217;</li>
<li>enter &#8217;su -&#8217;</li>
<li>enter &#8216;ln -s /var/lib/install/etc/init.d/thttpd /etc/init.d/thttpd&#8217;</li>
<li>enter &#8216;/etc/init.d/thttpd start&#8217; to start the server.</li>
<li>the webserver is now serving on http://127.0.0.1:8000.</li>
</ol>
<p>The configuration files are located at /var/lib/install/etc/thttpd. The server is running as user &#8216;user&#8217; and is serving to all requests and hosts - which means your 770 is externally browsable. If you want to restrict access to local only, add a &#8216;host=127.0.0.1&#8242; line to /var/lib/install/etc/thttpd/thttpd.conf.</p>
<p>Content is located at /var/lib/install/var/www and should be set to world readable.</p>
<p>For more information on the server go to <a href="http://www.acme.com/software/thttpd/">http://www.acme.com/software/thttpd/</a></p>
<p>NOTE - This is not a maemo port. Just a repackage of the debian arm thttpd package located at packages.debian.org.<br />
ubergEEk</p>
<p><strong>Update - I have found a way to create a fake connection that doesnt turn on the wifi at <a href="http://maemo.org/maemowiki/DummyIAP">http://maemo.org/maemowiki/DummyIAP</a>. It appears to work and once validated it will become part of my installation script. thanks to Andrew Barr for the quick response on the lists.</strong><br />
<font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">PS - Like everything else on this blog, use at your own risk. Just because it worked for me, does not mean I assume responsibility for anything you do.</font></font></font></font></font></font></p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/05/12/thttpd-webserver-for-maemo/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Theme Package - 14pt Fonts</title>
		<link>http://maemotalk.feelslikeburning.com/2006/04/28/theme-package-14pt-fonts/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/04/28/theme-package-14pt-fonts/#comments</comments>
		<pubDate>Fri, 28 Apr 2006 16:04:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/04/28/theme-package-14pt-fonts/</guid>
		<description><![CDATA[Following up on a post last week, I took the 4 standard themes and modified the default font to 14pts (instead of 16.75) and packaged them. When installed, they are at /var/lib/install/usr/share/themes.
Since the maemo theme manager only looks at /usr/share/themes for themes, I had to write a setup script located in /var/lib/install/usr/opt. It creates symbolic [...]]]></description>
			<content:encoded><![CDATA[<p>Following up on a post last week, I took the 4 standard themes and modified the default font to 14pts (instead of 16.75) and packaged them. When installed, they are at /var/lib/install/usr/share/themes.</p>
<p>Since the maemo theme manager only looks at /usr/share/themes for themes, I had to write a setup script located in /var/lib/install/usr/opt. It creates symbolic links, so that removing the package really removes them.</p>
<p><u><strong>Install</strong></u></p>
<ol>
<li>Install the theme package</li>
<li>Open xterm, enter &#8217;sudo gainroot&#8217;</li>
<li>enter &#8217;su -&#8217;</li>
<li>enter &#8216;cd /var/lib/install/usr/opt&#8217;</li>
<li>enter &#8216;./setup-themes-14pt.sh&#8217;</li>
<li>the themes should now be visible under the personalization applet.</li>
</ol>
<p>the package is <a title="themes-14pt.2006.04.28.deb" href="http://maemo.feelslikeburning.com/themes/themes-14pt.2006.04.28.deb">at</a></p>
<p>First note - If you are going to remove this theme package, run the setup script with the &#8216;restore&#8217; parameter. I am not sure how the 770 would react with empty theme links. It should be fine, but it has not been validated (yet).</p>
<p style="font-weight: bold">Second note - If you uninstall these themes while one of them is the active theme, it would probably brick your 770 (requiring a firmware flash).  I have verified that if you trash the active theme (for any reason), it will probably get stuck in a continuous boot cycle. (you been warned)<br />
<font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">ubergEEk</font></font></font></font></font></font></font></p>
<p><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">PS - Like everything else on this blog, use at your own risk. Just because it worked for me, does not mean I assume responsibility for anything you do. </font> </font></font> </font></font></font></p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/04/28/theme-package-14pt-fonts/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Metapackage : osso-xterm</title>
		<link>http://maemotalk.feelslikeburning.com/2006/04/27/metapackage-osso-xterm/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/04/27/metapackage-osso-xterm/#comments</comments>
		<pubDate>Thu, 27 Apr 2006 18:32:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<category><![CDATA[packaging]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/04/27/metapackage-osso-xterm/</guid>
		<description><![CDATA[First  - A metapackage is a aggregated package that contains the contents of several other packages.
Metapackages are useful if you find yourself re-installing the same packages, in the same manner often. One that screams out to be packaged for me is a osso-xterm metapackage. The quandary with all metapackages is to be both complete [...]]]></description>
			<content:encoded><![CDATA[<p>First  - A metapackage is a aggregated package that contains the contents of several other packages.</p>
<p>Metapackages are useful if you find yourself re-installing the same packages, in the same manner often. One that screams out to be packaged for me is a osso-xterm metapackage. The quandary with all metapackages is to be both complete as possible within a given context, and yet contain nothing extra. And of course have the widest possible appeal. I selected:</p>
<ul>
<li>osso-xterm</li>
<li>tiny-vim</li>
<li>slocate</li>
<li>openSSH</li>
<li>usbnet.sh</li>
</ul>
<p>In addition, i split my fixup scripts into three pieces, and rewrote them with full restore functions.</p>
<p>Firstly - If you are planning on installing this metapackage, remove any of the packages identified above. My package will overwrite them and (pkg management) confusion will result if you try to remove them afterwards.</p>
<p>The three scripts are:</p>
<ul>
<li>setup-meta-xterm-2006.04.27.sh - creates symbolic links, configures vim, openssh and allows for a complete restore (if needed).</li>
<li>automount-mmc.sh - patches the OS for automounting of a second rs-mmc partition. also includes a full restore.</li>
<li>filemgr-fixup.sh - maps the root filesystem and /MMC into the filemanager. also includes a full restore.</li>
</ul>
<p>After an install, these scripts are located in /var/lib/install/usr/opt.</p>
<p><u><strong>Installation  </strong></u></p>
<ol>
<li>remove any packages this metapackage may overwrite</li>
<li>install the xterm-metapackage</li>
<li>open xterm</li>
<li>enter &#8217;sudo gainroot&#8217;</li>
<li>enter &#8217;su -&#8217;</li>
<li>(optional) passwd setup - if you haven&#8217;t set it up already</li>
<ol>
<li>enter &#8216;passwd -l root&#8217;</li>
<li>enter &#8216;passwd root&#8217; (and set the root password)</li>
<li>enter &#8216;passwd user&#8217; (and set the user password)</li>
</ol>
<li>enter &#8216;cd /var/lib/install/usr/opt&#8217;</li>
<li>enter &#8216;./setup-meta-xterm-2006-04-27.sh&#8217; this will take a few minutes</li>
<li>(optional) enter &#8216;automount-mmc.sh&#8217; to automount a 2nd rs-mmc partition.</li>
<li>(optional) enter &#8216;filemgr-fixup.sh&#8217; to provide file manager access to your root filesystem.</li>
</ol>
<p>I have tested the script for both installation and restoral several times on my 770, but that is not a validation that they will run correctly in all scenarios.</p>
<p>The package is <a title="meta-xterm" href="http://maemo.feelslikeburning.com/metapackages/meta-xterm-2006.04.27d.deb">at</a></p>
<p><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">ubergEEk</font></font></font></font></font></font></font></p>
<p><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">PS - Like everything else on this blog, use at your own risk. Just because it worked for me, does not mean I assume responsibility for anything you do. </font> </font></font> </font></font></font></p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/04/27/metapackage-osso-xterm/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Personalizing Startup Images / BlueSun Hack</title>
		<link>http://maemotalk.feelslikeburning.com/2006/04/21/personalizing-startup-images-bluesun-hack/</link>
		<comments>http://maemotalk.feelslikeburning.com/2006/04/21/personalizing-startup-images-bluesun-hack/#comments</comments>
		<pubDate>Fri, 21 Apr 2006 19:51:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[maemo]]></category>

		<category><![CDATA[nokia770]]></category>

		<guid isPermaLink="false">http://maemotalk.feelslikeburning.com/2006/04/21/personalizing-startup-images-bluesun-hack/</guid>
		<description><![CDATA[After the first couple thousand times you reboot your 770 and look at the bland blue Nokia logo and the pair of pedophilic hands, you are thinking it is time for now startup images. It is a simple enough hack, and here are the rules.

The images must be PNG format, no larger than 800&#215;480, and [...]]]></description>
			<content:encoded><![CDATA[<p>After the first couple thousand times you reboot your 770 and look at the bland blue Nokia logo and the pair of pedophilic hands, you are thinking it is time for now startup images. It is a simple enough hack, and here are the rules.</p>
<ol>
<li>The images must be PNG format, no larger than 800&#215;480, and up to 24bit color depth.</li>
</ol>
<p>There are three images displayed at startup. These are:</p>
<ol>
<li>The first Nokia Image - Have not been able to change that. I have not dug far enough to find out where it is. I suspect it is being called as part of the kernel splash routine.</li>
<li>The second Nokia Image - /usr/share/icons/hicolor/scalable/hildon/qgn_indi_startup_nokia_logo.png. This image has the dimensions of 415&#215;68.</li>
<li>The hands image - /usr/share/icons/hicolor/scalable/hildon/qgn_indi_nokia_hands.png. This image is 800&#215;480.</li>
</ol>
<p>I grabbed a couple of thematic images from the web</p>
<p><img title="bluesun logo" alt="bluesun logo" src="http://maemo.feelslikeburning.com/770_theme_elements/serenity_movie/bluesun_logo.png" /></p>
<p>and the second one</p>
<p><img width="649" height="480" title="serenity logo" alt="serenity logo" src="http://maemo.feelslikeburning.com/770_theme_elements/serenity_movie/serenity_logo.png" /></p>
<p>I backup the current images, and copied / renamed the new images to the appropriate directory (to replace the two original image files). The bluesun logo replaced the Nokia logo and the Serenity logo replaced the hands.<br />
After a restart, i now have a more unique set of 770 startup images.</p>
<p>NOTE - I tried padding the bluesun logo out to 800&#215;480 in order to cover the green debug text, but got a completely blank screen with that. So 780&#215;480 works and 800&#215;480 does not (For the Nokia Logo image only). Not sure why. One pixel smaller than max may be sufficient to function, but i am out of time for this today.</p>
<p><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">ubergEEk</font></font></font></font></font></font></font></p>
<p><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont"><font id="osso-TitleFont">PS - Like everything else on this blog, use at your own risk. Just because it worked for me, does not mean I assume responsibility for anything you do. </font> </font></font> </font></font></font></p>
]]></content:encoded>
			<wfw:commentRss>http://maemotalk.feelslikeburning.com/2006/04/21/personalizing-startup-images-bluesun-hack/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
