I'm working on a project where I need to examine the different mechanisms mobile devices might employ to determine services and devices available nearby.
I'm aware of the more obvious methods like bluetooth, snmp, bonjour, mdns, and active directory. What other methods are available for nonlinear devices?
Also, what about software? Are there favorites used by different devices that I should look at? They might use the above methods or use emerging unique.
TIA.
Sent from my G-Tablet running Vegan-Tab (GingerEdition RC1)
Related
Hi,
We've all seen the Windows Phone presentations where the presenter streams the content of the phone on the projector or monitor using some sort of an internal Microsoft tool (as I've come to learn).
Any idea what the tool is? Where one can find it or what would it take to write one?
any answer to this? I need this info as well
Yes I can tell you why its not present on the consumer phones.
This is what I got as an answer to a related question:
The technology used to make this happen is patented and Microsoft is not allowed to distribute it into consumer devices. There are certain devices that are fully open (the devices they use to do the presentations with the TV-out) everything can be taken off those devices and can be added. The consumer devices have some remains of these things (for example in the registry). Only a couple of people own these devices and this technology may not leak for the above mentioned reason, that's why these devices are not widespread amongst developers outside of MS.
Correct me if I'm wrong, this is kind of what I've been told.
I am looking for analysis tools specific for Android app development!
I have found many tools online that are not specific for Android, only for Java, either free or commercial, like the famous FindBugs but it is not interprocedural so for example it loses several bad NullPointerExceptions that may occur at runtime! Other tools (like CheckStyle) perform just a syntax check that sometimes is not so powerful, and other tools are not suitable for Android app development
What are, among the available tools, those that you prefer and really use?
What kind of properties do these tools check?
What kind of bugs do these tools detect and remove (among the most common errors that an Android developer may do)?
Please help me with sharing your experiences and suggestions, thanks!
Call me old fashioned, or not, but I tend to stick with what's provided for me in the Android SDK/Eclipse. 90% of the time I'm working on games and I've never really felt the need to exceed the bounds of the Android SDK for debugging or development tools (aside from automation tools for repetitive tasks involved in development).
Out of curiosity, are you very familiar with Android's debugging environment? I think the reason why there are not many tools out there is because Android's got a pretty nice setup as it is.. but maybe that's just my opinion.
I prefer to use Eclipse with the built-in sdk tools. Using custom tags and monitoring the Logcat output is actually quite effective, considering the output happens during run-time. It also allows you to test at run-time on real devices as well as in the emulator.
Hi,
I have some doubts and do not know how to do, maybe you can help me.
so, I need to communicate between two different android apps on different devices.
Case study: i have tablet1 with app1 and tablet2 with app2 on a local network. I need app1 on tablet1 send and receive data to/from app2 on tablet2. So its a client/server communication (or better, i need many clients to one server).
There is a mechanism AIDL but only works different apps on same device, but i need on different devices. I have done some examples of services and messengers handler but without success. Applications must be version 4.0 and android app ( I say this because there is a NSD mechanism that discover services of other devices / apps android in local networks, but the minimum version is 4.1 and I already have several customers with tablet v4.0. I know it is possible but also do not want to install a web server on a tablet ( like a KWS or PAW server and others) ).
The documentation and examples that i use are google android site, like trainning, guide, references and others.
Thanks in advance for any tips.
I have a passing understanding of various bootstrap schemes used by device manufacturers. This applies especially to Archos generations 5 through 8, Exynos-based devices, and Qualcomm devices. The designs out there are similar in some respects but differ radically in others. I don't know how many designs utilize it, but some schemes have the baseband and application processors segregated. Sometimes they can mingle.
I'm interested in the mobile side of things. Can anyone tell me about network locks and mobile identifiers? I'd like to know things like:
Where that data is stored. (Is it on the same memory chip as the operating system?)
If any of this data is immutable (i.e., burned as fuses).
If this is something that can vary between device models or if they roughly follow the same template.
What Android devices, if any, when hacked are able to pick through this data.
I would like to create an IoT device by buying new, cheap android phones, strip them down and remove the screen, rebox into my own physical box, install a custom ROM without any bloatware (and that will boot without a screen!), and install my android app on the device to do stuff.
An example of a purpose for this could be a GPS tracker for a car. The box would be placed in the car, and record GPS and accelerometer readings, posting these readings back to a central server via the cellular network. (This is just a random example, so don't focus too much on the detail of this, but there are thousands of uses for a IoT board with the sensor, CPU, RAM, storage, and connectivity capabilities of a budget android smartphone)
The reason I want to use existing phones is that they are wonderful, mass produced, cheap devices with a variety of sensors I can use.
The reason I want to use Android is because it is because of the customization ability, and the mature development ecosystem.
To me, it seems an obvious thing to do, but I don't seem to be getting much joy trying to search for examples of this sort of thing (either here, or on the internet in general).
So some questions:
1. General thoughts? (Good idea? Am I missing some fundamental problem?)
2. What are the challenges of running Android without a screen connected?
3. Are there any custom ROMs you know of that specialize in this sort of thing?
(I've seen Google Brilo, but it still seems a bit early yet, and I really like the idea of just using the standard Android SDK to develop the app - and the abundance of help and information that comes with it)
Thanks!