Android Development

ACRA see: [link] [link]

hello abdul, did you got solved this problem? i am also facing this issue with my app. please let me know how i can solve this problem. thanks kapil

NVIDIA has really stepped up and made some great innovations for Android as a whole, and they’re not showing any signs of slowing down. The latest from the graphics chip maker is a demo of their Tegra 4i, which is the version of the Tegra 4 designed to be run in smartphones, complete with LTE modem. When the chip was first debuted, it was capable of reaching 100 mbps download speeds, which is considered CAT 3 speeds. (Most ethernet cables you probably use in your homes are CAT 5 cables, for reference) Well, fast forward a few months, and NVIDIA has introduced a software update for the 4i that bumps up the down speeds of the modem to reach 150 mbps, which is considered CAT 4. The impressive thing here is that no new hardware was introduced; NVIDIA software-defined radio tech is running the show here. So not only can this processor’s modem reach speeds higher than what’s even available in the world today, but it can be made faster through software tweaks instead of adding hardware and is only 40% of the size of other LTE modems in use today. Watch out, Qualcomm. source: NVIDIA Blogs Come comment on this article: NVIDIA shows off world’s most efficient CAT 4 LTE modem Visit TalkAndroid for Android news, Android guides, and much more!

LG has been releasing devices for a while now that have generated a decent amount of buzz, and it looks like the LS720 Optimus F3 is going to be added to that list. This phone will be a budget-friendly LTE handset, with a 4-inch WVGA screen and a dual-core processor. It will ship with Android Jelly Bean 4.1.2 and a strong 2,460mAh battery. Expect the phone to hit the shelves within the next few weeks, priced aggressively on contract. Source: Phone Arena Come comment on this article: Pictures of LG Optimus F3 released, expected to launch on Sprint in coming weeks Visit TalkAndroid for Android news, Android guides, and much more!

set the default uncaught exception handler, use it to launch your app with an intent/pendingintent that has the stacktrace, then use that activity to show the stacktrace.

I'm not too sure why this is happening... i'm guess that alignBaseline affects measuring differently and causes a cyclic dependency (Romain?) Try changing the relationships so you'll define A and B Below C instead, since C has a constant location anyhow. Also if your View hierarchy isnt too complex and wouldn't need to be

Hello, It would be great if it could be added back, or something equivalent, because otherwise from what I see then I will have to write a program to zip the parts, which adds to the complexity of the build system. The build system so far was very nice, everything could be done with 1 single .bat

Is this file present in your jni directory? *libnative-media-jni.so* Thanks.

I've been contemplating fatal errors. Back in the DOS days, I would just print them out and exit the program. This was often adequate because you could instantly see what had happened. However, with Android, when your program exits, nothing from it is left on the screen. Any ideas as to what is the best way to handle these? I want to have a

I think this is an Android bug. I have seen this so many times on differnt devices (more frequently on older ones). Common pattern is more often than not tapping the app icon as normal will launch the MAIN LAUNCHER activity on the top of the existing stack but occasionally will resume - i see this