Hi all,
I'm starting a project and I would like to understand (if possible) how to hack the legacy behavior of the HSDPA/LTE and/or WiFi stacks, e.g., transmission power, modulation schemes, channel bandwidth used, etc. I have some experience hacking into WiFi stacks from the linux wireless stack but I am newbie in modern android phones. I understand the drivers are not "open" to hack, but there still must be some way of inducing some simple changes on them.
Thanks for the pointers in advance!
Related
Hi Guys, i would like to know if someone is interested to work on a MANET running on android phones...
i have actual develop an specific Routing Protocol for Manets and simulated in Opnet and works well, i don't have to much skills on Java Programming or android software development and need help to develop the code for it...
basically the project is to run several android phone that will be able to use adhoc mode to create network and each node to be able repeat the signals to the next near node....
Regards
You may want to post code in C or C++ . No doubt someone would convert it into the proper Java android code. I suspect some of it would need to be wrapped anyway and that it's highly likely to require root access.
Finally
Finally someone working on Mobile Adhoc Network have acomplish a MANET protocol on android Phones, they have implemented an OLSR and BATMAN routing protocol..
http://www.servalproject.org/
Thank you serval for this implementation....
Hi guys,
I tried to find similar threads or answer but none specifically addressing this question.
I want to detect whether sound is being played on the device in general, then hijack that audio stream to find the BPM in a separate android application. This may or may not include decompressing the audio stream and measuring it based on peaks/troughs in the sound wave. But the general idea, so far as I can tell, is to reroute the IO stream from applications using the sound card and pipe it to another application.
I know this is theoretically possible using android libraries like BASS by XMPlay, but I've never seen this in practice (I assume there's a good reason).
My gut feeling is that when the sound device is in use, the thread is basically locked down and you can't do much to it. This is the case in many operating systems (but not all!, including Linux based os), so would not be surprised if this question is left unanswered or just not possible.
Also an fyi; I'm very new to Android development but I have a plethora of experience in Java and lower level languages. It's very possible that many of my assumptions are way of the mark here. Any input would be greatly appreciated.
Cheers,
Jopdan
I'm looking for Android Bluetooth / TCP/IP relay application.
-- Details --
I'm looking for RDP client which would be able to relay / bridge Bluetooth devices / peripherals to the RDP host (Windows server 2008 R2).
If there's no such RDP client, wehave a secondary option. Having separate background service which takes care of the data relaying part in background, and leaves the RDP connection / device display to foreground as completely separate process.
I've been planning developing such application. But if possible, I want to avoid re-inventing the wheel. Even if it sounds really simple, I'm sure there will be (too?) many problems before it works reliably.
I'm very curious to know, if such application already exists and where would I get it. I'm quite sure that someone has already made such an application. I just don't know where to look for it.
Additional bonus would come, if the application is quite easy to configure and if the sessions between RDP and this relay are easy to link and access on Windows server end.
As addition to the bluetooth relay, it would be nice to have a simple TCP/IP tunnel / bridge / relay feature in same packet. Allowing access to devices using TCP/IP without bluetooth using same app.
If it's true that such application doesn't exist. Would there be an market for such application if it's created? I could imagine I'm not the only person looking for such app.
I do have additional documentation & specification for there requirements, but I don't want to share it right here. I've been also discussion about this topic with a few Android Application developer companies, but as you might guess, this project won't be cheap. Therefore I'm looking for reasonably priced existing solution.
Here's simple use case sample. Customer is using industrial data collection solution where there are ten sensors attached to something being monitored which are then connected to tablet over bluetooth or wi-fi (TCP/IP). But the actual data processing / logging / control software is running on Windows server and can be accessed using RDP. Of course one solution would be using a full featured Windows laptop instead of that tablet, but we don't want to do that. So this expains what I'm looking for in more detail.
- Thank you
-- Footer --
KW: business, software development, android, thinclient, tablet, bluetooth, wifi, wlan, mobile
HTag: #android #peripheral #connectivity #remotedesktop #remotedesktopclient #softwaredevelopment #bluetooth #tablet #thinclient
Hello guys,
I would like to look deeper in the security of Android Beam and related technologies like S-Beam, Shoutr or AirDrop from Apple.
Unfortunately I could not find much specs or protocol description about those technologies. The Android docs only explain how to implement NFC file sharing in your application but I could not find anything that explains what actually happens (e.g.: which messages are exchanged) when two phones get paired.
Anybody that knows something on the topic?
Thanks
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!