[APP][2.3+] SDR Touch - Live radio on your Android device

Hi,

app not longer in development?

cheers

starbase64

starbase64 said:

Hi,

app not longer in development?

cheers

starbase64

Click to expand...

Click to collapse

Dev may still be busy with University studies: http://xdaforums.com/showpost.php?p=38815508&postcount=87

I would definitely buy this app if it had a frequency manager, and a basic scanning function.

Really looks good so far. Keep up the great work!

I just recently learned there are GUI interfaces for GNU radio that allow building and connecting blocks.

I'm hopeful we'll see something like that on Android in the not too distant future. The app name "SDR Touch" almost seems to indicate that's what you had in mind.

any chance you could add an option to use rtl_tcp running on another machine?

i could probably modify the rtl_tcp app to forward a connection instead of looking for a dongle, but it'd be a lot simpler and more efficient if sdr touch could just talk to the remote rtl_tcp server directly.

martintzvetomirov said:

SDR Touch has a "remote connect" option

Click to expand...

Click to collapse

now i feel like an idiot... i was looking everywhere in the app for such an option, but didn't think to try pressing the menu button.
i think i'm going to blame google and the anti-menu-button phase they're going through for conditioning me against using the menu button.

EDIT: now it's giving me an error that says "Please input the address and port as h ttp://hostname: port". I've entered it exactly like that to test it: "h ttp://hotaru-rpi:1234". if i leave off the "h ttp://", it doesn't give me an error, but doesn't seem to be working either.

martintzvetomirov said:

There is a "Remote connect" button in the latest version of SDR Touch. The buttons on the right are scrollable.

This is a mistake of mine, sorry. You should not enter http. Also keep in mind you need to have a good router and strong wireless signal since streaming the I/Q over network requires 2 MB/s bandwidth.

Click to expand...

Click to collapse

thanks, i've got it working now.

will be sdr touch in google play store again in future?
thx

martintzvetomirov said:

SDR Touch v.1.4 is out in the wild!

New features:

• Fine tuning via pinch-to-zoom
• Improved AM, LSB and USB
• minor GUI tweaks and bug fixes

Download

Click to expand...

Click to collapse

Wow just updated and WFM sounds so clear... Weird since it doesn't look like you did anything there lol.

The zoom feature looks like it could be handy.

If I just had a frequency manager for my car install this would be great!!!

Just an idea for the future maybe a widget with 6 presents would be awesome once that feature is added of course

Keep up the good work!!


Sent from my Galaxy Nexus using xda app-developers app

martintzvetomirov said:

SDR Touch v.1.4 is out in the wild!

Click to expand...

Click to collapse

Thanks ! I was waiting for 1.4 before buying.

I didn't realize the key APK was automatically generated and sent. I've been happy to let Google get their 30% (42+% markup), but such ease makes me wonder.

It's still a bit of a struggle to get everything working together. Re-plugging the dongle seems to help.


Now, how about an API ? I'd recommend the open ST-Ericsson proposed Android FM API that Sony uses, despite it's unclear future.

Of course a few simple public Intents for tuning would be useful too.

martintzvetomirov said:

Well, Google removed SDR Touch from Google Play, a long story. So me and Google are not in good business conditions.

Click to expand...

Click to collapse

I'm well aware of the story, and similar stories of others for various crazy reasons. You have my utmost sympathy on that. I try my best to be "squeaky clean" because my apps are my only income. If Google shut me down I might not be able to continue.

You may know that Google refuses to respond to small developers for most issues we may have. Most emails I've sent get ignored or get a canned response.

AFAICT, Google acts on the DMCA request and that's it. A small dev can do nothing. Frankly, your story has "chilled" any thoughts I might have of doing SDR stuff in my app. It might be interesting, for example, if I could set frequency in your app from mine, but the complainant might come after me.

martintzvetomirov said:

As for an API - I haven't thought about it. It is definitely something I should consider in future.

Click to expand...

Click to collapse

I'd be interested in frequency setting Intents or similar. But I'm very much the exception; pretty much nobody has asked for an API in my app.

Looking Good...

Thanks Sir..

martintzvetomirov said:

Google are actually breaching DMCA section 512(g)(2)(C) by not reinsantiating access to the app they have removed. I mean, I am ready to reveal my source code in front of a lawyer or a judge just to prove that I haven't copied anything from anyone if required. But as an indie developer the time investment is not worth it, what is important is that people that really want ot have the app can download it and use it.

P.S. Presets and waterfall are on the top of the TODO list for the next version or two

Click to expand...

Click to collapse

For frequency setting could one just send a packet to the rtl sdr dameon ?

---
OK, I feel I'm 100% on "your side" on this matter, so please don't misunderstand when I say this:

1 - Google tries to be an "almost everything is computerized" company. They do their best to minimize human contacts and the need for them. In a focused pursuit of money, this is an effective business strategy.

I refuse to be one of the many Internet "armchair CEOs" who think they know better how to run one of the few richest companies on Earth. I'm positive 99.9% of us couldn't run Google any better (strictly money wise) than they are. How can you argue with such success ? The "armchair CEOs" will say their way (IE being "nicer" to developers and users) is better in the long run.

So, in the strict pursuit of money, I think it likely makes sense that Google put very few resources into defending app devs against DMCA or similar requests. How many engineers and lawyers would it take for Google to analyze each situation and defend the devs ?

Yes, on the other side there may be more app sales which always helps Google. I'm sure they help defend larger devs, and/or the larger dev companies themselves are the DMCA target instead of Google.


2 - I don't know all DMCA particulars, but I'm not convinced Google is breaking any laws with their lack of response to DMCA counter claims.

If they ARE breaking laws, I hope and I'd expect that someone somewhere will take them to court, civil or criminal or whatever.

Each news item of a few I've read about this issue, sends some "shame" in Google's direction, but hasn't accomplished anything yet. Maybe some better "shaming" or "leverage" method is needed.

For apps, Google is not merely a file hosting provider, or a "You-tube" style provider. Google Play is very much more "curated", and they have a "contract" with all registered devs that is likely very one sided. I've never even bothered to read it, other than a few parts about bypassing Google's 30%, because I have zero leverage as a sole individual.

I think it's similar to this:

- In public spaces you cannot discriminate against people on the basis of race, religion etc.

- In a private business the owner is 100% within his legal rights to decide to admit people or not on the basis of race, religion, political affiliation, hair color, whatever they want. He may be a jerk, but it's his property and his choice.

Google is the private business owner on whose virtual Play property the apps are displayed.

Google can indefinitely pull apps for any or "no" reason.


Again, I'm not intending to defend Google; Except in the same way I defend free speech, even when I find that speech distasteful.

I, or the CM guys, or anybody can start their own app store and decide what apps will or won't be allowed.

---
Now, a further argument could be made that Google is dominant in the apps space. We could further argue that the apps space should be considered a public place for the good of all. We do the same (somewhat, still...) with the "public airways" of radio broadcasting.

But then, you've got some kind of governmental, or world body type entity that's deciding what apps to allow or not. LOL !