According to some of the docs from the Snowden leak, most bugs are pretty simple - mostly FM analogue devices, optionally with frequency inversion/scrambling, but GSM bugging/tracking are not uncommon. In fact, in one of the documents, the CIA recommended bugs were mostly available from amazon... which would make tracing it back to a particular government body a nightmare!
Don't want to expose your abilities, but I'm sure they have tiny environmental energy harvesting microburst transmitting bugs for when it really counts.
As I mentioned, it appears to depends on
what is being bugged - commercially available/disposable bugs were advised on two documents (I can only assume they were for low priority targets that aren't going to be actively searching for bugs

): while the NSA catalogue (2009) contained a lot of retroreflector bugs/beacons ("When the unit is illuminated with a CW signal from a nearby radar unit, the illuminating signal is amplitude-modulated with the PPM square wave. This signal is re-radiated, where it is picked up by the radar, then processed to recover the room audio.") they had a lot of fancier items in that and other documents (I quite like the look of that one that's built into a USB cable with intent on bridging air-gaps: it's
tiny!
A lot of how they're using firmware on commercial hardware (notably hard drives) to rewrite the BIOS (How? Haven't a clue!) to interface with "implanted" RF hardware (often RF retroreflector which comes off as an AM according to the NSA ANT catalogue

) makes for some fascinating reading!
Sources: All available on Wikileaks - specifically "German BND-NSA Inquiry Exhibits", "The Spy Files"(misc. curation) and "Vault 7"(misc. curation) - most of which are just collated leaks from lots of sources

Either way, this isn't my field - I'm relying on wikileaks for sources on what the big players are doing

I'm not going to dance with
that leviathan - if they ever decide to bug me, I'm not going to know about it regardless of what I build! But then again, that was never really my intention - rudimentary bug-finding was more a serendipitous use for my project rather than an actual goal!
...and on that note, I should probably stop directly talking about CIA/NSA leaks now, even if the tech side of things is fascinating!
ANYWAY - Back to the topic

......
> to OP: I would suggest getting that AF stage quiet before proceeding. Also some ideas:
whatever you use for a visual indicator (bar graph/moving coil/..) give it at least a fast/slow characteristic
AND have a non-selfresetting maximum pointer OR a bistable indicator corresponding to adjustable limit of
the range.
Hmmm - not a bad suggestion! As I said, I had hacked together an AF stage from an LM386 for testing - with intent on making a "better" audio stage once I had the RF stage(s) prototyped - it's a bit of a catch-22! The AF/RF/Monitor triangle of interrelated modules!
My current plan is to use the hacky-LM386 audio stage to prototype a low quality RF stage so that I can use that to redevelop the audio stage to a higher quality (which I can then use to redevelop the RF stage!)
While I'm doing that I'll be giving some consideration to what's going into the "monitor" stage (though I should really refer to it as a "display" stage... but then again it also monitors... hmmm... I'll figure out the correct nomenclature some other time!).
At the moment, the display side of things is just going to be 2x LM3914 driving a bar chart (may replace with LM3915, but a logarithmic response
may mess with the monitor functionality - will need to experiment!)
I was planning on having some sort of peak hold on that, but I also want it to just be 1 led for the peak - I've not really looked at how I'm going to do that yet, but I'm sure I can figure out something once I get round to that stage. Your suggestion of a bistable/manually re settable indicator would be a logical extension of that - I was originally intending on just having an adjustable hold time.
I was planning on using all-analogue parts for this project (as I always seem to be working with digital these days!), but I could probably upgrade it to a fancy OLED display with a micro-controller to do some processing - but at the moment, the aim is to make it more or less all-analogue (for increased learning potential of course!)
As for fast/slow response characteristic, I reckon a simple RC circuit with a SPDT to change the value of R might be enough? Except that will be frequency dependent - hmmm...
Lots of room for learning/experimentation =D
I'm wondering about the utility of this sort of gear, it'd be great for pinpointing noise around the house but for detecting bugs, perhaps not.
I wonder how 'easy' it'd be to bury a signal in the noise floor, raising it perhaps by a percentage of a dB across some relatively huge bandwidth, and then retrieve it, maybe this is the reason why some real time spectrum analysers are subject to export embargoes unless limi...
Hang on, there's two blokes wearing sunglasses at my door and a helicopter circling...
From what I gather, more complex bugs ("real" surveillance) have hundreds of ways to hide - I reckon it'd be pretty easy to hide something in the noise (speaking from a ham radio perspective that is, I've seen things man... those digital modes can work at incredibly low signal strengths even when there's plenty of noise!) - amateur bugging will be relatively easy to detect though xD
Either way, the rudimentary bugfinding functionality is rather serendipitous to (woah,
deja vu!) the actual goal of my project which was to find... um... "stuff" xD
Oh, and to get some analogue experience - everything I do these days seems to be digital!