nexus 5x手机刷go_五岁手机的使用寿命:Nexus 5的实验

2023-11-01 12:59

本文主要是介绍nexus 5x手机刷go_五岁手机的使用寿命:Nexus 5的实验,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

nexus 5x手机刷go

nexus 5x手机刷go

The Nexus 5 is my favorite Android phone of all time. I wanted to see what it would be like to use it in 2018, nearly five years after the phone was originally released. Here’s how it went.

Nexus 5是我一直以来最喜欢的Android手机。 我想看看在手机最初发布近五年后的2018年会使用它的感觉。 这是怎么回事。

第一天:还算不错 (Day One: This Isn’t So Bad)

To perform this little experiment, I wanted to go with pure, stock Android—the last version officially supported by Google. So I flashed it to start with a clean slate. That went smoothly (as per the norm), and I was on my way.

为了进行这个小实验,我想使用纯库存的Android,这是Google正式支持的最新版本。 所以我闪过它,从干净的石板开始。 一切进展顺利(按照规范),而我正在前进。

Given the phone’s age, I decided to start with a clean slate and only install the apps that I absolutely have to have. That turned out to be a good idea, because man this phone can get bogged down quickly. But I’m getting ahead of myself.

考虑到手机的使用年限,我决定从头开始,只安装我绝对需要的应用程序。 事实证明,这是一个好主意,因为老兄这个电话很快就会陷入困境。 但是我要超越自己。

It definitely shows its age.
它肯定显示了它的年龄。

After getting it set up and all my apps installed, I spent the evening settings up my home screens and logging in to all the apps that I use on a daily basis. It wasn’t awful, but the more things I used, the slower the phone was getting. I knew this was going to be a challenge.

设置好并安装了所有应用程序之后,我花了晚上设置主屏幕并登录到每天使用的所有应用程序。 并不可怕,但是我使用的东西越多,手机的速度就越慢。 我知道这将是一个挑战。

The first noticeable downside of using this phone wasn’t the performance, though. It was the battery life.

不过,使用这款手机的第一个明显缺点不是性能。 这是电池寿命。

Let me tell you guys: I was lucky to get an hour of screen on time before having to hit the charger. Granted, this is a nearly five year old phone with the original battery. I didn’t expect anything good, but man…this was bad.

让我告诉大家:我很幸运能按时得到一个小时的屏幕,而不必点击充电器。 当然,这是一部使用原始电池已使用近五年的手机。 我没想到会发生什么好事,但是,伙计……这很糟糕。

Still, day one with the Nexus 5 wasn’t totally awful! It wasn’t until the next day I really starting seeing how bad this was going to get.

尽管如此,使用Nexus 5的第一天并不完全糟糕! 直到第二天,我才真正开始看到这种情况会变得多么糟糕。

第二天:等待是最难的部分 (Day Two: Waiting is the Hardest Part)

So, the Nexus 5 did not age well. The performance is unbearable now. The way I use my phone can be pretty intense—it’s not uncommon for me to switch back and forth between a handful of apps very quickly, but that’s not happening on the Nexus 5. Not only was stock Marshmallow released before one of my favorite and most used multi-tasking features—the double-tap-to-switch-between-apps feature—but the performance just isn’t there in general. The Snapdragon 800 can’t keep up with modern day apps and multitasking.

因此,Nexus 5的没有陈年。 现在的表现令人无法忍受。 我使用手机的方式可能非常紧张-在很多应用程序之间来回快速切换的情况并不罕见,但在Nexus 5上却并非如此。不仅在我最喜欢的手机之一之前发布了棉花糖,大多数使用的多任务功能-应用之间的双击切换功能-但性能通常并不存在。 Snapdragon 800无法跟上现代应用程序和多任务处理的步伐。

One of the absolute worst offenders is Facebook Messenger, which I will readily admit is one of the heaviest apps I use on a regular basis—it can even be sluggish on my Pixel 2 XL and Galaxy S9. It’s just a poorly-written, super-heavy app.

绝对最糟糕的违规者之一是Facebook Messenger,我很容易承认这是我经常使用的最重的应用程序之一-在我的Pixel 2 XL和Galaxy S9上它甚至可能表现不佳。 这只是一个写得不好,超重的应用程序。

But using it on the Nexus 5 was awful. The lag was unbearable. At one point while trying to close a chat head, I accidentally called my buddy Dan, whose text message was running behind said chat head. But here’s the kicker: the phone was so delayed that it didn’t ring on my end, and I had no idea I ever called him until I got a text that said “butt dial?” The dialer never even opened, because the phone was so loaded down trying to close a simple chat head.

但是在Nexus 5上使用它却很糟糕。 滞后难以忍受。 在试图关闭聊天头时,有一次我不小心打电话给我的伙伴Dan,他的短信在聊天头后面。 但是,这里有一个问题:电话是如此延迟,以至于我没响,而且我不知道自己曾经打电话给他,直到收到一条说“对接拨号?”的短信。 拨号器甚至从未打开过,因为电话已经装得很重,试图关闭一个简单的聊天头。

Battery life issues continued to plague me the second day—I ended up having to keep a portable charger with me pretty much all the time just to use the phone. It was so bad that I was scared to make any important phone calls from it because it would die too quickly. I ended up using my iPhone (my second phone) for anything important—the Nexus 5 just couldn’t be trusted to not crap out on me.

第二天,电池寿命问题仍然困扰着我-我最终不得不一直随身携带一个便携式充电器,以仅使用手机。 实在太糟糕了,我不敢打出任何重要的电话,因为它很快就会死掉。 我最终将iPhone(第二部手机)用于任何重要的事情-不能相信Nexus 5会让我失望。

第三天:Android Aut-我的天哪 (Day Three: Android Aut—OH MY GOD)

We don’t leave the house that often (at least, I try not to—my wife often has other plans), so it was a couple of days before we hit the car, where I live and die (and drive) by my Android Auto head unit. If I thought the phone was laggy the day before, I hadn’t seen anything yet—the Android Auto experience was terrible.

我们不常出门(至少,我尽量不要-我的妻子经常有其他计划),所以几天前我们撞上了汽车,在那里我靠着我生存和死亡(并开车) Android Auto主机。 如果我以为前一天手机比较笨拙,那我还什么都没看到-Android Auto的体验真糟糕。

First off, it took ages for the Auto interface to launch in the first place. With modern phones, it’s usually up and running before I even pull out of the driveway. But that day? I was out of the driveway and at least 12 blocks away before it even attempted to launch. And even then it wasn’t doing much.

首先,它花了很长时间在首位的自动界面启动。 对于现代手机,通常在我退出车道之前就已经启动并运行。 但是那天? 我不在车道上,距离它至少12个街区,然后才试图发射。 即使那样,它也做不了什么。

Generally, when I use Auto, I play music and then jump over to the navigation screen for realtime traffic details (or, you know, navigation). But the Nexus 5 got so overwhelmed with those activities that it had no idea what to do. Just playing music was fine, but as soon as I switched over to the navigation screen, it basically gave up.

通常,当我使用“自动”时,我会播放音乐,然后跳转到导航屏幕以获取实时路况详细信息(或您知道的导航)。 但是Nexus 5对这些活动感到不知所措,以至于不知道该怎么办。 只是播放音乐就可以了,但是当我切换到导航屏幕时,它基本上就放弃了。

But that’s just the beginning. You now those battery issues I was talking about? They gets worse. On my way to go pick up my stepkids (about a 40 minute drive), the Nexus 5 managed to lose 15 percent battery—while plugged in.

但这仅仅是开始。 您现在遇到我正在谈论的电池问题吗? 他们变得更糟。 在接上继子的路上(大约40分钟的车程),Nexus 5 在插上电源后设法减少 15%的电量。

第四天:是时候制作ROM了 (Day Four: It’s Time for a ROM)

I haven’t rooted or ROMed my main phone in years. But back in the day when I was but a wee Android lad, this was the de facto way to squeeze more speed, performance, and everything else out of your phone. I figured it couldn’t get any worse, so why not give it a shot? I installed Lineage OS.

多年以来,我还没有扎根或ROM过我的主要电话 但是,在我还是一个疲惫的Android小伙子的那一天,这实际上是从手机中挤出更多速度,性能和其他所有功能的方法。 我认为它不会变得更糟,那么为什么不试一试呢? 我安装了Lineage OS 。

In short: performance was better, even if only slightly. Android Auto was still a disaster, but most other every day use was better. Multitasking was slightly improved, and memory management appeared to also be slightly better. Battery life wasn’t any better, but I’m going to chalk that one up to the fact that the phone has a five year old battery that really just needs to be replaced.

简而言之:即使只有一点点,性能也更好。 Android Auto仍然是一场灾难,但其他大多数日常使用都更好。 多任务处理得到了一些改进,并且内存管理似乎也有所改善。 电池寿命并没有得到改善,但是我要总结一个事实,那就是手机的电池已经使用了五年,实际上只需要更换电池即可。

I didn’t dive into all the root tools available, like custom kernels and overclocking, mostly because the Snapdragon 800 already gets hot enough on its own. It just seemed like a bad idea.

我没有深入研究所有可用的根工具,例如自定义内核和超频,主要是因为Snapdragon 800本身已经足够热。 这似乎是一个坏主意。

Despite the differences and improvements (as minor as they were), the Nexus 5 was still just unusable.

尽管存在差异和改进(虽然很小),但Nexus 5仍然无法使用。

第五天:我承认,这太糟糕了 (Day Five: I Concede, This is Awful)

My goal was to use the Nexus 5 for a full week, but after five days, I had to tap out. I gave up. I couldn’t do it anymore. I went back to my Pixel 2 XL, and I swear it was the most magical moment I’ve had with tech in years. Years.

我的目标是整周使用Nexus 5,但是五天后,我不得不使用Nexus 5。 我放弃。 我做不了了。 我回到了Pixel 2 XL,我发誓那是我多年来使用科技的最神奇的时刻。 年份。

Why? Because all the complaints I had about the Pixel were suddenly gone. The minor niggles didn’t matter at all, because it just works. It’s fast. Android Auto does exactly what it’s supposed to. It was a moment that I haven’t had with a piece of tech in a long, long time. It was eye opening to see how far we’ve come in just a few short years.

为什么? 因为我对Pixel的所有抱怨突然消失了 。 细微的小事根本没有关系,因为它可以工作。 它很快。 Android Auto完全可以实现预期的功能。 这是很长一段时间以来我从未拥有过的一项技术。 看到我们在短短的几年中走了多远,真是让人大开眼界。

外卖:一些最终的想法 (The Takeaway: Some Final Thoughts)

Like I said in the beginning, the Nexus 5 is my favorite Android phone of all time. And despite what an awful idea it was to use it as my primary mobile device in 2018, that feeling hasn’t changed.

就像我一开始所说的那样,Nexus 5是我一直以来最喜欢的Android手机。 尽管在2018年将其用作我的主要移动设备是一个可怕的想法,但这种感觉并没有改变。

I still love how the Nexus 5 feels, and I’d love it if Google would do a modern take on it as part of the Pixel line. Same size (or at least similar), same materials—I actually like plastic phones—but with modern specs. I’d be all over that.

我仍然喜欢Nexus 5的感觉,如果Google将其作为Pixel系列的一部分,对其进行现代化改造,我会非常喜欢 。 尺寸相同(或至少相似),材料相同(我实际上喜欢塑料电话),但具有现代规格。 我会全力以赴。

But going back to a point I touched on earlier: the amount of progress that has been made with mobile phones in just five years is staggering. More specifically, Android itself has improved dramatically in that time. Marshmallow is just two years old, but somehow it feels so much older when compared to Oreo. While it doesn’t look dramatically different, the small touches included in Oreo that aren’t present in Marshmallow (and older) make a huge difference.

但是回到我之前提到的一点:在短短的五年中,移动电话取得了巨大的进步。 更具体地说,Android本身在那段时间已经有了巨大的进步。 棉花糖只有两岁,但与奥利奥相比,它感觉要老得多。 尽管看起来并没有太大的不同,但Oreo中包含的,棉花糖(及更早版本)中不存在的细微差别会产生巨大的变化。

The number of times I thought “why did I think this was a good idea” while doing this little experiment can’t be understated, but all in all I’m glad I did it. To be reminded of where we came from—both in terms of software and hardware—compared to where we are now was a nice reminder of the things I take for granted with modern handsets (and technology in general).

进行这个小实验时,我认为“为什么我认为这是个好主意”的次数不能被低估,但是总的来说,我很高兴自己做到了。 与我们现在所处的位置相比,无论从软件和硬件方面还是从现在起,我们都想起了我,这很好地提醒了我对于现代手机(以及一般技术)的理解。

I’d be curious to see how the Nexus 5 would perform with Android Go, because it would likely be a totally different experience. Except maybe with Android Auto. I’m not sure anything could fix that.

我很想知道Nexus 5在Android Go上的性能如何 ,因为它可能会带来完全不同的体验。 除非使用Android Auto。 我不确定有什么办法可以解决这个问题。

翻译自: https://www.howtogeek.com/348521/life-with-a-five-year-old-phone-an-experiment-with-the-nexus-5/

nexus 5x手机刷go

这篇关于nexus 5x手机刷go_五岁手机的使用寿命:Nexus 5的实验的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/323167

相关文章

Go Playground 在线编程环境

For all examples in this and the next chapter, we will use Go Playground. Go Playground represents a web service that can run programs written in Go. It can be opened in a web browser using the follow

go基础知识归纳总结

无缓冲的 channel 和有缓冲的 channel 的区别? 在 Go 语言中,channel 是用来在 goroutines 之间传递数据的主要机制。它们有两种类型:无缓冲的 channel 和有缓冲的 channel。 无缓冲的 channel 行为:无缓冲的 channel 是一种同步的通信方式,发送和接收必须同时发生。如果一个 goroutine 试图通过无缓冲 channel

如何确定 Go 语言中 HTTP 连接池的最佳参数?

确定 Go 语言中 HTTP 连接池的最佳参数可以通过以下几种方式: 一、分析应用场景和需求 并发请求量: 确定应用程序在特定时间段内可能同时发起的 HTTP 请求数量。如果并发请求量很高,需要设置较大的连接池参数以满足需求。例如,对于一个高并发的 Web 服务,可能同时有数百个请求在处理,此时需要较大的连接池大小。可以通过压力测试工具模拟高并发场景,观察系统在不同并发请求下的性能表现,从而

cell phone teardown 手机拆卸

tweezer 镊子 screwdriver 螺丝刀 opening tool 开口工具 repair 修理 battery 电池 rear panel 后盖 front and rear cameras 前后摄像头 volume button board 音量键线路板 headphone jack 耳机孔 a cracked screen 破裂屏 otherwise non-functiona

STM32(十一):ADC数模转换器实验

AD单通道: 1.RCC开启GPIO和ADC时钟。配置ADCCLK分频器。 2.配置GPIO,把GPIO配置成模拟输入的模式。 3.配置多路开关,把左面通道接入到右面规则组列表里。 4.配置ADC转换器, 包括AD转换器和AD数据寄存器。单次转换,连续转换;扫描、非扫描;有几个通道,触发源是什么,数据对齐是左对齐还是右对齐。 5.ADC_CMD 开启ADC。 void RCC_AD

【Go】go连接clickhouse使用TCP协议

离开你是傻是对是错 是看破是软弱 这结果是爱是恨或者是什么 如果是种解脱 怎么会还有眷恋在我心窝 那么爱你为什么                      🎵 黄品源/莫文蔚《那么爱你为什么》 package mainimport ("context""fmt""log""time""github.com/ClickHouse/clickhouse-go/v2")func main(

HNU-2023电路与电子学-实验3

写在前面: 一、实验目的 1.了解简易模型机的内部结构和工作原理。 2.分析模型机的功能,设计 8 重 3-1 多路复用器。 3.分析模型机的功能,设计 8 重 2-1 多路复用器。 4.分析模型机的工作原理,设计模型机控制信号产生逻辑。 二、实验内容 1.用 VERILOG 语言设计模型机的 8 重 3-1 多路复用器; 2.用 VERILOG 语言设计模型机的 8 重 2-1 多

Go Select的实现

select语法总结 select对应的每个case如果有已经准备好的case 则进行chan读写操作;若没有则执行defualt语句;若都没有则阻塞当前goroutine,直到某个chan准备好可读或可写,完成对应的case后退出。 Select的内存布局 了解chanel的实现后对select的语法有个疑问,select如何实现多路复用的,为什么没有在第一个channel操作时阻塞 从而导

Go Channel的实现

channel作为goroutine间通信和同步的重要途径,是Go runtime层实现CSP并发模型重要的成员。在不理解底层实现时,经常在使用中对channe相关语法的表现感到疑惑,尤其是select case的行为。因此在了解channel的应用前先看一眼channel的实现。 Channel内存布局 channel是go的内置类型,它可以被存储到变量中,可以作为函数的参数或返回值,它在r

Go 数组赋值问题

package mainimport "fmt"type Student struct {Name stringAge int}func main() {data := make(map[string]*Student)list := []Student{{Name:"a",Age:1},{Name:"b",Age:2},{Name:"c",Age:3},}// 错误 都指向了最后一个v// a