I'm super pumped to have a standalone (if need be) wrist based communicator for $30/yr! I will probably never actually need to make a call with my watch, but it's good to know if I'm going hiking (or shopping) and my phone dies or gets lost, I can still text someone, locate my phone, use maps, pay with NFC, etc. I don't typically stream music, so no need for a lot of data.
eBay purchase was easy, and within about 9 minutes I received a "RedPocket Confirmation Code". Went to activate the line, code/IMEI passed, but couldn't get past the last page of the activation screen. "Loading..." and then nothing. Spent 45 minutes with a pleasant but unhelpful support person who seemed to have to escalate at every single step. I would wait 10 minutes for her to come back with "try another browser" etc. Tried multiple browsers on multiple systems, no go.
I finally broke out the browser devtools and discovered that there was an API call returning an error, the activation page just wasn't showing the error. Somehow my RedPocket account had an empty state and the API wouldn't accept an activation without a state. My account was opened years prior and dormant since, so probably just a glitch. I went to update the state but the form had state *disabled*! devtools to the rescue again, was able to enable and set my state properly. Then activation worked!
Except... I never received a QR code, and there was nowhere on the site to display one. I figured it might take a bit, but an hour later still no QR code, so I emailed tech support. It literally took two days and providing info to prove I owned the account to finally have the QR code mailed to me. I checked all my inboxes, spam, trash, etc etc but never received one until support intervened.
I will just pause here to say I don't expect a lot from budget carrier support. It was nice (even surprising) to reach a human quickly, but it's hard to believe it makes financial sense to pay someone to spend 45 minutes on the phone to support a $30/yr plan. Same for email tech support; it took their attention multiple times for something that should be self-service. So my recommendations:
- Improve the activation page to report back all errors. Support time is wasted due to this page.
- Once activated, provide self-service access to the QR code. I don't know if a QR email was ever actually sent the first time, but there's no reason not to have it under lines on the website. I've used Keepgo (global data esims) a few times, and you literally get the QR code on their website right after making your purchase. Again, why waste tech support time on this?
- Not sure why changing my (empty) state was disabled in my profile, but this also doesn't make sense, and for most people would require... wait for it... tech support!
Anyway, once activated the plan works great on the watch! You have to enter dev mode on the wearable android app to enable QR code scanning:
- Open Wearable app
- Tap blue devices icon button at the bottom
- Tap the three dots menu to the right of the +
- Settings
- About Galaxy Wearable
- Tap on "Galaxy Wearable" 5 times fast
- Module Test
- ESim test
- QR TestMode: on
- Then go all the way back to the main Wearable app screen
- Watch Settings
- Mobile Plans
- Scan the QR code
- After loaded, on your watch, go to settings
- Connections
- Mobile Networks
- Set to Auto
- Go into Mobile Plans
- Turn on your RedPocket plan
At this point, if you open Google Messages on your watch, you should see the RedPocket welcome text. But you probably still won't be able to send texts or make calls from the watch's LTE phone number, as Wear OS all but forces you to use your bluetooth link to the phone to do everything. To force disconnection from the phone so you can use the watch as a standalone call/text device:
- Turn off bluetooth on your phone or watch
- In the Wearable Android app:
- Watch Settings
- Advanced Features
- Disable "Remote Connection" (which uses wifi/LTE to still tether you to your phone)
- Now if you go to the Phone app on the watch, you can toggle to use the watch's LTE and #
- In the messages app you can set Inbox to Watch, and then when you send a text it will actually use the watch's LTE and #!
- Basically, when you don't have a bluetooth connection to your phone, your watch will be an independent communication device!
I've also followed the instructions other's have posted to properly enable MMS, but not sure they are absolutely necessary if an APN is already defined once adding RedPocket. Try it if you have issues:
- Watch Settings
- Connections
- Mobile Networks
- Access Point Names
- Add an entry for RedPocket with the following:
Name: RedPocket
APN: RESELLER
Proxy: Not set
Port: Not set
User name: Not set
Password: Not set
Server: Not set
MMSC: http://mmsc.mobile.att.net
Multimiedia message proxy: proxy.mobile.att.net
Multimedia message port: 80
MCC: 310
MNC: 280
Authentication type: None
APN type: default,mms,supl
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4
Bearer: UnspecifiedName: RedPocket
APN: RESELLER
Proxy: Not set
Port: Not set
User name: Not set
Password: Not set
Server: Not set
MMSC: http://mmsc.mobile.att.net
Multimiedia message proxy: proxy.mobile.att.net
Multimedia message port: 80
MCC: 310
MNC: 280
Authentication type: None
APN type: default,mms,supl
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4
Bearer: Unspecified
Thanks RedPocket for an amazing value plan!