OffLocSetu
OffLocSetu (Offline Location Setu)
Project Idea: Offline (no internet & gps) Location System
OfflocSetu is a location provider that works without internet and without GPS. It estimates approximate location using cellular network signals and is intended for safety and awareness use cases such as child and elderly care.
Introduction – Where This Idea Came From
This idea didn’t come from a tutorial, a YouTube video, or copying an existing app.
It came very naturally.
One day, while casually thinking about how location even when internet or GPS is off, I started wondering:
“A phone is still connected to a mobile tower even when everything else is disabled… so can that connection itself be useful?”
That curiosity led me to learn about something called TelephonyManager in Android - an API that gives access to cellular network information like connected cell tower, signal strength, and network type.
That’s when this idea clicked in my mind.
At present, I am not fully capable of implementing this system end-to-end, especially because it involves Android system APIs, backend services, SMS gateways, and careful system design. So instead of rushing into half-baked code, I decided to document the idea properly, explain it deeply, and share the full concept clearly.
Problem Statement – A Real-Life Observation
Most location-sharing apps today depend heavily on:
- GPS being ON
- Internet (mobile data or Wi-Fi)
- High battery usage
- Continuous background permissions
But in real life, many situations don’t meet these conditions:
- Children may turn off mobile data
- Elderly people may not understand GPS or settings
- Phones may be indoors where GPS is unreliable
- Rural or low-network areas may have unstable internet
- Battery saving modes may restrict background apps
Despite all this, one thing almost always remains active:
📡 The phone’s connection to a cellular tower.
This project idea explores whether that single fact can be used responsibly and safely.
Core Idea – What This Project Is About
The idea is to build a guardian–dependent location estimation system that:
- Does not depend on GPS
- Can work with very low or no internet
- Uses cell tower information for approximate location
- Shares location only with explicitly authorized guardians
- Is transparent, consent-based, and safety-focused
The goal is not exact tracking, but rough awareness.
For example:
“The child is near XYZ area, last updated 5 minutes ago.”
That alone can be extremely useful in many situations.
Who This System Is For
This concept is intended for:
- Children (basic safety awareness)
- Elderly people (especially with health risks)
- Guardians / parents / caretakers
- Low-connectivity or rural environments
It is not intended for:
- Secret tracking
- Surveillance without consent
- Spy or monitoring misuse
High-Level System Overview
The system consists of three main parts:
- Android App (installed on child / elderly phone)
- Backend Server (receives and processes data)
- Web Portal (used by guardians or caretaker)
Each part has a very clear responsibility.
How the Android App Works (Conceptually)
What the app can read
Using Android’s TelephonyManager API, the app can access:
- Connected cell tower ID (CID / NCI)
- Network operator
- Signal strength
- Network type (2G / 4G / 5G)
- Timestamp
Important point:
This data can be read even when mobile data and GPS are turned OFF.
How the app sends data (Key Design Choice: SMS)
Since internet may not always be available, the idea is to use SMS as the transport mechanism.
Why SMS?
- Works without mobile data
- Very reliable
- Supported everywhere
- Already used in banking, alerts, emergency systems
Example of data sent via SMS (conceptual):
UID:CHILD_01 | CID:345678 | TAC:1123 | NET:JIO | SIG:-92 | TIME:1912
This message is sent:
- At fixed intervals (e.g. every 10 minutes)
- Or when significant movement is detected
- Or in emergency mode (higher frequency)
Backend Server – Making Sense of Raw Data
The backend server receives incoming SMS data (via SMS gateway or receiver).
Its responsibilities:
- Parse incoming messages
- Authenticate the device/user
- Map cell tower ID → approximate coordinates
- Store last known location
- Calculate confidence radius
- Expose safe APIs to the web portal
The backend does not pretend to know exact location. It only estimates based on known tower data.
Guardian Web Portal - Recive Data
The web portal is intentionally simple.
A guardian can:
- Log in securely
- Add or select a dependent by username
-
View:
- Last estimated location
- Approximate area name
- Time since last update
- Confidence level (low / medium)
Example display:
“Last seen near abc,xyz area (±1 km), 10 minutes ago”
No live dots pretending GPS accuracy. Only honest, readable information.
Real-Life Usage Scenarios
Scenario 1: Child Returning From School
- Phone has no data
- GPS is off
- App sends SMS every 10 minutes
- Parent checks web portal
- Sees approximate area updates
Scenario 2: Elderly Person Living Alone or Go to Walk
- Internet disabled accidentally
- Guardian still receives periodic location updates
- Can detect unusual movement or inactivity
Scenario 3: Rural / Low Network Areas
- Internet unreliable
- SMS still works
- System remains functional
Accuracy & Limitations
This system:
- ✓ Works indoors
- ✓ Works without GPS
-
✓ Works with no internet
- ✘ Does not give exact location or coordinates
- ✘ Cannot update in real time without any connectivity (for connectivity we use SMS)
Expected accuracy:
- Locality / area level
- Radius may range from hundreds of meters (according to tower coverage)
The UI must clearly say:
“Estimated location, not exact.”
Why This Project Matters (Even as an Idea)
This project is not about building yet another location app.
It is about:
- Understanding how mobile networks actually work
- Designing fallback systems
- Thinking beyond GPS and internet
- Building for real-world constraints
It represents systems thinking, not just coding.
Why This Idea Is Different From Normal Location Apps
Most location-sharing apps try to answer only one question:
“Where is the person exactly right now?”
This idea asks a different and more realistic question:
“How can we still have some awareness of location when ideal conditions do not exist?”
Instead of assuming:
- GPS is always on
- Internet is always available
- Battery is never a problem
This idea accepts reality:
- Phones lose internet
- GPS fails indoors
- Users turn things off
- Networks are unstable
So the system is designed to degrade gracefully, not break completely.
That mindset is the core difference.
What This System Tries to Achieve (And What It Does Not)
What it tries to achieve
- Give guardians basic location awareness
- Work in low-connectivity situations
- Reduce dependency on GPS
- Be honest about accuracy
- Be transparent to the user
What it does NOT try to do
- Track exact movement on a map
- Replace GPS-based navigation
- Act as surveillance software
This project is about safety
Why Cell Tower–Based Estimation Makes Sense
A mobile phone can exist in three states:
State 1. GPS ON + Internet ON
State 2. GPS OFF + Internet ON
State 3. GPS OFF + Internet OFF
Most apps only work well in State 1.
This idea focuses on State 3, because:
- That is where most apps completely fail
- But the phone is still connected to a cellular network
Cell tower connection is:
- Mandatory for basic phone operation
- Always present when the phone has signal
- Independent of user settings like GPS or data
Using this signal is not clever trickery - it is using what already exists.
Why SMS Is Chosen Instead of Internet
SMS is often seen as outdated, but in system design it has strong advantages:
- Works without mobile data
- Works on very weak networks
- Consumes very little power
- Is supported everywhere
- Is predictable and reliable
In emergency systems, banking alerts, and rural communication, SMS is still trusted more than internet.
That is why this idea uses SMS as a fallback communication channel, not as a modern replacement.
How Guardians Benefit From This System
This system is not designed to overload guardians with data.
Instead, it gives calm, useful information, such as:
- “Last seen near this area (using area tower)”
- “Updated a few minutes ago”
This helps guardians:
- Reduce anxiety
- Notice unusual patterns
- Act early if something feels wrong
It is awareness, not micromanagement.
Why Approximate Location Is Often Enough
In many real-life situations, exact location is not required.
Examples:
- Knowing a child is still near school area
- Knowing an elderly person has not left their locality
- Knowing a device is still active and connected
Exact coordinates are less important than context.
This idea focuses on context.
Why This README Exists Before the Code ?
Many projects start with code and end with confusion.
This project intentionally starts with:
- Clear thinking
- Honest limitations
- Documented intent
Writing this README first helps ensure that:
- The problem is well understood
- The solution is realistic
- The system does not drift into misuse
Code can always be written later. Clarity must come first.
Current Status of This Project
Concept / Design Phase
At present:
- This is a documented idea
- No production-ready code exists
- Implementation requires deeper Android + backend expertise
This README exists to:
- Capture the idea clearly
- Share the thought process what i think
- Serve as a foundation for future work
Final Thoughts
Sometimes, a strong idea deserves time.
Instead of rushing into implementation, this project pauses to ask:
“Does this make sense in the real world?”
This README is my attempt to answer that honestly.
If one day this idea becomes a working prototype, it will be built on this foundation - carefully, responsibly, and transparently.
FAQ - Frequently Ask Questions
Frequently asked questions and clarifications are documented in the FAQ:
https://webdevpraveen.github.io/OffLocSetu/FAQ.html
License
This project is currently shared as a concept and documentation only.
| All rights reserved | Praveen Kumar Singh. |
Reuse, modification, implementation, or commercial use of this idea requires prior permission from the author.