Android Help Sunday Rant/Rage (Aug 18 2019) - Your weekly complaint thread! |
- Sunday Rant/Rage (Aug 18 2019) - Your weekly complaint thread!
- The Motorola One Action doesn't want you shooting vertical video
- Microsoft's SMS Organizer appears to have been made available in additional regions (early access)
- TIL I learned there's an alternative to adjust the ringer volume in android Pie
- Used YouTube Music for a day and it's nothing but a sad mess
- X-post: How Google Play “Terminated” a Developer for No Reason : androiddev
- PSA on Facebook phishing problems with Frost
- I created r/Mi9T (or K20) (Pro) to centralize the posts about this phone from now on
- GSMArena's Note 10 vs Pixel 3 camera comparison nicely highlighted two things I DO NOT like about Pixel's camera
- [DISCUSSION] Is AMOLED worth it considering screen burn-in?
| Sunday Rant/Rage (Aug 18 2019) - Your weekly complaint thread! Posted: 18 Aug 2019 04:16 AM PDT Note 1. Join our Discord, IRC, and Telegram chat-rooms! Please see our wiki for instructions. This weekly Sunday thread is for you to let off some steam and speak out about whatever complaint you might have about:
Rules 1) Please do not target any individuals or try to name/shame any individual. If you hate Google/Samsung/HTC etc. for one thing that is fine, but do not be rude to an individual app developer. 2) If you have a suggestion to solve another user's issue, please leave a comment but be sure it's constructive! We do not want any flame-wars. 3) Be respectful of other's opinions. Even if you feel that somebody is "wrong" you don't have to go out of your way to prove them wrong. Disagree politely, and move on. [link] [comments]  | ||
| The Motorola One Action doesn't want you shooting vertical video Posted: 18 Aug 2019 04:34 PM PDT
 | ||
| Microsoft's SMS Organizer appears to have been made available in additional regions (early access) Posted: 18 Aug 2019 05:19 PM PDT | ||
| TIL I learned there's an alternative to adjust the ringer volume in android Pie Posted: 18 Aug 2019 09:13 AM PDT The pie volume lever makes your phone ring every time you want to adjust it, and it's kinda irritating, so to skip this nuance, just hold some seconds both the volume up and down key, and adjust volume, and voila you can change ringer volume without waking up your whole neighborhood. I discovered this feature by playing around with an app that used accessibility shortcuts for activation. i hope it serves someone! [link] [comments]  | ||
| Used YouTube Music for a day and it's nothing but a sad mess Posted: 18 Aug 2019 12:49 AM PDT I'd been a GPM user for many years now, but lately the app seemed more and more abandoned and out of sync with the rest of Google services. It's blindingly white, there is little to no developer feedback re bugs and/or possible new updates, and with Google actively pushing YTM down everyone's collective throat it seems less and less likely that it is worth it to continue building your music library there. So I thought I'd start looking for a replacement app. I have to say that it really, really sucks. GPM had been almost perfect for me in a "basic, integrated into my phone" kind of way. Now Playing shows me the songs and sends me to GPM to like them and ad them to an auto-generated playlist of all my liked songs that are being downloaded to my device so that I don't get any shitty surprises on a plane. Some of the songs later go to my gym playlist, some I add to my jogging playlist etc. It's all very simple and perfect for me, and I don't need much. I started with Deezer, just because I'd seen it on the store a week ago. The app had felt like an improvement over GPM with much better recommendations, lots of charts and playlists and a sleek UI. There is also a 3-month testing period that is almost free, so I was almost ready to give it a try. But then a got an offer from one of my cell service providers (I have several phones for work) for a free 6-month subscription to YT Music Premium. 6 months. That's a lot of free music. On a new platform developed by Google. The future flagship music service by the company behind my Pixel phone. What could go wrong that I would regret taking up a free offer that wouldn't cost me anything but my time? A lot.
I can't even pick what's the worst thing about YTM and I'd only been using it for a day, but I'm certain about this:
I'd tried (and been disappointed by) YTM before, as my comment history will confirm, but some time had passed since then and I was sure that the app would have improved greatly by now. It has not. This seems like another Hangouts/Allo scenario, where an app that nobody had asked for comes to replace an app that people are already using, but is quickly killed off for this very reason. And you don't have a single app anymore. [link] [comments]  | ||
| X-post: How Google Play “Terminated” a Developer for No Reason : androiddev Posted: 18 Aug 2019 09:11 AM PDT | ||
| PSA on Facebook phishing problems with Frost Posted: 17 Aug 2019 10:31 PM PDT Hello all, developer of Frost here. In light of the post regarding temporary account locks with Frost, and ongoing concerns with third party wrappers in general, I'd like to provide a quick summary of my findings. TLDR: The problem was probably related to changing user agents, and it seems like most apps use one agent at a time. Frost also has a new release through Github, and will push one to F-Droid as soon as possible. I am happy to answer any questions you have in this thread, or you can create Github issues or email me (I'm not super active on Reddit). ---------------------------------------------------------------------------------------------------------- It seems like some time within the past month, Facebook became more restrictive towards user agents. Switching agents with the same authentication and executing some post request (eg commenting) would trigger a phishing warning, and would require identification + a password reset. This is still speculation, but with all the reports I've been given, I am reasonably confident that this is the problem. Up until now, Frost would use the default user agent upon login, to make sure that users would see their actual device through login sessions. It would then switch between a mobile agent or a desktop one to enable as many features as possible, as some pages like messages are disabled on mobile, whereas other actions like map intents will not work with a desktop agent. As of Frost 2.3.2, the desktop user agent is used for the entire session. The caveat is that your session will list a desktop instead of your actual device (which may make it harder for you to distinguish against actual unauthorized logins), and certain features that are mobile specific will be disabled. It appears that most other apps did not bother to allow switching per content, which explains why Frost was the only one affected. However, there are apps that allow you to select your own user agent, so I would be careful with doing so without logging out first. I still find it odd that this is the problem, as people use dev tools and spoof user agents all the time, but this has been the most consistent factor. There are also several secondary causes I've looked at. Frost provides a native notifications UI, and will mark notifications as read when you click on it. That, along with several other features, depends on getting specific ids found on your newsfeed, then using it to create other post requests on your behalf. This is a bit more hacky than just displaying browser information, or even parsing a website, so I now also provide a "web only" mode, which will disable all interactions outside of the browser, to essentially give an enhanced browser experience. It does appear that this was not the cause of the problem, which is why it is not enabled by default. The last, more troubling speculation, was that Frost was being targeted specifically. As an example, I use flags in the window to avoid loading js functions multiple times. Each one is prefixed with 'frost', and is freely accessible by other scripts. It appears that for a minority of users, obfuscating the tags fixed the ban. I do not yet have proof, and may spend some time looking at the source pages, but there's that. On a final note, I'd like to add some comments towards using web wrappers in general. Most of us have our best intentions in mind, and wish to give you a greater experience with whatever website we are building for. Projects tend to start from a need we ourselves possess, and grow as we wish to share that same experience with others. With that said, while you are certainly all aware of the power you give Facebook with your data, you should be equally cautious with entrusting other developers with your accounts. Facebook unfortunately does not provide a good API to use, and we are instead forced to display the login page directly for you to authenticate. This is not safe, and there is nothing stopping us from logging your account, scraping any data from your account, or posting on your behalf. To be fair, any app with your authorization can do that, but a web wrapper will know your password verbatim and have nearly full access, while a good API will only supply a temporary token, and will also limit the amount of interaction possible. Keep this in mind when you try out a new web wrapper, especially if the sources are unknown. With that said, I welcome any questions about this problem (or any other) in this thread. I will try to respond to them, but you can otherwise post a github issue or email me. I know that other developers will be reading this text, and so hopefully this information, along with Frost's source code, will help you in avoiding these bans. [link] [comments]  | ||
| I created r/Mi9T (or K20) (Pro) to centralize the posts about this phone from now on Posted: 18 Aug 2019 11:55 AM PDT The only reason for creating r/Mi9T is the fact that i recently bought the phone and i really like it, so i would like to create a community in which we can focus on our current/favorite phone. This is only intended to help the actual owners, future owners, or even buy-curious people. The subreddit contains discussions around problems, custom ROMs or even curiosities regarding different aspects of the phone. Feel free to join and contribute with knowledge! Thank you for your attention! [link] [comments]  | ||
| Posted: 18 Aug 2019 06:13 AM PDT TL;DR - Purple/blue tint, noise and grain. GSMArena did a camera comparison between Galaxy Note 10 and Pixel 3. I know Pixel is hailed as the absolute king of mobile photography but I thought their comparison samples highlighted two of Pixel's photo weaknesses (in my opinion of course) quite well - Pixel's tendency to add cooler blue-purplish tint to bright daylight images and the noise (it's very specific, you can always recognize a picture taken with a Pixel because of the way it handles noise and grain). Let me show you the examples: Photo 1 - Pixel 3 Photo 1 - Note 10 You can see above that the Pixel is a colder photo. Something that I don't like personally as I think a bright sunny day should feel warm. I think it has slightly more detail than Note 10, which is more noticeable with with trees - Pixel, Note 10. Note 10 just smudges details on trees, but overall the photo does not look as pleasant. Photo 2 - Pixel 3 Photo 2 - Note 10 Again, you can see that the Pixel photo is cold and has that blue/purple tint to it that characterizes Pixel photos taken in bright daylight. On a sunny day that effect is just not pleasant. Note 10 in comparison is brighter and warmer. I feel that it has a bit of a too much green tint in it, but it's still quite nice. Something in the middle would've been perfect. But there is another thing with the Pixel photo and that is grain! Lots of it. I know people justify this saying the photo looks more "natural" and less processed but in my opinion it does not. It just does not look good. Here's the example: Note 10, Pixel 3. Look at the grain and noise - All of that should not be there, the green arrow indicates the detail, which it has more than Note 10. I think Pixel has the most versatile camera on the market and that's why it's hailed as the best, because it'll get you nice images in almost all scenarios but I do think that it has those two weaknesses that I hope Google will fix eventually. [link] [comments]  | ||
| [DISCUSSION] Is AMOLED worth it considering screen burn-in? Posted: 18 Aug 2019 07:10 AM PDT My phones before were Galaxy S6 Edge and Galaxy A5 (2014), both of them had a lot of very visible burn-in after 1-2 years of usage. After those became almost unusable I bought a phone making sure it's not AMOLED and I can't tell what I was missing? I have a Huawei P20 which is just LCD, the PRO version has AMOLED as if it's a feature. Am I missing out on significantly more battery life or something? Or is that not relevant anymore with today's battery sizes? Being able to leave my phone running all the time without worrying about waking up to a burned screen is pretty nice. What do you think of AMOLED? Do people not care cause they buy a new phone every year anyway or am I using my phone too much? Or does the black on AMOLED just look that good [link] [comments]  |
| You are subscribed to email updates from Android. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment