[android-building] Re: Android 12 Released
Android 12 source code is now available. The following builds, tags, and devices are supported: - SP1A.210812.016.B2, android-12.0.0_r33, Pixel 3, Pixel 3 XL - SP1A.210812.016.C2, android-12.0.0_r34, Pixel 3, Pixel 3 XL The corresponding factory images, ota images, and proprietary binaries are available at https://developers.google.com/android/images https://developers.google.com/android/ota https://developers.google.com/android/drivers The kernel source is identical to SP1A.210812.016.A2. -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/3c1a596e-7e69-495b-9bcd-5820b2680014n%40googlegroups.com.
[android-building] Build android framework with Gradle
Hi All, I want to use Gradle to build android framework, can this be achieved? Please give some advice. Thanks -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAF%2BaDE%2Bqns%3DwbVBtbCFcuOGR2C1iS1DCc--Xjv6kjrwHgZZ_ng%40mail.gmail.com.
Re: [android-building] Backtrace in libmemunreachable
you'll need to find whatever that 30s timeout is and increase it.
On Mon, Jun 27, 2022 at 11:01 AM SHUBHAM SALUNKHE <
salunkheshubham1...@gmail.com> wrote:
> Hi,
> Thanks for solution. it worked but sometime its giving following timeout
> exception after executing command
>
> adb shell dumpsys -t 120 meminfo --unreachable
>
> Exception:-
> Applications Memory Usage (in Kilobytes):
> Uptime: 277719 Realtime: 277719
> ** MEMINFO in pid 5953 [] **
> Got IoException! java.io.IOException: Timeout
>
> in above command, -t is 120 sec. still it is exiting with above exception
> after 30 sec only. please help me in solving this exception.
>
> Thanks & Regards,
> Shubham Salunkhe
>
> On Tuesday, March 1, 2022 at 10:53:04 PM UTC+5:30 e...@google.com wrote:
>
>> the wrap.* properties are broken in AOSP right now... (they're broken in
>> S too.)
>>
>> here's the workaround to make the wrap. properties work:
>>
>> adb shell setprop dalvik.vm.force-java-zygote-fork-loop true
>> adb shell stop
>> adb shell start
>>
>> the commands you're using don't look right ... try this instead:
>>
>> adb shell setprop wrap. '"LIBC_DEBUG_MALLOC_OPTIONS=backtrace=4
>> logwrapper"'
>>
>> and then restart the app.
>>
>> On Tue, Feb 22, 2022 at 6:15 PM SHUBHAM SALUNKHE
>> wrote:
>>
>>> Hi,
>>> Thanks for reply.
>>>I have added debug statement as follows
>>> in system/memory/libmemunreachable/MemUnreachable.cpp. i giving "No. of
>>> Frames:0". that's why backtrace call is not happening. How it is possible
>>> if adb shell is giving memory leak address but backtrace frames are not
>>> available?
>>>
>>> *Debug tatement:-*
>>> ssize_t num_backtrace_frames =
>>> malloc_backtrace(reinterpret_cast(it.range.begin),
>>> leak->backtrace.frames, leak->backtrace.max_frames);
>>> MEM_ALOGI("No. of Frames: %zd",num_backtrace_frames);
>>> if (num_backtrace_frames > 0) {
>>> leak->backtrace.num_frames = num_backtrace_frames;
>>>
>>> *adb shell output:*
>>> Unreachable memory
>>> 704 bytes in 5 unreachable allocations
>>> ABI: 'arm64'
>>>
>>> 288 bytes unreachable at 7862adf450
>>>first 20 bytes of contents:
>>>7862adf450: 88 13 e8 07 00 00 00 00 9e 9f 15 08 00 00 00 00
>>>
>>>7862adf460: 2c bb 17 08 00 00 00 00 23 8a 89 08 00 00 00 00
>>> ,...#...
>>>
>>> Thanks & Regards,
>>> Shubham Salunkhe
>>> On Wednesday, February 16, 2022 at 2:52:17 AM UTC+5:30 e...@google.com
>>> wrote:
>>>
oh, and if you're on a recent AOSP build, you might want to try
cherrypicking
https://android-review.googlesource.com/c/platform/frameworks/base/+/1978990
--- the `wrap.` system properties are a bit broken atm. (the wrap.sh stuff
for apps works fine though.)
On Tue, Feb 15, 2022 at 12:40 PM enh wrote:
> you did replace `[process]` with your actual process name, right?
>
> On Tue, Feb 15, 2022 at 12:29 PM SHUBHAM SALUNKHE <
> salunkhes...@gmail.com> wrote:
>
>> Hi All,
>> I am trying to find memory leak using libmemunreachable
>> library in AOSP. i have getting following output on adb shell, but not
>> able
>> to find line number of code where memory leak present or any backtrace
>> logs
>> in adb logs. following commands are executed as mentioned in link
>>
>> .
>>
>> *Commands:-*
>> adb root
>> adb shell setprop libc.debug.malloc.program app_process
>> adb shell setprop wrap.[process] "\$\@"
>> adb shell setprop libc.debug.malloc.options backtrace=4
>> dumpsys -t 600 meminfo --unreachable [process].
>>
>> *adb shell output:-*
>> Unreachable memory
>> 704 bytes in 5 unreachable allocations
>> ABI: 'arm64'
>>
>> 288 bytes unreachable at 7862adf450
>>first 20 bytes of contents:
>>7862adf450: 88 13 e8 07 00 00 00 00 9e 9f 15 08 00 00 00 00
>>
>>7862adf460: 2c bb 17 08 00 00 00 00 23 8a 89 08 00 00 00 00
>> ,...#...
>>
>> No. of backtrace frames are 0 in debug logs. is there any
>> way to enable backtrace in adb logs or to get line no. of source code
>> from
>> above adb shell output.
>>
>> Thanks & Regards,
>> Shubham Salunkhe
>>
>> --
>> --
>> 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
>>
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "Android Buildin
[android-building] Build AOSP 11 with Google RBE service
Hi Android Building, I am following the site (https://groups.google.com/g/android-building/c/EJradKEiPl0) to build AOSP 11 with Google RBE service. I have created the service account and enabled the "Remote Build Execution API" service in Google Cloud. After setup env variables, the make always show a TLS CA cert issue. Could you show me the correct way to get the TLS CA cert for Google RBE service?Thanks! Below is env variables setup: export RBE_service=remotebuildexecution.googleapis.com:443 export RBE_tls_ca_cert=rbe.crt export RBE_use_rpc_credentials=true export GOOGLE_APPLICATION_CREDENTIALS=loyal-theater-204209-c0471ad7c674.json ... I got rbe.cert using command "openssl s_client -connect remotebuildexecution.googleapis.com:443 -showcerts" and converted to DER format, and loyal-theater-204209-c0471ad7c674.json is my service account key file. Afte make, it always output below error, seems the TLS CA cert is wrong: E0626 12:33:13.387181 10559 bootstrap.go:91] Unable to start reproxy: F0626 12:32:53.444195 10569 main.go:122] Error connecting to remote execution client: Could not create TLS config: failed to load TLS CA certificates from rbe.crt I tried several ways to get the TLS CA cert, neither works, it always show above error. Really appreciated your help on it. Thank! Regards, John -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/7644f3da-d8d8-40a6-9b87-ec679dbc0660n%40googlegroups.com.
Re: [android-building] Backtrace in libmemunreachable
Hi,
Thanks for solution. it worked but sometime its giving following timeout
exception after executing command
adb shell dumpsys -t 120 meminfo --unreachable
Exception:-
Applications Memory Usage (in Kilobytes):
Uptime: 277719 Realtime: 277719
** MEMINFO in pid 5953 [] **
Got IoException! java.io.IOException: Timeout
in above command, -t is 120 sec. still it is exiting with above exception
after 30 sec only. please help me in solving this exception.
Thanks & Regards,
Shubham Salunkhe
On Tuesday, March 1, 2022 at 10:53:04 PM UTC+5:30 e...@google.com wrote:
> the wrap.* properties are broken in AOSP right now... (they're broken in S
> too.)
>
> here's the workaround to make the wrap. properties work:
>
> adb shell setprop dalvik.vm.force-java-zygote-fork-loop true
> adb shell stop
> adb shell start
>
> the commands you're using don't look right ... try this instead:
>
> adb shell setprop wrap. '"LIBC_DEBUG_MALLOC_OPTIONS=backtrace=4
> logwrapper"'
>
> and then restart the app.
>
> On Tue, Feb 22, 2022 at 6:15 PM SHUBHAM SALUNKHE
> wrote:
>
>> Hi,
>> Thanks for reply.
>>I have added debug statement as follows
>> in system/memory/libmemunreachable/MemUnreachable.cpp. i giving "No. of
>> Frames:0". that's why backtrace call is not happening. How it is possible
>> if adb shell is giving memory leak address but backtrace frames are not
>> available?
>>
>> *Debug tatement:-*
>> ssize_t num_backtrace_frames =
>> malloc_backtrace(reinterpret_cast(it.range.begin),
>> leak->backtrace.frames, leak->backtrace.max_frames);
>> MEM_ALOGI("No. of Frames: %zd",num_backtrace_frames);
>> if (num_backtrace_frames > 0) {
>> leak->backtrace.num_frames = num_backtrace_frames;
>>
>> *adb shell output:*
>> Unreachable memory
>> 704 bytes in 5 unreachable allocations
>> ABI: 'arm64'
>>
>> 288 bytes unreachable at 7862adf450
>>first 20 bytes of contents:
>>7862adf450: 88 13 e8 07 00 00 00 00 9e 9f 15 08 00 00 00 00
>>
>>7862adf460: 2c bb 17 08 00 00 00 00 23 8a 89 08 00 00 00 00
>> ,...#...
>>
>> Thanks & Regards,
>> Shubham Salunkhe
>> On Wednesday, February 16, 2022 at 2:52:17 AM UTC+5:30 e...@google.com
>> wrote:
>>
>>> oh, and if you're on a recent AOSP build, you might want to try
>>> cherrypicking
>>> https://android-review.googlesource.com/c/platform/frameworks/base/+/1978990
>>>
>>> --- the `wrap.` system properties are a bit broken atm. (the wrap.sh stuff
>>> for apps works fine though.)
>>>
>>> On Tue, Feb 15, 2022 at 12:40 PM enh wrote:
>>>
you did replace `[process]` with your actual process name, right?
On Tue, Feb 15, 2022 at 12:29 PM SHUBHAM SALUNKHE <
salunkhes...@gmail.com> wrote:
> Hi All,
> I am trying to find memory leak using libmemunreachable
> library in AOSP. i have getting following output on adb shell, but not
> able
> to find line number of code where memory leak present or any backtrace
> logs
> in adb logs. following commands are executed as mentioned in link
>
> .
>
> *Commands:-*
> adb root
> adb shell setprop libc.debug.malloc.program app_process
> adb shell setprop wrap.[process] "\$\@"
> adb shell setprop libc.debug.malloc.options backtrace=4
> dumpsys -t 600 meminfo --unreachable [process].
>
> *adb shell output:-*
> Unreachable memory
> 704 bytes in 5 unreachable allocations
> ABI: 'arm64'
>
> 288 bytes unreachable at 7862adf450
>first 20 bytes of contents:
>7862adf450: 88 13 e8 07 00 00 00 00 9e 9f 15 08 00 00 00 00
>
>7862adf460: 2c bb 17 08 00 00 00 00 23 8a 89 08 00 00 00 00
> ,...#...
>
> No. of backtrace frames are 0 in debug logs. is there any
> way to enable backtrace in adb logs or to get line no. of source code
> from
> above adb shell output.
>
> Thanks & Regards,
> Shubham Salunkhe
>
> --
> --
> 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
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to android-buildi...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/3f5dac22-6aad-4e6a-b8
[android-building] Re: Android T Preview Released
Hi, all, Today, we pushed the kernel source for the following devices for the Android T Developer Beta 3.3. Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6, Pixel 6 Pro. Tag Project Branch android-t-beta-3.3_r0.1 device/google/coral-kernel android-msm-coral-4.14-t-beta-3 android-t-beta-3.3_r0.2 device/google/sunfish-kernel android-msm-sunfish-4.14-t-beta-3 android-t-beta-3.3_r0.3 device/google/redbull-kernel android-msm-redbull-4.19-t-beta-3 android-t-beta-3.3_r0.4 device/google/oriole-kernel android-gs-raviole-5.10-t-beta-3 bill -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/88e0615d-1ee4-41d6-b8fe-ac27a1d2c353n%40googlegroups.com.
