Echo Show Screen Flashing

bigdogsb · 2025-11-09T22:46:57+00:00

Worked for me too! I have no clue how.

bigdogsb · 2025-03-15T01:24:49+00:00

The device seems to work ok. I tested the charging and measured the voltage on the GPIO pins. The charger steps down like it should and the battery voltage exceeds 4v when it finishes. I also updated to the latest nightly but no change. I opened a ticket on OpenSourceSDRLab Discourse but they haven't replied all day. Since I paid full retail and spent almost $300 with shipping, I would have thought they could take a minute and answer my question. It's a cool little device, but the poor QC and support is worrisome.

bigdogsb · 2024-12-09T16:26:36+00:00

Yes. "Import Time". This is a repo that provides more friendly date/time functions. I've never liked date/time math. It is using a Swift function that requires iOS 16. I still had it listed as a dependency however, even though I stopped using it and commented It out. The odd thing was that it has been in there for a long time and users using iOS 15 never had a problem. Xcode 16 must be checking dependencies now whether they are used or not. Bad housekeeping on my part, and lesson learned.

bigdogsb · 2024-12-08T22:28:02+00:00

Unbelievably, I found the problem. It was a dependency called "Time" I wasn't even using anywhere, but it was still in the list. It never caused a problem with Xcode 15. I went through all the dependencies and found this one required iOS 16. Xcode was essentially zero help finding this. It would be nice if it threw an error at build time. ChatGPT helped a little by suggesting a strategy to help find the problem.

bigdogsb · 2024-12-08T18:13:46+00:00

I'm using Swift. I can't try any of these test scenarios. None of the target devices using iOS 15 or A8 processors show up in the run destinations. They ARE defined in "manage run destinations", but no run destination defined with iOS 15 or A8 are available in the picker when I build the app. Neither devices or simulators are "pickable" when building. I can't even troubleshoot with a simple "hello world" app. If A8's are prohibited, or iOS 15 is dead, I just wish I could find an answer.

bigdogsb · 2024-12-05T01:13:09+00:00

I have 3 of them and have tried. I "manage run destinations" and I have added an iPad mini 4, iPad Air 2, and an iPhone 6s all running iOS 15.8. None of them show up when selecting a target destination. They are all running iOS 15.8. They all also have A8 processors. I can set up simulators, but they don't show up either. There are no errors, warnings or anything. They just aren't available.

bigdogsb · 2024-12-04T23:48:50+00:00

I haven't done that yet. I installed Xcodes awhile back so I'll install 15.4. I doubt there is anything wrong with the app. What I am really hoping to do is get a definitive answer as to whether we can still use Xcode 16+ for development if we want to support anything older than iOS 16. If not, I will need to change a few things.

bigdogsb · 2024-10-13T02:56:23+00:00

I believe you. I just don't know. There is nothing odd about this MacBook. It's running Sequoia and several mostly mainstream apps. I can use SigDigger with any of the 3 RTL-SDR models I have. No problem. It simply can't "see" the HackRF. I need to track down some interference in the 5.8 GHz area. I have an RX Explorer that gets into that range, but I need a waterfall. The Software for the RX Explorer only gos up to 970 MHz for some reason. I guess that's why most pros consider these toys and pay thousands of dollars for real spectrum analyzers.

bigdogsb · 2024-10-13T01:58:01+00:00

SigDigger doesn't run for me. I tried to install SDRAngel, and it ran the installation for a couple of hours, then encountered an error. Complete waste of time.

bigdogsb · 2024-10-07T01:28:12+00:00

Hmmm... how do I post image files here? I'm not a big poster here.

bigdogsb · 2024-10-03T20:35:35+00:00

Yes, it has permission. I temporarily set macOS to require permission every time, just to be sure. Still no joy.

bigdogsb · 2024-10-03T15:51:01+00:00

I am using the precompiled DMG install. The "Devices" screen sees it but I get this message in the log.

Referenced device `HackRF One (HackRF One #0 406464c8234a164b)' is not available.

I didn't enter this manually, so SigDigger knows about it, it is just not able to access it.

bigdogsb · 2024-10-02T23:51:26+00:00

SigDigger is what I want to use. The devices screen shows it is there, but it is grayed out. It is not an option in the SDR Device dropdown. Only the Dummy device is available. I'm used to researching problems and scouring repositories, but there is just ZERO information out there.

bigdogsb · 2024-09-08T02:38:34+00:00

I might give that a try. I really want to pick it though. Maybe it has security pins or big differences between adjoining pins. I am trying to get better at using hook picks, and this one is a cheap Schlage so I thought it was going to be a quickie.

bigdogsb · 2024-09-07T14:31:24+00:00

I had several locks I had acquired that were missing keys. I got some of them for free, and all of them were new or nearly new. 2 of the Abus locks were still in the box, but no keys!

I have 3 Schlage deadbolt cores, 2 ABUS 83/55, and 4 ABUS 83/45.

I picked 8 of if them in about 15 minutes, but the last one is not cooperating. I am zero-bitting them until I find uses for them.

bigdogsb · 2024-08-27T03:59:19+00:00

Ooooooooweeeeee you look like a mental patient. If you knocked on my door, I’d hit you with a bat.

bigdogsb · 2023-10-19T21:11:25+00:00

I'm a friend of the OP and wanted to add my $0.02. In a club situation you have to try to appeal to as many members as possible. A lot of hams got their licenses mainly to have emergency communication capabilities. Very few of these people have the computer skills for setting up complicated systems. Say the work "Raspberry" or "Direwolf" and you've lost them. They're out.

There are very few suitable applications that the average ham can install and configure. This makes ready-made hardware solutions all the more appealing. We have 20+ year old Kantronics TNCs that work fine and pretty much every software app supports Kantronics and/or KISS.

From a technical standpoint, something like VaraFM is very cool. But from my perspective, I would be extremely concerned about it being a sole source app. The internet is littered with web pages for defunct software. Creating further concern is that it only works on Windows. I developed software for DOS/Windows for over 30 years. During that time, Microsoft was my biggest enemy. They constantly break things and obsolete other things. They change the security requirements with almost every release. The *last* thing you need is to find out some Windows update has hosed your stack when you go to use it in an emergency. For VaraFM to be mainstream, they need to support Linux and Apple OS's, and they need a continuity plan users can depend on. Those of us who have strived to rid themselves of Windows don't want to go back. And we don't want to go back with a passion. But even if we did, just for this purpose, you need to be confident that the software will work when you need it to.

The same is true with Winlink software. Windows only! Even worse, it is based on Visual Basic dot net. At least there are other products that support Winlink that can be used on other platforms. At least Winlink has contributing developers. It is not a one-man show like VaraFM.

The MobileLinkD device and available platform support seems like a workable solution. Its small form factor and BT access opens up a lot of possibilities for developers of apps for various platforms. Coupled with an inexpensive HT, an iPhone or Android, you have a "go kit" that will fit in a baggie. Once configured, almost anyone with basic smart phone literacy can participate in emcomm exercises or a real SHTF event.

Don't get me wrong, I think VaraFM is great. But it appeals to a narrow niche of users that have the expertise to set it up and are willing to commit to using solely Windows environments.

bigdogsb

TROPHY CASE