|
Endless Mike posted:I'm sure Galaxy S5's and Nexus 5's got the update, and that's all that really matters. That's the thing, the Moto X 2014 was a goddamn Google flagship. It's like they're trying to disavow it. I tried to get right, no root, locked bootloader, but apparently I never can be. gently caress it; I'm getting an iPhone; at least they keep their poo poo up to date. Wake me up if ChromeOS with extensions ever shows up on phones.
|
# ? Jul 11, 2016 21:55 |
|
|
# ? May 23, 2024 17:34 |
|
Sir Unimaginative posted:So I deserve to have my phone abandoned by Google Play entirely because some dipshit at Google forgot to add a phone from 2014 to their whitelist. Also if you're so adamant about this and want to stay philosophically consistent you should probably start up a campaign to criminalize sideloading, although I doubt even you want to see what's down that road. "anything" = phone malware. Apologies if you took it otherwise. Tell me you at least compare the checksum to the play store version.
|
# ? Jul 11, 2016 21:55 |
|
RZA Encryption posted:"anything" = phone malware. Apologies if you took it otherwise. Both manually and automatically (the Play Store version being there first). I know I'm a fool but I'd like to think I'm not an idiot.
|
# ? Jul 11, 2016 21:59 |
|
Sir Unimaginative posted:That's the thing, the Moto X 2014 was a goddamn Google flagship. It's like they're trying to disavow it. I tried to get right, no root, locked bootloader, but apparently I never can be. Moto X 2014 is not a Google device by any stretch of the imagination. edit: It shipped with goddamn Kitkat, by the way.
|
# ? Jul 11, 2016 22:00 |
|
nimper posted:Moto X 2014 is not a Google device by any stretch of the imagination. Not sure how what it shipped with is relevant, the iPhone 5 launched in 2012 and hasn't been manufactured since 2013 and is capable of running the latest iOS.
|
# ? Jul 11, 2016 22:13 |
|
nimper posted:Moto X 2014 is not a Google device by any stretch of the imagination. Google still owned them while it was being developed and it doesn't much matter how it started life; if Android is supposed to mean anything, official/stock firmware needs to be treated like it's still part of the Android ecosystem until it's no longer feasible to support (and feasible is a Big Word given that it's Marshmallow now and there's still supported Jellybean devices in 2016).
|
# ? Jul 11, 2016 22:15 |
|
uPen posted:Not sure how what it shipped with is relevant, the iPhone 5 launched in 2012 and hasn't been manufactured since 2013 and is capable of running the latest iOS. My point there was it's actually been pretty well supported compared with other android phones from 2014. The carrier unlocked version has Android 6.0 available (albeit with no security updates since November). Sir Unimaginative posted:Google still owned them while it was being developed and it doesn't much matter how it started life; if Android is supposed to mean anything, official/stock firmware needs to be treated like it's still part of the Android ecosystem until it's no longer feasible to support (and feasible is a Big Word given that it's Marshmallow now and there's still supported Jellybean devices in 2016). Google doesn't own Motorola now and bitching about stock firmware is not going to help since the X 2014 doesn't run stock Android to begin with. Sure it's near-stock but there are still OEM modifications.
|
# ? Jul 11, 2016 22:18 |
|
Sir Unimaginative posted:That's the thing, the Moto X 2014 was a goddamn Google flagship. Odd, I thought the Nexus line was Google's flagship.
|
# ? Jul 11, 2016 22:28 |
|
Sir Unimaginative posted:Google still owned them while it was being developed and it doesn't much matter how it started life; if Android is supposed to mean anything, official/stock firmware needs to be treated like it's still part of the Android ecosystem until it's no longer feasible to support (and feasible is a Big Word given that it's Marshmallow now and there's still supported Jellybean devices in 2016). I'm not sure how I feel about this whole argument, but I do know that I don't think it really matters if Google owned them. That's kind of incidental and most people didn't ever even know that. I think nerdy people who did know this information were hoping it meant Nexus-like support, but I don't really think there was any real firm reasons to believe that.
|
# ? Jul 11, 2016 22:28 |
|
Look, if you don't get a Nexus branded headset, don't expect updates. It's that simple. That being said, I understand the pain of not getting updates on a promising phone. It blows. Buy a Nexus or an iPhone and enjoy your updates.
|
# ? Jul 11, 2016 22:44 |
|
Maybe. I'd have to go look back and see if Nexus was still treated as a developer platform or whether Google had finally acknowledged them as The One True Google Phone Accept No Substitutes yet. Still, for a time they had their name on Motorola; of course people were hoping that Google adopting Motorola meant Google would actually take responsibility for their support. Clearly that was misguided, but were they actually bad/wrong/sickbrains for having thought that? ^ ^ ^ Believe me; I've learned that lesson and I've been telling anyone else sniffing around Android exactly that. Just seems like things are getting worse if anything. nimper posted:My point there was it's actually been pretty well supported compared with other android phones from 2014. The carrier unlocked version has Android 6.0 available (albeit with no security updates since November). This is all stuff you put out to support a point, not a point in and of itself. By the way, what is your point? It feels like trying to use an Android phone in the spirit in which carriers and OEMs and everyone else expects a consumer to do so is like being the only party in a bargain holding up their end. Really it's just part of a bigger problem: bad stuff still makes it to the Play Store and the ad circulation, and OEMs abuse the Android name, and Google catches all the flak for it and thanks to existing contracts, licenses and regulations probably can't get out from under it; I can't really blame them either because if I had to live with that as a legacy I'd probably stop putting in even 80% supporting it, let alone 110. It's just profoundly frustrating being on the receiving end.
|
# ? Jul 11, 2016 22:45 |
|
LastInLine posted:Odd, I thought the Nexus line was Google's flagship. Oh come on, you know Motorola Mobility was owned by Google at the time. Don't be a pedant.
|
# ? Jul 11, 2016 22:50 |
|
Sir Unimaginative posted:By the way, what is your point? Maybe I don't have one, but I'm not the one expecting Google to update my not-stock-Android Motorola phone. I can certainly sympathize with you since I own the exact same device but I wrote off the possibility of updates a while ago. Now, sure, this is a symptom of the overall problem with Android and Android phones, but you should at least know what to expect.
|
# ? Jul 11, 2016 22:50 |
|
Sir Unimaginative posted:Still, for a time they had their name on Motorola; of course people were hoping that Google adopting Motorola meant Google would actually take responsibility for their support. Clearly that was misguided, but were they actually bad/wrong/sickbrains for having thought that? To hope that Google owning Motorola mean Nexus-like levels of support is a pretty reasonable thing to hope. To expect it is typical nerd stuff, but not actually a reasonable thing...at least in the context of typical Android updates. We actually should expect Nexus-like levels of support from everyone, but lol at that.
|
# ? Jul 11, 2016 22:53 |
|
Pyroxene Stigma posted:Oh come on, you know Motorola Mobility was owned by Google at the time. Don't be a pedant. It's not a pedantic point, it's a pretty accurate point. Motorola phones were never Google's flagship phones in any meaningful sense of the word.
|
# ? Jul 11, 2016 22:54 |
|
Zorilla posted:Buying a dead Nexus 5 with an intact screen and swapping the main boards might be even easier. The Nexus 5 and 5X are pretty easy to disassemble, especially since there isn't much adhesive to deal with. I'd probably go that route since the dropped phone probably acquired some scuffs when dropped. Well, the replacement screen is also the surround, so a new screen is everything but the back (externally).
|
# ? Jul 11, 2016 23:00 |
|
Weird, have had nothing but good battery life off my Nexus 6p, but something happened today to drive it crazy. The battery is draining faster than usb slow charge can charge it. The only thing I was running was Awful App, Chrome, and Gmail. Have rebooted it to hopefully fix whatever death cycle was going on there, anyone else run into something similar?
|
# ? Jul 11, 2016 23:05 |
|
OnePlus rolled out an update for the OP3 that fixed the RAM management, added sRGB mode for nerds, and improved GPS for Pokemon GO players. Security level is June 2016.
|
# ? Jul 11, 2016 23:05 |
|
Scaramouche posted:Weird, have had nothing but good battery life off my Nexus 6p, but something happened today to drive it crazy. The battery is draining faster than usb slow charge can charge it. The only thing I was running was Awful App, Chrome, and Gmail. Have rebooted it to hopefully fix whatever death cycle was going on there, anyone else run into something similar? I bet you're getting nailed by that loving google backup bug. https://code.google.com/p/android/issues/detail?id=207700
|
# ? Jul 11, 2016 23:07 |
|
Blitter posted:Well, the replacement screen is also the surround, so a new screen is everything but the back (externally). Oh ok, I mistakenly assumed the part you linked was just the LCD, glass, and digitizer like it is with most phone parts. Without the frame, the repair would involve picking out millions of pieces of broken glass, praying you didn't miss any, and getting one shot to stick the new screen to the old frame and align everything perfectly. I see that most sellers in the U.S. on eBay aren't including the frame, but it still looks like a quite a few of them do for $30-40.
|
# ? Jul 11, 2016 23:09 |
|
Pokemon GO runs like poo poo on my Moto G 2014
|
# ? Jul 11, 2016 23:13 |
|
How do you get "ok google send text to blah blah blah" to send via your google voice number that you have tied in to hangouts? I use my Google Voice number for everything, I don't use my carrier number at all. When I get an SMS it comes in via Hangouts. When I send an SMS I do it via Hangouts. All that works. The problem is sending texts via voice command. I would have sworn I had this working on my old Moto X, but I can't seem to do anything to make it work. The text gets sent with my carrier number.
|
# ? Jul 11, 2016 23:17 |
|
namaste faggots posted:I bet you're getting nailed by that loving google backup bug. Huh, I don't seem to have any wakelock issues, but it did get me digging into the power usage profile, and something called system (mediaserver) has consumed 2h38m of cpu time since this morning, for 529mAh. The weird thing is, I never use it; my media volume is always off because I never use youtube, music players, etc. Looking around it seems a pretty common problem, but more linked to people who have cyanogen and other mods. I think the reboot kicked some cruft loose, because now slow charge is actually causing the battery to go up instead of steadily down.
|
# ? Jul 11, 2016 23:21 |
|
teagone posted:Pokemon GO runs like poo poo on my Moto G 2014 It runs like poo poo on all of the phones, they still haven't resolved their server issues.
|
# ? Jul 12, 2016 00:28 |
|
Pyroxene Stigma posted:It runs like poo poo on all of the phones, they still haven't resolved their server issues. It's because every man child that has no business playing it is playing it
|
# ? Jul 12, 2016 00:40 |
|
Pyroxene Stigma posted:Oh come on, you know Motorola Mobility was owned by Google at the time. Don't be a pedant. You mean in that situation where Google promised there'd be "a firewall between Motorola and Android development"? They were explicitly clear from the outset that they were buying Motorola for the patents and had no interest in being an OEM and even though they'd acquired an OEM in this process they would not be doing anything to make that OEM special. They were also explicitly clear that they wouldn't be hosting images for the phones in the way they did Nexus devices. Anyone who was aware of Google's ownership of Motorola had no reason to not understand the terms of it.
|
# ? Jul 12, 2016 02:05 |
|
Thermopyle posted:How do you get "ok google send text to blah blah blah" to send via your google voice number that you have tied in to hangouts? Unfortunately there has never been a way to do it. "Send a text" sends it through the messenger app, and "send a hangout" only works for people with hangouts. It's very annoying, especially when I forget and accidentally send someone a text from my number that nobody knows.
|
# ? Jul 12, 2016 02:26 |
|
So uh, I woke up to my phone this morning looking like this: dropped it last night and then used it for half an hour afterwards but I'm guessing the lcd is leaking and it's totally hosed? Too bad I'm not close to the 2 year window ending.
|
# ? Jul 12, 2016 13:45 |
|
mastershakeman posted:So uh, I woke up to my phone this morning looking like this: Looks broke.
|
# ? Jul 12, 2016 13:51 |
|
FAUXTON posted:Looks broke. Think there's any chance it's a defect I can get a replacement for free, or just suck it up?
|
# ? Jul 12, 2016 14:02 |
|
mastershakeman posted:Think there's any chance it's a defect I can get a replacement for free, or just suck it up? You dropped it, that's probably what they'll cite as "gently caress you, pay me" rationale.
|
# ? Jul 12, 2016 14:14 |
|
mastershakeman posted:Think there's any chance it's a defect I can get a replacement for free, or just suck it up? When the Turbo was first released they included one free screen repair. (That is a Turbo right?) If you bought it from Verizon it is worth checking at least.
|
# ? Jul 12, 2016 14:21 |
|
Bandire posted:When the Turbo was first released they included one free screen repair. (That is a Turbo right?) If you bought it from Verizon it is worth checking at least. Yeah, it looks like one. Give it a shot at least. I've heard they don't honor it if you have one that was only sold at Best Buy or something though. Like mine.
|
# ? Jul 12, 2016 14:36 |
|
Bandire posted:When the Turbo was first released they included one free screen repair. (That is a Turbo right?) If you bought it from Verizon it is worth checking at least. ^ This. I actually redeemed it and it was a pretty straightforward policy; I'm not sure why it existed, but Verizon will replace the screen on the Turbo if it breaks, even if it's accidental.
|
# ? Jul 12, 2016 14:36 |
|
Mogomra posted:Yeah, it looks like one. Give it a shot at least. Yea mines from best buy as well. It's a weird thing to have happen, I've never heard of a lcd doing this
|
# ? Jul 12, 2016 14:43 |
|
Vykk.Draygo posted:Unfortunately there has never been a way to do it. "Send a text" sends it through the messenger app, and "send a hangout" only works for people with hangouts. It's very annoying, especially when I forget and accidentally send someone a text from my number that nobody knows. Well poo poo I must be hallucinating, and yes it's very irritating for the reason you mentioned. Of course, it's also typical google.
|
# ? Jul 12, 2016 14:45 |
|
mastershakeman posted:Yea mines from best buy as well. It's a weird thing to have happen, I've never heard of a lcd doing this Out of curiosity, did you get the blue ballistic nylon that was only available from Best Buy? Or did you get one that you theoretically could have gotten from a VZW store? I feel like the latter might have better odds. Either way, it's at least worth a shot. For what it's worth, that's the first time I've seen a phone's screen do that, but I can count the times I've dropped all of my phones combined on one hand.
|
# ? Jul 12, 2016 14:55 |
|
The world governments need to unite and legislate for all smartphones to receive software and security updates for 10 years
|
# ? Jul 12, 2016 15:47 |
|
WattsvilleBlues posted:The world governments need to unite and legislate for all smartphones to receive software and security updates for 10 years Good god, that covers every model of Android and iPhone. There would only be one update every 10 years given all the snowflake poo poo that would entail.
|
# ? Jul 12, 2016 16:18 |
|
|
# ? May 23, 2024 17:34 |
|
I think the term of support is much less important than the frequency. It's worse long term if a phone receives updates for three years, but only updates once a year rather than receiving monthly (both security and version level) updates for two years. The latter would do a lot to clean up the so called fragmentation and improve user experience. It also may help the former since an already updated device is easier to keep updated.
|
# ? Jul 12, 2016 16:18 |