[Q] Build.prop: multiple voices related to the same property - Android Q&A, Help & Troubleshooting

When there are multiple voices that define the same property but with different values, which one is managed by the system?
Example: considering
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=6144,87380,110208,6144,16384,110208
does the system acquire/manage the first one or the second one?
Thanks

Related

[Q] User generated layouts

Hi all
I am developing an app in which I would like to allow user-generated content. Specifically, this will be a remote control application, and I would like people to be able to add custom layouts, capable of sending "events" through the app, but I am not sure how to do so.
There are a couple of ways I have been looking at. The first is using a WebView so that this content can be developed in HTML. This would be nice and easy from their point of view, but it does have it's downsides, especially where security is concerned. If I was to do this, I would want to bind a "send" Javascript interface to my app, but disallow any other Javascript (I do not, for example, want it to be able to relay the button presses to some other place). I'm not sure exactly how I could do this.
The second way I can see would be to use an XML file and build up the layout from that. Here, the only way I could see it to parse the XML file and programatically build the layout. This seems a lot of work, and I would rather avoid that.
A third way would be to import a layout purely as an image plus an XML file describing hot-spots for triggering events. This seems to have too many limitations.
The final option is to expose an interface to other apps, and allow users to build separate applications which hook in to provide these layouts. This seems a terrible approach for such a simple objective.
So, does anyone know of a simple way to do what I am after, or any comments on the options listed above? Has anyone done anything similar, or know of an open-source project which acheives something similar?
Thanks in advance

[Q] Does ro.config.low_ram=true have an effect on <4.4 ROMs?

As most of you following the KitKat developing scene for lower end devices probably know, Android 4.4 introduced the low_ram property. On 4.4 ROM's, transparent statusbar is disabled for example for devices with this property set to true.
Now, the situation is:
I'm running CM10 (4.1), because it's one of the most stable custom ROM's for my device. A few days ago I put the following line to build.prop:
Code:
ro.config.low_ram=true
hoping to notice better optimized RAM management. It's hard to claim an effect knowing that it could very well be placebo, so I was hoping someone understanding this better could explain the effects to me.
Added a new ActivityManager.isLowRamDevice() to allow applications to detect when running on low memory devices and choose to disable large-RAM features.
(...)
We are introducing a new API called ActivityManager.isLowRamDevice() for applications to determine if they should turn off specific memory-intensive features that work poorly on low-memory devices.
For 512MB devices, this API is expected to return: "true" It can be enabled by the following system property in the device makefile. PRODUCT_PROPERTY_OVERRIDES += ro.config.low_ram=true
Click to expand...
Click to collapse
http://source.android.com/devices/low-ram.html
I too noted that it says API, so that means that it's dependent on the OS version. Is there any way it can have an effect on memory mangement if not runnign 4.4?
Same goes for disabling JIT(see a bit lower on the source page), which needs to be set in the 'product makefile'
Bump
good queries always go unanswered
I asked it in a Reddit thread too and someone said it won't work, but I don't think that guy has more knowledge about it than you or me. However, since they say it's an API, and API's are bound to the Android version I don't have much hope for this to work...
For the time I've tried it, I didn't notice any difference anyway, if there is, tweaks like zRam will benefit you much more anyway.
On CM11 it disabled some effects and gave a lotof free ram. The effect depends on rom and implementation.
so we may as well just add it to the build.prop anyway, if it works then its a bonus if not no harm done.
i think it's only for KitKat
https://android.googlesource.com/platform/frameworks/base/+/b4e12494935697fa4ede006b37e6be889ef27109
https://android.googlesource.com/platform/frameworks/base/+/9fc5bae^!/
It was only added in kitkat.
Previously (only going as down as 4.2 though) if any you had isHighEndGfx and isLargeRAM (which at least on vanilla android were automatically detected at runtime, thus not user-settable)

[Q] Trimming Android libraries (.so) by hex-editing?

I've recently become interested in hex-editing prebuilt proprietary libraries. Many of the Android libraries have a lot of "00"s in hex code, so I was wondering if all those zeroes could be edited out (removed) to essentially "trim" the libraries, save space, and not cause any issues. Or are the many zeroes more than just fillers? Thank you.
I'd be wary of removing them, if they're pointed to by PBL/config_dat/etc it's the address it's located at and NOT the files name
*found this type of thing out by reading up on ELF files*
Bashing away at my HTC Desire C

Different sensors values across multiple android systems on the same smartphone

Hello guys,
On begin i would like to apologize if i chose wrong section for this thread.
It is possible that across multiple android systems on the same smartphone sensors register different value? I researched a luxometer in smartphone with same the artificial light which registered values vary around 200-600lx. What can cause such differences? The problem appear in more than one smartphone. Chart in attachment present registered values of luxometer. HAL may have an impact?

Development: how to add multiple images to ViewPager

I don't have the rights to post on the developers forum, that's why I ask here.
Sorry if my research is somewhat limited. I'm new to Android development, have a deadline soon, and I don't feel I'm quite close to getting it right.
I'd like to make a very simple app where you can browse a few predefined images fullscreen. I tried the following tutorial: "Using ViewPager for Screen Slides" by android developers site (link had to be removed per website policy).
Android is a bit complicated to me with the .xml files for resources etc. I thought XML was just to define the individual resources, but I realized they also act similarly to HTML pages when I want to create a view. I managed to display one image by replacing the second TextView "textView" by my ImageView in activity_screen_slide.xml.
But the problem is that it now it displays the same image with each page. How can I set a different one for each page? I tried to add multiple LinearLayouts with different images, but the app crashed.
I also tried using xliff:g to have a different image name on each view, like image1.png, image2.png etc, but it seems it's not supported to use it inside resource file names.
Of course I could make arbitrary number of copies of the view, and set a different image in each one, but I'm sure there is a better and way.
Any ideas?

Categories

Resources