• 1 Post
  • 78 Comments
Joined 10 months ago
cake
Cake day: November 20th, 2024

help-circle





  • I guess how much people care also depends on whether they tend to use laptops in ways and places that are prone to causing damage to the ports. I’ve never damaged any port on any laptop I’ve ever owned, and it’s unlikely I ever will because I like to keep the cables organized and out of the way (so it would require conscious effort to tug on them), and when I want to pick my laptop up, I always quickly run my hand around its perimeter to make sure everything is disconnected.

    I do not claim that this is the correct way to use a laptop or that others should do the same, it is a tool that should be used the way its user needs, I just want to point out that for some usecases, this is simply a non-issue in the same way a non-replaceable CPU is - nothing’s going to happen to it.

    Also, my current laptop does have both a barrel jack (probably works, I’ve never used it) and a USB-C charging connector, so it’s not necessarily an either-or proposition.


  • Also, Google is no longer releasing the Pixel-specific source code, meaning you can no longer just build AOSP for new Pixels and have all the hardware just work - this makes it harder for custom ROM developers and might eventually lead to some hardware being simply unsupported unless you use the stock ROM.





  • MarkaostoTechnology@lemmy.ml00000
    link
    fedilink
    arrow-up
    1
    ·
    21 days ago

    Just to be clear, the applets were stuck while the laptop was plugged in? If so, then it might just be the threshold - connected, not charging, not discharging (because the laptop is running off the AC adapter).

    For example on my IdeaPad laptop, when I enable the charge limiting feature it will get “stuck” at 59 or 60% while plugged in. It doesn’t have a configurable threshold. Although your laptop might provide a more fine-grained control given that you were able to fully discharge it while plugged in.






  • I don’t understand how having a notification is what’s keeping an app alive.

    Do you remember notifications that couldn’t be swiped away in older Android versions? Their point was to keep their app alive. They still exist and still work the same way, keeping their app alive until it cancels the notification, except they can now be dismissed like any other notification (which doesn’t really have any effect other than hiding it from you - it will still keep the app alive even when hidden).

    It’s possible that it’s broken in AOSP for some reason, but developer documentation says it should work like this and it does indeed work like this on stock Google ROMs on Pixels.


  • MarkaostoAndroid@lemmy.worldAndroid 15 (Lineage OS) agressively kills apps
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 months ago

    why would swiping away an app not kill it? why would you do that? leave it be until it’s done wtf

    Because if an app has a permanent notification, it cannot get killed. Before Android 15 or 14, you couldn’t even swipe such notifications away - the idea was that the app was forced to tell the user it’s running.

    Then Android added a list of apps running in the background and allowed users to dismiss the permanent notifications, but the behavior is still the same - an app can keep itself alive until it removes the notification on its own or gets force killed either by doze or from the settings.

    So swiping away a browser after you initiate a download is a perfectly valid use case that is intended to work without any problems. If it doesn’t, then it’s a bug either in LineageOS or in the browser.

    Also, I can confirm this works perfectly fine on stock Android 16 ROM on a Pixel with Vivaldi browser - the download finished, and then Vivaldi got killed, because nothing was keeping it alive after it cancelled its download notification.