I was also maybe a little low on patience after the fun I've been having the past day or so with my last phone that already had the sketchy USB port and (unsurprisingly) declining battery life. It is an S20 from 2020, and I did already get this replacement. (Thus even less urgency with doing anything about that thrashed screen protector which looks even worse in this lighting...)
It fell screen side down in the floor and hit the base of some metal shelving just wrong. So, now it's doing this shit. 🙃 Started out with a single green line like it gets when I plug it in here, and the very top of the screen very erratically responding to touch input. The screen also won't turn on unless it's put on charge, then it's grudgingly willing to wake up.
That progressed to what you're seeing here, over the past day or so. The screen was actually behaving remarkably well here, but it goes crazier the longer it's on. Usually now the notifications bar can only be pulled down at all from a homescreen that's empty at the top, and the top centimeter or so rarely responds. It's now also registering random phantom touches and swipes while I am actively trying to use it.
So yeah, I am avoiding touching the thing any more than has been necessary to try to get some of the important final shit migrated over. And I'm really hoping the poor thing will stay somewhat functional until after Mr. C gets back in another week or so.
This has primarily been a backup phone that I've been carrying around to continue running Diabox, and the Samsung watch that I mostly even got for the handy CGM display on my wrist. Still no luck getting Diabox reading the sensor right on the Pixel, trying again--and the devs couldn't figure out the issue either after I got the new phone and tried to get it working the first go around. ¯\_(ツ)_/¯ Same error this time.
But, whatevs. I did get xDrip+ up and running, which is at least as good other than not being able to directly carry my old Diabox data over.
No luck yet getting the watch to connect to this phone properly either, though I did find one more thing to check--and, due to the person I am, I haven't sought advice on the GrapheneOS forum yet. Where other people do seem to have managed OK. But yeah, while I'll be pissed if my smartwatch is effectively a paperweight now? I'll cope if that is the way things play out.
What really has me worried atm, though? My hard-won BankID is still set up on the S20. And you need it here for everything from online purchases, to logging into anything official like the health portal or the weirdest assortment of commercial sites. I'm not thrilled about the whole setup from a privacy perspective (a number of things in this country, tbqh), but it is what it is. It was difficult or impossible to get SO MUCH done before I finally got set up with BankID access, and I don't want to go back there. Even temporarily.
Being a filthy foreigner with a limited bank account, I also can't just transfer it to a new device online like pretty much everyone else. That would require online banking access. (Which I really don't need to get started on now. A whole rant of its own.) Nope, I need to get the Household Swede's assistance to set up a physical appointment at the bank, so they can do it. You can't just rock up, you do need to make an appointment during the roughly 3 hours a day that they're open and deigning to deal with customers. Banks here would really rather you do handle everything online.
And I can't set that up or really physically get there without some help, frustrating as it is on so many levels.
But, that's why the hope that Borked Phone holds out at least until after he gets back from that trip. I don't know if SEB will need to even see the existing app, though one would really hope not in case of lost/stolen or comprehensively busted devices. But, who knows. My main concern on a practical level is maybe getting stuck for weeks without a functioning BankID, while trying to at least minimally function as an adult. With no onsite backup for another week and a bit.
