My ISP provides me with 1GB data per day. So the data billing cycle in Nougat would actually make more sense to me if I could somehow make it show the amount of data I've used in a day and then have it reset for the next day. I'm using Resurrection Remix ROM 5.8.5. Is there a way to do this?

I'm looking for a screenshot, which I can see in Google Photos under *Device folders* -> *Screeshots*. But when I browse it from my PC (Windows 10), in *DCIM* folder I can only see *Camera* one (I read it should be *Screenshots* next to it). Why is that? Is it possible that I don't have permissions to see it?

I have Android 7.0 and I'm trying to upgrade it to Android 8 or 9 because some apps require that as the minimum version. The problem now is I feel like my phone has stopped receiving updates from the manufacturer so I want to know if it is possible to manually upgrade it through ADB (or something) with my laptop. When I check the phone's software updater it says there are no upgrades and it's the latest version but we both know that isn't true, so I'm trying to forcefully upgrade it. My phone is T-Mobile and the model is 5049W **Edit:** It doesn't even seem like there's a custom ROM/recovery for this particular model of T-Mobile.

After staying for so long on Marshmallow, today I finally made the decision to upgrade one of my secondary devices with Nougat (LineageOS 14.1 to be precise). Everything went smooth and most things stayed familiar... except this weird entry in Settings - Developer options - Running services. Screenshots (click images for larger variants) I'd keep the running process list as clean as possible (habit, don't question why), but when I clicked into this "Android Services Library" and tried to stop it, it says it runs a "Notification ranker service" (second screenshot). Clicking "Settings" there takes me to an app preference screen (third screenshot; likely the same as in Settings - Apps) that contains nothing about the service or the app: Furthermore, I can't find any reference on how this "notification ranker" mechanism works, or even what it is. Note that I also flashed stock Nougat on my Nexus 6P before, and from what I remember, that one also has this service running, so it's not specific to LineageOS. Can anyone with sufficient knowledge tell me what it does, and what will happen if I disable this service via external means, e.g. will notification functions be affected?

Is there a reliable, reproducible way to clear DNS cache on Android Nougat 7.0? I know there is at least one other question like this but that one was from 8 years ago and I hope I can ask again and see what people are doing these days. To explain a bit more my setup: I am testing a simple web page loading in Chrome browser with Wireshark packet capture to see the DNS requests. I am also running dnsmasq on my LAN and have mapped my webpages name: mymovies to the correct IP address of the machine on my LAN that the web server is on. So http://mymovies should work and it does load. The DNS lookups initially start with the DHCP server appending the DNS suffix (.home) so in the packet trace I see a DNS request for mymovies.home which fails because I don't have an IP address mapping for that in dnsmasq.conf. So a second DNS lookup for just mymovies appears and is successful. Mostly I find that subsequent DNS lookups are always just for mymovies and never again for mymovies.home no matter what I try to clear the DNS cache: I am testing over WiFi with a Moto G5 running Android 7.0 and it is rooted so I can run commands from within adb shell to the OS. I have tried lots of things like: 1. Closing down Chrome browser and starting it up again. 2. chrome://net-internals/#dns to clear host cache and flushing the sockets too 3. Settings > Apps > Chrome > Storage > Clear Cache 4. ndc resolver clearnetdns wlan0 The only thing that seemed to work for me was turning the phone off and on again. After restart I opened http://mymovies in Chrome on the phone. The page loaded and in the Wireshark trace I see the first DNS request for mymovies.home which fails as usual followed by a DNS request for mymovies that succeeds. I then closed down that tab and opened a new one and loaded the page again.. I did this twice. Each time now I see a dns request for mymovies only.. it doesn't even try mymovies.home. I restarted dnsmasq server and the first DNS lookup after that was for mymovies.home followed by a lookup for mymovies. But since then the DNS lookups are now only ever for mymovies. This is despite restarting the dnsmasq server a few times and trying the four so-called DNS cache clearing steps listed above. But to confuse the matters, I tried the trick of switching into and back out of Airplane Mode. Now when I load my little test web page a few times it doesn't seem to cache at all anymore? Loading the webpage always initially gives a DNS look up for mymovies.home which fails then a lookup for mymovies that succeeds. Even after restarting the phone the DNS lookups have now stopped caching completely and it firstly tries mymovies.home every time! I think this caching behavior is normal and expected but I'd just like a way to clear that cache so it goes back to trying mymovies.home without me having to restart the phone. I'm not sure if the IPv6 has anything to do with things? In my router I have specified the IP address of the Raspberry Pi on my LAN that dnsmasq is running on so the router directs DNS requests to it. I don't want the page to stop caching OR to always cache. I just want to be able to clear the DNS cache in a predictable manner so I can make the DNS request for mymovies.home appear once followed by the expected DNS caching.

According to a well-regarded QA answer by a member of our Android community here on Stack Exchange: > By the current schedule, Let's Encrypt cross signing will end on September the 30th 2024. After this date Android 7.1 stock devices will become more or less useless for Internet surfing as all Let's encrypt based certificates will be considered untrusted and the connection will not be established. Has this schedule changed? I haven't seen any announcement of a change, but I've noticed that affected devices suddenly have certificate validation failures when trying to connect to many internet hosts. The problem seems to stem from Let's Encrypt R3, which is affected by the changes that were supposed to be effective much later this year. Is there any documentation as to why these devices are being affected earlier than planned? Are there any workarounds for non-rooted devices? Relevant: - https://letsencrypt.org/2024/03/19/new-intermediate-certificates - https://letsencrypt.org/2020/12/21/extending-android-compatibility.html - https://community.letsencrypt.org/t/lets-encrypt-new-intermediate-certificates/209498