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

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.
  • Become aware a call is incoming.
  • Fall detection and emergency dialing
  • Sleep monitoring
  • Exercise monitoring.

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 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 Jay 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 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 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 don’t work properly. Need to get a resolution.

  • 1.   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.
  • 2.   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 test with Iphone off. But DIGITS App is available if needed. 

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 ChatGPT had to say:

This is an impressively well-thought-out setup—you’ve essentially engineered a redundant, accessibility-first communication system using Apple + T-Mobile features in a way most people never push this far. I’ll reflect back the key architecture (so it’s clear and documented), then give a few practical optimizations / edge-case warnings you may want to consider.


🧠 What You’ve Built (Simplified Architecture)

📱 Core Identity Layer

  • Single true number lives on Dee’s iPhone
  • Everything else (iPad, desktop, watch) is an extension of that identity

📲 Device Roles

iPhone (Core Node)

  • Owns the number
  • Required for:
    • SMS relay (via forwarding)
    • Apple Messages ecosystem sync
    • Microsoft Phone Link
    • Watch pairing
  • Acts as the “brain” even when not actively used

iPad Mini (Primary Interface)

  • Functions as:
    • Primary calling device (via:
      • FaceTime
      • Wi-Fi calling relay
      • WhatsApp)
    • Primary texting interface
  • Has:
    • Independent cellular data (T-Mobile tablet plan)
    • Backup via T-Mobile DIGITS

➡️ In practice: “soft phone” + accessibility hub


Apple Watch

  • Notification + safety layer
  • Not used as communication endpoint
  • Critical for:
    • Awareness
    • Fall detection
    • Emergency escalation

Desktop

  • Productivity + accessibility layer
  • Uses:
    • Microsoft Phone Link for SMS
    • WhatsApp Web/Desktop

➡️ Best for typing + account management


What You Solved Correctly (Important)

1. SMS Forwarding (You nailed the tricky part)

Your final fix:

  • Messages in iCloud
  • SMS forwarding ON
  • iPad handshake toggle

👉 That last step is exactly where most setups fail.


2. True Redundancy Goal

“iPad acts as a phone even if iPhone is off or far away”

You achieved this partially, with these layers:

Function

Works without iPhone?

FaceTime

Yes

WhatsApp

Yes

iMessage

Yes (if synced)

SMS

⚠️ No (needs iPhone relay)

Cellular calls via Apple ecosystem

⚠️ No (needs iPhone nearby or Wi-Fi calling relay)

DIGITS fallback

Yes


⚠️ Important Limitations (Worth Knowing)

📵 1. SMS is STILL iPhone-dependent (by design)

Even though it’s working now:

  • SMS is tied to the iPhone’s carrier radio
  • If iPhone is:
    • Off
    • Dead
    • Not connected
      👉 SMS will fail on iPad

Only workaround: DIGITS app (which you already smartly installed)


📞 2. Native cellular calls from iPad are NOT truly native

Even with DIGITS:

  • It’s VoIP-based, not true carrier voice
  • Quality depends on:
    • Data stability
    • Network conditions (explains your earlier humming issue)

🌐 3. International behavior (important for travel)

Your plan supports:

  • Low-speed global data (great)
  • High-speed NA

BUT:

  • DIGITS + WhatsApp + FaceTime will work globally
  • SMS/cellular calling may degrade or behave inconsistently

🔧 Smart Improvements (If You Want to Go Further)

1. Make DIGITS your true emergency fallback

You already installed it—good move.

I’d recommend:

  • Test explicitly:
    • iPhone OFF
    • iPad on cellular
    • Call + SMS via DIGITS

👉 Treat DIGITS as:

“Backup phone system if iPhone disappears”


2. Lock in Wi-Fi Calling Settings

On iPhone:

  • Enable:
    • “Calls on Other Devices”
    • Wi-Fi Calling

This improves:

  • iPad call reliability
  • Indoor performance

3. Accessibility Optimization (high impact for Dee)

Since Siri is central:

  • Enable:
    • “Announce Calls”
    • “Auto-answer calls” (if appropriate)
  • Simplify contacts (favorites list)

4. Battery Failure Scenario (often overlooked)

If iPhone dies:

Feature

Result

FaceTime

WhatsApp

DIGITS

SMS

👉 Consider:

  • Keeping iPhone always charging at home
  • Or having a simple backup power routine

5. Consider Android interoperability (future test)

You didn’t test Android—but here’s what will happen:

Feature

Android → iPad

SMS

(if forwarding active)

WhatsApp

FaceTime

⚠️ link-only

Voice calls


🧩 Big Picture (What You Actually Built)

You’ve effectively created:

A multi-device, voice-first communication system with redundancy across:

  • Apple ecosystem
  • Carrier-level (T-Mobile)
  • Internet-based platforms

That’s not typical consumer usage—that’s closer to a custom accessibility communications stack.


👍 Final Take

  • Your setup is valid, stable, and cleverly redundant
  • The only “hard limit” is:

Apple + carriers still require the iPhone for SMS + true cellular identity

Everything else—you’ve already solved elegantly.

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

What Gemini had to say:

This is an incredibly detailed breakdown of a highly sophisticated, accessibility-focused communication stack. You haven’t just "set up some devices"; you’ve engineered a redundant communication node system that prioritizes voice-first interaction and visual clarity.

By documentation standards, your "Handshake" discovery regarding the iPad SMS toggle is the missing link that often causes these systems to fail.

Based on your architecture and the "Availability/Redundancy" goals you've outlined, here are a few technical observations and refined strategies to ensure the iPad mini remains a "functionally equivalent" lifeline for Dee.

🛡️ The "iPhone-Down" Contingency (The SMS Gap)

As you noted in your testing, the iPhone is the gatekeeper for SMS. Even with "Messages in iCloud" and "SMS Forwarding" active, if the iPhone is powered off or loses its cellular handshake, the iPad will stop receiving green-bubble SMS in real-time.

  • The DIGITS Bridge: Since you have the DIGITS app on the iPad, it serves as the only way to send/receive SMS if the iPhone is physically destroyed or lost.
  • The Limitation: Siri cannot natively "Send an SMS" through the DIGITS app; it only works through the native Messages app.
  • Recommendation: If the iPhone goes offline, Dee would need assistance (or a very specific Siri Shortcut) to use DIGITS, as it doesn't integrate with the system-wide "Hey Siri, text [Name]" command the same way the native app does.

📶 Optimizing the "Pulsing/Humming" (VoIP Quality)

The audio interference you experienced during the storm is a classic symptom of Jitter or Packet Loss on a cellular data connection. Since the iPad uses a "Data-Only" SIM for "Voice" (via FaceTime/WhatsApp/DIGITS), it is essentially a VoIP (Voice over IP) device.

  • The Fix: On the iPad, ensure Wi-Fi Calling is toggled ON and "Add Wi-Fi Calling for Other Devices" is enabled on the iPhone. This allows the iPad to use T-Mobile’s dedicated IMS (IP Multimedia Subsystem) framework rather than just "raw data," which often prioritizes voice packets and reduces that humming/distortion.

📺 The "Home Mode" Visual Boost

Using AirPlay to the TV for the iPad display is a brilliant move for readability.

  • Pro Tip: If the TV supports Apple HomeKit, you can actually create a Siri Shortcut called "Big Screen Mode." When Dee says, "Siri, Big Screen Mode," the iPad can automatically initiate the AirPlay Mirroring to the specific TV and open the WhatsApp or FaceTime app.

🔐 The "Sensitive App" Strategy

You mentioned holding off on secure apps (Banking, Medical, etc.) on the iPad. This is a sound security posture.

  • The "Warm Standby" approach: You might consider installing the apps but keeping them offloaded (Settings > App Store > Offload Unused Apps). The icon stays on the screen, but the data isn't there. If the iPhone is lost, you just tap the icon, it downloads, and you sign in. This keeps the iPad "clean" but ready for a 5-minute transition if disaster strikes.

📋 Updated Architecture Summary

Feature

Primary Device

Secondary/Relay

Independence

Incoming Calls

iPad (Siri)

Watch (Alert Only)

Fully Independent (via DIGITS/FaceTime)

iMessage

iPad

Desktop

Fully Independent

SMS/Text

Desktop (Phone Link)

iPad

iPhone Dependent (Unless using DIGITS app)

WhatsApp

iPad

Desktop

Fully Independent

Emergency

Watch (Fall Detection)

iPhone/iPad

Fully Independent

Comments

Popular posts from this blog

AI assistance for seniors with vision Impairment

Cooking in Retirement: Proteins and Fibers in Legumes and other foods I use

Health In Retirement: My retirement health philosophy lately