Build source question
Alberich de megres
I have a Samsung Vibrant (T-mobile version), And now I wanted to start
developing for the phone (some apps, and test new kernels)
I downloaded the source with repo, choosen the combo for full crespo
eng, and builded the SDK.
Also readed the doc on android web page, but or some parts doesn't
seems up to date or I am doing something really wrong.
Then I have 2 questions:
1) what about this command? partner_setup generic
On android web page -> porting -> build system they talk about it but
I cannot find it.
2) When selecting a combo to build, I select crespo, for simulator,
and a debug eng. but them make -j4 PRODUCT-full_crespo-eng I get an
error:
make: *** No rule to build target `build/core/prelink-linux-x86.map',
needed by `out/debug/host/linux-x86/pr/crespo/symbols/system/lib/libjni_latinime.so'.
Stop
What am I doing wrong? What I want to do is compile a kernel for the
vibrant phone, and after that use it on the emulator.
Thanks!!
Albert
Jean-Baptiste Queru
-There's no support in AOSP for that specific phone, so eventually
you're going to be running into trouble.
-It's very possible that the command in question doesn't exist any
more. I'm not familiar with that part of the documentation, though.
-The simulator is a very special build configuration that attempts to
run parts of Android into an single process on a linux x86 host. It
doesn't mix-and-match with other build configurations.
-What you're really looking for is the following sequence of commands:
source build/envsetup.sh
lunch full_crespo-eng
make -j4
At that point though you won't be able to do anything useful with the
result unless you have a Nexus S to flash this on.
JBQ
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Alberich de megres
I understand AOSP doesn't support that phone. I only want to play with
images before start coding. I'm really a newbie on android.
But at some point I should be able to test my image on the emulator
isn't it? Before flash it on the phone. Am I wrong?
two posible scenarios:
- If i want to test new apps on froyo to my phone
- Or try to make new patches and test them
Also the generic build of the simulator uses a kernel older than the eclair one.
Thanks!
Jean-Baptiste Queru
S is an ARMv7 build and the emulator only emulates ARMv5.
JBQ
On Thu, Jan 13, 2011 at 7:55 AM, Alberich de megres
Alberich de megres
as far as i remenber nexus S is prety much the same hard than vibrant
S.
On the other hand, If I want to test the app i'm developing on froyo
for that I can use the emulator ins't it?
Jean-Baptiste Queru
"full_crespo-eng". That'll build a configuration tuned for the
emulator (ARMv5, emulator drivers).
JBQ
On Thu, Jan 13, 2011 at 8:20 AM, Alberich de megres
Alberich de megres
My question is if the only way to test is using the phone, even if
it's not a ADP.
Jean-Baptiste Queru
beginning of 2010) and Nexus S can be unlocked and flashed with
straight AOSP builds.
The only way to test a passion-specific build is on actual passion
hardware, and the only way to test a crespo-specific build is on
actual crespo hardware.
JBQ
On Thu, Jan 13, 2011 at 8:32 AM, Alberich de megres
Alberich de megres
One last question, offtopic, for the kernel developing there's a list
of issues? or some other place a part the android+kernel list to track
current work/bug?
thanks once again
Jean-Baptiste Queru
related to common Android-specific drivers, and possibly to the kernel
drivers that are specific to the emulator, Nexus One, and Nexus S.
For questions about porting Android to other devices, android-porting
is best. Questions that aren't android-specific can go to the relevant
upstream discussion forums, of course (e.g. lkml).
JBQ
On Thu, Jan 13, 2011 at 9:27 AM, Alberich de megres
Alberich de megres
you really help me :)
tl
assuming that I want to choose crespo when
building for Nexus S.
Thanks
Jean-Baptiste Queru
-b android-2.3.1_r1 ; repo sync)
You have 3 options for the proprietary drivers:
-Not using any and running a pure open-source build. This prevents you
from using the cell network, BT/wifi, gps, 3D graphics, compass. You
don't need to do anything in that case.
-Using the officially distributed drivers: download
http://dl.google.com/dl/android/aosp/imgtec-crespo-grh78-12c7db93.tgz
and extract it at the top of your source tree. execute the script,
agree to the license, and you have 3D graphics. No other drivers are
currently available.
-Using drivers extracted from your device:
after building adb, run "./extract-files.sh" from
device/samsung/crespo with adb enabled on your Nexus S. You're
responsible for making sure that you're allowed to do that.
Configure your build:
source build/envsetup.sh
lunch full_crespo-userdebug
rm -rf out # necessary if you switch between driver options
make
Unlock your Nexus S bootloader if you haven't already done so:
adb reboot bootloader (or press-and-hold VolUp while powering up).
# make sure that your device has the JK1 bootloader and the JK8
baseband to use with 2.3.1.
fastboot oem unlock # this wipes your device, for security reasons
Flash your build:
fastboot flashall
You can lock your device back from the bootloader: fastboot oem lock
WARNING: THERE IS CURRENTLY NO OFFICIAL WAY TO RETURN TO THE FACTORY SYSTEM.
JBQ
Kolja Dummann
2011/1/13 Alberich de megres <alber...@gmail.com>:
> So the only way will be use the phone? even if it's not the nexus S,
> as far as i remenber nexus S is prety much the same hard than vibrant
> S.
don't even flash or try to boot a Nexus S Kernel on you phone, just
because the CPU is the same it doesn't mean that the Phone is the
same! Only do this if have strong experience in Kernel world and
really know the differences between the devices! You can easily brick
your phone to total unrecovery. Flashlayout may differ or regulator
settings in the Kernel that will burn your hardware.
Josias Junior
userdata block.
I was really concerned with the use of flashall command, cause i
guessed (and still do not know this exactly) that if something goes
wrong during the process i will lost the nexus s phone, any chance to
recoverer the phone if anything goes wrong during the flashall
command?
Other detail is that after the flash of the new system ... all system
is in japan (including icons labels and so on). I already changed the
default language to english, however the icons labels are still in
japan (i really did not figure out how to change this part).
Any help really appreciate,
Best Regards,
Josias Junior.
On Jan 13, 6:09 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Start from the android-2.3.1_r1 source tree, which is GRH78 (repo init
> -b android-2.3.1_r1 ; repo sync)
>
> You have 3 options for the proprietary drivers:
>
> -Not using any and running a pure open-source build. This prevents you
> from using the cell network, BT/wifi, gps, 3D graphics, compass. You
> don't need to do anything in that case.
>
> agree to the license, and you have 3D graphics. No other drivers are
> currently available.
>
> -Using drivers extracted from your device:
> afterbuildingadb, run "./extract-files.sh" from
>
> Configure your build:
> source build/envsetup.sh
> lunch full_crespo-userdebug
> rm -rf out # necessary if you switch between driver options
> make
>
> baseband to use with 2.3.1.
> fastboot oem unlock # this wipes your device, for security reasons
>
> Flash your build:
> fastboot flashall
>
> You can lock your device back from the bootloader: fastboot oem lock
>
> WARNING: THERE IS CURRENTLY NO OFFICIAL WAY TO RETURN TO THE FACTORY SYSTEM.
>
> JBQ
>
> > How do I flash a AOSP build on a Nexus S. Also am I correct in
> > assuming that I want to choose crespo when
> > Thanks
>
> > On Jan 13, 11:40 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >> Retail Nexus Ones (the ones that were sold directly by Google in the
> >> beginning of 2010) and Nexus S can be unlocked and flashed with
> >> straight AOSP builds.
>
> >> The only way to test a passion-specific build is on actual passion
> >> hardware, and the only way to test a crespo-specific build is on
> >> actual crespo hardware.
>
> >> JBQ
>
> >> On Thu, Jan 13, 2011 at 8:32 AM, Alberich de megres
>
> >> <alberich...@gmail.com> wrote:
> >> > Sorry if I miss explained, I understood this part.
> >> > My question is if the only way to test is using the phone, even if
> >> > it's not a ADP.
>
> >> > On Thu, Jan 13, 2011 at 5:26 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>>>>>> To unsubscribe from this group, send email to
> >> >>>>>>> android-buildi...@googlegroups.com
> >> >>>>>>> For more options, visit this group at
> >> >>>>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>>>> --
> >> >>>>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>>>> Software Engineer, Android Open-Source Project, Google.
>
> >> >>>>>> Questions sent directly to me that have no reason for being private
> >> >>>>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>>>> warning.
>
> >> >>>>>> --
> >> >>>>>> To unsubscribe from this group, send email to
> >> >>>>>> android-buildi...@googlegroups.com
> >> >>>>>> For more options, visit this group at
> >> >>>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>>> --
> >> >>>>> To unsubscribe from this group, send email to
> >> >>>>> android-buildi...@googlegroups.com
> >> >>>>> For more options, visit this group at
> >> >>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>> --
> >> >>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>> Software Engineer, Android Open-Source Project, Google.
>
> >> >>>> Questions sent directly to me that have no reason for being private
> >> >>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>> warning.
>
> >> >>>> --
> >> >>>> To unsubscribe from this group, send email to
> >> >>>> android-buildi...@googlegroups.com
> >> >>>> For more options, visit this group at
> >> >>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>> --
> >> >>> To unsubscribe from this group, send email to
> >> >>> android-buildi...@googlegroups.com
> >> >>> For more options, visit this group at
> >> >>>http://groups.google.com/group/android-building?hl=en
>
> >> >> --
> >> >> Jean-Baptiste M. "JBQ" Queru
> >> >> Software Engineer, Android Open-Source Project, Google.
>
> >> >> Questions sent directly to me that have no reason for being private
> >> >> will likely get ignored or forwarded to a public forum with no further
> >> >> warning.
>
> >> >> --
> >> >> To unsubscribe from this group, send email to
> >> >> android-buildi...@googlegroups.com
> >> >> For more options, visit this group at
> >> >>http://groups.google.com/group/android-building?hl=en
>
> >> > --
> >> > To unsubscribe from this group, send email to
> >> > android-buildi...@googlegroups.com
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/android-building?hl=en
>
> >> --
> >> Jean-Baptiste M. "JBQ" Queru
> >> Software Engineer, Android Open-Source Project, Google.
>
> >> Questions sent directly to me that have no reason for being private
> >> will likely get ignored or forwarded to a public forum with no further
> >> warning.
>
> > --
Jean-Baptiste Queru
appropriate bootloader and baseband firmware, and only touches
partitions that aren't involved in the flashing path and therefore can
always be re-flashed (i.e. boot, system, recovery, userdata, cache).
When flashing individual partitions, there's no sanity-check on
version mismatches (so you could end up with a system that doesn't
boot) and there's a risk of flashing a more sensitive partition (which
is how you can really end up with a brick). There's also a risk that
you wouldn't be flashing all partitions, and some of those work
hand-in-hand (some people discovered last month that a gingerbread
system partition doesn't run on top of a froyo boot partition, because
they weren't flashing all partitions).
I definitely recommend flashing with flashall.
As for the languages, the default language in the UI is the first one
in PRODUCT_LOCALES in the product definition.
JBQ
> You received this message because you are subscribed to the "Android Building" mailing list.
Josias Junior
steps, however when i flashed the nexus s device i m gatting the
following message
"Sorry - The application Android Live Wallpapers (process
com.android.wallpaper) has stopped unexpectedly. Please try again"
Any idea, whats is happening at Android Live Wallpapers, other
questions is what i have to do to compile the gingerbread including
the android market?
I m compiling the source under ubuntu 10.10, 64 bits, i7. Any help
really appreciate.
Best Regards,
Josias Junior
***** Steps ******
# Tools
sudo add-apt-repository "deb http://archive.canonical.com/ lucid
partner"
sudo apt-get update
sudo apt-get install curl sun-java6-jdk sun-java6-jre git ia32-libs
flex bison gnupg gperf libsdl-dev libesd0-dev libwxgtk2.6-dev zip
zlib1g-dev build-essential libncurses5-dev libc6-dev-i386 valgrind
lib32ncurses5-dev lib32z1-dev g++-multilib
sudo update-java-alternatives -s java-6-sun
curl http://android.git.kernel.org/repo > repo
chmod a+x repo
-Download android source and extract to /usr/local/android
#Build Source
1. repo init -u git://android.git.kernel.org/platform/manifest.git -b
gingerbread
2. repo sync
gpg --import
and copy this code below, press enter and ctrl+D
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
/HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
=Wi5D
-----END PGP PUBLIC KEY BLOCK-----
3. export PATH=$PATH:/usr/local/android/platform-tools
4. cd device/samsung/crespo/
5. ./extract-files.sh
6. cd ../../..
7. vi device/samsung/crespo/full_crespo.mk
PRODUCT_LOCALES := en_US en_GB
8. source build/envsetup.sh
9. lunch full_crespo-userdebug
10. vi build/core/droiddoc.mk
11.
Open: build/core/droiddoc.mk
change
html_dir_files := $(shell find $(LOCAL_PATH)/$
(LOCAL_DROIDDOC_HTML_DIR) -type f)
to
html_dir_files := $(shell find $(LOCAL_DROIDDOC_HTML_DIR) -type f)
12. (32 bits machine only)
-- build/core/main.mk
vi build/core/main.mk
change
ifneq (64,$(findstring 64,$(build_arch)))
to
ifneq (i686,$(findstring i686,$(build_arch)))
-- external/clearsilver/cgi/Android.mk
change
LOCAL_CFLAGS += -m64
LOCAL_LDFLAGS += -m64
to
LOCAL_CFLAGS += -m32
LOCAL_LDFLAGS += -m32
-- external/clearsilver/cs/Android.mk
change
LOCAL_CFLAGS += -m64
LOCAL_LDFLAGS += -m64
to
LOCAL_CFLAGS += -m32
LOCAL_LDFLAGS += -m32
-- external/clearsilver/java-jni/Android.mk
change
LOCAL_CFLAGS += -m64
LOCAL_LDFLAGS += -m64
to
LOCAL_CFLAGS += -m32
LOCAL_LDFLAGS += -m32
-- external/clearsilver/util/Android.mk
change
LOCAL_CFLAGS += -m64
LOCAL_LDFLAGS += -m64
to
LOCAL_CFLAGS += -m32
LOCAL_LDFLAGS += -m32
13. make -j8
14. adb reboot bootloader
15. ./out/host/linux-x86/bin/fastboot oem unlock
16. ./out/host/linux-x86/bin/fastboot flashall
17. ./out/host/linux-x86/bin/fastboot oem lock
> -b android-2.3.1_r1 ; repo sync)
>
> You have 3 options for the proprietary drivers:
>
> -Not using any and running a pure open-source build. This prevents you
> from using the cell network, BT/wifi, gps, 3D graphics, compass. You
> don't need to do anything in that case.
>
> agree to the license, and you have 3D graphics. No other drivers are
> currently available.
>
> -Using drivers extracted from your device:
> device/samsung/crespo withadbenabled on your Nexus S. You're
>
> Configure your build:
> source build/envsetup.sh
> lunch full_crespo-userdebug
> rm -rf out # necessary if you switch between driver options
> make
>
> baseband to use with 2.3.1.
> fastboot oem unlock # this wipes your device, for security reasons
>
> Flash your build:
> fastboot flashall
>
> You can lock your device back from the bootloader: fastboot oem lock
>
> WARNING: THERE IS CURRENTLY NO OFFICIAL WAY TO RETURN TO THE FACTORY SYSTEM.
>
> JBQ
>
>
>
>
>
>
>
> On Thu, Jan 13, 2011 at 12:30 PM, tl <terence.l...@gmail.com> wrote:
> > How do I flash a AOSP build on a Nexus S. Also am I correct in
> > assuming that I want to choose crespo when
> > Thanks
>
> > On Jan 13, 11:40 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >> Retail Nexus Ones (the ones that were sold directly by Google in the
> >> beginning of 2010) and Nexus S can be unlocked and flashed with
> >> straight AOSP builds.
>
> >> The only way to test a passion-specific build is on actual passion
> >> hardware, and the only way to test a crespo-specific build is on
> >> actual crespo hardware.
>
> >> JBQ
>
> >> On Thu, Jan 13, 2011 at 8:32 AM, Alberich de megres
>
> >> <alberich...@gmail.com> wrote:
> >> > Sorry if I miss explained, I understood this part.
> >> > My question is if the only way to test is using the phone, even if
> >> > it's not a ADP.
>
> >> > On Thu, Jan 13, 2011 at 5:26 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>>>>>> To unsubscribe from this group, send email to
> >> >>>>>>> android-buildi...@googlegroups.com
> >> >>>>>>> For more options, visit this group at
> >> >>>>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>>>> --
> >> >>>>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>>>> Software Engineer, Android Open-Source Project, Google.
>
> >> >>>>>> Questions sent directly to me that have no reason for being private
> >> >>>>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>>>> warning.
>
> >> >>>>>> --
> >> >>>>>> To unsubscribe from this group, send email to
> >> >>>>>> android-buildi...@googlegroups.com
> >> >>>>>> For more options, visit this group at
> >> >>>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>>> --
> >> >>>>> To unsubscribe from this group, send email to
> >> >>>>> android-buildi...@googlegroups.com
> >> >>>>> For more options, visit this group at
> >> >>>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>>> --
> >> >>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>> Software Engineer, Android Open-Source Project, Google.
>
> >> >>>> Questions sent directly to me that have no reason for being private
> >> >>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>> warning.
>
> >> >>>> --
> >> >>>> To unsubscribe from this group, send email to
> >> >>>> android-buildi...@googlegroups.com
> >> >>>> For more options, visit this group at
> >> >>>>http://groups.google.com/group/android-building?hl=en
>
> >> >>> --
> >> >>> To unsubscribe from this group, send email to
> >> >>> android-buildi...@googlegroups.com
> >> >>> For more options, visit this group at
> >> >>>http://groups.google.com/group/android-building?hl=en
>
> >> >> --
> >> >> Jean-Baptiste M. "JBQ" Queru
> >> >> Software Engineer, Android Open-Source Project, Google.
>
> >> >> Questions sent directly to me that have no reason for being private
> >> >> will likely get ignored or forwarded to a public forum with no further
> >> >> warning.
>
> >> >> --
> >> >> To unsubscribe from this group, send email to
> >> >> android-buildi...@googlegroups.com
> >> >> For more options, visit this group at
> >> >>http://groups.google.com/group/android-building?hl=en
>
> >> > --
> >> > To unsubscribe from this group, send email to
> >> > android-buildi...@googlegroups.com
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/android-building?hl=en
>
> >> --
> >> Jean-Baptiste M. "JBQ"
>
>
> read more »
Jean-Baptiste Queru
which removes hdpi. That can cause resources to go missing, which can
then cause crashes.
JBQ
> You received this message because you are subscribed to the "Android Building" mailing list.
Johan Zander
> agree to the license, and you have 3D graphics. No other drivers are
> currently available.
Nexus S is by extracting the drivers from the device (since this
method only gives you the graphics drivers)?
> WARNING: THERE IS CURRENTLY NO OFFICIAL WAY TO RETURN TO THE FACTORY SYSTEM.
unofficial way should work right? E.g.
http://www.addictivetips.com/mobile/how-to-backup-your-android-phones-boot-recovery-and-system-partition-images/
Wouldn't it be possible to restore the phone to factory settings using
a method as this?
> The simulator is a very special build configuration that attempts to run parts of Android into an single process on a linux x86 host. It doesn't mix-and-match with other build configurations.
is not supposed to compile (which it does not for me on the
android-2.3.2_r1 branch)?
/Johan
On Jan 13, 10:09 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Start from the android-2.3.1_r1 source tree, which is GRH78 (repo init
> -b android-2.3.1_r1 ; repo sync)
>
> You have 3 options for the proprietary drivers:
>
> -Not using any and running a pure open-source build. This prevents you
> from using the cell network, BT/wifi, gps, 3D graphics, compass. You
> don't need to do anything in that case.
>
> agree to the license, and you have 3D graphics. No other drivers are
> currently available.
>
> -Using drivers extracted from your device:
> after building adb, run "./extract-files.sh" from
> device/samsung/crespo with adb enabled on your Nexus S. You're
> responsible for making sure that you're allowed to do that.
>
> Configure your build:
> source build/envsetup.sh
> lunch full_crespo-userdebug
> rm -rf out # necessary if you switch between driver options
> make
>
> Unlock your Nexus S bootloader if you haven't already done so:
> adb reboot bootloader (or press-and-hold VolUp while powering up).
> # make sure that your device has the JK1 bootloader and the JK8
> baseband to use with 2.3.1.
> fastboot oem unlock # this wipes your device, for security reasons
>
> Flash your build:
> fastboot flashall
>
> You can lock your device back from the bootloader: fastboot oem lock
>
> WARNING: THERE IS CURRENTLY NO OFFICIAL WAY TO RETURN TO THE FACTORY SYSTEM.
>
> JBQ
>
> >> >>>> Actually, you can't run the Nexus S code on theemulatorbecause Nexus
> >> >>>> S is an ARMv7 build and theemulatoronly emulates ARMv5.
>
> read more »
Jean-Baptiste Queru
to extract drivers from the device. You need authorization to do that.
-assuming that you're authorized to do it, it might be possible to
perform at least a partial backup. Please don't discuss details
further on this list.
-the simulator is somewhat maintained, but it's a very specialized and
very fragile tool which is only used by a handful of people at Google.
It is likely to require the very precise environment that those people
use, which is specific to Google and isn't publicly available.
JBQ