In recent days, T-Mobile customers stumbled upon an unannounced setting in the T-Mobile T-Life app that raised some eyebrows and has created a bit of a freakout. A new setting called “Screen recording tool” was found on select devices and was enabled with a description that doesn’t... #TMobile
It’s also android phones. All of the shots in the article are of android phones.
This is likely just recording sessions of the carrier’s app, not everything on your phone. Session recording for CS and UX is pretty common these days. It can be impossible to identify a problem unless you actually see what is happening in the app.
That said, you have to ask for consent for this shit. A lot of companies don’t alert customers when they release a new tool that requires privacy consent.
To help us give customers who use T-Life a smoother experience, we are rolling out a new tool in the app that will help us quickly troubleshoot reported or detected issues. This tool records activities within the app only and does not see or access any personal information. If a customer’s T-Life app currently supports the new functionality, it can be turned off in the settings under preferences.
So yes, it can only see itself, i.e. within the T-Mobile app. It’s still dumb.
I’m not well versed enough in Android app development to answer whether or not one userspace app can even access the screen contents of another app without root or special permissions, but it wouldn’t surprise me if there are several roadblocks in that path on the part of the OS for obvious reasons.
I’m not well versed enough in Android app development to answer whether or not one userspace app can even access the screen contents of another app without root or special permissions
This requires special permissions and explicit user approval every time an app starts screen recording, plus it shows a red notification whenever screen recording is active.
I think you could get by with a one-time user approval as a device administration or assistive app permission, which you’d need to manually grant in Settings. Unlikely anyone would do that by accident.
That might be different for system-level apps. I haven’t bought a carrier-branded phone in 10+ years so I’m not sure what that’s like these days.
It’s not possible on Android, which is incredibly disappointing because I play a card game exclusively on mobile, and would love to use a collection manager and stat tracking app. These exist for PC and Mac, but not for mobile because of the very hard no-record-other-apps wall.
That would be a pretty big security hole in iOS if that was allowed, but it isn’t. Notification and other UI elements are rendered on top of the underlying app, which does not have access to or cannot see the full screen’s canvas. We can see practical implementations of this “snapshot” test feature in code:
Not the tools I’ve used. A lot of them aren’t even actually recording video. They’re recording the user interactions in-app, then playing those back on a cached version of the experience that is hosted with the session recording company.
It’s also android phones. All of the shots in the article are of android phones.
This is likely just recording sessions of the carrier’s app, not everything on your phone. Session recording for CS and UX is pretty common these days. It can be impossible to identify a problem unless you actually see what is happening in the app.
That said, you have to ask for consent for this shit. A lot of companies don’t alert customers when they release a new tool that requires privacy consent.
This is so. At the bottom of the article it says:
So yes, it can only see itself, i.e. within the T-Mobile app. It’s still dumb.
I’m not well versed enough in Android app development to answer whether or not one userspace app can even access the screen contents of another app without root or special permissions, but it wouldn’t surprise me if there are several roadblocks in that path on the part of the OS for obvious reasons.
This requires special permissions and explicit user approval every time an app starts screen recording, plus it shows a red notification whenever screen recording is active.
I think you could get by with a one-time user approval as a device administration or assistive app permission, which you’d need to manually grant in Settings. Unlikely anyone would do that by accident.
That might be different for system-level apps. I haven’t bought a carrier-branded phone in 10+ years so I’m not sure what that’s like these days.
Last I checked, you can have a system app as an accessability provider and be enabled by default
It’s not possible on Android, which is incredibly disappointing because I play a card game exclusively on mobile, and would love to use a collection manager and stat tracking app. These exist for PC and Mac, but not for mobile because of the very hard no-record-other-apps wall.
I wonder if this would include on-screen notifications.
That would be a pretty big security hole in iOS if that was allowed, but it isn’t. Notification and other UI elements are rendered on top of the underlying app, which does not have access to or cannot see the full screen’s canvas. We can see practical implementations of this “snapshot” test feature in code:
https://github.com/uber/ios-snapshot-test-case
Not the tools I’ve used. A lot of them aren’t even actually recording video. They’re recording the user interactions in-app, then playing those back on a cached version of the experience that is hosted with the session recording company.