this post was submitted on 18 Feb 2024
237 points (87.4% liked)

Technology

59589 readers
3148 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

While flagship smartphones boast impressive features, spending $1,000 is not a prerequisite for a satisfying Android experience nowadays. If you’re in need of a new smartphone and have a budget of approximately $200, there are numerous excellent options available. Surprisingly, some of the best Android phones under $200 come equipped with features like 5,000mAh batteries, multi-lens camera setups, and the promise of extended software updates.

We thoroughly evaluate various Android phones to ensure optimal performance without encountering unexpected issues down the line. If we were to recommend one Android smartphone in the sub-$200 price range, it would be the latest addition to Samsung’s lineup, the Galaxy A15 5G. Boasting a 6.5-inch Super AMOLED screen, a sizable battery with 25W fast charging support, and more, it offers a compelling package. Alternatively, consider Motorola’s Moto G Play (2024) for a straightforward yet functional device.

you are viewing a single comment's thread
view the rest of the comments
[–] Altomes@lemm.ee 26 points 9 months ago (14 children)

Honestly in my mind the best phone is a used one with lineage, like my oneplus 8t was $130 it's in great shape with 256gb and I'm relatively confident it'll receive updates for years to come from Lineage.

[–] clark@midwest.social 4 points 9 months ago (2 children)

I’m sorry if this is the wrong place to ask, but do older phones running Lineage still receive updates? Say, Samsung S9, is it worth installing the OS despite its age? Not too knowledgable on this area, just wanna learn!

[–] drengbarazi@lemmy.world 3 points 9 months ago* (last edited 9 months ago) (1 children)

Looks like Samsung Galaxy S9 is still receiving updates. Last build (nightly) was like today.

[–] clark@midwest.social 3 points 9 months ago (2 children)

If the device no longer supports updates, is it safe to still run Lineage on it?

[–] Altomes@lemm.ee 5 points 9 months ago

Correct, lineage is actually a great way to extend the life of a device safely

[–] loki@lemmy.ml 4 points 9 months ago (1 children)

It is safer than not updating at all. Unsupported devices have a lot of exploits and vulnerabilities.

[–] clark@midwest.social 2 points 9 months ago (1 children)

Does that also go for devices that don’t receive Lineage updates anymore?

[–] drengbarazi@lemmy.world 0 points 9 months ago (1 children)

I mean, you might cover some vulnerabilities that were discovered after the manufacturer stopped updating your device, which is nice. But only time will tell what new vulnerabilies will be uncovered next; but be sure, they will.

Only a frequently updated device will have constant state-of-the-art vulnerability protection. That is, until the maintaner (someone with the know-how to make stable lineage-os builds and mess with the device's vendor tree doing all this work for free) decides to stop updating that device. Which sounds bad but that doesn't stop another maintainer from rising up to the task eventually.

Anyhow, with lineage and, generally, any custom OS aimed at phones that can't relock their bootloader safely you'll always lose device integrity (can be circumvented with things like magisk) and very likely IMS features (VoLTE and the like).

Another thing to consider is if your device ends up in the hands of a malicious party. If its bootloader is unlocked, you can be sure they'll have easy access to any personal data inside it.

If you wanna be safe for a looong time I'd consider a pixel phone from this list and flashing grapheneos and then relocking the bootloader.

In any case, good luck and all the best to you! :)


Sidenote: if you are on a Linux system and do intend to flash a custom recovery (necessary step before flashing a custom OS) on a samsung phone, take a look at the Heimdall tool. It's an open source alternative to Odin that runs natively on Linux.

[–] BigFatNips@sh.itjust.works 0 points 9 months ago (1 children)

Any source for unlocked bootloader meaning your data is just there for the taking? Afaik it's still encrypted and someone would have to pull off an evil maid style attack to get your password/PIN if they wanted to decrypt it. Which certainly is easier/possible with an unlocked bootloader but that's nowhere near "someone steals your device and bippity boppity boop they got ur data"

[–] drengbarazi@lemmy.world 0 points 9 months ago (1 children)

Yeah, if you use a relatively new device. Or you make sure your device is encrypted.

Big chunk of old android phones (pre 2016) came unencrypted by default. They could be encrypted if the user wished/knew how.

I remember having a motorola (moto g4 I think) that after flashing twrp it didn't ever asked for my pin. It was officially supported by LineageOS for a long time too. Still, damn fine phone lol

[–] BigFatNips@sh.itjust.works 0 points 9 months ago (1 children)

"Relatively new" is 8 years ago to you? If you have to make sure your phone is encrypted then it's either currently running or shipped with android 5.1.1 or lower (per your link) so yeah I don't think this is a real concern and I do not understand why people (apparently knowingly in your case) spread misinformation about BL unlocking.

[–] drengbarazi@lemmy.world 0 points 9 months ago

Okay wutelgi, have a good day

[–] LambdaRX@sh.itjust.works 2 points 9 months ago

Budget Redmi 4A from 2016 just got updated to android 14.

load more comments (11 replies)