Hacker News Reader

The same thing happened to me, and I wrote an angry blog post about it[0] It is not OK for Google to lock me out of a phone that I own!

LineageOS (running on a different device) has changed the game for me. It has been a smoother, more accessible Android experience, and I'm so grateful to the developers who make it happen.

[0] https://jacobhall.net/2022/01/29/000177

Unfortunately, Lineage has abandoned a large number of previously-supported devices, so this latest version will be met with some dismay.

The primary reason is the loss of iptables, and the older kernels that do not support eBPF.

U.S. carriers are also moving to VoLTE, and this is not supported on any Samsung devices at all. AT&T has already made the move, and published a list of allowed devices.

It's sad to see them go.

> Unfortunately, Lineage has abandoned a large number of previously-supported devices, so this latest version will be met with some dismay.

> The primary reason is the loss of iptables, and the older kernels that do not support eBPF.

It's worth noting that the pmOS folks are working on mainline kernel support for older devices. This is not always easy, since e.g. some devices are only supported via non-free kernel or userspace blobs. But good quality hardware might regain support at some point. If you have devices that are going unsupported because of this issue, you might want to experiment with porting them to a mainline kernel by following the instructions on the pmOS wiki.

Unrelated to the topic we're discussing, I just wanted to say that your website is super cool. Its design is so simple and appealing to my minimalist taste (and I noticed that it's open-sourced). Fantastic job!

Thank you very much! I'm nearly done with a backend rewrite, which I'm super excited about.

Just bookmarked your site for inspiration, I love how smooth it is to switch languages.

Did they send you back a Verizon phone? Verizon Pixels have locked bootloaders due to Verizon's own policies. They say they are "unlocked" but they only mean carrier-wise. Source: Owned a Verizon Pixel 1 that I sold due to it having a locked bootloader.

Anecdotally, I purchased a 4a 5g from Google with a dead headphone jack. My replacement also had an unlocked bootloader though I think it was also new.

It was not branded as a Verizon model, but it seems to have the Verizon behavior of carrier unlocked, bootloader locked (and not unlockable).

Based on anecdotes like yours, I believe Google stopped doing it after the Pixel 2, but that doesn't help me.

I don't think they stopped, my Pixel 3 XL is locked also in the same manner.

you can contact them and they will replace it with an unlocked one

Google refurbs are bootloader locked. Probably old Verizon stock

When you run out of uses for your smart phone you can always convert it to a wifi LAN camera using IP Webcam by Pavel Khlebovich and consume the output in VLC. I have been using an old phone for this purpose successfully for years.

In general, I'm pretty aggressive about reselling or giving away old hardware when I no longer use it. But I do appreciate innovative uses like that, and I wouldn't be surprised to hear that some previous phone of mine is serving as a LAN camera for someone else :)

Is it running 24/7? How is the camera (sensor) holding on? Is the image quality still ok?

I had the same plans, but I was always afraid that running the camera for a long(-er) time will degrade the sensor fast, so te phones are collecting dust in a drawer now :)

On Christmas morning we had a break-in at our house. Since then have been using an old droid connected to wifi as IP Webcam (I even bought pro actually)

There are enough settings to allow for just about any use-case. For me, I had issues doing full HD over wifi, since the router is upstairs in a different room, but you can play around with settings for resolution and FPS until you find something stable enough for your setup.

The heating seems okay, leave it on 24/7 with no downtime. Occasionally the phone falls off the wall due to the advanced taping mechanism keeping it there, but that's not the software's fault.

You can have it automatically run at boot. We have load shedding here often, and the phone recharges quickly enough after the 2 hour shutdown of power and can stream throughout (connected to mobile hotspot wifi - also for loadshedding reasons)

I don't buy many apps, but this one I recommend for sure.

This is less useful than it sounds because there’s no integrated night vision, unlike even the cheapest ip cams. So really only works as a webcam.

How do you manage the battery? I would be afraid of a fire after x years being on all the time.

Note that I have no specific knowledge on the subject ; it's quite possibly a fear without any reasonable ground.

But I had a cheap speaker that I used with a Chromecast audio to listening to podcasts ; I left it always on and... I came back just in time one night, the speaker was producing a large dark smoke.

I almost put fire to one of the oldest habitation building in Paris (1704) - with a lot of apparent wood etc. :-(

Not proud of it, but good lesson. I recently read about the risk of fire in cheap replacement phone chargers. Google's ought to be of quality but... still a no-no for me.

Obviously, advice from people with knowledge on the issue will be appreciated.

Another reason why non removable batteries are crap. I have an old Nexus phone kicking around, if I were to repurpose it I’d just remove the battery and power it via USB. But you can’t do that with newer devices.

I wish there was an ability to replace smartphone batteries with a capacitor bank. Dashcam users have had these battery problems since Day 1. The solution is to replace batteries with capacitors. They are far more durable and can tolerate heating well.

I didn't know about "capacitors". Thanks for mentioning it.

I'd say most smartphones are powered on 24/7 during their regular phone lifetime. Not much would change by turning a phone into a 24/7 webcam, if viewed from that angle. Then again, CPU load would certainly be higher when used as a webcam.

Old phones with that streaming software run hot, in my experience, so this is certainly very sub-optimal for the battery and safety compared to just normal use.

Having it plugged in, OTOH, probably doesn’t matter. There’s safety IC to prevent overcharging. Actually fully draining, mechanical damage, water damage etc. are more dangerous, which can happen during normal use anyway.

If you use the IP camera app software I recommended it does not heat the phone very much, especially at 1080p stock settings.

I do appreciate stuff like that but I wish there were more alternatives, I don’t need a LAN camera! And I can’t think of much else I’d repurpose the hardware for either. I wish it were a lot easier to use phones as phones for a long time.

Yeah, I'm in the same boat; so is this guy: https://jacobhall.net/2022/01/29/000177

I google "flashing unlock is not allowed" every few months, but there's nothing new to try.

You can’t unlock it? I got back a locked phone when I got mine repaired but I could unlock it just like I did with the one I sent them.

Yes. Was yours a Pixel 2?

I'm not the only one to experience this issue, see https://support.google.com/pixelphone/thread/14920605/google... and https://issuetracker.google.com/issues/73217322 and https://issuetracker.google.com/issues/68897739

I see. Mine was a 2 XL. Probably not the same exactly

Is that really their policy? Unlocked until it needs to be fixed? Seems like that’s worse than just locking it down in the first place.

It was never a publicly stated policy and, anecdotally, they seem to have stopped doing it on newer phones. But one person escalated to a manager (because the first-level support staff didn't understand the difference between carrier unlocking and bootloader unlocking), and the manager stated that it was their policy.

And, yeah, I agree that it's probably the worst of all situations. If I'd have known that a google repair would cut the phone's lifespan in half, I'd have just done the repair myself, or else hired someone local to do it.

Are you in the US? It doesn't solve the issue that you now have to deal with, but if you paid for the "repair" service, I'd have considered cancelling the payment through my bank.

I am in the US. It was a free repair (covered by the warranty), and I didn't realize the bootloader lock issue until a couple of years later. (I was running stock firmware at the time - it's only been since google dropped support for the phone that I tried to upgrade to a third-party firmware.)

Is that safe? I would assume that disputing a transaction with Google would get you locked out of all Google services.

I doubt it is intentional. I heard they'll fix it if you contact them

This sounds like it's class-action worthy.

You're not wrong, although I'd be a little hesitant to start that because my job is somewhat dependent on being in google's good graces (and I've definitely heard of entire companies being banned when a single employee - or even former employee's - account gets flagged.)

Also, I find it unlikely that we could compel google to do the right thing and unlock everyone's phones, even if we won. I think the more likely outcome would be a small monetary compensation that was hardly worth anyone's time (except for the lawyers).

> I'd be a little hesitant to start that because my job is somewhat dependent on being in google's good graces

It's clearly becoming mafia-like, you are afraid of them just because of their reach.

>small monetary compensation that was hardly worth anyone's time (except for the lawyers)

I've definitely had this stance in the past, but at the same time, where there is no repercussion for the company doing this kind of stuff, it just makes them(and others) more open to it in the future.

For comparison there was a successful class action against Sony for removing Linux support from the PS3 in an online update.

https://en.wikipedia.org/wiki/OtherOS

I wonder if you could take Google to small claims court to get some kind of monetary compensation from them. You'd have to figure out how to explain what a locked bootloader is in judge-friendly terms, though.

Then again, Google would probably terminate your Google Account if you did this. And good luck suing Google for retaliation...

Yeah, someone else suggested a class action, but as you said, retaliation is likely, and I've heard of Google banning entire businesses because an ex-employee's account got flagged, and I just don't want to risk that.

Also, given that you can get a used pixel 2 for under $100, I doubt it'd be worth the trouble in the first place.

I can guess what the reason for this is: probably every phone that leaves Google must pass SafetyNet, and an unlocked bootloader will make SafetyNet fail. This cannot be circumvented, see this thread from the Magisk developer:

https://nitter.net/topjohnwu/status/1237830555523149824

I should probably have clarified that I expected an unlockable phone, not an unlocked one. Unlockable meaning that it is still locked, and still passes SafteyNet, but I can flip the switch in developer options and run the fastboot command and then unlock it. That capability is what they took away.

IMO, that shouldn't cause SafteyNet to fail either, but that's a different issue...

Also, the phone was bought in 2017, and the repair happened in 2018, so I think all of it predates that SafteyNet tightening.

While that stinks, I purchased not too long ago a used Google Pixel 3 for about $70 on Swappa.com and have been happily running LineageOS without GAPPS ever since.

I didn't know that 19.1 was released until now but it looks like it can't be installed using the updater on that phone.