Related
Hi everyone
I read a lot about tracking mobile phone with the Cell ID and neighbour Cells via GSM service [1]
the GSM protocol can initiate a scan of the neighbor cells and their signal strength which leads to a position accuracy <100m
Does someone know more about it?
second using silent/stealth sms to receive cell id [2][3][4] (no English infos found you got censored? ) google translate if you don't speak German...
this special sms type does not show any information on your handset, its silent! So you can't detect when you receive one.
On which level of the phone is this behavior handled? Baseband/Radio or the OS?
As example on Android you get the kernel source and all the source of the standard apps running on it. Probably a way modify the way it reacts if it is in this part of the code.
The Radio/Baseband is NOT?[needs clarification] open source, so no chance here?
Is there a way to detect this behavior?
[1] http://en.wikipedia.org/wiki/GSM_localization#Handset_Based
[2] http://de.wikipedia.org/wiki/Short_Message_Service#Spezielle_Nachrichtentypen
[3] http://www.heise.de/mobil/artikel/ueberwachung-per-Mobilfunk-222789.html
[4] http://www.heise.de/newsticker/meld...ung-wird-zur-Massendienstleistung-130253.html
Hi mopodo,
just FYI, "silent sms" can be sent wia WM, a tool called "Hush SMS" allows this.
And there is no information carried via this SMS back to the originator.
Cell-ID based tracking can only be done by the owner of a cell tower, i.e. the operator. And since this requires lots of time, they (regularly) only do this on request of the prosecution.
But I do not know more about this topic, the above information is what I (supposedly) know about this.
Regards
Zuzler said:
Hi mopodo,
just FYI, "silent sms" can be sent wia WM, a tool called "Hush SMS" allows this.
And there is no information carried via this SMS back to the originator.
Cell-ID based tracking can only be done by the owner of a cell tower, i.e. the operator. And since this requires lots of time, they (regularly) only do this on request of the prosecution.
But I do not know more about this topic, the above information is what I (supposedly) know about this.
Regards
Click to expand...
Click to collapse
try to read more about CITA and ECITA : enhanced cell id timing advance hahaha
ghassen32 said:
try to read more about CITA and ECITA : enhanced cell id timing advance hahaha
Click to expand...
Click to collapse
Welcome to the forum! Tell us a little on what you know about CITA?
In reviewing the new page on the nexus s, the only thing I really am interested in is the internet dialing/SIP. I have tried SIPdroid on the captivate, and it works ok, but very staticy on the other end. I am curious as to whether anyone knows where the SIP client for 2.3 came from. Is it SIPdroid? Did Google buy SIPdroid? I would also be very interested in flashing only the SIP part of Gingerbread 2.3, the rest of the update isnt all that interesting to me. If anyone comes across info or files related to this, post here.
Thanks
Benny1234 said:
In reviewing the new page on the nexus s, the only thing I really am interested in is the internet dialing/SIP. I have tried SIPdroid on the captivate, and it works ok, but very staticy on the other end. I am curious as to whether anyone knows where the SIP client for 2.3 came from. Is it SIPdroid? Did Google buy SIPdroid? I would also be very interested in flashing only the SIP part of Gingerbread 2.3, the rest of the update isnt all that interesting to me. If anyone comes across info or files related to this, post here.
Thanks
Click to expand...
Click to collapse
Google bought Gizmo5 about 1 year ago. This is probably where they got the SIP client.
From what I read on the official document, internet calling works via wifi only.
I hope and i'm sure the devs will modify this to make it work via 3G.
A few things:
1) You are using VoIP over 3g? It's probably not goind to sound great, and any free client you have is not going to implement g729 b/c it requires a license so GSM is your best bet for low bandwidth, and it doesnt sound great.
2) a. No it is not sip droid. b. Sipdroid sucks - it is a terrible client. Basically the PBXes.org people who "wrote" sipdroid took the example "client" from mjsip and jammed an android interface on it. The backend sip implementation is pretty crappy, doesnt support call transfer, does multiple registrations and can flood a registrar.
2) CSipSimple is a much more promising client (IMO). And while has not yet implemented transfers yet, it is based on pjsip, a very well implemented sip stack that does fully support these features. Also, I have found that CSipSimple has less fuzzy audio too.
3) I have been looking at the 2.3 SIP stuff - It's not like you can just take that part from 2.3 and "flash" it to your device.
Besides that, the implementation that is in the 2.3 SDK looks very simplistic so far - and it is unclear to me whether or not the dialer will allow native SIP calling, or if google has just put in sip libraries for people to develop SIP applications. I see no where in any settings that allow you to specify "phone wide" sip credentials.
This would seem to be further backed by the sample "walkie talkie" application that is available with the 2.3 sdk.
4) I doubt google bought gizmo5 for their sip stack/client. There are many highly compliant open source sip stacks freeley available: sofia-sip, pjsip, jain-sip etc. etc. I dont know what is "under the hood" but what google has exposed via the SipProfile so far looks to be sub-par.
5) "Internet calling" support isnt going to be enabled on all devices, although i think the nexus s probably will be one of the few, in fact even in the AVD I get an "internet calling not supported" message when I try to call a sip URI from the dialer.
Your best bet right now - try out CSipSimple. Native SIP support is going to be a bit raw for a while is my guess.
SIP dialing
Thanks etamme ! Thats some good information! Yeah I would like to use SIP for international calls, wifi and 3G data. I use the phone when we travel and have foreign sims. So making GV /G5 calls would be perfect. I used to use an iphone, but unlocking became a PITA recently. (read as 6.15.00 BB)
Will check out CSSipSimple, I assume it will work with G5. I'm glad someone else realizes Sipdroid is terrible. Every time I use it the other party complains. With all the updates theyve done they have failed to address a major problem.
Thanks again!
have you tried this?
i'm trying it now
http://androidandme.com/2010/12/news/how-to-place-and-receive-internet-calls-with-android-2-3/
Benny1234 said:
I am curious as to whether anyone knows where the SIP client for 2.3 came from.
Click to expand...
Click to collapse
Gingerbread has a built-in SIP stack.
etamme said:
A few things:
1) You are using VoIP over 3g? It's probably not goind to sound great, and any free client you have is not going to implement g729 b/c it requires a license so GSM is your best bet for low bandwidth, and it doesnt sound great.
2) a. No it is not sip droid. b. Sipdroid sucks - it is a terrible client. Basically the PBXes.org people who "wrote" sipdroid took the example "client" from mjsip and jammed an android interface on it. The backend sip implementation is pretty crappy, doesnt support call transfer, does multiple registrations and can flood a registrar.
2) CSipSimple is a much more promising client (IMO). And while has not yet implemented transfers yet, it is based on pjsip, a very well implemented sip stack that does fully support these features. Also, I have found that CSipSimple has less fuzzy audio too.
3) I have been looking at the 2.3 SIP stuff - It's not like you can just take that part from 2.3 and "flash" it to your device.
Besides that, the implementation that is in the 2.3 SDK looks very simplistic so far - and it is unclear to me whether or not the dialer will allow native SIP calling, or if google has just put in sip libraries for people to develop SIP applications. I see no where in any settings that allow you to specify "phone wide" sip credentials.
This would seem to be further backed by the sample "walkie talkie" application that is available with the 2.3 sdk.
4) I doubt google bought gizmo5 for their sip stack/client. There are many highly compliant open source sip stacks freeley available: sofia-sip, pjsip, jain-sip etc. etc. I dont know what is "under the hood" but what google has exposed via the SipProfile so far looks to be sub-par.
5) "Internet calling" support isnt going to be enabled on all devices, although i think the nexus s probably will be one of the few, in fact even in the AVD I get an "internet calling not supported" message when I try to call a sip URI from the dialer.
Your best bet right now - try out CSipSimple. Native SIP support is going to be a bit raw for a while is my guess.
Click to expand...
Click to collapse
Running Gingerbread right now...I can tell you that "Internet Calling" works straight from the dialer. However, my experience with built in SIP over wifi on Pbxes.org is that cSipSimple is more usable. There is a noticeable lag using the built in SIP configuration and only UDP works for PBXes since it doesn't allow a hybrid mode like cSipSimple (TCP for registration, UDP for connection due to PBXes incomplete TCP implementation). The problem I have with cSipSimple is that the mic gain is way too high and it picks up all the background noise.
Benny1234 said:
In reviewing the new page on the nexus s, the only thing I really am interested in is the internet dialing/SIP. I have tried SIPdroid on the captivate, and it works ok, but very staticy on the other end. I am curious as to whether anyone knows where the SIP client for 2.3 came from. Is it SIPdroid? Did Google buy SIPdroid? I would also be very interested in flashing only the SIP part of Gingerbread 2.3, the rest of the update isnt all that interesting to me. If anyone comes across info or files related to this, post here.
Thanks
Click to expand...
Click to collapse
Looks to me that it is based on JAIN-SIP from inspecting the AOSP source. Have look at http://android.git.kernel.org/?p=platform/external/nist-sip.git;a=tree;hb=HEAD
JAIN-SIP was developed by NIST and the AOSP references NIST also. Haven't dug deeper to confirm however.
etamme said:
A few things:
3) I have been looking at the 2.3 SIP stuff - It's not like you can just take that part from 2.3 and "flash" it to your device.
Click to expand...
Click to collapse
What would it take to extract the SIP bits from the AOSP and use it as a reference library for a SIP enabled application? I have never tried but it should be possible no?
Wrong mic (top)
OCedHrt said:
The problem I have with cSipSimple is that the mic gain is way too high and it picks up all the background noise.
Click to expand...
Click to collapse
You can set the mic gain:
While in a call, click the menu button (bottom left)
Select Media
Move the Mic slider left to lower the volume (quickly before the screen goes back to default).
However, this does not really solve the problem because cSipSimple uses the mic on top of the phone which does not pick up your voice very well, and pics up the sound from the receiver (speaker) causing the person on the other end to hear an echo of everything they say.
I have not been able to find a way to change this behavior.
anyone having an issue with phone calls being rejected with sip dialing? I've tried sipdroid, csipsimple and native sip. using google voice forwarding a number i recieved from ipkall, and using iptel.org instead of pbxes
Hello Community,
My question is: What is possibe with the NFC-Interface today?
Only read and write? or
P2P connections?
Card Emulation?
I was looking for a long time...
Thank you
...Geselthyn
Geselthyn said:
Hello Community,
My question is: What is possibe with the NFC-Interface today?
Only read and write? or
P2P connections?
Card Emulation?
I was looking for a long time...
Thank you
...Geselthyn
Click to expand...
Click to collapse
The capability exists in the API as of 2.3.3 for Read and Write capability as well as P2P (there are SDK demos for these three up as well).
The hardware is present (including a secure element) for card emulation, but I can't say with certainty if that's present in the API yet (I don't believe it is).
krohnjw said:
The capability exists in the API as of 2.3.3 for Read and Write capability as well as P2P (there are SDK demos for these three up as well).
The hardware is present (including a secure element) for card emulation, but I can't say with certainty if that's present in the API yet (I don't believe it is).
Click to expand...
Click to collapse
Thank you for your answer. But what exactly means P2P? What is the different to the "read and write"?
Geselthyn said:
Thank you for your answer. But what exactly means P2P? What is the different to the "read and write"?
Click to expand...
Click to collapse
Read and Write allow for the reading of NFC tags and the Writing of NFC tags (format the tags for NDEF messages and write the message contents to the tag).
P2P refers to the fact that NFC can be used to open a communication socket between 2 NFC enabled phones. This socket can then be used to transfer data between the 2 devices.
krohnjw said:
P2P refers to the fact that NFC can be used to open a communication socket between 2 NFC enabled phones. This socket can then be used to transfer data between the 2 devices.
Click to expand...
Click to collapse
Thanks for the new Post
But is it just possible to use the communication between 2 phones?
It's very much possible to initiate P2P communication with any NFC enabled device that supports the NDEF format. P2P communication is not limited to (android) phones.
NDEF is a standard created by the NFC-Forum (= Phillips, Nokia, etc.) and you can expect future NFC phones (including those running Windows Phone or iOS) to also support that standard. I'm of yet unsure how this works with any desktop/terminal readers though... It appears the desktop/terminal must support the 'NPP - NDEF Push Protocol' in order to talk to an Android phone, which android devs say to publish a spec on soon. But I'm unsure why android devs need to publish a spec on communication on the desktop/terminal-end, if it's a standard created by a whole nother group.
Additionally: Card emulation is not supported (yet) in the Android SDK as it's "actually very hard to do this in a consistent way across the Android platform, due to the current hardware architecture of NFC", and I'm not sure how possible it is to share cards with P2P, or achieve any comparable result...
Thanks for the Answer!!!
Is it possible, that you can do more Things with the NDK than with the SDK?
Best Regards,
Geselthyn
hi,
i used an existing sound recorder and implmed, one by myselft.
There are some samples form MS, how to do sound recording too.
Now i want to send the recorded sound to another user's android phone.
Should be simple
- Send as email attachment
- Send via bluetooth
I did not find a program on the marketplace and trying to implent this by myself i found no example, how to do this. In this forum and on other resources, i read, that it currenty is not possible, to send email attachments programatically.
Is there really no way, to do such a simple task, as sending/sharing an audio file (after converting the recorded byte-array to .wav format) to another phone via email or bluetooth ?!
regards,
hannes
E-Mail attachment shouldnt be hard but WP7 does not support bluetooth file transport
Forget about bluetooth (until MS releases some kind of BT API). As for email attachment, you have a two options:
- implement smtp/exchange client by yourself;
- use (create) http "proxy" service on the external server (you sending audio data and additional parameters, and service forms the message with attachment).
Both ways a really not easy and expensive.
Send me a PM and I'll write something and upload it to the marketplace tonight.
MJCS said:
E-Mail attachment shouldnt be hard but WP7 does not support bluetooth file transport
Click to expand...
Click to collapse
The problem is: An email attachment in fact IS hard (impossible), without using some external service.
sensboston said:
- implement smtp/exchange client by yourself;
- use (create) http "proxy" service on the external server (you sending audio data and additional parameters, and service forms the message with attachment).
Both ways a really not easy and expensive.
Click to expand...
Click to collapse
Thank your for your response!
This is quiete the same, what i found out too. It is possible (i am a developer and i can host such a sevice on my domain) but that's not the way i like to do it.
I play in a band and recorded some demo with the phone and now want to send this recording to my band colleagues but it was not possible to do this.
This should be as simple as "open a bluetooth connection" + send.
On a windows phone, store it in the "media collection", on other phones, store it on a selectable location on the file system.
This is really anoying.
I like the platform and like developing for it but not beeing able to do such simple things...it's hard to argue, why WP is better than f.e. android.
MJCS said:
Send me a PM and I'll write something and upload it to the marketplace tonight.
Click to expand...
Click to collapse
I think, i don't get the point of your reply.
What do you want to write - a program, that does does recording audio + email it to other users?
I am searching for a solution, how to develop this by myself, not for a program on the marketplace.
regards,
hannes
HannesB said:
I think, i don't get the point of your reply.
What do you want to write - a program, that does does recording audio + email it to other users?
I am searching for a solution, how to develop this by myself, not for a program on the marketplace.
regards,
hannes
Click to expand...
Click to collapse
Oh...and I had already started programming it. Oh well. Basically do this:
Upload to SkyDrive using the API or...
Create a WCF Service that allows you to send a file stream
Have the files stream get written to the server as a GUID
Return link to file
Send link via e-mail
Have file expire after 24/hrs or something
hi,
thank you, for your response.
...and starting programming on it so fast.
(if you really started programming it - put it on marketplace, i am sure, many people would like souch a tool)
The "problem" with this approach (and email too) is:
- i need an internet connection to upload
- the people that want to download the file, need an internet connection
- there are still people, that don't have an internet flatrate for their phone or any internet connection (or have to use roming, if not at home) and jus say "..hey, you recorded it - send it to me via bluetooth".
Seem's, the steps you discribed, are the only option, to do it. The phone i used 5 year ago, could send pictures and audio recording via bluetooth and since the mango update is currently released and doest not contain an api for bluetooth access, i think it will not be released soon, if ever.
In another posting i read: "I take a picture with me and my friends and i can't send them over the bluetooth. They have cheap dumbphones and I have Omnia 7 and I'm embarrassed. Bluetooth filetransfer is essencial feature."
Ok, this is "offtopic" now, sorry but anyway thank you for your responses.
The steps you explained are possible for sure, but in my opinion a bit "much work", for simply sending some data != text.
HannesB, I agree with you, it's kinda annoying. But, probably, MS will open some new APIs in future (WP7 is based on WinCE so it's not such a big deal, code/drivers are already exists for that platform). Don't forget - WP7 platform is still too new.
I have an app called CopyCat. It will let you do recordings (and change the playback as well).
http://www.windowsphone.com/en-US/search?q=copycat
It will let you store to the Public folder of your DropBox account.
As previously mentioned, unfortunately there is no way to attach WAV files to an email currently.
Hope this can be of help.
Why are you guys complaining about a function that you can have with evernote you can record sound and save it on your evernote account over your windows phone
Hi to all,
sorry for my poor english but this is not my first language.
I'm a Ph.D student and i'm trying to understant if something we are working on is feasible.
We are looking for a method to know in real time, directly on the phone, which API an application is calling.
For example, i wonna know in realtime if an application call an API to turn on the bluetooth or call the API to send an information (of any kind) through the bluetooth connection.
Any help would be really appreciated.
If you need further information just ask, maybe my explanation was a little bit too shallow.
Lierus said:
Hi to all,
sorry for my poor english but this is not my first language.
I'm a Ph.D student and i'm trying to understant if something we are working on is feasible.
We are looking for a method to know in real time, directly on the phone, which API an application is calling.
For example, i wonna know in realtime if an application call an API to turn on the bluetooth or call the API to send an information (of any kind) through the bluetooth connection.
Any help would be really appreciated.
If you need further information just ask, maybe my explanation was a little bit too shallow.
Click to expand...
Click to collapse
Hi Lierus,
no problem about the english, it is not my mother tongue too (I'm a PhD too)...
Did you take a look at "Intent"? http://developer.android.com/guide/components/intents-filters.html
It is the common way to both start a new activity in the same application and start an Activity/Service in another application that expose an API invokable by an Intent.
I do not know if this can help you or not? however if you give more info maybe I can give you a more precise answer.
Simone
Hi Simone, thanks for your answer.
I bet you're Italian .. I am too
Maybe i was too generic in my original question.
My final purpose is to know when a generic application (a third party application) uses some devices or, more generally, calls an API to use such devices. These calls that i want to monitor are the ones related to the manifest's permissions.
This action should be registered by the application i'm writing..
Example:
Application "Pippo" has the permission to use the Bluetooth (grant by the user during installation).
My application "Monitor" should know and register when Pippo really invokes the Bluetooth Api!
Thanks again
Marco
Lierus said:
Hi Simone, thanks for your answer.
I bet you're Italian .. I am too
Maybe i was too generic in my original question.
My final purpose is to know when a generic application (a third party application) uses some devices or, more generally, calls an API to use such devices. These calls that i want to monitor are the ones related to the manifest's permissions.
This action should be registered by the application i'm writing..
Example:
Application "Pippo" has the permission to use the Bluetooth (grant by the user during installation).
My application "Monitor" should know and register when Pippo really invokes the Bluetooth Api!
Thanks again
Marco
Click to expand...
Click to collapse
ok, I understood.
I think that if you want to build an app like a "monitor" you have to monitor the "Intent" that the apps use in the Android ecosystem to call both external API (third party application) or internal (e.g., start a new Activity). For example, we have a device with an app (named Pippo) that sends data over the bluetooth connection.
Basically, Pippo calls isEnabled() to check whether Bluetooth is currently enable:
Code:
Intent enableBtIntent = new Intent(BluetoothAdapter.ACTION_REQUEST_ENABLE);
startActivityForResult(enableBtIntent, REQUEST_ENABLE_BT);
the Monitor app should register an intent-filter on the "ACTION_REQUEST_ENABLE" action, so when the Pippo sends the intent, the Monitor receives the Intent and then forwards the Intent to the right app (like a man-in-the-middle).
what do you think?
p.s. take a look at this app https://play.google.com/store/apps/details?id=uk.co.ashtonbrsc.android.intentintercept
Best,
Simone
Yes this is a good starting point..
I will investigate this opportunity
i hope that i can discriminate and understand who invokes the intent (not just when it is invoked).
Thanks again.
Marco
Is it works?
Sent from my LegoIce™Galaxy_S4 using XDA Premium 4 mobile app
dhirajahuja432 said:
Is it works?
Sent from my LegoIce™Galaxy_S4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes
try it yourself,
https://play.google.com/store/apps/details?id=uk.co.ashtonbrsc.android.intentintercept
the implementation of this app, is based on the idea explained above.
Simone