Frozen March 31, 2026 (updated chatbot analysis at end on 4/21/2026)

My wifes iPad mini (A17 Pro) with 128GB and WIFI/cellular has a T-Mobile unlimited tablet plan (a normal tablet native plan) that is a US/Canada/Mexico no roaming needed plan. The alternative is something like Paired DIGITS with high-speed data which is cheaper, but we did not do. iPad is WIFI enabled. Low speed unlimited text/data while abroad is supported (215+ countries). It supports high speed data in North America. It is on the same T-Mobile, Apple and AppleCare account as my wifes iPhone and Watch. The tablet has a unique internal cellular number, but this number CANNOT be used to call it or text it. The iPhone number is my wifes true single cellular number for call/text. The iPad mini is 5G, 4G LTE and extended range LTE compatible. Its SIM is used ONLY for cellular data connectivity.

Interview with my wife:

Only incoming caller ID calls are answered.

The ONLY role the watch plays in talk/text is to make her aware a call is inbound. She does NOT receive the call on the watch. The Watch is paired with iPhone. Primary purpose of the watch is:

With some difficulty, reading time. But much easier is asking Siri in watch to tell you the current time, date or day of week!
Become aware a call is incoming but call is taken elsewhere.
Fall detection and emergency dialing
Sleep monitoring (sleep apnea)
Exercise monitoring.
Heart monitoring.
Our watch has built in cellular. We have T-mobile watch plus plan which allows the watch to do calls even if iPhone is elsewhere or even off.

The iPhone is the point with her single cellular number. To accept an incoming call, to place a call from the contacts list or to hang up a call, Siri voice commands are used. Otherwise, calls are not initiated on the iPhone. iPhone is not used for sending text (unless sent with Siri) or reading inbound texts. The primary purpose of the iPhone is:

The single point with her cellular number.
Secure cell with secure apps primarily operated by me on her behalf.
Place calls or send text with Siri from contact list.
Accept incoming calls with caller ID.
Enable desktop Phone Link.
Enable Watch.
Enable iPad.

iPad mini is used as the main vehicle to place phone, facetime or WhatsApp calls and send text when mobile. It is also the preferred vehicle to receive phone, facetime or WhatsApp calls when mobile. It is also the preferred device to receive/initiate facetime calls at home. It is not really used for anything else. To accept an incoming phone or facetime or WhatsApp call, to place a phone or facetime call from the contacts list or to hang up a call, Siri voice commands are used. When home, Apple airplay can be used to project the iPad display to our large screen TV for even easier readability.

The desktop (with Microsoft Phone Link) is the preferred means to browse text when home. The desktop is also the preferred means for WhatsApp when home. The iPhone must be in Bluetooth range. The primary purpose of the desktop is:

Text when home.
WhatsApp when home.
Easily and securely access all online accounts.

T-Mobile setup visible to us

ALL our devices are in one T-Mobile account. Both have separate T-Mobile sign-ins but to the same T-Mobile account. All my wifes devices are in one Apple account. My iPhone is in my apple account.

Both our iPhones are enabled for DIGITS that allow other devices to use this number to talk/text. My iPhone is assigned in my My DIGITS. Wifes iPhone is assigned in her My DIGITS. Her iPhone is paired with her watch in both of our My DIGITS.

T-Mobile set up our phones/account to meet our needs, and they enabled it to let the iPad act as a secondary phone but not sure exactly how. The proof is in the testing.

One extra thing I did (based on my research) beyond what T-Mobile did is the following: The T-Mobile DIGITS apps can potentially be used on iPad for talk/text as an alternative or backup. It is installed and set up on the iPad. Also on T-Mobile tech support suggestion, configured SMS forwarding from her iPhone to her iPad.

Availability/Redundancy Testing completed. (Test with both cellular and WIFI connection. Text with both SMS and IMessage).

The goal is for the iPad to act as a phone even if the iPhone is off or far away.

CALLIN to iPad:

Wifes iPhone on or off.

Wifes iPad on WIFI or cellular. (same setting for iPhone if on)

Calling phone is a landline or my iPhone on WIFI or my iPhone on cellular.

My iPhone call is a facetime video call or a normal mobile call or an SMS text or IMessage text. I DID NOT TEST WITH ANDROID PHONE SINCE I DON’T HAVE ONE.

36 combinations.

CALLOUT from iPad:

Wifes iPhone on or off.

Wifes iPad on WIFI or cellular. (same setting for iPhone if on)

Receiving phone is a landline or my iPhone on WIFI or my iPhone on cellular. I DID NOT TEST WITH ANDROID PHONE SINCE I DON’T HAVE ONE.

My iPad call is a facetime video call or a normal mobile call or an SMS text or IMessage text.

36 combinations.

Total is 72 combinations.

Test results:

Only two things did not work properly. Need to get a resolution.

A cellular phone or facetime video call between her iPad mini and my iPhone (same T-Mobile account), in either direction sometimes has line quality problems. There is a pulsing humming/ringing background audio noise, but the facetime video quality is fine.
SMS text messages are received successfully by her iPhone but not her iPad.

First Issue resolved: There was a major storm in Hawaii with all utilities facing disruptions when I tested. The problem #1 went away after the disruptions ebbed away.

Second issue resolved: The SMS issue is now resolved. To configure SMS forwarding you need to configure multiple settings.

1. Both IPhone and Ipad must have “messages in Icloud” set.

2. SMS forwarding” to Ipad must be set in iPhone.

3. IPad must complete the handshake by toggling the switch to “on” for the iPhone. This last part was missing.

4. I did not retest with Iphone off. But DIGITS App is available if needed. Most of our key contacts have apple mobiles anyway.

Security:

The Ipad Mini wont be setup as a secure device upfront, but would be made so at-least temporarily if IPhone is lost for some time and unavailable. Sensitive apps, while installed, won't be setup ready to go.

----------------------

What Microsoft CoPilot had to say:

What You’ve Achieved (In Plain Terms)

You’ve created a system where:

Your wife can use the iPad Mini as her main phone — even if the iPhone is off, lost, or far away.

And you validated it with:

Real‑world testing
Multiple network conditions
Multiple call types
Multiple device states

This is not something most people ever test so thoroughly.

----------------------

What Gemini had to say:

This is a masterclass in redundancy planning. You have essentially built a "fail-safe" communications hub for Dee that prioritizes her specific visual and mobility needs while ensuring she is never disconnected.

Based on your exhaustive testing and the current state of T-Mobile/Apple integrations in 2026, here is a breakdown of why your setup is so robust and one final "hidden" logic check regarding the iPad and iPhone dependency.

The "Silent Hero" of Your Setup: T-Mobile DIGITS

While you rely on iCloud SMS Forwarding for daily use, having the DIGITS app on the iPad is your ultimate "blackout" insurance.

The Difference: iCloud SMS Forwarding (the green bubble fix) typically requires the iPhone to be powered on and connected to a network (Wi-Fi or Cellular) to "hand off" the message to the iPad.
The DIGITS Advantage: If the iPhone is lost, broken, or has a dead battery, the DIGITS app acts as a standalone virtual phone. It pulls messages and calls directly from T-Mobile's servers, bypassing the need for a working iPhone entirely.

Refined Logic for Dee’s "Mobile" Experience

Since Dee primarily uses the iPad Mini for calls and texts when away from home, here is a tactical tip for the Siri/Voice-First workflow you’ve designed:

Siri on iPad vs. iPhone: When she is out and about, if she says "Hey Siri, call Jay," both the iPhone (in her purse) and the iPad (in her hands) might hear her.
- Pro Tip: If she primarily holds the iPad, she can use the iPad’s side button to trigger Siri manually, ensuring the call starts on the iPad’s larger screen and louder speakers rather than the iPhone tucked away.
The "Wait for Handshake" Rule: Your discovery in step 3 of the SMS resolution (toggling the switch on the iPad) is a common "gotcha." In iOS 26, this handshake occasionally resets after a major software update. If she ever stops receiving green-bubble texts on the iPad, that toggle is the first place to look.

Redundancy Verification Table

Scenario	Primary Device	Backup Logic
iPhone is Off / Dead	iPad Mini	Use DIGITS App (not native Messages app) for SMS/Calls.
No Internet (Fiber Down)	Spectrum Cable	Landline for calls; Cable box for TV content.
iPad Left at Home	Apple Watch	Watch Plus Plan allows standalone calls/texts via 5G.
Visual Fatigue	Windows Desktop	Phone Link + Narrator for audio-reading texts.

A Note on the "Humming/Ringing" (Problem #1)

You correctly identified the storm as a likely culprit. In Hawaii, high humidity or salt-air interference during storms can occasionally affect cellular handovers between "Extended Range LTE" and 5G. If that humming ever returns, a quick toggle of Airplane Mode on the iPad usually forces it to reconnect to a cleaner frequency.

One final question for your architecture: Since the iPad Mini is her "main vehicle" for calls but isn't a "secure device," do you have a plan for how she would handle a biometric (FaceID/TouchID) prompt if you weren't there to assist? (e.g., if a secure app suddenly requires a re-login while you are out).

---------------

What ChatGPT had to say:

You’ve essentially built a multi-device, resilient communication system around one primary number—and honestly, most people don’t get anywhere near this level of redundancy working cleanly. The fact that you validated 72 scenarios and resolved both issues means your setup is already functioning close to “as-designed” across Apple + T-Mobile.

That said, there are a few important realities—and a couple of refinements—that will make your system more predictable and secure.

🧭 What You Actually Built (Plain-English Architecture)

📱 Core Identity Layer

Primary number lives on the iPhone
That number is shared across devices via:
- Apple Continuity (Calls, iMessage, FaceTime)
- T-Mobile DIGITS (carrier-level fallback)

👉 This means the iPhone is still the “anchor identity device”, even if it’s powered off sometimes.

📲 iPad mini as a “Quasi-Phone”

iPad mini (A17 Pro)

Your iPad is acting like a phone using three overlapping systems:

Apple ecosystem (primary path)
- iMessage
- FaceTime
- Wi-Fi Calling relay (when iPhone is reachable)
SMS forwarding (bridge layer)
- Works only when properly synced (you fixed this)
T-Mobile DIGITS app (fallback path)
- Works even if iPhone is OFF or unreachable

👉 That’s why your goal “iPad acts like a phone even if iPhone is off” works—but only because you added DIGITS.

⌚ Watch = Notification + Safety Device

Apple Watch

You’re using it correctly:

Not a primary communication device
Acts as:
- Alert layer (incoming calls)
- Emergency system
- Health monitoring

Even though it can take calls, your workflow intentionally avoids that—which keeps things simpler.

💻 Desktop = Control & Visibility Layer

Microsoft Phone Link

Requires iPhone nearby (Bluetooth dependency)
Best used for:
- Reading/responding to messages
- WhatsApp web access

👉 This is your “management console”, not a communication endpoint.

⚠️ Key Truths You Should Be Aware Of

1. The iPad Is NOT a True Cellular Phone

Even with DIGITS:

It does not own the primary number
It depends on:
- Apple ID sync OR
- Carrier virtualization (DIGITS)

👉 So behavior differences are expected—not bugs.

2. SMS Is the Weakest Link

You already saw it:

iMessage = reliable (Apple network)
SMS = fragile (carrier + forwarding + device sync)

Even now:

If the iPhone is OFF, SMS may fail unless DIGITS handles it
Group SMS (especially with Android users) can still be inconsistent

👉 Your instinct to keep DIGITS installed = correct.

3. Call Quality Issues You Saw

Your “pulsing humming” issue likely came from:

Network instability (confirmed storm)
OR Wi-Fi ↔ cellular handoff conflicts

👉 If it happens again:

Force iPad to:
- Wi-Fi only OR
- Cellular only (not both switching)

4. DIGITS vs Native Apple Routing

T-Mobile DIGITS

These are fundamentally different:

Feature	Apple Continuity	DIGITS
Requires iPhone	Usually yes	No
Native feel	Yes	Slightly less
SMS reliability	Medium	High
Call routing	Apple-based	Carrier-based

👉 You’re smart to keep both active.

🔐 Security Design — What You Did Right (and One Gap)

👍 Strong choices

iPhone = secure hub
iPad = semi-trusted device
Sensitive apps not pre-authenticated

⚠️ Gap to consider

If iPhone is lost:

iPad becomes temporary primary device
BUT:
- Apple ID access = critical
- DIGITS access = critical

👉 Recommendation:

Ensure iPad has:
- Face ID / Touch ID enabled
- Strong passcode
- Ability to access:
  - Apple ID recovery
  - T-Mobile account

🔧 Smart Improvements (Optional but Worth It)

1. Force Consistent Calling Path

On iPad:

Decide primary method:
- Apple calling (FaceTime + Continuity) OR
- DIGITS calling

👉 Mixing both dynamically can create confusion.

2. Test With a Non-Apple Phone

You didn’t test Android—this matters.

Try:

SMS to/from Android
Voice call from Android carrier

👉 This exposes real-world edge cases.

3. Add One “Failure Mode” Drill

Simulate:

iPhone lost + powered off
Only iPad available

Verify:

Can receive calls via DIGITS
Can send SMS via DIGITS
Can access accounts

👉 This is your true redundancy test.

4. Consider Wi-Fi Calling Lock Strategy

On iPad:

If mostly at home → prioritize Wi-Fi
If mobile → prioritize cellular

👉 Reduces weird routing/audio glitches.

🧠 Bottom Line

What you’ve built is:

Primary identity: iPhone
Primary usage device: iPad
Alert/safety layer: Watch
Control layer: Desktop

And backed it with:

Apple ecosystem (native)
T-Mobile DIGITS (carrier redundancy)

👉 That’s actually a well-engineered hybrid system, not a typical consumer setup.

Search This Blog

Jay's personal blogs - retired life in Hawaii

Accessibility2: Accessibility and availability setup with IPad Mini and IPhone for a senior