It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: AdmireTheDistance
originally posted by: StargateSG7
8) Custom HACKED software takes that UNFILTERED
electrical noise and digitally converts it to weak but
discernable impulses of numeric values that represent
amplitude and frequency too!
9) That series of numbers is compared to a secret onboard
database of human voice samples of COMMON phonemes
(male and female) ad pronunications of common vowels
and consonants.
Oh really? I reverse engineer and modify proprietary mobile device firmware (and write custom firmware/kernels) for a living, so where does this "secret onboard database" reside. Bear in mind, I have full access to the entire partition table on modern devices, including bootloaders and radios, so I want specifics; Which block(s) and in which partition(s)?
10) the VOCODER then re-creates a mimicry of what
the voice PROBABLY sounded like in it's original form.
That VOCODER data is then converted to easily compressible
text which is then transferred to VARIOUS locations using
common network tarnsmission techniques (TCP/IP or USB)
OR stored secretly on the connected computing system
for LATER PHYSICAL retrieval!
And how do such relatively resource intensive processes manage to completely mask themselves from the CPU's raw output and from the mobile radio?
originally posted by: combatmaster
a reply to: StargateSG7
Why oh why then, is there no app that makes your screen a mic?
originally posted by: StargateSG7
For which TYPE of connected device?
originally posted by: AdmireTheDistance
originally posted by: StargateSG7
For which TYPE of connected device?
Let's go with Android, just cause it's easier to dump and reverse everything. Again, my question is: Where exactly is your "secret onboard database" located, and where are the (presumably numerous) calls to it (and the data passed with those calls)?
Hell, where is the "custom hacked software" that encodes the information in the first place? Such a thing would be far too large to be contained in the low-level display drivers. I know for a fact that nothing like that resides at the kernel level, since I've written large parts of, modified, and built numerous kernels. I also know for a fact that no such code exists in the frameworks, libcore, or any of the native libraries, and to suggest that such a thing occurs at a higher level than that is just laughable. So where is it?
originally posted by: StargateSG7
I've got no idea where such code would be since
in any public repository or Linux distribution it
WOULD NOT BE EXPOSED there...I am suggesting
that it would be uploaded secretly...
...since HOW many people DO YOU KNOW would disassemble a linux/android/windows mobile/iOS distro!
originally posted by: AdmireTheDistance
originally posted by: StargateSG7
I've got no idea where such code would be since
in any public repository or Linux distribution it
WOULD NOT BE EXPOSED there...I am suggesting
that it would be uploaded secretly...
As I've already said, the idea of something such as what you're talking about running as a high-level process is laughable, at best, and any lower-level code, even if "uploaded secretly" somehow, wouldn't do anything, as it would require recompiling the entire operating system with the "secret" code in place.
...since HOW many people DO YOU KNOW would disassemble a linux/android/windows mobile/iOS distro!
Several, including myself.
originally posted by: StargateSG7
See where I am getting at?
1) You are speaking near a capacitive touchscreen.
2) The pressure waves produced by your vocal chords
follow a specific pattern of rise-times and fall times.
3) Those impulses HIT the screen bouncing back off
the front-side acoustically reflective surface.
4) Those bouncing waveforms disturb the microdust
and water vapour within the air close to the screens
surface.
5) That moving dust and water vapour (i.e. humidity)
changes the CONDUCTANCE of that 3D-XYZ space.
That change in conductance INDUCES a spurious
introduction of ELECTRICAL NOISE into the
capacitive touch screen circuits.
6) That noise travels to the ADAC (analog to digital
converter software/hardware) which NORMALLY filters
it out because it is UNWANTED ELECTRICAL NOISE.
7) That unwanted electrical noise follows the
SAME PATTERN as the acoustic waveform that
actually hit the screen as pressure waves.
8) Custom HACKED software takes that UNFILTERED
electrical noise and digitally converts it to weak but
discernable impulses of numeric values that represent
amplitude and frequency too!
9) That series of numbers is compared to a secret onboard
database of human voice samples of COMMON phonemes
(male and female) ad pronunications of common vowels
and consonants.
SO! CAN YOU READ THE ABOVE AND DO YOU UNDERSTAND IT?
If you can, DO YOU AGREE with the BASE engineering
and mathematics of such technology! If you CANNOT, then
I can't help you and you need to consult an expert level MScEE
who KNOWS something about Digital Signal Processing,
vocoder technology, and noise filtering.
originally posted by: BASSPLYR
Hey bedlam,
If you wanted to thwart laser mics on the old window trick would taping a speaker cone to a window pane and playing white noise be sufficient. Or would there be a software code that filters through the white noise. Like they can do with phones and bugs. If the volume on the speaker is high enough do you think it would work if your a poor dude on a budget like me. I got 4 10 inch subwoofers and 400 watts I can use. Would it work in your opinion.
originally posted by: TerryDon79
a reply to: Bedlam
Your additional point 10 has been pointed out before. Look back and he says that Occam's razor isn't always the case because (pick any 3 letter agency) wants to make it more secret and have money to burn.
:eye roll
originally posted by: StargateSG7
originally posted by: AdmireTheDistance
originally posted by: StargateSG7
I've got no idea where such code would be since
in any public repository or Linux distribution it
WOULD NOT BE EXPOSED there...I am suggesting
that it would be uploaded secretly...
As I've already said, the idea of something such as what you're talking about running as a high-level process is laughable, at best, and any lower-level code, even if "uploaded secretly" somehow, wouldn't do anything, as it would require recompiling the entire operating system with the "secret" code in place.
...since HOW many people DO YOU KNOW would disassemble a linux/android/windows mobile/iOS distro!
Several, including myself.
===
Other than someone like me and you, very FEW would
disassemble an OS and debug it. Consumers just want something
that works and if your smartphone is intercepted during shipment
and some chips and microcode swapped out by a large organization,
(i.e. NSA/CIA/DIA/MI6/CSE/GRU, etc) you'd never know
as a consumer what was happening.
From a technical point of view MANY AGENCIES recompile code
for their own purposes. I will use the example of the Aircraft Carrier
USS Ronald Reagan (CVN-76) which used (uses?) a re-compiled version
of Windows 2000 (YES! Windows 2000) for many of its on-board systems.
They put extra cryptographic functions into it and
some ship systems hardware-specific code in it!
In fact, I think some parts of (CVN-76) STILL run Win2000!
So it is NOT INCONCEIVABLE that agencies compile their
OWN OS'es for whatever purposes they desire and since
android is almost fully open source, it would be a piece
of cake to make a new version with DEEPLY HIDDEN
functionality.
In any case the system I am espousing would HARDLY be
regarded as a high-level task. It would be hidden deeply
and darkly into the Linux OS code / Windows System.
It simply WOULD NOT SHOW UP in any task manager
or CPU logging function.
You would have to do a hardware debug to find out
what instructions are being fed to which chips.
On smartphones if it was BASEBAND Radio Modem
microcode, Android/iOS/WinMobile would NEVER
SEE the code AT ALL since baseband OS'es operate
SEPARATE FROM AND BELOW the primary operating
system in an asynchronous manner!
originally posted by: Bedlam
originally posted by: StargateSG7
See where I am getting at?
1) You are speaking near a capacitive touchscreen.
2) The pressure waves produced by your vocal chords
follow a specific pattern of rise-times and fall times.
3) Those impulses HIT the screen bouncing back off
the front-side acoustically reflective surface.
4) Those bouncing waveforms disturb the microdust
and water vapour within the air close to the screens
surface.
Sound waves don't cause net motion of aerosols. The energy in speech audio is insanely low.
5) That moving dust and water vapour (i.e. humidity)
changes the CONDUCTANCE of that 3D-XYZ space.
That change in conductance INDUCES a spurious
introduction of ELECTRICAL NOISE into the
capacitive touch screen circuits.
It does not. Capacitive touch screens depend on the relatively large change in mutual coupling between drive and sense lines in the screen caused by the presence of a finger/stylus. You do not get a measurable change from sound. Hint: go look up a table of the change of dielectric constant vs air pressure. Now, find out how much air pressure change is associated with conversational level audio. Insanely small multiplied by insanely small = forget it. This is what you claim is being sensed with this method. Ain't happening.
6) That noise travels to the ADAC (analog to digital
converter software/hardware) which NORMALLY filters
it out because it is UNWANTED ELECTRICAL NOISE.
The front end of this system will filter it out. It can't be programmed away. And the noise is far far far far below a single bit change. Below the inherent noise in the ADC. Below the Johnson noise in the resistors in the front end. Below the transistor noise in the preamps. Below the switching noise that's caused by muxing the sense and drive lines. You might as well try to use the thing to detect electrical noise caused by the background RF of the universe.
7) That unwanted electrical noise follows the
SAME PATTERN as the acoustic waveform that
actually hit the screen as pressure waves.
The unwanted electrical noise is less than the other noise in the system by a few dozen orders of magnitude, and is lost.
8) Custom HACKED software takes that UNFILTERED
electrical noise and digitally converts it to weak but
discernable impulses of numeric values that represent
amplitude and frequency too!
All the King's hackers and all the King's software geeks can't put together something that isn't there.
9) That series of numbers is compared to a secret onboard
database of human voice samples of COMMON phonemes
(male and female) ad pronunications of common vowels
and consonants.
Right. Stored where? Compared by what?
SO! CAN YOU READ THE ABOVE AND DO YOU UNDERSTAND IT?
If you can, DO YOU AGREE with the BASE engineering
and mathematics of such technology! If you CANNOT, then
I can't help you and you need to consult an expert level MScEE
who KNOWS something about Digital Signal Processing,
vocoder technology, and noise filtering.
Raises hand. Got one right here. And it's just wrong.
You left out point 10: Or, you know, just use the microphone that's on the phone. Problem solved.
originally posted by: Bedlam
a reply to: StargateSG7
Exhaled air isn't sound.
The rest of your cites are either non sequiturs or you're making huge assumptive stretches of what they're telling you.
originally posted by: StargateSG7
Regarding the above papers...they are a bit of a stretch
but have SOME support for my assertions that indoor air
is dirty containing particulate matter that can have it's
electrical properties change is it moves about in a room
which was caused by exhalation (AND SPEECH!) which
can then affect in some small (or large?) way the noise
characteristics of an electronic device caused by induced
or stray current.