As everyone may know by now, T-Mobile plans to provide wifi calling to the Nexus 6 in early 2015.
http://newsroom.t-mobile.com/news/t...-to-its-data-strong-network-this-november.htm
My question is if this will only come to T-Mobile purchased Nexus 6 devices or will it be a global update pushed out by Google to allow wifi calling on carriers that provide this service. I would love to go with T-Mobile, but my home does not offer great service on their network. When wifi calling becomes available I'll jump on their network but until then I'll need to stick with either Verizon or AT&T. With that said, could I purchase the phone unlocked through Google Play or through Motorola (financing at 0%) and still use the phone with T-Mobile wifi calling once available?
Thoughts? Any input is appreciated.
There's one variant for the US so yes, you can.
PhantomGamers said:
There's one variant for the US so yes, you can.
Click to expand...
Click to collapse
Agreed. I know there's only one model for the US. I'm just not sure how this would work. I guess I don't know enough about wifi calling and the update that needs to be pushed for it to work. I know the only current phones that work with T-Mobile wifi calling are T-Mobile phones. I think I read somewhere it's baked into the kernal, but really not sure.
Thanks
Aspesi4 said:
Agreed. I know there's only one model for the US. I'm just not sure how this would work. I guess I don't know enough about wifi calling and the update that needs to be pushed for it to work. I know the only current phones that work with T-Mobile wifi calling are T-Mobile phones. I think I read somewhere it's baked into the kernal, but really not sure.
Thanks
Click to expand...
Click to collapse
I mean it's hard to say for certain until the update is pushed, but odds are what will happen is the update will be pushed to everyone with it restricted to working with t-mobile in the update, since the update is going to be from T-Mobile working with Google. I suppose there's hope that it'll support any carrier that will allow it but I wouldn't hold my breath for that.
Im assuming it will be the same hardware but with different device IDs for each carrier. This way OTAs will be more easily targeted.
It will be pushed to everyone. The same as a Verizon iPhone will work with t mobile Wi-Fi calling.
I was messing around with an unlocked At&t iPhone 5s I had gotten from my daughter which was supposed to have wifi calling pushed to it with ios 8 on T-mobile. Sorry to say it never happened. I am going to wait on the T-mobile sold phone just to be safe.
I don't see them pushing an update to all the phones for WiFi calling.
The way their current WiFi calling works is with a modified kernel. This means that only T-Mobile branded phones that get their updates from T-Mobile will be able to do WiFi calling. However, if they come up with a way for the Nexus 6 to support WiFi calling, i'm guessing it's going to be another app you'll have to install so that it can forward calls to your dialer. I do NOT think that they will push an update out to all Nexus phones to get this to work on ONE carrier. Since the Nexus 4, ALL of the nexus phones are the same across all carriers. At least in the US, if you buy the Nexus 5 from T-Mobile, you got the same Nexus 5 that you'd get from the Google Play Store. It also seems that they're the same phone for overseas too. The reason i say that is because if you look at the Galaxy Nexus (it had multiple versions; including international versions), it had multiple versions of the software, as you can see here: https://developers.google.com/android/nexus/images#takju. Takju and Yakju are both the Galaxy Nexus with different software. They haven't done that since.
I think this will be an app you can install on your phone to make it work with WiFi calling. Maybe Google will be pushing out an update to change the kernel to allow this... maybe... but the carriers will still need to build an app and push the users to download it. The carriers have not been allowed to change the software since the Nexus 4.
bryctucker said:
I don't see them pushing an update to all the phones for WiFi calling.
The way their current WiFi calling works is with a modified kernel. This means that only T-Mobile branded phones that get their updates from T-Mobile will be able to do WiFi calling. However, if they come up with a way for the Nexus 6 to support WiFi calling, i'm guessing it's going to be another app you'll have to install so that it can forward calls to your dialer. I do NOT think that they will push an update out to all Nexus phones to get this to work on ONE carrier. Since the Nexus 4, ALL of the nexus phones are the same across all carriers. At least in the US, if you buy the Nexus 5 from T-Mobile, you got the same Nexus 5 that you'd get from the Google Play Store. It also seems that they're the same phone for overseas too. The reason i say that is because if you look at the Galaxy Nexus (it had multiple versions; including international versions), it had multiple versions of the software, as you can see here: https://developers.google.com/android/nexus/images#takju. Takju and Yakju are both the Galaxy Nexus with different software. They haven't done that since.
I think this will be an app you can install on your phone to make it work with WiFi calling. Maybe Google will be pushing out an update to change the kernel to allow this... maybe... but the carriers will still need to build an app and push the users to download it. The carriers have not been allowed to change the software since the Nexus 4.
Click to expand...
Click to collapse
All nexus 5 phones got the update for sprint spark.
Can anyone on sprint with android 10 update confirm VOLTE functionality? Im on oreo. Before i take the plunge I want to be sure VOLTE has been enabled.
Guess that's a not. I Lol. Smh. Has any of the "security updates" added any new functionality?
Are there any Sprint users out there?
Are there any Sprint users out there?
I have the latest june update and VoLTE does not work. I even work at sprint as a technician. VoLTE is broken.
I have the U1 running in my Sprint model and VOLTE is nowhere to be found.
Hello ....SPCS User for A Long time here ... unfortunately VolTE does not work on android PIE.
I had to make a choice Go back to Android 8.0 and hack it to enable VoLte or use latest and greatest Android PIE.. I chose functionality over pretties so im back on 8.0.
There is a thread on XDA with the files to go back please note this is for the SM-N-960U1.
I have oreo running and i did the VOLTE hack. When in call however i keep losing packets. Its really hard to have a conversation on this $1000 computer. Either my voice cuts for long periods of time or their's does. The hack isnt super functional. Essentially its half a Voip phone/ computer. How the heck does sprint skip out on core functionality on a flagship device?
Can any sprint users confirm if VOLTE is in the july patch? If not im sticking with Oreo.
I'm on sprint.... but I'm using an unlocked phone..as of the latest update no..no volte setting and no way to hack around to achieve it...
Ok no VOLTE. Does the update at least have night mode patch?
How about the August patch?
Sprint Note10+ has VoLTE!!!!View attachment 4809678
Sent from my SM-N975U using Tapatalk
Not the Note 10 + lol. The Note 9 august update on sprint. The phone has officially been out a year and so has VOLTE. It would be nice for the feature to finally be officially supported.
docdg said:
How about the August patch?
Click to expand...
Click to collapse
It is not on the August patch. I just checked.
Sent from my SM-N960U using Tapatalk
docdg said:
Not the Note 10 + lol. The Note 9 august update on sprint. The phone has officially been out a year and so has VOLTE. It would be nice for the feature to finally be officially supported.
Click to expand...
Click to collapse
Yeah I know, I had the Note9 and got the last August update with no VoLTE. I was just saying that the Note10+ on Sprint has VoLTE is all.
Sent from my SM-N975U using Tapatalk
Dang you sprint dang you to heck
How about the android 10 update? Lol
Annie may. Oops i mean anyone.
Can anyone with a 960u on sprint confirm VOLTE functionality? Much appreciated
Frick_trump said:
.
Click to expand...
Click to collapse
okay.
i was the dumb one to say such thing about me.
its better that you think of me as a kid
noone should know who i am or what i do. better for me anyway hehe??
Hello,
Apologies in advance if this is discussed already. I tried but couldn't find this specific question discussed.
I bought this USA unlocked, carrier-agnostic version of LG V40 ThinQ (LM-V405QA) from a reputed warehouse club in US. Has been working fine with AT&T since January 2020. I had to get it because previous Samsung phone would not get Android 9. But I had used it for 4 years.
Now I must have Android 10 for my company apps to work. AT&T tried but could not push Android 10 to my phone. Probably because their version of this phone is different by a letter or digit.
Am I at the mercy of LG and must wait until they release Android 10 to USA unlocked version?
Thanks
You are right, it has been discussed many many times already, and unfortunately, you are not going to find a specific question because people tend to use their own way of asking.
There is no easy and fast way, if you want to wait for LG to update it may take a long time or
https://forum.xda-developers.com/lg-v40/how-to/sprint-crossflash-to-unlocked-pie-t3989149
I suggest you use the Verizon rom, that's the one that gets the fastest updates ...
There are, as mentioned, other options than waiting for LG (I do wish they would make that available soon). Another options besides vzw would be the Korean Open V409N (android 10), that's what I'm using, in the states. It does have a few more idiosyncrasies compared to say vzw, but it's an 'Open' version, thus not tied to any carrier, so only LG's bloatware.
I'm using the V409n myself now and the only thing I've not got to work is vowifi, but volte does work. Everything else seems to function normally. A major consideration when crossflashing is 'which rom supports the bands I need'? For at&t I think the vzw rom has all those bands, but if u want b71 for t-mo, then you'd need the us OP (a10 not out yet) OR, amazingly, the Korean v409n has b71.
keep in mind, crossflashing can lead to issues. I'd suggest backing up vital partitions **before** u do any crossflashing, just having the kdz **will not** restore it to factory.
cheers
AsItLies said:
There are, as mentioned, other options than waiting for LG (I do wish they would make that available soon). Another options besides vzw would be the Korean Open V409N (android 10), that's what I'm using, in the states. It does have a few more idiosyncrasies compared to say vzw, but it's an 'Open' version, thus not tied to any carrier, so only LG's bloatware.
I'm using the V409n myself now and the only thing I've not got to work is vowifi, but volte does work. Everything else seems to function normally. A major consideration when crossflashing is 'which rom supports the bands I need'? For at&t I think the vzw rom has all those bands, but if u want b71 for t-mo, then you'd need the us OP (a10 not out yet) OR, amazingly, the Korean v409n has b71.
keep in mind, crossflashing can lead to issues. I'd suggest backing up vital partitions **before** u do any crossflashing, just having the kdz **will not** restore it to factory.
cheers
Click to expand...
Click to collapse
Question, you have an actual V409N or some other 405 crossflashed like one.
Asking cause I have a UA (Sprint) crossflashed to QA that I use on T-Mobile. Okay without VoWifi, need VoLTE. I saw this V409NO30d_00_OPEN_KR_OP_0716.kdz. Wondering if it will work well with T-Mo in the US on a V405. That jump from 5 to 9 makes me doubtful.
Omizuke said:
Question, you have an actual V409N or some other 405 crossflashed like one.
Asking cause I have a UA (Sprint) crossflashed to QA that I use on T-Mobile. Okay without VoWifi, need VoLTE. I saw this V409NO30d_00_OPEN_KR_OP_0716.kdz. Wondering if it will work well with T-Mo in the US on a V405. That jump from 5 to 9 makes me doubtful.
Click to expand...
Click to collapse
Mine was (is) originally an UA at&t, not the korean. I'm in the states also, so no way I'd buy an oem Korean phone. The thing about volte and vowifi on t-mo, they allow it even with byo phones, but your sim (mvno types) have to be capable of it. I use Mint Mobile and had vowifi and volte - when I was using the US Open (QA) Pie rom. But I had to add (free) that feature (vowifi) on my mint mobile account.
Since you have qa, I would think volte would be working, what sim (t-mo) do u have? Not an mvno? As far as the korean rom goes, the 405 vs 409 isn't due to some incremental aspect, so there's no issue there. It's just an identifying Korea type number. But, I'd say if you don't have volte with QA Pie, then it's questionable you would get it working with korean rom.
do you know why volte isn't working for you now? Have you been given some 'official' explanation for that?
AsItLies said:
Mine was (is) originally an UA at&t, not the korean. I'm in the states also, so no way I'd buy an oem Korean phone. The thing about volte and vowifi on t-mo, they allow it even with byo phones, but your sim (mvno types) have to be capable of it. I use Mint Mobile and had vowifi and volte - when I was using the US Open (QA) Pie rom. But I had to add (free) that feature (vowifi) on my mint mobile account.
Since you have qa, I would think volte would be working, what sim (t-mo) do u have? Not an mvno? As far as the korean rom goes, the 405 vs 409 isn't due to some incremental aspect, so there's no issue there. It's just an identifying Korea type number. But, I'd say if you don't have volte with QA Pie, then it's questionable you would get it working with korean rom.
do you know why volte isn't working for you now? Have you been given some 'official' explanation for that?
Click to expand...
Click to collapse
Oh no, my VoLTE is currently working fine. Just pointing out that is something I can't lose. Where I am I have amazing LTE coverage. The 2/3G is not so great so phones that don't support it suffer on the calls. And I'm on a official T-mo Sim. Although coincidently I was recently looking at Mint, I came across this $90 all unlimited for 3 months. But it said it would reduce to 128 Kbps after 35GB and might further reduce it. And I use way over that. This last 2 months I went over 80GB... Wish carriers would start releasing plans base on speed not amount. I wouldn't mind 3-8 Mbps capped speed if it was cheap. I digress....
Phone, yeah, so to summarize. You got a UA, that you crossflashed to QA at some point (like me). But then to get Android 10 you cf to a 9N Open Kr and everything works fine except for the VoWiFi.
I did come across a reddit post of someone that also has a working 409N OS working on a UA it seems it does gets the 71. Was skeptical since it's not written on its specs on any site.
I know have 2 other questions. Did you went straight from QA Pie to 9N 10?
Thing is I am currently testing HavocOS. (Frankly, not impressed. Not Havoc, Android 10 in general. I think I like Android less and less with every update) Anyway. Not sure if jump directly to latest Kr kdz. The last Open is only 1 GB, which is about 1/4 of the last Pie. Wondering if something is missing. So thinking of going to last Pie kdz first and then update to the V409NO30d_00_OPEN_KR_OP_0716.kdz.
My second question would be: Are you experience any particular noticeable bug? I read that for some people the ATT/VZ update brought some problems. But unclear if its just an update problem from the carriers, a problem that don't happen if you factory reset. Or problems involving Android 10 on the V40, potentially affecting all V40. Although latest Kor Open been from August, they had enough time to fix any issues.
Omizuke said:
Oh no, my VoLTE is currently working fine. Just pointing out that is something I can't lose. Where I am I have amazing LTE coverage. The 2/3G is not so great so phones that don't support it suffer on the calls. And I'm on a official T-mo Sim. Although coincidently I was recently looking at Mint, I came across this $90 all unlimited for 3 months. But it said it would reduce to 128 Kbps after 35GB and might further reduce it. And I use way over that. This last 2 months I went over 80GB... Wish carriers would start releasing plans base on speed not amount. I wouldn't mind 3-8 Mbps capped speed if it was cheap. I digress....
Click to expand...
Click to collapse
Well then, the thing to know about getting volte on 409N is that it's a kind of a hack. It's not officially supported. So, because this isn't my daily driver phone, I've messed around with it trying to get vowifi and now volte isn't working, for some reason. Thus, I hesitate to recommend it if you depend on volte working consistently.
Omizuke said:
Phone, yeah, so to summarize. You got a UA, that you crossflashed to QA at some point (like me). But then to get Android 10 you cf to a 9N Open Kr and everything works fine except for the VoWiFi.
I did come across a reddit post of someone that also has a working 409N OS working on a UA it seems it does gets the 71. Was skeptical since it's not written on its specs on any site.
Click to expand...
Click to collapse
Yes, that's what I did. 71 does def work, surprisingly (saw the specs it would not also). I used LTE discovery and in the SVC / Field Test menu selected ONLY band71, it connected to a nearby 71 tower. So the 409N does support it, although it's not available in Korea :-|
Omizuke said:
I know have 2 other questions. Did you went straight from QA Pie to 9N 10?
Thing is I am currently testing HavocOS. (Frankly, not impressed. Not Havoc, Android 10 in general. I think I like Android less and less with every update) Anyway. Not sure if jump directly to latest Kr kdz. The last Open is only 1 GB, which is about 1/4 of the last Pie. Wondering if something is missing. So thinking of going to last Pie kdz first and then update to the V409NO30d_00_OPEN_KR_OP_0716.kdz.
My second question would be: Are you experience any particular noticeable bug? I read that for some people the ATT/VZ update brought some problems. But unclear if its just an update problem from the carriers, a problem that don't happen if you factory reset. Or problems involving Android 10 on the V40, potentially affecting all V40. Although latest Kor Open been from August, they had enough time to fix any issues.
Click to expand...
Click to collapse
Havoc is lineage based right? Thus it doesn't have vowifi or volte? Not sure how that would meet your needs? And that 1GB indication on the firmware site is wrong, it will be about 4GB when downloaded. It's the full rom. CF does seem to cause issues, but I found with the 409N anyway, if initially did a partition DL, then, before changing anything in the phone, do a refurbish with the same kdz, and it didn't have any problems with nt-code, but I did have to enter the S/N in the ftm partition, for that to show up in the 'about' menu.
It seems though, if you want to be on 10 and have reliable volte, it's either wait for the NA OP to become available, or get a carrier specific device and use their network. I think I'm going back to NA OP 9, as everything works no issues at all.
cheers
Well, I should add, I did a bit of a refurbish this morning, actually a Part DL of everything I might have changed, inadvertently, trying to get vowifi to work. And now, volte is working just fine again.
So, it isn't 'officially' working, as mentioned. That may not be the way some want to go if they depend on it to always work...
cheers
AsItLies said:
Well then, the thing to know about getting volte on 409N is that it's a kind of a hack. It's not officially supported. So, because this isn't my daily driver phone, I've messed around with it trying to get vowifi and now volte isn't working, for some reason. Thus, I hesitate to recommend it if you depend on volte working consistently.
Yes, that's what I did. 71 does def work, surprisingly (saw the specs it would not also). I used LTE discovery and in the SVC / Field Test menu selected ONLY band71, it connected to a nearby 71 tower. So the 409N does support it, although it's not available in Korea :-|
Click to expand...
Click to collapse
Oh yeah, I'm constantly messing with the Bands to force it to connect to specific towers. Sometime it will keep connecting to some nearby that are constantly congested. So I just turn those off. But when I go to the next town I have to re-enable them. I use Lte Discovery and Network Cell Info Lite.
AsItLies said:
Havoc is lineage based right? Thus it doesn't have vowifi or volte? Not sure how that would meet your needs? And that 1GB indication on the firmware site is wrong, it will be about 4GB when downloaded. It's the full rom. CF does seem to cause issues, but I found with the 409N anyway, if initially did a partition DL, then, before changing anything in the phone, do a refurbish with the same kdz, and it didn't have any problems with nt-code, but I did have to enter the S/N in the ftm partition, for that to show up in the 'about' menu.
Click to expand...
Click to collapse
I believe so, and as far as I know there are no AOSP with VoLTE. But it doesn't affect me, I'm just playing with it while I decide what to do since I had to format it. Taking advantage before I refill it. My SIM is on my V20. Still going strong, on it's third battery thou. So glad is replaceable. It lacks some bands that the V40 has, particularly the new towers in my area. But otherwise I like it better. The actual second screen for notifications and shortcuts, the IR for the TV and a removable battery. Latest V phones are just too similar to the rest. But I'll stick with them for the Quad-DAC and Amp.
And thanks for the info. I'll keep it in mind.
AsItLies said:
It seems though, if you want to be on 10 and have reliable volte, it's either wait for the NA OP to become available, or get a carrier specific device and use their network. I think I'm going back to NA OP 9, as everything works no issues at all.
cheers
Click to expand...
Click to collapse
I honestly don't think there will be an NA OP 10. And I wasn't sure you could downgrade from 10 to 9 without tripping something. Didn't looked it up. Got too used that some of my other new devices all have anti-rollback. Limiting how high you can go before locking you up. And as stated before the newer the Android the less I like it. It has turn me off of the modding, seems more restrictive every generation. Had I know I would've just test it myself. lol Hence why I was asking so many questions, I was looking at it as a permanent step up. And the custom ROM for the v40, or well LG in general, is lack luster. Once 10 I'd be stuck between stock or LineageOS. Think I'll just give it a go. If you downgrade let me know how it turned out.
Omizuke said:
Oh yeah, I
brevity...
d out.
Click to expand...
Click to collapse
Hey! thought I should let you know as you're interested in exactly this also. I just tried something I thought would simply not boot and would have to re-flash all over again. But no! I copied over the OPEN_US partition from us open Pie, into the V409N korean open directory. There was one cfg file I had to change to point to it rather than the old OPEN_KR directory (renamed it to OPEN_KR_ori).
Boom! Now I have vowifi and volte and they work exactly as they do on us open Pie! Get the HD and wifi indication icons on the little dialer phone symbol as well!!
pretty damn awesome, so it can be made to work wooohooo hahahaha
AsItLies said:
Hey! thought I should let you know as you're interested in exactly this also. I just tried something I thought would simply not boot and would have to re-flash all over again. But no! I copied over the OPEN_US partition from us open Pie, into the V409N korean open directory. There was one cfg file I had to change to point to it rather than the old OPEN_KR directory (renamed it to OPEN_KR_ori).
Boom! Now I have vowifi and volte and they work exactly as they do on us open Pie! Get the HD and wifi indication icons on the little dialer phone symbol as well!!
pretty damn awesome, so it can be made to work wooohooo hahahaha
Click to expand...
Click to collapse
Thanks for letting me know. I had just noticed your post on the [Crossflash] AT&T tread and was trying it. When I did whoever build the android for the US devices decided to violated my device, uninstall the LG Messaging app and install the google messaging app. Without my consent, and make it so that the LG one wouldn't work even if you tried installing it. Along with other apps like LGPay and LGUpdateCenter. That pissed me off.
Something I hated from the V40 vs the V20 was the googlefing everything. For one, the SMS app on the V20 is many times better, including the customization and independent sizing. You can have you system with one font size but on the sms app you can pinch to soom and increase everything if you need. The one on OpenKR Android 10 also has this feature. Google messenger doesn't. And second, really hate google forcing their everything down your throat. If i wanted a closed ecosystem I'd used iOS. My main reason for rooting is to get rid of bloatware, including most of what google now add on phones. Google folder has more crap than the carriers one lol.
BUT it was an easy fix and I ended up learning something. So I'll call it a win.
In the config folder, the featureset xml files there's a line with "set_default_sms_app_to_googlemessenger" it'll allow for the LG/Android Messaging to work. I had already backed up the apk because I had tried to use in on other the other kdz, didn't worked then, now I know why. But apkpure has it. AND the phone still do. On that same config folder there is the custom_apk_list.cfg file. It shows the apps it removed and the one it install. And you can fallow the path on that cfg file to the apk. (/system/product/priv-app/LGMessage) for the SMS app. Gotta delete the "featureset" line and reboot to get it to run. Oh, and the line on the cfg line file. Tho I just deleted the whole file altogether. With this new found info if I go back to 9 I'll know what to look for to get the stock Android sms app to work. There's more info among those xml. And the boot and power off sounds. So yay for custom sounds.
That said, tried the T-Mo sim and I'm not getting VoLTE. I did the FTM and everything. I'm gonna try one more time. But using Kor refurbish and see how it goes from there. If it doesn't work I'll just go back to Open US Pie and leave it be. I really did like the look on it. Native dark theme work so much better than the themes I had.
AsItLies said:
Deleted
Click to expand...
Click to collapse
I went to order a pixel 5 yesterday and all they had in stock were the Fi variants (ordered anyways), after some quick research I discovered that they were the same phone as the unlocked version. I'm a T-Mobile customer, with 2 numbers, one for personal and one for work. I read where some people have said the esim is tied to Fi, I'm hoping someone here can shed some light on that as my plan was to have T-Mobile activate the esim for one of my lines and using the traditional sim card in the slot. Anyone done this?
Also, I've read where they say 5g isn't an option with dual sims, yet I also read where changes were pushed to allow 5g with dual sims... Anyone have an answer on that as well? Thanks.
Ducter said:
I went to order a pixel 5 yesterday and all they had in stock were the Fi variants (ordered anyways), after some quick research I discovered that they were the same phone as the unlocked version. I'm a T-Mobile customer, with 2 numbers, one for personal and one for work. I read where some people have said the esim is tied to Fi, I'm hoping someone here can shed some light on that as my plan was to have T-Mobile activate the esim for one of my lines and using the traditional sim card in the slot. Anyone done this?
Also, I've read where they say 5g isn't an option with dual sims, yet I also read where changes were pushed to allow 5g with dual sims... Anyone have an answer on that as well? Thanks.
Click to expand...
Click to collapse
The only difference with the Fi phone vs. the Google one is who supports it. If you have a warranty replacement it will have to come from the Fi team and not Google. Weird but true. Otherwise they are exactly the same. That includes not being branded to any one carrier. If you have a Fi account when you set up your phone it will automatically download the eSim if you want but if you don't then just pop in your physical sim and you're off to the races. Then contact the provider for a scan code for the eSim. I've not done it with TM but with Verizon and all works easily enough. Get yourself a 5G sim too while you're at it.
Now the big question, lol, I do not have 5G with both my sims active.. yet. I do not have the December patch from VZW either so I can't say if the merged code made it into the patch. I've asked all around and no one even responds to my inquiries including Android Police and 9to5 who initially reported it from the XDA feed. But supposedly Monday I'll get the Dec build and know one way or the other.
bobby janow said:
Now the big question
Click to expand...
Click to collapse
Thanks for the reply. I assumed as much but you know what it's like after you do something, you begin to wonder lol. I do not have Fi, hopefully if I have an issue, that won't become one.
Hopefully the 5g on both sims made it into the update, or will be making it in shortly. I'm coming from a OnePlus 6t and dissatisfied with how OnePlus has been handling their updates. Phone gets great updates, timely and functional for 6 months, after that it's mainly focused on the newer models and the updates slow down but do still come, 12 months it starts to get left behind and now, they throw a security update at you occasionally. Been on lineage for a while and just decided spec wise, modern phones do all I care for them to do so the pixel 5 looked like a nice offering even if it's not "top of the line". We'll see I suppose.
Ducter said:
Thanks for the reply. I assumed as much but you know what it's like after you do something, you begin to wonder lol. I do not have Fi, hopefully if I have an issue, that won't become one.
Hopefully the 5g on both sims made it into the update, or will be making it in shortly. I'm coming from a OnePlus 6t and dissatisfied with how OnePlus has been handling their updates. Phone gets great updates, timely and functional for 6 months, after that it's mainly focused on the newer models and the updates slow down but do still come, 12 months it starts to get left behind and now, they throw a security update at you occasionally. Been on lineage for a while and just decided spec wise, modern phones do all I care for them to do so the pixel 5 looked like a nice offering even if it's not "top of the line". We'll see I suppose.
Click to expand...
Click to collapse
You'll be happy with the phone. It's the right price, right size and battery lasts all day no matter what you do to it. At least for me, lol. There have been some issues with Fi support buy you really won't be dealing with them unless you have a hardware issue. As soon as I get the update on Monday I'll chime in here but you might get the device before that. Make sure you are there to sign for it as I've heard of some empty boxes arriving on doorsteps.
As for 5G if you need it you can toggle off a sim very quickly and bring it back online just as easily. If I toggle off my work number 5G pops right up. I don't usually do it but I will on the weekends sometimes. I don't find it any faster than lte at this point but perhaps TM is better the VZW. Then again I've yet to connect to the super duper 5G they are touting.
Ducter said:
Hopefully the 5g on both sims made it into the update, or will be making it in shortly.
Click to expand...
Click to collapse
Nope, didn't make it in. Still LTE with both sims active.
bobby janow said:
Nope, didn't make it in. Still LTE with both sims active.
Click to expand...
Click to collapse
Yeah, I received the phone Sunday actually, surprised me they delivered then as it was scheduled for Monday. I wasn't home, they delivered it regardless, another surprise as tracking said signature required and I watched on my camera the FedEx guy walk up, put the phone by the door and walk away... Worked for me I suppose.
My time with the phone so far has been good. I'm coming from a OnePlus 6t that I was happy with the performance of the phone but it was starting to have gps issues and would drop calls fairly often. This phone is much smaller but I like it. I'm 6'4 with large hands but it still is a nice size. Performance wise, if I'm honest I can't really tell a difference. Sure, benchmarks likely would suggest different but I don't use them, I use the phone and in that regard, the pixel 5 is fine. Camera, even with it's aging hardware takes much better pictures. I can't comment fully on battery as of yet but then again my 6t would easily outlast my usage per day anyways.