I am profiling a JNI Android Application . So far I managed to profile it with Android-NDK-profiler. It is very simple so I want to go further and get info of the hardware too, like cache misses, bus speed etc.
I have read that the NVidia Tegra profiler is very powerfull but there is not much info about the devices that support it. I know that it needs Tegra 4, and that for example this device supports it: http://shield.nvidia.com/.
The problem is thta it has no camara integrated so it is not valid for me.
Has anybody tried any device like a mobile or tablet that is compatible with Nvidia Tegra profiler??
normally any Tegra4 and K1 based device should work, but I would recommend the Shield/Note from Nvidia for your work, not only are they quit cheap, but their android is left very much vanilla (aside from some stylus things on the note) which makes it easier to work with.
There is also the advantage (so far) of a "usable" update policy.
Related
I build an Android Application on my Nvidia Shield Tablet.
Now I want profile my application, not only to improve the performance but specially to analyze the power consumption.
I saw this link, but I really don't like this suggestion because is necessary root the device.
I installed Nvidia Gameworks and AndroidStudio to develop the application and my OS is Ubuntu 14.04.
I'm not expert about how to use profiling tools given by GameWorks so I would ask someone how to proceed to profile my application and investigate about power consumption.
I have not found easy and useful tutorials on the net so far
Thanks for the help.
I have tried Trepn Profiler, but for some reason it's not profiling the apps as it should on my Shield as it does on other devices. That said, it could be some weird setting on my devices, as overlay applications don't work well on my device in general. Thus, give it a try and see if the app works on your tablet. It does the best job for app power profiling on other Android devices, to my experience.
Is Way To Run Machine Code Instead Android OS In Android Devices ?
I Want Remove Android Os And Work With Cpu And Other Devices Directly .
What Compiler I Can Use ?
MASM is an x86 assembler, so it would not be suitable for most Android devices as the vast majority use ARM-based processors.
That said, Android phones are computers just like any other and can be programmed in assembly. The first thing you'll need to do is select a device running a well documented CPU and chipset.
Since you'll be removing Android and plan on programming in assembly you'll need to write your own routines for nearly everything. An understanding of the CPU, power management and some form of I/O (you can avoid having to write complex display code if you plan to interface with the phone through serial communication, for example).
Unfortunately, much of the information required for successfully writing your own OS for an Android device is unavailable so you'll need some hardware analysis tools to assist in reverse engineering some of this information. A logic analyzer may be useful in sniffing some of the protocols used between chips, although much of modern phones is done on a single SoC, so you'll need to experiment heavily and compile information from a wide variety of online sources.
Aside from that, it's smooth sailing. Programming an OS in assembly for Android is pretty much the same as programming an OS in assembly for any other computer and you'll find it to be rather familiar territory.
Can anyone point me towards a tried and tested development kit (board) for Bluetooth Low Energy?
I am especially interested in the proximity profile, and compatibility with smartphone (especially iPhones and Android devices - but also any other that would have BTLE).
Also, can you tell me which smartphones would support the proximity profile?
If you are looking for API support for BT LE features then there is very little at the moment. For example, Android at API16 does not support. It is all rather disappointing so far. In many instances the HW supports it but the middleware / upper layers do not. There is SOME support on iOS (with Iphone4s) and with certain Moto phones (need the SDK add on) but it is limited.
iOS is probably your best bet (who'd have thought that).
Personally I am looking to use the GAP and GATT interface on Android (ICS/JB), which is mandatory for a BT4.0 listed device (such as the BT ICs in high end smartphones) but GAP does not seem to be exposed.
Oh, and if you need a dev kit (for SW dev then this link might help > http://blog.bluetooth-smart.com/2011/10/05/bluetooth-low-energy-development-kits-2/)
The Bluegiga DKBLE112 Development Board (out of the box) can communicate with the iPhone 4S on IOS 6. The IOS code tutorials by http://olesitune.mine.nu/blelogg/?page_id=78 and http://olesitune.mine.nu/blelogg/?page_id=180 will discover the DKBLE112, the built-in thermometer service, and the associated characteristics. The code displays the BLE information on the iPhone and in the Xcode Console if the iPhone is tethered through USB. The DKBLE112 is expensive (nearly $400) but it does include many capabilities that I have not yet explored.
I note that tod list devices that have BT4.0 functionality. Of course that does not guarantee that APIs will be exposed in the SDK. If you stick with an already implemented profile then you may be ok but as I said, you certainly will not find that in the Android API16. SO, custom implementations.
One of the nice things with BT LE is that profiles are relatively "light" and hence, you can pretty easily make your own...but if the phone side API does not give access to the lower level (only talking GAP and GATT here) then not much use..
The guys who produce the tod seem to have done pretty well with a BLE device that functions as a proximity sensor.
They've managed to get their device working on the following phones:
iPhone 4s, Droid Razr and Razr Maxx, Samsung Galaxy S3, HTC One S, X, V, LG Optimus LTE2, Droid 4, Droid Incredible 4G LTE, HTC EVO 4g LTE, HTC Desire C, Sony Xperia GX, Sony Xperia SX, ASUS PadFone
So it is possible. My recommendation for a dev kit is the Bluegiga BLE112 with a CC Debugger from Texas Instruments. Your options for programming are either the $4,000 IAR compiler, the proprietary Bluegiga API "BGScript" (if you don't have access to IAR), or use an external microcontroller with the compiler of your choice.
I am using a TI ez430-rf256x development kit with "IAR Embedded Workbench for MSP430 v5.51.5". When TI 1st released the ez430, they were using a crappy stack that was buggy and just wasn't capable. They have now switched to a Bluetopia based stack and it is great! It comes with a LOT of samples, supports ALL profiles (including all the new low energy profiles), and is easy to use. I believe the Bluetopia stack also supports I have it talking to my Galaxy Nexus over classic bluetooth, but unfortunately, as of Android 4.2.2, there is still no support for Bluetooth low energy (which the ez430 does support.) It appears that Google may address this issue in Android 4.2.3. In my opinion, there is no reason to use something like Bluegiga, as you will pay more in licensing costs to them, than you will spend on a compiler like IAR. This is a link to an explanation of the new stack that TI is using: http://www.stonestreetone.com/bluetopiaLE.cfm
I realize this is an old question and in disclosure I am a developer on this project: Anaren Atmosphere.
Anaren has produced a Bluetooth Smart Multi-Sensor Development Board with the A27037 module based on the Broadcom BCM27037 that is compatible with the Wiced SDK. It also features an online development environment that is a GUI/IDE that allows you to both program the module and create associated iOS and android applications to communicate with it.
The development kit is available from various distributors and the development tool is free to use.
Will I be able to test my Open GL ES 2.0 application on Android Emulator? Or I will have to use Android 2.2 device to test it? What devices are best to test applications on it? I know that official Dev Phones are Nexus One and ADP 2 (as you can see on this website http://developer.android.com/index.html) but Im asking about your experience with other devices too.
You have to test those applications only on real devices. Emulator doesn't support OGL ES 2.0. You can also use remote testing devices (look at Motodev Studio, there is some of support for this).
There is no noticeable differences between dev phone and "standard" phone, if you are application developer.
It's hard to tell what's the best choice, cause there are so many devices now, and they just keep coming. Also you might think about testing your app on a tablet, if you consider designing for tablets, so here's a another problem of choice. Phones and tablets are very different in terms of performance, so you won't choose an ideal phone for testing. Testing on the emulator is also a waste of time with an OpenGL application, especially if it's dynamic, cause emulator will give you a very low FPS rate and very slow responsiveness.
I'm trying to chose the ARM development board for education purpose.
The goal is to learn how to run and play around with systems like Android (version 2.0 or higher),Linux, Windows CE. It must support touch-screen, Ethernet, USB host and device.
I've found many boards, the most interesting is Android6410. I've search Google and it seems that it is not very popular. Has anyone used it? Is it well documented? What about the support? How about the performance under Android?
I've also found some other development boards:
http://www.friendlyarm.net/products/mini2440?lang=en - the most popular one but probably it is too slow for android 2.0.
http://www.friendlyarm.net/products/mini6410?lang=en - the same CPU like Android6410 but it seems to be a new product so the support may be pretty bad
http://beagleboard.org/ - quite interesting and popular but no touch-screen in standard version. The external ones are very expensive (twice as expensive as the board itself)
http://pandaboard.org/ - very fast but also doesn't have standard touch-screen connector, no Windows CE support
Any hints will be appreciated.
Samsung has provided an android kernel, as well as a reasonably current "generic" linux kernel) that, amongst other Samsung SoCs, also supports the 6410. The Git repos are here:
https://android.googlesource.com/kernel/samsung
http://git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git
These do provide smdk6410 defconfig targets.
You also need an odroid bootloader (uboot for 6410) to be able to flash new kernels onto the board and/or the SDcard it boots from, as Samsung uses a special "fastboot" utility for this purpose (very different from OMAP which just puts the kernel into a file).
I can't comment on the performance of the device compared to others, as I haven't run extensive benchmark tests or anything, sorry. You're right, it's way ahead of 2440; it's an ARM1136 CPU, so it'll end up somewhat slower than the Cortex-A chips from omap3/4 boards.
Try the FL6410: http://www.arm9board.net/sel/prddetail.aspx?id=363&pid=200
A nice board with great Android support!