|
Jigoku posted:The Axon 7 has drat great hardware at $400 but you're going to want to ignore all the software features and I don't know what their commitment to updates is. That being said it got a bug fix and security update fairly recently. I just got this phone and thought I'd chime in. I had to replace my first one due to mic echoing issues and the second one I purchased has another problem where my mic will cut out during calls (turning speakerphone on and off seems to fix this). The cell reception is also worrisome, but I can partially blame the locations I live and work for that. Other than what I've mentioned, this phone is amazing. I just really hope they push another update soon, because I know I'm not the only one experiencing mic/reception quality deficits. Oh Lordy Lord fucked around with this message at 19:02 on Oct 7, 2016 |
# ? Oct 7, 2016 18:58 |
|
|
# ? May 25, 2024 21:49 |
|
Syrinxx posted:lol I know it's easy to poo poo on Verizon for all sorts of stuff, but I can't remember a recent device where Verizon was the sole reason behind a device not getting an already-developed update.
|
# ? Oct 7, 2016 19:06 |
|
Captain Yossarian posted:No build quality issues at all for me. I have mostly had a similar experience to this, but I find that daylight photos are often aggressively noise reduced or to the point where finer details are lost. Is there a way this can be altered via software or is this a limitation of the camera module?
|
# ? Oct 7, 2016 19:21 |
|
El Mido posted:I have mostly had a similar experience to this, but I find that daylight photos are often aggressively noise reduced or to the point where finer details are lost. Is there a way this can be altered via software or is this a limitation of the camera module? Thinking more about this, the camera itself is just... Odd. I haven't had the same issues (other then some noise reduction). I think I'll try a different camera app over the weekend and report back.
|
# ? Oct 7, 2016 19:31 |
|
CFox posted:Consumers would riot but with phones since it's been that way (with Android at least) for so long there's this weird stockholm syndrome going on where those that are aware of the issue pat themselves on the back for being smart and in the know since they can work around it. This is way too common. Tunga posted:It's rolling out to the N6 as of a few days ago so most likely within the next week or sooner if you want to flash the OTA yourself. Nitrousoxide posted:Opt into the beta, install the update, than opt out. That's how i forced the OTA to happen on my Nexus 6
|
# ? Oct 7, 2016 19:37 |
|
Not sure whether to ask Verizon thread or here: Is there a way to bypass the Motorola or Google setup wizard on a 2014 Moto X? Was just asked to do factory reset and it keeps on looping back to Motorola Privacy agreement from entering Google account information and I can't get past it. Doctor Butts fucked around with this message at 19:44 on Oct 7, 2016 |
# ? Oct 7, 2016 19:42 |
|
sleepwalkers posted:I know it's easy to poo poo on Verizon for all sorts of stuff, but I can't remember a recent device where Verizon was the sole reason behind a device not getting an already-developed update. The Droid Turbo. The exact same phone in Brazil has had Android M for a very long time. There's still no sign of it coming down the pipe for Verizon users. fake edit: in before, "lol, that's a 2 year old phone, bro."
|
# ? Oct 7, 2016 19:48 |
|
Doctor Butts posted:Not sure whether to ask Verizon thread or here: You can certainly skip adding a Google account.
|
# ? Oct 7, 2016 19:49 |
|
nimper posted:You can certainly skip adding a Google account. It detects it was factory reset and is asking for Google account. I don't have a skip option. Doctor Butts fucked around with this message at 19:57 on Oct 7, 2016 |
# ? Oct 7, 2016 19:53 |
|
That's device protection. To get around it, remove your google account from the phone before factory resetting. Dunno if there's a way around it now. https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/104542/~/device-protection
|
# ? Oct 7, 2016 20:25 |
|
Mogomra posted:The Droid Turbo. I wasn't going to try to dismiss it by it's age, mostly because it's not outside the two-year window quite yet (though it will be this month). I'm not sure why I didn't remember the Turbo, considering I had one. But you're right, that's exactly what seems to be happening with that phone. The Turbo is a bit of an oddball, AFAIK. Though I think it was only late July (of this year!) that Marshmallow was released for the non-Verizon variant. I remember the original Lollipop rollout on that phone and it took an exceptionally long time for that to be released as well. Edit: My original point was trying to say that it seems like lately, most flagship phones across all carriers are getting better at being provided updates, in large part due to the homogenization of flagship devices across carriers; you don't see Galaxy S and S2 levels of carrier-specific flagships anymore and I have to assume that helps. Even the Droid Turbo, despite technically being a variant on the XT1225 (or whatever it was) had a number of Droid-branded software features that differentiated itself. sleepwalkers fucked around with this message at 20:41 on Oct 7, 2016 |
# ? Oct 7, 2016 20:35 |
|
RZA Encryption posted:This is way too common. That it was delayed for the N6 sucks and shouldn't happen, but that they do updates as staged rollouts is not bad and people get far too angry about it.
|
# ? Oct 7, 2016 20:59 |
|
KS posted:That's device protection. To get around it, remove your google account from the phone before factory resetting. Thanks. Look like I can't get around it now.
|
# ? Oct 7, 2016 21:18 |
|
Thanks for all the Axon reports. I'm on a loaner phone for now, so I'm not feeling super urgent about the purchase. It seems SO close to being the perfect mid-priced phone though. I'm willing to wait to see if the next update fixes most of the software/reception issues I've read about.
|
# ? Oct 7, 2016 21:40 |
|
sleepwalkers posted:I know it's easy to poo poo on Verizon for all sorts of stuff, but I can't remember a recent device where Verizon was the sole reason behind a device not getting an already-developed update. The Galaxy Nexus had updates delayed every time and never got the final update the GSM version did, although I guess it's not really recent.
|
# ? Oct 7, 2016 21:50 |
|
pairofdimes posted:The Galaxy Nexus had updates delayed every time and never got the final update the GSM version did, although I guess it's not really recent. Google could have posted the updates if they wanted to. I think the real issue was due to it being LTE and Samsung not being able write a radio baseband to save their life. The vzw GNex might as well as been a completely different device. Hell, it was even a different size from the GSM version.
|
# ? Oct 7, 2016 22:00 |
|
I defied all logic and tried to snag a MXP since my Turbo broke, my girlfriend loves hers, it was on sale in September on the Moto Maker website, and I just needed something to make phonecalls and browse Facebook for 6 months. Turns out it's golden week in China so all of their shipments are delayed 7-10 days, and FedEx is saying Moto failed to provide some of the customs forms anyway so I shouldn't hold my breath. I'm thinking I'll just go buy a 5x or something instead.
|
# ? Oct 7, 2016 22:22 |
|
Shere posted:I defied all logic and tried to snag a MXP since my Turbo broke, I just posted about potentially picking up the MXP in the recommendation thread, so why does this defy all logic (My Moto X 2nd Gen just broke and I loved that thing.)
|
# ? Oct 7, 2016 22:29 |
|
Verizon and T-Mobile just joined Sprint & AT&T for a voluntary exchange program for the replacement Note 7s. People at Samsung are lovely their pants right now.
|
# ? Oct 7, 2016 22:36 |
|
bull3964 posted:Google could have posted the updates if they wanted to. I think the real issue was due to it being LTE and Samsung not being able write a radio baseband to save their life. What Cite please, I had that phone on VZW (my first smart phone and last android phone until the Pixel ships because it liked to brick itself for some reason) and I don't remember that at all
|
# ? Oct 7, 2016 22:47 |
|
My LG G4 just died out of nowhere, which is apparently a thing that happens. I had it for about a year and a half so i'm not heartbroken, but I need to get a phone quickly since my only backup is a nexus 4. I've tried to skim the thread back ten pages or so to see what's hot right now, and I'm having trouble deciding. I'd like to head to a store tomorrow to pick something up (I'm on tmobile but I'd get something unlocked at best buy if need be). Does anyone want to sell me on something that's actually available? A Pixel XL sounds real cool, not available. A Axon 7 sounds pretty good, doesn't seem to be available currently around me. I've never been a huge samsung fan, though i haven't had one since the Galaxy S1. I don't actually do a whole helluva lot with my phone besides listen to music, browse social media, take pictures, watch movies. Not really into gaming or anything.
|
# ? Oct 7, 2016 22:50 |
|
BENGHAZI 2 posted:What It was thicker, used a different battery, used a different SIM size, and had an LTE radio. It was significantly different than the GSM counterpart.
|
# ? Oct 7, 2016 22:54 |
|
Shere posted:I'm thinking I'll just go buy a 5x. A correct think.
|
# ? Oct 7, 2016 22:54 |
|
BENGHAZI 2 posted:What The fact that there was a "Nexus" device that was slow to receive updates and had different hardware was a big deal in the Android threads here at the time.
|
# ? Oct 7, 2016 23:45 |
|
Thermopyle posted:The fact that there was a "Nexus" device that was slow to receive updates and had different hardware was a big deal in the Android threads here at the time. I remember the slow to update part, I just didn't remember the hardware part. Probably because I didn't give a poo poo at the time if I was aware of it
|
# ? Oct 8, 2016 00:32 |
Borrowed Ladder posted:
Why don't you hold onto the N4 for a bit, then? The camera is probably dated, but it should be fine for everything else, and then you can order a Pixelon 7XL or whatever whiz bang phone you'd like.
|
|
# ? Oct 8, 2016 00:40 |
|
Thermopyle posted:The fact that there was a "Nexus" device that was slow to receive updates and had different hardware was a big deal in the Android threads here at the time. Funny how history repeats itself. And yeah, they were physically completely different phones. At least the differences between VZW and the real Pixel phones are just software. Borrowed Ladder posted:My LG G4 just died out of nowhere, which is apparently a thing that happens. I had it for about a year and a half so i'm not heartbroken, but I need to get a phone quickly since my only backup is a nexus 4.
|
# ? Oct 8, 2016 00:53 |
|
BENGHAZI 2 posted:I remember the slow to update part, I just didn't remember the hardware part. Probably because I didn't give a poo poo at the time if I was aware of it Iirc it was before the Nexus line had all radios included. I can't recall if it was because of licensing or what.
|
# ? Oct 8, 2016 00:58 |
|
I could honestly imagine VZW making some poor bastard apply an industrial strength Verizon sticker to each and every Pixel that's going to be sold in store.
|
# ? Oct 8, 2016 01:05 |
|
withoutclass posted:Iirc it was before the Nexus line had all radios included. I can't recall if it was because of licensing or what. LTE was a relatively new thing at the time and Verizon was still mostly CDMA.
|
# ? Oct 8, 2016 01:10 |
|
ilkhan posted:At least the differences between VZW and the real Pixel phones are just software. Even then, it's really just configuration. The only likely difference between the two models is a bootloader that can't be unlocked. That's pretty much it. Even the 'bloatware' that they are talking about is them using Google's own activation hooks to install apps from the play store on SIM activation (something ATT was doing with the N6, going so far as to even change the boot logo.)
|
# ? Oct 8, 2016 01:17 |
|
ilkhan posted:True. We spent a good amount of time laughing at the people who bought it from verizon instead of a GSM version from the play store. No, back then you couldn't use the play store version on Verizon. Well I guess you technically could but you'd be stuck on 3G. The differentiation of hardware included the CDMA modem that allowed for LTE on Verizon. E: vvv Yeah, you're right. Memory served me that this was around the time when they started getting a little less fragmented in that sense but that wasn't until later on. comper fucked around with this message at 03:01 on Oct 8, 2016 |
# ? Oct 8, 2016 02:27 |
|
You couldn't use the play store version on Verizon at all, it didn't have any of the right radios. Hell, there were 5 different variants of the Galaxy Nexus. The Sprint version didn't even have a SIM slot.
|
# ? Oct 8, 2016 02:42 |
|
Can't use use the Play Store on wifi?
|
# ? Oct 8, 2016 02:50 |
|
bull3964 posted:You couldn't use the play store version on Verizon at all, it didn't have any of the right radios. Hahaha, I just remembered something Wi-max
|
# ? Oct 8, 2016 03:01 |
|
Mu Zeta posted:Can't use use the Play Store on wifi? No, he means that the radio bands on the phone from the Play Store were incompatible with Verizon. I think.
|
# ? Oct 8, 2016 03:13 |
|
The Verizon Gnexus was a goddamn disaster. My brother got it, and I was super excited to see it because as a lifelong Verizon
|
# ? Oct 8, 2016 03:15 |
|
RZA Encryption posted:Hahaha, I just remembered something
|
# ? Oct 8, 2016 03:18 |
|
CLAM DOWN posted:No, he means that the radio bands on the phone from the Play Store were incompatible with Verizon. I think. Yes, the play store one only had GSM radios, no CDMA radios and no LTE radios. So it couldn't work under Verizon or Sprint at all. Also, don't forget that the international versions were updated by, I believe, Samsung and not Google. It's was common to reflash them to the Google version. Phones, in general, were a shitshow a few years ago.
|
# ? Oct 8, 2016 03:23 |
|
|
# ? May 25, 2024 21:49 |
|
bull3964 posted:Yes, the play store one only had GSM radios, no CDMA radios and no LTE radios. So it couldn't work under Verizon or Sprint at all.
|
# ? Oct 8, 2016 03:26 |