Bought an ebook that turned out to be a .DRM file
...that only worked with that publisher's Android app
......that only works with Android versions < 6.0 (I use Android 9)
Tried it anyway, which among incompatibility issues, was raising a certificate error. I contacted the publisher about it
..."sorry, the author did not give us permission to sell this. You can have your money back"

What
Why are you even advertising it on your website as a publisher then??

@dfox just noticed a bug (or is it a feature?)

If you happen to double tap a rant slow enough that it doesn't +1 it. But fast enough that the rant view isn't opening yet it seems to register two single tap events and opens two views, needing to go back twice do return to the feed.

Not sure if that's important enough to report as a bug. :)

Ps: I'm on a LG G4, android 6.0

Soo... Android 6.0

No avatars are loading xD

They load on my old phone.

- Bug-Report -
Description:
If you go to the comments section on your profile and click on an comment you made to a collab, devRant will load it as a normal rant instead of a collab and, therefore, nothing is shown.

Device Details:
- Device: Phone
- Android Version: 6.0

devRant Version:
1.9.0.3

Steps to reproduce:
- Write a comment to a collab
- Go to Profile -> Comments
- Click on that comment
- It will load it as a normal rant (See image)

Actual behaviour:
Show as normal rant

Expected behaviour:
Show as collab

I hope you can reproduce...

@dfox, @trogus

Which do you like Android
4.0 Kitkat
5.0 Lollipop
6.0 Marshmallow
7.0 Nougat

# bug
There seem to be some push notification weirdness with my device.
push notifications are shown like couple of hours after I've seen them in Notifs. up to like 6-7 hours.
anybody else?

Question about conditioning my new android lithium battery.

I dont understand what's happening with my phone. Have old Xperia Z3 D6603 (running android 6.0 marshmallow).

Had problems with battery since it was not lasting even 5 minutes so bought a new battery from ebay and installed it yesterday.

So first time I put it to my phone it showed that it had 70% of charge. I've read in battery description that I have to discharge the battery and recharge 3 times.

First time I wanted to discharge from 70% to 1% and with a battery discharge app + youtube 1080p videos + wifi signal it took only around 1 hour and phone was at 1%. From 1% till complete discharge it took me extra hour and then phone died.

I plugged it to charge and after 15 minutes it showed that battery now is at 100% (which is insane, it should take 2-3hrs to charge it up to 100%). So I charget it for 2-3 hrs ignoring that it said 100% already.

I discharget it from 100% to 1% in 1 hour and now again phone is stuck at 1% and it took me 2 more hours to discharge phone until battery died completely.

I don't believe that this behaviour will fix itself. How can I fix this problem so that battery percentage would be distributed evenly? Now it drops from 100% to 1% in 1hr and then from 1% to 0% in 2 hrs.

It's these individually tiny annoyances in products and software that together form a huge annoyance.

For example, it's 2022 and Chromium-based web browsers still interrupt an upload when hitting CTRL+S. This is why competition is important. If there was no Firefox, the only major web browsers would, without exception, have this annoyance, since they're all based on Chrmoium.

I remember Chromium for mobile formerly locking scrolling and zooming of the currently viewed page while the next page was loading. Thankfully, this annoyance was removed.

In 2016, the Samsung camera software was updated to show a "camera has been opened via quick launch" pop-up window when both front and rear sensors of the smartphone were covered while the camera was launched by pressing the home button twice, on the camera software Samsung bundled with their custom version of Android 6. What's more, if that pointless pop-up was closed by tapping the background instead of the tiny "OK" button or not responded to within five seconds, the camera software would exit itself. Needless to say, this defeats the purpose of a quick launch. It denies quick-launching while the phone is in the pocket, and the time necessary to get the phone out could cause moments to be missed.

Another bad camera behaviour Samsung introduced with the camera software bundled with their customized Android 6 was that if it was launched again shortly after exiting or switching to stand-by mode, it would also exit itself again within a few seconds. It could be that the camera app was initially designed around Android 5.0 in 2015 and then not properly adapted to Android 6.0, and some process management behaviour of Android 6.0 causes this behaviour. But whatever causes it, it is annoying and results in moments to not be captured.

Another such annoyance is that some home screen software for smartphones only allows access to its settings by holding a blank spot not occupied by a shortcut. However, if all home screen pages are full, one either needs to create a new page if allowed by the app, or temporarily remove a shortcut to be able to access the settings.

More examples are: Forced smartphone restart when replacing the SIM card, the minimum window size being far too large in some smartphones with multi-windowing functionality, accidental triggering of burst shot mode that can't be deactivated in the camera software, only showing the estimated number of remaining photos if less than 300 and thus a late warning, transition animations that are too slow, screenshots only being captured when holding a button combination for a second rather than immediately, the terminal emulator being inaccessible for the first three minutes after the smartphone has booted, and the sound from an online advertisement video causing pain from being much louder than the playing video.

Any of these annoyances might appear minor individually, but together, they form a major burden on everyday use. Therefore, developers should eliminate annoyances, no matter how minor they might seem.

The same also applies for missing features. The individual removal of a feature might not seem like a big of a deal, but removing dozens of small features accumulates to a significant lack of functionality, undermining the sense of being able to get work done with that product or software when that feature is unexpectedly needed. Examples for a products that pruned lots of functionality from its predecessor is the Samsung Galaxy S6, and newer laptops featuring very few USB ports. Web browsers have removed lots of features as well. Some features can be retrofitted with extensions, but they rely on a third-party developer maintaining compatibility. If many minor-seeming features are removed, users will repeatedly hit "sorry, this product/software can not do that anymore" moments.