Lost sheep finder in the white spaces, please.

by [EMAIL PROTECTED] » Fri, 20 Jun 2008 05:21:39 GMT

Sponsored Links
 Being a motivated non-expert. I understand that higher frequencies
carry more data, are more line of sight,and are absorbed by smaller
conductive bodies - like rain drops AND that lower frequencies carry
less data, go through and around buildings and are not as easily
absorbed by small conductive bodies. People are also more comfortable
with, and have more history with, television signal frequency
radiation than cell phone radiation.  I understand there is some white
space around 54 MHz.

We talked about an Android appliance type location reporting phone
that kids could wear laced into their shoes. In the interest of not
slighting such a phone, parents could use the same device to find
missing children in public places where vision may be obscured. To
avoid ad nauseum.

I cannot think of a better, more technology (physical characteristics
of spectrum and public acceptance of spectrum) matched, use of white
space than lisensed appliance spectrum where the appliances use modern
signaling and can triangulate off known towers to reliably get
position in the interest of reliable location of children by their

There has to be enough subscription service to pay for the radios, but
first reliably determine and communicate location in these
environments.  I think that means low frequency spectrum that is


Other Threads

1. AV sync and Audio HAL latency question


I'm currently working on an AV sync issue seen on froyo, seen mainly
with low audio sampling rates. Basically, I'm seeing that the video is
about 300 ms ahead of the audio. Now I've narrowed down the issue to
this formula in AudioTrack.cpp

mLatencyUs= afLatency + frameCount*1000/sampleRate.

mLatencyUs is used to calculate the realTimeClock, used by the avsync
algorithm in the Awesome player.

The afLatency is the audio latency reported by our audio HAL. For our
case it is reporting 92.8 ms (4096 buffer, 44100 sampling rate). The
second term of this formula is always giving me 371.5-372, which is 4
times the latency reported by the audio HAL. By doing experiments,
I've found that multiplying afLatency by 4 at audio HAL level (so
mLatency would be 372 + 372), is giving me good av sync.

does it makes sense to anyone what I'm doing ?
is mLatency just used for av sync ?
Could I have other bad consequences to increase the afLatency value ?
So far I haven't seen any.


unsubscribe: android-porting+unsubscr...@googlegroups.com


bikin acara ngumpul2 di depok yuk, skalian bisa sharing :)

"Indonesian Android Community [id-android]"

PING'S mobile
Email: sa...@pings-mobile.com  Ph. (021) 96087100
Yopie Ratjoen
Email: yo...@ratjoen.com  Ph. 08977726681
Gila original
Email: i...@gilaoriginal.com  Ph. (031) 91555898

Aturan Jual/Kloteran ID-Android  http://goo.gl/azW7

3. Energizer xpal xp200

4. 芦OOT禄 id-android never sleep

5. Messing with .apk

6. Image loading from remote problem

7. Nexus one USB Driver not working with 2.2 and W7