Question about differences between compiled Android and the one bundled with Dev Phone 1. Putting compiled version to device.

[szeldon]

Hi,

I've read

http://source.android.com/documentation/building-for-dream

and done all that. Now I have all this compiled for my phone but I
don't know what is a next step. I want my Dev Phone 1 to use it.

I also wonder if there's some kind of list of things that aren't
included in repositories, but bundled with the device (for instance
Gmail client as mentioned here:
http://groups.google.com/group/android-platform/browse_thread/thread/b774f9237f7dbdd/704d103d1b4e16e5?lnk=gst&q=gmail#704d103d1b4e16e5
). I want to have all standard apps on my phone.

[szeldon]

... and what about a bootloader that supports non-signed apps?

On Dec 17, 6:02 pm, szeldon <szeldon....@gmail.com> wrote:
> Hi,
>
> I've read
>
> http://source.android.com/documentation/building-for-dream
>
> and done all that. Now I have all this compiled for my phone but I
> don't know what is a next step. I want my Dev Phone 1 to use it.
>
> I also wonder if there's some kind of list of things that aren't
> included in repositories, but bundled with the device (for instance

> Gmail client as mentioned here:http://groups.google.com/group/android-platform/browse_thread/thread/...

[szeldon]

This is what I see in "mydroid/out/target/product/dream/system/
app/" (this is where default apps are stored, I think... this is a
version compiled as described here: http://source.android.com/documentation/building-for-dream
):

- AlarmClock.apk, Browser.apk, Calculator.apk, Calendar.apk,
CalendarProvider.apk, Camera.apk, Contacts.apk, Development.apk,
DownloadProvider.apk, DrmProvider.apk, Email.apk, Fallback.apk,
GlobalTime.apk, GoogleContactsProvider.apk, GoogleSearch.apk,
HTMLViewer.apk, IM.apk, ImProvider.apk, Launcher.apk,
MediaProvider.apk, Mms.apk, Music.apk, NotePad.apk,
PackageInstaller.apk, Phone.apk, Settings.apk, SettingsProvider.apk,
Snake.apk, SoundRecorder.apk, Stk.apk, SubscribedFeedsProvider.apk,
Sync.apk, TelephonyProvider.apk, Term.apk, Updater.apk,

and on device in "/system/app/":

- gtalkservice.apk, YouTube.apk, Vending.apk, Talk.apk, Maps.apk,
GoogleApps.apk, GDataFeedsProvider.apk, CalendarProvider.apk,
Calendar.apk, Browser.apk, Updater.apk, Street.apk,
TelephonyProvider.apk, SoundRecorder.apk, SetupWizard.apk, Sync.apk,
SettingsProvider.apk, Settings.apk, Phone.apk, PackageInstaller.apk,
Music.apk, Mms.apk, MediaProvider.apk, Launcher.apk, ImProvider.apk,
GoogleSearch.apk, HTMLViewer.apk, GmailProvider.apk, Gmail.apk,
FieldTest.apk, Email.apk, DrmProvider.apk, DownloadProvider.apk,
ContactsProvider.apk, Contacts.apk, Camera.apk, Calculator.apk,
Bugreport.apk, AlarmClock.apk

Am I right, that all the mentioned files, that are on the device and
aren't built basing on Android sources, are those that I have to
backup before flashing my Dev 1? If someone doesn't want to look for
differences between those two groups, there are a few:

* included on Android bundled with Dev Phone 1, but not built from
sources:
- Bugreport.apk
- ContactsProvider.apk
- FieldTest.apk
- GDataFeedsProvider.apk
- gtalkservice.apk
- GmailProvider.apk
- Gmail.apk
- GoogleApps.apk
- Maps.apk
- SetupWizard.apk
- Street.apk
- Talk.apk
- Vending.apk
- YouTube.apk
* included on Android built from sources, but not in Dev Phone 1
- Development.apk
- Fallback.apk
- GlobalTime.apk
- GoogleContactsProvider.apk
- IM.apk
- NotePad.apk
- Snake.apk
- Stk.apk
- SubscribedFeedsProvider.apk
- Term.apk

Maybe those apps are somewhere else in android tree. I don't know.

[Jason]

On DP1 but not on repo build:

> [Wed Dec 3 2008] [00:22:49] <jbq> RyeBrye: I don't know the
> exact list. I know there's the setup wizard, gmail, the contacts
> back-end, youtube, market, gtalk, the update system, and I
> must be missing some.

On G1 but not on DP1:
Voice Dialer, Amazon MP3 store (you could just extract it from a G1
update.zip), MyFaves

Not sure what you mean by a bootloader that accepts non-signed apps.
The unlocked bootloader of the DP1 can be used to flash unsigned data
directly into the MTD partitions. However, the signature checking for
actual apk files is done in Android (well after the bootloader has
done its job). It's basically just the same thing as Java's SHA1-
Digest-Manifest scheme.

[szeldon]

On Dec 17, 7:37 pm, Jason <jas...@gmail.com> wrote:
> On DP1 but not on repo build:
>
> > [Wed Dec 3 2008] [00:22:49] <jbq> RyeBrye: I don't know the
> > exact list. I know there's the setup wizard, gmail, the contacts
> > back-end, youtube, market, gtalk, the update system, and I
> > must be missing some.
>
> On G1 but not on DP1:
> Voice Dialer, Amazon MP3 store (you could just extract it from a G1
> update.zip), MyFaves
>
> Not sure what you mean by a bootloader that accepts non-signed apps.
> The unlocked bootloader of the DP1 can be used to flash unsigned data
> directly into the MTD partitions. However, the signature checking for
> actual apk files is done in Android (well after the bootloader has
> done its job). It's basically just the same thing as Java's SHA1-
> Digest-Manifest scheme.

It turns out that I didn't understand this.

[Koush]

I've noticed that building the system.img that is built for the
emulator does not include a working MapView, among a host of other
missing applications. Does the Dream build have a fully functional
Android stack? Ie, does it build exactly what ships on the Dev phone 1?

[Jean-Baptiste Queru]

There aren't enough files in the Android Open Source Project to build
the image that shipped on the Android Dev Phone 1.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

[szeldon]

On Dec 17, 10:51 pm, Jean-Baptiste Queru <j...@google.com> wrote:
> There aren't enough files in the Android Open Source Project to build
> the image that shipped on the Android Dev Phone 1.
>

So what do I have to do if I want to update my system? Basing on all
the discussions here and on other groups, I see that it's not possible
to have a fully-functional phone. Is there a plan to make all those
things public? I don't mean open-sourced, but at least downloadable,
or something. If not, is there a way to preserve all those things that
can't be build basing on Android sources? I know that I can "adb pull"
files from phone (at least some subset of those files) and that's
great, but I'd like to know the whole list of things that I have to
copy. I'd like to update my system in the future. Testing of
applications would be great with all the things that are normally on
G1.

[Koush]

Exactly: how can we reproduce the G1/Dream image using the open source
code and the files available on a real device?

From my understanding at looking at the source, it's not a simple as
just copying files over too. A lot of the API calls on Android are
stubbed out placeholders (so it can compile). Such as my initial
comment about the MapView. Those stubs would need to be removed and
the proper code/jar referenced or inserted...

[Dianne Hackborn]

There are a few issues:

(1) The G1 has bundled with it proprietary applications from a number of vendors: Google, Amazon, etc.  You need to talk with each of them about getting that code if you want to (or try pulling it off of the existing phone).

(2) The current open source tree is not exactly the same as what was shipping on the G1, which is what the dev phone is itself based on: it is a little more recent, with various work that remained to be done to separate proprietary code from open source code.  As a result, what you build is slightly different that what is on the phone and may cause problems when trying to mix and match pieces.

I don't really understand what you mean by MapView being stubbed out.  The MapView classes are part of a Google proprietary library, which is not in the open-source project.  That is why we note these as optional APIs, and applications must explicitly request them in their manifest instead of being able to expect for them to be there as part of the platform itself.  You may be able to pull the library off the phone and use it in your own system build, but no guarantees.

--
Dianne Hackborn
Android framework engineer
hac...@android.com

Note: please don't send private questions to me, as I don't have time to provide private support.  All such questions should be posted on public forums, where I and others can see and answer them.

[szeldon]

On Dec 17, 11:31 pm, "Dianne Hackborn" <hack...@android.com> wrote:
> There are a few issues:
>
> (1) The G1 has bundled with it proprietary applications from a number of
> vendors: Google, Amazon, etc.  You need to talk with each of them about
> getting that code if you want to (or try pulling it off of the existing
> phone).

Is there a list of those proprietary elements? If not, could at least
name some? I know about those .apk files described earlier in this
discussion, but what else?

>
> (2) The current open source tree is not exactly the same as what was
> shipping on the G1, which is what the dev phone is itself based on: it is a
> little more recent, with various work that remained to be done to separate
> proprietary code from open source code.  As a result, what you build is
> slightly different that what is on the phone and may cause problems when
> trying to mix and match pieces.
>
> I don't really understand what you mean by MapView being stubbed out.  The
> MapView classes are part of a Google proprietary library, which is not in
> the open-source project.  That is why we note these as optional APIs, and
> applications must explicitly request them in their manifest instead of being
> able to expect for them to be there as part of the platform itself.  You may
> be able to pull the library off the phone and use it in your own system
> build, but no guarantees.
>
> On Wed, Dec 17, 2008 at 2:16 PM, Koush <kou...@gmail.com> wrote:
>
> > Exactly: how can we reproduce the G1/Dream image using the open source
> > code and the files available on a real device?
>
> > From my understanding at looking at the source, it's not a simple as
> > just copying files over too. A lot of the API calls on Android are
> > stubbed out placeholders (so it can compile). Such as my initial
> > comment about the MapView. Those stubs would need to be removed and
> > the proper code/jar referenced or inserted...
>
> --
> Dianne Hackborn
> Android framework engineer

> hack...@android.com

[Dianne Hackborn]

On Wed, Dec 17, 2008 at 2:43 PM, szeldon <szeldon.com@gmail.com> wrote:

Is there a list of those proprietary elements? If not, could at least
name some? I know about those .apk files described earlier in this
discussion, but what else?

I couldn't give you a comprehensive list, off-hand.  I don't even know exactly what is on that particular system build, such as whether T-Mobile's apps like myFaves are on it.

--
Dianne Hackborn
Android framework engineer

hac...@android.com

[Jason]

If your goal is just to get all the functionality of the G1 on your
DP1, it may be possible to just flash a G1 update onto the DP1.

* Add DP1's fingerprint to the first assertion in update-script or
just remove that line completely.
* adb pull recovery.img from your DP1 and replace the one in the G1
update file with it.
* adb pull the otacerts.zip and cacerts.bks files from DP1 and replace
the ones in the G1 update with them.
* Resign the update file with the test keys.

After flashing that you'd have a system partition for all intents and
purposes identical to a G1. Theoretically anyway. Maybe someone from
the Android team could confirm whether this would be a workable hack?
I don't have a DP1 to try it out on, so try it at your own peril!

Regards,
Jason

[JS]

Hi,

So what's the consensus? I made some changes to Intent.java (I added
more debugging for extras) and recompiled the whole tree. Can I
install this new image on my DP1?

Thanks.

[Jinjun]

Hi,

I tried to use fastboot to flash system.img to /dev/mtd/mtd3 since I
have fastboot bootloader installed on my G1, I have tried commands as
the following,

1)fastboot flash /dev/mtd/mtd3 system.img
2)fastboot flash /system system.img
3)fastboot flash /dev/block/mtdblock3 system.img

It shows the sending is OKAY but writing failed because partition does
not exist. Also, between each command, it never come out on sending
and I have unpluged my device in order to try different name for the
desired partition.

Is it OKAY for me to flash myown system.img and keep bootloader,
kernel, data and everything else that come with my G1 and ADP1? I have
both of them.
Thanks,

Jinjun

> hack...@android.com

[David Turner]

Maybe I'm istaken, but I don't think that the bootloader that fastboot talks to is running linux.
which means you cannot use paths like /dev/mtd/mtd3 or /system to specify which partition to reflash

[Jason]

Correct. The partitions have names for using with flashboot:

splash1
splash2
recovery
boot
system
cache
userdata
radio
hboot

This should work:
fastboot flash system system.img

On Dec 20, 9:12 pm, "David Turner" <di...@android.com> wrote:
> Maybe I'm istaken, but I don't think that the bootloader that fastboot talks
> to is running linux.
> which means you cannot use paths like /dev/mtd/mtd3 or /system to specify
> which partition to reflash
>

[JS]

So I can run this command on my DP1 to push the system.img
built via
http://source.android.com/documentation/building-for-dream ?

Please confirm.

Thx

[Jinjun]

Thanks,

I have successfully flashed my own system.img to ADP1 and G1.

Reboot ADP1, I have the home menu. However, the bluetooth can not be
turned on. When Google released SDK1, it stated that Bluetooth is not
supported. Is there anyway or configuration that I can enable
Bluetooth?

Reboot G1, the phone get stuck with Android Robot and home menu never
show up. Any idea on the reason of different behaviors?

Finally, I forgot to save the original system.img. Anywhere I can
download that image and restor it?

Thanks for help.

Jinjun

On Dec 21, 12:28 am, Jason <jas...@gmail.com> wrote:

> > > > forums, where I and others can see and answer them.- Hide quoted text -
>
> - Show quoted text -

[Jason]

This tool should be useful for fastboot flashing:

Nandroid v2.0 - Full NAND backup and restore tool
http://forum.xda-developers.com/showthread.php?t=459830

[Disconnect]

Google hasn't got an official image out, but JF created an update.zip that can be used (just open it up and use fastboot boot boot.img ; fastboot system system.img ; fastboot userdata userdata.img ; fastboot recovery recovery.img ; fastboot reboot)

(http://www.gotontheinter.net/content/android-dev-phone-1-software-image has the image. http://www.gotontheinter.net/fastboot has a cheat sheet for using fastboot.)

[Eric]

The ADP1_StockSystem_v1.0.zip file does not contain the
individual .img files.

It seems to be geared toward a t-mobile "update.zip" method of
flashing.

Are the stock ADP1 image files available anywhere in case we people
would like to re-flash the original ADP1 firmware using the fastboot
method?

On Dec 21, 7:22 pm, Disconnect <dc.disconn...@gmail.com> wrote:
> Google hasn't got an official image out, but JF created an update.zip that
> can be used (just open it up and use fastboot boot boot.img ; fastboot
> system system.img ; fastboot userdata userdata.img ; fastboot recovery
> recovery.img ; fastboot reboot)
>
> (http://www.gotontheinter.net/content/android-dev-phone-1-software-imagehas

> the image.http://www.gotontheinter.net/fastboothas a cheat sheet for using

[Jinjun]

Hi,

Follow the instruction on the following URL
http://source.android.com/documentation/building-for-dream

On mydroid, do make and the images will be placed in out/target/
product/dream

fastboot flash system system.img,
fastboot flash userdata userdata.img,
fastboot reboot,

G1 or ADP1 will run the code compiled by you.

I still have one problem, the Bluetooth device can not be turn on. The
SDK released by Google does not support Bluetooth. Is there any way to
compile the code with Bluetooth functionality?

Thanks for help.

Jinjun

On Dec 21, 9:22 pm, Eric <ekrat...@gmail.com> wrote:
> The ADP1_StockSystem_v1.0.zip file does not contain the
> individual .img files.
>
> It seems to be geared toward a t-mobile "update.zip" method of
> flashing.
>
> Are the stock ADP1 image files available anywhere in case we people
> would like to re-flash the original ADP1 firmware using the fastboot
> method?
>
> On Dec 21, 7:22 pm, Disconnect <dc.disconn...@gmail.com> wrote:
>
>
>
> > Google hasn't got an official image out, but JF created an update.zip that
> > can be used (just open it up and use fastboot boot boot.img ; fastboot
> > system system.img ; fastboot userdata userdata.img ; fastboot recovery
> > recovery.img ; fastboot reboot)
>

> > (http://www.gotontheinter.net/content/android-dev-phone-1-software-ima...
> > the image.http://www.gotontheinter.net/fastboothasa cheat sheet for using

> > > > - Show quoted text -- Hide quoted text -

[Eric]

Hello,

I have built and flashed the latest firmware from the repo (as of 2
hours ago) via fastboot on my ADP1.

However, cupcake was merged a few days ago, and many things do not
work (although many of the improvements on the working stuff look
good.)

I did not make a backup of my stock ADP1 images, thinking they were
available in JF's file at http://www.gotontheinter.net/content/android-dev-phone-1-software-image.

I was wondering if anybody was more careful than I was and actually
backed of their stock ADP1 images and was willing to share them.

On Dec 22, 12:31 am, Jinjun <jinjunl...@gmail.com> wrote:
> Hi,
>

> Follow the instruction on the following URLhttp://source.android.com/documentation/building-for-dream

> > > the image.http://www.gotontheinter.net/fastboothasacheat sheet for using

[Nick Pelly]

On Sun, Dec 21, 2008 at 4:06 PM, Jinjun <jinju...@gmail.com> wrote:
>
> Thanks,
>
> I have successfully flashed my own system.img to ADP1 and G1.
>
> Reboot ADP1, I have the home menu. However, the bluetooth can not be
> turned on.

Sounds like you need to flash a boot.img to match your system.img

boot.img contains the kernel. We changed the kernel interface to turn
bluetooth power on just after 1.0. You can confirm this is the issue
by looking for an error about
/sys/module/board_trout/parameters/bluetooth_power_on not existing in
logcat during boot. If this is the issue try flashing a boot.img to
match system.img

If this is not the issue, there is likely some other error in logcat
that will tell you why Bluetooth is not working.

adb logcat is your friend for debugging issues like this.

> When Google released SDK1, it stated that Bluetooth is not supported.

Read our announcement. We clearly said Bluetooth is supported by the
platform, but we don't have API's in the SDK.

SDK support != Feature support

Nick Pelly
Android Systems Engineer

[Jinjun]

Thanks,
I could not find the error message of bluetooth_power_on on the log.
I did insert some log message in SystemServer.java where Bluetooth
service is added. It started Bluetooth service. However, the
Settins.System.getInt() returns a value of 0 and therefore the device
is not enabled.
Another question, if I flash boot.img to the phone, will the
bootloader be changed?


Jinjun

On Dec 22, 10:25 am, Nick Pelly <npe...@google.com> wrote:

[Jinjun]

Thanks,
I could not find the error message of bluetooth_power_on on the log.
I did insert some log message in SystemServer.java where Bluetooth
service is added. It started Bluetooth service. However, the
Settins.System.getInt() returns a value of 0 and therefore the device
is not enabled.
Another question, if I flash boot.img to the phone, will the
bootloader be changed?

Jinjun




On Dec 22, 10:25 am, Nick Pelly <npe...@google.com> wrote:

[Koush]

I wrote up a walkthrough on how to build and deploy to the device:
http://www.koushikdutta.com/2008/12/building-android-source-and-deploying.html

I had the same issue with Bluetooth not working in the current build.

[Jinjun]

Hi Nick,

There is a configuration setting BOARD_HAVE_BLUETOOTH, which has been
checked in frameworks/base/core/jni/Android.mk & system/bluetooth/
bluedroid/Android.mk. However, I can not see whether this flag has
been set. If needed, where should be the appropriate place to set this
flag?
Thanks,

Jinjun

On Dec 22, 2:46 pm, Koush <kou...@gmail.com> wrote:
> I wrote up a walkthrough on how to build and deploy to the device:http://www.koushikdutta.com/2008/12/building-android-source-and-deplo...

[Nick Pelly]

On Mon, Dec 22, 2008 at 4:06 PM, Jinjun <jinju...@gmail.com> wrote:
>
> Hi Nick,
>
> There is a configuration setting BOARD_HAVE_BLUETOOTH, which has been
> checked in frameworks/base/core/jni/Android.mk & system/bluetooth/
> bluedroid/Android.mk. However, I can not see whether this flag has
> been set. If needed, where should be the appropriate place to set this
> flag?
> Thanks,

This is a compile time option. You should set it to true in your
BoardConfig.mk. And yes you definitely need this set.

[Jinjun]

Just did that on vendor/htc/dream/BoardConfig.mk, however, it bombed
out in frameworks/base/core/jni/
android_server_BluetoothDeviceService.cpp because no file bluedroid/
bluetooth.h.
Will try to resolve this tonight.
Thanks,

Jinjun

On Dec 22, 4:11 pm, Nick Pelly <npe...@google.com> wrote:

> >> I had the same issue with Bluetooth not working in the current build.- Hide quoted text -

[homestah]

Jinjun,

How did you get your source to compile? I've been trying but I keep
on getting errors from AudioHardware.cpp.

Thanks.

On Dec 21, 9:31 pm, Jinjun <jinjunl...@gmail.com> wrote:
> Hi,
>

> Follow the instruction on the following URLhttp://source.android.com/documentation/building-for-dream

> > > the image.http://www.gotontheinter.net/fastboothasacheat sheet for using

[Jinjun]

I am building the source code on an Ubuntu8.04 virtual machine and
follow the procedures described in the following URL
http://source.android.com/documentation/building-for-dream
Make sure that vendor directory in in your mydroid directory.

> > > > the image.http://www.gotontheinter.net/fastboothasacheatsheet for using

[Jinjun]

Hi Nick,

I have done the following in order to build the source code after I
added BOARD_HAVE_BLUETOOTH := true in vendor/htc/dream/BoardConfig.mk,
1) Create a directory bluedroid in external/dbus and copy /system/
bluetooth/bluedroid/include/bluedroid/bluetooth.h to that directory
2) Modified system/bluetooth/bluedroid/bluetooth.c, change #include
<bluedroid/bluedroid.h> to #include <include/bluedroid/bluedroid.h>
The compilation finished. I then loaded system.img and userdata.img to
ADP1, still have the same problem with Bluetooth. Settins.System.getInt
() returns a value of 0 and the device is not enabled.
I then flashed boot.img to boot and now the phone stuck with Android
Robot. Build dream became building nightmare. :(
I appreciate if you can help me to resolve this issue.
Thanks,

Jinjun

On Dec 22, 4:11 pm, Nick Pelly <npe...@google.com> wrote:

> >> I had the same issue with Bluetooth not working in the current build.- Hide quoted text -

[Nick Pelly]

Hi Jinjun,

On Mon, Dec 22, 2008 at 11:25 PM, Jinjun <jinju...@gmail.com> wrote:
>
> Hi Nick,
>
> I have done the following in order to build the source code after I
> added BOARD_HAVE_BLUETOOTH := true in vendor/htc/dream/BoardConfig.mk,
> 1) Create a directory bluedroid in external/dbus and copy /system/
> bluetooth/bluedroid/include/bluedroid/bluetooth.h to that directory
> 2) Modified system/bluetooth/bluedroid/bluetooth.c, change #include
> <bluedroid/bluedroid.h> to #include <include/bluedroid/bluedroid.h>
> The compilation finished.

We fixed that problem a couple of weeks ago, looks like the cupcake
merge broke it again. You found a workaround. The correct solution is
to fix the include path in Android.mk's

> I then loaded system.img and userdata.img to
> ADP1, still have the same problem with Bluetooth. Settins.System.getInt
> () returns a value of 0 and the device is not enabled.

That is normal, this is just where we persist if BT should be on/off
across reboot.

> I then flashed boot.img to boot and now the phone stuck with Android
> Robot.

Logs please.

Nick

[homestah]

I followed those instructions as well but the compiler is giving me
errors.

I am compiling in Mac OSX, but I don't think that is the problem
because others have mentioned that they had to modify a few header
files for the AudioHardware.cpp in order to get it working. Did you
have to do the same as well?

On Dec 22, 11:15 pm, Jinjun <jinjunl...@gmail.com> wrote:
> I am building the source code on an Ubuntu8.04 virtual machine and

> follow the procedures described in the following URLhttp://source.android.com/documentation/building-for-dream

> > > > > the image.http://www.gotontheinter.net/fastboothasacheatsheetfor using

[Jinjun]

Hi Nick,

How can I turn on the Bluetooth? That is what we want to do.

The phone is stuck in Android screen, probably just load the boot
logo, therefore no adb shell is available.

Thanks,

Jinjun

On Dec 22, 11:58 pm, Nick Pelly <npe...@google.com> wrote:
> Hi Jinjun,
>

[Jinjun]

No, I did not modify anything except in my reply to Nick last night.

[JesusFreke]

I was playing around with this a bit tonight and figured out how to
get bluetooth working with the current G1 builds: You need to revert
commit "124e9edf063190b511c53d697711c7a5cf42dbbb" in the kernel/msm
repo.

http://android.git.kernel.org/?p=kernel/msm.git;h=124e9edf063190b511c53d697711c7a5cf42dbbb

so "git revert 124e9edf063190b511c53d697711c7a5cf42dbbb" should do the
trick.

It appears this commit changes how the bluetooth chip is turned off
and on. But it doesn't work with the current G1 builds since they are
still using the old method - the bluetooth_power_on parameter, which
this commit removes.

JesusFreke


On Dec 22, 4:46 pm, Koush <kou...@gmail.com> wrote:
> I wrote up a walkthrough on how to build and deploy to the device:http://www.koushikdutta.com/2008/12/building-android-source-and-deplo...