FYI
---------- Forwarded message ----------
From: Jean-Baptiste Queru <jbq(a)android.com>
Date: 28 August 2012 15:59
Subject: Contributions and conflict-prone areas
To: android-contrib(a)googlegroups.com
I've been looking at many Android contributions recently, which gives
be some good visibility over the difficulties in merging changes all
the way upstream into Google's internal tree.
Generally speaking, at the moment the gap between AOSP and Google's
internal master tree is unusually small, and that allows a very large
majority of contributions to merge without conflicts.
By looking at many changes, I spotted 3 areas where merges don't go
smoothly. Those areas are Bluetooth, Email, and Location, and most
changes related to those cause merge problems. Digging a bit, those
look like they've been refactored quite heavily in Google's internal
tree, which causes the conflicts. For anyone considering to contribute
in any of those 3 areas. I recommend waiting until the next major
release (and I don't have any ETA for it).
>From what I've seen, merges are uneventful in all other areas of the
Android tree.
Thanks,
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, 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.
--
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi Kejun
I see that ECM has now been committed to Jelly Bean, thanks for working
on this. :-)
However, I can't find any GUI in the 'Settings' app for editing the
ethernet connection like there was in ICS. Should there be one? Or am I
missing some configuration in my vexpress device files?
Thanks
--
Tixy
I am attempting to build Linaro's latest stable AOSP build for the
pandaboard (https://android-build.linaro.org/builds/~linaro-android/panda-master-gcc44-…).
It appears to build fine, but unfortunately when I load it on the SD
card and attempt to boot the pandaboard, I get the message:
"ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree"
I've attached the full log up through this error. I have followed the
directions from the page I linked above. Please let me know if you
need more information from me about my build environment, other logs,
etc. and I'll be happy to supply them.
Thanks!
-Aaron Lindsay
W dniu 23.08.2012 00:41, Ron Munitz pisze:
> Hi,
> Do you have ro.secure somewhere in your "getprop" ?
No, I've checked that, I also checked the privilege drop code path so
I'm sure I'm not taking it.
A hint: -tests builds run adbd as shell (or quickly drop so I could not
notice), -eng builds keep them as root.
> If ro.secure==1 you'll be defaulted to the shell user - so that's what
> you need to change (try build.prop)
build.prop is identical in both builds
>
> Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Hey
So this issue has kept me up all night today.
It seems that 'adb shell' gives me a non-root 'shell' account when using
-tests build that uses TARGET_BUILD_VARIANT=tests. I've patched this and
rebuilt but without success.
My patch and rationale is here: [1], any ideas about why it is not
working, what might be missing, etc - are welcome.
For context, adb shell needs to give me a root account for
lava-android-test to work properly.
Thanks
ZK
[1]: http://review.android.git.linaro.org/#change,2671
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/