Debug capabilities depend on your build type, or more precisely some system properties which it defines, and root is not meant for production so it is a debug capability.
E.g. you will never have root access to any purchased device...
As per your test builds, unless you are doing some security penetration tests I would keep the root. From my experience non rooted androids tend to make life difficult when testing bring ups, but I don't really know your cases so that's just a thought.
On Thu, Aug 23, 2012 at 1:18 PM, Bernhard Rosenkränzer
<bernhard.rosenkranzer@linaro.org> wrote:
> On 23 August 2012 00:54, Zygmunt Krynicki <zygmunt.krynicki@linaro.org> wrote:
>>> Does "adb root" work for you?
>>
>> Where should I run it? I never had to do that with -eng builds.
>
> Just run "adb root" instead of "adb shell" on your computer.
>
> The former is supposed to give you a root shell, the latter gives you
> a shell as some user who may or may not be root (depending on the
> build type).
>
Can you give background what's the approach android takes here? e.g.
when do they give you root and when do you get a "unprivileged" shell
and why is that?
Also, does it mean that a tests build is rather a production builds
with test and we would like to have an eng+tests target?
--
Alexander Sack
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________
linaro-android mailing list
linaro-android@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-android