Hello,
I was wondering if someone could point me in the right direction for a Bluetooth Networking Project I'd like to do.
The ultimate goal:
- Having some sort of bluetooth app with root privileges, which, when walking past someone, would allow some sort of passive communication without the users authorisation nor involvement.
This is similar to the idea on the 3DS called "SpotPass":
(I would have posted the link, but I'm not allowed to)
I do not have much experience on the subject, but suppose it would involve having root permissions to access the bluetooth module, being able to broadcast a message (to other users of this application).
I'm not sure if this might involve creating a completely different driver.
The reason is actually to create a short-distanced-passive-communication application useful for getting short messages or announcements across, with the low power consumption of bluetooth (vs wifi).
If this kind of communication if not possible, could someone please explain why, or at least give me some sort of link with the reason.
Thanks in advance
I've posted this question on a few other forums over the weekend and came up with nothing. Thought I'd branch out even more and found this forum. I've searched this forum and the wiki and google for far too long to just find out if it is possible and if so how hard it would be.
I'm on a youtube channel trying to follow a 200 lesson series on Android development when all I want to know first is if my app idea is possible. I want to make an app for mass texting to a small group probably under 100 people at any given time. I don't need any of that short code stuff, actually I'd like to use my GV# since that's a free long code. Right now what I do is I use GV & the Gmail workaround (if you don't know what that is you can ask me or google it) but it is a long and tedious process due to the fluctuation of subscribers. I need the keywords capability too, which GV does not provide which led me to think about making an app. I would also like to have people added to the list automatically via keyword. I will be sending out 10-20 or so bursts a month from my AT&T Samsung Galaxy S II. I'm obviously getting pretty desperate... any help, questions, or advice?
We have a Service with some threads dedicated to network communication. It's heartbeat-type traffic - a quick request-response a couple of times a second with small amounts of data. The problem is that a thread sometimes just stops being run for 20 or more seconds when a network request is made (that's based on calling System.currentTimeMillis() at the start and finish of the network request, and I know from measurements on the server side that the request was completed in a fraction of a second).
The advice out there suggests setting thread priorities using the Android-specific API and/or the pure Java API. It also suggests poking the service into the foreground with notifications, because Android favours foreground processes. I've tried the thread priorities, doesn't work. I'm currently trying the foreground notification trick, I don't know yet if it solves the problem.
Even if any of those techniques happen to work, it stil seems brittle - the kind of thing that could stop working with a hardware change or operating system upgrade. Is there any way of telling Android that a given thread is important enough to get attention a few times a second, and to have it treated as a requirement and not as a suggestion?
This isn't a general release application that needs to be a good citizen and let other apps have their turn: we're running it on a tablet that's dedicated just to running this application, and that we can modify in any way that's required to support the application.
Have you come across this problem before? What do you suggest?
Thanks.
Hello.
I am here seeking for help and advice on how to approach the development of a security framework (via APP or via hacked Android ROM to be used by kids, that could be monitored by adults (parents or legal tutors).
The idea would be to develop a (white hat) hacked ROM, that would allow the kids to communicate with their friends, but also would allow their parents to supervise/monitor in real time what their children are doing, who are they communicating with and that way protect their children. The thing is not to spy on our kids, but to be able to check regularly if there is anything wrong going on with our kids (mobbing, insults or harassment). Kids aged (10-14) could be influenced by other kids, adults, or adults simulating being kids, and on some occasions they can be tricked to do things without their parents consent/knowledge that can lead to a tricky situation.
When I was a kid, we had the telephone (wired telephone, of course) on the middle of the hallway, so all our conversations were basically family-public. The truth is that there are not many secret things a 10yo kid could/should talk about, but nowadays, it could be a little bit worrying to lend a smartphone to a kid. I think it's just as letting a kid drive a car; he can do it right, or not be able to evaluate the whole consequences of driving a car.
Talking to other parents around me, they all found very interesting the idea of having a telephone that one could lend to their son, having the kid available all the time, and with the peace of mind that you could know what's going on. Of course the kid should be aware of this, and that the telephone comms are being supervised. I think it's no big deal. "Kid, it's very simple. The telephone is mine, and if you want to use it you have to use it under my terms".
Probably, all of us working for a company, have also our communications supervised, cannot make personal phonecalls with the company's telephones, probably cannot navigate to webs looking for personal content, and we asume those rules (because neither the company's phones nor the computers are ours but our company's). It's basically the same, switching the company-employee role to a father-son one.
So, let's get to the point (technically). I am a tech-geek, linux pro-user, have compiled a few ROMs just for personal use, but don't feel capable enough of starting a project of these magnitude alone. If there is anyone willing to help, opine, or whatever, will be very welcome.
First of all, APP or ROM? I basically think that the ROM is the way to go, but I'm asking just in case someone can convince me on the contrary. I will make a poll on this question.
APP An APP could be easily downloaded and installed but would require a rooted phone, and I don't see it clearly if an APP could resolve all the needed issues (access to communications for example) and could be fairly easily uninstalled too.
ROM On the other hand, a ROM would be trickier to uninstall (basically flashing another ROM) but wouldn't be as easy to install as an APP (though the installer model of cyanogenmod could be kind of a solution). There could be an universal (if possible) independent flashable module, over whatever android ROM, or an entire ROM solution.
Features that I want to develop in this ROM (by the way, I call it 'Vigilante ROM'):
Suitable for as many devices as possible
Web interface for parents available to see device-related information
Some hack-proof measures to avoid kids bypassing the ROM's security
Alerts triggered on some events (offensive words, whatever)
Position of the mobile -just in case-
Suitable for as many devices as possible
The first thing I though was what platform should be used for this ROM. To select Android over others (iOS, Blackberry, W7) was a no-brainer. Now, the question is should we use pure Android or make a CyanogenMod fork?
In my opinion, even though every phone maker has to supply their ROM sources publicly, they usually introduce so many modifications (HTC Sense, Samsung Touchwizz and so on) that it looks more difficult to develop a common security framework over each manufacturer's version of Android, rather than using a more standardized one like CyanogenMod.
CyanogenMod already works with a wide number of devices (and a wider one if you count the unofficial supported devices), I think CyanogenMod should be the base of this ROM. If all the 'things' needed could be flash on top of any Android device, would be even better, but technically I need help with this one.
I understand that basically there should be an internal proxy setup, so that all the communications go through this internal proxy, and based on the kind of communication, we could log whatever we need. For example:
Visited URLs
Whatsapp or other messaging apps should be decrypted
Incoming/Outgoing calls/SMS
Social network activity
I know the Whatsapp protocol because I'm familiar with a project called WhatAPI. The key point to be able to intercept whatsapp messaging is a key generated and exchanged during the app install (although there are ways to later ask the Whatsapp server to renegotiate this keyword) and that's used later to encrypt all the messages between the phone and the whatsapp server.
Web interface for parents available to see device-related information
Behind every kid with a smartphone there should be a responsible adult supervising the kid -even if it's remotely-. In my idea, logs of messaging activity, incoming/outgoing calls/SMS and even the position should be available to the supervisor through a web interface.
Some hack-proof measures to avoid kids bypassing the ROM's security
That's an easy one. CRC checks on some keyfiles would guarantee that the device is not being 'counter-hacked'. Some kids are also very techie, and we should make some defences against kids trying to hack (counter-hack?) the phone.
Alerts triggered on some events (offensive words, whatever)
It could be interesting if somehow the supervisor could receive a notification whenever the kid sends/receives and offensive word, or tries to enter some special tagged website.
Hi! I'm a high school student and part of a team entering a competition where you have to pitch an app idea. For our idea we were thinking of helping people keep track of the foods in their kitchen and sending notifications to them when their foods are soon to be expired. Obviously there would be a lot of data involved in this (how long each food lasts) and we would need to keep the information of many foods to make an effective app.
Our competition was more about the idea side of things than the actual development, and I know nothing about app development, so I was wondering If anyone could explain how this information of mine could be stored (Through cloud i think) and link me to somewhere the could highlight the costs involved.
Anything would be appreciated, and also just general feedback of any difficulties or problems that this app idea could face as well.
Thanks so much!
You would need to either A. Keep the info on a private server that the app can tap into. This would be the fastest and most accurate method. Or B. You can have it pull from pre-defined websites. This will make it drag and unstable should the sites changes anything.