
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Android 1.5 branch available</title>
	<atom:link href="http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-android-1-5-branch-available</link>
	<description>www.johandekoning.nl</description>
	<lastBuildDate>Tue, 17 Jan 2012 22:41:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The One</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-444</link>
		<dc:creator>The One</dc:creator>
		<pubDate>Thu, 30 Jul 2009 11:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-444</guid>
		<description>I asked myself for hundred times now what AOSP stands for?? And did you build your build alone or is it a custom build of another developer?? Where do we get this driver? Also JBQ at Google Platform group said it would be a problem with missing prorietary files.</description>
		<content:encoded><![CDATA[<p>I asked myself for hundred times now what AOSP stands for?? And did you build your build alone or is it a custom build of another developer?? Where do we get this driver? Also JBQ at Google Platform group said it would be a problem with missing prorietary files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-431</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Mon, 27 Jul 2009 20:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-431</guid>
		<description>What do you mean with the old I2C drivers. Those are part of the 2.6.27 kernel?</description>
		<content:encoded><![CDATA[<p>What do you mean with the old I2C drivers. Those are part of the 2.6.27 kernel?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justanotherdev</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-430</link>
		<dc:creator>Justanotherdev</dc:creator>
		<pubDate>Mon, 27 Jul 2009 19:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-430</guid>
		<description>I don&#039;t think the 2.6.29 Kernel has an issue with the Camera, you just have to revert to the old I2C drivers. I have the 2.6.29 Kernel working fine with the Camera on my G1 using AOSP and HTC sourced builds. Let me know if you have any questions.</description>
		<content:encoded><![CDATA[<p>I don't think the 2.6.29 Kernel has an issue with the Camera, you just have to revert to the old I2C drivers. I have the 2.6.29 Kernel working fine with the Camera on my G1 using AOSP and HTC sourced builds. Let me know if you have any questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-420</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Thu, 23 Jul 2009 22:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-420</guid>
		<description>Just another update on my last command to make my opinion more clear

With the openess of Android I don&#039;t mean the Android OS by it self. But I mean the openess of the Android Dev Phone. This is official the only phone which can be used to try out own builds but it depends on closed parts at the core level which can stop/interrupt development.</description>
		<content:encoded><![CDATA[<p>Just another update on my last command to make my opinion more clear</p>
<p>With the openess of Android I don't mean the Android OS by it self. But I mean the openess of the Android Dev Phone. This is official the only phone which can be used to try out own builds but it depends on closed parts at the core level which can stop/interrupt development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-419</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Thu, 23 Jul 2009 22:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-419</guid>
		<description>Looks like building is not that straight forward as promised. 

First there is the discussion with the branch name. It though that cupcake-release was for devices and cupcake for general development. But now cupcake automatically gets the vendor/htc/dream-open project.

Inside the dream-open project the extract-files.sh and AndroidBoard.mk are not updated as patch 10501. This way you will miss some proprietary files. 

The SdkSetup is still needed (when not using the Google Apps) to make it possible to answer/make calls. 

The Google Apps are still not part of the tree. So if you want those you still need to add those by hand. 

I think that my build procedure is sill relevant. I will check it this weekend to see where things have been changed.

I am a little bit worried about the Open Sourceness of Android on a device. Because there are rumours that the G1 is not capable of getting another update (after 2.0). With the Dev Phone this can be different because space can be allocated differently (don&#039;t know the details yet). This will probally result in a device which will not get updates from HTC for the proprietary files and the radio stack (I am not meaning the 2.0 version but after that). And then we are stuck when we want to compile a newer version and the libraries are not supplied by HTC. And also now we don&#039;t know for sure if for example the Camera issue with 2.6.29 is a kernel problem or for example inside the libqcamera.so module?

When will there be a device for which those parts will also be open sourced? Or can we develop our own kernel modules based on hardware or (probally not legal) decompiling stuff? BTW Does anybody knows what is inside the radio image?</description>
		<content:encoded><![CDATA[<p>Looks like building is not that straight forward as promised. </p>
<p>First there is the discussion with the branch name. It though that cupcake-release was for devices and cupcake for general development. But now cupcake automatically gets the vendor/htc/dream-open project.</p>
<p>Inside the dream-open project the extract-files.sh and AndroidBoard.mk are not updated as patch 10501. This way you will miss some proprietary files. </p>
<p>The SdkSetup is still needed (when not using the Google Apps) to make it possible to answer/make calls. </p>
<p>The Google Apps are still not part of the tree. So if you want those you still need to add those by hand. </p>
<p>I think that my build procedure is sill relevant. I will check it this weekend to see where things have been changed.</p>
<p>I am a little bit worried about the Open Sourceness of Android on a device. Because there are rumours that the G1 is not capable of getting another update (after 2.0). With the Dev Phone this can be different because space can be allocated differently (don't know the details yet). This will probally result in a device which will not get updates from HTC for the proprietary files and the radio stack (I am not meaning the 2.0 version but after that). And then we are stuck when we want to compile a newer version and the libraries are not supplied by HTC. And also now we don't know for sure if for example the Camera issue with 2.6.29 is a kernel problem or for example inside the libqcamera.so module?</p>
<p>When will there be a device for which those parts will also be open sourced? Or can we develop our own kernel modules based on hardware or (probally not legal) decompiling stuff? BTW Does anybody knows what is inside the radio image?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-417</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Thu, 23 Jul 2009 08:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-417</guid>
		<description>This means that cupcake-release also downloads the HTC Dream project. If that is the case they had better call the project cupcake-dream to make this clear</description>
		<content:encoded><![CDATA[<p>This means that cupcake-release also downloads the HTC Dream project. If that is the case they had better call the project cupcake-dream to make this clear</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weiguo</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-416</link>
		<dc:creator>Weiguo</dc:creator>
		<pubDate>Thu, 23 Jul 2009 06:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-416</guid>
		<description>JBQ say in the platform group http://groups.google.com/group/android-platform/browse_thread/thread/2d496adb75997d2

build for dream is straightforward, no local_manifest necessary, no patching, anybody checking

I&#039;m syncing...</description>
		<content:encoded><![CDATA[<p>JBQ say in the platform group http://groups.google.com/group/android-platform/browse_thread/thread/2d496adb75997d2</p>
<p>build for dream is straightforward, no local_manifest necessary, no patching, anybody checking</p>
<p>I'm syncing...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-412</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Wed, 22 Jul 2009 06:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-412</guid>
		<description>BTW I don&#039;t have a HTC Magic so i cannot check if this is working. I think there is a difference in hardware between those devices meaning that other drivers are needed. Can you confirm that the HTC Magic can be flashed just like a HTC Dream?</description>
		<content:encoded><![CDATA[<p>BTW I don't have a HTC Magic so i cannot check if this is working. I think there is a difference in hardware between those devices meaning that other drivers are needed. Can you confirm that the HTC Magic can be flashed just like a HTC Dream?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-411</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Wed, 22 Jul 2009 06:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-411</guid>
		<description>I still compiled the Wifi driver by my own (as described inside the blogpost). I will check out later if the correct driver is part of the source tree

Te led drivers was never part of the source tree and should still be extracted from the device</description>
		<content:encoded><![CDATA[<p>I still compiled the Wifi driver by my own (as described inside the blogpost). I will check out later if the correct driver is part of the source tree</p>
<p>Te led drivers was never part of the source tree and should still be extracted from the device</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan de Koning</title>
		<link>http://www.johandekoning.nl/index.php/2009/07/21/new-android-1-5-branch-available/comment-page-1/#comment-410</link>
		<dc:creator>Johan de Koning</dc:creator>
		<pubDate>Wed, 22 Jul 2009 06:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.johandekoning.nl/?p=314#comment-410</guid>
		<description>Did not tried out yet and I think it will not work. There are problems with the camera and I think this has something to do with the proprietary files. 

I placed a question on the Android Platform Disccusion Group about the Camera issue &lt;a href=&quot;http://groups.google.com/group/android-platform/browse_thread/thread/224666a8f79897f0&quot; rel=&quot;nofollow&quot;&gt;http://groups.google.com/group/android-platform/browse_thread/thread/224666a8f79897f0&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Did not tried out yet and I think it will not work. There are problems with the camera and I think this has something to do with the proprietary files. </p>
<p>I placed a question on the Android Platform Disccusion Group about the Camera issue <a href="http://groups.google.com/group/android-platform/browse_thread/thread/224666a8f79897f0" rel="nofollow">http://groups.google.com/group/android-platform/browse_thread/thread/224666a8f79897f0</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

