Yeah, I just meant for explaining the function of what the thing does.
Yeah, I just meant for explaining the function of what the thing does.
It’s basically an analog version of an HDMI cable. Except no audio, only video.
It’s like the yellow RCA cable, but for computer monitors instead of TVs
There’s isn’t enough physical space for three sensors on a smaller phone especially if it’s the size of the iPhone mini
I wouldn’t go as far as to claim that “more cameras” is the complaints being made here. Sure, telephotos make sense as things that take up more space. But most people are using them for like 1 in 50 shots or something. I have an extremely hard time believing that someone would genuinely notice the difference unless they’re an extreme case or they’ve been told the other ones are better. Within reasonable effective focal lengths, these are pretty negligible in the sizes we’re talking about.
If Apple couldn’t make a smaller phone sell particularly well, I doubt anyone else could.
I hard disagree with this. Apple is literally the worst company to try to make this shit work. Apple’s core selling point is the status symbol of it all. People trying to show off having the flashiest phone are not going to buy a product being touted as a half baked smaller and cheaper version of something else. Their entire marketing was about it being mini. Apple customers are not the core audience for something like this, and Apple marketed it as exactly what people disliked about small phones.
around or less than 5% of total iPhone 12 and 13 sales
I find it more surprising that this was below expectations than I do that only 5% of people bought a smaller phone. I doubt much more than 1 in 20 people really is after a smaller phone. I’m sure they exist, but based on the people I know and the number of people I’ve heard interested in smaller phones, I’d estimate it more like 1 in 20 to 1 in 40. It’s not for most people by any means. But 1 in 20 is still a decent number of people.
They have to understand that the cameras on the biggest flagships occupy a lot of space and it isn’t feasible to bring it to a smaller form factor.
Not… Really… Sure it makes some difference, but the much more constraining factor is the money. Cameras arent that big, but they’re one of the priciest pieces of hardware in the device.
The problem is more that they keep trying to sell small phones at cheaper price points. So they end up with much worse screens, socs, and cameras so they perform like shit. People don’t want a small phone because they don’t care about their phone. People want small phones because the standard size is fucking huge. They need to make a high-ish tier small phone instead of low tier small phone that performs like the 50 Walmart shit.
I know it’s not everyones cup of tea but…
I ended up buying a Pixel Fold for the Fold aspect. There’s an added benefit that it’s really short when folded so I can reach the entire screen one handed. It’s heavier and thicker than a slate phone, but I actually enjoy the folded experience way better than other phones.
“Why spend thousands of dollars on paying someone to fix it when we can pay them hundreds to spend an hour writing a dialog box?” - Some storefront owner
It’s probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but… Nope.
There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings.
Fwiw, force stopping your actual launcher should fix the issue without restarting etc but it does come back.
I think I’ve tried doing this on the Pixel launcher with no dice, but going to give that a shot since it shouldn’t hurt. I doubt this would impact the issue if it’s actually based on what you claim though.
I’ve been crazy for months over this lmao. Glad I could help 😜
Lol, honestly, that’s probably fair. My memory basically ends at 95 though and I don’t remember any 3.1 menus well enough to make a call on that distinction.
That’s great and I’m glad that works for you.
But most people buying portable gaming handhelds are not doing that. And the people looking for things like that are likely landing closer to a surface or standard laptop, which Windows already supports well.
What do you mean? You can still open control panel from XP/Vista and basically every option menu still points to the same shit that hasn’t changed since Windows 95. Go open device manager and go to the properties of any device and you get like XP stuff at newest. Event Viewer, Disk Management, and many other high level panels haven’t changed from XP.
90 percent of windows menus are still the same as 2000, even on the consumer side. And they’re not virtually identical, they ARE identical.
I don’t know that Microsoft has any business trying to make Windows support these devices better…
Windows is entirely built around two pillars:
Portable game machines are not an enterprise product. Nor do you care about broad hardware support or upgradability. Nor do you care about plugging in your parallel port printer from 1985. Nor do you care about running your ancient vb6 code to run your production machines over some random firewire card.
Windows’ goal is entirely oppositional to portable gaming devices. It makes almost no sense for them to try to support it, as it’d go against their entire model. For things like these, you want a thin, optimized-over-flexible, purpose built OS that does one thing: play games. Linux is already built to solve this problem way better than Windows.
But, Microsoft will probably be stupid enough to try anyway.
Now we just need that GFX software from intel / amd / nvidia that is available on windows, taking advantage of that newly supported hardware
Stop, you’re making me too hard. I might be able to like, ditch Windows if that happens.
I wish I had a better answer for you… But…
This seems to be some bug in Android 14. I reported it numerous times during the beta program MONTHS ago, and it’s never been fixed. The public release came out and multiple friends have told me they’re having this issue too. It still isn’t fixed.
I don’t know what the fuck Google is doing, but I’ve heard people have this issue with different launchers so I can’t imagine they’ve all got the same bug - this seems to be Google’s fault. The launcher I use has fixed multiple Android 14 bugs, but not this one. I don’t think they can.
Fwiw, you should be able to force stop your launcher which is a little faster than changing launchers and changing back. And it’s a hell of a lot faster than a restart… Pull down notification shade, tap settings, type Kvaesitso in the search bar which should let you tap to get to the app settings, and on that page should be a “force stop” button. Tap that, tap home, and it should be fixed.
I find this shit infuriating and I don’t understand how Google deems this OK. I doubt this gets fixed before Android 15 at this point. Google has their fucking heads up their ass on this one.
I don’t know if it does anything, but there’s an issue about it here: https://issuetracker.google.com/issues/302132145 Commenting/subscribing/etc might help get this more attention.
Exactly this. Amazing engineers can still be run by brain dead management. Turns out being a manager gets you more decision making power though.
TL;DR: Employees say his actions led to a lot of direction changing that forced management to scramble, and the lower workers had to bear the brunt of this. They also complained that OW2 needed more work or would be review bombed on Steam and his leadership refused. Shareholders are still happy to fellate him though because he made them a lot of money.
So, no actual news here.
Yeah, that’s still true as well. But it feels like one step ahead. Before it was in a totally different field. It’s gotten that much worse.
Google Assistant is definitely getting worse and worse all the time. When the Google Homes first released they were actually pretty useful and handy. I was willing to pick a few up and they served a good purpose. They ran CIRCLES around Alexa and all those.
Now many years later, the devices don’t hear questions correctly, have to ask them four different times, they can’t even pick up my wife’s prompt words anymore, don’t even give reasonable answers when they do get the question right… It’s made hundreds of dollars worth of devices infuriating and useless.
I bought a product that worked. It no longer works because it’s been “updated”.
My experience is dated, but figured I’d share it in case no one else has any input.
I owned a few Motorola Android phones before and after the Google involvement. I think my most recent purchase was 2015.
At that time, they were extremely “pure android” with very few additions beyond the stock experience. The things they added were way ahead of their time - I still think those devices had the best “always on” display implementation to this day, and they did it way before it became a norm.
Their software and update support was rivaling Google at the time, and most other manufacturers were still in the days of 2 years of updates if you’re lucky.
They just stopped making phones it seemed like. I ended up moving towards Pixels over the years, but Moto is the one company that would tempt me to switch back. That or maybe HTC but they’re dead.
Hope you get a more recent answer - I didn’t even realize they were still making phones to be honest.