• Breaking News

    Thursday, January 30, 2020

    Home Unlabelled Android What should I buy Thursday (Jan 30 2020) - Your weekly device inquiry thread!

    Android What should I buy Thursday (Jan 30 2020) - Your weekly device inquiry thread!

    January 30, 2020

    Android What should I buy Thursday (Jan 30 2020) - Your weekly device inquiry thread!

    What should I buy Thursday (Jan 30 2020) - Your weekly device inquiry thread!

    Posted: 30 Jan 2020 03:11 AM PST

    Credits to the team at /r/PickAnAndroidForMe for compiling this information:

    Note 1. Join us at /r/MoronicMondayAndroid, a sub serving as a repository for our retired weekly threads. Just pick any thread and Ctrl-F your way to wisdom!

    Note 2. Join our IRC, and Telegram chat-rooms! Please see our wiki for instructions.

    submitted by /u/AutoModerator
    [link] [comments]

    Forensics detective says Android encryption now superior to iPhones

    Posted: 29 Jan 2020 03:08 PM PST

    Google app tests a darker shade of gray, shows a few signs of AMOLED black

    Posted: 29 Jan 2020 09:42 AM PST

    YSK: Apps that share your info/activities with Facebook

    Posted: 29 Jan 2020 10:34 AM PST

    One of my friends shared a link today to a Facebook Settings page called 'Off-Facebook Activity.' I was curious to find out what apps share stats & user info/activities with Facebook knowing that I have been using 'Simple Pro' for over 2 years and don't have the Facebook app installed on my phone.

    To my surprise, I found couple apps that have been sharing my activities with Facebook like the Alarm Clock app Alarmy Pro (WTF?), LinkedIn app, McDonald's app, MX Player Pro and many more.. Mind you, none of these apps are linked to my Facebook account whatsoever.

    To find out yourself, go to the this link:

    https://www.facebook.com/off_facebook_activity/

    submitted by /u/shichemt
    [link] [comments]

    Will the Samsung Galaxy S10e go down as just a one-off experiment?

    Posted: 29 Jan 2020 09:32 PM PST

    Unicode Emoji 13.0 — Now final for 2020

    Posted: 29 Jan 2020 01:28 PM PST

    Moto G Stylus Leaks Live, Hole-Punch Camera, Snapdragon 6 Series CPU and more

    Posted: 30 Jan 2020 12:21 AM PST

    One Today by Google is Shutting Down

    Posted: 29 Jan 2020 11:57 AM PST

    Just got this disappointing e-mail from the Google One Today team... if you're not familiar with the app it highlighted a different charity each day and let you donate $1 towards their cause.

    Hello,
    We have an important update to share with you.

    We launched Google One Today seven years ago to help people donate to causes they care about. In the last few years, we have seen donors choose other products to fundraise for their favorite nonprofits.

    As a result, we will shut down One Today on February 6th, 2020.

    New nonprofits will no longer be able to sign up for One Today. The Google One Today app will be turned off, and any open projects will be deleted. We will ensure that 100% of funds donated on One Today prior to February 6th are disbursed to the relevant nonprofits.

    If you have any questions, please feel free to contact the One Today team.

    Thank you for your donations and partnership.

    The Google One Today team

    submitted by /u/trigatch4
    [link] [comments]

    Google scoped storage is about to kill one of the best Android apps

    Posted: 29 Jan 2020 11:56 PM PST

    Google has artificially limited the number of search engine choices, ignoring the obvious fact that screens can scroll. - DuckDuckGo

    Posted: 29 Jan 2020 01:27 PM PST

    Moto G Stylus Running Android 10 and 4GB RAM Appeared on Geekbench

    Posted: 29 Jan 2020 09:49 PM PST

    r/Android Community Feedback Poll Results

    Posted: 29 Jan 2020 05:51 AM PST

    What is this?

    We ran a community feedback poll for around 6 weeks (the thread was stickied for the first 4 weeks). We got around 930 responses. These are the results.

    Before we start, though -- a big thanks to all who participated, be it in the feedback threads from which the poll was built, or the vote itself.

    Link to the results.

    Rule 1 (off-topic)

    • Should we allow benchmarks/press releases/major update threads about Android competitors?

    The preferred choice (45%) seems to be that the article should be drawing some kind of comparison to Android. If not, then the OP should do that in the self-text.

    That being said, this one's a bit tight with almost 39% wanting these threads being always accepted, as a comparison would then be "implicit" and made by commenters.

    The main lesson here is that we should've used preferential voting for questions with more than 2 answers.

    We'll be going with the main choice for now (as in our opinion, it would've most likely won in a preferential vote scenario with most of the 39% putting it as their 2nd preference). This is what we're already doing, but we're open to doing another poll (maybe with more options) if there's demand -- please let us know in the comments.

    • Should we allow threads about generic phone accessories made by major Android OEMs? (e.g. Pixel Buds, Galaxy Buds, OnePlus Bullets, etc)

    Most people (77%) say yes. This is already what's happening.

    • Should we allow threads about other Google products that aren't related to Android? (e.g. Google Home/Mini, ChromeOS)

    Most people (57%) say no. We currently allow these threads due to the last community poll we ran a few years ago.

    Starting now, we will only allow them if the article or OP makes a clear connection to Android that makes it relevant to Android users.

    For example, threads about updates that introduce new features related to Android (e.g. controlling your phone, or running Android on ChromeOS, etc) are fine. Threads about general updates/announcements/sales of these products are not.

    (P.S. You might be interested in r/Google, r/Stadia, /r/googlehome and /r/chromeos which are all fairly active.)

    • Should we allow general threads related to Google Stadia and competitors?

    Most people said yes if there's a relation to Android (63%).

    Starting now, we'll be doing the same as above.

    • Should we allow threads about other generic phone accessories? (Chargers, speakers, etc)

    Most people said yes (60%). This is what is already being done.

    • Should we allow threads about carrier news that aren't specific to Android? (e.g. 5G rollout, RCS)

    Most people said yes (62%).

    We're mostly already doing this, but we weren't very consistent so it's good to get a consensus.

    Rule 5 (blogspam and rehosted content)

    • We require the original source unless the article adds substantial information or the original isn't in English. Should we relax this?

    Most people said no (62%). This is already what we're doing, but we heavily rely on your reports to enforce this.

    • What about articles that cover the same topic when an original source has been submitted?

    Most people voted to only allow these if they add substantial information (68%). I think this is an area we can work on.

    Rumors

    • Should we allow rumor threads on r/Android?

    40% say yes, 34% want it in a weekly thread only, and another 27% want it to be more restricted. We really should've used preferential voting. The plan is to gather some feedback in this thread and probably make a new poll with preferential voting in a week or two.

    • Should we allow phone renders based on rumors?

    Most people say yes (62%). This is already what's happening.

    (I was expecting completely different results on this one based on the usual complaints we see.)

    • Should we ban websites with a track record of false rumors?

    A crushing 91% say yes. We'll be setting up a wiki page soon which we'll maintain based on your reports, and use it to enforce this. The wiki page will be editable by mods only as we don't see how else we'd do it, but everyone will be able to check it out and see false rumors, the corresponding Reddit link, and a note/link explaining how it was false.

    For reports, we will most likely go with a Google Form (linked in the sidebar). While we would've preferred normal reports, it is unfortunately much harder to maintain because we can't really keep track of past reports (if one of us actions a reported thread, the reports disappear until the thread is reported again... This is also true for the API). Using a Google Form should also be easier than Modmail, which a lot of mobile apps don't support very well.

    This will only apply to submissions posted on r/Android to keep it manageable. We'll be relying very heavily on your reports to enforce this.

    • After how many false rumors should we ban a website?

    56% say after 3 false rumors in a year.

    • How long should a website be banned for?

    Most people voted for "Until the website owners appeal and show that they've taken steps not to publish unverified rumors" (53%).

    Sticky and weekly threads

    • Should we have a permanent sticky thread for tech support, device recommendations and general questions/discussions?

    Most people (64%) think the existing threads are enough.

    • Should we have a weekly thread for sharing Swappa/eBay/etc listings, to facilitate phone sales and swaps?

    Most people say no (62%).

    • For the Saturday APPreciation thread, should we require providing a recommendation along with requests?

    Most people say no (56%).

    That being said, we really encourage you to please do so. <3

    Submissions & comments quality

    • Should we remove "circlejerk"/low-effort comments? (e.g. "headphone jack bad", "X and Y, name a better duo", etc)

    Most people say yes (63%).

    This will hopefully lead to a higher quality of comments just by driving down the noise and therefore discouraging people from repeating the same circlejerky comments.

    Please let us know which are the worst offenders in your opinion. We're also not sure about the best approach to implement this, so suggestions are also welcome.

    (P.S. You might be interested in r/androidcirclejerk.)

    • Sometimes posts that break our rules gain popularity and discussion before we catch them (~200+ up votes/100+ comments). We currently keep them up in order not to remove discussion, but add a flair or leave a comment explaining this. Should we keep doing this?

    Most people said yes (83%).

    • Should we require Twitter posts to be self-text posts with some context added if necessary?

    Most people said yes (71%). We shall be enforcing this starting now via AutoMod.

    • Should we require comments to have at least X characters?

    Most people said no.

    • Should we require new self-posts to have at least X characters?

    Most people said yes (57% across categories), but there is no clear agreement on how strict it should be. We'll start by enforcing the minimum proposed limit via AutoMod (>20 characters i.e. ~4 words), but we'll also be including this in the next poll.

    What's next?

    We'll gather your feedback here and have a new poll in the coming few weeks as noted above (and with any additional feedback you might have here). We'll likely only run the next polls for a couple of weeks at a time, as we noticed we got most responses during that time.

    Thanks!
    ­— The r/Android mod team

    submitted by /u/GermainZ
    [link] [comments]

    Something interesting about the Shield Controller connected to the phone

    Posted: 29 Jan 2020 07:59 AM PST

    So I just tried to connect my Shield Controller to my Pixel 4 through a USB cable and found out some interesting things:

    • the headphone jack doesn't work (you can't listen to the game's soundtrack, music nor audiobooks)

    • the home button does bring you back to the home screen, but it can't enable multitasking

    • the microphone button actually works!:

      • press it once to open the Google search bar or search things on your currently open app (does work with Reddit, for example!)
      • press it again to close the search bar
      • hold it to activate the Google Assistant

    • when selecting a Widget, the phone tries to move it and enables the old home screen options. However, the Controller is unable to do anything on that screen, besides returning to the home menu again.

    • the Controller is unable to open the App List, since the Pixel Launcher doesn't seem to have a dedicated button for that (at least with gestures activated, instate of the usual three button system)

    Android is poorly optimized for Controller controls, so it was really interesting to see that, although the headphone jack didn't work, the microphone button was fully supported and even gave some new features, that can't otherwise be accessed without it!

    I really hope that support for the Stadia Controller comes soon, so we can use it wirelessly on our Android phones, that all of it's buttons get fully utilized (Assistant, Screenshot and maybe new features with the other buttons, activating multitasking for example) and that it also allows us to use the headphone jack of that Controller!

    submitted by /u/Sonicjan
    [link] [comments]
    Read more
    at

    No comments:

    Post a Comment