I study about DropBoxManager of Android platform for crash tracking and debugging my app.
I referred this article. https://developer.android.com/reference/android/os/DropBoxManager
It describes that "The queue is size bounded and will drop old data if the enqueued data exceeds the maximum size." But I cannot find how big it is. What is the maximum size of DropBoxManager? If it is depends on devices, I would like to know Samsung flagship devices - Galaxy S20, Galaxy Note 20, etc.
Please help me. I tried to find the information, but it is very how to find.
Thank you
I don't know the answer, here's what I've discovered so far
According to https://android.stackexchange.com/a/218147/31304 it's possible to set the value, quote:
"settings put global dropbox_max_files 9
If you are rooted (or via adb shell - thanks #Irfan Latif) you can issue the command above to limit dropbox files in that dir to 9 (or any other number you prefer). You will only see only latest n events, older get overwritten."
We can list the global settings, however I cannot see any mention of settings for dropbox.
adb shell settings list global
There's an old version of the Java code online e.g. https://code.yawk.at/android/android-9.0.0_r35/android/os/DropBoxManager.java however that doesn't include the implementation details.
https://gitlab.tubit.tu-berlin.de/justus.beyer/streamagame_platform_frameworks_base/blob/marshmallow-x86/services/core/java/com/android/server/am/ActivityManagerService.java
Related
I'm creating an application, and I need to be able to get the battery's current (mA/mAh). I have the voltage/temp/level etc and this is the final thing I need to get, and coincidentally the hardest too.
I've looked at CurrentWidget source code and searched Google high and low, and I have all the classes/methods to pull the data out, it's just the path to the file containing the current which is stopping me from getting it.
"CurrentWidget" contains a lot of different paths to the file (for various devices) but none of them work on my ASUS EEPad Transformer on 4.0.3, which I need it to be working on as it's my testing device and all I can get my hands on. I've been in to the adb shell and dug around the root of the tablet for hours but I can't seem to find anything apart from things like name, temp, voltage_now and others which I already have. They're all stored in /sys/class/power_supply/battery, but there's no "current" like I expected, and like there seems to be on other devices.
Thanks for any help, I know this is a long one!
I tried changing the screen resolution in build.prop file in system, but it requires re booting.
I need a solution for changing screen resolution on android devices without re booting.
Thanks,
Krishna
Unfortunately that is not possible. Everytime when Android boots, it will read the build.prop file and set parameters pointed by it accordingly. After it has booted, it will not access that file dynamically to change parameters. So for any change to take effect, a reboot is compulsary, you cannot escape it.
Set resolution (e.g. 1024x768):
$ am display-size 1024x768
Reset:
$ am display-size reset
Doesn't require a reboot. This works with Android 4.2. Solution for 4.3 is mentioned by LiTTle
There is also an App for that called NOMone Resolution Changer.
Android can change the screen resolution.
I think that you need Android 4.0 and above version.
Only things you need is terminal emulator and root access.
Reproduce the following steps:
1. Open the terminal emulator app.
2. Type su.
3. Type wm.
Read the help message appeared and you will understand...
In case you want an App take a look at this on Play Store or the source from Github.
I have built android ICS(4.0.3) for virtualBox. And it runs well with default resolution 800x600.
However, when I change the virtualbox resolution to non-default ones, say 1280x800.
Then I get error "Unfornately, System UI has stopped". And the system hangs there. In addition, I cannot even connect to this device to see the logs when resolution changes.
Would you please give me some help? Thanks.
BTW,
The way I change resolution is suggested by Buildroid ----
First add a “custom video mode” to .vbox configuration file : Add the line
< ExtraDataItem name=”CustomVideoMode1″ value=”1280x800x16″/>
just after the already present “ExtraDataItem” entries.
Modify the linux kernel options to replace the existing vga=xxx by a vga=ask
Then, choose the expected resolution.
Maybe you find solution in this wiki article: Android Emulation.
If I want a certain application to be available for certain devices only or for tablets only, is there any way to make limitations by device (like I can limit the min/max Android OS version)?
I say it is impossible. Do you agree?
I understand that you are trying to limit the devices that can see the application in the Market but, like you, I do not think that is possible. You can, however, limit it within the app using details from and Build class. Build.PRODUCT looks like it would fit your needs - if the phone that has the app installed in not in a pre-set list of "products", tell the user that they have the wrong version and exit.
A similar idea for tablets is to check the screen size - if they are under a certain threshold, then display that same message.
It is possible, starting in june this year. Please take a look at this Google I/O session:
http://youtu.be/GxU8N21wfrM
I'm looking to create AVDs to test my apps on, and i'm trying to figure out the correct settings for a square screen such as the new Motorola Flip Out. I don't see a wikipedia article for it, or many specs...
On a related note, what about tablets? Actually.. Why aren't there a set of AVD instances with params from popular devices.. or at least a site that lists them for each of the 60+ devices.
Thanks in advance :)
The Motorola Flipout has a 320x240 screen.
For the specs of many other phones there are quite a few sites where you could find all the details. For example phonearena.com is one of them.
At the risk of getting another dubious badge for resurrecting old threads, I'll give the semi-official Motorola response... :)
Nearly every Motorola handset is accompanied by an SDK addon that includes a system image and a skin. In a few cases, the addon contains only the skin. Just download the archive and make sure the top-level directory of the archive is in into /addons. After that, you should be able to create new AVDs based on the addon. I find that it's a lot easier to use the GUI AVD Manager than a command line, but both are usable.
Download the addons at http://developer.motorola.com/docstools/tools/
Good luck.