Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
ClassActionFursuit
Mar 15, 2006

RZA Encryption posted:

drat straight. If I don't have full control of my mobile computer then I may as well just have two cans and some string.

I got it all sorted. It's nice now that I have it the way I want it. Hopefully I never have to mess with it again.
I would have to imagine if the carrier gets the opportunity to insert apps into its own partition when it sets up, it would also get that opportunity later on down the line unless they're relying on the Play Store to distribute updates to those apps.

I think that's something we just don't know yet.

Adbot
ADBOT LOVES YOU

ClassActionFursuit
Mar 15, 2006

SymmetryrtemmyS posted:

Has anyone here owned an HTC One Max? I might buy one soon (good deal for a huge phone with good enough specs) and I'm curious if I should avoid it for any reason. I've read the reviews, and I'm fine with the drawbacks (mainly, it's huge), but personal accounts sometimes hash out differently.
Doesn't the Max strip out all the good poo poo in the regular One hoping you won't notice? Like it has lovely instead of good speakers and removes OIS from the camera or something like that?

ClassActionFursuit
Mar 15, 2006

Deep Winter posted:

So, the Galaxy Note Edge on Verizon can only do simultaneous voice and data when you're on their Advanced Calling Voip poo poo. Really sad this wasn't a fringe case with the droid turbo. Guess it's the standard now. Going loving backwards. You like browsing the internet while on the phone? Congrats, now it's only to Verizon customers who still have this obscure feature on their plan and it's turned on in their phone, assuming their phone is compatible, and you're both in a perfect 4glte area. Great.
Well not just Verizon customers in those circumstances as everyone on every other network gets to do that.

ClassActionFursuit
Mar 15, 2006

SwissCM posted:

Manufacturers really have to start shipping phones with at least 16GB of onboard storage nowadays, anything less and it's a hell of a squeeze.
Even that would be pushing it given the bloated size of TouchWiz.

ClassActionFursuit
Mar 15, 2006

Knuc U Kinte posted:

System mem on my Note 4 is like 8 gb lol.
This is a little old (from January 2014) but should be accurate for KitKat:

ClassActionFursuit
Mar 15, 2006

bull3964 posted:

Whelp, I guess it's time to say goodbye to Qi.

http://www.androidcentral.com/two-three-wireless-charging-standard-groups-will-merge-mid-2015


So, the two other wireless charging groups merged and they have Intel, Samsung, AT&T, GM, Starbucks, Duracell, and Powermat. Intel and Samsung now merging with Qi's main competitor pretty much spells the end for Qi in the long run.
The two groups are merging because they're the ones that no one uses. The only thing that's going to define a "winner" is Apple including one and until they do it doesn't matter what happens in the space.

ClassActionFursuit
Mar 15, 2006

Lollipop has been fine on all my current devices. My only complaint has been dumb volume controls.

ClassActionFursuit
Mar 15, 2006

What's going to be great is when all these builds go through OEM and carrier testing and still come out lovely when the rest of us are on 5.1 which will refine Lollipop's rough edges and works just fine, that's when Samsung and the other OEMs will stop releasing updates and they'll all be stuck on broken builds forever.

Welp, guess it's time to give Samsung more money, and the cycle will begin again.

ClassActionFursuit
Mar 15, 2006

bull3964 posted:

Yes, hilarious. Serves those OEMs right for trying to update their devices in a timely manner.
Which is what The Merkinman was saying: Google is damned if they do, damned if they don't. OEMs are in the exact same boat, that boat is just six months behind Google's boat.

At the end of the day everyone is stuck with whatever decisions Google makes regarding Android. If they have a buggy release, those regressions and bugs come along with the OEM versions as well giving the OEMs three options, either to fix the bugs themselves delaying the release of software further, release their skinned version on top of the buggy release without fixing them, or not release the update at all and sit on their hands waiting for Google to fix their code.

Option one is labor-intensive for little benefit as Google will be fixing the software anyway and they'll have to be sure to properly adapt to the "proper" fixes once they're merged (like HTC's Bluetooth implementation back in the Froyo/Gingerbread days). This is probably more trouble than it's worth plus with OEMs working closely with Google on future releases it would seem to me this option should be able to be discarded in its entirety now but before was the way it was done.

Option two isn't great for the user at all and if the bugs are bad enough that the devices fail carrier testing then probably not feasible to even do.

So that really only leaves option three. With the cooperation speeding up OEM skinning efforts, this is likely the course things will run going forward with the Google-written fixes being incorporated as they build their updates. But that also means that moving to the next version is back to where it was before, which is so late that by the time they finish their build and it moves through carrier testing Google will be ready to release the next version.

That means that by the time that next version of Android is ready OEMs will still be in a position where they can't allocate resources toward updating older models while simultaneously working on their forthcoming ones. That, of course, leads to exactly what I said in the post you quoted.

ClassActionFursuit
Mar 15, 2006

Lblitzer posted:

Samsung announced the Note 2 (which is almost 2.5 years old albeit a flagship) is getting Lollipop. Say what you will about "timely updates" but the game is a lot different now than even just a year ago. Everybody is starting to get their head in the game on being close with updates. Lollipop has only been available for 2 months (not including developer preview) so we are just in the infancy of Android's largest update with some pretty major bugs on Google's own device.
2 months is 33% of the time it will be the current version.

eta: Also I'm not saying it's not way better than it used to be. It used to be a device launched at least a version behind, maybe two, and got maybe one update ever at which point it was three or maybe four versions behind. Now you're looking at probably only being one version out of date for most of the time you own the device which is a substantial improvement but let's not pretend it's equivalent to being up to date.

ClassActionFursuit fucked around with this message at 15:59 on Jan 7, 2015

ClassActionFursuit
Mar 15, 2006

bull3964 posted:

Android is not on a 6 month major release schedule.

It also means diddly squat if the current version is unusable (and by unusable, I mean a clear regression from the previous version.) Most would rather have a working device for those 2 months and be behind than have the latest version and hate their device because of it.
I have five devices on the latest version of Android, all working perfectly. The 2013 Nexus 7 in particular runs much, much better than it ever did on KitKat. :shrug:

bull3964 posted:

2 months is how long I've had my Nexus 9 and this is the first electronics purchase in a long time that I have regret about. If I could push a button and undo my purchase, going back to a N7 2013 with 4.4.4 on it, I would break my finger jabbing it so hard.
An Nvidia SoC with a really, really horrible architecture should've been a red flag to at least wait and see. I can't really speak to it since I don't have one but it's not like the Exynos Nexus 10 fared much better throughout equivalent software releases compared to Qualcomm SoCs.

bull3964 posted:

Google hosed up big time this round and they need to examine where things went so wrong. The solution isn't anything you listed. The solution is Google making sure their OS is ready to be released before pushing it out.
Isn't this exactly what I said:

LastInLine posted:

At the end of the day everyone is stuck with whatever decisions Google makes regarding Android.
Yes. Yes it was.

bull3964 posted:

This isn't an OEM issue at all at this point in time. It's an issue with Google continually treating everything like beta, hoping people won't stumble upon their problems before they have a chance to patch them. This one is one of the more egregious in memory, but nearly every single major release by Google has been marred in some way with a serious bug and some of them remain unresolved (i.e. bluetooth being poo poo) despite constant and continual feedback. What good is a quick iterative cycle if you don't actually respond quickly to issues other than pissing off your partners?
I didn't say it was OEM issue, I said OEMs will lag behind and either drop support or release progressively shittier updates, which they will.

What was wrong with the 2.3 > 4.0 release? Nothing that I remember. In fact the only Nexus device to get update, the Nexus S, only ever worked properly on that release. Considering that's the only major update that's happened I'd say their track record of 1 for 1 is pretty good but I guess they could try batting over 1.000. If the ICS update broke any OEM devices that is 100% on the OEM.

As for the quick iterative cycle, it seems to be doing just nicely. 5.0.2 fixed the 2012 Nexus 7 issues and all the other devices I've got access to (Nexus 4, 5, 6, 7, and Moto G) all seem to be doing a-okay on 5.0.1. If there are memory problems then they've got that marked as fixed too. What exactly would you prefer Google to do? Release another bugfix release right this second? They've already said that even these Nexus bugfix releases are being delayed by carrier testing so you kind of want to push through everything you can before you submit. OEMs already have access to those bugfixes as well. I'm not sure what more they could do that they aren't already doing except your claim that they should stop treating everything like a beta and only release perfect software. Given that perfect software doesn't exist and Google is not going to give up a rapid release cycle you might as well wish for unicorns offering blowjobs while you're at it.

Lastly I've never had a Bluetooth issue since they dropped BlueZ. Maybe I'm lucky.

ClassActionFursuit fucked around with this message at 16:43 on Jan 7, 2015

ClassActionFursuit
Mar 15, 2006

bull3964 posted:

My experience with 4.0 is with the Galaxy Nexus and it was not a good one. Granted, some of them were actual device issues, but it still points to Google releasing something they probably shouldn't have.

Lollipop on my N7 2013 killed its performance. It ran perfectly on 4.4.4, but Lollipop was a dog with constant home screen redraws and non-responsive home button that you had to jab 3 times before it registered.

I've given up on trying to use bluetooth to stream audio while streaming videos over wifi. The instant the audio starts I can visibly SEE the wifi indicator start fluctuating in strength and it's not long before the buffering starts. That's even on a 5ghz network so it's not like it's RF interference. Not that it would be very useful even if it did work since the lip sync is off so much I feel like I'm watching a badly dubbed korean movie. This has been a constant across 4 nexus tablets ever since they changed bluetooth stacks.

Honestly though, in general, the most stable responsive devices I've ever owned have always been Motorola. OG Droid, Droid Bionic, Droid Razr, Droid Razr HD MAXX, Droid MAXX, and now Droid Turbo. They've all had uptimes measured in months with no random reboots (dear god the N10 was bad for that for awhile) with no random slowdowns or other screwiness.

If Moto would release a 7-9" tablet tomorrow with a high resolution screen and wireless charging I would drop the N9 in a hot minute.
I don't really remember any problems with my GSM Galaxy Nexus on 4.0 but that was a long time ago and I know the Verizon one was a totally different beast.

I'll admit also to never using wifi and Bluetooth together so I don't doubt your issues there either. Is there at least a bug to star for that? Edit: Yes. My Bluetooth use is headset and car audio and for that I can't say anything bad about the current stack at all. It's been so much more reliable than the old stack that it's night and day. If there's a Google trait I believe in it's that they break one thing while fixing another. :(

I'll agree with you on Motorola too. They make the best radios and best devices hands down, though you've got a lot more access to them with Verizon. I would also buy a Moto (Nexus) tablet and the last two devices I've had people buy when they asked for a recommendation have been Motos.

Given the situation with the N9 though you might want to see if you can get rid of it and pick up the *shudder* Samsung tablet. I really think the N9 is going to be another Xoom.

ClassActionFursuit fucked around with this message at 17:20 on Jan 7, 2015

ClassActionFursuit
Mar 15, 2006

kitten smoothie posted:

After seeing how the Verizon Galaxy Nexus played out, I really wonder what would've happened had they actually shipped a Verizon Nexus One as planned rather than canceling it and just saying "go buy the Incredible instead."

Google probably would've thrown up their hands and EOL'd it at Froyo.
Maybe or maybe not. The Nexus One was such a solid device on all software versions that it probably wouldn't have suffered the myriad problems with carrier testing the Galaxy Nexus did. All the speculation was that the GN problems were radio-related and we all know how spectacularly lovely that separate LTE chip was for the radio.

The Nexus One on the other hand was just perfect all the time.

ClassActionFursuit
Mar 15, 2006

bull3964 posted:

One thing to remember about Verizon though with android. The effect the OG Droid had on Android cannot be understated. It put Android on the map as well as setting new standards in hardware specs.
A shame Motorola pissed all that goodwill away by letting the carrier define the branding which allowed Samsung to swoop in with the radical idea of "selling the same phone on different carriers with the same name". I know it was de rigueur at the time to allow the carrier to name the phone but if, of all hapless entities, Samsung could figure out how to let the carriers do that AND tell the customer the name of the device surely Motorola could've done it.

BoyBlunder posted:

How are people grabbing their Nexus 6's? Play store says that they update inventory on Wednesday, but I haven't seen anything yet today. I'm looking to snag a 64GB Blue.
My wife went through Motorola but they don't tell you when they're going to have some, you just have to be ready.

ClassActionFursuit
Mar 15, 2006

RZA Encryption posted:

My bank's app isn't compatible with my Nexus 6. =(
Neither is my wife's credit union app.

robodex posted:

What are you guys doing on your phones to not have any memory issues with Lollipop? :psyduck:
Nothing I didn't do before. It's running for me as good or better than it was under KitKat. :shrug: I haven't restarted since the day 5.0.1 came out.

ClassActionFursuit
Mar 15, 2006

The only thing I can say is that my battery drain both idle and in use seems much faster under Lollipop. I don't gently caress around my phone that much and I don't usually skip from app to app to app so maybe my routine of Something, Hangouts, and Chrome just doesn't trigger it.

I just don't know, man.

ClassActionFursuit
Mar 15, 2006

Thermopyle posted:

Which is why it was not appropriate for Google to update the 2012. They took a perfectly fine device and made it objectively worse.

Of course if they hadn't, people would have complained about not updating it, but Google should have just dealt with it.
To be fair, they've done that before with the Nexus S Jelly Bean update. Man did that kill that device.

ClassActionFursuit
Mar 15, 2006

monster on a stick posted:

Question on Location and battery life.

Turning off Location increases battery life of course. But when turned on, there are three settings (at least on my phone):
- Low which uses GPS only
- Medium which uses GPS and WiFi
- High which uses GPS, WiFi, and cell (presumably doing triangulation based off of the cell towers picked up by the phone)

Each of these settings is sold as increasing the quality (low->high), but does it impact battery life if enabled? Like, I'd think that using High would help decrease battery usage since triangulation should theoretically be sufficient and GPS sucks battery life.
It's just a matter of how precise you want your data to be. It's not like disabling WiFi and cell location disables the radios so there's no impact to battery life choosing one over the other.

For what it's worth I leave everything on all the time and have no complaints but I don't have things like Facebook requesting location data constantly.

ClassActionFursuit
Mar 15, 2006

ThermoPhysical posted:

Lollipop his hilariously broken on the Nexus 4. I just noticed that I can't make ANY calls out at all. Not via Voice or via my carrier number.

Glad I figured this out when I was just trying to call work and not something super super important. :v:

Anyone else here having this issue?

https://productforums.google.com/forum/#!topic/nexus/j74JlShhihc

Google has it on low priority in AOSP and someone claims it's on the Nexus 6 as well.
I know a few people with 4s and one with a 6 and never heard about it either. I'm guessing you've reflashed the stock ROM.

ClassActionFursuit
Mar 15, 2006

Pyroxene Stigma posted:

This is usually in developer options if I recall.
You're thinking of "Screen on while charging" which means the screen never goes off and the phone doesn't go sleep. There's no way to fiddle with how and when it comes on.

ClassActionFursuit
Mar 15, 2006

Klowns posted:

I know the Galaxy S5 Active doesn't really need a case but it'd be nice if more people made ones that would fit it. I have an extra button here.
This might be a stupid question but if you were always going to be putting it in a case why wouldn't you just opt for the Galaxy S5 which is water resistant and that you know has cases available?

ClassActionFursuit
Mar 15, 2006

SIR FAT JONY IVES posted:

Please link this app. If it's not from the chip manufacture directly then I'd be concerned.
He linked it below but yes, Qualcomm made a Greenify-esque app for Snapdragon SoC phones.

ClassActionFursuit
Mar 15, 2006

Daily Forecast posted:

I went with the Note 4 instead of a Nexus 6 because if I'm spending that much on a loving phone I better be able to replace the battery and expand the storage. What the gently caress even, Google, nobody wants your cloud bullshit
Are we going back to buying physical media and having landlines, too? Manually tagging and managing music? Syncing with a wire like a bitch?

I think I'll stick with :yaycloud: thanks.

ClassActionFursuit
Mar 15, 2006

Daily Forecast posted:

If you seriously can't think of more than 32GB (actually even less because of the OS) of stuff to keep on your phone then what are you even doing with a phone
My Nexus 5 has 32GB of storage, so 24GB after the OS. Right now I have 2GB of storage in use that isn't caches or app data.

What am I even doing? Living in America in 2015 where wifi and LTE coverage is ubiquitous and cheap.

ClassActionFursuit
Mar 15, 2006

Daily Forecast posted:

That is exactly what I am saying. Why would you buy a phone with worse/no features for the same amount of money? The only compelling thing there ever was about Nexus phones was the mid-high level hardware for a cheap price, but $700 for a Nexus 6 is pointless when you can get a much better phone for that much.
I'd say the people who buy Nexus devices also value the software.

I'd rather use have a flip phone than a TouchWiz device.

ClassActionFursuit
Mar 15, 2006

CLAM DOWN posted:

I've heard of this before, never experienced it myself, but could it be historical data usage for an app you've uninstalled recently?
That's exactly what it is.

r0ck0 posted:

I just got an update to the google now launcher via the play store on my Nexus 5 running 5.0.1. Do you think they will be able to fix the memory leak with a google play update? I hear they can push almost any type of system change via google play. Confirm/deny
Deny.

ClassActionFursuit
Mar 15, 2006

Variable_H posted:

Lol if you think that size is the only thing Samsung has going against it.
You're crazy and your frothing rage was uncalled for. I mean it's not like the entire UI looks to have been designed by a colorblind mentally disabled child or anything. Now excuse me while I go back to my blue and yellow messaging app.

ClassActionFursuit
Mar 15, 2006

Desk Lamp posted:

The messaging app can be whatever color you want it to be.
User choice is the crutch of the artless.

ClassActionFursuit
Mar 15, 2006

5436 posted:

So is being able to say 'shoot' or 'smile' and the phone will take a pic when the camera is open.
An odd choice given that "smile" is what you say before the photo is ready to be captured to prepare people for it. There isn't a single worse choice of command to take a photo except maybe "cheese".

My frothing rage leads me to point out this is exactly a case of a half thought-out UI choice where there's a good idea done in a bad way.

ClassActionFursuit
Mar 15, 2006

baka kaba posted:

Does it do smile detection though? I mean that's a thing
Thank god American Gothic is a painting and not a picture or we'd still be waiting.

ClassActionFursuit
Mar 15, 2006

5436 posted:

You say the word, it waits a second, then takes the picture. Its good for placing the phone somewhere and taking a pic, I do this with my niece sometimes cause she always wants to gently caress with the phone if I'm using it. Also just easier than hitting the shutter button.
I'm not disputing the utility of a spoken command for the shutter, I'm questioning the reasoning behind choosing that one.

ClassActionFursuit
Mar 15, 2006

DangerZoneDelux posted:

One of the cool new features on my Nexus 6 is when it doesn't load a chrome page until I back out and try again. Happens 50% of the time. Kind of neat!
That went away for me in Lollipop versus KitKat. By the way you don't have to back out, open a new tab and close it. It will only occur when on the first tab in Chrome so alternatively you can just leave a tab open and it will never happen.

ClassActionFursuit
Mar 15, 2006

Bob A Feet posted:

Literally happens all the time on my turbo, but only when I launch something from google now, ie I voice search something or search from the home screen search bar. Absolutely 100% of the time refuses to load until I close chrome and reopen.
Did you try opening and closing a tab (I can't remember if that second tab actually loads the view or not)? I lived with it for a long while, I'm certain I have the steps right to make it work.

What's weird is that it obviously loads the page. The bar goes across but the webview remains blank. Opening and closing a tab always caused the loaded tab to display immediately without a reload. I'd always keep a tab open to Google just to prevent it and it always did until I accidentally swiped it away.

I have no idea why it went away for me in Lollipop but I haven't seen it since. :shrug:

Edit: One thing I just thought of: In Lollipop I disabled the "show tabs in app switcher" option. Try that if you haven't. Given that it started about the time they were making background changes to Chrome to accommodate that and that it obviously affects the tab switching which would fix the problem I could see that fixing it.

ClassActionFursuit fucked around with this message at 19:36 on Jan 14, 2015

ClassActionFursuit
Mar 15, 2006

Straker posted:

Have you never said the word "cheese"? People use it because it forces you to smile even as you're saying it... not that it will look good if you don't catch on and make it more natural, but you know, it's actually a really good word.
This is only true if you're the only one in the picture. Otherwise saying "cheese" or "smile" is a cue for the other people in the frame to get ready. It's almost like I'm talking to people without friends or fami... ooohhhh.

Desk Lamp posted:

It works just the way you'd expect it to, it just doesn't fit his narrative. This is the same poster who "proved" Samsung's customer satisfaction was poo poo by linking a study that said it was second only to Apple's, that should tell you all you need to know.
It does, it tells me that confirmation bias is a thing that definitely exists.
I'll be honest, it's incredibly difficult to take any of this seriously. Maybe you've got a point and maybe you don't but I just can't get past fearing the cloud and my brain just tunes it out like I would someone talking about FEMA death camps.

ClassActionFursuit fucked around with this message at 07:36 on Jan 15, 2015

ClassActionFursuit
Mar 15, 2006

Daily Forecast posted:

What would you say if Microsoft released a new version of Windows that wouldn't allow you to install any hard drives of your own in your PC, but that's okay because you can just use their *cloud servers* to store all of your information? Is that the future? gently caress that.
When I need a fresh install of OS X, it's literally downloaded from the cloud by the computer with all updates installed prior to first boot.

I also have a Chromebook (because the alternative was a Windows laptop, lol) and that OS is completely in the cloud.

Can you imagine using an operating system in 2015 that comes on physical media? :lol: Edit: I don't even have a computer capable of reading optical media.

ClassActionFursuit fucked around with this message at 09:54 on Jan 15, 2015

ClassActionFursuit
Mar 15, 2006

Tunga posted:

Personally I wish I could toggle the removable battery-powered SD card slot on/off with a capacitive button below my physical keyboard.

Edit: And the headphone port would be on the side.
I was laughing along with you until the edit, you... you MONSTER!

ClassActionFursuit
Mar 15, 2006

Reverse Centaur posted:

We already have a good idea what it looks like

https://www.youtube.com/watch?v=G2DW6YKhLxY

Honestly that video is what made me go with the N6. It's better but still ugly.
Two clocks is the default? Really?

ClassActionFursuit
Mar 15, 2006

Vykk.Draygo posted:

Are two clocks not still the default on every Android device? Does GNL not default with a clock widget?

Also, is the Note 4 only sold with that disgusting fake leather back?
The last version with a default clock widget was Donut, 1.6. Eclair, Froyo, and Gingerbread had nothing at all on the default homescreen, and Honeycomb up through to Lollipop has the Google search bar at the top. Once folders were added it became the default to have a folder of Google apps right above the dock.

The thing that's so weird isn't putting a clock widget on the default homescreen, it's that OEMs who do it (just Samsung and LG as far as I know) are also creating a launcher and could easily make it so the clock in the statusbar doesn't show when a clock widget is used. Like, that's an option they could exercise and don't.

ClassActionFursuit fucked around with this message at 15:10 on Jan 16, 2015

ClassActionFursuit
Mar 15, 2006

RVProfootballer posted:

That isn't true, Galaxy Nexus and Nexus 4 both had a clock widget by default. Not the big numbers one, but the clock face widget. I'm pretty sure they did, anyway.
I was almost certain I was right that booted up to the yellow image they used promotional materials but you know what, you're right. The N4 had that bluish wallpaper with the analog clock and the Galaxy Nexus had that diffused spectrum wallpaper with the analog clock.

I'm nearly certain the N5 had no clock.

Thinking on the Eclair/Froyo/Gingerbread days they might've had the search widget up at the top by default but I don't have a device from that era to check. I think they may have had the onboarding Android Tips widget at the bottom over the dock as well but that may have been on the right homescreen which would leave room for an analog clock under the search widget. Maybe not though because a part of me has a strong memory of watching that Nexus One live wallpaper with the moving colors on an obstructed background.

Google definitely always used analog clocks when they did put them on there.

Adbot
ADBOT LOVES YOU

ClassActionFursuit
Mar 15, 2006

Straker posted:

Are you loving joking?

photographer: say cheese

group: *says cheese, smiles whether they want to or not*

LastInLine: :saddowns:
This is literally what happens any time you're around old people, like exactly.

"Oh! Are we taking a picture?" *Starts shifting position in order to capture their "good side"*

"WHERE'S THE CAMERA?"

"That is a camera, Grandma..."

"IT LOOKS LIKE A PHONE..."

On and on for what seems like an eternity. Maybe it's just my family but the delay after saying that codeword better be ten minutes.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply