The coupon is not working. Shame. $99 is steep to test out a service. I know it comes with more features than my US Mobile, but $30 would have got me to test it.
Hey everyone,
I’m looking into switching over to Cape as a Bring Your Own Device (BYOD) user with my Google Pixel. I’m trying to figure out if I can just leave my phone exactly as it is.
I know Cape actively supports and partners with GrapheneOS, but frankly, at the moment I just really don't want to go through the technical trouble or hassle of trying to install a whole new operating system on my phone. I want to keep using standard Stock Android.
I have a couple of questions for anyone currently running Cape on a Pixel:
Identifier (IMSI) Rotation on Stock Android: I read that IMSI rotation works out of the box on standard Pixel factory software without needing to flash GrapheneOS. Can anyone confirm if this is working smoothly for them on stock software? Do you lose out on any major network-level privacy protections by staying on stock?
Real-world pros/cons: For those who chose to stay on Stock Android just to avoid the hassle of flashing a custom OS, do you feel like you are still getting your money's worth? Does standard Google software telemetry feel like it defeats the purpose of Cape's network privacy, or do you still feel it's a massive upgrade from traditional major carriers?
Appreciate any insights or experiences you can share before I make the jump!
I’ve already gone to tech support about this and it’s been escalated, but no real solution without replacing the eSim and driving 5 miles.
There is no cell service at my house - I live in the hills outside of a major metro area and so we rely on wifi calling for service at home. Surprisingly the voice over wifi has been working well enough since we started but over the last few days, Cape somehow detached itself from my phone and my wife’s, and a cell service called ‘Proximus’ took over - replacing the cellular APN’s with its own, at which point there is no service, wifi or otherwise.
I hope this can get resolved as this obviously never happened with T-Mobile or Verizon.
The onl
Has anyone run into any issues with feedback or echo during calls? On iOS with airpods and getting some feedback, not terrible, but noticeable. This is the first time, maybe just had a bad connection on both sides but not sure if anyone else has had that experience while not on speaker.
Coming from being an AT&T user, I’ve been using Cape for a month and I can happily say the service has been solid. I have been wanting a service that eliminates KYC and focuses solely on privacy and this service was able to provide that with straightforward billing without extra fees.
Early in my first month, I experienced a few call drops and network reliability issues but I was able to stick it out and it improved recently the past week which I was grateful for. I know the Cape team has been working hard on improving the network and adding in new features and I’m excited to seeing how the project evolves.
I will be sticking with this service for the long term if anyone new wants to join the service and help the community grow I will drop my referral code down below and we both get $20 off our subscription. Thanks and stay blessed.
Referral code: 30AJMV6M
I just signed up for Cape service and I’m testing it alongside my old mobile provider, so I used a new number for Cape while I’m testing it out.
I want to know, can I port-in my old number in the future if I decide to completely leave my old mobile provider?
Save $20 a month with referral code: NNFR37P6
Graphene OS on pixel 10a, calling and texting does not work on secondary profiles with call and text enabled. Mobile data seems to work, but text get stuck on "sending" or "not sent. Trying again," and texts are not received either. I am using the messenger that comes with Graphene.
Phone calls say "mobile network not available." US mobile sim (text/call/data) does work on both profiles, cape does not. Has anyone else encountered this issue?
I have some very good news to share. Last week we shipped a fix to an issue with our GTP proxy that was causing packet loss and bottlenecking download speeds.
We have seen this more than 2-3x the download speed for us internally. I was previously getting around 80mb/sec at home and now regularly get over 300. I had one customer message me and say they saw over 800mb/s down now.
If you ran a speed test before and thought we were slow, I would encourage you to run it again and see if things have improved.
We’re not done. There are several other network upgrades we’re working on that should continue to improve coverage and performance throughout the rest of the year. Will share more about those in the future.
As a 5 years GOS/FOSS jockey I added a 2nd esim with Cape since I LOVE the IMSI rolling and 24 hour call log deletion. But sadly network coverage and data speeds just aren't ready for use as a primary phone in Arizona, if you spend any time in rural areas. Oddly my data seems to hit the internet in rural Kansas...
Sadly the referral program isn't something I can take advantage of since I cannot recommend the service. My family and friends would roast me if I convinced them to switch.
It's also a disappointing that instructions on cancelling service are not accurate enough to actually cancel the service.
Keep going Cape! LOVE the intent and I'll check back every 6 months or so to see how things are coming along.
So, I had the 4 referrals needed for my monthly to go to zero $ but then, mysteriously, the numbers dropped to 2... I contacted Cape support, and it turns out, that if some of your referrals cancel their subscription/account (even after they initially paid for the first month), you lose that referral. That didn’t seem logical to me (never seen a referral program where referrals just “disappear” after receiving credit for them, but they sent me to their FAQs page, which states:
“If one of your referrals cancels their account, you’ll lose the $20/month credit you were receiving from their subscription. Your total monthly discount will adjust in your next billing cycle.”
KIND OF IMPORTANT: If you want to keep your account at $0/month, you need to find 4 “high quality” referrals I guess, who will not cancel later, and that includes the referral code you yourself used when opening the account (being that the code you use counts as one of your 4 referrals). I consider myself one of those “high quality” referrers as I have no intention of canceling. If you are too, feel free to use my referral code: HW9EEBRD
I noticed my texts say “not encrypted”, and RCS (which can encrypt texts) is off. It just says “awaiting verification“. Support said it won’t work because I have IMSI rotation enabled. So much for security.
Now I have to reset and reinstall SIM to get RCS back.
Not sure it’s worth it. I’m paying more than what I could pay elsewhere for cell service.
If anyone is willing to use one of my referrals, I might keep cape.
Q36XG3N3
i have 3 slots available.
This would be the perfect ploy for an alphabet agency...
Today is day 3 after switching to Cape and I've already switched back to my previous carrier. Good god Cape is AWFUL. To preface this, I live in the DC/NoVa region, where every carrier has great coverage and strong signals, so it's not like I'm in the Mojave Desert or anything.
I was driving to meet a friend this morning and was on a major highway. I encountered a backup where every lane was at a standstill. I picked up my phone to check Google Maps to see how long a delay to expect, and...I couldn't get a signal. Same for Waze. Same for HERE We Go. Same for my browser. Nothing. Zero. So I dialed my friend to tell her I was going to be late, and...no signal. I couldn't make any calls, and texts weren't going through either. Then I started getting anxious. No signal? No coverage? HERE???!!??? I hadn't encountered a cellular dead zone since I had my first flip phone in 1998.
A couple of hours later, I made it home. The first thing I did was call my previous carrier and switch back. Never, ever, ever again will I use Cape. Hell, this was such a terrible experience that I'll likely never switch to ANY carrier again.
The website used to say, "voice coming soon" in the areas that talk about Secondary numbers. I see it now just says they are text only. Is there still a plan to make them voice numbers as well at some point? I'd argue that without voice access they are not usable for most use cases. For me, I would use it for banking/financial accounts, and other core services. All of those companies may have need to reach me by phone, not just text, at some point. This makes secondary numbers pretty useless for me. I can really only use them for when I want to get a code for some type of retailer promotion.
Is there an official recommendation on best practices to follow to secure the recovery phrase?
It makes me a bit nervous that I could lose my phone number forever if my phrase is lost or stolen. At least with traditional accounts there are multiple factors in place to prevent account theft and I could probably go to a physical location with an ID if I forgot my password or pin. Looking up suggestions on storing seed phrases in the crypto community only increased my paranoia. I know I’m more likely to lock myself out than have my number stolen, but I also don’t want to risk anyone who finds the phrase being able to irreversibly take over my number.
Where do people fall on the spectrum of storing the recovery phrase in a standard cloud based password manager and splitting the phrase into multiple shards, engraving each shard into steel, and locking them in different locations?
Enjoying it so far, although sometimes I can’t view my subscription information in Cape’s app (I’m using it on Graphene OS). Joined because I wanted a privacy focused network and phone that keeps of my activism stuff off of my primary phone.
I’m also excited—looks like someone used my referral code, and I’m now paying $8/month (was supposed to pay $70, but got a discount code in the mail with my phone, so I was paying about $28/month)
If anyone needs, my referral code is DC8MNT0W.
We recently completed a big upgrade to our mobile core that should make WiFi calling more reliable. We have been testing it some internally and seeing positive results. A number of you have volunteered and asked to help us test early features, so we figured why not turn this over to the community now to help test it in more diverse real world scenarios.
This does NOT mean WiFi calling is officially supported by Cape. If you enable it, you may experience loss of service. Only do this if you are willing to tolerate encountering some rough edges and documenting them for us via bug reports in the Cape app.
To enable it:
iOS: Go to Settings > Cellular > Cape SIM (if you have multiple SIM's) > WiFi Calling and toggle it ON
Graphene: Settings > Network & Internet > Cape SIM > Carrier setting overrides. Toggle OFF Enable Overrides, change WiFi Calling to "Forced available" and then Toggle back ON Enable Overrides.
If you are on any other non-Graphene Android device, it will not work yet. We expect it to be available on Samsungs + Pixels by EOY. It's on the same timeline and blocked by the same thing as RCS.
If you encounter any issues with WiFi calls or experience loss of service please file a bug report through the Cape app and let us know exactly what you did and what happened so we can reproduce it internally.
There is one known issue on iOS: You cannot have Identifier Rotation enabled in conjunction with WiFi calling (every time your identifier changes it will toggle WiFi calling back off). This is the same issue we've seen with RCS on iOS. We are working towards a long-term solution for these, but it will likely be EOY or early next year before we have a path forward for everything to work well with Identifier Rotation.
I’ve had a few people reach out to me over the past couple days saying that when they call me, it doesn’t ring and instead they receive the following message/recording: “the number you have dialed has calling restrictions that prevent the completion of the call”.
FYI, we are aware of an issue with RCS messaging currently not working on GrapheneOS. This is due to a recent change made by Google. GrapheneOS has already prepared a fix, but it has not been released and will be a part of their next OS update, which we typically see about once a week.
update: I spoke too soon, cape told me they can’t apply it but gave me the same price for next 6 months and refunded me for the first bill. Please help me out and use my referral code below :)
I forgot to apply one during setup, and Cape support (via chat) has offered to apply one now, which is awesome. Would love to get one I can confirm is working.
Here is mine if anyone needs one, I still have 4 slots left (but will update this if the number changes): Q36XG3N3