I'm having a AOSP codebase. I would like to enable ramoops in the system to debug system crashes. How can I enable ramoops in my AOSP ( Android Open Source Project ) code base?
Solution
Follow the instruction on
https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/ramoops.html
Summary
Add "mem_address", "mem_size" & "mem_type" to the BOOTARGS variable in device.mk according to your hardware specific memory address.
Eg. BOOT_ARGS += "mem=128M ramoops.mem_address=0x8000000 ramoops.ecc=1"
For Additional reference:
Visit Google Documentation
Related
I got flutter upgarade and imported a project from git.
and I want to run this app but Dart support is disabled.
Flutter SDK path seems apllied but Dart ( on Setting > Languages & Frameworks > Dart seems not be able to be enabled.
How could I solve this situation?
enter image description here
To solve this problem, you need to set the flag to "Enable Dart support for the following modules"
I had same issue and checking both boxes would do anything, it would always reset back. My fix is:
delete the repository
clone again with terminal (don't use Studio) and set different name for poject: git clone (url) newName
And it works.
My working environment is AOSP6.0.
I was hoping for some detailed instructions,
such as What do I need to do in Android.mk?
or How can the custom __sanitizer_cov_trace_pc_guard_init and __sanitizer_cov_trace_pc_guard functions be passed to the Android build system so that it can be used when piling?
thank you every one !
Hello and thanks for helping me solve my problem! I ask for an easier way, as I am trying to figure it out without success in this tutorial https://developer.android.com/guide/app-bundle. So far, I only worked with the Google Play Console itself, did not create an application in a third-party service. I first tried to download the Android App Bundle using Android Studio as described in this article https://medium.com/androiddevelopers/building-your-first-app-bundle-bbcd228bf631, but the first step describes pressing buttons that are not on Android Studio Panel "In Android Studio, select“ Build => Generate Signed Bundle / APK ”and follow the dialog." I do not see the options I need in the Android Studio panel (I attach a screenshot)enter image description here
, where do I need to click to create an Android App Bundle? Then I tried to create the Android App Bundle from this tutorial using the command line https://developer.android.com/studio/build/building-cmdline, I installed Grable manually as described in this tutorial https://docs.gradle.org/current/userguide/installation.html#installation unpacked and configured the system environment, as well as installed and unpacked JDK 17 for Windows/x64 (also on disk C but in a different non-Grable folder), but verifying the Grable installation when typing gradle -v in Windows PowerShell throws an error, and these instructions https://docs.gradle.org/current/userguide/troubleshooting.html#sec:troubleshooting_installation does not offer a solution what is displayed in my Windows PowerShell enter image description here
(The sentence highlighted in red from the screenshot in English looks like this "grable: The name grable is not recognized as the name of a cmdlet, function, script file or executable program. Check the spelling of the name, as well as the presence and correctness of the path, and then try again."), and when I enter gradle -v into the command line, it says "Grable is not an internal or external command, an executable program or a batch file.", I face the same problem if I enter into command line ./gradlew bundleRelease as suggested in this tutorial https://medium.com/androiddevelopers/building-your-first-app-bundle-bbcd228bf631. I'm stumped, what am I doing wrong, and what method is easier for me to create an Android App Bundle? Thanks again for the help in solving my problem and I apologize in advance if I have provided little information necessary to solve my problem.
i am trying to add drawable-tvdpi for an app in AOSP tree. But drwable-tvdpi is not reflected in the resulting apk resources.
When i try to build the same using eclipse i can see drawable-tvdpi in the resulting apk resources.
Please let me know how to enable AOSP for adding drwable-tvdpi.
Eclipse builds are for all types of devices, while building aosp is for a single type of device.
You need to edit build/core/product_config.mk.
search for PRODUCT_AAPT_CONFIG and add tvdpi to this variable.
I have a custom Android image using a custom built goldfish kernel. I have been using the Emulator for SW development.
emulator -kernel out/target/product/atom/kernel
When I upgraded to SDK 20 I no longer get keyboard input from neither the host nor the graphic keyboard. This used to work. I have seen the comments about setting the hw.keyboard property=yes. I am not able to find a sequence of operations that work.
a) try and launch the emulator and force my hardware config
emulator -verbose -kernel out/target/product/atom/kernel -qemu -android-hw /home/jgrecco/work/ics-4.0.4/out/target/product/atom/hardware-qemu.ini
The hardware-qemu gets overwritten and the hw.keyboard option is no.
b) Create an AVD and have it load my custom kernel and image
ex: android create avd --force -b x86 -n aal_emul -t 3
emulator -kernel out/target/product/atom/kernel -show-kernel #aal_emul
But have not been able to get the AVD to boot my custom image. It seems to boot a default image. I've tried copying over the img files but no luck
c) Tried modifying the default hardware.ini settings
ics-4.0.4/external/qemu/android/avd/hardware-properties.ini with no effect.
many many other variants.
If someone could make any of the solutions above work or tell me one that will I would appreciate it. BTW this is for x86 atom.
TIA
After much experimentation, Googling, lots of cursing inaccurate (out of date) documentation and updating all of my sources (fighting with repo sync hangs – rant off), I’ve figured out a work around. I thought I would post this for the benefit of others.
The basic problem was that after upgrading to SDK 20 I no longer could input to an application using ANY means (real or emulator keyboard). This only occurred when loading my own custom image "lunch #; emulator -kernel out/target/product/...". None of the attempts to override the hw.keyboard property as described above worked for me.
The work around I’ve found is to change the setting in the emulator at runtime. Settings->Language & input->default_Hardware Physical keyboard (OFF). While I can’t use the host keyboard I can now use the emulator keyboard for input.
Try setting 'hw.keyboard=true' in the file config.ini which exists alongside hardware-qemu.ini.
This overrides the default value in hardware-qemu.ini and shouldn't be overwritten.