|
Nitrousoxide posted:What's the average data usage for folks here who switched from t-mobile's nerd plan? I'm at about 1.5 GB/month, but I don't use my office's wifi. Could probably halve that if I did.
|
#
?
Dec 21, 2016 00:40
|
|
|
|
| # ? May 12, 2024 00:07 |
|
|
I use about 1GB/month, and I'm always on wifi at work/home. This would be higher if I didn't cache music/podcasts etc ahead of time.
|
|
#
?
Dec 21, 2016 00:48
|
|
|
~1.4 gigs with 500 megs being android os chewing up data while on wifi for no reason, and Fi support claiming is literally not possible.
|
|
#
?
Dec 21, 2016 01:07
|
|
|
I range from 1/2 gb when I'm at home to over 3 gb if I out and about. I'd go way higher if I wasn't careful about caching stuff offline and conscious of data costing money. With the Nerd Plan, I was hitting 5 gb easily, but work didn't have WiFi and streaming Google Play Music and podcasts added up quick.
|
|
#
?
Dec 21, 2016 01:56
|
|
|
Does anyone know if the T-Mobile nerd plan allows Wi-Fi calling? That's one of the best things about Project Fi, using the home and work wifi to replace a weak signal in the basement.
|
|
#
?
Dec 21, 2016 02:45
|
|
|
Silly Burrito posted:Does anyone know if the T-Mobile nerd plan allows Wi-Fi calling? That's one of the best things about Project Fi, using the home and work wifi to replace a weak signal in the basement. Yes but it still uses minutes because gently caress you that's my name.
|
|
#
?
Dec 21, 2016 02:48
|
|
|
monster on a stick posted:Yes but it still uses minutes because gently caress you that's my name. Lol, good to know. Thanks!
|
|
#
?
Dec 21, 2016 03:07
|
|
|
Anyone have a referral code? Going to sign up tonight or tomorrow
|
|
#
?
Dec 22, 2016 03:21
|
|
|
weinus posted:Anyone have a referral code? Going to sign up tonight or tomorrow Just sent you a link!
|
|
#
?
Dec 22, 2016 03:26
|
|
|
Where do you find your own referral code?
|
|
#
?
Dec 22, 2016 14:12
|
|
|
Johnny Truant posted:Where do you find your own referral code? https://fi.google.com/account?u=0#share My link looks like this: https://g.co/fi/r/HXE34U HXE34U is my referral code.
|
|
#
?
Dec 22, 2016 14:15
|
|
|
If anyone else is looking to sign up and get $20 each for us both here's my referral link: https://g.co/fi/r/1F92N6 I've had Fi for over a year now and it's well worth it. I travel a lot for my job overseas and it works really well. Even better now that they support 4G in most countries.
|
|
#
?
Dec 23, 2016 16:08
|
|
|
Nitrousoxide posted:What's the average data usage for folks here who switched from t-mobile's nerd plan? Its hard to tell with TMobile because free music streaming screws up your usage tracking. I was probably between 1-2 GB on the nerd plan not counting music streaming. I switched out of that to a regular TMobile plan because my job changed and the minutes were killing me. On Fi since Nov 29, I'm at 1.1 GB cell, and 21.87GB wifi. I'm a lot more conscious about connecting to public wifi now. If you're only looking at a data perspective, Nerd Plan is (was?) $30 for 5 gigs and free music, and Fi is $70 for 5 gigs ($20 + $10 per gig). If you need unlimited minutes, Fi is the better deal over a TMobile regular plan if you use less than 4 gigs.
|
|
#
?
Dec 23, 2016 17:03
|
|
|
Is it just me or is call quality on Fi really lovely? Even when going from Pixel to Pixel, my girlfriend's (who's on Verizon) voice sounds like it's coming out of a tin can. I used to believe it might have been a combination of her old SGS5 + Sprint. Since she switched networks and phone devices, though, the fact that I'm still experiencing lovely incoming audio quality has me wondering if it's Fi to blame. Is decent-sounding incoming phone audio restricted to wifi calling?
|
|
#
?
Dec 23, 2016 17:40
|
|
|
I don't know if I'm the only one, but between all the handsets and cellular providers I've been on, call quality has never been particularly great. Mobile phone calls have always sounded fuzzy, choppy, and they still drop constantly. I sincerely don't think it's a Fi vs. Other Guy thing.
|
|
#
?
Dec 23, 2016 19:28
|
|
|
Only issue with Fi service I've seen is it takes 5-30 extra seconds to actually initiate the call, from my end. Other than that the quality has been the same, if not slightly better(?) than my Sprint service. 
|
|
#
?
Dec 23, 2016 20:11
|
|
|
Fi is a huge improvement over my AT&T service, just in the first ~24 hours of use, and the Pixel is pretty rad. One thing I can't seem to figure out is getting the Google Assistant to send SMS via Hangouts. Maybe that's not supported yet? I switched over from Messenger to unify SMS etc across phone/tablet/desktop whatever, but I can't seem to figure out how to have the Assistant use Hangouts.
|
|
#
?
Dec 24, 2016 20:06
|
|
|
FreelanceSocialist posted:Fi is a huge improvement over my AT&T service, just in the first ~24 hours of use, and the Pixel is pretty rad. One thing I can't seem to figure out is getting the Google Assistant to send SMS via Hangouts. Maybe that's not supported yet? I switched over from Messenger to unify SMS etc across phone/tablet/desktop whatever, but I can't seem to figure out how to have the Assistant use Hangouts. It doesn't and won't. Don't burn energy trying to figure out the rationale. My gut feeling is that hangouts SMS integration is going away in the future. Maybe when RCS rolls out.
|
|
#
?
Dec 24, 2016 21:50
|
|
|
So I'm having an interesting issue with Fi. I chose to bring my Google Voice number over to Fi, and the activation process completed after a few hours. However, when people like my friends and family try calling my phone they get an incredibly strange-sounding error recording that starts with static, then says "...Cannot be completed. Please check your number and try again" but then, over the last end of that message, a male robot voice says something along the lines of "D S O, FOUR ZERO TWO D-" and then the line goes silent before switching to a busy/off hook tone. Thing is, long-distance incoming calls have no problem. If my girlfriend uses Hangouts dialer to call my Fi number (she doesn't have GV so it just comes up as Restricted on my phone) the call comes through. I can set my Cricket number to forward calls to GV and those calls come through without a problem as well. It's literally just local numbers dialing my Fi number that get the creepy error recording. Hangouts does not ring on any other devices when this happens, though the call is listed in my history on the Fi website. I can make outgoing calls without a problem. I can send and receive texts without a problem, and data works just fine. I called the support folks and they escalated the issue, but I'm wondering if anyone has a similar problem.
|
|
#
?
Jan 6, 2017 06:12
|
|
|
Congratulations, you figured out the secret of number stations.
|
|
#
?
Jan 6, 2017 06:25
|
|
|
"escalated the issue" means "got you to go away" half the time. Good luck.
|
|
#
?
Jan 6, 2017 06:27
|
|
|
https://www.youtube.com/watch?v=QPr1WtJM1iY Maybe I'm supposed to solve a mystery with this. (It's all blurred to poo poo because I'm not going to just post my phone number on the internet thanks)
|
|
#
?
Jan 6, 2017 07:11
|
|
|
That video is unavailable 
|
|
#
?
Jan 6, 2017 08:15
|
|
|
Quidthulhu posted:That video is unavailable  I had it still set to private while the blur was being applied. Should be fine now.
|
|
#
?
Jan 6, 2017 09:02
|
|
|
Uthor posted:Congratulations, you figured out the secret of number stations. it sounds more like their phone number evolved into a numbers station. maybe if they change carriers again, the number will turn into, like, the ghost of alan turing. worth a shot imo
|
|
#
?
Jan 7, 2017 16:42
|
|
|
That sounds like a SIP error code. Do/did you have an outstanding balance on your Google Voice number or something?
|
|
#
?
Jan 7, 2017 17:35
|
|
|
FreelanceSocialist posted:That sounds like a SIP error code. Do/did you have an outstanding balance on your Google Voice number or something? Nope, I only use GV for the "one number to ring them all" function. Last thing I ever got charged for was porting the number in in 2012. E: I also found out that calling from my desk phone at work (a local number) works. Now I need to find someone I know with a local mobile number who doesn't have cricket after convincing drat near everyone to switch to cricket, to see if it's just the carrier. FAUXTON fucked around with this message at 23:09 on Jan 7, 2017 |
|
#
?
Jan 7, 2017 23:05
|
|
|
Have any of you dealt with moving to Fi from T-Mobile, where you had two lines on T-Mobile and want to keep one there but port the primary number to Fi? If so, did you just port that one number over normally or did you have to deal with T-Mo or have any other issues?
|
|
#
?
Jan 9, 2017 02:16
|
|
|
I'm no telecommunications engineer but I don't think the new SIM card they're sending is going to solve the problem. I've narrowed it down to local cricket mobile numbers (I.e. my entire drat family). I did the MMI code from my cricket number way back when I got it so when someone calls that number it forwards to my GV (now Fi, maybe?) number. That occurs without a problem. However, if I call my GV?/Fi? number from my cricket number I get that screwy error message. Local calls from non-Cricket mobiles work fine. Long distance calls from non-Cricket mobiles work fine. Local landlines work fine. Texts and data work fine. I ported this number into GV in 2012 so I'm more than a little attached to the loving thing.
|
|
#
?
Jan 10, 2017 04:26
|
|
|
FAUXTON posted:I'm no telecommunications engineer I am, though admittedly I don't handle voice much. But what you've been describing sounds like a voice translations issue on the Cricket side - something like them having your GV/Fi number built in the switch their customers are calling you from, so because it's built locally and likely not port triggered (an option for lines that are ported or going to be ported to another carrier), it's not checking the LRN (local routing number) to know it is supposed to send it to another carrier/switch. This is just one moderately common possibility. It could be something else, of course, but the quickest way to sort it out is to call Cricket support to report the call failures. They should take failed calls at least moderately to very seriously, but will want the calling number, called number, error info and the time of the call to research it - a few call examples from different times won't hurt. Don't try to explain or theorize too much with them, just report the failed calls, tell them other local Cricket users are telling you they're getting the same thing and ask them to research and fix it. Have friends test call and call support, too, if you don't get a reasonable response (I have no idea how Cricket support is).
|
|
#
?
Jan 10, 2017 05:33
|
|
|
rattrap posted:I am, though admittedly I don't handle voice much. But what you've been describing sounds like a voice translations issue on the Cricket side - something like them having your GV/Fi number built in the switch their customers are calling you from, so because it's built locally and likely not port triggered (an option for lines that are ported or going to be ported to another carrier), it's not checking the LRN (local routing number) to know it is supposed to send it to another carrier/switch. Oh so it's like a URL that doesn't yet have the DNS propagation for its actual IP so when someone throws the GV/Fi (???) number at the system there's no path for the switch to say "OK this is a Fi number, kick it to them?" It would sort of make sense since I ported the number from Sprint to GV in 2012. It only stopped functioning properly when I ported it over from GV to Fi so if there's separate systems for GV and Fi and Cricket is still hurling that number at GV who is like "lol wtf is this, this isn't our number" instead of Fi where it should be going, then I can see it just falling into the ether as observed. Anyway, I just called their so-very-friendly offshore support guys and had it escalated as a failed call issue. Had to go over all the stuff I did to rule out other causes and the CSR eventually agreed that it seemed like a Cricket issue and kicked it up the chain. Hopefully. Thanks for the advice, I'd just assumed it was on the Fi side of things since it started when I activated Fi, and everything I run into online is saying that moving a number from GV to Fi is a legendary briar patch.
|
|
#
?
Jan 10, 2017 06:13
|
|
|
FAUXTON posted:Oh so it's like a URL that doesn't yet have the DNS propagation for its actual IP so when someone throws the GV/Fi (???) number at the system there's no path for the switch to say "OK this is a Fi number, kick it to them?" Something like that. Telephone switching is a bit hard to compare to IP. LRNs are basically pseudo-telephone numbers that correspond with a switch. Every TN has an LRN associated to it, identifying the switch it's built in. If a TN isn't locally configured in a switch, it knows it needs to look up the LRN. If it is locally configured, then it generally won't look up the LRN unless the port trigger option is set, which is the scenario I described. Port triggering is just a flag to tell the switch that it should look up the LRN even if the line's local - it's what allows your current carrier to leave your line active/configured/working even though you're about to port out and helps keep the service transition/interruption short when porting numbers around. That was all just a guess based on experience/your description. It could always be them straight mis-delivering the call, too, which if it happened at the time of the GV->Fi port, could mean they haven't picked up the new LRN (assuming GV/Fi use separate LRNs for the two services in that area). But honestly, I don't think that's normally an issue - not something that would persist beyond a day or two (depending on how long they cache LRN lookups) unless Cricket was having some larger issue pulling LRNs.  Glad Cricket agreed it was their issue. Hopefully it's fixed soon.
|
|
#
?
Jan 10, 2017 08:28
|
|
|
Cancelled Fi service, here's to hoping they can just put my number back in GV like it always was and I don't have to go around playing "new fone who dis" with everyone and everything in my life since I've been giving that number out for close to a decade (almost 6 years with GV and for a few before that before porting it out of Sprint).
|
|
#
?
Jan 12, 2017 04:08
|
|
|
FAUXTON posted:Cancelled Fi service, here's to hoping they can just put my number back in GV like it always was and I don't have to go around playing "new fone who dis" with everyone and everything in my life since I've been giving that number out for close to a decade (almost 6 years with GV and for a few before that before porting it out of Sprint). I had no issues bringing my number back to GV from Fi. It was so painless I don't even remember how I did it.
|
|
#
?
Jan 12, 2017 15:05
|
|
|
Just got back from a cruise to Cozumel/Progreso and Google Fi worked like a champ when we pulled into port. We only made one call (20 cents a minute) but the data and texts worked with no issues at all. It was a much better experience than when we used AT&T a couple of years ago and were trying to avoid roaming charges.
|
|
#
?
Jan 12, 2017 15:50
|
|
|
Any reviews in here on how their 5x responded to 7.1? I have the update taunting me but after getting burned on an older tablet I thought I would wait a bit.
|
|
#
?
Jan 12, 2017 16:20
|
|
|
Mercury Ballistic posted:Any reviews in here on how their 5x responded to 7.1? I have the update taunting me but after getting burned on an older tablet I thought I would wait a bit. I installed it yesterday and it seemed to work fine for me. I don't know if there are any known issues with it or what to look out for though, so I'm not a very knowledgeable source here.
|
|
#
?
Jan 12, 2017 17:09
|
|
|
It is working fine for me so far, downloaded it yesterday as well.
|
|
#
?
Jan 12, 2017 20:13
|
|
|
Updated mine about an hour ago. I'm seeing a 100% success rate!
|
|
#
?
Jan 12, 2017 21:12
|
|
|
|
| # ? May 12, 2024 00:07 |
|
|
Installed, fingers crossed...
|
|
#
?
Jan 12, 2017 22:41
|
|