Urgent.News

What's breaking now, across thousands of outlets.

Tech

Will an Old 3G Phone Work as a Security Camera on Mobile Data? What the E, H and 4G Icons Mean for Offline and Low-Data Setups

Many old Android phones in drawers today are 3G phones. Some are 4G phones that have been set to 3G or 2G years ago and never changed back. If you want to use one as a shop or home camera with a SIM card for mobile data, the network letters at the top of the screen tell you most of what you need to know. This guide is written for budget and older phones, prepaid data, and places where the mobile…

Many old Android phones in drawers today are 3G or even 2G phones, even if they show newer network icons. The letter next to the signal bars indicates the type of mobile data connection the phone can use. Here's what the icons mean:

G: GPRS, which is very slow 2G data, and cannot handle live video streaming.

E: EDGE, still slower than G but not fast enough for live video.

3G/UHS/ HSPA+: These are the 3G networks, which may work for low-quality streams if the network is still available.

4G/LTE: This is the best choice for live streaming over mobile data, but it's not always available everywhere.

2G and 3G-only phones can still be good offline security cameras. They can record to the phone's own storage without needing any network connection at all. Watching the live view remotely only requires a Wi-Fi connection, not mobile data.

The short answer is: A phone limited to 2G data (G or E icon) cannot carry a live YouTube stream, while a 3G-enabled phone (3G, H, or H+) may work if 3G is still available in your area. However, a 2G or 3G-only phone can still function well as a security camera, recording to its own storage without needing any network connection.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

RAG Context Budget: Pack Evidence Without Burying the Answer

When a RAG answer is wrong, the reflex is often to raise top_k . More retrieved chunks feels safer. In production, it can do the opposite: the one useful passage gets surrounded by repeated, stale, or…

  • Context budget is a context budget, not a retrieval strategy
  • Retrieval and generation serve different purposes, not the same topk values
  • Effective context packer has four gates: retrieval, filtering, reranking, and packing

17,651 subdomains, one server: what checking "is this job still open?" taught us

I run Job Opportunities API (JOA), a jobs API that only reads employers' own career sites and applicant-tracking systems. The hard part is not finding jobs. It is knowing when a job is gone.

  • JOA's checker treated each subdomain as separate host, causing 17,651 requests per second
  • JOA now groups hosts into lanes based on server that answers, not hostname
  • JOA distinguishes between 410 (gone) and 429 (rate limit exceeded) status responses

Your Gumroad license check probably lets refunded buyers in (and how to fix it)

If you sell software on Gumroad and gate it with license keys, there's a good chance your check looks like this: const res = await fetch ( " https://api.gumroad.com/v2/licenses/verify " , { method : "…

  • Gumroad license check may allow refunded buyers to use software
  • Verify endpoint returns true status even after refunds or cancellations

More from Tuesday 20 October →